Intermediate Networking Devices
US-2020107226-A1 · Apr 2, 2020 · US
US11196652B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11196652-B2 |
| Application number | US-201716483448-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 7, 2017 |
| Priority date | Feb 7, 2017 |
| Publication date | Dec 7, 2021 |
| Grant date | Dec 7, 2021 |
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.
The present disclosure is directed to aspects of assessing performance of a session between an OTT service provider endpoint and an OTT service recipient endpoint in regard of a particular OTT service. The performance assessment is based on a series of data records generated for the session. Data record generation includes monitoring, at a network site between the two endpoints and during successive periods of time, at least one transport layer connection of the session. The monitoring is performed to determine, for each period of time, an activity metric indicative of a pending transport layer activity of the session in the respective period of time. This activity metric is then evaluated in connection with service performance assessment.
Opening claim text (preview).
The invention claimed is: 1. A network entity for monitoring Over The Top (OTT) performance, the network entity comprising: processing circuitry; memory containing instructions executable by the processing circuitry whereby the network entity is operative to: monitor, at a network site between the two endpoints and during successive periods of time, at least one Transport Layer (TL) connection of the session, wherein the monitoring includes, for each period of time, determining for the at least one TL connection of the session at least one activity metric indicative of at least one pending TL activity of the session in the respective period of time; wherein the at least one pending TL activity is a TL messaging procedure in which one endpoint is presently waiting for at least one TL message from the other endpoint; wherein the at least one activity metric is indicative of at least one pendency period associated with the at least one pending TL activity of the session; and generate, for a period of time with at least one pending TL activity, a data record that includes the activity metric associated with that period of time. 2. The network entity of claim 1 , wherein the at least one TL message includes: an acknowledgement message from a receiving endpoint for a previously transmitted data unit; an acknowledgement message in a TL connection setup procedure; and/or a resumption message from a receiving endpoint having paused a data transfer for being busy processing one or more previously received data units. 3. The network entity of claim 1 : wherein the session comprises multiple pending TL activities in the respective period of time; and wherein the activity metric is indicative of the aggregated pendency periods of the multiple pending TL activities. 4. The network entity of claim 1 : wherein the session comprises multiple co-existing TL connections in a given period of time; wherein the instructions are such that the network entity is operative to aggregate pending TL activities in the given period of time across the multiple TL connections; and wherein the activity metric for the given period of time is indicative of the aggregated pending TL activities. 5. The network entity of claim 1 , wherein the data record is indicative of one or more activity metrics, wherein each activity metric is associated with a dedicated activity type. 6. The network entity of claim 5 , wherein the activity types include: a data transfer from the service provider endpoint to the service recipient endpoint; a data transfer from the service recipient endpoint to the service provider endpoint; a TL connection setup; a data transfer being paused by the service recipient endpoint for being busy processing one or more previously received data units; and/or a data transfer being paused by the service provider endpoint for being busy processing one or more previously received data units. 7. The network entity of claim 1 , wherein the activity metric included in the data record is indicative of a maximum acknowledgement delay for a transmitted data unit occurring during the period of time associated with that data record. 8. The network entity of claim 1 , wherein the data record includes a separate sub-record for: each individual pending TL activity occurring during the period of time associated with that data record; and if pending TL activities are grouped into activity types, each individual activity type occurring during the period of time associated with that data record. 9. The network entity of claim 1 , wherein the data record is indicative of a data volume transmitted during the period of time associated with that data record. 10. The network entity of claim 9 , wherein the data record differentiates between a first data volume transmitted from the service provider endpoint to the service recipient endpoint and a second data volume transmitted from the service recipient endpoint to the service provider endpoint. 11. The network entity of claim 1 : wherein the data transfer between the service provider endpoint and the service recipient endpoint is encrypted; and wherein the instructions are such that the network entity is operative to determine the activity metric without decrypting the data transfer. 12. An apparatus for assessing service performance from a session between an Over The Top (OTT) service provider endpoint and an OTT service recipient endpoint in regard of an OTT service, the apparatus comprising: processing circuitry; memory containing instructions executable by the processing circuitry whereby the apparatus is operative to: access data records generated for successive periods of time for the session, wherein each data record includes at least one activity metric indicative of at least one pending Transport Layer (TL) activity of the session in the period of time associated with that data record; wherein the at least one pending TL activity is a TL messaging procedure in which one endpoint is presently waiting for at least one TL message from the other endpoint; wherein the at least one activity metric is indicative of at least one pendency period associated with the at least one pending TL activity of the session; and assess performance of the OTT service based on the at least one activity metric. 13. The apparatus of claim 12 , wherein the instructions are such that the apparatus is operative to assess the OTT service performance by: processing the data records to differentiate between idle phases and activity phases during the session; and assess the OTT service performance based on the activity phases and not based on the idle phases. 14. The apparatus of claim 12 , wherein the instructions are such that the apparatus is operative to assess the OTT service performance by: identifying one or more data delivery bursts from the data records; estimating a media bitrate from the identified one or more data delivery bursts; and assessing the OTT service performance based on the estimated data rate. 15. The apparatus of claim 14 , wherein the instructions are such that the apparatus is operative to: classify the identified one or more data delivery bursts at least into an initial buffering burst type and an update burst type; and estimate the media bitrate from one or more update bursts and not from any initial buffering burst. 16. The apparatus of claim 12 , wherein the instructions are such that the apparatus is operative to assess the OTT service performance by: estimating, from the received data records, a buffer state of the service recipient as a function of time; and assessing the OTT service performance based on a temporal variation of the buffer state. 17. A method of generating a data record indicative of pending Transport Layer (TL) activities of a session between an Over The Top (OTT) service provider endpoint and an OTT service recipient endpoint, the method comprising: monitoring, at a network site between the two endpoints and during successive periods of time, at least one TL connection of the session, wherein the monitoring includes, for each period of time, determining for the at least one TL connection of the session at least one activity metric indicative of at least one pending TL activity of the session in the respective period of time; wherein the at least one pending TL activity is a TL messaging procedure in which one endpoint is presently waiting for at least one TL message from the other endpoint; wherein the at least one activity metric is indicative of at least one pendency period asso
Throughput · CPC title
Round trip delays · CPC title
Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF] · CPC title
Processing captured monitoring data, e.g. for logfile generation · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.