Week 5: Management of the Sporadic Nature of Data Flows 4 - UE-Triggered Service Request

We saw, in the previous video, that, after a certain
period of inactivity the radio connections and a few
tunnels or connections are released.
在之前的视频中，我们看到，在一段时间不活动之后，无线电连接和一些隧道或连接被释放。

The question we must ask now is: can I
use my terminal once the radio connection has been released?
我们现在必须要问的问题是：一旦无线电连接被释放，我可以使用我的终端吗？

Or, if I have an application running,
can my terminal transmit data rapidly after a long
period of inactivity?
或者，如果我的应用程序正在运行，我的终端可以在长时间不活动后快速传输数据吗？

We’re going to consider the following scenario.
我们将考虑以下场景。

A terminal has, for example, been turned on.
例如，终端已经打开。

All the tunnels were established, which means that, at
the end of the attach procedure, the terminal is
in EMM-Registered ECM-Connected state.
所有隧道都已建立，这意味着，在附着过程结束时，终端处于EMM注册ECM连接状态。

The TEIDs used for the data bearers are
101 on the eNodeB side,
102 on the Serving Gateway side,
again 101 for the tunnel between the Serving
Gateway and the P-Gateway and 32,000
on the P-Gateway side.
用于数据承载的TEID在eNodeB侧是101，在服务网关侧是102，在服务网关和P网关之间的隧道再次是101，在P-网关侧是32,000。

We assume that the user has not done anything
with his terminal.
我们假设用户没有对他的终端做任何事情。

After a moment, it will return to standby mode and
the tunnels will be released, especially the S1 tunnel.
片刻之后，它将返回待机模式，隧道将被释放，尤其是S1隧道。

If the user then moves
and goes into the cell represented here with a
green eNodeB, what happens when the user
wants to, for example, load a Web page?
如果用户然后使用绿色eNodeB移动并进入此处表示的单元格，那么当用户想要加载网页时会发生什么？

We’re going to need
a procedure to re-establish connections and tunnels that
is as fast as possible.
我们需要一个程序来尽快重建连接和隧道。

The first thing that comes to mind is:
let’s re-establish the tunnels after everything has been released.
首先想到的是：让我们在一切都被释放后重新建立隧道。

So, there are data to transmit.
所以，有数据要传输。

For example, the application sends a
request to a Web server, it will make a random
access procedure on the radio interface, an
RNTI is allocated, and after a handshake, the RNTI is confirmed.
例如，应用程序向Web服务器发送请求，它将在无线接口上进行随机接入过程，分配RNTI，并在握手后确认RNTI。

The terminal then sends
a message called EMM Service Request to say, “I want
connectivity again to transmit data.”
终端然后发送称为EMM服务请求的消息，说“我想再次连接以传输数据”。

This message is transmitted in an RRC
message, connection set up complete.
该消息在RRC消息中发送，连接建立完成。

It is received by the eNodeB.
它由eNodeB接收。

The eNodeB will re-establish the S1-AP connection.
eNodeB将重新建立S1-AP连接。

At the same time it sends an EMM Service
Request message, with KSI (data related to security keys).
同时，它使用KSI（与安全密钥相关的数据）发送EMM服务请求消息。

The MME checks to see if
the subscriber is authorized and requests the
re-establishment of various radio bearers, various radio
connections with the management of quality of service
(if there is quality of service).
MME检查用户是否被授权并请求重新建立各种无线承载，各种无线连接与服务质量管理（如果有服务质量）。

eNodeB2 selects a value for TEID, for example 16,538.
eNodeB2选择TEID的值，例如16,538。

eNodeB1 had chosen 101, but this eNodeB2
is unaware of that, so the value is completely different.
eNodeB1选择了101，但是这个eNodeB2没有意识到这一点，所以价值完全不同。

Before it was 101, now it is is 16,538.
在101之前，现在是16,538。

This value (16,538) is sent in the S1-AP
Initial Context Set up complete message
and the MME sends back a GTP-C
Modify Bearer Request message with the TEID,
to request the establishment of the tunnel between the
eNodeB and the Serving Gateway.
该值（16,538）在S1-AP初始上下文建立完成消息中发送，并且MME发回带有TEID的GTP-C修改承载请求消息，以请求在eNodeB和服务网关之间建立隧道。

The Serving Gateway chooses a TEID.
服务网关选择REID。

This TEID should be sent back to the eNodeB.
该TEID应该发送回eNodeB。

So there must be a message from the Serving Gateway
to the MME, from the MME to the eNodeB.
因此，必须存在从服务网关到MME的消息，从MME到eNodeB。

These messages make the procedure longer.
这些消息使程序更长。

Even if the additional time is small (several dozens ms),
the effect isn’t negligible.
即使额外的时间很短（几十毫秒），效果也不容忽视。

So, we’ll try to be
a bit more subtle when re-establishing the various bearers.
因此，在重建各种承载者时，我们会尝试更加微妙。

When we look at the scenario,
given that all the messages for the establishment of the
initial tunnel go through the MME,
the MME can memorize the TEID
used by the Serving Gateway
for the S1 tunnel.
当我们查看场景时，假设建立初始隧道的所有消息都通过MME，则MME可以记住服务网关用于S1隧道的TEID。

So, this value is memorized and when we release the
connection because of “radio inactivity,” we do not
completely release the S1 tunnel.
因此，这个值被记忆，当我们因“无线电不活动”而释放连接时，我们不会完全释放S1隧道。

We’ll retain the TEID value of 102.
我们将保留TEID值102。

This means that, when the cell phone
reappears in another cell, this TEID
is reused for the new tunnel.
这意味着，当手机重新出现在另一个小区中时，该TEID将重新用于新隧道。

So, when the tunnel is re-established, we will
avoid message exchanges between the MME
and the Serving Gateway.
因此，当重新建立隧道时，我们将避免MME和服务网关之间的消息交换。

Let’s see how that works.
让我们看看它是如何工作的。

The beginning of the procedure is the same.
程序的开头是一样的。

In this slide, to underscore that the MME
retains in memory some things, we show that the TEID value
is stored by the MME, and this
value is considered as still allocated
by the Serving Gateway.
在这张幻灯片中，为了强调MME在内存中保留了一些东西，我们显示TEID值由MME存储，并且该值被认为仍由服务网关分配。

The cell phone has data to transmit: we have random
access, the allocation of an RNTI
like earlier, the establishment of a radio connection,
confirmation of the RNTI like earlier,
sending a Service Request with security
data, and like earlier, the establishment of the
S1-AP connection:
a new connection, between the eNodeB where the terminal is located and the MME.
手机有数据传输：我们有随机接入，像之前一样分配RNTI，建立无线连接，像之前一样确认RNTI，发送带有安全数据的服务请求，和之前一样，建立 S1-AP连接：终端所在的eNodeB与MME之间的新连接。

The MME verifies that the
subscriber is authorized and he can
respond directly by sending the TEID
102 to the eNodeB.
MME验证订户是否被授权并且他可以通过将TEID 102发送到eNodeB来直接响应。

This way, the eNodeB has a
tunnel which has been re-established, on the uplink,
because it knows the TEID used by the Serving Gateway;
it can then easily send data
using the TEID of the recipient
(here the TEID allocated by the Serving Gateway).
这样，eNodeB在上行链路上具有已经重建的隧道，因为它知道服务网关使用的TEID; 然后，它可以使用接收方的TEID（这里是服务网关分配的TEID）轻松发送数据。

The radio connection is re-established,
the eNodeB chooses its TEID (in accordance with its own
system of reference), then sends an
S1-AP Set up Complete message, with the value of
the TEID, and this value will be stored
by the Serving Gateway.
重新建立无线电连接，eNodeB选择其TEID（根据其自己的参考系统），然后发送带有TEID值的S1-AP设置完成消息，该值将由 服务网关。

At the end of this exchange, the S1 tunnel and the S1
Bearer are completely re-established.
在此交换结束时，S1隧道和S1承载完全重建。

But we can see that, very rapidly, from
this phase on , data to transmit
could be sent on the radio connection and on
the S1 tunnel.
但是我们可以非常迅速地看到，从这个阶段开始，可以在无线连接和S1隧道上发送要传输的数据。

So, we have a procedure that
enables us to rapidly re-establish the connection.
因此，我们有一个程序，使我们能够快速重新建立连接。

This procedure will still take a few tens of
milliseconds, up to one hundred milliseconds, typically.
通常，此过程仍需要几十毫秒，最多一百毫秒。

To summarize, after radio inactivity, the S1 bearer
is only PARTIALLY released.
总而言之，在无线电不活动之后，S1承载仅被部分释放。

The TEID values are stored by the MME.
TEID值由MME存储。

A procedure called UE Triggered
service request is defined to re-establish
as quickly as possible the bearers
and the connections.
称为UE触发服务请求的过程被定义为尽可能快地重建承载和连接。

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