Sie sind auf Seite 1von 6

UE eNB

CCCH:UL-SCH :RRC :connection_requst--->


<---CCCH:DL-SCH :RRC :connection_setup
DCCH:UL-SCH :RRC :connection_steup_comlete--->
DCCH:UL-SCH :RRC :UL_nas transfer--->

S1AP: INITIAL UE MESSAGE (NAS,eNB_UE_S1AP_ID


,TAI,EUTRAN_CGI_ID ,RRC_Establishment_Cause
,GUMMEI_ID )---->

<---S1AP:DOWNLINK NAS TRANSPORT (MME_UE_S1AP_ID


,eNB_UE_S1AP_ID ,NAS_PDU )
<---DCCH:DL-SCH :RRC :DL Information Transfer
(NAS EMM PDU)

DCCH:UL-SCH :RRC UL Information Transfer (NAS PDU - EMM


Authentication Response {SRES}--->
S1AP:S1AP - UL NAS Transport
(NAS EMM PDU)---->

<---S1AP:security_mode_command
<---DCCH:DL-SCH :RRC :DL Information Transfer
(NAS EMM PDU)

DCCH:UL-SCH :RRC security_mode_complete--->


S1AP:S1AP - security_mode_complete---->
<---S1AP - Initial Context Setup
(UE S1AP ID, Aggregate Maximum Bit Rate, default/dedicated
bearer {E-RAB IDs, QoS, SGW GTP TEID, NAS PDU, EPC
Transport address}, UE Security Capabilities, Security key
KeNB)

<---DCCH:DL-SCH :RRC AS Security Mode Command


(Ciphering algorithm, Integrity algorithm

<---DCCH:DL-SCH RRC Connection_Reconfiguraion


[EPS bearer ID, DRB ID, Radio configs - RLC/PDCP/MAC/PHY,
NAS pdu]

RRC Security Mode Complete


.1RRC/L2/PHY would be configured for SRB2 and DRB. RRC
would acknowledge this is to eNB and pass on NAS PDU to
EMM.--->

RRC Connection Reconfiguration Complete


S1AP - Initial Conext Setup Response
(UE S1AP IDs, E-RABs setup {E-RAB ID, eNB GTP-U TEID, eNB
Transport address})--->

<<<<<<<< GTP Tun


MME HSS S-gw

NB_UE_S1AP_ID
shment_Cause

S6a/Dia: Auc_info_request (IMSI)--->


<---S6a/Dia: Auc_info_response(xres,rand,algo)
(MME_UE_S1AP_ID
PDU )

sport
>

ommand

omplete---->

S6a/Dia: - Update Location Request(IMSI, Visited


PLMN ID, RAT type)--->

<---Diameter - Upda_Loca_Answer
(Subscription data,AMBR,QCI,ARP,profile related
information ,Charging-Characteristics)

GTPC:CREATE_SESSION_REQUEST (IMSI, APN, PGW S5/S8 address/F-TEID, PDN type, EPS


Bearer ID(5), Default EPS QoS, AMBR, PDN address,user location info)--->

GTPC:CREATE_SESSION_REQUEST (IMSI,
gtpuTEID, PDN type, EPS Bearer ID-5, De
QoS, AMBR, PDN address (fixed), PC
<---GTP-C - Create Session Respon
(PDN address, AMBR, PCO, Default/De
bearer contexts {EPS bearer ID, PGW Us
TEID, QoS} piggybacking possibl

User DL data (if any)on GTP tunn


<<<< S5/S8 Data Tunnel >>>>>
<---GTP-C - Create Session Response
(PDN address, AMBR, PCO, Default/Dedicated bearer contexts{SGW User plane TEID ,ip
address of sgw }
Setup
te, default/dedicated
ID, NAS PDU, EPC
ilities, Security key

Response
NB GTP-U TEID, eNB
->
GTP-C - Modify Bearer Request
(EPS bearer IDs, eNB F-TEID)---->

<----GTP-C - Modify Bearer Response

<<<<<<<< GTP Tunnel for Data >>>>>>>.

S6a/Dia : Notify-Request ---->


P-gw PCRF

EATE_SESSION_REQUEST (IMSI, APN, SGW


D, PDN type, EPS Bearer ID-5, Default EPS
, AMBR, PDN address (fixed), PCO)--->

Gx/Dia:Request for PCC rules(QoS


policy ,charging rules)--->
Gx/Dia:Provisioning of PCC rules(QoS
policy ,charging rules)--->
---GTP-C - Create Session Response
address, AMBR, PCO, Default/Dedicated
contexts {EPS bearer ID, PGW User plane
TEID, QoS} piggybacking possible

User DL data (if any)on GTP tunnel


<<<< S5/S8 Data Tunnel >>>>>

Das könnte Ihnen auch gefallen