Académique Documents
Professionnel Documents
Culture Documents
GBSS17.1
Issue 01
Date 2015-04-20
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
2 Overview......................................................................................................................................... 3
2.1 Introduction.................................................................................................................................................................... 3
2.2 NEs Supporting the Feature............................................................................................................................................3
3 Technical Description...................................................................................................................5
3.1 Establishment of an Uplink TBF.................................................................................................................................... 5
3.1.1 Establishment of an Uplink TBF on the CCCH.......................................................................................................... 5
3.1.2 Establishment of an Uplink TBF on the PCCCH........................................................................................................ 8
3.1.3 Establishment of an Uplink TBF on the PACCH........................................................................................................ 9
3.2 Establishment of a Downlink TBF............................................................................................................................... 11
3.2.1 Establishment of a Downlink TBF on the CCCH..................................................................................................... 12
3.2.2 Establishment of a Downlink TBF on the PCCCH................................................................................................... 13
3.2.3 Establishment of a Downlink TBF on the PACCH................................................................................................... 13
3.2.4 Establishment of a Downlink TBF on the Uplink..................................................................................................... 13
3.2.5 Establishment of a Downlink TBF on the Downlink................................................................................................ 14
3.2.6 Early Establishment of a Downlink TBF.................................................................................................................. 15
3.3 Release of a TBF.......................................................................................................................................................... 15
3.3.1 Release of a Non-extended Uplink TBF....................................................................................................................16
3.3.2 Release of an Extended Uplink TBF......................................................................................................................... 17
3.3.3 Release of a Downlink TBF...................................................................................................................................... 18
3.4 Uplink Data Transmission............................................................................................................................................ 19
3.4.1 Dynamic Allocation Mode........................................................................................................................................ 19
3.4.2 Extended Dynamic Allocation Mode........................................................................................................................ 20
3.4.3 Handling of LLC PDUs and RLC Data Blocks.........................................................................................................21
3.4.4 RLC Mode................................................................................................................................................................. 21
3.4.4.1 RLC Acknowledged Mode..................................................................................................................................... 22
3.4.4.2 RLC Unacknowledged Mode................................................................................................................................. 22
3.4.5 Uplink Access Congestion Control........................................................................................................................... 22
3.5 Downlink Data Transmission....................................................................................................................................... 22
4 Related Features...........................................................................................................................32
4.1 GBFD-119202 Packet Assignment Taken Over by the BTS........................................................................................32
4.2 GBFD-119203 Extended Uplink TBF..........................................................................................................................32
4.3 GBFD-119205 Dynamically Adjusting the RRBP Frequency..................................................................................... 33
4.4 GBFD-119503 Early TBF Establishment.....................................................................................................................33
4.5 GBFD-119509 GPRS Packet Fast Transmission..........................................................................................................34
5 Network Impact........................................................................................................................... 35
5.1 Packet Assignment Taken Over by the BTS.................................................................................................................35
5.1.1 System Capacity........................................................................................................................................................ 35
5.1.2 Network Performance................................................................................................................................................35
5.2 Extended Uplink TBF...................................................................................................................................................35
5.2.1 System Capacity........................................................................................................................................................ 35
5.2.2 Network Performance................................................................................................................................................35
5.3 Dynamically Adjusting the RRBP Frequency..............................................................................................................36
5.3.1 System Capacity........................................................................................................................................................ 36
5.3.2 Network Performance................................................................................................................................................36
5.4 Early TBF Establishment..............................................................................................................................................36
6 Engineering Guidelines............................................................................................................. 37
6.1 When to Use GPRS/EGPRS Connection Control and Transfer................................................................................... 37
6.1.1 Packet Assignment Taken Over by the BTS..............................................................................................................37
6.1.2 Extended Uplink TBF................................................................................................................................................37
6.1.3 Dynamically Adjusting the RRBP Frequency...........................................................................................................37
6.1.4 Early TBF Establishment...........................................................................................................................................37
6.1.5 GPRS Fast Transmission........................................................................................................................................... 37
6.2 Required Information................................................................................................................................................... 37
6.2.1 Packet Assignment Taken Over by the BTS..............................................................................................................38
6.2.2 Extended Uplink TBF................................................................................................................................................38
6.2.3 Dynamically Adjusting the RRBP Frequency...........................................................................................................38
6.2.4 Early TBF Establishment...........................................................................................................................................38
6.2.5 GPRS Fast Transmission........................................................................................................................................... 38
6.3 Planning........................................................................................................................................................................ 38
6.3.1 RF Planning............................................................................................................................................................... 38
6.3.2 Network Planning...................................................................................................................................................... 38
6.3.3 Hardware Planning.................................................................................................................................................... 38
6.4 Deploying Packet Assignment Taken Over by the BTS...............................................................................................38
6.4.1 Deployment Requirements........................................................................................................................................ 38
6.4.2 Activation.................................................................................................................................................................. 39
6.4.3 Activation Observation..............................................................................................................................................40
6.4.4 Deactivation...............................................................................................................................................................41
6.5 Deploying Extended Uplink TBF.................................................................................................................................42
6.5.1 Deployment Requirements........................................................................................................................................ 42
6.5.2 Activation.................................................................................................................................................................. 42
6.5.3 Activation Observation..............................................................................................................................................44
6.5.4 Deactivation...............................................................................................................................................................44
6.6 Deploying Dynamically Adjusting the RRBP Frequency............................................................................................ 45
6.7 Deploying Early TBF Establishment............................................................................................................................45
6.7.1 Deployment Requirements........................................................................................................................................ 46
6.7.2 Activation.................................................................................................................................................................. 46
6.7.3 Activation Observation..............................................................................................................................................47
6.7.4 Deactivation...............................................................................................................................................................47
6.8 Deploying GPRS Fast Transmission............................................................................................................................ 48
6.8.1 Deployment Requirements........................................................................................................................................ 48
6.8.2 Activation.................................................................................................................................................................. 49
6.8.3 Activation Observation..............................................................................................................................................50
6.8.4 Deactivation...............................................................................................................................................................50
6.9 Performance Monitoring...............................................................................................................................................51
6.9.1 Packet Assignment Taken Over by the BTS..............................................................................................................51
6.9.2 Extended Uplink TBF................................................................................................................................................51
6.9.3 Dynamically Adjusting the RRBP Frequency...........................................................................................................51
6.9.4 Early TBF Establishment...........................................................................................................................................52
6.9.5 GPRS Fast Transmission........................................................................................................................................... 52
6.10 Parameter Optimization.............................................................................................................................................. 52
6.10.1 Packet Assignment Taken Over by the BTS............................................................................................................52
6.10.2 Extended Uplink TBF..............................................................................................................................................52
6.10.3 Dynamically Adjusting the RRBP Frequency.........................................................................................................52
6.10.4 Early TBF Establishment.........................................................................................................................................52
6.10.5 GPRS Fast Transmission......................................................................................................................................... 52
6.11 Troubleshooting.......................................................................................................................................................... 52
7 Parameters..................................................................................................................................... 53
8 Counters........................................................................................................................................ 83
9 Glossary......................................................................................................................................... 84
10 Reference Documents............................................................................................................... 85
1.1 Scope
This document describes GPRS/EGPRS Connection Control and Transfer, including its
technical principles, related features, network impact, and engineering guidelines.
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier
version
01 (2015-04-20)
This issue does not include any changes.
Draft A (2015-01-15)
Compared with Issue 02 (2014-06-30) of GBSS16.0, Draft A (2015-01-15) of GBSS17.1
includes the following changes.
2 Overview
2.1 Introduction
GPRS/EGPRS connection control refers to the establishment and release of TBFs. It includes
the following functions:
l Establishment of uplink and downlink TBFs
l Release of uplink and downlink TBFs
l Reassignment of TBFs
l Suspension and resumption of TBFs
GPRS/EGPRS transfer refers to the transfer of data within TBFs. It includes the following
functions:
l Uplink and downlink data transmission
l Enhancement of extended uplink TBFs
l Dynamic adjustment of relative reserved block period (RRBP) frequency
NOTE
√ indicates that the NE supports this feature. × indicates that the NE does not support this feature.
3 Technical Description
In the previous procedure, if the PDCHs are configured on the BCCH TRX and the packet
uplink immediate assignment function needs to be taken over by the BTS, set the
IMMASSDLSHIFT (BSC6900, BSC6910) parameter to YES(Support) to enable the
GBFD-119202 Packet Assignment Taken Over feature. This feature enables the BTS to send
Immediate Assignment messages. This shortens the message exchange delay between the
BSC and the BTS, and shortens MS access delay by about 100 ms when an external PCU is
used, thereby improving user experience and increasing the revenue of the operator.
The BTS supports takeover of the packet uplink immediate assignment function only during
one-phase access. Figure 3-2 shows the procedure for BTS takeover.
Figure 3-2 Takeover of the packet immediate assignment function by the BTS
1. The BSC sends a Preallocation Uplink TBF Resource Request message to the BTS,
allocating the required uplink TBF resources in advance. The BTS then responds with a
Preallocation Uplink TBF Resource Acknowledgement message.
2. After receiving the Channel Request message from the MS, the BTS schedules uplink
data blocks using the preemption mechanism. Upon receiving the Immediate Assignment
message from the BTS over the AGCH, the MS starts to send data blocks to the BSC.
3. Upon receiving a Channel Request(assist) message from the BTS, the BSC initiates the
procedure for establishing an uplink TBF. The BSC then sends an Immediate
Assignment(assist) message to the BTS. The establishment of an uplink TBF is
complete.
When the Force2Phase (BSC6900, BSC6910) parameter is set to Open(Open) on the BSC,
the forced two-phase access on the CCCH is allowed for an MS.
The basic procedure for one-/two-phase packet access on the PCCCH is mostly the same as
that for one-/two-phase packet access on the uplink CCCH, except for the differences in the
following aspects:
1. The channel request is initiated over the PRACH.
2. Uplink assignment instead of immediate assignment is initiated over the packet access
grant channel (PAGCH).
1. An MS is in packet transfer mode and there is a downlink TBF. If the BSC sets the S/P
field to 1, the MS is instructed to send a Packet Downlink Ack/Nack message in the
reserved uplink block to acknowledge the reception of downlink data. The S/P field
indicates whether the RRBP field is valid. The RRBP field indicates how many TDMA
frames the MS should wait for before sending uplink RLC data blocks. If the S/P field is
set to 1 in the header of a downlink data block, the MS is instructed to acknowledge that
the RRBP field is valid. If the S/P field is set to 0, the RRBP field is invalid.
2. If the MS has uplink data to transmit, the MS sends a Packet Downlink Ack/Nack
message with the Channel Request Description information element (IE) to the BSC over
the PACCH.
3. After receiving the message (the downlink TBF is now in packet transfer mode), the
BSC starts the procedure for establishing an uplink TBF on the downlink. The BSC then
sends a Packet Uplink Assignment message with the TLLI to the MS over the PACCH,
establishes an uplink TBF, and assigns a packet channel to the MS. The contention
resolution procedure is not required during the establishment of an uplink TBF on the
downlink.
4. The MS sends uplink data blocks without the TLLI over the assigned channel. The
establishment of an uplink TBF is complete.
In the previous procedure, if the PDCHs are configured on the BCCH TRX and the packet
assignment function needs to be taken over by the BTS, set the PACKASSDLSHIFT
(BSC6900, BSC6910) parameter to YES(Support) to enable the GBFD-119202 Packet
Assignment Taken Over by the BTS feature. This shortens the message exchange delay
between the BSC and the BTS, and shortens MS access delay by about 100 ms when an
external PCU is used, thereby improving user experience and increasing the revenue of the
operator. Figure 3-5 shows the procedure for BTS takeover:
1. When an uplink TBF that does not support the Extended Uplink TBF feature is to be
released, the BSC sends a Packet Uplink Ack/Nack message with the FAI set to 1. If the
BSC detects that the downlink TBF is in packet transfer mode, the BSC reserves the
uplink TBF and then preassigns it to the BTS.
2. After receiving a Packet Control Ack message from the MS, the BSC starts releasing the
uplink TBF.
3. The BTS receives a Packet Downlink Ack/Nack message with the Channel Request
Description IE from the MS. The BTS then directly assigns the MS the packet channel
that is preassigned by the BSC and performs resource scheduling. The BTS sends a
Packet Uplink Assignment message to the MS, and the MS uploads data blocks. Packet
assignment is therefore successfully taken over by the BTS. At the same time, the BTS
forwards the Packet Downlink Ack/Nack message with the Channel Request Description
IE to the BSC.
4. After receiving the message, the BSC starts establishing an uplink TBF on the downlink.
5. The BSC sends a Packet Uplink Assignment message to the MS over the PACCH. The
BTS transparently transmits the downlink messages on the packet data channel (PDCH).
Therefore, the MS receives the Packet Uplink Assignment message twice. Then, instead
of the BTS, the BSC takes charge of scheduling uplink data blocks.
The BSC resends the Packet Downlink Assignment message for the configured number of
times when both the following conditions are met:
This increases the establishment success rate for a downlink TBF but increases the congestion
rate during peak hours. The smaller the value of the DlAssRetryTimesMax (BSC6900,
BSC6910) parameter, the lower the congestion rate during peak hours, and the lower the
success rate of downlink TBF establishments.
The BSC can resend the Packet Polling Request message for the configured number of times
when both the following conditions are met:
This increases the success rate for downlink TBF establishments but increases the congestion
rate during peak hours. The smaller the value of the PollingRetryTimesMax (BSC6900,
BSC6910) parameter, the lower the congestion rate during peak hours, and the lower the
success rate of downlink TBF establishments.
The BSC sends an RA-CAPABILITY-UPDATE message to obtain the MS capability from the
SGSN when both the following conditions are met:
l The BSC does not obtain the MS capability when the downlink TBF is established or
channel resources are reassigned.
l The SendRACapUpdate (BSC6900, BSC6910) parameter is set to ON(ON).
This helps the BSC to quickly obtain the MS support capability for resource allocation but
increases the signaling traffic over the Gb interface.
The BSC can reject the TBF establishment request when the channel resources are insufficient
or due to other reasons. The MaxDlEstRetryNum (BSC6900, BSC6910) parameter
determines the number of downlink TBF establishment attempts.
1. After receiving a downlink LLC PDU from the SGSN, the BSC inserts the downlink
LLC PDU into the LLC PDU queue. The BSC then sends an Immediate Assignment
message to an MS over the CCCH to assign a channel to the MS. The message carries
the TFI and the start time of the TBF.
2. During the downlink TBF establishment, if the BSC does not obtain the timing advance
(TA) value after sending an Immediate Assignment message, the BSC sends a Packet
Polling Request message with TFI over the PACCH that is used to carry the downlink
TBF. During an immediate assignment procedure, the MaxPollingRetryTimes
(BSC6900, BSC6910) parameter determines the number of times the BSC resends the
Packet Polling Request message. The MS sends a Packet Control Ack message to the
BSC. The BSC then obtains the TA value from the Packet Control Ack message and
sends a Packet Power Control/Timing Advance message to notify the MS of the TA
value.
The CTRLACKTYPE (BSC6900, BSC6910) parameter determines the format of the
message used to obtain the TA. When CTRLACKTYPE (BSC6900, BSC6910) is set to
4BURST(4Burst), the BSC can obtain the TA without sending a Packet Polling Request
message. When CTRLACKTYPE (BSC6900, BSC6910) is set to RLC/MAC(RLC/
MAC), the BSC must send a Packet Polling Request message to obtain the TA value.
3. If the channel (indicated in the Immediate Assignment message) assigned to the MS does
not meet the multislot capability of the MS, the BSC initiates reassigning a downlink
TBF and sends a Packet Downlink Assignment message to assign several channels to a
TBF.
4. After the downlink TBF is successfully established, the BSC starts to send data blocks.
The BSC disassembles the downlink LLC PDU into downlink RLC data blocks and then
sends them to the MS over the assigned downlink packet channel. The BSC sets S/P to 1
in the downlink RLC data block header. The MS sends a Packet Downlink Ack/Nack
message in response to the received downlink RLC data blocks.
The procedure is as follows: During uplink TBF transmission, the BSC receives a downlink
LLC PDU from the SGSN. The BSC then includes the TFI of the uplink TBF and sets S/P to
1 in a Packet Downlink Assignment message sent to the MS over the PACCH. The downlink
TBF is therefore established, and the BSC starts to send RLC data blocks.
1. During downlink TBF transmission, the BSC sends all the data blocks in the LLC PDU
queue to an MS. In the last downlink data block, the BSC sets both the final block
indicator (FBI) and the S/P to 1.
2. The MS responds with a Packet Downlink Ack/Nack message with the FAI set to 1. The
BSC then sets the T3192 (BSC6900, BSC6910) parameter.
– If no PBCCH is configured for a cell, the BSC sends the system information SI13
and PSI13 to inform the MS of this parameter's value.
– If the PBCCH is configured for a cell, the BSC sends the system information PSI1
and PSI13 to inform the MS of this parameter's value.
The MS starts the T3192 timer, and the BSC automatically starts the T3193 timer.
The length of the T3193 timer is a little shorter than that of the T3192 timer.
3. If the previous downlink TBF on the BSC side has been released, the T3193 timer has
not expired, and the BSC needs to transmit downlink PS data, the BSC sends a Packet
Downlink Assignment message with the previous TFI and the RRBP to the MS over the
PACCH that carries the previous downlink TBF. In response to the Packet Downlink
Assignment message, the MS sends a Packet Control Acknowledgement message on the
uplink radio block specified by the RRBP. A downlink TBF is therefore established, and
the BSC sends downlink data blocks to the MS and stops the T3193.
Timer T3191 (BSC6900, BSC6910) is started when the last data block over the downlink
TBF is sent and the FBI in the data block is set to 1. After T3191 expires, the BSC releases all
resources occupied by the TBF. For details about T3191, see 3GPP TS 44.060.
1. The release of a non-extended uplink TBF is initiated by an MS. During uplink TBF
transmission, the MS sets the CV to 0 in the last uplink data block.
2. If the BSC receives all the uplink data blocks, it sends a Packet Uplink Ack/Nack
message in which the FAI and the S/P are set to 1 to the MS. If the BSC does not receive
all the uplink data blocks, it sends a Packet Uplink Ack/Nack message with the FAI set
to 0 to the MS, instructing the MS to retransmit the data blocks that are not received.
3. If the MS receives the Packet Uplink Ack/Nack message in which the FAI and the S/P
are set to 1, it responds with a Packet Control Ack message. The uplink TBF is therefore
released normally.
A monitoring mechanism is required to ensure that the uplink TBF on the BSC side can be
released even if the Packet Control Ack message is lost.
1. After the BSC correctly receives all downlink data blocks, the BSC sends a Packet
Uplink Ack/Nack message in which the FAI and the S/P are set to 1 to the MS. At the
same time, the BSC starts the N3103 counter, whose maximum value is specified by the
N3103 (BSC6900, BSC6910) parameter. After receiving a Packet Control Ack message
from the MS, the BSC resets the N3103 counter to 0.
2. If the BSC does not receive a correct Packet Control Ack message in the corresponding
uplink data block, the N3103 counter is increased by 1.
3. If the N3103 counter reaches its maximum value, the BSC automatically starts the
internal timer T3169.
4. After the T3169 timer expires, the BSC releases the TBF. The corresponding resources
can then be reused.
If an MS does not support an extended uplink TBF and the BSC has received the last uplink
RLC data block with CA set to 0, the BSC sends a Packet Uplink Ack/Nack message with the
FAI set to 1 to the MS, instructing the MS to release the extended uplink TBF. The release of
the non-extended uplink TBF is delayed. The release delay is specified by the
UPTBFRELDELAY (BSC6900, BSC6910) parameter. If the BSC needs to establish a
downlink TBF during the delay period, the downlink TBF can be established on the uplink
TBF that is not released. This reduces the time required by the downlink TBF establishment.
After the downlink TBF is successfully established, this uplink TBF is automatically released.
If the BSC does not need to establish a downlink TBF during the delay period, the MS
releases this uplink TBF after the delay period ends.
1. After receiving the last uplink RLC data block with CV set to 0, the BSC does not
immediately release the extended uplink TBF. Instead, the BSC sends a Packet Uplink
Ack/Nack message with the FAI set to 0. The TBF then enters the inactive period and the
BSC starts the inactive period timer. The length of the timer is specified by the
UPEXTTBFINACTDELAY (BSC6900, BSC6910) parameter. The BSC continues to
allocate uplink resources to the MS until the inactive period timer expires. Uplink
resources are used for the MS to transfer control blocks.
2. If there are uplink RLC data blocks to transmit during the inactive period, the MS can
directly use the uplink TBF that enters the inactive period without establishing a new
uplink TBF. The uplink TBF used by the MS automatically enters the active period. If
there are no uplink RLC data blocks to transmit, the MS sends a Packet Uplink Dummy
Block message to the BSC.
3. When the inactive period ends and there are no uplink RLC data blocks to transmit, the
BSC sends a Packet Uplink Ack/Nack message with the FAI set to 1 to the MS,
instructing the MS to release this uplink TBF. After receiving this message, the MS
sends a Packet Control Ack message to the BSC. The uplink TBF is then released
normally.
1. During downlink TBF transmission, the BSC sends all the data blocks in the LLC PDU
queue to an MS. In the last downlink data block, the BSC sets both the FBI and the S/P
to 1.
2. If an MS correctly receives all the downlink data blocks, it sends a Packet Downlink
Ack/Nack message with the FAI set to 1 to the BSC. Otherwise, the MS sends the BSC a
Packet Downlink Ack/Nack message with the FAI set to 0, requesting the BSC to
retransmit the data blocks that are not received.
3. After receiving the Packet Downlink Ack/Nack message with the FAI set to 1, the BSC
releases the downlink TBF normally.
A monitoring mechanism is required to ensure that the downlink TBF can be released even if
the Packet Downlink Ack/Nack message is lost.
1. Each time the BSC sets S/P to 1 in the downlink TBF data blocks, the BSC starts the
N3105 counter, whose maximum value is specified by the N3105 parameter. If the BSC
correctly receives a Packet Downlink Ack/Nack message from the MS, the BSC resets
the N3105 counter to 0.
2. If the BSC does not correctly receive a Packet Downlink Ack/Nack message from the
MS, the N3105 counter is increased by 1.
3. If the N3105 counter reaches its maximum value (N3105_max), the BSC automatically
starts the internal T3195 timer.
4. After the T3195 timer expires, the downlink TBF is abnormally released.
USF allocation has two modes: dynamic allocation mode and extended dynamic allocation
mode.
When an MS can transmit uplink blocks in extended dynamic allocation mode, the MS does
not need to listen to the subsequently allocated channels. Therefore, the MS can use more
uplink channels than in dynamic allocation mode. Extended dynamic allocation mode helps
increase the uplink data transmission rate and facilitates the transmission of services with a
large data flow on the uplink. This improves user satisfaction. Extended dynamic allocation
mode requires the support from the MS. The RAC reported by an MS indicates whether the
MS supports the GPRS or EGPRS extended dynamic allocation mode.
The MS starts timer T3198 after sending an RLC data block, and sets the RLC data block
status to Unacknowledged after the timer expires. When this happens, the BSC resends the
RLC data block. By default, timer T3198 is set to the total transmission duration of N RLC
data blocks (N is specified by BS_CV_MAX). BS_CV_MAX is used by the MS to calculate
the CV and is specified by the BSCVMAX (BSC6900, BSC6910) parameter. The BSC sends
the value of timer T3198 to the MS in SI.
The radio blocks used by an MS are temporarily allocated by the BSC. The BSC includes the
number of PDCHs allocated to the MS and the value of the USF corresponding to each PDCH
in the assignment uplink resource message or reassignment uplink resource message. After
receiving this message, the MS starts to listen to the USF value in the downlink radio block
header of the allocated channel. If this value is equal to the assigned USF value, the MS is
allowed to use the uplink channel. The MS then transmits data blocks on this channel in the
next radio block period.
The reserved USF is a USF value that is not assigned to a GPRS- or EGPRS-capable MS. It is
used to prevent more than one GPRS- or EGPRS-capable MS from transmitting data on the
same PDCH. By default, the reserved USF value is 7. The BSC informs a GPRS- or EGPRS-
capable MS that one or more uplink radio blocks have been reserved for it on a particular
PDCH. The GPRS- or EGPRS-capable MS may have an uplink or downlink TBF, or no TBF
at all. When the radio block period ends, the BSC notifies the MS of the reserved USF. Only
the MS to which this radio block has been assigned is allowed to transmit data.
l The reserved USF is used in the following scenarios:
– The packet channel request is in the second phase of two-phase access.
– If a downlink RLC/MAC control block contains a valid RRBP field, the MS uses its
reserved radio blocks to send a single control message.
– If the USF granularity is 4, the MS uses its three reserved blocks to send RLC/MAC
data blocks or control messages.
l The free USF is used on the PRACH in the next uplink block period. The PRACH is
used during the first phase of an establishment procedure. All MSs are allowed to
transmit a packet channel request on the PRACH.
A monitoring mechanism is required to ensure that the uplink TBF can be released.
1. After starting to assign a USF to the uplink TBF (that is, the uplink TBF is successfully
established), the BSC starts the N3101 counter to check whether the uplink data is
received. The maximum value of this counter is specified by the N3101 (BSC6900,
BSC6910) parameter.
2. If the BSC receives valid uplink data blocks on the block resources reserved for the MS,
the N3101 counter resets. Otherwise, the value of the N3101 counter is incremented by
one.
3. If the N3101 counter reaches its maximum value N3101_max, the TBF is abnormally
released.
Uplink √ √ √ √
NOTE
All assignment-related messages contain a list of assigned PDCHs and the corresponding USF
value of each PDCH. If the assigned resources do not allow an MS to listen to the USF values
of all the assigned PDCHs, the MS listens to USF values according to the following
principles:
In a block period for data transfer, the MS obtains the USFs of all the timeslots from the
timeslot to which the MS listens to the current timeslot. For example, if the USF in timeslot 3
to which the MS listens is consistent with the locally stored USF, the MS can transfer data in
timeslots 3 to 6. If the USF in timeslot 5 to which the MS listens is consistent with the locally
stored USF, the MS can transfer data in timeslots 5 to 7.
If the PDCHs on which EGPRS and GPRS services are multiplexed use the USF granularity
4, the downlink traffic volume of the EGPRS TBF increases. A GPRS-capable MS and an
EGPRS-capable MS use the same PDCH. Therefore, the EGPRS-capable MS uses on the
downlink the radio blocks with the GPRS coding scheme but cannot use the radio blocks with
the EGPRS coding scheme. After receiving a downlink radio block, the MS triggers the
transmission of uplink radio blocks. The EGPRS-capable MS obtains its own USF value from
the header of the downlink radio block.
l If the USF granularity is 4, uplink data is transmitted on the PDCH in the next four radio
block periods.
l If the USF granularity is 1, uplink data is transmitted on the PDCH in the next radio
block period.
If the USF granularity is 1 and the EGPRS-capable MS needs to transfer one more uplink
radio block, the BSC must send one more downlink radio block with the Gaussian minimum
shift-frequency keying (GMSK) coding scheme to trigger the transmission. Therefore, the
downlink EGPRS bandwidth is adversely affected. If the USF granularity is 4, one downlink
radio block triggers four uplink radio blocks. Therefore, fewer downlink radio blocks with the
GMSK coding scheme are required and the downlink EGPRS bandwidth is negligibly
affected.
When the UsrUlPduTBitValue (BSC6900, BSC6910) parameter is set to 0, the T bit in the
QoS Profile IE of the uplink LLC PDU is forcibly set to 0, indicating that the PDU contains
signaling information.
l One-phase access
– In 8-bit access, only acknowledged mode is used.
– In 11-bit access, unacknowledged mode is used if the EGPRS Packet Channel
Request message carries the "One phase Access Request in RLC unacknowledged
mode" IE; Acknowledged mode is used if the message does not carry the "One
phase Access Request in RLC unacknowledged mode" IE.
l The Channel Request Description IE carried in the Packet Resource Request and Packet
Downlink Ack/Nack messages from the MS indicates which RLC mode should be used
by the network.
Each downlink TBF has a radio block queue, which is used to transmit radio blocks to an MS.
An RLC/MAC control block has a higher priority than an RLC data block. Radio blocks are
transmitted on all the PDCHs that are assigned to the MS. In RLC acknowledged mode, a
radio block that is not acknowledged by the MS is retransmitted or a new radio block is
generated.
When the DlFirstBlkPolling (BSC6900, BSC6910) parameter is set to ON(ON), the RRBP
field is set to 1 in the first scheduling data block over the downlink EGPRS TBF. The RRBP
information instructs the MS to send the Packet Downlink Ack/Nack message in the reserved
data block for fast acknowledgement. This improves the downlink transmission efficiency.
When the StallNackBlkPolling (BSC6900, BSC6910) parameter is set to ON(ON) and the
downlink EGPRS TBF is pending, the RRBP field is set to 1 in the NACK data block sent
over the downlink TBF. The MS then sends the Packet Downlink Ack/Nack message in the
next uplink scheduling data block to the BSC for fast acknowledgement. This improves the
downlink transmission efficiency.
The LLC PDUs are disassembled into RLC data blocks and then scheduled. For EGPRS
services, a radio block contains one or two RLC data blocks, depending on the modulation
and coding scheme (MCS) used.
l For MCS-1 to MCS-6, a radio block contains one RLC data block.
l For MCS-7 to MCS-9, a radio block contains two RLC data blocks.
If a downlink TBF is in transfer mode and the LLC PDU queue of this TBF has downlink
data, the downlink data is sent to the MS. If a downlink TBF is not in transfer mode, the
downlink data is not sent to the MS.
When the SupRAStatus (BSC6900, BSC6910) parameter is set to ON(ON), the BSC sends a
notification message to the SGSN when the radio environment deteriorates or a cell
reselection occurs. The SGSN suspends or stops transmitting LLC PDU packets according to
the received message.
The LLC PDU order specified by N(U) may be broken if the transmission delay over the Gb
interface is different or the packet loss rate is high. When this happens, setting the
LLCPDUReorder (BSC6900, BSC6910) parameter to ON(ON) to reorder the LLC PDUs
that are discontinuously received by the BSC. This decreases the retransmission rate of
downlink LLC PDUs. In addition, configure the time for waiting for the lagged LLC PDUs
using the LLCPDUReorderTime (BSC6900, BSC6910) parameter. This parameter must be
configured based on the jitter delay on the Gb transmission network.
After sending a certain number of RLC data blocks to a GPRS- or EGPRS-capable MS, the
BSC sets the S/P to 1 in the next radio block to be sent.
There are two RLC modes: acknowledged mode and unacknowledged mode.
The BSC checks data validity when forwarding downlink LLC PDUs. If the capacity of
queued LLC PDUs exceeds half of the queue capacity, the BSC performs flow control and
sends flow control messages over the Gb interface. The flow control procedure then starts as
long as the cell is working properly. The BSC regularly reports the bucket size and bucket
flow rate of the cell to the SGSN based on the radio packet channels in the cell. In addition,
the BSC reports the bucket sizes and bucket flow rates of the MSs based on the amount of
radio resources occupied by the MSs. The SGSN adjusts the downlink data flow rate of the
cell and MSs in real time based on the bucket sizes and bucket flow rates of the cell and the
MSs, respectively, to control the downlink data.
NOTE
The bucket size of a cell refers to the maximum storage space that the BSC reserves for the cell to store
packet data. The bucket size varies depending on the number of packet channels in the cell.
The bucket size of an MS refers to the maximum storage space that the BSC reserves for the MS to store
packet data. The bucket size varies depending on the number of channels allocated to the MS.
The bucket flow rate refers to the data transmission rate.
Downlink flow control consists of downlink BVC flow control and downlink MS flow
control.
Discarding LLC PDUs is delayed to reduce the negative impacts of temporary transmission
interruptions in the downlink at the RLC layer. Temporary transmission interruptions at the
RLC layer may be caused by:
l Preemption of PDCHs
l TBF establishment failures
l Intra-cell handovers in dual transfer mode (DTM) connection
l Cell reselection in SGSN during packet transfer
Reassignment can better meet service requirements of users and optimize and adjust channel
resources. However, reassignment may cause call drops. In this situation, setting the
ReAssignResendSw (BSC6900, BSC6910) parameter to ON(On) can add the number of
reassignment attempts to decrease the probability of call drops.
The procedure is as follows: The BSC sends a Packet Timeslot Reconfigure message to the
MS to assign new PDCHs, new USFs, and new TFIs. After a period of time, the MS
continues to transmit data over the new PDCHs.
3.7.1 Suspension
To suspend GPRS services, the BSC sends a Suspend PDU message to the SGSN to suspend
the scheduling of the TBF. The TBF is then released. The SGSN responds with a Suspend-
Ack PDU or Suspend-Nack PDU message to the BSC.
l If the BSC receives a Suspend-Ack PDU message, the suspend procedure is completed.
l If the BSC receives a Suspend-Nack PDU message, the CS connection is released and
the suspend procedure is considered a failure.
3.7.2 Resumption
The BSC initiates the resume procedure when the CS connection is complete.
l If the suspend procedure is completed and the call is released in the routing area in which
it was set up, the BSC sends a Resume PDU message to the SGSN.
– If the SGSN responds with a Resume-Ack PDU message, the GPRS service is
resumed.
– If the SGSN responds with a Resume-Nack PDU message, the GPRS service fails
to be resumed.
l If the call is released in a routing area different from the one in which it was set up, the
network cannot perform the resume procedure for the MS. The MS has to perform a
routing area update.
If the uplink TBF needs to be established during the downlink packet transmission, the MS
includes the EARLY_TBF_ESTABLISHMENT field in the PACKET DOWNLINK Ack/
Nack, EGPRS PACKETDOWNLINK Ack/Nack, or EGPRS2 PACKET DOWNLINK Ack/
Nack message to notify the BSC of the early TBF establishment. After the BSC establishes
the TBF, the processing is the same as that described above.
The BSC sends the system information PSI1, PSI13, or SI13 with the EXT_UTBF_NODATA
parameter to an MS, indicating whether the MS should send the PACKET UPLINK DUMMY
CONTROL BLOCK message.
The value of the EXT_UTBF_NODATA parameter depends on the setting of the cell-level
parameter EXTUTBFNODATA (BSC6900, BSC6910). If EXTUTBFNODATA (BSC6900,
BSC6910) is set to SEND(SEND), the MS sends the PACKET UPLINK DUMMY
CONTROL BLOCK message to the BSC when it has no other block to transmit. If
EXTUTBFNODATA (BSC6900, BSC6910) is set to NOTSEND(NOTSEND), the MS does
not send the PACKET UPLINK DUMMY CONTROL BLOCK message to the BSC when it
has no other block to transmit.
interval of transmitting the RRBP field should be increased because there may not be uplink
data for transmission.
4 Related Features
Impacted Features
Feature ID Feature Name Description
GBFD-114101 GPRS -
GBFD-114201 EGPRS -
Impacted Features
Feature ID Feature Name Description
Impacted Features
None
Impacted Features
None
GBFD-114101 GPRS -
Impacted Features
None
5 Network Impact
6 Engineering Guidelines
Penetration rate of MSs that support the Early TBF Establishment feature =
(EARLY.TBF.ESTAB/CELL.TOTAL.PSCALL.NUM) x 100%
6.3 Planning
6.3.1 RF Planning
N/A
Aspect Requirement
MS None
MSC None
License None
Others None
6.4.2 Activation
NOTE
The BSC6900 supports configuring the built-in and external PCUs, whereas the BSC6910 supports
configuring only the built-in PCU.
l Immediate Assignment Taken Over by the BTS
If an external PCU is used, run the PCU CfgPara ADD allrppu
g_bCellSptImmAssDlShift 4 1 command on the PCU operation maintenance center
(OMC) to activate this feature. After the command is executed, reset the cell.
l Packet Assignment Taken Over by the BTS:
If an external PCU is used, run the PCU CfgPara ADD allrppu
g_bCellSptPackAssDlShift 4 1 command on the PCU OMC to activate this feature.
After the command is executed, reset the cell.
When configuring the Packet Assignment Taken Over by the BTS feature on the CME, you must
perform a single configuration first, and then perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter.
You are advised to perform batch modifications before logging out of the parameter setting interface.
Set parameters on the CME configuration interface according to the operation sequence
described in Table 6-2. For the method of performing the CME single configuration, see
CME Single Configuration Operation Guide.
Step 2 Modify objects in batches on the CME. (CME batch modification center)
To modify objects, such as BSCs, BTSs, cells, and TRXs, in batches, click the icon on
the CME configuration interface to start the batch modification wizard. For the method of
performing batch modifications through the CME batch modification center, press F1 on the
wizard interface to obtain online help.
----End
6.4.4 Deactivation
l Immediate Assignment Taken Over by the BTS
If an external PCU is used, run the PCU CfgPara ADD allrppu
g_bCellSptImmAssDlShift 4 0 command on the PCU OMC to deactivate this feature.
After the command is executed, reset the cell.
l Packet Assignment Taken Over by the BTS
If an external PCU is used, run the PCU CfgPara SET allrppu
g_bCellSptPackAssDlShift 4 0 command on the PCU OMC to deactivate this feature.
After the command is executed, reset the cell.
When configuring the Packet Assignment Taken Over by the BTS feature on the CME, you must
perform a single configuration first, and then perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter.
You are advised to perform batch modifications before logging out of the parameter setting interface.
Set parameters on the CME configuration interface according to the operation sequence
described in Table 6-3. For the method of performing the CME single configuration, see
CME Single Configuration Operation Guide.
Step 2 Modify objects in batches on the CME. (CME batch modification center)
To modify objects, such as BSCs, BTSs, cells, and TRXs, in batches, click the icon on
the CME configuration interface to start the batch modification wizard. For the method of
performing batch modifications through the CME batch modification center, press F1 on the
wizard interface to obtain online help.
----End
BTS None
MS None
MSC None
License None
Others None
6.5.2 Activation
NOTE
The BSC6900 supports the networking mode with built-in PCUs or external PCUs. The BSC6910
supports only the networking mode with built-in PCUs.
If an external PCU is used, run the PCU add privateoptpara command on the PCU OMC
with the inactive period of the extended uplink TBF set to a value greater than 0.
NOTE
Run the SET GCELLPSBASE command with Not Send Dummy Message with Extended Uplink
TBF set to NOTSEND(NOTSEND). This helps further reduce power consumption.
When configuring the Extended Uplink TBF feature on the CME, you must perform a single
configuration first, and then perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter.
You are advised to perform batch modifications before logging out of the parameter setting interface.
To modify objects, such as BSCs, BTSs, cells, and TRXs, in batches, click the icon on
the CME configuration interface to start the batch modification wizard. For the method of
performing batch modifications through the CME batch modification center, press F1 on the
wizard interface to obtain online help.
----End
Expected result: The uplink TBF is not released immediately after uplink data transmission is
complete. After the period specified by Inactive Period of Extended Uplink TBF is reached,
the uplink TBF is released normally.
----End
6.5.4 Deactivation
If an external PCU is used, run the PCU set privateoptpara command on the PCU OMC
with the inactive period of the extended uplink TBF set to 0.
When configuring the Extended Uplink TBF feature on the CME, you must perform a single
configuration first, and then perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter.
You are advised to perform batch modifications before logging out of the parameter setting interface.
To modify objects, such as BSCs, BTSs, cells, and TRXs, in batches, click the icon on
the CME configuration interface to start the batch modification wizard. For the method of
performing batch modifications through the CME batch modification center, press F1 on the
wizard interface to obtain online help.
----End
BSC The BSC is configured with a built-in PCU, packet service processing
boards, and Gb interface boards.
BTS None
GSM None
networking
MSC None
License The license controlling this feature has been activated. For details about
how to activate the license, see License Management Feature Parameter
Description. For details about license items, see License Control Item
Description.
Others None
6.7.2 Activation
When configuring the GPRS Fast Transmission feature on the CME, you must perform a single
configuration first, and then perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter.
You are advised to perform batch modifications before logging out of the parameter setting interface.
Set parameters on the CME configuration interface according to the operation sequence
described in Table 6-8. For the method of performing the CME single configuration, see
CME Single Configuration Operation Guide.
Step 2 Modify objects in batches on the CME. (CME batch modification center)
To modify objects, such as BSCs, BTSs, cells, and TRXs, in batches, click the icon on
the CME configuration interface to start the batch modification wizard. For the method of
performing batch modifications through the CME batch modification center, press F1 on the
wizard interface to obtain online help.
----End
6.7.4 Deactivation
When configuring the GPRS Fast Transmission feature on the CME, you must perform a single
configuration first, and then perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter.
You are advised to perform batch modifications before logging out of the parameter setting interface.
Set parameters on the CME configuration interface according to the operation sequence
described in Table 6-9. For the method of performing the CME single configuration, see
CME Single Configuration Operation Guide.
Step 2 Modify objects in batches on the CME. (CME batch modification center)
To modify objects, such as BSCs, BTSs, cells, and TRXs, in batches, click the icon on
the CME configuration interface to start the batch modification wizard. For the method of
performing batch modifications through the CME batch modification center, press F1 on the
wizard interface to obtain online help.
----End
Aspect Requirement
BTS None
MS None
MSC None
License The license controlling this feature has been activated. For details on
how to activate the license, see License Management Feature
Parameter Description. For details about license items, see License
Control Item Description.
Others None
6.8.2 Activation
NOTE
The BSC6900 can be configured with a built-in or external PCU. The BSC6910 can be configured only
with a built-in PCU.
MML Examples
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, DlGprsTbfExpandOp=96;
When configuring the GPRS Fast Transmission feature on the CME, you must perform a single
configuration first, and then perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter.
You are advised to perform batch modifications before logging out of the parameter setting interface.
Set parameters on the CME configuration interface according to the operation sequence
described in Table 6-11. For the method of performing the CME single configuration, see
CME Single Configuration Operation Guide.
Step 2 Modify objects in batches on the CME. (CME batch modification center)
To modify objects, such as BSCs, BTSs, cells, and TRXs, in batches, click the icon on
the CME configuration interface to start the batch modification wizard. For the method of
performing batch modifications through the CME batch modification center, press F1 on the
wizard interface to obtain online help.
----End
Step 3 Obtain the backward sequence number (BSN) of the first unreceived data block
acknowledged by the MS from the Packet Downlink Ack/Nack message.
The SSN and RECEIVE_BLOCK_BITMAP IEs in the Packet Downlink Ack/Nack message
jointly determine whether the MS has received each downlink data block and the BSN of the
block.RECEIVE_BLOCK_BITMAP is a 64-bit bitmap. The value 0 in the bitmap indicates
that the data block with the specified BSN has not been received. The BSN is calculated using
the following formula:
For example, if the SSN value is 90 and the value of bit 32 in RECEIVE_BLOCK_BITMAP
corresponding to the first unreceived data block acknowledged by the MS is 0, the BSN of the
first unreceived data block acknowledged by the MS is 57 (90 – 33).
Step 4 Check the BSN of the latest data block to be sent by the BSC in the Downlink Data Block
message.
Step 5 Calculate the difference between the BSN of the latest data block to be sent and that of the
first unreceived data block acknowledged by the MS. The calculated difference is the size of
the downlink GPRS RLC send window.
Expected result: The size of the downlink GPRS RLC send window may be greater than 64
and the maximum window size is specified by the Downlink GPRS TBF Window
Expansion Optimization parameter.
----End
6.8.4 Deactivation
MML Examples
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, DlGprsTbfExpandOp=0;
When configuring the GPRS Fast Transmission feature on the CME, you must perform a single
configuration first, and then perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter.
You are advised to perform batch modifications before logging out of the parameter setting interface.
Set parameters on the CME configuration interface according to the operation sequence
described in Table 6-12. For the method of performing the CME single configuration, see
CME Single Configuration Operation Guide.
Step 2 Modify objects in batches on the CME. (CME batch modification center)
To modify objects, such as BSCs, BTSs, cells, and TRXs, in batches, click the icon on
the CME configuration interface to start the batch modification wizard. For the method of
performing batch modifications through the CME batch modification center, press F1 on the
wizard interface to obtain online help.
----End
– If the interval between two ping commands is shorter than the delayed period for
releasing downlink TBFs and shorter than 900 ms, the ping delay further shortens.
Based on the signaling tracing result:
– If an uplink TBF does not exist, a Packet Downlink Ack message is sent at an
interval of about 150 ms within 900 ms before the delayed release of a downlink
TBF.
– If an uplink TBF does not exist, a Packet Downlink Ack message is sent at an
interval of about 400 ms within 900 ms before the delayed release of a downlink
TBF.
– If an uplink TBF exists, a Packet Downlink Ack message is sent at an interval of
1000 ms when delayed release of a downlink TBF.
6.11 Troubleshooting
None
7 Parameters
bAdvEs BSC690 SET GBFD-1 EGPRS Meaning: Whether the early downlink TBF
tDlTbf 0 BSCPS 14201 GPRS establishment is allowed. Early downlink TBF
SOFTP GBFD-1 establishment indicates that the downlink TBF is
ARA 14101 established immediately after the uplink TBF of the
MS is established rather than after the SGSN sends a
data block. If this parameter is set to LOCALTLLI,
the early downlink TBF establishment is allowed only
for MSs that use the local TLLI to process PS
services. If this parameter is set to ALLTLLI, the early
downlink TBF establishment is allowed for all MSs
that process PS services. If this parameter is set to
CLOSE, the early downlink TBF establishment is not
allowed for all MSs that process PS services.
GUI Value Range: CLOSE(Close),
LOCALTLLI(Local TLLI Opt), ALLTLLI(All TLLI
Opt)
Unit: None
Actual Value Range: CLOSE, LOCALTLLI,
ALLTLLI
Default Value: ALLTLLI(All TLLI Opt)
bAdvEs BSC691 SET GBFD-1 EGPRS Meaning: Whether the early downlink TBF
tDlTbf 0 BSCPS 14201 GPRS establishment is allowed. Early downlink TBF
SOFTP GBFD-1 establishment indicates that the downlink TBF is
ARA 14101 established immediately after the uplink TBF of the
MS is established rather than after the SGSN sends a
data block. If this parameter is set to LOCALTLLI,
the early downlink TBF establishment is allowed only
for MSs that use the local TLLI to process PS
services. If this parameter is set to ALLTLLI, the early
downlink TBF establishment is allowed for all MSs
that process PS services. If this parameter is set to
CLOSE, the early downlink TBF establishment is not
allowed for all MSs that process PS services.
GUI Value Range: CLOSE(Close),
LOCALTLLI(Local TLLI Opt), ALLTLLI(All TLLI
Opt)
Unit: None
Actual Value Range: CLOSE, LOCALTLLI,
ALLTLLI
Default Value: ALLTLLI(All TLLI Opt)
CONTE BSC690 SET GBFD-1 Access Meaning: Whether to enable the contention solution
NTRES 0 BSCPS 19110 optimization function. When this function is enabled,
OLUTP UMPA the BSC sends a PACKET UPLINK ACK/NACK
OLICY RA message carrying the TLLI to an MS upon receiving
an uplink RLC data block carrying the TLLI from the
MS. The BSC sends a maximum of three PACKET
UPLINK ACK/NACK messages carrying the TLLI to
ensure that the uplink contention solution is complete.
GUI Value Range: NOTFORCE(Not Forcibly),
FORCETHREEULACK(Three Forcibly sent)
Unit: None
Actual Value Range: NOTFORCE,
FORCETHREEULACK
Default Value: NOTFORCE(Not Forcibly)
CONTE BSC691 SET GBFD-1 Access Meaning: Whether to enable the contention solution
NTRES 0 BSCPS 19110 optimization function. When this function is enabled,
OLUTP UMPA the BSC sends a PACKET UPLINK ACK/NACK
OLICY RA message carrying the TLLI to an MS upon receiving
an uplink RLC data block carrying the TLLI from the
MS. The BSC sends a maximum of three PACKET
UPLINK ACK/NACK messages carrying the TLLI to
ensure that the uplink contention solution is complete.
GUI Value Range: NOTFORCE(Not Forcibly),
FORCETHREEULACK(Three Forcibly sent)
Unit: None
Actual Value Range: NOTFORCE,
FORCETHREEULACK
Default Value: NOTFORCE(Not Forcibly)
Force2P BSC690 SET GBFD-1 Access Meaning: Whether two phase access is forcibly used
hase 0 BSCPS 19110 when an MS access the network on the CCCH.
SOFTP GUI Value Range: Close(Close), Open(Open)
ARA
Unit: None
Actual Value Range: Close, Open
Default Value: Close(Close)
Force2P BSC691 SET GBFD-1 Access Meaning: Whether two phase access is forcibly used
hase 0 BSCPS 19110 when an MS access the network on the CCCH.
SOFTP GUI Value Range: Close(Close), Open(Open)
ARA
Unit: None
Actual Value Range: Close, Open
Default Value: Close(Close)
DlAssR BSC690 SET GBFD-1 EGPRS Meaning: Maximum number of attempts the BSS
etryTim 0 GCELL 14201 GPRS sends a downlink packet assignment message to an
esMax PRIVA GBFD-1 MS.
TEOPT 14101 GUI Value Range: 0~5
PARA
Unit: None
Actual Value Range: 0~5
Default Value: 0
DlAssR BSC691 SET GBFD-1 EGPRS Meaning: Maximum number of attempts the BSS
etryTim 0 GCELL 14201 GPRS sends a downlink packet assignment message to an
esMax PRIVA GBFD-1 MS.
TEOPT 14101 GUI Value Range: 0~5
PARA
Unit: None
Actual Value Range: 0~5
Default Value: 0
Polling BSC690 SET GBFD-1 EGPRS Meaning: Maximum number of attempts the BSS
RetryTi 0 GCELL 14201 GPRS sends a polling message to an MS.
mesMa PRIVA GBFD-1 GUI Value Range: 0~5
x TEOPT 14101
PARA Unit: None
Actual Value Range: 0~5
Default Value: 0
Polling BSC691 SET GBFD-1 EGPRS Meaning: Maximum number of attempts the BSS
RetryTi 0 GCELL 14201 GPRS sends a polling message to an MS.
mesMa PRIVA GBFD-1 GUI Value Range: 0~5
x TEOPT 14101
PARA Unit: None
Actual Value Range: 0~5
Default Value: 0
SendRA BSC690 SET GBFD-1 EGPRS Meaning: Whether the BSC sends the RA-
CapUp 0 BSCPS 14201 GPRS CAPABILITY-UPDATE message to the SGSN
date GBPAR GBFD-1 GUI Value Range: OFF(OFF), ON(ON)
A 14101 Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(OFF)
SendRA BSC691 SET GBFD-1 EGPRS Meaning: Whether the BSC sends the RA-
CapUp 0 BSCPS 14201 GPRS CAPABILITY-UPDATE message to the SGSN
date GBPAR GBFD-1 GUI Value Range: OFF(OFF), ON(ON)
A 14101 Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(OFF)
MaxDl BSC690 SET GBFD-1 Access Meaning: Number of attempts to re-establish the
EstRetr 0 BSCPS 19110 downlink TBF
yNum SOFTP GUI Value Range: 0~5
ARA
Unit: None
Actual Value Range: 0~5
Default Value: 1
MaxDl BSC691 SET GBFD-1 Access Meaning: Number of attempts to re-establish the
EstRetr 0 BSCPS 19110 downlink TBF
yNum SOFTP GUI Value Range: 0~5
ARA
Unit: None
Actual Value Range: 0~5
Default Value: 1
MaxPol BSC690 SET GBFD-1 Access Meaning: Maximum number of times the Packet
lingRetr 0 BSCPS 19110 Polling Request message is resent when downlink
yTimes SOFTP TBFs are established on the CCCH during an
ARA immediate assignment.
GUI Value Range: 0~5
Unit: None
Actual Value Range: 0~5
Default Value: 5
MaxPol BSC691 SET GBFD-1 Access Meaning: Maximum number of times the Packet
lingRetr 0 BSCPS 19110 Polling Request message is resent when downlink
yTimes SOFTP TBFs are established on the CCCH during an
ARA immediate assignment.
GUI Value Range: 0~5
Unit: None
Actual Value Range: 0~5
Default Value: 5
CTRLA BSC690 SET GBFD-1 GPRS Meaning: Format of the transmit control acknowledge
CKTYP 0 GCELL 14101 message of the MS. Four access bursts are used to
E PSBAS obtain timing advance without sending polling
E message; RLC/MAC control block is used to obtain
timing advance after sending a polling message.
GUI Value Range: 4BURST(4Burst), RLC/
MAC(RLC/MAC)
Unit: None
Actual Value Range: 4BURST, RLC/MAC
Default Value: RLC/MAC(RLC/MAC)
CTRLA BSC691 SET GBFD-1 GPRS Meaning: Format of the transmit control acknowledge
CKTYP 0 GCELL 14101 message of the MS. Four access bursts are used to
E PSBAS obtain timing advance without sending polling
E message; RLC/MAC control block is used to obtain
timing advance after sending a polling message.
GUI Value Range: 4BURST(4Burst), RLC/
MAC(RLC/MAC)
Unit: None
Actual Value Range: 4BURST, RLC/MAC
Default Value: RLC/MAC(RLC/MAC)
DLTBF BSC690 SET GBFD-1 EGPRS Meaning: Time interval between sending of the Packet
ESTDE 0 GCELL 14201 GPRS Uplink Ack/Nack message and setup of the DL TBF.
LAY PRIVA GBFD-1 After receiving the Packet Uplink Ack/Nack message
TEOPT 14101 (FAI = 1), the MS releases the UL TBF and starts to
PARA monitor CCCH. In this case, if the MS receives the
downlink assignment message before being handed
over to the CCCH, the MS fails to respond to the
downlink assignment message. Therefore, a delay is
required for establishing DL TBF, to avoid such a
situation. That is, the DL TBF will not be set up
immediately after the Packet Uplink Ack/Nack
message (FAI = 1) is sent. In this way, the MS can
respond to the downlink assignment message properly.
GUI Value Range: 0~300
Unit: ms
Actual Value Range: 0~300
Default Value: 140
DLTBF BSC691 SET GBFD-1 EGPRS Meaning: Time interval between sending of the Packet
ESTDE 0 GCELL 14201 GPRS Uplink Ack/Nack message and setup of the DL TBF.
LAY PRIVA GBFD-1 After receiving the Packet Uplink Ack/Nack message
TEOPT 14101 (FAI = 1), the MS releases the UL TBF and starts to
PARA monitor CCCH. In this case, if the MS receives the
downlink assignment message before being handed
over to the CCCH, the MS fails to respond to the
downlink assignment message. Therefore, a delay is
required for establishing DL TBF, to avoid such a
situation. That is, the DL TBF will not be set up
immediately after the Packet Uplink Ack/Nack
message (FAI = 1) is sent. In this way, the MS can
respond to the downlink assignment message properly.
GUI Value Range: 0~300
Unit: ms
Actual Value Range: 0~300
Default Value: 140
MSCon BSC690 SET GBFD-1 Access Meaning: Time during which the MS context is
textLife 0 BSCPS 19110 reserved after uplink and downlink TBFs are released.
Time SOFTP After the uplink and downlink TBFs of an MS are
ARA released, the MS context release timer, whose value
equals the value of this parameter, is started. If the MS
accesses the network again before the MS context
release timer expires, the timer is stopped. The MS
context is released after the timer expires.
GUI Value Range: 0~300
Unit: s
Actual Value Range: 0~300
Default Value: 30
MSCon BSC691 SET GBFD-1 Access Meaning: Time during which the MS context is
textLife 0 BSCPS 19110 reserved after uplink and downlink TBFs are released.
Time SOFTP After the uplink and downlink TBFs of an MS are
ARA released, the MS context release timer, whose value
equals the value of this parameter, is started. If the MS
accesses the network again before the MS context
release timer expires, the timer is stopped. The MS
context is released after the timer expires.
GUI Value Range: 0~300
Unit: s
Actual Value Range: 0~300
Default Value: 30
ForceR BSC690 SET None None Meaning: Duration for forcibly releasing a TBF in the
elTbfDu 0 BSCPS transfer state. When the uplink and downlink LLC
ration SOFTP PDUs fail to be transmitted within the duration
ARA specified by this parameter, the TBF is forcibly
released.
GUI Value Range: 4~20
Unit: s
Actual Value Range: 4~20
Default Value: 6
ForceR BSC691 SET None None Meaning: Duration for forcibly releasing a TBF in the
elTbfDu 0 BSCPS transfer state. When the uplink and downlink LLC
ration SOFTP PDUs fail to be transmitted within the duration
ARA specified by this parameter, the TBF is forcibly
released.
GUI Value Range: 4~20
Unit: s
Actual Value Range: 4~20
Default Value: 6
PDCHD BSC690 SET GBFD-1 Adaptiv Meaning: PDCH downlink multiplex threshold,
WNLE 0 GCELL 19501 e Indicating the maximum dowlink TBFs on the
V PSCH GBFD-1 Adjustm downlink PDCH (parameter value/10). We
M 14201 ent of recommend that the value of
Uplink "DWNDYNCHNTRANLEV" should be less than
GBFD-1 and "PDCHDWNLEV" for triggering converting dynamic
14101 Downlin channel in time and reducing PDCH multiplex.
GBFD-1 k GUI Value Range: 10~160
19303 Channel
s Unit: None
GBFD-1
13101 EGPRS Actual Value Range: 10~160
Load
Sharing
PDCH
Dynami
c
Adjustm
ent
PDCHD BSC691 SET GBFD-1 Adaptiv Meaning: PDCH downlink multiplex threshold,
WNLE 0 GCELL 19501 e Indicating the maximum dowlink TBFs on the
V PSCH GBFD-1 Adjustm downlink PDCH (parameter value/10). We
M 14201 ent of recommend that the value of
Uplink "DWNDYNCHNTRANLEV" should be less than
GBFD-1 and "PDCHDWNLEV" for triggering converting dynamic
14101 Downlin channel in time and reducing PDCH multiplex.
GBFD-1 k GUI Value Range: 10~160
19303 Channel
s Unit: None
GBFD-1
13101 EGPRS Actual Value Range: 10~160
Load
Sharing
PDCH
Dynami
c
Adjustm
ent
T3191 BSC690 SET GBFD-1 EGPRS Meaning: Duration of timer T3191. For details, see
0 GCELL 14201 GPRS 3GPP TS44.060.
PRIVA GBFD-1 GUI Value Range: 0~255
TEOPT 14101
PARA Unit: s
Actual Value Range: 0~255
Default Value: 5
T3191 BSC691 SET GBFD-1 EGPRS Meaning: Duration of timer T3191. For details, see
0 GCELL 14201 GPRS 3GPP TS44.060.
PRIVA GBFD-1 GUI Value Range: 0~255
TEOPT 14101
PARA Unit: s
Actual Value Range: 0~255
Default Value: 5
BSCV BSC690 SET GBFD-1 GPRS Meaning: This parameter is used to set the parameter
MAX 0 GCELL 14101 BS_CV_MAX for MS countdown. This parameter is
PSBAS used for the MS to calculate the CV. This parameter
E also determines the duration of the timer T3198.
When the MS sends one uplink RLC data block, the
receiving state of this data block is set to Pending and
the timer T3198 is started. If the MS receives the
packet uplink acknowledge before the timer T3198
expires, the MS updates the receiving state of each
uplink RLC data block according to the bit map in the
message. If the timer T3198 of the RLC data block in
the Pending state expires, the MS sets the receiving
state of this data block to Nack and retransmits the
data block.
GUI Value Range: 0~15
Unit: None
Actual Value Range: 0~15
Default Value: 10
BSCV BSC691 SET GBFD-1 GPRS Meaning: This parameter is used to set the parameter
MAX 0 GCELL 14101 BS_CV_MAX for MS countdown. This parameter is
PSBAS used for the MS to calculate the CV. This parameter
E also determines the duration of the timer T3198.
When the MS sends one uplink RLC data block, the
receiving state of this data block is set to Pending and
the timer T3198 is started. If the MS receives the
packet uplink acknowledge before the timer T3198
expires, the MS updates the receiving state of each
uplink RLC data block according to the bit map in the
message. If the timer T3198 of the RLC data block in
the Pending state expires, the MS sets the receiving
state of this data block to Nack and retransmits the
data block.
GUI Value Range: 0~15
Unit: None
Actual Value Range: 0~15
Default Value: 10
UsrUlP BSC690 SET GBFD-1 EGPRS Meaning: T bit value of the LLC packet data unit
duTBit 0 BSCPS 14201 GPRS (PDU) QoS profile on the uplink user plane.
Value GBPAR GBFD-1 GUI Value Range: 0~1
A 14101 Unit: None
Actual Value Range: 0~1
Default Value: 0
UsrUlP BSC691 SET GBFD-1 EGPRS Meaning: T bit value of the LLC packet data unit
duTBit 0 BSCPS 14201 GPRS (PDU) QoS profile on the uplink user plane.
Value GBPAR GBFD-1 GUI Value Range: 0~1
A 14101 Unit: None
Actual Value Range: 0~1
Default Value: 0
DlFirst BSC690 SET GBFD-1 EGPRS Meaning: Whether to set RRBP to valid when
BlkPolli 0 BSCPS 14201 scheduling the first data block carried on a downlink
ng SOFTP EGPRS TBF. When RRBP is set to valid, the BSC
ARA requests an MS to respond to a Packet Downlink Ack
or Packet Downlink Nack message.
GUI Value Range: OFF(OFF), ON(ON)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(OFF)
DlFirst BSC691 SET GBFD-1 EGPRS Meaning: Whether to set RRBP to valid when
BlkPolli 0 BSCPS 14201 scheduling the first data block carried on a downlink
ng SOFTP EGPRS TBF. When RRBP is set to valid, the BSC
ARA requests an MS to respond to a Packet Downlink Ack
or Packet Downlink Nack message.
GUI Value Range: OFF(OFF), ON(ON)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(OFF)
SptDlT BSC690 SET GBFD-1 EGPRS Meaning: Whether the PACK data block is
bfSched 0 BSCPS 14201 GPRS retransmitted when the PDCH is idle on the downlink
Optimiz SOFTP GBFD-1 GUI Value Range: NO(NO), YES(YES)
e ARA 14101 Unit: None
Actual Value Range: NO, YES
Default Value: YES(YES)
SptDlT BSC691 SET GBFD-1 EGPRS Meaning: Whether the PACK data block is
bfSched 0 BSCPS 14201 GPRS retransmitted when the PDCH is idle on the downlink
Optimiz SOFTP GBFD-1 GUI Value Range: NO(NO), YES(YES)
e ARA 14101 Unit: None
Actual Value Range: NO, YES
Default Value: YES(YES)
SupRA BSC690 SET GBFD-1 EGPRS Meaning: Whether the BSC sends the RADIO-
Status 0 BSCPS 14201 GPRS STATUS message to the SGSN.
GBPAR GBFD-1 GUI Value Range: OFF(OFF), ON(ON)
A 14101 Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(OFF)
SupRA BSC691 SET GBFD-1 EGPRS Meaning: Whether the BSC sends the RADIO-
Status 0 BSCPS 14201 GPRS STATUS message to the SGSN.
GBPAR GBFD-1 GUI Value Range: OFF(OFF), ON(ON)
A 14101 Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(OFF)
ReAssig BSC690 SET GBFD-1 Assignm Meaning: Whether the BSC resends a downlink
nResen 0 GCELL 19111 ent packet reassignment message or Packet Timeslot
dSw PRIVA Reconfigure message if it has failed to send the
TEOPT message. If this parameter is set to ON, the BSC
PARA resends the downlink packet reassignment message or
the Packet Timeslot Reconfigure message twice at
most. If this parameter is set to OFF, the BSC does not
resend the downlink packet reassignment message or
the Packet Timeslot Reconfigure message.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
ReAssig BSC691 SET GBFD-1 Assignm Meaning: Whether the BSC resends a downlink
nResen 0 GCELL 19111 ent packet reassignment message or Packet Timeslot
dSw PRIVA Reconfigure message if it has failed to send the
TEOPT message. If this parameter is set to ON, the BSC
PARA resends the downlink packet reassignment message or
the Packet Timeslot Reconfigure message twice at
most. If this parameter is set to OFF, the BSC does not
resend the downlink packet reassignment message or
the Packet Timeslot Reconfigure message.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
IMMAS BSC690 SET GBFD-1 Packet Meaning: Whether the BSC supports the takeover of
SDLSH 0 GCELL 19202 Assignm packet immediate assignment by the BTS, which
IFT PSOTH ent corresponds with the uplink immediate assignment. To
ERPAR Taken improve the access rate of an MS, the BSC allocates
A Over by uplink temporary block flow (TBF) resources to the
the BTS BTS in advance. Upon receiving a Channel Request
message from the MS, the BTS sends an Immediate
Assignment message to the MS by using the TBF
resources allocated by the BSC. The MS uploads the
data blocks when it receives the Immediate
Assignment message from the BTS.
GUI Value Range: NO(Not Support), YES(Support)
Unit: None
Actual Value Range: NO, YES
Default Value: NO(Not Support)
IMMAS BSC691 SET GBFD-1 Packet Meaning: Whether the BSC supports the takeover of
SDLSH 0 GCELL 19202 Assignm packet immediate assignment by the BTS, which
IFT PSOTH ent corresponds with the uplink immediate assignment. To
ERPAR Taken improve the access rate of an MS, the BSC allocates
A Over by uplink temporary block flow (TBF) resources to the
the BTS BTS in advance. Upon receiving a Channel Request
message from the MS, the BTS sends an Immediate
Assignment message to the MS by using the TBF
resources allocated by the BSC. The MS uploads the
data blocks when it receives the Immediate
Assignment message from the BTS.
GUI Value Range: NO(Not Support), YES(Support)
Unit: None
Actual Value Range: NO, YES
Default Value: NO(Not Support)
PACKA BSC690 SET GBFD-1 Packet Meaning: Whether to support the function of moving
SSDLS 0 GCELL 19202 Assignm the packet assignment down to the BTS. To improve
HIFT PSOTH ent the access speed of the MS, after the packet
ERPAR Taken assignment is moved down to the BTS, the BSC
A Over by reserves the uplink resources for the BTS. The BTS
the BTS obtains the channel request of the MS by analyzing
the downlink acknowledgement message sent by the
MS. Then the BTS allocates the reserved uplink
resources to the MS to move the packet assignment to
the BTS.
GUI Value Range: NO(Not Support), YES(Support)
Unit: None
Actual Value Range: NO, YES
Default Value: NO(Not Support)
PACKA BSC691 SET GBFD-1 Packet Meaning: Whether to support the function of moving
SSDLS 0 GCELL 19202 Assignm the packet assignment down to the BTS. To improve
HIFT PSOTH ent the access speed of the MS, after the packet
ERPAR Taken assignment is moved down to the BTS, the BSC
A Over by reserves the uplink resources for the BTS. The BTS
the BTS obtains the channel request of the MS by analyzing
the downlink acknowledgement message sent by the
MS. Then the BTS allocates the reserved uplink
resources to the MS to move the packet assignment to
the BTS.
GUI Value Range: NO(Not Support), YES(Support)
Unit: None
Actual Value Range: NO, YES
Default Value: NO(Not Support)
T3192 BSC690 SET GBFD-1 EGPRS Meaning: Duration of releasing the TBF after the MS
0 GCELL 14201 GPRS receives the last data block. When the MS receives the
PSBAS GBFD-1 RLC data block containing the flag identifying the last
E 14101 data block and confirms that all the RLC data blocks
in the TBF are received, the MS sends the packet
downlink acknowledge message containing the last
flag acknowledgement and the timer T3192 is started.
If the timer T3192 expires, the MS releases the TBF
related resources and starts monitoring the paging
channel. During TBF releasing, if the MS is the half
duplex mode and receives the packet downlink
assignment, the MS responds this command. During
TBF releasing, if the MS is the half duplex mode and
receives no packet downlink assignment message, the
MS enters the packet idle mode. If the MS is in the
dual transmission mode, the MS enters the special
mode.
GUI Value Range: 0ms(0ms), 80ms(80ms),
120ms(120ms), 160ms(160ms), 200ms(200ms),
500ms(500ms), 1000ms(1000ms), 1500ms(1500ms)
Unit: ms
Actual Value Range: 0ms, 80ms, 120ms, 160ms,
200ms, 500ms, 1000ms, 1500ms
Default Value: 500ms(500ms)
T3192 BSC691 SET GBFD-1 EGPRS Meaning: Duration of releasing the TBF after the MS
0 GCELL 14201 GPRS receives the last data block. When the MS receives the
PSBAS GBFD-1 RLC data block containing the flag identifying the last
E 14101 data block and confirms that all the RLC data blocks
in the TBF are received, the MS sends the packet
downlink acknowledge message containing the last
flag acknowledgement and the timer T3192 is started.
If the timer T3192 expires, the MS releases the TBF
related resources and starts monitoring the paging
channel. During TBF releasing, if the MS is the half
duplex mode and receives the packet downlink
assignment, the MS responds this command. During
TBF releasing, if the MS is the half duplex mode and
receives no packet downlink assignment message, the
MS enters the packet idle mode. If the MS is in the
dual transmission mode, the MS enters the special
mode.
GUI Value Range: 0ms(0ms), 80ms(80ms),
120ms(120ms), 160ms(160ms), 200ms(200ms),
500ms(500ms), 1000ms(1000ms), 1500ms(1500ms)
Unit: ms
Actual Value Range: 0ms, 80ms, 120ms, 160ms,
200ms, 500ms, 1000ms, 1500ms
Default Value: 500ms(500ms)
N3103 BSC690 SET GBFD-1 EGPRS Meaning: Maximum value of N3103. Upon receiving
0 GCELL 14201 GPRS the last RLC data block during uplink transmission,
STAND GBFD-1 the BSC sends an MS a Packet Uplink Ack/Nack
ARDOP 14101 message containing the FAI field with the value being
TPARA 1, and starts N3103. If the BSC does not receive a
Packet Control Ack message within the time reserved
for receiving the control blocks from the MS, N3103
increases, and the BSC resends the MS the Packet
Uplink Ack/Nack message. When the value of N3103
overflows, T3169 starts. When T3169 expires, the
current uplink TBF is abnormally released.
GUI Value Range: 0~255
Unit: None
Actual Value Range: 0~255
Default Value: 3
N3103 BSC691 SET GBFD-1 EGPRS Meaning: Maximum value of N3103. Upon receiving
0 GCELL 14201 GPRS the last RLC data block during uplink transmission,
STAND GBFD-1 the BSC sends an MS a Packet Uplink Ack/Nack
ARDOP 14101 message containing the FAI field with the value being
TPARA 1, and starts N3103. If the BSC does not receive a
Packet Control Ack message within the time reserved
for receiving the control blocks from the MS, N3103
increases, and the BSC resends the MS the Packet
Uplink Ack/Nack message. When the value of N3103
overflows, T3169 starts. When T3169 expires, the
current uplink TBF is abnormally released.
GUI Value Range: 0~255
Unit: None
Actual Value Range: 0~255
Default Value: 3
UPTBF BSC690 SET GBFD-1 Extende Meaning: Delay of releasing the non-extended uplink
RELDE 0 GCELL 19203 d Uplink TBF. After receiving the last uplink RLC data block
LAY PRIVA TBF (CountValue=0), the network side sends the message
TEOPT Packet Uplink Ack/Nack with FAI=1 to notify the MS
PARA of releasing the uplink TBF. After this parameter is
set, the network side notifies the MS of releasing this
TBF after specified delay. In this way, the downlink
TBF can be established on the unreleased uplink TBF.
This uplink TBF is automatically released when the
downlink TBF is established or when the delay
duration exceeds the time set by the uplink non-
extended TBF. If this parameter is set to 0, the release
delay of non-extended TBF is disabled.
GUI Value Range: 0~2000
Unit: ms
Actual Value Range: 0~2000
Default Value: 120
UPTBF BSC691 SET GBFD-1 Extende Meaning: Delay of releasing the non-extended uplink
RELDE 0 GCELL 19203 d Uplink TBF. After receiving the last uplink RLC data block
LAY PRIVA TBF (CountValue=0), the network side sends the message
TEOPT Packet Uplink Ack/Nack with FAI=1 to notify the MS
PARA of releasing the uplink TBF. After this parameter is
set, the network side notifies the MS of releasing this
TBF after specified delay. In this way, the downlink
TBF can be established on the unreleased uplink TBF.
This uplink TBF is automatically released when the
downlink TBF is established or when the delay
duration exceeds the time set by the uplink non-
extended TBF. If this parameter is set to 0, the release
delay of non-extended TBF is disabled.
GUI Value Range: 0~2000
Unit: ms
Actual Value Range: 0~2000
Default Value: 120
UPEXT BSC690 SET GBFD-1 Extende Meaning: Inactive period of extended uplink TBF.
TBFIN 0 GCELL 19203 d Uplink After the network side receives the last uplink RLC
ACTDE PRIVA TBF data block (CountValue=0) of the MS supporting the
LAY TEOPT extended uplink TBF, the uplink TBF is not released
PARA immediately. Instead, the uplink TBF is set to the
inactive state. In the inactive period, if the MS needs
to transmit the uplink RLC data block, the MS can use
the inactive uplink TBF without rebuilding a new
uplink TBF. This inactive uplink TBF is switched to
the active state automatically. At the end of the
inactive period, if the MS does not transmit the uplink
RLC data block, the network side sends the message
Packet Uplink Ack/Nack to notify the MS of releasing
the uplink TBF. When the uplink TBF is inactive, the
downlink TBF can be established according to this
uplink TBF. 0: disable the function of the extended
uplink TBF (this function can be disabled on the BSC
side).
GUI Value Range: 0~5000
Unit: ms
Actual Value Range: 0~5000
Default Value: 2000
UPEXT BSC691 SET GBFD-1 Extende Meaning: Inactive period of extended uplink TBF.
TBFIN 0 GCELL 19203 d Uplink After the network side receives the last uplink RLC
ACTDE PRIVA TBF data block (CountValue=0) of the MS supporting the
LAY TEOPT extended uplink TBF, the uplink TBF is not released
PARA immediately. Instead, the uplink TBF is set to the
inactive state. In the inactive period, if the MS needs
to transmit the uplink RLC data block, the MS can use
the inactive uplink TBF without rebuilding a new
uplink TBF. This inactive uplink TBF is switched to
the active state automatically. At the end of the
inactive period, if the MS does not transmit the uplink
RLC data block, the network side sends the message
Packet Uplink Ack/Nack to notify the MS of releasing
the uplink TBF. When the uplink TBF is inactive, the
downlink TBF can be established according to this
uplink TBF. 0: disable the function of the extended
uplink TBF (this function can be disabled on the BSC
side).
GUI Value Range: 0~5000
Unit: ms
Actual Value Range: 0~5000
Default Value: 2000
DlGprs BSC690 SET GBFD-1 GPRS Meaning: Whether to expand and optimize the
TbfExp 0 GCELL 19509 Fast downlink GPRS RLC window. If this parameter is set
andOp PSOTH Transmi to 64 or larger, the downlink GPRS RLC window will
ERPAR ssion be expanded, and the parameter value indicates the
A window size after the expansion. If this parameter is
set to a value less than 64, the downlink GPRS RLC
window is not expanded. That is, the window size is
still 64.
GUI Value Range: 0~127
Unit: None
Actual Value Range: 0~127
Default Value: 0
DlGprs BSC691 SET GBFD-1 GPRS Meaning: Whether to expand and optimize the
TbfExp 0 GCELL 19509 Fast downlink GPRS RLC window. If this parameter is set
andOp PSOTH Transmi to 64 or larger, the downlink GPRS RLC window will
ERPAR ssion be expanded, and the parameter value indicates the
A window size after the expansion. If this parameter is
set to a value less than 64, the downlink GPRS RLC
window is not expanded. That is, the window size is
still 64.
GUI Value Range: 0~127
Unit: None
Actual Value Range: 0~127
Default Value: 0
EarlyT BSC690 SET GBFD-1 Early Meaning: Whether the BSC supports early TBF
BFEst 0 GCELL 19503 TBF establishment. When this parameter is set to "ON", the
PSBAS Establis uplink TBF can be established at an early time when
E hment the MS does not have any data to transmit on the
uplink.
GUI Value Range: OFF(OFF), ON(ON)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(OFF)
EarlyT BSC691 SET GBFD-1 Early Meaning: Whether the BSC supports early TBF
BFEst 0 GCELL 19503 TBF establishment. When this parameter is set to "ON", the
PSBAS Establis uplink TBF can be established at an early time when
E hment the MS does not have any data to transmit on the
uplink.
GUI Value Range: OFF(OFF), ON(ON)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(OFF)
EXTUT BSC690 SET GBFD-1 PS Meaning: Whether to send the Dummy message
BFNOD 0 GCELL 19508 Uplink during the deactivated period of the extended uplink
ATA PSBAS GBFD-1 DTX TBF.
E 19203 Extende GUI Value Range: SEND(SEND),
d Uplink NOTSEND(NOTSEND)
TBF Unit: None
Actual Value Range: SEND, NOTSEND
Default Value: SEND(SEND)
EXTUT BSC691 SET GBFD-1 PS Meaning: Whether to send the Dummy message
BFNOD 0 GCELL 19508 Uplink during the deactivated period of the extended uplink
ATA PSBAS GBFD-1 DTX TBF.
E 19203 Extende GUI Value Range: SEND(SEND),
d Uplink NOTSEND(NOTSEND)
TBF Unit: None
Actual Value Range: SEND, NOTSEND
Default Value: SEND(SEND)
DNTBF BSC690 SET GBFD-1 GPRS Meaning: Delay of releasing the downlink TBF. After
RELDE 0 GCELL 14101 the last downlink RLC data block is transmitted on the
LAY PRIVA network side and all the transmitted downlink data
TEOPT blocks are received, the MS is not informed to stop
PARA this downlink TBF. Instead, the state of the last data
block is forcibly set to "not received" and the last data
block with the RRBP flag is retransmitted
continuously so that the downlink TBF is not released.
During the downlink delay release, if the upper layer
of the network side needs to transmit downlink data,
the downlink RLC block for unpacking can be
transmitted in the downlink TBF for delay release.
The state of the downlink TBF is changed from delay
releasing to downlink transmitting. In addition, the
MS must respond to the Packet Downlink Ack/Nack
message through the uplink data block of the RRBP to
exchange messages with the network side. When the
MS needs to send data, the MS can send the uplink
request to the network sides through the Packet
Downlink Ack/Nack with the channel request
description. If this parameter is set to 0, the release
delay of downlink TBF is disabled.
GUI Value Range: 0~12000
Unit: ms
Actual Value Range: 0~12000
Default Value: 2400
DNTBF BSC691 SET GBFD-1 GPRS Meaning: Delay of releasing the downlink TBF. After
RELDE 0 GCELL 14101 the last downlink RLC data block is transmitted on the
LAY PRIVA network side and all the transmitted downlink data
TEOPT blocks are received, the MS is not informed to stop
PARA this downlink TBF. Instead, the state of the last data
block is forcibly set to "not received" and the last data
block with the RRBP flag is retransmitted
continuously so that the downlink TBF is not released.
During the downlink delay release, if the upper layer
of the network side needs to transmit downlink data,
the downlink RLC block for unpacking can be
transmitted in the downlink TBF for delay release.
The state of the downlink TBF is changed from delay
releasing to downlink transmitting. In addition, the
MS must respond to the Packet Downlink Ack/Nack
message through the uplink data block of the RRBP to
exchange messages with the network side. When the
MS needs to send data, the MS can send the uplink
request to the network sides through the Packet
Downlink Ack/Nack with the channel request
description. If this parameter is set to 0, the release
delay of downlink TBF is disabled.
GUI Value Range: 0~12000
Unit: ms
Actual Value Range: 0~12000
Default Value: 2400
8 Counters
9 Glossary
10 Reference Documents
1. 3GPP TS 43.064: "Overall description of the GPRS Radio Interface; Stage 2"
2. 3GPP TS 48.018: "BSS GPRS Protocol (BSSGP)"
3. 3GPP TS 44.060: "Radio Link Control/Medium Access Control (RLC/MAC) protocol"
4. 3GPP TS 44.018: "Radio Resource Control (RRC) protocol"