WO2008113236A1 - Méthode d'interruption anormale d'un appel basé sur un tcs - Google Patents

Méthode d'interruption anormale d'un appel basé sur un tcs Download PDF

Info

Publication number
WO2008113236A1
WO2008113236A1 PCT/CN2007/003928 CN2007003928W WO2008113236A1 WO 2008113236 A1 WO2008113236 A1 WO 2008113236A1 CN 2007003928 W CN2007003928 W CN 2007003928W WO 2008113236 A1 WO2008113236 A1 WO 2008113236A1
Authority
WO
WIPO (PCT)
Prior art keywords
state
call
tcs
calling
called
Prior art date
Application number
PCT/CN2007/003928
Other languages
English (en)
French (fr)
Inventor
Shuliang Lin
Original Assignee
Zte Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zte Corporation filed Critical Zte Corporation
Publication of WO2008113236A1 publication Critical patent/WO2008113236A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the present invention relates to the field of short-range wireless communications, and in particular to Bluetooth technology. Background technique
  • Bluetooth technology is an open standard, short-range, low-cost wireless communication technology. It can wirelessly connect various communication devices. Up to seven other Bluetooth devices can be connected to one device. It works in the 2.4GHz ISM free frequency band with a transmission distance of 10cm ⁇ 10m. If you increase the power, you can reach a transmission distance of 100m. The technology consumes less power, is less harmful to humans, and supports multiple application models. In recent years, the integration of Bluetooth technology on mobile terminals has become increasingly popular. Nokia, Motorola, Sony Ericsson, LG, ZTE and other major mobile device providers have launched a variety of Bluetooth mobile terminals. At present, the number of mobile terminals carrying Bluetooth modules in the world has reached several hundred million, and it is increasing at a rate of tens of millions every year.
  • Bluetooth cordless telephone gateway which is a Cordless Telephony Profile (CTP) developed by the Bluetooth Special Interest Group (SIG), so it is called a CTP gateway.
  • CTP gateway can access the fixed telephone network (PSTN), can also access any other type of telephone communication network, and allows the joining of up to seven communication terminals with Bluetooth wireless communication capabilities.
  • the communication terminal can be a Bluetooth model mobile phone or other communication device, such as a Bluetooth single mode cordless phone.
  • the CTP gateway and the CTP Bluetooth terminal follow the Bluetooth TCF specification (Bluetooth Telephony Control Protocol Specification) established by the SIG.
  • the Bluetooth TCS specification specifies the cooperation requirements that both the gateway and the Bluetooth terminal need to follow to ensure different
  • the CTP gateway and CTP Bluetooth terminal developed by the manufacturer can communicate with each other normally to complete the call flow.
  • the call creation process (referred to from the TCS call flow specified by the TCS specification of the SIG) as shown in Figure 1 of the SIG's TCS specification, is as follows:
  • Step 1 The calling side (Outgoing Side) sends a TCS Call Control (hereinafter referred to as the CO SETUP message to the called side (Incoming Side), and the ⁇ 303 timer is turned on, and enters Call initiated (l) state; After the called side (Incoming Side) receives the TCS CC SETUP message, the state transitions to Call Present (6);
  • Step 2 The Incoming Side starts the T302 timer, sends a TCS CC SETUP ACKNOWLEDGE message to the calling side (Outgoing Side), the state transitions to Overlap receiving (25), and the calling side (Outgoing Side) receives the TCS CC.
  • SETUP ACKNOWLEDGE message turn off the T303 timer, turn on the T304 timer, and the state transitions to Overlap sending(2); this step is an optional step;
  • Step 3 The outgoing side sends a TCS CC INFORMATION message to the called side (Incoming Side), and then re-enables the T304 timer. After the called side (Incoming Side) receives the TCS CC INFORMATION message, the T302 timer is restarted. ; This step is optional and can be repeated multiple times;
  • Step 4 The Incoming Side sends a TCS CC CALL PROCEEDING message to the calling side (Outgoing Side), turns off the T302 timer, and the state transitions to Incoming call proceeding ⁇ ; the calling side (Outgoing Side) receives the TCS CC CALL.
  • the T304 timer is turned off, and the T310 timer is turned on; this step is an optional step;
  • Step 5 The Incoming Side sends a TCS CC ALERTING message to the calling side (Outgoing Side), and the state moves to Call received (7);
  • the calling side (Outgoing Side) closes the T310 after receiving the TCS CC ALERTING message.
  • Timer turn on the T301 timer; this step is an optional step;
  • Step 6 The Incoming Side sends a TCS CC CONNECT message to the outgoing side (Outgoing Side), starts the T313 timer, and the state transitions to Connect request (8); Step 7.
  • the calling side receives After the TCS CC CONNECT message, the T301 timer is turned off if it is already enabled, the status is changed to ACTIVE(IO), the TCS CC CONNECT ACKNOWLEDGE message is sent to the called side (Incoming Side); and the called side (Incoming Side) receives the TCS CC. After the CONNECT ACKNOWLEDGE message, the T313 timer is turned off and the state is migrated to ACTIVE(10). At this point, the calling party successfully establishes a call.
  • the TCS protocol has a collaboration problem that the protocol writer did not consider.
  • the specific situation is: The call state is Overlap receiving (25), Incoming call proceeding (9), Call. Received (7).
  • Connect request (8) only the RELEASE message can be accepted. Only the call status is Call initiated (1), Call present (6), Release request (19) can accept the TCS CC RELEASE COMPLETE message.
  • This process design will create a problem: When the called party receives the TCS CC Setup message, it can directly go to the next message transmission process (the next message can be: SETUP ACKNOWLEDGE, CALL PROCEEDING. ALERTING.
  • the technical problem to be solved by the present invention is to provide a method for aborting a call based on TCS, which solves the problem that the call cannot be suspended when the calling party is in a call initiation state due to a defect in the TCS call flow in the prior art.
  • the method for aborting a call based on the TCS according to the present invention wherein the abnormal abort refers to a call suspension when the calling side is in a call initiation state call initiated in the TCS, and includes the following processing steps:
  • the receiving side After receiving the disconnection request message, the receiving side sends a connection disconnected message RELEASE COMPLETE to the originating side, and changes the state of the receiving side to the idle state Null;
  • the originating side After the originating side receives the disconnected message, the originating side is changed to the idle state.
  • the receiving side refers to the called party.
  • the current state is the TCS calling party call originating state Call initiated.
  • the receiving side refers to the calling party, and when the originating side, that is, the called side encounters an abnormality, the receiving side, that is, the calling side, the state at this time is the TCS calling party.
  • the calling side receives the RELEASE COMPLETE message sent by the called party, and moves the calling side state to the idle state.
  • the calling side initiates the RELEASE message to the called side, and starts a timer for monitoring the duration of receiving the RELEASE COMPLETE message sent by the called side.
  • the called side receives the RELEASE COMPLETE message sent by the calling side, and moves the state of the called side to the idle state.
  • step 2.1 when the called side encounters an abnormality, it is in a TCS call state. Call present
  • the called side initiates the RELEASE message to the calling side, and starts a timer for monitoring the receipt of the RELEASE sent by the calling side.
  • the length of the COMPLETE message The length of the COMPLETE message.
  • the second handshake method adopted in the traditional strict call flow design is not adopted because the performance of the air interface to send and receive messages is not high enough.
  • the method of the present invention can make up for the defect that the TCS protocol can initiate the call suspension process when the TCS call state is Call initiated (1), and can effectively improve the fault tolerance of both the calling party and the called party of the voice call.
  • FIG. 1 is a flow chart of a TCS call creation message in the existing SIG TCS specification
  • FIG. 2 is a flowchart of a process for aborting a call abort by a calling party on a TCS according to a preferred embodiment of the present invention
  • FIG. 3 is a flow chart of a process for aborting a call from a called side of a TCS according to a preferred embodiment of the present invention.
  • the essence of the present invention is to send a disconnection request message to the opposite end of the side that initiates the abort (referring to the call suspension when the calling side is in the call initiated (1) state in the TCS), and causes the other side to send feedback to the originating side.
  • the disconnected message is connected; the state transitions of the initiator and the receiver are standardized, so that the abnormal abort call can be handled. That is, for the current process defects, the process of aborting the call by the outgoing side of the outgoing party and the process of aborting the call by the called side (Incoming Side) are improved to improve the fault tolerance of both parties.
  • the method details are as follows:
  • Step 1 When the calling party is in the TCS call state Call initiated (1), if an exception is encountered, to initiate the call flow, the TCS CC RELEASE message must be initiated to enter the TCS call state Release request (19);
  • Step 2 When the called party receives the TCS CC RELEASE message sent by the calling party, if the status has not been migrated and is still in the Call present (6) state, the TCS CC RELEASE COMPLETE message is directly sent to the calling side and migrated. Status to TCS call state NULL(O); If the state has been migrated to one of the states of Overlap receiving (25), Incoming call proceeding (9) > Call received (7), Connect request (8), etc., the SIG TCS specification has specified Should support TCS Processing of CC RELEASE messages.
  • Step 3 The calling side receives the TCS CC RELEASE COMPLETE message sent by the called party. In this case, it is in the Release request (19) state. According to the SIG TCS specification, the TCS call state NULL (0) should be returned.
  • Step 1 When the called side is in the TCS call state Call present (6), if an abnormality is encountered, to initiate the call flow, the TCS CC RELEASE message must be initiated to enter the TCS call status Release request (19);
  • Step 2 When the calling side receives the TCS CC RELEASE message sent by the called party, if the status has not been migrated and is still in the Call initiated (l) state, the TCS CC RELEASE COMPLETE message is directly sent to the called side, and the status is migrated.
  • the TCS call state NULL(O); if the state has been migrated to one of the states of Overlap sending(2), Outgoing call proceeding(3)>Call delivered(4) (after performing some optional business processes, the calling party The state may be migrated to Outgoing call proceeding (3) or Call delivered (4), and the called party is still in the state Call present (6).
  • the state is migrated to Outgoing call proceeding ( 3), when the calling party sends a TCS Answer message, the state is migrated to Call delivered(4)), and the SIG TCS specification has specified that the handling of the TCS CC RELEASE message should be supported.
  • Step 3 The called party receives the TCS CC RELEASE COMPLETE message sent by the calling party. In this case, it is in the Release request (19) state. According to the SIG TCS specification, the TCS call state NULL (0) should be returned.
  • Figure 2 depicts the solution to the abortion process initiated by the caller of the process A TCS on the calling side
  • the outgoing side sends a TCS CC SETUP message to the called side to initiate a call (S401);
  • the calling party sends the TCS CC SETUP
  • the optional processes S402, S403, S404, and S405 specified by the SIG TCS specification the TCS status is still Call initiated (1), which needs to be initiated due to internal reasons.
  • the calling side must send a TCS CC RELEASE message to the called side, enable the T308 timer, and migrate the status to the Release request (19).
  • the T308 timer is in the Release request (19) state, waiting for the RELEASE COMPLETE timer, the timer.
  • duration (refer to the SIG TCS specification), start call release (S406); if the calling and called parties perform one or more steps of the optional processes S402, S403, S404, S405 specified by the SIG TCS specification, the calling party At this time, the TCS call state has been correspondingly transferred to one of the states of Overlap sending (2), Outgoing call proceeding (3) > Call delivered (4) (correspondence reference SIG TCS specification), if the calling party is due to internal reasons Want to initiate a release, according to SIG TCS regulations;
  • the TCS call state of the called side is still in the Call present (6) state.
  • the calling side receives the TCS CC RELEASE COMPLETE message, and is in the Release request (19) state.
  • the TCS call state is returned to NULL(O).
  • FIG. 3 illustrates the improvement of the abortion process initiated by the solution in this paper to the called side of the process B TCS;
  • the outgoing side sends a TCS CC SETUP message to the called side to initiate a call (S501);
  • the TCS call state of the called party is still in the Call present (6) state.
  • the called party must send a TCS CC RELEASE message to the called party.
  • the T308 timer is enabled, and the migration status is released to Release request (19) (the T308 timer is waiting for the RELEASE COMPLETE timer in the Release request (19) state, and the specific definition of the timer duration is referred to the SIG TCS specification), and the call is released.
  • the TCS status is still Call initiated (1), and the calling side receives the TCS.
  • the CC RELEASE message directly sends the TCS CC RELEASE COMPLETE message to the called side, and migrates the state to the TCS call state NULL(O) (S507); if the calling party and the called party perform the optional processes S502, S503 specified by the SIG TCS specification, In one or more steps of S504 and S505, the calling party's TCS call state has been migrated to one of the states of Overlap sending (2), Outgoing call proceeding (3), and Call delivered (4) (correspondence reference SIG)
  • the TCS specification at this time, the calling side receives the TCS CC RELEASE message, and completes the processing of the TCS CC RELEASE message according to the SIG TCS specification (the new processing of the above-mentioned Call initiated (1) state in this step);
  • the called side receives the TCS CC RELEASE COMPLETE message, and is in the Release request (19) state. According to the SIG TCS specification, the TCS call state is returned to NULL(O). At this point, the called side actively initiates the abnormal removal call flow.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Description

一种基于 TCS的异常中止呼叫方法
技术领域
本发明涉及短距离无线通信领域， 具体来说， 涉及蓝牙技术。 背景技术
蓝牙技术是一种开放标准的， 短距离， 低成本的无线通信技术。 它可以 将各种通信设备用无线方式联接起来。一个设备可以连接多达七台其它的蓝 牙设备。 它工作在 2.4GHz ISM免费频段， 传输距离为 10cm ~ 10m, 如果增 加功率便可达到 100m的传输距离。 该技术功耗低、 对人体危害小， 并支持 多种应用模型。近几年移动终端上集成蓝牙技术日趋流行， Nokia、 Motorola. 索尼-爱立信、 LG、 ZTE等各大移动设备供应商纷纷推出多款的蓝牙移动终 端。 目前全球携带蓝牙模块的移动终端数量已达到几亿台， 并且每年以成百 上千万的速度递增。
目前蓝牙技术一个重要的应用模型是蓝牙无绳电话网关，应用的是蓝牙 特别兴趣小组 （Special Interest Group, 简称 SIG ) 制订的无绳电话协议 ( Cordless Telephony Profile, 简称 CTP ) ， 因此称之为 CTP网关。 CTP网 关可以接入固定电话网（PSTN )， 也可以接入任何其它类型的电话通信网， 并允许多达七部具有蓝牙无线通信能力的通讯终端的加入。通讯终端可以是 蓝牙欢模移动电话， 也可以是其它的通讯设备， 如蓝牙单模无绳电话。 CTP 网关和 CTP蓝牙终端遵循 SIG制定的蓝牙 TCS规范 (Bluetooth Telephony Control Specification VI.1 , 蓝牙电话控制协议规范）， 蓝牙 TCS规范中规定 了网关和蓝牙终端双方需要遵循的协作性要求，来保证不同厂商开发出来的 CTP网关和 CTP蓝牙终端能够正常互相通信， 完成呼叫流程。
如图 1所示 SIG的 TCS规范规定的呼叫创建流程（引用自 SIG的 TCS 规范规定的 TCS呼叫流程） ， 具体步骤如下：
步骤一、 主叫侧 ( Outgoing Side )发送 TCS Call Control (后文均简称 CO SETUP消息给被叫侧（Incoming Side ) , 并开启 Τ303定时器， 进入 Call initiated(l)状态； 被叫侧（ Incoming Side )收到 TCS CC SETUP消息后， 状态迁移至 Call Present(6);
步骤二、被叫侧（ Incoming Side )开启 T302定时器，发送 TCS CC SETUP ACKNOWLEDGE 消息给主叫侧 （Outgoing Side ) , 状态迁移至 Overlap receiving(25);主叫侧（ Outgoing Side )收到 TCS CC SETUP ACKNOWLEDGE 消息，关闭 T303定时器，开启 T304定时器，状态迁移至 Overlap sending(2); 此步骤为可选步骤；
步骤三、 主叫侧（ Outgoing Side )发送 TCS CC INFORMATION消息给 被叫侧（ Incoming Side ) ， 重新开启 T304定时器； 被叫侧 （ Incoming Side ) 收到 TCS CC INFORMATION消息后， 重新开启 T302定时器； 此步骤为可 选步骤， 且可重复多次；
步骤四、 被叫侧（ Incoming Side )发送 TCS CC CALL PROCEEDING消 息给主叫側（Outgoing Side ) , 关闭 T302定时器， 状态迁移到 Incoming call proceeding^; 主叫侧 （ Outgoing Side )收到 TCS CC CALL PROCEEDING 消息后， 关闭 T304定时器， 开启 T310定时器； 此步骤为可选步骤；
步骤五、 被叫侧（ Incoming Side )发送 TCS CC ALERTING消息给主叫 侧（ Outgoing Side )， 状态迁移到 Call received (7); 主叫侧（ Outgoing Side ) 收到 TCS CC ALERTING消息后， 关闭 T310定时器， 开启 T301定时器； 此步骤为可选步骤；
步骤六、 被叫側 （ Incoming Side )发送 TCS CC CONNECT消息给主叫 侧 ( Outgoing Side ) ， 开启 T313定时器， 状态迁移到 Connect request(8); 步骤七、主叫侧（ Outgoing Side )收到 TCS CC CONNECT消息后， T301 定时器如果已经开启的话则关闭， 迁移状态至 ACTIVE(IO), 发送 TCS CC CONNECT ACKNOWLEDGE 消息给被叫側 （Incoming Side ) ； 被叫侧 ( Incoming Side )收到 TCS CC CONNECT ACKNOWLEDGE消息后， 关闭 T313定时器， 迁移状态至 ACTIVE(10)。 至此呼叫双方成功建立通话。
上述步骤中所述的 TCS CC呼叫控制信令的具体含义请参考表 1。
表 1 TCS呼叫控制信令表 (Table of TCS Call Control Messages) 序号 TCS呼叫控制信令名称 含义
1 ALERTING 被叫侧振铃消息
2 CALL PROCEEDING 被叫侧呼叫进展流程消息
3 CONNECT 被叫侧用户摘机消息
4 CONNECT ACKNOWLEDGE 主叫侧摘机应答消息
5 PROGRESS 被叫侧呼叫进展消息
6 SETUP 主叫侧呼出消息
7 SETUP ACKNOWLEDGE 被叫侧呼出应答消息
8 DISCONNECT 一侧拆除连接消息（主被叫侧均可主动挂机 )
9 RELEASE 断开连接请求消息
10 RELEASE COMPLETE 连接已断开消息
11 INFORMATION 呼叫附带信息消息（如来电显示等）
上述步骤中所述的 TCS CC呼叫状态的具体含义请参考表 2。
表 2 TCS CC呼叫状态表 (Table of TCS Call Status Messages)
Figure imgf000005_0001
但是， TCS协议存在协议编写者没有考虑到的一个协作性问题， 具体情 况为： 在呼叫状态为 Overlap receiving(25)、 Incoming call proceeding(9)、 Call received (7). Connect request(8)时， 仅能接受 RELEASE消息， 只有呼叫状 态为 Call initiated (1) 、 Call present (6) 、 Release request (19)三者时才能接 受 TCS CC RELEASE COMPLETE消息。 这个流程设计将产生一个问题： 被 叫一方在收到了 TCS CC Setup消息时， 均可以直接进入下一条消息的发送 处理（下一条消息可以是： SETUP ACKNOWLEDGE, CALL PROCEEDING. ALERTING. CONNECT )， 消息发送后迁移状态至下一状态（下一状态有： Overlap receiving(25)、 Incoming call proceeding(9)> Call received (7) Connect request(8) ) , 但是主叫一方尚未收到被叫方发送的这一消息时， 其状态仍然 为 Call initiated (1)， 此时主叫一方用户挂机， 发送给对方的消息为 TCS CC RELEASE COMPLETE 消息， 而被叫一方的呼叫状态已经迁移至下一状态 ( 25或 9或 7或 8 )，已经不能处理 TCS CC RELEASE COMPLETE消息了， 导致被叫侧的呼叫无法释放。 因此， 需要一个方法来弥补 TCS呼叫流程的 这个缺陷。 发明内容
本发明所要解决的技术问题是提出一种基于 TCS的异常中止呼叫方法， 以解决现有技术中由于 TCS呼叫流程存在缺陷， 导致在主叫側处于呼叫发 起状态时， 无法中止呼叫的问题。
本发明提出的基于 TCS的异常中止呼叫方法， 所述异常中止是指 TCS 中主叫侧处于呼叫发起状态 call initiated时的呼叫中止，包括以下处理步骤：
1 )当发起侧遇到异常， 向接收侧发起断开连接请求消息 RELEASE, 并 将发起侧的状态转入断开连接请求状态 Release request;
2 )接收侧收到断开连接请求消息后， 向发起侧发送连接已断开消息 RELEASE COMPLETE, 并将接收侧的状态改为空闲状态 Null;
3 )发起侧收到连接已断开消息后， 将发起侧的状态改为空闲状态。
进一步地， 所述发起侧为主叫时， 所述接收侧指被叫， 当所述发起侧即 主叫側遇到异常时，其此时的状态为 TCS主叫侧呼叫发起状态 Call initiated。 进一步地， 所述发起侧为被叫时， 所述接收侧指主叫， 当所述发起侧即 被叫侧遇到异常时， 所述接收侧即主叫侧此时的状态为 TCS主叫侧呼叫发 起状态 Call initiated。
进一步地， 当发起侧异常中止请求的为主叫侧时， 具体包括以下处理步 骤：
1.1 )主叫侧处于 TCS呼叫状态 Call initiated 时， 如果遇到异常， 欲主 动中止呼叫流程， 向被叫侧发起所述 RELEASE消息， 并使主叫侧进入所述 Release request状态 ^
1.2 )被叫侧收到主叫侧发来的所述 RELEASE消息时，被叫侧发送所述 RELEASE COMPLETE消息给主叫側， 并将被叫側的状态迁移至空闲状态；
1.3 )主叫侧收到被叫侧发来的所述 RELEASE COMPLETE消息， 将主 叫側状态迁移至空闲状态。
进一步地， 所述步骤 1.1 ) 中主叫側向被叫側发起所述 RELEASE消息 的同时开启一个定时器， 用于监控收到被叫側发来的所述 RELEASE COMPLETE消息的时长。
进一步地， 当发起侧异常中止请求的为被叫侧时， 具体包括以下处理步 骤：
2.1 )主叫侧处于 TCS呼叫状态 Call initiated 时， 此时被叫侧如果遇到 异常， 欲主动中止呼叫流程， 向主叫侧发起所述 RELEASE消息， 并使主叫 侧进入所述 Release request状态；
2.2 )主叫侧收到被叫侧发来的所述 RELEASE消息时，主叫侧发送所述 RELEASE COMPLETE消息给被叫侧， 并将主叫侧的状态迁移至空闲状态；
2.3 )被叫侧收到主叫側发来的所述 RELEASE COMPLETE消息， 将被 叫側的状态迁移至空闲状态。
进一步地， 在所述步骤 2.1 ) 中， 所述被叫侧遇到异常时正处于 TCS呼 叫状态 Call present
进一步地， 所述步骤 2.1 ) 中被叫側向主叫侧发起所述 RELEASE消息 的同时开启一个定时器， 用于监控收到主叫侧发来的所述 RELEASE COMPLETE消息的时长。
现有技术中由于空口收发消息性能不够高而没有采用传统严格的呼叫 流程设计中采取的二次握手方法。 釆用本发明所述方法， 可以弥补 TCS协 议在 TCS呼叫状态 Call initiated(l)时发起中止呼叫流程而无法处理的缺陷， 并且能有效提高语音呼叫的主被叫双方的容错能力。 附图概述
图 1为现有 SIG TCS规范中的 TCS呼叫创建消息的流程图；
图 2为本发明优选实施例中 TCS主叫侧发起呼叫异常中止处理流程图； 图 3为本发明优选实施例中 TCS被叫侧发起呼叫异常中止流程流程图。
本发明的较佳实施方式
本发明的实质是让发起异常中止（指 TCS中主叫侧处于 call initiated(l) 状态时的呼叫中止）的一側向对端发送断开连接请求消息， 并使另一側向发 起侧反馈连接已断开消息； 并将发起端和接收端的状态迁移进行规范， 使得 能够处理异常中止呼叫。即针对目前流程缺陷，完善主叫一侧 (Outgoing Side) 异常中止呼叫的流程， 和被叫一侧 (Incoming Side)异常中止呼叫的流程， 来 提高呼叫双方的容错能力， 方法细节如下：
流程 A 主叫一侧主动中止呼叫的完善步骤：
步骤一、主叫一側处于 TCS呼叫状态 Call initiated (1)时，如果遇到异常， 欲主动中止呼叫流程， 必须发起 TCS CC RELEASE消息， 进入 TCS呼叫状 态 Release request (19);
步骤二、 被叫一侧收到主叫侧发来的 TCS CC RELEASE消息时， 如果 状态尚未迁移， 还处于 Call present(6)状态， 则直接发送 TCS CC RELEASE COMPLETE消息给主叫侧， 并迁移状态至 TCS呼叫状态 NULL(O); 如果状 态已经迁移至 Overlap receiving(25)、 Incoming call proceeding(9) > Call received (7)、 Connect request(8)等状态之一， SIG TCS规范已经规定了应当支持 TCS CC RELEASE消息的处理。
步骤三、 主叫側收到被叫侧发来的 TCS CC RELEASE COMPLETE消 息， 此时处于 Release request (19)状态， 根据 SIG TCS规范， 应该退回 TCS 呼叫状态 NULL(0)。
流程 B被叫一侧主动中止呼叫的完善步骤：
步骤一、 被叫侧处于 TCS呼叫状态 Call present(6)时， 如果遇到异常， 欲主动中止呼叫流程， 必须发起 TCS CC RELEASE消息， 进入 TCS呼叫状 态 Release request (19);
步骤二、 主叫侧收到被叫侧发来的 TCS CC RELEASE消息时， 如果状 态尚未迁移， 还处于 Call initiated(l)状态， 则直接发送 TCS CC RELEASE COMPLETE消息给被叫側， 并迁移状态至 TCS呼叫状态 NULL(O); 如果状 态已经迁移至 Overlap sending(2)、 Outgoing call proceeding(3)>Call delivered(4) 等状态之一 （在执行某些可选业务流程之后， 主叫的状态可能会迁移到 Outgoing call proceeding(3)或 Call delivered(4) , 而被叫仍处于状态 Call present(6), 如当主叫方发出 TCS Call Proceeding 消息后， 状态则迁移到 Outgoing call proceeding(3), 当主叫方发出 TCS Answer消息后， 状态迁移到 Call delivered(4) ) ， SIG TCS规范已经规定了应当支持 TCS CC RELEASE 消息的处理。
步骤三、 被叫侧收到主叫侧发来的 TCS CC RELEASE COMPLETE消 息， 此时处于 Release request (19)状态， 根据 SIG TCS规范， 应该退回 TCS 呼叫状态 NULL(0)。
下面结合图 2、图 3对上述技术解决方案的实施例作进一步的详细描述， 应当理解，此处所描述的优选实施例仅用于说明和解释本发明， 并不用于限 定本发明。 在附图中：
图 2描述了本文的解决方案对流程 A TCS主叫侧发起呼叫异常中止流 程的完善；
如图 2所示，主叫侧 (Outgoing Side)发送 TCS CC SETUP消息给被叫側， 发起呼叫 （ S401 ) ； 主叫側发出 TCS CC SETUP后， 如果主被叫双方没有执行 SIG TCS规 范规定的可选流程 S402、 S403、 S404、 S405,此时 TCS状态仍为 Call initiated (1)， 由于内部原因而需要发起释放时， 主叫侧必须发送 TCS CC RELEASE 消息给被叫側， 开启 T308定时器， 迁移状态至 Release request (19) ( T308 定时器为 Release request (19)状态下等待 RELEASE COMPLETE定时器， 定 时器时长等具体定义参考 SIG TCS规范） ， 开始呼叫释放 ( S406 ) ； 如果 主被叫双方执行了 SIG TCS规范规定的可选流程 S402、 S403、 S404、 S405 的一个或者多个步骤， 则主叫方此时的 TCS 呼叫状态已经对应迁移至 Overlap sending(2)、 Outgoing call proceeding(3)> Call delivered (4)等状态之一 (对应关系参考 SIG TCS规范） ， 此时如果主叫方由于内部原因想发起释 放， 根据 SIG TCS规范规定处理即可；
被叫側收到 TCS CC RELEASE消息时， 如果主被叫双方没有执行 SIG TCS规范规定的可选流程 S402、 S403、 S404、 S405, 被叫侧的 TCS呼叫状 态仍处于 Call present(6)状态，直接发送 TCS CC RELEASE COMPLETE消息 给主叫侧， 并迁移状态至 TCS呼叫状态 NULL(O) ( S407 ) ； 如果主被叫双 方执行了 SIG TCS规范规定的可选流程 S402、 S403、 S404、 S405的一个或 者多个步骤， 则被叫方此时的 TCS 呼叫状态已经迁移至 Overlap receiving(25)、 Incoming call proceeding(9)^ Call received (7), Connect request(8) 等状态之一（对应关系参考 SIG TCS规范） ， 根据 SIG TCS规范规定完成 TCS CC RELEASE消息的处理即可 （同本步骤的上述 Call present(6)状态的 新处理）；
主叫侧收到 TCS CC RELEASE COMPLETE 消息， 此时处于 Release request (19)状态， 根据 SIG TCS规范， 退回 TCS呼叫状态 NULL(O), 至此 流程 A主叫侧主动发起异常拆除呼叫的流程结束。
图 3描述了本文的解决方案对流程 B TCS被叫侧发起呼叫异常中止流 程的完善；
如图所示， 主叫侧 (Outgoing Side)发送 TCS CC SETUP消息给被叫侧， 发起呼叫 （S501 ) ；
被叫侧收到 TCS CC SETUP消息时，如果主被叫双方没有执行 SIG TCS 规范规定的可选流程 S502、 S503, S504、 S505, 被叫側的 TCS呼叫状态仍 处于 Call present(6)状态， 此时内部原因而需要发起释放时， 被叫侧必须发 送 TCS CC RELEASE消息给主叫侧，开启 T308定时器，迁移状态至 Release request (19) ( T308 定时器为 Release request (19)状态下等待 RELEASE COMPLETE定时器， 定时器时长等具体定义参考 SIG TCS规范） ， 开始呼 叫释放（S506 );如果主被叫双方执行了 SIG TCS规范规定的可选流程 S502、 S503、 S504、 S505的一个或者多个步骤， 则被叫方此时的 TCS呼叫状态已 经迁移至 Overlap receiving(25)、 Incoming call proceeding(9)、 Call received (7)、 Connect request(8)等状态之一（对应关系参考 SIG TCS规范） ， 此时如果被 叫方由于内部原因想发起释放， 根据 SIG TCS规范规定处理即可；
主叫侧发出 TCS CC SETUP后， 如果主被叫双方没有执行 SIG TCS规 范规定的可选流程 S502、 S503、 S504、 S505， TCS状态仍为 Call initiated (1)， 此时主叫側收到 TCS CC RELEASE 消息， 直接发送 TCS CC RELEASE COMPLETE消息给被叫側，并迁移状态至 TCS呼叫状态 NULL(O) ( S507 )； 如果主被叫双方执行了 SIG TCS规范规定的可选流程 S502、 S503、 S504、 S505 的一个或者多个步骤， 则主叫方此时的 TCS 呼叫状态已经迁移至 Overlap sending(2)、 Outgoing call proceeding(3)、 Call delivered (4)等状态之一 (对应关系参考 SIG TCS规范），此时主叫侧收到 TCS CC RELEASE消息， 根据 SIG TCS规范规定完成 TCS CC RELEASE消息的处理即可（同本步骤 的上述 Call initiated (1)状态的新处理） ；
被叫侧收到 TCS CC RELEASE COMPLETE 消息， 此时处于 Release request (19)状态， 根据 SIG TCS规范， 退回 TCS呼叫状态 NULL(O), 至此 流程 B 被叫侧主动发起异常拆除呼叫流程结束。
以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本 领域的技术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和 原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护 范围之内。 工业实用性
采用本发明所述方法， 可以弥补 TCS 协议在 TCS 呼叫状态 Call initiated 1 )时发起中止呼叫流程而无法处理的缺陷， 有效地提高了语音呼叫 的主被叫双方的容错能力。

Claims

权 利 要 求 书
1、 一种基于 TCS的异常中止呼叫方法， 所述异常中止是指 TCS中主 叫侧处于呼叫发起状态 call initiated时的呼叫中止， 其特征在于， 所述方法 包括以下处理步骤：
1 )当发起侧遇到异常， 向接收侧发起断开连接请求消息 RELEASE, 并 将发起侧的状态转入断开连接请求状态 Release request;
2 )接收侧收到断开连接请求消息后， 向发起侧发送连接已断开消息 RELEASE COMPLETE, 并将接收侧的状态改为空闲状态 Null;
3 )发起侧收到连接已断开消息后， 将发起侧的状态改为空闲状态。 2、 根据权利要求 1所述的方法， 其特征在于，
所述发起侧为主叫时， 所述接收侧指被叫， 当所述发起侧即主叫侧遇到 异常时， 其此时的状态为 TCS主叫側呼叫发起状态 Call initiated。
3、 根据权利要求 1所述的方法， 其特征在于，
所述发起側为被叫时， 所述接收侧指主叫， 当所述发起侧即被叫侧遇到 异常时， 所述接收侧即主叫侧此时的状态为 TCS主叫侧呼叫发起状态 Call initiated。
4、 根据权利要求 1或 2所述的方法， 其特征在于， 当发起侧异常中止 请求的为主叫侧时， 所述方法具体包括以下处理步骤：
1.1 )主叫側处于 TCS呼叫状态 Call initiated 时， 如果遇到异常， 欲主 动中止呼叫流程， 向被叫侧发起所述 RELEASE消息， 并使主叫侧进入所述 Release request状态 ^
1.2 )被叫侧收到主叫侧发来的所述 RELEASE消息时，被叫侧发送所述 RELEASE COMPLETE消息给主叫侧， 并将被叫侧的状态迁移至空闲状态；
1.3 )主叫侧收到被叫侧发来的所述 RELEASE COMPLETE消息， 将主 叫侧状态迁移至空闲状态。
5、 根据权利要求 4所述的方法， 其特征在于， 所述步骤 U )中主叫侧 向被叫侧发起所述 RELEASE消息的同时开启一个定时器， 用于监控收到被 叫侧发来的所述 RELEASE COMPLETE消息的时长。
6、 根据权利要求 1或 3所述的方法， 其特征在于， 当发起侧异常中止 请求的为被叫侧时， 所述方法具体包括以下处理步骤：
2.1 )主叫侧处于 TCS呼叫状态 Call initiated 时， 此时被叫侧如果遇到 异常， 欲主动中止呼叫流程， 向主叫侧发起所述 RELEASE消息， 并使主叫 侧进入所述 Release request状态；
2.2 )主叫侧收到被叫侧发来的所述 RELEASE消息时， 主叫侧发送所述 RELEASE COMPLETE消息给被叫侧， 并将主叫側的状态迁移至空闲状态； 2.3 )被叫侧收到主叫侧发来的所述 RELEASE COMPLETE消息， 将被 叫侧的状态迁移至空闲状态。
7、 根据权利要求 6所述的方法， 其特征在于， 在所述步骤 2.1 )中， 所 述被叫侧遇到异常时正处于 TCS呼叫状态 Call present。
8、 根据权利要求 6所述的方法， 其特征在于， 所述步骤 2.1 )中被叫侧 向主叫侧发起所述 RELEASE消息的同时开启一个定时器， 用于监控收到主 叫侧发来的所述 RELEASE COMPLETE消息的时长。
PCT/CN2007/003928 2007-03-20 2007-12-29 Méthode d'interruption anormale d'un appel basé sur un tcs WO2008113236A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710073602.X 2007-03-20
CN200710073602XA CN101076188B (zh) 2007-03-20 2007-03-20 一种基于tcs的异常中止呼叫方法

Publications (1)

Publication Number Publication Date
WO2008113236A1 true WO2008113236A1 (fr) 2008-09-25

Family

ID=38976960

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/003928 WO2008113236A1 (fr) 2007-03-20 2007-12-29 Méthode d'interruption anormale d'un appel basé sur un tcs

Country Status (2)

Country Link
CN (1) CN101076188B (zh)
WO (1) WO2008113236A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101076188B (zh) * 2007-03-20 2013-01-16 中兴通讯股份有限公司 一种基于tcs的异常中止呼叫方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1471314A (zh) * 2002-07-26 2004-01-28 华为技术有限公司 会议电视系统中断线重呼方法
CN1794867A (zh) * 2005-06-30 2006-06-28 华为技术有限公司 多播业务中停止用户会话的方法
CN1798447A (zh) * 2004-12-28 2006-07-05 乐金电子(中国)研究开发中心有限公司 移动通信系统的呼叫连接失败提示方法
CN101076188A (zh) * 2007-03-20 2007-11-21 中兴通讯股份有限公司 一种基于tcs的异常中止呼叫方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3624869B2 (ja) * 2001-09-07 2005-03-02 日本電気株式会社 呼接続システム
CN100442908C (zh) * 2004-11-15 2008-12-10 华为技术有限公司 蓝牙接入点的链路管理方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1471314A (zh) * 2002-07-26 2004-01-28 华为技术有限公司 会议电视系统中断线重呼方法
CN1798447A (zh) * 2004-12-28 2006-07-05 乐金电子(中国)研究开发中心有限公司 移动通信系统的呼叫连接失败提示方法
CN1794867A (zh) * 2005-06-30 2006-06-28 华为技术有限公司 多播业务中停止用户会话的方法
CN101076188A (zh) * 2007-03-20 2007-11-21 中兴通讯股份有限公司 一种基于tcs的异常中止呼叫方法

Also Published As

Publication number Publication date
CN101076188B (zh) 2013-01-16
CN101076188A (zh) 2007-11-21

Similar Documents

Publication Publication Date Title
JP5340525B2 (ja) 通話再開システム、通話再開プログラム、通話再開方法、携帯端末および中継装置
CN105430143B (zh) 通讯处理器及实现VoLTE的方法、移动终端及数据卡
CA2581203A1 (en) System and method for bridge call appearance in distributed peer-to-peer network
JP2006005936A (ja) 移動通信システム及びそのセッション解除方法
JP2009510809A (ja) 発呼端末と着呼端末との間で呼を確立する方法
WO2009076851A1 (zh) 处理业务的方法、终端及网络系统
WO2014134902A1 (zh) 在双卡双待双通移动终端上进行三方通话的方法及终端
CN104602361B (zh) 一种用WiFi网络扩展手机无线网络业务的方法
CN102577283B (zh) 用于语音和其他cs域服务的规定的设备及方法
JP2004364301A5 (zh)
CN111787496B (zh) 一种手机间转接电话的方法及设备
CN1855968B (zh) 一种蓝牙语音终端设备与多个远端用户进行通话的方法
WO2016045293A1 (zh) 一种全呼方法、系统、相关装置及计算机存储介质
CN104602214A (zh) 一种扩展手机无线语音和短信业务的方法
WO2011029363A1 (zh) 一种支持电路域电话和网络电话的呼叫控制装置及方法
WO2008113236A1 (fr) Méthode d'interruption anormale d'un appel basé sur un tcs
EP2173110B1 (en) A realizing method for re-answering call
US6606498B2 (en) State model for a wireless device
JPH11164357A (ja) 無線通信システム
CN106817685B (zh) 紧急呼叫控制方法及终端设备
CN100583927C (zh) 呼叫等待中通信终端选择呼叫的方法
JP2019220898A (ja) 無線通信端末、通信方法、及び通信プログラム
CN106713646B (zh) 一种基于嵌入式设备的应急语音通话装置与通话方法
JPH11127482A (ja) 移動通信端末の通話切れ防止システム
JP6310505B2 (ja) 中継システム、制御装置、中継機器及びプログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07855928

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07855928

Country of ref document: EP

Kind code of ref document: A1