Internet Standards/CD2.mdf/ccitt/1992/i/i210.asc

Text File | 1993-06-28 | 54KB | 2,090 lines

Recommendation I.210 - Principles of telecommunication services supported by an ISDN and the means to describe them



1.    General



    An ISDN will support a wide range of services as described generally in Recommendation I.120. The purpose of this
Recommendation is to provide a classification of such services, the means for the description of such services based on
the description method as defined in RecommendationI.130 as well as giving a basis for the definition of the network
capabilities required by an ISDN. These network capabilities are defined in the I.300-Series of Recommendations.



    Using the service concept and the means for the description of services as given in this Recommendation, recom-
mended bearer services are defined and described in the I.230-Series of Recommendations, recommended teleservices are
defined and described in the I.240-Series of Recommendations and recommended supplementary services are defined and
described in the I.250-Series of Recommendations.



2.    Service concepts



2.1    Services supported by an ISDN are the communication capabilities made available to customers by telecommunication
service providers. An ISDN will provide a set of network capabilities which are defined by standardized protocols and func-
tions and enable telecommunication services to be offered to customers.



    A service provision by a telecommunication service provider to a customer connected to an ISDN may cover the whole
or only part of the means required to fully support the service. The operational and commercial features associated with
provision of the service are included in the service concept.



    The service classification and descriptions which follow are independent of different possible arrangements for owner-
ship and provision to the customer of the means required to support a service. The customer may therefore be offered, by
the administration/RPOA, services or service support.



2.2    The method used for the characterization of telecommunication services is described in Recommendation I.130 "The
method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN".
Within this method the first stage is an overall service description from the user's point of view. In stage 1 there are three
steps:



    Step 1.1    Prose service definition and description



    Step 1.2    Static description of the service using attributes



    Step 1.3    Dynamic description of the service using graphic means



    Together these three steps define the service characteristics as they apply at a given reference point where the cus-
tomer accesses the service.



    Annexes A to D of this Recommendation give the format of Stage 1 service descriptions as follows:



    Annex A: Structure for prose service definition and description



    Annex B: List of attributes and their possible values for describing

                  bearer services



    Annex C: List of attributes and their possible values for describing

                  teleservices



    Annex D: Dynamic description of the service using graphic means



Note 1 - Recommendation I.140 describes the use of attributes for this purpose.



Note 2 - The use of attributes for describing supplementary services is for further study.



    This format allows the information contained within Stage 1 to be structured in a consistent, comprehensive and logical
manner. Only one overall format is recommended but it is recognized that certain sections of this format are only appli-
cable to certain types of services.



2.3    Telecommunication services are classified using their static characteristics described by attributes. Therefore this Rec-
ommendation (except Annexes A and D) deals mainly with Step 1.2 of the description method.



    A telecommunication service is, from the static point of view, composed of:



    -    technical attributes as seen by the customer; and



    -    other attributes associated with the service provision, e.g. operational and commercial attributes.



    Realization of the technical attributes of a telecommunication service requires a combination of network and terminal
capabilities and other service providing systems.



2.4    Telecommunication services are divided in two broad families, i.e.,



    -    bearer services, and



    -    teleservices.



    A supplementary service modifies or supplements a basic telecommunication service. Consequently, it cannot be offered
to a customer as a stand alone service. It must be offered together with or in association with a basic telecommunication
service. The same supplementary service may be common to a number of telecommunication services.



Note - The concept of supplementary services corresponds to the concept of optional user facilities in the X-Series of
Recommendations.



    The concepts introduced here are illustrated in Table 1/I.210 and are defined in more detail in _ 5.



TABLE 1/I.210



Classification of telecommunication services





+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+  |                             TELECOMMUNICATION SER-
VICE                        |+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|           BEARER SERVICE                |           TELESERVICE              |+ûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûû+û
ûûûûûûûûûûûûûûûûûû+

| Basic bearer   | Basic bearer service + | Basic          | Basic teleservice | |service        | supplementary services |
teleservice    | + supplementary   | |               |                        |                | services          |+ûûûûûûûûûûûûûû
ûû+ûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûû+

                                                                               3.    Customer access to telecommunication
services supported                        by an
ISDN
                     3.1    Considering the reference configurations defined in RecommendationI.411, customers can access
various telecommunication services at different access points. Figure 1/I.210 shows these access points.                                                                                                 This figure takes
into account that the network provider may offer to a customer connected to an ISDN the whole or only part of the means
to fully support the service.

























                                                              T1806880-88



FIGURE 1/I.210



Customer access to services supported by an ISDN

3.2    The definitions of the access points introduced in Figure1/I.210 are as follows:



    i)    access points 1 (reference point T) and 2 (reference point S) are the access points for bearer services sup-
ported by an ISDN. The choice between access point 1 (T) and 2 (S) depends on the ownership and form of provision
(to the customer) of the communications equipment at the customer premises. The service classification and descrip-
tions in the following are independent of different possible arrangements for such provision;



    ii)    at access point 4 (reference point R), depending on the type of terminal adaptors provided, other CCITT stan-
dardized services may be accessed, e.g. according to the X- and V-Series of Recommendations;



    iii)    at access points 3 and 5 (user-to-terminal interface), teleservices are accessed - the teleservice concept
includes the terminal capabilities.



3.3    The following customer entities may be connected at access

points 1 and 2:



    -    customer terminals;



    -    customer systems, e.g. PABXs, LANs, service vendor systems;



    -    private networks.



Note - Customer terminals and systems may be private or provided by administrations or RPOAs.



    All customer equipment connected to an ISDN interface at one of these access points should meet the specifications
of the protocols at that interface for all the layers that are included in the definition of the telecommunication service
used.



    For some telecommunication services the service definition also covers some terminal functions and characteristics in
addition to those specified by the protocols at the interface. This relates in particular to teleservices, and also to supple-
mentary services (see Recommendation I.250).



3.4    From the user's point of view the telecommunication services as defined in the I.200-Series of Recommendations will
be used for some applications.

For example, the telephony teleservice will be typically used for a human conversation (application). Likewise bearer ser-
vices will be used for applications. The area of applications is outside the scope of the I-Series of Recommendations. The
user's application of services is the responsibility of the user and not of the network. The network can have no knowledge
of what application is being used at any time.



3.5    The telecommunication service, as described in this Recommendation, is time-independent, that is to say that the
description is valid for all the time the service is available. Whenever a demand or reserved service is invoked by a user,
then the particular instance of the service is referred to as a CALL.  Similarly, the instance also applies to the application
as described in section3.4. The instance of an application is referred to as a COMMUNICATION.



4.    Capabilities to support a telecommunication service



4.1    The capabilities required to fully support a telecommunication service for a customer connected to an ISDN include:



    -    network capabilities;



    -    terminal capabilities, when required;



    -    other services providing capabilities, when required;



    -    operational and commercial features associated with the service provision (i.e. sales or marketing aspects).



4.2    Network capabilities are described in detail in RecommendationI.310.  Two different levels of ISDN network capabilities
are introduced in that Recommendation:



    -    low layer capabilities which relate to bearer services;



    -    high layer capabilities which together with low layer capabilities relate to teleservices.



    The low layer capabilities are defined as a set of Low Layer Functions(LLF) (relating to layers 1-3 in Recommendation
X.200) which provide the capability for the carriage of user information over an ISDN connection.



    These functions include:



    -    Basic Low Layer Functions (BLLF) supporting the necessary layer1-3 requirements;



    -    Additional Low Layer Functions (ALLF) supporting, in addition to BLLFs, lower layer requirements of supplemen-
tary services.



    High Layer Capabilities are defined as a set of High Layer Functions(HLF)generally associated with layers 4-7 in Rec-
ommendation X.200.



    High Layer Functions are sub-divided into Basic High Layer Functions(BHLF) and additional High Layer Functions
(AHLF).



Note - Dependent upon national regulations, ALLF, BHLF, and AHLF may be provided by administrations, RPOAs or other
suppliers.



4.3    The concept of describing network capabilities in terms of Low Layer Capabilities and High Layer Capabilities can equally
be applied to describe terminal capabilities. In the description of teleservices the HLF and LLF are included in the service
definition. In the case of bearer service definition the terminal capabilities are not included but the terminal must conform
to the LLF of the bearer service.



Note - The relationships between service categories, network/terminal capabilities and functions are illustrated in Table 2/
I.210.



4.4    The operational service capabilities associated with a service offering may include capabilities for maintenance, charg-
ing, user control of service features, etc.



    The use of such capabilities may involve terminal-network communication and may therefore be viewed as specific
applications.



    A more precise description of these capabilities and the relationship to Recommendation X.200 needs further study.



TABLE 2/I.210



Relationship between service families, network/terminal

capabilities and functions















































X: specified        opt: optional           -: not specified



Note - Dependent upon national regulations, ALLF, BHLF and AHLF may be provided by administrations, RPOAs or other
suppliers.



5.    Telecommunication service classification



5.1    The static characteristics of a telecommunication service supported by an ISDN are described by service attributes.
They are given in Annexes B and C of this Recommendation.



    There are two groups of service attributes applicable to user information flow:



    -    low layer attributes;



    -    high layer attributes.



    Bearer services are defined as including only Low Layer Attributes. Teleservices are defined as including both Low Layer
Attributes and High Layer Attributes.



    The relationship between telecommunication service attributes and low/high layer functions is illustrated in Table 3/
I.210.



TABLE 3/I.210



Relationship between service attributes and

low/high layer functions



















































                                                             T1806890-88





Notes to Table 3/I.210



Note 1 - A supplementary service cannot be offered as a stand alone service. This attribute is mainly concerned by sup-
plementary services associated to basic telecommunications services. It could be split into sub-attributes depending on
results of further studies. Supplementary services could also have an influence on some attributes characterizing basic
telecommunication services.



Note 2 - The characterization of supplementary services using attributes requiresfurther studies.



5.2    Bearer services supported by an ISDN



5.2.1    Bearer services supported by an ISDN provide the capability for information transfer between ISDN access points 1 or
2 and involve only low layer functions.



    The customer may choose any set of high layer (at least 4-7) protocols for his communication, and the ISDN does not
ascertain compatibility at these layers between customers. An example of a bearer service is a switched circuit- mode 64
kbit/s unrestricted digital information service.



5.2.2    Bearer services are characterized from a static point of view by a set of low layer attributes given in Annex B of this
Recommendation. These attributes are classified into three categories:



    -    information transfer attributes;



    -    access attributes; and



    -    general attributes, including operational and commercial attributes.



    The bearer capability defines the technical features of a bearer service as they appear to the user at the appropriate
access point (1 or 2).



    The bearer capability is characterized by information transfer and access attributes. A bearer capability is associated
with every bearer service.



Note - It is likely that some quality of service parameters - such as error rate or call set-up delay - should be extracted
in order to form a new attribute allocated to the information transfer category. Identification and definition of such param-
eters require further consideration.



    Individual bearer services categories are defined and described in the I.230-Series of Recommendations.



5.2.3    A bearer service provides the user with the possibility of gaining access to various forms of communication, covering
for example:



    -    information transfer between users employing the same access points (1 or 2) and access attributes (see Fig-
ure2a/I.210);



    -    information transfer between users employing different access attributes at the access points (1 or 2) involved,
(see Figure2b/I.210); and



    -    information transfer between a user and a separate resource providing high layer functions (see Figure2c/
I.210).





















































                                                           T1806900-88





        Access points 1 and 2, see Figure 1/I.210



* Access point to be defined but not necessarily subject to CCITT  Recommendations (see Recommendation I.324).



Note 1 - Further study is required on bearer services extending beyond the ISDN.



Note 2 - Further study is required on possible communications involving bearer services with different values allocated to
information transfer attributes.



FIGURE 2/I.210



Examples of bearer service operation





5.3    Teleservices supported by an ISDN



5.3.1    Teleservices provide the full capacity for communication by means of terminal and network functions and possibly
functions provided by dedicated centres.



    A teleservice supported by an ISDN should use only one (or a small number of) bearer capability(ies) recommended by
the CCITT. It should be noted that in the case where more than one of the recommended bearer capabilities is used for a
given teleservice, network interworking functions may be required under the responsibility of the teleservice provider. How-
ever, a user operating a specific application is not prevented from using a terminal compatible with a given teleservice in
association with a bearer capability not recommended for this teleservice. Examples of teleservices are telephony, Teletex
and Videotex.



5.3.2    Teleservices are described from a static point of view by a set of low layer and high layer attributes, and operational
and commercial attributes, as given in Annex C of this Recommendation.



    Low layer attributes are those used to characterize the bearer capability (see section5.2.2). High layer attributes are
used in RecommendationI.241 to describe message (i.e. message on layer 7) related characteristics of a service (basic
high layer attributes) or of a supplementary service (supplementary high layer attributes). They refer to the functions and
protocols of layers4-7 in the Recommendation X.200 framework which are concerned with the transfer, storage and pro-
cessing of user messages (provided by a subscriber's terminal, a retrieval centre, or a network service centre).



    Therefore, not all these attributes can be applied directly at the user to terminal interface (access points 3 or 5) as
they represent two kinds of features, the bearer capability and the terminal features, that are not directly perceivedby the
user.



    The definition of appropriate attributes and the specifications of teleservices at this access point from the user point
of view (man-machine interface) is for further study and the subject of E-and F-Series of Recommendations.



    Individual teleservices are defined and described in the I.240-Series of Recommendations.



5.3.3    A teleservice provides the user with the possibility of gaining access to various forms of applications (or teleservice
applications) covering, for example:



    -    teleservice application involving two terminals providing the same teleservice attributes at both access points (3
or 5) - (see Figure 3a/I.210);



    -    teleservice application involving a terminal at one access point (3 or 5) and HLF functions located within the
ISDN - (see Figure3b/I.210);



    -    teleservice application involving terminals based on different teleservice attributes at each access point - in
this case, the use of HLF functions in the ISDN is necessary (interworking situation) - (see Figure3c/I.210);



    -    teleservice application involving a terminal at one access point (3 or 5) and a system providing HLF functions
(see Figure 3d/I.210);



    -    teleservice application involving two terminals at both access points (3 or 5) and an intervening system pro-
viding HLF functions (see Figure3e/I.210). In this case, teleservice attributes can be different at each terminal
access point.



























































FIGURE 3/I.210



Examples of teleservice application



5.4    Supplementary services supported by an ISDN



    Supplementary services supported by an ISDN provide additional capabilities to be used with bearer services and
teleservices. They cannot be offered to a customer as a stand alone service.



    Supplementary services are characterized by a prose definition and description following the layout given in Annex A
and a dynamic description applying the means given in Annex D.



    The use of the attribute technique for supplementary services is for further study. The individual supplementary services
are described in the

I.250-Series of Recommendations.



6.    Provision of telecommunication services



6.1    A telecommunication service is provided by an administration, RPOA and/or other service providers. Customer terminals
and systems may be privately owned or provided by administrations or RPOAs. Depending on the nature of customer own-
ership within the customer premises (TE or TE and NT2), a telecommunication service is provided at different access
points.



6.2    The provision of telecommunication services implies:



    -    subscription ensuring the basic service and possibly subscription to supplementary services;



    -    registration into a service directory in the case where demand services are used;



    -    compatibility between terminals;



    -    interworking capabilities (this point needs further study).



6.3    The provision of individual bearer services is given in the

I.230-Series of Recommendations, the provision of individual teleservices is given in the I.240-Series of Recommendations
and the association of supplementary services to bearer services and teleservices is given in Recommendation I.250.









ANNEX A



(to Recommendation I.210)



Structure for prose service definition and

description - step 1.1 of description method (Recommendation I.130)





A.1    Structure of prose service definition and description



    Prose service definition and description is the first step (1.1) of the Stage 1 overall service description from the user's
point of view (RecommendationI.130). The prose definition of a telecommunication service will be structured as follows:



1.    Definition



2.    Description



2.1    General description



2.2    Specific terminology



2.3    Qualifications



3.    Procedures



3.1    Provision/withdrawal



3.2    Normal procedures



3.2.1    Activation/deactivation/registration



3.2.2    Invocation and operation



(3.2.3    Interrogation/editing)



3.3    Exceptional procedures



3.3.1    Activation/deactivation/registration



3.3.2    Invocation and operation



(3.3.3    Interrogation/editing)



3.4    Alternative procedures



3.4.1    Activation/deactivation/registration



3.4.2    Invocation and operation



(3.5    Verification)



4.    Network capabilities for charging



5.    Interworking requirements



6.    Interaction with other supplementary services



Note 1 - Where a particular section would not be appropriate for a particular service (basic or supplementary) "not appli-
cable" appears in that section for that service. Some such items have been identified by paragraph numbering in paren-
thesis.



Note 2 - Where information contained under one item (e.g. 3.2.1) for a particular service is extensive, then this item may
be further sub-divided under sub-headings as necessary.



A.2    Explanation of the terms and content of the items in the

    service prose definition and description



1.    Definition



    This paragraph provides a short description of the service in terms of the perceptions of the user receiving the service
and any other users involved in the service.



2.    Description



    This paragraph expands on the definition and summarizes the operation of the service in a generic form which does
not constrain terminal or network design. It is intended to allow an understanding of the service without regard to imple-
mentation. It also includes any specific terminology used within the prose definition and description, and any qualifications.
For basic services this section details the applications which could utilize the service whilst for supplementary services this
section details their applicability to particular telecommunication services.



3.    Procedures



    The overall operation of the service in its various states is described in this section 3. These procedures relate to all
actions between the user(s)  and the network during the period that the service is available.



3.1    Provision/withdrawal



    This paragraph describes the means by which the service is made available by the service provider e.g. it may be gen-
erally available to all customers, or, only be available to those customers who have made a prior arrangement.



3.2    Normal procedures



    The paragraphs under this heading describe the normal procedures for activation, deactivation, registration, invocation
and operation for the service as appropriate. This section describes only the successful outcome of each procedure, and
the procedures which are executed as a result of such successful outcomes. The procedures are described in a time-
based sequence of events. They describe the interactions of the users involved in the service with the service provider and
with each other which lead to and are elements of the successful operation of the service.



3.2.1    Activation/deactivation/registration



    The procedures for activation, which is the operation of bringing the service into the "ready for invocation" state, and
deactivation, which is the complementary action, are described in this paragraph. For some services there may be a spe-
cific user procedure to allow activation and deactivation as necessary, whilst for others the service is permanently activated
on provision and thus no procedure is provided.



    Registration describes the procedures by which any specific information, necessary for the successful operation of the
supplementary service, is given to the network. The need to register information with the network e.g. a forwarding number,
only applies to certain supplementary services.



3.2.2    Invocation and operation



    This paragraph describes the procedures for invocation, which is the action and conditions under which the service is
brought into operation, which in the case of a supplementary service may only be on a particular call. It should be noted
that although a supplementary service may be activated, it may not necessarily be invoked on all calls. (Invocation takes
place either subsequent to or simultaneously with activation.)



    In the case of basic services this section describes the events, perceived at the service access point, during the
establishment, information transfer and clearing phases.



    Operation is the procedure which occurs once a service has been invoked. In the case of a supplementary service this
is described in terms of the way in which the supplementary service modifies/enhances the network's treatment of a call.
This description gives details of the significant actions of the network, treated in principle as a single entity, and the per-
ception of the users involved on the call. It includes details of the information exchanged between the network and relevant
users and the indications given to each user, by the network, concerning the states of the call.



3.2.3    Interrogation/editing



    Interrogation is the facility which enables a served user to determine, from the service provider, the current status of
a particular service. Whether this facility is provided for the service being described, and if so the procedures that accom-
pany it, are detailed in this paragraph.



    Editing describes the process whereby any registered information (see paragraph 3.2.1) specific to a service may be
erased or modified by the served user.



3.3    Exceptional procedures



    The paragraphs under this heading describe, for each of the items shown under paragraph 3.2, the exceptional proce-
dures which result in an unsuccessful outcome of the call. Included within this description are the details for such situa-
tions as invalid user action and the handling of certain network and interface conditions. For the case of basic services this
includes the handling of such network conditions as congestion.



3.4    Alternative procedures



    The paragraphs under this heading describe any alternative procedures, where available, for each of the items shown
under paragraph 3.2. These either allow an alternative way of activating or invoking the service, or detail a possible alter-
native treatment of the call by the network.



3.5    Verification



    This paragraph describes the facilities that are provided by the network to enable the subscriber to verify the operation
of the service once it has been activated. Not all services allow provision for verification of the operation of the service.



4.    Networking capabilities for charging



    This paragraph details only those charging aspects specific to the service in question and includes, where necessary,
both static (subscription)  and dynamic (call related) aspects.



5.    Interworking requirements



    This section describes special aspects of the individual service, if the service is used in a connection which exists partly
inside and partly outside a given ISDN, or for certain operational aspects, which routes through more than one ISDN.



6.    Interaction with other supplementary services



    This section only applies in the case of supplementary services and describes all interactions of the supplementary
service being described with other supplementary services as far as they have been identified and which are of relevance
to be standardized.



    For example, for some supplementary service pairs there is no interaction as the two supplementary services are not
permitted to both be in operation at the same time. For other pairs, one or both supplementary services may be modified
whilst the pair of services are in operation simultaneously.



    It is recognized that although the layout, and the detailed work to date, has only dealt with the interactions between
two supplementary services, further work is necessary on combinations of more than two supplementary services.









ANNEX B



(to Recommendation I.210)



List of attributes and their possible values for describing

bearer services - step 1.2 of description method (Recommendation I.130)





B.1    Framework for the static description of bearer services

    supported by an ISDN



    Static description of the service using attributes is the second step (1.2) of the Stage 1 overall service description
from the user's point of view (Recommendation I.130). These attributes are described and defined in Recommendation
I.140. Attributes to describe bearer services are intended to be independent and are grouped into three categories:



    i)    information transfer attributes which characterize the network capabilities for transferring information from one
S/T reference point to one (or more) other S/T reference points, corresponding to access point 2 and 1 as defined
in Recommendation I.210;



    ii)    access attributes which describe the means for accessing network functions or facilities as seen at one S/T
reference point; and



    iii)    general attributes which deal with the service in general.



    Figure B-1/I.210 shows the relation between the groups of attributes and their fields of applicability.



































FIGURE B-1/I.210



Relationship between the groups of attributes and

fields of applicability





    Table B-1/I.210 gives the list of the attributes. For the definitions and possible values of these attributes, see Rec-
ommendation I.140.



TABLE B-1/I.210



List of attributes





Information transfer attributes



    1 - Information transfer mode



    2 - Information transfer rate



    3 - Information transfer capability



    4 - Structure



    5 - Establishment of communication



    6 - Symmetry



    7 - Communication configuration



Access attributes (Note)



    8 - Access channel and rate



    9 - Access protocol



General attributes



        10 - Supplementary services provided



        11 - Quality of service



        12 - Interworking possibilities



        13 - Operational and commercial



Note - Different access attributes may apply at each of the (two or more) network interfaces involved in the use of a
bearer service.



    Figure B-2/I.210 presents a list of possible values for each attribute. Where options exist for a given attribute, the
selection is subject to agreement between the customer and the administration or RPOA.



    According to Recommendation I.210 the bearer capability defines the technical features of a bearer service as they
appear to the user at the S/T reference point. The bearer capability is characterized by information transfer and access
attributes. A bearer capability is associated with every bearer service.



+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+  |Attributes (Note 5)|Possible values of attributes| +û
ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûû+

|Information transfer attributes    |                                                 |                       | |1. Information
transfer mode|Circuit|Packet| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûû+

|2. Information transfer rate       |Bit rate kbit/s|Throughput| |                                  +ûûû+ûûûûû+ûûû+ûûûû+ûûûûûû+ûûûûûûûûû
ûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûû+

|                                   |64|2x64|384|1536|1920|Other values for|Options for further| |                                   |
|     |   |    |     |further study|study| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûû+ûûûûû+ûûû+ûûû++ûûûûûû+ûûûûûûûû+ûûûûûûû+ûûûûûû+ûûûûûûû+ûûûûûûûûûûûûûûûû+

|3. Information transfer capability|Unrestricted|Speech |3.1 kHz|7 kHz|15 kHz| Video | Others for     |
|                                   |digital|      |audio|audio|audio |       | further study  | |                                  |infor-
mation|       |        |       |      |       |                |+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûû+ûûûûûûû+ûûûûûûûû+ûûûûûûû+ûûûûûû+ûûûûûû
û+ûûûûûûû+ûûûûûûûû+

|4. Structure|8 kHz integrity|Service data unit|Unstructured  |TSSI   |   RDTD | |                                   |                 |
integrity|              | (7)   |    (7) |+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûû+ûûûûûûû+ûûûûûûûû+

|5. Establishment of communication|Demand|     Reserved|Permanent| |   (Note 4)|                 |                       |
|+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|6. Symmetry|Unidirectional|Bidirectional symmetric|Bidirectional asymmetric| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûû
ûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|7. Communication configuration|Point-to-point|Multipoint|Broadcast(Note 1)| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûû+ûûûûûûûûûûû+ûûûû+ûûûû+ûûû
ûûû+ûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|Access attributes|     |           |    |    |      |       |                              | |8. Access channel and rate|D(16)|-
D(64)|B|H0|H11| H12|Others for further study| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûû+ûûûûû+ûûûûû+ûûûû+ûûûû+ûûûûûû+ûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|9.1 Signalling access|I.430/I.431|I.461|I.462|I.463|(V.120)|Others FS| |    protocol Layer 1|           |     |        |      | I.465
|                               |+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûû+ûûûûû+ûûûûûûûûû+ûûûûûû+ûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|9.2 Signalling access|                 |         |      |                                      | |    protocol Layer 2|I.440/
I.441|I.462|X.25|Others FS| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûû+ûûûûûûû+û+ûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûû+

|9.3 Signalling access|I.450/I.451|I.461|I.462|X.25|I.463|Others FS| |    protocol Layer 3|                 |       |       |       |
|                       |+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûû+ûûûûûûû+ûûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûû+

+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|Attributes (Note 5)|Possible values of attributes| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûû+ûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûû+ûûûûû+ûûûûûûû
ûûûû+

|9.4 Information access|I.430/I.431|I.460|I.461|I.462|I.463|(V.120)|G.711|G.722|Others FS| |    protocol Layer 1|           |(Note
|      |       |       |I.465|     |     |           | |                                  |           |6)|       |       |       |
|     |     |           |+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûû+ûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûû+ûûûûû+ûûûûûûûûûûû+

|9.5 Information access|HDLC LAP B|X.25I.462|Others FS| |    protocol Layer 2|           |
|                               |+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|9.6 Information access|T.70-3|X.25I.462|Others FS| |    protocol Layer 3 (Note 3)|           |                              |
|+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|General attributes|                                                                         | |10. Supplementary services|
| |   provided|Under study| |11. Quality of service|                                                                         | |12.
Interworking possibilities|                                                                         | |13. Operational and commercial|
|+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+



Note 1 - The characterization of the information transfer configuration attribute "broadcast" is for further study.

Note 2 - The need for a "data sequence integrity" attribute is for further study.

Note 3 - The use of Recommendation I.451 as an information access protocol is for further study.

Note 4 - A definition of the establishment of communication is given in I.140.

Note 5 - The attributes are intended to be independent of each other.

Note 6 - The inclusion of I.460 implies the support of non-ISDN CCITT standardized services (e.g. at X.1 rate).

The necessary user-network signalling is provided in Recommendation I.451.

Note 7 - TSSI = Time slot sequence integrity; RDTD = Restricted differential time delay.



FIGURE B-2/I.210



Values for each bearer service attribute

ANNEX C



(to Recommendation I.210)



List of attributes and their possible values for

describing teleservices - step 1.2 of description

method (Recommendation I.130)



C.1    Framework for the static description of teleservices supported

    by an ISDN



    Static description of the service using attributes is the second step (1.2) of the Stage 1 overall service description from
the user's point of view (Recommendation I.130). These attributes are described and defined in Recommendation I.140.



    Attributes to describe teleservices supported by an ISDN are intended to be largely independent. They are grouped into
three categories:



    a)    low layer attributes



        -    information transfer attributes,

        -    access attributes;



    b)    high layer attributes;



    c)    general attributes.



Note - Teleservices generally make use of underlying lower layer capabilities of bearer services specified in the I.230-Series
of Recommendations. However, where teleservices are provided by a single administration, RPOAs or other service providers,
the combination of values of lower layer attributes applicable to specific teleservices may not necessarily be identical to any
of those identified for the bearer services appearing in the I.230-Series of Recommendations.



    Figure C-1/I.210 shows the relationship between the different categories of service attributes and their scope within a
teleservice.































                                                           FIGURE C-1/I.210



Relationship between the categories of service

attributes and their scope with a teleservice



C.2    List of the teleservice attributes



C.2.1    Low layer attributes



Information transfer attributes



    1.    Information transfer mode



    2.    Information transfer rate



    3.    Information transfer capability



    4.    Structure



    5.    Establishment of communication



    6.    Symmetry



    7.    Communication configuration



Access attributes



    8.    Access channel and rate



    9.1    Signalling access protocol Layer 1



    9.2    Signalling access protocol Layer 2



    9.3    Signalling access protocol Layer 3



    9.4    Information access protocol Layer 1



    9.5    Information access protocol Layer 2



    9.6    Information access protocol Layer 3



C.2.2    High layer attributes



    10.    Type of user information



    11.    Layer 4 protocol functions



    12.    Layer 5 protocol functions



    13.    Layer 6 protocol functions



        -    Resolution    ) if applicable         -    Graphic mode  ) (Note 1)



    14.    Layer 7 protocol functions



        -    TE-to-TE protocol functions  ) if applicable

        -    TE-to-HLF protocol functions ) (Note 2)



C.2.3    General attributes



    15.    Supplementary services provided



    16.    Quality of service



    17.    Interworking possibilities



    18.    Operational and commercial



    Figure C-2/I.210 presents a list of possible values for each service attribute. Where optional values of given attributes
are offered, their selection is subject to agreement between the customer and service provider.



+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+  |Attributes (Note 3)|Possible values of attributes|
+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûû+

|Information transfer attributes|                                            |                         | |1. Information transfer
mode|Circuit|Packet| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûû+

|2. Information transfer rate|Bit rate [kbit/s]|Throughput| |                                       +ûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû
ûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûû+

|                                        |64|Other values for further study|Options for further study| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû
ûûû+ûûûû+ûûûûûûûû+ûûûûûûûû+ûûûûûûûûûûûû+ûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûû+

|3. Information transfer capability|Unrestricted|Speech|3.1 kHz|7 kHz|Others for further study|
|                                        |digital|       |audio|audio|                         | |
|information|        |            |         |                         |+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûû+ûû+ûûûûû+ûûûûûûûûûûûû+û+û
ûûûûûû+ûûûûû+ûûûûûûûûûûûûûûûûûûû+

|4. Structure|8 kHz integrity|Service data unit|Unstructured|Others for further| |
|               |integrity|             |study| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûû+ûûû+ûûûûûûûûû+ûûûûûûûûûûûûûûûûûûû+

|5. Establishment of communication|Demand|Reserved|Permanent| |   (Note 2)                             |                |
|                             |+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|6. Symmetry|Undirectional |Bidirectional symmetric|Bidirectional asymmetric| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûû
ûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|7. Communication configuration|Point-to-point|Multipoint|Broadcast (Note 1)| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûû+ûûûûûû+ûû+ûûûû+ûû
ûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|Access attributes|      |      |       |                                                | |8. Access channel and rate|D(16))|-
D(164)|B|Others for further study| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûû+ûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûû+

|9.1 Signalling access protocol Layer 1|I.430/I.431|I.461|.462|I.463|I.465|Others FS| |                                        |
|       |      |       |(V.120)|                         |+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûûûûûûûûû
ûûûûûûûûûûû+

|9.2 Signalling access protocol Layer 2|I.440/I.441|I.462|X.25|Others FS| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûû
û+ûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûû+

|9.3 Signalling access protocol Layer 3|I.450/I.451|I.461|I.462|X.25|I.463|Others FS| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûû+ûûûûûûû
+ûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûû+

(Cont.) +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+  |Attributes (Note 3)|Possible values of
attributes| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûûûû+

|9.4 Information access protocol Layer 1|I.430/I.431|I.460|I.461|I.462|I.463|I.465 |G.711|Others FS|
|                                        |             |      | (X.30)| (X.31)|(V.110)|(V.120)|       |         |+ûûûûûûûûûûûûûûûûûûûûûûûûû
ûûûûûûûûûûûûûûû+ûûûûûûû+ûûûûû+ûû+ûûûû+û+ûûûûû++ûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûûûûûû+

|9.5 Information access protocol Layer 2|HDLC|I.440/|X.75|X.25|Others FS| |                                        |LAP B|I.441|S-
LP|LAP B|                                        |+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûû+ûûûû+ûûû+ûûûûûû+ûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|9.6 Information access protocol Layer 3|IS0 8208   |     X.25        |            Others FS                  |
|                                        | (X.25 PLP) |    PLP         |                                        |+ûûûûûûûûûûûûûûûûûûûû
ûûûûûûûûûûûûûûûûûûûû+ûûûûûûû+ûûûû++ûûûûûû+ûûûûûûûûû+ûûûûûûûûû+ûûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûû+

|10. Type of user information|Speech |Sound|Text|Facsimile|Text|Videotex|Video|Text|Other| |
|(Tele- |    |(Tele-|(Telefax |facsimile|        |       |inter-|     | |                                       | phony)|     | tex)|
4)|(Mixed|        |       |active|     | |                                       |       |     |      |         | mode)|       |
|(Telex)|     |+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûû+ûûûû++ûûûûûû+ûûûûûû+ûû+ûûûûûûûûû+ûûûûûûûû+ûûûûûûû+ûûûûûûû+ûûûûû+

|11. Layer 4 protocol|X.224|T.70|Others| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûû+ûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|12. Layer 5 protocol|X.225|T.62|Others| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûû+ûûûû+ûûû+ûûûûûûûûûû+ûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|13. Layer 6 protocol|T.400-|G.711|T.61|T.6|Others| |                                       |Series|        |          |       |
|+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûû+ûûûûûûûû+ûûûûûûû+ûû+ûûû+ûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|Resolution (Note) (Note 5)|200|240|300|400|Others| |                                       |ppi|ppi|ppi|ppi|| +ûûûûûûûûûûûûûûûûûûûûûûûûûû
ûûûûûûûûûûûûûû+ûûûûûûû+ûûûûûûûû+ûûûûûûû+ûûû+ûû+ûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûû+

|Graphic mode (Note) (Note 6)|Alpha-mosaic|Geometric|Photographic|Others| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûû+ûû+ûûûûûûûûûûû
+ûû+ûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûû+

|14. Layer 7 protocol|T.60|T.500-Series|Others| +ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

|General attributes 15-18|Under study|

+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+ûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûûû+

Note - If applicable.                                                         SLP = Single link protocol

                                                                              PLP = Packet layer protocol

                                                                              ppi = Picture elements/inch



FIGURE C-2/I.210



Possible values for attributes (characterizing teleservices)

Notes to Figure 2/I.210, Annex C





Note 1 - The characterization of the information transfer configuration attribute "broadcast" is for further study.



Note 2 - A definition of the establishment of communication is given in I.140.



Note 3 - The attributes are intended to be independent of each other.



Note 4 - For those teleservices that use circuit mode bearer capability X.25 PLP          description is as per ISO 8208.



Note 5 - These attribute values are mentioned in order to give an example of a specific presentation description of char-
acteristics such as coding of the user information, resolution, and graphic mode. Attribute values for other presentation
characteristics are for further study.



Note 6 - These attribute values are shown in order to give an example of a description of a teleservice application involving
two terminals at both access points (3 or 5) and an intervening system providing HLF functions (see Figure3c/I.210 and
Figure 3e/I.210). A specific teleservice attribute description for this case is for further study.









ANNEX D



(to Recommendation I.210)



Dynamic description of the service using graphic means -

step 1.3 of description method (Recommendation I.130)





D.1    Introduction



    Dynamic description of the service using graphic means is the third step (1.3) of the Stage 1 overall service description
from the user's point of view (Recommendation I.130).



    The dynamic description of a service contains all the information that is sent and received by the user from activation/
invocation of the service to completion of the service. The information is presented in the form of an Overall Specification
and Description Language (SDL) diagram or state transition diagrams (Note).



    An overall SDL diagram shows the flow of events, and states within the service, in a time sequenced format and identi-
fies all possible actions relevant to the service as perceived by the user. It treats the network as a single entity, that is no
information flows between nodes within the network are considered.



    SDL diagrams, drawn according to the principles laid down in RecommendationZ.100, are included in step 1.3 in order to
help to clarify and support the processing and information flows necessary for each service.



D.2    Overall specifications and description language (OSDL)



    In this third step of stage 1 each service state is shown in conjunction with all the external or internal actions which
cause state changes.  The actions may be inputs from users or the outcome of an internal process. Ideally all situations are
included in a single diagram although the diagram may have to be distributed over more than one document because of its
complexity.



Note:  Currently state transition diagrams are not used for the dynamic descriptions of services.



    The symbols used in OSDL and their meanings are as follows:





















































































        T1806920-88











































































        T1806030-88