返回论文解读

sync reader

分组化对 Network Calculus 分析的影响

Impact of Packetization on Network Calculus Analysis · 2025-09-21

仿真与测试调度算法CC BY-NC-SA,非商业署名相同方式共享

本页提供英文原文段落与中文逐段译稿。译稿包含自动复核状态;标记为需人工复核的段落应回到 PDF/HTML 校对公式、表格和符号。

本站范围
全文逐段对照
内容来源
本地英文段落 + 中文译稿
阅读规模
61/61 段已生成译稿
中文逐段译稿
P001已复核

网络演算(network calculus, NC)是一种用于通信网络性能保证分析的理论 [1][2][3][4]。网络演算的一个关键思想是使用某些界函数对流量过程和服务过程建模,并以这些界函数为基础进行分析。在各种网络演算模型中,服务曲线模型起着核心作用;基于服务曲线模型,可以推导出各种性能界 [1][2][3][4]。自 20 世纪 90 年代初被提出以来 [5][6],网络演算已经被扩展并应用于各种类型的分组交换通信网络。特别是,对于 IEEE 802.1 时间敏感网络(Time-Sensitive Networking, TSN)[7] 和 IETF 确定性网络(Deterministic Networking, DetNet)[8],该理论已被广泛用于构造服务模型并计算性能界。代表性结果包括 [9]、[10]、[11] 和 [12]。可在 [13] 中找到一篇综合性综述,较新的结果还包括 [14][15]。所有这些结果都基于所研究传输选择机制的服务曲线模型;其中,恒定比特率链路和严格优先级调度是最基础的设置,或者说是默认设置 [7][8]。

术语“network calculus”译为“网络演算”,“service curve”译为“服务曲线”,“constant bit rate link”译为“恒定比特率链路”,“strict priority scheduling”译为“严格优先级调度”,与领域常用译法一致。引用编号、年代、TSN/DetNet 标准组织与缩写均已保留。未发现明显问题。

P002已复核

然而,本文的研究揭示,针对这两种基础设置而被广泛采用的服务曲线刻画结果,例如 [9]、[10]、[11]、[12]、[14] 和 [15],是有缺陷的。特别地,可以构造反例,从而否定所采用服务曲线的结果。进一步观察表明,这些结果忽略了分组化效应。本文还将研究扩展到考察由这些有缺陷的服务曲线推导出的性能界是否有效。对于输出界和积压界,以及对于串联系统服务曲线的刻画,同样可以构造反例。这表明,有必要更新服务曲线模型,并因此也更新性能界。为满足这一需要,本文基于将分组化效应直接纳入服务模型的思想,推导出这两种基础设置下修正后的服务曲线和性能界。这些结果提醒人们,在应用网络演算分析时,有必要将分组化效应考虑在内。

“packetization effect”译为“分组化效应”,保留了因果链条:服务曲线有缺陷、反例否定、原因是忽略分组化效应、进而需要更新模型与性能界。“disapproves”原文语义应为“disproves/否定”,译文按上下文处理为“否定”。该处可能是原文用词瑕疵,但不影响翻译逻辑。

P003已复核

本文其余部分组织如下。在下一节中,介绍系统模型和网络演算基础。在第 3 节中,通过反例表明,由于忽略了分组化效应,针对这两种基础设置而被广泛采用的服务曲线是有缺陷的。随后,研究使用这类有缺陷的服务曲线会对性能界产生何种影响。在第 3 节末尾,讨论网络演算理论中的相关结果;这些讨论揭示,理论上针对分组化所建议的调整已被这些有缺陷的服务曲线结果所忽略。在第 4 节中,证明修正后的服务曲线和性能界。最后,在第 5 节中给出结论。

章节编号、研究顺序、因果关系均已保留。“adjustments suggested by the theory for packetization”译为“理论上针对分组化所建议的调整”,表达准确。未发现明显问题。

P004已复核

我们考虑分组交换网络中的系统。特别地,我们关注数据流量在恒定比特率链路上的传输,以及数据流量通过一个优先级队列进行的传输;该优先级队列会与其他优先级队列竞争在这类链路上的传输。按照惯例,在这样的系统中,当且仅当一个分组的最后一比特已经到达时,才称该分组已经到达;相应地,当且仅当一个分组的最后一比特已经离开时,才称该分组已经被服务 [7]。当一个分组到达时,该分组可能会进入队列,并且假定该队列的缓冲区大小足够大,从而确保不会发生分组丢失。该队列是 FIFO 队列,并且初始为空。

“packet-switched network”译为“分组交换网络”,“priority queue”译为“优先级队列”,“FIFO”保留缩写并译为队列属性。到达/服务的定义严格保留“最后一比特”和“当且仅当”。未发现明显问题。

P005已复核

如图 1 所示,该系统由输入流量过程 \(A(t)\)、服务过程 \(S\) 和输出流量过程 \(A^{*}(t)\) 建模。具体而言,\(A(t)\) 表示截至时间 \(t\)(不包括 \(t\))进入系统的输入流的累计流量;\(A^{*}(t)\) 表示截至时间 \(t\)(不包括 \(t\))离开系统的该流的累计流量。按照惯例,我们采用 \(A(0)=A^{*}(0)=0\)。此外,我们定义 \(A(s,t)\equiv A(t)-A(s)\) 和 \(A^{*}(s,t)\equiv A^{*}(t)-A^{*}(s)\),它们分别表示时间区间 \([s,t)\) 内的输入流量量和输出流量量。由于时间 \(t\) 处的流量被排除在外,按照惯例有 \(A(t,t)=0\),并且同样有 \(A^{*}(t,t)=0\)。

公式符号 \(A(t)\)、\(S\)、\(A^{*}(t)\)、\(A(s,t)\)、\(A^{*}(s,t)\)、区间 \([s,t)\) 均已保留。原 JSON 中公式存在重复显示如 “A ​ (t) A(t)”,译文按规范公式形式合并处理。未发现明显问题。

P006已复核

此外,我们还可以使用标记点过程(marked-point processes)对该流的输入过程和输出过程建模,其中会显式考虑流量的分组化 [1]。具体而言,对于输入,标记点过程 \((\overrightarrow{a},\overrightarrow{l})\) 由两个变量序列组成,即 \(\overrightarrow{a}=\{a(n),n=0,1,2,\ldots\}\) 和 \(\overrightarrow{l}=\{l(n),n=0,1,2,\ldots\}\),其中 \(a(n)\) 表示分组 \(n\) 的到达时间,\(l(n)\) 表示其长度。对于输出,定义类似的标记点过程 \((\overrightarrow{d},\overrightarrow{l})\),其中 \(\overrightarrow{d}=\{d(n),n=0,1,2,\ldots\}\),\(d(n)\) 表示第 \(n\) 个分组从系统离开的时间。这里,分组 0 是一个虚拟分组,并且按照惯例有 \(a(0)=0\)、\(l(0)=0\) 和 \(d(0)=0\)。

“marked-point processes”译为“标记点过程”,并保留英文术语以降低歧义。向量序列、下标起点、虚拟分组 0 以及三个初始条件均已保留。未发现明显问题。

P007已复核

时间 \(t\) 处的积压记为 \(B(t)\),定义为: \[ B(t)=A(t)-A^{*}(t). \] (1) 分组 \(n\)(\(n\geq 1\))的时延记为 \(D(n)\),定义为: \[ D(n)=d(n)-a(n). \] (2) 在网络演算中,还采用了一个相关的时延概念,称为虚拟时延。具体而言,时间 \(t\)(\(t>0\))处的虚拟时延记为 \(D(t)\),定义为 [1][2][3][4]: \[ D(t)=\inf\{\tau\geq 0:A(t)\leq A^{*}(t+\tau)\}. \] (3)

backlog 译为“积压”,delay 译为“时延”,virtual delay 译为“虚拟时延”。公式 (1)(2)(3) 中变量、条件 \(n\geq1\)、\(t>0\)、\(\inf\)、\(\tau\geq0\) 均已保留。注意 \(D(n)\) 与 \(D(t)\) 使用同一字母但含义不同,译文已通过“分组”和“时间”区分。未发现明显问题。

P008已复核

令 \(\mathbf{\mathcal{F}}\) 表示非负非递减函数的集合,令 \(\mathbf{\mathcal{F}}_{0}\) 表示其中满足 \(f(0)=0\) 的子集。根据它们的定义,\(A(\cdot)\) 和 \(A^{*}(\cdot)\) 都属于 \(\mathbf{\mathcal{F}}_{0}\)。

集合符号 \(\mathbf{\mathcal{F}}\)、\(\mathbf{\mathcal{F}}_{0}\)、条件 \(f(0)=0\) 均已保留。“nonnegative nondecreasing”译为“非负非递减”,准确。未发现明显问题。

P009已复核

如果对于所有 \(0\leq s\leq t\),流量 \(A(s,t)\) 均受到如下上界约束 [2]: \[ A(s,t)\leq \alpha(t-s), \] (4) 则称流 \(A\) 具有到达曲线 \(\alpha\in\mathbf{\mathcal{F}}\)。

“arrival curve”译为“到达曲线”。原句先给定义再给公式,译文为中文自然语序但逻辑等价;条件 \(0\leq s\leq t\)、\(\alpha\in\mathbf{\mathcal{F}}\)、公式 (4) 均已保留。未发现明显问题。

P010已复核

如果对于任意时间 \(t\geq0\),都存在某个时间 \(s\in[0,t]\),使得 \[ A^{*}(t)\geq A(s)+\beta(t-s), \] 或者等价地,对于所有 \(t\geq0\),都有 [2] \[ A^{*}(t)\geq A\otimes\beta(t)\equiv\inf_{0\leq s\leq t}\{A(s)+\beta(t-s)\}, \] 则称一个系统提供服务曲线 \(\beta\in\mathbf{\mathcal{F}}_{0}\)。

“service curve”译为“服务曲线”,保留 \(\beta\in\mathbf{\mathcal{F}}_{0}\)、\(t\geq0\)、\(s\in[0,t]\)、卷积符号 \(\otimes\)、下确界表达式和等价定义。公式上下文完整,未发现明显问题。

P011需人工复核

如果输入流具有到达曲线 α,且系统向该输入流提供服务曲线 β,则有 [2]:(i)输出具有到达曲线 α\*(t) ≡ sup_{u≥0}{α(u+t)−β(u)},即 ∀s,t≥0,A\*(s,s+t)≤α\*(t);(5)(ii)积压 B(t) 的上界为,∀t≥0,B(t)≤sup_{t≥0}{α(t)−β(t)};(6)(iii)虚拟时延 D(t) 的上界为,∀t≥0:D(t)≤sup_{t≥0} inf{τ≥0: α(t)≤β(t+τ)}。(7)

术语“arrival curve”译为“到达曲线”,“service curve”译为“服务曲线”,“backlog”译为“积压”,“virtual delay”译为“虚拟时延”,符合网络演算常用译法。公式中的 sup 下标和外层 ∀t 使用同一符号 t,原文如此,可能存在排版或变量复用风险,但译文已保留。A\* 既表示输出过程也出现在区间 A\*(s,s+t),保留原符号。状态建议人工关注公式 (6)(7) 中 sup 的变量命名。

P012已复核

作为一个例子,假设输入流受令牌生成速率为 ρ、桶大小为 σ 的令牌桶约束 [5],或者具有到达曲线 α(t)=ρt+σ。此外,系统向输入提供一个时延-速率服务曲线 β(t)=R(t−T)^+,其中 R 称为速率项,T 称为时延项。如果 ρ≤R,则定理 2.1 给出的界可以写为:α\*(t)=ρt+(σ+ρT);(8) B(t)≤σ+ρT;(9) D(t)≤σ/R+T。(10)

“token bucket”译为“令牌桶”,“latency-rate service curve”译为“时延-速率服务曲线”。保留了 ρ、σ、R、T、α\*、B(t)、D(t) 及公式编号。原文中公式排版将等号和不等号拆分显示,译文已合并为标准表达。D(t)≤σ/R+T 中分式来自原 LaTeX `\frac{\sigma}{R}+T`,无明显问题。

P013已复核

在网络演算分析中,用于寻找系统服务曲线刻画的一项重要技术,利用了严格服务曲线的概念,以及严格服务曲线与服务曲线模型之间的关系;这些内容概括如下。

“network calculus analysis”译为“网络演算分析”,“strict service curve”译为“严格服务曲线”,“characterization”译为“刻画”。逻辑为引出下文定义与结论,未发现明显问题。

P014已复核

若在任意长度为 t 的积压期内,输出满足 [2] A\*(t)≥β(t),则称系统提供严格服务曲线 β∈ℱ₀。

“backlogged period”译为“积压期”。原文写作“during any backlogged period of length t, the output satisfies A\*(t)≥β(t)”,其中 A\*(t) 未显式写区间,可能是简化记号;译文保留该形式。β∈ℱ₀ 保留数学符号。未发现明显问题。

P015需人工复核

如果 β(∈ℱ₀)是某一系统的严格服务曲线,则它也是该系统的一条服务曲线 [2]。

原文括号似有排版缺失,写作“If β (∈ℱ₀ is...”,应理解为 β∈ℱ₀。译文按合理数学表达处理。术语与逻辑无明显问题,但原文括号残缺需注意。

P016已复核

对于级联系统,以下结果对于寻找其服务曲线刻画是重要的。

“concatenation system”译为“级联系统”。句子为引出后续定理,未发现明显问题。

P017已复核

考虑一个流依次穿过两个系统 S₁ 和 S₂。如果每个系统 Sᵢ(i=1,2)都向其输入提供服务曲线 βᵢ,则该级联系统向该流提供服务曲线 β₁⊗β₂ [2]。

“traverses ... in sequence”译为“依次穿过”。⊗ 保留为网络演算中的卷积/最小加卷积记号,未展开解释。数字 i=1,2 和引用 [2] 均保留。未发现明显问题。

P018需人工复核

在本文中,我们关注分组交换网络中的两种基本传输选择设置。一种是(工作保持的)恒定比特率链路,另一种是在这种链路上用于分组传输的严格优先级队列。前者是任何其他传输选择算法的基础,而后者通常被实现,例如作为时间敏感网络的默认设置 [7]。对于这两种基本情形,以下服务曲线结果已被广泛应用,例如见 [9][10][11][12][13][14] 和 [15]:• 具有恒定比特率 c 的(工作保持)链路提供一条(严格)服务曲线 ct。• 当链路上应用(非抢占式)严格优先级时,最高优先级队列获得一条(严格)服务曲线 c(t−l^{M_l}/c)^+,其中 l^{M_l} 表示所有较低优先级队列中的最大分组长度,且 (x)^+≡max{x,0}。

“packet-switched network”译为“分组交换网络”,“work-conserving”译为“工作保持”,“constant bit rate link”译为“恒定比特率链路”,“strict priority queue”译为“严格优先级队列”。公式 c(t−l^{M_l}/c)^+ 按原文保留;l^{M_l} 的上标/下标组合较不常见,但原文如此。P018 内含两个项目符号,且 P019、P020 又分别重复这些项目,属于输入结构重复,译文仍按段落完整保留。

P019已复核

具有恒定比特率 c 的(工作保持)链路提供一条(严格)服务曲线 ct。

与 P018 中第一个项目相同。术语“工作保持”“恒定比特率”“严格服务曲线”一致,公式 ct 保留。未发现明显问题。

P020需人工复核

当链路上应用(非抢占式)严格优先级时,最高优先级队列获得一条(严格)服务曲线 c(t−l^{M_l}/c)^+,其中 l^{M_l} 表示所有较低优先级队列中的最大分组长度,且 (x)^+≡max{x,0}。

与 P018 中第二个项目相同。“non-preemptive”译为“非抢占式”,“highest priority queue”译为“最高优先级队列”。公式与定义完整保留。l^{M_l} 的符号识别可能需结合论文符号表确认,但未作改写。

P021已复核

不幸的是,如以下第 3.1 节所示,二者都是有缺陷的。

“both” 指代前文中的两个结论或服务曲线用法,需结合上文确认具体对象;术语和逻辑未发现明显问题。

P022已复核

将 \(ct\) 用作该系统的(严格)服务曲线,其背后的直观理由如下。由于链路是 work-conserving 的,在任意积压时段内,链路以速率 \(c\) 输出流量(以 bit 计),因此具有严格服务曲线 \(ct\);同时,根据命题 1,也可以推出 \(ct\) 是一条服务曲线。虽然这听起来很直接,但下面的例子和讨论强调,当需要考虑分组化效应时,必须格外小心。

work-conserving 保留英文术语,避免译为可能不统一的“工作保持”;“strict service curve”和“service curve”分别译为“严格服务曲线”和“服务曲线”;公式 \(ct\)、速率 \(c\)、命题 1 均保留。未发现明显问题。

P023需人工复核

考虑如图 2 所示,链路上传输分组 \(n\) 的情形。如果不考虑分组化效应,我们会有 \(A(s,t)=A^{*}(s,t)=c(t-a(n))\)(以 bit 计)。然而,在分组模型下,将分组化考虑在内时,实际有 \(A(s,t)=l(n)\),而 \(A^{*}(s,t)=0\)。前者成立是因为在时刻 \(a(n)\),该时刻位于 \([s,t)\) 内,分组的(最后一个 bit)已经到达,因此传输可以开始。相反,对于 \(A^{*}(s,t)\),\(d(n)\) 不在该时段内,这意味着该分组的最后一个 bit 尚未完成传输,因此在所考虑的时段 \([s,t)\) 内,该分组不被认为已经被传输或被服务。由于 \(0\leq c(t-a(n))\leq l(n)\),我们有 \(A^{*}(s,t)\leq c(t-s)\);如果将 \(ct\) 用作严格服务曲线,这就会与严格服务曲线的定义相矛盾。

原文 “contracts the definition” 很可能应为 “contradicts the definition”,译为“相矛盾”;\(A\)、\(A^*\)、\(a(n)\)、\(d(n)\)、\(l(n)\)、区间 \([s,t)\) 和不等式均已保留。由于原文疑似存在拼写/识别错误,建议人工确认。

P024已复核

上述讨论否定了将 \(ct\) 用作严格服务曲线的有效性。然而,\(ct\) 是否是一条有效服务曲线这一问题仍然存在。为此,我们构造一个情形,在该情形中,对于 \(\beta(t)=ct\),\(A^{*}(t)\geq A\otimes\beta(t)\) 并不成立。

“disapproves the validity” 译为“否定……有效性”;服务曲线条件 \(A^{*}(t)\geq A\otimes\beta(t)\) 和 \(\beta(t)=ct\) 已保留。未发现明显问题。

P025需人工复核

考虑第一个分组。令 \(a(1)\) 为其到达时间,令 \(l(1)(>0)\) 为其长度。于是,对于任意时刻 \(t\in[a(1),a(1)+\frac{l(1)}{c})\),时段 \((a(1),t)\) 是积压的,因为该分组已经到达但尚未离开。此外,我们有: \[ \begin{aligned} A\otimes\beta(t) &= \inf_{0\leq s\leq t}\{A(s)+c(t-s)\} \\ &= \min\left\{\inf_{0\leq s<a(1)}\{A(s)+c(t-s)\},\inf_{a(1)\leq s\leq t}\{A(s)+c(t-s)\}\right\} \\ &= \min\{c(t-a(1)),l(1)\} \\ &= c(t-a(1))>0 . \end{aligned} \] 注意,\(A^{*}(t)=0\),因为只有当一个分组的最后一个 bit 已经离开时,该分组才被认为已经被服务;第一个分组在 \(t(<a(1)+\frac{l(1)}{c})\) 时尚未离开,因此该分组不能被计入 \(A^{*}(t)\)。换言之,对于任意 \(t\in[a(1),a(1)+\frac{l(1)}{c})\),都有 \(A\otimes\beta(t)>A^{*}(t)\),这与 \(\beta\) 成为服务曲线所需满足的条件 \(A^{*}(t)\geq A\otimes\beta(t),\forall t\geq0\) 相矛盾。命题 2 由此得出。

原文中区间上界在部分位置被识别为 \(a(1)+l(1)c\),但随后的 LaTeX 明确为 \(a(1)+\frac{l(1)}{c}\),译文按后者处理;公式链条、编号 (11) 未单独保留但公式内容完整;“inf/min”、卷积符号 \(\otimes\)、严格不等式均已保留。因原文存在公式识别混排风险,建议人工确认。

P026已复核

对于一个具有恒定比特率 \(c\)(单位为 bps)的系统,\(ct\) 既不是严格服务曲线,也不是服务曲线。

“constant bit rate \(c\) (in bps)” 已准确保留;“neither...nor...” 译为“既不是……也不是……”。未发现明显问题。

P027需人工复核

对于(非抢占式)严格优先级情形,将 \(c(t-\frac{l^{M_l}}{c})^{+}\) 用作(严格)服务曲线,其背后的直观理由如下。在该表述中,\(\frac{l^{M_l}}{c}\) 将非抢占效应纳入考虑;也就是说,在到达时,即便正在传输的分组来自较低优先级队列,一个最高优先级分组也必须等待该正在传输的分组完成。然而,如命题 2 的讨论所示,当分组化被考虑在内时,\(ct\) 并不是该链路的一条(严格)服务曲线。特别地,在图 2 的 \(a(n)\) 处纳入非抢占效应并加上 \(\frac{l^{M_l}}{c}\) 后,可以对最高优先级队列进行同样的、考虑分组化的分析;由此我们可以进一步得出命题 3。

原文公式混排为 \(c(t-\frac{l^{M_l}}{c})^{+}\),译文按该式处理;\(l^{M_l}\) 的上标/下标含义需结合论文符号表确认;non-preemptive strict priority 译为“(非抢占式)严格优先级”。由于公式识别存在混排风险,建议人工确认。

P028需人工复核

对于一条具有恒定比特率 \(c\) 的链路上的最高优先级队列,\(c(t-\frac{l^{M_l}}{c})^{+}\) 既不是严格服务曲线,也不是服务曲线。

公式 \(c(t-\frac{l^{M_l}}{c})^{+}\)、恒定比特率 \(c\)、最高优先级队列均已保留;由于 \(l^{M_l}\) 的排版可能存在识别风险,建议结合原 PDF 确认。

P029已复核

如上所研究并在命题 2 和命题 3 中总结的,分组化对服务曲线刻画结果的影响具有两个直接含义:

“service curve characterization results” 译为“服务曲线刻画结果”;命题 2 和命题 3 已保留。未发现明显问题。

P030已复核

第一,由这些有缺陷的服务曲线推导出的各种性能界,例如输出到达曲线、积压界和时延界,必须重新检查其有效性,并且可能需要更新。第二,对于任何建立在这两个基本情形之上的复杂设置,如果其服务曲线结果对于命题 2 和命题 3 所指出的两个基本情形中的任一情形蕴含了一条有缺陷的服务曲线,那么该复杂设置的服务曲线结果以及相应推导出的性能界都将需要重新检查,并且可能需要更新。

原文项目符号合并在同一段内,译文保留为同一 P030 段落并用“第一/第二”表达两个要点;output arrival curve、backlog、delay bounds 分别译为“输出到达曲线、积压界、时延界”;逻辑条件 “if... either of the two fundamental cases...” 已保留。未发现明显问题。

P031已复核

从这些有缺陷的服务曲线推导出的各种性能界,例如输出到达曲线、积压界和时延界,都必须重新检查其有效性,并且可能需要更新。

术语“faulty service curves”译为“有缺陷的服务曲线”,“output arrival curve”译为“输出到达曲线”,“backlog and delay bounds”译为“积压界和时延界”,与网络演算语境一致;未涉及数字或公式。未发现明显问题。

P032已复核

对于任何建立在这两个基本情形之上的复杂设置,如果其服务曲线结果会推出命题 2 和命题 3 所指出的、针对这两个基本情形中任一情形的有缺陷服务曲线,那么该复杂设置的服务曲线结果以及相应推导出的性能界,都需要重新检查,并且可能需要更新。

“two fundamental cases”译为“两个基本情形”,“Propositions 2 and 3”保留为“命题 2 和命题 3”;逻辑上保留了“如果复杂设置的结果蕴含任一基本情形的错误服务曲线,则复杂设置及其性能界需复查”的条件关系。未发现明显问题。

P033需人工复核

对于后者,由于一个基本情形是该复杂设置的一个特例,如果该特例的结果是有缺陷的,那么该复杂设置的结果也不可能成立。对于前者,值得强调的是,恒定比特率情形被包含在严格优先级情形(SP)之中。具体而言,它是系统中只有单个队列时的 SP 的一个特例。

“latter/former”的指代依赖前文上下文,译文按原句顺序保留“后者/前者”;“constant bit rate case”译为“恒定比特率情形”,“strict priority case (SP)”译为“严格优先级情形(SP)”。由于“前者/后者”的具体指代需要结合更早段落确认,存在轻微上下文风险。

P034已复核

在本小节中,我们研究有缺陷的服务曲线对相应获得的性能界结果的影响。通过构造反例,我们表明,有缺陷的服务可以导致有缺陷的输出界、有缺陷的积压界以及有缺陷的串联系统服务曲线;而对于时延界,则不能得出同样的结论。我们聚焦于恒定比特率情形。因为它是最基本的设置,并且是 SP 的一个特例,所以关于某个界无效性的相关结论也适用于 SP 情形。

“faulty output bound / backlog bound / concatenation service curve”分别译为“有缺陷的输出界 / 积压界 / 串联系统服务曲线”;“while for delay bound the same conclusion cannot be made”译为“对于时延界,则不能得出同样的结论”,保留了作者的限定。未发现明显问题。

P035需人工复核

为了便于讨论,考虑一个简单的输入情形。具体而言,输入流周期性地向系统发送分组。令 τ 表示两个相邻分组之间的间隔。除分组 1 之外,所有分组都具有相同长度 l,而分组 1 的长度为 σ(> l)。为保证稳定性,假设 l/τ < c。对于这一输入情形,可以验证它具有到达曲线 α(t)=l/τ·t+σ。A(t) 和 α(t) 的示意图见图 3,其中还示出了输出 A*(t) 以及一个使用与 α 相同斜率的输出到达曲线 α*(t)。(注:对于 α 和 α*,它们分别对应于从 a(1) 和 d(1) 开始的区间。)对于输出,若将 β(t)=ct 作为服务曲线应用于定理 2.1,则会得到 A*(s,s+t)≤l/τ·t+σ=α(t),∀s,t≥0,或者换言之 α*=α。然而,如图 3 所示,α*(t) 需要具有比初始 σ 更高的 σ*。换言之,输出并不受 α(t) 约束,因此,基于从有缺陷的服务曲线推导而使用 α 作为输出的上界,是错误的。

保留了 τ、l、σ、c、α(t)、A(t)、A*(t)、α*(t)、a(1)、d(1) 等符号;“arrival curve”译为“到达曲线”,“output arrival curve”译为“输出到达曲线”。原文公式抽取中存在重复符号和排版噪声,如“τ \tau”“l l”“α ​ (t)”等,译文按数学含义整理;“higher σ*”译为“更高的 σ*”符合纵截距/突发项语境。因该段公式较多且依赖图 3,需人工核对排版和图示上下文。

P036需人工复核

对于积压,若将 β(t)=ct 作为服务曲线应用于定理 2.1,则得到 B(t)≤σ,∀t≥0。然而,这个积压界 σ 是不正确的。考虑与图 3 所示相同的情形。特别地,在分组 1 完成之前,分组 2 已经到达。因此,对于 t=d(1)- 的 B(t),即分组 1 刚完成传输之前的时刻,系统中的积压为 σ+l,其中 σ 是分组 1 的大小,l 是分组 2 的大小。由于 σ+l>σ,因此由有缺陷的服务曲线得到的积压界 σ 是不正确的。

“backlog”译为“积压”;“t=d(1)_-”译为“t=d(1)-”,表示 d(1) 左极限或刚完成前时刻,含义已在译文中说明。公式 B(t)≤σ、∀t≥0、σ+l>σ 均保留。原文中 “t = d(1) − t=d(1)_{-}”存在抽取重复/排版问题,需人工核对原 PDF 公式。

P037已复核

对于时延,若将 β(t)=ct 作为服务曲线应用于定理 2.1,则得到 D(t)≤σ/c,∀t≥0。令人意外的是,不同于从有缺陷的服务曲线推导出的输出界和积压界也是有缺陷的,对于时延界不能得出类似结论。这是因为 σ/c 实际上是一个有效的时延界;这一点已经被证明,但使用的是另一种服务建模技术 [16]。与此相关的更多说明见第 3.3 节。

“delay bound”译为“时延界”;D(t)≤σ/c、∀t≥0 保留;“using another service-modeling technique [16]”译为“使用另一种服务建模技术 [16]”,引用编号保留。未发现明显问题。

P038已复核

假设一个流依次经过两个交换机 S1 和 S2,其中相应的输出链路分别具有恒定比特率 c1 和 c2。令 β_i(t)=c_i t,(i=1,2)。如果它们分别是 S1 和 S2 的正确服务曲线,那么我们会得到 β1⊗β2(t)=min{c1,c2}t 作为该串联系统的服务曲线。于是,如果输入具有到达曲线 ρt+σ,且 ρ≤min{c1,c2},则任一分组的时延都会被 σ/min{c1,c2} 所上界;然而,可以为此构造反例。具体而言,为简单起见,考虑所有分组都具有相同长度 l、σ=l 且 c1=c2≡c 的情形。那么有 σ/min{c1,c2}=l/c。进一步地,容易验证,对于任一分组,由于它在两个系统上各自的传输时间均为 l/c,它的时延至少为 2×l/c,这大于 l/c。这意味着,有缺陷服务曲线的串联会导致串联系统得到一个有缺陷的串联服务曲线。

“traverses two switches in sequence”译为“依次经过两个交换机”;卷积符号 β1⊗β2、min{c1,c2}、ρt+σ、ρ≤min{c1,c2}、σ/min{c1,c2}、c1=c2≡c、2×l/c 均保留。逻辑上保留了通过传输时间下界反驳串联服务曲线的论证。未发现明显问题。

P039需人工复核

值得强调的是,形式相同的服务曲线已经在网络演算理论中针对类似系统被引入,但处于不同的上下文之下。• 在 [1] 中,采用离散时间,并且服务率 c 以单位时间内的分组数计。在这些假设下,ct 被证明是恒定速率服务器以及最高优先级队列的一个服务曲线,在 [1] 中称为 f-server。• 在 [2] 和 [4] 中,分析和结果并不依赖于时间模型是离散的还是连续的,本文的情形也是如此。在 [2] 和 [4] 中,通过定义在比特层面计数的服务量,ct 被证明是恒定比特率情形的严格服务曲线;对于这种链路上的最高优先级队列,c(t-l^{M_l}/c)^+ 也是严格服务曲线(参见 [2] 中的命题 1.3.4 以及 [4] 中的第 1.2 节)。

保留了 [1]、[2]、[4]、ct、f-server、c(t-l^{M_l}/c)^+、Proposition 1.3.4、Section 1.2 等关键信息;“highest priority queue”译为“最高优先级队列”。原文公式 `c(t-\frac{l^{M_l}}{c})^+` 可能由 PDF 抽取得到,`l^{M_l}` 的含义和排版需结合原文确认;本段还包含项目符号,可能与后续 P040 存在重复切分。

P040需人工复核

在 [1] 中,采用离散时间,并且服务率 c 以单位时间内的分组数计。在这些假设下,ct 被证明是恒定速率服务器以及最高优先级队列的一个服务曲线,在 [1] 中称为 f-server。

本段与 P039 中第一条项目内容重复,可能是输入分段或 PDF 抽取造成的重复;译文仍按输入段落单独翻译。术语、引用和 ct 均已保留。因存在重复上下文风险,需人工复核。

P041需人工复核

在文献 [2] 和 [4] 中,分析和结果并不依赖于时间模型是离散的还是连续的;本文中的情况也是如此。在文献 [2] 和 [4] 中,通过在比特级定义所计量的服务量,证明了对于恒定比特率情形,\(ct\) 是一条严格服务曲线;并且对于这种链路上的最高优先级队列,\(c(t-\frac{l^{M_l}}{c})^{+}\) 也是一条严格服务曲线(参见文献 [2] 中的 Proposition 1.3.4 以及文献 [4] 中的 Section 1.2)。

原文中公式存在 OCR 重复显示,如 “c ​ t ct” 和 “c ​ (t − l M l c) + c(t-\frac{l^{M_{l}}}{c})^{+}”,按 LaTeX 形式理解为 \(ct\) 与 \(c(t-\frac{l^{M_l}}{c})^{+}\)。术语 “strict service curve” 译为“严格服务曲线”。需注意 \(l^{M_l}\) 的上标/下标可能来自识别错误,需结合论文公式确认。

P042已复核

为了考虑分组化的影响,特别是一个流由一系列(可变长度)分组组成,并且调度算法是在分组级而不是比特级运行,文献 [1] 引入了一个称为 packetizer(分组化器)的新概念,文献 [2] 和 [4] 也采用了这一概念。其思想是将系统视为两个概念性子系统的串联,如图 4 所示。一个是逐比特系统,即系统中分组化生效之前的部分;另一个是分组化器,它把前一个子系统输出的流量组装成分组。

“packetizer” 保留英文并译为“分组化器”。“scheduling algorithm is at the packet level while not at the bit level” 已按“分组级而不是比特级”处理。图号 Fig. 4 保持一致。未发现明显问题。

P043已复核

借助 packetizer 概念,文献 [1]、[2] 和 [4] 强调,可能需要在服务曲线和性能界结果中加入额外项。特别地,服务曲线、积压界以及串联服务曲线都必须进行调整,尽管已经证明 packetizer 不会增加最大分组时延 [1]、[2]、[4]。遗憾的是,在近期网络演算分析的应用中,这一点似乎在很大程度上被忽视了,例如在文献 [9]、[10]、[11]、[12]、[13]、[14] 和 [15] 中,直接采用了有缺陷的服务曲线,而没有考虑分组化影响。

“backlog bound” 译为“积压界”,“concatenation service curve” 译为“串联服务曲线”。引用列表中原文 “[12] [13]” 缺少逗号,译文按连续引用处理。逻辑上保留了“虽不增加最大分组时延,但仍需调整服务曲线/性能界”的转折。未发现明显问题。

P044已复核

不同于文献 [1]、[2] 和 [4] 中依赖 packetizer 概念来考虑分组化影响,我们在建模到达过程和服务过程时直接将分组化纳入考虑。更具体地,如第 2 节所介绍,我们采用如下约定:当且仅当一个分组的最后一个比特已经到达时,才称该分组已经到达;相应地,当且仅当其最后一个比特已经离开时,才称该分组已经被服务。因此,我们将到达过程和离开过程建模为带标记的点过程。基于这一思想,我们开展网络演算分析,并在接下来的第 4 节中针对两个基本情形给出修正后的服务曲线和性能界。

“marked point processes” 译为“带标记的点过程”。“respectively” 的对应关系已保留为“到达/离开”。“next Section 4” 译为“接下来的第 4 节”。未发现明显问题。

P045已复核

对于恒定比特率情形,修正后的服务曲线在 Proposition 4 中给出。

“constant bit rate” 译为“恒定比特率”。“Proposition 4” 保留原论文命名。未发现明显问题。

P046需人工复核

一个具有恒定比特率 \(c\) 的系统提供一条严格服务曲线以及一条服务曲线 \(c(t-\frac{l^{M}}{c})^{+}\),其中 \(l^{M}\) 表示系统中的最大分组长度。

原文 “c c” 与 “l M l^{M}” 为 OCR 重复,译文按 \(c\) 与 \(l^{M}\) 处理。该句中“strict service curve and a service curve” 可能省略了第一条曲线的显式公式,结合上一段和上下文应为严格服务曲线 \(c(t-\frac{l^{M}}{c})^{+}\),但原文显示不完整,需人工核对 Proposition 4 原始排版。

P047需人工复核

考虑任意一个积压期 \((s,t]\),如图 5 所示,并令 \(n_{0}\) 表示其到达使该积压期开始的分组。显然,有 \(s\geq a(n_{0})\)。不失一般性,假设分组 \(m\) 是在时刻 \(s\) 之后离开的第一个分组,分组 \(n\) 是在时刻 \(t\) 之后离开的第一个分组。根据它们的定义,必有 \(d(m-1)<s\leq d(m)\) 且 \(d(n-1)\leq t<d(n)\)。由于系统在 \((s,t]\) 期间处于积压状态,因此它在以下区间内也必然处于积压状态:(i) \((s,d(m)]\),(ii) \((d(m),d(n-1)]\),以及 (iii) \((d(n-1),t]\)。因为该系统具有恒定比特率 \(c\),所以在任意持续时间为 \(\tau\) 的积压期内,它服务/传输的流量为 \(c\tau\)(以比特计)。因此有 \[ c(d(m)-s)\leq l(m), \] \[ c[d(n-1)-d(m)]=\sum_{k=m+1}^{n-1}l(k), \] 并且 \[ c[t-d(n-1)]\leq l(n)\leq l^{M}. \] 由于如图 5 所示, \[ A^{*}(s,t)=\sum_{k=m}^{n-1}l(k), \] 我们有 \[ A^{*}(s,t)=l(m)+c[d(n-1)-d(m)] \tag{12} \] \[ \geq c[d(n-1)-s]\geq c(t-s-\frac{l^{M}}{c}), \] 这与事实 \(A^{*}(s,t)\geq 0\) 结合起来,即完成证明。

原文公式因 OCR 混入重复片段,译文按可识别 LaTeX 重构。重点关系包括 \(d(m-1)<s\leq d(m)\)、\(d(n-1)\leq t<d(n)\)、求和范围 \(k=m+1\) 到 \(n-1\)、以及 \(A^{*}(s,t)=\sum_{k=m}^{n-1}l(k)\)。其中“packet \(n\) the first packet that departs after time \(t\)” 与条件 \(d(n-1)\leq t<d(n)\) 一致。由于公式排版残缺且 (12) 的换行/等号需结合原 PDF 核对,建议人工复核。

P048已复核

借助 Proposition 4,可以立即从 Theorem 2.1 推导出各种性能界。作为一个具体例子,当输入受到令牌桶到达曲线约束时,这些性能界在 Corollary 1 中进行了总结。

“token-bucket arrival curve” 译为“令牌桶到达曲线”。“Theorem 2.1”“Corollary 1” 保留原论文命名。未发现明显问题。

P049已复核

考虑一个在具有恒定比特率 \(c\) 的链路上传输的流量流。如果该流量具有令牌桶到达曲线 \[ \alpha(t)=\rho t+\sigma \] 且 \(\rho\leq c\),则有: (i) 输出具有到达曲线 \[ \rho t+\sigma+\rho\frac{l^{M}}{c}, \] 即 \[ \forall s,t\geq 0,\quad A^{*}(s,s+t)\leq \rho t+\sigma+\frac{\rho}{c}l^{M}; \tag{13} \] (ii) 积压量 \(B(t)\) 的上界为 \[ \forall t\geq 0,\quad B(t)\leq \sigma+\frac{\rho}{c}l^{M}; \tag{14} \] (iii) 虚拟时延 \(D(t)\) 的上界为 \[ \forall t\geq 0:\quad D(t)\leq \frac{\sigma+l^{M}}{c}. \tag{15} \]

原文中 (i) 的公式先写为 \(\rho t+\sigma+\rho\frac{l^{M}}{c}\),随后等价写为 \(\rho t+\sigma+\frac{\rho}{c}l^{M}\),译文保持一致。(iii) 原文 OCR 中出现 “D(t) ≤ σ + lM c.”,结合 LaTeX 为 \(D(t)\leq\frac{\sigma+l^{M}}{c}\)。公式和编号 (13)-(15) 已保留。未发现明显问题。

P050已复核

此外,借助 Proposition 4 和 Theorem 2.2,可以为第 3.2 节中讨论的反例情形找到一条修正后的串联服务曲线。

“counterexample case” 译为“反例情形”,“corrected concatenation service curve” 译为“修正后的串联服务曲线”。章节与定理编号已保留。未发现明显问题。

P051已复核

考虑一个依次穿越两个交换机的流。相应的输出链路分别具有恒定比特率 \(c_i,(i=1,2)\)。该串联系统向该流提供的服务曲线为 \(\min\{c_1,c_2\}(t-\frac{l^M}{c_1}-\frac{l^M}{c_2})^+\)。

术语“串联系统”“服务曲线”“恒定比特率”一致;数字 \(i=1,2\) 和公式中的 \(\min\{c_1,c_2\}\)、\(l^M/c_i\) 已保留。原文公式存在重复 OCR 片段,但可识别为标准形式。 **状态:** 已复核

P052已复核

对于严格优先级情形,一个修正后的严格服务曲线,同时也是一个服务曲线,在命题 5 中给出。对于证明,它与命题 4 的证明类似。关键区别在于,\(s\) 可能处于一个较低优先级分组的传输期间,该分组已经开始传输,并且不能被最高优先级分组 \(n_0\) 的到达所抢占。在这种场景下,我们有 \(c(s-d(n_0))\leq l(n_0)+l^{M_l}\),\(c(d(n-1)-d(n_0))=\sum_{k=n_0+1}^{n-1}l(k)\),以及 \(c[t-d(n-1)]\leq l(n)\leq l^M\)。由此,我们得到 \[ A^*(s,t)=\sum_{k=n_0}^{n-1}l(k)\geq c[d(n-1)-s-\frac{l^{M_l}}{c}]\geq c(t-s-\frac{l^M}{c}-\frac{l^{M_l}}{c}) \tag{16} \] 其中,\(l^M\) 和 \(l^{M_l}\) 分别表示所考虑的最高优先级队列的最大分组长度,以及所有较低优先级队列的最大分组长度。对于其他场景,即最高优先级分组 \(n_0\) 的到达没有遇到任何正在进行的较低优先级分组传输的场景,它们与命题 4 的证明相同,因此 \(A^*(s,t)\geq c(t-s-\frac{l^M}{c})\)。结合所有场景以及 \(A^*(s,t)\geq 0\) 这一事实,可以得出命题 5。

保留了严格优先级、不可抢占、最高/较低优先级队列等关键术语;公式编号 (16)、求和上下界、\(l^M\)、\(l^{M_l}\)、\(n_0\)、\(d(n)\) 均已保留。原文中 \(s\)、\(l^M\)、\(l^{M_l}\) 有 OCR 重复和排版混杂,但语义可恢复。 **状态:** 已复核

P053已复核

对于一个具有恒定服务速率 \(c\)(单位为 bps)的系统中的最高优先级队列,\(c(t-\frac{l^M}{c}-\frac{l^{M_l}}{c})^+\) 既是严格服务曲线,也是服务曲线。

公式、单位 bps、最高优先级队列均已保留。原文存在重复排版片段,但公式主体明确。 **状态:** 已复核

P054已复核

类似地,借助命题 5,也可以从定理 2.1 推导出各种性能界。具体而言,如果输入受令牌桶到达曲线约束,则相应的界总结在推论 3 中。

“令牌桶到达曲线”“性能界”“推论 3”“定理 2.1”翻译准确;逻辑关系“借助命题 5 推导”已保留。未发现明显问题。 **状态:** 已复核

P055已复核

考虑一个业务流,它与其他流竞争在一条具有恒定比特率 \(c\) 的链路上传输,并且所考虑的流被赋予最高优先级。如果最高优先级流的业务具有令牌桶到达曲线 \(\alpha(t)=\rho t+\sigma\),且 \(\rho\leq c\),则有:(i)输出具有到达曲线 \(\rho t+\sigma+\rho\frac{l^M+l^{M_l}}{c}\),即 \(\forall s,t\geq 0\), \[ A^*(s,s+t)\leq \rho t+\sigma+\frac{\rho}{c}(l^M+l^{M_l}); \tag{17} \] (ii)积压 \(B(t)\) 的上界为,\(\forall t\geq 0\), \[ B(t)\leq \sigma+\frac{\rho}{c}(l^M+l^{M_l}); \tag{18} \] (iii)虚拟时延 \(D(t)\) 的上界为,\(\forall t\geq 0\): \[ D(t)\leq \frac{\sigma+l^M+l^{M_l}}{c}. \tag{19} \]

三个结论 (i)-(iii)、公式编号 (17)-(19)、条件 \(\rho\leq c\)、量词 \(\forall s,t\geq0\)、\(\forall t\geq0\) 均已保留。原文中虚拟时延公式前有 OCR 混排“\(\sigma + l^M + l^{M_l} c\)”片段,但 LaTeX 给出的是 \(\frac{\sigma+l^M+l^{M_l}}{c}\),译文采用该形式。 **状态:** 已复核

P056已复核

类似地,借助命题 5 和定理 2.2,可以为两个优先级系统的串联找到一个服务曲线。

“两个优先级系统的串联”“服务曲线”“命题 5 和定理 2.2”均已保留。未发现明显问题。 **状态:** 已复核

P057已复核

考虑一个依次穿越两个系统的流。两个系统都采用严格优先级调度,以便在各流之间共享恒定的服务速率(单位为 bps)\(c_i,(i=1,2)\)。该流在两个系统中都被赋予最高优先级。则该串联系统向该流提供的服务曲线为 \[ \min\{c_1,c_2\}\left(t-\frac{l^M+l^{M_l}}{c_1}-\frac{l^M+l^{M_l}}{c_2}\right)^+. \]

保留了“严格优先级调度”“两个系统”“最高优先级”“恒定服务速率 bps”及完整串联服务曲线。原文公式排版中分子 \(l^M+l^{M_l}\) 被 OCR 拆散,但结合命题 5 可识别。 **状态:** 已复核

P058已复核

第 3.3 节中的讨论已经指出,分组器的思想已在 [1]、[2]、[4] 中被采用,用来刻画分组化效应。特别地,对于命题 4 和命题 5 中所示的相应界,所建议的调整可以在 [1]、[2]、[4] 中找到。

“packetizer”译为“分组器”,“packetization effect”译为“分组化效应”;引用 [1]、[2]、[4] 与命题编号均已保留。未发现明显问题。 **状态:** 已复核

P059需人工复核

更具体地,对于恒定比特率情形,服务曲线被调整为与命题 4 中所示的相同;并且对于串联系统的服务曲线,该调整也相同。此外,输出的上界为,\(\forall s,t\geq 0\),\(A^*(s,s+t)\leq \rho t+\sigma+l^M\);积压的上界为,\(\forall t\geq 0\),\(B(t)\leq \sigma+l^M\);而对于虚拟时延,其上界为,\(\forall t\geq 0\),\(D(t)\leq \frac{\sigma}{c}\)。与推论 1 中所示的界相比,我们的输出界和积压界更紧。然而,对于虚拟时延,从忽略分组器效应得到的界更好。对于严格优先级情形,可以进行类似比较,并且也观察到,分组器方法给出了相同的服务曲线、较松的输出界和积压界,但给出了较紧的时延界。

恒定比特率情形、串联系统、输出/积压/虚拟时延三个界及比较结论均已保留。需注意“ignoring the packetizer effect”直译为“忽略分组器效应”,上下文可能意指由该方法导致的某种延迟界比较,建议结合前文确认术语一致性。 **状态:** 需人工复核

P060已复核

最后一条说明是,在服务建模中直接考虑分组化效应的方法已经在网络演算文献中被采用,例如在 [1]、[16] 和 [17] 中。近期工作 [17] 特别指出,对于两个基本系统,使用这种方法也可以推导出相同的时延界。关于更详细的讨论,由于超出了本文范围,感兴趣的读者可参见 [1]、[16] 和 [17]。

“服务建模”“分组化效应”“网络演算文献”“两个基本系统”“相同的时延界”及引用 [1]、[16]、[17] 均已保留。未发现明显问题。 **状态:** 已复核

P061需人工复核

网络演算分析已被应用于时间敏感网络中作为基础设定或默认设定的两个基本系统。研究重点一直放在分析它们的服务曲线表征和性能界限上。通过反例已经表明,在一些近期文献中被广泛用于这两个基本设定的服务曲线 s 实际上是有缺陷的。此外,文中还表明,对于由这些有缺陷的服务曲线推导出的输出界、积压界以及串接服务曲线结果,也可以构造反例。这意味着,为了考虑分组化效应,这两个基本设定的服务曲线表征以及相应推导出的性能界限都需要加以调整或重新研究。为此,本文通过探索将分组化直接纳入服务建模的思路,对服务曲线和性能界限进行了修正。这些结果不仅例示了如果忽略分组化效应,网络演算分析可能产生有缺陷的结果,也例示了如何在分析中纳入分组化效应。

术语方面,“network calculus”译为“网络演算”,“time-sensitive networks”译为“时间敏感网络”,“service curve”译为“服务曲线”,“performance bounds”译为“性能界限”,“output bound/backlog bound/concatenation service curve”分别译为“输出界/积压界/串接服务曲线”,与该领域常见译法一致。数字方面,原文提到“two basic systems”“two fundamental settings”,译文均保留“两个”。逻辑方面,先说明既有应用与关注点,再说明反例揭示服务曲线及其派生结果有缺陷,随后推出需要考虑分组化效应并给出修正思路,因果链条完整。公式/缩写方面,保留了服务曲线符号 s;但原文 “service curve s” 可能存在复数或符号排版上下文缺失,需结合全文确认 s 的具体格式和是否应为某个公式符号。

切换查看英文原文
P001Block 4

Network calculus (NC) is a theory for performance guarantee analysis of communication networks [ 1 ] [ 2 ] [ 3 ] [ 4 ]. A key idea of network calculus is to model traffic and service processes using some bounding functions and base the analysis on them. Among the various network calculus models, service curve models play a central role, based on which various performance bounds can be derived [ 1 ] [ 2 ] [ 3 ] [ 4 ]. Since its introduction in the early 1990s [ 5 ] [ 6 ], the network calculus has been extended and applied to various types of communication networks that are packet-switched. In particular, for IEEE 802.1 Time-Sensitive Networking (TSN) networks [ 7 ] and for IETF Deterministic Networking (DetNet) networks [ 8 ], the theory has been extensively utilized to construct service models and compute performance bounds. Representative results include [ 9 ], [ 10 ], [ 11 ] and [ 12 ]. A comprehensive review can be found in [ 13 ], and more recent results include [ 14 ] [ 15 ]. All these results are based on the service curve models of the transmission selection schemes studied, among which the constant bit rate link and strict priority scheduling are the most fundamental or default settings [ 7 ] [ 8 ].

P002Block 5

However, the investigation in this paper reveals that the widely adopted service curve characterization results, e.g. [ 9 ], [ 10 ], [ 11 ], [ 12 ], [ 14 ], and [ 15 ], for the two fundamental settings are faulty. In particular, counterexamples can be constructed, which disapproves the results of the adopted service curves. A closer look shows that the packetization effect is overlooked in them. The investigation is extended to examine the validity of the performance bounds derived from the faulty service curves. Counterexamples can also be constructed for output and backlog bounds as well as for the characterisation of the service curve of a concatenation system. This indicates that there is a need to update the service curve models and consequently also the performance bounds. To meet this need, corrected service curves and performance bounds for the two fundamental settings are derived, based on the idea of factoring the packetization effect directly into the service model. These results remind the necessity of taking the packetization effect into account when applying network calculus analysis.

P003Block 6

The rest is organized as follows. In the next section, the system model and network calculus basics are introduced. In Section 3, it is shown with counterexamples that the widely adopted service curves for the two fundamental settings are faulty due to ignoring the packetization effect. Then, a study on the impact of using such faulty service curves on performance bounds is conducted. At the end of Section 3, discussion on related results from the network calculus theory is provided, which reveals that adjustments suggested by the theory for packetization have been overlooked by the faulty service curve results. In Section 4, corrected service curves and performance bounds are proved. Finally, conclusions are drawn in Section 5.

P004Block 9

We consider systems in a packet-switched network. In particular, we focus on data traffic transmission over a constant bit rate link and through a priority queue that competes transmission over such a link with other priority queues. By convention, in such a system, a packet is said to have arrived (respectively, been served) when and only when its last bit has arrived (respectively, departed) [ 7 ]. When a packet arrives, the packet may be queued and the buffer size for the queue is assumed to be large enough, ensuring no packet loss. The queue is FIFO and initially empty.

P005Block 10

The system is modeled by an input traffic process A ​ (t) A(t), a service process S S, and an output traffic process A ∗ ​ (t) A^{*}(t) as illustrated in Figure 1. Specifically, A ​ (t) A(t) denotes the cumulative amount of traffic from the input flow entering the system and A ∗ ​ (t) A^{*}(t) the cumulative amount of traffic from the flow leaving the system, up to time t t (excluded). By convention, we adopt A ​ (0) = A ∗ ​ (0) = 0 A(0)=A^{*}(0)=0. In addition, we define A ​ (s, t) ≡ A ​ (t) − A ​ (s) A(s,t)\equiv A(t)-A(s) and A ∗ ​ (s, t) ≡ A ∗ ​ (t) − A ∗ ​ (s) A^{*}(s,t)\equiv A^{*}(t)-A^{*}(s), which respectively denote the amount of input traffic and the amount of output traffic in period [ s, t) [s,t). Since traffic at t t is excluded, A ​ (t, t) = 0 A(t,t)=0 by convention and so is A ∗ ​ (t, t) = 0 A^{*}(t,t)=0.

P006Block 11

In addition, we can also model the input and output processes of the flow using marked-point processes, where packetization of traffic is explicitly taken into account [ 1 ]. Specifically, for the input, the marked point process (a →, l →) (\overrightarrow{a},\overrightarrow{l}) consists of two sequences of variables a → = { a (n), n = 0, 1, 2, … } \overrightarrow{a}=\{a(n),n=0,1,2,...\} and l → = { l (n), n = 0, 1, 2, … } \overrightarrow{l}=\{l(n),n=0,1,2,...\}, where a ​ (n) a(n) denotes the arrival time of packet n n and l ​ (n) l(n) its length. For the output, a similar marked point process is defined which is (d →, l →) (\overrightarrow{d},\overrightarrow{l}) with d → = { d (n), n = 0, 1, 2, … } \overrightarrow{d}=\{d(n),n=0,1,2,...\}, where d ​ (n) d(n) denotes the departure time of the n n -th packet from the system. Here, the packet 0 is a virtual packet, and by convention a ​ (0) = 0 a(0)=0, l ​ (0) = 0 l(0)=0 and d ​ (0) = 0 d(0)=0.

P007Block 12

The backlog at time t t, denoted as B ​ (t) B(t), is: B ​ (t) = A ​ (t) − A ∗ ​ (t). B(t)=A(t)-A^{*}(t). (1) The delay of packet n (≥ 1) n(\geq 1), denoted by D ​ (n) D(n), is: D ​ (n) = d ​ (n) − a ​ (n). D(n)=d(n)-a(n). (2) In network calculus, a related delay concept, called virtual delay, has been adopted. Specifically, the virtual delay at time t (> 0) t(>0), denoted as D ​ (t) D(t), is defined as [ 1 ] [ 2 ] [ 3 ] [ 4 ]: D ​ (t) = inf { τ ≥ 0: A ​ (t) ≤ A ∗ ​ (t + τ) }. D(t)=\inf\{\tau\geq 0:A(t)\leq A^{*}(t+\tau)\}. (3)

P008Block 14

Let ℱ \mathbf{\mathcal{F}} denote the set of nonnegative nondecreasing functions, and ℱ 0 \mathbf{\mathcal{F}}_{0} its subset with f ​ (0) = 0 f(0)=0. By their definitions, A ​ (⋅) A(\cdot) and A ∗ ​ (⋅) A^{*}(\cdot) are both in ℱ 0 \mathbf{\mathcal{F}}_{0}.

P009Block 16

A flow A A is said to have an arrival curve α ∈ ℱ \alpha\in\mathbf{\mathcal{F}}, if for all 0 ≤ s ≤ t 0\leq s\leq t, the traffic A ​ (s, t) A(s,t) is upper-constrained by [ 2 ]: A ​ (s, t) ≤ α ​ (t − s). A(s,t)\leq\alpha(t-s). (4)

P010Block 18

A system is said to provide a service curve β ∈ ℱ 0 \beta\in\mathbf{\mathcal{F}}_{0}, if for any time t ≥ 0 t\geq 0, there exists some time s ∈ [ 0, t ] s\in[0,t] such that A ∗ ​ (t) ≥ A ​ (s) + β ​ (t − s) A^{*}(t)\geq A(s)+\beta(t-s) or equivalently, there holds for all t ≥ 0 t\geq 0 [ 2 ], A ∗ ​ (t) ≥ A ⊗ β ​ (t) ≡ inf 0 ≤ s ≤ t { A ​ (s) + β ​ (t − s) }. A^{*}(t)\geq A\otimes\beta(t)\equiv\inf_{0\leq s\leq t}\{A(s)+\beta(t-s)\}.

P011Block 20

If the input flow has an arrival curve α \alpha and the system provides to the input flow a service curve β \beta, there hold [ 2 ]: (i) the output has an arrival curve α ∗ ​ (t) ≡ sup u ≥ 0 { α ​ (u + t) − β ​ (u) } \alpha^{*}(t)\equiv\sup_{u\geq 0}\{\alpha(u+t)-\beta(u)\}, i.e. ∀ s, t ≥ 0 \forall s,t\geq 0, A ∗ ​ (s, s + t) ≤ α ∗ ​ (t); A^{*}(s,s+t)\leq\alpha^{*}(t); (5) (ii) the backlog B ​ (t) B(t) is upper-bounded by, ∀ t ≥ 0 \forall t\geq 0, B ​ (t) ≤ sup t ≥ 0 { α ​ (t) − β ​ (t) }; B(t)\leq\sup_{t\geq 0}\{\alpha(t)-\beta(t)\}; (6) (iii) the virtual delay D ​ (t) D(t) is upper-bounded by, ∀ t ≥ 0 \forall t\geq 0: D ​ (t) ≤ sup t ≥ 0 inf { τ ≥ 0: α ​ (t) ≤ β ​ (t + τ) }. D(t)\leq\sup_{t\geq 0}\inf\{\tau\geq 0:\alpha(t)\leq\beta(t+\tau)\}. (7)

P012Block 21

As an example, suppose that the input flow is constrained by a token bucket with token generating rate ρ \rho and bucket size σ \sigma [ 5 ] or has an arrival curve α ​ (t) = ρ ​ t + σ \alpha(t)=\rho t+\sigma. In addition, the system provides to the input a latency-rate service curve β ​ (t) = R ​ (t − T) + \beta(t)=R(t-T)^{+}, where R R is called the rate term and T T the latency term. If ρ ≤ R \rho\leq R, the bounds from Theorem 2.1 can be written as α ∗ ​ (t) \displaystyle\alpha^{*}(t) = \displaystyle= ρ ​ t + (σ + ρ ​ T) \displaystyle\rho t+(\sigma+\rho T) (8) B ​ (t) \displaystyle B(t) ≤ \displaystyle\leq σ + ρ ​ T \displaystyle\sigma+\rho T (9) D ​ (t) \displaystyle D(t) ≤ \displaystyle\leq σ R + T \displaystyle\frac{\sigma}{R}+T (10)

P013Block 22

In network calculus analysis, an important technique for finding the service curve characterization of a system makes use of the concept of strict service curve and its relation with the service curve model as summarized below.

P014Block 24

A system is said to provide a strict service curve β ∈ ℱ 0 \beta\in\mathbf{\mathcal{F}}_{0}, if during any backlogged period of length t t, the output satisfies [ 2 ] A ∗ ​ (t) ≥ β ​ (t) A^{*}(t)\geq\beta(t).

P015Block 26

If β (∈ ℱ 0 \beta(\in\mathbf{\mathcal{F}}_{0}) is a strict service curve of a system, it is also a service curve of the system [ 2 ].

P016Block 27

For a concatenation system, the following result is important for finding its service curve characterization.

P017Block 29

Consider a flow that traverses two systems S 1 S_{1} and S 2 S_{2} in sequence. If each system S i, (i = 1, 2) S_{i},(i=1,2) offers a service curve of β i \beta_{i} to its input, then the concatenated system offers a service curve of β 1 ⊗ β 2 \beta_{1}\otimes\beta_{2} to the flow [ 2 ].

P018Block 31

In this paper, we focus on two fundamental transmission selection settings in a packet-switched network. One is a (work-conserving) constant bit rate link, and the other is a strict priority queue for packet transmission on such a link. The former is the foundation of any other transmission selection algorithm, while the latter is commonly implemented, e.g. as the default setting for time-sensitive networking [ 7 ]. For the two fundamental cases, the following service curve results have been widely applied, e.g. in [ 9 ] [ 10 ] [ 11 ] [ 12 ] [ 13 ] [ 14 ] and [ 15 ]: • A (work-conserving) link with constant bit rate c c provides a (strict) service curve c ​ t ct. • When (non-preemptive) strict priority is applied on the link, the highest priority queue receives a (strict) service curve c ​ (t − l M l c) + c(t-\frac{l^{M_{l}}}{c})^{+}, where l M l l^{M_{l}} denotes the maximum packet length of all lower priority queues and (x) + ≡ max ⁡ { x, 0 } (x)^{+}\equiv\max\{x,0\}.

P019Block 32

A (work-conserving) link with constant bit rate c c provides a (strict) service curve c ​ t ct.

P020Block 33

When (non-preemptive) strict priority is applied on the link, the highest priority queue receives a (strict) service curve c ​ (t − l M l c) + c(t-\frac{l^{M_{l}}}{c})^{+}, where l M l l^{M_{l}} denotes the maximum packet length of all lower priority queues and (x) + ≡ max ⁡ { x, 0 } (x)^{+}\equiv\max\{x,0\}.

P021Block 34

Unfortunately, as shown in the following Section 3.1, both are faulty.

P022Block 37

The intuition behind using c ​ t ct as a (strict) service curve of the system is as follows. Since the link is work-conserving, during any backlogged period, the link outputs traffic (in bits) at a rate c c and hence has a strict service curve c ​ t ct, with which c ​ t ct as a service curve can also be concluded from Proposition 1. While this sounds straightforward, the following example and discussion highlight that special care is needed when packetization effect needs to be taken into account.

P023Block 38

Consider the transmission of a packet n n on the link as illustrated in Figure 2. Without considering the packetization effect, we would have A ​ (s, t) = A ∗ ​ (s, t) = c ​ (t − a ​ (n)) A(s,t)=A^{*}(s,t)=c(t-a(n)) (in bits). However, under the packet model, taking packetization into account, we actually have A ​ (s, t) = l ​ (n) A(s,t)=l(n) while A ∗ ​ (s, t) = 0 A^{*}(s,t)=0. The former is because at time a ​ (n) a(n) which is within [ s, t) [s,t), the (last bit of the) packet has arrived so that transmission can start. In contrast, for A ∗ ​ (s, t) A^{*}(s,t), d ​ (n) d(n) is not within the period, which means that the last bit of the packet has not finished transmission, so the packet is not considered to have been transmitted or served in the period considered [ s, t) [s,t). Because 0 ≤ c ​ (t − a ​ (n)) ≤ l ​ (n) 0\leq c(t-a(n))\leq l(n), we have A ∗ ​ (s, t) ≤ c ​ (t − s) A^{*}(s,t)\leq c(t-s), which contracts the definition of strict service curve if c ​ t ct were used as a strict service curve.

P024Block 39

The discussion above disapproves the validity of using c ​ t ct as a strict service curve. However, the question of whether c ​ t ct is a valid service curve remains. For this, we construct a case where A ∗ ​ (t) ≥ A ⊗ β ​ (t) A^{*}(t)\geq A\otimes\beta(t) does not hold for β ​ (t) = c ​ t \beta(t)=ct.

P025Block 40

Consider the first packet. Let a ​ (1) a(1) be its arrival time and l ​ (1) (> 0) l(1)(>0) its length. Then, for any time t ∈ [ a ​ (1), a ​ (1) + l ​ (1) c) t\in[a(1),a(1)+\frac{l(1)}{c}), the period (a ​ (1), t) (a(1),t) is backlogged because the packet has arrived but has not left. In addition, we have: A ⊗ β ​ (t) \displaystyle A\otimes\beta(t) = \displaystyle= inf 0 ≤ s ≤ t { A ​ (s) + c ​ (t − s) } \displaystyle\inf_{0\leq s\leq t}\{A(s)+c(t-s)\} (11) = \displaystyle= min ⁡ { inf 0 ≤ s < a ​ (1) { A ​ (s) + c ​ (t − s) }, inf a ​ (1) ≤ s ≤ t { A ​ (s) + c ​ (t − s) } } \displaystyle\min\left\{\inf_{0\leq s<a(1)}\{A(s)+c(t-s)\},\inf_{a(1)\leq s\leq t}\{A(s)+c(t-s)\}\right\} = \displaystyle= min ⁡ { c ​ (t − a ​ (1)), l ​ (1) } \displaystyle\min\{c(t-a(1)),l(1)\} = \displaystyle= c ​ (t − a ​ (1)) > 0 \displaystyle c(t-a(1))>0 Note that A ∗ ​ (t) = 0 A^{*}(t)=0 because a packet is considered to have been served only when its last bit has left, the first packet has not left at t (< a ​ (1) + l ​ (1) c) t(<a(1)+\frac{l(1)}{c}) and therefore the packet cannot be counted in A ∗ ​ (t) A^{*}(t). In other words, for any t ∈ [ a ​ (1), a ​ (1) + l ​ (1) c) t\in[a(1),a(1)+\frac{l(1)}{c}), A ⊗ β ​ (t) > A ∗ ​ (t) A\otimes\beta(t)>A^{*}(t), which contradicts the requirement of A ∗ ​ (t) ≥ A ⊗ β ​ (t), ∀ t ≥ 0 A^{*}(t)\ \geq A\otimes\beta(t),\forall t\geq 0 for β \beta to be a service curve. Proposition 2 is now concluded.

P026Block 42

For a system with constant bit rate c c (in bps), c ​ t ct is neither a strict service curve nor a service curve.

P027Block 44

For the (non-preemptive) strict priority case, the intuition behind using c ​ (t − l M l c) + c(t-\frac{l^{M_{l}}}{c})^{+} as a (strict) service curve is as follows. In the formulation, l M l c \frac{l^{M_{l}}}{c} factors in the non-preemption effect, which is, upon arrival, a highest priority packet will have to wait for the packet under transmission to complete even though the packet under transmission is from a lower priority queue. However, as discussed for Proposition 2, when packetization is taken into account, c ​ t ct is not a (strict) service curve for the link. In particular, factoring the non-preemption effect and adding l M l c \frac{l^{M_{l}}}{c} at a ​ (n) a(n) in Figure 2, the same analysis taking packetization into account can be conducted for the highest priority queue, from which we can consequently conclude Proposition 3.

P028Block 46

For the highest priority queue on a link with constant bit rate c c, c ​ (t − l M l c) + c(t-\frac{l^{M_{l}}}{c})^{+} is neither a strict service curve nor a service curve.

P029Block 48

The impact of packetization on the service curve characterization results as investigated above and summarized in Propositions 2 and 3 has two immediate implications:

P030Block 49

• The various performance bounds derived from the faulty service curves, such as output arrival curve, backlog and delay bounds, must be re-examined for their validity and possibly updated. • For any complex setting that builds on the two fundamental cases, if its service curve result implies a faulty service curve for either of the two fundamental cases as indicated in Propositions 2 and 3, the service curve result for the complex setting as well as the correspondingly derived performance bounds will need to be re-examined and possibly updated.

P031Block 50

The various performance bounds derived from the faulty service curves, such as output arrival curve, backlog and delay bounds, must be re-examined for their validity and possibly updated.

P032Block 51

For any complex setting that builds on the two fundamental cases, if its service curve result implies a faulty service curve for either of the two fundamental cases as indicated in Propositions 2 and 3, the service curve result for the complex setting as well as the correspondingly derived performance bounds will need to be re-examined and possibly updated.

P033Block 52

For the latter, since a fundamental case is a special case of the complex setting, if the result for the special case is faulty, the result for the complex setting cannot hold either. For the former, it is worth highlighting that the constant bit rate case is implied in the strict priority case (SP). Specifically, it is a special case of SP with a single queue in the system.

P034Block 54

In this subsection, we investigate the impact of a faulty service curve on the correspondingly obtained performance bound results. By constructing counterexamples, we show that the faulty service can lead to faulty output bound, faulty backlog bound and faulty concatenation service curve, while for delay bound the same conclusion cannot be made. We focus on the constant bit rate case. Because it is the most fundamental setting and is a special case of SP, the related conclusion on the invalidity of a bound is also applicable to the SP case.

P035Block 56

To ease discussion, a simple input case is considered. Specifically, the input flow sends packets periodically to the system. Let τ \tau denote the interval between two adjacent packets. All, except packet 1, have the same length l l, while the length of packet 1 is σ (> l) \sigma(>l). For stability, assume l τ < c \frac{l}{\tau}<c. For this input case, it can be verified that it has an arrival curve α ​ (t) = l τ ​ t + σ \alpha(t)=\frac{l}{\tau}t+\sigma. An illustration of A ​ (t) A(t) and α ​ (t) \alpha(t) is presented in Fig. 3, where the output A ∗ ​ (t) A^{*}(t) and an output arrival curve α ∗ ​ (t) \alpha^{*}(t) that uses the same slope as α \alpha are also illustrated. (Remark: For α \alpha and α ∗ \alpha^{*}, they correspond to intervals starting from a ​ (1) a(1) and d ​ (1) d(1) respectively.) For the output, applying β ​ (t) = c ​ t \beta(t)=ct as a service curve to Theorem 2.1 would give A ∗ ​ (s, s + t) ≤ l τ ​ t + σ = α ​ (t) A^{*}(s,s+t)\leq\frac{l}{\tau}t+\sigma=\alpha(t), ∀ s, t ≥ 0 \forall s,t\geq 0, or in other words α ∗ = α \alpha^{*}=\alpha. However, as illustrated in Fig. 3, α ∗ ​ (t) \alpha^{*}(t) needs to have a higher σ ∗ \sigma^{*} than the initial σ \sigma. In other words, the output is not constrained by α ​ (t) \alpha(t) and therefore using α \alpha as an upper bound on the output, based on derivation from the faulty service curve, is wrong.

P036Block 58

For backlog, applying β ​ (t) = c ​ t \beta(t)=ct as service curve to Theorem 2.1 gives B ​ (t) ≤ σ B(t)\leq\sigma, ∀ t ≥ 0 \forall t\geq 0. However, this backlog bound σ \sigma is incorrect. Consider the same case as illustrated in Fig. 3. In particular, before packet 1 finishes, packet 2 has arrived. Hence, B ​ (t) B(t) for t = d ​ (1) − t=d(1)_{-}, i.e. the time just before packet 1 has finished its transmission, the backlog in the system is σ + l \sigma+l where σ \sigma is the size of packet 1 and l l is that of packet 2. Since σ + l > σ \sigma+l>\sigma, the backlog bound σ \sigma from the faulty service curve is therefore incorrect.

P037Block 60

For delay, applying β ​ (t) = c ​ t \beta(t)=ct as service curve to Theorem 2.1 gives D ​ (t) ≤ σ c D(t)\leq\frac{\sigma}{c}, ∀ t ≥ 0 \forall t\geq 0. Surprisingly, unlike that the output bound and backlog bound derived from the faulty service curve are also faulty, no similar conclusion can be made for the delay bound. This is because σ c \frac{\sigma}{c} is actually a valid delay bound, which has been proved but using another service-modeling technique [ 16 ]. More remarks related to this are provided in Section 3.3.

P038Block 62

Assume a flow traverses two switches S 1 S_{1} and S 2 S_{2} in sequence where the corresponding output links have constant bit rate c 1 c_{1} and c 2 c_{2} respectively. Let β i ​ (t) = c i ​ t, (i = 1, 2) \beta_{i}(t)=c_{i}t,(i=1,2). If they were correct service curves for S 1 S_{1} and S 2 S_{2} respectively, we would have β 1 ⊗ β 2 ​ (t) = min ⁡ { c 1, c 2 } ​ t \beta_{1}\otimes\beta_{2}(t)=\min\{c_{1},c_{2}\}t to be a service curve for the concatenation system. Then, if the input has an arrival curve of ρ ​ t + σ \rho t+\sigma with ρ ≤ min ⁡ { c 1, c 2 } \rho\leq\min\{c_{1},c_{2}\}, the delay of any packet would be upper-bounded by σ min ⁡ { c 1, c 2 } \frac{\sigma}{\min\{c_{1},c_{2}\}}, for which, however, counter examples can be constructed. Specifically, for simplicity, consider the case where all packets have the same length l l, σ = l \sigma=l and c 1 = c 2 ≡ c c_{1}=c_{2}\equiv c. Then we have σ min ⁡ { c 1, c 2 } = l c \frac{\sigma}{\min\{c_{1},c_{2}\}}=\frac{l}{c}. Furthermore, it is easily verified that for any packet, its delay is at least 2 × l c 2\times\frac{l}{c} due to its transmission time of l c \frac{l}{c} on both systems, which is larger than l c \frac{l}{c}. This implies that concatenation of faulty service curves leads to a faulty concatenation service curve for the concatenated system.

P039Block 64

It is worth highlighting that the service curves in the same forms for similar systems have been introduced in the network calculus theory but under different contexts. • In [ 1 ], discrete time is adopted and the service rate c c is in the number of packets per unit time. Under these assumptions, c ​ t ct is proved to be a service curve, called an f f -server in [ 1 ], for the constant rate server and for the highest priority queue. • In [ 2 ] and [ 4 ], the analysis and results do not depend on whether the time model is discrete or continuous, which is also the case in the present paper. In [ 2 ] and [ 4 ], by defining the amount of service counted at the bit level, c ​ t ct is shown to be a strict service curve for the constant bit rate case and so is c ​ (t − l M l c) + c(t-\frac{l^{M_{l}}}{c})^{+} for the highest priority queue on such a link (cf. Proposition 1.3.4 in [ 2 ] and Section 1.2 in [ 4 ]).

P040Block 65

In [ 1 ], discrete time is adopted and the service rate c c is in the number of packets per unit time. Under these assumptions, c ​ t ct is proved to be a service curve, called an f f -server in [ 1 ], for the constant rate server and for the highest priority queue.

P041Block 66

In [ 2 ] and [ 4 ], the analysis and results do not depend on whether the time model is discrete or continuous, which is also the case in the present paper. In [ 2 ] and [ 4 ], by defining the amount of service counted at the bit level, c ​ t ct is shown to be a strict service curve for the constant bit rate case and so is c ​ (t − l M l c) + c(t-\frac{l^{M_{l}}}{c})^{+} for the highest priority queue on such a link (cf. Proposition 1.3.4 in [ 2 ] and Section 1.2 in [ 4 ]).

P042Block 67

To account for the effect of packetization, particularly that a flow is composed of a sequence of (variable-length) packets and that the scheduling algorithm is at the packet level while not at the bit level, a novel concept called packetizer is introduced in [ 1 ] and also adopted in [ 2 ] and [ 4 ]. Its idea is to treat the system as the concatenation of two conceptual subsystems, as shown in Fig. 4. One is the bit-by-bit system, which is the part of the system before packetization is taken effect, and the other is a packetizer that assembles output traffic from the previous subsystem into packets.

P043Block 68

With the packetizer concept, it is highlighted in [ 1 ], [ 2 ] and [ 4 ] that additional terms may need to be added to the service curve and performance bound results. In particular, the service curve, the backlog bound, and the concatenation service curve must be adjusted, although the packetizer is shown to not increase the maximum packet delay [ 1 ], [ 2 ] [ 4 ]. Unfortunately, this seems to have been largely overlooked in the recent application of network calculus analysis, e.g., in [ 9 ], [ 10 ], [ 11 ], [ 12 ] [ 13 ], [ 14 ] and [ 15 ], where the faulty service curves are directly adopted without considering the packetization effect.

P044Block 69

Unlike relying on the concept of packetizer to account for the packetization effect in [ 1 ], [ 2 ], and [ 4 ], we take packetization into direct consideration when modeling the arrival and service processes. More specifically, as introduced in Section 2, we adopt the convention that a packet is said to have arrived (respectively, been served) when and only when its last bit has arrived (respectively, departed) and hence model the arrival and departure processes as marked point processes. Based on this idea, we conduct network calculus analysis and present corrected service curves and performance bounds for the two fundamental cases in the next Section 4.

P045Block 72

For the constant bit rate case, corrected service curves are presented in Proposition 4.

P046Block 74

A system with constant bit rate c c offers a strict service curve and a service curve c ​ (t − l M c) + c(t-\frac{l^{M}}{c})^{+}, where l M l^{M} denotes the maximum packet length in the system.

P047Block 76

Consider any backlogged period (s, t ] (s,t] as shown in Figure 5, and let n 0 n_{0} denote the packet whose arrival starts the backlogged period. Clearly, we have s ≥ a ​ (n 0) s\geq a(n_{0}). Without loss of generality, suppose that packet m m is the first packet that leaves after time s s, and n n the first packet that departs after time t t. By their definitions, we must have d ​ (m − 1) < s ≤ d ​ (m) d(m-1)<s\leq d(m) and d ​ (n − 1) ≤ t < d ​ (n) d(n-1)\leq t<d(n). Since the system is backlogged during (s, t ] (s,t], it must also be so during (i) (s, d ​ (m) ] (s,d(m)], (ii) (d ​ (m), d ​ (n − 1) ] (d(m),d(n-1)] and (iii) (d ​ (n − 1), t ] (d(n-1),t]. Because the system has a constant bit rate c c, during any backlogged period of duration τ \tau, the amount of traffic it serves / transmits is c ​ τ c\tau (in bits). We hence have c ​ (d ​ (m) − s) ≤ l ​ (m) c(d(m)-s)\leq l(m), c ​ [ d ​ (n − 1) − d ​ (m) ] = ∑ k = m + 1 n − 1 l ​ (k) c[d(n-1)-d(m)]=\sum_{k=m+1}^{n-1}l(k), and c ​ [ t − d ​ (n − 1) ] ≤ l ​ (n) ≤ l M c[t-d(n-1)]\leq l(n)\leq l^{M}. Since A ∗ ​ (s, t) = ∑ k = m n − 1 l ​ (k) A^{*}(s,t)=\sum_{k=m}^{n-1}l(k) as illustrated by Fig. 5, we have A ∗ ​ (s, t) \displaystyle A^{*}(s,t) = \displaystyle= l ​ (m) + c ​ [ d ​ (n − 1) − d ​ (m) ] \displaystyle l(m)+c[d(n-1)-d(m)] (12) ≥ \displaystyle\geq c ​ [ d ​ (n − 1) − s ] ≥ c ​ (t − s − l M c) \displaystyle c[d(n-1)-s]\geq c(t-s-\frac{l^{M}}{c}) which, together with the fact that A ∗ ​ (s, t) ≥ 0 A^{*}(s,t)\geq 0, ends the proof.

P048Block 77

With Proposition 4, various performance bounds can immediately be derived from Theorem 2.1. As a specific example where the input is constrained by a token-bucket arrival curve, they are summarized in Corollary 1.

P049Block 79

Consider a traffic flow transmitting over a link that has a constant bit rate c c. If the traffic has a token-bucket arrival curve α ​ (t) = ρ ​ t + σ \alpha(t)=\rho t+\sigma with ρ ≤ c \rho\leq c, there hold: (i) the output has an arrival curve ρ ​ t + σ + ρ ​ l M c \rho t+\sigma+\rho\frac{l^{M}}{c}, i.e. ∀ s, t ≥ 0 \forall s,t\geq 0, A ∗ ​ (s, s + t) ≤ ρ ​ t + σ + ρ c ​ l M; A^{*}(s,s+t)\leq\rho t+\sigma+\frac{\rho}{c}l^{M}; (13) (ii) the backlog B ​ (t) B(t) is upper-bounded by, ∀ t ≥ 0 \forall t\geq 0, B ​ (t) ≤ σ + ρ c ​ l M; B(t)\leq\sigma+\frac{\rho}{c}l^{M}; (14) (iii) the virtual delay D ​ (t) D(t) is upper-bounded by, ∀ t ≥ 0 \forall t\geq 0: D ​ (t) ≤ σ + l M c. D(t)\leq\frac{\sigma+l^{M}}{c}. (15)

P050Block 80

In addition, with Proposition 4 and Theorem 2.2, a corrected concatenation service curve can be found for the counterexample case discussed in Section 3.2.

P051Block 82

Consider a flow that traverses two switches in sequence. The corresponding output links have constant bit rate c i, (i = 1, 2) c_{i},(i=1,2) respectively. The concatenation system offers to the flow a service curve of min ⁡ { c 1, c 2 } ​ (t − l M c 1 − l M c 2) + \min\{c_{1},c_{2}\}(t-\frac{l^{M}}{c_{1}}-\frac{l^{M}}{c_{2}})^{+}.

P052Block 84

For the strict priority case, a corrected strict service curve, which is also a service curve, is presented in Proposition 5. For the proof, it is similar to that of Proposition 4. The key difference is that s s may be within the transmission period of a lower priority packet that has started its transmission and cannot be preempted by the arrival of the highest priority packet n 0 n_{0}. In such a scenario, we have c ​ (s − d ​ (n 0)) ≤ l ​ (n 0) + l M l c(s-d(n_{0}))\leq l(n_{0})+l^{M_{l}}, c ​ (d ​ (n − 1) − d ​ (n 0)) = ∑ k = n 0 + 1 n − 1 l ​ (k) c(d(n-1)-d(n_{0}))=\sum_{k=n_{0}+1}^{n-1}l(k), and c ​ [ t − d ​ (n − 1) ] ≤ l ​ (n) ≤ l M c[t-d(n-1)]\leq l(n)\leq l^{M}. From these, we obtain A ∗ ​ (s, t) \displaystyle A^{*}(s,t) = \displaystyle= ∑ k = n 0 n − 1 l ​ (k) ≥ c ​ [ d ​ (n − 1) − s − l M l c ] ≥ c ​ (t − s − l M c − l M l c) \displaystyle\sum_{k=n_{0}}^{n-1}l(k)\geq c[d(n-1)-s-\frac{l^{M_{l}}}{c}]\geq c(t-s-\frac{l^{M}}{c}-\frac{l^{M_{l}}}{c}) (16) where l M l^{M} and l M l l^{M_{l}} respectively denote the maximum packet length of the considered highest priority queue and the maximum packet length of all lower priority queues. For other scenarios, where the arrival of the highest priority packet n 0 n_{0} does not see any ongoing transmission of a lower priority packet, they are the same as in the proof of Proposition 4 and hence A ∗ ​ (s, t) ≥ c ​ (t − s − l M c) A^{*}(s,t)\geq c(t-s-\frac{l^{M}}{c}). Combining all scenarios and the fact that A ∗ ​ (s, t) ≥ 0 A^{*}(s,t)\geq 0, Proposition 5 can be concluded.

P053Block 86

For the highest priority queue in a system with constant service rate c c (in bps), c ​ (t − l M c − l M l c) + c(t-\frac{l^{M}}{c}-\frac{l^{M_{l}}}{c})^{+} is both a strict service curve and a service curve.

P054Block 87

Similarly, with Proposition 5, various performance bounds can also be derived from Theorem 2.1. Specifically, if the input is constrained by a token-bucket arrival curve, the corresponding bounds are summarized in Corollary 3.

P055Block 89

Consider a traffic flow competing with other flows to transmit on a link that has a constant bit rate c c, and the considered flow is given the highest priority. If the traffic of the highest priority flow has a token-bucket arrival curve α ​ (t) = ρ ​ t + σ \alpha(t)=\rho t+\sigma with ρ ≤ c \rho\leq c, there hold: (i) the output has an arrival curve ρ ​ t + σ + ρ ​ l M + l M l c \rho t+\sigma+\rho\frac{l^{M}+l^{M_{l}}}{c}, i.e. ∀ s, t ≥ 0 \forall s,t\geq 0, A ∗ ​ (s, s + t) ≤ ρ ​ t + σ + ρ c ​ (l M + l M l); A^{*}(s,s+t)\leq\rho t+\sigma+\frac{\rho}{c}(l^{M}+l^{M_{l}}); (17) (ii) the backlog B ​ (t) B(t) is upper-bounded by, ∀ t ≥ 0 \forall t\geq 0, B ​ (t) ≤ σ + ρ c ​ (l M + l M l); B(t)\leq\sigma+\frac{\rho}{c}(l^{M}+l^{M_{l}}); (18) (iii) the virtual delay D ​ (t) D(t) is upper-bounded by, ∀ t ≥ 0 \forall t\geq 0: D ​ (t) ≤ σ + l M + l M l c. D(t)\leq\frac{\sigma+l^{M}+l^{M_{l}}}{c}. (19)

P056Block 90

Similarly, with Proposition 5 and Theorem 2.2, a service curve can be found for the concatenation of two priority systems.

P057Block 92

Consider a flow that traverses two systems in sequence. Both systems adopt strict priority scheduling to share among flows the service rate (in bps) c i, (i = 1, 2) c_{i},(i=1,2), which is constant. The flow is given highest priority at both systems. Then, the concatenation system offers the flow a service curve of min ⁡ { c 1, c 2 } ​ (t − l M + l M l c 1 − l M + l M l c 2) + \min\{c_{1},c_{2}\}(t-\frac{l^{M}+l^{M_{l}}}{c_{1}}-\frac{l^{M}+l^{M_{l}}}{c_{2}})^{+}.

P058Block 94

The discussion in Section 3.3 has indicated that the idea of packetizer has been adopted in [ 1 ] [ 2 ] [ 4 ] to account for the packetization effect. In particular, for the corresponding bounds as shown in Propositions 4 and 5, the suggested adjustments can be found in [ 1 ] [ 2 ] [ 4 ].

P059Block 95

More specifically, for the constant bit case, the service curve is adjusted to be the same as shown in Proposition 4, and the service curve for the concatenation system, the adjustment is also the same. In addition, the output is upper-bounded by, ∀ s, t ≥ 0, A ∗ ​ (s, s + t) ≤ ρ ​ t + σ + l M \forall s,t\geq 0,A^{*}(s,s+t)\leq\rho t+\sigma+l^{M} and the backlog is upper-bounded by ∀ t ≥ 0, B ​ (t) ≤ σ + l M \forall t\geq 0,B(t)\leq\sigma+l^{M}, while for virtual delay, it is upper-bounded by ∀ t ≥ 0, D ​ (t) ≤ σ c \forall t\geq 0,D(t)\leq\frac{\sigma}{c}. Comparing with the bounds shown in Corollary 1, our output and backlog bounds are tighter. However, for virtual delay, the bound derived from ignoring the packetizer effect is better. For the strict priority case, similar comparison can be conducted, and it is also observed that the packetizer approach gives the same service curves, looser output and backlog bounds, but tighter delay bound.

P060Block 96

A final remark is that the approach of taking the packetization effect directly into account in service-modeling has been exploited in the network calculus literature, e.g. in [ 1 ] [ 16 ] and [ 17 ]. Recent work [ 17 ] particularly indicates that the same delay bounds can also be derived for the two basic systems using this approach. For a more detailed discussion, which is beyond the scope of the present paper, interested readers are referred to [ 1 ] [ 16 ] and [ 17 ].

P061Block 98

Network calculus analysis has been applied to two basic systems that are fundamental or default settings in time-sensitive networks. The focus has been on analyzing their service curve characterizations and performance bounds. It was shown through counterexamples that the service curve s, which have been widely adopted in some recent literature for the two fundamental settings, are actually faulty. Additionally, it was also shown that for the output bound, backlog bound and concatenation service curve results derived from the faulty service curves, counterexamples can also be constructed. This implies that both the service curve characterizations of the two fundamental settings and the correspondingly derived performance bounds need to be adjusted or re-investigated to account for the packetization effect. To this end, the service curves and performance bounds were corrected by exploring the idea of factoring packetization directly into service-modeling. The results exemplify not only that if the packetization effect is overlooked, network calculus analysis can produce faulty results, but also how the packetization effect can be factored in the analysis.