The present invention generally relates to wireless communication. In particular, the present invention relates to a DECT (Digital Enhanced Cordless Telecommunications) based video phone system.
This section is to provide the reader with background information to facilitate a better understanding of the various aspects of the present invention. It should not be understood as admissions of prior art.
DECT is a digital communication standard, which is primarily used for creating cordless phone systems. A DECT phone system is popular. A DECT phone base of the DECT phone system can be integrated with a VoIP gateway to provide a SIP (Session Initiation Protocol, a signaling protocol widely used for controlling communication sessions such as voice and video calls over Internet Protocol) call on the outside line of the system and a DECT call on the inside line. However, since DECT does not support video transport, an outside SIP video call cannot enter inside a DECT phone system.
On the other hand, a phone set inside the DECT phone system, which supports WiFi, can take video call directly on SIP rather than DECT. Therefore, the media transportation of video SIP call will be on WiFi. However, a home WiFi network normally has a worse capacity of real-time media transportation compared with DECT, which will result in a poor voice performance during SIP video call on WiFi.
According one aspect of the invention, an apparatus is provided. The apparatus comprises: a VoIP gateway for communicating voice data of a video call stream over a DECT channel between at least one DECT terminal and a peer; and a WiFi access point for communicating video data of a video call stream over a WiFi channel between at least one WiFi video terminal and the peer.
It is to be understood that more aspects and advantages of the invention will be found in the following detailed description of the present invention.
The accompanying drawings, which are included to provide a further understanding of the illustrate embodiments of the invention together with the description which serves to explain the principle of the invention. Therefore, the invention is not limited to the embodiments. In the drawings:
An embodiment of the present invention will now be described in detail in conjunction with the drawings. In the following description, some detailed descriptions of known functions and configurations may be omitted for clarity and conciseness.
According to an embodiment of the present invention, a video phone system is provided wherein, for an incoming video call, the voice data and video data of the video call are transmitted in separated channels within the video phone system. In particular, the voice data is transmitted on DECT channel and the video data will be transmitted on WiFi channel.
In the embodiment, DECT channel is used for voice data transmission since DECT has a voice performance much better than WiFi. Given the fact that people is normally more sensitive to voice than to video during a phone call, it is meaningful to have the voice data transmitted on DECT channel. At the same time, WiFi channel is used for video data transmission since WiFi has a video performance better than DECT.
Next, a video phone system according to the embodiment of the invention will be described in detail. In the video phone system, a DECT base will be a control center for receiving SIP video call from an external SIP network and implement a video phone function by transmitting the voice data and video data respectively on DECT and WiFi channels. The voice data can be reproduced on a DECT handset registered to the DECT base. The video data can be reproduced on a multimedia mobile terminal which supports WiFi and DECT and is registered to the DECT base. For example, the mobile terminal could be a wireless Tablet.
As shown in
In the network shown in
In the network shown in
In the video phone system as shown in
It can be appreciated that the Tablet can also be provided with its own SIP stack, in which case the Tablet can be considered as an advanced DECT handset and receive voice data from the DECT base. That is, both the DECT base and the Tablet can have respective SIP account and the SIP server needs to support sip-forking and allow the registration from several devices with the same account. In the present invention, no further detailed description will be provided for this case.
For the practical implementation of the video phone system according to the embodiment of the invention, the DECT base and the Tablet may need to have the following functions:
Tablet:
Terminal for private communication protocol;
Media transactor;
NAT (Network Address Translation) traverse.
In addition, the Tablet may also realize a lightweight video framework for camera, display out, encoder, decoder and video mixer (preferably Gstreamer) for purpose of the video call. It can build pipeline according to video information from the DECT base.
DECT Base:
Terminal for private communication protocol;
To integrate the terminal with SIP stack;
Support video in SIP application;
In this embodiment, since the Tablet is not provided with a SIP stack, the DECT base also needs to support video for SIP signaling and maintain a state machine for remote video on the Tablet.
A video control is needed for the video data exchange on both the Tablet and the DECT base:
There is a specification of communication between the DECT base and the Tablet for purpose of video control of the video data transmitted from the DECT base and the Tablet. The communication is network-independent, which can be realized on DECT transport channel or on WiFi.
The DECT base handles state machine to control remote video on the Tablet during call initiation, negotiation and the whole video call. The initial state is “STOP”. When a SIP video call is initiated (sip-INVITE), the DECT base will send SDP (Session Description Protocol) describing video information like IP, port and codecs. For building the SDP, the DECT base needs to get video information from the Tablet through private protocol. This process can be carried out in a conventional flow, which is shown in
There are sub-states within “START”. For example, if a user on the Tablet wants to hold actively the call, the DECT base will turn the state to “send” from “sendrecv” and send sip-reINVITE to the remote peer. After the user recovers the call, the state becomes “sendrecv” from “send”.
During a call, the control works also in case of call hold, call transfer or other actions happen. For example, when a user wants to close video temporarily, the DECT base turns remote video from “sendrecv” to “stop”.
During ringing, SM is getting codec from the Tablet. After SIP negotiation, the DECT base will control the Tablet to start video sending and receiving. As shown in
The following references are used throughout
“EXT”: extended private signaling for video control between the DECT base and the Tablet
“DECT”: DECT signaling
“SIP ”: SIP signaling
“Active”: the Tablet initiates dialog
“Passive”: the Tablet received dialog initiated by remote peer
In home network, all of Tablets and DECT handsets are registered on the DECT base though DECT, and the DECT base is registered on a SIP server through SIP.
As shown in
The DECT base tells also Tablet the call-type is voice. The Tablet knows the call is voice, than will select ringtone specific for voice. This feature is for notifying a user with different ringtone.
After ringing, the DECT base will get a list of video codec from the Tablet and negotiate with the remote peer. If the negotiation is successful, the DECT base will turn the video state to “START” and send specific command to the Tablet. The terminal on Tablet listening to the command will start video to display and start camera to capture video on the Tablet. In this command, the DECT base will tell the Tablet the detailed parameters of the video.
During a video call, a voice stream is transmitted via the DECT base, but a video stream is transmitted between the remote peer and the Tablet, which is on WiFi, not via the DECT base.
The Tablet can accept an incoming call as voice call by return “no video codec” to the base.
Although incoming call is video call, a user of the Tablet has chance to take it as voice call. For this scenario, when the DECT base gets codec from the Tablet, the Tablet will return “no codec”. Then the DECT base will negotiate with the remote peer with voice call.
As shown in
As shown in
The above
If the Tablet wants to change codec, it will sends “notify” to the DECT base which will get the codec and then send out re-invite on SIP.
Four scenarios are shown in the
ReINVITE from remote peer (passive in the view of Tablet) requires video to voice
ReINVITE from remote peer requires voice to video
ReINVITE from local Tablet (active in the view of Tablet) requires video to voice
ReINVITE from local Tablet (active in the view of Tablet) requires voice to video
As shown in
In this case, the Tablet needs to control the direction of video according to commands from the DECT base.
Call hold and recover are traditional scenarios on telephone. SIP supports these scenarios by sending reINVITE with SDP, which describes a stream direction. The commands and state machine between the DECT base and Tablet support these features. For example, hold on Tablet means “send only” in reINVITE, state of video becomes “send”, and the DECT base stops video download on Tablet.
There are two kinds of call transfer. The first one is DECT transfer between the Tablet and handset at home. The SIP call established between the DECT base and the remote peer is not changed. When call is transferred from Tablet with video to DECT handset without video, the DECT base will stop video and then initiate a DECT transfer. The second is SIP transfer between Tablet and remote peer. The DECT base initiates a SIP transfer, and the DECT base will stop video on Tablet if the transfer target has no video.
The Tablet needs to have a video mixer for purpose of a video conference call.
It is important for VoIP to traverse NAT (Network Address Translation). There are several techniques that have been developed to facilitate the traversal of NAT. These techniques were described in the document “Considerations for Selection of Techniques for NAT Traversal”, draft-iab-nat-traversal-considerations-00, J. Rosenberg. These techniques can be summarized as follows:
Modify the NAT: Application Layer Gateways (ALG)
Modify the Clients: Unilaternal Self-Address Fixing (UNSAF)
Modify the Servers: Server Involvement in NAT Navigation (SINN) SBC (Session Border Controller)
Modify the NAT and the Client: RSIP (Realm Specific Internet P o ocol), NSIS (Next Steps in Signaling)
Modify the NAT and the Server: MIDCOM (Middlebox Communications)
Modify the Clients and Servers: Protocol Update
Modify Everything: IPv6
STUN and SBC can be used for VoIP to traverse NAT in the video phone system of the embodiment of the present invention.
For SBC, the voice RTP (Real-time Transport Protocol) transportation is between SBC and the DECT base, but video RTP is between SBC and the Tablet. In the operations of the Tablet for NAT traverse, normally RTP to SBC (even “recvonly” for Tablet) will be initiated first, after which NAT binding will be created. And binding on NAT needs to be kept alive.
For STUN, there will be a STUN client on the Tablet and the binding on NAT needs to be kept alive.
According to the embodiment of the present invention, audio and video data are transmitted at separated channels. As SIP-DECT bridge, the DECT base does not have big delay, so AV synchronization is not necessary.
With the video phone system according to an embodiment of the invention, since the voice data is transmitted on DECT channel and the video data is transmitted on WiFi channel, good quality of both the voice and the video data is expected. Voice call on DECT has longer talk time and better coverage indoor and outdoor than that on WiFi. In addition, the system has a seamless hand-over between DECT base, which is better than a hand-over on WiFi.
For requirement “simultaneous” ringing on several home devices, the solution also does not SIP-forking on the proxy server of operator.
It will be understood that the present invention has been described purely by way of example, and modifications of detail can be made without departing from the scope of the invention. Each feature disclosed in the description and (where appropriate) the claims and drawings may be provided independently or in any appropriate combination. Features may, where appropriate be implemented in hardware, software, or a combination of the two.
Number | Date | Country | Kind |
---|---|---|---|
PCT/CN2011/075599 | Jun 2011 | CN | national |
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/CN2012/076632 | 6/8/2012 | WO | 00 | 12/9/2013 |