Epc Design Hld and Dld

EPC introduction HLD/DLD and MOP

Best Practice by: Silverio Beltran

Customer: Globe

CD CSI Philippines

Ericsson Internal | Page 2

background

› Basic EPC was offered to Globe which includes test bed & Live setup.

› This is the very first implementation of EPC for Ericsson on Philippines

› The experience & MOPs on this document will be helpful for other Solution Architect who will be dping the same EPC introduction

Ericsson Internal | Page 3

background

› Basic EPC was offered to Globe which includes test bed & Live setup.

› This is the very first implementation of EPC for Ericsson on Philippines

› The experience & MOPs on this document will be helpful for other Solution Architect who will be dping the same EPC introduction

Ericsson Internal | Page 4

Description

› The Evolved Packet System (EPS) is a new system for packet data transmission over broadband radio access. The Evolved Packet Core involves all the core technology that provides broadband services to the subscriber.

› The Ericsson EPS solution complies with the 3GPP Release 8 specification, and it is seen as the evolution from 3GPP 2G and 3G.

Ericsson Internal | Page 5

EPC Architecture

Ericsson Internal | Page 6

Globe EPC Physical network topology for Testbed

Ericsson Internal | Page 7

Globe EPC Physical network topology for LIVE implementation

Ericsson Internal | Page 8

Interfaces involve

› S6a– The interface S6a is defined between the HSS and the MME

Ericsson Internal | Page 9

Interfaces involve

› S1-MME– This is the interface between eNodeBs and MME. As a control

plane interface it is similar to Radio Access Network Application Part (RANAP) protocol, with some simplifications and changes due to the different functional split and mobility within EPS.

Ericsson Internal | Page 10

Interfaces involve

› S1-U– This is the interface between eNodeBs and S-GW

Ericsson Internal | Page 11

Interfaces involve

› SGi– The SGi interface is defined between the PDN GW and external IP

networks (also called ‘PDNs’). The external networks may be Internet and/or Intranets and IPv4 may be used.

Ericsson Internal | Page 12

involve

› S11– The S11 interface is defined between MME and the Serving GW,

this interface exclusively uses GTPv2-C and for LTE access only.

Ericsson Internal | Page 13

Design Documents

› Solution Description

https://ericoll.internal.ericsson.com/sites/GKO//Lists/GKO/DispForm.aspx?ID=155675&Source=http://ericoll.internal.ericsson.com/sites/GSN_SW_Deployment_and_Support/SAE/default.aspx

› High Level & low Level Design

https://ericoll.internal.ericsson.com/sites/GKO//Lists/GKO/DispForm.aspx?ID=159748&Source=http://ericoll.internal.ericsson.com/sites/GSN_SW_Deployment_and_Support/SAE/default.aspx

Ericsson Internal | Page 14

IMPLEMENTATION DOCUMENT

› MOP

https://ericoll.internal.ericsson.com/sites/GKO//Lists/GKO/DispForm.aspx?ID=159494&Source=http://ericoll.internal.ericsson.com/sites/GSN_SW_Deployment_and_Support/SAE/default.aspx

Ericsson Internal | Page 15

Acceptance approach

› System Acceptance Document

https://ericoll.internal.ericsson.com/sites/GKO//Lists/GKO/DispForm.aspx?ID=155589&Source=http://ericoll.internal.ericsson.com/sites/GSN_SW_Deployment_and_Support/SAE/default.aspx

Ericsson Internal | Page 16

Man-hours spent

› Solution Description– 1 CU Solution Architect– 32 man-hours

› Potential saving ~16 man-hours

› High Level & Low Level Design– 1 GSC Design Engineer

› 304 man-hours› Potential savings ~ 150 man-hours

– 1 CU Solution Architect› 120 man-hours› Potential savings ~ 60 man-hours

Ericsson Internal | Page 17

Man-hours spent

› Method of Procedure– 1 CU services engineer

› 16 man-hours› Potential savings ~ 8 man-hours

– 1 GSC services engineer› 16 man-hours› Potential savings ~ 6 man-hours

› Acceptance Document– 1 CU Solution Architect

› 24 man-hours› Potential savings ~ 12 man-hours