1、 TIA-41.324-E-1E (Addendum to TIA-41.324-E) August 2012Mobile Application Part (MAP) - Voice Feature Scenarios: Calling Number Identification Presentation, Calling Number Identification Restriction ANSI/TIA-41.324-E-1E-2012 APPROVED: AUGUST 13, 2012 NOTICE TIA Engineering Standards and Publications
2、are designed to serve the public interest through eliminating misunderstandings 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. T
3、he existence of such Standards and Publications shall not in any respect 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 N
4、on-TIA members, either domestically or internationally. Standards and 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 t
5、o parties adopting the Standard or Publication. This Standard does not 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
6、 the applicability of regulatory limitations before its use. (From Project No. SP-3-3590.324-RV5-AD1-E-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). Publi
7、shed by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Technology Department 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-518
8、7) International (303-397-2896) or search online at http:/www.tiaonline.org/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 prohibi
9、ted without copyright permission. For copyright permission to reproduce portions 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
10、.cfm#copyright or Telecommunications Industry Association Technology (b) there 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 editi
11、ng process. The use or practice of contents of this Document may involve the 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 pendi
12、ng patent applications are claimed and called to TIAs attention, a statement 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
13、will neither be a party to discussions of any licensing terms or conditions, 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
14、 suggested or provided in the Manual have been complied with as respects the 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
15、designated as a standard, specification, recommendation or otherwise), whether 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 S
16、SO for IPR or letters of assurance relating to any such Normative Reference; (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
17、 records or publications of the other SSO shall not constitute identification 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
18、products, designs or services or any claims of compliance with the contents 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 US
19、E, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL 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 REG
20、ULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR 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 HEREI
21、N, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL 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 OTHERWIS
22、E, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION 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. 1234567891011121314151617181920212223242526272829303132333435363738394041424
23、34445464748495051525354555657585960iiREVISION HISTORYRevision Date RemarksX.S0004-324-E v1.0 January 2007 Initial publication.X.S0004-324-E v2.0 December 2008 Addition of section 2.6 based on Miscellaneous Enhancements 10.0X.S0004-324-E v2.012345678910111213141516171819202122232425262728293031323334
24、3536373839404142434445464748495051525354555657585960324-1 INTRODUCTION1 INTRODUCTIONUnless otherwise noted, the scenarios in this part depict features operating individually; i.e.,feature interactions are not considered unless specifically noted. The scenarios in this part do not include a complete
25、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 Parts-540 and -550
26、.2 Calling Number Identification PresentationThis section depicts the communications between network entities in various situations relatedto automatic roaming and Calling Number Identification Presentation (CNIP). These scenariosare for illustrative purposes only.2.1 CNIP Invocation to an Idle Subs
27、criberThis scenario describes CNIP invocation to an idle, authorized MS.Figure 1 CNIP Invocation to an Idle SubscriberabcdefghijMSC HLR VLR MSC MS Originating SystemServing Systemcall setup call answer LRTROUTREQ MSID, CNIdigitsASCII, CNIsubaddressInfo locreq TERMLIST, REDIND routreq TLDN LOCREQ DGT
28、SDIAL, CNIdigitsBCD, CNIsubaddressInfo ROUTREQ MSID, CNIdigitsASCII, CNIsubaddressInfo routreq TLDN alert (CNIP info) call origination (w/CNI) RRTRRTX.S0004-324-E v2.0Calling Number Identification Presentation1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950
29、51525354555657585960324-2a. A call origination with a dialed MS address digits (i.e., directory number) is receivedby the Originating MSC. Also included in the call origination is calling numberidentification (CNI) information, which may include: one or two calling partynumbers, a calling party suba
30、ddress, a redirecting number, and a redirectingsubaddress.b. The Originating MSC sends a LOCREQ to the MSs HLR, including parameters basedon the CNI information received in Step a.c. The HLR constructs a ROUTREQ, including parameters based on the CNI informationreceived in Step b, and sends it to th
31、e VLR where the MS is registered.d. The VLR forwards the ROUTREQ to the current Serving MSC. Parameters are as inStep c.e. In reaction to the ROUTREQ, the Serving MSC checks its internal data structures anddetermines that the MS is currently idle. Therefore the Serving MSC allocates a TLDNand return
32、s this information to the VLR in the routreq. The Serving MSC stores thereceived CNI information.f. The VLR sends the routreq to the HLR.g. When the routreq is received by the HLR, it returns a locreq to the OriginatingMSC. The locreq includes routing information in the form of the TerminationListpa
33、rameter, along with an indication of the reason for extending the incoming call (i.e.,for CD) in the DMH_RedirectionIndicator parameter.Additional Parameters Usage TypeCNIdigitsBCD: CNI digits parameters in BCD format:CallingPartyNumber-Digits1Calling number digits (network-provided), incl. presenta
34、tion restriction information.RCallingPartyNumber-Digits2Calling number digits (user-provided), incl. presentation restriction information.ORedirectingNumber-DigitsRedirecting number digits, incl. presentation restriction information.OCNIsubaddressInfo: CNI subaddress information:CallingPartySubad-dr
35、essCalling number subaddress (user-provided).ORedirectingSubaddress Redirecting number subaddress. OAdditional Parameters Usage TypeCNIdigitsASCII: CNI digits parameters in ASCII format:CallingPartyNumber-String1Calling number digits (network-provided), incl. presentation restriction information.RCa
36、llingPartyNumber-String2Calling number digits (user-provided), incl. presentation restriction information.ORedirectingNumber-StringRedirecting number digits, incl. presentation restriction information.OCNIsubaddressInfo: CNI subaddress information:CallingPartySubad-dressCalling number subaddress (us
37、er-provided).ORedirectingSubaddress Redirecting number subaddress. OX.S0004-324-E v2.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960324-3 Calling Number Identification Presentationh. A voice path is then established between the Origina
38、ting MSC and the Serving MSCusing protocols defined by the interconnection method.1i. When the inter-MSC call is received at the Serving MSC, the MS is alerted. Includedin the alert is the appropriate Calling Number Identification Presentation information.j. When the served MS answers, the call is e
39、stablished.1If SS7 ISUP is used end-to-end, the IAM message can be used to deliver CNI information.X.S0004-324-E v2.0Calling Number Identification Presentation123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960324-42.2 CNIP Interaction with
40、 CWThis scenario describes CNIP invocation to a busy, authorized MS for which CW is active.a. A call involving the served MS is in progress.b-e. Same as CNIP, Section 2.1, Steps a-d, respectively.f. In reaction to the ROUTREQ, the Serving MSC checks its internal data structures anddetermines that th
41、e MS is busy in another call but has CW active. Therefore, theServing MSC allocates a TLDN (Temporary Local Directory Number) and returns thisinformation to the VLR in the routreq. The Serving MSC stores the received CNIinformation.g-i. Same as CNIP, Section 2.1, Steps f-h, respectively.j. When the
42、(second) inter-MSC call is received at the Serving MSC, the Serving MSCprovides the MS with a CW notification. Included in the notification is the appropriateCalling Number Identification Presentation information.Figure 2 CNIP Interaction with CWabcdefghijMSC HLR VLR MSC MSOriginating SystemServing
43、Systemcall setup call in progress ROUTREQ MSID, CNIdigitsASCII, CNIsubaddressInfo locreq TERMLIST, REDIND routreq TLDN LOCREQ DGTSDIAL, CNIdigitsBCD, CNIsubaddressInfo ROUTREQ MSID, CNIdigitsASCII, CNIsubaddressInfo routreq TLDN alert (CNIP info) call origination (w/CNI) LRTRRT RRTX.S0004-324-E v2.0
44、123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960324-5 Calling Number Identification Presentation2.3 CNIP Interaction with CW After HandoffThis scenario describes CNIP invocation to a busy, authorized MS for which CW is active, afterinter
45、system handoff of the MS.a. A call involving the served MS is in progress.b-e. Same as CNIP, Section 2.1, Steps a-d, respectively.f. In reaction to the ROUTREQ, the Serving MSC checks its internal data structures anddetermines that the MS is busy in another call but has CW active. Therefore, theServ
46、ing MSC allocates a TLDN (Temporary Local Directory Number) and returns thisinformation to the VLR in the routreq. The Serving MSC stores the received CNIinformation.Figure 3 CNIP Interaction with Call Waiting After HandoffabcdefghijklmnoMSC VLR MSC MS Originating System Serving System HLR MSC call
47、origination (w/CNI) routreq TLDN locreq TERMLIST, REDIND inter-MSC call setup INFOFWD CNIdigitsASCII, CNIsubaddressInfo ROUTREQ MSID, CNIdigitsASCII, CNIsubaddressInfo LOCREQ DGTSDIAL, CNIdigitsBCD, CNIsubaddressInfo MSC Anchor System Tandem System routreq TLDN CNI Presentation infofwd infofwd ROUTR
48、EQ MSID, CNIdigitsASCII, CNIsubaddressInfo call waiting alert call in progress LRT RRTTLDNATIFTINFOFWD CNIdigitsASCII, CNIsubaddressInfo IFTRRTX.S0004-324-E v2.0Calling Number Identification Presentation1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
49、54555657585960324-6g-i. Same as CNIP, Section 2.1, Steps f-h, respectively.j. The Anchor MSC then sends an INFOFWD to the Tandem MSC, including the CNIinformation.k. The Tandem MSC adjusts the InterMSCCircuitID to identify the circuit between it andthe Serving MSC, and forwards the INFOFWD to the Serving MSC.l. The Serving MSC presents the CNI information to the served MS in an appropriatefashion.m. The Serving MSC acknowledges receipt by sending an infofwd to the TandemMSC.n. The Tandem MSC forwards the infofwd to the
