ZTE UMTS Cell Broadcast Service Feature Guide

Cell Broadcast Service
Feature Guide

Version
V1.00
Date
2014/03/28
Author
Zeng
Lingling
Reviewer
Wu He
Notes
First Edition
2014 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used
without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to
change without notice.
ZTE Confidential Proprietary
TABLE OF CONTENTS
1
Feature Attribute ............................................................................................... 6
2
2.1
2.2
2.3
Overview ............................................................................................................ 6
Feature Introduction ............................................................................................. 6
License Control .................................................................................................... 8
Correlation with Other Features ........................................................................... 8
3
3.1
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.4
3.4.1
3.4.2
3.4.3
3.5
3.5.1
3.5.2
3.6
Technical Description ....................................................................................... 8

CBS system Architecture ..................................................................................... 9
CBS Basic Function ........................................................................................... 10
Supporting the SABP ......................................................................................... 12
RESTART Function ........................................................................................... 12
WRITE/REPLACE/KILL Functions ..................................................................... 13
Status Query Function ....................................................................................... 15
RESET Function ................................................................................................ 16
Interconnection Solution .................................................................................... 17
Interconnection with a Third-Party CBC ............................................................. 17
EMS Built-in CBC............................................................................................... 19
CBC Transmission Policies ................................................................................ 22
CBC Transmission Policies ................................................................................ 24
Key Algorithm .................................................................................................... 25
Channel Mapping and Multiplexing Principles .................................................... 25
CBS Scheduling Policies.................................................................................... 27
CTCH Occasion ................................................................................................. 28
Operation and Maintenance ............................................................................... 29
CBS LICENSE ................................................................................................... 29
Signaling Tracing ............................................................................................... 29
ETWS Function.................................................................................................. 30
4
4.1
4.2
Parameters....................................................................................................... 31
Radio Parameter ................................................................................................ 31
Ground Parameter ............................................................................................. 43
5
5.1
5.2
Related Counters and Alarms ........................................................................ 46

Related Counters ............................................................................................... 46
Related Alarms .................................................................................................. 47
6
6.1
6.2
Engineering Guide .......................................................................................... 47

Application Scenario .......................................................................................... 47
Feature Activation Procedure ............................................................................. 47
6.3
6.4
6.5
Feature Validation Procedure ............................................................................ 54

Feature Deactivation Procedure......................................................................... 55
Network Impact .................................................................................................. 55
Abbreviation .................................................................................................... 56
Reference Document....................................................................................... 57
FIGURES
Figure 2-1 Logical Architecture of CBS System ...................................................................7
Figure 3-1 Basic Network Structure of a CBS System........................................................10
Figure 3-2 Restart Indication Procedure: Successful Operation .........................................13
Figure 3-3 Write-Replace Procedure: Successful Operation ..............................................14
Figure 3-4 Write-Replace Procedure: Unsuccessful Operation ..........................................14
Figure 3-5 Message Status Query Procedure: Successful Operation.................................15
Figure 3-6 Message Status Query Procedure: Unsuccessful Operation .............................15
Figure 3-7 Reset Procedure: Successful Operation ...........................................................16
Figure 3-8 Reset Procedure: Unsuccessful Operation .......................................................17
Figure 3-9 Interconnection between a ZTE RNC and a CBC Server ..................................18
Figure 3-10 Connection Mode ............................................................................................18
Figure 3-11 EMS Built-in CBC Network Topology ..............................................................20
Figure 3-12 EMS Built-in CBC network topology ................................................................21
Figure 3-13 CTCH Multiplexing Mode with the MCCH Configured .....................................26
Figure 3-14 CTCH Multiplexing Mode without the MCCH Configured ................................27
Figure 3-15 ETWS System Architecture.............................................................................30
Figure 6-1 Parameters configuration interface 1 ................................................................48
TABLES
Table 2-1 License Control List .............................................................................................8

Table 4-1 Parameter Description .......................................................................................31
Table 5-1 Related Counters for Iu-BC Messages ...............................................................46
Table 5-2 Related Counters for Iu-BC Flow: ......................................................................46
Table 5-3 Related Counters for Uu Interface: .....................................................................46
Table 6-1 Feature Validation Procedure.............................................................................54
Table 6-2 RNC parameter list 3 .........................................................................................55
Feature Attribute
BSC/RNC Version: [ZXWR RNC V3.13.10.15/ZXUR 9000 V4.13.10.15]
BTS/Node B Version: [ZXSDR V4.13.10.20]
Attribute: [Optional]
Involved NEs:
NE Name
Related or Not
MS/UE
BTS/Node B
BSC/RNC
iTC
MSC
MGW
SGSN
GGSN
HLR
CBC
Special Requirement
: involved, -: not involved
Overview
2.1
Feature Introduction
This feature is used to support the cell broadcast short message service and can be used
to deploy text broadcast services like weather forecast and traffic information. The ETWS
is expected to be deployed based on the CBS system to warn people in areas where
disasters, for example earthquake, typhoon and tsunami, take place.
The CBS is a basic tele-service defined by the UMTS to provide text broadcast services
in a mobile telecommunication system. It is also called SMS-CB. The main difference
between the CBS and SMS is that the receiver of an SMS message is a specific user in
the network but the receivers of a CBS message involve all users in an area, including
roaming users. The minimum CBS address granularity is a cell in the PLMN. The
contents of the CBS can be but not limited to: service notice, weather forecast, traffic
information, international and domestic news, emergency events, and advertisements.
The logical architecture of the CBS system is shown in the following figure.
Figure 2-1
Logical Architecture of the CBS System

UTRAN
Routing
Node
Node B
UE
RNC
(e.g.
3GSGSN)
Node B
UE
Cell
Broadcast
Center
(CBC)
Iub
Uu
Iu
Bc
The Cell Broadcast Entity (CBE) is the source of the CBS contents. It provides users with
an interface to release information and formats CBS messages. The CBC is the
broadcast center of the cell and it saves and manages CBS messages generated by the
CBS. The CBC is connected to the RNC through the Iu-BC interface. The RNC receives
commands and CBS messages from the CBC and broadcasts CBS messages in
specified areas and specified periods. The RNC also needs to respond to the querying
CBC and report broadcasting states of CBS messages.
ZTE RNC supports the standard Iu-BC interface and the SABP protocol (refer to 3GPP
TS25.419). ZTE RNC can be connected to one or more CBC devices from a third party
with the standard Iu-BC interface.
ZTE RNC also supports the ETWS service (refer to 3GPP TS 22.168) that allows users
to receive warning CBS messages in case of a disaster. To enable the ETWS function,
the CBC and UE must operate together.
2.2
License Control
Table 2-1
License Control List
Feature ID
ZWF21-02-025
2.3
Feature
License Control
Configured
Name
Item
NE
Cell
WCDMA
Broadcast
Broadcast
Service
Support
Unit
Cell
Service
RNC
RNC
Correlation with Other Features

1. Required Features
None.
2. Mutually Exclusive Features
None.
3. Affected Features
None.
Technical Description
This feature provides the Cell Broadcast Service. As a basic telecommunication service
defined for the UMTS system, it sends short text messages to all users in a certain radio
area by broadcasting messages without connection or confirmation. The CBS is different
from the point-to-point SMS service. SMS messages are sent to individual mobile users,
while CBS messages are sent to all mobile users in a specific area, including the external
users roaming in this area. For the CBS, the minimum addressable area in a network is a
radio cell.
With the CBS function, operators can provide various services in the UMTS network,
such as emergency alarms, weather forecasts, traffic information, enterprise
advertisements, news, and quotations of stock markets. In the 3G network, the CBS can
be used for two major types of applications: One application is to cooperate with
government departments to use cell broadcast as a platform for publishing public
information, like the above-mentioned disastrous weather forecasts and emergency
broadcasts. The other application is to serve as a mobile advertisement carrier, which
enables the cooperation between operators and enterprises to use cell broadcast for
mobile advertisements. To operators, for one thing, more government departments and
enterprises are included as VIP customers in the cell broadcast information sources; also,
the successful application of the CBS may produce a positive brand effect, attract more
users to their communications networks, and promote the development of other services
in mobile networks. Therefore, there are optimistic prospects when CBS application is
introduced to the UMTS network due to its low investment and diversity.
In this document, the CN is referred in particular to the broadcast domain CN, which
means the CBC.
3.1
CBS System Architecture

The CBS, similar to the caption play service for digital televisions, is used to send
broadcast information to users in a certain area. The CBS messages can be broadcast in
predefined areas, which can be one or multiple cells or even an entire PLMN. The
broadcasting area is determined by the negotiation between the information provider and
the operator. Each CBS message page can contain 82 octets, which can represent 93
characters in case that the GSM default character table defined by 3GPP is used. Each
CBS message can contain 15 pages at most, all of which have the same tag indicating
that they belong to the same message, and each of which has an associated serial
number. Each CBS message also contains message classification and language
information, and the UE can be set to filter out undesired short messages, like broadcast
in an unknown language. CBS messages are broadcast periodically in cells, and both
transmission frequency and duration can be determined by the information provider. For
example, traffic information needs to be updated more frequently than antenna
information; messages in a fast-moving environment need a shorter period.
ZTE provides the CBC service in two ways:
Using a built-in EMS to simplify the CBC: The OMCR provides the CBC access
function, and the EMS provides the CBC processing function.
Interconnecting with a third-party CBC through the IuBC interface: The basic
network structure of a CBS system is shown in the following figure.
Figure 3-1
Basic Network Structure of a CBS System
UTRAN
Cell
Broadcast
Center
Node B
UE
RNC
Node B
UE
CBE
CBE
(CBC)
Iub
Uu
IuBC
The CBS system architecture can be implemented as above, in which a Cell Broadcast
Center (CBC) is connected to an RNC through an IuBC interface and is connected to two
CBEs through interface 1. One CBC can be connected to multiple RNCs and CBEs, and
one RNC may be connected to multiple CBC nodes. Each CBC node is an external node
of the RNC. Moreover, a CBE is responsible for all aspects of formatting the CBS,
including splitting a CBS message into multiple pages. Interface 1 between CBEs or
between a CBE and a CBC is not defined in 3GPP specifications, but defined by the
equipment provider.
3.2
CBS Basic Function

In the UMTS system, a CBC is an integral part of the CN and is used to manage CBS
messages. Physically, a CBC can be connected to an RNC through a routing node like
an SGSN, and the upper layer uses the IuBC logic interface and the SABP. Each CBS
message generated by a CBE is sent by a CBC to an RNC (carrying a list of the cells to
which messages are broadcast), and the RNC controls broadcast within the cells
specified in the CBC.
According to the protocol, a CBC should implement the following functions:
Modifying or deleting CBS messages sent to an RNC
10
Initiating broadcasts by sending fixed-length CBS messages to a BSC/RNC in each

language provided by the cell, and where necessary, padding the pages to the
length of 82 octets (Send fixed-length CBS messages to the RNC, if the message is
shorter than 82 bytes, padding data will be added.)
Determining the cells to which a CBS message should be broadcast, which

indicates the geographical scope of each CBS message
Determining the start time when a CBS message should be broadcast
Determining the stop time when a CBS message stops being broadcast and
subsequently instructing each RNC to cease the broadcast of the CBS message
Determining the cycle in which the CBS message should be repeatedly broadcast
Identifying the emergency broadcast service if there is one as required by the R8

protocol and indicating the RNC of the emergency broadcast service to implement
the PWS (ETWS)
A CBC sends CBS data and control commands to an RNC in the form of message
primitive, and the RNC implements the broadcast of CBS messages in specified cells.
Whether
cell
supports
the
CBS,
it
is
UUtranCellFDD.refUServiceAreaBC,
controlled
jointly
by
the
URncFunction.cbsSwitch,
UUtranCellFDD.sccpchCfgScene and USccpch.sccpchUsage parameters. A cell can

support
the
CBS
only
when
UUtranCellFDD.refUServiceAreaBC
URncFunction.cbsSwitch
is
not
NULL,
is
TRUE,
and
and
both
UUtranCellFDD.sccpchCfgScene and USccpch.sccpchUsage has the value that

supports the CBS.
When
UUtranCellFDD.refUServiceAreaBC
is
not
NULL,
UServiceAreaBc.sacbc
referenced by it defines the service area code of the BC domain where the cell is located.
A service area code identifies uniquely one or several cells in the same location area
(LA). It is used to indicate the location of a UE to a CN. One cell has one or two SACs.
One is in the CS or PS domain, and the other is in the BC domain. An SA in the BC
domain can contain only one cell.
11
3.2.1
Supporting the SABP

The Service Area Broadcast Protocol (SABP) is a 3G UMTS protocol used for the
information broadcast service. It is a protocol used in the Iu-BC domain. Introduced to
implement the cell broadcast function, it is mainly used for the interaction between the
core network (CBC) and the RAN (the BMC protocol bearer is controlled by
broadcast/multicast) in the BC domain.
The protocol stack in the Iu-BC domain, unlike the Iu-CS and Iu-PS domains, has only
one plane, which contains both control information and user information. The SABP
implements the control signaling and data transmission functions. To implement the CBS
function, as defined in the RRC protocol stack by 3GPP, the BMC protocol entity
performs data processing on the Uu interface, and the RRC performs RB control on the
Uu interface for the CBS.
This feature additionally implements the SABP to support the WRITE-REPLACE
(hereinafter abbreviated as WR), KILL, MESSAGE STATUS QUERY, RESTART, and
RESET, as well as their response messages. RESTART and RESET can provide
exception protection processing for the cell broadcast function.
3.2.2
RESTART Function
The purpose of the Restart Indication procedure is for the RNC to inform the CN that a
Service Area broadcast has started in one or more of its Service Areas (for example,
when a Service Area becomes operational or when the RNC is initialized).
The CBS supports the restart of a service area or cell in various scenarios like system
power-on and cell reconstruction.
The RNC shall initiate the procedure by sending a RESTART message to the CN.
12
Figure 3-2
Restart Indication Procedure: Successful Operation
CN
RNC
RESTART
This message shall contain a Service Areas List IE for reference and may also include
the Recovery Indication IE to indicate whether the previous broadcast information needs
to be loaded. In the absence of the Recovery Indication IE, the CN shall interpret it as
"lost".
3.2.3
WRITE/REPLACE/KILL Functions
The CBS supports the Write-Replace, or Kill (WR/KILL) function of broadcast messages.
The purpose of this Write-Replace procedure is to broadcast new information or replace
a message already broadcast to a chosen Service Area(s). The purpose of the Kill
procedure is to stop the broadcast of the indicated message.
The CN shall initiate the procedure by sending a WRITE-REPLACE message to the RNC.
The RNC will initiate the broadcasting of a new message or replace a message already
broadcast as requested to the service areas as indicated in the Service Area(s) List.
13
Figure 3-3 Write-Replace Procedure: Successful Operation
CN
RNC
WRITE-REPLACE
WRITE-REPLACE
COMPLETE
If there is at least one Service Area specified in the WRITE-REPLACE message for
which the RNC cannot allocate all the resources requested or for which the RNC cannot
complete the operation as requested, then the RNC shall return a WRITE-REPLACE
FAILURE message to the CN as an outcome of the procedure. A list of Service Area(s)
where the requested resources are unavailable or for which the RNC cannot complete
the operation as requested and an appropriate cause value shall be provided in this
WRITE-REPLACE FAILURE message in the Failure List.
This WRITE-REPLACE FAILURE message may also include those Service Area(s)
where the requested resources were available and shall indicate in the Number of
Broadcasts Completed List those Service Area(s) which completed the request
successfully.
Figure 3-4 Write-Replace Procedure: Unsuccessful Operation

CN
RNC
WRITE-REPLACE
WRITE-REPLACE
FAILURE
14
The CN shall initiate the KILL procedure by sending a KILL message to the RNC. Upon
receipt of the KILL message the RNC shall stop broadcasting the CBS message. If the
RNC fails to stop broadcasting the CBS message as indicated in the KILL message in at
least one service area, the RNC shall return the KILL FAILURE message to the CN.
3.2.4
Status Query Function

The Message Status Query procedure is used by the CN to obtain the message status of
a broadcast message.
Figure 3-5
Message Status Query Procedure: Successful Operation
CN
RNC
MESSAGE STATUS QUERY

COMPLETE
Figure 3-6
Message Status Query Procedure: Unsuccessful Operation
CN
RNC

FAILURE
15
The CN shall initiate the procedure by sending a MESSAGE STATUS QUERY message
to the RNC.
Successful operation: Upon receipt of the MESSAGE STATUS QUERY message, the
RNC shall return the MESSAGE STATUS QUERY COMPLETE message.
Unsuccessful operation: If the requested operation fails (for example, the CBS message
is unknown, or the RNC cannot send the status for a known CBS message), the RNC
shall send a MESSAGE STATUS QUERY FAILURE message to the CN containing a
Failure List for Service Area(s) for which the requested operation failed.
3.2.5
RESET Function
The service supports broadcast reset (RESET) in a service area. The CN shall initiate
the procedure by sending a RESET message to the RNC, in order to end broadcasting in
one or more Service Areas of the RNC.
Figure 3-7
Reset Procedure: Successful Operation
CN
RNC
RESET
RESET COMPLETE
16
Figure 3-8
Reset Procedure: Unsuccessful Operation
CN
RNC
RESET
RESET FAILURE
Successful operation: Upon receipt of this message, the RNC shall end broadcasting in
the indicated Service Area(s) and shall return a RESET COMPLETE message.
Unsuccessful operation: Upon receipt of this message, if the RNC cannot end
broadcasting in the indicated Service Area(s), it shall return a RESET FAILURE
message. The RESET FAILURE message may contain the Service Area(s) List and shall
contain the FAILURE LIST indicating the relevant Service Area(s) in which the RESET
message was successful and unsuccessful respectively, along with the appropriate
cause value.
3.3
Interconnection Solution
3.3.1
Interconnection with a Third-Party CBC

The topological graph of the interconnection between a ZTE RNC and a CBC server is
shown as below.
17
Figure 3-9
Interconnection between a ZTE RNC and a CBC Server
WAN
RNC
CBC
IuBC
TCP Transmission Protocol
Figure 3-10
Connection Mode
RNC
C
M
P
IP
Iterface
Board
WAN
Router
C
M
P
CBC
Router
Iterfa
ce
Borad
Nodeb
In V3, IP Interface Board means GIPI, and Interface Board meas GIPI/APBE.
In V4, IP Interface Board means EGPB, and Interface Board meas EGPB/EAPB.
When the CBC is provided by a third party, appropriate configurations are required on
the RNC side in order to enable interconnection between radio devices and the CBC.
Choose one of the RNC IP interface boards connected with the CBC server, and the IP
interface board needs to be configured with the interface IP address. The CMP module
needs to be configured with the local and peer IP addresses for the CBS connection. The
port of the CBC connection is 3452 for the UMTS RNC and the CBC server, which does
not need to be configured for the RNC.
The following parameters are involved in the configuration process.
18
UIubcLink.UIubcLinkId: To configure the TCP connection number for the CBC (it is
set to 1)
UIubcLink.LocalRole: To configure whether the CBC is connected as a client or a

server
UIubcLink.refModule: To configure the CMP ID of the service
UIubcLink.LocalIpAddr and UIubcLink.PeerIpAddr: To configure the local and peer

IP addresses for the CBS connection
UIubcLink.LocalIpVersion and UIubcLink.PeerIpVersion: To configure the lengths of

the local and peer IP addresses for the CBS connection
UIubcLink.PeerIpMaskLen: To configure the mask of the peer IP address for the

CBC connection
3.3.2
UIubcLink.refVpnVrf: To configure the VPN of the local IP address
UIubcLink.TcpIpDscp: To configure the DSCP priority for the CBC connection
EMS Built-in CBC

In the network management system, the cell broadcast center system exists as a
subsystem. The system does not need to be interfaced to any other CBC equipment
which provides the broadcasting service, and takes the EMS itself as cell broadcast
equipment by adopting the network management system connecting with the RNC, to
complete the broadcast center function. It can save the cost of purchasing a third-party
CBC for the operator.
The network topology is different in V3 and V4 version.
1. The network topology in V4 version is as below:
19
Figure 3-11
EMS Built-in CBC Network Topology

O
M
M
RNC
E
G
P
B
C
M
P
Transmissio
n
network
CBC
Server
Router
C
M
P
EAPB/
EGPB
Nodeb
The EMS built-in CBC networking principles are described as below:
The CMP is the actual processing module of CBC messages, which means the
external IP address outside belongs to the module No. of the CMP. It can select an
existing CMP board, and there is no need to add a new CMP board.
Both the EGPB and the OMM are connected to the transmission network, and the
end of the transmission network is the CBC server.
Remarkably, the function of the OMM is to forward the service layer data, as shown
in the figure above.
From the point of the CMP in the RNC, the OMM is the CBC server, and the
TCP connection ends at the OMM.
From the point of the CBC inside the EMS, the OMM is the RNC, and the TCP
connection ends at the OMM.
The CBC server should take the OMM address as the IP address for the TCP
connection.
2. The network topology in V3 version is as below:
20
Figure 3-12
EMS Built-in CBC network topology
RNC
EMS
G
I
P
I
C
M
P
S
w
i
t
c
h
O
M
M
Transmission
network
CBC Server
The EMS Built-in CBC networking principle is described below:
The CMP is the actual processing module of CBC messages, which means the
external IP address outside belongs to the module No. of the CMP. It can select an
existing CMP board as the processer, and there is no need to add a new CMP
board.
The GIPI and the switch are responsible for IP forwarding, so the OMM should route
the subnet, which the CMP belongs to, to the GIPI.
Remarkably, the function of the OMM is to forward the service layer data, as shown
in the figure above.
From the point of the CMP in the RNC, the OMM is the CBC server, and the
TCP connection ends at the OMM;
From the point of the CBC inside the EMS, the OMM is the RNC, and the TCP
connection ends at the OMM.
The CBC server should take the OMM address as the IP address for the TCP
connection.
From the GIPI to the switch, and from the switch to the OMM, it can adopt the
original OMC-B interface, and there is no need to add new physical connections.
From the EMS to the OMM, it also can adopt the original physical connections.
For both V3 and V4 version, when using the EMS built-in CBC the following parameters
are involved in the configuration process.
21
UIubcLink.UIubcLinkId: To configure the TCP connection number for the CBC (it is
set to 1)
UIubcLink.LocalRole: To configure as a server
UIubcLink.refModule: To configure the CMP ID of the service
UIubcLink.LocalIpAddr and UIubcLink. PeerIpAddr: To configure the local and peer

IP addresses for the CBS connection (UIubcLink.LocalIpAddr is set to a network
segment and does not overlap the existing address. UIubcLink.PeerIpAddr is set to
the IP of the OMM.)
UIubcLink.LocalIpVersion and UIubcLink.PeerIpVersion: To configure the lengths of

the local and peer IP addresses for the CBS connection
UIubcLink.PeerIpMaskLen: To configure the mask of the peer IP address of the

OMM
3.3.3
UIubcLink.refVpnVrf: To configure the VPN of the local IP address
UIubcLink.TcpIpDscp: To configure the DSCP priority for the CBC connection
CBC Transmission Policies

With regard to the port for the TCP on the Iu-BC interface, there is an agreement in the
TS 25.414 that:
1.
Both the RNC and CBC can originate a TCP connection.
2.
The listener ports of the RNC and CBC, no matter whichever is the service provider,
are both 3452 ports. That is, no matter whichever originates the connection, the
peer port is a 3452 port invariably.
Therefore, in the system, even if the RNC is the connection originator, it must use a 3452
port as its local port.
At present, we think the RNC needs to connect with only one CBC, and there is only one
TCP connection between an RNC and a CBC.
22
In addition, although in the TS 23.041 and TS 25.414, UDP is also listed as one of the
Iu-BC bearer protocols, there is an agreement only for the TCP in TS 25.414. Therefore,
we only consider the implementation of the TCP protocol.
When the EMS built-in CBC is used, the system uses passive mode, which means the
RNC, as the passive side of TCP, is waiting for the OMM to start the TCP connection.
The Iu-BC is used mainly to provide TCP services upwards, including connection
management, and data sending and reception. The transmission is intended to provide
management and interface for the TCP link of the CBC. Its main functions include:
According to the OMC configuration, the transmission originates the TCP

connection (active mode) for the CBC or monitors the TCP port of the CBC (passive
mode). Once the connection is established, the RNLC will be informed.
In the active mode, if a disconnection occurs, a notification will be announced and

the RNLC will be informed that the connection state has been changed. In addition,
a connection establishment request message will immediately be initiated by the
TNL, and then this connection may be recovered quickly.
If the board handling the Iu-BC connection is changed from active mode to passive
mode, the TCP connection will be cut off automatically. If it is changed from passive
mode to active mode, the change of the connection should be informed first and a
new TCP connection should be activated or the TCP port should be monitored
according to the configuration. After reestablishing the connection, the RNLC also
should be informed.
The TNL needs to monitor the connected socket port, and notify the CBC upon
receipt of data.
The TNL needs to receive messages from the upper layer, and forward the required
data to the corresponding socket.
If the local end is the server and there is already a connection, any subsequent
connection will be rejected directly.
23
The TNL is responsible mainly for managing the TCP connection of the CBC. The
connection-related information (such as sending data) must be carried in the
message and transferred to the upper-layer TCP ID.
3.3.4
CBC Transmission Policies

With regard to the port for the TCP on the Iu-BC interface, there is an agreement in the
TS 25.414 that:
1.
Both the RNC and CBC can originate a TCP connection.
2.
The listener ports of the RNC and CBC, no matter whichever is the service provider,
are both 3452 ports. That is, no matter whichever originates the connection, the
peer port is a 3452 port invariably.
Therefore, in the system, even if the RNC is the connection originator, it must use a 3452
port as its local port.
At present, we think the RNC needs to connect with only one CBC, and there is only one
TCP connection between an RNC and a CBC.
In addition, although in the TS 23.041 and TS 25.414, UDP is also listed as one of the
Iu-BC bearer protocols, there is an agreement only for the TCP in TS 25.414. Therefore,
we only consider the implementation of the TCP protocol.
When the EMS built-in CBC is used, the system uses passive mode, which means the
RNC, as the passive side of TCP, is waiting for the OMM to start the TCP connection.
The Iu-BC is used mainly to provide TCP services upwards, including connection
management, and data sending and reception. The transmission is intended to pro
vide management and interface for the TCP link of the CBC. Its main functions in
clude:
According to the OMC configuration, the transmission originates the TCP

connection (active mode) for the CBC or monitors the TCP port of the CBC (passive
mode). Once the connection is established, the RNLC will be informed.
In the active mode, if a disconnection occurs, a notification will be announced and

the RNLC will be informed that the connection state has been changed. In addition,
24
a connection establishment request message will immediately be initiated by the

TNL, and then this connection may be recovered quickly.
If the board handling the Iu-BC connection is changed from active mode to passive
mode, the TCP connection will be cut off automatically. If it is changed from passive
mode to active mode, the change of the connection should be informed first and a
new TCP connection should be activated or the TCP port should be monitored
according to the configuration. After reestablishing the connection, the RNLC also
should be informed.
The TNL needs to monitor the connected socket port, and notify the CBC upon
receipt of data.
The TNL needs to receive messages from the upper layer, and forward the required
data to the corresponding socket.
If the local end is the server and there is already a connection, any subsequent
connection will be rejected directly.
The TNL is responsible mainly for managing the TCP connection of the CBC. The
connection-related information (such as sending data) must be carried in the
message and transferred to the upper-layer TCP ID.
3.4
Key Algorithm
This feature additionally follows the Broadcast/Multicast Control (BMC) protocol and this
protocol adapts broadcast and multicast services on the radio interface.
Key algorithms related to the CBS include channel mapping and multiplexing principles
and CBS scheduling policies.
3.4.1
Channel Mapping and Multiplexing Principles

According to the related protocols, the CBS supports the following two channel mapping
modes:
25
In the SCCPCH, it is allowed to multiplex or not to multiplex the CTCH->FACH

carrying the CBS with the PCH. In other words, it is unnecessary to support
simultaneously the PCH on the SCCPCH of the CTCH->FACH carrying the CBC.
The CTCH->FACH carrying the CBS can multiplex one FACH together with other
logical channels.
According to the current implementation strategies, the PCH of paging information and
the FACH of signaling are carried on different SCCPCHs. If the FACH carrying the CBS
is multiplexed with the PCH, it may fail to select the correct SCCPCH according to the
SCCPCH selection method used by the UE. Therefore, the second mapping mode is
used to multiplex the CTCH and the CCCH/DCCH/MCCH on one FACH.
Based on the current implementation for multiplexing of R99 and MBMS on the SCCPCH,
when the new CTCH is added, two multiplexing solutions are available as follows:
Figure 3-13
CTCH Multiplexing Mode with the MCCH Configured
DTCH
CCCH
FACH
DCCH
MCCH
CTCH
FACH
SCCPCH
26
Figure 3-14
CTCH Multiplexing Mode without the MCCH Configured
DTCH
CCCH
FACH
DCCH
CTCH
FACH
SCCPCH
The two multiplexing modes depend on whether the cell supports the MBMS. From the
easy implementation perspective, these two modes are similar because, upon the
completion of multiplexing on the logical channels, the subsequent processing flow is
totally the same as that has been implemented, and the original implemented channel
flag bits are used continuously without being changed. The only thing that needs
additional consideration is that when the multiplexed CTCH is added, it has the highest
priority as the CCCH/MCCH, and must be able to send information before the period
expires, so the bandwidth of the SCCPCH needs to be increased.
3.4.2
CBS Scheduling Policies

When both the CCCH and DCCH have data, the CCCH data has the higher priority, and
is scheduled first. When there is no data on the CCCH, the DCCH data is scheduled.
When the MCCH is introduced, it carries the important MBMS control information, so it
has the same priority as the CCCH does. With the introduction of the CTCH, when the
CTCH and other logical channels are multiplexed, the CTCH information has the highest
priority for scheduling. If resources permit, the TTI may be filled up with the data blocks of
other logical channels. To sum up, the priorities of these channels for scheduling are as
follows:
Pr iorityCTCH Pr iorityCCCH Pr iorityMCCH Pr iorityDCCH
27
During the non-CBS scheduling period, the scheduling policies about bandwidth sharing
are the same as the former policies. When it is the CBS scheduling time, the CBS has
the highest priority, so it must be guaranteed that CBS data blocks can be scheduled
within each TTI until this CBS message is sent.
Therefore, the CBS scheduling is as follows: According to the bandwidth, TB_SIZE and
TB_num are configured. At the beginning of the scheduling time, the CBS occupies all
bandwidth resources exclusively, and the data on other logical channels are not
scheduled until the CBS message is sent.
3.4.3
CTCH Occasion
The CTCH occasions are identified by the first radio frame of the TTI that can contain
CTCH data. The CTCH occasions are fixed on the system frame number cycle 0... 4095
(i.e. no modulo calculation) and thus repeated cyclically.
The CTCH occasions are determined by a set of parameters.
MTTI: number of radio frames within the TTI of the FACH used for CTCH
N: period of CTCH allocation on S-CCPCH, integer number of radio frames,
MTTI N 256, where N is a multiple of MTTI (see [27] and [31]). N is broadcasted in
system information and corresponds to the parameter UCelInfoFDD.CtchAllocPrd.
MaxSFN: maximum system frame number = 4095 (see [10]).
K:
CBS frame offset, integer number of radio frames. 0 K N-1, where K is a
multiple of MTTI. K represents the start point of the computation of the CTCH occasions,
is
broadcasted
in
system
information
and
corresponds
to
the
parameter
UCelInfoFDD.CbsFrameOffset.
The CTCH occasions are calculated as follows:
SFN = (K + m N), m = 0, 1,..., M, with M chosen that K+MN MaxSFN.
28
If the IE "Period of BMC scheduling messages (P)" is included in System Information

Block type 5 or System Information Block type 5bis then BMC Schedule Messages are
transmitted periodically every P CTCH occasions. One BMC Schedule Message may be
segmented across more than one CTCH occasion. The CTCH occasions that contain the
start of the BMC Schedule Messages are calculated as follows:
SFN = (K + m P N), where m is an integer and 0 SFN MaxSFN
If the IE "Period of BMC scheduling messages (P)" is not included in system information
block type 5 then BMC Schedule Messages could be transmitted in any CTCH occasion.
P corresponds to the parameter UCelInfoFDD.BmcSchMsgPrd. Whether P is
broadcasted
in
system
information
depends
on
the
parameter
UCelInfoFDD.BmcSchMsgPrdPre. This parameter indicates whether the period of BMC

scheduling messages is configured or not. If this parameter is set to "1: True" and CBS is
used in the cell, "Period of BMC scheduling messages (P)" IE will be included in the SIB5,
and BMC Schedule Messages could be transmitted only in "Period of BMC scheduling
messages (P)"; else, the IE will not included in the SIB5 and BMC Schedule Messages
could be transmitted in any CTCH occasion.
3.5
Operation and Maintenance
3.5.1
CBS LICENSE
Whether the CBS function is enabled or not is controlled by the LICENSE parameter
URncFunction.cbsSwitch. If URncFunction.cbsSwitch is enabled, the system supports
the CBS function. If URncFunction.cbsSwitch is disabled, the system does not support
the CBS function.
3.5.2
Signaling Tracing
The SABP signaling on the IU-BC interface can be traced.
29
3.6
ETWS Function
Earthquake and Tsunami Warning Service (ETWS) is a type of Public Warning Service
(PWS) provided by a PLMN operator, which transmits disaster information, like
earthquake and tsunami, from alarm originators (usually some government organizations)
to users. For the architecture of the ETWS system, see the following figure.
Figure 3-15
ETWS System Architecture
The basic description of the RNC ETWS paging processing is as follows:

For the ETWS cell broadcast, besides the standard BMC broadcast process, the RNC
also requires the ETWS paging process. To be specific, upon receipt of the ETWS
information, the RNC may regard it as valid if the WRITE-REPLACE message on the
IuBC interface contains the Paging ETWS Indicator and Warning Type (WT).
1.
To the IDLE, PCH, and FACH users, the system sends the Paging Type 1 message
through PCCH/PCH or the SYSTEM INFORMATION CHANGE INDICATION
message (including WT) through BCCH/FACH to notify the UE of the warning type.
30
2.
If the WS is valid, upon completion of step 1, the system sends the ETWS
PRIMARY NOTIFICATION WITH SECURITY message that carries the WT and WS
(Warning Security Information) through the CCCH..
3.
For the DCH user, the system sends directly the ETWS PRIMARY NOTIFICATION
WITH SECURITY message that carries WT and WS through the DCCH.
In this version, the RNC supports only one valid piece of ETWS information. If the CBC
updates the valid ETWS information, the BMC entity on the RNC user plane instantly
updates the ETWS information on the Uu interface, which replaces the existing old
information. The RNC control plane instantly sends ETWS PRIMARY NOTIFICATION
WITH SECURITY messages to update the ETWS information received by the DCH
users.
Parameters
4.1
Radio Parameter
Table 4-1
Parameter
Name
Parameter Description
GUI Name
Parameter
Value
Description
Range
Unit
Default
Recommend
Value
ed Value
This
parameter
indicates
the
switch for the

Cell
URncFunc
tion.cbsSw
itch
Broadcast
CBS
Switch
Function Service (CBS) 0:off

function. If it is 1:on
set
to
(On),
N/A
0:off
"1"
the
RNC supports
the
CBS
function. If it is
set
to
"0"
31
Parameter
Name
GUI Name
Parameter
Value
Description
Range
(Off),
Unit
Default
Recommend
Value
ed Value
the
RNC does not

support
the
CBS function.
0: Carrying
PCH
1: Carrying
R99
FACH, not
Supporting
CBS
2: Carrying
R99
FACH,
This
Supporting
parameter
indicates
the
purpose
of
SCCPCH.
It
should
USccpch.s
ccpchUsa
ge
SCCPCH
Usage
be
configured
according
to
whether PCH,
CBS
3: Carrying
R99
FACH&PC
H,
not
Supporting
Sccpch_Def Sccpch_Defa
CBS
ault
ult
R99 FACH or 4: Carrying

MCCH
is R99
carried by this FACH&PC
SCCPCH and H,
whether CBS Supporting
is supported. CBS
5: Carrying
MCCH
FACH&R9
9
FACH,
not
Supporting
CBS
6: Carrying
MCCH
FACH&R9
32
Parameter
Name
GUI Name
Parameter
Value
Description
Range
9
Unit
Default
Recommend
Value
ed Value
FACH,
Supporting
CBS
7: Carrying
MCCH
FACH
0:
The
SCCPCHs
parameter
are
indicates
Configured
typical
SCCPCH
Supporting
not
configuration MBMS,
not
scenarios.
The
Supporting
approviate
CBS
scenario can 1:
be
chosen SCCPCHs
according
FDD.sccpc
hCfgScen
e
SCCPCH
Configuration
Scene
or ,
be supported MBMS,
and
1,2
whether Supporting
or
are
not
should Supporting
3 CBS
SCCPCHs
2:
are
SCCPCH
2 1:
SCCPCHs SCCPCHs
Configured
MBMS
CBS
0:
to are
whether
UUtranCell
are
Configured, Configured,
N/A
not
not
Supporting Supporting
MBMS, not MBMS,
Supporting Supporting
CBS
CBS
configured.Fo is
r
each Configured
scenario, the ,
not
correspondin Supporting
g
load MBMS,
balance
not
parameters
Supporting
can be set as CBS

different
3:
values.
SCCPCH
is
33
Parameter
Name
GUI Name
Parameter
Value
Description
Range
Unit
Default
Recommend
Value
ed Value
Configured
,
not
Supporting
MBMS,
Supporting
CBS
4:
SCCPCHs
are
Configured
,
Supporting
MBMS,
not
Supporting
CBS
5:
SCCPCHs
are
Configured
,
Supporting
MBMS,
Supporting
CBS
6:
SCCPCHs
are
Configured
,
Supporting
MBMS,
not
Supporting
CBS
7:
SCCPCHs
are
Configured
34
Parameter
Name
GUI Name
Parameter
Value
Description
Range
Unit
Default
Recommend
Value
ed Value
,
Supporting
MBMS,
Supporting
CBS
This
parameter
indicates
the
Service Area
Code
for
(SAC)
the
BC
domain that a
cell uses. This
parameter
should
be
configured
if
the
cell
supports
the
Cell
Broadcast
UUtranCell
FDD.refUS
erviceArea
BC
Used
Service
Area
in
Domain
BC
Service
(CBS).
An
SACPC
NULL
N/A
N/A
N/A
uniquely
identifies one
or
multiple
cells
that
belong to the
same
Location Area
(LA). An SAC
indicates
UE
the
location
for the Core

Network (CN).
An SAC is a
part of an SAI
(that is, SAI =
PLMN-ID
35
Parameter
Name
GUI Name
Parameter
Value
Description
Range
Unit
Default
Recommend
Value
ed Value
LAC + SAC).
The SAC is
set
by
an
operator
through
the
RNC O&M. A
cell
can
belong to one
or two SAs,
correspondin
g to one or
two
SACs
respectively.
If
cell
belongs
to
two SAs, one

SAC is used
in
the
BC
domain
and
the other in
the
CS+PS
domain. If a
cell
belongs
to one SA, the

SAC must be
used in the
CS+PS
domain.
The
SA of the BC
domain
contains only
one cell.
This
UServiceA Service
reaBc.sac Code
bc
parameter
Area indicates the
for BC Service Area 0..65535
Domain
Code
for
N/A
N/A
(SAC)
the
domain
N/A
BC
that
36
Parameter
Name
GUI Name
Parameter
Value
Description
Range
the
cell
Unit
Default
Recommend
Value
ed Value
is
referenced.
This
parameter
should
be
configured
if
the
cell
supports
the
Cell
Broadcast
Service
(CBS).
Otherwise,
is
it
not
necessary.
An
SACPC
uniquely
identifies one
or
multiple
cells
that
belong to the
same
Location Area
(LA). An SAC
indicates
UE
the
location
for the Core

Network (CN).
An SAC is a
part of an SAI
(that is, SAI =
PLMN-ID
LAC + SAC).
The SAC is
set
by
an
operator
through
the
RNC O&M. A
cell
can
37
Parameter
Name
GUI Name
Parameter
Value
Description
Range
Unit
Default
Recommend
Value
ed Value
belong to one
or two SAs,
correspondin
g to one or
two
SACs
respectively.
If
cell
belongs
to
two SAs, one

SAC is used
in
the
BC
domain
and
the other in
the
CS+PS
domain. If a
cell
belongs
to one SA, the

SAC must be
used in the
CS+PS
domain.
The
SA of the BC
domain
contains only
one cell.
This
parameter
indicates
the
period
of
BMC
UCelInfoF Period of BMC
DD.BmcSc Scheduling
hMsgPrd Messages
scheduling
(8, 16, 32,
messages,
64,
128,
which is used 256)

for
CTCH frames
Frame 64
64
Scheduling.
The larger the
parameter the
slower
receiving CBS
38
Parameter
Name
GUI Name
Parameter
Value
Description
Range
Unit
Default
Recommend
Value
ed Value
information
and the more
capacity
of
non-CBS
service using
the
same
FACH
as
CBS.The less
the parameter
the
faster
receiving CBS
information
and the less
capacity
of
non-CBS
service using
the
same
FACH
as
CBS.
This
parameter
indicates
whether
the
period
of
BMC
scheduling
UCelInfoF
DD.BmcSc
hMsgPrdP
re
Period of BMC
Scheduling
Messages
Configuration
Tag
messages
is
configured or
not.
this 0:off
If
parameter
set
is 1:on
to
N/A
"1:
True"
and
CBS is used
in
the
cell,
"Period
of
BMC
scheduling
messages
(P)" IE will be
39
Parameter
Name
GUI Name
Parameter
Value
Description
Range
included
Unit
Default
Recommend
Value
ed Value
in
the SIB5, and

BMC
Schedule
Messages
could
be
transmitted
only
in
"Period
of
BMC
scheduling
messages
(P)"; else, the
IE
will
not
included
in
the SIB5 and

BMC
Schedule
Messages
could
be
transmitted in
any
CTCH
occasion.
This
parameter
indicates
CBS
the
frame
offset, used to
calculate the
UCelInfoF
DD.CbsFr
ameOffset
CTCH
CBS
Offset
Frame occasions.
The
formula
is:
(0..255)fra
mes, step Frame 8
1frame
SFN = (K + m
N), m = 0,
1, ..., M. M
takes K + mN
<= MaxSFN.
MTTI: number
40
Parameter
Name
GUI Name
Parameter
Value
Description
Range
of
Unit
Default
Recommend
Value
ed Value
radio
frames within
the TTI of the
FACH
used
for CTCH
N: period of
CTCH
allocation on
S-CCPCH,
integer
number
of
radio frames,
MTTI * N *
256, where N
is a multiple of
MTTI.
MaxSFN:
maximum
system frame
number
4095.
K: CBS frame
offset, integer
number
radio
of
frames
0 * K * N-1
where K is a
multiple
of
MTTI.
This
parameter
indicates
UCelInfoF
DD.CtchAll
ocPrd
the
CTCH
Period of CTCH occasions.
Allocation
The
CTCH
occasions are
(1..256)fra
mes, step Frame 64
64
1frame
calculated as
follows:
SFN = (K + m
41
Parameter
Name
GUI Name
Parameter
Value
Description
Range
Unit
Default
Recommend
Value
ed Value
N), m = 0,
1, ..., M, with
M chosen that
K + MN <=
MaxSFN.
The
parameters N
and
are
broadcast as
system
information.
MTTI: number
of
radio
frames within
the TTI of the
FACH
used
for CTCH.
N: period of
CTCH
allocation on
S-CCPCH,
integer
number
of
radio frames,
MTTI * N *
256, where N
is a multiple of
MTTI.
MaxSFN:
maximum
system frame
number
4095.
K: CBS frame
offset, integer
number
radio
of
frames
0 * K * N-1
where K is a
42
Parameter
Name
GUI Name
Parameter
Value
Description
Range
multiple
Unit
Default
Recommend
Value
ed Value
of
MTTI.
4.2
Ground Parameter
Parameter
Name
GUI Name
Parameter
Value
Description
Range
Unit
Default
Recommend
Value
ed Value
Considering
multiple CBCs
may
be
supported
later,
this
parameter
is
used
to
represent the
key indexes of
UIubcLink.
CBC
UIubcLinkI
connections, 1
starting
Same
None
None
None
None
None
None
from
as
default value.
1. At present,
the
system
supports only
one
CBC
connection,
so
this
connection
number
can
only be 1.
This
The Cmp Module
UIubcLink. No. which is used

refModule to provide CBC
function
parameter
indicates
the
CMP module None

on which the
CBC
service
is started.
UIubcLink. CBC connection This
LocalRole mode
parameter
0,1
0:Client
43
Parameter
GUI Name
Name
Parameter
Value
Description
Range
indicates
Unit
Default
Recommend
Value
ed Value
the 1:Server
CBC(Cell
Broadcast
Center)
connection
mode,
which
determines
whether
RNC
the
serves
as a client or
server when a
TCP
connection is
established
between
the
RNC and the

CBC.
This
parameter
UIubcLink.
LocalIpVer
sion
The
Local
Address
IP
Length
for
CBC
Connection
indicates
the
IP version of 4,16
the local IP 4:Ipv4
None
None
None
None
None
None
None
None
address of the 16:Ipv6

CBC
connection,
IPv4 or IPv6.
This
parameter
UIubcLink. The
Local
IP indicates
the
LocalIpAd Address for CBC local

dr
Connection
IP None
address of the
CBC
connection.
This
UIubcLink.
refVpnVrf
The
Local
IP parameter
Address Vpn for determines
None
CBC Connection the VPN for
the local IP
44
Parameter
GUI Name
Name
Parameter
Value
Description
Range
Unit
Default
Recommend
Value
ed Value
address of the
CBC
connection.
This
parameter
UIubcLink.
PeerIpVer
sion
The
Peer
Address
IP
Length
for
CBC
Connection
indicates
the
IP version of 4,16
the remote IP 4:Ipv4
None
None
None
None
None
0..128
None
None
None
0..63
None
46
None
address of the 16:Ipv6

CBC
connection,
IPv4 or IPv6.
This
parameter
UIubcLink. The
Peer
IP indicates
the
PeerIpAdd Address for CBC remote

r
IP None
address of the
Connection
CBC
connection.
This
parameter
UIubcLink. The
Peer
IP
PeerIpMas Address Mask for

kLen
CBC Connection
indicates
mask
the
length
of the remote
IP address of
the
CBC
connection.
This
parameter
indicates
the
DSCP(Differe
UIubcLink. DSCP for CBC ntiated
TcpIpDscp Connection
Services
Code
Point)
value of the
CBC
connection.
45
Related Counters and Alarms
5.1
Related Counters
Table 5-1
Related Counters for Iu-BC Messages
Counter No.
Description
C310720351
Number of Write-Replace Msg From CBC
C310720352
Number of Write-Replace Complete Msg To CBC
C310720353
Number of Write-Replace Failure Msg To CBC
C310720354
Number of Kill Msg from CBC
C310720355
Number of Kill Complete Msg to CBC
C310720356
Number of Kill Failure Msg to CBC
C310720360
Number of Message Status Query Msg From CBC
C310720361
Number of Message Status Query Complete Msg To CBC
C310720362
Number of Message Status Query Failure Msg To CBC
C310720363
Number of RESET Msg From CBC
C310720364
Number of RESET Complete Msg To CBC
C310720365
Number of RESET Failure Msg To CBC
C310720366
Number of Restart Msg To CBC
Table 5-2
Related Counters for Iu-BC Flow:
Counter No.
Description
C310720369
Total Msg Bytes From CBC
C310720370
Total Msg Bytes Msg To CBC
Table 5-3
Related Counters for Uu Interface:
Counter No.
C310055563
Description
Downlink traffic of CTCH
46
5.2
Related Alarms
This feature has no related alarms.
Engineering Guide
6.1
Application Scenario
This feature supports cell broadcast services in RNC. The target of the CBS involves all
mobile users in a certain area, including roaming users. This feature should be enabled
according operators requirement.
This feature cannot be used if UEs do not support the CBS function. If most UEs in an
area do not support the function, it is not suggested to enable the feature.
6.2
Feature Activation Procedure

The purpose of this chapter is just to guide the reader how to find the GUI location of the
parameters which are related to the deployment of this feature. The values indicated by
the captures possibly are not the real value to configure. Please refer to the last column
of table in chapter 4 for the practical configuration value.
In the configuration resource tree window, open the [Modify Area->Managed
Element->UMTS Logical Function Configuration] interface and set the parameter CBS
Function Switch, as shown in Figure 6-1.
47
Figure 6-1
Parameters configuration interface 1
In the configuration resource tree window, open the [Modify Area->Managed Element->
UMTS Logical Function Configuration->UTRAN Cell] interface and set the parameter
Used Service Area in BC Domain and SCCPCH Configuration Scene, as shown in
Figure 6-2.
48
Figure 6-2
UMTS Logical Function Configuration->UTRAN Cell->Extended Info of UTRAN Cell]
interface and set the parameter Period of BMC Scheduling Messages, Period of BMC
Scheduling Messages Configuration Tag, CBS Frame Offset and Period of CTCH
Allocation, as shown in Figure 6-3.
49
Figure 6-3
UMTS Logical Function Configuration->UTRAN Cell->Extended Info of UTRAN Cell]
interface and set the parameter Service Area Code for BC Domain, as shown in Figure
6-4.
50
Figure 6-4
Path: View->Configuration Management->Managed Element ->Transport Network->IP

Configuration ->IP Interface Configuration->Ethernet Interface -> Ethernet IP
Interface->Parent MO description, IP Address, Subnet Mask Length
51
Figure 6-5
Configured an IP address used for Service IP of RNC for CBS

Path: View->Configuration Management->Managed Element ->Transport Network->IP
Configuration ->IP Interface Configuration->Loopback IP Interface->Parent MO
Description, IP Address 1, Subnet mask length of the first IP Address
52
Figure 6-6
Configured IUBC link

Path: Managed Element->UMTS Logical Function Configuration->Link
Configuration->IuBC Link-> IuBC Link Object ID, CBC connection mode, The Cmp
Module No. which is used to provide CBC function, The Local Ip Address for CBC
Connection, The Local Ip Address Length for CBC Connection, The Peer Ip Address for
CBC Connection, The Peer Ip Address Length for CBC Connection, The Peer Ip Address
Mask for CBC Connection, DSCP for CBC Connection
53
Figure 6-7
6.3
Feature Validation Procedure

Table 6-1
Feature Validation Procedure
Test Item
54
Test Item
Preconditio
ns

1.
WCDMA and CBC system are ready.
2.
Iu-BC interface works normally.
3.
WCDMA Cell1 supports HSUPA, HSDPA and DCH. Cell1 belongs

to RNC1/NodeB1.
4.
UE1 camps on Cell1 in Idle mode.
1.
Add some topics to cell broadcast topic list on CBC.
2.
Set the status of some topic to subscribe, set other topics status to
Test Steps
Unsubscribed.
3.
Anticipative
Result
6.4
Turn on CB message reception on UE1.
In step3, Cell broadcast messages are received correctly by UE,

messages which are subscribed can be received; messages which are
unsubscribed cant be received.
Feature Deactivation Procedure

Table 6-2
RNC parameter list 3
Managed Object. logic

name
URncFunction.cbsSwitch
6.5
Default Value
GUI Name
CBS
Function
Switch
Deactivation
Value
0:Off
0:Off
Impact on the Network

In this feature, CBS contents transformation shall occupy the FACH band. The following
counters are influenced by this feature.
Counters that the values will increase:

C310053370 DL payload volume of signal fach
C310053374 DL header volume of signal fach
55
C310055563 Downlink traffic of CTCH
Counters that the values may decrease:

C310053371 DL payload volume of data fach
C310053375 DL header volume of data fach
FACH average use rate counters including both signaling and data may increase:
C310476527 Statistics Times of SigFach Use Rate
C310474569 Sum of SigFach Use Rate
C310476529 Statistics Times of DataFach Use Rate
C310474575 Sum of DataFach Use Rate
Abbreviation
Abbreviation
Full Name
rd
3GPP
3 Generation Partnership Project
BCCH
Broadcast Control Channel
BMC
Broadcast/Multicast Contro
CBC
Cell Broadcast Center
CBE
Cell Broadcast Entity
CBS
CN
Core Network
CS
Circuit Switch
CTCH
Common Traffic Channel
DL
Down Link
ETWS
Earthquake and Tsunami Warning System
PS
Packet Switch
PWS
Public Warning Service
RNC
Radio Network Controller
SABP
Service Area Broadcast Protocol
56
SAC
Service Area Code
TNS
Transport Network Sub-system
UL
Up Link
UTRAN
UMTS Terrestrial Radio Access Network
WCDMA
Wideband Code Division Multiple Access
Reference Document
[1]ZXUR
9000
UMTS(V4.13.10.15)Radio
Network
Controller
Radio
Parameter
Reference
[2]ZXUR 9000 UMTS(V4.13.10.15)Radio Network Controller Ground Parameter
Reference
[3]ZXUR 9000 UMTS(V4.13.10.15)Radio Network Controller Performance Counter
Reference
[4]ZXWR RNC(V3.13.10.15)Radio Network Controller Radio Parameter Reference
[5]ZXWR RNC(V3.13.10.15)Radio Network Controller Ground Parameter Reference
[6]ZXWR RNC(V3.13.10.15)Radio Network Controller Performance Counter Reference
57

ZTE UMTS Cell Broadcast Service Feature Guide

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

ZTE UMTS Cell Broadcast Service Feature Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

Cell Broadcast Service

Cell Broadcast Service

Cell Broadcast Service

2014 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary

Cell Broadcast Service

Feature Attribute ............................................................................................... 6

Technical Description ....................................................................................... 8

Related Counters and Alarms ........................................................................ 46

Engineering Guide .......................................................................................... 47

ZTE Confidential Proprietary

Cell Broadcast Service

Feature Validation Procedure ............................................................................ 54

ZTE Confidential Proprietary

Cell Broadcast Service

ZTE Confidential Proprietary

Cell Broadcast Service

Table 2-1 License Control List .............................................................................................8

ZTE Confidential Proprietary

Cell Broadcast Service

: involved, -: not involved

ZTE Confidential Proprietary

Cell Broadcast Service

Logical Architecture of the CBS System

ZTE Confidential Proprietary

Cell Broadcast Service

License Control List

Correlation with Other Features

ZTE Confidential Proprietary

Cell Broadcast Service

CBS System Architecture

ZTE Confidential Proprietary

Cell Broadcast Service

Basic Network Structure of a CBS System

CBS Basic Function

Modifying or deleting CBS messages sent to an RNC

ZTE Confidential Proprietary

Cell Broadcast Service

Initiating broadcasts by sending fixed-length CBS messages to a BSC/RNC in each

Determining the cells to which a CBS message should be broadcast, which

Determining the start time when a CBS message should be broadcast

Identifying the emergency broadcast service if there is one as required by the R8

UUtranCellFDD.sccpchCfgScene and USccpch.sccpchUsage parameters. A cell can

UUtranCellFDD.sccpchCfgScene and USccpch.sccpchUsage has the value that

ZTE Confidential Proprietary

Cell Broadcast Service

Supporting the SABP

ZTE Confidential Proprietary

Cell Broadcast Service

Restart Indication Procedure: Successful Operation

ZTE Confidential Proprietary

Cell Broadcast Service

Figure 3-3 Write-Replace Procedure: Successful Operation

Figure 3-4 Write-Replace Procedure: Unsuccessful Operation

ZTE Confidential Proprietary

Cell Broadcast Service

Status Query Function

Message Status Query Procedure: Successful Operation

MESSAGE STATUS QUERY

Message Status Query Procedure: Unsuccessful Operation

MESSAGE STATUS QUERY

ZTE Confidential Proprietary

Cell Broadcast Service

Reset Procedure: Successful Operation