Professional Documents
Culture Documents
CSFB Feature Parameter Description: GSM Bss GBSS19.0
CSFB Feature Parameter Description: GSM Bss GBSS19.0
GBSS19.0
Issue 01
Date 2016-09-05
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
2 Overview......................................................................................................................................... 3
2.1 Background.....................................................................................................................................................................4
2.2 Introduction.................................................................................................................................................................... 4
2.2.1 CSFB........................................................................................................................................................................... 4
2.2.2 Ultra-Flash CSFB........................................................................................................................................................ 4
2.3 Benefits........................................................................................................................................................................... 4
2.3.1 CSFB........................................................................................................................................................................... 4
2.3.2 Ultra-Flash CSFB........................................................................................................................................................ 4
2.4 Feature Support by NE................................................................................................................................................... 5
3 Technical Description...................................................................................................................6
3.1 CSFB.............................................................................................................................................................................. 6
3.1.1 MOC CSFB................................................................................................................................................................. 6
3.1.2 MTC CSFB................................................................................................................................................................10
3.2 Ultra-Flash CSFB......................................................................................................................................................... 14
4 Related Features...........................................................................................................................18
4.1 GBFD-511313 CSFB....................................................................................................................................................18
4.2 GBFD-171212 Ultra-Flash CSFB................................................................................................................................ 19
5 Network Impact........................................................................................................................... 20
5.1 GBFD-511313 CSFB....................................................................................................................................................20
5.2 GBFD-171212 Ultra-Flash CSFB................................................................................................................................ 21
6 Engineering Guidelines............................................................................................................. 22
6.1 GBFD-511313 CSFB....................................................................................................................................................22
6.1.1 When to Use CSFB....................................................................................................................................................22
6.1.2 Required Information................................................................................................................................................ 23
6.1.3 Planning..................................................................................................................................................................... 23
6.1.4 Deploying CSFB........................................................................................................................................................23
6.1.4.1 Deployment Requirements..................................................................................................................................... 23
7 Parameters..................................................................................................................................... 42
8 Counters........................................................................................................................................ 60
9 Glossary......................................................................................................................................... 64
10 Reference Documents............................................................................................................... 65
1.1 Scope
This document describes circuit switched fallback (CSFB), including its technical principles,
related features, network impact, and engineering guidelines.
l GBFD-511313 CSFB
l GBFD-171212 Ultra-Flash CSFB
01 (2016-09-05)
This issue does not include any changes.
Draft A (2016-06-30)
Compared with Issue 04 (2015-10-31) of GBSS17.1, Draft A (2016-06-30) of GBSS19.0
includes the following changes.
2 Overview
CSFB is one of a number of interoperability features provided by Huawei to enable GSM and
LTE networks to work together smoothly.
NOTE
2.1 Background
As an IP network, an LTE network is typically deployed with an IP multimedia subsystem
(IMS) to support circuit switched (CS) services. At the initial stage of LTE network
deployment, some operators expect to provide CS services without deploying an IMS. If the
core network (CN) is not deployed with an IMS, the LTE network cannot use voice over IP
(VoIP) to carry CS services.
2.2 Introduction
2.2.1 CSFB
With CSFB, a UE initiating CS services in an LTE cell is migrated to a GSM cell and then
performs CS services on the GSM network.
2.3 Benefits
2.3.1 CSFB
The CSFB feature provides the following benefits:
l Allows operators to provide CS services without deploying an IMS at the initial stage of
LTE network deployment.
l Allows UEs in areas covered by both GSM and LTE networks to process CS services on
the GSM network, fully utilizing legacy GSM networks.
CSFB √ √ √ √
Ultra-Flash √ √ √ √
CSFB
NOTE
√ indicates that the NE supports this feature. × indicates that the NE does not support this feature.
3 Technical Description
3.1 CSFB
On a CSFB-enabled network, a UE camping on an LTE cell is migrated to a GSM cell to
originate a CS call or receive a CS paging message. A CSFB call follows the same procedure
as that when the UE camps on a GSM cell.
NOTE
In Figure 3-1, the procedures enclosed in the white dotted line frame are optional and those enclosed in
the gray dotted line frame have branch procedures.
The UE sends an Extended Service Request message only when both the following conditions are met:
l The UE is attached to the CS domain with a combined EPS Attach.
l The UE cannot initiate IMS voice services.
2. The MME sends an S1-AP Request message carrying the CS Fallback Indicator IE to the
eNodeB, instructing the eNodeB to migrate the UE to a GSM cell.
3. The eNodeB selects a target GSM cell for the UE based on the measurement result or
LTE network configuration.
For details, see CSFB Feature Parameter Description.
4. (Optional) If GBFD-511308 eNACC Between GSM and LTE has been enabled on a
GSM network, and the LTE network and CN support the RAN information management
(RIM) procedure, the eNodeB starts the RIM procedure.
4a to 4c. The eNodeB requests the GSM system information (SI) from the BSS using the RIM
procedure.
5. The eNodeB instructs the UE to access the target GSM cell as follows:
l 5a. If both the UE and the network support PS handovers, the eNodeB initiates an LTE-
to-GSM PS handover.
l 5b. If both the UE and the network support LTE-to-GSM CCO instead of PS handovers,
the eNodeB sends a MobilityFromEUTRACommand message to the UE. The
MobilityFromEUTRACommand message indicates that the purpose is cellChangeOrder.
If the LTE-to-GSM eNACC procedure is used, the MobilityFromEUTRACommand
message carries the GSM cell ID and the SI (including SIB1, SIB3, and SIB13). If this
procedure is not used, the message carries only the GSM cell ID.
l 5c. If redirection is allowed, the eNodeB sends an RRC connection release message to
redirect the UE to the target GSM cell.
6. The eNodeB releases the S1 UE Context.
7. The UE sends a Channel Request message to the BSC.
If the location area (LA) has changed, the BSC proceeds with 9.
l If the cause value is the same as that corresponding to the NECI in the GSM system, the
BSC determines that the call is processed within the GSM system.
l If the cause value is the same as that corresponding to the NECI in the RIM procedure,
the BSC determines that the call is a CSFB call. This process is referred to as CSFB
MOC identification.
If the LA remains unchanged and CSFBIDENTIFYMOSW(BSC6900,BSC6910) is set to
OFF(Off), this call is not identified as a CSFB call.
8. (Optional) If the CSFBIMMASSENSW parameter involved in the GBFD-160203
CSFB QoS feature is set to ON(On), the BSC starts the TCH immediate assignment
procedure. For details about the CSFB QoS, see CSFB QoS Feature Parameter
Description.
9. (Optional) If the LA has changed, a local area update (LAU) procedure or combined
routing area update (RAU)/LAU procedure is performed.
The BSC determines whether the call is a CSFB call based on the value of CSMO in the
"Additional update parameters" IE contained in the RAU or LAU message.
– If the call is not a CSFB call, the BSC processes the call following the common call
access procedure.
– If the call is a CSFB call and SUPPORTCSFB(BSC6900,BSC6910) has been set to
SUPPORT(Support), the BSC proceeds with subsequent steps.
– If the call is a CSFB call but SUPPORTCSFB(BSC6900,BSC6910) has been set to
UNSUPPORT(Not Support), the BSC rejects the call.
NOTE
Some UEs cannot report the "Additional update parameters" IE to the BSC. Without this IE, the
BSC processes the call following the common call access procedure.
10 to 13. (Optional) If the UE is processing PS services before initiating a call, and neither the
UE nor the network supports Dual Transfer Mode (DTM), the UE suspends the PS services.
14 to 19. The UE initiates a CS call setup procedure.
The BSC determines whether the call is a CSFB call based on the value of CSMO in the
"Additional update parameters" IE contained in the CM Service Request message.
l If the call is not a CSFB call, the BSC processes the call following the common call
access procedure.
l If the call is a CSFB call and SUPPORTCSFB(BSC6900,BSC6910) has been set to
SUPPORT(Support), the BSC proceeds with subsequent steps.
l If the call is a CSFB call but SUPPORTCSFB(BSC6900,BSC6910) has been set to
UNSUPPORT(Not Support), the BSC rejects the call.
NOTE
Some UEs cannot report the "Additional update parameters" IE to the BSC. Without this IE, the BSC
processes the call following the common call access procedure.
If the MSC that the UE was attached to in the LTE cell before CSFB is not the MSC that the
UE was attached to in the GSM cell after CSFB, and if the UE has not performed any location
updates, the MSC rejects the MOC. After receiving a CM Service Reject message, the UE
performs an LAU procedure and then proceeds with the call procedure.
If a UMTS network is available, set SendUtranECSCFlag(BSC6900,BSC6910) to YES(Yes)
to allow UEs to proactively report 3G classmarks to the BSC. However, Classmark reporting
increases the call setup delay. To shorten this delay, set
UTRANCMDELAYFORCSFBSW(BSC6900,BSC6910) to ON(On) for CSFB calls. This
setting prohibits UEs from reporting 3G classmarks to the BSC. If an early assignment
procedure is used, the BSC proactively queries 3G classmarks after the alerting procedure. If
a late assignment procedure is used, the BSC proactively queries 3G classmarks after
assignment is complete.
20. (Optional) After the CS call is complete:
l If the GBFD-511312 Fast LTE Reselection at 2G CS Call Release feature is enabled, the
UE quickly returns to an LTE cell. If there are suspended PS services, the UE restores
the PS services in the LTE cell.
l If the GBFD-511312 Fast LTE Reselection at 2G CS Call Release feature is disabled, the
UE continues to camp on the GSM cell. If there are suspended PS services, the UE
initiates an RAU in the GSM cell to restore the PS services.
NOTE
In Figure 3-2, the procedures enclosed in the white dotted line frame are optional and those enclosed in
the gray dotted line frame have branch procedures.
NOTE
This process is referred to as CSFB MTC identification. According to 3GPP TS 44.018 v8.9.0,
depending on the Paging Indication value contained in the paging message from the GSM network, the
called UE contains any cause value (except the value corresponding to "Any channel") in the Channel
Request message. On the LTE network, however, the paging message from the eNodeB does not contain
the Paging Indication IE, and a UE that falls back to the GSM network contains the cause value
corresponding to "Any channel" in the Channel Request message.
14 to 17. (Optional) If the UE is processing PS services before initiating a call, and neither the
UE nor the network supports Dual Transfer Mode (DTM), the UE suspends the PS services.
18 and 19. The UE sends a paging response message to the MSC through the BSS.
The BSC determines whether the call is a CSFB call based on the value of CSMT in the
"Additional update parameters" IE carried in the paging response message. The determination
process is the same as that described in step 13.
In MSC pool networking mode, after receiving a message in response to the CSFB paging
message from a UE accessing a GSM cell, the BSC performs either of the following
operations:
l If the CSFB paging response message delivered by the eNodeB carries the Temporary
Mobile Subscriber Identity (TMSI), the BSC obtains the DSP of the MSC according to
the NRI in the TMSI information and sends a paging response message to the MSC.
l If the CSFB paging response message delivered by the eNodeB carries the IMSI
(International Mobile Subscriber Identity): When the
CSFBPAGRSPBCSWITCH(BSC6900,BSC6910) parameter is set to YES (namely, the
MSC supports Roaming Retry), the BSC randomly selects an MSC from the MSC pool
and sends the paging response message to the MSC. When the
CSFBPAGRSPBCSWITCH(BSC6900,BSC6910) parameter is set to NO (namely, the
MSC does not support Roaming Retry), the BSC discards the CSFB paging response
message.
20 to 22. (Optional) If the UE does not register with the MSC or the UE is not allowed to
access the LA, the MSC rejects the paging response and releases the A interface links. The
BSC then releases the signaling channel over the Um interface. After the signaling channel
over the Um interface is released, the UE obtains the location area identity (LAI) and
performs an LAU procedure.
23. The MSC initiates a CS call setup procedure.
If a UMTS network is available, set SendUtranECSCFlag(BSC6900,BSC6910) to YES(Yes)
to allow UEs to proactively report 3G classmarks to the BSC. However, Classmark reporting
increases the call setup delay. To shorten this delay, set
UTRANCMDELAYFORCSFBSW(BSC6900,BSC6910) to ON(On) for CSFB calls. This
setting prohibits UEs from reporting 3G classmarks to the BSC. If an early assignment
procedure is used, the BSC proactively queries 3G classmarks after the alerting procedure. If
a late assignment procedure is used, the BSC proactively queries 3G classmarks after
assignment is complete.
24. (Optional) The UE performs an LAU or combined RAU/LAU procedure.
l If the GBFD-511312 Fast LTE Reselection at 2G CS Call Release feature is enabled, the
UE quickly returns to an LTE cell. If there are suspended PS services, the UE restores
the PS services in the LTE cell.
l If the GBFD-511312 Fast LTE Reselection at 2G CS Call Release feature is disabled, the
UE continues to camp on the GSM cell. If there are suspended PS services, the UE
initiates an RAU in the GSM cell to restore the PS services.
1a to 3a. A UE initiates voice services in an LTE cell. The eNodeB triggers an LTE-to-GSM
SRVCC handover for the UE.
NOTE
In the MTC Ultra-Flash CSFB procedure, the MSC sends the Paging request or CS Paging Notification
message to the UE before the UE sends the Extend Service Request message to the MME.
3b. After receiving the SRVCC handover request from the MSC, the BSC identifies the Ultra-
Flash CSFB call and prepares CS resources for the call.
The BSC checks whether the configurations of MCC, MNC, LAC, and SAC in the service
area identifier (SAI) for a call are consistent with those configured on the MSC server. If they
are, the BSC determines the call is an Ultra Flash CSFB call. If they are not, the BSC
determines that the UE performed a UMTS-to-GSM inter-RAT handover.
The MCC, MNC, LAC, and SAC can be configured using parameters in the
GCELLCSFBPARA or GSAIFORLTE MO. The details are as follows:
In the MME pool or MOCN scenarios, if a BSC is connected to multiple MSC servers, which
are configured with different SAI values, the BSC also needs to be configured with multiple
SAI values. The GCELLCSFBPARA MO can only be used to configure one set of SAI
parameters. To add more SAI values, the GSAIFORLTE MO can be used. The MCC, MNC,
LAC, and SAC on the BSC are the combination of the GCELLCSFBPARA MO and
GSAIFORLTE MO.
NOTE
When no SAI parameter has been configured through the GCELLCSFBPARA MO, the
GSAIFORLTE MO can also be used to configure multiple sets of SAI parameters.
4. The CN sends the Handover Command message to the eNodeB, and the eNodeB sends the
message to the UE.
Ultra-Flash CSFB eliminates the dimmed signaling procedures shown in Figure 3-3 and
Figure 3-4. The following details the reasons why these signaling procedures are eliminated:
l Authentication
The UE has been authenticated on the LTE side before it is handed over from an LTE
cell to a GSM cell.
l Encryption
The UE has performed encryption as instructed during the SRVCC handover.
l IMEI query
The MME has sent the IMEI to the MSC during the preparation for the SRVCC
handover.
l CS resource establishment
The GSM network has prepared CS resources during the SRVCC handover procedure
and the UE does not need to reestablish CS resources after the SRVCC handover.
4 Related Features
LOFD-001034 CS Fallback to -
GERAN
Impacted Features
Feature ID Feature Name Impact
Impacted Features
Feature ID Feature Name Impact
5 Network Impact
Network Performance
l Deteriorating PS service experience
If a UE initiates a CS call or receives a paging message during a PS service in an LTE
cell, the UE reselects a GSM cell using CSFB to perform the CS service. The PS service
will be interrupted or the PS user rate decreases.
If the UE supports only the full rate, CSFB calls may be mistakenly identified, increasing
the TCH congestion rate.
l Prolonging the call setup delay
In CSFB, a UE in an LTE cell must reselect to a GSM cell to perform CS services. This
prolongs the call setup delay.
In scenarios where a UE sends the Utran Classmark Change message to the BSC when
accessing the GSM network, enabling the "access delay decrease with unreported 3G
classmark in the RIM procedure" function helps decrease the CSFB MOC or CSFB
MTC setup delay by 0.47s to 1.2s.
l Increasing the signaling load
The number of LAUs or RAUs increases. If the CSFB is performed through PS
handovers, the number of PS handovers also increases.
l Increasing the CPU load
When CSFB MTC identification is used, the paging message carrying the TMSI is to be
buffered and queried during call access. If this function is enabled, CPU load will
increase by up to 1%.
Network Performance
The CSFB call setup delay when the Ultra-Flash CSFB feature is used is 1s to 2s shorter than
that when the CSFB feature is used.
6 Engineering Guidelines
If a UE does not comply with 3GPP TS 44.018 v8.9.0 when sending the Channel Request
message to the BSC, the BSC may identify a CSFB call as a non-CSFB call, which cannot
experience CSFB services. Alternatively, the BSC may identify a non-CSFB call as a CSFB
call, which unexpectedly occupies TCHs, increasing the TCH congestion rate.
l If the proportion of MOCs not complying with 3GPP TS 44.018 v8.9.0 exceeds 5% in a
cell, you are advised not to enable CSFB MOC identification.
MOC protocol incompliance is determined when MOC signaling over the Um interface
meets either of the following conditions:
– When NECI is 1, the cause value of the Channel Request IE is 111xxxxx.
– When NECI is 0, the cause value of the Channel Request IE is 0100xxxx.
l If the proportion of MTCs not complying with 3GPP TS 44.018 v8.9.0 exceeds 5% in a
cell, you are advised not to enable CSFB MTC identification.
MTC protocol incompliance is determined when MTC signaling over the Um interface
meets either of the following conditions:
– The Paging request message on the network side does not contain the Paging
Indication IE.
– The Paging request message on the network side contains the Paging Indication IE,
and the cause value of the Channel Request IE for the MTC is 0001xxxx,
0010xxxx, or 0011xxxx.
If the proportion of UEs not supporting half rate exceeds 5% in a cell, you are advised not to
enable CSFB MOC identification.
6.1.3 Planning
The cells to be enabled with CSFB must be covered by both GSM and LTE networks.
It is a good practice to jointly plan LTE tracking areas (TAs) and GSM LAs if the CSFB MOC
and MTC identification is required. This ensures that CSFB MOCs and CSFB MTCs are
correctly identified even when location updates occur in the CSFB procedure.
The capacity of GSM cells depends on the proportion of calls made by LTE subscribers.
Aspect Requirement
BSC None
BTS None
GSM This feature can be enabled only when the E-UTRAN network covers the
networking same area as the GERAN network.
License The license controlling this feature has been activated. For details about
how to activate the license, see License Management Feature Parameter
Description. For details about license items, see License Control Item
Description.
Others The SGs interface has been configured between the MSC server and the
MME.
The LTE network must support CSFB.
UTRAN
classmark,
reducing
the CSFB
establishm
ent delay.
If the
UTRAN
classmark
reporting
function
does not
take effect
in a cell,
you are
advised not
to set this
parameter
to
ON(On).
NOTE
Before
setting this
parameter
to
ON(On),
ensure that
the RIM
function
has been
enabled on
GSM and
LTE
networks
and UEs
comply
with the
R9
protocol.
Step 2 (Optional) To enable CSFB call identification based on paging, run the SET
BSCEXSOFTPARA command with CSFB Paging Identify Switch set to ON(On).
----End
When configuring CSFB on the CME, perform a single configuration first, and then perform batch
modifications if required. Configure the parameters of a single object before a batch modification.
Perform a batch modification before logging out of the parameter setting interface.
Set parameters on the CME configuration interface according to the operation sequence
described in Table 6-4. For instructions on how to perform the CME single configuration, see
CME Single Configuration Operation Guide.
Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)
----End
SN MO NE Parameter Configurable
Name in CME Batch
Modification
Center
Step 2 Enable CSFB for LTE NEs on the E-UTRAN side and for the MSC on the GERAN side.
NOTE
For instructions on how to enable CSFB for LTE NEs and for the MSC, see the related feature
configuration guide.
Step 3 Trigger a CS paging to the UE after the UE performs services properly on the E-UTRAN
network.
Expected result: The UE successfully sets up a call at the BSC side. Both signaling and the
CS paging are processed properly.
----End
NOTE
When configuring CSFB on the CME, perform a single configuration first, and then perform batch
modifications if required. Configure the parameters of a single object before a batch modification.
Perform a batch modification before logging out of the parameter setting interface.
Set parameters on the CME configuration interface according to the operation sequence
described in Table 6-5. For instructions on how to perform the CME single configuration, see
CME Single Configuration Operation Guide.
Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)
----End
Counter Description
Counter Description
l Monitor TCH assignment for CSFB calls and CSFB call identification. Table 6-7 lists
the counters related to TCH assignment for CSFB calls and CSFB call identification.
Table 6-7 Counters related to TCH assignment for CSFB calls and CSFB call
identification
Counter Description
6.1.7 Troubleshooting
None
requirements on the call setup delay. This feature decreases the call setup delay more
significantly than the CSFB feature.
Aspect Requirement
BSC None
BTS None
GSM This feature can be enabled only when the E-UTRAN network covers the
networking same area as the GERAN network.
License The license controlling this feature has been activated. For details about
how to activate the license, see License Management Feature Parameter
Description. For details about license items, see License Control Item
Description.
Others The Sv interface has been configured between the MSC server and the
mobile management entity (MME). The MME and eNodeB are provided
by Huawei and support Ultra-Flash CSFB.
(Optional) In the MME pool or MOCN scenarios, if a BSC is connected to multiple MSC
servers, which are configured with different SAI values, the BSC also needs to be configured
with multiple SAI values using the GSAIFORLTE MO.
Step 2 (Optional) Run the BSC MML command ADD GSAIFORLTE to configure extended SAI
values. For the conditions of this step, see 6.2.4.2.1 Data Preparation.
----End
When configuring Ultra-Flash CSFB on the CME, perform a single configuration first, and then perform
batch modifications if required. Configure the parameters of a single object before a batch modification.
Perform a batch modification before logging out of the parameter setting interface.
Set parameters on the CME configuration interface according to the operation sequence
described in Table 6-11. For instructions on how to perform the CME single configuration,
see CME Single Configuration Operation Guide.
Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)
----End
Step 2 Enable Ultra-Flash CSFB for LTE NEs at the E-UTRAN side and for the MSC at the GERAN
side.
NOTE
For details about how to enable Ultra-Flash CSFB for LTE NEs and for the MSC, see the feature
configuration guide for Ultra-Flash CSFB.
Step 3 Trigger a CS paging to the MS after the MS performs services properly on the E-UTRAN
network.
Expected result: The MS successfully sets up a call at the BSC side. Both signaling and the
CS paging are processed properly.
Step 5 Monitor the counter listed in Table 6-12. If the value of this counter is not 0, the Ultra-Flash
CSFB feature has taken effect.
----End
When configuring Ultra-Flash CSFB on the CME, perform a single configuration first, and then perform
batch modifications if required. Configure the parameters of a single object before a batch modification.
Perform a batch modification before logging out of the parameter setting interface.
----End
6.2.7 Troubleshooting
None
7 Parameters
CNNO BSC690 ADD GBFD-5 SRVCC Meaning: Index of an MSC. It is used in storing and
DEIDX 0 GSAIF 11309 Ultra- querying the MSC attributes.
ORLTE GBFD-1 Flash GUI Value Range: 0~31
MOD 71212 CSFB Unit: None
GSAIF
ORLTE Actual Value Range: 0~31
Default Value: None
CNNO BSC691 ADD GBFD-5 SRVCC Meaning: Index of an MSC. It is used in storing and
DEIDX 0 GSAIF 11309 Ultra- querying the MSC attributes.
ORLTE GBFD-1 Flash GUI Value Range: 0~31
MOD 71212 CSFB Unit: None
GSAIF
ORLTE Actual Value Range: 0~31
Default Value: None
CSFBI BSC690 SET GBFD-5 CSFB Meaning: Whether to identify CSFB MOCs by
DENTI 0 GCELL 11313 modifying the new establishment causes indication
FYMO SOFT (NECI) in a cell. When this parameter is set to
SW ON(ON), CSFB MOCs are identified by modifying
the NECI in a cell. When this parameter is set to
OFF(Off), CSFB MOCs are not identified.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
CSFBI BSC691 SET GBFD-5 CSFB Meaning: Whether to identify CSFB MOCs by
DENTI 0 GCELL 11313 modifying the new establishment causes indication
FYMO SOFT (NECI) in a cell. When this parameter is set to
SW ON(ON), CSFB MOCs are identified by modifying
the NECI in a cell. When this parameter is set to
OFF(Off), CSFB MOCs are not identified.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
SendUt BSC690 SET GBFD-1 System Meaning: This parameter controls the value of the 3G
ranECS 0 OTHSO 11101 Informat Early Classmark Sending Restriction field when the
CFlag FTPAR ion BSC sends system information (SI) 3 to an MS. If this
A Sending parameter is set to YES, the value of the 3G Early
Classmark Sending Restriction field is 1, indicating
that the early classmark message sent by the MS
contains the 3G classmark information. If this
parameter is set to NO, the value of the 3G Early
Classmark Sending Restriction field is set to 0,
indicating that the early classmark message sent by
the MS does not contain the 3G classmark
information.This parameter is valid for dual-mode
MSs and is invalid for single-mode MSs.
GUI Value Range: NO(No), YES(Yes)
Unit: None
Actual Value Range: NO, YES
Default Value: NO(No)
SendUt BSC691 SET GBFD-1 System Meaning: This parameter controls the value of the 3G
ranECS 0 OTHSO 11101 Informat Early Classmark Sending Restriction field when the
CFlag FTPAR ion BSC sends system information (SI) 3 to an MS. If this
A Sending parameter is set to YES, the value of the 3G Early
Classmark Sending Restriction field is 1, indicating
that the early classmark message sent by the MS
contains the 3G classmark information. If this
parameter is set to NO, the value of the 3G Early
Classmark Sending Restriction field is set to 0,
indicating that the early classmark message sent by
the MS does not contain the 3G classmark
information.This parameter is valid for dual-mode
MSs and is invalid for single-mode MSs.
GUI Value Range: NO(No), YES(Yes)
Unit: None
Actual Value Range: NO, YES
Default Value: NO(No)
CSFBI BSC690 SET GBFD-5 CSFB Meaning: Whether to identify CSFB MTCs by filling
DENTI 0 GCELL 11313 or modifying the Channel Need information element
FYMTS SOFT (IE) of the Paging message in a cell. When this
W parameter is set to ON(ON), CSFB MTCs are
identified by filling or modifying the Channel Need IE
of the Paging message in a cell. When this parameter
is set to OFF(Off), CSFB MTCs are not identified.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
CSFBI BSC691 SET GBFD-5 CSFB Meaning: Whether to identify CSFB MTCs by filling
DENTI 0 GCELL 11313 or modifying the Channel Need information element
FYMTS SOFT (IE) of the Paging message in a cell. When this
W parameter is set to ON(ON), CSFB MTCs are
identified by filling or modifying the Channel Need IE
of the Paging message in a cell. When this parameter
is set to OFF(Off), CSFB MTCs are not identified.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
CSFBP BSC690 SET GBFD-5 CSFB Meaning: Whether to identify CSFB calls based on
agingId 0 BSCEX 11313 paging messages. If the parameter is set to ON, the
entifyS SOFTP BSC identifies mobile terminated calls (MTCs) for
w ARA which no paging message has been sent as CSFB
calls. If the parameter is set to OFF, the BSC does not
identify CSFB calls based on paging messages.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
CSFBP BSC691 SET GBFD-5 CSFB Meaning: Whether to identify CSFB calls based on
agingId 0 BSCEX 11313 paging messages. If the parameter is set to ON, the
entifyS SOFTP BSC identifies mobile terminated calls (MTCs) for
w ARA which no paging message has been sent as CSFB
calls. If the parameter is set to OFF, the BSC does not
identify CSFB calls based on paging messages.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
CSFBP BSC690 SET GBFD-5 Cell Meaning: When the paging response message carries
AGRSP 0 GCELL 11301 Reselect IMSI, the BSC cannot obtain the mapping between the
BCSWI SOFT GBFD-5 ion IMSI and the MSC signaling point because the paging
TCH 11313 Between message is not delivered from the BSC. If this
GSM parameter is set to "YES", the BSC sends the paging
and LTE response message to one MSC in the MSC pool.
CSFB GUI Value Range: NO(No), YES(Yes)
Unit: None
Actual Value Range: NO, YES
Default Value: NO(No)
CSFBP BSC691 SET GBFD-5 Cell Meaning: When the paging response message carries
AGRSP 0 GCELL 11301 Reselect IMSI, the BSC cannot obtain the mapping between the
BCSWI SOFT GBFD-5 ion IMSI and the MSC signaling point because the paging
TCH 11313 Between message is not delivered from the BSC. If this
GSM parameter is set to "YES", the BSC sends the paging
and LTE response message to one MSC in the MSC pool.
CSFB GUI Value Range: NO(No), YES(Yes)
Unit: None
Actual Value Range: NO, YES
Default Value: NO(No)
ECSC BSC690 SET GBFD-1 GSM/T Meaning: The early classmark sending control
0 GCELL 14302 D- (ECSC) parameter specifies whether the MSs in a cell
CCBAS GBFD-1 SCDMA use early classmark sending. After a successful
IC 11101 Interope immediate assignment, the MS sends additional
rability classmark information to the network as early as
System possible. The additional classmark information mainly
Informat contains the CM3 (classmark 3) information. The
ion CM3 (classmark 3) information contains the
Sending frequency band support capability of the MS (used for
the future channel assignment), power information
about each frequency band supported by the MS (used
for the handover between different frequency bands),
and encryption capability of the MS.
GUI Value Range: NO(No), YES(Yes)
Unit: None
Actual Value Range: NO, YES
Default Value: YES(Yes)
ECSC BSC691 SET GBFD-1 GSM/T Meaning: The early classmark sending control
0 GCELL 14302 D- (ECSC) parameter specifies whether the MSs in a cell
CCBAS GBFD-1 SCDMA use early classmark sending. After a successful
IC 11101 Interope immediate assignment, the MS sends additional
rability classmark information to the network as early as
System possible. The additional classmark information mainly
Informat contains the CM3 (classmark 3) information. The
ion CM3 (classmark 3) information contains the
Sending frequency band support capability of the MS (used for
the future channel assignment), power information
about each frequency band supported by the MS (used
for the handover between different frequency bands),
and encryption capability of the MS.
GUI Value Range: NO(No), YES(Yes)
Unit: None
Actual Value Range: NO, YES
Default Value: YES(Yes)
CNNO BSC690 ADD None None Meaning: Index of an MSC. It is used in storing and
DEIDX 0 GCNN querying the MSC attributes.
ODE GUI Value Range: 0~31
MOD Unit: None
GCNN
ODE Actual Value Range: 0~31
CNNO BSC691 ADD None None Meaning: Index of an MSC. It is used in storing and
DEIDX 0 GCNN querying the MSC attributes.
ODE GUI Value Range: 0~31
MOD Unit: None
GCNN
ODE Actual Value Range: 0~31
8 Counters
9 Glossary
10 Reference Documents