Media Relay Server
US-2016380789-A1 · Dec 29, 2016 · US
US9917871B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9917871-B2 |
| Application number | US-201615090729-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 5, 2016 |
| Priority date | Apr 5, 2016 |
| Publication date | Mar 13, 2018 |
| Grant date | Mar 13, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In one embodiment, a first device in a network sends a Session Traversal Utilities for Network Address Translation (STUN) binding request towards an endpoint device of a media session between the first and endpoint devices. The binding request includes one or more network attribute fields. The first device receives a binding response from an intermediate node between the first and endpoint devices in the network, in response to sending the binding request towards the endpoint device. The intermediate node inserted the one or more network attribute fields into the binding response. The received binding response includes one or more metrics for the media session in the one or more network attribute fields. The first device adjusts one or more bitrates of the media session based on the one or more metrics for the media session in the received binding response.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: sending, by a first device in a network, a Session Traversal Utilities for Network Address Translation (STUN) binding request towards an endpoint device of a media session between the first and endpoint devices, wherein the binding request includes one or more network attribute fields; receiving, at the first device, a binding response from an intermediate node between the first and endpoint devices in the network, in response to sending the binding request towards the endpoint device, wherein the intermediate node inserted the one or more network attribute fields into the binding response, and wherein the received binding response comprises one or more metrics for the media session in the one or more network attribute fields; and adjusting, by the first device, one or more bitrates of the media session based on the one or more metrics for the media session in the received binding response. 2. The method as in claim 1 , wherein the one or more network attribute fields comprises at least one of: a stream type attribute for the media session, a bandwidth usage attribute for the media session, or a network status attribute for the media session. 3. The method as in claim 1 , wherein adjusting the one or more bitrates of the media session comprises: adjusting, by the first device, a transmit bitrate at which the first device sends traffic for the media session. 4. The method as in claim 1 , wherein adjusting the one or more bitrates of the media session comprises: sending, by the first device, a bitrate adjustment request to the endpoint device. 5. The method as in claim 4 , wherein the bitrate adjustment request comprises a Temporary Maximum Media Stream Bit Rate (TMMBR) request. 6. The method as in claim 1 , wherein the one or more network attribute fields comprise one or more Differentiated Priorities and Status Code-Points Using Stun Signaling (DISCUSS) fields. 7. The method as in claim 1 , wherein the received binding response comprises an indication that the one or more metrics for the media session were provided by the intermediate node instead of the endpoint device. 8. The method as in claim 1 , wherein the binding request comprises an indication that the intermediate node should insert the one or more network attribute fields into a binding response from the endpoint device, if the endpoint device does not support the one or more network attribute fields. 9. The method as in claim 1 , further comprising: cross-verifying, by the first device, the one or more metrics for the media session included in the binding response with information regarding the media session generated by a delay sensing mechanism. 10. The method as in claim 1 , further comprising: maintaining, by the first device, a STUN transaction for a period of time after receiving the binding response; and detecting, by the first device, a potential network attack based on receipt of a second binding response during the period of time. 11. A method, comprising: receiving, at an intermediate node along a network path for a media session between first and second endpoint devices, a binding response sent by the second endpoint device in response to receiving a Session Traversal Utilities for Network Address Translation (STUN) binding request from the first endpoint device; determining, by the intermediate node, that the binding response does not include the one or more network attribute fields included in the binding request; generating, by the intermediate node, a binding response that includes one or more metrics for the media session in the one or more network attribute fields, based on a determination that the binding response from the second endpoint device does not include the one or more metrics; and sending, by the intermediate node, the generated binding response to the first endpoint device. 12. The method as in claim 11 , further comprising: including, by the intermediate node, an indication in the generated binding response that the one or more metrics for the media session were provided by the intermediate node instead of the second endpoint device. 13. The method as in claim 12 , wherein the one or more network attribute fields comprise one or more Differentiated Priorities and Status Code-Points Using Stun Signaling (DISCUSS) fields. 14. The method as in claim 11 , wherein the generated binding response is generated based further in part on an indication in the binding request that the intermediate node should include the one or more network attribute fields in a binding response from the endpoint device if the second endpoint device does not support the one or more network attribute fields. 15. The method as in claim 11 , wherein the generated binding response is generated based further in part on a determination that a time to live (TTL) associated with the binding request has expired. 16. The method as in claim 11 , wherein intermediate node is a wireless access point or gateway, and wherein the generated binding response is generated based further in part on a determination that the first endpoint device is directly associated with the wireless access point or gateway. 17. An apparatus, comprising: one or more network interfaces to communicate with a network; a processor coupled to the network interfaces and adapted to execute one or more processes; and a memory configured to store a process executable by the processor, the process when executed operable to: send a Session Traversal Utilities for Network Address Translation (STUN) binding request towards an endpoint device of a media session between the apparatus and the endpoint device, wherein the binding request includes one or more network attribute fields; receive a binding response from an intermediate node between the apparatus and the endpoint device in the network, in response to sending the binding request towards the endpoint device, wherein the intermediate node inserted the one or more network attribute fields into the binding response, and, wherein the received binding response comprises one or more metrics for the media session in the one or more network attribute fields; and adjust one or more bitrates of the media session based on the one or more metrics for the media session in the received binding response. 18. The apparatus as in claim 17 , wherein the one or more network attribute fields comprise one or more Differentiated Priorities and Status Code-Points Using Stun Signaling (DISCUSS) fields. 19. The apparatus as in claim 18 , wherein the bitrate adjustment request comprises a Temporary Maximum Media Stream Bit Rate (TMMBR) request. 20. The apparatus as in claim 17 , wherein the binding request comprises an indication that the intermediate node should insert the one or more network attribute fields into a binding response from the endpoint device, if the endpoint device does not support the one or more network attribute fields.
using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN] · CPC title
Arrangements for multi-party communication, e.g. for conferences (data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15) · CPC title
Avoiding congestion; Recovering from congestion · CPC title
Electricity · mapped topic
Electricity · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.