ANSI TIA-41.324-E-2007 Mobile Application Part (MAP) C Voice Feature Scenarios Calling Number Identification Presentation Calling Number Identification Restriction《移动应用部分(MAP).声音特点.pdf

1、 TIA-41.324-E September 2007Mobile Application Part (MAP) Voice Feature Scenarios: Calling Number Identification Presentation, Calling Number Identification Restriction ANSI/TIA-41.324-E-2007 APPROVED: JULY 11, 2007 REAFFIRMED: JANUARY 10, 2013 NOTICE TIA Engineering Standards and Publications are d

2、esigned 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. The ex

3、istence 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 Non-TI

4、A 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 to par

5、ties 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 the

6、applicability of regulatory limitations before its use. (From Project No. 3-3590.324-RV5-RF1, formulated under the cognizance of the TIA TR-45 Mobile (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 Docum

7、ent 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 the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no se

8、arch or investigation for IPR. When IPR consisting of patents and published pending 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

9、 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 conditions, which are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or n

10、on-discriminatory. TIA does not warrant or represent that procedures or practices 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 SS

11、O”) engaged in the formulation, development or publication of standards (whether 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 dis

12、claims 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 Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending

13、patent applications shall apply; and (iii) Information as to claims of IPR in the 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 conten

14、ts of the Document. TIA does not certify, inspect, test or otherwise investigate 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 ACCURA

15、CY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, 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 WARR

16、ANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, 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

17、 OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, 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 CONTRAC

18、T, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, 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 LIMITATI

19、ONS. TIA-41.324-EMobile Application Part (MAP) - Voice Feature Scenarios: Calling Number Identification Presentation, Calling Number Identification RestrictionREVISION HISTORYCopyright Telecommunications Industry Association 2007. All rights reserved.This document is subject to change.Revision Date

20、RemarksTIA-41.324-E January 2007 Initial publication.TIA-41.324-EiiThis page is left blank intentionally.TIA-41.324-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960324-1 INTRODUCTION1 INTRODUCTIONUnless otherwise noted, the scenarios in

21、 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 listing of operation parameters, either in thefigures or in the accompanying text descriptions. Parameters are included where

22、 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.2 Calling Number Identification PresentationThis section depicts the communications between network entities in various situ

23、ations relatedto automatic roaming and Calling Number Identification Presentation (CNIP). These scenariosare for illustrative purposes only.2.1 CNIP Invocation to an Idle SubscriberThis scenario describes CNIP invocation to an idle, authorized MS.Figure 1 CNIP Invocation to an Idle Subscriberabcdefg

24、hijMSC HLR VLR MSC MS Originating SystemServing Systemcall setup call answer LRTROUTREQ MSID, CNIdigitsASCII, CNIsubaddressInfo locreq TERMLIST, REDIND routreq TLDN LOCREQ DGTSDIAL, CNIdigitsBCD, CNIsubaddressInfo ROUTREQ MSID, CNIdigitsASCII, CNIsubaddressInfo routreq TLDN alert (CNIP info) call or

25、igination (w/CNI) RRTRRTTIA-41.324-ECalling Number Identification Presentation123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960324-2a. A call origination with a dialed MS address digits (i.e., directory number) is receivedby the Originati

26、ng MSC. Also included in the call origination is calling numberidentification (CNI) information, which may include: one or two calling partynumbers, a calling party subaddress, a redirecting number, and a redirectingsubaddress.b. The Originating MSC sends a LOCREQ to the MSs HLR, including parameter

27、s 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 the VLR where the MS is registered.d. The VLR forwards the ROUTREQ to the current Serving MSC. Parameters are as inStep c.e. In react

28、ion 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 returns this information to the VLR in the routreq. The Serving MSC stores thereceived CNI information.f. The VLR sends the routreq to th

29、e 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 TerminationListparameter, along with an indication of the reason for extending the incoming call (i.e.,for CD) in the DMH_RedirectionIndicator param

30、eter.Additional Parameters Usage TypeCNIdigitsBCD: CNI digits parameters in BCD format:CallingPartyNumber-Digits1Calling number digits (network-provided), incl. presentation restriction information.RCallingPartyNumber-Digits2Calling number digits (user-provided), incl. presentation restriction infor

31、mation.ORedirectingNumber-DigitsRedirecting number digits, incl. presentation restriction information.OCNIsubaddressInfo: CNI subaddress information:CallingPartySubad-dressCalling number subaddress (user-provided).ORedirectingSubaddress Redirecting number subaddress. OAdditional Parameters Usage Typ

32、eCNIdigitsASCII: CNI digits parameters in ASCII format:CallingPartyNumber-String1Calling number digits (network-provided), incl. presentation restriction information.RCallingPartyNumber-String2Calling number digits (user-provided), incl. presentation restriction information.ORedirectingNumber-String

33、Redirecting number digits, incl. presentation restriction information.OCNIsubaddressInfo: CNI subaddress information:CallingPartySubad-dressCalling number subaddress (user-provided).ORedirectingSubaddress Redirecting number subaddress. OTIA-41.324-E123456789101112131415161718192021222324252627282930

34、313233343536373839404142434445464748495051525354555657585960324-3 Calling Number Identification Presentationh. A voice path is then established between the Originating MSC and the Serving MSCusing protocols defined by the interconnection method.1i. When the inter-MSC call is received at the Serving

35、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 established.1If SS7 ISUP is used end-to-end, the IAM message can be used to deliver CNI information.TIA-41.324-ECalling Number Identificat

36、ion Presentation123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960324-42.2 CNIP Interaction with 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

37、. 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, theServing MSC allocates a TLDN (Temporary Local Directory Number) and returns thisi

38、nformation 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 (second) inter-MSC call is received at the Serving MSC, the Serving MSCprovides the MS with a CW notification. Included in the notification is

39、the appropriateCalling Number Identification Presentation information.Figure 2 CNIP Interaction with CWabcdefghijMSC HLR VLR MSC MSOriginating SystemServing Systemcall setup call in progress ROUTREQ MSID, CNIdigitsASCII, CNIsubaddressInfo locreq TERMLIST, REDIND routreq TLDN LOCREQ DGTSDIAL, CNIdigi

40、tsBCD, CNIsubaddressInfo ROUTREQ MSID, CNIdigitsASCII, CNIsubaddressInfo routreq TLDN alert (CNIP info) call origination (w/CNI) LRT RRTRRTTIA-41.324-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960324-5 Calling Number Identification Pr

41、esentation2.3 CNIP Interaction with CW After HandoffThis scenario describes CNIP invocation to a busy, authorized MS for which CW is active, afterintersystem 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 t

42、he ROUTREQ, the Serving MSC checks its internal data structures anddetermines that the 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 receive

43、d CNIinformation.Figure 3 CNIP Interaction with Call Waiting After HandoffabcdefghijklmnoMSC VLR MSC MS Originating System Serving System HLR MSC call origination (w/CNI) routreq TLDN locreq TERMLIST, REDIND inter-MSC call setup INFOFWD CNIdigitsASCII, CNIsubaddressInfo ROUTREQ MSID, CNIdigitsASCII,

44、 CNIsubaddressInfo LOCREQ DGTSDIAL, CNIdigitsBCD, CNIsubaddressInfo MSC Anchor System Tandem System routreq TLDN CNI Presentation infofwd infofwd ROUTREQ MSID, CNIdigitsASCII, CNIsubaddressInfo call waiting alert call in progress LRT RRTTLDNATIFTINFOFWD CNIdigitsASCII, CNIsubaddressInfo IFTRRTTIA-41

45、.324-ECalling Number Identification Presentation123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960324-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 CNIinfo

46、rmation.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 i

47、nfofwd to the TandemMSC.n. The Tandem MSC forwards the infofwd to the Anchor MSC.o. When the (second) inter-MSC call is received at the Anchor MSC, the Anchor MSCprovides the MS with a Call Waiting notification.Additional Parameters Usage TypeCNIdigitsASCII: CNI digits parameters in ASCII format:Cal

48、lingPartyNumber-String1Calling number digits (network-provided), incl. presentation restriction information.RCallingPartyNumber-String2Calling number digits (user-provided), incl. presentation restriction information.ORedirectingNumber-StringRedirecting number digits, incl. presentation restriction

49、information.OCNIsubaddressInfo: CNI subaddress information:CallingPartySubad-dressCalling number subaddress (user-provided).ORedirectingSubaddress Redirecting number subaddress. OTIA-41.324-E123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960324-7 Calling Number Identification Presentation2.4 CNIP Interaction with CFUThis scenario describes CNIP invocation to an authorized MS for which CFU is active. a-b. Same as CNIP, Section 2.1, Steps a-b.c. The HLR det