ICS
M36
YD
Communications industry standard of The People's
Republic of China YD/T XXXXX—XXXX
Technical Specification for Uu-T
Interface of LTE based Broadband
Trunking Communication (B-Trunc)
System (Phase 1)
The Ministry of industry and information
technology of P.R.C China
XX/T XXXXX—XXXX
Contents
Foreword ............................................................................. 2
1 Scope ............................................................................... 2
2 Normative References .................................................................. 2
3 Abbreviations ........................................................................ 3
4 Physical Layer Part 1: General Description ................................................. 4
5 Physical Layer Part2: Physical Channels and Modulation ...................................... 5
6 Physical Layer Part3: Physical Layer Multiplexing and Channel Coding .......................... 5
6.1 Mapping of the transport channel to physical channel ..................................... 5
6.2 Channel coding, multiplexing and interleaving........................................... 6
7 Physical Layer Part4: Physical layer procedures.............................................. 6
7.1 UE procedure for receiving the physical downlink shared channel ........................... 6
7.2 CQI/PMI/RI Reporting ............................................................. 8
7.3 ACK/NACK Reporting ............................................................. 8
7.4 Physical uplink shared channel related procedures ........................................ 8
7.5 Physical downlink control channel procedures ........................................... 8
8 Physical layer, part 5：Physical Layer Measurement ......................................... 10
9 Lay2, part 1:Medium Access Control (MAC) protocol........................................ 10
9.1 MAC Structure .................................................................. 10
9.2 Channel structure and channel mapping ............................................... 11
9.3 Protocol Data Units ............................................................... 13
9.4 RNTI values and usage ............................................................ 14
9.5 DL-SCH data transfer ............................................................. 15
9.6 TPCH reception .................................................................. 16
9.7 PDCCH search space control for trunking group call ..................................... 17
9.8 Trunking Buffer Status Report (Optional) .............................................. 18
10 Lay2, part2: Radio Link Control (RLC) protocol ......................................... 20
11 Lay2, part3: Packet Data Convergence Protocol (PDCP) ................................ 20
12 Layer 3 Part 1: RRC Protocol .......................................................... 21
12.1 Overview ...................................................................... 21
12.2 System Information .............................................................. 22
12.3 RRC Process ................................................................... 22
12.4 Others ........................................................................ 26
12.5 Protocol Data Unit, Format, and Parameter (Table and ASN.1) ............................ 28
12.6 Variable and Constant ............................................................ 48
13 Layer 3 Part 2: Trunking Services of UEs in Idle Mode ...................................... 50
13.1 UEs In Idle Mode Receiving Data from the Trunking Control Channel and Traffic Channel ..... 50
13.2 Trunking Paging DRX ............................................................ 51
1
XX/T XXXXX—XXXX
Foreword
The present document is one of a series standards for the LTE based broadband trunking communication
(B-TrunC) system and will consist of the following standards:
a) YD/T ××××: Technical Specification for LTE based Broadband Trunking Communication
(B-Trunc) System (Phase 1)》
b) YD/T ××××: Technical Specification for Uu-T Interface of LTE based Broadband Trunking
Communication (B-Trunc) System (Phase 1)
c) YD/T ××××: Technical Requirement for Interface between User Equipment (UE) and Evolved
Packet Core (EPC) of LTE based Broadband Trunking Communication (B-Trunc) System (Phase 1)
d) YD/T ××××: Technical Requirement for Interface between Evolved Packet Core (EPC) and
Dispatch Controller (DC) of LTE based Broadband Trunking Communication (B-Trunc) System
(Phase 1)
e) YD/T × × × × : Test Method for Uu-T Interface of LTE based Broadband Trunking
Communication (B-Trunc) System (Phase 1)
f) YD/T ××××: Test Method for Interface between User Equipment (UE) and Evolved Packet
Core (EPC) of LTE based Broadband Trunking Communication (B-Trunc) System (Phase 1)
g) YD/T ××××: Test Method for Interface between Evolved Packet Core (EPC) and Dispatch
Controller (DC) of LTE based Broadband Trunking Communication (B-Trunc) System (Phase 1)
This document has been produced by China Communications Standards Association (CCSA).
The structure of the series standards are subject to the continuing work within CCSA TC5.
1
Scope
The present document specifies the Uu-T interface of LTE based broadband trunking communication (B-Trunc)
system (Phase 1).
The present document applies to UEs and eNodeBs of LTE based broadband trunking communication
(B-Trunc) system (Phase 1).
2
Normative References
The following documents contain provosions which, through reference in this text, constitute provisions of the
present document. References are either specific (identified by date of publications, edition number, version
2
XX/T XXXXX—XXXX
number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific
reference, the latest version (including any amendments) applies.
[1] 3GPP TS 36.201: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Layer – General
Description(Release 9)”
[2] 3GPP TS 36.211: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and
modulation(Release 9)”
[3] 3GPP TS 36.212: “Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel
coding(Release 9)”
[4] 3GPP TS 36.213: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer
procedures(Release 9)”
[5] 3GPP TS 36.214: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer –
Measurements(Release 9)”
[6] 3GPP TS36.321, “Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control
(MAC) protocol specification(Release 9)”
[7] 3GPP TS36.322, “Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC)
protocol specification(Release 9)”
[8] 3GPP TS36.322, “Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence
Protocol (PDCP) Specification(Release 9)”
[9] 3GPP TS36.331, “Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC)
protocol specification(Release 9)”
[10] 3GPP TS 36.304, “Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
procedures in idle mode(Release 9)”
3
Abbreviations
For the purpose of the present document, the following abbreviations apply.
BSR
CQI
Buffer Status Report
Channel Quality Indication
CRC
Cyclic Redundancy Check
DL-SCH
Downlink Shared Channel
eNode B
Evolved NodeB
E-UTRAN
Evolved UTRAN
G-RNTI
Group-Radio Network Temporary Identifier
HARQ
Hybrid Automatic Repeat Request
LCID
Logical Channel ID
LTE
Long Time Evolution
MAC
Medium Access Control
3
XX/T XXXXX—XXXX
4
NAS
Non-Access Stratum
PBCH
PCH
Physical Broadcast Channel
Paging Channel
PCFICH
PDCCH
PDCP
Physical Control Format Indicator Channel
Physical Downlink Control Channel
Packet Data Convergence Protocol
PDSCH
PHICH
PMCH
PMI
Physical Downlink Shared Channel
Physical Hybrid ARQ Indicator Channel
Physical Multicast Channel
Precoding Matrix Indicator
PRACH
PUCCH
PUSCH
RI
Physical Random Access Channel
Physical Uplink Control Channel
Physical Uplink Shared Channel
Rank Indication
RLC
Radio Link Control
RNTI
RRC
TCCH
Radio Network Temporary Identifier
Radio Resource Control
Trunking Control Channel
TDD
Time Division Duplex
TDRB
Trunking Data Radio Bearer
TGID
Trunking Group Identification
TPCCH
Trunking Paging Control Channel
TPCH
Trunking Paging Channel
TP-RNTI
Trunking Paging-Radio Network Temporary Identifier
TSRB
Trunking Signalling Radio Bearer
TTCH
Trunking Traffic Channel
Physical Layer Part 1: General Description
This Part follows 3GPP TS 36.201.
The physical layer process for point-to-point services (e.g. individual calls) of broadband trunking
communication (B-TrunC) system is specified in [1] and that for point-to-multipoint services (e.g. group calls)
is defined in the present document.
The definition of physical channels, modulation and channel coding scheme in [1] applies to the B-Trunc
system.
4
XX/T XXXXX—XXXX
The following downlink physical channels of B-TrunC are defined:
——Physical Downlink Shared Channel, PDSCH
——Physical Downlink Control Channel, PDCCH
——Physical Broadcast Channel, PBCH
——Physical Control Format Indicator Channel, PCFICH
——Physical Hybrid ARQ Indicator Channel, PHICH
The following uplink physical channels of B-Trunc are defined:
——Physical Random Access Channel, PRACH
——Physical Uplink Shared Channel, PUSCH
——Physical Uplink Control Channel, PUCCH
The system shall support intra-system L1 measurement while inter-system L1 measurement is not considered.
5
Physical Layer Part2: Physical Channels and Modulation
This part is specified in [2].
6
Physical Layer Part3: Physical Layer Multiplexing and Channel Coding
6.1 Mapping of the transport channel to physical channel
For uplink transmission, the mapping of uplink transport channels and uplink channel control information to
their corresponding physical channels is specified in [3].
For downlink transmission, trunking paging channel (TPCH), a new downlink transport channel is defined to
carry pagings related to the trunking calls including group calls and individual calls. TPCH maps to downlink
shared channel (PDSCH) while the mapping of other downlink transport channels and downlink channel
control information to their corresponding physical channels is specified in [3].
Table 1 specifies the mapping of the downlink transport channels to their corresponding physical channels.
Table 1: Mapping of the downlink transport channel to physical channel
5
XX/T XXXXX—XXXX
Transport channel
Physical channel
Downlink shared Channel, DL-SCH
Physical Downlink Shared Channel, PDSCH
Broadcast Channel, BCH
Physical Broadcast Channel, PBCH
Paging Channel, TPCH
Physical Downlink Shared Channel, PDSCH
Trunking Paging Channel, TPCH
Physical Downlink Shared Channel, PDSCH
6.2 Channel coding, multiplexing and interleaving
Besides the requirements specified in [3], the following channel coding, multiplexing and interleaving shall
also apply:
——The same coding scheme and coding rate for the PCH applies to the TPCH.
——The same transport channel processing for the PCH applies to the TPCH.
——Downlink control information (DCI) format 1A/1C is enhanced to support with CRC scrambled by
the new defined TP-RNTI.
——Upon receiving the DCI format 1A/1C with CRC scrambled by TP-RNTI, a UE shall perform all the
fields in the DCI format 1A/1C the same as P-RNTI.
7
Physical Layer Part4: Physical layer procedures
7.1 UE procedure for receiving the physical downlink shared channel
If a UE is configured by higher layers to decode PDCCH with CRC scrambled by the TP-RNTI (Trunking
Paging RNTI), the UE shall decode the PDCCH and the corresponding PDSCH according to any of the
combinations defined in Table 2. The scrambling initialization of PDSCH corresponding to these PDCCHs is
by TP-RNTI.
Table2: PDCCH and PDSCH configured by TP-RNTI
DCI format
Search Space
DCI format 1A
Common
Transmission scheme of PDSCH
If the number of PBCH antenna ports is one, port 0 is used, otherwise
transmit diversity.
If the number of PBCH antenna ports is one, port 0 is used, otherwise
DCI format 1C
Common
transmit diversity.
If a UE is in RRC_IDLE state and configured by higher layers to decode PDCCH with CRC scrambled by the
G-RNTI (Group RNTI), the UE shall decode the PDCCH and the corresponding PDSCH according to any of
the combinations defined in Table 3. The scrambling initialization of PDSCH corresponding to these PDCCHs
is by G-RNTI.
6
XX/T XXXXX—XXXX
Table 3: PDCCH and PDSCH configured by G-RNTI (UE in RRC_IDLE state)
DCI format
Search Space
DCI format 1A
Transmission scheme of PDSCH
Common and
If the number of PBCH antenna ports is one, port 0 is used, otherwise
group-specific by
transmit diversity.
G-RNTI
If a UE is in RRC_CONNECTED state and configured by higher layers to decode PDCCH with CRC
scrambled by the G-RNTI, the UE shall decode the PDCCH and the corresponding PDSCH according to any
of the combinations defined in Table 4. The scrambling initialization of PDSCH corresponding to these
PDCCHs is by G-RNTI.
Table 4: PDCCH and PDSCH configured by G-RNTI (UE in RRC_CONNECTED state)
DCI format
Search Space
Transmission scheme of PDSCH
Blind decoding capability of G-RNTI PDCCH
class1: Common and group-specific by
DCI format
If the number of PBCH antenna ports is one, port 0 is
G-RNTI;
1A
used, otherwise transmit diversity.
Blind decoding capability of G-RNTI PDCCH
class2: common
Note: Blind decoding capability of G-RNTI PDCCH class1and class 2 are defined in section 9.7.1.
If a UE is in RRC_IDLE state and configured by higher layers to decode PDCCH with CRC scrambled by the
SPS G-RNTI, the UE shall decode the PDCCH and the corresponding PDSCH according to any of the
combinations defined in Table 5. The same PDSCH related configuration applies in the case that a PDSCH is
transmitted without a corresponding PDCCH. The scrambling initialization of PDSCH corresponding to these
PDCCHs and PDSCH without a corresponding PDCCH is by SPS G-RNTI.
Table 5: PDCCH and PDSCH configured by SPS-RNTI (UE in RRC_IDLE state)
DCI format
DCI format 1A
Search space
Transmission scheme of PDSCH
Common and
If the number of PBCH antenna ports is one, port 0 is used, otherwise
group-specific by
transmit diversity.
G-RNTI
If a UE is in RRC_IDLE state and configured by higher layers to decode PDCCH with CRC scrambled by the
SPS G-RNTI, the UE shall decode the PDCCH and the corresponding PDSCH according to any of the
combinations defined in Table 6. The same PDSCH related configuration applies in the case that a PDSCH is
7
XX/T XXXXX—XXXX
transmitted without a corresponding PDCCH. The scrambling initialization of PDSCH corresponding to these
PDCCHs and PDSCH without a corresponding PDCCH is by SPS G-RNTI.
Table 6: PDCCH and PDSCH configured by SPS-RNTI (UE in RRC_CONNECTED state)
DCI format
Search Space
Transmission scheme of PDSCH
Blind decoding capability of G-RNTI PDCCH
class1: Common and group-specific by
DCI format
If the number of PBCH antenna ports is one, port 0 is
G-RNTI;
1A
used, otherwise transmit diversity.
Blind decoding capability of G-RNTI PDCCH
class2: common
Note: Blind decoding capability of G-RNTI PDCCH class1 and class 2 are defined in section 9.7.1.
The same determination of modulation order and transport block size (TBS) for the PDSCH scrambled by
P-RNTI applies to PDSCH scrambled by TP-RNTI.
The same determination of modulation order and transport block size (TBS) for the PDSCH scrambled by
C-RNTI applies to PDSCH scrambled by G-RNTI.
7.2 CQI/PMI/RI Reporting
This part is specified in [4].
7.3 ACK/NACK Reporting
ACK/NACK is not provided for the PDSCH transmission scrambled by the G-RNTI
7.4 Physical uplink shared channel related procedures
This part is specified in chapter 8 of [4].
7.5 Physical downlink control channel procedures
7.5.1 PDCCH assignment procedures
Besides the requirements specified in 3GPP TS 36.213 chapter 9, an additonal group-specific search space is
defined.
The CCEs corresponding to PDCCH candidate m of the group-specific search space

S k(L )
are given by

L  Yk  m  mod  NCCE,k / L   i
( L)
(L )
where Yk is defined below, i  0, , L 1 ， m  0, , M  1 . M is the number of PDCCH candidates to
monitor in the given search space.
The UE shall monitor one group-specific search space at each of the aggregation levels 1,2,4,8.
8
XX/T XXXXX—XXXX
The aggregation levels defining the search space are listed in Table 7.
Table 7: PDCCH candidates of the group-specific space monitored by a UE
Number of PDCCH
(L )
Search space S k
candidates M
Aggregation level L
Size [in CCEs]
1
6
6
Group-
2
12
6
specific
4
8
2
8
16
2
Type
For the group-specific search space
S k(L )
(L )
at aggregation level L , the variable Yk is defined by
Yk   A  Yk 1  mod D
k   ns 2 ns
where Y1  nRNTI  0 , A  39827 , D  65537 and
,
is the slot number within a radio frame.
The RNTI value used for nRNTI is set to G-RNTI assigned to the group.
7.5.2 PDCCH validation for semi-persistent scheduling of group call
A UE shall validate a Semi-Persistent Scheduling assignment PDCCH of group call only if all the following
conditions are met:
- The CRC parity bits obtained for the PDCCH payload are scrambled with the Semi-Persistent
Scheduling C-RNTI
- The new data indicator field is set to ‘0’.
Validation is achieved if all the fields for the DCI format 1A are set according to Table 8 or Table 9.
If validation is achieved, the UE shall consider the received DCI information accordingly as a valid
semi-persistent activation or release.
Table 8: Special fields for Semi-Persistent Scheduling Activation PDCCH Validation
DCI format 1A
HARQ process number
Modulation and coding
scheme
Redundancy version
Set to ‘0000’
MSB is set to ‘0’
Set to ‘00’
9
XX/T XXXXX—XXXX
Table 9: Special fields for Semi-Persistent Scheduling Release PDCCH Validation
DCI format 1A
HARQ process number
Set to ‘0000’
Modulation
scheme
Set to ‘11111’
and
coding
Set to ‘00’
Redundancy version
Set to all ‘1’s
Resource block assignment
7.5.3 Physical uplink control channel procedures
This part is specified in chapter 10 of [4].
8
Physical layer, part 5：Physical Layer Measurement
This section is based on YD/T 2560.5-2013 “TD-LTE digital cellular mobile telecommunication network Uu
Interface Technical Requirement – Part 5: Physical Layer Measurement”
9
Lay2, part 1:Medium Access Control (MAC) protocol
9.1 MAC Structure
Figure 1 illustrates one possible structure for the UE side MAC entity, and it should not restrict
implementation.
PCCH TPCCH MCCH MTCH
TCCH
TTCH
BCCH
CCCH DCCH
DTCH
MAC-control
Logical Channel prioritisation (UL only)
De multiplexing
(De-) Multiplexing
De multiplexing
HARQ
PCH
TPCH
MCH
Control
Random Access
Control
BCH DL-SCH UL-SCH
RACH
Figure 1: MAC structure overview, UE side
10
XX/T XXXXX—XXXX
9.2 Channel structure and channel mapping
Table10 illustrates the logical channels related to trunking service. Some Trunking service special logical
channels are added besides LTE logical channels.
Table10:logical channels related to trunking service
Logical channel
CCCH
PCCH
functions
Channel for transmitting control information
between UEs and network. This channel is
used for UEs having no RRC connection with
the network.
A downlink channel that transfers paging
information of LTE service and system
information change notifications. This
channel can transfer group call and private
call of trunking service.
BCCH
A downlink channel for broadcasting system
control information.
TCCH
A point-to-multipoint downlink channel used
for transmitting trunking control information
from the network to the UE.
TTCH
A point-to-multipoint downlink channel for
transmitting trunking traffic data from the
network to the UE.
DCCH
A point-to-point bi-directional channel that
transmits dedicated control information
between a UE and the network. Used by UEs
having an RRC connection.
DTCH
TPCCH
A Dedicated Traffic Channel (DTCH) is a
point-to-point channel, dedicated to one UE,
for the transfer of user information. A DTCH
can exist in both uplink and downlink.
A point-to-multipoint downlink channel that
transfers trunking paging information and
trunking
system
information
change
notifications.
11
XX/T XXXXX—XXXX
9.2.1 TCCH
TCCH is a point-to-multipoint downlink channel used for transmitting trunking control information from the
network to the Group UE. TCCH can be mapped to DL-SCH.
9.2.2 TTCH
TCCH is a point-to-multipoint downlink channel for transmitting trunking traffic data from the network to the
Group UE. TTCH can be mapped to DL-SCH.
9.2.3 TPCCH
TPCCH is a point-to-multipoint downlink channel that transfers trunking paging information and trunking
system information change notifications. TPCCH can be mapped to TPCH.
9.2.4 Mapping of Trunking related Downlink Channels
BCCH
CCCH
DCCH
DTCH
TTCH
TCCH
TPCCH
PCCH
Downlink
Logical channels
Downlink
Transport channels
BCH
DL-SCH
TPCH
PCH
Downlink
Physical channels
PBCH
PDSCH
PHICH
PCFICH
PDCCH
Figure 2: Downlink channel mapping
9.2.5 Uplink mapping
The uplink logic channels，CCCH, DCCH and DTCH, have the same mapping relationship as LTE, The uplink
logical channels can be mapped as described in Figure 3.
12
XX/T XXXXX—XXXX
CCCH
DCCH
DTCH
RACH
UL-SCH
PRACH
PUSCH
Uplink
Logical channels
Uplink
Transport channels
Uplink
Physycial channels
Figure 3: Uplink channel mapping.
9.3 Protocol Data Units
The design of MAC PDU for the new trunking related channels is same as the design of LTE. The
corresponding LCID should be defined when the new logical channels are mutiplexed.
The LCID for the DL-SCH of trunking group transmission identifies the logical channel instance of the
corresponding MAC SDU or padding as described in Table 11.
Table 11:
Values of LCID for DL-SCH of trunking group transmission
Index
LCID values
01011
TCCH
01100-10101
Identity of the logical channel of
TTCH
10110-11011
Reserved
11111
Padding
The LCID for the UL-SCH of trunking group/private transmission identifies the logical channel instance of the
corresponding MAC SDU or padding as described in Table 12.
Table 12: Values of LCID for UL-SCH of trunking group/private
transmission
Index
LCID values
00000
CCCH
00001-01010
Identity of the logical channel
01011
G-RNTI
01100-11001
Reserved
11010
Power Headroom Report
13
XX/T XXXXX—XXXX
11011
C-RNTI
11100
Truncated BSR
11101
Short BSR
11110
Long BSR
11111
Padding
9.3.1 G-RNTI MAC Control Element
The G-RNTI MAC Control Element is identified by MAC PDU subheader with LCID as specified in Table 12.
It has a fixed size and consists of a single field defined as follows (Figure 4):
G-RNTI
Oct 1
G-RNTI
Oct 2
Figure 4: G-RNTI MAC Control Element
9.4 RNTI values and usage
RNTI values are presented in Table 13.
Table 13: RNTI values
14
XX/T XXXXX—XXXX
Value (hexa-decimal)
RNTI
0000
N/A
0001-003C
RA-RNTI, C-RNTI, Semi-Persistent Scheduling C-RNTI, Temporary
C-RNTI, TPC-PUCCH-RNTI 和 TPC-PUSCH-RNTI，G-RNTI，
Semi-Persistent Scheduling G-RNTI
003D-FFF3
C-RNTI, Semi-Persistent Scheduling C-RNTI, Temporary C-RNTI,
TPC-PUCCH-RNTI 和 TPC-PUSCH-RNTI，G-RNTI，
Semi-Persistent Scheduling G-RNTI
FFF4
TP-RNTI
FFF5-FFFC
Reserved for future use
FFFD
M-RNTI
FFFE
P-RNTI
FFFF
SI-RNTI
NOTE: G-RNTI is used to scramble the DCI for the control channel and traffic channels of trunking group
transmission. TP-RNTI is used to scramble the DCI for the trunking paging channel.
RNTI usage and associated Transport Channels and Logical Channels are presented in Table14.
Table14: RNTI usage
RNTI
Usage
G-RNTI
Dynamically scheduled trunking group
transmission
Semi-Persistent Scheduling
G-RNTI
Semi-Persistently scheduled trunking group
transmission
Transport
Channel
Logical
Channel
DL-SCH
TTCH，
TCCH
DL-SCH
TTCH，
TCCH
9.5 DL-SCH data transfer
9.5.1 DL Assignment reception
15
XX/T XXXXX—XXXX
Downlink assignments transmitted on the PDCCH indicate if there is a transmission on the DL-SCH for a
particular UE/group UE and provide the relevant HARQ information for the services, except for downlink
trunking group service.
When the UE has C-RNTI, SPS C-RNTI, or Temporary C-RNTI(the RNTI usage are described in
subclause 7.1, YD/T 2561.1-2013), for each TTI during which it monitors PDCCH, the UE shall :
——if a downlink assignment for this TTI has been received on the PDCCH for the UE’s C-RNTI, or
Temporary C-RNTI, or SPS C-RNTI, the UE should do according to rules in subclause 5.3.1, YD/T
2561.1-2013.
——else, if a downlink assignment for this TTI has been configured and there is no measurement gap in
this TTI and this TTI is not an MBSFN subframe, the UE should do according to rules in subclause
5.3.1, YD/T 2561.1-2013.
When the UE has a G-RNTI, Semi-Persistent Scheduling G-RNTI (the RNTI usage are described in
subclause 10.4), for each TTI during which it monitors PDCCH, the UE shall:
——If a downlink assignment for this TTI has been received on the PDCCH for the UE’s G-RNTI,
 if a TB of DL-SCH has been successfully decoded, the UE shall demultiplex MAC PDU.
 if the MAC PDU demultiplexed is the data of TCCH, the UE shall deliver the decoded
MAC SDU(s) to upper layers.

if the MAC PDU demultiplexed is the data of TTCH, the UE shall deliver the decoded
MAC SDU(s) to upper layers.
——else，if a downlink assignment for this TTI has been received on the PDCCH for the UE’s
Semi-Persistent Scheduling G-RNTI, the UE shall:


if PDCCH contents indicate SPS release:
 clear the configured downlink assignment (if any);
else：
 store the downlink assignment as configured downlink assignment for trunking;
 initialise (if not active) or re-initialise (if already active) the configured downlink
assignment to start in this TTI and to recur according to rules;


receive and attempt to decode the TB on the, basing on the indication of PDCCH.
if the TB of DL-SCH has been decoded successfully:
 demultiplex the MAC PDU, and deliver the decoded MAC SDU(s) to upper layers..
——else, if a downlink assignment for this TTI has been configured for trunking group transition and
there is no measurement gap in this TTI and this TTI is not an MBSFN subframe:

instruct the physical layer to receive, in this TTI, transport block on the DL-SCH according to
the configured downlink assignment.


attempt to decode the TB on the DL-SCH.
if the TB of DL-SCH has been decoded successfully:
 demultiplex the MAC PDU, and deliver the decoded MAC SDU(s) to upper layers..
9.6 TPCH reception
When the UE needs to receive TPCH, the UE shall:
——if a TPCH assignment has been received on the PDCCH for the TP-RNTI:
16
XX/T XXXXX—XXXX
 attempt to decode the TB on the TPCH as indicated by the PDCCH information.
——if a TB on the TPCH has been successfully decoded:
 deliver the decoded MAC PDU to upper layers.
9.7 PDCCH search space control for trunking group call
9.7.1 UE capability of PDCCH search space
In order to describe the convenience, two classes UE blind decoding capability of G-RNTI PDCCH
search space are defined as follows:
Blind decoding capability of G-RNTI PDCCH class 1: in one downlink subframe, the UE can blind
decode the C-RNTI/SPS C-RNTI/Temporary C-RNTI in PDCCH common search space and UE specific
search space, at the same time, the UE can blind decode the G-RNTI/SPS G-RNTI in PDCCH common search
space and group specific search space.
Blind decoding capability of G-RNTI PDCCH class 2: in one downlink subframe, the UE can blind
decode the C-RNTI/SPS C-RNTI/Temporary C-RNTI in PDCCH common search space and UE specific
search space, at the same time, the UE can blind decode the G-RNTI/SPS G-RNTI in PDCCH common search
space.
The blind decoding capability of G-RNTI PDCCH class 1 UE shall support:
In RRC IDLE mode, the UE shall support blind decode G-RNTI/SPS G-RNTI in PDCCH common
search space and group specific search space.
In RRC Connected mode, the UE shall support blind decode the G-RNTI/SPS G-RNTI in PDCCH
common search space and group specific search space, at the same time, the UE shall support blind decode the
C-RNTI/SPS C-RNTI/Temporary C-RNTI in PDCCH common search space and UE specific search space.
The blind decoding capability of G-RNTI PDCCH class 2 UE shall support:
In RRC IDLE mode, the UE shall support blind decode G-RNTI/SPS G-RNTI in PDCCH common
search space and group specific search space.
In RRC Connected mode, the UE shall support blind decode the G-RNTI/SPS G-RNTI in PDCCH
common search space, at the same time, the UE shall support blind decode the C-RNTI/SPS
C-RNTI/Temporary C-RNTI in PDCCH common search space and UE specific search space.
9.7.2 UE capability report
For the blind decoding capability of G-RNTI PDCCH class 2 UE, and/or the UE don’t support decode
C-RNTI PDSCH and G-RNTI PDSCH at the same time in one downlink TTI, the UE shall send a G-RNTI
MAC CE in Msg3 on random access procedure in following scenarios:
——in RRC Connected mode, receives group call paging (scenario1)
——from RRC IDLE to RRC Connected when the UE is receiving group call (scenario2)
——RRC Connected mode UE applies handover procedure when it is receiving group call (scenario3)
17
XX/T XXXXX—XXXX
——IDLE mode UE applies cell reselection procedure when it is receiving group call (scenario4)
——G-RNTI change (scenario5)
NOTE: in order to transmit G-RNTI MAC CE in Msg3, eNB shall set the threshold of
messageSizeGroupA of Random Access Preamble group A no less than 144bit.
9.7.3 Handling process of eNB
The eNB shall schedule the G-RNTI in PDCCH common search space when eNB detects there is a blind
decoding capability of G-RNTI PDCCH class 2 UE in RRC Connected mode who is listening the group call.
for scenario1 and scenario 4 in subclause 9.7.2, eNB and UE shall support:
1. the eNB set a timer(300ms) when a trunking paging is send, before the timer expired, eNB shall
schedule the G-RNTI in PDCCH common search.
2. A blind decoding capability of G-RNTI PDCCH class2 UE, in RRC Connected mode, shall send an
G-RNTI MAC CE when it received a trunking paging.
3. When timer expired and no group UE send G-RNTI MAC CE, the eNB can change the schedule space
form PDCCH common search to group search space, otherwise, the eNB shall schedule the G-RNTI in
PDCCH common search.
Except the above situations, eNB may schedule the G-RNTI in PDCCH common search or group search
space.
When the eNB receives the G-RNTI MAC CE sent by a UE through the MAC layer, and the UE is still in
the RRC connection mode, the eNB can stagger C-RNTI PDSCH and G-RNTI PDSCH scheduling time for the
UE.
9.8 Trunking Buffer Status Report (Optional)
Trunking Buffer Status Report is an optional function, and UE needn’t mandatory support it.
9.8.1 Buffer Status Report MAC Control Elements
Buffer Status Report (BSR) MAC control elements consist of either:
——Short BSR and Truncated BSR format
——Long BSR format
——Trunking Short BSR and Trunking Truncated BSR format
——Trunking Long BSR format
The formats of short BSR, truncated BSR and long BSR are identified by MAC PDU subheaders with
LCIDs as specified in subclause 6.1.3.1, YD/T 2012-0382.
for trunking BSR control element:
——the Trunking Short BSR and Trunking Truncated BSR format: one LC ID field and one
corresponding Buffer Size field (figure 5)
——the Trunking Long BSR format: four Buffer Size fields, corresponding to LCG IDs #0 through #3
(figure 6)
The Logical Channel ID field in BSR MAC CE identifies the group of trunking logical channel(s) which buffer
status is being reported. The length of the field is 2 bits;
18
XX/T XXXXX—XXXX
LC ID
Buffer Size
Oct 1
Figure 5: Trunking Short BSR and Trunking Truncated BSR MAC control element
Buffer Size #0
Buffer Size #1
Buffer
Size #2
Buffer
Size #1
Buffer Size #2
Buffer Size #3
Oct 1
Oct 2
Oct 3
Figure 6: Trunking Long BSR MAC control element
9.8.2 Values of LCID for trunking BSR
For Trunking Short BSR, Trunking Truncated BSR and Trunking Long BSR MAC CE, the corresponding
values of LCID as described in table 15。
Table 15: Values of LCID for DL-SCH（Trunking BSR）
Index
Value of LCID
01111
Trunking Truncated BSR
10000
Trunking Short BSR
10001
Trunking Long BSR
9.8.3 Buffer Status Reporting
The Buffer Status reporting are classified into:
——Regular BSR
——Padding BSR
——Periodic BSR
——Trunking BSR
Regular and Periodic BSR shall be triggered and reported following the rules in subclause 5.4.5, YD/T
2012-0382.
The trunking BSR is a BSR which is triggered by trunking traffic transmition. For trunking BSR:
——if more than one LCG has trunking traffic data available for transmission in the TTI where the BSR
is transmitted: report Trunking Long BSR;
——else report Trunking Short BSR.
if an uplink grant is not configured after Trunking BSR was triggered, a Scheduling Request shall be
triggered.
For Padding BSR
19
XX/T XXXXX—XXXX
For LTE UE，Padding BSR shall be triggered and reported following the rules in subclause 5.4.5, YD/T
2012-0382.
For trunking UE, when an uplink grant is configured and the number of padding bits is equal to or larger
than the size of the BSR MAC control element plus its subheader, BSR will be triggered.
-
if more than one logical channel related to trunking service has data available for transmission in
the TTI:
-
if the number of padding bits is equal to or larger than the size of the Trunking Short BSR plus its
subheader but smaller than the size of the Trunking Long BSR plus its subheader
-
if more than one LCG has data available for transmission in the TTI where the BSR is
transmitted: report Truncated BSR of the LCG with the highest priority logical channel
with data available for transmission;
-
else report Trunking Short BSR.
else if the number of padding bits is equal to or larger than the size of the Trunking Long BSR
plus its subheader, report Trunking Long BSR.
-
else，if the number of padding bits is equal to or larger than the size of the Short BSR plus its
subheader but smaller than the size of the Long BSR plus its subheader:
-
if more than one LCG has data available for transmission in the TTI where the BSR is
transmitted: report BSR of the LCG with the highest priority logical channel with data available
for transmission;
-
-
else report Short BSR
else if the number of padding bits is equal to or larger than the size of the Long BSR plus its
subheader, report Long BSR.
A MAC PDU may contain one MAC BSR control element and/or one trunking MAC BSR control element,
even when multiple events trigger a BSR by the time a BSR can be transmitted in which case.
10
Lay2, part2: Radio Link Control (RLC) protocol
Trunking traffic channel/Trunking control channel: UM mode.
Trunking Paging channel (TPCCH): TM mode.
11
Lay2, part3: Packet Data Convergence Protocol (PDCP)
For private call: following the rules in YD/T 2561.3-2013.
For group call, TCCH, TTCH, PDCP supports the following functions:
——header compression and decompression of IP data flows using the ROHC protocol; (optional, see
20
XX/T XXXXX—XXXX
note)
——transfer of data (user plane or control plane);
——maintenance of PDCP SNs;
——in-sequence delivery of upper layer PDUs at re-establishment of lower layers;
——timer based discard;
——duplicate discarding.
Note: header compression and decompression for TCCH/TTCH is an optional function for trunking UE.
PDCP uses the services provided by the RLC sublayer.
PDCP is used for TSRBs and TDRBs mapped on TCCH and TTCH type of logical channels.
PDCP transparent Mode is applied to TPCCH.
12 Layer 3 Part 1: RRC Protocol
12.1 Overview
12.1.1 UE Status
The UE status complies with the regulations in section 4.2.1 in YD/T 2562.1-2013 TD-LTE digital
cellular mobile telecommunication network Uu interface layer 3 technical requirements (Phase 1) (Part 1: RRC
protocol). In addition, trunking UEs must comply with the following descriptions:
UEs in the RRC_IDLE state:
——obtain system information, including trunking related system information.
——periodically listen to the trunking paging control channel.
——listen to the trunking control channel (the listening is triggered by trunking paging).
——if a trunking group call has been set up, listen to the trunking service channels and obtain
trunking service data.
Called UEs in the RRC_CONNECTED state:
——obtain system information, including trunking related system information.
——periodically listen to the trunking paging control channel.
——listen to the trunking control channel (the listening is triggered by trunking paging).
——if a trunking group call has been set up, listen to the trunking service channels and obtain
trunking service data.
12.1.2 Signaling Radio Bearer (SRB)
SRB refers to a radio bearer (RB) used only for transmitting RRC and NAS messages. There are four
types of SRBs:
——SRB0 is used for transmitting RRC messages on the CCCH.
——SRB1 is used for transmitting RRC messages, which may contain certain NAS messages, on
the DCCH. Before SRB2 is established, SRB1 may also be used for transmitting NAS messages on the
21
XX/T XXXXX—XXXX
DCCH.
——SRB2 is used for transmitting NAS messages on the DCCH. SRB2 has a lower priority than
SRB1 and is configured by the E-UTRAN after security activation.
——TSRB is used to transmit the trunking-group-related downlink RRC messages (certain NAS
messages may be included in the RRC messages) and NAS messages on the TCCH.
12.2 System Information
12.2.1 Overview
UE
E-UTRAN
MasterInformationBlock
SystemInformationBlockType1
SystemInformation
Figure 7: system information
Figure 7 shows the system message transmission procedure. This procedure follows the regulations in
section 5.2.2 in YD/T 2562.1-2013. In addition, trunking UEs must comply with the following descriptions.
A type of new system messages, SystemInformationBlockTypeTrunking, is added. The UE obtains
trunking-related system information from SystemInformationBlockTypeTrunking messages. Accordingly,
SystemInformation and SystemInformationBlockType1 messages are added with a new SIB type,
SystemInformationBlockTypeTrunking.
12.2.2 Receiving SystemInformationBlockTypeTrunking Messages
Except for special regulations in other chapters in the YD/T 2562.1-2013, such as system message processing
and/or domain processing, no more requirements are imposed for UEs.
12.3 RRC Process
12.3.1 Paging
12.3.1.1 Overview
22
XX/T XXXXX—XXXX
UE
EUTRAN
TrunkingPaging
Figure 8 Paging procedure
As show in Figure 8, paging messages are sent to UEs in the RRC_IDLE and RRC_CONNECTED state
for informing the UEs of trunking group call and private call services.
12.3.1.2 Initializing
The E-UTRAN initiates a paging procedure by transmitting a TrunkingPaging message at the UE paging
occasion. For details about the UE paging occasion, see "Procedure of UEs in Idle Mode". One
TrunkingPaging message may contain multiple PagingRecord information elements, each for one group or UE.
This way, the E-UTRAN can use one paging message to page UEs for multiple group calls and/or specified
UEs for private calls. The E-UTRAN can also use the TrunkingPaging message to notify UEs of changes of
system information.
12.3.1.3 UE Receiving the TrunkingPaging Message
When a UE detects the PDCCH scrambled by the TP-RNTI and receives the TrunkingPaging message on
the PDSCH indicated by the PDCCH, the UE shall:
1> extract parameters for all groups calls, such as Group ID and Group Priority, from the paging message;
1> extract private call parameters from the paging message if the UE ID in the message is consistent with
the ID of the UE;
2> report the paging information to the upper layer;
1> after the UE determines to receive a group call or private call according to the priority, on the RRC
layer:
2> if the UE receives a group call service:
3> if the message contains information about group resource configuration:
4> establish group context and configure group resources according to the information about
resource configuration for the group in the paging message;
5> use the G-RNTI to listen to the PDCCH and receive group signaling and service data
with information about service configuration in the group signaling message neglected;
3> if the message does not contain information about group resource configuration:
4> use the G-RNTI to listen to the PDCCH and receive group signaling messages;
5> upon receiving information about service configuration in the group signaling message,
23
XX/T XXXXX—XXXX
establish group context, configure group resources, and receive service data according to the
information about service configuration;
2> if the UE receives a private call service:
3> initiate RRC connection setup and joint the call as the called party.
If
the
UE,
according
to
the
configuration
information
contained
in
the
SystemInformationBlockTypeTrunking message, detects the PDCCH scrambled by the P-RNTI and receives
the TrunkingPaging message from the PDSCH indicated by the PDCCH during the trunking paging period
(TrunkingPaging), the UE shall:
1> if the Paging message contains a TrunkingPagingRecordList IE:
2> if the Trunk group ID (TGID) in the TrunkingPagingRecordList is the same as a TGID assigned by
an upper layer:
3> inform the upper layer of the TGID and pagingCause;
3> save the mapping between TGIDs and G-RNTIs, use the matching G-RNTI to listen to the
PDCCH based on the TGID specified by the upper layer, and try to receive signaling and
service data of the target group.
12.3.2 Setting up RRC Connection
12.3.2.1 Overview
UE
EUTRAN
RRCConnectionRequest
RRCConnectionSetup
RRCConnectionSetupComplete
Figure 9: RRC Connection Setup
Figure 9 shows the RRC connection setup procedure.
The RRC connection setup procedure follows regulations in section 5.3.3 in YD/T 2562.1-2013. In
addition, trunking UEs must comply with the following descriptions.
This procedure can be used to trigger trunking procedures by UEs.
24
XX/T XXXXX—XXXX
12.3.2.2 Transmitting the RRCConnectionRequest Message
The Trunking UE shall set IsTrunkingUser to 1 in RRCConnectionRequest messages:
12.3.3 Reconfiguring RRC Connection
12.3.3.1 Overview
UE
EUTRAN
RRCConnectionReconfiguration
RRCConnectionReconfigurationComplete
Figure 10: Reconfiguring RRC Connection
Figure 10 shows the RRC connection reconfiguration procedure.
The RRC connection reconfiguration procedure follows regulations in section 5.3.5.1 in YD/T
2562.1-2013. In addition, trunking UEs must comply with the following descriptions.
This procedure can be used for handing over a UE in the RRC_CONNECTED state in a group call (as
talking party or listening party) to a target cell, achieving the mobility of receiving inter-cell group calls.
12.3.3.2 Initializing
The E-UTRAN configures data for joining the group call as a listening party in the target cell for the UE
by sending an RRCConnectionReconfiguration message.
12.3.3.3 UE Receiving the RRCConnectionReconfiguration message containing
RRCConnectionReconfiguration-Trunking-IEs
After the UE in the RRC_CONNECTED state receives a message containing mobilityControlInfo and
RRCConnectionReconfiguration-Trunking-IEs, the UE shall:
——after
being
handed
over
to
the
target
cell,
based
on
RRCConnectionReconfiguration-Trunking-IEs contained in the message, configure the TPCCH and
TTCH and establish the downlink bearer for the group call.
12.3.4 Measurement Report
The measurement report procedure follows regulations in section 5.5.5 in YD/T 2562.1-2013. In addition,
trunking UEs must comply with the following descriptions.
25
XX/T XXXXX—XXXX
Figure 11: Measurement report
Figure 11 shows the measurement report procedure.
If a UE in the RRC_CONNECTED state sends a measurement report when it is joining a group call as the
talking party or listening party, the measurement report should contain MeasurementReport-Trunking-IEs, in
which, trunkingGroupID indicates the group call ID.
12.4 Others
12.4.1 Trunking Downlink Direct Transfer
12.4.1.1 Overview
UE
EUTRAN
DLTrunkingInformationTransfer
Figure 12: Trunking Downlink Direct Transfer
Figure 12 shows the trunking downlink direct transfer procedure.
The E-UTRAN can use this procedure to transmit NAS information to trunking UEs in the RRC_IDLE or
RRC_CONNECTED state. The DLTrunkingInformationTransfer message is transmitted on the TCCH.
12.4.1.2 Initializing
When NAS information needs to be transmitted, the E-UTRAN initializes the trunking downlink direct
transfer procedure. The E-UTRAN sends the DLTrunkingInformationTransfer message to initialize this
procedure.
12.4.1.3 UE Receiving the DLTrunkingInformationTransfer Message
Upon receiving the DLTrunkingInformationTransfer message, the UE shall:
1> if dedicatedInfoType is set to dedicatedInfoNAS:
26
XX/T XXXXX—XXXX
2> transmit dedicatedInfoNAS to the NAS upper layer.
12.4.2 Configuring a Group Call Traffic Channel
12.4.2.1 Overview
UE
EUTRAN
GroupCallConfig
Figure 13: Configuring a group call traffic channel
Figure 13 shows the procedure of configuring a group call traffic channel.
The GroupCallConfig message contains configuration information about the trunking group call downlink
bearer, which is used for establishing a trunking group call service.
12.4.2.2 Initializing
The E-UTRAN sends the GroupCallConfig message to initialize the procedure of configuring a group call
traffic channel.
12.4.2.3 UE Receiving the GroupCallConfig Message
Upon receiving the GroupCallConfig message, a UE in the RRC_IDLE or RRC_CONNECTED state shall:
——based on the parameters in the received message, configure the TTCH and establish the
downlink bearer for the group call.
12.4.3 Releasing a Group Call Traffic Channel
12.4.3.1 Overview
UE
EUTRAN
GroupCallRelease
Figure 14: Releasing a group call
Figure 14 shows the procedure of releasing a group call.
The GroupCallRelease message is used to notify the UE of releasing group call resources.
27
XX/T XXXXX—XXXX
12.4.3.2 Initializing
The E-UTRAN initializes the procedure of releasing a group call by sending the GroupCallRelease
message.
12.4.3.3 UE Receiving the GroupCallRelease Message
Upon receiving the GroupCallRelease message, the UE shall:
——release the TDRBs related to the group call, and stop listening to the TCCHs and TTCHs used
by the group call.
12.5 Protocol Data Unit, Format, and Parameter (Table and ASN.1)
12.5.1 RRC Message Components
– TPCCH-Message
TPCCH-Message is the aggregation of RRC messages and is transmitted from the E-UTRAN to UEs on the
logical TPCCH.
-- ASN1START
TPCCH-Message ::= SEQUENCE {
message
TPCCH-MessageType
}
TPCCH-MessageType ::= CHOICE {
c1
CHOICE {
trunkingPaging
TrunkingPaging
},
messageClassExtension SEQUENCE {}
}
-- ASN1STOP
– TCCH-Message
TCCH-Message is the aggregation of RRC messages and is transmitted from the E-UTRAN to UEs on the
downlink TCCH.
-- ASN1START
TCCH-Message ::= SEQUENCE {
28
XX/T XXXXX—XXXX
message
TCCH-MessageType
}
TCCH-MessageType ::= CHOICE {
c1
CHOICE {
dlTrunkingInformationTransfer
DLTrunkingInformationTransfer,
groupCallConfig
GroupCallConfig,
groupCallRelease
GroupCallRelease,
spare3 NULL,
spare2 NULL,
spare1 NULL
},
messageClassExtension SEQUENCE {}
}
-- ASN1STOP
12.5.2 RRC Message Definition
– SystemInformation
The SystemInformation message contains one or multiple system information blocks (SIBs).All the SIBs are
transmitted at the same interval.
SRB: N/A
RLC-SAP: TM
Logical channel: BCCH
Direction: from E-UTRAN to UEs
SystemInformation Message
-- ASN1START
SystemInformation ::=
criticalExtensions
SEQUENCE {
CHOICE {
systemInformation-r8
SystemInformation-r8-IEs,
criticalExtensionsFuture
SEQUENCE{}
}
}
SystemInformation-r8-IEs ::=
sib-TypeAndInfo
sib2
SEQUENCE {
SEQUENCE (SIZE (1..maxSIB)) OF CHOICE {
SystemInformationBlockType2,
29
XX/T XXXXX—XXXX
sib3
SystemInformationBlockType3,
sib4
SystemInformationBlockType4,
sib5
SystemInformationBlockType5,
sib6
SystemInformationBlockType6,
sib7
SystemInformationBlockType7,
sib8
SystemInformationBlockType8,
sib9
SystemInformationBlockType9,
sib10
SystemInformationBlockType10,
sib11
SystemInformationBlockType11,
...,
sib12-v920
SystemInformationBlockType12-r9,
sib13-v920
SystemInformationBlockType13-r9,
sib14
SEQUENCE{},
sib15
SEQUENCE{},
sib16
SEQUENCE{},
sib17
SEQUENCE{},
sib18
SEQUENCE{},
sib19
SEQUENCE{},
sib20
SEQUENCE{},
sib21
SEQUENCE{},
sib22
SEQUENCE{},
sib23
SEQUENCE{},
sib24
SEQUENCE{},
sib25
SEQUENCE{},
sib26
SEQUENCE{},
sib27
SEQUENCE{},
sib28
SEQUENCE{},
sib29
SEQUENCE{},
sib30
SEQUENCE{},
sib31
SEQUENCE{},
sib32
SystemInformationBlockTypeTrunking
},
nonCriticalExtension
SystemInformation-v8a0-IEs
OPTIONAL
}
SystemInformation-v8a0-IEs ::= SEQUENCE {
lateNonCriticalExtension
OCTET STRING OPTIONAL,
-- Need OP
nonCriticalExtension
SEQUENCE {}
-- Need OP
OPTIONAL
}
-- ASN1STOP
30
XX/T XXXXX—XXXX
– SystemInformationBlockType1
When a UE is allowed to work in a cell, the SystemInformationBlockType1 message contains the cell
information and defines scheduling of other system information.
SRB: N/A
RLC-SAP: TM
Logical channel: BCCH
Direction: E-UTRAN to UEs
SystemInformationBlockType1 Message
-- ASN1START
SystemInformationBlockType1 ::=
cellAccessRelatedInfo
SEQUENCE {
SEQUENCE {
plmn-IdentityList
PLMN-IdentityList,
trackingAreaCode
TrackingAreaCode,
cellIdentity
CellIdentity,
cellBarred
ENUMERATED {barred, notBarred},
intraFreqReselection
ENUMERATED {allowed, notAllowed},
csg-Indication
BOOLEAN,
csg-Identity
CSG-Identity
OPTIONAL
-- Need OR
OPTIONAL
-- Need OP
},
cellSelectionInfo
SEQUENCE {
q-RxLevMin
Q-RxLevMin,
q-RxLevMinOffset
INTEGER (1..8)
},
p-Max
P-Max
freqBandIndicator
INTEGER (1..64),
schedulingInfoList
SchedulingInfoList,
tdd-Config
TDD-Config
si-WindowLength
ENUMERATED {
OPTIONAL,
-- Need
OP
OPTIONAL,
-- Cond TDD
ms1, ms2, ms5, ms10, ms15, ms20,
ms40},
systemInfoValueTag
INTEGER (0..31),
nonCriticalExtension
SystemInformationBlockType1-v890-IEs
OPTIONAL
}
SystemInformationBlockType1-v890-IEs::= SEQUENCE {
lateNonCriticalExtension
OCTET STRING
OPTIONAL,
-- Need OP
31
XX/T XXXXX—XXXX
nonCriticalExtension
SystemInformationBlockType1-v920-IEs
OPTIONAL
}
SystemInformationBlockType1-v920-IEs ::=
SEQUENCE {
ims-EmergencySupport-r9
ENUMERATED {true}
OPTIONAL,
-- Need
cellSelectionInfo-v920
CellSelectionInfo-v920
OPTIONAL,
-- Need
nonCriticalExtension
SEQUENCE {}
OPTIONAL
-- Need
OR
OP
OP
}
PLMN-IdentityList ::=
SEQUENCE (SIZE (1..6)) OF PLMN-IdentityInfo
PLMN-IdentityInfo ::=
SEQUENCE {
plmn-Identity
PLMN-Identity,
cellReservedForOperatorUse
ENUMERATED {reserved, notReserved}
}
SchedulingInfoList ::= SEQUENCE (SIZE (1..maxSI-Message)) OF SchedulingInfo
SchedulingInfo ::=
SEQUENCE {
si-Periodicity
ENUMERATED {
rf8, rf16, rf32, rf64, rf128, rf256, rf512},
sib-MappingInfo
SIB-MappingInfo
}
SIB-MappingInfo ::= SEQUENCE (SIZE (0..maxSIB-1)) OF SIB-Type
SIB-Type ::=
ENUMERATED {
sibType3, sibType4, sibType5, sibType6,
sibType7, sibType8, sibType9, sibType10,
sibType11, sibType12-v920, sibType13-v920, spare5,
spare4, spare3, spare2, spare1, ... , spare18, spare17,
spare16, spare15, spare14, spare13, spare12, spare11,
spare10, spare9, spare8, spare7, spare6,
sibTypeTrunking}
CellSelectionInfo-v920 ::=
SEQUENCE {
q-QualMin-r9
Q-QualMin-r9,
q-QualMinOffset-r9
INTEGER (1..8)
OPTIONAL
-- Need OP
}
32
XX/T XXXXX—XXXX
-- ASN1STOP
– DLTrunkingInformationTransfer
The DLTrunkingInformationTransfer message is used to implement downlink transmission of trunking-related
NAS information.
SRB: TSRB
RLC-SAP: UM
Logical channel: TCCH
Direction: E-UTRAN to UEs
DLTrunkingInformationTransfer Message
-- ASN1START
DLTrunkingInformationTransfer ::=
SEQUENCE {
rrc-TransactionIdentifier
RRC-TransactionIdentifier,
criticalExtensions
CHOICE {
c1
CHOICE {
dlTrunkingInformationTransfer-r8
DLTrunkingInformationTransfer-r8-IEs,
spare3 NULL, spare2 NULL, spare1 NULL
},
criticalExtensionsFuture
SEQUENCE {}
DLTrunkingInformationTransfer-r8-IEs ::=
SEQUENCE {
}
}
dedicatedInfoNAS
DedicatedInfoNAS,
nonCriticalExtension
DLTrunkingInformationTransfer-v8a0-IEs
OPTIONAL
}
DLTrunkingInformationTransfer-v8a0-IEs ::= SEQUENCE {
lateNonCriticalExtension
OCTET STRING
OPTIONAL,
-- Need OP
nonCriticalExtension
SEQUENCE {}
OPTIONAL
-- Need OP
}
-- ASN1STOP
33
XX/T XXXXX—XXXX
– TrunkingPaging
The TrunkingPaging message is used to notify UEs under a cell of the information about group calls and
private calls initiated under the cell.
SRB: N/A
RLC-SAP: TM
Logical channel: TPCCH
Direction: E-UTRAN to UEs
TrunkingPaging Message
-- ASN1START
TrunkingPaging ::=
SEQUENCE {
GroupPaging
GroupPagingRecordList
OPTIONAL, -- Need ON
UePaging
UePagingRecordList
OPTIONAL, -- Need ON
TrunkingSystemInformationModification
nonCriticalExtension
ENUMERATED {true}
SEQUENCE {}
OPTIONAL,
-- Need ON
OPTIONAL
}
GroupPagingRecordList::=
UePagingRecordList::=
SEQUENCE (SIZE (1..maxGroupPageRec)) OF GroupPagingRecord
SEQUENCE (SIZE (1..maxUEPageRec)) OF UePagingRecord
GroupPagingRecord::=
SEQUENCE {
trunkingGroupID
TGID,
g-Rnti
BIT STRING (SIZE (16)),
semiPersistSchedG-RNTI
BIT STRING (SIZE (16))
callPriority
BIT STRING (SIZE (8)),
dedicatedInfoNAS
DedicatedInfoNAS
groupResourceIndexList
GroupResourceIndexList OPTIONAL,
groupShortMsg-Indication
ENUMERATED {true}
callSeqNumber
INTEGER(0..7)
OPTIONAL,
-- Need ON
OPTIONAL, -- Need ON
-- Need ON
OPTIONAL,
OPTIONAL
}
GroupResourceIndexList
::=
GroupResourceIndexItem ::=
SEQUENCE (SIZE (1..maxGroupResourceIndex)) OF GroupResourceIndexItem
SEQUENCE {
groupResourceIndex
INTEGER (0..maxGroupResourceConfig-1),
dedicatedInfoNAS
DedicatedInfoNAS
OPTIONAL, -- Need ON
...
}
34
XX/T XXXXX—XXXX
UePagingRecord::=
SEQUENCE {
ue-Identity
PagingUE-Identity,
callPriority
BIT STRING (SIZE (8))
}
TGID ::= BIT STRING (SIZE (44))
-- ASN1STOP
TrunkingPaging Field
GroupPagingRecord
Describes paging records of a trunking group call.
UePagingRecord
Describes paging records of a trunking private call.
callPriority (BIT STRING (SIZE (8))
Describes priorities of trunking group calls or private calls. Principles for specifying priorities are as follows:
0: reversed; 1: the highest priority (emergency calls); 255: the lowest priority
groupResourceIndexList
Describes the resource index.
groupShortMsg-Indication
Indicates transmission of broadcast short messages when being set to TRUE. The broadcast short message function is optional for terminals
and systems.
trunkingGroupID
Indicates a trunking group ID. BIT STRING (SIZE (44)) consists of 11 decimal digits. Every four bits starting from the most significant bit
(the leftmost) indicate a decimal BCD code. The decimal number corresponding to the four bits starting from the most significant bit is the most
significant bit of the trunking group ID.
The coding structure of trunkingGroupID is not specially required.
callSeqNumber
When a group call is set up or released, the value of callSeqNumber does not change. When a group call is set up next time, the value of
callSeqNumber is mod 8 (callSeqNumber + 1).
The call sequence number function is optional for terminals and systems.
35
XX/T XXXXX—XXXX
– Paging (For Trunking)
To enhance the Paging message, TrunkingPagingRecord is added for implementing paging of UEs
involved in one or multiple groups.
SRB: N/A
RLC-SAP: TM
Logical channel: PCCH
Direction: E-UTRAN to UE
Paging Message
-- ASN1START
Paging ::=
SEQUENCE {
pagingRecordList
PagingRecordList
OPTIONAL,
-- Need ON
systemInfoModification
ENUMERATED {true}
OPTIONAL,
-- Need ON
etws-Indication
ENUMERATED {true}
OPTIONAL,
-- Need ON
nonCriticalExtension
Paging-v890-IEs
OPTIONAL
}
Paging-v890-IEs ::=
SEQUENCE {
lateR8NonCriticalExtension
OCTET STRING
OPTIONAL,
nonCriticalExtension
Paging-v920-IEs
OPTIONAL
-- Need OP
}
Paging-v920-IEs ::=
SEQUENCE {
cmas-Indication-r9
ENUMERATED {true}
OPTIONAL,
nonCriticalExtension
Paging-v920-Trunking-IEs
OPTIONAL
-- Need ON
}
Paging-v920-Trunking-IEs ::=
trunkingPagingRecordList
nonCriticalExtension
SEQUENCE {
TrunkingPagingRecordList
SEQUENCE {}
OPTIONAL,
-- Need ON
OPTIONAL
-- Need OP
}
PagingRecordList ::=
SEQUENCE (SIZE (1..maxPageRec)) OF PagingRecord
PagingRecord ::=
SEQUENCE {
ue-Identity
PagingUE-Identity,
cn-Domain
ENUMERATED
{ps, cs},
...
36
XX/T XXXXX—XXXX
}
PagingUE-Identity ::=
CHOICE {
s-TMSI
S-TMSI,
imsi
IMSI,
...
}
IMSI ::=
SEQUENCE (SIZE (6..21)) OF IMSI-Digit
IMSI-Digit ::=
INTEGER (0..9)
TrunkingPagingRecordList::=
SEQUENCE (SIZE (1..maxTrunkingCallRec)) OF
TrunkingPagingRecord
TrunkingPagingRecord::=
SEQUENCE{
trukingGroupID
g-RNTI
TGID,
G-RNTI,
pagingCause
ENUMERATED {Emergency,spare7, spare6, spare5, spare4,spare3,
spare2, spare1},
}
TGID ::= BIT STRING (SIZE (44))
-- ASN1STOP
Paging Field
g-RNTI
Indicates RNTI for scheduling trunking group calls.
pagingCause
Indicates causes for special paging. Only one type of cause, emergency call, is specified at present.
– RRCConnectionRequest
The RRCConnectionRequest message is used to request establishment of an RRC connection.
SRB: SRB0
RLC-SAP: TM
Logical channel: CCCH
Direction: UE to E-UTRAN
RRCConnectionRequest Message
37
XX/T XXXXX—XXXX
-- ASN1START
RRCConnectionRequest ::=
criticalExtensions
SEQUENCE {
CHOICE {
rrcConnectionRequest-r8
RRCConnectionRequest-r8-IEs,
criticalExtensionsFuture
SEQUENCE {}
}
}
RRCConnectionRequest-r8-IEs ::=
SEQUENCE {
ue-Identity
InitialUE-Identity,
establishmentCause
EstablishmentCause,
IsTrunkingUser
BIT STRING (SIZE (1))
}
InitialUE-Identity ::=
CHOICE {
s-TMSI
S-TMSI,
randomValue
BIT STRING (SIZE (40))
}
EstablishmentCause ::=
ENUMERATED {
emergency, highPriorityAccess, mt-Access, mo-Signalling,
mo-Data, spare3, spare2, spare1}
-- ASN1STOP
RRCConnectionRequest Field
IsTrunkingUser
Indicates whether the user is a trunking user, for trunking user “IsTrunkingUser” should be set to 1, for other
user“IsTrunkingUser” should be set to 0.
– GroupCallConfig
The GroupCallConfig message is used to configure the trunking traffic channel (TTCH).
38
XX/T XXXXX—XXXX
SRB: TSRB
RLC-SAP: UM
Logical channel: TCCH
Direction: E-UTRAN to UEs
GroupCallConfig Message
-- ASN1START
GroupCallConfig ::=
SEQUENCE {
GroupCallConfigInfo
GroupCallConfig-IEs,
dedicatedInfoNAS
DedicatedInfoNAS
nonCriticalExtension
SEQUENCE {}
OPTIONAL, -- Need ON
OPTIONAL –- Need OP
}
GroupCallConfig-IEs ::=
SEQUENCE {
configSeqNumber
BIT STRING (SIZE (3)) OPTIONAL,
tradioResourceConfigDedicated
TRadioResourceConfigDedicated
nonCriticalExtension
SEQUENCE {}
OPTIONAL
OPTIONAL,
-- Need OP
}
TRadioResourceConfigDedicated ::=
SEQUENCE {
tdrb-ToAddList
TDRB-ToAddList
OPTIONAL, -Need ON
tdrb-ToReleaseList
DRB-ToReleaseList
tgsps-Config
TGSPS-Config
tgphysicalConfigDedicated
TGPhysicalConfigDedicated
OPTIONAL,
OPTIONAL,
-- Need ON
-- Need ON
OPTIONAL
-- Need ON
}
TDRB-ToAddList ::=
SEQUENCE (SIZE (1..maxTDRB)) OF TDRB-ToAdd
TDRB-ToAdd ::=
SEQUENCE {
trunking-eps-BearerIdentity
tdrb-Config
INTEGER (0..15),
CHOICE {
groupResourceIndex
INTEGER (0..maxResourceConfig-1),
groupResourceExplicitConfig
SEQUENCE {
tdrb-Identity
INTEGER (1..32),
pdcp-Config
PDCP-Config,
rlc-Config
RLC-Config,
logicalChannelIdentity
INTEGER (12..21) ,
...
}
}
dedicatedInfoNAS
DedicatedInfoNAS
OPTIONAL, -- Need ON
}
39
XX/T XXXXX—XXXX
TGSPS-Config ::=
SEQUENCE{
tgsps-RNTI
C-RNTI,
semiPersistSchedIntervalDL
ENUMERATED {
sf10, sf20, sf30, sf40, sf60, sf80,
sf120, sf160, sf320, sf640, spare6,
spare5, spare4, spare3, spare2,
spare1},
tgsps-Setup
SEQUENCE {
offset
INTEGER (0..639),
mcs
INTEGER(0..28),
localizedDistributedVRBassignmentflag
riv
ENUMERATED{t_lvrb,t_dvrb},
INTEGER(0..65535),
...
}
OPTIONAL,
-- Need OR
...
}
TGPhysicalConfigDedicated ::=
SEQUENCE {
pdsch-ConfigDedicated
PDSCH-ConfigDedicated
OPTIONAL,
-- Need ON
...
}
-- ASN1STOP
GroupCallConfig Field
radioResourceConfigDedicated
Indicates the TTCH resource configuration information.
configSeqNumber
When the value of this parameter does not change, UEs consider that configurations involved in GroupCallConfig do not
change.
tgsps-Setup
Indicates semi-persistent scheduling resources. This parameter is optional for UEs.
If tdrb-Identity, pdcp-Config, rlc-Config, and logicalChannelIdentity are unavailable, a UE use default
values configured for the TTCH. The default values configured for the TTCH are listed in the following table.
TTCH default configurations
TTCH
Parameter
Value
Description
40
XX/T XXXXX—XXXX
TDRB ID
Varying
with
groupResourceIndex
TTCH Parameter
Value
LCID
12
TDRB ID
12
LCID
13
TDRB ID
13
LCID
14
TDRB ID
14
LCID
15
TDRB ID
15
0
Logical
1
Channel
ID
2
3
PDCP SN Size
RLC mode
RLC SN Size
12 bits
Length of PDCP SN
UM
RLC UM mode
10 bits
Length of RLC Data PDU SN
– GroupCallRelease
The GroupCallRelease message is used for releasing group call resources.
SRB: TSRB
RLC-SAP: UM
Logical channel: TCCH
Direction: E-UTRAN to UEs
GroupCallRelease Message
-- ASN1START
GroupCallRelease::=
SEQUENCE {
dedicatedInfoNAS
nonCriticalExtension
DedicatedInfoNAS
OPTIONAL, -- Need ON
SEQUENCE {}
}
-- ASN1STOP
– MeasurementReport
The MeasurementReport message provides measurement results.
41
XX/T XXXXX—XXXX
SRB: SRB1
RLC-SAP: AM
Logical channel: DCCH
Direction: UE to E-UTRAN
MeasurementReport Message
-- ASN1START
MeasurementReport ::=
SEQUENCE {
criticalExtensions
CHOICE {
c1
CHOICE{
measurementReport-r8
MeasurementReport-r8-IEs,
spare7 NULL,
spare6 NULL, spare5 NULL, spare4 NULL,
spare3 NULL, spare2 NULL, spare1 NULL
},
criticalExtensionsFuture
SEQUENCE {}
}
}
MeasurementReport-r8-IEs ::=
SEQUENCE {
measResults
MeasResults,
nonCriticalExtension
MeasurementReport-v8a0-IEs
OPTIONAL
}
MeasurementReport-v8a0-IEs ::= SEQUENCE {
lateNonCriticalExtension
OCTET STRING (CONTAINING MeasurementReport-Trunking-IEs)
OPTIONAL,
nonCriticalExtension
SEQUENCE {}
OPTIONAL
}
MeasurementReport-Trunking-IEs ::= SEQUENCE {
trunkingGroupID
nonCriticalExtension
TGID
SEQUENCE {}
OPTIONAL,
OPTIONAL
-- Need OP
-- Need OP
}
-- ASN1STOP
42
XX/T XXXXX—XXXX
– RRCConnectionReconfiguration
The RRCConnectionReconfiguration message is used for trunking group call configuration of the target call
during the handover in RRC_CONNECTED mode.
SRB: SRB1
RLC-SAP: AM
Logical channel: DCCH
Direction: E-UTRAN to UE
RRCConnectionReconfiguration Message
-- ASN1START
RRCConnectionReconfiguration ::=
SEQUENCE {
rrc-TransactionIdentifier
RRC-TransactionIdentifier,
criticalExtensions
CHOICE {
c1
CHOICE{
rrcConnectionReconfiguration-r8
RRCConnectionReconfiguration-r8-IEs,
spare7 NULL,
spare6 NULL, spare5 NULL, spare4 NULL,
spare3 NULL, spare2 NULL, spare1 NULL
},
criticalExtensionsFuture
SEQUENCE {}
}
}
RRCConnectionReconfiguration-r8-IEs ::= SEQUENCE {
measConfig
MeasConfig
OPTIONAL,
-- Need ON
mobilityControlInfo
MobilityControlInfo
OPTIONAL,
-- Cond HO
dedicatedInfoNASList
SEQUENCE (SIZE(1..maxDRB)) OF
OPTIONAL,
-- Cond nonHO
DedicatedInfoNAS
radioResourceConfigDedicated
RadioResourceConfigDedicated
OPTIONAL, -- Cond
securityConfigHO
SecurityConfigHO
OPTIONAL,
nonCriticalExtension
RRCConnectionReconfiguration-v890-IEs
HO-toEUTRA
-- Cond HO
OPTIONAL
}
RRCConnectionReconfiguration-v890-IEs ::= SEQUENCE {
43
XX/T XXXXX—XXXX
lateNonCriticalExtension
OCTET STRING (CONTAINING RRCConnectionReconfiguration-
Trunking-IEs)
OPTIONAL,
nonCriticalExtension
-- Cond HO
RRCConnectionReconfiguration-v920-IEs
OPTIONAL
}
RRCConnectionReconfiguration-v920-IEs ::= SEQUENCE {
otherConfig-r9
OtherConfig-r9
OPTIONAL,
-- Need ON
fullConfig-r9
ENUMERATED {true}
OPTIONAL,
-- Cond
SEQUENCE {}
OPTIONAL
-- Need OP
HO-Reestab
nonCriticalExtension
}
SecurityConfigHO ::=
SEQUENCE {
handoverType
CHOICE {
intraLTE
SEQUENCE {
securityAlgorithmConfig
SecurityAlgorithmConfig
keyChangeIndicator
BOOLEAN,
nextHopChainingCount
NextHopChainingCount
OPTIONAL,
-- Cond
fullConfig
},
interRAT
SEQUENCE {
securityAlgorithmConfig
SecurityAlgorithmConfig,
nas-SecurityParamToEUTRA
OCTET STRING (SIZE(6))
}
},
...
}
RRCConnectionReconfiguration-Trunking-IEs ::= SEQUENCE {
tPCCH-Config
TPCCH-Config,
trunkingGroupID
TGID
OPTIONAL,
-- Need ON
g-Rnti
BIT STRING (SIZE (16))
OPTIONAL,
-- Need ON
p-t
ENUMERATED {dB-6, dB-4dot77, dB-3, dB-1dot77, dB0, dB1, dB2, dB3} OPTIONAL, -- Need OP
TrunkingReconfig
CHOICE {
GroupCallConfigInfo
GroupCallConfig-IEs,
trunkingGroupInfo
TrunkingReconfigGroupInfo,
...
} OPTIONAL,
nonCriticalExtension
SEQUENCE {}
OPTIONAL
-- Need OP
OPTIONAL,
-- Need ON
}
TrunkingReconfigGroupInfo
semiPersistSchedG-RNTI
::= SEQUENCE {
BIT STRING (SIZE (16))
44
XX/T XXXXX—XXXX
groupResourceIndexList
GroupResourceIndexList
OPTIONAL
-- Need ON
}
-- ASN1STOP
RRCConnectionReconfiguration Field
TPCCH-Config
Describes TPCCH configuration parameters.
p-t: Indicates p-a configuration of a trunking group call.
When p-t is not involved, p-a configured in GroupCallConfig is used. In this case, the TCCH adopts QPSK modulation.
eps-BearerIdentity
The eps-BearerIdentity for trunking-specific bearing (private call and group call users) ranges from 12 to 15, and that for
other services ranges from 5 to 11.
drb-Identity
Indicates DRB ID of trunking-specific bearing (private call and group call users). The value of this parameter ranges from
17 to 32, and that for other services ranges from 1 to 16.
12.5.3 RRC Information Elements
– SystemInformationBlockTypeTrunking
The SystemInformationBlockTypeTrunking message contains trunking-related system information.
SystemInformationBlockTypeTrunking information element
-- ASN1START
SystemInformationBlockTypeTrunking ::=
SEQUENCE {
TPCCH-Config
TPCCH-Config,
CellFailureInd
ENUMERATED {true}
OPTIONAL,
-- Need OR
p-t
ENUMERATED {dB-6, dB-4dot77, dB-3, dB-1dot77, dB0, dB1, dB2, dB3} OPTIONAL, -- Need OP
TrunkingBsrInd
ENUMERATED {true}
OPTIONAL,
-- Need OR
nonCriticalExtension
SEQUENCE {}
OPTIONAL
-- Need OP
}
45
XX/T XXXXX—XXXX
-- ASN1STOP
SystemInformationBlockTypeTrunking Field
TPCCH-Config
Describes TPCCH configuration parameters.
CellFailureInd
Indicates whether a cell is in fault weakening mode.
p-t: Indicates p-a configuration of a trunking group call.
When broadcasting p-t is not involved in SystemInformationBlockTypeTrunking, p-a configured in Groupcallconfig is used.
In this case, the TCCH adopts QPSK modulation.
TrunkingBsrInd:
When an eNodeB supports trunking BSR, this parameter is set to true. If a UE does not supports trunking BSR, the UE can
ignore the IE.
– TPCCH -Config
IE TPCCH-Config describes TPCCH configuration parameters.
TPCCH –Config Information Element
-- ASN1START
TPCCH-Config ::=
SEQUENCE {
pagingCycle
ENUMERATED {rf2,rf4, rf8, rf16, rf32, rf64, rf128},
frameNumber
INTEGER {0..127},
subframeNumber
INTEGER {0..9},
}
-- ASN1STOP
46
XX/T XXXXX—XXXX
TPCCH –Config Field
pagingCycle
Indicates the TPCCH paging period. The parameter value rf32 corresponds to 32 radio frames, and rf64 corresponds to 64
radio frames. The default value is rf16.
frameNumber
Indicates the sequence number of a radio frame on which a message is transmitted on the TPCCH in a paging period. The
default value is 0.
A UE can use the following formula to obtain PF:
PF mod pagingCycle = frameNumber
subframeNumber
Indicates the sequence number of a PF sub-frame on which a message is transmitted on the TPCCH in a paging period. The
default value is 1. A UE can use the following formula to obtain PO:
PO = subframeNumber
– LogicalChannelConfig
IE LogicalChannelConfig is used to configure logical channel parameters.
LogicalChannelConfig Information Elements
-- ASN1START
LogicalChannelConfig ::=
ul-SpecificParameters
SEQUENCE {
SEQUENCE {
priority
INTEGER (1..16),
prioritisedBitRate
ENUMERATED {
kBps0, kBps8, kBps16, kBps32, kBps64, kBps128,
kBps256, infinity, kBps512-v1020, kBps1024-v1020,
kBps2048-v1020, spare5, spare4, spare3, spare2,
spare1},
bucketSizeDuration
ENUMERATED {
ms50, ms100, ms150, ms300, ms500, ms1000, spare2,
spare1},
logicalChannelGroup
}
INTEGER (0..3)
OPTIONAL
OPTIONAL,
-- Need OR
-- Cond UL
...,
[[
logicalChannelSR-Mask-r9
ENUMERATED {setup}
OPTIONAL
-- Cond SRmask
]]
47
XX/T XXXXX—XXXX
}
-- ASN1STOP
LogicalChannelConfig Field
logicalChannelGroup
When TrunkingBSRInd in the SystemInformationBlockTypeTrunking message is set to true:

If a UE supports reporting of BSR by BSR MAC CE and the DRB ID ranges from 17 to 32, trunking BSR MAC
CE reports BSR. The logical channel maps the logical channel group of the trunking BSR. When the DRB ID ranges from 1
to 16, LTE BSR MAC CE reports BSR. The logical channel maps the logical channel group of the LTE BSR.

If the UE does not support reporting of BSR by BSR MAC CE, the UE uses the LTE BSR MAC CE to report
BSR. The logical channel maps the logical channel group of the LTE BSR.
If TrunkingBSRInd is unavailable in the SystemInformationBlockTypeTrunking message, the UE uses the LTE BSR MAC
CE to report BSR. The logical channel maps the logical channel group of the LTE BSR.
12.5.4 RRC Multiplicity and Type Constraint Values
– RRC multiplicity and type constraint values
-- ASN1START
maxGroupPageRec
INTEGER ::= 16
maxUEPageRec
INTEGER ::= 16
maxGroupResourceConfig-1
maxGroupResourceIndex
INTEGER ::= 15
INTEGER ::= 8
maxTDRB
INTEGER ::= 11
-- Maximum number of Data Radio Bearers
-- ASN1STOP
12.6 Variable and Constant
TCCH default configuration
Name
Value
LogicalChannelIdentity
01011
TSRB Identity
0
PDCP
pdcp-SN-Size
Len5bits
RLC
UM-Uni-Directional-DL
48
XX/T XXXXX—XXXX
Name
Value
LogicalChannelIdentity
01011
TSRB Identity
0
Sn-FieldLength
Size5
t-Reordering
0
TTCH configuration index
TTCH-Config-0
Name
Value
LogicalChannelIdentity
12
trunking-eps-BearerIdentity
15
TDRB ID
32
Semantics description
Ver
Semantics description
Ver
Semantics description
Ver
PDCP
pdcp-SN-Size
len7bits
headerCompression
> notUsed
NULL
RLC
UM-Uni-DirectionalDL
Sn-FieldLength
size5
TTCH-Config-1
Name
Value
LogicalChannelIdentity
12
trunking-eps-BearerIdentity
15
TDRB ID
32
PDCP
pdcp-SN-Size
Len12bits
headerCompression
> notUsed
NULL
RLC
UM-Uni-DirectionalDL
Sn-FieldLength
Size10
TTCH-Config-2
Name
Value
LogicalChannelIdentity
13
trunking-eps-BearerIdentity
14
TDRB ID
31
PDCP
pdcp-SN-Size
Len12bits
49
XX/T XXXXX—XXXX
Name
Value
LogicalChannelIdentity
13
trunking-eps-BearerIdentity
14
TDRB ID
31
Semantics description
Ver
Value
Semantics description
Ver
Value
Semantics description
Ver
headerCompression
> notUsed
NULL
RLC
UM-Uni-DirectionalDL
Sn-FieldLength
Size10
t-Reordering
0
SPS-Config-0
Name
SPS
semiPersistSchedIntervalDL
sf20
SPS-Config-1
Name
SPS
semiPersistSchedIntervalDL
sf30
Resource
Index
SPS
TTCH
0
TTCH-Conifg-0
SPS-Config-0
1
TTCH-Conifg-1
SPS-Config-0
2
TTCH-Conifg-1
SPS-Config-1
3
TTCH-Conifg-2
None
…
15
13 Layer 3 Part 2: Trunking Services of UEs in Idle Mode
13.1 UEs In Idle Mode Receiving Data from the Trunking Control Channel and Traffic
Channel
In addition to operations defined in 3GPP protocols, UEs in the RRC_IDLE state should also support the
following operations:
 If UEs have not started trunking services, the UEs:
 Listen to the TPCCH based on the trunking PO configured for the RRC.
50
XX/T XXXXX—XXXX
 Set up group resources and bearer and receive data from the TCCH and TTCH if the
group paging message contains the information about the groups to be listened to.
 Trigger establishment of RRC connection for bearing private calls if the group paging
message contains information about the private call of the UE.
 If UEs have started trunking services, the UEs:
 Release resources and bearer of the group if receiving the release indication for the
listened group services from the TCCH.
 Listen to the TPCCH based on the trunking PO configured for the RRC.
13.2 Trunking Paging DRX
UEs can reduce power consumption by applying discontinuous reception in idle mode. Trunking group
call paging provides the same paging occasion (PO) for all UEs involved in the group. Trunking private calls
and trunking group calls apply the same PO.
PO is determined by the following parameters configured in SystemInformationBlockTypeTrunking:
 agingCycle: TPCCH paging period. The period equals the number of radio frames.
 frameNumber: Sequence number of a radio frame on which a message is transmitted on the TPCCH
in a paging period. The default value is 0. A UE can use the following formula to obtain PF:
PF mod pagingCycle = frameNumber
 subframeNumber: Sequence number of a PF sub-frame on which a message is transmitted on the
TPCCH in a paging period. The default value is 0. A UE can use the following formula to obtain PO:
PO = subframeNumber
51