Signalling of dejittering buffer capabilities for TSN integration

US12074809B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12074809-B2
Application numberUS-201817294729-A
CountryUS
Kind codeB2
Filing dateNov 19, 2018
Priority dateNov 19, 2018
Publication dateAug 27, 2024
Grant dateAug 27, 2024

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

It is provided a method, including determining a parameter of a data flow to pass through a non-deterministic network and a buffering device; configuring the data flow in at least one of a network element of the non-deterministic network and the buffering device based on the parameter, wherein the parameter is determined based on a capability of the buffering device.

First claim

Opening claim text (preview).

The invention claimed is: 1. An apparatus, comprising: at least one processor; and at least one non-transitory memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: determine a parameter of a data flow to pass through a non-deterministic network and a buffering device; configure the data flow in at least one of a network element of the non-deterministic network or the buffering device based on the parameter of the data flow; and receive, from the buffering device, signaling of a notification that comprises a capability of the buffering device; wherein the parameter is determined based on the capability of the buffering device. 2. The apparatus of claim 1 , wherein the parameter is determined at least partially based on the capability of the buffering device defined for a terminal device category of a terminal device involved in the data flow. 3. The apparatus of claim 2 , wherein a respective capability of the buffering device is defined for each of plural terminal device categories, and wherein the instructions, when executed by the at least one processor, cause the apparatus at least to: get the terminal device category of the terminal device involved in the data flow; and retrieve the capability of the buffering device for the gotten terminal device category. 4. The apparatus of claim 1 , wherein the instructions, when executed by the at least one processor, cause the apparatus at least to: retrieve the capability from a storage device. 5. The apparatus of claim 1 , wherein the capability comprises at least one of a memory available to buffer data of the data flow in the buffering device or a processing time per data volume of the data flow to be buffered in the buffering device. 6. The apparatus of claim 1 , wherein the parameter comprises at least one of: the egress time window for the data flow, a minimum delay within the non-deterministic network, or a quality of service within the non-deterministic network. 7. The apparatus of claim 1 , wherein the instructions, when executed by the at least one processor, cause the apparatus at least to: check whether the data flow is configured to carry deterministic traffic; and inhibit the determining of the parameter of the data flow when the data flow is not configured to carry deterministic traffic. 8. The apparatus of claim 1 , wherein the instructions, when executed by the at least one processor, cause the apparatus at least to: hold the data of the data flow for a time period with the network element or the buffering device. 9. The apparatus of claim 1 , wherein the instructions, when executed by the at least one processor, cause the apparatus at least to: hold the data of the data flow for a time period with the network element or the buffering device prior to an egress time within the egress time window. 10. The apparatus of claim 1 , wherein the parameter is determined at least partially based on the capability of the buffering device defined for the terminal device category of the terminal device involved in a downlink direction of the data flow. 11. The apparatus of claim 1 , wherein the instructions, when executed by the at least one processor, cause the apparatus at least to: configure multiplexing of multiple stream packets with overlapping time windows, based at least partially on the egress time window. 12. The apparatus of claim 11 , wherein the multiple stream packets are configured for multiplexing with overlapping time windows based on a configuration of a network controller. 13. The apparatus of claim 1 , wherein the apparatus comprises a session management function of a core network. 14. The apparatus of claim 1 , wherein the apparatus comprises a policy control function of a core network. 15. An apparatus, comprising: at least one processor; and at least one non-transitory memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: determine an egress time window of a received data packet; buffer the data packet with a buffering device until an egress time within the egress time window; provide the data packet for transmission at the egress time; and transmit, to a control device, signaling of a notification that comprises a capability of the buffering device; wherein the egress time window or the egress time is determined at least partially based on the capability of the buffering device. 16. The apparatus of claim 15 , wherein the instructions, when executed by the at least one processor, cause the apparatus at least to: retrieve a time stamp out of the received data packet; wherein the determining comprises determining the egress time window of the data packet based on the time stamp and a predetermined transmission time range. 17. The apparatus of claim 15 , wherein the instructions, when executed by the at least one processor, cause the apparatus at least to: identify a data flow to which the data packet belongs; wherein the determining comprises determining the egress time window based on the data flow. 18. The apparatus of claim 15 , wherein the determining comprises determining a closest upcoming transmit window as the egress time window of the received data packet. 19. The apparatus of claim 15 , wherein the capability comprises at least one of a memory available to buffer data in the buffering device or a processing time per data volume to be buffered in the buffering device. 20. The apparatus of claim 15 , wherein the control device comprises a session management function of a core network. 21. The apparatus of claim 15 , wherein the control device comprises a policy control function of a core network. 22. The apparatus of claim 15 , wherein the egress time window or the egress time is determined at least partially based on the capability of the buffering device defined for a terminal device category of a terminal device involved in a data flow associated with the data packet. 23. A method, comprising: determining a parameter of a data flow to pass through a non-deterministic network and a buffering device; configuring the data flow in at least one of a network element of the non-deterministic network or the buffering device based on the parameter of the data flow; and receiving, from the buffering device, signaling of a notification that comprises a capability of the buffering device; wherein the parameter is determined based on the capability of the buffering device. 24. The method of claim 23 , wherein the parameter is determined at least partially based on the capability of the buffering device defined for a terminal device category of a terminal device involved in the data flow. 25. The method of claim 24 , wherein a respective capability of the buffering device is defined for each of plural terminal device categories, and the method further comprises: getting the terminal device category of the terminal device involved in the data flow; and retrieving the capability of the buffering device for the gotten terminal device category. 26. The method of claim 23 , further comprising: retrieving the capability from a storage device. 27. The method of claim 23 , wherein the capability comprises at least one of a memory available to buffer data of the data flow in the buffering device or a processing time per data volume of the data flow to b

Assignees

Inventors

Classifications

  • H04L49/90Primary

    Buffering arrangements · CPC title

  • H04L1/1838Primary

    for semi-reliable protocols, e.g. for less sensitive applications such as streaming video (buffer level management for video bitstream receiver H04N21/44004) · CPC title

  • for semi-reliable protocols, e.g. for less sensitive applications like streaming video (buffer level management for video bitstream control arrangements H04N21/44004) · CPC title

  • jitter monitoring · CPC title

  • Details of sliding window management · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12074809B2 cover?
It is provided a method, including determining a parameter of a data flow to pass through a non-deterministic network and a buffering device; configuring the data flow in at least one of a network element of the non-deterministic network and the buffering device based on the parameter, wherein the parameter is determined based on a capability of the buffering device.
Who is the assignee on this patent?
Nokia Technologies Oy
What technology area does this patent fall under?
Primary CPC classification H04L49/90. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Aug 27 2024 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 2 related publications on this page (citations in our corpus or others sharing the same primary CPC).