Integrated Services Digital Network (ISDN); Advice of Charge (AOC) supplementary service; Functional capabilities and information flows

Stage 2 descriptions for priority 1 and 2 services covered in the MoU on ISDN

Digitalno omrežje z integriranimi storitvami (ISDN) - Dopolnilna storitev: obvestilo o ceni (AOC) - Funkcijske zmožnosti in informacijski tokovi

General Information

Status
Published
Publication Date
30-Apr-1997
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-May-1997
Due Date
01-May-1997
Completion Date
01-May-1997

Buy Standard

Standard
ETS 300 181:1997
English language
47 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day
Standard
P ETS 300 181:1997
English language
47 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 181:1997
01-maj-1997
Digitalno omrežje z integriranimi storitvami (ISDN) - Dopolnilna storitev: obvestilo
o ceni (AOC) - Funkcijske zmožnosti in informacijski tokovi
Integrated Services Digital Network (ISDN); Advice of Charge (AOC) supplementary
service; Functional capabilities and information flows
Ta slovenski standard je istoveten z: ETS 300 181 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST ETS 300 181:1997 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 181:1997

---------------------- Page: 2 ----------------------

SIST ETS 300 181:1997
EUROPEAN ETS 300 181
TELECOMMUNICATION April 1993
STANDARD
Source: ETSI TC-SPS Reference: T/S 22-04
ICS: 33.080
ISDN, supplementary service.
Key words:
Integrated Services Digital Network (ISDN);
Advice of Charge (AOC) supplementary service
Functional capabilities and information flows
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - secretariat@etsi.fr
X.400: Internet:
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 the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1993. All rights reserved.
New presentation - see History box

---------------------- Page: 3 ----------------------

SIST ETS 300 181:1997
Page 2
ETS 300 181: April 1993
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: 4 ----------------------

SIST ETS 300 181:1997
Page 3
ETS 300 181: April 1993
Contents
Foreword.5
1 Scope .7
2 Normative references .7
3 Definitions.8
4 Symbols and abbreviations.8
5 Description .8
6 Derivation of a functional model .9
6.1 Functional model description .9
6.2 Description of the functional entities.9
6.3 Relationship with a basic service .9
7 Information flows.10
7.1 Information flow diagrams.10
7.1.1 Information flows for charging information at call set-up time (AOC-S).10
7.1.1.1 Receipt of charging information on charging rates
(AOC-S) .10
7.1.1.2 Change of charging rate during the active state of a call
(AOC-S) .11
7.1.1.3 Receipt of charging rate after TP RETRIEVE (AOC-S).11
7.1.2 Information flows for charging information during a call (AOC-D).12
7.1.2.1 Transfer of charging information at call establishment
(AOC-D).12
7.1.2.2 Transfer of charging information during the active state of
a call (AOC-D) .12
7.1.2.3 Transfer of charging information at TP HOLD (AOC-D).13
7.1.2.4 Transfer of charging information at TP RETRIEVE
(AOC-D).14
7.1.2.5 Transfer of charging information at call clearing (AOC-D). 15
7.1.3 Information flows for charging information at the end of a call (AOC-E) .16
7.1.3.1 Request for AOC-E at call set-up time (AOC-E). 16
7.1.3.2 Information flows for AOC at call clearing (AOC-E) .16
7.1.3.3 Information flows at immediate call diversions (AOC-E).17
7.1.3.4 Information flows when diversion of a call occurs after the
call has been presented (AOC-E) .18
7.1.3.5 Information flows for AOC at call failure during call
establishment (AOC-E) .19
7.2 Definition of individual information flows.19
7.2.1 Relationship ra.19
7.2.2 Relationship rb.22
7.2.3 Relationship rc .28
8 SDL diagrams for functional entities.32
8.1 FE1.33
8.2 FE2.34
8.3 FE3.39
8.4 FE4.43

---------------------- Page: 5 ----------------------

SIST ETS 300 181:1997
Page 4
ETS 300 181: April 1993
9 Functional Entity Actions (FEAs).44
9.1 FEAs for FE1.44
9.2 FEAs for FE2.44
9.3 FEAs for FE3.44
9.4 FEAs for FE4.45
10 Allocation of functional entities to physical locations.45
Annex A (informative): Interworking between two charging domains .46
History .47

---------------------- Page: 6 ----------------------

SIST ETS 300 181:1997
Page 5
ETS 300 181: April 1993
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols &
Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).
In accordance with CCITT Recommendation I.130 [1], the following three level structure is used to
describe the supplementary telecommunications services as provided by European public
telecommunications operators under the pan-European Integrated Services Digital Network (ISDN):
- Stage 1: is an overall service description, from the user's stand-point;
- Stage 2: identifies the functional capabilities and information flows needed to support the service
described in stage 1; and
- Stage 3: defines the signalling system protocols and switching functions needed to implement the
service described in stage 1.
This ETS details the stage 2 aspects (functional capabilities and information flows) needed to support the
Advice Of Charge (AOC) supplementary service. The stage 1 and stage 3 aspects are detailed in ETSs
300 178-180 (1992) and ETS 300 182 (1993), respectively.

---------------------- Page: 7 ----------------------

SIST ETS 300 181:1997
Page 6
ETS 300 181: April 1993
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 181:1997
Page 7
ETS 300 181: April 1993
1 Scope
This standard defines the stage two of the Advice of Charge (AOC) supplementary service for the pan-
European Integrated Services Digital Network (ISDN) as provided by the European public
telecommunications operators. Stage two identifies the functional capabilities and the information flows
needed to support the service description. The stage two description also identifies user operations not
directly associated with a call (see CCITT Recommendation I.130 [1]).
This standard is defined according to the methodology specified in CCITT Recommendation Q.65 [2].
In addition this standard does not specify the requirements where the service is provided to the user via a
private ISDN. This standard does not specify the requirements for the allocation of defined functional
entities within a private ISDN, it defines which functional entities may be allocated to a private ISDN.
This standard does not specify the additional requirements where the service is provided to the user via a
telecommunications network that is not an ISDN.
The AOC supplementary service provides the served user with usage based charging information.
The AOC supplementary service is applicable to all circuit switched telecommunication services.
This standard is applicable to the stage three standards for the ISDN AOC supplementary services. The
term "stage three" is defined in CCITT Recommendation I.130 [1]. Where the text indicates the status of a
requirement, i.e. as a strict command or prohibition, as authorisation leaving freedom, as a capability or
possibility, this shall be reflected in the text of the relevant stage three standards.
Furthermore, conformance to this standard is met by conforming to the stage three standards with the field
of application appropriate to the equipment being implemented. Therefore, no method of testing is provided
for this standard.
This standard does not formally describe the relation between this supplementary service and the basic
call, but where possible, this information is included for guidance.
2 Normative references
This standard incorporates by dated or undated reference, provisions from other publications. These
normative 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 standard only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] CCITT Recommendation I.130 (1988): "Method for the characterisation of
telecommunication services supported by an ISDN and network capabilities of an
ISDN".
[2] CCITT Recommendation Q.65 (1988): "Stage 2 of the method for the
characterisation of services supported by an ISDN".
[3] CCITT Recommendation I.112 (1988): "Vocabulary of terms for ISDNs".
[4] CCITT Recommendation I.210 (1988): "Principles of telecommunication services
supported by an ISDN and the means to describe them".
[5] CCITT Recommendation E.164 (1988): "Numbering plan for the ISDN era".
[6] CCITT Recommendation Z.100 (1988): "Functional Specification and Description
Language (SDL)".
[7] CCITT Recommendation Q.71 (1988): "ISDN 64 kbit/s circuit mode switched
bearer service".

---------------------- Page: 9 ----------------------

SIST ETS 300 181:1997
Page 8
ETS 300 181: April 1993
3 Definitions
For the purposes of this standard, the following definitions apply:
Advice of Charge (AOC): information about usage based charging.
Charged number: the number which shall be charged for the call.
Dialled number: the destination for the charged call.
Integrated Services Digital Network (ISDN): see CCITT Recommendation I.112 [3], § 2.3, definition
308.
ISDN number: a number conforming to the numbering plan and structure specified in CCITT
Recommendation E.164 [5].
Service; telecommunications service: see CCITT Recommendation I.112 [3], § 2.2, definition 201.
Supplementary service: see CCITT Recommendation I.210 [4], § 2.4.
4 Symbols and abbreviations
AOC Advice of Charge
CD Call Deflection
CFB Call Forwarding Busy
CFNR Call Forwarding No Reply
CFU Call Forwarding Unconditional
CT Call Transfer
FEA Functional Entity Action
ISDN Integrated Services Digital Network
LE Local Exchange
PTNX Private Telecommunications Network eXchange
SDL Specification and Description Language
TE Terminal Equipment
TP Terminal Portability
5 Description
Advice of Charge (AOC) is a group of supplementary services allowing the served user to be informed of
usage-based charging information.
These supplementary services are not meant to replace the charge metering inside the network which is
considered to be the correct one in all cases.

---------------------- Page: 10 ----------------------

SIST ETS 300 181:1997
Page 9
ETS 300 181: April 1993
The AOC group of supplementary services may include the following:
AOC-S Charging information at call set-up time;
AOC-D Charging information during the call;
AOC-E Charging information at the end of a call.
6 Derivation of a functional model
6.1 Functional model description
The functional model for the AOC supplementary service is shown in figure 1.
�˜˜˜¿ ra �˜˜˜¿ rb �˜˜˜¿ rc �˜˜˜¿
‡FE1ˆ˜˜˜˜˜˜·FE2ˆ˜˜˜˜˜˜·FE3ˆ˜˜˜˜˜˜·FE4‡
�˜˜˜�   �˜˜˜�   �˜˜˜�   �˜˜˜�
Figure 1
6.2 Description of the functional entities
FE1: AOC served entity
FE2: AOC information options check
FE3: AOC controlling entity
FE4: AOC information formatting
6.3 Relationship with a basic service
The relationship with a basic service is shown in figure 2.
NOTE: The basic call model is defined in CCITT Recommendation Q.71 [7], § 2.1, with the
exception that r1 represents an outgoing relationship from a CCA and r3 represents an
incoming relationship to a CCA.
                �˜˜˜¿
                ‡FE4‡
                �˜´˜�
                 ‡rc
   �˜˜˜¿  ra  �˜˜˜¿  rb  �˜`˜¿
   ‡FE1ˆ˜˜˜˜˜˜˜˜·FE2ˆ˜˜˜˜˜˜˜˜·FE3‡
  �`˜˜´�    �`˜´˜�    �`˜´˜�   �˜˜¿    �˜˜˜¿
  ‡CCAˆ˜˜˜˜˜˜˜˜·CCˆ˜˜˜˜˜˜˜˜˜·CCˆ˜˜˜˜˜˜˜˜·CCˆ˜˜˜˜˜˜˜˜·CCA‡
  �˜˜˜�  r1  �˜˜�  r2  �˜˜�  r2  �˜˜�  r3  �˜˜˜�
Figure 2

---------------------- Page: 11 ----------------------

SIST ETS 300 181:1997
Page 10
ETS 300 181: April 1993
7 Information flows
7.1 Information flow diagrams
It is assumed that the coding of the AOC-Information is done in such a way that whenever this information
is received by a FE1 the content shall be complete in itself.
The flows are intended to show the information flowing for the AOC supplementary service. These flows
can in many cases be combined with the flows for the basic call, depending upon call state. Whether or not
this can take place is considered to be a stage 3 matter.
7.1.1 Information flows for charging information at call set-up time (AOC-S)
7.1.1.1 Receipt of charging information on charging rates (AOC-S)
      �˜˜˜¿         �˜˜˜¿         �˜˜˜¿         �˜˜˜¿
      ‡FE1‡ - - - ra - - - - ‡FE2‡ - - - rb - - - - ‡FE3‡ - - - rc - - - - ‡FE4‡
      ˆ˜˜˜·         ˆ˜˜˜·         ˆ˜˜˜·         ˆ˜˜˜·
     211‡  ‡211  SETUP  221‡  ‡         ‡  ‡         ‡  ‡
    >>>>‡  ‡>>>>‡- - - ->‡>>>>ˆ˜˜˜·         ‡  ‡         ‡  ‡
      ‡  ‡   req.ind   ‡  ‡         ‡  ‡         ‡  ‡
      ‡  ‡         ‡  ‡         ‡  ‡         ‡  ‡
      ‡910‡  REQUEST1   ‡  ‡         ‡  ‡         ‡  ‡
      ˆ˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜>‡  ‡         ‡  ‡         ‡  ‡
      ‡  ‡   req.ind   ‡920‡         ‡  ‡         ‡  ‡
      ‡  ‡         ‡923‡         ‡  ‡         ‡  ‡
      ‡  ‡         ‡921‡  REQUEST2   ‡  ‡         ‡  ‡
      ‡  ‡         ˆ˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜>ˆ˜˜˜·         ‡  ‡
      ‡  ‡         ‡  ‡   req.ind   ‡930‡         ‡  ‡
      ‡  ‡         ‡  ‡         ‡936‡         ‡  ‡
      ‡  ‡         ‡  ‡         ‡931‡         ‡  ‡
      ‡  ‡         ‡  ‡         ‡932‡  REQUEST3   ‡  ‡
      ‡  ‡         ‡  ‡         ˆ˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜>ˆ˜˜˜·
      ‡  ‡         ‡  ‡         ‡  ‡   req.ind   ‡940‡
      ‡  ‡         ‡  ‡         ‡  ‡         ‡941‡
      ‡  ‡         ‡  ‡         ‡  ‡         ‡  ‡
      ‡  ‡         ‡  ‡         ‡  ‡  REQUEST3   ‡942‡
      ‡  ‡         ‡  ‡         ˆ˜˜˜·<˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜·
      ‡  ‡         ‡  ‡         ‡933‡  resp.conf   ‡  ‡
      ‡  ‡         ‡  ‡  REQUEST2   ‡934‡         ‡  ‡
      ‡  ‡         ˆ˜˜˜·<˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜·         ‡  ‡
      ‡  ‡         ‡924‡  resp.conf   ‡  ‡         ‡  ‡
      ‡  ‡    SETUP  224‡  ‡         ‡  ‡         ‡  ‡
      ‡  ‡  ‡<- - - -‡<<<<‡  ‡         ‡  ‡         ‡  ‡
      ‡  ‡  resp.conf   ‡  ‡         ‡  ‡         ‡  ‡
      ‡  ‡         ‡  ‡         ‡  ‡         ‡  ‡
      ‡  ‡   INFORM4   ‡  ‡         ‡  ‡         ‡  ‡
      ‡  ‡<˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜·922‡         ‡  ‡         ‡  ‡
  INFORM4 ‡911‡   req.ind   ‡  ‡         ‡  ‡         ‡  ‡
 <˜˜˜˜˜˜˜˜˜¯˜˜˜·         ‡925‡   INFORM1   ‡  ‡         ‡  ‡
   ind  ‡  ‡         ˆ˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜>ˆ˜˜˜·         ‡  ‡
      ‡  ‡         ‡  ‡   req.ind   ‡935‡         ‡  ‡
      ‡  ‡         ‡  ‡         ‡  ‡         ‡  ‡
      ‡  ‡         ‡  ‡         ‡  ‡         ‡  ‡
      �˜˜˜�         �˜˜˜�         �˜˜˜�         �˜˜˜�
Figure 3

---------------------- Page: 12 ----------------------

SIST ETS 300 181:1997
Page 11
ETS 300 181: April 1993
7.1.1.2 Change of charging rate during the active state of a call (AOC-S)
     �˜˜˜¿         �˜˜˜¿         �˜˜˜¿         �˜˜˜¿
     ‡FE1‡ - - - ra - - - - ‡FE2‡ - - - rb - - - - ‡FE3‡ - - - rc - - - - ‡FE4‡
     ˆ˜˜˜·         ˆ˜˜˜·         ˆ˜˜˜·         ˆ˜˜˜·
     ‡  ‡         ‡  ‡         ‡937‡         ‡  ‡
     ‡  ‡         ‡  ‡         ‡931‡         ‡  ‡
     ‡  ‡         ‡  ‡         ‡932‡  REQUEST3   ‡  ‡
     ‡  ‡         ‡  ‡         ˆ˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜>ˆ˜˜˜·
     ‡  ‡         ‡  ‡         ‡  ‡   req.ind   ‡940‡
     ‡  ‡         ‡  ‡         ‡  ‡         ‡941‡
     ‡  ‡         ‡  ‡         ‡  ‡         ‡  ‡
     ‡  ‡         ‡  ‡         ‡  ‡  REQUEST3   ‡942‡
     ‡  ‡         ‡  ‡         ˆ˜˜˜·<˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜·
     ‡  ‡         ‡  ‡         ‡933‡  resp.conf   ‡  ‡
     ‡  ‡         ‡  ‡   INFORM3   ‡934‡         ‡  ‡
     ‡  ‡         ˆ˜˜˜·<˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜·         ‡  ‡
     ‡  ‡         ‡924‡   req.ind   ‡  ‡         ‡  ‡
     ‡  ‡   INFORM4   ‡922‡         ‡  ‡         ‡  ‡
     ‡  ‡<˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜·         ‡  ‡         ‡  ‡
 INFORM4 ‡911‡   req.ind   ‡  ‡         ‡  ‡         ‡  ‡
<˜˜˜˜˜˜˜˜¯˜˜˜·         ‡  ‡         ‡  ‡         ‡  ‡
  ind  ‡  ‡         ‡  ‡         ‡  ‡         ‡  ‡
     �˜˜˜�         �˜˜˜�         �˜˜˜�         �˜˜˜�
Figure 4
7.1.1.3 Receipt of charging rate after TP RETRIEVE (AOC-S)
     �˜˜˜¿           �˜˜˜¿           �˜˜˜¿           �˜˜˜¿
     ‡FE1‡ - - - - ra - - - - -‡FE2‡ - - - - rb - - - - -‡FE3‡ - - - - rc - - - - -‡FE4‡
     ˆ˜˜˜·           ˆ˜˜˜·           ˆ˜˜˜·           ˆ˜˜˜·
     ‡  ‡   TP RETRIEVE 922‡  ‡           ‡  ‡           ‡  ‡
     ‡  ‡   - - - - ->‡>>>>‡  ‡           ‡  ‡           ‡  ‡
     ‡  ‡    req.ind    ‡925‡           ‡  ‡           ‡  ‡
     ‡  ‡           ‡921‡   REQUEST2    ‡  ‡           ‡  ‡
     ‡  ‡           ˆ˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜>ˆ˜˜˜·           ‡  ‡
     ‡  ‡           ‡  ‡   req.ind    ‡930‡           ‡  ‡
     ‡  ‡           ‡  ‡           ‡931‡           ‡  ‡
     ‡  ‡           ‡  ‡           ‡932‡   REQUEST3    ‡  ‡
     ‡  ‡           ‡  ‡           ˆ˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜>ˆ˜˜˜·
     ‡  ‡           ‡  ‡           ‡  ‡   req.ind    ‡940‡
     ‡  ‡           ‡  ‡           ‡  ‡           ‡941‡
     ‡  ‡           ‡  ‡           ‡  ‡           ‡  ‡
     ‡  ‡           ‡  ‡           ‡  ‡   REQUEST3    ‡942‡
     ‡  ‡           ‡  ‡           ˆ˜˜˜·<˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜·
     ‡  ‡           ‡  ‡           ‡933‡   resp.conf    ‡  ‡
     ‡  ‡           ‡  ‡   REQUEST2    ‡934‡           ‡  ‡
     ‡  ‡           ˆ˜˜˜·<˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜·           ‡  ‡
     ‡  ‡           ‡924‡   resp.conf    ‡  ‡           ‡  ‡
     ‡  ‡           ‡  ‡           ‡  ‡           ‡  ‡
     ‡  ‡914 TP RETRIEVE  922‡  ‡           ‡  ‡           ‡  ‡
     ‡  ‡<<<<‡<- - - - - ‡<<<<‡  ‡           ‡  ‡           ‡  ‡
     ‡  ‡   resp.conf    ‡  ‡           ‡  ‡           ‡  ‡
     ‡  ‡           ‡  ‡           ‡  ‡           ‡  ‡
     ‡  ‡   INFORM4    ‡922‡           ‡  ‡           ‡  ‡
     ‡  ‡<˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜·           ‡  ‡           ‡  ‡
 INFORM4 ‡911‡   req.ind    ‡  ‡           ‡  ‡           ‡  ‡
<˜˜˜˜˜˜˜˜˜¯˜˜˜·           ‡  ‡           ‡  ‡           ‡  ‡
  ind  ‡  ‡           ‡  ‡           ‡  ‡           ‡  ‡
     �˜˜˜�           �˜˜˜�           �˜˜˜�           �˜˜˜�
Figure 5
NOTE: The TP RETRIEVE function is a part of the Terminal Portability (TP) supplementary
service, and the corresponding FEA numbers refer to this service.

---------------------- Page: 13 ----------------------

SIST ETS 300 181:1997
Page 12
ETS 300 181: April 1993
7.1.2 Information flows for charging information during a call (AOC-D)
7.1.2.1 Transfer of charging information at call establishment (AOC-D)
       �˜˜˜¿         �˜˜˜¿         �˜˜˜¿         �˜˜˜¿
       ‡FE1‡ - - - ra - - - - ‡FE2‡ - - - rb - - - - ‡FE3‡ - - - rc - - - - ‡FE4‡
       ˆ˜˜˜·         ˆ˜˜˜·         ˆ˜˜˜·         ˆ˜˜˜·
     211 ‡  ‡211  SETUP  221‡  ‡         ‡  ‡         ‡  ‡
     >>>>‡  ‡>>>>‡- - - ->‡>>>>‡  ‡         ‡  ‡         ‡  ‡
       ‡  ‡   req.ind   ‡221‡         ‡  ‡         ‡  ‡
       ‡  ‡         ‡  ‡         ‡  ‡         ‡  ‡
       ‡910‡  REQUEST1   ‡  ‡         ‡  ‡         ‡  ‡
       ˆ˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜>ˆ˜˜˜·         ‡  ‡         ‡  ‡
       ‡  ‡   req.ind   ‡920‡         ‡  ‡         ‡  ‡
       ‡  ‡         ‡923‡         ‡  ‡         ‡  ‡
       ‡  ‡         ‡921‡   REQUEST4   ‡  ‡         ‡  ‡
       ‡  ‡         ˆ˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜>ˆ˜˜˜·         ‡  ‡
       ‡  ‡         ‡  ‡   req.ind   ‡930‡         ‡  ‡
       ‡  ‡         ‡  ‡         ‡936‡         ‡  ‡
       ‡  ‡         ‡  ‡         ‡931‡         ‡  ‡
       ‡  ‡         ‡  ‡         ‡932‡  REQUEST5   ˆ˜˜˜·
       ‡  ‡         ‡  ‡         ˆ˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜>‡940‡
       ‡  ‡         ‡  ‡         ‡  ‡  req.ind    ‡  ‡
       ‡  ‡         ‡  ‡         ‡  ‡         ‡941‡
       ‡  ‡         ‡  ‡         ‡  ‡         ‡  ‡
       ‡  ‡         ‡  ‡         ‡  ‡  REQUEST5   ‡942‡
       ‡  ‡         ‡  ‡         ˆ˜˜˜·<˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜·
       ‡  ‡         ‡  ‡         ‡933‡  resp.conf   ‡  ‡
       ‡  ‡         ‡  ‡   REQUEST4   ‡934‡         ‡  ‡
       ‡  ‡         ˆ˜˜˜·<˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜·         ‡  ‡
       ‡  ‡         ‡924‡   resp.conf  ‡  ‡         ‡  ‡
       ‡  ‡   SETUP  224‡  ‡         ‡  ‡         ‡  ‡
       ‡  ‡<<<<‡<- - - -‡<<<<‡  ‡         ‡  ‡         ‡  ‡
       ‡  ‡  resp.conf   ‡  ‡         ‡  ‡         ‡  ‡
       ‡  ‡         ‡  ‡         ‡  ‡         ‡  ‡
       ‡  ‡  INFORM2    ‡  ‡         ‡  ‡         ‡  ‡
       ‡  ‡<˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜·922‡         ‡  ‡         ‡  ‡
   INFORM  ‡911‡  req.ind    ‡  ‡         ‡  ‡         ‡  ‡
  <˜˜˜˜˜˜˜˜˜˜¯˜˜˜·         ‡925‡   INFORM1   ‡  ‡         ‡  ‡
    ind  ‡  ‡         ˆ˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜>ˆ˜˜˜·         ‡  ‡
       ‡  ‡         ‡  ‡   req.ind   ‡935‡         ‡  ‡
       ‡  ‡         ‡  ‡         ‡  ‡         ‡  ‡
       ‡  ‡         ‡  ‡         ‡  ‡         ‡  ‡
       �˜˜˜�         �˜˜˜�         �˜˜˜�         �˜˜˜�
Figure 6
7.1.2.2 Transfer of charging information during the active state of a call (AOC-D)
       �˜˜˜¿         �˜˜˜¿         �˜˜˜¿         �˜˜˜¿
       ‡FE1‡ - - - ra - - - - ‡FE2‡ - - - rb - - - - ‡FE3‡ - - - rc - - - - ‡FE4‡
       ˆ˜˜˜·         ˆ˜˜˜·         ˆ˜˜˜·         ˆ˜˜˜·
       ‡  ‡         ‡  ‡         ‡937‡         ‡  ‡
       ‡  ‡         ‡  ‡         ‡931‡         ‡  ‡
       ‡  ‡         ‡  ‡         ‡932‡  REQUEST5   ‡  ‡
       ‡  ‡         ‡  ‡         ˆ˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜>ˆ˜˜˜·
       ‡  ‡         ‡  ‡         ‡  ‡   req.ind   ‡940‡
       ‡  ‡         ‡  ‡         ‡  ‡         ‡941‡
       ‡  ‡         ‡  ‡         ‡  ‡         ‡  ‡
       ‡  ‡         ‡  ‡         ‡  ‡   REQUEST5   ‡942‡
       ‡  ‡         ‡  ‡         ˆ˜˜˜·<˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜·
       ‡  ‡         ‡  ‡         ‡933‡
...

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digitalno omrežje z integriranimi storitvami (ISDN) - Dopolnilna storitev: obvestilo o ceni (AOC) - Funkcijske zmožnosti in informacijski tokoviIntegrated Services Digital Network (ISDN); Advice of Charge (AOC) supplementary service; Functional capabilities and information flows33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:ETS 300 181 E13SIST ETS 300 181:1997en01-MDQXDU19973SIST ETS 300 181:1997SLOVENSKI
STANDARD



SIST ETS 300 181:1997



EUROPEANETS 300 181TELECOMMUNICATIONApril 1993STANDARDSource: ETSI TC-SPSReference: T/S 22-04ICS:33.080Key words:ISDN, supplementary service.Integrated Services Digital Network (ISDN);Advice of Charge (AOC) supplementary serviceFunctional capabilities and information flowsETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal 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: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright 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 1993. All rights reserved.SIST ETS 300 181:1997



Page 2ETS 300 181: April 1993Whilst 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.SIST ETS 300 181:1997



Page 3ETS 300 181: April 1993ContentsForeword.51Scope.72Normative references.73Definitions.84Symbols and abbreviations.85Description.86Derivation of a functional model.96.1Functional model description.96.2Description of the functional entities.96.3Relationship with a basic service.97Information flows.107.1Information flow diagrams.107.1.1Information flows for charging information at call set-up time (AOC-S).107.1.1.1Receipt of charging information on charging rates(AOC-S).107.1.1.2Change of charging rate during the active state of a call(AOC-S).117.1.1.3Receipt of charging rate after TP RETRIEVE (AOC-S).117.1.2Information flows for charging information during a call (AOC-D).127.1.2.1Transfer of charging information at call establishment(AOC-D).127.1.2.2Transfer of charging information during the active state ofa call (AOC-D).127.1.2.3Transfer of charging information at TP HOLD (AOC-D).137.1.2.4Transfer of charging information at TP RETRIEVE(AOC-D).147.1.2.5Transfer of charging information at call clearing (AOC-D).157.1.3Information flows for charging information at the end of a call (AOC-E).167.1.3.1Request for AOC-E at call set-up time (AOC-E).167.1.3.2Information flows for AOC at call clearing (AOC-E).167.1.3.3Information flows at immediate call diversions (AOC-E).177.1.3.4Information flows when diversion of a call occurs after thecall has been presented (AOC-E).187.1.3.5Information flows for AOC at call failure during callestablishment (AOC-E).197.2Definition of individual information flows.197.2.1Relationship ra.197.2.2Relationship rb.227.2.3Relationship rc.288SDL diagrams for functional entities.328.1FE1.338.2FE2.348.3FE3.398.4FE4.43SIST ETS 300 181:1997



Page 4ETS 300 181: April 19939Functional Entity Actions (FEAs).449.1FEAs for FE1.449.2FEAs for FE2.449.3FEAs for FE3.449.4FEAs for FE4.4510Allocation of functional entities to physical locations.45Annex A (informative):Interworking between two charging domains.46History.47SIST ETS 300 181:1997



Page 5ETS 300 181: April 1993ForewordThis European Telecommunication Standard (ETS) has been produced by the Signalling Protocols &Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).In accordance with CCITT Recommendation I.130 [1], the following three level structure is used todescribe the supplementary telecommunications services as provided by European publictelecommunications operators under the pan-European Integrated Services Digital Network (ISDN):-Stage 1: is an overall service description, from the user's stand-point;-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 ETS details the stage 2 aspects (functional capabilities and information flows) needed to support theAdvice Of Charge (AOC) supplementary service.
The stage 1 and stage 3 aspects are detailed in ETSs300 178-180 (1992) and ETS 300 182 (1993), respectively.SIST ETS 300 181:1997



Page 6ETS 300 181: April 1993Blank pageSIST ETS 300 181:1997



Page 7ETS 300 181: April 19931ScopeThis standard defines the stage two of the Advice of Charge (AOC) supplementary service for the pan-European Integrated Services Digital Network (ISDN) as provided by the European publictelecommunications operators. Stage two identifies the functional capabilities and the information flowsneeded to support the service description. The stage two description also identifies user operations notdirectly associated with a call (see CCITT Recommendation I.130 [1]).This standard is defined according to the methodology specified in CCITT Recommendation Q.65 [2].In addition this standard does not specify the requirements where the service is provided to the user via aprivate ISDN. This standard does not specify the requirements for the allocation of defined functionalentities within a private ISDN, it defines which functional entities may be allocated to a private ISDN.This standard does not specify the additional requirements where the service is provided to the user via atelecommunications network that is not an ISDN.The AOC supplementary service provides the served user with usage based charging information.The AOC supplementary service is applicable to all circuit switched telecommunication services.This standard is applicable to the stage three standards for the ISDN AOC supplementary services. Theterm "stage three" is defined in CCITT Recommendation I.130 [1]. Where the text indicates the status of arequirement, i.e. as a strict command or prohibition, as authorisation leaving freedom, as a capability orpossibility, this shall be reflected in the text of the relevant stage three standards.Furthermore, conformance to this standard is met by conforming to the stage three standards with the fieldof application appropriate to the equipment being implemented. Therefore, no method of testing is providedfor this standard.This standard does not formally describe the relation between this supplementary service and the basiccall, but where possible, this information is included for guidance.2Normative referencesThis standard incorporates by dated or undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter, for dated references, subsequent amendments to or revisions of any of these publications applyto this standard only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]CCITT Recommendation I.130 (1988): "Method for the characterisation oftelecommunication services supported by an ISDN and network capabilities of anISDN".[2]CCITT Recommendation Q.65 (1988): "Stage 2 of the method for thecharacterisation of services supported by an ISDN".[3]CCITT Recommendation I.112 (1988): "Vocabulary of terms for ISDNs".[4]CCITT Recommendation I.210 (1988): "Principles of telecommunication servicessupported by an ISDN and the means to describe them".[5]CCITT Recommendation E.164 (1988): "Numbering plan for the ISDN era".[6]CCITT Recommendation Z.100 (1988): "Functional Specification and DescriptionLanguage (SDL)".[7]CCITT Recommendation Q.71 (1988): "ISDN 64 kbit/s circuit mode switchedbearer service".SIST ETS 300 181:1997



Page 8ETS 300 181: April 19933DefinitionsFor the purposes of this standard, the following definitions apply:Advice of Charge (AOC): information about usage based charging.Charged number: the number which shall be charged for the call.Dialled number: the destination for the charged call.Integrated Services Digital Network (ISDN): see CCITT Recommendation I.112 [3], § 2.3, definition308.ISDN number: a number conforming to the numbering plan and structure specified in CCITTRecommendation E.164 [5].Service; telecommunications service: see CCITT Recommendation I.112 [3], § 2.2, definition 201.Supplementary service: see CCITT Recommendation I.210 [4], § 2.4.4Symbols and abbreviationsAOCAdvice of ChargeCDCall DeflectionCFBCall Forwarding BusyCFNRCall Forwarding No ReplyCFUCall Forwarding UnconditionalCTCall TransferFEAFunctional Entity ActionISDNIntegrated Services Digital NetworkLELocal ExchangePTNXPrivate Telecommunications Network eXchangeSDLSpecification and Description LanguageTETerminal EquipmentTPTerminal Portability5DescriptionAdvice of Charge (AOC) is a group of supplementary services allowing the served user to be informed ofusage-based charging information.These supplementary services are not meant to replace the charge metering inside the network which isconsidered to be the correct one in all cases.SIST ETS 300 181:1997



Page 9ETS 300 181: April 1993The AOC group of supplementary services may include the following:AOC-SCharging information at call set-up time;AOC-DCharging information during the call;AOC-ECharging information at the end of a call.6Derivation of a functional model6.1Functional model descriptionThe functional model for the AOC supplementary service is shown in figure 1.ÚÄÄÄ¿
ra
ÚÄÄÄ¿
rb
ÚÄÄÄ¿
rc
ÚÄÄÄ¿³FE1ÃÄÄÄÄÄÄ´FE2ÃÄÄÄÄÄÄ´FE3ÃÄÄÄÄÄÄ´FE4³ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙFigure 16.2Description of the functional entitiesFE1:AOC served entityFE2:AOC information options checkFE3:AOC controlling entityFE4:AOC information formatting6.3Relationship with a basic serviceThe relationship with a basic service is shown in figure 2.NOTE:The basic call model is defined in CCITT Recommendation Q.71 [7], § 2.1, with theexception that r1 represents an outgoing relationship from a CCA and r3 represents anincoming relationship to a CCA.
ÚÄÄÄ¿
³FE4³
ÀÄÂÄÙ
³rc
ÚÄÄÄ¿
ra
ÚÄÄÄ¿
rb
ÚÄÁÄ¿
³FE1ÃÄÄÄÄÄÄÄÄ´FE2ÃÄÄÄÄÄÄÄÄ´FE3³
ÚÁÄÄÂÙ
ÚÁÄÂÄÙ
ÚÁÄÂÄÙ
ÚÄÄ¿
ÚÄÄÄ¿
³CCAÃÄÄÄÄÄÄÄÄ´CCÃÄÄÄÄÄÄÄÄÄ´CCÃÄÄÄÄÄÄÄÄ´CCÃÄÄÄÄÄÄÄÄ´CCA³
ÀÄÄÄÙ
r1
ÀÄÄÙ
r2
ÀÄÄÙ
r2
ÀÄÄÙ
r3
ÀÄÄÄÙFigure 2SIST ETS 300 181:1997



Page 10ETS 300 181: April 19937Information flows7.1Information flow diagramsIt is assumed that the coding of the AOC-Information is done in such a way that whenever this informationis received by a FE1 the content shall be complete in itself.The flows are intended to show the information flowing for the AOC supplementary service. These flowscan in many cases be combined with the flows for the basic call, depending upon call state. Whether or notthis can take place is considered to be a stage 3 matter.7.1.1Information flows for charging information at call set-up time (AOC-S)7.1.1.1Receipt of charging information on charging rates (AOC-S)
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
³FE1³ - - - ra - - - - ³FE2³ - - - rb - - - - ³FE3³ - - - rc - - - - ³FE4³
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
211³
³211
SETUP
221³
³
³
³
³
³
>>>>³
³>>>>³- - - ->³>>>>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³910³
REQUEST1
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>³
³
³
³
³
³
³
³
req.ind
³920³
³
³
³
³
³
³
³923³
³
³
³
³
³
³
³921³
REQUEST2
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³930³
³
³
³
³
³
³
³936³
³
³
³
³
³
³
³931³
³
³
³
³
³
³
³932³
REQUEST3
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³940³
³
³
³
³
³
³
³941³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
REQUEST3
³942³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³933³
resp.conf
³
³
³
³
³
³
REQUEST2
³934³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³924³
resp.conf
³
³
³
³
³
³
SETUP
224³
³
³
³
³
³
³
³
³<- - - -³<<<<³
³
³
³
³
³
³
³
resp.conf
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
INFORM4
³
³
³
³
³
³
³
³<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´922³
³
³
³
³
INFORM4 ³911³
req.ind
³
³
³
³
³
³
<ÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³925³
INFORM1
³
³
³
³
ind
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³935³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙFigure 3SIST ETS 300 181:1997



Page 11ETS 300 181: April 19937.1.1.2Change of charging rate during the active state of a call (AOC-S)
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
³FE1³ - - - ra - - - - ³FE2³ - - - rb - - - - ³FE3³ - - - rc - - - - ³FE4³
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
³
³
³
³
³937³
³
³
³
³
³
³
³931³
³
³
³
³
³
³
³932³
REQUEST3
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³940³
³
³
³
³
³
³
³941³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
REQUEST3
³942³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³933³
resp.conf
³
³
³
³
³
³
INFORM3
³934³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³924³
req.ind
³
³
³
³
³
³
INFORM4
³922³
³
³
³
³
³
³<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
INFORM4 ³911³
req.ind
³
³
³
³
³
³ <ÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³
³
ind
³
³
³
³
³
³
³
³
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙFigure 47.1.1.3Receipt of charging rate after TP RETRIEVE (AOC-S)
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
³FE1³ - - - - ra - - - - -³FE2³ - - - - rb - - - - -³FE3³ - - - - rc - - - - -³FE4³
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
³
³
TP RETRIEVE
922³
³
³
³
³
³
³
³
- - - - ->³>>>>³
³
³
³
³
³
³
³
req.ind
³925³
³
³
³
³
³
³
³921³
REQUEST2
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³930³
³
³
³
³
³
³
³931³
³
³
³
³
³
³
³932³
REQUEST3
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³940³
³
³
³
³
³
³
³941³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
REQUEST3
³942³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³933³
resp.conf
³
³
³
³
³
³
REQUEST2
³934³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³924³
resp.conf
³
³
³
³
³
³
³
³
³
³
³
³
³
³914 TP RETRIEVE
922³
³
³
³
³
³
³
³<<<<³<- - - - - ³<<<<³
³
³
³
³
³
³
³
resp.conf
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
INFORM4
³922³
³
³
³
³
³
³<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
INFORM4 ³911³
req.ind
³
³
³
³
³
³<ÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³
³
ind
³
³
³
³
³
³
³
³
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙFigure 5NOTE:The TP RETRIEVE function is a part of the Terminal Portability (TP) supplementaryservice, and the corresponding FEA numbers refer to this service.SIST ETS 300 181:1997



Page 12ETS 300 181: April 19937.1.2Information flows for charging information during a call (AOC-D)7.1.2.1Transfer of charging information at call establishment (AOC-D)
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
³FE1³ - - - ra - - - - ³FE2³ - - - rb - - - - ³FE3³ - - - rc - - - - ³FE4³
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
211 ³
³211
SETUP
221³
³
³
³
³
³
>>>>³
³>>>>³- - - ->³>>>>³
³
³
³
³
³
³
³
req.ind
³221³
³
³
³
³
³
³
³
³
³
³
³
³
³910³
REQUEST1
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³920³
³
³
³
³
³
³
³923³
³
³
³
³
³
³
³921³
REQUEST4
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³930³
³
³
³
³
³
³
³936³
³
³
³
³
³
³
³931³
³
³
³
³
³
³
³932³
REQUEST5
ÃÄÄÄ´
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>³940³
³
³
³
³
³
³
req.ind
³
³
³
³
³
³
³
³
³941³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
REQUEST5
³942³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³933³
resp.conf
³
³
³
³
³
³
REQUEST4
³934³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³924³
resp.conf
³
³
³
³
³
³
SETUP
224³
³
³
³
³
³
³
³<<<<³<- - - -³<<<<³
³
³
³
³
³
³
³
resp.conf
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
INFORM2
³
³
³
³
³
³
³
³<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´922³
³
³
³
³
INFORM
³911³
req.ind
³
³
³
³
³
³
<ÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³925³
INFORM1
³
³
³
³
ind
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³935³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙFigure 67.1.2.2Transfer of charging information during the active state of a call (AOC-D)
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
³FE1³ - - - ra - - - - ³FE2³ - - - rb - - - - ³FE3³ - - - rc - - - - ³FE4³
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
³
³
³
³
³937³
³
³
³
³
³
³
³931³
³
³
³
³
³
³
³932³
REQUEST5
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³940³
³
³
³
³
³
³
³941³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
REQUEST5
³942³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³933³
resp.conf
³
³
³
³
³
³
INFORM5
³934³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³924³
req.ind
³
³
³
³
³
³
INFORM2
³922³
³
³
³
³
³
³<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
INFORM2
³911³
req.ind
³
³
³
³
³
³
<ÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³
³
ind
³
³
³
³
³
³
³
³
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙFigure 7SIST ETS 300 181:1997



Page 13ETS 300 181: April 19937.1.2.3Transfer of charging information at TP HOLD (AOC-D)
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
³FE1³ - - - ra - - - - ³FE2³ - - - rb - - - - ³FE3³ - - - rc - - - - ³FE4³
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
³
³
TP HOLD
921³
³
³
³
³
³
³
³
- - - ->³>>>>³
³
³
³
³
³
³
³
req.ind
³925³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³921³
REQUEST4
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³930³
³
³
³
³
³
³
³931³
³
³
³
³
³
³
³932³
REQUEST5
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³940³
³
³
³
³
³
³
³941³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
REQUEST5
³942³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³933³
resp.conf
³
³
³
³
³
³
REQUEST4
³934³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³924³
resp.conf
³
³
³
³
³
³
³
³
³
³
³
³
³
³913
TP HOLD
921³
³
³
³
³
³
³
³<<<<³<- - - -³<<<<³
³
³
³
³
³
³
³
resp.conf
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
INFORM2
³922³
³
³
³
³
³
³<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
INFORM2 ³911³
req.ind
³
³
³
³
³
³
<ÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³
³
ind
³
³
³
³
³
³
³
³
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙFigure 8NOTE:The TP HOLD function is a part of the Terminal Portability (TP) supplementary service,and the corresponding FEA numbers refer to this service.SIST ETS 300 181:1997



Page 14ETS 300 181: April 19937.1.2.4Transfer of charging information at TP RETRIEVE (AOC-D)
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
³FE1³ - - - - ra - - - - -³FE2³ - - - - rb
- - - -³FE3³ - - - - rc - - - - ³FE4³
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
³
³
TP RETRIEVE
922³
³
³
³
³
³
³
³
- - - - ->³>>>>³
³
³
³
³
³
³
³
req.ind
³925³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³921³
REQUEST4
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³930³
³
³
³
³
³
³
³931³
³
³
³
³
³
³
³932³
REQUEST5
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³940³
³
³
³
³
³
³
³941³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
REQUEST5
³942³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³933³
resp.conf
³
³
³
³
³
³
REQUEST4
³934³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³924³
resp.conf
³
³
³
³
³
³
³
³
³
³
³
³
³
³914 TP RETRIEVE
922³
³
³
³
³
³
³
³<<<<³<- - - - - ³<<<<³202³
³
³
³
³
³
³
resp.conf
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
INFORM2
³922³
³
³
³
³
³
³<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
INFORM2
³911³
req.ind
³
³
³
³
³
³
<ÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³
³
ind
³
³
³
³
³
³
³
³
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙFigure 9NOTE 1:The TP RETRIEVE function is a part of the Terminal Portability (TP) supplementaryservice, and the corresponding FEA numbers refer to this service.NOTE 2:In the case that the called party clears the call during calling party TP-HOLD state, theINFORM2 shall be associated with the TP REJECT information flow.SIST ETS 300 181:1997



Page 15ETS 300 181: April 19937.1.2.5Transfer of charging information at call clearing (AOC-D)7.1.2.5.1Call clearing in forward direction
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
³FE1³ - - - ra - - - - ³FE2³ - - - rb - - - - ³FE3³ - - - rc - - - - ³FE4³
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
³
³
DISC
321³
³
³
³
³
³
³
³
- - - ->³>>>>³
³
³
³
³
³
³
³
req.ind
³925³
³
³
³
³
³
³
³921³
REQUEST4
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³931³
³
³
³
³
³
³
³932³
REQUEST5
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³940³
³
³
³
³
³
³
³941³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
REQUEST5
³942³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³933³
resp.conf
³
³
³
³
³
³
REQUEST4
³934³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³924³
resp.conf
³
³
³
³
³
³
INFORM2
³922³
³
³
³
³
³
³<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
INFORM2 ³911³
req.ind
³
³
³
³
³
³
<ÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³
³
ind
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙFigure 107.1.2.5.2Call clearing in backward direction
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
³FE1³ - - - ra - - - - ³FE2³ - - - rb - - - - ³FE3³ - - - rc - - - - ³FE4³
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
³
³
³
³421
RELEASE
431³
³
³
³
³
³
³
³<<<<³<- - - -³<<<<³
³
³
³
³
³
³
³
req.ind
³
³
³
³
³
³
³925³
³
³
³
³
³
³
³921³
REQUEST4
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³931³
³
³
³
³
³
³
³932³
REQUEST5
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³940³
³
³
³
³
³
³
³941³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
REQUEST5
³942³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³933³
resp.conf
³
³
³
³
³
³
REQUEST4
³934³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³924³
resp.conf
³
³
³
³
³
³
INFORM2
³922³
³
³
³
³
³
³<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
INFORM2 ³911³
req.ind
³
³
³
³
³
³<ÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³
³
ind
³
³
³
³
³
³
³
³
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙFigure 11SIST ETS 300 181:1997



Page 16ETS 300 181: April 19937.1.3Information flows for charging information at the end of a call (AOC-E)7.1.3.1Request for AOC-E at call set-up time (AOC-E)
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
³FE1³ - - - ra - - - - ³FE2³ - - - rb - - - - ³FE3³
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´ 211³
³211
SETUP
221³
³
³
³>>>>³
³>>>>³- - - ->³>>>>³
³
³
³
³
³
req.ind
³
³
³
³
³
³
³
³
³
³
³910³
REQUEST1
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
req.ind
³920³
³
³
³
³
³923³
³
³
³
³
³921³
REQUEST4
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
req.ind
³930³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³224
SETUP
³
³
³
³
³
³<<<<³<- - - -
³
³
³
³
³
³
resp.conf
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³925³
INFORM1
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
req.ind
³935³
³
³
³
³
³
³
³
³
³
³
³
³
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙFigure 127.1.3.2Information flows for AOC at call clearing (AOC-E)7.1.3.2.1Call clearing in forward direction (AOC-E)
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
³FE1³ - - - ra - - - - ³FE2³ - - - rb - - - - ³FE3³ - - - rc - - - - ³FE4³
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
³
³
DISC
321³
³
³
³
³
³
³
³
- - - ->³>>>>³
³
³
³
³
³
³
³
req.ind
³925³
³
³
³
³
³
³
³921³
REQUEST4
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³931³
³
³
³
³
³
³
³932³
REQUEST5
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³940³
³
³
³
³
³
³
³941³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
REQUEST5
³942³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³933³
resp.conf
³
³
³
³
³
³
REQUEST4
³934³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³924³
resp.conf
³
³
³
³
³
³
INFORM2
³922³
³
³
³
³
³
³<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
INFORM2 ³911³
req.ind
³
³
³
³
³
³
<ÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³
³
ind
³
³
³
³
³
³
³
³
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙFigure 13SIST ETS 300 181:1997



Page 17ETS 300 181: April 19937.1.3.2.2Call clearing in backward direction (AOC-E)
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
³FE1³- - - - ra - - - -³FE2³- - - - rb - - - -³FE3³- - - - rc - - - -³FE4³
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
³
³
³
³421
RELEASE
³
³
³
³
³
³
³
³<<<<³<- - - -
³
³
³
³
³
³
³
³
req.ind
³
³
³
³
³
³
³925³
³
³
³
³
³
³
³921³
REQUEST4
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³931³
³
³
³
³
³
³
³932³
REQUEST5
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³940³
³
³
³
³
³
³
³941³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
REQUEST5
³942³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³933³
resp.conf
³
³
³
³
³
³
REQUEST4
³934³
³
³
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³924³
resp.conf
³
³
³
³
³
³
INFORM2
³922³
³
³
³
³
³
³<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
INFORM2 ³911³
req.ind
³
³
³
³
³
³<ÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³
³
ind
³
³
³
³
³
³
³
³
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙFigure 147.1.3.3Information flows at immediate call diversions (AOC-E)ÚÄÄÄ¿
ÚÄÄÄÂ
ÚÄÄÄ¿³FE1³- - - - ra - - - -³FE2³- - - - rb - - - -³FE3³ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´³
³
³
³224
SETUP
³
³³
³
/*leg 1*/³
³<<<<³<- - - -
³
³³
³
³
³
req.ind
³
³³
³
³
³
³
³³
³
³
³221
SETUP
231³
³³
³
/*leg 2*/³
³>>>>³- - - ->³>>>>³
³³
³
³
³
req.ind
³
³³
³
³923³
³
³³
³
³921³
REQUEST4
³
³³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´³
³
³
³
req.ind
³930³³
³
³
³
³
³³
³
³
³
³
³³
³
³
³224
SETUP
³
³³
³
/*leg 2*/³
³<<<<³<- - - -
³
³³
³
³
³
resp.conf
³
³³
³
³
³
³
³³
³
³
³
³
³³
³
³925³
INFORM1
³
³³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´³
³
³
³
req.ind
³935³³
³
³
³
³
³ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙNOTE:Leg 1 refers to the leg between the calling and the forwarding user.Leg 2 refers to the leg between the forwarding and the forwarded-to user.Figure 15Call clearing of the forwarded call in either direction as in subclause 7.1.3.2.SIST ETS 300 181:1997



Page 18ETS 300 181: April 19937.1.3.4Information flows when diversion of a call occurs after the call has been presented(AOC-E)
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
³FE1³- - - - ra - - - - - -³FE2³- - - - - rb - - - - ³FE3³
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
³
³251
REPORT(alert) 244³
³
³
³
³
³>>>>³- - - - - ->³>>>>³
³
³
³
³
³
req.ind
³
³
³
³
³
³
³
³
³
³
³
³
³
³241
SETUP
³
³
³
³
/*CFNR 945 >>>>³
³>>>>³ - - - - ->
³
³
³
³
leg 2*/
³
³
req.ind
³
³
³
³
³
³
³
³
³
³
³921³
REQUEST4
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
req.ind
³930³
³
³
³
³
³
³
³
³
³
³245
SETUP
³
³
³
³
/*leg 2*/ ÃÄÄÄ´<<<<³<- - - - -
³
³
³
³
³
³
resp.conf
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³925³
INFORM1
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
req.ind
³935³
³
³
³
³
³
³
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙNOTE:Leg 1 refers to the leg between the calling and the forwarding users.Leg 2 refers to the leg between the forwarding and the forwarded-to users.Figure 16Call clearing in either direction as in subclause 7.1.1.2.Addressing information indicating the AOC-served user must be included in all cases where the FE1 is notlocated at a CCA, e.g. when CFU takes place and AOC is given to the user having invoked CFU.When the AOC-served user is not a part of the basic charged call (i.e. at CFU, CFB, CFNR, CD) or thecall has been transferred (CT has been invoked), then the charged number and the dialled number shall begiven together with the AOC.
The same requirement exists when the AOC-served user is a "third party"(e.g. in hotel PTNXs).SIST ETS 300 181:1997



Page 19ETS 300 181: April 19937.1.3.5Information flows for AOC at call failure during call establishment (AOC-E)
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
ÚÄÄÄ¿
³FE1³ - - - ra - - - - ³FE2³ - - - - rb - - - ³FE3³ - - - rc - - - - -³FE4³
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
ÃÄÄÄ´
211³
³
SETUP
221³
³
³
³
³
³
>>>>³
³>>>>³- - - ->³>>>>³
³
³
³
³
³
³
³
req.ind
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³910³
REQUEST1
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³920³
³
³
³
³
³
³
³923³
³
³
³
³
³
³
³921³
REQUEST4
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³
req.ind
³930³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³421
RELEASE
³
³
³
³
³
³
³
³<<<<³<- - - -
³
³
³
³
³
³
³
³
req.ind
³
³
³
³
³
³
³
³
³
³
³
³
³
³
³
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.