Lte epc trial experience

LTE-EPC LTE-EPC TRIAL EXPERIENCE

Hussien Mahmoud- PS Core/EPC Consultant

LTE-EPC Trial Experience

IntroductionThis presentation is done to list the configuration parts for a simple LTE-EPC script done

with Cisco, the presentation assumes that u have a good LTE as well as Cisco Experience

Packet Core experience. For more information, Cisco Documentations are included in the

references part.

Author InformationHussien Mahmoud

PS Core/ EPC Consultant

Packet Core Networks

Linkedin: https://eg.linkedin.com/in/hussienmahmoud

LTE Workshop


https://eg.linkedin.com/in/hussienmahmoud

LTE Workshop


Introduction

IP Plan And Context Creation

MME Creation and related HSS, DNS configuration

Operator Policy and Topology Plan

SGW and PGW Creation

APN and CDR Configuration


LTE-EPC Trial

Experience



We are using a simple design to include all Core

Nodes MME,SGW and PGW in one Node. All

types of traffic are included in only one interface

carrying S1-AP, S1-U ,S6a ,S5/S8 and SGi

interface.

LTE-EPC Trial ExperienceIntroduction





LTE-EPC Trial ExperienceIP Plan And Context Creation

Make ur IP plan and define Two types of LTE interfaces; Internal

interfaces which u r using in the network and external interfaces

which u will communicate with.

Define each interface and loop-back for each Node, In this

example I am using only one physical interface (EPC_Interface) that

carries all types of traffic, and then I am defining a loop-back for

each service. for example; MME DNS interface, u have to define

the source and Destination IPs MME "mme_dns" as a source and

DNS "idns_lo" as a destination. later in this post I will show at

which part u will configure this IP's.



##EPC-Script####################################

#Internal IP's #################################

# Physical EPC_Interface (MME,SGW,PGW) = X.X.X.X/24

# MME Loopback mme_dns = M.M.M.M

# MME Loopback mme_s1ap = Z.Z.Z.Z

# MME Loopback mme_s11 = K.K.K.K

# MME Loopback mme_s6a = L.L.L.L

# SGW Loopback sgw_s1U_s11 = N.N.N.N

# SGW Loopback sgw_s5_s8 = P.P.P.P

# PGW Loopback pgw_s5s8 = Q.Q.Q.Q

# External IP's ################################

# HSS Loopback hss_s6a = Y.Y.Y.Y

# DNS Loopback idns_lo = C.C.C.C

# EnodeB Loopback enodb_C = W.W.W.W

# EnodeB Loopback enodb_U = R.R.R.R

#IP Pool Subnet ################################

# IP Pool as a test subnet = V.V.V.V/24LTE-EPC Trial Experience


After u finish ur IP plan, configure a context named EPC and place

all the interfaces under the required context as below, it is

recommended to name each interface with a meaningful acronyms.

I am also adding a simple static route for all the interfaces.


#########Define EPC Context for MME,SGW,PGW

config

context EPC

interface EPC_Interface

ip address X.X.X.X 255.255.255.0

exit

interface hss_s6a loopback

ip address Y.Y.Y.Y 255.255.255.255

exit

interface mme_dns loopback

ip address M.M.M.M 255.255.255.255

exit

interface mme_s1ap loopback

ip address Z.Z.Z.Z 255.255.255.255

exit



interface mme_s11 loopback

ip address K.K.K.K 255.255.255.255

exit

interface mme_s6a loopback

ip address L.L.L.L 255.255.255.255

exit

interface sgw_s1U_s11 loopback

ip address N.N.N.N 255.255.255.255

exit

interface sgw_s5_s8 loopback

ip address P.P.P.P 255.255.255.255

exit

interface pgw_s5s8 loopback

ip address Q.Q.Q.Q 255.255.255.255

exit

end




Create an HSS endpoint and HSS service, u must

have a mandatory information like endpoint host

name, realm and address. for example we are

using realm

"epc.mcc999.mnc99.3gppnetwork.org" as our

realm domain (MCC 999 and MNC 99 is just an

example).

LTE-EPC Trial ExperienceMME Creation and related HSS, DNS configuration


#########HSS Configuration

#Create HSS Service and diameter endpoint

#MCC 999, MNC 99 is for testing

config

context EPC

hss-peer-service hss_service

diameter hss-endpoint MME-S6A

request timeout 1

exit

diameter endpoint MME-S6A

origin realm epc.mcc999.mnc99.3gppnetwork.org

origin host mme-s6a-endpoint.epc.mcc999.mnc99.3gppnetwork.org address L.L.L.L

peer hss-s6a-endpoint.epc.mcc999.mnc99.3gppnetwork.org realm

epc.mcc999.mnc99.3gppnetwork.org address Y.Y.Y.Y

exit

end


################DNS Configuration

config

context EPC

dns-client DNS

bind address M.M.M.M

exit

ip name-servers C.C.C.C

end



Create a simple DNS Service and bind it with

the related interface, in this example I am using

only one DNS server.

#############MME Configuration

config

context EPC

egtp-service mme_egtp

interface-type interface-mme

gtpc bind ipv4-address K.K.K.K

exit

mme-service mme_service

s1-mme sctp port 25

mme-id group-id 40000 mme-code 1

plmn-id mcc 999 mnc 99

associate egtp-service mme_egtp context EPC

associate hss-peer-service hss_service context EPC

associate subscriber-map SM

bind s1-mme ipv4-address Z.Z.Z.Z

exit

exit

end LTE-EPC Trial Experience


MME has two standard interfaces S11 and

S1AP. S11 is used for communication between

MME and SGW (requires GTPv2 Protocol), and

S1AP is the interface used for communication

between MME and EnodeB (S1AP protocol).


In this step , u are creating a default action for ur MME and enodeb information (TAI group), and also behavior regarding the SGW and PGW selection.

APN profile is used for PGW selection and in this case we are giving the DNS quires a higher priority. Call Control Profile configures the Context information for DNS selection in both SGW and PGW, As well as the TAI database. both APN profile and Call control profile are associated with Operator Policy, and the operator policy is then used under the lte policy with TAI identifications.

LTE-EPC Trial ExperienceOperator Policy and Topology Plan

######################## Operator Policy and Topology

config

lte-policy

subscriber-map SM

precedence 1 match-criteria all operator-policy-name OP

exit

tai-mgmt-db tai_mgmt_db

tai-mgmt-obj tai_mgmt_table

zone-code 1234

tai mcc 999 mnc 99 tac 10

sgw-address N.N.N.N s5-s8-protocol gtp weight 1

exit

exit

exit

operator-policy name OP

associate call-control-profile CCP

apn default-apn-profile AP1

exitLTE-EPC Trial Experience


######################## Operator Policy and Topology

call-control-profile CCP

dns-sgw context EPC

dns-pgw context EPC

gw-selection co-location

associate tai-mgmt-db tai_mgmt_db

exit

apn-profile AP1

address-resolution-mode fallback-for-dns

pgw-address Q.Q.Q.Q

accounting mode gtpp

exit

end



LTE-EPC Trial ExperienceSGW and PGW Creation

###########SGW Configuration Part

config

context EPC

gtpu-service sgw_gtpu_ingress

source-port standard

bind ipv4-address N.N.N.N bearer-type all

exit

egtp-service sgw_egtp_ingress

interface-type interface-sgw-ingress

associate gtpu-service sgw_gtpu_ingress

gtpc bind ipv4-address N.N.N.N

exit

gtpu-service sgw_gtpu_egress


bind ipv4-address P.P.P.P bearer-type all

exit


SGW has a standard two interfaces;

Ingress interface (S11, S1U) and Egress

interface (S5/S8). Each of the two

interfaces should include two protocols

GTPv2 as a control plane and GTPUv1

as a user plane.

###########SGW Configuration Part

egtp-service sgw_egtp_egress

interface-type interface-sgw-egress

associate gtpu-service sgw_gtpu_egress

gtpc bind ipv4-address P.P.P.P

exit

sgw-service sgw_service

associate ingress egtp-service sgw_egtp_ingress

associate egress-proto gtp egress-context EPC

plmn id mcc 999 mnc 99 primary

exit

end



######################## PGW Configuration Part

config

context EPC

gtpu-service pgw_gtpu


bind ipv4-address Q.Q.Q.Q bearer-type all

exit

egtp-service pgw_egtp

interface-type interface-pgw-ingress

associate gtpu-service pgw_gtpu

gtpc bind ipv4-address Q.Q.Q.Q

exit



PGW has only one interface as ingress (S5/S8),

this interface should support also GTPv2 as a

control plane and GTPUv1 as a user plane.

pgw-service pgw_service

plmn id mcc 602 mnc 02

associate qci-qos-mapping qci_test

associate egtp-service pgw_egtp

exit

end

# QCI Mapping ################################

Config

qci-qos-mapping qci_test

qci 128 downlink user-datagram dscp-marking 0x01

exit

end



######################## APN Configuration Part

config

context EPC

ip pool ltepool.0 V.V.V.V 255.255.255.0 private 0

apn lte.trial

bearer-control-mode mixed

selection-mode subscribed sent-by-ms

gtpp group pgwnode accounting-context EPC

ip context-name EPC

ip address pool name ltepool.0

exit



In this sample, I am creating a very simple APN

profile with Postpaid category, No Gx or Gy is

required as it is an illustrative.

gtpp group pgwnode

gtpp charging-agent address F.F.F.F

gtpp attribute local-record-sequence-number

gtpp dictionary XXXXXX

gtpp storage-server mode local

gtpp storage-server local file format XXXXXXX

gtpp storage-server local file rotation volume mb 2

gtpp storage-server local file rotation time-interval 300

gtpp storage-server local file name prefix pgwnode01

exit

exit

end

##################################end###############



References


supporting links:

http://www.cisco.com/c/dam/en/us/td/docs/wirel

ess/asr_5000/14_0/OL-27215_MME_Admin.pdf


ess/asr_5000/14_0/OL-27245_SGW_Admin.pdf


ess/asr_5000/14_0/OL-27242_PGW_Admin.pdf

http://www.cisco.com/c/dam/en/us/td/docs/wireless/asr_5000/14_0/OL-27215_MME_Admin.pdf




http://www.cisco.com/c/dam/en/us/td/docs/wireless/asr_5000/14_0/OL-27245_SGW_Admin.pdf




http://www.cisco.com/c/dam/en/us/td/docs/wireless/asr_5000/14_0/OL-27242_PGW_Admin.pdf





Thanks


Technology

Lte epc trial experience