9.2 Requirements on the CBC-RAN, CBC-MME and CBCF-AMF interfaces
23.0413GPPRelease 18Technical realization of Cell Broadcast Service (CBS)TS
9.2.0 General
The requirements are described by primitives. The term primitive is used to indicate "an abstract, implementation independent interaction between a service user and a service provider" (see ITU-T Recommendation X.210 [12]). For the CBC-BSC/RNC/MME or CBCF-AMF interface, the service provider would be the protocol interconnecting the CBC and BSC/RNC/MME or the CBCF and AMF. A Primitive may therefore be viewed as an abstract, implementation independent request/indication or response/confirm interaction between the service user (CBC/CBCF or BSC/RNC/MME/AMF) and the service provider (protocol). A set of primitives for use between the CBC and BSC/RNC/MME and CBCF and AMF are specified appropriate to the functionality assigned to the CBC/CBCF and BSC/RNC/MME/AMF in clause 5 and clause 6. In order to allow future extensions to the primitives, where possible a primitive shall not be rejected because a parameter is not recognized; the recipient shall ignore the parameter in question and process the remainder of the primitive’s parameters as usual.
NOTE: The primitives for the CBCF-AMF interface are also applicable to the PWS-IWF – AMF interface, and the primitives for the CBC-MME interface are also applicable to the CBC-PWS-IWF interface.
The following table gives an overview over the existing primitives:
|
Name |
Originator |
Type |
Reference |
|
WRITE-REPLACE |
CBC |
Request/Indication |
9.2.2 |
|
KILL |
CBC |
Request/Indication |
9.2.3 |
|
REPORT |
BSC/RNC |
Response/Confirm |
9.2.4 |
|
STATUS-LOAD-QUERY |
CBC |
Request/Indication |
9.2.5 |
|
STATUS-LOAD-QUERY |
BSC/RNC |
Response/Confirm |
9.2.6 |
|
STATUS-MESSAGE-QUERY |
CBC |
Request/Indication |
9.2.7 |
|
STATUS-MESSAGE-QUERY |
BSC/RNC |
Response/Confirm |
9.2.8 |
|
REJECT |
BSC/RNC |
Response/Confirm |
9.2.9 |
|
RESTART-INDICATION |
BSC/RNC |
Request/Indication |
9.2.10 |
|
RESET |
CBC |
Request/Indication |
9.2.11 |
|
FAILURE-INDICATION |
BSC/RNC |
Request/Indication |
9.2.12 |
|
SET-DRX |
CBC |
Request/Indication |
9.2.13 |
|
SET-DRX-REPORT |
BSC |
Response/Confirm |
9.2.14 |
|
WRITE-REPLACE-WARNING-REQUEST |
CBC |
Request/Indication |
9.2.16 |
|
WRITE-REPLACE-WARNING-CONFIRM |
MME |
Response/Confirm |
9.2.17 |
|
STOP-WARNING-REQUEST |
CBC |
Request/Indication |
9.2.18 |
|
STOP-WARNING-CONFIRM |
MME |
Response/Confirm |
9.2.19 |
|
WRITE-REPLACE-WARNING-INDICATION |
MME |
Request/Indication |
9.2.20 |
|
STOP-WARNING-INDICATION |
MME |
Request/Indication |
9.2.21 |
|
RESTART-INDICATION-E-UTRAN |
MME |
Request/Indication |
9.2.22 |
|
FAILURE-INDICATION-E-UTRAN |
MME |
Request/Indication |
9.2.23 |
|
RESET-COMPLETE |
BSC/RNC |
Response/Confirm |
9.2.24 |
|
RESET-FAILURE |
BSC/RNC |
Response/Confirm |
9.2.25 |
|
WRITE-REPLACE-WARNING-REQUEST-NG-RAN |
CBCF/PWS-IWF |
Request/Indication |
9.2.26 |
|
WRITE-REPLACE-WARNING-CONFIRM-NG-RAN |
AMF |
Response/Confirm |
9.2.27 |
|
STOP-WARNING-REQUEST-NG‑RAN |
CBCF/PWS-IWF |
Request/Indication |
9.2.28 |
|
STOP-WARNING-CONFIRM-NG‑RAN |
AMF |
Response/Confirm |
9.2.29 |
|
WRITE-REPLACE-WARNING-INDICATION-NG‑RAN |
AMF |
Request/Indication |
9.2.30 |
|
STOP-WARNING-INDICATION-NG‑RAN |
AMF |
Request/Indication |
9.2.31 |
|
RESTART-INDICATION-NG‑RAN |
AMF |
Request/Indication |
9.2.32 |
|
FAILURE-INDICATION-NG‑RAN |
AMF |
Request/Indication |
9.2.33 |
In GSM the CBC is integrated into the Core Network. The protocol between the CBC and BSC is defined in 3GPP TS 48.049 [30].
In UMTS the CBC is integrated into the Core Network. The protocol between the CBC and RNC is defined in 3GPP TS 25.419 [29].
In E-UTRAN the CBC is integrated into the Core Network. The protocol between the CBC and MME is defined in 3GPP TS 29.168 [35].
In NG-RAN the CBCF/PWS-IWF is integrated into the Core Network. The protocol between the CBCF/PWS-IWF and AMF is defined in 3GPP TS 29. 518 [41].
NOTE 1: The primitives used in NG-RAN are transported with the NonUeN2MessageTransfer and NonUeN2InfoNotfy service operations between CBCF and the AMF (see clause 9A) and via N2 from AMF to NG-RAN.
NOTE 2: In the following definitions, M indicates "mandatory parameter", O indicates "optional parameter" and C indicates "conditional parameter".
9.2.1 Identification of a CBS message
In GSM within a CBC-BSC interface, a CBS message is uniquely identified by the quartet (Message Identifier, Serial Number, Cell Identifier, Channel Indicator).
In UMTS within the CBC-RNC interface, in E-UTRAN within the CBC-MME interface, and in NG-RAN within the CBCF-AMF interface and CBC – PWS-IWF interface, a CBS message is uniquely identified by the triplet (Message Identifier, Serial Number, Cell Identifier).
This means that even when two CBS messages have the same semantic contents (for example the same weather forecast) but in different languages or coding schemes, they are considered as different and must therefore be identified by a different quartet.
The Serial Number (Old-Serial-Number or New-Serial-Number) is managed cyclically and therefore this does not prevent the re-use of the same quartet for a different CBS message when the serial number have been incremented a sufficient number of times. How to manage the ambiguity is described subsequently.
This unique identification of a CBS message across the CBC-BSC interface is used in all the primitives defined hereafter. This means that the quartet/triplet will be implicitly or explicitly present in every interface primitive which applies to a given CBS message.
This unique quartet/triplet will be referred in the rest of the document as the "message reference".
9.2.2 WRITE-REPLACE Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE (UMTS/GSM) |
|
Message-Identifier |
9.3.1 |
M/M |
|
Old-Serial-Number |
9.3.2 |
O/O |
|
New-Serial-Number |
9.3.3 |
M/M |
|
Cell-List |
9.3.5.1 |
M/M |
|
GSM only [Channel Indicator |
9.3.6 |
O] (note 1) |
|
Category |
9.3.7 |
O/C (note 2) |
|
Repetition-Period |
9.3.8 |
M/C (note 2) |
|
No-of-Broadcasts-Requested |
9.3.9 |
M/C (note 2) |
|
Number-of-Pages |
9.3.4 |
M/C (note 2) |
|
Data Coding Scheme |
9.3.18 |
M/C (note 2) |
|
CBS-Message-Information-Page 1 |
9.3.19 |
M/C (note 2) |
|
CBS-Message-Information-Length 1 |
9.3.20 |
M/C (note 2) |
|
CBS-Message-Information-Page 2 |
9.3.19 |
O/O |
|
CBS-Message-Information-Length 2 |
9.3.20 |
O/O |
|
: |
: |
|
|
CBS-Message-Information-Page n |
9.3.19 |
O/O |
|
CBS-Message-Information-Length n |
9.3.20 |
O/O |
|
Paging-ETWS-Indicator |
9.3.23 |
O/O (note 1) |
|
Warning-Type |
9.3.24 |
O/C (note 3) |
|
Warning-Security-Information |
9.3.25 |
O/C (note 3) |
|
GSM only [Warning Period |
9.3.26 |
C] (note 3) |
|
UMTS only [Broadcast Message Content Validity Indicator |
9.3.48 |
O] (note 4) |
|
NOTE 1: Only one of these two optional parameters may be simultaneously present in the primitive. The Channel Indicator parameter is included if the primitive contains a CBS message. The Paging-ETWS-Indicator parameter is included if the primitive contains an ETWS emergency message. |
||
|
NOTE 2: In GSM this parameter is included if the Channel Indicator parameter is present in the primitive. |
||
|
NOTE 3: In GSM this parameter is included if the Paging-ETWS-Indicator parameter is present in the primitive. NOTE 4: In UMTS this parameter is included if the Broadcast Message Content IE present in the primitive does not contain any valid information. |
||
This primitive is sent by the CBC to the BSC/RNC. As this primitive can be used either to broadcast a new CBS message or replace a CBS message already broadcast, the CBC will use the presence and content of the Old‑Serial‑Number and New-Serial-Number fields in this primitive to instruct the BSC/RNC as follows:
a) Old-Serial-Number not present/New-Serial-Number present:
– This is a write request which will be interpreted by the BSC/RNC as an instruction to broadcast a new CBS message in all the cells of the Cell list.
– GSM only [The CBS message will be broadcasted on the channel derived by the Channel Indicator (see the clause on parameters that describes the implicit value of the Channel Indicator when not present in the CBS message)].
The following table identifies the BSC/RNC’s behaviour:
|
Success/Failure of write request |
BSC/RNC behaviour |
|
Success |
The BSC/RNC completes the following parameters to be returned in the Report PDU: – a ‘0’ value is entered in the number of broadcasts completed list for the cell – no entry is made in the failure list for the cell |
|
Failure |
The BSC/RNC completes the following parameters to be returned in the Report PDU: – no entry is made in the number of broadcasts completed list for the cell – an entry is made in the failure list for the new CBS message identifying the failure cause for the cell |
– The BSC/RNC will build as many message references as the number of cells in the list. These message references will be used in particular in the subsequent primitives.
– When a message reference is already known by the BSC/RNC for certain cells in the list (even if the Update field of the Serial-Number is different), the primitive will be rejected for those cells with the cause "message reference already used". The list of cells where the message reference is not valid will be provided in the failure list of the REPORT primitive. For these cells no entry will be made in the number of broadcasts completed parameter.
b) Old-Serial-Number present/New-Serial-Number present.
– This is a replace request which will be interpreted by the BSC/RNC as a kill request for the CBS message with the old serial number, followed by a write request for the CBS message with the new serial number. The handling of the new serial number in the write part of this request, is as described above in the write request where no Old-Serial-Number is supplied. These two kill and write requests are executed sequentially. If the kill request is unsuccessful, the BSC/RNC does not proceed to execute the write request. The kill request will stop broadcast of, and cause all information currently associated with the combination of message identifier, old serial number, GSM only [Channel Indicator] and the list of cells in the Cell list to be deleted from the cells in the BSC/RNC (i.e. for all cells provided in the Cell-List parameter). If the kill request is successful, the subsequent write request information conveyed in the primitive replaces the killed CBS message. The following table identifies the BSC/RNC’s behaviour:
|
Success/Failure of kill request |
BSC/RNC behaviour |
|
Success |
The BSC/RNC proceeds to execute the write request: – Write successful: the BSC/RNC completes the following parameters to be returned in the Report PDU: – An entry is made in the number of broadcasts completed list for the cell. – No entry is made in the failure list for the cell. – Write unsuccessful: the BSC/RNC completes the following parameters to be returned in the Report PDU: – An entry is made in the number of broadcasts completed list for the cell. – An entry is made in the failure list for the new CBS message identifying the failure cause for the cell. |
|
Failure |
The BSC/RNC does not proceed to execute the write request, and completes the following parameters to be returned in the Report PDU: – no entry is made in the number of completed broadcasts list. – an entry is made for the old CBS message in the failure list identifying the failure cause for the cell. |
All cells which should perform the broadcasting are mentioned in the Cell-List parameter.
The broadcast of the referenced CBS message in the cells which are not mentioned in the Cell-List remains unaffected.
If no category is present, the default category is interpreted by the BSC/RNC, see the parameter clause.
This primitive is responded by a REPORT or REJECT primitive.
NOTE: GSM only [In the case of multipage CBS messages, the individual pages are considered as independent by the BSC scheduling algorithm].
9.2.3 KILL Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message-Identifier |
9.3.1 |
M |
|
Old-Serial-Number |
9.3.2 |
M |
|
Cell-List |
9.3.5.1 |
M |
|
GSM only [Channel Indicator |
9.3.6 |
O] |
This primitive is sent by the CBC to the BSC/RNC. The CBC will use this primitive to kill the message indicated by the combination of message identifier, serial number, GSM only [Channel Indicator] and the cells indicated in the Cell-List of this KILL request, i.e. the primitive will halt broadcast of the message in the indicated cells and remove any knowledge of the message from the BSC/RNC for these cells. The broadcast of the referenced message in the cells which are not mentioned in the Cell-List remains unaffected. This primitive is responded with a REPORT or REJECT primitive.
9.2.4 REPORT Response/Confirm
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message-Identifier |
9.3.1 |
M |
|
Serial-Number |
9.3.2/9.3.3 |
M |
|
GSM only [Channel Indicator |
9.3.6 |
O] |
|
No-of-Broadcasts-Completed-List |
9.3.10 |
O |
|
Failure-List |
9.3.14 |
O |
This primitive will be sent by the BSC/RNC to the CBC in response to WRITE-REPLACE and KILL primitives. The Serial-Number field will contain the old serial number if this primitive is sent in response to a KILL primitive, and the new serial number if the primitive is sent in response to a WRITE-REPLACE primitive.
The No-of-Broadcasts-Completed-List, if present, may contain for each cell the number of broadcasts of the (replaced or killed) CB message with the old message reference sent to this particular cell for broadcast. The serial number information element in the case of a WRITE-REPLACE does not refer to the message for which the number of broadcasts completed information is supplied. The Failure-List, if present, may contain those cells which were present in the related WRITE-REPLACE or KILL primitive and failed the requested operation.
9.2.5 STATUS-LOAD-QUERY Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Cell-List |
9.3.5.1 |
M |
|
GSM only [Channel Indicator] |
9.3.6 |
O |
This primitive is sent by the CBC to the BSC/RNC in order to obtain the current loading of the CBCH/UTRAN Radio Resource of particular cells referenced in the Cell-List parameter. This primitive is responded by a STATUS‑LOAD‑QUERY Response/Confirm or a REJECT primitive.
9.2.6 STATUS-LOAD-QUERY Response/Confirm
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Radio-Resource-Loading-List |
9.3.15 |
O |
|
Failure-List |
9.3.14 |
O |
|
GSM only [Channel Indicator] |
9.3.6 |
O |
This primitive will be sent by the BSC/RNC in response to the STATUS-LOAD-QUERY Request/Indication primitive.
The Radio-Resource-Loading-List, if present, may contain each cell which successfully performed the requested operation and for each of these cells the CBCH loading/ UTRAN Radio Resource loading of this particular cell.
NOTE: For cells with DRX the load caused by the schedule messages will be included in the load calculation.
The Radio-ResourceLoading-List will not be present if all cells indicated in the related STATUS-LOAD-QUERY Request/Indication failed the requested operation.
The Failure-List, if present, may contain all cells for which the requested operation failed (e.g. because the cells CBCH is not available in a BTS). The STATUS-LOAD-QUERY Response/Confirm will not contain the Failure-List parameter if none of the cells in the Cell-List of the related STATUS-LOAD-QUERY Request failed the requested operation.
9.2.7 STATUS-MESSAGE-QUERY Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message-Identifier |
9.3.1 |
M |
|
Old-Serial-Number |
9.3.2 |
M |
|
Cell-List |
9.3.5.1 |
M |
|
GSM only [Channel Indicator] |
9.3.6 |
O |
This primitive is sent by the CBC to the BSC/RNC in order to obtain the current status of a CB-message for the cells referenced in the Cell-List parameter. This primitive is responded by the STATUS-MESSAGE-QUERY Response/Confirm or by a REJECT Response/Confirm.
9.2.8 STATUS-MESSAGE-QUERY Response/Confirm
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message-Identifier |
9.3.1 |
M |
|
Old-Serial-Number |
9.3.2 |
M |
|
No-of-Broadcasts-Completed-List |
9.3.10 |
O |
|
Failure-List |
9.3.14 |
O |
|
GSM only [Channel Indicator] |
9.3.6 |
O |
This primitive will be sent by the BSC/RNC to the CBC in response to a STATUS-MESSAGE-QUERY Request/Indication primitive.
The No-of-Broadcasts-Completed-List, if present, may contain each cell which successfully performed the requested operation and for each of these cells the number of times this CB message has been sent to this particular cell for broadcast (parameter Number-of-Broadcasts-Completed; this parameter is not included for the cell if the old message reference is not known to the BSC/RNC, and an entry is made in the failure list). The No-of-Broadcasts-Completed-List will not be present if all cells indicated in the related STATUS-MESSAGE-QUERY Request failed the requested operation.
The Failure-List may contain all cells for which the requested operation failed (e.g. because the broadcast of the requested message was never requested before or because the cells CBCH is not available). The STATUS‑MESSAGE‑QUERY Response/Confirm will not contain the Failure-List parameter if none of the cells in the Cell-List of the related STATUS-MESSAGE-QUERY Request failed the requested operation.
9.2.9 REJECT Response/Confirm
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Cause |
9.3.16 |
M |
|
Diagnostic |
9.3.17 |
O |
|
Message-Identifier |
9.3.1 |
O |
|
Serial Number |
9.3.2 |
O |
This primitive is sent by the BSC/RNC to the CBC in response to any primitive which is not understood (e.g. invalid parameter or parameter value).
9.2.10 RESTART-INDICATION Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Cell-List |
9.3.5.2 |
M |
|
Recovery Indication |
9.3.21 |
O |
|
GSM only [Broadcast Message Type] |
9.3.27 |
O |
The RESTART-INDICATION Request is used by the BSC/RNC to indicate to the CBC a CB related restart situation in one or more of its cells (e.g. when an existing or a new cell becomes operational during normal BSC/RNC operation or when the BSC/RNC initialises).
Any referenced cell are again in CB-operational state (have resumed CB operation). The parameter Recovery Indication, if present, indicates whether CB related data are lost for the cells referenced in the Cell-List and have to be re-loaded. If the Recovery Indication parameter is absent, the CBC shall interpret it as the Recovery Indication with the value data lost.
The CBC upon receiving a RESTART INDICATION indication, marks the cell as operational again. It will usually generate WRITE-REPLACE requests for this cell, according to the actual CB message loading at the moment of the restart.
NOTE: A RESTART-INDICATION can be triggered from the CBC by a RESET Request. This allows recovery from situations, where a PDU occasionally may be lost.
9.2.11 RESET Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Cell-List |
9.3.5.1 |
M |
The RESET Request is used by the CBC to force one or more cells of one BSC/RNC into CB-idle state.
The RESET Request may also be used by the CBC to request the CB operational state of cells earlier indicated to have failed (polling CB operational state).
If a BSC/RNC receives a RESET Request, the indicated cells enter idle state (same state as after "power on"). All CB related information concerning earlier CB messages in a referenced cell is lost.
The BSC/RNC acknowledges the RESET Request for each cell by a RESET-COMPLETE response or, if not adequate, by a RESET-FAILUREresponse.
Several responses may be combined using a cell list in the RESET-COMPLETE or RESET-FAILURE response.
9.2.12 FAILURE-INDICATION Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Cell-List |
9.3.5.2 |
M |
|
GSM only [Broadcast Message Type] |
9.3.27 |
O |
The FAILURE-INDICATION Request is used by the BSC/RNC to indicate to the CBC a CB related problem situation in one or more of its cells.
Any referenced cell enters CB-not-operational state. The status of the CBS messages is undefined until the Restart‑Indication is sent. It remains in not-operational state until a RESTART-INDICATION request (see clause 9.1.10) indicates normal CB operation (again).
The CBC upon receiving a FAILURE-INDICATION, marks this cell as failed. It will generally not generate further WRITE‑REPLACE requests for this cell, up to the point when the CBC is informed by a RESTART indication, that the cell has resumed CB operation.
The BSC/RNC refuses further WRITE-REPLACE requests from the CBC with the cause "cell‑broadcast‑not‑operational" when any referenced cell is in the CB-not-operational state.
NOTE: A FAILURE-INDICATION can be triggered by a RESET Request. This allows recovery from situations, where a PDU occasionally may be lost.
9.2.13 SET-DRX Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Cell-List |
9.3.5.1 |
M |
|
Schedule-Period |
9.3.12 |
O |
|
Reserved-Slots |
9.3.13 |
O |
|
GSM only [Channel Indicator] |
9.3.6 |
O |
This primitive is applicable in GSM only. In UMTS DRX is a mandatory feature in the RNC and no activation/ deactivation function on CBS related radio resources controlled by the CBC is necessary.
The SET-DRX Request is used by the CBC to set DRX specific parameters i.e. the schedule period and the number of slots reserved for high priority CBS messages, see 3GPP TS 44.012 [7]. At least one of the Schedule-Period or Reserved-Slots parameters must be present in the primitive. If this primitive is not supported, the BSC may use default values.
If a BSC receives a SET-DRX Indication, the new DRX parameters will be taken into account starting from the next schedule period in each cell, see 3GPP TS 44.012 [7].
If a BSC receives a SET-DRX Indication, the new DRX parameters will be applied for all cells that do not handle any broadcast message (null loading).
9.2.14 SET-DRX- REPORT Response/Confirm
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Cell-List |
9.3.5.2 |
O |
|
Failure-List |
9.3.14 |
O |
|
GSM only [Channel Indicator] |
9.3.6 |
O |
This primitive will be sent by the BSC to the CBC in response to a SET-DRX Request/Indication primitive.
The Failure-List will contain those cells which were present in the Request message and which failed the requested operation.
If the new schedule period parameters are not acceptable on a cell due to the load of the cell, the cause "bss‑capacity‑exceeded" is used in the Failure-list.
9.2.15 Void
9.2.16 WRITE-REPLACE-WARNING-REQUEST Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Message Identifier |
9.3.1 |
M |
|
Serial-Number |
9.3.3 |
M |
|
Repetition-Period E-UTRAN |
9.3.36 |
M |
|
No-of-Broadcasts-Requested |
9.3.9 |
M |
|
List of TAIs |
9.3.29 |
O |
|
Warning Area List |
9.3.30 |
O |
|
Extended Repetition-Period |
9.3.37 |
O |
|
Warning-Type |
9.3.24 |
O |
|
Warning-Security-Information |
9.3.25 |
O |
|
Data Coding Scheme |
9.3.18 |
O (NOTE 1) |
|
Warning Message Content E-UTRAN |
9.3.35 |
O |
|
OMC ID |
9.3.31 |
O |
|
Concurrent Warning Message Indicator |
9.3.32 |
O |
|
Send Write-Replace-Warning-Indication |
9.3.39 |
O |
|
Global eNB ID |
9.3.46 |
O |
|
List of NG-RAN TAIs |
9.3.54 |
O |
|
Warning Area List NG-RAN |
9.3.55 |
O |
|
Warning Message Content NG-RAN |
9.3.51 |
O |
|
Global RAN Node ID |
9.3.53 |
O |
|
RAT Selector NG-RAN |
9.3.56 |
O |
|
Warning Area Coordinates |
9.3.63 |
O |
|
Test Flag |
9.3.64 |
O (NOTE 2) |
|
NOTE1: The Data Coding Scheme IE is not required for ETWS primary notification but it is mandatory for ETWS secondary notification and CMAS warning messages when Warning Message Content E-UTRAN IE is present. NOTE 2: This IE may only be included if the CBC sends the request to a PWS-IWF. |
||
This primitive is sent by the CBC to the MME or to the PWS-IWF.
The WRITE-REPLACE-WARNING-REQUEST Request/Indication primitive is to request the MME and the AMF to start or overwrite a warning message broadcast. The response to this Request/Indication primitive is sent by the MME or the AMF in a corresponding WRITE-REPLACE-WARNING-CONFIRM primitive.
If the message is sent to the MME, then the List of TAIs IE, the Warning Area List IE, the Warning Message Content E‑UTRAN IE and the Global eNB ID IE may be used and the List of NG-RAN TAIs IE, the Warning Area List NG-RAN IE, the Warning Message Content NG-RAN IE, the Global RAN Node ID IE and the RAT Selector NG-RAN IE shall not be used.
If the message is sent to the PWS-IWF, then the List of NG-RAN TAIs IE, the Warning Area List NG-RAN IE, the Warning Message Content NG-RAN IE, the Global RAN Node ID IE and the RAT Selector NG-RAN IE may be used and the List of TAIs IE, the Warning Area List IE, the Repetition-Period E-UTRAN IE, the Extended Repetition Period IE, the Warning Message Content E-UTRAN IE, and the Global eNB ID IE shall not be used. The WRITE-REPLACE-WARNING-REQUEST Request/Indication primitive shall then be forwarded to the AMF.
NOTE: For ETWS Primary Notification, the Repetition Period IE and the Number of Broadcasts Requested IE are ignored by eNB if included in WRITE-REPLACE-WARNING-REQUEST message (see 3GPP TS 36.413 [34]).
9.2.17 WRITE-REPLACE-WARNING-CONFIRM Response/Confirm
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Message Identifier |
9.3.1 |
M |
|
Serial-Number |
9.3.3 |
M |
|
Cause E-UTRAN |
9.3.33 |
M |
|
Criticality Diagnostics |
9.3.34 |
O |
|
Unknown Tracking Area List |
9.3.38 |
O |
|
Cause NG-RAN |
9.3.50 |
O |
|
Unknown NG-RAN Tracking Area List |
9.3.57 |
O |
This primitive is sent by the MME or by the PWS-IWF to the CBC. The PWS-IWF receives this message from the AMF.
The WRITE-REPLACE-WARNING-CONFIRM Response/Confirm primitive is to acknowledge the start or overwrite of a WRITE-REPLACE-WARNING-REQUEST for a warning message.
If the message is received from an MME then the Cause E-UTRAN IE and the Unknown Tracking Area IE may be present. If the message is received from an AMF via a PWS-IWF then the Cause NG-RAN IE and the Unknown NG-RAN Tracking Area List may be present.
9.2.18 STOP-WARNING-REQUEST Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Message Identifier |
9.3.1 |
M |
|
Serial-Number |
9.3.3 |
M |
|
List of TAIs |
9.3.29 |
O |
|
Warning Area List |
9.3.30 |
O |
|
OMC ID |
9.3.31 |
O |
|
Send Stop Warning Indication |
9.3.41 |
O |
|
Stop-All Indicator |
9.3.43 |
O |
|
List of NG-RAN TAIs |
9.3.54 |
O |
|
Warning Area List NG-RAN |
9.3.55 |
O |
|
RAT Selector NG-RAN |
9.3.56 |
O |
This primitive is sent by the CBC to the MME or to the PWS-IWF.
The STOP-WARNING-REQUEST Request/Indication primitive is sent to request to stop a warning message broadcast. The response to this Request/Indication primitiveis sent by the MME or the AMF in a corresponding STOP-WARNING-CONFIRM primitive.
If the message is sent to an MME, then the List of TAIs IE and the Warning Area List IE may be used and the List of NG-RAN TAIs IE, the Warning Area List NG-RAN IE and the RAT Selector NG-RAN IE shall not be used.
If the message is sent to the PWS-IWF, then the List of NG-RAN TAIs IE, the Warning Area List NG-RAN IE and the RAT Selector NG-RAN IE may be used and the List of TAIs IE and the Warning Area List IE shall not be used. The STOP-WARNING-REQUEST Request/Indication primitive shall then be forwarded to the AMF.
9.2.19 STOP-WARNING-CONFIRM Response/Confirm
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Message Identifier |
9.3.1 |
M |
|
Serial-Number |
9.3.3 |
M |
|
Cause E-UTRAN |
9.3.33 |
M |
|
Criticality Diagnostics |
9.3.34 |
O |
|
Unknown Tracking Area List |
9.3.38 |
O |
|
Cause NG-RAN |
9.3.50 |
O |
|
Unknown NG-RAN Tracking Area List |
9.3.57 |
O |
This primitive is sent by the MME or by the PWS-IWF to the CBC. The PWS-IWF receives this message from the AMF.
The STOP-WARNING-CONFIRM Response/Confirm primitive is to acknowledge the receipt of the STOP-WARNING-REQUEST primitive for a warning message.
If the message is received from an MME then the Cause E-UTRAN IE and the Unknown Tracking Area IE may be present. If the message is received from an AMF via the PWS-IWF then the Cause NG-RAN IE and the Unknown NG-RAN Tracking Area List may be present.
9.2.20 WRITE-REPLACE-WARNING-INDICATION Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Message Identifier |
9.3.1 |
M |
|
Serial-Number |
9.3.3 |
M |
|
Broadcast Scheduled Area List |
9.3.40 |
O |
|
Broadcast Scheduled Area List NG-RAN |
9.3.58 |
O |
|
Broadcast Empty Area List |
9.3.44 |
O |
|
Broadcast Empty Area List NG-RAN |
9.3.60 |
O |
This Indication is sent by the MME to report to the CBC the Broadcast Scheduled Area List(s) the MME has received from the eNodeB(s) as Broadcast Completed Area List. If the MME has received a WRITE REPLACE WARNING RESPONSE without a Broadcast Completed Area List, then the eNodeB ID shall be included in the Broadcast Empty Area List instead. Multiple responses from eNodeBs may be combined in a Broadcast Scheduled Area List.
This Indication is sent by an AMF via the PWS-IWF to report to the CBC the Broadcast Scheduled Area List(s) NG-RAN the AMF has received from the NG-RAN node(s) as Broadcast Completed Area List. If the AMF has received a WRITE-REPLACE WARNING RESPONSE without a Broadcast Completed Area List, then the gNodeB ID shall be included in the Broadcast Empty Area List NG-RAN instead. Multiple responses from NG-RAN nodes may be combined by the AMF in a Broadcast Scheduled Area List NG-RAN.
If the MME or the PWS-IWF interfaces with multiple CBCs (i.e. has active SCTP associations established with multiple CBCs), the MME or PWS-IWF shall forward the same WRITE-REPLACE-WARNING-INDICATION message to all CBCs.
The Broadcast Scheduled Area List IE or Broadcast Scheduled Area List NG-RAN IE is not included in the WRITE-REPLACE WARNING INDICATION when the broadcast is unsuccessful in all the cells within the eNodeBs or NG-RAN nodes.
If the message is received from an MME then the Broadcast Scheduled Area List IE may be present. If the message is received from an AMF via the PWS-IWF then the Broadscast Scheduled Area List NG-RAN IE may be present.
The Broadcast Empty Area List IE may be included in the WRITE-REPLACE-WARNING-INDICATION when the MME has received at least one WRITE REPLACE WARNING RESPONSE without Broadcast Completed Area List IE.
The Broadcast Empty Area List NG-RAN IE may be included in the WRITE-REPLACE-WARNING-INDICATION when the AMF has received at least one WRITE REPLACE WARNING RESPONSE without Broadcast Completed Area List IE.
9.2.21 STOP-WARNING-INDICATION Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Message Identifier |
9.3.1 |
M |
|
Serial-Number |
9.3.3 |
M |
|
Broadcast Cancelled Area List |
9.3.42 |
O |
|
Broadcast Empty Area List |
9.3.44 |
O |
|
Broadcast Cancelled Area List NG-RAN |
9.3.59 |
O |
|
Broadcast Empty Area List NG-RAN |
9.3.60 |
O |
This primitive is sent by the MME to the CBC.
The STOP-WARNING-INDICATION Request/Indication primitive is to report to the CBC the Broadcast Cancelled Area List the MME has received from the eNodeB in a KILL RESPONSE. If the MME has received a KILL RESPONSE without a Broadcast Cancelled Area List IE, then the eNodeB ID shall be included in the Broadcast Empty Area List instead. The MME may aggregate Broadcast Cancelled Area Lists it receives from eNodeBs.
If the MME interfaces with multiple CBCs (i.e. has active SCTP associations established with multiple CBCs), the MME shall forward the same STOP-WARNING-INDICATION primitive to all CBCs.
This primitive is sent by an AMF via the PWS-IWF to the CBC.
The STOP-WARNING-INDICATION Request/Indication primitive is to report to the CBC the Broadcast Cancelled Area List the AMF has received from the NG-RAN nodes in a PWS CANCEL RESPONSE. If the AMF has received a PWS CANCEL RESPONSE without a Broadcast Cancelled Area List IE, then the NG-RAN node ID shall be included in the Broadcast Empty Area List NG-RAN instead. The AMF may aggregate Broadcast Cancelled Area Lists it receives from NG-RAN nodes and send them to the CBC via the PWS-IWF.
If the message is received from an MME then the Broadcast Cancelled Area List IE may be present. If the message is received from an AMF via the PWS-IWF then the Broadcast Cancelled Area List NG-RAN IE may be present.
The Broadcast Cancelled Area List IE or Broadcast Cancelled Area List NG-RAN IE is included in the STOP-WARNING-INDICATION when stopping the broadcast was successful in at least one of the cells within the eNodeBs or NG-RAN nodes.
The Broadcast Empty Area List IE shall be included in the STOP-WARNING-INDICATION when the MME has received at least one KILL RESPONSE without Broadcast Cancelled Area List IE.
The Broadcast Empty Area List NG-RAN IE shall be included in the STOP-WARNING-INDICATION when the AMF has received at least one PWS CANCEL RESPONSE without Broadcast Cancelled Area List IE.
9.2.22 RESTART-INDICATION-E-UTRAN Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Restarted Cell List |
9.3.45 |
M |
|
Global eNB ID |
9.3.46 |
M |
|
List of TAIs |
9.3.29 |
M |
|
Emergency Area ID List |
9.3.47 |
O |
|
Restarted Cell List NG-RAN |
9.3.61 |
O |
|
Global RAN Node ID |
9.3.53 |
O |
|
List of NG-RAN TAIs |
9.3.54 |
O |
The RESTART-INDICATION-E-UTRAN message is sent by the MME to the CBC upon receipt of a PWS Restart Indication from an eNodeB, to indicate that the PWS service is restarted in one or more or all cells served by an eNodeB, i.e. the service has become operational and no warning message data is available for these cell(s). Upon receipt of that message, the CBC shall reload the cells if required. See clause 15A.1 of 3GPP TS 23.007 [38].
If the MME interfaces with multiple CBCs (i.e. has active SCTP associations established with multiple CBCs), the MME shall forward the same RESTART-INDICATION-E-UTRAN message to all CBCs.
The RESTART-INDICATION-E-UTRAN primitive is sent by a PWS-IWF to the CBC, triggered by the AMF sending a RESTART-INDICATION-NG-RAN message to the PWS-IWF upon receipt of a PWS Restart Indication from a NG-RAN node. The RESTART-INDICATION-E-UTRAN message indicates to the CBC that the PWS service is restarted in one or more or all cells served by a NG-RAN node, i.e. the service has become operational and no warning message data is available for these cell(s). Upon receipt of that message, the CBC shall reload the cells if required.
If the indication is received from the PWS-IWF then the Restarted Cell List NG‑RAN IE, the Global RAN Node ID IE and List of NG-RAN TAIs IE shall be present and the Restarted Cell List IE, the Global eNB ID IE and List of TAIs IE are populated with a dummy value (all zeros).
The List of TAIs or List of NG-RAN TAIs, and the Emergency Area ID List shall contain the Tracking Area IDs and Emergency Area IDs (if any) that are configured for the restarted cells listed in the Restarted Cell List, or in the Restarted Cell List NG-RAN.
Upon receiving a RESTART-INDICATION-E-UTRAN shortly after a preceding one, if:
a) the same Restarted Cell List NG-RAN is included in both messages; or
b) the same Restarted Cell List is included in both messages and the Restarted Cell List NG-RAN is absent in both messages;
the CBC shall consider the RESTART-INDICATION-E-UTRAN as a duplicate message and shall ignore it.
NOTE: The CBC can receive the same PWS Restart Indication message via two MMEs of the MME pool for redundancy reasons (see clause 15A.1 of 3GPP TS 23.007 [38]).
9.2.23 FAILURE-INDICATION-E-UTRAN Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Failed Cell List |
9.3.49 |
M |
|
Global eNB ID |
9.3.46 |
M |
|
Failed Cell List NG-RAN |
9.3.62 |
O |
|
Global RAN Node ID |
9.3.53 |
O |
The FAILURE-INDICATION-E-UTRAN message is sent by the MME to the CBC upon receipt of a PWS Failure Indication from an eNodeB, to indicate that ongoing PWS operation in one or more or all cells served by that eNodeB has failed.
If the MME interfaces with multiple CBCs (i.e. has active SCTP associations established with multiple CBCs), the MME shall forward the same FAILURE-INDICATION-E-UTRAN message to all CBCs.
The FAILURE-INDICATION-E-UTRAN message is sent by a PWS-IWF to the CBC, triggered by the AMF sending a FAILURE-INDICATION-NG-RAN message to the PWS-IWF upon receipt of a PWS Failure Indication from a NG-RAN node. The FAILURE-INDICATION-E-UTRAN message indicates to the CBC that ongoing PWS operation in one or more or all cells served by that NG-RAN node has failed.
If the indication is received from a PWS-IWF then the Failed Cell List NG-RAN IE and the Global RAN Node ID IE shall be present and the Failed Cell List IE and the Global eNB ID IE are populated with a dummy value (all zeros).
9.2.24 RESET-COMPLETE Response/Confirm
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Cell List |
9.3.5.2 |
M |
This primitive will be sent by the BSC/RNC to the CBC in response to a RESET Request primitive if the RESET Request was successful in all the cells, which are indicated in the Cell List.
If the RESET Request was not successful in all the cells then the BSC/RNC shall respond with a RESET-FAILURE Response.
9.2.25 RESET-FAILURE Response/Confirm
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Failed Cell List |
9.3.5.2 |
M |
|
Cell List |
9.3.5.2 |
O |
This primitive will be sent by the BSC/RNC to the CBC in response to a RESET Request/Indication primitive if the RESET Request was not successful in all the cells.
The cells where the RESET Request failed are indicated in the Failed Cell List and the Cell List contains the list of cells where the RESET was successful, if any.
9.2.26 WRITE-REPLACE-WARNING-REQUEST-NG-RAN Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Message Identifier |
9.3.1 |
M |
|
Serial-Number |
9.3.3 |
M |
|
Repetition-Period NG-RAN |
9.3.52 |
M |
|
No-of-Broadcasts-Requested |
9.3.9 |
M |
|
RAT Selector NG-RAN |
9.3.56 |
M |
|
List of NG-RAN TAIs |
9.3.54 |
O |
|
Warning Area List NG-RAN |
9.3.55 |
O |
|
Warning-Type |
9.3.24 |
O |
|
Warning-Security-Information |
9.3.25 |
O |
|
Data Coding Scheme |
9.3.18 |
O (NOTE) |
|
Warning Message Content NG-RAN |
9.3.51 |
O |
|
OMC ID |
9.3.31 |
O |
|
Concurrent Warning Message Indicator |
9.3.32 |
O |
|
Send Write-Replace-Warning-Indication |
9.3.39 |
O |
|
Global RAN Node ID |
9.3.53 |
O |
|
Warning Area Coordinates |
9.3.63 |
O |
|
Test Flag |
9.3.64 |
O |
|
NOTE: The Data Coding Scheme IE is not required for ETWS primary notification but it is mandatory for ETWS secondary notification and CMAS warning messages when Warning Message Content NG-RAN IE is present. |
||
This primitive is sent by the CBCF to the AMF to request start or overwrite of a warning message broadcast and is responded to by the AMF in a WRITE-REPLACE-WARNING-CONFIRM-NG-RAN response.
NOTE: For ETWS Primary Notification, the Repetition Period IE and the Number of Broadcasts Requested IE are ignored by NG-RAN node if included in WRITE-REPLACE-WARNING-REQUEST-NG-RAN.
9.2.27 WRITE-REPLACE-WARNING-CONFIRM-NG-RAN Response/Confirm
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Message Identifier |
9.3.1 |
M |
|
Serial-Number |
9.3.3 |
M |
|
Cause NG-RAN |
9.3.50 |
M |
|
Criticality Diagnostics |
9.3.34 |
O |
|
Unknown NG-RAN Tracking Area List |
9.3.57 |
O |
This primitive is sent by the AMF to the CBCF to acknowledge the CBCF on the start or overwrite of a WRITE-REPLACE-WARNING-REQUEST-NG-RAN for a warning message.
9.2.28 STOP-WARNING-REQUEST-NG-RAN Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Message Identifier |
9.3.1 |
M |
|
Serial-Number |
9.3.3 |
M |
|
RAT Selector NG-RAN |
9.3.56 |
M |
|
List of NG-RAN TAIs |
9.3.54 |
O |
|
Warning Area List NG-RAN |
9.3.55 |
O |
|
OMC ID |
9.3.31 |
O |
|
Send Stop Warning Indication |
9.3.41 |
O |
|
Stop-All Indicator |
9.3.43 |
O |
This primitive is sent by the CBCF to the AMF to request to stop a warning message broadcast and is responded to by the AMF in a STOP-WARNING-CONFIRM-NG-RAN response.
9.2.29 STOP-WARNING-CONFIRM-NG-RAN Response/Confirm
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Message Identifier |
9.3.1 |
M |
|
Serial-Number |
9.3.3 |
M |
|
Cause NG-RAN |
9.3.50 |
M |
|
Criticality Diagnostics |
9.3.34 |
O |
|
Unknown NG-RAN Tracking Area List |
9.3.57 |
O |
This primitive is sent by the AMF to the CBCF to acknowledge the CBCF on receipt of the STOP-WARNING-REQUEST-NG-RAN for a warning message.
9.2.30 WRITE-REPLACE-WARNING-INDICATION-NG-RAN Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Message Identifier |
9.3.1 |
M |
|
Serial-Number |
9.3.3 |
M |
|
Broadcast Scheduled Area List NG-RAN |
9.3.58 |
O |
|
Broadcast Empty Area List NG-RAN |
9.3.60 |
O |
This Indication is sent by the AMF to report to the CBCF the Broadcast Scheduled Area List(s) the AMF has received from the NG-RAN node(s) as Broadcast Completed Area List. If the AMF has received a WRITE-REPLACE WARNING RESPONSE without a Broadcast Completed Area List, then the gNodeB ID shall be included in the Broadcast Empty Area List NG-RAN instead. Multiple responses from NG-RAN nodes may be combined in a Broadcast Scheduled Area List.
If the AMF interfaces with multiple CBCFs, the AMF shall forward the same WRITE-REPLACE-WARNING-INDICATION-NG-RAN message to all CBCFs.
The Broadcast Scheduled Area List IE is not included in the WRITE-REPLACE WARNING INDICATION-NG‑RAN when the broadcast is unsuccessful in all the cells within the NG-RAN nodes.
The Broadcast Empty Area List NG-RAN IE may be included in the WRITE-REPLACE-WARNING-INDICATION when the AMF has received at least one WRITE REPLACE WARNING RESPONSE without Broadcast Completed Area List IE.
9.2.31 STOP-WARNING-INDICATION-NG-RAN Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Message Identifier |
9.3.1 |
M |
|
Serial-Number |
9.3.3 |
M |
|
Broadcast Cancelled Area List NG-RAN |
9.3.59 |
O |
|
Broadcast Empty Area List NG-RAN |
9.3.60 |
O |
This message is sent by the AMF to report to the CBCF the Broadcast Cancelled Area List the AMF has received from the NG-RAN node in a CANCEL RESPONSE. If the AMF has received a CANCEL RESPONSE without a Broadcast Cancelled Area List IE, then the NG-RAN node ID shall be included in the Broadcast Empty Area List instead. The AMF may aggregate Broadcast Cancelled Area Lists it receives from NG-RAN nodes.
If the AMF interfaces with multiple CBCFs, the AMF shall forward the same STOP-WARNING-INDICATION-NG‑RAN message to all CBCFs.
The Broadcast Cancelled Area List IE is included in the STOP-WARNING-INDICATION-NG-RAN when cancelling the broadcast was successful in at least one of the cells within the NG-RAN nodes.
The Broadcast Empty Area List IE shall be included in the STOP-WARNING-INDICATION-NG-RAN when the AMF has received at least one CANCEL RESPONSE without Broadcast Cancelled Area List IE.
9.2.32 RESTART-INDICATION-NG-RAN Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Restarted Cell List NG-RAN |
9.3.61 |
M |
|
Global RAN Node ID |
9.3.53 |
M |
|
List of NG-RAN TAIs |
9.3.54 |
M |
|
Emergency Area ID List |
9.3.47 |
O |
The RESTART-INDICATION-NG-RAN message is sent by the AMF to the CBCF upon receipt of a PWS Restart Indication from a NG-RAN node, to indicate that the PWS service is restarted in one or more or all cells served by an NG-RAN node, i.e. the service has become operational and no warning message data is available for these cell(s). Upon receipt of that message, the CBCF shall reload the cells if required. See 3GPP TS 23.527 [45].
If the AMF interfaces with multiple CBCFs, the AMF shall forward the same RESTART-INDICATION-NG-RAN message to all CBCFs.
The List of TAIs and the Emergency Area ID List shall contain the Tracking Area IDs and Emergency Area IDs (if any) that are configured for the restarted cells listed in the Restarted Cell List.
Upon receiving a RESTART-INDICATION-NG-RAN shortly after a preceding one, if the same Restarted Cell List NG-RAN is included in both messages, the CBCF shall consider the RESTART-INDICATION-NG-RAN as a duplicate message and shall ignore it.
NOTE: The CBCF can receive the same PWS Restart Indication message via two AMFs of the AMF region for redundancy reasons (see 3GPP TS 23.527 [45]).
9.2.33 FAILURE-INDICATION-NG-RAN Request/Indication
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Message Type |
9.3.28 |
M |
|
Failed Cell List NG-RAN |
9.3.62 |
M |
|
Global RAN Node ID |
9.3.53 |
M |
The FAILURE-INDICATION-NG-RAN message is sent by the AMF to the CBCF upon receipt of a PWS Failure Indication from a NG-RAN node, to indicate that ongoing PWS operation in one, more or all cells served by that NG-RAN node has failed.
If the AMF interfaces with multiple CBCFs, the AMF shall forward the same FAILURE-INDICATION-NG-RAN message to all CBCFs.