1、 TIA-41.335-E August 2012Mobile Application Part (MAP) - Voice Feature Scenarios: Calling Name Presentation, Calling Name Restriction ANSI/TIA-41.335-E-2012 APPROVED: AUGUST 9, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misund
2、erstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any res
3、pect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards an
4、d Publications are adopted by TIA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does n
5、ot purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. (From P
6、roject No. SP-3-3590.335-RV5-A, formulated under the cognizance of the TIA TR-45 Mobile and Personal Communications Systems Standards, TR-45.8 Subcommittee on Core Networks- Mobile and Personal Communications Standards). Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Technology D
7、epartment 2500 Wilson Boulevard Arlington, VA 22201 U.S.A. PRICE: Please refer to current Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS AND ENGINEERING PUBLICATIONS or call IHS, USA and Canada (1-877-413-5187) International (303-397-2896) or search online at http:/www.tiaonline.or
8、g/standards/catalog/ All rights reserved Printed in U.S.A. NOTICE OF COPYRIGHT This document is copyrighted by the TIA. Reproduction of these documents either in hard copy or soft copy (including posting on the web) is prohibited without copyright permission. For copyright permission to reproduce po
9、rtions of this document, please contact the TIA Standards Department or go to the TIA website (www.tiaonline.org) for details on how to request permission. Details are located at: http:/www.tiaonline.org/standards/catalog/info.cfm#copyright or Telecommunications Industry Association Technology (b) t
10、here is no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may involve t
11、he use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a stateme
12、nt from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or condition
13、s, which are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects t
14、he Document or its contents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whe
15、ther such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Referenc
16、e; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identificat
17、ion to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the content
18、s of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLE
19、CTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR
20、 SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL
21、OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGAT
22、ION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. REVISION HISTORYRevision Date RemarksX.S0004-335-E v1.0 January 2009 Initial publication.X.S0004-335-E v1.01234567891011121314151617181920212223242526
23、27282930313233343536373839404142434445464748495051525354555657585960335-1 INTRODUCTION1 INTRODUCTIONUnless otherwise noted, the scenarios in this section depict features operating individually; i.e.,feature interactions are not considered unless specifically noted.The scenarios in this part do not i
24、nclude a complete listing of operation parameters, either in thefigures or in the accompanying text descriptions. Parameters are included where they aredeemed necessary to improve the understanding of the scenario. For a complete description ofthe parameters associated with each operation, refer to
25、Parts 540 and 550.2 CALLING NAME PRESENTATIONThis section depicts the interactions between network entities in various situations related toautomatic roaming and Calling Name Presentation (CNAP). These scenarios are for illustrativepurposes only.X.S0004-335-E v1.0CALLING NAME PRESENTATION12345678910
26、1112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960335-22.1 CNAP Invocation to an Idle MSThis scenario describes CNAP invocation to an idle, authorized MS which has CNAP active.The HLR queries an SCP to obtain the text to present to the called subscri
27、ber.a. A call origination with dialed MS address digits (i.e., Directory Number) is receivedby the Originating MSC. Also included in the call origination are calling numberidentification (CNI) and, if delivered by the network, the calling name identification(CNA).Figure 1 CNAP Invocation to an Idle
28、MSabcdefghijklHLR SCP VLR MS Serving System Called Party MSC call setup ROUTREQ MSID, DISPTEXT servreq DISPTEXT locreq TERMLIST, REDIND TLDNATSVRTLRTcall origination (w/ calling party information) MSC Originating System SERVREQ SRVID, CNIdigitsBCD, NAME, PLIND LOCREQ DGTSDIAL, CNIdigitsBCD, NAME ROU
29、TREQ MSID, DISPTEXT routreq TLDN routreq TLDN call answer alert (CNAP info) RRTRRTX.S0004-335-E v1.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960335-3 CALLING NAME PRESENTATIONb. The Originating MSC sends a LOCREQ to the MSs HLR, incl
30、uding the CNIinformation. The CNA information is included if received at Step-a.c. The HLR determines CNAP should be invoked and sends a SERVREQ to a ServiceControl Point (SCP) to obtain the text to present to the called subscriber. TheSERVREQ includes the CNI information, and the CNA information if
31、 received atStep-b. The SRVID parameter is set to indicate whether the SCP shall execute theCNAP service or the CNAP and redirecting name display (RND) service. (Note: theHLR may obtain the text to present to the called subscriber from an alternate source inlieu of performing the ServiceRequest oper
32、ation.).Parameters Usage TypeCNIdigitsBCD: CNI digits parameters in BCD format: RCPNDGTS1 CallingPartyNumberDigits1. Calling number digits (network-provided), including presen-tation restriction information.OCPNDGTS2 CallingPartyNumberDigits2. Calling number digits (user-provided), including present
33、ation restriction information.ORNDGTS Redirecting number digits, including presen-tation restriction information.ODGTSDIAL Digits identifying called party. RNAME: The calling name identification parameters: CGNAME CallingPartyName. The calling name identi-fication of the original calling party, incl
34、uding presentation restriction information.ORDNAME RedirectingPartyName. The calling name identification of the last redirecting party, including presentation restriction infor-mation.OParameters Usage TypeSRVD ServiceID. The identifier of the specific calling name presentation service for the SCP t
35、o execute.RCNIdigitsBCD: CNI digits parameters in BCD format: RCPNDGTS1 CallingPartyNumberDigits1. Calling number digits (network-provided), including presen-tation restriction information.OCPNDGTS2 CallingPartyNumberDigits2. Calling number digits (user-provided, passed screening), including present
36、ation restriction infor-mation.ORNDGTS Redirecting number digits, including presen-tation restriction information.ONAME: The calling name identification parameters: CGNAME CallingPartyName. The calling name identi-fication of the original calling party, including presentation restriction information
37、.ORDNAME RedirectingPartyName. The calling name identification of the last redirecting party, including presentation restriction infor-mation.OX.S0004-335-E v1.0CALLING NAME PRESENTATION123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960335
38、-4d. The SCP sends the servreq to the HLR including the text to present to the calledsubscriber in the DisplayText (DISPTEXT) parameter. If the CallingPartyNameparameter is not received in the SERVREQ and the calling partys number is markedas presentation restricted, the SCP may treat the calling pa
39、rtys name as presentationrestricted as well. If the CallingPartyName parameter is not received in the SERVREQand the calling partys number is marked as presentation allowed, the SCP may use thedefault presentation status of the calling partys name (as stored in the network). TheSCP uses network-vali
40、dated CNI information to identify the calling party. Network-validated is network-provided or user-provided (screening passed). (Note: the SCPmay obtain the text to present to the called subscriber from an alternate database.)e. The HLR sends a ROUTREQ to the VLR where the MS is registered and inclu
41、des theDISPTEXT parameterf. The VLR forwards the ROUTREQ to the current Serving MSC. Parameters are as inStep-e.g. In response to the ROUTREQ, the Serving MSC checks its internal data structures anddetermines that the MS is currently idle. Therefore, the Serving MSC allocates aTemporary Local Direct
42、ory Number (TLDN) and returns this information to the VLRin the routreq. The Serving MSC stores the received DISPTEXT parameter.h. The VLR sends the routreq to the HLR.i. When the routreq is received by the HLR, it returns a locreq to the OriginatingMSC. The locreq includes routing information in th
43、e form of the TerminationListparameter, along with an indication of the reason for extending the incoming call (i.e.,for CD) in the DMH_RedirectionIndicator parameter. The DISPTEXT parameter willbe included for local termination.j. A connection is established between the Originating MSC and the Serv
44、ing MSC usingprotocols defined by the interconnection method.k. When the inter-MSC call is received at the Serving MSC, the MS is alerted. Includedin the alert is the text received in the DISPTEXT parameter.When the VMS answers,it is connected to the served MS.l. When the served MS answers, the call
45、 is connected.PLIND The subscribers preferred language. OParameters Usage TypeMIN Called MS MIN. RDISPTEXT Text for display by the MS. RX.S0004-335-E v1.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960335-5 CALLING NAME PRESENTATION2.2
46、CNAP Interaction with CWThis scenario describes CNAP invocation to a busy, authorized MS for which CNAP and CWare active.a. A call involving the served MS is in progress.b-g. Same as Section 2.1, Steps a-f respectively.h. In reaction to the ROUTREQ, the Serving MSC checks its internal data structure
47、s and determines that the MS is busy in another call but has CW active. Therefore, the Serving MSC allocates a TLDN (Temporary Local Directory Number) and returns this information to the VLR in the routreq. The Serving MSC stores the received DISPTEXT parameter.i-k. Same as Section 2.1, Steps h-j re
48、spectively.l. When the (second) inter-MSC call is received at the Serving MSC, the Serving MSC provides the MS with a CW notification. Included in the notification is the text received in the DISPTEXT parameter.Figure 2 CNAP Invocation to an Idle MSabcdefghijklHLR SCP VLR MS Serving System Called Pa
49、rty MSC call setup ROUTREQ MSID, DISPTEXT servreq DISPTEXT locreq TERMLIST, REDIND TLDNATSVRTLRTcall origination (w/ calling party information) MSC Originating System SERVREQ SRVID, CNIdigitsBCD, NAME, PLIND LOCREQ DGTSDIAL, CNIdigitsBCD, NAME ROUTREQ MSID, DISPTEXT routreq TLDN routreq TLDN call in progress call waiting alert (CNAP info) RRTRRTX.S0004-335-E v1.0CALLING NAME PRESENTATION123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960335-62.3 CNAP Interaction with
