0% found this document useful (0 votes)
705 views9 pages

LTE Trial: - EPC Testing Notes

The document discusses an LTE trial and provides details about: 1) The S1 interface control plane uses S1AP and SCTP. 2) The X1 user plane uses IPv4 or IPv6, UDP, and GTP-U to transfer user data. 3) S1AP consists of elementary procedures like handover preparation and resource allocation that make up complete interaction sequences.
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
705 views9 pages

LTE Trial: - EPC Testing Notes

The document discusses an LTE trial and provides details about: 1) The S1 interface control plane uses S1AP and SCTP. 2) The X1 user plane uses IPv4 or IPv6, UDP, and GTP-U to transfer user data. 3) S1AP consists of elementary procedures like handover preparation and resource allocation that make up complete interaction sequences.
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 9

LTE Trial

-EPC testing notes


eNB-MME

• S1 -Control plane:
S1-AP (3GPP TS 36.413 V8.7.0 (2009-09))
SCTP (RFC4960)

• X1-User plane:
IPv4 (RFC 791) or Ipv6 (RFC 2460)
UDP (RFC 768)
GTP-U (3GPP TS 29.060)
User data (UDP/IPv4/iPv6) (RFC 768, RFC 791, RFC 2460)
S1AP
• Elementary Procedure: S1AP consists of Elementary Procedures (EPs). An
Elementary Procedure is a unit of interaction between eNBs and the EPC.
These Elementary Procedures are defined separately and are intended to
be used to build up complete sequences in a flexible manner. If the
independence between some EPs is restricted, it is described under the
relevant EP description. Unless otherwise stated by the restrictions, the EPs
may be invoked independently of each other as stand alone procedures,
which can be active in parallel. The usage of several S1AP EPs together or
together with EPs from other interfaces is specified in stage 2 specifications
(e.g. [11] and [14]).
• An EP consists of an initiating message and possibly a response message.
Two kinds of EPs are used:
- Class 1: Elementary Procedures with response (success and/or failure).
- Class 2: Elementary Procedures without response.
Elementary Procedure
S1AP Procedures
Initiating Message Successful Outcome Unsuccessful Outcome
Response message Response message
Handover Preparation HANDOVER REQUIRED HANDOVER COMMAND HANDOVER PREPARATION
FAILURE
Handover Resource Allocation HANDOVER REQUEST HANDOVER REQUEST HANDOVER FAILURE
ACKNOWLEDGE
Path Switch Request PATH SWITCH REQUEST PATH SWITCH REQUEST PATH SWITCH REQUEST FAILURE
ACKNOWLEDGE
Handover Cancellation HANDOVER CANCEL HANDOVER CANCEL
ACKNOWLEDGE
E-RAB Setup E-RAB SETUP REQUEST E-RAB SETUP RESPONSE

E-RAB Modify E-RAB MODIFY REQUEST E-RAB MODIFY RESPONSE

E-RAB Release E-RAB RELEASE COMMAND E-RAB RELEASE RESPONSE

Initial Context Setup INITIAL CONTEXT SETUP INITIAL CONTEXT SETUP INITIAL CONTEXT SETUP FAILURE
REQUEST RESPONSE
Reset RESET RESET ACKNOWLEDGE
S1 Setup S1 SETUP REQUEST S1 SETUP RESPONSE S1 SETUP FAILURE
UE Context Release UE CONTEXT RELEASE UE CONTEXT RELEASE
COMMAND COMPLETE
UE Context Modification UE CONTEXT UE CONTEXT MODIFICATION UE CONTEXT MODIFICATION
MODIFICATION REQUEST RESPONSE FAILURE

eNB Configuration Update ENB CONFIGURATION ENB CONFIGURATION UPDATE ENB CONFIGURATION UPDATE
UPDATE ACKNOWLEDGE FAILURE

MME Configuration Update MME CONFIGURATION MME CONFIGURAION UPDATE MME CONFIGURATION UPDATE
UPDATE ACKNOWLEDGE FAILURE

Write-Replace Warning WRITE-REPLACE WARNING WRITE-REPLACE WARNING


REQUEST RESPONSE

Class 1 Procedures
S1AP Procedures (cont.)
Elementary Procedure Message
Handover Notification HANDOVER NOTIFY
E-RAB Release Indication E-RAB RELEASE INDICATION
Paging PAGING
Initial UE Message INITIAL UE MESSAGE
Downlink NAS Transport DOWNLINK NAS TRANSPORT
Uplink NAS Transport UPLINK NAS TRANSPORT
NAS non delivery indication NAS NON DELIVERY INDICATION
Error Indication ERROR INDICATION
UE Context Release Request UE CONTEXT RELEASE REQUEST
DownlinkS1 CDMA2000 Tunneling DOWNLINK S1 CDMA2000 TUNNELING

Uplink S1 CDMA2000 Tunneling UPLINK S1 CDMA2000 TUNNELING


UE Capability Info Indication UE CAPABILITY INFO INDICATION
eNB Status Transfer eNB STATUS TRANSFER
MME Status Transfer MME STATUS TRANSFER
Deactivate Trace DEACTIVATE TRACE
Trace Start TRACE START
Trace Failure Indication TRACE FAILURE INDICATION
Location Reporting Control LOCATION REPORTING CONTROL
Location Reporting Failure Indication LOCATION REPORTING FAILURE INDICATION

Location Report LOCATION REPORT


Overload Start OVERLOAD START
Overload Stop OVERLOAD STOP
eNB Direct Information Transfer eNB DIRECT INFORMATION TRANSFER

MME Direct Information Transfer MME DIRECT INFORMATION TRANSFER

eNB Configuration Transfer eNB CONFIGURATION TRANSFER


MME Configuration Transfer MME CONFIGURATION TRANSFER
Cell Traffic Trace CELL TRAFFIC TRACE

Class 2 Procedures
NAS
• The purpose of the NAS Transport procedure is to carry UE
– MME signalling over the S1 Interface.
• The NAS messages are not interpreted by the eNB
• The procedure may use an existing UE-associated logical
S1-connection. If no UE-associated logical S1-connection
exists, the establishment of the UE-associated logical S1-
connection is initiated (and may be established) as part of
the procedure.
• The NAS messages are transported in an IE of the INITIAL
UE MESSAGE, DOWNLINK NAS TRANSPORT or UPLINK
NAS TRANSPORT messages.
NAS- Initial UE Message

UE eNB MME
(Attach)
RRC (Attach Request)
INITIAL UE MESSAGE

• When the eNB has received from the radio interface the
first UL NAS message transmitted on an RRC connection to
be forwarded to an MME, the eNB shall invoke the NAS
Transport procedure and send the INITIAL UE MESSAGE to
the MME including the NAS message as a NAS-PDU IE.
MME-HSS
• S6a TS 29.272 V8.4.0 (2009-09)
– Diameter based
• SCTP/TCP
MME-SGW

You might also like