Professional Documents
Culture Documents
LTE Main Signaling Anlaysis
LTE Main Signaling Anlaysis
Release history
Date
Version
Description
Author
2013-11-19
V1.00
Draft
Ahmed Awwad
A. Abstract
In (3GPP) specifications, all standard interfaces for an eNodeB code and decode
messages based on Abstract Syntax Notation (ASN). With ASN, the messages traced
over a standard interface are coded by an eNodeB, an evolved packet core (EPC), or
user equipment (UE). Then, the data link layer (DLL) for a specific interface is used to
decode and resolve the messages. The following describes Abstract Syntax Notation
One (ASN.1).
B. Background
ASN1, also called ASN, is a standard notation that applies to various protocols. As an
advanced language, ASN1 describes different structures and rules for representing,
coding, and decoding data. Before ASN1 is used, the meaning of each bit or byte in a
message must be specified for a message during protocol defining. ASN1 simplifies
protocol defining and ensures the successful communication between data coding
languages or between environment conditions from different equipment
manufacturers.
Compared with ASN1, the S1, X2, and Uu interfaces use different coding modes. As
ground interfaces, the S1and X2 interfaces have sufficient signaling transmission
resources and use aligned coding mode. As an air interface, the Uu interface has few
signaling transmission resources and uses unaligned coding mode.
C. Contenets
ii
eRAN2.2
Signaling Analysis Instances
ASN1
In (3GPP) specifications, all standard interfaces for an eNodeB code and decode messages based
on Abstract Syntax Notation (ASN). With ASN, the messages traced over a standard interface are
coded by an eNodeB, an evolved packet core (EPC), or user equipment (UE). Then, the data link
layer (DLL) for a specific interface is used to decode and resolve the messages. The following
describes Abstract Syntax Notation One (ASN.1).
ASN1, also called ASN, is a standard notation that applies to various protocols. As an advanced
language, ASN1 describes different structures and rules for representing, coding, and decoding
data. Before ASN1 is used, the meaning of each bit or byte in a message must be specified for a
message during protocol defining. ASN1 simplifies protocol defining and ensures the successful
communication between data coding languages or between environment conditions from different
equipment manufacturers.
Compared with ASN1, the S1, X2, and Uu interfaces use different coding modes. As ground
interfaces, the S1and X2 interfaces have sufficient signaling transmission resources and use
aligned coding mode. As an air interface, the Uu interface has few signaling transmission
resources and uses unaligned coding mode.
Most information elements (IEs) in the messages traced over the S1 or X2 interface contain
identities (IDs) that are unique within a protocol. Each ID represents an IE. Each IE with an ID is
coded with a length during coding. If the decoding end cannot identify the ID due to an earlier
protocol version, it ignores the IE and starts to decode the next IE. In this way, protocols in different
versions are compatible with each other. The importance is a crucial attribute for each IE or
message. The value reject for this attribute indicates that the IE or message is important. If the IE
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co.,
Ltd.
eRAN2.2
Signaling Analysis Instances
or message cannot be identified or the decoding fails, the signaling procedure or the message
processing procedure stops.
Messages traced over the Uu interface do not have an ID. Therefore, an IE is added to the end of
each message during the update of a protocol to ensure the protocol compatibility over the Uu
interface. A decoder in an earlier version stops decoding after it considers that it has decoded the
end of a message. In fact, the ending point may not be the end of the message. A decoder in a
later version continues decoding the message after it considers that it has decoded the end of the
message.
IEs in the messages traced over the Uu interface are sorted in an unaligned sequence.
The first byte in each message traced over the Uu interface is added by the eNodeB tracing
module. The reason is as follows:
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co.,
Ltd.
eRAN2.2
Signaling Analysis Instances
The messages are grouped based on the type of the channels on which the messages are
transmitted, and do not contain information about channels. Without the channel information, the
decoding module for an eNodeB and UEs can identify messages from different channels and
decode messages.
The tracing resolution tool cannot identify the messages from different channels. Therefore, the
eNodeB tracing module adds a byte head to each message to provide instructions for the tracing
resolution tool to correctly resolve messages.
Internal use
Attach Process
Signaling Involved in the Attach Process
Error: Reference source not found shows the messages related to the calling party during the
Attach process.
Internal use
Internal use
S1AP_INITIAL_CONTEXT_SETUP_REQ
The EPC transmits an S1AP_INITIAL_CONTEXT_SETUP_REQ message to an eNodeB to
instruct the eNodeB to allocate resources to UEs for data bearer setup.
Internal use
S1AP_INITIAL_CONTEXT_SETUP_REQ
Internal use
S1AP_INITIAL_CONTEXT_SETUP_RSP
The eNodeB transmits an S1AP_INITIAL_CONTEXT_SETUP_RSP message to the EPC for
bearer setup acknowledgement.
Internal use
S1AP_INITIAL_CONTEXT_SETUP_RSP