WPCL 2BJ|x  HH   x|@  6'6' Recommendation I.210 Principles of telecommunication services supported by an ISDN and the means to describe them 1.HGeneral HAn 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.300Series of Recommendations. HUsing the service concept and the means for the description of services as given in this Recommendation, recommended bearer services are defined and described in the I.230Series of Recommendations, recommended teleservices are defined and described in the I.240Series of Recommendations and recommended supplementary services are defined and described in the I.250Series of Recommendations. 2.HService concepts 2.1HServices 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 functions and enable telecommunication services to be offered to customers. HA 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. HThe service classification and descriptions which follow are independent of different possible arrangements for ownership 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.2HThe 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: HStep 1.1Prose service definition and description HStep 1.2Static description of the service using attributes HStep 1.3Dynamic description of the service using graphic means HTogether these three steps define the service characteristics as they apply at a given reference point where the customer accesses the service. HAnnexes A to D of this Recommendation give the format of Stage 1 service descriptions as follows: HAnnex A: Structure for prose service definition and description HAnnex B: List of attributes and their possible values for describing bearer services HAnnex C: List of attributes and their possible values for describing teleservices HAnnex 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. HThis 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 applicable to certain types of services. 2.3HTelecommunication services are classified using their static characteristics described by attributes. Therefore this Recommendation (except Annexes A and D) deals mainly with Step 1.2 of the description method. HA telecommunication service is, from the static point of view, composed of: H technical attributes as seen by the customer; and H other attributes associated with the service provision, e.g. operational and commercial attributes. HRealization of the technical attributes of a telecommunication service requires a combination of network and terminal capabilities and other service providing systems. 2.4HTelecommunication services are divided in two broad families, i.e., H bearer services, and H teleservices. HA 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 XSeries of Recommendations. HThe concepts introduced here are illustrated in Table 1/I.210 and are defined in more detail in  5. KTABLE 1/I.210 Q ;Classification of telecommunication servicesă    TELECOMMUNICATION SERVICE    BEARER SERVICE  TELESERVICE    Basic bearer  Basic bearer service +  Basic  Basic teleservice   service  supplementary services  teleservice  + supplementary      services     , 3.HCustomer access to telecommunication services supported by an ISDN 3.1K#LConsidering 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. T180688088 JFIGURE 1/I.210 Q 9Customer access to services supported by an ISDNă 3.2HThe definitions of the access points introduced in Figure1/I.210 are as follows: Hi)h  access points 1 (reference point T) and 2 (reference point S) are the access points for bearer services supported 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 descriptions in the following are independent of different possible arrangements for such provision; Hii)  at access point 4 (reference point R), depending on the type of terminal adaptors provided, other CCITT standardized services may be accessed, e.g. according to the X and VSeries of Recommendations; HHX HHiii) at access points 3 and 5 (usertoterminal interface), teleservices are accessed the teleservice concept includes the terminal capabilities. 3.3HThe following customer entities may be connected at access points 1 and 2: H customer terminals; H customer systems, e.g. PABXs, LANs, service vendor systems; H private networks. Note Customer terminals and systems may be private or provided by administrations or RPOAs. HAll 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. HFor 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 supplementary services (see Recommendation I.250). 3.4HFrom the user's point of view the telecommunication services as defined in the I.200Series of Recommendations will be used for some applications. For example, the telephony teleservice will be typically used for a human conversation (application). Likewise bearer services will be used for applications. The area of applications is outside the scope of the ISeries 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.5HThe telecommunication service, as described in this Recommendation, is timeindependent, 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.HCapabilities to support a telecommunication service 4.1HThe capabilities required to fully support a telecommunication service for a customer connected to an ISDN include: H network capabilities; H terminal capabilities, when required; H other services providing capabilities, when required; H operational and commercial features associated with the service provision (i.e. sales or marketing aspects). 4.2HNetwork capabilities are described in detail in RecommendationI.310. Two different levels of ISDN network capabilities are introduced in that Recommendation: H low layer capabilities which relate to bearer services; H high layer capabilities which together with low layer capabilities relate to teleservices. HThe low layer capabilities are defined as a set of Low Layer Functions(LLF) (relating to layers 13 in Recommendation X.200) which provide the capability for the carriage of user information over an ISDN connection. HThese functions include: H Basic Low Layer Functions (BLLF) supporting the necessary layer13 requirements; H Additional Low Layer Functions (ALLF) supporting, in addition to BLLFs, lower layer requirements of supplementary services. HHigh Layer Capabilities are defined as a set of High Layer Functions(HLF) , generally associated with layers 47 in Recommendation X.200. HHigh Layer Functions are subdivided 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.3HThe 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.4HThe operational service capabilities associated with a service offering may include capabilities for maintenance, charging, user control of service features, etc. HThe use of such capabilities may involve terminalnetwork communication and may therefore be viewed as specific applications. HA more precise description of these capabilities and the relationship to Recommendation X.200 needs further study. KTABLE 2/I.210 Q 6Relationship between service families, network/terminală Dcapabilities 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.HTelecommunication service classification 5.1HThe 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. HThere are two groups of service attributes applicable to user information flow: H low layer attributes; H high layer attributes. HBearer services are defined as including only Low Layer Attributes. Teleservices are defined as including both Low Layer Attributes and High Layer Attributes. HThe relationship between telecommunication service attributes and low/high layer functions is illustrated in Table 3/I.210. KTABLE 3/I.210 Q <Relationship between service attributes andă Elow/high layer functionsă T180689088 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 supplementary services associated to basic telecommunications services. It could be split into subattributes 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 requires , further studies. 5.2HBearer services supported by an ISDN 5.2.1HBearer services supported by an ISDN provide the capability for information transfer between ISDN access points 1 or 2 and involve only low layer functions. HThe customer may choose any set of high layer (at least 47) 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.2HBearer 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: H information transfer attributes; H access attributes; and H general attributes, including operational and commercial attributes. HThe bearer capability defines the technical features of a bearer service as they appear to the user at the appropriate access point (1 or 2). HThe 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 setup delay should be extracted in order to form a new attribute allocated to the information transfer category. Identification and definition of such parameters require further consideration. HIndividual bearer services categories are defined and described in the I.230Series of Recommendations. 5.2.3HA bearer service provides the user with the possibility of gaining access to various forms of communication, covering for example: H information transfer between users employing the same access points (1 or 2) and access attributes (see Figure2a/I.210); H information transfer between users employing different access attributes at the access points (1 or 2) involved, (see Figure2b/I.210); and H information transfer between a user and a separate resource providing high layer functions (see Figure2c/I.210). T180690088 H 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. JFIGURE 2/I.210 Q ?Examples of bearer service operationă 5.3HTeleservices supported by an ISDN 5.3.1HTeleservices provide the full capacity for communication by means of terminal and network functions and possibly functions provided by dedicated centres. HA 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. However, 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.2HTeleservices 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. HLow 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 layers47 in the Recommendation X.200 framework which are concerned with the transfer, storage and processing of user messages (provided by a subscriber's terminal, a retrieval centre, or a network service centre). HTherefore, 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 perceived , by the user. HThe definition of appropriate attributes and the specifications of teleservices at this access point from the user point of view (manmachine interface) is for further study and the subject of Eand FSeries of Recommendations. HIndividual teleservices are defined and described in the I.240Series of Recommendations. 5.3.3HA teleservice provides the user with the possibility of gaining access to various forms of applications (or teleservice applications) covering, for example: H teleservice application involving two terminals providing the same teleservice attributes at both access points (3 or 5) (see Figure 3a/I.210); H teleservice application involving a terminal at one access point (3 or 5) and HLF functions located within the ISDN (see Figure3b/I.210); H 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); H teleservice application involving a terminal at one access point (3 or 5) and a system providing HLF functions (see Figure 3d/I.210); H teleservice application involving two terminals at both access points (3 or 5) and an intervening system providing HLF functions (see Figure3e/I.210). In this case, teleservice attributes can be different at each terminal access point. JFIGURE 3/I.210 ?Examples of teleservice application 5.4HSupplementary services supported by an ISDN HSupplementary 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. HSupplementary 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. HThe use of the attribute technique for supplementary services is for further study. The individual supplementary services are described in the I.250Series of Recommendations. 6.HProvision of telecommunication services 6.1HA 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 ownership within the customer premises (TE or TE and NT2), a telecommunication service is provided at different access points. 6.2HThe provision of telecommunication services implies: H subscription ensuring the basic service and possibly subscription to supplementary services; H registration into a service directory in the case where demand services are used; H compatibility between terminals; H interworking capabilities (this point needs further study). 6.3HThe provision of individual bearer services is given in the I.230Series of Recommendations, the provision of individual teleservices is given in the I.240Series of Recommendations and the association of supplementary services to bearer services and teleservices is given in Recommendation I.250. NANNEX A Q E(to Recommendation I.210) Q <Structure for prose service definition andă 0description step 1.1 of description method (Recommendation I.130)ă A.1HStructure of prose service definition and description HProse 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.HDefinition 2.HDescription 2.1HGeneral description 2.2HSpecific terminology 2.3HQualifications 3.HProcedures 3.1HProvision/withdrawal 3.2HNormal procedures 3.2.1HActivation/deactivation/registration 3.2.2HInvocation and operation (3.2.3 Interrogation/editing) 3.3HExceptional procedures 3.3.1HActivation/deactivation/registration 3.3.2HInvocation and operation (3.3.3 Interrogation/editing) 3.4HAlternative procedures 3.4.1HActivation/deactivation/registration 3.4.2HInvocation and operation (3.5HVerification) 4.HNetwork capabilities for charging 5.HInterworking requirements 6.HInteraction with other supplementary services Note 1 Where a particular section would not be appropriate for a particular service (basic or supplementary) "not applicable" appears in that section for that service. Some such items have been identified by paragraph numbering in parenthesis. 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 subdivided under subheadings as necessary. A.2HExplanation of the terms and content of the items in the Hservice prose definition and description 1.HDefinition HThis 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.HDescription HThis 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 implementation. 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.HProcedures HThe 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.1HProvision/withdrawal HThis paragraph describes the means by which the service is made available by the service provider e.g. it may be generally available to all customers, or, only be available to those customers who have made a prior arrangement. 3.2HNormal procedures HThe 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 timebased 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.1HActivation/deactivation/registration HThe 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 specific 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. HRegistration 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.2HInvocation and operation HThis 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.) HIn the case of basic services this section describes the events, perceived at the service access point, during the establishment, information transfer and clearing phases. ,Ԍ HOperation 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 perception 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.3HInterrogation/editing HInterrogation 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 accompany it, are detailed in this paragraph. HEditing 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.3HExceptional procedures HThe paragraphs under this heading describe, for each of the items shown under paragraph 3.2, the exceptional procedures which result in an unsuccessful outcome of the call. Included within this description are the details for such situations 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.4HAlternative procedures H HThe 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 alternative treatment of the call by the network. 3.5HVerification HThis 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.HNetworking capabilities for charging HThis 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.HInterworking requirements HThis 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.HInteraction with other supplementary services HThis 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. HFor 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. HIt 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. NANNEX B Q E(to Recommendation I.210) Q 4List of attributes and their possible values for describingă .bearer services step 1.2 of description method (Recommendation I.130)ă B.1HFramework for the static description of bearer services Hsupported by an ISDN HStatic 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: Hi)h  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; Hii)  access attributes which describe the means for accessing network functions or facilities as seen at one S/T reference point; and HHX HHiii) general attributes which deal with the service in general. HFigure B1/I.210 shows the relation between the groups of attributes and their fields of applicability.  ,ԌIFIGURE B1/I.210 Q 9Relationship between the groups of attributes andă Ffields of applicabilityă HTable B1/I.210 gives the list of the attributes. For the definitions and possible values of these attributes, see Recommendation I.140. JTABLE B1/I.210 Q HList of attributesă Q Information transfer attributes H1 Information transfer mode H2 Information transfer rate H3 Information transfer capability H4 Structure H5 Establishment of communication H6 Symmetry H7 Communication configuration Access attributes (Note) H8 Access channel and rate H9 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. HFigure B2/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. HAccording 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.  H H&'H&'   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   information         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 Pointtopoint 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  X 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 nonISDN CCITT standardized services (e.g. at X.1 rate). The necessary usernetwork signalling is provided in Recommendation I.451.  Note 7 TSSI = Time slot sequence integrity; RDTD = Restricted differential time delay.  MFIGURE B2/I.210 U AValues for each bearer service attributeă  ` > 6'6' ANNEX C A 5(to Recommendation I.210) A )List of attributes and their possible values foră )describing teleservices step 1.2 of descriptionă 3method (Recommendation I.130)ă   C.1HFramework for the static description of teleservices supported Hby an ISDN  H HStatic 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. HAttributes to describe teleservices supported by an ISDN are intended to be largely independent. They are grouped into three categories: Ha)  low layer attributes H information transfer attributes, H access attributes; Hb)  high layer attributes; Hc)  general attributes.  h Note Teleservices generally make use of underlying lower layer capabilities of bearer services specified in the I.230Series 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.230Series of Recommendations. HFigure C1/I.210 shows the relationship between the different categories of service attributes and their scope within a teleservice. FIGURE C1/I.210 8R 8;Relationship between the categories of serviceă ; Ԍ8<attributes and their scope with a teleserviceă  X  C.2HList of the teleservice attributes C.2.1HLow layer attributes Information transfer attributes H1.  Information transfer mode H2.  Information transfer rate H3.  Information transfer capability H4.  Structure H5.  Establishment of communication H6.  Symmetry H7.  Communication configuration Access attributes H8.  Access channel and rate H9.1  Signalling access protocol Layer 1 H9.2  Signalling access protocol Layer 2 H9.3  Signalling access protocol Layer 3 H9.4  Information access protocol Layer 1 H9.5  Information access protocol Layer 2 H9.6  Information access protocol Layer 3 C.2.2HHigh layer attributes H10.  Type of user information H11.  Layer 4 protocol functions H12.  Layer 5 protocol functions H13.  Layer 6 protocol functions H Resolution ) if applicable /00123Graphic mode ) (Note 1) H14.  Layer 7 protocol functions H TEtoTE protocol functions ) if applicable H TEtoHLF protocol functions ) (Note 2) C.2.3HGeneral attributes H15.  Supplementary services provided H16.  Quality of service H17.  Interworking possibilities H18.  Operational and commercial HFigure C2/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.   H&'H&'   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 Pointtopoint 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)     X  9.5 Information access protocol Layer 2 HDLC I.440/ X.75 X.25 Others FS   LAP B I.441 SLP 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) Alphamosaic Geometric Photographic Others   14. Layer 7 protocol T.60 T.500Series Others   General attributes 1518 Under study    Note If applicable. SLP = Single link protocol   PLP = Packet layer protocol   ppi = Picture elements/inch U MFIGURE C2/I.210 U 7Possible values for attributes (characterizing teleservices)ă  ` 1 6'6' 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.  h 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 characteristics 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. 8OANNEX D 8R 8F(to Recommendation I.210) 8R 86Dynamic description of the service using graphic means ă 88step 1.3 of description method (Recommendation I.130)ă 8R 8R D.1HIntroduction ; Ԍ  X HDynamic 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). HThe 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). HAn overall SDL diagram shows the flow of events, and states within the service, in a time sequenced format and identifies 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. HSDL 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.2HOverall specifications and description language (OSDL) HIn 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. HThe symbols used in OSDL and their meanings are as follows: H T180692088 H T180603088