US10356141B2 - Method and device for exchanging endpoint information, and telepresence endpoint - Google Patents

Method and device for exchanging endpoint information, and telepresence endpoint Download PDF

Info

Publication number
US10356141B2
US10356141B2 US15/025,686 US201415025686A US10356141B2 US 10356141 B2 US10356141 B2 US 10356141B2 US 201415025686 A US201415025686 A US 201415025686A US 10356141 B2 US10356141 B2 US 10356141B2
Authority
US
United States
Prior art keywords
multiplexing
information
exchanging
telepresence
terminal
Prior art date
Legal status (The legal status 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 status listed.)
Active, expires
Application number
US15/025,686
Other versions
US20160234270A1 (en
Inventor
Liang Wang
Xiaoyang Ye
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 Corp filed Critical ZTE Corp
Assigned to ZTE CORPORATION reassignment ZTE CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: WANG, LIANG, YE, XIAOYANG
Publication of US20160234270A1 publication Critical patent/US20160234270A1/en
Application granted granted Critical
Publication of US10356141B2 publication Critical patent/US10356141B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/4069—
    • H04L65/1006—
    • H04L65/1009—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1106—Call signalling protocols; H.323 and related
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/403—Arrangements for multi-party communication, e.g. for conferences
    • H04L65/608—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/24—Negotiation of communication capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/14—Systems for two-way working
    • H04N7/15—Conference systems

Definitions

  • the present disclosure relates to the field of communications, and in particular to a method and device for exchanging endpoint information, and a telepresence endpoint.
  • a video session system adopts a conventional protocol stack, the transmission of a path of main video stream between terminals is supported, a transmission requirement for multiple paths of main video streams is not supported, and the requirement of capture features of each stream is not described. For example, a spatial area at which a camera captures video streams is not described.
  • the video session system is improved, the transmission of multiple paths of media streams is supported, and the capture features of each stream are described.
  • the problem how to transmit the multiple paths of media streams by means of a telepresence session system also exists currently. If a traditional transmission mode of transmitting one path of media stream via one port is still adopted, there will be a obstacle when performing Network Address Translation (NAT) or crossing firewall due to the adoption of too many ports.
  • NAT Network Address Translation
  • a method and device for exchanging endpoint information are provided in the embodiment of the present disclosure, which are intended to at least solve the problem in the related art that there are too many ports and multiplexing transmission is unsmooth due to the fact that the multiplexing transmission mode of the traditional session system is still adopted in the telepresence system based on the conventional protocol architecture.
  • a method for exchanging endpoint information comprising: telepresence endpoints exchanging multiplexing information.
  • the multiplexing information comprises at least one of: multiplexing indication information used for indicating whether a telepresence endpoint adopts multiplexing; multiplexing type information used for indicating a multiplexing type by which multiplexing mapping information is exchanged; and the multiplexing mapping information used for describing a mapping relationship between a media capture code stream and a transmission code stream.
  • the telepresence endpoints exchange the multiplexing indication information in at least one of following manners: the telepresence endpoints exchanging the multiplexing indication information when the telepresence endpoints are exchanging a terminal capability set; and the telepresence endpoints exchanging the multiplexing indication information when the telepresence endpoints are setting up a call.
  • the telepresence endpoints exchange the multiplexing type information in at least one of following manners: the telepresence endpoints exchanging the multiplexing type information when the telepresence endpoints are exchanging a terminal capability set; and the telepresence endpoints exchanging the multiplexing type information when the telepresence endpoints are setting a call.
  • the telepresence endpoints exchange the multiplexing mapping information in at least one of following manners: in a signalling exchange process, the telepresence endpoints exchanging the multiplexing mapping information by carrying the multiplexing mapping information in signalling information; and when transmitting a media stream, the telepresence endpoints exchanging the multiplexing mapping information by carrying the multiplexing mapping information at an extended header of the transmitting media stream.
  • the method further comprising: performing multiplexing transmission on a media stream according to a result of exchanging the multiplexing information.
  • a device for exchanging endpoint information applicable to telepresence endpoints, comprising: an exchanging component, configured to exchange multiplexing information.
  • the exchanging component comprises at least one of: a first exchanging element, configured to exchange multiplexing indication information comprised in the multiplexing information when exchanging a terminal capability set; and a second exchanging element, configured to exchange multiplexing indication information comprised in the multiplexing information when setting up a call.
  • the exchanging component comprises at least one of: a third exchanging element, configured to exchange multiplexing type information comprised in the multiplexing information when exchanging a terminal capability set; and a fourth exchanging element, configured to exchange multiplexing type information comprised in the multiplexing information when setting up a call.
  • the exchanging component comprises at least one of: a fifth exchanging element, configured to, in a signalling exchange process, exchange multiplexing mapping information by carrying the multiplexing mapping information in signalling information; and a sixth exchanging element, configured to, when transmitting a media stream, exchange the multiplexing mapping information by carrying the multiplexing mapping information at an extended header of the transmitting media stream.
  • a transmitting component configured to perform multiplexing transmission on a media stream according to a result of exchanging the multiplexing information.
  • a telepresence endpoint comprising any one of the above devices.
  • telepresence endpoints exchange the multiplexing information, so that the problem in the related art that there are too many ports and multiplexing transmission is unsmooth due to the fact that the multiplexing transmission mode of the traditional session system is still adopted in the telepresence system based on the conventional protocol architecture is solved, and the effect of exchanging the multiplexing information between the telepresence endpoints and therefore multiplexing can be successfully performed in the telepresence system is further achieved.
  • FIG. 1 is a flowchart of a method for exchanging endpoint information according to an embodiment of the present disclosure
  • FIG. 2 is a structure block diagram of a device for exchanging endpoint information according to an embodiment of the present disclosure
  • FIG. 3 is a first examplary structure block diagram of the exchanging component 22 in the device for exchanging endpoint information according to an embodiment of the present disclosure
  • FIG. 4 is a second examplary structure block diagram of the exchanging component 22 in the device for exchanging endpoint information according to an embodiment of the present disclosure
  • FIG. 5 is a third examplary structure block diagram of the exchanging component 22 in the device for exchanging endpoint information according to an embodiment of the present disclosure
  • FIG. 6 is an examplary structure block diagram of the device for exchanging endpoint information according to an embodiment of the present disclosure
  • FIG. 7 is a structure block diagram of a telepresence endpoint according to an embodiment of the present disclosure.
  • FIG. 8 is a flowchart of implementing the multiplexing transmission indication when the telepresence endpoints perform message exchange according to an examplary implementation mode of the present disclosure
  • FIG. 9 is a flowchart of implementing the multiplexing transmission indication when the telepresence endpoints send a call message according to an examplary implementation mode of the present disclosure
  • FIG. 10 is a flowchart of implementing a multiplexing transmission indication when telepresence endpoints send capability set messages according to an examplary implementation mode of the present disclosure
  • FIG. 11 is a flowchart of performing mapping when telepresence endpoints send a capability set message according to an examplary implementation mode of the present disclosure
  • FIG. 12 is a flowchart of performing mapping when telepresence endpoints send an open logical channel message according to an examplary implementation mode of the present disclosure
  • FIG. 13 is a flowchart of implementing an indication 1 when H.323-based telepresence endpoints send a call message according to an examplary implementation mode of the present disclosure
  • FIG. 14 is a flowchart of implementing an indication 2 when H.323-based telepresence endpoints send a call message according to an examplary implementation mode of the present disclosure
  • FIG. 15 is a flowchart of implementing an indication 1 when H.323-based telepresence endpoints adopt a Generic Extensible Framework (GEF) according to an examplary implementation mode of the present disclosure;
  • GEF Generic Extensible Framework
  • FIG. 16 is a flowchart of implementing an indication 2 when H.323-based telepresence endpoints adopt a GEF according to an examplary implementation mode of the present disclosure
  • FIG. 17 is a flowchart of implementing an indication when H.323-based telepresence endpoints send a terminal capability set message according to an examplary implementation mode of the present disclosure
  • FIG. 18 is a flowchart of implementing an indication when H.323-based telepresence endpoints adopt a generic parameter according to an examplary implementation mode of the present disclosure
  • FIG. 19 is a flowchart of implementing an indication 1 when Session Initiation Protocol (SIP)-based telepresence endpoints adopt an offer/answer model according to an examplary implementation mode of the present disclosure
  • SIP Session Initiation Protocol
  • FIG. 20 is a flowchart of implementing an indication 2 when SIP-based telepresence endpoints adopt an offer/answer model according to an examplary implementation mode of the present disclosure
  • FIG. 21 is a flowchart of performing mapping of a telepresence terminal in a terminal capability set message according to an examplary implementation mode of the present disclosure
  • FIG. 22 is a flowchart of performing mapping of a telepresence terminal in a CLUE message according to an examplary implementation mode of the present disclosure
  • FIG. 23 is a flowchart of performing mapping of a telepresence terminal in an offer/answer model message according to an examplary implementation mode of the present disclosure
  • FIG. 24 is a flowchart of performing mapping of a telepresence terminal during opening of a logical channel according to an examplary implementation mode of the present disclosure.
  • FIG. 25 is a flowchart of performing mapping of a telepresence terminal during reopening of a logical channel according to an examplary implementation mode of the present disclosure.
  • FIG. 1 is a flowchart of a method for exchanging endpoint information according to an embodiment of the present disclosure. As shown in FIG. 1 , the flow includes the steps as follows.
  • Step S 102 telepresence endpoints exchange multiplexing information.
  • the telepresence endpoints exchange the multiplexing information, compared with in the related art the adoption of a traditional media stream transmission mode instead of the exchange of the multiplexing information, which meets requirements of a telepresence system for a multiplexing transmission mode, and enables the telepresence endpoints be able to obtain the multiplexing information of opposite ends in time; and multiplexing media stream transmission is performed according to the exchanged multiplexing information, the smoothness of multiplexing is improved.
  • the multiplexing information may comprise at least one of: multiplexing indication information used for indicating whether a telepresence endpoint adopts multiplexing; multiplexing type information used for indicating a multiplexing type by which multipath mapping information is exchanged; and the multiplexing mapping information used for describing a mapping relationship between a media capture code stream and a transmission code stream.
  • the telepresence endpoints can exchange the multiplexing indication information in the multiplexing information in multiple processing manner.
  • the telepresence endpoints exchange the multiplexing indication information in at least one of the manner as follows.
  • the telepresence endpoints exchange the multiplexing indication information when the telepresence endpoints are exchanging a terminal capability set.
  • the telepresence endpoints exchange the multiplexing indication information when the telepresence endpoints are setting up a call.
  • the telepresence endpoints can exchange the multiplexing type information in the multiplexing information in multiple processing manner.
  • the telepresence endpoints can exchange the multiplexing type information in at least one of the manner as follows.
  • the telepresence endpoints exchange the multiplexing type information when the telepresence endpoints are exchanging a terminal capability set.
  • the telepresence endpoints exchange the multiplexing mode information when the telepresence endpoints are setting up a call.
  • the telepresence endpoints may exchange the multiplexing mapping information in the multiplexing information in multiple processing manners.
  • the telepresence endpoints can exchange the multiplexing mapping information in at least one of the modes as follows. For example, in a signalling exchange process, the telepresence endpoints exchange the multiplexing mapping information by carrying the multiplexing mapping information in signalling information; and when transmitting a media stream, the telepresence endpoints exchange the multiplexing mapping information by carrying the multiplexing mapping information at an extended header of the transmitting media stream.
  • the flow can further comprise that: multiplexing transmission is performed on a media stream according to a result of exchanging the multiplexing information.
  • a device for exchanging endpoint information is further provided.
  • the device is configured to realize the embodiments and the examplary implementation modes which have been explained without detailed descriptions.
  • a term ‘component’ used below the combination of software and/or hardware with predetermined functions can be realized.
  • the device described by the following embodiment is better realized by the software, the realization of the hardware and the combination of the software and the hardware may be possible and may be constructed.
  • FIG. 2 is a structure block diagram of a device for exchanging endpoint information according to an embodiment of the present disclosure. As shown in FIG. 2 , the device for exchanging endpoint information 20 includes an exchanging component 22 , and the exchanging component 22 is described below.
  • the exchanging component 22 is configured to exchange multiplexing information between the telepresence endpoints.
  • FIG. 3 is a first examplary structure block diagram of the exchanging component 22 in the device for exchanging endpoint information according to an embodiment of the present disclosure.
  • the exchanging component 22 comprises at least one of: a first exchanging element 32 and a second exchanging element 34 , and the exchanging component 22 is described below.
  • the first exchanging element 32 is configured to exchange multiplexing indication information comprised in the multiplexing information when exchanging a terminal capability set; and the second exchanging element 34 is configured to exchange multiplexing indication information comprised in the multiplexing information when setting up a call.
  • FIG. 4 is a second examplary structure block diagram of the exchanging component 22 in the device for exchanging endpoint information according to an embodiment of the present disclosure.
  • the exchanging component 22 comprises at least one of: a third exchanging element 42 and a fourth exchanging element 44 , and the exchanging component 22 is described below.
  • the third exchanging element 42 is configured to exchange multiplexing type information comprised in the multiplexing information when exchanging a terminal capability set; and the fourth exchanging element 44 is configured to exchange multiplexing type information comprised in the multiplexing information when setting up a call.
  • FIG. 5 is a third examplary structure block diagram of the exchanging component 22 in the device for exchanging endpoint information according to an embodiment of the present disclosure.
  • the exchanging component 22 comprises at least one of: a fifth exchanging element 52 and a sixth exchanging element 54 , and the exchanging component 22 is described below.
  • the fifth exchanging element 52 is configured to, in a signalling exchange process, exchange multiplexing mapping information by carrying the multiplexing mapping information in signalling information; and the sixth exchanging element 54 is configured to, when transmitting a media stream, exchange the multiplexing mapping information by carrying the multiplexing mapping information at an extended header of the transmitting media stream.
  • FIG. 6 is an examplary structure block diagram of the device for exchanging endpoint information according to an embodiment of the present disclosure. As shown in FIG. 6 , the device further comprises a transmitting component 62 in addition to all the components shown in FIG. 2 , and the transmitting component 62 is described below.
  • the transmitting component 62 is connected to the exchanging component 22 and is configured to perform multiplexing transmission on a media stream according to a result of exchanging the multiplexing information.
  • FIG. 7 is a structure block diagram of a telepresence endpoint according to an embodiment of the present disclosure.
  • the telepresence endpoint 70 comprises the device for exchanging endpoint information 20 according to any one of the content mentioned above.
  • a method for carrying multiplexing transmission information in a telepresence system comprises that: telepresence endpoints exchange multiplexing transmission indication (which is a part of the above mentioned multiplexing information).
  • FIG. 8 is a flowchart of implementing the multiplexing transmission indication when the telepresence endpoints perform message exchange according to an examplary implementation mode of the present disclosure.
  • a terminal A and a terminal B are the telepresence endpoints
  • a multiplexing transmission indication is given when message exchange is performed between the telepresence endpoint A and the telepresence endpoint B
  • actual media stream transmission is performed between the two telepresence endpoints after the multiplexing transmission indication is exchanged.
  • FIG. 9 is a flowchart of implementing the multiplexing transmission indication when the telepresence endpoints send a call message according to an examplary implementation mode of the present disclosure.
  • the terminal A and the terminal B are the telepresence endpoints, and the telepresence endpoint A and the telepresence endpoint B give the multiplexing transmission indications in a call message by using an H.323 GEF.
  • a sending end can give the multiplexing transmission indication in a setup message
  • a receiving end can give the multiplexing transmission indication in an altering or connect message.
  • intermediate devices such as a Gate Keeper (GK) need to support the GEF, besides the terminals support the GEF.
  • GK Gate Keeper
  • FIG. 10 is a flowchart of implementing a multiplexing transmission indication when telepresence endpoints send capability set messages according to an examplary implementation mode of the present disclosure.
  • the terminal A and the terminal B are the telepresence endpoints, and the telepresence endpoint A and the telepresence endpoint B can give the multiplexing transmission indications in terminal capability set messages: TerminalCapabilitySet or an offer/answer model message.
  • the multiplexing transmission indication of the telepresence endpoints comprises clear indicating using of multiplexing and/or indicating a multiplexing type.
  • multiplexing transmission When there is a lack of the multiplexing transmission indication of the telepresence endpoints, multiplexing transmission will not be adopted.
  • the telepresence endpoints need to describe mapping of multiplexing.
  • the telepresence endpoints need to describe mapping from a media capture code stream to a Real-time Transport Protocol (RTP) stream.
  • RTP Real-time Transport Protocol
  • FIG. 11 is a flowchart of performing mapping when telepresence endpoints send a capability set message according to an examplary implementation mode of the present disclosure.
  • the terminal A and the terminal B are the telepresence endpoints, and the telepresence endpoint A and the telepresence endpoint B can perform mapping in at least one of messages: the terminal capability set message TerminalCapabilitySet, and the offer/answer model message in a CLUE message.
  • FIG. 12 is a flowchart of performing mapping when telepresence endpoints send an open logical channel message according to an examplary implementation mode of the present disclosure.
  • the terminal A and the terminal B are the telepresence endpoints, and the telepresence endpoint A and the telepresence endpoint B perform mapping during opening or reopening of a logical channel.
  • a substantial flow of completing a media call via the terminals may comprise: a call flow, a capability set exchange flow, a media stream transmission channel preparation (logical channel opening) flow and an actual media stream transmission flow.
  • Exemplary implementation mode 1 H.323-based telepresence endpoints give indications when sending a call message
  • the sending end can give an indication in a Setup message, and the receiving end can give an indication in an Altering or Connect message.
  • the multiplexing transmission indication will be given in the call message by the terminals, and opposite ends are informed as soon as possible of that the media stream will be transmitted in a multiplexing mode.
  • the indication parts may be altered or deleted by the GK.
  • FIG. 13 is a flowchart of implementing an indication 1 when H.323-based telepresence endpoints send a call message according to an examplary implementation mode of the present disclosure.
  • the terminal A and the terminal B are the telepresence endpoints, the terminal A sends the Setup message to the terminal B, wherein a multiplexing indication is carried in the Setup message; after receiving the Setup message, the terminal B determines, by analysis, that the terminal A will transmit the media stream by multiplexing; after sending a Call proceeding message to the terminal A, the terminal B sends the Altering message carrying the multiplexing indication to the terminal A; and after receiving the Altering message, the terminal A determines, by analysis, that the terminal B will transmit the media stream in the multiplexing manner; and the terminal B sends the Connect message to the terminal A.
  • FIG. 14 is a flowchart of implementing an indication 2 when H.323-based telepresence endpoints send a call message according to an examplary implementation mode of the present disclosure.
  • the terminal A and the terminal B are the telepresence endpoints, the terminal A sends the Setup message to the terminal B, wherein the multiplexing indication is carried in the Setup message; and after receiving the Setup message, the terminal B determines, by analysis, that the terminal A will transmit the media stream by multiplexing; after sending the Call proceeding message and the Altering message to the terminal A, the terminal B sends the Connect message carrying the multiplexing indication to the terminal A; and after receiving the Connect message, the terminal A determines, by analysis, that the terminal B will transmit the media stream in the multiplexing manner.
  • FIG. 15 is a flowchart of implementing an indication 1 when H.323-based telepresence endpoints adopt a GEF according to an examplary implementation mode of the present disclosure.
  • FIG. 16 is a flowchart of implementing an indication 2 when H.323-based telepresence endpoints adopt a GEF according to an examplary implementation mode of the present disclosure. As shown in FIG. 15 and FIG.
  • the terminal A and the terminal B are the telepresence endpoints
  • the telepresence sending terminals can give indications by using parameters (neededFeatures or desiredFeatures) in the Setup message
  • telepresence receiving terminals can give indications by using a supportedFeatures message in the Altering or Connect message.
  • Exemplary implementation mode 2 the H.323-based telepresence endpoints give indications when sending a terminal capability set
  • a conventional protocol stack can be completely multiplexed, and a call flow does not need to be involved when the multiplexing transmission indication of the terminals is altered.
  • FIG. 17 is a flowchart of implementing an indication when H.323-based telepresence endpoints send a terminal capability set message according to an examplary implementation mode of the present disclosure.
  • the terminal A and the terminal B are the telepresence endpoints.
  • the terminal A sends the terminal capability set message (TerminalCapabilitySet) carrying the multiplexing indication of the telepresence endpoints to the terminal B; after the terminal B receives the message sent by the terminal A, it is parsed that the multiplexing indication exists, so as to determine that the terminal A will transmit the media stream by multiplexing and a multiplexing transmission type is substantially described; the terminal B sends a terminal capability set response message (TerminalCapabilitySetAck) to the terminal A; the terminal B sends the terminal capability set message (TerminalCapabilitySet) carrying the multiplexing indication to the terminal A; after the terminal A receives the message sent by the terminal B, it is parsed that the multiplexing indication exists, so as to determine that the terminal B will adopt the multiplexing transmission mode and the multiplexing transmission type is substantially described; and the terminal A sends the terminal capability set response message (TerminalCapabilitySetAck) to the terminal B.
  • TerminalCapabilitySet terminal capability set message carrying the multiplexing indication of the telepresence endpoints
  • FIG. 18 is a flowchart of implementing an indication when H.323-based telepresence endpoints adopt a generic parameter according to an examplary implementation mode of the present disclosure.
  • the terminal A and the terminal B are the telepresence endpoints.
  • the multiplexing indication can be given between the terminals in the terminal capability set message by using the generic parameter.
  • the multiplexing parameter relates to supporting or not of multiplexing (multiplexTransfer) and the type of multiplexing (multiplexTransferType).
  • multiplexTransfer multiplexTransfer
  • multiplexTransferType the type of multiplexing
  • the receiving end parses multiplexing type fields, and it is represented that the sending end supports multiplexing.
  • a value of multiplexTransfer can be set to be false or the multiplexing indication is not carried.
  • the media stream is transmitted in a non-multiplexing mode, namely one transmission address is used for transmitting one path of media stream.
  • Exemplary implementation mode 3 SIP-based telepresence endpoints given indications in an offer/answer model message
  • FIG. 19 is a flowchart of implementing an indication 1 when SIP-based telepresence endpoints adopt an offer/answer model message according to an examplary implementation mode of the present disclosure.
  • the SIP-based telepresence endpoints give the multiplexing indication in the offer/answer model message by using two pairs of messages.
  • the terminal A and the terminal B are the telepresence endpoints.
  • the terminal A sends an offer message carrying the multiplexing indication to the terminal B, and the terminal B parses the message to determine that the terminal A will send the media stream in the multiplexing manner.
  • the terminal B returns an answer message to the terminal A.
  • the terminal B sends an offer message carrying the multiplexing indication to the terminal A, and the terminal A parses the message to determine that the terminal B will also send the media stream in the multiplexing manner.
  • the terminal A returns an answer message to the terminal B.
  • FIG. 20 is a flowchart of implementing an indication 2 when SIP-based telepresence endpoints adopt an offer/answer model according to an examplary implementation mode of the present disclosure.
  • the SIP-based telepresence endpoints give the multiplexing indication in the offer/answer model message by using a pair of messages.
  • the terminal A and the terminal B are the telepresence endpoints.
  • the terminal A sends an offer message carrying the multiplexing indication to the terminal B, and the terminal B parses the message to determine that the terminal A will send the media stream in the multiplexing mode.
  • the terminal B sends an answer message carrying the multiplexing indication to the terminal A, and the terminal A parses the message to determine that the terminal B will also send the media stream in the multiplexing mode.
  • Exemplary implementation mode 4 the telepresence endpoints perform mapping in the terminal capability set message TerminalCapabilitySet
  • a multiplexing mapping type can comprise static mapping, dynamic mapping and comprehensive mapping.
  • the static mapping refers to that, during the signalling exchange process, a mapping relationship between the RTP stream and the media capture code stream, such as a mapping relationship between an identifier of the RTP stream and an identifier of the media capture code stream, is carried in a message.
  • the identifier of the RTP stream can be used for uniquely identifying one path of RTP stream by using a Synchronous Source (SSRC), and the identifier of the media capture code stream can be used for uniquely identifying one path of media capture code stream by using a captureID (media capture ID) and an encodingID (the coding ID used for coding this path of captureID); or a new field such as a media capture code stream identifier (demultiplexID) is adopted to identify one path of media capture code stream, and a corresponding relationship exists between the demultiplexID and the captureID, the encodingID substantially.
  • SSRC Synchronous Source
  • demultiplexID media capture code stream identifier
  • mapping between the RTP stream and the media capture code stream are not described in a signalling.
  • a mapping relationship between the demultiplexID and the captureID, the encodingID is exchanged in the signalling; and when the captureID and the encodingID are adopted to describe the media capture code stream, the new field is not adopted to describe the media capture code stream, and any mapping does not need to be carried in the signalling.
  • an RTP header needs to be extended by the terminals, the identifier of the media capture code stream (demultiplexID or captureID, encodingID) is filled, and the terminals need to parse an extended part of the header of the RTP stream, so as to dynamically obtain the mapping relationship between the media capture code stream and the RTP stream.
  • the comprehensive mapping is the combination of the static mapping and the dynamic mapping.
  • the mapping relationship between the RTP stream and the media capture code stream is described in signalling exchange, the RTP header is also extended, and the identifier of the media capture code stream is carried in the extended header.
  • multiple paths of received streams can be processed in a dynamic mapping manner, the extended part of the header of the RTP stream of each path of stream is parsed to obtain the captureID and the encodingID corresponding to each path of stream, and the selected media capture code stream captureID and encodingID corresponding to a certain path of RTP stream can be determined.
  • FIG. 21 is a flowchart of performing mapping of a telepresence terminal in a terminal capability set message according to an examplary implementation mode of the present disclosure.
  • the terminal A and the terminal B are the telepresence endpoints, the terminal A sends a TerminalCapabilitySet message carrying a mapping relationship to the terminal B, and the terminal B receives and maintains the mapping relationship; the terminal B sends ACK to the terminal A; the terminal B sends the TerminalCapabilitySet message carrying the mapping relationship to the terminal A, and the terminal A receives and maintains the mapping relationship; and the terminal A sends ACK to the terminal B.
  • Exemplary implementation mode 5 the telepresence endpoints perform mapping in the CLUE message
  • FIG. 22 is a flowchart of performing mapping of a telepresence terminal in a CLUE message according to an examplary implementation mode of the present disclosure.
  • the terminals exchange a capability set by using the CLUE message based on a CLUE channel
  • the telepresence endpoints can perform mapping in the CLUE message.
  • the terminal A and the terminal B are the telepresence endpoints.
  • the terminal A sends an advertisement message (advertisement) to the terminal B, wherein the advertisement message comprises all media capture streams information and encoding information capable of being provided by the terminal A; the terminal B selects two of multiple paths of stream, associates a field (demultiplexID) with a captureID (VC) and an encodingID (ENC), and then sends to the terminal A in a configuration message (configure); after the terminal A receives the configuration message, the demultiplexID is adopted as an extended header of each path of RTP stream, and after the terminal B receives the RTP stream, the extended header can be parsed to obtain a needed mapping relationship.
  • the process of sending the advertisement message to the terminal A by the terminal B and the process of sending the configuration message to the terminal B by the terminal A are consistent to the abovementioned process without repetition.
  • Exemplary implementation mode 6 the telepresence endpoints perform mapping in the offer/answer model message
  • FIG. 23 is a flowchart of performing mapping of a telepresence terminal in an offer/answer model message according to an examplary implementation mode of the present disclosure.
  • the terminal A and the terminal B are the telepresence endpoints, and mapping is performed in the offer/answer model message.
  • the carrier of an offer/answer model generally adopts, but not limited to, an invite/200 OK message.
  • the terminal A sends an offer message carrying multiplexing mapping to the terminal B, and after receiving the offer message, the terminal B maintains a mapping relationship.
  • the terminal B sends an answer message to the terminal A.
  • the process of sending the message to the terminal A by the terminal B is consistent to the abovementioned process without repetition.
  • Exemplary implementation mode 7 the telepresence endpoints perform mapping during opening of a logical channel
  • FIG. 24 is a flowchart of performing mapping of a telepresence terminal during opening of a logical channel according to an examplary implementation mode of the present disclosure.
  • the telepresence endpoints perform mapping from the media capture code stream to the RTP stream during the opening of the logical channel.
  • the terminal A and the terminal B are the telepresence endpoints, the terminal A sends an OpenLogicalChannel (OLC) message carrying a mapping relationship to the terminal B, and the mapping relationship is borne by using a generic parameter field in a generic message in an OLC.
  • OLC OpenLogicalChannel
  • the terminal B returns an open logical channel response message to the terminal A.
  • the terminal B sends the OLC message carrying the mapping relationship to the terminal A.
  • the terminal A returns a response to the terminal B.
  • Exemplary implementation mode 8 the telepresence endpoints perform mapping during reopening of the logical channel
  • FIG. 25 is a flowchart of performing mapping of a telepresence terminal during reopening of a logical channel according to an examplary implementation mode of the present disclosure.
  • the telepresence endpoints perform mapping during reopening of the logical channel.
  • the terminal A and the terminal B are the telepresence endpoints.
  • a conventional logical channel between the terminal A and the terminal B is closed firstly, and then a new logical channel is opened.
  • the terminal A sends an OLC message carrying a mapping relationship to the terminal B.
  • the terminal B returns an open logical channel response message to the terminal A.
  • the terminal B sends a OLC message carrying the mapping relationship to the terminal A.
  • the terminal A returns an open logical channel response to the terminal B.
  • modules or all steps in the present disclosure can be realized by using a generic computation device, can be centralized on a single computation device or can be distributed on a network composed of a plurality of computation devices.
  • they can be realized by using executable program codes of the computation devices, so that they can be stored in a storage device and executed by the computation devices, the shown or described steps can be executed in a sequence different from this sequence under certain conditions, or they are manufactured into each integrated circuit module respectively, or a plurality of modules or steps therein are manufactured into a single integrated circuit module.
  • the present disclosure is not limited to combination of any specific hardware and software.
  • the method and device for exchanging endpoint information and the telepresence endpoint provided by the embodiments of the present disclosure can bring the following beneficial effects that: the problem in the related art that there are too many ports and multiplexing transmission is unsmooth due to the fact that the multiplexing transmission mode of the traditional session system is still adopted in the telepresence system based on the conventional protocol architecture is solved, and the effect of exchanging the multiplexing information between the telepresence endpoints and therefore multiplexing can be successfully performed in the telepresence system is further achieved.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Telephonic Communication Services (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

Provide are a method and device for exchanging endpoint information and a telepresence endpoint. The method includes that: multiplexing information is exchanged between telepresence endpoints. By means of the present disclosure, the problem in the related art that there are too many ports and multiplexing transmission is unsmooth due to the fact that a multiplexing transmission mode of a traditional session system is still adopted in a telepresence system based on a conventional protocol architecture is solved, and the effect of exchanging the multiplexing information between the telepresence endpoints and therefore multiplexing can be successfully performed in the telepresence system is further achieved.

Description

TECHNICAL FIELD
The present disclosure relates to the field of communications, and in particular to a method and device for exchanging endpoint information, and a telepresence endpoint.
BACKGROUND
A video session system adopts a conventional protocol stack, the transmission of a path of main video stream between terminals is supported, a transmission requirement for multiple paths of main video streams is not supported, and the requirement of capture features of each stream is not described. For example, a spatial area at which a camera captures video streams is not described. When designing a telepresence system, the video session system is improved, the transmission of multiple paths of media streams is supported, and the capture features of each stream are described. The problem how to transmit the multiple paths of media streams by means of a telepresence session system also exists currently. If a traditional transmission mode of transmitting one path of media stream via one port is still adopted, there will be a obstacle when performing Network Address Translation (NAT) or crossing firewall due to the adoption of too many ports. The best way refers to that multiplexing transmission is performed on the multiple paths of media streams on the same transmission address, and the compatibility of new devices and old devices is supported on the basis of supporting multiplexing transmission. However, there is no corresponding solution how to transmit the multiple paths of media streams by the telepresence system in the related art.
Thus, the problem that there are too many ports and multiplexing transmission is unsmooth due to the fact that a multiplexing transmission mode of a traditional session system is still adopted in the telepresence system based on a conventional protocol architecture exists in the related art.
SUMMARY
A method and device for exchanging endpoint information are provided in the embodiment of the present disclosure, which are intended to at least solve the problem in the related art that there are too many ports and multiplexing transmission is unsmooth due to the fact that the multiplexing transmission mode of the traditional session system is still adopted in the telepresence system based on the conventional protocol architecture.
According to one aspect of the embodiment of the present disclosure, a method for exchanging endpoint information is provided, comprising: telepresence endpoints exchanging multiplexing information.
In an example embodiment, the multiplexing information comprises at least one of: multiplexing indication information used for indicating whether a telepresence endpoint adopts multiplexing; multiplexing type information used for indicating a multiplexing type by which multiplexing mapping information is exchanged; and the multiplexing mapping information used for describing a mapping relationship between a media capture code stream and a transmission code stream.
In an example embodiment, the telepresence endpoints exchange the multiplexing indication information in at least one of following manners: the telepresence endpoints exchanging the multiplexing indication information when the telepresence endpoints are exchanging a terminal capability set; and the telepresence endpoints exchanging the multiplexing indication information when the telepresence endpoints are setting up a call.
In an example embodiment, the telepresence endpoints exchange the multiplexing type information in at least one of following manners: the telepresence endpoints exchanging the multiplexing type information when the telepresence endpoints are exchanging a terminal capability set; and the telepresence endpoints exchanging the multiplexing type information when the telepresence endpoints are setting a call.
In an example embodiment, the telepresence endpoints exchange the multiplexing mapping information in at least one of following manners: in a signalling exchange process, the telepresence endpoints exchanging the multiplexing mapping information by carrying the multiplexing mapping information in signalling information; and when transmitting a media stream, the telepresence endpoints exchanging the multiplexing mapping information by carrying the multiplexing mapping information at an extended header of the transmitting media stream.
In an example embodiment, after the telepresence endpoints exchanging the multiplexing information, the method further comprising: performing multiplexing transmission on a media stream according to a result of exchanging the multiplexing information.
According to another aspect of the embodiment of the present disclosure, a device for exchanging endpoint information is provided, applicable to telepresence endpoints, comprising: an exchanging component, configured to exchange multiplexing information.
In an example embodiment, the exchanging component comprises at least one of: a first exchanging element, configured to exchange multiplexing indication information comprised in the multiplexing information when exchanging a terminal capability set; and a second exchanging element, configured to exchange multiplexing indication information comprised in the multiplexing information when setting up a call.
In an example embodiment, the exchanging component comprises at least one of: a third exchanging element, configured to exchange multiplexing type information comprised in the multiplexing information when exchanging a terminal capability set; and a fourth exchanging element, configured to exchange multiplexing type information comprised in the multiplexing information when setting up a call.
In an example embodiment, the exchanging component comprises at least one of: a fifth exchanging element, configured to, in a signalling exchange process, exchange multiplexing mapping information by carrying the multiplexing mapping information in signalling information; and a sixth exchanging element, configured to, when transmitting a media stream, exchange the multiplexing mapping information by carrying the multiplexing mapping information at an extended header of the transmitting media stream.
In an example embodiment, further comprising: a transmitting component, configured to perform multiplexing transmission on a media stream according to a result of exchanging the multiplexing information.
According to still another aspect of the embodiment of the present disclosure, a telepresence endpoint is provided, comprising any one of the above devices.
By means of the present disclosure, telepresence endpoints exchange the multiplexing information, so that the problem in the related art that there are too many ports and multiplexing transmission is unsmooth due to the fact that the multiplexing transmission mode of the traditional session system is still adopted in the telepresence system based on the conventional protocol architecture is solved, and the effect of exchanging the multiplexing information between the telepresence endpoints and therefore multiplexing can be successfully performed in the telepresence system is further achieved.
BRIEF DESCRIPTION OF THE DRAWINGS
The drawings described herein are intended to provide further understanding of the present disclosure, and form a part of the present disclosure. The schematic embodiments and descriptions of the present disclosure are intended to explain the present disclosure, and do not form improper limits to the present disclosure. In the drawings:
FIG. 1 is a flowchart of a method for exchanging endpoint information according to an embodiment of the present disclosure;
FIG. 2 is a structure block diagram of a device for exchanging endpoint information according to an embodiment of the present disclosure;
FIG. 3 is a first examplary structure block diagram of the exchanging component 22 in the device for exchanging endpoint information according to an embodiment of the present disclosure;
FIG. 4 is a second examplary structure block diagram of the exchanging component 22 in the device for exchanging endpoint information according to an embodiment of the present disclosure;
FIG. 5 is a third examplary structure block diagram of the exchanging component 22 in the device for exchanging endpoint information according to an embodiment of the present disclosure;
FIG. 6 is an examplary structure block diagram of the device for exchanging endpoint information according to an embodiment of the present disclosure;
FIG. 7 is a structure block diagram of a telepresence endpoint according to an embodiment of the present disclosure;
FIG. 8 is a flowchart of implementing the multiplexing transmission indication when the telepresence endpoints perform message exchange according to an examplary implementation mode of the present disclosure;
FIG. 9 is a flowchart of implementing the multiplexing transmission indication when the telepresence endpoints send a call message according to an examplary implementation mode of the present disclosure;
FIG. 10 is a flowchart of implementing a multiplexing transmission indication when telepresence endpoints send capability set messages according to an examplary implementation mode of the present disclosure;
FIG. 11 is a flowchart of performing mapping when telepresence endpoints send a capability set message according to an examplary implementation mode of the present disclosure;
FIG. 12 is a flowchart of performing mapping when telepresence endpoints send an open logical channel message according to an examplary implementation mode of the present disclosure;
FIG. 13 is a flowchart of implementing an indication 1 when H.323-based telepresence endpoints send a call message according to an examplary implementation mode of the present disclosure;
FIG. 14 is a flowchart of implementing an indication 2 when H.323-based telepresence endpoints send a call message according to an examplary implementation mode of the present disclosure;
FIG. 15 is a flowchart of implementing an indication 1 when H.323-based telepresence endpoints adopt a Generic Extensible Framework (GEF) according to an examplary implementation mode of the present disclosure;
FIG. 16 is a flowchart of implementing an indication 2 when H.323-based telepresence endpoints adopt a GEF according to an examplary implementation mode of the present disclosure;
FIG. 17 is a flowchart of implementing an indication when H.323-based telepresence endpoints send a terminal capability set message according to an examplary implementation mode of the present disclosure;
FIG. 18 is a flowchart of implementing an indication when H.323-based telepresence endpoints adopt a generic parameter according to an examplary implementation mode of the present disclosure;
FIG. 19 is a flowchart of implementing an indication 1 when Session Initiation Protocol (SIP)-based telepresence endpoints adopt an offer/answer model according to an examplary implementation mode of the present disclosure;
FIG. 20 is a flowchart of implementing an indication 2 when SIP-based telepresence endpoints adopt an offer/answer model according to an examplary implementation mode of the present disclosure;
FIG. 21 is a flowchart of performing mapping of a telepresence terminal in a terminal capability set message according to an examplary implementation mode of the present disclosure;
FIG. 22 is a flowchart of performing mapping of a telepresence terminal in a CLUE message according to an examplary implementation mode of the present disclosure;
FIG. 23 is a flowchart of performing mapping of a telepresence terminal in an offer/answer model message according to an examplary implementation mode of the present disclosure;
FIG. 24 is a flowchart of performing mapping of a telepresence terminal during opening of a logical channel according to an examplary implementation mode of the present disclosure; and
FIG. 25 is a flowchart of performing mapping of a telepresence terminal during reopening of a logical channel according to an examplary implementation mode of the present disclosure.
 DETAILED DESCRIPTION OF THE EMBODIMENTS
The present disclosure is described below with reference to the drawings and the embodiments in detail. It is important to note that the embodiments of the present disclosure and the characteristics in the embodiments can be combined when there is no conflict.
The present disclosure is described below with reference to the drawings and the embodiments in detail. It is important to note that the embodiments of the present disclosure and the characteristics in the embodiments can be combined when there is no conflict.
In the embodiment, a method for exchanging endpoint information is provided. FIG. 1 is a flowchart of a method for exchanging endpoint information according to an embodiment of the present disclosure. As shown in FIG. 1, the flow includes the steps as follows.
Step S102: telepresence endpoints exchange multiplexing information.
By means of the step, the telepresence endpoints exchange the multiplexing information, compared with in the related art the adoption of a traditional media stream transmission mode instead of the exchange of the multiplexing information, which meets requirements of a telepresence system for a multiplexing transmission mode, and enables the telepresence endpoints be able to obtain the multiplexing information of opposite ends in time; and multiplexing media stream transmission is performed according to the exchanged multiplexing information, the smoothness of multiplexing is improved.
It is important to note that the multiplexing information may comprise at least one of: multiplexing indication information used for indicating whether a telepresence endpoint adopts multiplexing; multiplexing type information used for indicating a multiplexing type by which multipath mapping information is exchanged; and the multiplexing mapping information used for describing a mapping relationship between a media capture code stream and a transmission code stream.
The telepresence endpoints can exchange the multiplexing indication information in the multiplexing information in multiple processing manner. For example, the telepresence endpoints exchange the multiplexing indication information in at least one of the manner as follows. For example, the telepresence endpoints exchange the multiplexing indication information when the telepresence endpoints are exchanging a terminal capability set. For another example, the telepresence endpoints exchange the multiplexing indication information when the telepresence endpoints are setting up a call.
The telepresence endpoints can exchange the multiplexing type information in the multiplexing information in multiple processing manner. For example, the telepresence endpoints can exchange the multiplexing type information in at least one of the manner as follows. For example, the telepresence endpoints exchange the multiplexing type information when the telepresence endpoints are exchanging a terminal capability set. For another example, the telepresence endpoints exchange the multiplexing mode information when the telepresence endpoints are setting up a call.
The telepresence endpoints may exchange the multiplexing mapping information in the multiplexing information in multiple processing manners. For example, the telepresence endpoints can exchange the multiplexing mapping information in at least one of the modes as follows. For example, in a signalling exchange process, the telepresence endpoints exchange the multiplexing mapping information by carrying the multiplexing mapping information in signalling information; and when transmitting a media stream, the telepresence endpoints exchange the multiplexing mapping information by carrying the multiplexing mapping information at an extended header of the transmitting media stream.
In an exemplary embodiment, after the telepresence endpoints exchange the multiplexing information, the flow can further comprise that: multiplexing transmission is performed on a media stream according to a result of exchanging the multiplexing information.
In the embodiment, a device for exchanging endpoint information is further provided. The device is configured to realize the embodiments and the examplary implementation modes which have been explained without detailed descriptions. Just as a term ‘component’ used below, the combination of software and/or hardware with predetermined functions can be realized. Although the device described by the following embodiment is better realized by the software, the realization of the hardware and the combination of the software and the hardware may be possible and may be constructed.
FIG. 2 is a structure block diagram of a device for exchanging endpoint information according to an embodiment of the present disclosure. As shown in FIG. 2, the device for exchanging endpoint information 20 includes an exchanging component 22, and the exchanging component 22 is described below.
The exchanging component 22 is configured to exchange multiplexing information between the telepresence endpoints.
FIG. 3 is a first examplary structure block diagram of the exchanging component 22 in the device for exchanging endpoint information according to an embodiment of the present disclosure. As shown in FIG. 3, the exchanging component 22 comprises at least one of: a first exchanging element 32 and a second exchanging element 34, and the exchanging component 22 is described below.
The first exchanging element 32 is configured to exchange multiplexing indication information comprised in the multiplexing information when exchanging a terminal capability set; and the second exchanging element 34 is configured to exchange multiplexing indication information comprised in the multiplexing information when setting up a call.
FIG. 4 is a second examplary structure block diagram of the exchanging component 22 in the device for exchanging endpoint information according to an embodiment of the present disclosure. As shown in FIG. 4, the exchanging component 22 comprises at least one of: a third exchanging element 42 and a fourth exchanging element 44, and the exchanging component 22 is described below.
The third exchanging element 42 is configured to exchange multiplexing type information comprised in the multiplexing information when exchanging a terminal capability set; and the fourth exchanging element 44 is configured to exchange multiplexing type information comprised in the multiplexing information when setting up a call.
FIG. 5 is a third examplary structure block diagram of the exchanging component 22 in the device for exchanging endpoint information according to an embodiment of the present disclosure. As shown in FIG. 5, the exchanging component 22 comprises at least one of: a fifth exchanging element 52 and a sixth exchanging element 54, and the exchanging component 22 is described below.
The fifth exchanging element 52 is configured to, in a signalling exchange process, exchange multiplexing mapping information by carrying the multiplexing mapping information in signalling information; and the sixth exchanging element 54 is configured to, when transmitting a media stream, exchange the multiplexing mapping information by carrying the multiplexing mapping information at an extended header of the transmitting media stream.
FIG. 6 is an examplary structure block diagram of the device for exchanging endpoint information according to an embodiment of the present disclosure. As shown in FIG. 6, the device further comprises a transmitting component 62 in addition to all the components shown in FIG. 2, and the transmitting component 62 is described below.
The transmitting component 62 is connected to the exchanging component 22 and is configured to perform multiplexing transmission on a media stream according to a result of exchanging the multiplexing information.
FIG. 7 is a structure block diagram of a telepresence endpoint according to an embodiment of the present disclosure. As shown in FIG. 7, the telepresence endpoint 70 comprises the device for exchanging endpoint information 20 according to any one of the content mentioned above.
The examplary implementation modes of the present disclosure are described below with reference to the drawings.
For solving the problem in the related art, in the embodiment, on the basis of a conventional protocol, a method for carrying multiplexing transmission information in a telepresence system is proposed. The method comprises that: telepresence endpoints exchange multiplexing transmission indication (which is a part of the above mentioned multiplexing information).
When a telepresence endpoint transmits media stream by multiplexing, a multiplexing transmission indication needs to be given during message exchange. FIG. 8 is a flowchart of implementing the multiplexing transmission indication when the telepresence endpoints perform message exchange according to an examplary implementation mode of the present disclosure. As shown in FIG. 8, a terminal A and a terminal B are the telepresence endpoints, a multiplexing transmission indication is given when message exchange is performed between the telepresence endpoint A and the telepresence endpoint B, and actual media stream transmission is performed between the two telepresence endpoints after the multiplexing transmission indication is exchanged.
FIG. 9 is a flowchart of implementing the multiplexing transmission indication when the telepresence endpoints send a call message according to an examplary implementation mode of the present disclosure. As shown in FIG. 9, the terminal A and the terminal B are the telepresence endpoints, and the telepresence endpoint A and the telepresence endpoint B give the multiplexing transmission indications in a call message by using an H.323 GEF. A sending end can give the multiplexing transmission indication in a setup message, and a receiving end can give the multiplexing transmission indication in an altering or connect message. When the multiplexing transmission indications are supported by the GEF, intermediate devices such as a Gate Keeper (GK) need to support the GEF, besides the terminals support the GEF.
FIG. 10 is a flowchart of implementing a multiplexing transmission indication when telepresence endpoints send capability set messages according to an examplary implementation mode of the present disclosure. As shown in FIG. 10, the terminal A and the terminal B are the telepresence endpoints, and the telepresence endpoint A and the telepresence endpoint B can give the multiplexing transmission indications in terminal capability set messages: TerminalCapabilitySet or an offer/answer model message.
The multiplexing transmission indication of the telepresence endpoints comprises clear indicating using of multiplexing and/or indicating a multiplexing type.
When there is a lack of the multiplexing transmission indication of the telepresence endpoints, multiplexing transmission will not be adopted.
The telepresence endpoints need to describe mapping of multiplexing. The telepresence endpoints need to describe mapping from a media capture code stream to a Real-time Transport Protocol (RTP) stream.
FIG. 11 is a flowchart of performing mapping when telepresence endpoints send a capability set message according to an examplary implementation mode of the present disclosure. As shown in FIG. 11, in a first mapping mode, the terminal A and the terminal B are the telepresence endpoints, and the telepresence endpoint A and the telepresence endpoint B can perform mapping in at least one of messages: the terminal capability set message TerminalCapabilitySet, and the offer/answer model message in a CLUE message.
FIG. 12 is a flowchart of performing mapping when telepresence endpoints send an open logical channel message according to an examplary implementation mode of the present disclosure. As shown in FIG. 12, in a second mapping mode, the terminal A and the terminal B are the telepresence endpoints, and the telepresence endpoint A and the telepresence endpoint B perform mapping during opening or reopening of a logical channel.
The examplary implementation modes of the present disclosure are described below with reference to the drawings.
A substantial flow of completing a media call via the terminals may comprise: a call flow, a capability set exchange flow, a media stream transmission channel preparation (logical channel opening) flow and an actual media stream transmission flow.
Exemplary implementation mode 1: H.323-based telepresence endpoints give indications when sending a call message
When the H.323-based telepresence endpoints send the call message, the sending end can give an indication in a Setup message, and the receiving end can give an indication in an Altering or Connect message.
By means of the method, the multiplexing transmission indication will be given in the call message by the terminals, and opposite ends are informed as soon as possible of that the media stream will be transmitted in a multiplexing mode. When the method is adopted, and a message passes through the GateKeeper (GK), the indication parts may be altered or deleted by the GK.
FIG. 13 is a flowchart of implementing an indication 1 when H.323-based telepresence endpoints send a call message according to an examplary implementation mode of the present disclosure. As shown in FIG. 13, the terminal A and the terminal B are the telepresence endpoints, the terminal A sends the Setup message to the terminal B, wherein a multiplexing indication is carried in the Setup message; after receiving the Setup message, the terminal B determines, by analysis, that the terminal A will transmit the media stream by multiplexing; after sending a Call proceeding message to the terminal A, the terminal B sends the Altering message carrying the multiplexing indication to the terminal A; and after receiving the Altering message, the terminal A determines, by analysis, that the terminal B will transmit the media stream in the multiplexing manner; and the terminal B sends the Connect message to the terminal A.
FIG. 14 is a flowchart of implementing an indication 2 when H.323-based telepresence endpoints send a call message according to an examplary implementation mode of the present disclosure. As shown in FIG. 14, the terminal A and the terminal B are the telepresence endpoints, the terminal A sends the Setup message to the terminal B, wherein the multiplexing indication is carried in the Setup message; and after receiving the Setup message, the terminal B determines, by analysis, that the terminal A will transmit the media stream by multiplexing; after sending the Call proceeding message and the Altering message to the terminal A, the terminal B sends the Connect message carrying the multiplexing indication to the terminal A; and after receiving the Connect message, the terminal A determines, by analysis, that the terminal B will transmit the media stream in the multiplexing manner.
FIG. 15 is a flowchart of implementing an indication 1 when H.323-based telepresence endpoints adopt a GEF according to an examplary implementation mode of the present disclosure. FIG. 16 is a flowchart of implementing an indication 2 when H.323-based telepresence endpoints adopt a GEF according to an examplary implementation mode of the present disclosure. As shown in FIG. 15 and FIG. 16, the terminal A and the terminal B are the telepresence endpoints, the telepresence sending terminals (the telepresence endpoint A and the telepresence endpoint B) can give indications by using parameters (neededFeatures or desiredFeatures) in the Setup message, and telepresence receiving terminals can give indications by using a supportedFeatures message in the Altering or Connect message.
Exemplary implementation mode 2: the H.323-based telepresence endpoints give indications when sending a terminal capability set
By means of the method, a conventional protocol stack can be completely multiplexed, and a call flow does not need to be involved when the multiplexing transmission indication of the terminals is altered.
FIG. 17 is a flowchart of implementing an indication when H.323-based telepresence endpoints send a terminal capability set message according to an examplary implementation mode of the present disclosure. As shown in FIG. 17, the terminal A and the terminal B are the telepresence endpoints. The terminal A sends the terminal capability set message (TerminalCapabilitySet) carrying the multiplexing indication of the telepresence endpoints to the terminal B; after the terminal B receives the message sent by the terminal A, it is parsed that the multiplexing indication exists, so as to determine that the terminal A will transmit the media stream by multiplexing and a multiplexing transmission type is substantially described; the terminal B sends a terminal capability set response message (TerminalCapabilitySetAck) to the terminal A; the terminal B sends the terminal capability set message (TerminalCapabilitySet) carrying the multiplexing indication to the terminal A; after the terminal A receives the message sent by the terminal B, it is parsed that the multiplexing indication exists, so as to determine that the terminal B will adopt the multiplexing transmission mode and the multiplexing transmission type is substantially described; and the terminal A sends the terminal capability set response message (TerminalCapabilitySetAck) to the terminal B.
FIG. 18 is a flowchart of implementing an indication when H.323-based telepresence endpoints adopt a generic parameter according to an examplary implementation mode of the present disclosure. As shown in FIG. 18, the terminal A and the terminal B are the telepresence endpoints. The multiplexing indication can be given between the terminals in the terminal capability set message by using the generic parameter. In FIG. 18, the multiplexing parameter relates to supporting or not of multiplexing (multiplexTransfer) and the type of multiplexing (multiplexTransferType). When the terminals decide to adopt multiplexing, fields for judging whether to support multiplexing can be omitted, and the multiplexing indication is given only by the multiplexing type. The receiving end parses multiplexing type fields, and it is represented that the sending end supports multiplexing. When the terminals do not adopt multiplexing, a value of multiplexTransfer can be set to be false or the multiplexing indication is not carried.
When there is a lack of the multiplexing indication in the capability set message, it is represented that the media stream is transmitted in a non-multiplexing mode, namely one transmission address is used for transmitting one path of media stream.
Exemplary implementation mode 3: SIP-based telepresence endpoints given indications in an offer/answer model message
FIG. 19 is a flowchart of implementing an indication 1 when SIP-based telepresence endpoints adopt an offer/answer model message according to an examplary implementation mode of the present disclosure. As shown in FIG. 19, the SIP-based telepresence endpoints give the multiplexing indication in the offer/answer model message by using two pairs of messages. The terminal A and the terminal B are the telepresence endpoints. The terminal A sends an offer message carrying the multiplexing indication to the terminal B, and the terminal B parses the message to determine that the terminal A will send the media stream in the multiplexing manner. The terminal B returns an answer message to the terminal A. The terminal B sends an offer message carrying the multiplexing indication to the terminal A, and the terminal A parses the message to determine that the terminal B will also send the media stream in the multiplexing manner. The terminal A returns an answer message to the terminal B.
FIG. 20 is a flowchart of implementing an indication 2 when SIP-based telepresence endpoints adopt an offer/answer model according to an examplary implementation mode of the present disclosure. As shown in FIG. 20, the SIP-based telepresence endpoints give the multiplexing indication in the offer/answer model message by using a pair of messages. The terminal A and the terminal B are the telepresence endpoints. The terminal A sends an offer message carrying the multiplexing indication to the terminal B, and the terminal B parses the message to determine that the terminal A will send the media stream in the multiplexing mode. The terminal B sends an answer message carrying the multiplexing indication to the terminal A, and the terminal A parses the message to determine that the terminal B will also send the media stream in the multiplexing mode.
Exemplary implementation mode 4: the telepresence endpoints perform mapping in the terminal capability set message TerminalCapabilitySet
After it is determined that multiplexing (multiplexing indication) and multiplexing types are adopted, a multiplexing mapping type can comprise static mapping, dynamic mapping and comprehensive mapping.
the static mapping refers to that, during the signalling exchange process, a mapping relationship between the RTP stream and the media capture code stream, such as a mapping relationship between an identifier of the RTP stream and an identifier of the media capture code stream, is carried in a message. The identifier of the RTP stream can be used for uniquely identifying one path of RTP stream by using a Synchronous Source (SSRC), and the identifier of the media capture code stream can be used for uniquely identifying one path of media capture code stream by using a captureID (media capture ID) and an encodingID (the coding ID used for coding this path of captureID); or a new field such as a media capture code stream identifier (demultiplexID) is adopted to identify one path of media capture code stream, and a corresponding relationship exists between the demultiplexID and the captureID, the encodingID substantially. In a static mapping mode, the mapping relationship is informed only in signalling exchange, an RTP header field in an actual media stream does not need to be extended for mapping, and the steps of receiving an RTP media stream by the terminals are not changed.
During the dynamic mapping, mapping between the RTP stream and the media capture code stream are not described in a signalling. When a new field demultiplexID is adopted to describe the media capture code stream, a mapping relationship between the demultiplexID and the captureID, the encodingID is exchanged in the signalling; and when the captureID and the encodingID are adopted to describe the media capture code stream, the new field is not adopted to describe the media capture code stream, and any mapping does not need to be carried in the signalling. During dynamic mapping, an RTP header needs to be extended by the terminals, the identifier of the media capture code stream (demultiplexID or captureID, encodingID) is filled, and the terminals need to parse an extended part of the header of the RTP stream, so as to dynamically obtain the mapping relationship between the media capture code stream and the RTP stream.
The comprehensive mapping is the combination of the static mapping and the dynamic mapping. The mapping relationship between the RTP stream and the media capture code stream is described in signalling exchange, the RTP header is also extended, and the identifier of the media capture code stream is carried in the extended header. For example, the receiving end expects the sending end to send the media capture code stream (captureID=1 and encodingID=1) to the receiving end, and a static mapping relationship that the RTP stream (SSRC=1) corresponds to the media capture code stream (captureID=1 and encodingID=1) is known. In addition to the maintenance of the static mapping relationship, the sending end extends a mapping field at the header of the RTP stream (SSRC=1), and fills captureID=1 and encodingID=1. Under common conditions, the terminals parse each RTP stream according to the static mapping relationship, and after the receiving end receives multiple paths of RTP streams, the needed multiple paths of streams can be processed according to the maintained static relationship between the RTP stream (SSRC=1) and the media capture code stream (captureID=1 and encodingID=1). Under special conditions such as that a static mapping maintenance table is lost or there is a mistake in the static mapping maintenance contents, multiple paths of received streams can be processed in a dynamic mapping manner, the extended part of the header of the RTP stream of each path of stream is parsed to obtain the captureID and the encodingID corresponding to each path of stream, and the selected media capture code stream captureID and encodingID corresponding to a certain path of RTP stream can be determined.
Next, how to map in the terminal capability set message TerminalCapabilitySet by the telepresence endpoints is introduced. FIG. 21 is a flowchart of performing mapping of a telepresence terminal in a terminal capability set message according to an examplary implementation mode of the present disclosure. As shown in FIG. 21, the terminal A and the terminal B are the telepresence endpoints, the terminal A sends a TerminalCapabilitySet message carrying a mapping relationship to the terminal B, and the terminal B receives and maintains the mapping relationship; the terminal B sends ACK to the terminal A; the terminal B sends the TerminalCapabilitySet message carrying the mapping relationship to the terminal A, and the terminal A receives and maintains the mapping relationship; and the terminal A sends ACK to the terminal B.
Exemplary implementation mode 5: the telepresence endpoints perform mapping in the CLUE message
FIG. 22 is a flowchart of performing mapping of a telepresence terminal in a CLUE message according to an examplary implementation mode of the present disclosure. As shown in FIG. 22, when the terminals exchange a capability set by using the CLUE message based on a CLUE channel, the telepresence endpoints can perform mapping in the CLUE message. The terminal A and the terminal B are the telepresence endpoints. The terminal A sends an advertisement message (advertisement) to the terminal B, wherein the advertisement message comprises all media capture streams information and encoding information capable of being provided by the terminal A; the terminal B selects two of multiple paths of stream, associates a field (demultiplexID) with a captureID (VC) and an encodingID (ENC), and then sends to the terminal A in a configuration message (configure); after the terminal A receives the configuration message, the demultiplexID is adopted as an extended header of each path of RTP stream, and after the terminal B receives the RTP stream, the extended header can be parsed to obtain a needed mapping relationship. The process of sending the advertisement message to the terminal A by the terminal B and the process of sending the configuration message to the terminal B by the terminal A are consistent to the abovementioned process without repetition.
Exemplary implementation mode 6: the telepresence endpoints perform mapping in the offer/answer model message
FIG. 23 is a flowchart of performing mapping of a telepresence terminal in an offer/answer model message according to an examplary implementation mode of the present disclosure. As shown in FIG. 23, the terminal A and the terminal B are the telepresence endpoints, and mapping is performed in the offer/answer model message. The carrier of an offer/answer model generally adopts, but not limited to, an invite/200 OK message. The terminal A sends an offer message carrying multiplexing mapping to the terminal B, and after receiving the offer message, the terminal B maintains a mapping relationship. The terminal B sends an answer message to the terminal A. The process of sending the message to the terminal A by the terminal B is consistent to the abovementioned process without repetition.
Exemplary implementation mode 7: the telepresence endpoints perform mapping during opening of a logical channel
FIG. 24 is a flowchart of performing mapping of a telepresence terminal during opening of a logical channel according to an examplary implementation mode of the present disclosure. As shown in FIG. 24, the telepresence endpoints perform mapping from the media capture code stream to the RTP stream during the opening of the logical channel. The terminal A and the terminal B are the telepresence endpoints, the terminal A sends an OpenLogicalChannel (OLC) message carrying a mapping relationship to the terminal B, and the mapping relationship is borne by using a generic parameter field in a generic message in an OLC. The terminal B returns an open logical channel response message to the terminal A. The terminal B sends the OLC message carrying the mapping relationship to the terminal A. The terminal A returns a response to the terminal B.
Exemplary implementation mode 8: the telepresence endpoints perform mapping during reopening of the logical channel
FIG. 25 is a flowchart of performing mapping of a telepresence terminal during reopening of a logical channel according to an examplary implementation mode of the present disclosure. As shown in FIG. 25, the telepresence endpoints perform mapping during reopening of the logical channel. The terminal A and the terminal B are the telepresence endpoints. A conventional logical channel between the terminal A and the terminal B is closed firstly, and then a new logical channel is opened. The terminal A sends an OLC message carrying a mapping relationship to the terminal B. The terminal B returns an open logical channel response message to the terminal A. The terminal B sends a OLC message carrying the mapping relationship to the terminal A. The terminal A returns an open logical channel response to the terminal B.
Obviously, those skilled in the art should understand that all modules or all steps in the present disclosure can be realized by using a generic computation device, can be centralized on a single computation device or can be distributed on a network composed of a plurality of computation devices. Optionally, they can be realized by using executable program codes of the computation devices, so that they can be stored in a storage device and executed by the computation devices, the shown or described steps can be executed in a sequence different from this sequence under certain conditions, or they are manufactured into each integrated circuit module respectively, or a plurality of modules or steps therein are manufactured into a single integrated circuit module. Thus, the present disclosure is not limited to combination of any specific hardware and software.
The above is only the examplary embodiments of the present disclosure, and is not intended to limit the present disclosure. There can be various modifications and variations in the present disclosure for those skilled in the art. Any modifications, equivalent replacements, improvements and the like within the spirit and principle of the present disclosure shall fall within the protection scope of the present disclosure.
INDUSTRIAL APPLICABILITY
As mentioned above, the method and device for exchanging endpoint information and the telepresence endpoint provided by the embodiments of the present disclosure can bring the following beneficial effects that: the problem in the related art that there are too many ports and multiplexing transmission is unsmooth due to the fact that the multiplexing transmission mode of the traditional session system is still adopted in the telepresence system based on the conventional protocol architecture is solved, and the effect of exchanging the multiplexing information between the telepresence endpoints and therefore multiplexing can be successfully performed in the telepresence system is further achieved.

Claims (17)

What is claimed is:
1. A method for exchanging endpoint information, comprising:
telepresence endpoints exchanging multiplexing information:
wherein the multiplexing information comprises multiplexing mapping information used for describing a mapping relationship between a media capture code stream and a transmission code stream;
wherein the telepresence endpoints exchange the multiplexing mapping information in at least one of the following manners: in a signalling exchange process, the telepresence endpoints exchanging the multiplexing mapping information by carrying the multiplexing mapping information in signalling information; and when transmitting a media stream, the telepresence endpoints exchanging the multiplexing mapping information by carrying the multiplexing mapping information at an extended header of the transmitting media stream.
2. The method as claimed in claim 1, wherein the multiplexing information further comprises at least one of:
multiplexing indication information used for indicating whether a telepresence endpoint adopts multiplexing; and
multiplexing type information used for indicating a multiplexing type by which the multiplexing mapping information is exchanged.
3. The method as claimed in claim 2, wherein the telepresence endpoints exchange the multiplexing indication information in at least one of following manners:
the telepresence endpoints exchanging the multiplexing indication information when the telepresence endpoints are exchanging a terminal capability set; and
the telepresence endpoints exchanging the multiplexing indication information when the telepresence endpoints are setting up a call.
4. The method as claimed in claim 2, wherein the telepresence endpoints exchange the multiplexing type information in at least one of following manners:
the telepresence endpoints exchanging the multiplexing type information when the telepresence endpoints are exchanging a terminal capability set; and
the telepresence endpoints exchanging the multiplexing type information when the telepresence endpoints are setting a call.
5. The method as claimed in claim 1, after the telepresence endpoints exchanging the multiplexing information, the method further comprising:
performing multiplexing transmission on a media stream according to a result of exchanging the multiplexing information.
6. A device for exchanging endpoint information, applicable to telepresence endpoints, comprising:
an exchanging component, configured to exchange multiplexing information:
wherein the multiplexing information comprises multiplexing mapping information used for describing a mapping relationship between a media capture code stream and a transmission code stream;
wherein the exchanging component comprises at least one of: a fifth exchanging element, configured to, in a signalling exchange process, exchange multiplexing mapping information by carrying the multiplexing mapping information in signalling information; and a sixth exchanging element, configured to, when transmitting a media stream, exchange the multiplexing mapping information by carrying the multiplexing mapping information at an extended header of the transmitting media stream.
7. The device as claimed in claim 6, wherein the exchanging component comprises at least one of:
a first exchanging element, configured to exchange multiplexing indication information comprised in the multiplexing information when exchanging a terminal capability set; and
a second exchanging element, configured to exchange multiplexing indication information comprised in the multiplexing information when setting up a call.
8. The device as claimed in claim 6, wherein the exchanging component comprises at least one of:
a third exchanging element, configured to exchange multiplexing type information comprised in the multiplexing information when exchanging a terminal capability set; and
a fourth exchanging element, configured to exchange multiplexing type information comprised in the multiplexing information when setting up a call.
9. The device as claimed in claim 6, further comprising:
a transmitting component, configured to perform multiplexing transmission on a media stream according to a result of exchanging the multiplexing information.
10. A telepresence endpoint, comprising the device as claimed in claim 6.
11. The method as claimed in claim 2, after the telepresence endpoints exchanging the multiplexing information, the method further comprising:
performing multiplexing transmission on a media stream according to a result of exchanging the multiplexing information.
12. The method as claimed in claim 3, after the telepresence endpoints exchanging the multiplexing information, the method further comprising:
performing multiplexing transmission on a media stream according to a result of exchanging the multiplexing information.
13. The method as claimed in claim 4, after the telepresence endpoints exchanging the multiplexing information, the method further comprising:
performing multiplexing transmission on a media stream according to a result of exchanging the multiplexing information.
14. The method of as claimed in claim 1, after the telepresence endpoints exchanging the multiplexing information, the method further comprising:
performing multiplexing transmission on a media stream according to a result of exchanging the multiplexing information.
15. The device as claimed in claim 7, further comprising:
a transmitting component, configured to perform multiplexing transmission on a media stream according to a result of exchanging the multiplexing information.
16. The device as claimed in claim 8, further comprising:
a transmitting component, configured to perform multiplexing transmission on a media stream according to a result of exchanging the multiplexing information.
17. The device as claimed in claim 6, further comprising:
a transmitting component, configured to perform multiplexing transmission on a media stream according to a result of exchanging the multiplexing information.
US15/025,686 2013-09-29 2014-04-21 Method and device for exchanging endpoint information, and telepresence endpoint Active 2035-01-23 US10356141B2 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201310455367 2013-09-29
CN201310455367.8A CN104519304B (en) 2013-09-29 2013-09-29 Terminal point information interaction processing method, device and endpoint is remotely presented
CN201310455367.8 2013-09-29
PCT/CN2014/075844 WO2015043170A1 (en) 2013-09-29 2014-04-21 Endpoint information interaction processing method, apparatus and telepresence endpoint

Publications (2)

Publication Number Publication Date
US20160234270A1 US20160234270A1 (en) 2016-08-11
US10356141B2 true US10356141B2 (en) 2019-07-16

Family

ID=52741942

Family Applications (1)

Application Number Title Priority Date Filing Date
US15/025,686 Active 2035-01-23 US10356141B2 (en) 2013-09-29 2014-04-21 Method and device for exchanging endpoint information, and telepresence endpoint

Country Status (5)

Country Link
US (1) US10356141B2 (en)
EP (1) EP3051805B1 (en)
JP (1) JP2016540454A (en)
CN (1) CN104519304B (en)
WO (1) WO2015043170A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180316732A1 (en) * 2015-11-09 2018-11-01 Nokia Solutions And Networks Oy Enhanced media plane optimization in web real time communication scenarios

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105530223B (en) * 2014-09-29 2019-08-30 中兴通讯股份有限公司 The configuration method and device of end-point capability collection
US10050870B2 (en) * 2016-02-02 2018-08-14 Cisco Technology, Inc. Handling multipath flows in service function chaining

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5812534A (en) 1993-01-08 1998-09-22 Multi-Tech Systems, Inc. Voice over data conferencing for a computer-based personal communications system
US5815234A (en) * 1997-03-07 1998-09-29 Dileo; Frank Apparatus and method for viewing a surface through a mirror
CN1290107A (en) 1999-12-18 2001-04-04 深圳市中兴通讯股份有限公司 Method for implementing picture-in-picture mode at remote end
US20040174817A1 (en) * 2002-12-12 2004-09-09 Dilithium Networks Pty Ltd. Methods and system for fast session establishment between equipment using H.324 and related telecommunications protocols
JP2005057362A (en) 2003-08-07 2005-03-03 Renesas Technology Corp Transmitting/receiving and recording system for voice and picture
US20060034332A1 (en) * 2004-07-27 2006-02-16 Kenichi Haga Multiplexed transmission system, multiplexed transmission apparatus, its program and recording medium
WO2006066454A1 (en) 2004-12-22 2006-06-29 Zte Corporation A method for transmitting the multichannel video sources on video conferencing system
US20070058794A1 (en) * 2004-07-15 2007-03-15 Nischal Abrol Method and apparatus for performing call setup for a video call in 3G-324M
US20070297352A1 (en) * 2002-12-12 2007-12-27 Dilithium Networks Pty Ltd. Methods and apparatus for combining session acceleration techniques for media oriented negotiation acceleration
US20080266377A1 (en) * 2004-10-22 2008-10-30 Sk Telecom Co., Ltd. Video Telephony Service Method in Mobile Communication Network
CN101374330A (en) 2007-08-20 2009-02-25 华为技术有限公司 Video intercommunication gateway equipment, system and method for implementing video call business
US20140139618A1 (en) * 2011-07-08 2014-05-22 Zte Corporation Media transmission method and system based on telepresence
US20140333712A1 (en) * 2004-10-22 2014-11-13 Sk Telecom Co., Lto. Video telephony service method in mobile communication network
US20160277246A1 (en) * 2013-11-27 2016-09-22 Huawei Technologies Co., Ltd. Method and device for media multiplexing negotiation

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4704106B2 (en) * 2005-05-27 2011-06-15 アルパイン株式会社 Videophone device and videophone system
JP4818309B2 (en) * 2008-04-21 2011-11-16 富士通東芝モバイルコミュニケーションズ株式会社 Video phone terminal
KR101589524B1 (en) * 2008-11-07 2016-01-29 삼성전자주식회사 Apparatus and method for providing high quality video service on video telephony using the multiple video format in mobile communication terminal

Patent Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5812534A (en) 1993-01-08 1998-09-22 Multi-Tech Systems, Inc. Voice over data conferencing for a computer-based personal communications system
US5815234A (en) * 1997-03-07 1998-09-29 Dileo; Frank Apparatus and method for viewing a surface through a mirror
CN1290107A (en) 1999-12-18 2001-04-04 深圳市中兴通讯股份有限公司 Method for implementing picture-in-picture mode at remote end
US20040174817A1 (en) * 2002-12-12 2004-09-09 Dilithium Networks Pty Ltd. Methods and system for fast session establishment between equipment using H.324 and related telecommunications protocols
US20070297352A1 (en) * 2002-12-12 2007-12-27 Dilithium Networks Pty Ltd. Methods and apparatus for combining session acceleration techniques for media oriented negotiation acceleration
JP2005057362A (en) 2003-08-07 2005-03-03 Renesas Technology Corp Transmitting/receiving and recording system for voice and picture
CN101015189A (en) 2004-07-15 2007-08-08 高通股份有限公司 Method and apparatus for performing call setup for a video call in 3g-324m
US20070058794A1 (en) * 2004-07-15 2007-03-15 Nischal Abrol Method and apparatus for performing call setup for a video call in 3G-324M
US20060034332A1 (en) * 2004-07-27 2006-02-16 Kenichi Haga Multiplexed transmission system, multiplexed transmission apparatus, its program and recording medium
US20080266377A1 (en) * 2004-10-22 2008-10-30 Sk Telecom Co., Ltd. Video Telephony Service Method in Mobile Communication Network
US20140333712A1 (en) * 2004-10-22 2014-11-13 Sk Telecom Co., Lto. Video telephony service method in mobile communication network
WO2006066454A1 (en) 2004-12-22 2006-06-29 Zte Corporation A method for transmitting the multichannel video sources on video conferencing system
CN101374330A (en) 2007-08-20 2009-02-25 华为技术有限公司 Video intercommunication gateway equipment, system and method for implementing video call business
EP2114049A1 (en) * 2007-08-20 2009-11-04 Huawei Technologies Co., Ltd. Video inter-working gateway equipment, system and method for realizing video call service
US20140139618A1 (en) * 2011-07-08 2014-05-22 Zte Corporation Media transmission method and system based on telepresence
US20160277246A1 (en) * 2013-11-27 2016-09-22 Huawei Technologies Co., Ltd. Method and device for media multiplexing negotiation

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
E. IVOV JITSI E. MAROCCO TELECOM ITALIA P. THATCHER GOOGLE: "No Plan: Economical Use of the Offer/Answer Model in WebRTC Sessions with Multiple Media Sources; draft-ivov-rtcweb-noplan-01.txt", NO PLAN: ECONOMICAL USE OF THE OFFER/ANSWER MODEL IN WEBRTC SESSIONS WITH MULTIPLE MEDIA SOURCES; DRAFT-IVOV-RTCWEB-NOPLAN-01.TXT, INTERNET ENGINEERING TASK FORCE, IETF; STANDARDWORKINGDRAFT, INTERNET SOCIETY (ISOC) 4, RUE DES FALAISES CH- 1205 GENEV, draft-ivov-rtcweb-noplan-01, 17 June 2013 (2013-06-17), Internet Society (ISOC) 4, rue des Falaises CH- 1205 Geneva, Switzerland, pages 1 - 20, XP015090531
EP Search Report, dated Sep. 5, 2016, EP Application No. 14847689.8, 8 pages.
International Search Report for corresponding application PCT/CN2014/075844 filed on Apr. 21, 2014; dated Aug. 4, 2014.
Ivov Jitsi E Marocco Telecom Italia P Thatcher Google E: "No Plan: Economical Use of the Offer/Answer Model in WebRTC Sessions with Multiple Media Sources; draft-ivov-rtcweb-noplan-01.txt", draft-Ivov-Rtcweb-noplan-01.txt, Internet Engineering Task Force, IETF; Standardworkingdraft, Internet Society (ISOC) 4, Rue Des Falaises Ch-1205 Genev, Jun. 17, 2013, pp. 1-20, XP015090531, [retrieved on Jun. 17, 2013].

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180316732A1 (en) * 2015-11-09 2018-11-01 Nokia Solutions And Networks Oy Enhanced media plane optimization in web real time communication scenarios
US11310293B2 (en) * 2015-11-09 2022-04-19 Nokia Solutions And Networks Oy Enhanced media plane optimization in web real time communication scenarios

Also Published As

Publication number Publication date
EP3051805A4 (en) 2016-10-05
EP3051805A1 (en) 2016-08-03
CN104519304B (en) 2018-07-20
EP3051805B1 (en) 2019-03-06
CN104519304A (en) 2015-04-15
JP2016540454A (en) 2016-12-22
WO2015043170A1 (en) 2015-04-02
US20160234270A1 (en) 2016-08-11

Similar Documents

Publication Publication Date Title
US20200145466A1 (en) System and method for using software defined networking in internet protocol multimedia subsystems
US7881338B2 (en) Handling quality of service in a communication system
US20140115650A1 (en) Media data control method and apparatus
US10027496B2 (en) Method for distributing identifiers of multicast sources
US20070217430A1 (en) Method and system for initiating communications
CN101414950A (en) Method for address translation device traversal for sip signaling messages through temporary use of the TCP transport protocol
US10015097B2 (en) Fast access telecommunication tunnel cloning
US9332049B1 (en) Media compression for tunneled real-time communications
WO2019184262A1 (en) Multi-type media data network address translation traversing method, terminal and system
US20140164543A1 (en) Communication System, Application Server and Communication Method for Server Cooperation
US10356141B2 (en) Method and device for exchanging endpoint information, and telepresence endpoint
US8971311B2 (en) Methods, systems and computer readable media for supporting a plurality of real-time transport protocol (RTP) multiplexing enablement methods in a media gateway
US7948971B2 (en) Method and device for controlling media resources, method and system for establishing calls
US20050100047A1 (en) Method of reducing media relay of a network address translation apparatus
US7221384B2 (en) Method for operating a multimedia communications network
US9888208B2 (en) Method and apparatus for exchanging endpoint information, and telepresence endpoint
Manjur et al. Conference gateway for heterogeneous clients: Real time switching clients and interasterisk exchange clients
KR101502250B1 (en) Establishing a packet stream having symmetrical quality of service by means of the negotiation of the quality indicator
Daldal et al. Using web services for webrtc signaling interoperability
JP2010507296A (en) Method, system, and network entity for obtaining session description protocol capability information
CN107332815B (en) Method and device for establishing channel between heterogeneous endpoints
US11811843B2 (en) Supporting quality of service for media communications
US10171518B2 (en) Performing an action on certain media streams in a multimedia communications network
CN100461749C (en) Method for centralized distributing H.248 message
CN115277874A (en) IPv4/IPv6 protocol intercommunication method based on SIP protocol and related equipment

Legal Events

Date Code Title Description
AS Assignment

Owner name: ZTE CORPORATION, CHINA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WANG, LIANG;YE, XIAOYANG;REEL/FRAME:038126/0232

Effective date: 20160326

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4