BSC Local Switching: About This Chapter
BSC Local Switching: About This Chapter
45.1 Overview
This provides the definition and describes the purposes of BSC local switching.
45.2 Availability
This lists the NEs, software versions, and other support required for the implementation of BSC
local switching.
45.3 Impact
This describes the impact of BSC local switching on system performance and other features.
45.4 Technical Description
This describes the technical aspects of BSC local switching, consisting of start, recovery, and
handover of BSC local switching calls.
45.5 Implementation
This describes how to configure and verify BSC local switching.
45.6 Maintenance Information
This lists the alarms and performance counters related to BSC local switching.
45.7 References
None.
45.1 Overview
This provides the definition and describes the purposes of BSC local switching.
Definition
BSC local switching refers to a process in which speech signals on the Abis interface loop back
to the MS without passing through the NSS when the calling party and called party are served
by the same BSC, as shown in Figure 45-1. BSC local switching saves transmission resources
of section C.
A B C D E
BTS
BSC MGW
BTS
E
NOTE
BSC local switching is performed on the BSC side without involving the NSS. Speech signals do not pass
through the MSC. The transmission resources of section D and section E on the MSC side, however, are
not released.
Purposes
BSC local switching saves transmission resources of the Ater interface.
Terms
Term Definition
BTS local switching When the calling party and called party are served by the
same BTS or BTS group, speech signals on the Abis
interface loop back to the MS in a BTS or BTS group
without passing through the BSC and MSC.
Loopback recovery Calls in the local switching state are recovered to the
ordinary conversation state.
MPTY supplementary service This supplementary service enables a user to have a multi-
connection call, that is, a simultaneous communication
with more than one party. This supplementary service is
categorized into two types: three-party service and
conference call.
Abbreviations
Abbreviation Full Spelling
45.2 Availability
This lists the NEs, software versions, and other support required for the implementation of BSC
local switching.
– √ √ – – – – –
NOTE
l –: not involved
l √: involved
Software Versions
Table 45-2 describes the software versions of GBSS products that support BSC local switching.
Product Version
Miscellaneous
The other requirements for BSC local switching are as follows:
45.3 Impact
This describes the impact of BSC local switching on system performance and other features.
l After BSC local switching is enabled, the success rate of handover may decrease, and the
call drop rate may increase. For details about the causes, refer to 45.4.3 Handover of BSC
Local Switching Calls.
l When the GTCS is locally configured, BSC local switching should not be enabled because
the transmission line of the Ater interface is relatively short.
l When BSC local switching is enabled, a forced handover must be initiated. When the BSC
requests channels, it does not support a request to the PCU for TCH changeback and queuing
preemption. Enabling BSC local switching may fail because no radio resources are
available.
l Enabling BSC local switching may cause discontinuous voice for a short time.
l After BSC local switching is enabled, call completion supplementary services and MPTY
supplementary services are not supported.
l After BSC local switching is enabled, the announcement and lawful interception services
of the MSC are not supported.
As the same rate set is used for a call when the call uses Adaptive MultiRate (AMR), AMR is not selected
when neither the speech version used by the calling party nor the speech version used by the called party
belongs to the intersection.
Table 45-3 Policies for selecting a speech version for local switching
AMR Whether the Full- or Half- Speech Adjustment
ACS Is Rate Channel Version Policy
Consistent
and Uses the
Same Rate
Both the calling Yes Not involved Not involved The conditions
and called for local switch
parties use are met. There is
AMR. no need for
adjustment.
When the speech versions used by both parties are consistent, the BSC sets up speech signal
links, and both parties perform TDM switching in the BSC. After the TDM switching is
successful, the call enters the BSC local switching state, and the redundant resources on the Ater
interface are released.
NOTE
l The MSC cannot obtain BSC local switching information because speech signals do not pass through
the MSC. During a BSC local switching call, the MSC does not support announcement, lawful
interception, or supplementary services.
l To ensure the consistency of circuit resources on the MSC and BSC sides, the BSC does not release
the CIC circuit.
The BSC sets up the Ater interface transmission channel between the GMPS or GEPS and the
GTCS. The speech signals are sent to the MSC through the BSC and then are switched to the
MS.
The recovery of BSC local switching calls is determined by the BSC without manual intervention
and configuration parameters.
Intra-BSC Handover
The difference between the intra-BSC handover of BSC local switching calls and the common
handover is that the speech version cannot be changed during the handover of BSC local
switching calls. That is, the speech version before the handover must be consistent with that
after the handover. Therefore, the success rate of handover may decrease, and the call drop rate
may increase.
l After the intra-BSC handover succeeds, the BSC local switching call may be maintained
or switched to a BTS local switching call and then recovered to an ordinary call depending
on the local switching support capability of the target channel.
l If the intra-BSC handover fails, the BSC local switching call is kept in the BSC local
switching state.
1. The BSC decides to initiate an outgoing BSC handover through the handover decision
algorithm and sends a handover request to the MSC.
2. Upon receipt of the handover request, the MSC sends a handover command to the BSC.
l After receiving the handover command from the MSC, the BSC instructs the MS to
recover the call to an ordinary call to ensure that the outgoing BSC handover is
successful and the voice quality is sound.
l If the BSC does not receive the handover command, the BSC local switching call is
maintained.
l If the MS reports a handover failure message, the BSC local switching call is recovered
to an ordinary call at the party that initiates the handover.
45.5 Implementation
This describes how to configure and verify BSC local switching.
Procedure
Step 1 Apply for a license and activate it.
1. When you apply for a license for BSC local switching, ensure that in the
BSC6000V900R003 (None) Commercial License Application Template, the Number of
resources corresponding to the Number of the TRX supporting BSC local switching in
the Resource control items column is not 0 and input the actual number of TRXs that
support BSC local switching.
2. Activate the license on the BSC6000 Local Maintenance Terminal. For details, refer to
Activating the BSC License.
Step 2 Configure BSC local switching on the BSC.
1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-
click BSC6000 and choose Configure BSS Local Switching from the shortcut menu. A
dialog box is displayed, as shown in Figure 45-2.
5. Click the BSC Local Switching Prefix Close tab, as shown in Figure 45-4.
l If BSC Close Based on Number in Figure 45-2 is set to Yes, set Avoid Number for
BSC and Number. Go to Step 2.6.
l If BSC Close Based on Number in Figure 45-2 is set to No, go to Step 2.6.
----End
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, choose BSC Maintenance > Maintain User
Resource > Query Call Resources . A dialog box is displayed, as shown in Figure 45-5.
Step 2 Enter an ID number in the Calling ID field, and then click Query. The query results are
displayed, as shown in Figure 45-6.
If BSC local switching is started successfully, the following output is displayed in the Query
Result window:
l The TC subrack information contains only A interface information instead of Ater
interface information.
l The BM subrack information contains Abis interface information.
----End
Alarms
None.
Counters
Table 45-4 lists the counters related to BSC local switching.
Counter Description
Counter Description
Counter Description
Counter Description
45.7 References
None.