Gprsegprs Overview
Gprsegprs Overview
GPRS/EGPRS Overview
Feature Parameter Description
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 commercial contract made between
Huawei and the customer. All or partial products, services and features described in this document may not
be within the purchased scope or the usage scope. Unless otherwise agreed by 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 the warranty of any kind, express or implied.
Contents
1 Introduction............................................................................... 1-1
1.1 Scope........................................................................................................................................... 1-1
1.2 Intended Audience........................................................................................................................ 1-1
1.3 Change History............................................................................................................................ 1-1
2 Overview................................................................................... 2-1
3 Technical Description.................................................................3-1
3.1 Networking Configuration............................................................................................................. 3-1
3.1.1 Overview.............................................................................................................................. 3-1
3.1.2 Gb Interface......................................................................................................................... 3-3
3.1.3 Pb Interface......................................................................................................................... 3-6
3.2 Definitions.................................................................................................................................... 3-9
3.2.1 Modulation and Coding Schemes........................................................................................3-9
3.2.2 Packet Data Logical Channels........................................................................................... 3-13
3.2.3 Radio Link Control Modes................................................................................................. 3-15
3.2.4 Network Operation Modes................................................................................................. 3-16
3.2.5 Packet System Information................................................................................................ 3-16
3.3 System Procedures.................................................................................................................... 3-17
3.3.1 Packet Access................................................................................................................... 3-17
3.3.2 Radio Resource Allocation................................................................................................. 3-18
3.3.3 TBF Resource Assignment................................................................................................ 3-19
3.3.4 EGPRS Link Quality Control.............................................................................................. 3-20
3.3.5 Paging............................................................................................................................... 3-21
3.3.6 Timing Advance................................................................................................................. 3-22
3.3.7 Flow Control...................................................................................................................... 3-22
3.3.8 PS QoS.............................................................................................................................. 3-23
3.3.9 PS Power Control.............................................................................................................. 3-24
3.3.10 Cell Reselection Control.................................................................................................. 3-25
3.3.11 Idle Timeslot Assignment................................................................................................. 3-25
4 Parameters................................................................................ 4-1
5 Counters...................................................................................5-1
6 Glossary.................................................................................... 6-1
7 Reference Documents................................................................7-1
Document Issues
The document issues are as follows:
01 (2010-06-30)
Draft (2010-03-30)
01 (2010-6-30)
This is the first release of GBSS12.0.
Compared with issue Draft (2010-03-30) of GBSS12.0, issue 01 (2010-06-30) of GBSS12.0
incorporates the changes described in the following table.
Editorial change Parameters are presented in the form of Parameter ID instead None.
of Parameter Name.
GSM BSS
1 Introduction GPRS/EGPRS Overview
Draft (2010-03-30)
This is the draft release of GBSS12.0.
Huawei BSS supports only EGPRS. Unless otherwise specified, EDGE mentioned in this document indicates EGPRS.
GPRS provides MSs with high-speed packet data services. It prolongs the life expectancy of GSM,
enhances the utilization of radio resources. It can smoothly evolve to the 3G network and thus
effectively secure the investment of the operators.
By using new modulation and coding schemes, EDGE increases the data rates by about three times on
the Um interface and meets the requirements of high-speed data services.
3 Technical Description
3.1 Networking Configuration
3.1.1 Overview
With GPRS support nodes (GSNs) and packet control units (PCUs), the GPRS can be implemented in
the GSM system through software upgrade. There are two GPRS networking modes: with external
PCUs and with built-in PCUs.
The components of the GPRS network are as follows:
Serving GPRS support node (SGSN)
Gateway GPRS support node (GGSN)
Border gateway
Charging gateway
HLR/AUC
PCU
BSC
BTS
DNS
Firewall
Huawei BSC supports both built-in PCU and external PCU. This enables flexible network deployment
according to actual requirements.
When built-in PCUs are used for networking, the number of DPUd boards and Gb interface boards is
determined by GPRS traffic volume. Figure 3-1 shows the GPRS network topology with built-in PCUs.
GSM BSS
3 Technical Description GPRS/EGPRS Overview
PSTN
MSC HLR
Abis
BTS A
BSC
Gs Gr Gc
Gb Gn
Abis A
Gb SGSN GGSN
BTS
BSC PDN
PSTN
MSC HLR
Abis
BTS A
BSC
A Gs Gc
Gr
Pb
Gb Gn
Abis Pb
Pb
SGSN GGSN
PCU
Gb
BTS
Pb
BSC PDN
PCU
3.1.2 Gb Interface
This section describes the feature GBFD-119001 Gb Interface Function.
The Gb interface is an interface between the SGSN and the BSS. On this interface, the SGSN
communicates with the BSS and the MS and performs packet data transfer, mobility management, and
session management. The Gb interface is a standard interface. It is mandatory for the GPRS network.
Figure 3-3 shows the protocol stack of the Gb interface.
SGSN
GMM/SM
BSC LLC
BSSGP BSSGP
NS NS
FR/IP FR/IP
Gb interface
If ISNCMODE is set to Static Configuration, the BSC searches a remote NSVL list for the IP path to the SGSN.
If ISNCMODE is set to Dynamic Configuration, the BSC accesses the SVRIP through the specified UDP port No. to
obtain the signaling address and port number of the SGSN and then the IP path to the SGSN.
The BVC is a virtual connection between BSSGP entities. There are point-to-point BSSGP virtual
connections (PTPBVCs), point-to-multipoint BSSGP virtual connections (PTMBVCs), and signal
BSSGP virtual connections (SIGBVCs) between BSSGP entities. The PTPBVC and PTMBVC transmit
user data, and the SIGBVC transmits signaling messages. Each NSE is allocated an SIGBVC. The
BVC is associated with the NSE through NSEI.
P
E E1/T1
BSC
U
a
SGSN
Figure 3-5 shows the connection between the BSC and the SGSN through the FR network.
Figure 1.2 Network connection in Gb over FR mode
P
E E1/T1 Frame relay network E1/T1
BSC
U
a
SGSN
If the physical layer of the Gb interface uses the IP protocol, the BSC and the SGSN can be connected
directly or through an IP network.
Directconnection in Gb over IP mode means that the BSC and the SGSN are connected without any
intermediate IP network. In this connection, switches can be used to provide layer 2 switching
services for the BSC and SGSN. Figure 1.3 shows the direct connection in Gb over IP mode.
Figure 1.3 Direct connection in Gb over IP mode
F
G FE/GE
BSC 2
a
SGSN
Network connection in Gb over IP mode means that the BSC and the SGSN are connected through
an IP network. In this connection, routers can be used to provide layer 3 routing services for the BSC
and SGSN. Figure 3-7 shows the network connection in Gb over IP mode.
Figure 1.4 Network connection in Gb over IP mode
F
G FE/GE FE/GE
BSC IP netwrok
2
a
Router Router
SGSN
Compared with FR networking, IP networking greatly increases the bandwidth on the Gb interface and
protects the investment in network construction, operation, and maintenance.
3.1.3 Pb Interface
The Pb interface is a nonstandard interface between the PCU and the BSC. It is used only with external
PCU. The Pb interface manages shared resources such as cells, packet channels, E1 trunks, and
system information between the PCU and the BSC. In addition, the Pb interface supports dynamic
channel conversion and network access from the CCCH. The BTS is connected to the PCU through the
BSC. The links between the PCU and the BSC consist of signaling links and traffic links.
Figure 3-8 shows the protocol stack of the Pb interface.
BSC PCU
RR
APP
PbIP
LAPD LAPD
Layer 1 Layer 1
Pb
PCIC circuits can be blocked, unblocked, and reset on the PCU side. The status of PCIC circuits on
the BSC side is not affected.
If a PCIC circuit is blocked on the PCU LocalWS, the BSC cannot unblock this circuit.
Radio resource management
Radio resource management on the Pb interface refers to the management of the radio resources
only related to PS services. Information about the radio resources of the PCU is obtained from the
BSC. The procedure consists of three steps:
The cells on the BSC side and those on the PCU side are reset.
The radio resource configuration for PS services in each cell is sent by the BSC to the PCU.
Packet system information (PSI) is broadcast.
CS services and PS services share radio resources, which are allocated on demand. CS services
take priority over PS services in resource allocation. Allocation on demand enables the BSC to
allocate radio resources between CS services and PS services in real time based on actual
requirements. This means a dynamic conversion between TCH and PDTCH. The channel conversion
procedures on the Pb interface are classified into the following types:
When the PDTCHs are insufficient for PS services, the PCU requests the BSC to convert some
TCHs into PDTCHs. The BSC accepts or rejects the request based on the number of available
TCHs. If there are many idle TCHs, the BSC accepts the request, performs channel conversion, and
instructs the BTS to modify the channel attributes.
When the TCHs are insufficient for CS services, the BSC requests the PCU to release some
PDTCHs and converts them into TCHs. This request must be accepted to ensure the QoS of CS
services.
When the PCU finds that there are excessive PDTCHs, it automatically releases the PDTCHs for
conversion to TCHs. This ensures the QoS of CS services.
The BSC is responsible for allocating TCHs, and the PCU is responsible for allocating PDTCHs. After
a TCH is converted into a PDTCH, the assignment and release of the PDTCH are determined by the
PCU. The assignment and release of the TCH are still determined by the BSC.
The status of radio resources on the BSC side should be consistent with that on the PCU side. To
ensure the consistency, the BSC needs to notify the PCU of the change in the BTS and the impact of
operation and maintenance on the radio resource status. For example, after a packet channel is
blocked, the BSC instructs the PCU to update the status of the channel.
PS service access support
To support GPRS, System Information 13 (SI13) needs to be broadcast on the BCCH. In addition, SI3
and SI7 need to be modified to include relevant GPRS information such as GPRS Indicator. Based on
the system information, the MS decides whether and how to access the network in the serving cell to
request PS services.
If no PCCCH is configured in the serving cell, the MS requests PS services through a CCCH. The MS
can request PS services through one or more of following procedures:
MS originated packet access
MS terminated packet access
Suspension and restoration of PS services of class-B MSs
Transmission management
When converting a TCH into a PDTCH, the BSC connects the trunk circuits on the Abis interface with
those on the Pb interface. When converting a PDTCH into a TCH, the BSC disconnects the trunk
circuits. During transmission of packet data, the BSC forwards packets between the BTS and the
PCU. Generally, each PDTCH corresponds to a 16 kbit/s timeslot. During data transmission, if the
PCU finds that the transmission quality is satisfactory, it can use a more efficient coding scheme,
such as CS-3 or CS-4. In this case, the BSC assigns one more 16 kbit/s timeslot to the PDTCH.
Thus, the PDTCH corresponds to a 32 kbit/s timeslot.
PbSL management
A Pb signaling link (PbSL) is an LAPD link. PbSL management involves link load sharing, message
transmission, and message reception.
If no PCCCH is configured in a cell, disconnection of all PbSLs or recovery of any disconnected PbSL
leads to a change in the status of a cell on the PCU side.
3.2 Definitions
3.2.1 Modulation and Coding Schemes
GPRS uses the gaussian minimum shift keying (GMSK) modulation scheme and supports CS-1 to CS-
4 coding schemes. EGPRS uses the 8PSK modulation scheme and supports MCS-1 to MCS-9 coding
schemes. The peak rate of EGPRS is about three times that of GPRS. Figure 3-9 shows the rates of
GPRS channels and those of EGPRS channels.
Figure 1.1 Rates of GPRS channels and those of EGPRS channels
kbit/s
59.2
60.0
54.4
GPRS
50.0
44.8
EGPRS
40.0
29.6
30.0
22.4
20.2
20.0 17.6
14.4 14.8
12.2 11.2
8.0 8.8
10.0
0.0
CS-1 CS-2 CS-3 CS-4 MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9
GMSK 8PSK
modulation modulation
Modulation Scheme
GMSK uses signal phase changes to represent symbols. Each symbol is mapped to one bit, namely 0
or 1.
8PSK uses absolute signal phases to represent symbols. Each symbol is mapped to three bits, and
there are eight possible symbols. Therefore, the theoretical peak rate on the Um interface in EGPRS is
three times that in GPRS.
Figure 3-10 shows the I/Q diagrams for GPRS GMSK and EGPRS 8PSK.
Figure 1.1 I/Q diagrams for GPRS GMSK and EGPRS 8PSK
GPRS: EGPRS:
GMSK modulation 8PSK modulation
Q Q
(0,1,0)
(0,0,0) (0,1,1)
1
(0,0,1)
I I
(1,1,1)
0
(1,0,1) (1,1,0)
(1,0,0)
In terms of network operation, the transceiver for EGPRS must have the same spectrum features as an
ordinary transceiver. Thus, when sending the signals modulated by 8PSK, the transceiver for EGPRS
uses the transmit power that is 2-5 dB less than the average power in GMSK modulation. This is
implemented in the BSS through the parameter CELL8PSKPOWERLEVEL. The default value of this
parameter is 0.
The data rates of CS-1 and CS-2 are fairly slow. To address the needs of higher data rates, Huawei
provides the CS-3 and CS-4 schemes for the GPRS. The CS-3 and CS-4 schemes provide the
transmission rate of 15.6 kbit/s and 21.4 kbit/s respectively for data including the head of the RLC
block. In addition, the CS-3 and CS-4 schemes have higher requirements for C/I. During the data
transmission, the BSC dynamically adjusts the channel encoding/decoding scheme according to the
retransmission rate of the RLC data blocks transmitted on the uplink TBF and downlink TBF. This
increases the transmission rate on the basis of guaranteed transmission quality and maximizes the use
of radio resources (GBFD-118901 CS-3/CS-4).
The coding schemes initially used for a GPRS service are specified by UPDEFAULTCS and
DNDEFAULTCS. Whether the coding schemes can be dynamically adjusted on the basis of signal
qualities during the GPRS service processing is specified by UPFIXCS and DNFIXCS. If the GPRS
coding schemes can be dynamically adjusted on the basis of signal qualities, the retransmission rate of
temporary block flows (TBFs) is used as the adjustment trigger.
For uplink GPRS, if the signal quality is good and the TBF retransmission rate is lower than the
predefined threshold, the GPRS coding schemes are adjusted to high-rate coding schemes. The
involved parameters are as follows:
UPTHDCSUPGRADE1
UPTHDCSUPGRADE2
UPTHDCSUPGRADE3
For uplink GPRS, if the signal quality is poor and the TBF retransmission rate is higher than the
predefined threshold, the GPRS coding schemes are adjusted to low-speed coding schemes. The
involved parameters are as follows:
UPTHDCSDEGRADE1
UPTHDCSDEGRADE2
UPTHDCSDEGRADE3
For downlink GPRS, if the signal quality is good and the TBF retransmission rate is lower than the
predefined threshold, the GPRS coding schemes are adjusted to high-rate coding schemes. The
involved parameters are as follows:
DNTHDCSUPGRADE1
DNTHDCSUPGRADE2
DNTHDCSUPGRADE3
For downlink GPRS, if the signal quality is poor and the TBF retransmission rate is higher than the
predefined threshold, the GPRS coding schemes are adjusted to low-speed coding schemes. The
involved parameters are as follows:
DNTHDCSDEGRADE1
DNTHDCSDEGRADE2
DNTHDCSDEGRADE3
For 544 + 48 and 272 + 24 in Table 3-2, 544 and 272 indicate the numbers of significant bits, and 48 and 24 indicate the
numbers of padding bits.
The coding schemes initially used for an EGPRS service are specified by UPDEFAULTMCS and
DNDEFAULTMCS. Whether the MSC coding schemes can be adjusted during the EGPRS service
processing is specified by UPFIXMCS and DNFIXMCS. If the MCS coding schemes can be adjusted,
the BSS notifies the MS of BEPPERIOD when sending system information. The MS calculates the
downlink bit error probability (BEP) and notifies the BSS of the result in the measurement report. Then,
the BSS adjusts the uplink and downlink MCS coding schemes based on the downlink BEP.
EGPRS Priority Channel: EGPRS MSs get preference to use it. When it is idle, GPRS MSs can use
it. When an EGPRS MS requests it, the GPRS MSs that are using it must be handed over to other
channels. The EGPRS MS and the GPRS MS cannot use it simultaneously.
EGPRS Normal Channel: Both GPRS MSs and EGPRS MSs can use it.
GPRS Channel: Only GPRS MSs use it. If no EGPRS Channel is available in a cell, EGPRS MSs
can be provided with only GPRS services.
The PDTCH on an EDGE-unsupported TRX can be configured only as a GPRS Channel.
For different services, the preferred channel types are different:
ForGPRS services, the preferred channel types are firstly the GPRS Channel, secondly the EGPRS
Normal Channel, and thirdly the EGPRS Priority Channel.
For EGPRS services, the preferred channel types are firstly the EGPRS Special Channel, secondly
the EGPRS Priority Channel, and thirdly the EGPRS Normal Channel.
Thus, the GPRS MS and EGPRS MS may use the same EGPRS Normal Channel for uplink
transmission and downlink transmission respectively. Such multiplexing can be avoided through the
parameter FORBIDEDGU. To avoid such multiplexing completely, do not configure the EGPRS Normal
Channel.
The use of a channel depends on the type of the channel. For example, if a channel on an EGPRS-supported TRX is
configured as a GPRS Channel, this channel can be used for only GPRS services. The EGPRS Special Channel can be
configured only as static channels. The other three types of channels can be configured as static or dynamic channels.
PDCCHs are classified into packet timing advance control channel (PTCCH) and packet associated
control channel (PACCH):
The PTCCH is used to control the timing advance of the MS.
The PACCH carries signaling messages, including acknowledgment messages and power control
messages. The PACCH also carries resource assignment and reassignment messages, which are
used to assign a capacity to a PDTCH or a new PACCH. One or more PDTCHs of an MS share the
same PACCH.
Combination Application
Number Combination Type Condition Description
Combination 3 PDTCH + PACCH + None. This combination is
PTCCH used to transmit uplink
and downlink packet
data. One cell can be
configured with more
than one Combination
3.
If the external PCU is configured, channels are classified into static packet channel, speech channel,
and dynamic packet channel.
Static packet channel
The static packet channel is used to broadcast the GPRS packet system information (PSI) and
transmit packet data. It cannot be used for CS services. The channel types include PBCCH+PDTCH,
PCCCH+PDTCH, or PDTCH.
Speech channel
The speech channel is dedicated for speech services. The channel types include TCH, BCCH, and
SDCCH.
Dynamic packet channel
The dynamic packet channel is initially a TCH and can be dynamically converted into a PDCH.
If the built-in PCU is configured, no dynamic packet channel needs to be configured. When the
parameter CHNTYPE is set to TCH Full Rate, the parameter GPRSCHPRI needs to be set. The
maximum number of PDCHs in a cell is specified by MAXPDCHRATE.
The highest capability of a single PDCH to process PS services in a cell is specified by PDCHUPLEV
and PDCHDWNLEV.
1. When PS services are busy and the threshold UPDYNCHNTRANLEV or DWNDYNCHNTRANLEV
is exceeded, the BSC converts some available TCHs into the PDCHs.
2. When CS services are busy and they request new TCHs, the BSC converts some PDCHs into
TCHs.
In this process, CS services take priority over PS services. Thus, the QoS of CS services can be
ensured. Whether and how many dynamic channels can be preempted are specified by
DYNCHNPREEMPTLEV and DYNCHTRANRESLEV respectively. For details, see GPRS/EGPRS
Channel Management Parameter Description.
In acknowledged mode, each data block in a TBF must be acknowledged by the peer end. If the data
block is unacknowledged, it needs to be retransmitted. The TBF is released only after all the data
blocks are transmitted and acknowledged. In unacknowledged mode, the data block need not be
acknowledged by the peer end. If a data block is lost or erroneously transmitted, it is replaced with
padding bits. The TBF is released as long as all the data blocks are transmitted.
The BSC supports both acknowledged mode and unacknowledged mode at the RLC layer. For uplink
data transmission, the BSC determines the RLC mode based on the request of the MS. For downlink
data transmission, the BSC determines the RLC mode based on the type of LLC PDUs.
The network operation mode is specified by the parameter NMO. Usually, the GPRS network is not
configured with the Gs interface or PCCCH, and therefore NMO is set to Network Operation Mode II.
For the CS/PS paging procedures in different network operation modes, see 3.3.5Paging.
more information than the Packet Channel Request message. The information includes the temporary
logical link identity (TLLI), multislot capability of the MS, and radio priority. This helps assign appropriate
resources to the MS.
The capability of a cell to support packet access is specified by the parameter PRIACCTHR.
are multiplexed on the same PDCH, USF granularity 4 can be used to increase the downlink
throughput.
In extended dynamic allocation mode, the packet assignment message contains an assigned PDCH list
and USF values corresponding to the PDCHs. If the resources allocated by the network do not allow
the MS to listen to the USF values on all the assigned PDCHs, the MS listens to the USF values in the
following ways:
When the MS receives a USF value in an RLC/MAC block on a PDCH, the MS regards that the
corresponding RLC/MAC block on each PDCH following this PDCH in the list is allocated to the MS.
Thus, when allocating an RLC/MAC block on a PDCH to the MS, the network allocates the
corresponding RLC/MAC block on each PDCH following this PDCH in the list to the MS. For
example, the network allocates a list of timeslots 1, 2, and 3 to the MS. If a USF value is detected in
an RLC/MAC block on timeslot 1, the RLC/MAC blocks on timeslots 1, 2, and 3 are allocated to the
MS. If a USF value is detected in an RLC/MAC block on timeslot 2, the RLC/MAC blocks on timeslots
2 and 3 are allocated to the MS.
In an RLC/MAC block period of data transfer, the MS must listen to the USF values on all the PDCHs
from the header to the current PDCH (inclusive) in the PDCH list. For example, if the list contains
PDCHs 1, 2, and 3 and the RLC/MAC blocks are being transferred on PDCHs 2 and 3, the MS must
listen to the USF values on PDCHs 1 and 2. If the RLC/MAC blocks are being transferred on PDCH
3, the MS must listen to the USF values on PDCHs 1, 2, and 3.
The BSC supports the following assignment modes. For details, see the GPRS/EGPRS Connection
Control and Transfer Parameter Description.
Uplink packet resource assignment on the PACCH
Downlink packet resource assignment on the PACCH
Simultaneous uplink and downlink packet resource assignments on the PACCH
Uplink immediate assignment for TBF establishment on the CCCH
Downlink immediate assignment for TBF establishment on the CCCH
Basic Principle of LA
In LA mode, the sender selects the best modulation and coding schemes based on the actual radio
environment, and the receiver need not buffer the erroneous data blocks received.
Basic Principle of IR
In IR mode, the sender uses a coding scheme with high rates but weak data protection for initial data
transmission. If the data is received erroneously, the sender retransmits the data by using a different
puncturing scheme. The receiver combines the new data with the previously received data and then
performs decoding. This process is repeated until the decoding succeeds.
During uplink data transmission, the system instructs the MS to use the IR mode by including
RESEGMENT=0 (segmentation forbidden) in a packet uplink resource assignment message or uplink
packet acknowledgment message. In IR mode, the receiver should have sufficient memory to save
history information. If the memory is insufficient, the system notifies the MS of memory insufficiency by
including RESEGMENT=1 in an UPLINK ACK/NACK message.
During downlink data transmission, if the MS memory is insufficient, the MS sends "MS OUT OF
MEMORY" to the network through a downlink ACK/NACK message. Then, the network changes the
control mode to LA.
3.3.5 Paging
This section describes the feature GBFD-119112 Paging.
In the GPRS/GSM system, paging consists of PS paging and CS paging.
PS Paging
In the GPRS/GSM system, the PS paging procedure is as follows:
1. When the network needs to transmit data to an MS, the SGSN initiates PS paging to locate the MS.
The Packet Paging Request message is sent to the BSC over the Gb interface.
If the PCCCH is configured in the BSC, the Packet Paging Request message is sent on the PPCH.
If no PCCCH is configured in the BSC, the Packet Paging Request message is sent on the PCH.
If
the cell supports DTM and the paged MS is in dedicated mode, the BSC can send the PACKET
NOTIFICATION message on the DCCH. For details, see DTM Parameter Description.
2. After receiving the Packet Paging Request message, the MS initiates the uplink TBF establishment
procedure. Then, the MS sends a paging response packet to the BSC over the Um interface. The
BSC forwards the paging response packet to the SGSN. After receiving the paging response packet,
the SGSN processes it and then starts transmitting downlink data.
When external PCUs are used, BSS paging coordination is not supported.
Initial TA estimation
The BSC estimates an initial TA value based on a single access burst requesting a packet channel.
Then, the BSC sends the estimated TA value to the MS through a Packet Uplink Assignment or a
Packet Downlink Assignment message. Before the TA value is updated, the MS transmits data in the
uplink based on the initial TA.
Continuous TA update
The MS in packet transfer mode must update the TA value continuously. The TA value is transmitted on
the packet timing advance control channel (PTCCH) that is assigned to the MS.
For uplink packet transfer, the BSC sends a Packet Uplink Assignment message to the MS to assign
the timing advance index (TAI).
For downlink packet transfer, the BSC sends a Packet Downlink Assignment message to the MS to
assign the TAI.
TAI specifies the PTCCH to be used by the MS. In the uplink, the MS sends access bursts on the
PTCCH specified by the TAI. The BTS extracts the TA value from the received access bursts.
The BTS analyzes the TA value and determines a new TA value for each MS that performs continuous
TA update on the PDCH. The new TA value is sent to the MS through a downlink signaling message on
the PTCCH/D. The BSC can also send the new TA value to the MS through a Packet Power
Control/Timing Advance or a Packet Uplink ACK/NACK message on the PACCH.
3.3.8 PS QoS
This section describes the feature GBFD-119109 QoS(Best Effort).
PS QoS refers to GPRS/EGPRS QoS, that is, the qualities of GPRS/EGPRS services on the GSM
EDGE Radio Access Network (GERAN). The requirements for PS QoS are defined by QoS attributes,
including the traffic class, transfer delay, maximum bit rate (MBR), guaranteed bit rate (GBR), traffic
handling priority (THP), allocation/retention priority (ARP), and reliability.
3GPP TS 23.107 defines four traffic classes: conversational class, streaming class, interactive class,
and background class. Huawei BSC supports the last three classes and provides different QoS for
different traffic classes and PS service users.
Typical streaming services are the real-time video stream and real-time audio stream. The
characteristics of streaming services are as follows: The time sequence and delay variation between
information entities (for example, packets) of the stream should be preserved; streaming class does not
have strict requirements on transfer delay.
The interactive service is a classical data communication scheme. Typical interactive services include
web browsing, database retrieval, and server access. One of the characteristics of interactive services
is that a timely response to the request is required. Therefore, the round-trip delay time is one of the
key attributes. Another characteristic is that the content of the packets should be transferred at a low bit
error rate.
The background service is another classical data communication scheme. Typical background services
include file download and email. The characteristics of background services are as follows: The traffic is
insensitive to transfer delay; the content of the packets should be transferred at a low bit error rate.
According to the R99 specifications, the BSS and the SGSN can negotiate QoS information through the
packet flow management (PFM) procedure during the activation of the MS Packet Data Protocol (PDP)
context.
GBR QoS
For a streaming service, such as the Push to talk (PoC) service, the BSC dynamically allocates Um
resources to the MS based on the radio environment and ensures that the bandwidth is not lower than
the GBR. To ensure the real-time performance of the PoC service, the parameters POCGBRMIN and
POCGBRMAX are used to specify the required bandwidth, and the parameter POCDELAY is used to
specify the transfer delay. When the Um resources are insufficient, the BSC originates a packet flow
context (PFC) modification procedure.
Whether the GBR QoS is supported is specified by the parameter GBRQOS.
User QoS
Whether different QoS can be provided for users of different priorities is specified by the parameter
QOSOPT.
For interactive, background, and Best Effort (BE) services, the BSC sets the user priority weight based
on the traffic class, ARP, and THP, where THP is considered only for interactive services. The user
priority weight determines the number of radio blocks that can be allocated to a TBF. BE service refer to
the service of which the QoS attributes are not obtained from the BSC or the service of which the traffic
class is unknown. The radio resource allocation and scheduling of this type of service are performed on
the basis of the best effort policy. The configured user priority weight reflects the user priority. High-
priority users can obtain more radio resources and bandwidth.
For more QoS information, see GPRS/EGPRS QoS Parameter Description.
If SERVICEMODE on the Abis interface is set to IP or HDLC, there is no idle timeslot for assignment.
If Flex Abis is enabled for the BTS and the CS traffic is light, idle timeslots may not be configured and EDGE services
can still operate properly.
If Flex Abis is enabled for the BTS and the CS traffic is heavy, idle timeslots should be configured. Otherwise, EDGE
services may fail for a long time.