Escolar Documentos
Profissional Documentos
Cultura Documentos
TELECOMMUNICATIONS NWS/MSG/NI
Page
CONTENTS
1. 2. 3. 4. Executive summary REASON OF CROSSTALK ACTIONS TO PREVENT CROSSTALK
4 Error: Reference source not found Error: Reference source not found Error: Reference source
not found
Page
1.EXECUTIVE SUMMARY
The Crosstalk phenomenon has been found out to happen within some of the GSM networks. One known Crosstalk situation happens in the following way: A mobile call is going on (a mobile originated or a mobile terminated call). A subscriber (A or B) hears suddenly a speech from some other call, and other end of the original call may be dropped. However the call is not always dropped, in some case the subscriber gets occasionally very short cuts of another unknown caller and the original call is going on. The known reason for this Crosstalk phenomenon is related to the GSM networks where Ciphering is not used and Frequency and Base Station Identity Code (BSIC) pairs are used too close each other in Radio Network planning. If a certain frequency and BSIC combination is used too tight in the network, this may occasionally cause interference and disturbance and in certain circumstances, two independent Handover messages may cause a short Crosstalk phenomenon. Whether Ciphering is in used then too tight use of Frequency and Base Station Identity Code (BSIC) pairs may cause interference and disturbance and it is heard as a short mute in speech and the call may be dropped. This System Technical Note explains the known reason and actions to prevent Crosstalk. There might occur more Crosstalk phenomenon in live GSM networks. We are interested in to receive any information related to other Crosstalk situations and will distribute the received information, if any to you in next System Technical Notes.
Page
2.REASON OF CROSSTALK
Crosstalk is caused in simultaneous Handover (HO) phase within two separate calls. In the following example (ref. steps 1-5 in Figure 1.Crosstalk), the Crosstalk situation is explained more detailed. The used frequencies, BSIC values etc. are illustrated in this case. The subscriber is located in Cell 1 with the frequency 55. He is having a call on and it is going to make Handover to Cell 2 that has the frequency 78 and BSIC 8. Suddenly the mobile makes Handover to another Cell x that has the similar BSIC (8) and the similar frequency (78), but this Cell x is not the one the mobile was signalling concerning Handover attempt. At this point, the subscriber hears some unknown subscribers speech. Crosstalk occurs because there are two cells with the same combination of the frequency (78) and the BSIC (8) influencing to each other. It does not matter whether these cells were situated several kilometres from each other, but the antennas are pointing to the same direction causing the co-channel interference seen between these two cells. The area where the subscriber gets Crosstalk is situated in this interference area. When a mobile is making a handover it gets Handover Command from BSC. Handover Command includes among others the frequency, BSIC and the Handover_Reference. The Handover_Reference has information of a new timeslot. The mobile sends back Handover Access to BTS where it is going to make a handover. Handover Access includes the Handover_Reference. With the Handover_Reference BTS identifies the mobile that is making the handover. In this situation the subscriber was expecting to make a handover to Cell 2 with the frequency 78. At the same time there was another mobile going to make a handover to another Cell x that had the same frequency 78. Both mobiles had received Handover command (ref. Steps 1 and 3 in Figure 1.) from the BSC and were sending to BTS Handover access (ref. Steps 2 and 4 in Figure 1.). In this case both mobiles were defined to make Handover to a similar timeslot in different cells. Handover_Reference of Subscriber MS1 was noticed in Cell x with frequency 78 although Cell 2 (with the same frequency) was expecting it (ref. Step 5 in Figure 1.). The mismatch happened because of the same BSIC code and the same frequency. While Ciphering is not yet used in the network the subscriber is able to hear clear speech from an unknown person. It might happen that the call drops within Crosstalk situation. Then the MSC clear code for the drop is B14 (handover failure).
Page
Page
1
Handover Command to MS1 Signalling message: HO Command: (BSC1) Cell 1 -> MS1 ARCN=78 BSIC=8 Handover Reference: Timeslot=3
2
Handover Access from MS1 Signalling message: HO Access: MS1 uplink HO response -> (BSC1) Cell 2 ARCN=78 BSIC=8 Handover Reference: Timeslot=3
3
Handover Command to MSx Signalling message: HO Command: (BSC2) Cell x+1 -> MSx ARCN=78 BSIC=8 Handover Reference: Timeslot=3
4
Handover Response from MSx Signalling message: HO Access: MSx uplink HO response -> (BSC2) Cell x ARCN=78 BSIC=8 Handover Reference: Timeslot=3
5
CROSSTALK HAPPENS Cell x reacts first to MS1s HO Access (Step 2) although Cell x should have reacted to MSxs HO Access (Step 4).
Page
- BTS id - Frequency - Base Station Colour Code (BCC) - Network Colour Code (NCC)
The Base Station Identity Code (BSIC) consists of BCC and NCC. When using same frequencies in a network the meaning of BSIC is to separate cells with similar frequencies from each other. It is normally used one value for NCC in whole network. All frequencies have to be listed with the used BSIC values (i.e. BCC and NCC values). Same frequencies should have a different BSIC code as far as possible. For example if the frequency 50 is used 5 times in the area, these cells can use BCC values 0,1,2,3,4,5 (not for example 0,0,1,1,1). If the same frequency is needed to use more than eight times (BCC can vary between 0 7), then the network planning has to be made carefully. This means that similar frequency & BCC pairs have to be located so far away that they do not interference to each other.
Page
Sep. 5/1994
NOTE: Depending on the operators environment the listed STNs may still be valid.
Page