Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 23.041  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   2   3…   4…   6…   9…   9.1.3.3   9.1.3.4   9.1.3.5   9.1.4…   9.2…   9.2.10…   9.2.21…   9.3…   9.3.20…   9.3.40…   9.4…   9.4.2…   9.5   9A…   10…   B…

 

9.2  Requirements on the CBC-RAN, CBC-MME and CBCF-AMF interfacesWord‑p. 37

9.2.0  General |R15|

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.
The following table gives an overview over the existing primitives:
Name Originator Type Reference
WRITE-REPLACECBCRequest/Indication 9.2.2
KILLCBCRequest/Indication 9.2.3
REPORTBSC/RNCResponse/Confirm 9.2.4
STATUS-LOAD-QUERYCBCRequest/Indication 9.2.5
STATUS-LOAD-QUERYBSC/RNCResponse/Confirm 9.2.6
STATUS-MESSAGE-QUERYCBCRequest/Indication 9.2.7
STATUS-MESSAGE-QUERYBSC/RNCResponse/Confirm 9.2.8
REJECTBSC/RNCResponse/Confirm 9.2.9
RESTART-INDICATIONBSC/RNCRequest/Indication 9.2.10
RESETCBCRequest/Indication 9.2.11
FAILURE-INDICATIONBSC/RNCRequest/Indication 9.2.12
SET-DRXCBCRequest/Indication 9.2.13
SET-DRX-REPORTBSCResponse/Confirm 9.2.14
WRITE-REPLACE-WARNING-REQUESTCBCRequest/Indication 9.2.16
WRITE-REPLACE-WARNING-CONFIRMMMEResponse/Confirm 9.2.17
STOP-WARNING-REQUESTCBCRequest/Indication 9.2.18
STOP-WARNING-CONFIRMMMEResponse/Confirm 9.2.19
WRITE-REPLACE-WARNING-INDICATIONMMERequest/Indication 9.2.20
STOP-WARNING-INDICATIONMMERequest/Indication 9.2.21
RESTART-INDICATION-E-UTRANMMERequest/Indication 9.2.22
FAILURE-INDICATION-E-UTRANMMERequest/Indication 9.2.23
RESET-COMPLETEBSC/RNCResponse/Confirm 9.2.24
RESET-FAILUREBSC/RNCResponse/Confirm 9.2.25
WRITE-REPLACE-WARNING-REQUEST-NG-RANCBCF/PWS-IWFRequest/Indication 9.2.26
WRITE-REPLACE-WARNING-CONFIRM-NG-RANAMFResponse/Confirm 9.2.27
STOP-WARNING-REQUEST-NG-RANCBCF/PWS-IWFRequest/Indication 9.2.28
STOP-WARNING-CONFIRM-NG-RANAMFResponse/Confirm 9.2.29
WRITE-REPLACE-WARNING-INDICATION-NG-RANAMFRequest/Indication 9.2.30
STOP-WARNING-INDICATION-NG-RANAMFRequest/Indication 9.2.31
RESTART-INDICATION-NG-RANAMFRequest/Indication 9.2.32
FAILURE-INDICATION-NG-RANAMFRequest/Indication 9.2.33
 
In GSM the CBC is integrated into the Core Network. The protocol between the CBC and BSC is defined in TS 48.049.
In UMTS the CBC is integrated into the Core Network. The protocol between the CBC and RNC is defined in TS 25.419.
In E-UTRAN the CBC is integrated into the Core Network. The protocol between the CBC and MME is defined in TS 29.168.
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 TS 29.518.
Up

9.2.1  Identification of a CBS messageWord‑p. 38
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".
Up

9.2.2  WRITE-REPLACE Request/IndicationWord‑p. 39
Parameter Reference Presence
(UMTS/GSM)
Message-Identifier 9.3.1M/M
Old-Serial-Number 9.3.2O/O
New-Serial-Number 9.3.3M/M
Cell-List 9.3.5.1M/M
GSM only [Channel Indicator] 9.3.6O (1)
Category 9.3.7O/C (2)
Repetition-Period 9.3.8M/C (2)
No-of-Broadcasts-Requested 9.3.9M/C (2)
Number-of-Pages 9.3.4M/C (2)
Data Coding Scheme 9.3.18M/C (2)
CBS-Message-Information-Page 1 9.3.19M/C (2)
CBS-Message-Information-Length 1 9.3.20M/C(2)
CBS-Message-Information-Page 2 9.3.19O/O
CBS-Message-Information-Length 2 9.3.20O/O
.
.
.
.
.
.
CBS-Message-Information-Page n 9.3.19O/O
CBS-Message-Information-Length n 9.3.20O/O
Paging-ETWS-Indicator 9.3.23O/O (1)
Warning-Type 9.3.24O/C (3)
Warning-Security-Information 9.3.25O/C (3)
GSM only [Warning Period] 9.3.26C (3)
UMTS only [Broadcast Message Content Validity Indicator] 9.3.48O (4)
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.
Up

9.2.3  KILL Request/IndicationWord‑p. 41
Parameter Reference Presence
Message-Identifier 9.3.1M
Old-Serial-Number 9.3.2M
Cell-List 9.3.5.1M
GSM only [Channel Indicator] 9.3.6O
 
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.
Up

9.2.4  REPORT Response/Confirm

Parameter Reference Presence
Message-Identifier 9.3.1M
Serial-Number 9.3.2
9.3.3
M
GSM only [Channel Indicator] 9.3.6O
No-of-Broadcasts-Completed-List 9.3.10O
Failure-List 9.3.14O
 
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.
Up

9.2.5  STATUS-LOAD-QUERY Request/IndicationWord‑p. 42
Parameter Reference Presence
Cell-List 9.3.5.1M
GSM only [Channel Indicator] 9.3.6O
 
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.
Up

9.2.6  STATUS-LOAD-QUERY Response/Confirm

Parameter Reference Presence
Radio-Resource-Loading-List 9.3.15O
Failure-List 9.3.14O
GSM only [Channel Indicator] 9.3.6O
 
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.
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.
Up

9.2.7  STATUS-MESSAGE-QUERY Request/Indication

Parameter Reference Presence
Message-Identifier 9.3.1M
Old-Serial-Number 9.3.2M
Cell-List 9.3.5.1M
GSM only [Channel Indicator] 9.3.6O
 
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.
Up

9.2.8  STATUS-MESSAGE-QUERY Response/ConfirmWord‑p. 43
Parameter Reference Presence
Message-Identifier 9.3.1M
Old-Serial-Number 9.3.2M
No-of-Broadcasts-Completed-List 9.3.10O
Failure-List 9.3.14O
GSM only [Channel Indicator] 9.3.6O
 
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.
Up

9.2.9  REJECT Response/Confirm

Parameter Reference Presence
Cause 9.3.16M
Diagnostic 9.3.17O
Message-Identifier 9.3.1O
Serial Number 9.3.2O
 
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).
Up


Up   Top   ToC