.rs .\" Troff code generated by TPS Convert from ITU Original Files .\" Not Copyright ( c) 1991 .\" .\" Assumes tbl, eqn, MS macros, and lots of luck. .TA 1c 2c 3c 4c 5c 6c 7c 8c .ds CH .ds CF .EQ delim @@ .EN .nr LL 40.5P .nr ll 40.5P .nr HM 3P .nr FM 6P .nr PO 4P .nr PD 9p .po 4P .rs \v | 5i' .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 1 of 19), p.\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 2 of 19), p.\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 3 of 19), p. (\*`a l'italienne)\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 4 of 19), p. (\*`a l'italienne)\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 5 of 19), p.\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 6 of 19), p.\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 7 of 19), p.\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 8 of 19), p.\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 9 of 19), p.\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 10 of 19), p.\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 11 of 19), p. (\*`a l'italienne)\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 12 of 19), p.\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 13 of 19), p.\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 14 of 19), p.\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 15 of 19), p. (\*`a l'italienne)\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 16 of 19), p.\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 17 of 19), p.\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 47P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 18 of 19), p.\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 21P .ad r \fBFigure 2\(hy9/Q.71 (Sheet 19 of 19), p.\fR .sp 1P .RT .ad b .RT .sp 1P .LP 2.4 \fIFunctional entity actions\fR .sp 9p .RT .PP Functional entities are assumed to have the basic capabilities required to properly perform their assigned functions in the ISDN (e.g. synchronism, signalling capabilities,\ etc.). In addition, the actions that occur at the functional entities during call processing stages for providing services described in this Recommendation have been given reference numbers and brief descriptions. The reference numbers are shown on the information flow diagrams and on SDL diagrams. The detailed list of descriptions of actions, together with references to the information flow diagrams, follow: .RT .sp 2P .LP \fIReference\fR .sp 1P .RT .LP \fInumber\fR \fIActions\fR .sp 1P .LP 211 \fIProcess service request\fR .sp 9p .RT .LP \(em Receive, analyze and acknowledge (as required) user's SETUP.req .LP \(em Interact with user to accumulate information .LP \(em Select network access resource .LP \(em Formulate call SETUP req.ind .sp 1P .LP \fIConnect\fR .sp 9p .RT .LP \(em Establish connection as required .sp 2P .LP 221 \fIPerform originating screening\fR .sp 1P .RT .LP \(em Receive and react to SETUP req.ind from the CCA .LP \(em Analyze the service request .LP \(em Identify the calling terminal, terminal characteristics and user priority level, if any .LP \(em Verify the user's authorization, capabilities and availability of appropriate resources .LP \(em Establish call reference .bp .sp 2P .LP \fIReference\fR .sp 1P .RT .LP \fInumber\fR \fIActions\fR .sp 1P .LP \fIProcess attempt\fR .sp 9p .RT .LP \(em Reserve incoming resources .LP \(em Analyze information (called number, routing requirements,\ etc.) .LP \(em Determine connection elements type, outgoing resource (or virtual circuit), other resources (echo control, pads,\ etc.), charging treatment, network management controls in effect and any other elements involved in call setup. .LP \(em Select path through entity .LP \(em Reserve outgoing resource and any other required resources .LP \(em Formulate PROCEEDING req.ind and SETUP req.ind .LP \(em Start call control timing, as required .sp 2P .LP 223 \fIThrough connect\fR .sp 1P .RT .LP \(em Establish through connection as required (see Note\ 1 to Figures\ 2\(hy2/Q.71 through 2\(hy9/Q.71) .sp 2P .LP 224 \fIThrough connect\fR .sp 1P .RT .LP \(em Receive and react to SETUP resp.conf .LP \(em Establish through connection as required (see Note\ 2 to Figures\ 2\(hy2/Q.71 through 2\(hy9/Q.71) .LP \(em Formulate SETUP resp.conf .sp 1P .LP \fIStart charging\fR .sp 9p .RT .LP \(em Start charging timing (see Note 3 to Figures\ 2\(hy2/Q.71 through 2\(hy9/Q.71) .sp 2P .LP 225 \fIStart timer\fR .sp 1P .RT .LP \(em Receive and react to REPORT req.ind .LP \(em Start user\(hyanswer timer .LP \(em Formulate REPORT (Alerting) req.ind .sp 2P .LP 231 \fIProcess attempt\fR .sp 1P .RT .LP \(em Receive and analyze SETUP req.ind .LP \(em Establish call reference .LP \(em Reserve incoming resources .LP \(em Analyze called number, routing information, network management and/or priority information .LP \(em Determine connection elements type, outgoing resource, neet for other resources .LP \(em Select and reserve outgoing resource, other resources as required and path through the entity .LP \(em Formulate SETUP req.ind .sp 2P .LP 232 \fIThrough connect\fR .sp 1P .RT .LP \(em Establish through connection as required (see Note\ 1 to Figures\ 2\(hy2/Q.71 through 2\(hy9/Q.71) .bp .sp 2P .LP \fIReference\fR .sp 1P .RT .LP \fInumber\fR \fIActions\fR .sp 2P .LP 241 \fIPerform terminating screening\fR .sp 1P .RT .LP \(em Receive and analyze SETUP req.ind .LP \(em Reserve incoming resources .LP \(em Analyze service request, called number and any routing information .LP \(em Identify the called line(s), called terminal characteristics, any priorities and resources required .LP \(em Verify called user's authorization/capabilities .LP \(em Establish call reference .sp 1P .LP \fIProcess attempt\fR .sp 9p .RT .LP \(em Select and reserve outgoing resource, other resources and path through entity .LP \(em Formulate SETUP req.ind including requested service indication .sp 2P .LP 243 \fIThrough connect\fR .sp 1P .RT .LP \(em Establish through connection, if required (see Note\ 1 to Figures\ 2\(hy2/Q.71 through 2\(hy9/Q.71) .LP \(em Start user\(hyresponse timer .sp 2P .LP 244 \fIApply ringing tone\fR .sp 1P .RT .LP \(em Receive and react to REPORT (Alerting) req.ind .LP \(em Apply ringing tone, if required, to resource toward calling user (see Note\ 6 to Figures\ 2\(hy2/Q.71 through 2\(hy9/Q.71) .LP \(em Formulate REPORT req.ind .sp 2P .LP 245 \fIRemove ringing tone\fR .sp 1P .RT .LP \(em Receive and react to SETUP resp.conf .LP \(em If applied, remove ringing tone .LP \(em Establish through connection if not done in Ref. 243 (see Note\ 2 to Figures\ 2\(hy2/Q.71 through 2\(hy9/Q.71) .LP \(em Formulate SETUP resp.conf .sp 2P .LP 251 \fIProcess attempt\fR .sp 1P .RT .LP \(em Receive and react to SETUP req.ind .LP \(em Analyze service request .LP \(em Identify called user .LP \(em Verify compatibility of called user terminal .LP \(em Reserve resources .LP \(em Send SETUP.ind to called user .LP \(em Formulate REPORT (Alerting) req.ind .sp 2P .LP 252 \fIConnect\fR .sp 1P .RT .LP \(em Receive and react to CONNECTED req.ind .LP \(em Establish connection .sp 2P .LP 311 \fIDisconnect\fR .sp 1P .RT .LP \(em Recognize user DISCONNECT.req .LP \(em Formulate DISCONNECT req.ind .LP \(em Disconnect resources .bp .sp 2P .LP \fIReference\fR .sp 1P .RT .LP \fInumber\fR \fIActions\fR .sp 2P .LP 312 \fIRelease resources\fR .sp 1P .RT .LP \(em Receive and react to RELEASE req.ind .LP \(em Release resources \(em both directions .sp 2P .LP 321 \fIDisconnect\fR .sp 1P .RT .LP \(em Receive and react to DISCONNECT req.ind .LP \(em Disconnect resources .LP \(em Formulate RELEASE req.ind .sp 1P .LP \fIStop charging\fR .sp 9p .RT .LP \(em Stop charging per Note 3 to Figures 2\(hy2/Q.71 through 2\(hy9/Q.71 .sp 2P .LP 322 \fIRelease resources\fR .sp 1P .RT .LP \(em Receive and react to RELEASE resp.conf .LP \(em Release resources in direction of incoming RELEASE resp.conf .sp 2P .LP 323 \fIRelease resources\fR .sp 1P .RT .LP \(em Receive and react to RELEASE resp.conf .LP \(em Release resources in direction of incoming RELEASE resp.conf .sp 2P .LP 331 \fIDisconnect\fR .sp 1P .RT .LP \(em Receive and react to RELEASE req.ind .LP \(em Disconnect resources .LP \(em Formulate RELEASE req.ind .sp 1P .LP \fIRelease resource\fR .sp 9p .RT .LP \(em Release resource in direction of incoming RELEASE req.ind .LP \(em Formulate RELEASE resp.conf .sp 2P .LP 332 \fIRelease resources\fR .sp 1P .RT .LP \(em Receive and react to RELEASE resp.conf .LP \(em Release resources in direction of incoming RELEASE resp.conf .sp 2P .LP 341 \fIDisconnect\fR .sp 1P .RT .LP \(em Receive and react to RELEASE req.ind .LP \(em Disconnect resources .LP \(em Formulate DISCONNECT req.ind .sp 1P .LP \fIApply disconnect tone\fR .sp 9p .RT .LP \(em If used, apply disconnect tone to resource toward user (see Note\ 6 to Figures\ 2\(hy2/Q.71 through 2\(hy9/Q.71) .sp 1P .LP \fIRelease resources\fR .sp 9p .RT .LP \(em Release resources in direction of incoming RELEASE req.ind .LP \(em Formulate RELEASE resp.conf .sp 2P .LP 342 \fIRemove tone\fR .sp 1P .RT .LP \(em Receive and react to RELEASE req.ind .LP \(em If applied, remove tone .bp .sp 2P .LP \fIReference\fR .sp 1P .RT .LP \fInumber\fR \fIActions\fR .sp 1P .LP \fIRelease resources\fR .sp 9p .RT .LP \(em Release resources in direction of incoming RELEASE req.ind .LP \(em Formulate RELEASE resp.conf .sp 2P .LP 351 \fIProcess demand\fR .sp 1P .RT .LP \(em Receive and react to DISCONNECT req.ind .LP \(em Initiate action to send DISCONNECT.ind to user .sp 2P .LP 352 \fIDisconnect\fR .sp 1P .RT .LP \(em Receive and react to DISCONNECT.req from user .LP \(em Disconnect resources .sp 2P .LP 353 \fIRelease resources\fR .sp 1P .RT .LP \(em Receive and react to RELEASE resp.conf .LP \(em Release resources \(em both directions .sp 2P .LP 411 \fIProcess demand\fR .sp 1P .RT .LP \(em Receive and react to DISCONNECT req.ind .LP \(em Initiate action to send DISCONNECT.ind to user .sp 2P .LP 412 \fIDisconnect\fR .sp 1P .RT .LP \(em Receive and react to DISCONNECT.req from user .LP \(em Disconnect resources .LP \(em Formulate RELEASE req.ind .sp 2P .LP 413 \fIRelease resources\fR .sp 1P .RT .LP \(em Receive and react to RELEASE resp.conf .LP \(em Release resources \(em both directions .sp 2P .LP 421 \fIDisconnect\fR .sp 1P .RT .LP \(em Receive and react to RELEASE req.ind .LP \(em Disconnect resources .LP \(em Formulate DISCONNECT req.ind .sp 1P .LP \fIStop charging\fR .sp 9p .RT .LP \(em Stop charging per Note 3 to Figures 2\(hy2/Q.71 through 2\(hy9/Q.71 .sp 1P .LP \fIApply disconnect tone\fR .sp 9p .RT .LP \(em If used, apply disconnect tone to resource toward user (see Note\ 6 to Figures\ 2\(hy2/Q.71 through 2\(hy9/Q.71) .sp 1P .LP \fIRelease resources\fR .sp 9p .RT .LP \(em Release resource in direction of incoming RELEASE req.ind .LP \(em Formulate RELEASE resp.conf .sp 2P .LP 422 \fIRemove tone\fR .sp 1P .RT .LP \(em Receive and react to RELEASE req.ind .LP \(em If applied, remove tone .bp .sp 2P .LP \fIReference\fR .sp 1P .RT .LP \fInumber\fR \fIActions\fR .sp 1P .LP \fIRelease resources\fR .sp 9p .RT .LP \(em Release resources in direction of incoming RELEASE req.ind .LP \(em Formulate RELEASE resp.conf .sp 2P .LP 431 \fIDisconnect\fR .sp 1P .RT .LP \(em Receive and react to RELEASE req.ind .LP \(em Disconnect resources .LP \(em Formulate RELEASE req.ind .sp 1P .LP \fIRelease resources\fR .sp 9p .RT .LP \(em Release resources in direction of incoming RELEASE req.ind .LP \(em Formulate RELEASE resp.conf .sp 2P .LP 432 \fIRelease resource\fR .sp 1P .RT .LP \(em Receive and react to RELEASE resp.conf .LP \(em Release resource in direction of incoming RELEASE resp.conf .sp 2P .LP 441 \fIDisconnect\fR .sp 1P .RT .LP \(em Receive and react to DISCONNECT req.ind .LP \(em Disconnect resources .LP \(em Formulate RELEASE req.ind .sp 2P .LP 442 \fIRelease resource\fR .sp 1P .RT .LP \(em Receive and react to RELEASE resp.conf .LP \(em Release resource in direction of incoming RELEASE resp.conf .sp 2P .LP 443 \fIRelease resource\fR .sp 1P .RT .LP \(em Receive and react to RELEASE resp.conf .LP \(em Release resource in direction of incoming RELEASE resp.conf .sp 2P .LP 451 \fIDisconnect\fR .sp 1P .RT .LP \(em Recognize user DISCONNECT.req .LP \(em Formulate DISCONNECT req.ind .LP \(em Disconnect resources .sp 2P .LP 452 \fIRelease resources\fR .sp 1P .RT .LP \(em Receive and react to RELEASE req.ind .LP \(em Release resources \(em both directions .LP \(em Formulate RELEASE resp.conf .sp 2P .LP 2.5 \fIAdditional FEAs required for digit\(hyby\(hydigit call setup cases:\fR .sp 1P .RT .PP Under study. .RT .sp 1P .LP 2.6 \fIAllocation of functions to physical entities\fR .sp 9p .RT .PP The functional model relates to functions involved in handling a single call or call attempt. The scenarios in Table\ 2\(hy2/Q.71 identify the roles a physical device (e.g., exchange, NT2, terminal equipment,\ etc.) may play in handling that call or call attempt. A specific physical device may fulfill different roles in different scenarios, e.g., a local exchange may provide both CCA and CC capabilities. (See scenario\ D.) .bp .RT .LP .rs .sp 29P .ad r \fBTable 2\(hy2/Q.71 \ \ (\*`a traiter comme figure MEP), p.\fR .sp 1P .RT .ad b .RT .sp 2P .LP \fB3\fR \fBIn\(hycall modification procedures for alternate speech/unrestricted information transfer service\fR .sp 1P .RT .PP Under study. .RT .LP .rs .sp 16P .ad r Blanc .ad b .RT .LP .bp