Upload
others
View
3
Download
0
Embed Size (px)
Citation preview
ETSI ETR 285
TECHNICAL March 1996
REPORT
Source: ETSI TC-SPS Reference: DTR/SPS-01030
ICS: 33.080
Key words: ISDN, supplementary service
Integrated Services Digital Network (ISDN);User-to-User Signalling (UUS) supplementary service;
Functional capabilities and information flows
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [email protected]
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1996. All rights reserved.
Page 2ETR 285: March 1996
Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.
Page 3ETR 285: March 1996
Contents
Foreword .......................................................................................................................................................5
1 Scope ..................................................................................................................................................7
2 Normative references..........................................................................................................................7
3 Definitions............................................................................................................................................8
4 Abbreviations.......................................................................................................................................8
5 Description ..........................................................................................................................................9
6 Derivation of the functional model .....................................................................................................106.1 Functional model description .............................................................................................106.2 Description of functional entities ........................................................................................106.3 Relationship with the basic service ....................................................................................10
7 Information flows ...............................................................................................................................107.1 Information flow diagrams..................................................................................................10
7.1.1 Service 1 .......................................................................................................117.1.2 Service 2 .......................................................................................................157.1.3 Service 3 .......................................................................................................16
7.2 Definition of individual information flows............................................................................187.2.1 Relationship ra ..............................................................................................18
7.2.1.1 SERVICE 1 ..........................................................................187.2.1.2 SERVICE 1 REJECTED......................................................187.2.1.3 SERVICE 2 ..........................................................................187.2.1.4 SERVICE 2 REJECTED......................................................187.2.1.5 SERVICE 3 ..........................................................................197.2.1.6 SERVICE 1 REJECTED......................................................197.2.1.7 DATA UNIT..........................................................................197.2.1.8 FLOW CONTROL ...............................................................19
7.2.2 Relationship rb ..............................................................................................207.2.2.1 SERVICE 1 ..........................................................................207.2.2.2 SERVICE 1 REJECT...........................................................207.2.2.3 SERVICE 2 ..........................................................................207.2.2.4 SERVICE 2 REJECT...........................................................207.2.2.5 SERVICE 3 ..........................................................................207.2.2.6 SERVICE 3 REJECT...........................................................207.2.2.7 DATA UNIT..........................................................................20
7.2.3 Relationship rc...............................................................................................207.2.3.1 SERVICE 1 ..........................................................................207.2.3.2 SERVICE 1 REJECTED......................................................207.2.3.3 SERVICE 2 ..........................................................................207.2.3.4 SERVICE 2 REJECTED......................................................217.2.3.5 SERVICE 3 ..........................................................................217.2.3.6 SERVICE 1 REJECTED......................................................217.2.3.7 DATA UNIT..........................................................................217.2.3.8 FLOW CONTROL ...............................................................21
8 SDL diagrams for functional entities .................................................................................................218.1 SDL diagrams for FE1 .......................................................................................................22
8.1.1 Service 1 .......................................................................................................228.1.2 Service 2 .......................................................................................................258.1.3 Service 3 .......................................................................................................28
Page 4ETR 285: March 1996
8.2 SDL diagrams for FE2....................................................................................................... 318.2.1 Service 1....................................................................................................... 318.2.2 Service 2....................................................................................................... 348.2.3 Service 3....................................................................................................... 38
8.3 SDL diagrams for FE3....................................................................................................... 418.3.1 Service 1....................................................................................................... 418.3.2 Service 2....................................................................................................... 448.3.3 Service 3....................................................................................................... 48
8.4 SDL diagrams for FE4....................................................................................................... 518.4.1 Service 1....................................................................................................... 518.4.2 Service 2....................................................................................................... 548.4.3 Service 3....................................................................................................... 57
9 Functional Entity Actions (FEAs) ...................................................................................................... 609.1 FEAs of FE1...................................................................................................................... 609.2 FEAs of FE2...................................................................................................................... 609.3 FEAs of FE3...................................................................................................................... 609.4 FEAs of FE4...................................................................................................................... 60
10 Allocation of functional entities to physical locations ........................................................................ 61
History ......................................................................................................................................................... 62
Page 5ETR 285: March 1996
Foreword
This ETSI Technical Report (ETR) has been produced by the Signalling Protocols and Switching (SPS)Technical Committee of the European Telecommunications Standards Institute (ETSI).
ETRs are informative documents resulting from ETSI studies which are not appropriate for EuropeanTelecommunication Standard (ETS) or Interim European Telecommunication Standard (I-ETS) status. AnETR may be used to publish material which is either of an informative nature, relating to the use or theapplication of ETSs or I-ETSs, or which is immature and not yet suitable for formal adoption as an ETS oran I-ETS.
In accordance with CCITT Recommendation I.130, the following three level structure is used to describethe supplementary telecommunications services as provided by European public telecommunicationsoperators under the pan-European Integrated Services Digital Network (ISDN):
- Stage 1: is an overall service description, from the user's standpoint;
- Stage 2: identifies the functional capabilities and information flows needed to support the servicedescribed in stage 1; and
- Stage 3: defines the signalling system protocols and switching functions needed to implement theservice described in stage 1.
This ETR details the stage 2 aspects (functional capabilities and information flows) needed to support theUser-to-User Signalling (UUS) supplementary service. The stage 1 and stage 3 aspects are detailed inETS 300 284 and ETS 300 286-1, respectively.
Page 6ETR 285: March 1996
Blank page
Page 7ETR 285: March 1996
1 Scope
This ETSI Technical Report (ETR) defines the stage two for the User-to-User Signalling (UUS)supplementary service of the pan-European Integrated Services Digital Network (ISDN) as provided byEuropean public telecommunications operators. Stage two identifies the functional capabilities and theinformation flows needed to support the service description. The stage two description also identifies useroperations not directly associated with a call (see CCITT Recommendation I.130 [2]).
NOTE: This stage 2 description reflects a premature status of the UUS supplementaryservice, i.e. the functional capabilities and information flows are not complete and maynot be in full alignment with the corresponding stage 1 and stage 3 descriptions.
This ETR is specified according to the methodology specified in CCITT Recommendation Q.65 [4].
This ETR does not formally describe the relationship between this supplementary service and the basiccall but, where possible this information is included for guidance.
In addition this ETR does not specify the requirements where the service is provided to the user via aprivate ISDN. This ETR does not specify the requirements for the allocation of defined functional entitieswithin a private ISDN; it does however, define which functional entities may be allocated to a private ISDN.
This ETR does not specify the additional requirements where the service is provided to the user via atelecommunications network that is not an ISDN.
The UUS supplementary service enables a user to send/receive a limited amount of information to/fromanother user over the signalling channel in association with a call to the other user.
The UUS supplementary service is applicable to all circuit-switched telecommunications services.
This ETR is applicable to the stage three standards for the UUS service. The term stage three is alsodefined in CCITT Recommendation I.130 [2]. Where the text indicates the status of a requirement, i.e. astrict command or prohibition, as authorisation leaving freedom, as capability or possibility, this shall bereflected in the text of the relevant stage three standard.
Furthermore, conformance to this ETR is met by conforming to the stage three standards with the field ofapplication appropriate to the equipment being implemented. Therefore, no method of testing is providedfor this ETR.
2 Normative references
This ETR incorporates by dated and undated reference, provisions from other publications. Thesereferences are cited at the appropriate places in the text and the publications are listed hereafter. Fordated references, subsequent amendments to or revisions of any of these publications apply to this ETRonly when incorporated in it by amendment or revision. For undated references the latest edition of thepublication referred to applies.
[1] ITU-T Recommendation I.112 (1993): "Vocabulary of terms of ISDN".
[2] CCITT Recommendation I.130 (1988): "Method for the characterisation oftelecommunication services supported by an ISDN and network capabilities ofan ISDN".
[3] ITU-T Recommendation I.210 (1993): "Principles of telecommunication servicessupported by an ISDN and the means used to describe them".
[4] CCITT Recommendation Q.65 (1988): "Stage 2 of the method for thecharacterisation of services supported by an ISDN".
Page 8ETR 285: March 1996
[5] CCITT Recommendation Q.71 (1988): "ISDN 64 kbit/s circuit mode switchedbearer service".
[6] CCITT Recommendation Z.100 (1988): "Specification and DescriptionLanguage (SDL)".
3 Definitions
For the purposes of this ETR, the following definitions apply:
data unit: A unit of UUI to be transferred at any instance by the UUS supplementary service.
explicit request: The UUS supplementary service is considered as explicitly requested when a userrequests the activation of the UUS supplementary service.
implicit request: The UUS supplementary service is considered as implicitly requested when no explicitrequest for the UUS supplementary service is made and UUI is sent by the user when originating a call.
Integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [1], definition 308.
point-to-multipoint configuration: A situation where multiple responses to an incoming call can occur.
point-to-point configuration: A situation where multiple responses to an incoming call cannot occur.
service; telecommunication service: See ITU-T Recommendation I.112 [1], definition 201.
service 1: A form of the UUS supplementary service where UUI can be sent and received during theorigination and termination of calls.
service 2: A form of the UUS supplementary service where UUI can be sent and received after the callinguser has received an indication that the called user is being informed of the call and prior to theestablishment of the connection.
service 3: A form of the UUS supplementary service where UUI can be sent and received only while theconnection is established.
supplementary service: See ITU-T Recommendation I.210 [3], subclause 2.4.
"UUS not required" request: A request where originating a call shall continue even if the request for theUUS supplementary service cannot be accepted.
"UUS required" request: A request where originating a call shall be rejected if the request for the UUSsupplementary service cannot be accepted.
4 Abbreviations
For the purposes of this ETR, the following abbreviations apply:
FEA Functional Entity ActionISDN Integrated Services Digital NetworkLE Local ExchangePTNX Private Telecommunication Network ExchangeSDL Specification and Description LanguageTE Terminal EquipmentUUI User-to-User InformationUUS User-to-User Signalling
Page 9ETR 285: March 1996
5 Description
The user can transfer User-to-User Information (UUI) data units in different phases of the call dependingon the service(s) to which the user subscribes. These are:
Service 1: the UUI data units are transferred during the setup and clearing phases of the call inassociation with basic call information flows (see CCITT Recommendation Q.71 [5]);
Service 2: the UUI data units are transferred during the alerting phase of the call (i.e. after REPORT(alerting) req.ind and before SETUP resp.conf) independently of the call messages. Twodedicated UUI data units can be transmitted in each direction;
Service 3: the UUI data units are transferred during the active phase of the call (i.e. after SETUPresp.conf) independently of the call control messages. The necessary limitation of the amountof UUI service 3 can be placed on the number of UUI data units transmitted or the throughputcan be limited (network option).
Service 1, service 2 and service 3 allow the transmission of 128 octets per message as a maximum.
Service 1 and service 2 shall be requested by the calling user at the setup of the call, if UUI data units isdesired in either direction. Service 3 may be requested by the calling user at the setup or during the activephase of the call. As a service provider option, service 3 can be requested by the called user only duringthe active phase of the call.
Service 2 and service 3 shall be explicitly requested. Service 1 may be implicitly or explicitly requested.The service is implicitly requested when UUI data units are included in the call request (i.e. the service isrequested at the same time it is invoked).
At the call setup, the calling user can request service 1, service 2 and service 3 as "UUS required" and ifUUI data units cannot be passed then the call is cleared. If service 3 is requested during the call, it cannotbe requested as "UUS required".
For service 2 and service 3 the network shall confirm the request for the UUS supplementary service. Thisconfirmation is preceded by an end-to-end check by the network for service availability.
When service 1 is explicitly requested, the network shall inform the remote user of the request. Theremote user shall accept or reject the activation as described for service 2 and service 3.
For service 2 and service 3 the network shall interrogate the destination user for the service availability.No response from the destination user is taken by the network as a rejection of the UUS supplementaryservice request. The network shall explicitly indicate to the originating user whether the requested servicehas been successfully activated or not. In the case of unsuccessful activation, the network shall indicatewhether this condition is due to the destination user or not.
When service 1 is explicitly requested, the network shall inform the destination user of the request. Thedestination party shall accept or reject the activation as described for service 2 and service 3.
Page 10ETR 285: March 1996
6 Derivation of the functional model
6.1 Functional model description
The functional model for the UUS supplementary service is shown in figure 1.
ÚÄÄÄ¿ ra ÚÄÄÄ¿ rb ÚÄÄÄ¿ rc ÚÄÄÄ¿³FE1ÃÄÄÄÄÄÄÄÄ´FE2ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´FE3ÃÄÄÄÄÄÄÄÄ´FE4³ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ
Figure 1: Functional model
6.2 Description of functional entities
The functional entities required for the UUS supplementary service above those of basic call are:
FE1: Requesting user's agent;FE2: Requesting control entity;FE3: Responding control entity;FE4: Responding user's agent.
6.3 Relationship with the basic service
The relationship of the UUS supplementary service with the basic service is shown in figure 2.
NOTE: The basic call model is defined in CCITT Recommendation Q.71 [5], § 3.2.1 with theexception that r1 represents an outgoing call relationship from a CCA and r3 representsan incoming call relationship to a CCA.
ÚÄÄÄ¿ ra ÚÄÄÄ¿ rb ÚÄÄÄ¿ rc ÚÄÄÄ¿³FE1ÃÄÄÄÄÄÄÄÄ´FE2ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´FE3ÃÄÄÄÄÄÄÄÄ´FE4³ÃÄÄÄ´ r1 ÃÄÄÄ´ r2 ÚÄÄÄ¿ r2 ÃÄÄÄ´ r3 ÃÄÄÄ´³CCAÃÄÄÄÄÄÄÄÄ´CC ÃÄÄÄÄÄÄÄÄ´CC ÃÄÄÄÄÄÄÄÄ´CC ÃÄÄÄÄÄÄÄÄ´CCA³ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ
Figure 2: Relationship between the UUS supplementary service and the basic service
7 Information flows
7.1 Information flow diagrams
Figures 3 to 6 are related to service 1, figure 7 is related to service 2 and figures 8 and 9 are related toservice 3.
Page 11ETR 285: March 1996
7.1.1 Service 1 rc Ú-----------------------------------¿ | | ÚÄÄÄÄÄ¿ ra ÚÄÄÄÄÄ¿ rb ÚÄÄÄÄÄ¿ rc ÚÄÄÄÄÄ¿ ÚÄÄÄÄÄ¿ ³ FE1 ³--------------³ FE2 ³--------------³ FE3 ³--------------³ FE4 ³ ³ FE4 ³ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ³ ³ SETUP ³ ³ ³ ³ ³ ³ ³ ³ SERVICE 1 ³ ³ |----->| ³ ³ ³ ³ ³ ³ ³ ³ ÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ req.ind ³ ³ ³ ³ ³ ³ ³ ³ req. ³911³ ³ ³ SETUP ³ ³ ³ ³ ³ ³ ³912³ DATA UNIT ³ ³ |----->| ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ req.ind ³ ³ ³ ³ ³ ³ ³ ³ req.ind ³921³ ³ ³ SETUP ³ ³ ³ ³ ³ ³ ³922³ DATA UNIT ³ ³ |----->| ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ req.ind ³ ³ ³ ³ ³ ³ ³ ³ req.ind ³931³ ³ ³ ³ ³ ³ ³ ³ ³ ³932³ DATA UNIT ³ ³ ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ ³ ³ req.ind ³941³ ³ ³ ³ ³ ³ ³ ³ ³ ³942³ ³ ³ SERVICE 1 ³ ³ ³ ³ ³ ³ SETUP ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ÃÄÄÄÄÄÄÄÄÄÄÄ> ³ ³ ³ ³ ³ ³ |----->| ³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ req.ind ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ DATA UNIT ³ ³ ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ÃÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³ ³ ³941³ ³ ³ ³ ³ ³ ³ ³ ³ ³942³ SERVICE 1 ³ ³ ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ> ³ ³ ³ ³ ³ ³REPORT(alerting)³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ |<-----| ³ ³ ³ ³ ³ ³ ³ ³REPORT(alerting)³ ³ req.ind ³ ³ ³ ³ DATA UNIT ³ ³ ³ ³ |<-----| ³ ³ ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄ´ ÃÄÄÄÄÄÄÄÄÄÄÄÄ ³ ³REPORT(alerting)³ ³ req.ind ³ ³ DATA UNIT ³942³ ³ ³ resp. ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ req.ind ³ ³ DATA UNIT ³932³ req.ind ³ ³ ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ DATA UNIT ³922³ req.ind ³ ³REPORT(alerting)³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ |<-----| ³ ³ ³ ³ DATA UNIT ³911³ req.ind ³ ³ ³ ³ req.ind ³ ³ ³ ³ DATA UNIT<ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄconf. ³ ³ ³ ³ ³ ³ DATA UNIT ³ ³ ³942³ resp. ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ÃÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ SETUP ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ |<-----| ³ ³ ³ ³ ³ ³ ³ ³ SETUP ³ ³ resp.conf ³ ³ ³ ³ DATA UNIT ³ ³ ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄ´ ÃÄÄÄÄÄÄÄÄÄÄÄÄ ³ ³ SETUP ³ ³ resp.conf ³ ³ DATA UNIT ³944³ ³ ³ req. ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ resp.conf ³ ³ DATA UNIT ³934³ req.ind ³ ³ ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ DATA UNIT ³924³ req.ind ³ ³ ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ DISCONNECT ³ ³ ³ ³ DATA UNIT ³914³ req.ind ³ ³ ³ ³ |<-----| ³ ³ ³ ³ <ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ RELEASE ³ ³ req.ind ³ ³ ³ ³ DATA UNITind. ³ ³ ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄ´ ÃÄÄÄÄÄÄÄÄÄÄÄÄ ³ ³ DISCONNECT ³ ³ req.ind ³ ³ DATA UNIT ³944³ ³ ³ req. ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ req.ind ³ ³ DATA UNIT ³934³ req.ind ³ ³ ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ DATA UNIT ³924³ req.ind ³ ³ ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ DATA UNIT ³914³ req.ind ³ ³ ³ ³ ³ ³ ³ ³ <ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ
Figure 3: Service 1 of UUS supplementary service, successful implicit "UUS not required" request, called user is point-to-multipoint
Page 12ETR 285: March 1996
ÚÄÄÄÄÄ¿ ra ÚÄÄÄÄÄ¿ rb ÚÄÄÄÄÄ¿ rc ÚÄÄÄÄÄ¿ ³ FE1 ³--------------³ FE2 ³--------------³ FE3 ³--------------³ FE4 ³ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ³ ³ SETUP ³ ³ ³ ³ ³ ³ SERVICE 1 ³ ³ |----->| ³ ³ ³ ³ ³ ³ ÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ req.ind ³ ³ ³ ³ ³ ³ req. ³911³ ³ ³ SETUP ³ ³ ³ ³ ³912³ DATA UNIT ³ ³ |----->| ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ req.ind ³ ³ ³ ³ ³ ³ req.ind ³921³ ³ ³ SETUP ³ ³ ³ ³ ³922³ DATA UNIT ³ ³ |----->| ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ req.ind ³ ³ ³ ³ ³ ³ req.ind ³931³ ³ ³ ³ ³ ³ ³ ³932³ DATA UNIT ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³941³ ³ ³ ³ ³ ³ ³ ³942³ SERVICE 1 ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ> ³ ³ ³ ³ ³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³REPORT(alerting)³ ³ ³ ³ ³ ³ ³ ³ |<-----| ³ ³ ³ ³ ³ ³REPORT(alerting)³ ³ req.ind ³ ³ DATA UNIT ³ ³ ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄ ³ ³REPORT(alerting)³ ³ req.ind ³ ³ DATA UNIT ³941³ req. ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ req.ind ³ ³ DATA UNIT ³931³ req.ind ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³921³ req.ind ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³911³ req.ind ³ ³ ³ ³ ³ ³ <ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ SETUP ³ ³ ind. ³ ³ ³ ³ ³ ³ |<-----| ³ ³ ³ ³ ³ ³ SETUP ³ ³ resp.conf ³ ³ DATA UNIT ³ ³ ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄ ³ ³ SETUP ³ ³ resp.conf ³ ³ DATA UNIT ³944³ req. ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ resp.conf ³ ³ DATA UNIT ³934³ req.ind ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³924³ req.ind ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³914³ req.ind ³ ³ ³ ³ ³ ³ <ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DISCONNECT ³ ³ ind. ³ ³ ³ ³ ³ ³ |<-----| ³ ³ ³ ³ ³ ³ RELEASE ³ ³ req.ind ³ ³ DATA UNIT ³ ³ ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄ ³ ³ DISCONNECT ³ ³ req.ind ³ ³ DATA UNIT ³944³ req. ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ req.ind ³ ³ DATA UNIT ³934³ req.ind ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³924³ req.ind ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³914³ req.ind ³ ³ ³ ³ ³ ³ <ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ ³ ³ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ
Figure 4: Service 1 of UUS supplementary service, successful implicit "UUS not required" request, called user is point-to-point
Page 13ETR 285: March 1996
ÚÄÄÄÄÄ¿ ra ÚÄÄÄÄÄ¿ rb ÚÄÄÄÄÄ¿ rc ÚÄÄÄÄÄ¿ ³ FE1 ³--------------³ FE2 ³--------------³ FE3 ³--------------³ FE4 ³ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ³ ³ SETUP ³ ³ ³ ³ ³ ³ SERVICE 1 ³ ³ |----->| ³ ³ ³ ³ ³ ³ ÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ req.ind ³ ³ ³ ³ ³ ³ req. ³911³ ³ ³ SETUP ³ ³ ³ ³ ³912³ SERVICE 1 ³ ³ |----->| ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ req.ind ³ ³ ³ ³ ³ ³ req.ind ³921³ ³ ³ SETUP ³ ³ ³ ³ ³922³ SERVICE 1 ³ ³ |----->| ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ req.ind ³ ³ ³ ³ ³ ³ req.ind ³931³ ³ ³ ³ ³ ³ ³ ³932³ SERVICE 1 ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³941³ ³ ³ ³ ³ ³ ³ ³942³ SERVICE 1 ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ> ³ ³ ³ ³ ³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³REPORT(alerting)³ ³ ³ ³ ³ ³ ³ ³ |<-----| ³ ³ ³ ³ ³ ³REPORT(alerting)³ ³ req.ind ³ ³ SERVICE 1 ³ ³ ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄ ³ ³REPORT(alerting)³ ³ req.ind ³ ³ SERVICE 1 ³941³ resp. ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ req.ind ³ ³ SERVICE 1 ³931³ resp.conf ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ SERVICE 1 ³921³ resp.conf ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ SERVICE 1 ³911³ resp.conf ³ ³ ³ ³ ³ ³ <ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ SETUP ³ ³ conf. ³ ³ ³ ³ ³ ³ |<-----| ³ ³ ³ ³ ³ ³ SETUP ³ ³ resp.conf ³ ³ DATA UNIT ³ ³ ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄ ³ ³ SETUP ³ ³ resp.conf ³ ³ DATA UNIT ³944³ req. ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ resp.conf ³ ³ DATA UNIT ³934³ req.ind ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³924³ req.ind ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³914³ req.ind ³ ³ ³ ³ ³ ³ <ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DISCONNECT ³ ³ ind. ³ ³ ³ ³ ³ ³ |<-----| ³ ³ ³ ³ ³ ³ RELEASE ³ ³ req.ind ³ ³ DATA UNIT ³ ³ ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄ ³ ³ DISCONNECT ³ ³ req.ind ³ ³ DATA UNIT ³944³ req. ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ req.ind ³ ³ DATA UNIT ³934³ req.ind ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³924³ req.ind ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³914³ req.ind ³ ³ ³ ³ ³ ³ <ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ ³ ³ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ
Figure 5: Service 1 of UUS supplementary service, successful explicit "UUS required" or "UUS not required" request, called user is point-to-point
Page 14ETR 285: March 1996
rc Ú-----------------------------------¿ | | ÚÄÄÄÄÄ¿ ra ÚÄÄÄÄÄ¿ rb ÚÄÄÄÄÄ¿ rc ÚÄÄÄÄÄ¿ ÚÄÄÄÄÄ¿ ³ FE1 ³--------------³ FE2 ³--------------³ FE3 ³--------------³ FE4 ³ ³ FE4 ³ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ³ ³ SETUP ³ ³ ³ ³ ³ ³ ³ ³ SERVICE 1 ³ ³ |----->| ³ ³ ³ ³ ³ ³ ³ ³ ÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ req.ind ³ ³ ³ ³ ³ ³ ³ ³ req. ³911³ ³ ³ SETUP ³ ³ ³ ³ ³ ³ ³912³ SERVICE 1 ³ ³ |----->| ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ req.ind ³ ³ ³ ³ ³ ³ ³ ³ req.ind ³921³ ³ ³ SETUP ³ ³ ³ ³ ³ ³ ³922³ SERVICE 1 ³ ³ |----->| ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ req.ind ³ ³ ³ ³ ³ ³ ³ ³ req.ind ³931³ ³ ³ ³ ³ ³ ³ ³ ³ ³932³ SERVICE 1 ³ ³ ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ ³ ³ req.ind ³941³ ³ ³ ³ ³ ³ ³ ³ ³ ³942³ ³ ³ SERVICE 1 ³ ³ ³ ³ ³ ³ SETUP ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄ´ ÃÄÄÄÄÄÄÄÄÄÄÄ> ³ ³ ³ ³ ³ ³ |----->| ³ ³ ³ ³ ³ ³ ³ ³ ³ ´ req.ind ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ SERVICE 1 ³ ³ ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ÃÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³ ³ ³941³ ³ ³ ³ ³ ³ ³ ³ ³ ³942³ SERVICE 1 ³ ³ ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ> ³ ³ ³ ³ ³ ³REPORT(alerting)³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ |<-----| ³ ³ ³ ³ ³ ³ ³ ³REPORT(alerting)³ ³ req.ind ³ ³ ³ ³ SERVICE 1 ³ ³ ³ ³ |<-----| ³ ³ ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄ´ ÃÄÄÄÄÄÄÄÄÄÄÄÄ ³ ³REPORT(alerting)³ ³ req.ind ³ ³ SERVICE 1 ³942³ ³ ³ resp. ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄ¿ ³ ³ ³ ³ req.ind ³ ³ SERVICE 1 ³932³ resp.conf ³ ³ ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ SERVICE 1 ³922³ resp.conf ³ ³REPORT(alerting)³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ |<-----| ³ ³ ³ ³ SERVICE 1 ³911³ resp.conf ³ ³ Ã Å req.ind ³ Ã ³ ³ SERVICE 1<ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄconf. ³ ³ ³ ³ ³ ³ SERVICE 1 ³ ³ ³942³ resp. ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ÃÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ resp.conf ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ SETUP ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ |<-----| ³ ³ ³ ³ ³ ³ ³ ³ SETUP ³ ³ resp.conf ³ ³ ³ ³ DATA UNIT ³ ³ ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄ´ ÃÄÄÄÄÄÄÄÄÄÄÄÄ ³ ³ SETUP ³ ³ resp.conf ³ ³ DATA UNIT ³944³ ³ ³ req. ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ resp.conf ³ ³ DATA UNIT ³934³ req.ind ³ ³ ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ DATA UNIT ³924³ req.ind ³ ³ ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ DISCONNECT ³ ³ ³ ³ DATA UNIT ³914³ req.ind ³ ³ ³ ³ |<-----| ³ ³ ³ ³ <ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ RELEASE ³ ³ req.ind ³ ³ ³ ³ DATA UNITind. ³ ³ ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄ´ ÃÄÄÄÄÄÄÄÄÄÄÄÄ ³ ³ DISCONNECT ³ ³ req.ind ³ ³ DATA UNIT ³944³ ³ ³ req. ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ req.ind ³ ³ DATA UNIT ³934³ req.ind ³ ³ ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ DATA UNIT ³924³ req.ind ³ ³ ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ DATA UNIT ³914³ req.ind ³ ³ ³ ³ ³ ³ ³ ³ <ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ
Figure 6: Service 1 of UUS supplementary service, successful explicit "UUS not required" request, called user is point-to-multipoint
Page 15ETR 285: March 1996
7.1.2 Service 2
ÚÄÄÄÄÄ¿ ra ÚÄÄÄÄÄ¿ rb ÚÄÄÄÄÄ¿ rc ÚÄÄÄÄÄ¿ ³ FE1 ³--------------³ FE2 ³--------------³ FE3 ³--------------³ FE4 ³ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ³ ³ SETUP ³ ³ ³ ³ ³ ³ ³ ³ |----->| ³ ³ ³ ³ ³ ³ SERVICE 2 ³ ³ req.ind ³ ³ SETUP ³ ³ ³ ³ ÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ |----->| ³ ³ ³ ³ req. ³911³ SERVICE 2 ³ ³ req.ind ³ ³ SETUP ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ |----->| ³ ³ ³ ³ req.ind ³921³ SERVICE 2 ³ ³ req.ind ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³931³ SERVICE 2 ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³941³ SERVICE 2 ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ> ³ ³ ³ ³ ³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³REPORT(alerting)³ ³ ³ ³ ³ ³ ³ ³ |<-----| ³ ³ ³ ³ ³ ³REPORT(alerting)³ ³ req.ind ³ ³ SERVICE 2 ³ ³ ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄ ³ ³REPORT(alerting)³ ³ req.ind ³ ³ SERVICE 2 ³941³ resp. ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ req.ind ³ ³ SERVICE 2 ³931³ resp.conf ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ SERVICE 2 ³921³ resp.conf ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ SERVICE 2 ³911³ resp.conf ³ ³ ³ ³ ³ ³ <ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ conf. ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ DATA UNIT ³ ³ ³ ³ ³ ³ ³ ³ ÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req. ³913³ DATA UNIT ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³923³ DATA UNIT ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³933³ DATA UNIT ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³943³ DATA UNIT ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ> ³ ³ ³ ³ ³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ DATA UNIT ³ ³ ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄ ³ ³ ³ ³ ³ ³ DATA UNIT ³943³ req. ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³933³ req.ind ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³923³ req.ind ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³913³ req.ind ³ ³ ³ ³ ³ ³ <ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ ³ ³ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ
Figure 7: Service 2 of UUS supplementary service, successful "UUS required" or "UUS not required" request, called user is point-to-point
Page 16ETR 285: March 1996
7.1.3 Service 3
ÚÄÄÄÄÄ¿ ra ÚÄÄÄÄÄ¿ rb ÚÄÄÄÄÄ¿ rc ÚÄÄÄÄÄ¿ ³ FE1 ³--------------³ FE2 ³--------------³ FE3 ³--------------³ FE4 ³ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ³ ³ SETUP ³ ³ ³ ³ ³ ³ ³ ³ |----->| ³ ³ ³ ³ ³ ³ SERVICE 3 ³ ³ req.ind ³ ³ SETUP ³ ³ ³ ³ ÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ |----->| ³ ³ ³ ³ req. ³911³ SERVICE 3 ³ ³ req.ind ³ ³ SETUP ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ |----->| ³ ³ ³ ³ req.ind ³921³ SERVICE 3 ³ ³ req.ind ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³931³ SERVICE 3 ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³941³ SERVICE 3 ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ> ³ ³ ³ ³ ³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ SETUP ³ ³ ³ ³ ³ ³ ³ ³ |<-----| ³ ³ ³ ³ ³ ³ SETUP ³ ³ resp.conf ³ ³ SERVICE 3 ³ ³ ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄ ³ ³ SETUP ³ ³ resp.conf ³ ³ SERVICE 3 ³941³ resp. ³ ³ |<-----| ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ resp.conf ³ ³ SERVICE 3 ³931³ resp.conf ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ SERVICE 3 ³921³ resp.conf ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ SERVICE 3 ³911³ resp.conf ³ ³ ³ ³ ³ ³ <ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ conf. ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ DATA UNIT ³ ³ ³ ³ ³ ³ ³ ³ ÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req. ³914³ ³ ³ ³ ³ ³ ³ Ã915Å DATA UNIT Å ´ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³924³ DATA UNIT ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³934³ DATA UNIT ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³944³ DATA UNIT ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ> ³ ³ ³ ³ ³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ DATA UNIT ³ ³ ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄ ³ ³ ³ ³ ³ ³ ³944³ req. ³ ³ ³ ³ ³ ³ DATA UNIT ³945³ ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³934³ req.ind ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³924³ req.ind ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³914³ req.ind ³ ³ ³ ³ ³ ³ <ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ ³ ³ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ
Figure 8: Service 3 of UUS supplementary service, successful "UUS required" or "UUS not required" request
Page 17ETR 285: March 1996
ÚÄÄÄÄÄ¿ ra ÚÄÄÄÄÄ¿ rb ÚÄÄÄÄÄ¿ rc ÚÄÄÄÄÄ¿ ³ FE1 ³--------------³ FE2 ³--------------³ FE3 ³--------------³ FE4 ³ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ ÀÂÄÄÄÂÙ SERVICE 3 ³ ³ ³ ³ ³ ³ ³ ³ ÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req. ³911³ SERVICE 3 ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³921³ SERVICE 3 ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³931³ SERVICE 3 ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³941³ SERVICE 3 ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ> ³ ³ ³ ³ ³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ SERVICE 3 ³ ³ ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄ ³ ³ ³ ³ ³ ³ SERVICE 3 ³941³ resp. ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ SERVICE 3 ³931³ resp.conf ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ SERVICE 3 ³921³ resp.conf ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ SERVICE 3 ³911³ resp.conf ³ ³ ³ ³ ³ ³ <ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ conf. ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ DATA UNIT ³ ³ ³ ³ ³ ³ ³ ³ ÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req. ³914³ ³ ³ ³ ³ ³ ³ ³915³ DATA UNIT ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³924³ DATA UNIT ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³934³ DATA UNIT ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÅÄÄÄ´ ³ ³ ³ ³ ³ ³ req.ind ³944³ DATA UNIT ³ ³ ³ ³ ³ ³ ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ> ³ ³ ³ ³ ³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ ³ DATA UNIT ³ ³ ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄ ³ ³ ³ ³ ³ ³ ³944³ req. ³ ³ ³ ³ ³ ³ DATA UNIT ³945³ ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³934³ req.ind ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³924³ req.ind ³ ³ ³ ³ ÃÄÄÄÅ<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ DATA UNIT ³914³ req.ind ³ ³ ³ ³ ³ ³ <ÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´ ³ ³ ³ ³ ³ ³ ind. ³ ³ ³ ³ ³ ³ ³ ³ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ ÀÄÄÄÙ
NOTE: For the UUS supplementary service, the requesting user agent is always FE1. For a request during the active phase of basic call, FE1 is located at the callingside, or as a network option, at the called side.
Figure 9: Service 3 of UUS supplementary service, successful "UUS required" or "UUS not required" request
Page 18ETR 285: March 1996
7.2 Definition of individual information flows
7.2.1 Relationship ra
7.2.1.1 SERVICE 1
The SERVICE 1 information flow is used to request and respond to the activation of service 1 of the UUSsupplementary service.
The contents of the SERVICE 1 information flow are as contained in table 1.
Table 1: SERVICE 1 information flow
Parameter Value req.ind resp.confForm - UUS request required M
- UUS request not required
7.2.1.2 SERVICE 1 REJECTED
The contents of the SERVICE 1 REJECTED information flow are as contained in table 2.
Table 2: SERVICE 1 REJECTED information flow
Parameter Value req.indReason - rejected by user M
- rejected by network
7.2.1.3 SERVICE 2
The SERVICE 2 information flow is used to request and respond to the activation of service 2 of the UUSsupplementary service.
The contents of the SERVICE 2 information flow are as contained in table 3.
Table 3: SERVICE 2 information flow
Parameter Value req.ind resp.confForm - UUS request required M
- UUS request not required
7.2.1.4 SERVICE 2 REJECTED
The contents of the SERVICE 2 REJECTED information flow are as contained in table 4.
Table 4: SERVICE 2 REJECTED information flow
Parameter Value req.indReason - rejected by user M
- rejected by network
Page 19ETR 285: March 1996
7.2.1.5 SERVICE 3
The SERVICE 3 information flow is used to request and respond to the activation of service 3 of the UUSsupplementary service.
The contents of the SERVICE 3 information flow are as contained in table 5.
Table 5: SERVICE 3 information flow
Parameter Value req.ind resp.confForm - UUS request required M
- UUS request not requiredNOTE: The value "UUS request required" shall only be used in conjunction with a request at call
establishment.
7.2.1.6 SERVICE 1 REJECTED
The contents of the SERVICE 1 REJECTED information flow are as contained in table 6.
Table 6: SERVICE 3 REJECTED information flow
Parameter Value req.indReason - rejected by user M
- rejected by network
7.2.1.7 DATA UNIT
The DATA UNIT information flow is used to transfer data during the invocation for all three services of theUUS supplementary service.
The contents of the DATA UNIT information flow are as contained in table 7.
Table 7: DATA UNIT information flow
Parameter Value req.indUser protocol identifier MData O (NOTE 2)More data O (NOTE 1)NOTE 1: Parameter is included for service 3 only.NOTE 2: Mandatory except in the case of a service 1 implicit request.
7.2.1.8 FLOW CONTROL
The FLOW CONTROL information flow is used to indicate to the user agent the need to restrict the flow ofdata during service 3 of the UUS supplementary service.
The contents of the FLOW CONTROL information flow are as contained in table 8.
Table 8: FLOW CONTROL information flow
Parameter Value req.indStatus - On M
- Off
Page 20ETR 285: March 1996
7.2.2 Relationship rb
7.2.2.1 SERVICE 1
The meaning and contents of the SERVICE 1 information flow are identical to those for relationship ra asshown in subclause 7.2.1.1.
7.2.2.2 SERVICE 1 REJECT
The meaning and contents of the SERVICE 1 REJECT information flow are identical to those forrelationship ra as shown in subclause 7.2.1.2.
7.2.2.3 SERVICE 2
The meaning and contents of the SERVICE 2 information flow are identical to those for relationship ra asshown in subclause 7.2.1.3.
7.2.2.4 SERVICE 2 REJECT
The meaning and contents of the SERVICE 2 REJECT information flow are identical to those forrelationship ra as shown in subclause 7.2.1.4.
7.2.2.5 SERVICE 3
The meaning and contents of the SERVICE 3 information flow are identical to those for relationship ra asshown in subclause 7.2.1.5.
7.2.2.6 SERVICE 3 REJECT
The meaning and contents of the SERVICE 3 REJECT information flow are identical to those forrelationship ra as shown in subclause 7.2.1.6.
7.2.2.7 DATA UNIT
The meaning and contents of the DATA UNIT information flow are identical to those for relationship ra asshown in subclause 7.2.1.7.
7.2.3 Relationship rc
7.2.3.1 SERVICE 1
The meaning and contents of the SERVICE 1 information flow are identical to those for relationship ra asshown in subclause 7.2.1.1.
7.2.3.2 SERVICE 1 REJECTED
The contents of the SERVICE 1 REJECTED information flow are as contained in table 9.
Table 9: SERVICE 1 REJECTED information flow
Parameter Value req.indReason - rejected by user M
7.2.3.3 SERVICE 2
The meaning and contents of the SERVICE 2 information flow are identical to those for relationship ra asshown in subclause 7.2.1.3.
Page 21ETR 285: March 1996
7.2.3.4 SERVICE 2 REJECTED
The contents of the SERVICE 2 REJECTED information flow are as contained in table 10.
Table 10: SERVICE 2 REJECTED information flow
Parameter Value req.indReason - rejected by user M
7.2.3.5 SERVICE 3
The meaning and contents of the SERVICE 3 information flow are identical to those for relationship ra asshown in subclause 7.2.1.5.
7.2.3.6 SERVICE 1 REJECTED
The contents of the SERVICE 1 REJECTED information flow are as contained in table 11.
Table 11: SERVICE 3 REJECTED information flow
Parameter Value req.indReason - rejected by user M
7.2.3.7 DATA UNIT
The meaning and contents of the DATA UNIT information flow are identical to those for relationship ra asshown in subclause 7.2.1.7.
7.2.3.8 FLOW CONTROL
The meaning and contents of the FLOW CONTROL information flow are identical to those for relationshipra as shown in subclause 7.2.1.8.
8 SDL diagrams for functional entities
All Specification and Description Language (SDL) diagrams for FEs are described according to CCITTRecommendation Z.100 [6].
NOTE: The dotted elements in the following SDL diagrams are part of basic call model definedin CCITT Recommendation Q.71 [5], and are present for information purposes only.
Page 22ETR 285: March 1996
8.1 SDL diagrams for FE1
The SDL diagrams for FE1 are shown in figures 10, 11 and 12.
8.1.1 Service 1
Process FE1_UUS1 Page_1(3)
clear_on_fail:= false
UUS1Idle
SERVICE 1ind.
implicit
"include datain request"
data : ="required UU1 data"
DATA UNITreq.ind (data) ra
UUS1Active
data : ="null data"
form
"include datain request"
SERVICEreq.ind(form) (data)
UUS1Requested
ra
data :="required UUI data"
Clear_on_fail:= true
user
YES
NO
YESNO
preferred
No
Yes
required
Figure 10 (sheet 1 of 3)
Page 23ETR 285: March 1996
Process FE1_UUS1 Page_2(3)
UUS1Requested
basic callcleared
clearing fornormal basiccall reasons
from basic call
SERVICE 1REJECTreq. ind.reason
ra
SERVICE 1REJECTind.
user
Clear-on-fail
clearbasic call to basic call
basic callconnectedfrom basic call
SERVICE 1REJECTind.
user
clear-on-fail
clear basic call
to basiccall
SERVICE 1resp.conf(data)
ra
"data included"
SERVICE 1conf.user
UUS 1active
send data to user
TRUE
FALSE
TRUE
FALSE
No
Yes
Figure 10 (sheet 2 of 3)
Page 24ETR 285: March 1996
Process FE1_UUS1 Page_3(3)
UUS1Active
DATA UNITreq.ind(data)
DATA UNITind.
UUS1Active
user
raDATA UNITreq.user
Data: ="required UU1 data"
DATA UNITreq.ind(data)
UUS1Active
ra
basic callcleared
from basiccall
Figure 10 (sheet 3 of 3)
Page 25ETR 285: March 1996
8.1.2 Service 2
Process FE1_UUS2 Page_1(3)
Clear_on_fail:= false
UUS2Idle
SERVICE 2ind.
form
clear_on_fail:= true
SERVICE 2req.ind(form)
ra
UUS2Requested
user
required
preferred
Figure 11 (sheet 1 of 3)
Page 26ETR 285: March 1996
Process FE1_UUS2 Page_2(3)
UUS2Requested
SERVICE 2REJECTreq.ind(reason)
SERVICE 2 REJECTind.
user
Clear-on-fail
Clear basic call to basic call
ra
SERVICE 2resp.conf
SERVICE 2conf.user
UUS2Active
ra
basic callalertingfrom basic call
basic callcleared from basic call
TRUE
FALSE
Figure 11 (sheet 2 of 3)
Page 27ETR 285: March 1996
Process FE1_UUS2 Page_3(3)
UUS2Active
DATA UNITreq. ind.(data)(more_data)
ra
DATA UNITind. user
UUS1Active
DATA UNITreq.
Data :="Required UUI data"
indicatemore data
DATA UNITreq.ind(data)(more_data)
ra
UUS1Active
more_data:= true
userbasic call cleared from basic call
No
Yes
Figure 11 (sheet 3 of 3)
Page 28ETR 285: March 1996
8.1.3 Service 3
Process FE1_UUS3 Page_1(3)
Clear_on_fail:= true
UUS3Idle
SERVICE 3ind.
form
request withSETUPreq.ind
SET (NOW +UUS3 response,
T-UUS3_response)
SERVICE 3req.ind(form)
UUS3Requested
ra
Clear_on_fail: = true
user
preferred
NO
YES
required
Figure 12 (sheet 1 of 3)
Page 29ETR 285: March 1996
Process FE1_UUS3 Page_2(3)
UUS3Requested
T-UUS3response
SERVICE 2 REJECTind.
user
Clear_on_fail
Clear basic call to basic call
SERVICE 3REJECTreq.ind(reason)
rabasic callconnected from basic call
SERVICE 3resp.conf
SERVICE 3conf.user
UUS3Active
ra
basic callcleared from basic call
TRUE
FALSE
Figure 12 (sheet 2 of 3)
Page 30ETR 285: March 1996
Process FE1_UUS3 page_3(3)
UUS3Active
DATA UNITreq.ind(data) (more_data)
DATA UNITind.
UUSActive
user
raDATA UNITreq.
data :="required UUI data"
indicatemore data
DATA UNITreq.ind(data) (more_data)
UUS3Active
more_data:= true
userbasic call cleared
from basiccall
No
Yes
Figure 12 (sheet 3 of 3)
Page 31ETR 285: March 1996
8.2 SDL diagrams for FE2
The SDL diagrams for FE2 are shown in figures 13, 14 and 15.
8.2.1 Service 1
Process FE2_UUS1 page_1(3)
clear_on_fail:= false
UUS1Idle
DATA UNITreq.ind(data)
available
Discarddata
DATA UNITreq.ind(data)
rb
UUS1Active
raSERVICE 1req.ind(data)
available
discarddata
reason :="rejected by the network"
SERVICE 1REJECTreq.ind(reason)
ra
form
Clear basiccall to basic call
form
SERVICE 1req.ind(form) (data)
rb
UUS1Requested
Clear_on_fail:= true
ra
NO
YES
NO
Required
Preferred
Yes
Preferred
Required
Figure 13 (sheet 1 of 3)
Page 32ETR 285: March 1996
Process FE2_UUS1 page_2(3)
UUS1Requested
basiccall cleared
clearing for normal basiccall reasons
from basiccall
basic callconnected
reason :="rejected by the network"
SERVICE 1REJECTreq.ind(reason)
clear_on_fail
clearbasic call
to basiccall
ra
frombasic call
SERVICE 1REJECTreq.ind(reason)
rbSERVICE 1resp.conf(data)
rb
SERVICE 1resp.conf(data)
UUS1Active
ra
True
False
Figure 13 (sheet 2 of 3)
Page 33ETR 285: March 1996
Process FE2_UUS1 page_3(3)
UUS1Active
DATA UNITreq.ind(data)
rb
DATA UNITreq.ind(data)
ra
UUS1Active
DATA UNITreq.ind(data)
ra
DATA UNITreq.ind(data)
rb
UUS1Active
basic callcleared
from basiccall
Figure 13 (sheet 3 of 3)
Page 34ETR 285: March 1996
8.2.2 Service 2
Process FE2_UUS2 page_1(4)
clear_on_fail :=false
UUS2Idle
SERVICE 2req.ind(form)
form
Available
SERVICE 2req.ind(form)
rb
UUS2Requested
reason :="rejected by the network"
SERVICE 2REJECTreq.ind(reason)
rb
clear_on_fail
Clear basiccall to basic call
clear_on_fail :=true
rb
preferred
Yes
No
false
true
required
Figure 14 (sheet 1 of 4)
Page 35ETR 285: March 1996
Process FE2_UUS2 page_2(4)
UUS2Requested
basic callclearing
reason :="rejected bythe network"
SERVICE 2REJECTreq.ind(reason)
ra
clear_on_fail
clearbasic call
to basiccall
from basiccall
basic callalerting
from basiccall
SERVICE 2REJECTreq.ind(reason)
rb
SERVICE 2REJECTreq.ind(reason)
ra
SERVICE 2resp.conf rb
N1 := 2
SERVICE 2resp.confra
UUS2Active
true
false
Figure 14 (sheet 2 of 4)
Page 36ETR 285: March 1996
Process FE2_UUS2 page_3(4)
UUS2Active
DATA UNITreq.ind(data) (more_data)
N1 := N1 - 1
N1 <= 0
Discard(data)
UUS2Active
DATA UNITreq.ind(data) (more_data)
UUS2Active
rb
ra
DATA UNITreq.ind(data)(more_data)
DATA UNITreq.ind(data) (more_data)
ra
UUS2Active
rb basic callconnected
from basiccall
"transfer UUS2in active phase"
UUS2Active (in Connect)
basic callcleared
from basiccall
YesNo
YesNo
Figure 14 (sheet 3 of 4)
Page 37ETR 285: March 1996
Process FE2_UUS2 page_4(4)
UUS2Active (in Connect)
DATA UNITreq.ind(data) (more_data)
N1 := N1 - 1
N1 <= 0
Discard(data)
UUS2Active (in Connect)
DATA UNITreq.ind(data) (more_data)
UUS2Active (in Connect)
rb
ra basic callcleared
from basiccall
YesNo
Figure 14 (sheet 3 of 4)
Page 38ETR 285: March 1996
8.2.3 Service 3
Process FE2_UUS3 Page_1(3)
clear-on-fail : =false
UUS3Idle
SERVICE3req. ind.(form)
form
Available
SERVICE 3req. ind.(form)
requestwith
SETUPreq. ind.
SET (NOW +UUS3 response,
T-UUS3 response)
UUS3requested
rbreason : =
"rejected by thenetwork"
SERVICE 3REJECTreq. ind.(reason)
clear-on-fail
clear basic call to basic call
ra
clear-on-fail : =true
ra
required
YES
NO
YES
NO
false
true
preferred
Figure 15 (sheet 1 of 3)
Page 39ETR 285: March 1996
Process FE2_UUS3 Page_2(3)
UUS3Requested
T-UUS3response
reason : ="rejected by the
network"
SERVICE 3REJECTreq.ind
clear-on-fail
clearbasic call
tobasic call
SERVICE 3REJECTreq.ind
rbbasic callconnected
frombasic call
basic callcleared
frombasic call
SERVICE 3resp.conf
N1 := 16
SET (NOW + 10s,Replenishment)
flow control:= false
UUS3Active
true
false
Figure 15 (sheet 2 of 3)
Page 40ETR 285: March 1996
Process FE2_UUS3 Page_3(3)
UUS3Active
Replenishment
N1 := N1 + 8
N1 >= 16
SET (NOW + 10s,Replenishment)
Flow control:= false
FLOW CONTRreq.ind(off)
UUS3Active
ra
N1 := 16
Basic callcleared
tobasic call
DATA UNITreq.ind rb
DATA UNITreq.ind ra
UUS3Active
DATA UNITreq.ind(data)
N1 > 0
Discard(data)
Congestion
UUS3Active
Flow control := true
FLOW CONTROLreq.ind(on)
UUS3Active
ra
N1 := N1 - 1
DATA UNITreq.ind
UUS3Active
rb
ra
NoYes
Yes
No
Yes
No
Figure 15 (sheet 3 of 3)
Page 41ETR 285: March 1996
8.3 SDL diagrams for FE3
The SDL diagrams for FE3 are shown in figures 16, 17 and 18.
8.3.1 Service 1
Process FE3_UUS1 page_1(3)
clear_on_fail:= false
UUS1Idle
DATA UNITreq.ind(data)
available
Discarddata
DATA UNITreq.ind(data)
rc, to all FE4s
UUS1Active
rbSERVICE 1req.ind(data)
available
reason :="rejected by the
network"
SERVICE 1REJECTreq.ind
rb
form
clearbasic call
to basiccall
form
SERVICE 1req.ind(form) (data)
rc,to all FE4s
UUS1Requested
Clear_on_fail :=true
rb
No
Yes
No
Required
Preferred
Yes
Preferred
Required
Figure 16 (sheet 1 of 3)
Page 42ETR 285: March 1996
Process FE3_UUS1 page_2(3)
UUS1Requested
basiccall to clear tocalling user
stored response
clearing fornormal basiccall reason
reason :=response_reason
SERVICE 1REJECTreq.ind(reason)
rb
from basiccall
basic callconnected
reason :="rejected by the
user"
SERVICE 1REJECTreq.ind(reason)
clear_on_fail
clearbasic call
to basiccall
rb
frombasic call
SERVICE 1REJECTreq.ind(reason)
rcSERVICE 1resp.conf(data)
rc
in first REPORT(alerting)
req.ind
SERVICE 1resp.conf(data)
UUS1Active
rb
in first SETUPresp.conf
SETUP REJECTreq.ind
or DISCONNECTreq.ind
discardresponse
UUS1Requested
higherpriority basic
call reason
store response
UUS1Requested
NO
YES
true
false
Yes
No
Yes
No
No
Yes
No
Yes
Figure 16 (sheet 2 of 3)
Page 43ETR 285: March 1996
Process FE3_UUS1 page_3(3)
UUS1Active
DATA UNITreq.ind(data)
contained inbasic call
information flow
firstREPORT (alerting)
receivedimplicit only
discard data
UUS1Active
DATA UNITreq.ind(data)
rb
UUS1Active
basic callconnected ?
higher prioritybasic call
reason
discard data
UUS1Active
storedata
first SETUPresp.confreceived
implicit only
discard data
UUS1Active
rcDATA UNITreq.ind(data)
rb
DATA UNITreq.ind(data)
rc,to all FE4s
UUS1Active
basic callcleared
stored data
data : =stored data
DATA UNITreq. ind.(data)
from basiccall
REPORT(alerting)req.ind
No
Yes
SETUPREJECTreq.ind orDISCONNECTreq.ind.
Yes
No
No
Yes
SETUPresp.conf
No
Yes
YES
NO
Figure 16 (sheet 3 of 3)
Page 44ETR 285: March 1996
8.3.2 Service 2
Process FE3_UUS2 page_1(4)
clear_on_fail :=false
UUS2Idle
SERVICE 2req.ind(form)
form
Available
SERVICE 2req.ind(form)
rc
UUS2Requested
reason :="rejected by the network"
SERVICE 2REJECTreq.ind(reason)
rb
clear_on_fail
Clear basiccall
to basiccall
clear_on_fail :=true
rb
preferred
Yes
No
false
true
required
Figure 17 (sheet 1 of 4)
Page 45ETR 285: March 1996
Process FE3_UUS2 page_2(4)
UUS2Requested
basic callclearing
reason :="rejected by
the user"
SERVICE 2REJECTreq.ind(reason)
ra
clear_on_fail
clearbasic call
to basiccall
frombasic call
basic callalerting
frombasic call
SERVICE 2REJECTreq.ind(reason)
rb
SERVICE 2REJECTreq.ind(reason)
ra
SERVICE 2resp.conf rb
N1 := 2
SERVICE 2resp.conf ra
UUS2Active
true
false
Figure 17 (sheet 2 of 4)
Page 46ETR 285: March 1996
Process FE3_UUS2 page_3(4)
UUS2Active
DATA UNITreq.ind(data) (more_data)
N1 := N1 - 1
N1 <= 0
Discard(data)
UUS2Active
DATA UNITreq.ind(data) (more_data)
UUS2Active
rb
rc
DATA UNITreq.ind(data)(more_data)
DATA UNITreq.ind(data) (more_data)
rc
UUS2Active
rb basic callconnected
from basiccall
"transfer UUS2in active phase"
UUS2Active (in Connect)
basic callcleared
from basiccall
YesNo
YesNo
Figure 17 (sheet 3 of 4)
Page 47ETR 285: March 1996
Process FE3_UUS2 page_4(4)
UUS2Active (in Connect)
DATA UNITreq.ind(data)(more_data)
DATA UNITreq.ind(data) (more_data)
rc
UUS2Active (in Connect)
rb basic callcleared
from basiccall
Figure 17 (sheet 3 of 4)
Page 48ETR 285: March 1996
8.3.3 Service 3
Process FE3_UUS3 Page_1(3)
clear-on-fail : =false
UUS3Idle
SERVICE3req. ind.(form)
form
Available
SERVICE 3req. ind.(form)
requestwith
SETUPreq. ind.
SET (NOW +UUS3 response,
T-UUS3 response)
UUS3requested
rcreason : =
"rejected by theuser"
SERVICE 3REJECTreq. ind.(reason)
clear-on-fail
clear basic call to basic call
rb
clear-on-fail : =true
rb
required
YES
NO
YES
NO
false
true
preferred
Figure 18 (sheet 1 of 3)
Page 49ETR 285: March 1996
Process FE3_UUS3 Page_2(3)
UUS3Requested
T-UUS3response
reason : ="rejected by the
user"
SERVICE 3REJECTreq.ind
clear-on-fail
clearbasic call
tobasic call
SERVICE 3REJECTreq.ind
rcbasic callconnected
frombasic call
basic callcleared
frombasic call
SERVICE 3resp.conf
N1 := 16
SET (NOW + 10s,Replenishment)
flow control:= false
UUS3Active
true
false
Figure 18 (sheet 2 of 3)
Page 50ETR 285: March 1996
Process FE3_UUS3 Page_3(3)
UUS3Active
Replenishment
N1 := N1 + 8
NI >= 16
SET (NOW + 10s,Replenishment)
Flow control:= false
FLOW CONTROLreq.ind(off)
UUS3Active
rc
N1 := 16
Basic callreleared
tobasiccall
DATA UNITreq.ind rb
DATA UNITreq.ind rc
UUS3Active
DATA UNITreq.ind(data)
N1 > 0
Discard(data)
Congestion
UUS3Active
Flow control := true
FLOW CONTROLreq.ind(on)
UUS3Active
rc
N1 := N1 - 1
DATA UNITreq.ind
UUS3Active
rb
rc
NoYes
Yes
No
Yes
No
Figure 18 (sheet 3 of 3)
Page 51ETR 285: March 1996
8.4 SDL diagrams for FE4
The SDL diagrams for FE4 are shown in figures 19, 20 and 21.
8.4.1 Service 1
Process FE4_UUS1 Page_1(3)
Clear-on-fail: = false
UUS1Idle
DATA UNITreq.ind
SERVICE 1req.
UUS1Active
user
rc
SERVICE 1req.ind(data) (form)
form
SERVICE 1req. user
UUS1Requested
Clear-on-fail: = true
rc
required
preferred
Figure 19 (sheet 1 of 3)
Page 52ETR 285: March 1996
Process FE4_UUS1 Page_2(3)
UUS1Requested
basic callcleared from basic call
SERVICE1REJECTind.
reason : ="rejected by user"
SERVICE 1REJECTreq.ind(reason)
Clear on fail
Clear basic call to basic call
rc
userSERVICE 1resp.
"include data in response"
SERVICE 1resp.conf(data)
rc
UUS1Active
data :="required UUI data"
user
FALSE
TRUE
YES
NO
Figure 19 (sheet 2 of 3)
Page 53ETR 285: March 1996
Process FE4_UUS1 Page_3(3)
UUS1Active
basic callclearing from basic call
DATA UNITreq. ind.(data)
DATA UNITind. user
UUS1Active
rcDATA UNITreq.
"Data : ="requested data"
DATA UNITreq.ind(data)
UUS1Active
rc
user
Figure 19 (sheet 3 of 3)
Page 54ETR 285: March 1996
8.4.2 Service 2
Process FE4_UUS2 Page_1(3)
Clear-on-fail: = false
UUS2Idle
SERVICE 2req.ind(data) (form)
form
SERVICE 2req.(data)
UUS2Requested
user
Clear-on-fail: = true
rc
preferred
required
Figure 20 (sheet 1 of 3)
Page 55ETR 285: March 1996
Process FE4_UUS2 Page_2(3)
UUS2Requested
basic callclearing from basic call
SERVICE 2REJECTind.
reason : ="rejected by
user"
SERVICE 2REJECTreq.ind(reason)
rc
Clear on fail
Clear basic call to basic call
userSERVICE 2resp.
SERVICE 2resp.conf(data)
UUS2Active
rc
user
TRUE
FALSE
Figure 20 (sheet 2 of 3)
Page 56ETR 285: March 1996
Process FE4_UUS2 Page_3(3)
UUS2Active
basic callconnectedfrom basic call
basic callclearing from basic call
DATA UNITreq.ind(data)
DATA UNITind. user
UUS2Active
rcDATA UNITreq.
Data :="requested UU1 data"
DATA UNITreq.ind(data)
UUS2Active
rc
user
Figure 20 (sheet 3 of 3)
Page 57ETR 285: March 1996
8.4.3 Service 3
Process FE4_UUS3 Page_1(3)
Clear-on-fail: = false
UUS3Idle
SERVICE 3req.ind(data) (form)
form
SERVICE 3req.(data)
UUS3Requested
user
Clear-on-fail: = true
rc
required
preferred
Figure 21 (sheet 1 of 3)
Page 58ETR 285: March 1996
Process FE4_UUS3 Page_2(3)
UUS3Requested
basic callcleared from basic call
SERVICE 3REJECTind.
reason : =rejected by user
SERVICE 3REJECTreq.ind(reason)
Clear-on-fail
Clear basic call to basic call
rc
userSERVICE 3resp.
SERVICE 3resp.conf(data)
UUS3Active
rc
user
TRUE
FALSE
Figure 21 (sheet 2 of 3)
Page 59ETR 285: March 1996
Process FE4_UUS3 Page_3(3)
UUS3Active
basic callcleared from basic call
DATA UNITreq.ind(data)
DATA UNITind. user
UUS3Active
rc
DATA UNITreq. user
Data : ="requested data"
DATA UNITreq.ind(data)
UUS3Active
rc
Figure 21 (sheet 3 of 3)
Page 60ETR 285: March 1996
9 Functional Entity Actions (FEAs)
9.1 FEAs of FE1
911: Service request for UUS services.
912: Handling of explicit or implicit UUS service 1.
913: Handling of UUS service 2.
914: Handling of UUS service 3.
9.2 FEAs of FE2
921: Service request for UUS services.
922: Handling of explicit or implicit UUS service 1.
923: Handling of UUS service 2.
924: Handling of UUS service 3.
925: Flow control for UUS service 3.
9.3 FEAs of FE3
931: Service request for UUS services.
932: Handling of explicit or implicit UUS service 1.
933: Handling of UUS service 2.
934: Handling of UUS service 3.
935: Flow control for UUS service 3.
936: Subsequent DATA UNIT req.ind information flows received from other FE4safter the first DATA UNIT req.ind information flow are discarded and no action istaken.
9.4 FEAs of FE4
941: Service request for UUS services.
942: Handling of explicit or implicit UUS service 1.
943: Handling of UUS service 2.
944: Handling of UUS service 3.
Page 61ETR 285: March 1996
10 Allocation of functional entities to physical locations
The allocation of functional entities to physical locations is shown in table 12.
Table 12
Scenario FE1 FE2 FE3 FE4Scenario 1 Orig. TE Orig. LE Dest. LE Dest TEScenario 2 Orig. TE Orig. PTNX Dest. LE Dest TEScenario 3 Orig. TE Orig. LE Dest. PTNX Dest TEScenario 4 Orig. TE Orig. PTNX Dest. PTNX Dest TEScenario 5 Dest. TE Dest. LE Orig. LE Orig. TEScenario 6 Dest. TE Dest. PTNX Orig. LE Orig. TEScenario 7 Dest. TE Dest. LE Orig. PTNX Orig. TEScenario 8 Dest. TE Dest. PTNX Orig. PTNX Orig. TE
NOTE: Scenarios 5, 6, 7 and 8 are only applicable for service 3 of the UUSsupplementary service when the network provides the option of thecalled user requesting the service in the active state.
Page 62ETR 285: March 1996
History
Document history
March 1996 First Edition
ISBN 2-7437-0549-3Dépôt légal : Mars 1996