Uplink/Downlink Traffic
PACKETSNOTMATCHED BY POLICIES AREROUTED
3.38 SR000650: TDM fallback for GSM Application .1 Description of SR000650: TDM fallback for GSM.1 Description of SR000650: TDM fallback for GSM
Application
Introduction to the feature
This feature provides a transport backup path for an SBTS with GSM operating Packet Abis over Ethernet.
3.38.1.1 Benefits
End-user benefits
This feature does not affect the end-user experience.
Operator benefits
This feature enables GSM service continuation in case of packet network unavailability.
3.38.1.2 Requirements
Hardware requirements
This feature requires Flexi Multiradio 10 System Module (FSMF).
3.38.1.3 Functional description
Functional overview
This feature provides a transport backup path for an SBTS operating Packet Abis over Ethernet. In case the packet network becomes unavailable it is possible to use an existing time-division multiplexing (TDM) connection and operate Packet Abis over ML-PPP.
The packet network is monitored by single or multiple Bidirectional Forwarding Detection (BFD) sessions. Depending on the use case, single hop or multi hop BFD sessions are applied. These sessions can be individually configured for use inside or outside of an IPSec tunnel.
The status changes in BFD session trigger changes to:
• routing entries to transmit the traffic over TDM links.
• IPSec policies to disable the encryption of GSM traffic (if IPsec is applied to Packet Abis traffic across the packet network).
A routing decision in downlink is made by the transport network, depending on the BFD
g
Note: Alternatively, an additional BFD session can be used. This function is however not provided by this feature.Selection of the synchronization source is independent of the switchover and is based on the configured synchronization hierarchy. During TDM fallback the SBTS might select TDM as well as the synchronization source.
Figure 29 TDM fallback mechanism
EthernetIF
NoIPecvia TDMforGSM Metric100
BFDMH1/2
SecGW
Relationship to other redundancy mechanisms
There are networks which support redundant packet network paths to the SBTS with
In any case it needs to be ensured that the BFD session(s) which are selected as a trigger for TDM fallback are terminated at a location in the network that is common for both packet network paths to the SBTS and both IPsec gateways.
In case BSC redundancy/pooling is applied, TDM fallback provides only a backup path for the primary BSC.
BTS solution details
This feature introduces the SBTS capability to logically combine the status of multiple BFD sessions and install or uninstall static routes and IPsec policies based on the outcome:
• As long as the BFD session or logically combined BFD sessions are up, bound static routes are applied based on the given metric/preference values and longest prefix match rules.
• As long as the BFD session or all logically combined BFD sessions are down, bound IPsec policy rules are applied.
• When the BFD session and all logically combined BFD sessions are down, TDM fallback path is used.
The configuration in SBTS needs to ensure that these BFD session(s) are never carried using the TDM path.
The feature builds on the following existing functionalities:
• The BFD session(s) can start at any configured virtual, alias, or BTS interface IP address.
• The GSM application can be bound to any configured virtual, alias, or BTS interface IP address, and can be separated from other applications.
For efficient configuration in case of network layer backhaul, one virtual IP address is used to exclusively bind GSM application and for the BFD sessions.
BSC/BSC site solution details
mcBSC L3 connectivity is applied. That means that routing is enabled on basic mcBSC modules. In addition to the BSC site routers, a dedicated media conversion router is connected directly to the Ethernet backhaul interfaces of the two mcBSC basic modules.
All routers including the mcBSC need to share the same open shortest path first (OSPF) domain.
3.38.1.4 System impact
Interdependencies between features
This feature requires the following features:
• SR000176: ML-PPP Termination
• SR000350: Ethernet Termination
• SR000361: Link Supervision with BFD
• SR000344: Fast IP Rerouting
• SR000356: IPsec for BTS
• BSS101431: L3 Connectivity for Multicontroller BSC Related features:
Impact on interfaces
This feature has no impact on interfaces.
Impact on network and network element management tools
This feature has no impact on network management or network element management tools.
Impact on system performance and capacity
This feature has an impact on system performance and capacity as beneath:
• System performance and capacity are not degraded.
• The switchover time must be less than one second starting from the fault detection.
• The overall GSM radio application performance is limited by the currently available bandwidth of the transport connections.
3.38.1.5 SR000650: TDM fallback for GSM Application management data
For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.
Alarms
There are no alarms related to this feature.
BTS faults and reported alarms
There are no BTS faults related to this feature.
Measurements and counters
There are no measurements or counters related to this feature.
Key performance indicators
There are no measurements or counters related to this feature.
Parameters
Table 109: New parameters lists parameters introduced with this feature.
Table 109 New parameters
Full name Abbreviated name Managed object
Trigger identifier triggerId IPRT
Trigger identifier triggerId IPRTV6
Trigger identifier triggerId SECPOL
False to true delay false2TrueDelay TRIGGER
List of considerable items itemList TRIGGER
item pointer itemPointer TRIGGER
Table 109 New parameters (Cont.)
Full name Abbreviated name Managed object
Logical operation logic TRIGGER
TRIGGER object identifier triggerId TRIGGER
True to false delay true2FalseDelay TRIGGER
3.38.1.6 Sales information
Table 110 Sales information
BSW/ASW License control in network element
BSW