1、 INTERNATIONAL TELECOMMUNICATION UNION Q.81 THE INTERNATIONAL (02/92) TELEGRAPH AND TELEPHONE CONSULTATIVE COMMITTEE FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN STAGE 2 DESCRIPTION FOR NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES SECTION 2 MULTIPLE SUBSCRIBER NUMBER SECTION 8 SUB-ADDRES
2、SING (SUB) Addenda to: Recommendation Q.81 Geneva, 1992 FOREWORD The CCITT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issui
3、ng Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The Plenary Assembly of CCITT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of C
4、CITT between Plenary Assemblies is covered by the procedure laid down in CCITT Resolution No. 2 (Melbourne, 1988). Recommendation Q.81, 2 and 8 was prepared by Study Group XI and was approved under the Resolution No. 2 procedure on the 4th of February 1992. _ CCITT NOTE In this Recommendation, the e
5、xpression “Administration” is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency. ITU 1992 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including p
6、hotocopying and microfilm, without permission in writing from the ITU. Recommendation Q.81 1 Recommendation Q.81 Recommendation Q.81 STAGE 2 DESCRIPTION FOR NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES 2 Multiple Subscriber Number 2.1 Scope This Recommendation defines the stage 2 of the Multiple Sub
7、scriber Number (MSN) supplementary service for the integrated services digital network (ISDN) as provided by telecommunications operators. Stage 2 identifies the functional capabilities and the information flows needed to support the stage 1 service description. The stage 2 description also identifi
8、es user operations not directly associated with a call (see Recommendation I.130 1). This Recommendation is specified according to the methodology specified in Recommendation Q.65 2. This Recommendation does not formally describe the relationship between this supplementary service and the basic call
9、, but where possible this information is included for guidance. In addition, this Recommendation does not specify the requirements where the service is provided to the user via a private ISDN. This Recommendation does not specify the requirements for the allocation of defined functional entities wit
10、hin a private ISDN, it does, however, define which functional entities may be allocated to a private ISDN. This Recommendation does not specify the additional requirements where the service is provided to the user via a telecommunications network that is not an ISDN. The MSN supplementary service pr
11、ovides the possibility for assigning multiple numbers to a single public or private access. Note This allows e.g.: 1) a calling user to select, via the public network, one or multiple distinct terminals out of a multiple choice; 2) to identify the terminal to the network for the application of other
12、 supplementary services. It is considered: that in the case of a basic access some service providers may not have knowledge or control over what is connected, e.g. a private ISDN or a terminal configuration; that service providers have differing numbering methods. The MSN supplementary service is ap
13、plicable to all telecommunication services. This Recommendation is applicable to the stage 3 Recommendations for the ISDN MSN supplementary service as defined in Recommendation I.130 1. 2.2 References This Recommendation incorporates, by dated or undated reference, provisions from other publications
14、. These references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to, or revisions of any of these publications apply to this Recommendation only when incorporated in it by amendment or revision. For undated refe
15、rences the latest edition of the publication referred to applies. 2 Recommendation Q.81 1 CCITT Rec. I.130 Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN, 1988. 2 CCITT Rec. Q.65 Stage 2 of the method for the characterization of
16、 services supported by an ISDN, 1988. 3 CCITT Rec. I.112 Vocabulary of terms for ISDNs, 1988. 4 CCITT Rec. E.164 Numbering plan for the ISDN era, 1991. 5 CCITT Rec. Q.711) ISDN 64 kbit/s circuit mode switched bearer services, 1993. 6 CCITT Rec. I.210 Principles of telecommunication services supporte
17、d by an ISDN and the means used to describe them, 1988. 7 CCITT Rec. Z.100 Specification and description language (SDL), 1988. 2.3 Definitions For the purposes of this Recommendation the following definitions apply: Integrated Services Digital network (ISDN) See Recommendation I.112 3, 2.3, definiti
18、on 308. Service: telecommunications service See Recommendation I.112 3, 2.2, definition 201. Supplementary service See Recommendation I.210 6, 2.4. ISDN number A number conforming to the numbering plan and structure specified in Recommendation E.164 4. 2.4 Symbols and abbreviations CC Call control C
19、CA Call control agent FE Functional entity FEA Functional entity action ISDN Integrated services digital network LE Local exchange MSN Multiple subscriber number SDL Specification and description language TE Terminal equipment. 2.5 Description Not applicable. _ 1)Recommendation Q.71 will be submitte
20、d for approval at the CCITT Plenary Assembly in March, 1993. Recommendation Q.81 3 2.6 Derivation of the functional model 2.6.1 Functional model description The functional model for the MSN supplementary service is shown in Figure 2-1/Q.81. 2.6.2 Description of the functional entities The functional
21、 entities required by the MSN supplementary service above those of the basic call are as follows: FE1 Served users service agent FE2 MSN service control entity. 2.6.3 Relationship with a basic service The relationship with a basic service is shown in Figure 2-2/Q.81 4 Recommendation Q.81 2.7 Informa
22、tion flows 2.7.1 Information flow diagrams 2.7.2 Definition of individual information flows There are no information flows specific to this service. Note The contents for SETUP in basic call are as specified for basic call (see Recommendation Q.71 5). 2.8 SDL diagrams for functional entities The SDL
23、s are provided according to Recommendation Z.100 7. Recommendation Q.81 5 2.8.1 FE1 The SDLs for FE1 are shown in Figure 2-5/Q.81. 6 Recommendation Q.81 2.8.2 FE2 The SDL for FE2 is shown in Figure 2-6/Q.81. Recommendation Q.81 7 2.9 Functional entity actions (FEAs) The FEAs of FE1 shall be optional
24、 for the basic call but shall be mandatory for the MSN supplementary service. 2.9.1 FEAs of FE1 For an incoming call: 911: the functional entity shall analyse the multiple subscriber number digits in the call set-up information and compare them with the configured multiple subscriber digits for use
25、in the basic call. For an outgoing call: 912: the functional entity shall insert the multiple subscriber number digits in the call set-up information as the calling party number. 2.9.2 FEAs of FE2 For an incoming call: 921: the functional entity shall check and validate subscription options and deri
26、ve the multiple subscriber number digits from the ISDN number. 922: the functional entity shall insert the multiple subscriber number digits into the call set-up information for transmission over the interface. For an outgoing call: 923: the functional entity shall check and validate subscription op
27、tions and obtain and screen the digits from the call set-up information. 924: the functional entity shall derive the ISDN number from the multiple subscriber number digits. 2.10 Allocation of functional entities to physical locations The possible locations of functional entities FE1 and FE2 are show
28、n in Table 2-1/Q.81. TABLE 2-1/Q.81 Note FE2 and FE1 are always allocated at opposite ends of the same access. FE2 FE1 Scenario 1 LE TE 8 Recommendation Q.81 8 Sub-addressing (SUB) 8.1 Scope This Recommendation defines the stage 2 description of the Sub-addressing (SUB) supplementary service for the
29、 integrated services digital network (ISDN) as provided by public telecommunications operators. Stage 2 description identifies the functional capabilities and the information flows needed to support the stage 1 service description. The stage 2 description also identifies user operations not directly
30、 associated with a call (see Recommendation I.130 1). This Recommendation is specified according to the methodology specified in Recommendation Q.65 2. This Recommendation does not formally describe the relationship between this supplementary service and the basic call but, where possible, this info
31、rmation is included for guidance. In addition, this Recommendation does specify the requirements where the service is provided to the user via a private ISDN. This Recommendation does not specify the requirements for the allocation of defined functional entities within a private ISDN; it does, howev
32、er, define which functional entities may be allocated to a private ISDN. This Recommendation does not specify the additional requirements where the service is provided to the user via a telecommunications network that is not an ISDN. The Sub-addressing (SUB) supplementary service allows the called (
33、served) user to expand his addressing capacity beyond the one given by the public or private ISDN number. The SUB supplementary service is applicable to all telecommunication services. This Recommendation is applicable to the stage 3 description Recommendation for the ISDN Sub-addressing supplementa
34、ry service. The term “stage 3” is also defined in Recommendation I.130 1. 8.2 References The references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references subsequent amendments to, or revisions of any of these publications apply to this Re
35、commendation only when incorporated in it by amendment or revision. For undated references the latest edition of the publication referred to applies. 1 CCITT Rec. I.130 Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN, 1988. 2 CCI
36、TT Rec. Q.65 Stage 2 of the method for the characterization of services supported by an ISDN, 1988. 3 CCITT Rec. E.164 Numbering plan for the ISDN era, 1991. 4 CCITT Rec. I.251.8 Sub-addressing (SUB). 5 CCITT Rec. Q.711) ISDN 64 kbit/s circuit mode switched bearer service, 1993. 6 CCITT Rec. I.210 P
37、rinciples of telecommunication services supported by an ISDN and the means used to describe them, 1988. 7 CCITT Rec. I.112 Vocabulary of terms for ISDNs, 1988. 8 CCITT Rec. Z.100 Specification and description language (SDL), 1988. _ 1)Recommendation Q.71 will be submitted for approval at the CCITT P
38、lenary Assembly in March, 1993. Recommendation Q.81 9 8.3 Definitions For the purposes of this Recommendation, the following definitions apply: Integrated services digital network (ISDN) See Recommendation I.112 7, 2.3 definition 308. Service: telecommunications service See Recommendation I.112 7, 2
39、.2, definition 201. Supplementary service See Recommendation I.210 6, 2.4. Called party sub-address The called party sub-address is the sub-address of the called party ISDN address. ISDN number: A number conforming to the numbering plan and structure specified in Recommendation E.164 3. 8.4 Symbols
40、and abbreviations CC Call control CCA Call control agent CDSA Called party sub-address FE Functional entity FEA Functional entity action ISDN Integrated services digital network LE Local exchange OLE Originating local exchange PN Private network SDL Specification and description language SUB Sub-add
41、ressing TE Terminal equipment TLE Terminating local exchange. 8.5 Description The general description of the SUB supplementary service is specified in Recommendation I.251.8 4, 5. The relation of the called party sub-address to the ISDN number is given in Recommendation E.164 3. 8.6 Derivation of th
42、e functional model 8.6.1 Functional model description The functional model for the SUB supplementary service is shown in Figure 8-1/Q.81. 10 Recommendation Q.81 8.6.2 Description of the functional entities The functional entities required by the SUB supplementary service in addition to those of the
43、basic call are as follows: FE1 CDSA insertion entity FE2 CDSA length controlling entity FE3 SUB supplementary service controlling entity FE4 CDSA using entity. 8.6.3 Relationship with a basic service The relationship of the SUB supplementary service with a basic service is shown in Figure 8-2/Q.81.
44、8.7 Information flows 8.7.1 Information flow diagrams The information flow diagrams for the SUB supplementary service are shown in Figures 8-3/Q.81 and 8-4/Q.81. Recommendation Q.81 11 12 Recommendation Q.81 8.7.2 Definition of individual information flows 8.7.2.1 Relationship ra8.7.2.1.1 INFORM The
45、 contents of the INFORM information flow are shown in Table 8-1/Q.81. TABLE 8-1/Q.81 8.8 SDL diagrams for functional entities FIGURE 8-5 D13 = 14 cm Parameter Allowed value req. ind. Called party sub-address 20 octets Mandatory Recommendation Q.81 13 14 Recommendation Q.81 Recommendation Q.81 15 8.9
46、 Functional entity actions 8.9.1 FEAs of FE1 910: the functional entity shall accept called party sub-address from the calling party. The functional entity shall insert called party sub-address in the INFORM and forward it to FE2. 8.9.2 FEAs of FE2 920: the functional entity shall accept called part
47、y sub-address. The functional entity shall compare the length of the called party sub-address and shall send called party sub-address if length does not exceed 20 octets; otherwise FE2 shall discard called party sub-address. 8.9.3 FEAs of FE3 930: the functional entity shall accept and forward calle
48、d party sub-address if subscription is valid, otherwise the functional entity shall discard called party sub-address. 16 Recommendation Q.81 8.9.4 FEAs of FE4 940: the functional entity shall receive called party sub-address. The functional entity shall check called party sub-address, and if recogni
49、zed: shall continue call handling; if not recognized: shall ignore the call. 8.10 Allocation of functional entities to physical locations The possible locations of functional entities FE1, FE2, FE3 and FE4 are shown in Table 8-2/Q.81. TABLE 8-2/Q.81 a)This TE (terminal equipment) is connected to a PN (private network). Note 1 All functional entities above “&” are provided with appropriate relatio
