热门标签 | HotTags
当前位置:  开发笔记 > 编程语言 > 正文

TheEvolvedPacketCore

ThisarticlelooksattheEvolvedPacketCore(EPC),thecorenetworkoftheLTEsystem,givinganovervie

This article looks at the Evolved Packet Core (EPC), the core network of the
LTE system, giving an overview of the architecture of the core network,
describing some of its key elements.

The EPC is the latest evolution of the 3GPP core network architecture.

In GSM, the architecture relies on circuit-switching (CS). This means that
circuits are established between the calling and called parties throughout the
telecommunication network (radio, core network of the mobile operator, fixed
network). This circuit-switching mode can be seen as an evolution of the "two
cans and a string". In GSM, all services are transported over circuit-switches
telephony principally, but short messages (SMS) and some data is also seen.

In GPRS, packet-switching (PS) is added to the circuit-switching. With this
technology, data is transported in packets without the establishment of
dedicated circuits. This offers more flexibility and efficiency. In GPRS, the
circuits still transport voice and SMS (in most cases). Therefore, the core
network is composed of two domains: circuit and packet.
In
UMTS (3G), this dual-domain concept is kept on the core network side. Some
network elements have evolved but the concept remains very similar.

When designing the evolution of the 3G system, the 3GPP community decided to
use IP (Internet Protocol) as the key protocol to transport all services. It was
therefore agreed that the EPC would not have a circuit-switched domain anymore
and that the EPC should be an evolution of the packet-switched architecture used
in GPRS/UMTS. 
This decision had consequences on the
architecture itself but also on the way that the services were provided.
Traditional use of circuits to carry voice and short messages needed to be
replaced by IP-based solutions in the long term.

bubuko.com,布布扣 src="https://img8.php1.cn/3cdc5/18867/978/881fbb929cc58334.jpeg">


Architecture of the EPC

EPC was first introduced by 3GPP in Release 8 of the standard.

It was decided to have a "flat architecture". The idea is to handle the
payload (the data traffic) efficiently from performance and costs perspective.
Few network nodes are involved in the handling of the traffic and protocol
conversion is avoided.

It was also decided to separate the user data (also known as the user plane)
and the signalling (also know as the control plane) to make the scaling
independent. Thanks to this functional split, the operators can dimension and
adapt their network easily.

Figure 2 shows a very basic architecture of the EPS when the User Equipment
(UE) is connected to the EPC over E-UTRAN (LTE access network). The Evolved
NodeB (eNodeB) is the base station for LTE radio. In this figure, the EPC is
composed of four network elements: the Serving Gateway (Serving GW), the PDN
Gateway (PDN GW), the MME and the HSS. The EPC is connected to the external
networks, which can include the IP Multimedia Core Network Subsystem (IMS).

bubuko.com,布布扣 src="https://img8.php1.cn/3cdc5/18867/978/91364317852dec76.jpeg">

HSS

Basically, the HSS (for Home Subscriber Server) is a database that contains
user-related and subscriber-related information. It also provides support
functions in mobility management, call and session setup, user authentication
and access authorization.
It is based on the pre-3GPP Release
4 - Home Location Register (HLR) and Authentication Centre (AuC).

Serving GW

The gateways (Serving GW and PDN GW) deal with the user plane. They transport
the IP data traffic between the User Equipment (UE) and the external
networks.
The Serving GW is the point of interconnect between
the radio-side and the EPC. As its name indicates, this gateway serves the UE by
routing the incoming and outgoing IP packets.

It is the anchor point for the intra-LTE mobility (i.e. in case of handover
between eNodeBs) and between LTE and other 3GPP accesses.
It
is logically connected to the other gateway, the PDN GW.

PDN GW

The PDN GW is the point of interconnect between the EPC and the external IP
networks. These networks are called PDN (Packet Data Network), hence the name.
The PDN GW routes packets to and from the PDNs.

The PDN GW also performs various functions such as IP address / IP prefix
allocation or policy control and charging.

3GPP specifies these gateways independently but in practice they may be
combined in a single "box" by network vendors.

MME
The MME (for Mobility Management
Entity) deals with the control plane. It handles the signalling related to
mobility and security for E-UTRAN access.

The MME is responsible for the tracking and the paging of UE in idle-mode. It
is the termination point of the Non-Access Stratum (NAS).


Support of multiple access technologies

As seen in figure 2, the UE can reach the EPC using E-UTRAN however this is
not the only access technology supported.

3GPP specified support of multiple access technologies and also the handover
between these accesses. The idea was to bring convergence using a unique core
network providing various IP-based services over multiple access
technologies.

Existing 3GPP radio access networks are supported. 3GPP specifications define
how the interworking is achieved between an E-UTRAN (LTE and LTE-Advanced),
GERAN (radio access network of GSM/GPRS) and UTRAN (radio access network of
UMTS-based technologies WCDMA and HSPA).

The EPS also allows non-3GPP technologies to interconnect the UE and the EPC.
Non-3GPP means that these accesses were not specified in the 3GPP. These
technologies includes e.g. WiMAX, cdma2000?, WLAN or fixed networks.

Non-3GPP accesses can be split into two categories: the "trusted" ones and
the "untrusted":



  • Trusted non-3GPP accesses can interact directly with the EPC.

  • Untrusted non-3GPP accesses interwork with the EPC via a network entity
    called the ePDG (for Evolved Packet Data Gateway). The main role of the ePDG
    is to provide security mechanisms such as IPsec tunnelling of connections with
    the UE over an untrusted non-3GPP access.

3GPP does not specify which non-3GPP technologies should be considered
trusted or untrusted. This decision is made by the operator.

bubuko.com,布布扣 src="https://img8.php1.cn/3cdc5/18867/978/dff153d1ae72a0f4.jpeg">

 

 

原文:http://www.3gpp.org/technologies/keywords-acronyms/100-the-evolved-packet-core


推荐阅读
  • 本文介绍了OC学习笔记中的@property和@synthesize,包括属性的定义和合成的使用方法。通过示例代码详细讲解了@property和@synthesize的作用和用法。 ... [详细]
  • HDU 2372 El Dorado(DP)的最长上升子序列长度求解方法
    本文介绍了解决HDU 2372 El Dorado问题的一种动态规划方法,通过循环k的方式求解最长上升子序列的长度。具体实现过程包括初始化dp数组、读取数列、计算最长上升子序列长度等步骤。 ... [详细]
  • 高质量SQL书写的30条建议
    本文提供了30条关于优化SQL的建议,包括避免使用select *,使用具体字段,以及使用limit 1等。这些建议是基于实际开发经验总结出来的,旨在帮助读者优化SQL查询。 ... [详细]
  • 本文介绍了一种解析GRE报文长度的方法,通过分析GRE报文头中的标志位来计算报文长度。具体实现步骤包括获取GRE报文头指针、提取标志位、计算报文长度等。该方法可以帮助用户准确地获取GRE报文的长度信息。 ... [详细]
  • vue使用
    关键词: ... [详细]
  • Monkey《大话移动——Android与iOS应用测试指南》的预购信息发布啦!
    Monkey《大话移动——Android与iOS应用测试指南》的预购信息已经发布,可以在京东和当当网进行预购。感谢几位大牛给出的书评,并呼吁大家的支持。明天京东的链接也将发布。 ... [详细]
  • 在Android开发中,使用Picasso库可以实现对网络图片的等比例缩放。本文介绍了使用Picasso库进行图片缩放的方法,并提供了具体的代码实现。通过获取图片的宽高,计算目标宽度和高度,并创建新图实现等比例缩放。 ... [详细]
  • 基于layUI的图片上传前预览功能的2种实现方式
    本文介绍了基于layUI的图片上传前预览功能的两种实现方式:一种是使用blob+FileReader,另一种是使用layUI自带的参数。通过选择文件后点击文件名,在页面中间弹窗内预览图片。其中,layUI自带的参数实现了图片预览功能。该功能依赖于layUI的上传模块,并使用了blob和FileReader来读取本地文件并获取图像的base64编码。点击文件名时会执行See()函数。摘要长度为169字。 ... [详细]
  • IhaveconfiguredanactionforaremotenotificationwhenitarrivestomyiOsapp.Iwanttwodiff ... [详细]
  • 本文讨论了如何优化解决hdu 1003 java题目的动态规划方法,通过分析加法规则和最大和的性质,提出了一种优化的思路。具体方法是,当从1加到n为负时,即sum(1,n)sum(n,s),可以继续加法计算。同时,还考虑了两种特殊情况:都是负数的情况和有0的情况。最后,通过使用Scanner类来获取输入数据。 ... [详细]
  • Mac OS 升级到11.2.2 Eclipse打不开了,报错Failed to create the Java Virtual Machine
    本文介绍了在Mac OS升级到11.2.2版本后,使用Eclipse打开时出现报错Failed to create the Java Virtual Machine的问题,并提供了解决方法。 ... [详细]
  • 1,关于死锁的理解死锁,我们可以简单的理解为是两个线程同时使用同一资源,两个线程又得不到相应的资源而造成永无相互等待的情况。 2,模拟死锁背景介绍:我们创建一个朋友 ... [详细]
  • 后台获取视图对应的字符串
    1.帮助类后台获取视图对应的字符串publicclassViewHelper{将View输出为字符串(注:不会执行对应的ac ... [详细]
  • 《数据结构》学习笔记3——串匹配算法性能评估
    本文主要讨论串匹配算法的性能评估,包括模式匹配、字符种类数量、算法复杂度等内容。通过借助C++中的头文件和库,可以实现对串的匹配操作。其中蛮力算法的复杂度为O(m*n),通过随机取出长度为m的子串作为模式P,在文本T中进行匹配,统计平均复杂度。对于成功和失败的匹配分别进行测试,分析其平均复杂度。详情请参考相关学习资源。 ... [详细]
  • 本文介绍了C#中数据集DataSet对象的使用及相关方法详解,包括DataSet对象的概述、与数据关系对象的互联、Rows集合和Columns集合的组成,以及DataSet对象常用的方法之一——Merge方法的使用。通过本文的阅读,读者可以了解到DataSet对象在C#中的重要性和使用方法。 ... [详细]
author-avatar
weibophp
这个家伙很懒,什么也没留下!
PHP1.CN | 中国最专业的PHP中文社区 | DevBox开发工具箱 | json解析格式化 |PHP资讯 | PHP教程 | 数据库技术 | 服务器技术 | 前端开发技术 | PHP框架 | 开发工具 | 在线工具
Copyright © 1998 - 2020 PHP1.CN. All Rights Reserved | 京公网安备 11010802041100号 | 京ICP备19059560号-4 | PHP1.CN 第一PHP社区 版权所有