ANSI ATIS 1000622A-1998 Message Waiting Indicator and Notification Supplementary Services and Associated Switching and Signaling Specifications (Supplement to ATIS-1000622-1992).pdf

《ANSI ATIS 1000622A-1998 Message Waiting Indicator and Notification Supplementary Services and Associated Switching and Signaling Specifications (Supplement to ATIS-1000622-1992).pdf》由会员分享，可在线阅读，更多相关《ANSI ATIS 1000622A-1998 Message Waiting Indicator and Notification Supplementary Services and Associated Switching and Signaling Specifications (Supplement to ATIS-1000622-1992).pdf（12页珍藏版）》请在麦多课文档分享上搜索。

1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-1000622.a.1998(R2013) Message Waiting Indicator and Notification Supplementary Services and Associated Switching and Signaling Specifications As a leading technology and solutions development organization, ATIS brings together the top global IC

2、T companies to advance the industrys most-pressing business priorities. Through ATIS committees and forums, nearly 200 companies address cloud services, device solutions, emergency services, M2M communications, cyber security, ehealth, network evolution, quality of service, billing support, operatio

3、ns, and more. These priorities follow a fast-track development lifecycle from design and innovation through solutions that include standards, specifications, requirements, business use cases, software toolkits, and interoperability testing. ATIS is accredited by the American National Standards Insti

4、tute (ANSI). ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of oneM2M, a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications sectors, and a member of the Inter-Ameri

5、can Telecommunication Commission (CITEL). For more information, visit. AMERICAN NATIONAL STANDARD Approval of an American National Standard requires review by ANSI that the requirements for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is

6、 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 means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objection

7、s 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 preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using pr

8、oducts, processes, or procedures not conforming to the standards. The American National Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretati

9、on 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 name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or withdr

10、awn 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 American National Standards may receive current information on all standards by calling or writing the American Nationa

11、l Standards Institute. Notice of Disclaimer otherwise it shall be included. When included, the NFE shall be coded as follows: sourceEntity = end-PINX, destinationEntity = endPINX.6. In 6.2.1.1, the contents shall be replaced with the following:MWICN is call independent as defined in ANSI T1.610 and

12、utilizes the connection-oriented signaling proce-dures. Additional service states required are:a) Service Null: no service has been requested;b) Service requested: Awaiting response.7. In 6.2.1.2, timer MWI-T1 shall be modified to support a range of 10 seconds to 25 seconds with a default of 10secon

13、ds.8. In 6.2.1.2, the following shall be added:TimerMWI-T3: This timer specifies the maximum length of time that the serving switch will wait for a responseto a Detailed Notification sent to an NT2. The range of this timer shall be from 4 seconds to 7 seconds. Thedefault value is 4 seconds.9. In 6.2

14、.2, the contents shall be replaced with the following:The MWI Control service is invoked by an MSR System by sending an Invoke component to the network in aFacility information element contained in an NCICS SETUP or FACILITY message.10. In 6.2.3, the following shall be added as the last paragraph:No

15、tification of waiting messages is provided to an NT2 as described in 6.2.4.3.ANSI T1.622a-1998Page 3of 10 pages11. In 6.2.4.1.1, the first and second paragraphs (including the two dashed items) shall be replaced with the following:When the MSR System wishes to notify a client user of a waiting messa

16、ge, the MSR System shall send anMWI Control request to its serving network. The MWI Control request is carried in the Facility information el-ement contained in the NCICS SETUP or FACILITY message that uses the call reference established by anNCICS SETUP message. A FACILITY message may be sent at an

17、y time by the MSR System after receivingthe CALL PROCEEDING message. The network shall send an acknowledgement of a successful or unsuc-cessful completion to the MSR System in a Facility information element in an NCICS CONNECT or FACILITYmessage with the same call reference in accordance with ANSI T

18、1.610. The MSR System is allowed to initiatemultiple MWI control transactions using the same call reference. The MSR System should clear the call ref-erence with a RELease message when the following conditions exist:- all outstanding invocations have received a response from the network; and - the M

19、SR System does not wish to initiate any additional invocations for the moment.Under normal conditions, the network should not initiate clearing of an NCICS connection initiated by the userside of the ISDN interface.Each logical MWI entity which resides in a network switch shall be assigned an E.164

20、address for the purposeof establishing an NCICS connection. In the case of a user directly served by the public network, the MSRSystem establishes an NCICS connection to its serving network switch over which MWI Control requests aresent. The TON/NPI field of the Called Party Number information eleme

21、nt is coded to Subscriber number/(ISDN/telephony numbering plan) with digits representing the local 7-digit address of the logical MWI entity orNational number/(ISDN/telephony numbering plan) with digits representing the national 10-digit address of thelogical MWI entity. When the network switch rec

22、eives an NCICS SETUP message containing this addressinginformation, it shall establish an NCICS connection between the MSR System and the logical MWI entity in-dicated by the E.164 address digits.12. In 6.2.4.1.9, the definition of the invalidArgument error shall be changed to include a PARAMETER “i

23、nvalidAr-gumentIdentifier“ that is defined to include the invalid parameter received in the operation. The invalidMSRIDparameter shall be removed as it is no longer necessary. The new error definition for the invalidArgumenterror shall be as shown below:invalidArgument ERRORPARAMETER controltype, de

24、stinationDN, mSRID:=1 2 840 10005 1 101-used when an argument provided by the requesting user in the -messageWaitingIndicatorControl operation is not valid. The error-PARAMETER contains the argument(s) that were determined to be -invalid.13. In 6.2.4.1.9, the comment describing the coding of the “be

25、arerCapability“ argument of the “messageWaiting-IndicatorControl“ operation in the ASN.1 description shall be clarified as follows (new text underlined, deletedtext stricken through):bearerCapability 3 IMPLICIT OCTET STRING OPTIONAL,- coded as shown for octets 3 and 4 following in the bearer - capab

26、ility information element defined in ANSI T1.60714. In 6.2.4, the following 3 subclauses shall be added:6.2.4.3 Message Waiting Notification to an NT2This subclause includes the protocol and procedures for sending a detailed notification to an NT2.ANSI T1.622a-1998Page 4of 10 pages6.2.4.3.1 Sending

27、a Message Waiting Notification to an NT2When the network receives and accepts a request from an MSR System to send an MWI control request toan NT2, and the interface to the NT2 is permitted to receive such a notification, the network shall send a de-tailed notification using the NCICS procedures. Th

28、e detailed notification shall be sent in an Invoke componentcontained in a Facility information element in either an NCICS SETUP message (which also initiates a newNCICS connection) or in a FACILITY message (if an appropriate NCICS connection already exists betweenthe network and the NT2). The conte

29、nts of the Invoke component are described in 6.2.4.3.2. If a new NCICSconnection is established for the sending of the MWI control request, the network may code the Called PartyNumber information element to indicate a local NCICS connection or a networked connection, as appropriate.Whether or not to

30、 establish and clear an NCICS connection for each notification, or to keep the NCICS con-nection up for long term is a network option. The coding of the operation and error value in the ASN.1 description in 6.2.4.3.2 uses object identifiers. Thenational-specific operation value for the “message wait

31、ing notification detailed“ operation is defined with anISO object identifier in number form as 1 2 840 10005 0 7. In name form this object identifier can also bewritten as iso member-body us ansi-t1-610 operations messageWaitingNotificationNT2. The numbers (andnames) in braces represent, in sequence

32、, International Organization for Standardization ISO, member body,United States of America, ANSI T1.610, operations, and the specific subidentifier for “message waiting noti-fication-detailed notification to an NT2.“After sending the Invoke component, the network shall start timer MWI-T3. The NT2 sh

33、all indicate a success-ful notification by sending a Return Result component in a Facility information element contained in a FACIL-ITY or CONNect message, as appropriate. Upon receiving this response, the network switch serving the NT2shall stop timer MWI-T3, and return an indication of successful

34、completion to the MSR System that originatedthe request.The NT2 may reject the notification by sending a Return Error component with an appropriate Error value, forexample, “notification unavailable to destination DN” (see 6.2.5.3 for more information). If the Detailed Noti-fication application is n

35、ot supported by the NT2, the NT2 should reject the notification using a Reject compo-nent with the Problem value “unrecognized operation.“ The NT2 should reject a notification which containsprotocol errors using a Reject component with the appropriate Problem value (see ANSI T1.610). These Re-turn E

36、rror and Reject components shall be returned in a Facility information element contained in a FACILITYor CONNect message, as appropriate.When the serving switch receives a rejection of Detailed Notification from the NT2, the switch shall stop timerMWI-T3 and send an indication of an unsuccessful not

37、ification attempt corresponding to the received indica-tion, for example, “notification unavailable to destination DN,“ to the requesting MSR System. Upon expiry oftimer MWI-T3, the network shall send a RELEASE COMPLETE to the NT2 and return an indication of an un-successful notification attempt, co

38、rresponding to “notification unavailable to destination DN,“ to the requestingMSR System.In the case of data link layer failure between the network and the NT2, the network shall return an indicationof the unsuccessful attempt, corresponding to “notification is unavailable to the destination DN,“ to

39、 the re-questing MSR System.ANSI T1.622a-1998Page 5of 10 pages6.2.4.3.2 ASN.1 Description of Message Waiting Notification - Detailed Notification to an NT2messageWaitingNotificationNT2 OPERATIONARGUMENT SEQUENCE controlType 0 IMPLICIT ENUMERATED activate (0),deactivate (1),destinationDN 1 IMPLICIT D

40、igits,mSRID 2 IMPLICIT NumericString SIZE (10) OPTIONAL,bearerCapability 3 IMPLICIT OCTET STRING OPTIONAL,- coded as shown for octets 3 and 4 in the Bearer - capability information element defined in ANSI T1.607callingNumber 4 IMPLICIT Digits OPTIONAL,timestamp UTCTime OPTIONAL,mwiType 5 IMPLICIT EN

41、UMERATED active1 (1), - normalactive2 (2),active3 (3) OPTIONALRESULT-to indicate successful completionERRORSunassignedDN,missingCustomerRecord,notificationUnavailableToDestinationDN,mSRIDdidNotMatchUserProfile,resourcesUnavailable:=1 2 840 10005 0 7Digits:= OCTET STRING- coded as shown for octets 3

42、and following in the Called party number - information element defined in ANSI T1.607- UTCTime is coded as YYMMDDhhmm plus or minus hhmm- local time Time difference from- Greenwich Mean Time-The following errors are of global significance.unassignedDN ERRORPARAMETER destinationDN:= 1 2 840 10005 1 1

43、4-used when the destination DN is not currently assigned-to an active interfacemissingCustomerRecord ERRORPARAMETER destinationDN:=1 2 840 10005 1 4-used when the destination DN/BCis not subscribed to the-Message Waiting Notification featureANSI T1.622a-1998Page 6of 10 pagesnotificationUnavailableTo

44、DestinationDN ERROR:=1 2 840 10005 1 16-used when the notification cannot be provided to the-destination DN for some short term reason (e.g., the-line is temporarily out of service)mSRIDdidNotMatchUserProfile ERRORPARAMETER mSRID:=1 2 840 10005 1 17-used when the MSRID did not match the-Authorized M

45、SRID(s) in the client users DN profile-The following error is of local significance on the switch which serves -the ISDN User equipment receiving this detailed notification.resourcesUnavailable ERROR:=11-used to provide flow control on the local access15. In subclause 6.2.5.1.1, to align with the ab

46、ove changes, the supporting text shall be revised as follows (newtext underlined, deleted text stricken through):If the “controlType“ argument is not valid, then the MWI control request shall be rejected with a Fa-cility information element contained in a FACILITY message. The Facility information e

47、lement shall contain a Return Error component with the error “invalid argument,“ containing the “controlType“ argument received in the “messageWaitingIndicatorControl“ operation in the Error PARAMETER.If the “destination DN“ argument is present, but the network determines that the argument does not

48、con-tain a valid DN, and that a valid DN cannot be derived, the network shall reject the MWI control request with a Facility information element in a FACILITY message. The Facility information element shall con-tain a Return Error component with the error “invalid argument,“ and containing the “dest

49、inationDN“ ar-gument received in the “messageWaitingIndicatorControl“ operation in the Error PARAMETER.If the “MSRID“ argument does not pass screening, then the MWI control request shall be rejected with a Facility information element contained in a FACILITY message. The Facility information ele-ment shall contain a Return Error component with the error “invalid MSRID.“ “invalid argument,“ containing the “mSRID“ argument received in the “mess