zte umts cbs feature guide

CBS WCDMA RAN

Feature Guide

Operator Logo

CBS Feature Guide

ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. I

CBS Feature Guide

Version Date Author Approved By Remarks

V4.50 2010-10-15 Lin Yumei Yang Ping Not open to the Third Party

2010 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.

CBS Feature Guide

ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. II

TABLE OF CONTENTS

1 Function Attributes ............................................................................................. 1

2 Overview .............................................................................................................. 1 2.1 Function Introduction ............................................................................................ 1 2.1.1 Cell Broadcast Service.......................................................................................... 1

3 Technical Description......................................................................................... 2

3.1 CBS System Architecture ..................................................................................... 2 3.2 Basic CBS Functions ............................................................................................ 3 3.2.1 Supporting the SABP Protocol ............................................................................. 4 3.2.2 RESTART Function .............................................................................................. 5 3.2.3 WRITE/REPLACE/KILL Functions ....................................................................... 5 3.2.4 Status Query Function .......................................................................................... 7 3.2.5 RESET Function ................................................................................................... 8 3.3 Interconnection Solution ....................................................................................... 9 3.3.1 Interconnection with a Third-Party CBC ............................................................... 9 3.3.2 EMS Built-in CBC................................................................................................ 10 3.3.3 CBC Transmission Policies ................................................................................ 11 3.4 Key Algorithm ...................................................................................................... 12 3.4.1 Channel Mapping and Multiplexing Principles ................................................... 13 3.4.2 CBS Scheduling Polices ..................................................................................... 14 3.5 Operation and Maintenance ............................................................................... 15 3.5.1 CBS LICENSE .................................................................................................... 15 3.5.2 Signaling Tracing ................................................................................................ 15 3.6 ETWS Function ................................................................................................... 15

4 Parameters and Configuration ........................................................................ 17

4.1 Parameter List ..................................................................................................... 17 4.2 Parameter Configuration..................................................................................... 18 4.2.1 CbsLicense ......................................................................................................... 18 4.2.2 SACBPre ............................................................................................................. 18 4.2.3 SACB................................................................................................................... 18 4.2.4 SignalFach .......................................................................................................... 19 4.2.5 CtchAllocPrd ....................................................................................................... 19 4.2.6 CbsFrameOffset.................................................................................................. 19 4.2.7 BmcSchMsgPrdPre............................................................................................. 20 4.2.8 BmcSchMsgPrd .................................................................................................. 20 4.2.9 CtchInd ................................................................................................................ 20 4.2.10 CbcRspModule.................................................................................................... 21 4.2.11 CbcConnectMode ............................................................................................... 21 4.2.12 CbcTcpId ............................................................................................................. 21 4.2.13 CbcTcpLocIpAddr ............................................................................................... 21 4.2.14 CbcTcpPeerIpAddr ............................................................................................. 22 4.2.15 CbcTcpPeerIpMask ............................................................................................ 22

5 Counter and Alarm............................................................................................ 23

5.1 Counter List ......................................................................................................... 23

CBS Feature Guide

ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. III

5.2 Alarm List ............................................................................................................ 23

6 Abbreviations .................................................................................................... 23

CBS Feature Guide

ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. IV

FIGURES

Figure 3-1 Basic Network Structure of CBS system ............................................................... 3

Figure 3-2 Restart Indication Procedure: Successful Operation............................................. 5

Figure 3-3 Write-Replace Procedure: Successful Operation .................................................. 6

Figure 3-4 Write-Replace Procedure: Un-Successful Operation ............................................ 6

Figure 3-5 Message Status Query Procedure: Successful Operation .................................... 7

Figure 3-6 Message Status Query Procedure: Un-Successful Operation .............................. 7

Figure 3-7 Reset Procedure: Successful Operation................................................................ 8

Figure 3-8 Reset Procedure: Un-Successful Operation.......................................................... 8

Figure 3-9 Integrated ZTE RNC With CBC ............................................................................. 9

Figure 3-10 Connection Mode ................................................................................................. 9

Figure 3-11 EMS Built-in CBC network topology .................................................................. 10

Figure 3-12 CTCH multiplexing mode with the MCCH configured ....................................... 13

Figure 3-13 CTCH multiplexing mode without MCCH configured ........................................ 14

Figure 3-14 ETWS system architecture................................................................................. 16

CBS Feature Guide

ZTE Confidential Proprietary 2010 ZTE Corporation. All rights reserved. 1

1 Function Attributes

System version: [RNC V3.09, Node B V4.09, OMMR V3.09, and OMMB V4.09]

Attribute: [Optional function]

Involved NE:

UE NodeB RNC MSCS MGW SGSN GGSN HLR

- - - - - -

Note:

* -: Not involved

* : Involved

Dependency: [None]

Mutual exclusion: [None]

Note: [None]

2 Overview

2.1 Function Introduction

2.1.1 Cell Broadcast Service

This feature provides the Cell Broadcast Service (CBS, also referred to as SMS-CB). As

a basic telecommunication service defined by the UMTS system, it is intended to send

textual short messages to all users in a certain radio area in a broadcast way without

need of connection or confirmation. The CBS service is different from the point -to-point

SMS service in that the recipient of the latter is a specific mobile user, while the recipient

of the former refers to all mobile users in a specific area, including the external users

roaming into 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 alarm, weather forecast, traffic condition, enterprise advertisement,

news, and quotations on the stock markets. In the 3G network, the CBS service can be

used for two major types of applications: one is for cooperation with government

departments to use the cell broadcast as a platform for publishing public information, like

above-mentioned disastrous weather forecast and emergency broadcast; the other is to

serve as a mobile advertisement carrier, which enables cooperation between operators

CBS Feature Guide


and enterprises to use the cell broadcast as an important means of mobile

advertisements in this day and age when mobile media advertisements are booming. To

operators, for one thing, more and more government departments and enterprises are

included as VIP customers in the cell broadcast information sources; for another,

successful application of cell broadcast may produce a positive brand ef fect, attracting

more users to their communications networks and promote development of other

services of the mobile networks. Therefore, there are optimistic prospects for application

of the CBS service when int roduced to the UMTS network due to its low investment and

diversified forms.

3 Technical Description

3.1 CBS System Architecture

The CBS service, similar to the caption play service for digital television, 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 a whole PLMN and

determined through negotiation between information providers and operators. The page

of each CBS message can contain 82 octets, which can represent 93 characters in the

case of use of the GSM default character table defined by 3GPP. Each CBS message

can contain 15 pages at most, all of which have the same tag indicating they belong to

the same message, and each of which has an associated serial number. Each CBS

message also carries message classification and language information, and the UE can

be set to shield undesirable short messages, like those broadcast in an unknown

language. CBS messages are broadcast periodically in cells, and both transmission

frequency and duration can be determined by information providers. For example, traffic

information needs to be updated at a larger frequency than antenna information;

messages in a fast-moving environment need a shorter period.

ZTE system supports two ways providing CBC service:

Adopting EMS built-in to simplify CBC, OMCR provides CBC access function, EMS

provides CBC processing function;

Adopting Interconnection with a Third-Party CBC by IuBC interface, the basic

network structure of CBS system is below.

CBS Feature Guide


Figure 3-1 Basic Network Structure of CBS system

Uu

Cell

BroadcastCenter

(CBC)

UTRAN

RNC Node B

Node B UE

UE

1

Iub

IuBC

CBE

CBE

The CBS system architecture can be implemented as in the illustration above, in which a

CBC (Cell Broadcast Center) connects with an RNC through an IuBC inter face and

connects with two CBEs with interface 1. One CBC can connect with multiple RNCs and

CBEs, and one RNC may connect with multiple CBC nodes. Each CBC node is an

external node of the RNC. Moreover, a CBE is responsible for all aspects of formatting

CBS, including the splitting of a CBS message into a number of pages, and interface 1

between CBEs and between a CBE and a CBC is not defined in the 3GPP specifications

but defined by equipment providers themselves.

3.2 Basic CBS Functions

In the UMTS system, a CBC is an integral part of the CN (while in the GSM system, a

CBC is independent) and is used to manage CBS messages. Physically, a CBC can

connect with an RNC through a routing node like SGSN, and on the upper layer are

used the IuBC logic interface and the SABP protocol. 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 functions as follows:

Modifying or deleting CBS message held to an RNC;

Initiating broadcast by sending fixed length CBS messages to a BSC/RNC for each

language provided by the cell, and where necessary padding the pages to a length

of 82 octets. Send length-fixed CBS message to RNC, if the message is shorter

than 82 bytes, Padding data will be added

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

indicating within the Serial Number the geographical scope of each CBS message

Determining the time at which a CBS message should commence being broadcast

Determining the time at which a CBS message should cease being broadcast and

subsequently instructing each RNC to cease broadcast of the CBS message

CBS Feature Guide


Determining the period at which broadcast of the CBS message should be

repeated

Being able to identify an emergency broadcast service as required by the R8

protocol in order to implement PWS (ETWS).

A CBC sends to a RNC the CBS data and control commands in the form of message

primitive, and it is the RNC that actually carries out broadcast of CBS messages in

specified cells.

Whether a cell supports the CBS service is controlled jointly by the SACBPre and

CbsLicense parameters. When both parameters are TRUE, the cell can suppo rt the

service, or otherwise not. When SACBPre is TRUE, the SACB is valid, or otherwise not.

The parameter SACB represents 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 to a CN the location of a UE. One cell has one or

two SACs. One is CS+PS-domain SAC, and the other is BC-domain SAC. Any BC-

domain SA can contain only one cell.

When there is a new CBS service, the Period of CTCH Allocation cell will be used to

notify the UE of the scheduling period of this CBS message, which corresponds to the

parameter CtchAllocPrd, a mandatory parameter; the CBS Frame Offset cell will be used

to notify the UE of the transmission deviation time of this CBS message, which

corresponds to the parameter CbsFrameOffset, also a mandatory parameter. The

CtchInd parameter is used to indicate whether there is a CTCH mapped to the FACH. At

present, the OMCR is configured with three FACHs in total. One is used to carry the R99

signaling, one the R99 data, and the other the MCCH. The parameter SignalFach

indicates the usage of these FACHs.

3.2.1 Supporting the SABP Protocol

The SABP (Service Area Broadcast Protocol) is a 3G UMTS protocol used for

information broadcast service, and is a protocol that belongs to the Iu-BC domain.

Introduced to implement cell broadcast function, it is mainly used for 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

protocol implements the functions of control signaling and data transmission. To

implement the CBS function, in the RRC protocol stack defined by the 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 service. The BmcSchMsgPrdPre parameter

indicates whether a transmission period is configured for the BMC scheduling

information, and the BmcSchMsgPrd parameter indicates the transmission period of the

BMC scheduling information.

CBS Feature Guide


This feature additionally implements the SABP protocol to support the WRITE-

REPLACE (hereinafter called WR), KILL, MESSAGE STATUS QUERY, RESTART, and

RESET, as well as their response messages. RESTART and RESET 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 indicate to the CN that

a Service Area broadcasting related restart situation has occurred in one or more of its

Service Areas e.g. when a Service Area becomes operational or when the RNC is

initialized.

The CBS service supports RESTART of a service area/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.

Figure 3-2 Restart Indication Procedure: Successful Operation

CN

RESTART

RNC

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 service supports write, modification, and deletion (WR/KILL) of broadcast

messages.

The purpose of this Write-Replace procedure is to broadcast new i nformation or replace

a message already broadcast to a chosen Service Area(s). And 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 broadcasting of a new message or replace a message

CBS Feature Guide


already broadcast as requested to the service areas as indicated in the Service Area(s)

List.

Figure 3-3 Write-Replace Procedure: Successful Operation

CN

WRITE-REPLACE

WRITE-REPLACECOMPLETE

RNC

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 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 as

requested and 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: Un-Successful Operation

CN

WRITE-REPLACE

WRITE-REPLACEFAILURE

RNC

CBS Feature Guide


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

MESSAGE STATUS QUERY

MESSAGE STATUS QUERY COMPLETE

RNC

Figure 3-6 Message Status Query Procedure: Un-Successful Operation

CN

MESSAGE STATUS QUERY

MESSAGE STATUS QUERY FAILURE

RNC

The CN shall initiate the procedure by sending a MESSAGE STATUS QUERY message

to the RNC.

CBS Feature Guide


In a successful operation: upon receipt of the MESSAGE STATUS QUERY message the

RNC shall respond using the MESSAGE STATUS QUERY COMPLETE message.

In un-successful operation: if the requested operation fails (e.g. because the CBS

message is unknown, or when 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

RESET

RNC

RESET COMPLETE

Figure 3-8 Reset Procedure: Un-Successful Operation

CN

RESET

RNC

RESET FAILURE

CBS Feature Guide


In a successful operation: upon receipt of this message the RNC shall end broadcasting

in the indicated Service Area(s) and shall respond using a RESET COMPLETE

message.

In un-successful operation: if upon receipt of this message the RNC cannot end

broadcasting in the indicated Service Area(s), it shall respond using 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 integration between ZTE RNC and CBC server is shown as

below.

Figure 3-9 Integrated ZTE RNC With CBC

WANRNC CBC

IuBC

TCP Transmission Protocol

Figure 3-10 Connection Mode

WAN

G

I

P

I

R

S

P

RNC

CBC

Router Router

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.

CBS Feature Guide


The following parameters are involved in the configuration process.

CbcConnectMode To configure whether the CBC is connected as a client or a server;

CbcRspModule To configure the RSP ID of the service;

CbcTcpId To configure the TCP connection number for the CBC;

CbcTcpLocIpAddr and CbcTcpPeerIpAddr To configure the local and peer IP addresses

for CBS connection;

CbcTcpPeerIpMask To configure the peer IP address mask for CBC connection.

3.3.2 EMS Built-in CBC

In the networking management system, cell broadcast center system exist as a

subsystem. The system does not consider interface of equipment which provides

broadcasting service, and take the user client as cell broadcast equipment. By adopting

the networking management connecting with RNC, realize the broadcast center function.

It can save for the user to purchase broadcasting center and network costs .

The network topology is as below:

Figure 3-11 EMS Built-in CBC network topology

G

I

P

I

R

S

P

RNC

CBC Server

S

w

i

t

c

h

O

M

M

EMS

Transmission

network

The EMS Built-in CBC networking principle is described below:

1 The RSP is the actual processing module of CBC messages , which means the

external IP address outside is the module No. of the RSP. It can select an existing

RSP board as the processer, and there is no need to add a new RSP board.

2 The GIPI and the switch are responsible for IP forwarding, so the OMM should route the

subnet, which the RSP belongs to, to the GIPI.

CBS Feature Guide


3 Remarkably, the function of the OMM is to forward the service layer data, as shown in the

figure above.

3.1. From the point of the RSP in the RNC, the OMM is the CBC server, and the TCP

connection ends at the OMM;

3.2. From the point of the CBC inside the EMS, the OMM is the RNC, and the TCP

connection ends at the OMM.

4 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.

When adopting the EMS built-in CBC, the following parameters are involved in the

configuration process.

CbcTcpId To configure the TCP connection number for the CBC and it is configured as 1;

CbcConnectMode To configure as server, indicating the CBC is connected as a client or

a server;

CbcTcpLocIpAddr and CbcTcpPeerIpAddr To configure the local and peer IP addresses

for CBS connection. CbcTcpLocIpAddr is configured to a network segment and does not

overlap existing address. CbcTcpPeerIpAddr is configured to the IP of OMM;

CbcTcpPeerIpMask To configure the peer IP address mask of OMM.

3.3.3 CBC Transmission Policies

With regard to the port for the TCP on the Iu-BC interface, there is an agreement in the

TS25.414 protocol that:

1 Both the RNC and CBC can originate 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 the RNC and CBC.

CBS Feature Guide


In addition, although in the bearer protocols in 23.041 and 25.414, the UDP is also listed

as one of the Iu-BC bearer protocols, there is an agreement only for the TCP in 25.414.

Therefore, we only consider implementation of the TCP protocol.

When adopting EMS built-in CBC, system uses passive mode, which means RNC, as

the passive side of TCP, is waiting for OMM starting TCP connection.

The Iu-BC is used mainly to provide TCP service 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:

1 According to the OMC configuration, the transmission originates TCP connection

(active mode) for the CBC or monitors the TCP port of the CBC (passive mode).

Once the connection is built, RNLC will be informed.

2 In the Active Mode, if a disconnection happens, an alarm will be announced and

RNLC will be informed that the connection state has been changed. Besides, a

connection establishment request message will immediately be initiated by TNL,

and then this connection may be fast recovery.

3 If the board mode of handling the Iu-BC connection is changing from Active Mode to

Passive Mode, the TCP connection will be cutoff automatically. If it is from Passive

Mode to Active Mode, the change of the connection should be informed first and

activate a new TCP connection or monitor the TCP port according to the

configuration. After rebuilding the connection RNLC also should be informed.

4 TNL needs to monitor the connected Socket port, and notify the CBS upon receiving

data.

5 TNL needs to receive messages from the upper layer, and forward the required

data to the corresponding Socket.

6 If the local end is the Server, and there is already a connection, any subsequent

connection will be rejected directly.

TNL is responsible mainly for management of the TCP connection of the CBC. The

connection-related information (such as sending data) must be carried in the information

and transferred to the upper-layer TCP ID.

3.4 Key Algorithm

This feature additionally implements the BMC (Broadcast/Multicast Control ) 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 polices.

CBS Feature Guide


3.4.1 Channel Mapping and Multiplexing Principles

According to the related protocols, the CBS service supports two channel mapping

modes as follows:

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, so if the FACH carrying the

CBS is multiplexed with the PCH, it is possible to 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.

Judging from the current implementation of multiplexing of R99 and MBMS on the

SCCPCH, with the new CTCH added, two multiplexing solutions are available as follows:

Figure 3-12 CTCH multiplexing mode with the MCCH configured

DCCHCCCH

FACH

SCCPCH

MCCHDTCH

FACH

CTCH

CBS Feature Guide


Figure 3-13 CTCH multiplexing mode without MCCH configured

DCCHCCCH

FACH

SCCPCH

DTCH

FACH

CTCH

The two multiplexing modes depend on the support attributes of the cells for the MBMS,

and have no difference judging simply from implementation because, upon completion of

multiplexing on the logical channels, the subsequent processing flow is totally the same

as what has been implemented, and the original implemented channel flag bits are used

continuously without change. 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 upon arrival of the period, so it is necessary to

consider increasing the bandwidth of the physical channel SCCPCH.

3.4.2 CBS Scheduling Polices

When both the CCCH and DCCH have data, the CCCH data is considered with higher

priority, and thus is scheduled first. Only when there is no data on the CCCH will the

DCCH data be scheduled. When the MCCH is int roduced, it carries the MBMS control

information, which is very important, so it can be regarded with the same priority as the

CCCH. Now the CTCH is introduced additionally, indicating when the CTCH and other

logical channels are multiplexed, the CTCH information has the highest priority for

scheduling, so if resources permit, the TTI may be filled up with the data blocks on other

logical channels. To sum up, the priorities of these channels for scheduling are as

follows:

Pr Pr Pr PrCTCH CCCH MCCH DCCHiority iority iority iority

During the non-CBS scheduling period, the scheduling polices about bandwidth sharing

are the same as formerly. When the CBS scheduling time arrives, according to the

priorities, 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 out completely.

CBS Feature Guide


Therefore, the CBS scheduling is that: According to the bandwidth, TB_SIZE and

TB_num are configured. Upon start of scheduling time, the CBS occupies all bandwidth

resources exclusively, and the data on other logical channels are not scheduled until the

CBS information is sent out completely.

3.5 Operation and Maintenance

3.5.1 CBS LICENSE

Whether the CBS function is enabled or not is controlled by the LICENSE parameter

CbsLicense. If CbsLicense is enabled, the system supports the CBS function; if

CbsLicense is disabled, the system does not support the CBS function.

3.5.2 Signaling Tracing

The RCBC is used to trace the SABP signaling of the IU-BC interface. As the IU

interface is divided into CS, PS and BC domains, the signaling tracing control method for

the IU-BC domain can be the same as those for the IU-CS/IU-PS interface.

The CBA is used to trace the RCBC-CBA interface signaling and the CBA-BMC interface

signaling. The signaling tracing control method can be the same as those methods for

controlling the inter-RNLC module message and the RNLC-RNLU interface message.

3.6 ETWS Function

ETWS (Earthquake and Tsunami Warning Service) is a type of PWS (Public Warning

Service) provided by the PLMN operator, which transmits to users disaster information,

like earthquake and tsunami, from alarm originators (usually some government

organizations). The ETWS system architecture is illustrated as follows :

CBS Feature Guide


Figure 3-14 ETWS system architecture

Here is a basic note about the RNC ETWS paging processing: for the ETWS cell

broadcast, the RNC needs to have ETWS paging process added, apart from the

standard BMC broadcast process. To be specific, upon receiving ETWS information, the

RNC may regard it as valid i f the WRITE-REPLACE message on the IuBC interface

contains the Paging ETWS Indicator and WT (Warning Type).

1 To the IDLE, PCH, and FACH users, the system sends the Paging Type 1 or

SYSTEM INFORMATION CHANGE INDICATION message, including WT, to

arouse the UE and indicate the warming type.

2 If the WS is valid, upon completion of (1), the system will send through the CCCH

the ETWS PRIMARY NOTIFICATION WITH SECURITY message, which carries

WT and WS (Warning Security Information).

3 For the DCH user, the system will send directly through the DCCH the ETWS

PRIMARY NOTIFICATION WITH SECURITY message, which carries WT and WS.

The internal coordination flow of the RNC ETWS paging process is described as follows:

Upon receiving a WRITE-REPLACE message, the RCBC distributes it to the CBA.

1 Notifying the IDLE/PCH/FACH users.

Upon receiving an EV_RCBC_CBA_WRITE_REPLACE_REQ message, CBA will start

ETWS-related processing if it contains valid ETWS information.

CBS Feature Guide


RNLU assembles the RRC code stream of Paging Type 1, issues Paging Type 1

messages from PCCH/PCH, and issues SYSTEM INFORMATION CHANGE

INDICATION messages from BCCH/FACH.

2 Notifying the DCH users.

The RCBC sends to all RCP boards the ETWS Paging Type 2 messages, which carry a

cell ID list, WT, and WS. (The cell ID lists correspond to the service area lists specified

by the CBC, that is, not only the cell lists associated with each RCP board.) The RCBC

finds out all terminal users and forwards ETWS Paging Type 2 messages to them. The

UCIC starts processing of the ETWS Paging Type 2 messages: if this terminal is in the

DCH state at present, and the current and target active set cells are included in the

ETWS cell list, the UCIC will send the ETWS PRIMARY NOTIFICATION WITH

SECURITY message.

At present, the RNC supports only one valid piece of ETWS information. That is, if the

CBC updates valid ETWS information, the BMC module on the RNC user plane will

instantly update the ETWS information on the Uu interface, which will replace the

existing old information. The RNC control plane will instantly send ETWS PRIMARY

NOTIFICATION WITH SECURITY messages to update the ETWS information of the

DCH users.

4 Parameters and Configuration

4.1 Parameter List Parameter Field Name Interface Name

CbsLicense CBS License

SACBPre SACB Configuration Tag

SACB Service Area Code for BC Domain

SignalFach FACH Usage

CtchAllocPrd Period of CTCH Allocation

CbsFrameOffset CBS Frame Offset

BmcSchMsgPrdPre Period of BMC Scheduling Messages Configuration Tag

BmcSchMsgPrd Period of BMC Scheduling Messages

CtchInd CTCH Indicator

CbcRspModule The RSP Module ID which is used to provide CBS function

CbcConnectMode CBC connection mode

CbcTcpId CBC connection No

CbcTcpLocIpAddr Local IP address for CBC Connection

CbcTcpPeerIpAddr Peer IP Address for CBC Connection

CbcTcpPeerIpMask[16] The Peer IP Address Mask for CBC Connection

CBS Feature Guide


4.2 Parameter Configuration

4.2.1 CbsLicense

OMC path

View -> Configuration Management -> RNC NE -> RNC Radio Resource Management -

> Basic Informationll -> CBS License.

Parameter configuration

This parameter is used to control authorization of the CBS service functions. 0: Disabled;

1: Enabled.

4.2.2 SACBPre

OMC path


> UTRAN Cell -> UTRAN Cell xx -> UTRAN Cell Global Information.


This parameter is the SACB Configuration Tag, indicating whether the SACB is

configured. If this cell supports the CBS, the SACB must be configured. Otherwise, it is

not needed. 0: Not configured; 1: Configured.

4.2.3 SACB

OMC path


> UTRAN Cell -> UTRAN Cell xx -> UTRAN Cell Global Information.


This parameter is the Service Area Code for BC Domain, which identifies uniquely one

or several cells in the same location area (LA). It is used to indicate to a CN the location

of a UE. SAC is an integral part of SAI (SAI = PLMN-ID + LAC + SAC). SAC is set by the

operator through the RNC O&M. One cell has one or two SACs. One is CS+PS-domain

SAC, and the other is BC-domain SAC. There must be one that is a CS +PS domain

SAC. Any BC-domain SA can contain only one cell. This parameter is valid only when

the SACB Configuration Tag is TRUE and the following restraint condition is met: one

LCA+SACB can correspond to only one cell. Its value ranges from 0 to 65535.

CBS Feature Guide


4.2.4 SignalFach

OMC path


> UTRAN Cell -> UTRAN Cell xx -> Modify Advanced Parameter -> FACH.


This parameter indicates the FACH Usage. 0: R99 data; 1: R99 signaling; 2: R99

signaling+MCCH; 3: MCCH.

4.2.5 CtchAllocPrd

OMC path




This parameter carries the Period of CTCH Allocation for the CBS service. When there is

a new CBS, this parameter is used to send a notification to the UE for instruction of the

scheduling period of this CBS information. Its value range: MTTI N 256, which is an

integer multiplier of both the radio frame and MTTI. MTTI means the number of radio

frames (20/10=2) available for the CTCH in the TTI of one FACH

When both CbsLicense and CtchInd are TRUE, it is needed to configure this parameter

CtchAllocPrd.

4.2.6 CbsFrameOffset

OMC path




This parameter indicates the CBS scheduling frame offset. When there is a new CBS,

this parameter is used to send a notification to the UE for instruction of the transmission

offset period of this CBS information. Its value range: 0 K N-1, in which K is the CBS

Frame Offset value, an integer multiplier of both the radio frame and MTTI. MTTI means

the number of radio frames (20/10=2) available for the CTCH in the TTI of one FACH. N

is the value of Period of CTCH Allocation.

CBS Feature Guide


When both CbsLicense and CtchInd are TRUE, it is needed to configure CtchAllocPrd

and CbsFrameOffset, and the latter must be smaller than the former.

4.2.7 BmcSchMsgPrdPre

OMC path




This parameter is the Period of BMC Scheduling Messages Configuration Tag,

indicating whether the transmission period of BMC scheduling messages is configured

or not.

4.2.8 BmcSchMsgPrd

OMC path




This parameter indicates the Period of BMC Scheduling Messages, which is an optional

cell, with the values of 8, 16, 32, 64, 128, and 256. When this cell is configured in the

SIB5, the BMC scheduling messages are transmitted at the intervals of P Periods of

CTCH Allocation, and one piece of BMC scheduling information can be transmitted by

segments in several Periods of CTCH Allocation; if this cell is not configured in the SIB5,

it can be transmitted in any Period of CTCH Allocation.

When CbsLicense, CtchInd, and BmcSchMsgPrdPre are all TRUE, it is needed to

configure this parameter BmcSchMsgPrd.

4.2.9 CtchInd

OMC path


> UTRAN Cell -> UTRAN Cell xx -> Modify Advanced Parameter -> FACH-> CTCH

Indicator.


CBS Feature Guide


This parameter indicates whether there is a logical channel CTCH mapped to this FACH.

It can be configured to 0 or 1. 0 indicates there is no CTCH mapped to the FACH; while

1 indicates there is a CTCH mapped to this FACH.

4.2.10 CbcRspModule

OMC path

View -> Configuration Management -> RNC NE -> Global Supplemented Configuration -

> The RSP Module ID Which is Used to Provide CBS Function.


This parameter is used to enable the CBS RSP module number (RSP ID). It can be

configured to any available RSP. Its value ranges from (128-RSP_MAX) to 127, and 0 is

an invalid value.

4.2.11 CbcConnectMode

OMC path

View -> Configuration Management -> RNC NE -> Global Supplemented Configuration -

> CBC Connection Mode.


This is an interconnection parameter. If the peer CBC is the Server, the local end should

be set as the Client, or otherwise set as the Server. 0: Client; 1: Server.

4.2.12 CbcTcpId

OMC path

View -> Configuration Management -> RNC NE -> RNC Ground Resource Management

-> Transmission Configuration -> IuBC TCP Connection Configuration -> CBC

Connection No.


Considering subsequent possible support of multiple CBCs, this parameter is used to

represent the key indexes of CBC connection, and starts from 1. At present, the system

supports only one CBC connection, so this connection number can be only 1.

4.2.13 CbcTcpLocIpAddr

OMC path

CBS Feature Guide



-> Transmission Configuration -> IuBC TCP Connection Configuration -> Local IP

address for CBC Connection.


As an interconnection parameter, it indicates an available interface IP planned from the

Interface, and the peer needs corresponding configuration. It indicates the local IP

address used for the CBC connection, that is, the IP address used by the RSP.

4.2.14 CbcTcpPeerIpAddr

OMC path


-> Transmission Configuration -> IuBC TCP Connection Configuration -> Peer IP

address for CBC Connection.


This parameter indicates the Peer IP Address for CBC Connection. It is an

interconnection parameter, which is set to the peer IP address, and the corresponding IP

route must be configured appropriately. In the Client mode, this parameter is required; in

the Server mode, this parameter and the subsequent mask indicate the address scope

for connection.

4.2.15 CbcTcpPeerIpMask

OMC path


-> Transmission Configuration -> IuBC TCP Connection Configuration -> The Peer IP

address Mask for CBC Connection.


This parameter indicates the Peer IP Address Mask for CBC Connection. It is available

only in the Server mode, and is used with the peer IP to judge whether the accessed IP

is legal or not. In the Client mode, this parameter must consist of F only; in the Server

mode, this parameter and the previous peer IP address indicate the address scope for

connection.

CBS Feature Guide


5 Counter and Alarm

5.1 Counter List

Iu-BC message statistics

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

Iu-BC traffic statistics

Counter No. Description

C310720369 Total Msg Bytes From CBC

C310720370 Total Msg Bytes Msg To CBC

5.2 Alarm List Alarm No. Description

16778060 TCP connect on IuBC interface is interrupted

16778054 TCP connect on IuBC interface establishment failed

6 Abbreviations

ANSI American National Standards Institute

ARPU Average Revenue Per User

BMC Broadcast and Multicast Control

CBS Feature Guide


CAPEX Capital Expenditure

CBA Cell Broadcast Agent

CBC Cell Broadcast Center

CBE Cell Broadcast Entity

CBS Cell Broadcast Service

CN Core Network

CTCH Common Traffic Channel

DRX Discontinuous Reception

EMS Element Management System

ETWS Earthquake and Tsunami Warning System

FACH Forward Access Channel

GIPI Gigabit IP Interface board

GSM Global System for Mobile communication

IMT International Mobile Telecommunications

ITU International Telecommunication Union

LCS Location Service

LTE Long Term Evolution

MAC Medium Access Control

MBMS Multimedia Broadcast/Multicast Service

NBLOMM Node B Logical Maintenance Model

OPEX Operating Expenditure

OMCR Operations & Maintenance Centre Radio

OMM Operation and Maintenance Module

PLMN Public Land Mobile-communication Network

PWS Public Warning System

CBS Feature Guide


QoS Quality of Service

RB Radio Bearer

RCBC Radio Cell Broadcast Center

RLC Radio Link Control

RNC Radio Network Controller

RNLC Radio Network Layer Control -plane

RNLU Radio Network Layer User-plane

RRC Radio Resource Control

RSP RNC SIGTRAN Signaling Processer

SABP Service Area Broadcast Protocol

SAE System Architecture Evolution

SCCPCH Secondary Common Control Physical Channel

SGSN Serving GPRS Support Node

TCP Transmission Control Protocol

TIA Telecommunication Industry Alliance

TNL Transport Network Layer

UDP User Datagram Protocol

UE User Equipment

UMTS Terrestrial Radio Access Network

WCDMA Wideband Code Division Multiple Access

zte umts cbs feature guide

Documents

zte corporation

proprietary information

cbs wcdma

cbs scheduling

cbs license

improvement of zte products

basic cbs functions

cbs system architecture