Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method for configuring a network path of a network for transferring an individual data flow end-to-end from a source device to a destination device, said path comprising at least one network device susceptible of network congestion and arranged for storing at least a part of said individual data flow, the method comprising the step of: determining at least one possible network path for transferring said individual data flow end-to-end from said source device to said destination device, said individual data flow having been previously classified according to a footprint measure of said individual data flow, said footprint measure being indicative of a possible difference between the total amount of incoming data and the total amount of outgoing data in said at least one network device over a time interval having a duration of one or more time units, whereby said time unit is so chosen that individual data units of the individual data flow are distinguishable at byte level by said at least one network device; and configuring said at least one network path according to said footprint measure.
A method configures a network path for transferring a data flow from a source to a destination. The path includes a network device susceptible to congestion that can store part of the data flow. The method determines possible paths, where the data flow is classified by a "footprint measure." This measure indicates the difference between incoming and outgoing data at the network device over a time interval. The time unit is small enough to distinguish individual data units (bytes) at the network device. The path is then configured based on this footprint measure.
2. The method for configuring as in claim 1 , further comprising, before the step of determining, a step of classifying said individual data flow according to said footprint measure.
The method for configuring a network path described previously (for transferring a data flow from a source to a destination, determining possible paths based on a "footprint measure" that indicates the difference between incoming and outgoing data at a network device over a time interval where the time unit is small enough to distinguish individual data units (bytes), and configuring the path based on the footprint measure) includes an initial step of classifying the data flow according to the "footprint measure" *before* determining the possible network paths.
3. The method for configuring as in claim 2 , wherein prior to the step of classifying a step is performed of determining said footprint measure.
The method for configuring a network path previously described (for transferring a data flow from a source to a destination, classifying the data flow according to a "footprint measure" before determining possible paths based on the footprint measure that indicates the difference between incoming and outgoing data at a network device over a time interval where the time unit is small enough to distinguish individual data units (bytes), and configuring the path based on the footprint measure) further includes a step of determining the "footprint measure" *before* classifying the data flow.
4. The method for configuring as claim 1 , wherein said step of configuring the at least one network path comprises setting at least one parameter related to the physical layout of said network path.
In the previously described method for configuring a network path (for transferring a data flow from a source to a destination, determining possible paths based on a "footprint measure" that indicates the difference between incoming and outgoing data at a network device over a time interval where the time unit is small enough to distinguish individual data units (bytes), and configuring the path based on the footprint measure), configuring the path involves setting parameters related to the physical layout of the network path. This might include selecting specific cables, ports, or network interfaces to use.
5. The method for configuring as in claim 1 , wherein said step of configuring comprises setting at least one parameter related to the logical layout of said network path.
In the previously described method for configuring a network path (for transferring a data flow from a source to a destination, determining possible paths based on a "footprint measure" that indicates the difference between incoming and outgoing data at a network device over a time interval where the time unit is small enough to distinguish individual data units (bytes), and configuring the path based on the footprint measure), configuring the path involves setting parameters related to the logical layout of the network path. This concerns software-defined configurations.
6. The method for configuring as in claim 5 , wherein said setting at least one parameter related to said logical layout comprises setting the routing of said at least one network device.
The method described where configuring a network path involves setting parameters related to its logical layout (transferring a data flow from a source to a destination, determining possible paths based on a "footprint measure" that indicates the difference between incoming and outgoing data at a network device over a time interval where the time unit is small enough to distinguish individual data units (bytes), and configuring the path based on the footprint measure) includes setting the routing configuration of at least one network device, determining the path data should take through the network.
7. The method as in claim 5 , wherein said setting at least one parameter related to said logical layout comprises setting at least one quality-of-service parameter of said at least one network device.
In the described method where configuring a network path involves setting parameters related to its logical layout (transferring a data flow from a source to a destination, determining possible paths based on a "footprint measure" that indicates the difference between incoming and outgoing data at a network device over a time interval where the time unit is small enough to distinguish individual data units (bytes), and configuring the path based on the footprint measure) includes setting quality-of-service (QoS) parameters on at least one network device. This can prioritize traffic based on its "footprint."
8. A management system for configuring a network path of a network for transferring an individual data flow end-to-end from a source device to a destination device, said network path comprising at least one network device susceptible of network congestion and arranged for storing at least a part of said individual data flow, said management system comprising a traffic management module arranged for determining at least one possible path for transferring said individual data flow end-to-end from said source device to said destination device, said individual data flow having been previously classified according to a footprint measure of said individual data flow, said footprint measure being indicative of a possible difference between the total amount of incoming data and the total amount of outgoing data in said at least one network device on a network path over a time interval having a duration of one or more time units, whereby said time unit is so chosen that individual data units of the individual data flow are distinguishable at byte level by said network device, and the management system further arranged for configuring said at least one network path according to said footprint measure.
A management system configures a network path for transferring a data flow from source to destination. The path contains a network device susceptible to congestion that stores part of the flow. The system includes a traffic management module that determines possible paths. The data flow is classified by a "footprint measure," indicating the difference between incoming and outgoing data at the network device over a time interval. The time unit is small enough that individual data units (bytes) are distinguishable. The system configures the path based on this footprint measure.
9. The management system as in claim 8 , wherein said traffic management module is arranged for imposing traffic restrictions and/or for shaping traffic to be transferred over said network path.
The management system previously described (for configuring a network path by determining possible paths based on a "footprint measure" and configuring the path based on this measure) has a traffic management module that imposes traffic restrictions (e.g., bandwidth limits) and/or shapes traffic (e.g., smoothing bursts) to be transferred over the configured network path.
10. The management system as in claim 8 wherein said traffic management module is further arranged for dynamically reconfiguring said at least one network path.
The management system previously described (for configuring a network path by determining possible paths based on a "footprint measure" and configuring the path based on this measure) has a traffic management module that dynamically reconfigures the network path. This means the path can be adjusted in real-time based on changing network conditions or data flow characteristics.
11. The management system as in claim 8 , wherein said traffic management module is further arranged for launching said individual data flow.
The management system previously described (for configuring a network path by determining possible paths based on a "footprint measure" and configuring the path based on this measure) has a traffic management module that launches (starts) the individual data flow.
12. The management system as in claim 8 , wherein said traffic management module is further arranged for monitoring said at least one network device.
The management system previously described (for configuring a network path by determining possible paths based on a "footprint measure" and configuring the path based on this measure) has a traffic management module that monitors the network device to provide data for the reconfiguration.
13. The management system as in any of claim 8 , further comprising a data flow management module for controlling said individual data flow, said data flow management module arranged for communication with said traffic management module and for controlling said traffic management module.
The management system (that configures a network path by determining possible paths based on a "footprint measure" and configuring the path based on this measure) includes a traffic management module and a data flow management module. The data flow management module controls the data flow and communicates with the traffic management module to control its operation.
14. The management system as in claim 13 , wherein said data flow management module is arranged for receiving information on the load of said network.
The management system with both traffic management and data flow management modules (where the traffic management module configures a network path by determining possible paths based on a "footprint measure" and configuring the path based on this measure) has a data flow management module that receives information about the network load. This allows it to make informed decisions about data flow control.
15. The management system as in claim 13 , further comprising a work flow management module for managing work flows of a process comprising a sequence of operations on at least one file containing media related data, said work flow management module arranged for communication with said data flow management module.
The management system with traffic management and data flow management modules (where the traffic management module configures a network path by determining possible paths based on a "footprint measure" and configuring the path based on this measure) further comprises a work flow management module. The workflow management module manages work flows that consist of a sequence of operations on media files, communicating with the data flow management module to handle the data transfer aspects of these workflows.
Unknown
November 25, 2014
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.