1、 TIA-41.325-E August 2012Mobile Application Part (MAP) - Voice Feature Scenarios: Conference Calling ANSI/TIA-41.325-E-2012 APPROVED: AUGUST 10, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturer
2、s 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 respect preclude any member or non-
3、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 and Publications are adopted by TI
4、A 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 not purport to address all safety
5、 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 Project No. SP-3-3590.325-RV5-A,
6、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 Department 2500 Wilson Boulevard
7、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.org/standards/catalog/ All rights
8、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 portions of this document, please
9、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) there is no assurance that the Do
10、cument 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 the use of intellectual property
11、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 statement from the holder thereof is re
12、quested, 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 conditions, which are instead left to the
13、 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 the Document or its contents. If
14、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), whether such reference consists of
15、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 Reference; (ii) TIAs policy of encourage
16、ment 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 identification to TIA of a claim of Essenti
17、al 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 contents of the Document. ALL WARRANTIE
18、S, 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 INTELLECTUAL PROPERTY RIGHTS. TIA EXPRE
19、SSLY 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 SERVICE REFERRED TO IN THE DOCU
20、MENT 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 OR CONSEQUENTIAL DAMAGES (INCLUD
21、ING 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 NEGATION OF DAMAGES IS A FUNDAMENTAL
22、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-325-E v1.0 April 2008 Initial publication.X.S0004-325-E v1.012345678910111213141516171819202122232425262728293031323334353637383940414243
23、4445464748495051525354555657585960325-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 listing of operatio
24、n 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.2 THREE-WAY CALLING
25、No feature-specific intersystem operations are required for the Three-Way Calling (3WC)feature.3 CONFERENCE CALLINGThis section depicts the interactions between network entities in various situations related toautomatic roaming and Conference Calling (CC). These scenarios are for illustrative purpos
26、esonly.X.S0004-325-E v1.0CONFERENCE CALLING123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960325-23.1 CC Invocation with Call Setup RequestThis scenario describes the invocation of CC by an authorized MS. The invocation occurs witha concur
27、rent call setup request. It also illustrates how another party is added to the conferencecall via the entry of a feature code string by the controlling subscriber.a. A call origination and dialed digits are received by the Serving MSC. During analysisof the dialed digits, the Serving MSC detects a f
28、eature code string.b. The dialed digits are included in a FEATREQ and sent from the Serving MSC to theHLR associated with the MS.Figure 1 CC Invocation with Call Setup Request abcdefghijklmnopMS HLR Serving System FEATREQ DGTSDIAL feature confirmation featreq CCI, TERMLIST *FC+#+TA+ SEND STATE MSCId
29、le FEATREQ DGTSDIAL, CCI featreq CCI, TERMLIST *FC+#+TA+ SEND call setup feature confirmation Conference Conference Adding On Idle SEND put call-leg1 on hold extend call-leg2 to conferee-2 Conference 2-way Conference END SEND connect conferees and MS in conference call release conferees and MS FRRTF
30、RRTX.S0004-325-E v1.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960325-3 CONFERENCE CALLINGc. The HLR detects the authorized CC request and sends a featreq to the ServingMSC. The featreq includes call routing information in the Termina
31、tionListparameter. It also includes the ConferenceCallingIndicator parameter, indicating thatConference Calling is active for the call.d. The Serving MSC stores the ConferenceCallingIndicator information, activatesconference calling, and provides treatment to the served MS as indicated in thefeatreq
32、. In this case, the treatment is to apply feature confirmation.e. The Serving MSC extends the call using the call routing information in theTerminationList parameter (call-leg-1).f. MS-1 sends a flash request to the Serving MSC (i.e., presses the key).g. The Serving MSC puts call-leg-1 on hold.h. Di
33、aled digits are received by the Serving MSC. During analysis of the dialed digits,the Serving MSC detects a feature code string.i. The dialed digits are included in a FEATREQ and sent from the Serving MSC to theHLR associated with the MS. The Serving MSC also includes theConferenceCallingIndicator p
34、arameter, indicating the number of conferees already inthe call.j. The HLR detects the authorized CC request and sends a featreq to the ServingMSC. The featreq includes call routing information in the TerminationListparameter. It also includes the ConferenceCallingIndicator parameter, indicating tha
35、tConference Calling is active for the call and the maximum number of allowedconferees.k. The Serving MSC provides treatment to the served MS as indicated in the featreq.In this case, the treatment is to apply feature confirmation.l. The Serving MSC extends the call using the call routing information
36、 in theTerminationList parameter (call-leg-2).m. MS-1 sends a Flash Request to the Serving MSC (i.e., presses the key).n. The Serving MSC connects the served MS, the held conferee and the new party into aconference call.o. MS-1 sends a Disconnect Request to the Serving MSC (i.e., presses the key).p.
37、 The Serving MSC releases the served MS and conferees and discards theConferenceCallingIndicator information.Additional Parameters Usage TypeCCI ConferenceCallingIndicator. Presence of this parameter indicates that the outgoing call is to be handled as a Conference Call. The parameter carries the ma
38、ximum number of allowed conferees.RSENDSENDENDX.S0004-325-E v1.0CONFERENCE CALLING123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960325-43.2 CC Add Party (Without Feature Code Entry)This scenario describes the invocation of CC by an author
39、ized MS. The invocation occurs witha concurrent call setup request. It also illustrates how another party is added to the conferencecall via the entry of a termination address only (i.e., no feature code is entered when adding thesecond party) by the controlling subscriber. a-g. Same as CC, Section
40、3.1, Steps a-g.h. Dialed digits are received by the Serving MSC.i. Since a feature code string is not present, the Serving MSC provides treatment to theserved MS based on the fact that conference calling is active. If the maximum numberof conferees has not been exceeded, the Serving MSC applies call
41、 confirmation.j. The Serving MSC extends the call using the termination address digits provided (call-leg-2).k. MS-1 sends a flash request to the Serving MSC (i.e., presses the key).Figure 2 CC Add Party (Without Feature Code Entry)abcdefghijklmnMS HLR Serving System FEATREQ DGTSDIAL feature confirm
42、ation FRRTfeatreq CCI, TERMLIST *FC+#+TA+ SEND STATE MSCIdle TA+ SEND call setup feature confirmation Conference Conference Adding On Idle SEND put call-leg1 on hold extend call-leg2 to conferee-2 Conference 2-way Conference END SEND connect conferees and MS in conference call release conferees and
43、MS SENDX.S0004-325-E v1.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960325-5 CONFERENCE CALLINGl. The Serving MSC connects the served MS, the held conferee and the new party into aconference call.m. MS-1 sends a Disconnect Request to t
44、he Serving MSC (i.e., presses the key).n. The Serving MSC releases the served MS and conferees and discards theConferenceCallingIndicator information.3.3 CC Invocation During a CallThis scenario describes the invocation of CC by an authorized MS. The invocation occursduring a call. a. MS-1 is engage
45、d in a call (call-leg-1)b. MS-1 sends a flash request to the Serving MSC (i.e., presses the key).c. The Serving MSC puts call-leg-1 on hold.d. Dialed digits are received by the Serving MSC. During analysis of the dialed digits,the Serving MSC detects a feature code string.e. The dialed digits are in
46、cluded in a FEATREQ and sent from the Serving MSC to theHLR associated with the MS.Figure 3 CC Invocation During a CallENDabcdefghijklMS HLR Serving System FEATREQ DGTSDIAL feature confirmation featreq CCI, TERMLIST *FC+#+TA+ SEND STATE MSC2-way put call-leg1 on hold Conference Adding On Idle SEND c
47、all-leg1 in progress extend call-leg2 to conferee-2 Conference 2-way Conference END SEND connect conferees and MS in conference call release conferees and MS FRRTSENDX.S0004-325-E v1.0CONFERENCE CALLING12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535
48、4555657585960325-6f. The HLR detects the authorized CC request and sends a featreq to the ServingMSC. The featreq includes call routing information in the TerminationListparameter. It also includes the ConferenceCallingIndicator parameter, indicating thatConference Calling is active for the call.g.
49、The Serving MSC stores the ConferenceCallingIndicator information, activatesconference calling, and provides treatment to the served MS as indicated in thefeatreq. In this case, the treatment is to apply feature confirmation.h. The Serving MSC extends the call using the call routing information in theTerminationList parameter (call-leg-2).i. MS-1 sends a flash request to the Serving MSC (i.e., presses the key).j. The Serving MSC connects the served MS, the held conferee and the new party into aconference call.k. MS-1 sends a Disconnect Request to the Serving MSC (i
