Tech-invite3GPPspaceIETF RFCsSIP

Content for  TS 25.419  Word version:  16.0.0

Top   Top   None   None   Next
1…   8…


1  ScopeWord‑p. 7

The present document specifies the Service Area Broadcast Protocol (SABP) between the Cell Broadcast Centre (CBC) and the Radio Network Controller (RNC). It fulfils the CBC - RNC communication requirements specified in TS 23.041 and is defined over the Iu-BC - reference point.

2  References

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]  Void
[2]  Void
[3]  Void
TR 25.931: "UTRAN Functions: Examples on Signalling Procedures".
TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
TS 25.414: "UTRAN Iu Interface Data Transport and Transport Signalling".
ITU-T Recommendation X.680 (2002-07): "Information Technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation".
ITU-T Recommendation X.681 (2002-07): "Information Technology - Abstract Syntax Notation One (ASN.1): Information object specification".
ITU-T Recommendation X.691 (2002-07): "Information Technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER)".
TR 25.921: (Version 7.0.0) "Guidelines and Principles for Protocol Description and Error Handling".
TS 25.324: "Broadcast/Multicast Control BMC".
TS 23.003: "Numbering, addressing and identification".

3  Definitions and abbreviations

3.1  Definitions

For the purposes of the present document, the following terms and definitions apply:
Elementary Procedure:
SABP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between the CN (CBC) and the RNC. These EPs are defined separately and are intended to be used to build up complete sequences in a flexible manner. If the independence between some EPs is restricted, it is described under the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked independently of each other as stand alone procedures, which can be active in parallel. Examples on using several SABP EPs together with each other and EPs from other interfaces can be found in reference TR 25.931.
An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used:
  • Class 1: Elementary Procedures with response (success or failure).
  • Class 2: Elementary Procedures without response.
For Class 1 EPs, the types of responses can be as follows:
  • A signalling message explicitly indicates that the elementary procedure successfully completed with the receipt of the response.
  • A signalling message explicitly indicates that the EP failed.
  • On time supervision expiry (i.e. absence of expected response).
Class 2 EPs are considered always successful.
Message Reference:
This is defined as consisting of the following parameters: Message Identifier, Serial Number, and SAI (Service Area Identifier).

3.2  AbbreviationsWord‑p. 8

For the purposes of the present document, the following abbreviations apply:
Cell Broadcast Centre
Cell Broadcast Service
Core Network
Elementary Procedure
Frame Protocol
Protocol Data Unit
Radio Network Controller
Service Area
Service Area Broadcast Protocol

4  General

The protocol described in the present document is the protocol between CN (CBC) and RNC needed for the CBC Application. The CBC Application is described in TS 23.041.

4.1  Procedure Specification Principles

The principle for specifying the procedure logic is to specify the functional behaviour of the RNC exactly and completely. The CN functional behaviour is left unspecified.
The following specification principles have been applied for the procedure text in clause 8:
  • The procedure text discriminates between:
    1. Functionality which "shall" be executed:
      • The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value.
    2. Functionality which "shall, if supported" be executed:
      • The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality.
  • Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included.

4.2  Forwards and Backwards CompatibilityWord‑p. 9

The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and IEs or groups of related IEs, include Id and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version.

4.3  Specification Notations

For the purposes of the present document, the following notations apply:
When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Write-Replace procedure.
When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. WRITE-REPLACE message.
When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. Old Serial Number IE.
Value of an IE
When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 9.2 enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)" or "Background ".

5  Services provided by SABP

  • During normal operation the CN (CBC) initiates all message transfer and query operations. The RNC responds to the message transfer and query operations initiated by the CBC.
  • The RNC will open the connection only in case an error (Failure Indication Procedure) or recovery (Restart Indication Procedure) is to be reported.
  • The initiator of a connection is responsible for the termination of the connection.

6  Services expected from the Transport layer

Following service is expected from the transport layer:
  • in sequence delivery of Signalling data TS 25.414.

7  Functions of SABPWord‑p. 10

The SABP has the following functions:
  • Message Handling. This function is responsible for the broadcast of new messages, amend existing broadcasted messages and to stop the broadcasting of specific messages.
  • Load Handling. This function is responsible for determining the loading of the broadcast channels at any particular point in time.
  • Reset. This function permits the CBC to end broadcasting in one or more Service Areas.
  • Error Handling. This function allows the reporting of general error situations, for which function specific error messages have not been defined.
These functions are implemented by one or several SABP elementary procedures described in the following clauses.

Up   Top   ToC