1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Q.2726.4 (0612 O0 O) SERIES Q: SWITCHING AND SIGNALLING Broadband ISDN - B-ISDN application protocols for the network signalling Extensions to the B-ISDN user part- Application generated identifiers ITU-T Rec
2、ommendation Q.2726.4 (Formerly CCITT Recommendation) ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 SPECIFICATIONS OF SIGNALLING SYSTE
3、M No. 6 SPECIFICATIONS OF SIGNALLING SYSTEM R1 SPECIFICATIONS OF SIGNALLING SYSTEM R2 DIGITAL EXCHANGES INTERWORIUNG OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q3 INTERFACE DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 PUBLIC LAND MOBILE NETWORK INTERWORIUNG WITH SATELLITE MOBILE S
4、YSTEMS INTELLIGENT NETWORK BROADBAND ISDN INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 General aspects Signalling ATM adaptation layer (SAAL) Signalling network protocols Common aspects of B-ISDN ap
5、plication protocols for access signalling and network signalling and interworking B-ISDN application protocols for access signalling Q.lLQ.3 Q.4-Q.59 Q.60.99 Q. 100.119 Q. 120.249 Q.250.309 Q.310.399 Q.400.499 Q.500.599 Q.600.699 Q.700.799 Q.800.849 Q.850.999 Q. 1000. 1099 Q. 1 100.1199 Q. 1200.1699
6、 Q.1700.1799 Q.2000.2999 Q.2000.2099 Q.2100.2199 Q.2200.2299 Q.2600.2699 Q.2900.2999 For further details, please re$er to the list of ITD-T Recommendations. ITU-T Recommendation 4.2726.4 Extensions to the B-ISDN user part - Application generated identifiers Summary This Recommendation defines B-ISUP
7、 capability to transport application generated identifiers. This capability allows the transport through the B-ISDN of identifiers required and used by various distributed applications. This capability allows an originating entity (e.g. a calling party) to transmit identifiers that can be used by a
8、peer entity. Source ITU-T Recommendation 4.2726.4 was revised by ITU-T Study Group 11 (1997-2000) and approved under the WTSC Resolution 1 procedure on 15 June 2000. ITU-T 4.2726.4 (06/2000) 1 FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the fi
9、eld of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The W
10、orld Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1
11、. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a r
12、ecognized operating agency. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed
13、 Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommend
14、ation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. o ITU 2001 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mech
15、anical, including photocopying and microfilm, without permission in writing fi-om ITU. 11 ITU-T 4.2726.4 (06/2000) CONTENTS 1 Scope . 2 References . 3 Definitions 4 Abbreviations 5 B-ISDN user part messages and parameters . 5.1 Messages . 5.1.1 IAM 5.1.2 ACM 5.1.3 CPG . 5.1.4 ANM 5.1.5 REL 5.2 Appli
16、cation generated identifier parameter . 5.3 Application process procedures Completion of the call/connection setup request . Application service elements and primitives 5.5 Intenvorking Intenvorking with nodes which do not support the procedures described in this Recommendation 5.5.2 Intenvorking wi
17、th ISUP . 5.5.3 Intenvorking with DSS2 5.3.1 Call/connection establishment . 5.3.2 5.3.3 CaWconnection release 5.4 5.4.1 Primitives between SACF and AP . 5.5.1 Appendix I . Setting of instruction indicators . ITU-T 4.2726.4 (06/2000) 1 1 1 1 2 2 7 . 111 ITU-T Recommendation 4.2726.4 Extensions to th
18、e B-ISDN user part - Application generated identifiers 1 Scope This Recommendation defines B-ISUP capability to transport application generated identifiers. This capability allows the transport through the B-ISDN of identifiers required and used by various distributed applications. This capability a
19、llows an originating entity (e.g. a calling party) to transmit identifiers that can be used by a peer entity. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of p
20、ublication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A li
21、st of the currently valid ITU-T Recommendations is regularly published. i ITU-T 4.2722.1 (1996), B-ISDN user part - Network node interface specijkation for point- to-multipoint call/connection control. 2 ITU-T 4.2761 (1999), Functional description of the B-ISDN user part -ISUP) of signalling system
22、No. 7. 3 ITU-T 4.2762 (1999), General functions of messages and signals of the B-ISDN user part -ISUP) of signalling system No. 7. 4 ITU-T 4.2763 (1999), Signalling System No. 7 B-ISDN User Part -ISUP) - Formats and codes. 5 ITU-T 4.2764 (1999), Signalling System No. 7 B-ISDN User Part -ISUP) - Basi
23、c call procedures. 6 ITU-T 4.2941.1 (1997), Digital Subscriber Signalling System No. 2 - Generic identiper transport. 3 Definitions No new definitions are required. 4 Abbreviations No new abbreviations are used. The abbreviations of ITU-T 4.2722.1, 4.2761, 4.2762, 4.2763 and 4.2764 apply. ITU-T 4.27
24、26.4 (06/2000) 1 5 B-ISDN user part messages and parameters 5.1 Messages 5.1.1 IAM The IAM contains the following additional parameter: - Application generated identifier. 5.1.2 ACM The ACM contains the following additional parameter: - Application generated identifier. 5.1.3 CPG The CPG contains th
25、e following additional parameter: - Application generated identifier. 5.1.4 ANM The ANM contains the following additional parameter: - Application generated identifier. 5.1.5 REL The REL contains the following additional parameter: - Application generated identifier. 5.2 Application generated identi
26、fier parameter The parameter name code allocated to the application generated identifier parameter is O 1 1 O 1 O 1 O. The application generated identifier parameter carries one or more instances of the DSS2 generic identifier transport information element. The format of the application generated id
27、entifier is shown in Figwe 1. 8 7 6 5 4 3 2 1 Octets Spare Priority One or more instances of the generic identifier transport information element defined in ITU-T 4.2941.1 starting with octet 1 2 Figure UQ.2726.4 - Application generated identifier parameter The following codes are used in the subfie
28、lds of the application generated identifier parameter field. a) Repeat indicator (octet 1) O Information element not repeated 1 Information element repeated 2 ITU-T 4.2726.4 (06/2000) b) Priority (octet 1) O000 No prioritized order O00 1 O0 1 O Prioritized list for selecting one possibility: ascendi
29、ng order Prioritized list for selecting one possibility: descending order Reserved 1111 c) Generic identiper transport information elements (octet 2-n) This field contains all instances of the generic identifier transport information element received rom DSS2 or generated by an originating or addres
30、sed entity located in the network. The format of the generic identifier transport information elements is the same as specified in ITU-T 4.2941.1 6. The order of the information elements is not changed. The number of instances or maximum length of the generic identifier transport information element
31、 is network-dependent. 5.3 Application process procedures 5.3.1 Calkonnection establishment a) Originating exchange The Set-up request primitive may include an application generated identifier parameter carrying unaltered, one or more instances of the generic identifier transport information element
32、 received rom the DSS2 or generated by an application entity located in the originating exchange. b) Intermediate national exchange If an incoming side of an intermediate national exchange receives an application generated identifier parameter in a Set-up indication primitive, the outgoing side of t
33、he exchange will include it unaltered in the Set-up request primitive it will issue. c) Outgoing international exchange If an outgoing international exchange receives an application generated identifier parameter in a Set-up indication primitive, it shall include it unaltered in the Set-up request p
34、rimitive it will issue. d) Incoming international exchange It is a network option how an incoming international gateway shall proceed when it receives an application generated identifier parameter. If the application generated identifier service is not supported by the network, the incoming internat
35、ional exchange may either: i) clear the call with cause # 63, “Service option not available, unspecified“, or ii) pass on the parameter and progress the call establishment. If the incoming international gateway decides to progress the call establishment, it will issue a Set-up request primitive cont
36、aining unaltered, the application generated identifier parameter it has received. ITU-T 4.2726.4 (06/2000) 3 5.3.2 a) 5.3.3 a) 4 Destination exchange If the Set-up request primitive contains an application generated identifier parameter, it will be transferred unaltered in the indication sent to the
37、 called party as specified in ITU-T 4.294 1.1 6. Alternatively, the destination exchange may process the application generated identifier parameter, if the addressed entity is located in the destination exchange. Completion of the caWconnection setup request Destination exchange Primitives issued by
38、 the destination exchange after receiving a signal rom the called party may contain an application generated identifier parameter. The application generated identifier parameter will contain unaltered, the identifiers received rom the access or generated by the addressed entity. The following primit
39、ives may carry the application generated parameter: - Address - Complete request; - Progress request; - Answer request. Intermediate national or international exchange The incoming side of an intermediate national or international exchange may receive in the Address-Complete indication, the Progress
40、 indication or the Answer indication primitive an application generated identifier parameter. The outgoing side of the exchange will pass the application generated identifier parameter in a corresponding Address-Complete indication, Progress indication or Answer indication primitive. It is a network
41、 option how an incoming or outgoing international gateway shall proceed when it receives an application generated identifier parameter. The options defined in 5.3.1 d) are applicable. Originating exchange The originating exchange may receive an Address-Complete indication, a Progress indication or a
42、n Answer indication primitive containing an application generated identifier parameter. The access side of the originating exchange will relay the contents of the application generated identifier parameter to the calling party in the appropriate access signal or to the application entity. CalVconnec
43、tion release Access exchange initiating the release procedure When the call/connection release is initiated by a user, the access exchange may receive rom the user initiating the release, a signal carrying one or more application generated identifiers. The Release request primitive will carry them i
44、n an application generated identifier parameter. Intermediate national or international exchange If an incoming side of an intermediate exchange receives an application generated parameter in a Release indication primitive, the outgoing side of the exchange will include them unaltered in the Release
45、 request primitive to be issued. It is a network option how an incoming or outgoing international gateway shall proceed when it receives an application generated identifier parameter. The options defined in 5.3.1 d) are applicable. ITU-T 4.2726.4 (06/2000) c) Access exchange receiving a release indi
46、cation If an access exchange receives a Release indication primitive containing an application generated identifier parameter, the contents will be transferred unaltered in the indication sent to the user as specified in ITU-T 4.2941.1 6. Set-up requesthndication Application generated identifier 5.4
47、 The following primitives are affected. Application service elements and primitives B-ISDN O 5.4.1 Primitives between SACF and AP Address-Complete Requesthndication Application generated identifier 5.4.1.1 Set-up requesthdication primitives Table 1 shows the parameter that must be added to the Set-u
48、p requestlindication primitives. B-ISDN O Table UQ.2726.4 - Parameter for the Set-up requesthdication primitives Progress requesthndication B-ISDN 5.4.1.2 Address-Complete requesthdication primitives Table 2 shows the parameter that must be added to the AddressComplete requestlindication primitives.
49、 5.4.1.3 Progress requestlindication primitives Table 3 shows the parameter that must be added to the Progress requestlindication primitives. I Application generated identifier I O I 5.4.1.4 Answer requestlindication primitives Table 4 shows the parameter that must be added to the Answer requestlindication primitives. Table 4/Q.2726.4 - Parameter for the Answer requesthdication primitives I Answer requesthdication I B-ISDN I I Application generated identifier I O I ITU-T 4.2726.4 (06/2000) 5 5.4.1.5 Release requesthdication primitives Table 5 shows the parameter
