TIA-664-510-B-2007 Wireless Features Description Conference Calling (CC).pdf

上传人:feelhesitate105 文档编号:1060797 上传时间:2019-03-31 格式:PDF 页数:32 大小:3.61MB
下载 相关 举报
TIA-664-510-B-2007 Wireless Features Description Conference Calling (CC).pdf_第1页
第1页 / 共32页
TIA-664-510-B-2007 Wireless Features Description Conference Calling (CC).pdf_第2页
第2页 / 共32页
TIA-664-510-B-2007 Wireless Features Description Conference Calling (CC).pdf_第3页
第3页 / 共32页
TIA-664-510-B-2007 Wireless Features Description Conference Calling (CC).pdf_第4页
第4页 / 共32页
TIA-664-510-B-2007 Wireless Features Description Conference Calling (CC).pdf_第5页
第5页 / 共32页
点击查看更多>>
资源描述

1、 TIA-664.510-B (Revision of TIA-664.510-A) October 2007Wireless Features Description: Conference Calling (CC) ANSI/TIA-664.510-B-2007 APPROVED: OCTOBER 12, 2007 REAFFIRMED: JANUARY 24, 2013 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminatin

2、g 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 existence of such Standards and Publications shall not in

3、 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-TIA members, either domestically or internationally. Stan

4、dards 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 parties adopting the Standard or Publication. This Standar

5、d 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 applicability of regulatory limitations before its use.

6、 (From Project No. SP-3-4652.510-RV2-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 Document may be amended, modified or changed in the stand

7、ards 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 search or investigation for IPR. When IPR consisting o

8、f 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 to investigate or inquire into, the scope or validi

9、ty 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 non-discriminatory. TIA does not warrant or represent

10、 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 SSO”) engaged in the formulation, development or publi

11、cation 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 disclaims any duty or obligation to search or investiga

12、te 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 patent applications shall apply; and (iii) Informati

13、on 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 contents of the Document. TIA does not certify, inspect, t

14、est 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 ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS F

15、OR 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 WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY AP

16、PLICABLE 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 OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF

17、 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 CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE),

18、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 LIMITATIONS. TIA-664.510-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14

19、15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 510-i Contents Wireless Features Description: Conference Calling Contents List of Figures .ii List of Tablesiii Revision History.iv 1 Conference Calling (CC) 1 1.

20、1 Normal Procedures with Successful Outcome1 1.2 Exception Procedures or Unsuccessful Outcome .10 1.3 Alternative Procedures .12 1.4 Interactions with Other Wireless Services15 TIA-664.510-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 4

21、0 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 List of Figures 510-ii List of Figures Figure 1: Conference Calling State Diagram 9 TIA-664.510-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50

22、 51 52 53 54 55 56 57 58 59 60 510-iii List of Tables List of Tables Table 1: Idle State for Conference Calling 3 Table 2: 2-Way State for Conference Calling .4 Table 3: Adding On State for Conference Calling 4 Table 4: Conference Adding On State for Conference Calling .5 Table 5: Conference 2-Way S

23、tate for Conference Calling 7 Table 6: Alerting State for Conference Calling .8 Table 7: Conference State for Conference Calling8 Table 8: 2-Way State for ConferenceException 10 Table 9: Adding On State for Conference CallingException 11 Table 10: Adding On State for Conference CallingException 11 T

24、able 11: Conference 2-Way State for Conference CallingException12 Table 12: 2-Way State for Conference CallingAlternative13 Table 13: Conference 2-Way StateAlternative14 Table 14: Conference StateAlternative15 TIA-664.510-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 2

25、9 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Revision History 510-iv Revision History Revision Date Remarks IS-53, Revision 0 August 1991 Initial publication IS-53, Revision A May 1995 Updated publication ANSI/TIA/EIA-664, Revision 0 June 1996 Initia

26、l ANSI publication ANSI/TIA/EIA/664-510-A July 2000 Updated ANSI publication TIA-664.510-B September 2007 Updated publication TIA-664.510-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 5

27、7 58 59 60 510-1 Conference Calling (CC) 1 Conference Calling (CC) Conference Calling (CC) provides a subscriber with the ability to have a multi-connection call, i.e., a simultaneous communication between three or more parties (conferees). If any of the conferees to a conference call disconnects, t

28、he remaining parties remain connected. If the controlling subscriber of a conference call disconnects, the conference circuit and all conferees are released. CC remains in effect until the controlling subscriber disconnects. The controlling party may drop the conferee connected the shortest time wit

29、h the “drop last party” feature code. Any number of conferees may be dropped this way. The conference call terminates when no other conferee remains. CC does not impact a subscribers ability to originate calls. Applicability to Telecommunications Services CC is applicable to voice telecommunication

30、services. 1.1 Normal Procedures with Successful Outcome Authorization CC may be generally available or may be provided after prearrangement with the service provider. The subscription parameters may include the maximum number of conferees allowed in a subscribers conference call. The maximum number

31、of conferees in any conference call is also dependent upon the local service provider. Deauthorization CC may be withdrawn at the subscribers request or for administrative reasons. Registration CC has no registration. Deregistration CC has no deregistration. TIA-664.510-B 1 2 3 4 5 6 7 8 9 10 11 12

32、13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Conference Calling (CC) 510-2 Activation CC is activated upon authorization. Deactivation CC shall be deactivated upon deauthorization. Invocation Invocatio

33、n with a Call Setup Request CC may be invoked by an authorized subscriber concurrently with a call setup request with the following feature activation sequence: *FC + # + termination address + SEND . Alternatively: *FC + termination address + SEND is possible, if a fixed length invocation feature co

34、de is distinct from the drop last party invocation feature code. Invocation within a Two-Way Call CC may be invoked from within a two-way call by an authorized subscriber (with or without a preceding flash request) followed by one of the following feature activation sequences: *FC + SEND or *FC + #

35、+ termination address + SEND . Alternatively: *FC + termination address + SEND is possible, if a fixed length invocation feature code is distinct from the drop last party invocation feature code. Adding a Party to a Conference Call Once invoked, CC remains invoked until the controlling subscriber di

36、sconnects. Additional parties may be added with one of the following feature activation sequences: termination address + SEND or *FC + # + termination address + SEND . Alternatively: *FC + termination address + SEND TIA-664.510-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 2

37、7 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 510-3 Conference Calling (CC) is possible, if a fixed length invocation feature code is distinct from the drop last party invocation feature code. Drop Last Party Invocation within a Conference Call

38、The conferee most recently added to a conference call may be dropped from within the call or after placing the call on hold, by the controlling subscriber specifying the “drop last party” feature code (with or without a preceding flash request), as in: *FC0 + SEND . Alternatively: *FC + termination

39、address + SEND is possible, if a fixed length drop last party invocation feature code is distinct from the conference invocation feature code. Drop the conferee most recently added to the conference, if any, and play an optional warning tone to announce the departure of the conferee. The controlling

40、 subscriber shall be connected to the remaining conferees. If there are no confereesall conferees have already been dropped or disconnecteddisconnect the controlling subscriber and terminate the conference call. Normal Operation with Successful Outcome The following tables describe call party action

41、s and system reactions for CC. Table 1: Idle State for Conference Calling State Idle Condition The controlling subscriber is idle. XID Call Party Action System Reaction 1F 3 The controlling subscriber enters the CC invocation feature code string, as in: *FC + SEND . Apply prompting treatment. Go to

42、the conference adding on state. 1U 2 The controlling subscriber enters the CC invocation feature code and termination address, as in: *FC + # + termination address + SEND . Attempt to establish a connection to the termination address allowing the controlling subscriber to hear call progress tones an

43、d announcements. Go to the Conference 2-way state. TIA-664.510-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Conference Calling (CC) 510-4 Table 2: 2-Way State for Conferenc

44、e Calling State 2-way Condition The controlling subscriber is alerting the other party, or the controlling subscriber is in a two-way conversation with the other party. XID Call Party Action System Reaction 3S 2 The controlling subscriber presses the SEND key without digits while in a wo-way convers

45、ation. tPut the other party on hold. Apply prompting treatment. Go to the Adding on state. Table 3: Adding On State for Conference Calling State Adding on Condition One party is on hold. The system is waiting for the controlling subscriber to enter a feature code or the address of a third party. XID

46、 Call Party Action System Reaction 4F 1 The controlling subscriber enters the CC feature code string, as in: *FC + SEND . Apply prompting treatment. Go to the Conference adding on state. 4U 1 The controlling subscriber enters the CC feature code string with a call setup request, as in: *FC + # + ter

47、mination address + SEND . Attempt to establish a connection to the termination address allowing the controlling subscriber to hear call progress tones and announcements. Go to the Conference 2-way state. 4H 1 The held party disconnects. Release the held party. The voice channel may be released. Any

48、further action by the subscriber is treated as a new service request. Go to the Idle state. 4I 1 An incoming call arrives for the ontrolling subscriber. cApply busy treatment to the calling party. emain in the Adding on state. RTIA-664.510-B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 2

49、3 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 510-5 Conference Calling (CC) Table 4: Conference Adding On State for Conference Calling State Conference adding on Condition Zero or more conferees on hold and are allowed to converse. The system is waiting for the controlling subscriber to enter the address of a new conferee. XID Call Party Action System Reaction 9S1 The controlling subscriber presses the SEND key without digits and at least one conferee is on hold. Reconnect the held conferee(s) and the con

展开阅读全文
相关资源
猜你喜欢
相关搜索

当前位置:首页 > 标准规范 > 国际标准 > 其他

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1