7 Traffic volume monitoring
25.3033GPPInterlayer procedures in Connected ModeRelease 17TS
An algorithm will be defined for the UE to trigger a message to the NW based on transmitter buffer status.
Figure 48 illustrates the example of message sequence of traffic volume monitoring procedure. RRC in UE gets the parameters necessary for traffic volume measurement from Measurement Control message or System information message sent by RRC in UTRAN. RRC in UE passes the MAC the parameters for traffic volume measurement with the CMAC-Measurement-REQ. Meanwhile, RLC passes the data to MAC with buffer status. There are two ways MAC indicates the traffic volume measurement report to RRC, periodic and event-triggered. If it is periodic report, the MAC reports the measurement result to RRC periodically. If it is event-triggered, MAC in UE reports the measurement result to RRC when the result is beyond the specified threshold value. After that, based on the measurement report from MAC and reporting criteria received from UTRAN, RRC makes a decision whether it should send Measurement Report Message to UTRAN. When RRC in UTRAN receives the Measurement Report Message, it takes a proper action based on the measurement report from UE. It can be bearer reconfiguration, transport channel reconfiguration, physical channel reconfiguration or transport channel combination control procedure. The report mode, periodic and event-triggered, can be used exclusively, or simultaneously as shown in figure 1.
Figure 48: Traffic Volume Measurement Report Procedure
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
06/1999 |
RP-04 |
RP-99310 |
– |
Approved at TSG-RAN #4 placed under Change Control |
3.0.0 |
||
|
10/1999 |
RP-05 |
RP-99462 |
001 |
RRC connection establishment procedure |
3.1.0 |
||
|
RP-05 |
RP-99462 |
002 |
1 |
RRC Connection release procedure |
3.1.0 |
||
|
RP-05 |
RP-99462 |
003 |
Cell update and URA update procedures |
3.1.0 |
|||
|
RP-05 |
RP-99462 |
004 |
Removal of FFS in DSCH transmission example |
3.1.0 |
|||
|
RP-05 |
RP-99462 |
005 |
Incorporation of DSCH transmission with one TFCI |
3.1.0 |
|||
|
RP-05 |
RP-99462 |
006 |
RRC Traffic Volume Monitoring Procedure |
3.1.0 |
|||
|
RP-05 |
RP-99462 |
007 |
Transfer and update of system information |
3.1.0 |
|||
|
RP-05 |
RP-99462 |
008 |
UE controlled AMR mode adaptation |
3.1.0 |
|||
|
RP-05 |
RP-99462 |
009 |
Model of RACH procedures |
3.1.0 |
|||
|
RP-05 |
RP-99462 |
012 |
USCH/DSCH data transfer for TDD |
3.1.0 |
|||
|
RP-05 |
RP-99462 |
013 |
Removal of UE State Description |
3.1.0 |
|||
|
RP-05 |
RP-99462 |
014 |
Editorial renaming request |
3.1.0 |
|||
|
RP-05 |
RP-99462 |
015 |
Release version for Asymmetric transport channel reconfiguration procedure |
3.1.0 |
|||
|
RP-05 |
RP-99462 |
016 |
Example message sequence for RACH transmissions in TDD mode |
3.0.0 |
|||
|
12/1999 |
RP-06 |
RP-99629 |
017 |
1 |
Support of shared channel operation in TDD and alignment to Mac-c/sh merge |
3.2.0 |
|
|
RP-06 |
RP-99628 |
018 |
2 |
Corrections to RRC State Names |
3.2.0 |
||
|
RP-06 |
RP-99628 |
021 |
Editorial issues |
3.2.0 |
|||
|
03/2000 |
RP-07 |
RP-000036 |
022 |
4 |
CPCH start of message indication |
3.3.0 |
|
|
RP-07 |
RP-000036 |
023 |
Correction to Transport Format Combination Control procedure |
3.3.0 |
|||
|
RP-07 |
RP-000036 |
025 |
1 |
CPCH Emergency Stop sequence |
3.3.0 |
||
|
RP-07 |
RP-000036 |
026 |
1 |
Variable Rate Packet Transmission for uplink DCH |
3.3.0 |
||
|
RP-07 |
RP-000036 |
027 |
Random access transmission sequence |
3.3.0 |
|||
|
06/2000 |
RP-08 |
RP-000216 |
029 |
Corrections to L2 link management and radio link setup in interlayer message sequence charts |
3.4.0 |
||
|
RP-08 |
RP-000216 |
030 |
Alignment of FDD downlink shared channel descriptions with 25.331 |
3.4.0 |
|||
|
RP-08 |
RP-000216 |
031 |
1 |
End of CPCH transmission |
3.4.0 |
||
|
RP-08 |
RP-000216 |
033 |
Out-of-synch corrections |
3.4.0 |
|||
|
RP-08 |
RP-000216 |
034 |
Traffic Volume Monitoring |
3.4.0 |
|||
|
09/2000 |
RP-09 |
RP-000354 |
035 |
2 |
SRNS relocation |
3.5.0 |
|
|
RP-09 |
RP-000354 |
037 |
Variable Rate Transmission |
3.5.0 |
|||
|
12/2000 |
RP-10 |
RP-000564 |
038 |
1 |
Corrections to SRNS Relocation |
3.6.0 |
|
|
RP-10 |
RP-000564 |
040 |
Correction to Relocation text |
3.6.0 |
|||
|
03/2001 |
RP-11 |
RP-010021 |
041 |
1 |
Text corrections |
3.7.0 |
|
|
RP-11 |
RP-010021 |
042 |
SRNS relocation |
3.7.0 |
|||
|
RP-11 |
RP-010021 |
044 |
Clean-up |
3.7.0 |
|||
|
RP-11 |
RP-010037 |
043 |
1.28Mcps TDD |
4.0.0 |
|||
|
06/2001 |
RP-12 |
RP-010304 |
046 |
Corrections to procedure examples |
4.1.0 |
||
|
09/2001 |
RP-13 |
RP-010538 |
051 |
SRNS relocation and header compression protocol |
4.2.0 |
||
|
RP-13 |
RP-010538 |
053 |
Alignment on active set update |
4.2.0 |
|||
|
RP-13 |
RP-010538 |
057 |
Proposed correction to SRNS relocation procedure |
4.2.0 |
|||
|
12/2001 |
RP-14 |
RP-010755 |
059 |
Correction to RNTI in cell-update and URA-update procedures |
4.3.0 |
||
|
RP-14 |
RP-010755 |
061 |
HFN transfer between network nodes in SRNS relocation |
4.3.0 |
|||
|
03/2002 |
RP-15 |
RP-020062 |
064 |
Correction on RRC connection establishment procedure |
4.4.0 |
||
|
RP-15 |
RP-020062 |
067 |
Alignment of SRNS relocation in CELL_DCH |
4.4.0 |
|||
|
RP-15 |
RP-020062 |
069 |
Corrections on combined Cell/URA update and SRNS relocation |
4.4.0 |
|||
|
RP-15 |
– |
– |
Upgrade to Release 5 – no technical change |
5.0.0 |
|||
|
06/2002 |
RP-16 |
RP-020323 |
072 |
Clarification on lossless SRNS Relocation |
5.1.0 |
||
|
RP-16 |
RP-020345 |
073 |
RFC 3095 context relocation |
5.1.0 |
|||
|
12/2003 |
RP-22 |
– |
– |
Upgrade to Release 6 – no technical change |
6.0.0 |
||
|
09/2004 |
RP-25 |
RP-040338 |
074 |
Clarification to SRNS Relocation |
6.1.0 |
||
|
12/2004 |
RP-26 |
RP-040478 |
076 |
Clarification of inter-layer dependencies |
6.2.0 |
||
|
06/2005 |
RP-28 |
RP-050308 |
0078 |
Feature Clean-up: Removal of DSCH (FDD) |
6.3.0 |
||
|
RP-28 |
RP-050309 |
0080 |
Feature Clean Up: Removal of CPCH |
6.3.0 |
|||
|
03/2006 |
RP-31 |
– |
– |
Upgrade to the Release 7 – no technical change |
7.0.0 |
||
|
12/2007 |
RP-38 |
– |
– |
Upgrade to the Release 8 – no technical change |
8.0.0 |
||
|
12/2009 |
RP-46 |
– |
– |
Upgrade to the Release 9 – no technical change |
9.0.0 |
||
|
03/2011 |
RP-51 |
– |
– |
– |
Upgrade to the Release 10 – no technical change |
10.0.0 |
|
|
09/2012 |
RP-57 |
– |
– |
– |
Upgrade to the Release 11 – no technical change |
11.0.0 |
|
|
09/2014 |
RP-65 |
– |
– |
– |
Upgrade to the Release 12 – no technical change |
12.0.0 |
|
|
12/2015 |
RP-70 |
– |
– |
– |
Upgrade to the Release 13 – no technical change |
13.0.0 |
|
|
03/2017 |
RP-75 |
– |
– |
– |
Upgrade to the Release 14 – no technical change |
14.0.0 |
|
|
06/2018 |
RP-80 |
– |
– |
– |
Upgrade to the Release 15 – no technical change |
15.0.0 |
|
|
2020-07 |
RP-88e |
– |
– |
– |
– |
Upgrade to Rel-16 version without technical change |
16.0.0 |
|
2022-03 |
RP-95e |
– |
– |
– |
– |
Upgrade to Rel-17 version without technical change |
17.0.0 |