Communication protocol and method for operating a volp communication with additional data transmission
Claim Score by NHIP
Abstract
The present invention concerns a communication protocol suitable for bi-directional VoIP communication with media streams including audio and/or video data, and based on a real-time transport protocol (RTP) as described in IETF RFC 1889, wherein packets mainly comprised of a header part and a payload part are exchanged between at least two users, thus forming a RTP channel, wherein at least one sub-channel is embedded within the RTP channel, said sub-channel being adapted to carry command, signaling and/or information data.

Term
Term ended
Projected expiry passed 18 August 2023, 3.1 years ago.
- Priority and filed
- Published
- Projected expiry
- Today
8 claims: 4 independent, 4 dependent
- 1Broadest claimClaim Score 57, broad(NHIP)A communication method, having a protocol suitable for bi-directional Voice over Internet Protocol (VoIP) communications with media streams including audio and/or video data, and based on a real-time transport protocol (RTP) in Internet Engineering Task Force (IETF) Request for Comments (RFC) 1889, the method comprising:exchanging packets comprised of a header part and a payload part between at least two users to form a RTP channel;and providing at least one sub-channel, which is embedded within the RTP channel, to carry command, signaling and/or information data.
- 3A method for operating a bi-directional Voice over Internet Protocol (VoIP) communication over an Internet Protocol (IP) network, based on a real-time transport protocol (RTP) in Internet Engineering Task Force (IETF) Request For Comments (RFC) 1889, the method comprising:exchanging media streams including audio and/or video data, over a RTP channel, between at least two users, in the form of packets comprised of a header part and a payload, wherein additional command, signaling and/or information data is transmitted in both transmission directions through at least one sub-channel embedded within the RTP channel.
- 8A multimedia telecommunication terminal adapted to perform a bi-directional Voice over Internet Protocol (VoIP) communication based on a real-time transport protocol (RTP) in Internet Engineering Task Force (IETF) Request For Comments (RFC) 1889, said terminal comprises:means for exchanging media streams including audio and/or video data, over a RTP channel, between at least two users, in the form of packets comprised of a header part and a payload, wherein additional command, signaling and/or information data is transmitted in both transmission directions through at least one sub-channel embedded within the RTP channel.
Independent claims3
30 paragraphs in 5 sections, as filed
TECHNICAL FIELD
0001The present invention is related to the field of the telecommunications, in particular in connection with Voice over Internet (VoIP) applications. The invention is based on a priority application PCT/EP03/09118 which is hereby incorporated by reference.
BACKGROUND OF THE INVENTION
0002Nowadays, the real-time transport protocols using RTP channels as described in IETF RFC 1889, such as for example the protocols known as H.323, Session Initiation Protocol (SIP) or H.248/Megaco, only consider call-related information exchanges between terminating points.
0003Indeed, these protocols consider signaling between communications terminals only for call set up and evolution. Once the RTP communication channel is established, there is no possibility to transmit additional data, i.e. data other than the audio and/or video data forming the payload of the exchanged streams.
0004When considering the foregoing context, one must differentiate the two planes involved in such communications, namely the signaling plane and the user plane.
0005In the signaling plane, data is exchanges between signaling gateways using the afore mentioned protocols (H.323, SIP, . . . ) in order to configure the communication or session and to make it evolve if wanted or needed (invite another user, cut the communication, . . . ).
0006In the user plane, data is exchanged between media gateways over a RTP channel, the useful data being the payload.
0007Nowadays, no possibility is provided to allow transmission of additional media related data over said RTP channel, which for example could allow to modify the use of the media.
0008One must point out that the H.323 protocol provides a specific H.320 channel for exchanging such additional data. Nevertheless, using a proper channel for such purposes seems excessive and too resources consuming.
0009Furthermore, it must also be noticed that current IP networks do not provide means for inband end-to-end signaling.
SUMMARY OF THE INVENTION
0010The main aim of the present invention is to fill the lack expressed before and to provide a simple solution allowing user-to-user additional data exchange during communications over IP networks.
0011Therefore, the present invention concerns first a communication protocol suitable for bi-directional VoIP communication with media streams including audio and/or video data, and based on a real-time transport protocol (RTP) as described in IETF RFC 1889, wherein packets mainly comprised of a header part and a payload part are exchanged between at least two users, thus forming a RTP channel, characterised in that at least one sub-channel is embedded within the RTP channel, said sub-channel being adapted to carry command, signaling and/or information data.
0012Preferably, the header part of each packet comprises at least one extension bit in a predetermined place, whereby allowing to provide one or several additional fields in the header or in a header extension of said packets to carry said command, signaling and/or information data.
0013The present invention also encompasses a method for operating a bi-directional VoIP communication over an IP network, based on a real-time transport protocol (RTP) as described for example in IETF RFC 1889, wherein media streams including audio and/or video data are exchanged, over a RTP channel, between at least two users, in the form of packets mainly comprised of a header part and a payload, characterised in that additional command, signaling and/or information data is transmitted through at least one sub-channel embedded within the RTP channel and available in both transmission directions.
0014As indicated before, additional fields are provided in the header part or in a header extension of the transmitted packets, in particular by setting at least one extension bit.
0015Thus, bi-directional user-to-user exchanges of information during a normal or a multimedia communication is made possible by creating sub-channels in a RTP channel to carry other types of data than said multimedia data.
0016For example, several kinds of sub-channels are possible: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0017"> command sub-channel </li><li id="ul0002-0002" num="0018"> signaling sub-channel </li><li id="ul0002-0003" num="0019"> information sub-channel. </li></ul></li></ul>
0020Advantageously, the bi-directional VoIP communication is operated on the basis of the protocol as described before.
BRIEF DESCRIPTION OF THE DRAWINGS
0021A preferred structure of an RTP packet incorporating the additional fields proposed by the invention, is schematically shown on the enclosed figure.
DETAILED DESCRIPTION OF THE INVENTION
0022Thus, as can be seen from said figure, providing additional field(s) to carry said additional signaling data for transmission between users consists, in relation to the IETF RFC 1899 protocol features and for each transmitted packet, in setting the marker bit M and the extension bit X, in coding the payload type bits PT with the information of the user to user signals and in providing a header extension following the normal RTP header and comprising a profile indication field, a length indication field, a signaling type indication field and several bytes for receiving the additional data to be carried, the number of bytes corresponding to the value of the content of the length indication field.
0023When carrying out the method of the invention, the communication terminal of the user on the reception side analyses, upon receipt of a RTP packet, the header, in particular at least one extension bit, of the received packet and takes into account the command, signaling and/or information data contained in the additional fields of the said header or header extension.
0024The invention will now be described further on in a non limitative way and in relation to specific examples.
0025As exposed before, the main purpose of the invention is to introduce some additional information in media streams carried over a RTP channel. During bi-directional VoIP communication, media streams including either audio or video information or both are sent through a RTP channel fully described in the IETF RFC 1889 document.
0026Current RTP channels convey only media streams with few additional information like timestamps and sequence numbers.
0027The present invention proposes a new scheme of this RTP channel basically built on its current description by adding signaling messages on both paths of the bi-directional communication.
0028To add information in the RTP channel, it is necessary to extend the field of information to be carried. This is done by adding a new element in the header indicated by an extension bit. This extension bit enables to create new fields in the header to multiply considerably the possibilities of the RTP channel.
0029At reception of such a RTP packet, the receiving terminal analyses the header and reacts accordingly in taking into account the information contained in the sub-channel.
0030By way of the two following examples of two possible scenarii of communications between two users A and B, the practical advantages of the invention will become apparent.
0031As a first example, a VoIP call between A and B is considered: <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0032"> A and B are talking and A asks B to spell a particular word, </li><li id="ul0004-0002" num="0033"> B could choose either to spell it vocally or to write it on the keyboard of this own terminal then to send to A, via an information sub-channel, by activating a command on his terminal, </li><li id="ul0004-0003" num="0034"> at reception, the terminal of user A analyses the header and then display the information on the screen/display. </li></ul></li></ul>
0035As a second example, a multimedia communication (voice +video) between A and B is considered: <ul id="ul0005" list-style="none"><li id="ul0005-0001" num="0000"><ul id="ul0006" list-style="none"><li id="ul0006-0001" num="0036"> A and B are talking and use each their own motorized camera to show document and/or objects, </li><li id="ul0006-0002" num="0037"> A presents an object in the field of the camera connected to his terminal, </li><li id="ul0006-0003" num="0038"> B activates on his own terminal the joystick for zooming and/or modifying the angle of view, </li><li id="ul0006-0004" num="0039"> the commands are transmitted via the existing RTP channel (either voice or video channel) from terminal B to terminal/camera A on an embedded sub-channel, </li><li id="ul0006-0005" num="0040"> at reception, the terminal of user A analyses the header and then forwards the command to the camera. </li></ul></li></ul>
0041The present invention is, of course, not limited to the preferred embodiment described and represented herein, changes can be made or equivalents used without departing from the scope of the invention.
Contents5
2 sheets
Sheet 1 Sheet 2
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US10841357B1 | Cited by | United States of America | Search report |
| US7852833B2 | Cited by | United States of America | Search report |
| US2008317018A1 | Cited by | United States of America | Pre-grant |
| US8355323B2 | Cited by | United States of America | Search report |
| US8060094B2 | Cited by | United States of America | Search report |
| US7821940B2 | Cited by | United States of America | Search report |
| US2008101336A1 | Cited by | United States of America | Pre-grant |
| US10244559B2 | Cited by | United States of America | Search report |
| US2015092761A1 | Cited by | United States of America | Pre-grant |
| CN102916939A | Cited by | China | Search report |
| US2005208972A1 | Cited by | United States of America | Pre-grant |
| US10932298B2 | Cited by | United States of America | Applicant |
| US2005220028A1 | Cited by | United States of America | Pre-grant |
| US12069729B2 | Cited by | United States of America | Applicant |
| US2003097476A1 | Cites | United States of America | Pre-grant |
| US2003121117A1 | Cites | United States of America | Pre-grant |
| US2003235184A1 | Cites | United States of America | Pre-grant |
5 members in 5 offices
Priority claims4
| Document | Office | Kind | Date |
|---|---|---|---|
| 0309118 | European Patent Office (EPO) | W | |
| 0309118 | European Patent Office (EPO) | W | |
| PCTEP0309118 | – | – | – |
| WO2003EP09118 | – | – | – |
Members5
| Document | Office | Kind | |
|---|---|---|---|
| WO2005018192A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AU2003284867A1 | Australia | A1 | |
| EP1656779A1 | European Patent Office (EPO) | A1 | |
| CN1802834A | China | A | |
| US2007115945A1 | United States of America | A1 |
26 transactions on the USPTO file
Abandoned after 1 non-final rejection and 1 final rejection.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Email NotificationEML_NTR | EML_NTR | |
| Filing Receipt - CorrectedFLRCPT.C | FLRCPT.C | |
| Correspondence Address ChangeC.ADB | C.ADB | |
| Mail Abandonment for Failure to Respond to Office ActionAbandonedMABN2 | MABN2 | |
| Aband. for Failure to Respond to O. A.AbandonedABN2 | ABN2 | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Notice of DO/EO Acceptance MailedM903 | M903 | |
| Cleared by OIPE CSRL194 | L194 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Substitute Specification FiledC604 | C604 | |
| Preliminary AmendmentA.PE | A.PE | |
| 371 Completion Date371COMP | 371COMP | |
| Initial Exam Team nnIEXX | IEXX |
1 recorded assignment at the USPTO, latest first
- Now
Now: Held by
ALCATEL - 2006-01-11
Assignment of assignors interest.
Ownership change- From
- GASS RAYMONDPINIER FRANCOIS
- To
- ALCATEL
Recorded 2006-01-11, Signed 2005-10-05
2 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Information on status: application discontinuationABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTIONSTCB | STCB | |
| AssignmentAS | AS |
Numbers
- Publication
- 20070115945
- Publication, DOCDB
- 2007115945
- Publication, EPODOC
- US2007115945
- Application
- 10564162
- Application, DOCDB
- 56416203
- Application, EPODOC
- US20030564162
Titles
- English
- Communication protocol and method for operating a volp communication with additional data transmission
Classification
- CPC, 4
- H04M7/006
- H04L65/65
- H04L65/70
- H04L65/1101
- IPC, 3
- H04L12 66
- H04L29 06
- H04M7 00
- USPC, 1
- 370356000