6 BSC/RNC/MME/AMF Functionality

23.0413GPPRelease 18Technical realization of Cell Broadcast Service (CBS)TS

The BSC/RNC shall interface to only one CBC. A BSC may interface to several BTSs as indicated by 3GPP TS 48.052 [10]. An RNC may interface to several Node Bs.

The MME may interface to one CBC or multiple CBCs (i.e. the MME is allowed to have SCTP transport associations established with one or multiple CBCs). An MME may interface to several eNodeBs.

The AMF may interface to one CBCF or multiple CBCFs (i.e. the AMF is allowed to have HTTP/2 application layer associations with one or multiple CBCFs). An AMF may interface to several NG-RAN nodes.

The BSC/RNC/MME/AMF shall be responsible for:

BSC

RNC

MME

AMF

Interpretation of commands from the CBC.

Storage of messages from the CBC.

Not applicable

Scheduling of CBS messages on the CBCH.

Scheduling of CBS messages on the CBS related radio resources.

Not applicable

Not applicable

Providing an indication to the CBC when the desired repetition period cannot be achieved.

Not applicable

Providing to the CBC acknowledgement of successful execution/forwarding of commands received from the CBC.

Reporting to the CBC failure when a command received from the CBC is not understood or cannot be executed.

Not applicable.

Not applicable.

Report the Broadcast Completed Area List, the Broadcast Cancelled Area List, PWS Restart Indication and the PWS Failure Indication received from eNB(s) to all CBCs that the MME interfaces with.

Report the Broadcast Completed Area List, the Broadcast Cancelled Area List, PWS Restart Indication and the PWS Failure Indication received from NG-RAN nodes to all CBCFs and PWS-IWFs that the AMF interfaces with.

Routing of CBS messages to the appropriate BTSs.

Routing of CBS messages to the appropriate Node Bs.

Routing of warning messages to the appropriate eNodeBs in the indicated Tracking Area.

Routing of warning messages to the appropriate NG-RAN nodes in the indicated Tracking Area.

Transferring CBS information to each appropriate BTS via a sequence of 4 SMS BROADCAST REQUEST messages or 1 SMS BROADCAST COMMAND message (see 3GPP TS 48.058 [11]), indicating the channel which shall be used.

The Node B has no functionality regarding CBS. This implies that CBS messages do not have to be transmitted explicitly to the Node Bs for further processing.

Not applicable.

Not applicable.

Optionally generating Schedule Messages, indicating the intended schedule of transmissions (see 3GPP TS 44.012 [7]).

Generating Schedule Messages, indicating the intended schedule of transmissions (see 3GPP TS 25.324 [19]). The conversion of GSM related CB DRX Information is a function of the RNC (3GPP TS 25.401 [17]).

Not applicable.

Not applicable.

Optionally receiving CBCH Load Indication messages and reacting by broadcasting a burst of scheduled CBS messages or by suspending the broadcast for a period indicated by BTS (see 3GPP TS 48.058 [11]).

Not applicable.

Not applicable.

Not applicable.

Broadcasting the ETWS Primary Notification message upon receipt of the WRITE-REPLACE message including the Paging-ETWS-Indicator. The ETWS Primary Notification message is broadcasted according to the Warning Period parameter.

Sending ETWS messages to mobile terminals upon receiving CBS transmission request from CBC including the Paging-ETWS-Indicator. Emergency indication can be included in the paging messages, based on the warning type information conveyed from CBC.

Sending the Write-Replace Warning Request message to the appropriate eNodeBs upon receiving warning message transmission request from CBC.

Sending the Write-Replace Warning Request message to the appropriate NG-RAN nodes upon receiving warning message transmission request from CBCF or PWS-IWFs.

To work efficiently on the interfaces, the BSC/RNC should forward CB related messages to the CBC using cell lists as far as applicable.