Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
NETWORKS)
3rd Edition
compiled by
Hery Supriyanto
hery.supriyanto.0301@gmail.com
hery.supriyanto@yahoo.com
http://www.linkedin.com/in/herysupriyanto
these document compilation from many resource feel free to share for knowledges purpose
SDCCH drop reasons
Every time a SACCH message can not be decoded the radio link time-out
counter is decreased by 1. If the message can be decoded the counter is
incremented by 2. However, the value can not exceed the initial value. The
initial value is set by the parameter RLINKT for radio link time-out in the
mobile station and by RLINKUP for timeout in the BSC. If the mobile moves
out of coverage and no measurement reports are received in the BSC, there
will be a radio link time-out and the message Channel Release (cause:
abnormal release, unspecified) is sent to the mobilestation and the SACCH is
deactivated in the BTS. A Clear Request message is sent to the MSC. To be
sure that the mobile has stopped transmitting, the BSC now waits RLINKT
SACCH periods before the timeslot is released and a new call can be
established on the channel.
2. Layer 2 Time-Out
If the BTS never get an acknowledge on a Layer 2 message after the time
T200XN200, the BTS will send Error Indication (cause: T200 expired) to the
BSC, which will send Channel Release (cause: abnormal release, timer
expired) to the mobilestation and a Clear Request to the MSC. The SACCH is
deactivated and the BSC waits RLINKT SACCH periods before the timeslot is
released and a new call can use the channel. This is only valid if the call is in
steady state, i.e. not during handover or assignment.
3. Release Indication
When the BTS received a layer 2 DISC frame from the mobile it replies with a
Layer 2 UA frame to the mobile station and a Release Indication to the BSC.
The system does only react on Release Indication if it is received during a
normal disconnection situation. If such a message is received unexpectedly
this will usually cause radio link time-out or timer T200 expiration as the
mobilestation stops the transmitting of measurement reports. It is also
possible that the release will be normal depending on when the Release
Indication is received.
4. MSC Time-Out
Normal Release:
If the MSC never received a response on a message (e.g. Identity Request)
and there is no radio link time-out or layer 2 time-out, the MSC will send a
Clear Command to the BSC. The time-out is depending on the message.
When receiving Clear Command, the BSC will send a Channel Release (cause:
normal release) and then deactivates the SACCH.
Reject (only SDCCH):
If the MSC never receives a response on the first message after Establish
Indication, the MSC will send a reject message. If the connection was a
Location Update it will be a Location Update Reject (cause: network failure)
and if the connection was a mobile originating call (CM Service Request) a
CM Service Reject (cause: network failure) will be sent. The MSC will then
send a Clear Command to the BSC and the call is cleared by Channel Release
(cause: normal release).
5. Assignment to TCH
Before sending an Assignment Command from the BSC at TCH assignment,
the following two criterion have to be fulfilled:
a. There must be a TCH channel available, i.e. no congestion
b. The locating algorithm must have received at least one valid measurement
report.
If either of the criterion is not fulfilled, Assignment Command will not be sent
and a Channel Release (cause: abnormal release, unspecified) will be sent to
the mobilestation and a Clear Request to the MSC.
Mobile Error
Some old mobiles may cause dropped calls if certain radio network features
are used. Another reason is that the MS is damaged and not working
properly.
Action: Check MS fleet.
Solution: Inform operator.
Subscriber Behavior
Poorly educated subscribers could use their handsets incorrectly by not
raising antennas, choosing illadvised locations to attempt calls, etc.
Action: Check customer complaints and their MS.
Battery Flaw
When a subscriber runs out of battery during a conversation, the call will be
registered as dropped call due to low signal strength or others.
Action: Check if MS power regulation is used. Check if DTX uplink is used.
Congestion on TCH
The SDCCH is dropped when congestion on TCH.
Action: Check TCH congestion
Solution: Increase capacity on TCH or using features like Assignment to
another cell, Cell Load Sharing, HCS, Dynamic Half-Rate Allocation and FR-HR
Mode Adaptation etc
Probable Reason:
1) No dominant serving cell: The serving cell cannot cope with the TCH
traffic.
2) Severe congestion on TCH: Failing TCH allocation for assignment or
handover due to congestion
3) Low signal strength for call access: The signal strength might be higher on
the BCCH than on the TCH.
4) Interference: Disturbance on SDCCH or target TCH
5) Faulty transceiver: Faulty equipment
The following procedure should be performed for TCH Assignment analysis:
For TCH assignment success rate, the first thing, check the TCH Time Congestion.
If there is congestion on TCH, it is recommend doing the dimensioning and adding TRU based
on carried TCH traffic demand.
If there is no congestion on TCH, check the output power of the BTS. If the output power is
low, increase the output power.
If the output power is ok, check the faulty BTS by extracting BTS error log.
If hardware fault found, swap or repair HW.
Perform drivetests to check the coverage and received RxLEV.
If no dominant cell or similar signal strengths of a few cells found during drivetests, it is
recommended to add BTS.
If there is no problem on the dominant cell, check the interference whether co-channel or
adjacent channel.
Check the disturbance whether it is on SDCCH or target TCH. If disturbance found, improve
the frequency plan.
Mostly, the problems of low TCH assignment are TCH availability and interference.
---Low Availability
Action: Check SDCCH Availability. Check if the channels are manual, control
or automatic blocked.
---HW faults.
Action: Check BTS error log.
---Congestion
A high congestion might lead to dragged calls (handover performed at a not
intended location) and a lot of unsuccessful handovers.
Action: Check TCH congestion.
Ping Pong handover is shown from the successful handover back to old cell
within pre-defined time of total handover, e.g. less than 10 seconds. Since
not all BSS vendors provide such performance counters it might be identified
by simple metric that shall be expressed as total successfulhandover over
number of call or connection, e.g. more than 200% indicates ping pong
handover.
The actual ping pong handover is easily identified through drive test with
sense of optimization engineer without require any calculation. Coverage
holes might lead to Ping-Ponghandover especially for slow moving mobiles. It
may be cause by shadowing by high building. Several possible equal signals
from two or more base stations might lead to Ping-Ponghandover as well
which is so called not optimized cell dominance.
The following action items shall be used for optimization solutions:
• Check the parameter setting such as hysteresis, offset, priority layer in
dual-band case, etc. If poor parameters setting found, then correct the
related parameters. Compare to default parameters design.
• Check the output power BSPWR and BSPWRT which normally put on
maximum value or compare to design.
• Check path balance on transceiver link, e.g. loss in uplink and downlink
chain. Defective RF modules might be the reason of imbalanced link.
• Check the site location such as possible coverage holes or no dominant
cells.
• Perform drive test on that particular area to check the signal strength, if the
average of signal strength of the neighbors are the same, no dominant cell is
found.
• For Long term action if no dominant cell shall be adding new site, while short
term action shall be uptilt the most dominant cell as the serving cell for that
area and reduce coverage for others.
Drive Testing
Drive testing can take place during the day or at night and is dependant upon
the
Operator’s requirements and subscriber habits.
Drive testing during the day will mimic the conditions as seen by subscribers,
but may
clog up the network if call analysis is being performed.
Drive testing during the night will allow a greater area to be surveyed due to
the reduction
in vehicular congestion. It will also allow for certain test signals to be
transmitted and
tested, particularly when setting up a new site, without interrupting normal
operation.
However, night-time testing does not mimic the conditions experienced by
subscribers.
For planning purposes, drive testing is typically performed at night and for
maintenance
purposes, drive testing is performed during the day.
Layer 1 Messages
Other Layer 1 criteria that is useful for field measurements include:
C1 criteria •
ARFCN of Serving Cell - (TCH in dedicated mode, BCCH in idle mode)) •
Time Slot (TS) •
Layer 3 Messages
All Layer 3 messages should be collected where possible. Layer 3 Messages
are used by
Analysts to determine more accurately the cause of a problem within the
network.
Some field test equipment can perform basic analysis of particular Layer 3
messages
during data collection. This enables certain conditions such as call
classification or
handovers to be flagged to the survey technician.
Call Classification
In principle there are five call classifications, some of which can be sub-
divided further.
Good Calls: These are calls that are successfully placed on the network and
maintained
for the required duration.
Dropped Calls: These are calls that are successfully placed on to the network
but are
terminated without authorisation. Using Layer 3 Messages, these calls can be
sub-divided
into:
End User Hang-up •
System Hang-up •
Other •
Blocked Calls: These are calls that cannot be placed on to the network. Again,
using
Layer 3 messages, these can be sub-divided as follows:
System Busy •
End User Engaged •
No Service •
Other •
Roamed Calls: These are calls that are successfully placed on another
network. Roamed
calls may also be good calls or dropped calls.
Noisy Calls: These are calls which have been successfully completed for the
duration of
the call but which experienced a number of noise bursts that a subscriber
may find
intolerable. The threshold for determining the level of poor audio is
programmed during
the set-up of the test.
In GSM, this particular classification is very difficult to determine with great
accuracy. It
should be noted that it is not enough to monitor just the RxLEV and the
RxQUAL.
Troubleshooting
No Data Collected
Occasionally, the equipment fails to trigger the collection device to save the
data to file.
Check • all cables
Ensure the Processing Unit is powered •
Re-start the laptop computer •
Re-start the equipment •
Re-drive the test. •
Dropped Calls
Handover Problems
Handover problems are generally caused by inaccurate settings of the
handover boundary.
This can cause ping-ponging, where the server will keep changing, and
congestion at the
switch. Check the following.
The transceiver antenna is fitted correctly •
Collection of Layer 3 Messages •
Collection of Neighbour Cell List (BA Table) •
Collection of Scanning Information •
Collection of Cell Identities •
Collection of T.Adv for the Serving Cell •
Also, ensure that the collection of data from the new serving cell immediately
after the
handover has occurred (particularly RxLEV and RxQUAL) is not timed to occur
prior to
the-synchronisation of the transceiver itself.
If a particular serving cell can be isolated as a potential cause of handover
problems,
slowly drive around the cell in a radius of around 500m - 1km, checking when
handovers
occur.
Blocked Calls / System Busy
If calls are repeatedly classified as blocked, it is recommended that the drive
test is
temporarily halted in order to try and locate the cause.
Check that the number called is fully functional •
Check that there is adequate coverage from the expected serving BTS •
Check the equipment transceiver is functioning correctly by using an
ordinary •
mobile to call the office
If all appears functional, try to place calls through an alternative BTS. If
this •
succeeds, inform the office immediately and re-suspend the drive test.
T3124: This timer is used in the seizure procedure during a hand-over, when
the two cells are not synchronized.Its purpose is to detect the lack of answer
from the network to the special signal. Its value is set to 675 ms if the
channel type of the channel allocated in the HANDOVER COMMAND is an
SDCCH (+ SACCH); otherwise its value is set to 320 ms.
T3130:This timer is started after sending the first UPLINK ACCESS message
during a VGCS uplink access procedure.It is stopped at receipt of a VGCS
ACCESS GRANT message.At its expiry, the uplink access procedure is
aborted.The value of this timer is set to 5 seconds.
T3110:This timer is used to delay the channel deactivation after the receipt
of a (full) CHANNEL RELEASE. Its purpose is to let some time for
disconnection of the main signalling link. Its value is set to such that the DISC
frame is sent twice in case of no answer from thenetwork. (It should be
chosen to obtain a good probability of normal termination (i.e. no time out of
T3109) of the channel release procedure.)
T3142:The timer is used during packet access on CCCH, after the receipt of
an IMMEDIATE ASSIGNMENT REJECT message. Its value is given by the
network in the IMMEDIATE ASSIGNMENT REJECT message.
T3113:This timer is started when the network has sent a PAGING REQUEST
message and is stopped when the network has received the PAGING
RESPONSE message. Its value is network dependent. NOTE: The value could
allow for repetitions of the Channel Request message and the requirements
associated with T3101.
T3115:This timer is used for the repetition of the VGCS UPLINK GRANT
message during the uplink access procedure. Its value is network dependent.
NOTE: This timer may be set to such a low value that the message is in fact
continuously transmitted.
6. The MSC allocates a voice circuit on one the digital trunks between the
MSC and the BSS.
7. MSC informs the BSS about the allocated voice circuit. The call is also
switched from signaling to voice.
8. The BSS notifies the Mobile about the changeover to voice mode.
9. The MSC routes the call and sends the call towards the called
subscriber.
10. The PSTN indicates to the MSC that it has received all the digits and the
called subscriber is being rung.
11. The MSC informs the mobile that the called subscriber is
beingalerted via a ring.
12. The called subscriber answers the call.
GSM identities
The GSM network is complex and consists of the Switching System (SS) and
the Base Station System (BSS). The switching system, which consists of HLR,
MSC, VLR, AUC and EIR, interfaces both the Base Station System and also
other networks like PSTN/ISDN, data networks or other PLMNs.
In order to switch a call to a mobile subscriber, the right entities need to be
involved. It is therefore important to address them correctly. The numbers
used to identify the identities in a GSM/PLMNnetwork is described in this
chapter. See also Figure 56.
Numbering plans are used to identify different networks. For a telephone
number in the PSTN/ISDN network, numbering plans E.164 is used.
1. Excessive TA
2. Low Signal Strength
3. Bad Quality
4. Sudden Drop
As named, stright forward meaning for the dropped call is described for the
first three items. However, Sudden Drop is quite not easy to understand.
Sudden Loss are drops that have not been registered as bad quality, signal
strength, timing advance. The term Sudden Loss is used because if the
network cannot establish a connection with the lost MS after a pre-defined
period, the sudden loss counter is incremented if the last reported
measurement from the MS does not fulfill any of the reasons mentioned.
• Handover Lost.
• BTS HW faults.
• Synchronization or Abis link fault (transmission faults).
• MS Faults.
SMS is a service that allows subscribers to send short messages (up to 160
characters) to other mobile subscribers. Rather than having to set up a call
on a traffic channel, SMS uses spare capacity on the Standalone Dedicated
Control Channel (SDCCH).
GSM Interfaces
TENTANG SATUAN dB
The decibel (dB) represents a logrithmic ratio between two quantities and
is unitless. If the ratio is refered to a specific quantity this is indicated by a
suffix (dBm is referenced against 1 mW and dBV is 1 Volt).
Originally the dB was for power ratios, given by dB=10 log (P1/P2)
dBm = The Gain of the Antenna Output signal compared to one milli volt.
notice where the "output" is in each sentence.
dBi is relative.
we like to know the optimum value for T200 on LAPDm. All vendors have different
default values (Siemens 145 ms, Nokia 220 ms, Satellite Abis 400 ms etc.) for this
timer - but which value is the best to reduce SDCCH drops and to keep the
retransmissions at an acceptable level ?
Example: SDCCH/8
During a 51er multiframe the SDCCH/8 occupies four consecutive TDMA frames (four
bursts are sent). Than the MS / BTS has to wait for the next 51er multiframe (i.e. 235
ms) before the next Layer 2 frame could be sent. 145 ms / 220 ms are shorter than
the 51er multiframe (235 ms) so in case of an missing acknowledgement this is always
a T200 expiry. The SDCCH drop will occur if T200 expired N200+1 times. If the T200 is
increased (for example to 500 ms) we have two 51er multiframe to get the
acknowledgement and the SDCCH drops are reduced.
The Qos Stats show a clear & strong corelation between the KPI and the parameter T200. That's
amazing !
Regarding the Ack from the BTS, I'm not sure (and I'm tired to look in the 3GPP
specs :) ). Take the subchannel "0" from the SDCCH ts.
in DL : the BTS sends SDCCH/0 on burst 0, 1, 2, 3 and the SACCH/0 on burst 32, 33,
34, 35
And I ***believe*** that the Lapdm acknowledgments can be sent on either the SACCH
or the SDCCH, since both of them are sent over the same LapDm link. I'm not sure at
all about this though, but it sounds logical.
The value of the SDCCH Drop due to Radio failures (in ALU) is usually around 1% in a
fairly good network. The SDCCH Drop due to Radio Failures is a counter that
encompasses both the Radio Link Timeout and the "T200*N200+1 times" failures.
I am not able to test your changes because I am not working on a live network (i am a
gsm trainer, living in a world of theory...)
Looking at those timers, I fear that the LapDm link for SDCCH is different than the
LapDm link for the SACCH of the SDCCH... I'll let you look it up though :)
Answer2:Can you verify the ciphering algo used in both External Cells? You can also
confirm this via DT. (In case of ciphering issue, handover from one side to other
should be happening. i.e. the side using higher ciphering algo will be able to
transfer the call to cell with lower ciphering algo)
Low Signal strength is one of the reason of drop call. It can be indicated by many calls
disconnected at low signal strength by subscriber, drop calls due to excessive TA, poor
handover performance and poor call setup performance.
Probable Reason
Poor BSC High LOWSSDL & LOWSSUL will
Exchange give more drop reason due to
Property SS and this might not show the
setting actual drop. It is because drop
due to SS is more priority than
Quality.
No dominant Cell might be isolated or
cell standalone.
Antenna tilt & Too much downtilt sometimes
orientation might not cover a larger area
and the subscriber might lose
the SS.
Output Power Low output power might cause
smaller border cell.
1:Identify the baseline requirement of design and BSC exchange property (setting for
LOWSSUL/LOWSSDL).
2:Check the value for LOWSSDL & LOWSSUL. If it is higher than ACCMIN, change the parameter to a
reasonable value since the drop reason will be more priority to SS compared to Quality.
3:Check the site position, antenna direction, position etc. This is to ensure the possible location is open
to interference (open water environment) or isolated. Good map is needed for this.
4:Check if the site is sectorized or Omni. If it is Omni, set the cell into sectorized cell.
5:Check if the signal strength is uplink or downlink limited. Mostly, It is designed to be downlink
limited.
6:Check the coverage cover expected area from the planet. If it is not, check the antenna tilt and
orientation. Change the direction or tilt if it is too much downtilt or pointing to a wrong direction.
7:Sometime, low output power might cause low SS. Check output power and if it is low, increase the
output power.
8:Check cell whether it has hotspots from drivetests. If found, adding new site is recommend.
9:In order to check power distribution, run Cell Traffic Recording (CTR) to that particular cell.
10:Check if the cell has indoor coverage problem. If yes, add micro site instead.
1, change the angle under directional antenna, hanging high, and the corresponding cell parameters
such as base station transmit power to change the size of coverage to achieve the purpose of regulating
telephone traffic.
2, the temporary increase in telephone traffic, can temporarily increase or decrease the carrier
frequency transmission power to change the signal coverage.
3, changing the carrier frequency is the number of residential telephone traffic is one common method
of regulation, drawn from telephone traffic small cell carrier frequency to high residential telephone
traffic.
4, using OVERLAY / UNDERLAY-level cell structure or addition of micro-cellular base stations, reducing
telephone traffic per channel.
5, the verification value to allow access to the minimum level ACCMIN, changes in coverage by cell
telephone traffic indirect adjustment.Note that this value adjustment is too large may cause blind
spots, too small may result in decreased voice quality.
6, according to the site re-election testing, adjusting cell reselection parameters CRO.
7, adjusting the switching offset and delay parameters, change the switch and the switch to bring the
border to achieve Call divert.
What is E1 and T1
The PDH (plesiochronous Digital Hierarchy) has 2 primary communication
systems as its foundation.
These are,
T1 system based on 1544kbit/s that is recommended by ANSI &
E1 system based on 2048kbit/s that is recommended by ITU-T.
Common Characteristics :-
Differing Characteristics :-
1. beware ! that operators are , looking for TRAFFIC mostly ...not just
good KPI but low traffic.
I. Definition
T3101 is the BSC timer controlling time of immediate assignment
process.
II. Format
T3101 ranges from 0 to 255s. The recommended value is 3s.
III. Configuration and Influence
In an immediate assignment process, the BSC requires BTS to
provide SDCCH to set up signaling channel. When the BSC sends a
channel activation message, T3101 starts timing. When the BSC
receives the setup instruction sent by BTS, T3101 stops timing.
When T3101 expires, the system releases corresponding SDCCH
resources. Proper configuration of T3101 reduces congestion due to
dual assignment SDCCH effectively.
The greater the T3101 is, the longer the inefficient time for using
signaling resources is. For example, if the extended transmission
delay is improperly configured (usually the sum of T and S is over
small), the MS fails in responding to the network side, so the MS
resends the random access request message.
Therefore, the network side will assign SDCCH (the network cannot
distinguish the repeated sending access request from the first
send). For better use of signaling resources, especially in activating
queue function, you must configure T3101 to a smaller value. The
minimum interval for sending channel activation message and
receiving setup indicator is 600ms. For non-overload BSS, the
maximum interval is 1.8s.
4.10.2 T3103
I. Definition
In inter- and intra-BSS handover, the BSC determines the time for
keeping TCH both in handover-originated cell and target cell. When
the time receives handover completion (intra-BSC) or clearing
(inter-BSC) message, T3103 stops.
II. Format
T3103 ranges from 0 to 255s. The recommended value is 5s.
III. Configuration and Influence
The following paragraph is an example of inter-BSS handover.
When T3103 receives the handover command, it is reset and starts
timing. When it receives clearing command, it is reset. This means
that T3103 reserves two channels when it is timing, one channel for
source BSC, and one channel for target BSC. If it is over long, two
channels are occupied for a long time and resources might be
wasted.
According to the tests, if the NSS timer is properly configured, the
handover process occurs within 5s. Therefore, the recommended
value is 5s.
4.10.3 T3105
I. Definition
See the protocol 0408 and 0858. When sending physical
information, the network starts T3105. If the timer expires before
receiving any correct frames from MS, the network resends physical
information and restarts the T3105. The maximum repeated times
is Ny1.
II. Format
T3105 ranges from 0 to 255, with unit of 10ms.
III. Configuration and Influence
The physical information is sent on FACCH. The time for sending
four TDMA in a time on FACCH is about 18ms. If the next physical
information is just sent 18ms after the first one, probably the first
physical information is still being sent. The minimum time for
sending physical information continuously and most quickly is
20ms.
IV. Precautions
T3105 is related to the timer NY1. If T3105 is small, configure NY1
to a greater value. If a handover trial fails and the T3105 of the
target cell expires for Ny times before the original cell receives the
HANDOVER FAILURE message, the target BTS sends the
CONNECTION FAILURE INDICATION message to the target BSC.
The counter of target BSC is renewed though MS might return to the
original channel. To avoid this, the T3105 must meet the following
foulard:
Ny * T3105 > T3124 + delta
Wherein, delta is the time between expiration of T3124 and
receiving HANDOVER FAILURE message by original BSC.
4.10.4 T3107
I. Definition
T3107 is a BSC timer, restricting the time for executing TCH
assignment instruction. It caters for TCH assignment of intracell
handover and channel assignment of calling.
II. Format
T3107 ranges form 0s to 255s. The recommended values are as
follows:
10s when channel resources are enough.
5s when channel resources are limited.
III. Configuration and Influence
T3107 starts after the BSC sends the ASS_CMD message to BTS. It
stops after the BSC receives the ASS_CMP or ASS_FAIL message
sent by BTS. If T3107 expires, the system judges that the MS
disconnects to the network, so the occupied resource is released to
other MSs. According to the measured statistics result of network,
the channel assignment is complete within 2s. If the BSC does not
receive ASS_CMP message after 2s, the assignment command fails.
If the radio link is bad and some information must be resent, the
process might be prolonged to 5s. To avoid premature
disconnection, configure T3107 to 10s. In this way, the MS can
reuse the original channel when handover or assignment fails.
Therefore the call drop due to intracell handover decreases or the
system service quality of re-assignment is improved (if the system
supports re-assignment function). However, the channel resource
might be wasted for several seconds. When the network capacity is
limited, you must save the resource as possible.
4.10.5 T3109
I. Definition
The BSC restricts the releasing resource of SACCH by T3109.
II. Format
T3109 ranges from 3s to 34s. The recommended T3109 is as
follows:
T3109 = a + RdioLinktimeOut x 0.480s, a = 1s or 2s.
III. Configuration and Influence
T3109 measures the time for channel releasing indicator after
sending MS clearing instructions. It starts after the BSC sends
DEACT_SACCH message to BTS. It stops after the BSC receives the
REL_INC message sent by BTS. When T3109 expires, the BSC sends
the CLEAR REQUEST message to MSC.
IV. Precautions
The sum of T3111 and T3109 must be greater than
RadioLinkTimeOut. If T3109 is over small, the corresponding radio
resources are re-allocated before RadioLinkTimeOut is due (radio
link is not released).
4.10.6 T3111
I. Definition
T3111 is a connection release delay timer, used in deactivation of
delayed channel after disconnection of major signaling link. T3111
aims to spare some time for repeated disconnections. When BSC
receives the REL_IND message sent by BTS, T3111 starts. For time
protection, T3111 stops until expiration and the BSC sends the
RF_CHAN_REL message to BTS.
II. Format
T3111 ranges from 0s to 5s.
The recommended value is 2s.
III. Configuration and Influence
After the disconnection of major signaling link, T3111 delays the
release of channels. It allows the base station to retransmit the
instruction for releasing radio channels to MS within delayed time.
After the base station sends a release request massage, the radio
resources remain for T3111 time.
If the system capacity is small, configure T3111 as short as
possible. The minimum value of T3111 is 2s, over five multiples of
the time for resending MS the instruction for releasing radio channel
resources. A greater T3111 might be of no help, but affects
congestion of SDCCH and TCH easily.
I. Definition
In a GSM network, the causes to location updating are as follows:
The MS attach.
The MS detects that its location area changes.
The network forces MS to update location periodically.
The network controls how frequent the MS updates location, and
the period for location updating is determined by the parameter
T3212.
II. Format
T3212 ranges from 0 to 255, with unit of 6 minutes (1/10 hour). If
T3212 = 1, it means that T3212 is 6 minutes. If T3212 = 255, it
means that T3212 is 25 hours and 30 minutes. If T3212 = 0, it
means that MS is not required for periodical location updating in the
cell. The recommended T3212 is 240.
III. Configuration and Influence
As an important means, the periodical location updating enables
network to connect to MSs closely. Therefore, the short the period
is, the overall service performance of the network is. Anyhow
frequent periodical location updating brings two negative aspects:
The signaling flow of the network increases sharply and the
utilization of radio resource declines. When the period is over
long, the processing capability of network elements (NE,
including MSC, BSC, and BTS) is directly affected.
The MS must transmit signals with greater power, so the
average standby time is shortened sharply.
Therefore, configure T3212 according to resource utilization in
various aspects of network.
T3212 is configured by equipment room operators. Its value
depends on the flow and processing capability of each NE.
Configure T3212 as follows:
Configure T3212 to a greater value (such as 16 hours, 20
hours, or even 25 hours) in areas with heavy traffic and
signaling flow.
Configure T3212 to a smaller value (such as 3 hours or 6
hours) in areas with low traffic and signaling flow.
Configure T3212 to 0 in areas with traffic overrunning the
system capacity.
To configure T3212 properly, you must permanently measure the
processing capability and flow of each UE in the running network,
such as:
The processing capability of MSC and BSC
A interface, Abis interface, and Um interface
The capability of HLR and VLR
If any of the previously listed NEs is overloaded, you can consider
increasing T3212.
IV. Precautions
T3212 cannot be over small. Otherwise, the signaling flow at each
interface increases sharply and the MS (especially handset)
consumes increasing power. If the T3212 is smaller than 30 minutes
(excluding 0), the network will be fiercely impacted.
Configuring T3212 of different cells in the same location area to the
same value is recommended. In addition, the T3212 must be
consistent with related parameters of switching side (smaller than
the implicit detach timer at switching side).
If the T3212 of different cells in the same location area is the same,
in the cell reselection, the MS continues to time according the
T3212 of the original cell. If the T3212 of the original and target cell
in the same location area is different, the MS uses the T3212 of the
original cell modulo that of the serving cell.
According to the actual tests of MS in the network, if the T3212 in
the same location area is different, after the MS performs modulo
algorithm based on behaviors of some users, the MS might power
on normally. However, the MS fails in originating location updating,
so the network identifies it as implicit detach. Now the MS powers
on normally, but a user has powered off prompt appears when it
is called.
4.10.8 T3122
I. Definition
T3122 defines the period that the MS must wait for before the
second trial calling if the first trial calling fails. It aims to avoid
congestion of SDCCH due to repeated trial calling by MS and to
relieve system load.
II. Format
T3122 ranges from 0s to 255s. The recommended value is 10s.
III. Configuration and Influence
The value of T3122 is included in the immediate assignment reject
message. After the MS receives the immediate assignment reject
message (no channels for signaling, A interface failure, overload of
central processing unit, namely, CPU), it can send new trial calling
request after T3122. T3122 aims to relieve radio signaling and voice
channel resources.
T3122 also help avoid systematic overload. When the CPU is
overloaded, the system multiplies T3122 by a factor (determined by
processorLoadSupconf) to increase T3122 through overload control.
In peak load time, you can manage network access by increasing
T3122. Namely, you can increase the interval between two
continuous trial callings to relieve network load.
4.10.9 T3124
I. Definition
T3124 is used in occupation process in asynchronous handover. It is
the time for MS to receive the physical information send by network
side.
II. Format
Configure it to 675ms when the channel type of assigned channel
for HANDOVER COMMAND message is SDCCH (+ SACCH). Configure
it to 320ms in other situations.
III. Configuration and Influence
When the MS sends the HANDOVER ACCESS message on the
primary DCCH, T3124 starts. When the MS receives a PHYSICAL
INFORMATION message, the MS stops T3124, stops sending access
burst, activates the PCH in sending and receiving mode, and
connects to the channel if necessary.
If the assigned channel is a SDCCH (+ SACCH), you must enable MS
to receive a correct PHYSICAL INFORMATION message sent by
network side in any block. If T3124 expires (only in
asynchronization) or the low layer link fails in the new channel
before sending the HANDOVER COMPLETE message, the MS
proceeds as follows:
1) Deactivate the new channel
2) Restart the original channel
3) Reconnect to TCH
4) Trigger to setup primary signaling link
Then the MS sends the HANDOVER FAILURE message on the
primary signaling link and return normal operation before trial
handover. The parameters for returning the original channel are
those before response to the HANDOVER COMMAND message (such
as in encryption mode).
4.10.10 T11
I. Definition
T11 is an assignment request queue timer.
II. Format
T11 is determined by equipment room operators. It indicates the
maximum queuing delay for assignment request.
III. Configuration and Influence
When the BSC is sending the ASSIGNMENT REQUEST message, no
TCHs are available. The ASSIGNMENT REQUEST message must be
put to a queue and the BSC sends the QUEUING INDICATION
message to MSC. Meanwhile, T11 starts timing.
When the BSC sends the ASSIGNMENT COMPLETE message (TCH is
successfully assigned) or the ASSIGNMENT FAILURE message (TCH
is not assigned) to MSC, T11 stops timing.
If T11 expires, the corresponding ASSIGNMENT REQUEST message
is removed from queue and the BSC sends a CLEAR REQUEST
message with the cause of no radio resource available to MSC to
clear calling. Assignment queuing helps reduce service rejection
times due to congestion, so enabling it is recommended in a
network. Anyhow, T11 cannot be over great and it must be
configured according to customer habits.
4.10.11 T200
I. Definition
T200 is important (both the MS and base station have T200) at Um
interface in data link layer LAPDm. LAPDm has different channels,
such as SDCCH, FACCH, and SACCH, and the transmission rate of
different channel is different, so T 200 must be configured with
different values. The type of the channels corresponding to T200 is
the value of the T200.
II. Format
Different channels corresponds different values of T200. According
to the protocol, when SAPI = 0 and SAPI = 3, the T200 of
corresponding data link is dependently implemented, depending on
delay of synchronous processing mechanism and process in layer 1
and layer 2.
Table 7-1 Value range and default of each type of T200
T200 Minimum Maximum Default
4.10.12 N200
I. Definition
N200 is the resending times after expiration of T200.
II. Format
To configure N200, follow rules below:
1) When SAPI = 0 or 3, N200 depends on the state and the
channel used.
When multiframe operation is set up, it ensures a common time
value for layer 2 link failure in all channels. For layer 2 link
establishment and release, configure N200 to 5.
2) In timer recovery state, configure N200 as below:
5 (SACCH)
23 (SDCCH)
34 (FACCH of full rate)
29 (FACCH of half rate)
3) When SAPI is unequal to 0 or 3, configure N200 to 5, as
shown in Table 1-6.
Table 7-2 Situations of SAPI unequal to 0 or 3
Minimum
Valid response Maximum
SAPI Channel resending
delay resending delay
delay
Tresp Trmin Trmax Note 3
0 SDCCH MS: 11 51 51
BSS: 32
0 FACCH/Full rate 9 26 39
0 FACCH/Half rate 10 34 44
3 SDCCH MS: 11 51 51 Note 1
BSS: 32
3 SACCH(with TCH) 25/129 Note 2 312 416 Note 2
The TDMA frame is the measurement unit of values in this table,
equal to 120/26ms (approximately 4.615ms)
Note 1: It caters for the process without SAPI 0 transmission.
Otherwise, it does not have a upper limit due to the priority
of SAPI 0 transmission.
Note 2: You can configure it to a greater value only when
PCH is unavailable due to SAPI frame transmission if SAPI =
3.
Note 3: It caters only for sending monitoring frames that are
available and without F equal to 1.
Why “cellular”?
Radio spectrum is very limited, that’s why we have only 10-25MHz dedicated to wireless
communication. Such narrow bandwidth allows 100-400 channels of reasonable quality, which is
not rational and commercially not profitable to develop network for such small number of mobile
subscribers. Genius idea lead to division of the whole geographical area to relatively small cells,
and each cell may reuse the same frequencies by reducing power of transmission. Each cell has
its own antenna (base station), and all base stations are interconnected using microwave or cable
communication.
History
Once upon a time there was analog cellular communication that didn’t support encryption,
compression, and ISDN compatibility; in addition each country (company) developed its own
system, which was incompatible with everyone else’s in equipment and operation.
So, in early 80s Europeans realized that pan-European public mobile system should be developed.
The new system had to meet certain criteria:
Mobile Station
Consists of:
• Mobile Equipment (ME) such as hand portable and vehicle mounted unit
• Subscriber Identity Module (SIM), which contains the entire customer related
information (identification, secret key for authentication, etc.)
Consists of:
• Base Transceiver Station (BTS) defines a cell and is responsible for radio link
protocols with the Mobile Station
• Base Station Controller (BSC) controls multiple BTSs and manages radio channel
setup, and handovers. The BSC is the connection between the Mobile Station and
Mobile Switching Center.
Consists of:
• Mobile Switching Center (MSC) is the central component of the NSS. Operates all
switching functions for the mobiles within its jurisdiction. Interface between mobile
and other (including fixed) network. Its functions:
• Home Location Register (HLR) contains all the subscriber information for
the purposes of call control, and location determination. There is logically
one HLR per GSM network, although it may be implemented as a
distributed database.
• Visitors Location Register (VLR) is only a temporary storage while the
particular subscriber is located in the geographical area controlled by the
MSC/VLR. Contains only the necessary information provision of
subscribed services.
• Authentication Center (AuC) is a protected database that stores the
security information for each subscriber (a copy of the secret key stored in
each SIM).
• Equipment Identity Register (EIR) is a list of all valid mobile equipment on
the network.
As we have mentioned above radio spectrum is very limited resource shared by all users. The
method to divide up the bandwidth among as many users as possible, chosen by GSM, is a
combination of Time- and Frequency-Division Multiple Access (TDMA/FDMA). FDMA divides
frequency bandwidth of the (maximum) 25 MHz into 124 carrier frequencies. Each Base Station
(BS) is assigned one or more carrier frequencies. Using a TDMA scheme each carrier frequency is
divided in time, which forms logical channels.
Time Division Multiple Access (TDMA) - the users take turns (in a round robin), each one
periodically getting the entire bandwidth for a little burst of time.
Frequency Division Multiple Access (FDMA) - the frequency spectrum is divided among the logical
channels, with each user having exclusives possession of some frequency band.
Figure 2. Organization of bursts, TDMA frames, and multiframes for speech and data
The fundamental unit of time in TDMA scheme is called a burst period and it lasts 15/26 msec.
Eight bust periods are grouped in one TDMA frame (120/26 msec), which forms a basic unit of
logical channels. One physical channel is one burst period per TDMA frame.
Traffic channels are defined as 26-frame multiframe. 26-frame multiframe lasts 120 msec (26 *
120/26). Out of 26 frames, 24 are for traffic, 1 is used for Slow Associated Control Channel
(SACCH), and 1 is currently unused.
Speech coding
Discontinuous transmission
The idea is based on the fact that a person speaks less than 40% of time in normal conversation,
so turning the transmitter off can save power. In order to distinguish voice and background noise,
very accurate Voice Activity Detector should be used. While transmitter is off, the receiving end
will hear a total silence, that’s due to digital transmission. To avoid this, comfort noise is
generated trying to match the characteristics of background noise.
Discontinuous reception
While being in idle mode mobile station has to listen only to Paging Channel, that uses almost no
power.
Power Control
To minimize co-channel interference and to conserve power, both the mobile and BTS operate at
the lowest power level that will maintain an acceptable signal quality. Mobile decides that power
level is acceptable using bit errors ratio.
Network Aspects
We have already seen structure used by physical layer, so we won’t expand it any more. Data layer
is modified version of some protocol used in ISDN and in Signaling System Number 7. So the only
interesting thing that is left for us is Layer 3 - GSM signaling protocol. Layer 3 is itself divided into
three sub-layers.
The RR-Layer is concerned with the management of RR-session, which is the time that a mobile is
in dedicated mode, as well as the configuration of radio channels. In addition RR-Layer manages
power control, discontinues transmission and reception, and handovers.
The first two types of handover, called internal because they involve only BSC, and MSC is notified
only on completion of the handover.
The last two types of handover, called external because they involve MSC.
Handover may be initiated by MSC (traffic balancing) or by mobile unit. The mobile unit always
scans Broadcast Control Channel of up to 16 neighboring cells, and forms a list of the six best
candidates for possible handover. This information is transmitted to current Base Station at least
once per second. BSC and MSC use this information for handover algorithm.
One of the problems while making handover decision is whether the poor signal quality is due to
physical interference or mobile having moved to another cell. There are two basic algorithms for
making handover decision:
Manages problem that arise from mobility of the subscriber. The ideal situation is when system
always knows where the subscriber is located (what cell) in each moment. But this will cause the
subscriber to update the system on every move, and this means a lot of obsolete update
messages, wasting bandwidth. Another extreme situation is when system never knows
subscriber’s position, but this will cause the system to look for the user over the whole
geographical area, that means a lot of paging messages on every terminating call. Strategy used
by GSM is as following, group of neighbor cells is grouped in one location area and subscriber
updates its position when moving from one location area to another. Paging is done only in the
current location area. The only question is "what division of cells to location areas is optimal?".
There are various algorithm for solving this problem, they are mostly based statistical data.
As seen form Figure 4, when a subscriber registers to MSC it sends registration message that
contains subscriber’s information. MSC updates its VLR and sends a message to subscriber’s
HLR.
Since the radio medium may be accessed by anyone, authentication is used to prove that the
users are who they claim to be. Each subscriber is given a secret key that is recorded in
subscriber’s SIM and Authentication Center (AuC), during authentication AuC generates a random
number that is sent to mobile. Using the secret key and this random number mobile produces a
response using ciphering algorithm A3. The response number should be equal to the one
calculated by AuC.
The same initial random number in conjunction with secret key is used to generate the ciphering
key using A8 algorithm. This ciphering key together with TDMA frame number is used compute a
sequence that is XORed with the sent data.
Tantang BLACKBERRY
If your BlackBerry cannot send or receive email, follow the steps below in the order given to
determine the problem.
To make sure that you are in a place with a strong enough signal for BlackBerry communication,
click the Options icon, and then click Status. For some models, the path is Settings, then
Options, and then Status.
In the "Signal" field, verify that the value is above -100Bm. Note the "-"; this is a negative
number. If the signal is weaker than -100Bm (i.e., the figure you see is bigger [105Bm or
110Bm]), the signal strength in your area is too weak for normal functions. If your signal is
stronger than -100Bm (with a smaller number, i.e., -90Bm), continue troubleshooting.
Verify that you are in a coverage area where email transmission is supported
For AT&T
Note the uppercase letters on both. If the "G" or "EDGE" is not uppercase, this indicates that the
devices are in range of an area with limited coverage. Phone calls and texting will work, but data
like web browsing and BES mail delivery will most likely not.
For more, including a breakdown on what an AT&T customer can and cannot do depending on
the indicated signal, see AT&T's Check the Wireless Network Availability for the RIM
BlackBerry Bold 9000 using Handheld Software Version 4.6.
The 3G network is faster; Indianapolis and Bloomington users should see that level of service.
Older models that do not support EDGE or 3G will most likely have a "GPRS" indicator;
"GPRS" should be capitalized. Following is a table of network status indicators for those models:
For Verizon
The network status indicator for Verizon should be "1X" or "1XEV". The "X" or "XEV" should
be upper case, and the same size on the screen as the "1":
Regardless of whether you use AT&T, Verizon, or any other carrier, if your network status
indicates email is not supported in your area, you must move to a location where email is
supported. If your network status indicates email support, but you still cannot send or receive
email, continue troubleshooting.
On most models, click the Options icon, and then click Date/Time.
If the date and time are incorrect, fix them, and then test to see if you can send or receive email.
If the date and time are correct, or if you have problems after fixing them, continue
troubleshooting.
Restart
Once the BlackBerry has restarted, test to see whether you can now send and receive email. If
you cannot, continue troubleshooting.
1. Click the Options icon, and then click Network or Network Settings.
4. Verify that the "Status" is active, and then click the trackwheel. A menu will appear.
5. Click Register Now and verify that the registration request is sent.
If you are unable to register the handheld or connect to the network, or do not have the correct
options displayed in the "Roaming" or "Status" fields, contact your service provider. If these
settings are all correct, and you are able to register your BlackBerry, continue troubleshooting.
Remove the device battery for about five minutes to ensure a complete disconnect from the
BlackBerry network. This causes a hard reset, forcing the network to register the device as a new
device on the network. This is a common fix for coverage areas in which you normally have a
connection and can send and receive email, but are now having trouble (see the charts above to
determine coverage areas).
Open Desktop Manager and double-click Redirector Settings. Make sure Redirect
incoming messages to your handheld is checked.
From the BlackBerry handheld
4. On the Folder Redirection page, select Mailbox- (Name of User), and choose Expand.
You should see a list of folders that includes Deleted Items, Inbox, Junk E-mail, and
Sent Items. For mail messages to be received, the Inbox folder must have a checkmark
next to it. Sent Items is checked by default and will not affect mail delivery.
For more information, see With a BlackBerry, how do I wirelessly reconcile the folders
from my mailbox?
If redirection is enabled and you are still unable to send or receive email, continue
troubleshooting.
For general information on mail filters and mail redirection, see With the BlackBerry Desktop
Manager, how do I configure filters to control mail redirection? For more information on wireless
mail redirection, see With a BlackBerry, how do I wirelessly reconcile the folders from my
mailbox?
If your device is still not able to send or receive email, contact the Support Center or your
BlackBerry provider.
4)Hardware Fault
Action: Check TCH availability
Check BTS error log
Check if sleeping TS.
Handover is an important function, which shows the integrity of the GSM network. If the
handover performance is poor, the subscriber will perceive the quality of the network as bad.
- Check for the handover success rate below certain criteria for example X%. If it doesn’t meet
the criteria and change the X% to a higher value and check for the next cell.
- Check the handover activity from the number of handover performed. If the number is above
certain value for example Y and then take into consideration.
- Check the site location, whether the site to site distance or co-sited. (Good map is needed here).
- Check whether the cell is isolated or not, if already known problem of no dominant serving cell
and take other cell.
- Check the handover flow whether is balance between incoming and outgoing.
- Check the difference performance of incoming and outgoing handover. This is to ensure the
priority for more problem direction.
- Check the cell whether it is external or internal. If external, start inter-BSC analysis.
- If the cell is internal, check the high ratio of lost handover, urgency handover and reversion.
- If one of them is yes, check the uplink & downlink interference problem.
- Check the frequency plan. There might be problem on co-channel or adjacent channel.
- Check the handover related parameters such as relation, BA-list, BSIC, hysteresis, offsets etc.
- Check if congested target cell. If the target cell is congested and then solve the congestion by
adding TRU.
- Perform measures to improve HO performance. This is the assumption comes from the above
analysis.
- Check the neighbor relation with low traffics (less than 10% of average number of handover per
relation) and unbalance relations.
- Check from the unbalance relation whether the target cell is congested, if congested, solves the
congestion problem.
- Check the missing measurement frequency (MBCCHNO) in Double BA-list in active list (if
yes, add the measurement frequency in the BA-list.
- Check unnecessary neighbor cell relations and if found, remove unnecessary relations.
- Check NCCPERM, if NCC of the neighbor is missing, add the NCC of the neighbor list into the
NCCPERM list.
- Check the setting of the cells whether they are set in different layer of HCS. (Layer 1 is the
highest priority)
- Check if the cell is at the inter BSC border, if so , check the inter BSC HO performance
(SIEMENS System).
- Check locating parameters and list out.
- Check the poor setting of parameter and if so, correct the parameter setting
- Check if BTS is defined but might not be in service. If yes, correct parameter setting or deblock
it.