Overview
Uu RRC: SIB5 BMC signalling (25.324) Logical ch: CTCH Transport ch: FACH1 Physical ch: S-CCPCH
UTRAN UE UE Node B RNC Node B Iub Uu IuBC Cell Broadcast Center (CBC)
Iu-BC SABP signalling (25.419) Signalling transport (25.414) -TCP/IP (port: 3452) -IP or ATM transport
Concepts
Cell Broadcast (CB) message
User data as transmitted from the CBC to the UE A CBSA represents the smallest geographical area where CB messages can be broadcast. One CBSA contains one UTRAN cell BC CB messages are sent from WCDMA RAN to the UE using the BMC protocol. A BMC CB message contents one CB message A radio frame on the S-CCPCH where CTCH can be sent
BMC CB message
CTCH occasion
CN requirements: None Hardware requirements: R4 HW for the RANAP/RNSAP MP in RNC UE requirements: Support for CBS according to 3GPP Rel-99 Initial tuning: Not applicable
Feature Activation
SW license for FAJ 121 1326 installed and activated in RNC MO IuBcLink created and unlocked Cell Broadcast Service Area defined per UtranCell (parameter cellBroadcastSac) Note: Activation of this feature will impact UE battery consumption in idle mode and state URA_PCH
Radio Protocol
Functions
Storage of Cell Broadcast Messages Scheduling of BMC messages Transmission of BMC messages to UE
CTCH-SAP
Note : E/// P7 will not support Traffic volume monitoring and radio resource request
Message contains a list of all CBSAs that have triggered within last 30second
Write-Replace
Message type Message identifier
Identify the type of message (e.g. Write-Replace) RNC uniquely identify the CB message by this identifier with the 12 left most bits of the Serial number
Category
High priority : Broadcast immediately Background : Broadcast when No High priority or Normal Traffic broadcast Normal : Broadcast according to the repetition period IE
Note : In Ericssons implementation RNC will not use the Category information. All CB messages are sent immediately after reception of a Write-Replace message.
Write-Replace
Repetition Period
Indicates the periodicity of message broadcasts Set from once per one second to once per -1 hour
Write-Replace
RNC action
Checks all service areas are defined as CBSA then responds Write-Replace complete message
If not, responds Write-replace failure message The new message is stored
If the cell contained in the CBSA is enabled If the Message contains old serial number New message is broadcast on CTCH
The previously stored message replaced with the new message
With the repetition period requested by CBC For infinite Broadcast the CB message is repeated until it is deleted by CBC
Deletion of CB messages
Kill Procedure
Used to stop broadcast of one CB message in one or several CBSs
Reset Procedure
Used to stop broadcast of all CB messages stored in one or several CBSs
CTCH
CTCH
SFN 0
SFN 1
SFN 2
SFN N
SFN N+1
ctchOccasionPeriod
CTCH Occasions
CTCH occasions are defined as SFN=K+m*N, m=0,1,2.M
K: Offset of the first CTCH, Hard coded to 0 N: Period of CTCH occasion, ctchOccasionPeriod:1-256 M: Chosen so that SFN=K+m*N <=4095 (Max SFN)
10mS
S-CCPCH
......
......
N:ctchOccasionPeriod
SFN cycle : 0..4095 Maximum BW of CTCH Channel can vary from 0.18kbps to up to 30.4kbps
Need to make sure CTCH occasion period is not set to a multiple of DRX cycle length coefficient to avoid same UE will miss CTCH occasion
IuBC Interface
The Iu-BC interface is standardized by 3GPP. The CBC node must be connected to the O&M IP network The O&M IP network must allow the TCP port for SABP 3452 and will compete for bandwidth with the O&M traffic
IP transport (Iu-BC)
Iu-BC and O&M traffic will share the same IP host in RNC. For ATM case, Iu-BC traffic is carried to O&M router using ATM. The CBC node must be connected using IP/Ethernet to O&M Router.
IP transport (Iu-BC)
For IP case Iu-BC can be carried over IP/Ethernet straight to the CBC node from RNC all IP Routing configuration in RNC for Mur can be reused for Iu-BC as the Iu-BC interface is connected to the same O&M IP network as Mur. There is no need to add or modify routes as all traffic is sent to the O&M Router.
QoS
From RNC to CBC node the Iu-BC traffic will get the same QoS characteristics as O&M traffic. For the traffic from the CBC to the RNC, QoS separation in the IP network using different settings of the DSCP (DiffServ Code Point) can be done if the CBC node supports it. The QoS characteristics currently recommended for O&M traffic is assumed to be adequate for IuBC traffic. An operator may choose to implement an O&M IP network with a higher QoS level.
Dimensioning
The dimensioning of the O&M IP network should take into account Iu-BC traffic. The Iu-BC traffic volume is expected to be low and the impact on the dimensioning should be small. The Iu-BC capacity demand can be calculated using the formula below: C Iu-BC = Msglength * numMsgs/second Msglength is the length of the SABP message.
Note that the maximum length of a SABP message that can be processed in WCDMA RAN is limited to 18000 octets.
numMsgs/second is the number of SABP messages sent over the Iu-BC interface per second.
<Network example>
RNC3810
Backplane
CBS
OSS Server
ET-M4
Core MP
Mur
O&M Router <ATM/IP Converter>
<Network example>
RNC3810
Backplane
CBS
OSS Server
Core MP
Mur
O&M Router
ET-M4
Mur
X
O&M Router <ATM/IP Converter>
NW Address Translation
IuBC Host
Area 1
Area N
O&M
New/Modified MO structure
RncFunction 1 1 0..47 LA 1 1 0..2304 0..2304 SA 1 0..2304 # ... # ctchOccasionPeriod # cellBroadcastSac # .. 0..2304 UtranCell # administrativeState # operationalState # availabilityStatus # cbcIpAddress #sourceIpAddressValida tion 1 0..1 IubcLink
S-CCPCH
CTCH ctchOccasionPeriod
......
CTCH
sourceIpAddressValidation
Filter for IP source address validation in the RNC If it set to true filter will avoid the establishment of connections from other IP addresses
Observability (1/2)
No impact on KPIs New pm counters
pmNoReceivedSABPMsgs: Number of received SABP messages over Iu-Bc pmNoSentSABPMsgs: Number of sent SABP messages over Iu-Bc pmNoRejectedTcpConnections: Number of rejected TCP connections because of disallowed source IP address pmNoDiscardedCbsMsgOrders: Number of discarded CB message orders per cell pmNoDiscardedBmcMsgs: Number of discarded BMC PDUs per cell. Each BMC PDU contains one BMC CB message. pmBmcTrafficVolume: Accumulated BMC payload (bytes) per cell
Observability (2/2)
New GPEH events
CBS_MESSAGE_ORDER_DISCARDED triggered each time counter pmNoDiscardedCbsMsgOrders is stepped. New events for all SABP messages transmitted over Iu-BC: SABP_WRITE_REPLACE SABP_WRITE_REPLACE_COMPLETE SABP_WRITE_REPLACE_FAILURE SABP_KILL SABP_KILL_COMPLETE SABP_KILL_FAILURE SABP_RESET SABP_RESET_COMPLETE SABP_RESET_FAILURE SABP_RESTART SABP_ERROR_INDICATION