1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000619.a.1994(R2012) Integrated Services Digital Network (ISDN) Multi-Level Precedence and Preemption (MLPP) Service Capability (MLPP Service Domain and Cause Value Changes) ATIS is the leading technical planning and standards development orga
2、nization committed to the rapid development of global, market-driven standards for the information, entertainment and communications industry. More than 200 companies actively formulate standards in ATIS Committees and Forums, covering issues including: IPTV, Cloud Services, Energy Efficiency, IP-Ba
3、sed and Wireless Technologies, Quality of Service, Billing and Operational Support, Emergency Services, Architectural Platforms and Emerging Networks. In addition, numerous Incubators, Focus and Exploratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Connect
4、ed Vehicle, IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications S
5、ectors, and a member of the Inter-American Telecommunication Commission (CITEL). ATIS is accredited by the American National Standards Institute (ANSI). For more information, please visit .AMERICAN NATIONAL STANDARD Approval of an American National Standard requires review by ANSI that the requireme
6、nts for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgment of the ANSI Board of Standards Review, substantial agreement has been reached by directly and materially affected interests. Substantial agreement
7、means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a concerted effort be made towards their resolution. The use of American National Standards is completely voluntary; their existence does not in any respect
8、 preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the standards. The American National Standards Institute does not develop standards and will in no circumstances give an interpreta
9、tion of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American National Standard in the name of the American National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose nam
10、e appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures of the American National Standards Institute require that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of A
11、merican National Standards may receive current information on all standards by calling or writing the American National Standards Institute. Notice of Disclaimer The use of Cause value #45 with a location code of 0110 to indicate preemption with circuitreservation for reuse is changed to Cause value
12、 #9; Cause value #46 is in codeset 0 instead of codeset 5; The MLPP Service Domain code format is changed from a 7-bit field in the Precedencelevel information element (for DSS1) and in the Precedence parameter (for SS7) to a 3-octetparameter for both DSS1 and SS7; The MLPP Service Domain is prefixe
13、d with a 2-octet Network Identity (NI) in thePrecedence level information element (for DSS1) and in the Precedence parameter (for SS7).Some other minor errors are also corrected.These changes result in a protocol that is incompatible with that which was described in ANSIT1.619-1992. Implementors of
14、the protocol described in the original ANSI T1.619-1992 or of thatPage 1 of 11 pagesANSI T1.619a-1994described in this supplement should be aware of this incompatibility and are cautioned to deter-mine the compatibility of interconnecting equipment.Specifically, the following changes should be made
15、to ANSI T1.619-1992:In clause 2, change references to the new editions as follows and delete footnote 1:ANSI T1.113-1992, Telecommunications Signaling system no. 7 (SS7) Integrated servicesdigital network (ISDN) user partANSI T1.114-1992, Telecommunications Signaling system no. 7 (SS7) Transaction c
16、apabil-ity application part (TCAP) user partAdd the following reference to clause 2:ITU-T Recommendation Q.850 (1993), Usage of cause and location in the DSS1 and the SS7ISDN user partPage 2 of 11 pagesANSI T1.619a-1994Replace figure 1 with the following figure:Page 3 of 11 pagesANSI T1.619a-1994ISC
17、ALL CPRECEDENCECALL?YMLPPCALL A-DINCOMINGCALL FROM CCOMPAREPRECEDENCESISUSER DPREEMPTABLE?NOTIFY USER DOF PREEMPTIONSTART RESPONSETIMER TDISCONNECTTO A(PREEMPTED)WAITING FORPOSITIVERESPONSETIMER TEXPIRESDIVERT CALLFROM CREQUEST FROMC TO CLEARCALLUSER DACKNOWLEDGERELEASECALL RESOURCESSTOP TIMERTUSER
18、D IDLENORMALCALL SETUPSETUPCALL D-CCALL D-CPRESENTDISCONNECT(NOT EQUIPPEDFOR PREEMPTION)MLPPCALL A-DOFFERED WITHCALL SETUPINFORMATIONNPRECEDENCEOF CALL A-DOR = CALL CMLPPCALL A-DUSER DACCEPTSTHE CALL( USER A AND USER B ARE ON AN MLPP CALL A-B-DAND USER C INITIATES A PRECEDENCE CALL)USER A, C,AND D I
19、DLEALTERNATEPARTYSPECIFIED?DIVERT CALLFROM CYNALTERNATEPARTYSPECIFIED?DIVERT CALLFROM C NYALTERNATEPARTYSPECIFIED?NYKKKCALLC-ALTERNATEPRESENTIndicates changesin the figureDDFigure 1 SDL diagram of MLPP (preemption at the called users interface)In figure 6, change all references to “B” to “D” (three
20、places) and change the label “FE7” to “FE8”.Replace subclause 6.1.2 with the following and delete footnote 2:All information elements (IE), except the Precedence level IE, are in codeset 0. ThePrecedence level IE is in codeset 5. Signal value 66, contained in the Signal IE, is defined inANSI T1.607.
21、 An additional meaning for this signal value 66, besides the one given in ANSIT1.607, is provided in informative annex D of this standard.In the figure in subclause 6.1.3.1, replace the last octet currently labeled “4a,b,.” with the follow-ing octets and replace the statement immediately after the f
22、igure as given below:The Precedence level IE identifier shall be in codeset 5.At the end of subclause 6.1.3.1, replace the definition of octets 4a and 4b with the following:Octets 56 (Network identity, NI)Each digit is coded in a binary coded decimal representation from 0 to 9.The first digit is cod
23、ed 0. The Telephony Country Code (TCC) follows in the 2nd to the 4th NIdigits (the most significant TCC digit is in the 2nd NI digit). If the TCC is one or two digits long,the excess digit(s) is inserted with the code for RPOA or network identification, if necessary. Ifoctet 6 is not required, it is
24、 coded all zeros.Octets 79 (MLPP Service Domain)A code expressing in pure binary the number allocated to a national MLPP Service Domain touniquely identify a customer domain across multiple ISDN networks. Bit 8 of octet 7 is the mostsignificant bit and bit 1 of octet 9 is the least significant bit.R
25、eplace subclause 6.1.3.3 with the following:For indicating the preemption of the call in the network and in the access or the failure to pre-empt, the Cause IE, as described in 4.5.11 of ANSI T1.607, shall be used with the followingITU-T codepoints described in Q.850:Number Cause Meaning8 Preemption
26、 Call is being preempted, circuit is not reservedfor reuse9 Preemption circuit reserved Call is being preempted, circuit is reserved for reuse for reuse46 Precedence No preemptable circuit or called user is busycall blocked with a call of equal or higher precedence level1st NI digit 2nd NI digit 53r
27、d NI digit 4th NI digit 6Most significant bit 7MLPP service domain 8Least significant bit 9Page 4 of 11 pagesANSI T1.619a-1994Page 5 of 11 pagesIn subclause 6.1.3.7 (ASN.1), replace the last parameter “Notsubscribed” by “userNotSubscribed”.In the first paragraph of subclause 6.2.1.1, replace:cause v
28、alues: 45, “preemption” and.by:cause values 8, “preemption” and 9, “preemption circuit reserved for reuse” and.In the second paragraph of subclause 6.2.1.1, replace:cause values: 45, “preemption” and.by:cause values 8, “preemption” and.and delete two occurrences of “US national” associated with caus
29、e values.In subclause 6.2.5, change the reference to:cause 45 and 46to read:causes 8, 9, and 46.Change:Cause #45, Location =0 1 1 0used with the HOLD message in figures 10 and 11 to:Cause 8to align with the text.Change the beginning of the last sentence in 6.2.6.1.1 c) 2) ii) C) from:An announcement
30、 48 of.to:An announcement of.Change all occurrences of the text:cause 45, “preemption” (with location coded “0 1 1 0” to indicate that circuit is reserved forreuse or with location coded as “0 1 1 0”)to:cause 9, “preemption circuit reserved for reuse”in the following places:6.2.6.1.1 c) 2) ii) C)Fig
31、ure 10 (two places)6.2.6.1.2 b) 3)6.2.6.1.3 b) 2) ii)Figure 11 (two places)6.3.2.4, 2nd paragraph6.3.2.4.b)ANSI T1.619a-1994Change all occurrences of the text:cause 45, “preemption” (with location coded other than “0 1 1 0” to indicate that circuit is notreserved for reuse or with location coded as
32、other than “0 1 1 0”)to:cause 8, “preemption”in the following places:6.2.6.1.1 c) 2) ii) C)Figure 10 (four places)6.2.6.1.2 b) 3)6.2.6.1.3 b) 2) ii)Figure 11 (four places)6.3.2.4 b)Change all occurrences of:cause 45to:cause 8in the following places:6.2.6.1.1 f) 2nd sentence6.3.2.4 1st paragraph, las
33、t sentenceAnnex A, Figure A.3 (continued) (b) Procedures without DSS1 LFB query (in HOLD message)6.3.2.4 2nd paragraph, last sentence7.2.4 a)Replace text in subclause 6.2.6.1.3 b) 3) ii) A) I) with:I) If preemptable access resources exist, the existing MLPP call shall be cleared to the remote (tobe
34、preempted) user with a cause 8, the circuit to the called user shall be reserved with a HOLDmessage delivered to the called user with cause 8 (in order to notify the called user of intendedpreemption), and timer TKis started. The HOLD message shall also contain the Call identity IEand Signal IE with
35、 signal value 9 so that a “preemption tone” may be applied to the called user. Anannouncement of “intended preemption” may also be provided to the called user. Then:If the timer TKexpires before a HOLD ACK message, containing the Call identity IE, is receivedand an alternate party is subscribed to,
36、the incoming (preempting) call shall be diverted toalternate party, using call forwarding procedures and the circuit reservation to the called usershall be canceled.If the timer TKexpires before a HOLD ACK message is received and no alternate party is sub-scribed to, the setup shall be continued for
37、 the incoming (preempting) call, using a SETUPmessage and by employing the reserved circuit to the called user.If the HOLD ACK message is received before the expiry of timer TK(indicating acceptance ofintended preemption), the setup shall be continued for the incoming (preempting) call, using aSETUP
38、 message and by employing the reserved circuit to the called user.If a STATUS message is received in response to the HOLD message sent by the network indi-cating that the called user does not support the HOLD family of messages, the setup shall becontinued for the incoming (preempting) call, using a
39、 SETUP message and by employing thereserved circuit to the called user (see 6.2.7).In all cases above, the SETUP message shall contain the Call identity IE and Signal IE withsignal value 66 so that a “precedence call alerting” may be provided to the called user;Page 6 of 11 pagesANSI T1.619a-1994Pag
40、e 7 of 11 pagesReplace text in subclause 6.2.7 with:a) If the called user does not support the HOLD family of messages, the user may return aSTATUS message with cause 88, “message not compatible with call state or message typenon-existent or not implemented,” or cause 97, “message type non-existent
41、or not implement-ed,” in response to the HOLD message sent by the destination exchange. In this case, thesetup shall be continued for the incoming (preempting) call, using a SETUP message and byemploying the reserved circuit to the called user see 6.2.6.1.3 b) 3) ii) A) I).b) If the incoming call is
42、 a precedence call, and if the called user is busy with a call of lowerprecedence, has preemptable access resources, and responds with a HOLD REJ messagewithin response timer TKto the HOLD message sent by the network, then the setup shall becontinued for the incoming (preempting) call, using a SETUP
43、 message and by employing thereserved circuit to the called user see 6.2.6.1.3 b) 3) ii) A) I).Change all occurrences of:cause #45, “Preemption” indicating Circuit Reserved for Reuseto:cause 9, “Preemption Circuit Reserved for Reusein the following places in annex A:Annex A, Figure A.1 (continued) (
44、b) Procedures without DSS1 LFB queryAnnex A, Figure A.2 (continued) (b) Procedures without DSS1 LFB queryAnnex A, Figure A.3 (continued) (b) Procedures without DSS1 LFB queryChange all occurrences of:cause #45, “Preemption” indicating Circuit Not Reserved for Reuseto:cause 8, “Preemption”in the foll
45、owing places in annex A:Annex A, Figure A.1 (continued) (b) Procedures without DSS1 LFB queryAnnex A, Figure A.2 (continued) (b) Procedures without DSS1 LFB queryAnnex A, Figure A.3 (continued) (b) Procedures without DSS1 LFB queryReplace subclause 7.1.1.2.1 with the following:The format of the prec
46、edence parameter is shown below. The subfields in the precedenceparameter identify the precedence level, the network identification and domain, and whether apath has been reserved or path reservation is allowed.8 7 6 5 4 3 2 1octet1spare LFB spare Precedence Level2 1st NI digit 2nd NI digit3 3rd NI
47、digit 4th NI digit4 Most significant bit5 MLPP Service Domain6 Least significant bitANSI T1.619a-1994The following codes are used in the Precedence parameter subfields:Octet 1LFBBits7 6 meaning0 0 LFB Allowed1 0 LFB Not Allowed0 1 Path reserved1 1 sparePrecedence LevelBits4 3 2 1 meaning0 0 0 0 FLAS
48、H OVERRIDE (0)0 0 0 1 FLASH (1)0 0 1 0 IMMEDIATE (2)0 0 1 1 PRIORITY (3)0 1 0 0 ROUTINE (4)0 1 0 1to Spare1 1 1 1Octets 23 contain a code for Network identity (NI). Each digit is coded in binary coded decimalrepresentation from 0 to 9. The first digit of this field is coded 0. The TCC (Telephony Cou
49、ntryCode) follows in the second to fourth NI digits (the most significant TCC digit is in the 2nd NIdigit). If the TCC is one or two digits long, the excess digit(s) is inserted with the code forRPOA or network identification, if necessary. If octet 3 is not required, it is coded all zeros. Octets 46 contain a code expressing in pure binary representation the number allocated to anMLPP Service domain. These numbers are allocated from the set of National Business GroupIdentifier codes in accordance with the procedures in Annex B, in chapter T1.113.3
