edx 4G Network Essentials Week 3: 7 - PDCP and Global Vision

Up to now we have focused on what happens between an
eNodeB and the UEs.
到目前为止，我们一直关注eNodeB和UE之间发生的事情。

In this video, we will see how this radio interface is
connected to the core network and therefore with the rest
of the world through the IP protocol.
在本视频中，我们将了解该无线接口如何通过IP协议连接到核心网络，从而与世界其他地方连接。

This is the role of the PDCP protocol which
relies on the top of the radio interface protocol stack.
这是PDCP协议的作用，它依赖于无线电接口协议栈的顶部。

Next, we’ll put in perspective all the principles we have
seen this week to create a global view of the radio interface.
接下来，我们将了解本周我们所看到的所有原则，以创建无线电接口的全局视图。

PDCP stands for Packet Data Convergence Protocol.

PDCP代表分组数据汇聚协议。

It is implemented on top of
every instance of R. L. C,
except those working in Transparent Mode.
除了在透明模式下工作的那些实例之外，它在R.L.C的每个实例之上实现。

It provides the interface with the core of the network,
in other words, with the IP protocol for users’ data
and with R. R. C for signalling messages.
它提供与网络核心的接口，换句话说，提供用户数据的IP协议和用于信令消息的R. R.C.

PDCP provides three types of service.
PDCP提供三种类型的服务。

To start: header compression.
开始：标头压缩。

As you know, applications rely on protocol stacks and
each protocol adds its own header.
如您所知，应用程序依赖于协议栈，每个协议都添加自己的头。

For example, VoIP data are typically 30 bytes long.
例如，VoIP数据通常为30个字节长。

They are encapsulated in RTP
which adds a 12 bytes long header,
then, they are encapsulated in UDP which adds 8 bytes,
and finally in IPv6 which adds 40 bytes.
它们被封装在RTP中，它增加了一个12字节长的报头，然后，它们被封装在UDP中，增加了8个字节，最后在IPv6中增加了40个字节。

so, the total length of the headers is 60 bytes.
所以，标题的总长度是60个字节。

So, we are transmitting twice as much protocol data as useful data.
因此，我们传输的协议数据是有用数据的两倍。

These protocol data change very little from one packet to another.
这些协议数据从一个数据包到另一个数据包变化很小。

Hence the possibility of compression.
因此压缩的可能性。

To do this, L. T. E uses a standard Internet protocol
called ROHC or Robust Header Compression.
为此，L.T.E使用称为ROHC或鲁棒标头压缩的标准互联网协议。

It is no coincidence that L. T. E re-uses
protocols from the Internet.
L. T. E重新使用来自互联网的协议并非巧合。

Indeed, one goal of L. T. E.
is to reuse when possible, existing standards,
notably for the core of its network.
实际上，L。T. E.的一个目标是在可能的情况下重用现有标准，特别是其网络的核心。

Another role of PDCP is to avoid packet loss
or the de-sequencing that can happen during handovers.
PDCP的另一个作用是避免丢包或切换期间可能发生的解码。

We saw that R. L. C manages retransmissions and
re-sequences, but only within the cell.
我们看到R. L. C管理重传和重新序列，但仅限于小区内。

With PDCP, when changing cell,
the old eNodeB can inform the new one about the status of
the current transmissions and can forward data waiting to be transmitted.
利用PDCP，当改变小区时，旧的eNodeB可以向新的eNodeB通知当前传输的状态并且可以转发等待传输的数据。

The last function of PDCP is about security.
PDCP的最后一个功能是关于安全性。

Obviously, the radio link is particularly vulnerable
in terms of security.
显然，无线电链路在安全性方面特别容易受到攻击。

Therefore, PDCP enables data cyphering to guarantee confidentiality.
因此，PDCP使数据加密能够保证机密性。

And it offers an integrity
control system to verify that signalling data were
not modified during transmission.
它还提供完整性控制系统，以验证在传输过程中信号数据是否未被修改。

Not all PDCP functions are used in every case.
并非所有PDCP功能都适用于所有情况。

Here is a summary.
这是一个总结。

Header compression, for example, will only work for data encapsulated in IP.
例如，标头压缩仅适用于封装在IP中的数据。

So it can’t be implemented for R. R. C control messages.
因此无法实现R. R. C控制消息。

Handover-related loss prevention only works for R. L. C instances
working in Acknowledged Mode.
与切换相关的损失防止仅适用于以确认模式工作的R. L. C实例。

Cyphering is always possible.
加密始终是可能的。

It is optional but strongly recommended.
它是可选的，但强烈建议。

Finally, integrity control is only possible for control messages.

最后，完整性控制仅适用于控制消息。

But that is where it is the most important, because if
the system considers a corrupted control message, it is a
direct security flaw for L. T. E.
但这是最重要的地方，因为如果系统考虑到损坏的控制消息，那么它是L. T. E.的直接安全漏洞。

And if applications need integrity control, they can
implement it by themselves.

如果应用程序需要完整性控制，他们可以自己实现。

This chapter about the radio interface is about to finish.
关于无线电接口的这一章即将完成。

Let’s sum up what we have seen this week.
让我们总结一下本周所看到的情况。

This diagram presents a synthesized view of the radio
interface protocol stack.
该图呈现了无线电接口协议栈的合成视图。

Going from the bottom to the top.
从底部到顶部。

We first see the physical layer.
我们首先看到物理层。

It takes care of error correction and modulation.
它负责纠错和调制。

Above, the MAC layer controls independently for each terminal the
choice of the modulation used by physical layer.
它负责纠错和调制。在此之后，MAC层独立地控制每个终端选择物理层使用的调制。

This defines the transmission capacity.
这定义了传输容量。

On the eNodeB, the MAC layer ensures resource allocation
for both the uplink and downlink.
在eNodeB上，MAC层确保上行链路和下行链路的资源分配。

It also takes care of low-level transmission reliability
with a repetition mechanism called H. A. R. Q.

它还通过称为H. A. R. Q.的重复机制来处理低级传输可靠性。

And builds the transport blocks by
multiplexing the data from different logical channels.
并通过多路复用来自不同逻辑信道的数据来构建传输块。

The R. L. C layer proposes optional re-sequencing,
segmentation, and retransmission services.

R.L.C层提出可选的重新排序，分段和重传服务。

Several R. L. C instances run in parallel, corresponding to different
applications and different levels of service.
几个R.L.C实例并行运行，对应于不同的应用和不同的服务级别。

Finally, the PDCP layer implements
the interface with the core network; under IP for useful
data, and R. R. C for signalling messages.
最后，PDCP层实现与核心网络的接口; 在IP下用于有用数据，而R. R. C用于信令消息。

It proposes optional services of header compression,
handover mitigation and security.

它提出了报头压缩，切换缓解和安全性的可选服务。

This last diagram represents the path followed by data packets.
最后一个图表表示数据包所遵循的路径。

User data on IP are shown in pink
and an R. R. C control message is shown in blue.

IP上的用户数据以粉红色显示，而R. R. C控制消息以蓝色显示。

It’s more of a reference diagram but let’s point out the
most interesting things.

它更像是一个参考图，但让我们指出最有趣的事情。

At the PDCP level, we see
the header compression that applies to the IP
messages and not to R. R. C.
在PDCP级别，我们看到适用于IP消息的头压缩，而不是R. R. C.

At the R. L. C level, the two pink
messages belong to the same R. L. C instance;
they have been concatenated into the same R. L. C-PDU.
在R.L.C级别，两个粉红色消息属于相同的R.L.C实例; 它们被连接成相同的R. L. C-PDU。

This is not the case for the control message.
控制消息不是这种情况。

At the MAC level, we merge the MAC-SDU from the two R. L. C instances.
在MAC级别，我们合并来自两个R.L.C实例的MAC-SDU。

We add headers to create a
transport block that will be delivered to the physical layer.

我们添加标头以创建将传递到物理层的传输块。

On the physical layer, the RNTI appears in a dotted box.
在物理层上，RNTI显示在虚线框中。

It’s because it is not transmitted with the data,
but supplied implicitly through the allocation table.
这是因为它不与数据一起传输，而是通过分配表隐式提供。

Finally, this slide summaries the acronyms that have been used this week.
最后，本幻灯片总结了本周使用的首字母缩略词。

This is the end of this chapter about the radio interface.
这是本章关于无线电接口的结尾。

Thank you for watching.
谢谢你的收看。

We’ll be in touch on the forum!
Bye!
我们将在论坛上保持联系！
再见！

转载于:https://www.cnblogs.com/sec875/articles/9970270.html