| SN | RRC Message | SRB | RLC SAP | Logical Channel | Direction | Desc |
| 1 | Paging | N/A | TM | PCCH | E-UTRAN to UE | The Pagingmessage is used for the notification of one or more UEs. |
| 2 | MasterInformationBlock | N/A | TM | BCCH | E-UTRAN to UE | The MasterInformationBlock includes the system information transmitted on BCH. |
| 3 | SystemInformationBlockType1 | N/A | TM | BCCH | E-UTRAN to UE | SystemInformationBlockType1contains
information relevant when evaluating if a UE is allowed to access a cell and
defines the scheduling of other system information. |
| 4 | SystemInformation | N/A | TM | BCCH | E-UTRAN to UE | The
SystemInformationmessage is used to convey one or more SystemInformation
Blocks. All the SIBs included are transmitted with the same periodicity. |
| 5 | RRCConnectionRequest | SRB0 | TM | CCCH | UE to E-UTRAN | The RRCConnectionRequestmessage is used to request the establishment of an RRC connection. |
| 6 | RRCConnectionSetup | SRB0 | TM | CCCH | E-UTRAN to UE | The RRCConnectionSetupmessage is used to establish SRB1. |
| 7 | RRCConnectionSetupComplete | SRB1 | AM | DCCH | UE to E-UTRAN | The RRCConnectionSetupCompletemessage is used to confirm the successful completion of an RRC connection establishment. |
| 8 | RRCConnectionReject | SRB0 | TM | CCCH | E-UTRAN to UE | The RRCConnectionRejectmessage is used to reject the RRC connection establishment. |
| 9 | RRCConnectionRelease | SRB1 | AM | DCCH | E-UTRAN to UE | The RRCConnectionReleasemessage is used to command the release of an RRC connection. |
| 10 | RRCConnectionReject | SRB0 | TM | CCCH | E-UTRAN to UE | The RRCConnectionRejectmessage is used to reject the RRC connection establishment. |
| 11 | RRCConnectionReconfiguration | SRB1 | AM | DCCH | E-UTRAN to UE | The RRCConnectionReconfigurationmessage is the command to modify an RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (including RBs, MAC main configuration and physical channel configuration) including any associated dedicated NASinformation and security configuration. |
| 12 | RRCConnectionReconfigurationComplete | SRB1 | AM | DCCH | UE to E-UTRAN | The
RRCConnectionReconfigurationCompletemessage is used to confirm the successful
completion of an RRC connection reconfiguration. |
| 13 | RRCConnectionReestablishment | SRB0 | TM | CCCH | E-UTRAN to UE | The RRCConnectionReestablishmentmessage is used to re-establish SRB1. |
| 14 | RRCConnectionReestablishmentRequest | SRB0 | TM | CCCH | UE to E-UTRAN | The RRCConnectionReestablishmentRequestmessage is used to request the reestablishment of an RRC connection. |
| 15 | RRCConnectionReestablishmentComplete | SRB1 | AM | DCCH | UE to E-UTRAN | The
RRCConnectionReestablishmentCompletemessage is used to confirm the successful
completion of an RRC connection reestablishment. |
| 16 | RRCConnectionReestablishmentReject | SRB0 | TM | CCCH | E-UTRAN to UE | The
RRCConnectionReestablishmentReject message is used to indicate the rejection
of an RRC connection reestablishment request. |
| 17 | SecurityModeCommand | SRB1 | AM | DCCH | E-UTRAN to UE | The SecurityModeCommandmessage is used to command the activation of AS security. |
| 18 | SecurityModeComplete | SRB1 | AM | DCCH | UE to E-UTRAN | The SecurityModeCompletemessage is used to confirm the successful completion of a security mode command. |
| 19 | SecurityModeFailure | SRB1 | AM | DCCH | UE to E-UTRAN | The SecurityModeFailuremessage is used to indicate an unsuccessful completion of a security mode command. |
| 20 | UECapabilityEnquiry | SRB1 | AM | DCCH | E-UTRAN to UE | The
UECapabilityEnquirymessage is used to request the transfer of UE radio access
capabilities for E-UTRA as well as for other RATs. |
| 21 | UECapabilityInformation | SRB1 | AM | DCCH | UE to E-UTRAN | The UECapabilityInformationmessage is used to transfer of UE radio access capabilities requested by the E-UTRAN. |
| 22 | UEInformationRequest | SRB1 | AM | DCCH | E-UTRAN to UE | The UEInformationRequestis the command used by E-UTRAN to retrieve information from the UE. |
| 23 | UEInformationResponse | SRB1 | AM | DCCH | UE to E-UTRAN | The UEInformationResponse message is used by the UE to transfer the information requested by the E-UTRAN. |
Wednesday, March 16, 2016
RRC Messages on LTE
Cause in LTE
RRC Connection Establishment Cause:
1. emergency
2. highPriorityAccess
3. mt-Access
4. mo-Signalling
5. mo-Data
6. delayTolerantAccess-v1020
7. spare2
8. spare1
RRC Connection Re-Establishment Cause:
1. reconfigurationFailure,
2. handoverFailure,
3. otherFailure,
4. spare1
RRC Connection Release Cause:
1. LoadBalancingTAURequired
2. 'other'
3. 'CS Fallback High Priority'
4. Normal
LTE Attach Type in Attach Request:
EPS attach type value (octet 1)
Bits
3 2 1
0 0 1 EPS attach
0 1 0 combined EPS/IMSI attach
1 1 0 EPS emergency attach
1 1 1 reserved
All other values are unused and shall be interpreted as "EPS attach", if received by the
network.
Bit 4 of octet 1 is spare and shall be coded as zero.
LTE Attach Result in Attach Accept:
EPS attach result value (octet 1)
Bits
3 2 1
0 0 1 EPS only
0 1 0 combined EPS/IMSI attach
All other values are reserved.
Bit 4 of octet 1 is spare and shall be coded as zero.
Additional update type value (AUTV) (octet 1)
Bit
1
0 No additional information. If received it shall be interpreted as request for combined
attach or combined tracking area updating.
1 SMS only
Bits 4 to 2 of octet 1 are spare and shall be all coded as zero.
Additional update result value (octet 1)
Bits
2 1
0 0 no additional information
0 1 CS Fallback not preferred
1 0 SMS only
1 1 reserved
Bits 4 and 3 of octet 1 are spare and shall all be coded as zero.
Tracking area update request Type:
EPS update type value (octet 1, bit 1 to 3)
Bits
3 2 1
0 0 0 TA updating
0 0 1 combined TA/LA updating
0 1 0 combined TA/LA updating with IMSI attach
0 1 1 periodic updating
1 0 0 unused; shall be interpreted as "TA updating", if received by the network.
1 0 1 unused; shall be interpreted as "TA updating", if received by the network.
All other values are reserved.
"Active" flag (octet 1, bit 4)
Bit
4
0 No bearer establishment requested
1 Bearer establishment requested
Tracking area update accept Result Type:
EPS update result value (octet 1, bit 1 to 3)
Bits
3 2 1
0 0 0 TA updated
0 0 1 combined TA/LA updated
1 0 0 TA updated and ISR activated (NOTE)
1 0 1 combined TA/LA updated and ISR activated (NOTE)
All other values are reserved.
Bit 4 of octet 1 is spare and shall be coded as zero.
NOTE: Values "TA updated and ISR activated" and "combined TA/LA updated and
ISR activated" are used only for a UE supporting also A/Gb or Iu mode.
Type Of Detach:
Type of detach (octet 1)
In the UE to network direction:
Bits
3 2 1
0 0 1 EPS detach
0 1 0 IMSI detach
0 1 1 combined EPS/IMSI detach
1 1 0 reserved
1 1 1 reserved
All other values are interpreted as "combined EPS/IMSI detach" in this version of the
protocol.
In the network to UE direction:
Bits
3 2 1
0 0 1 re-attach required
0 1 0 re-attach not required
0 1 1 IMSI detach
1 1 0 reserved
1 1 1 reserved
All other values are interpreted as "re-attach not required" in this version of the
protocol.
Switch off (octet 1)
In the UE to network direction:
Bit
4
0 normal detach
1 switch off
In the network to UE direction bit 4 is spare. The network shall set this bit to zero.
PDN type value (octet 1)
Bits
3 2 1
0 0 1 IPv4
0 1 0 IPv6
0 1 1 IPv4v6
1 0 0 unused; shall be interpreted as "IPv6" if received by the network
All other values are reserved.
Bit 4 of octet 1 is spare and shall be coded as zero.
1. emergency
2. highPriorityAccess
3. mt-Access
4. mo-Signalling
5. mo-Data
6. delayTolerantAccess-v1020
7. spare2
8. spare1
RRC Connection Re-Establishment Cause:
1. reconfigurationFailure,
2. handoverFailure,
3. otherFailure,
4. spare1
RRC Connection Release Cause:
1. LoadBalancingTAURequired
2. 'other'
3. 'CS Fallback High Priority'
4. Normal
LTE Attach Type in Attach Request:
EPS attach type value (octet 1)
Bits
3 2 1
0 0 1 EPS attach
0 1 0 combined EPS/IMSI attach
1 1 0 EPS emergency attach
1 1 1 reserved
All other values are unused and shall be interpreted as "EPS attach", if received by the
network.
Bit 4 of octet 1 is spare and shall be coded as zero.
LTE Attach Result in Attach Accept:
EPS attach result value (octet 1)
Bits
3 2 1
0 0 1 EPS only
0 1 0 combined EPS/IMSI attach
All other values are reserved.
Bit 4 of octet 1 is spare and shall be coded as zero.
Additional update type value (AUTV) (octet 1)
Bit
1
0 No additional information. If received it shall be interpreted as request for combined
attach or combined tracking area updating.
1 SMS only
Bits 4 to 2 of octet 1 are spare and shall be all coded as zero.
Additional update result value (octet 1)
Bits
2 1
0 0 no additional information
0 1 CS Fallback not preferred
1 0 SMS only
1 1 reserved
Bits 4 and 3 of octet 1 are spare and shall all be coded as zero.
Tracking area update request Type:
EPS update type value (octet 1, bit 1 to 3)
Bits
3 2 1
0 0 0 TA updating
0 0 1 combined TA/LA updating
0 1 0 combined TA/LA updating with IMSI attach
0 1 1 periodic updating
1 0 0 unused; shall be interpreted as "TA updating", if received by the network.
1 0 1 unused; shall be interpreted as "TA updating", if received by the network.
All other values are reserved.
"Active" flag (octet 1, bit 4)
Bit
4
0 No bearer establishment requested
1 Bearer establishment requested
Tracking area update accept Result Type:
EPS update result value (octet 1, bit 1 to 3)
Bits
3 2 1
0 0 0 TA updated
0 0 1 combined TA/LA updated
1 0 0 TA updated and ISR activated (NOTE)
1 0 1 combined TA/LA updated and ISR activated (NOTE)
All other values are reserved.
Bit 4 of octet 1 is spare and shall be coded as zero.
NOTE: Values "TA updated and ISR activated" and "combined TA/LA updated and
ISR activated" are used only for a UE supporting also A/Gb or Iu mode.
Type Of Detach:
Type of detach (octet 1)
In the UE to network direction:
Bits
3 2 1
0 0 1 EPS detach
0 1 0 IMSI detach
0 1 1 combined EPS/IMSI detach
1 1 0 reserved
1 1 1 reserved
All other values are interpreted as "combined EPS/IMSI detach" in this version of the
protocol.
In the network to UE direction:
Bits
3 2 1
0 0 1 re-attach required
0 1 0 re-attach not required
0 1 1 IMSI detach
1 1 0 reserved
1 1 1 reserved
All other values are interpreted as "re-attach not required" in this version of the
protocol.
Switch off (octet 1)
In the UE to network direction:
Bit
4
0 normal detach
1 switch off
In the network to UE direction bit 4 is spare. The network shall set this bit to zero.
PDN type value (octet 1)
Bits
3 2 1
0 0 1 IPv4
0 1 0 IPv6
0 1 1 IPv4v6
1 0 0 unused; shall be interpreted as "IPv6" if received by the network
All other values are reserved.
Bit 4 of octet 1 is spare and shall be coded as zero.
Subscribe to:
Posts (Atom)