ETSI TS 129 168 V11.5.0 (2016-01)

Universal Mobile Telecommunications System (UMTS); LTE; Cell Broadcast Centre interfaces with the Evolved Packet Core; Stage 3 (3GPP TS 29.168 version 11.5.0 Release 11)

RTS/TSGC-0429168vb50

General Information

• Status: Published
• Publication Date: 25-Jan-2016
• Technical Committee: 3GPP CT 4 - MAP/CAMEL/GTP/BCH/SS/TrFO/IMS/GUP/WLAN (formely CN4)
• Current Stage: 12 - Completion
• Due Date: 20-Jan-2016
• Completion Date: 26-Jan-2016

Standards Content (Sample)

ETSI TS 1129 168 V11.5.0 (201616-01)

TECHNICAL SPECIFICATIONION
Universal Mobile Telelecommunications System ( (UMTS);
LTE;
Cell Broadcasast Centre interfaces with thehe
Evvoolved Packet Core;
Stage 3
(3GPP TS 29.1.168 version 11.5.0 Release 11 11)

3GPP TS 29.168 version 11.5.0 Release 11 1 ETSI TS 129 168 V11.5.0 (2016-01)

Reference
RTS/TSGC-0429168vb50
Keywords
LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2016.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3GPP TS 29.168 version 11.5.0 Release 11 2 ETSI TS 129 168 V11.5.0 (2016-01)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 29.168 version 11.5.0 Release 11 3 ETSI TS 129 168 V11.5.0 (2016-01)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 SBc description . 8
4.1 Transport . 8
4.1.1 General . 8
4.1.2 Network layer . 8
4.1.3 Transport layer . 8
4.1.4 Services expected from signalling transport . 8
4.2. SBc-AP functions . 8
4.2.1 Function of SBc-AP . 8
4.3 SBc-AP procedure . 9
4.3.1 General . 9
4.3.2 List of SBc-AP elementary procedure. 9
4.3.3 Write Replace Warning Procedure . 9
4.3.3.1 General . 9
4.3.3.2 Successful Operation . 9
4.3.3.3 Unsuccessful Operation . 10
4.3.3A Stop Warning Procedure . 10
4.3.3A.1 General . 10
4.3.3A.2 Successful Operation . 10
4.3.3A.3 Unsuccessful Operation . 11
4.3.3B Error Indication . 11
4.3.3B.1 General . 11
4.3.3B.2 Successful Operation . 11
4.3.3B.3 Abnormal Conditions . 12
4.3.4 Message functional definition and content . 12
4.3.4.1 Message contents . 12
4.3.4.1.1 Presence . 12
4.3.4.1.2 Criticality . 12
4.3.4.1.3 Range . 12
4.3.4.1.4 Assigned Criticality . 12
4.3.4.2 Warning Message Transmission Messages . 12
4.3.4.2.1 WRITE-REPLACE WARNING REQUEST . 12
4.3.4.2.2 WRITE-REPLACE WARNING RESPONSE . 13
4.3.4.2.3 STOP WARNING REQUEST . 13
4.3.4.2.4 STOP WARNING RESPONSE . 14
4.3.4.2A Management Messages . 14
4.3.4.2A.1 ERROR INDICATION . 14
4.3.4.3 Information element definition. 14
4.3.4.3.1 Message Type . 14
4.3.4.3.2 Cause . 15
4.3.4.3.3 Criticality Diagnostics . 15
4.3.4.3.4 OMC ID . 16
4.4 Message and information element abstract syntax . 16
4.4.1 General . 16
ETSI
3GPP TS 29.168 version 11.5.0 Release 11 4 ETSI TS 129 168 V11.5.0 (2016-01)
4.4.2 Usage of protocol extension mechanism for non-standard use . 17
4.4.3 Elementary procedure definitions . 17
4.4.4 PDU definitions . 19
4.4.5 Information element definitions . 22
4.4.6 Common definitions . 25
4.4.7 Constant definitions . 25
4.4.8 Container Definitions . 26
4.4.9 Message sransfer syntax . 29
4.5 Handling of unknown, unforeseen or erroneous protocol data . 29
4.5.1 General . 29
4.5.2 Transfer Syntax Error . 29
4.5.3 Abstract Syntax Error . 29
4.5.3.1 General . 29
4.5.3.2 Criticality information . 30
4.5.3.3 Presence information . 30
4.5.3.4 Not comprehended IE/IE group . 31
4.5.3.4.1 Procedure code . 31
4.5.3.4.2 Type of Message . 31
4.5.3.4.3 IEs other than the Procedure Code and Type of Message . 31
4.5.3.5 Missing IE or IE group . 32
4.5.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present . 33
4.5.4 Logical Error . 34
4.5.5 Exceptions . 34
Annex A (informative): Change history: . 35
History . 36

ETSI
3GPP TS 29.168 version 11.5.0 Release 11 5 ETSI TS 129 168 V11.5.0 (2016-01)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.

ETSI
3GPP TS 29.168 version 11.5.0 Release 11 6 ETSI TS 129 168 V11.5.0 (2016-01)
1 Scope
The present document specifies the procedures and the SBc Application Part (SBc-AP) messages used on the SBc-AP
interface between the Mobility Management Entity (MME) and the Cell Broadcast Centre (CBC).
The present document supports the following functions.
• Warning Message Transmission function in the EPS.
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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] IETF RFC 2460 (December 1998): "Internet Protocol, Version 6 (IPv6) Specification".
[3] IETF RFC 791 (September 1981): "Internet Protocol".
[4] IETF RFC 4960 (September 2007): "Stream Control Transmission Protocol".
[5] Void
[6] Void
[7] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1
Application Protocol (S1AP)"
[8] ITU-T Recommendation X.680 (07/2002): "Information Technology - Abstract Syntax Notation
One (ASN.1): Specification of basic notation".
[9] ITU-T Recommendation X.681 (07/2002): "Information Technology - Abstract Syntax Notation
One (ASN.1): Information object specification".
[10] ITU-T Recommendation X.691 (07/2002): "Information Technology - ASN.1 encoding rules -
Specification of Packed Encoding Rules (PER)".
[11] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[12] Void
[13] 3GPP TS 22.268: "Public Warning System (PWS) requirements".
[14] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
[15] Void
ETSI
3GPP TS 29.168 version 11.5.0 Release 11 7 ETSI TS 129 168 V11.5.0 (2016-01)
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following
apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP
TR 21.905 [1].
Elementary Procedure: SBc-AP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of
interaction between MME and CBC. These Elementary Procedures 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 SBc-APs together with
each other and EPs from other interfaces can be found in reference [FFS].
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 and/or failure).
- Class 2: Elementary Procedures without response.
For Class 1 EPs, the types of responses can be as follows:
Successful:
- A signalling message explicitly indicates that the elementary procedure successfully completed with the
receipt of the response.
Unsuccessful:
- A signalling message explicitly indicates that the EP failed.
- On time supervision expiry (i.e. absence of expected response).
Successful and Unsuccessful:
- One signalling message reports both successful and unsuccessful outcome for the different included requests.
The response message used is the one defined for successful outcome.
Class 2 EPs are considered always successful.
3.2 Symbols
For the purposes of the present document, the following symbols apply:

Editor"s note: To be completed or section removed.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
CMAS Commercial Mobile Alert System
CBC Cell Broadcast Center
CBS Cell Broadcast Service
EPC Evolved Packet Core
EPS Evolved Packet System
ETWS Earthquake and Tsunami Warning System
MME Mobility Management Entity
ETSI
3GPP TS 29.168 version 11.5.0 Release 11 8 ETSI TS 129 168 V11.5.0 (2016-01)
PWS Public Warning System
SCTP Stream Control Transmission Protocol

4 SBc description
4.1  Transport
4.1.1 General
This subclause specifies the standards for signalling transport to be used across SBc-AP interface. SBc-AP interface is a
logical interface between the MME and the CBC. All the SBc-AP messages described in the present document require
an SCTP association between the MME and the CBC.
4.1.2 Network layer
The MME and the CBC shall support IPv6 (see IETF RFC 2460 [2]) and/or IPv4 (see IETF RFC 791 [3]).
The IP layer of SBc-AP only supports point-to-point transmission for delivering SBc-AP messages.
4.1.3 Transport layer
SCTP (see IETF RFC 4960 [4]) shall be supported as the transport layer of SBc-AP messages.
Semi-permanent SCTP associations shall be established between MME and CBC, i.e. the SCTP associations shall
remain up under normal circumstances.
Local multi-homing should be supported. Remote multi-homing shall be supported.
Multiple local SCTP endpoints may be supported. Multiple remote SCTP endpoints shall be supported. When multiple
local or remote SCTP endpoints are configured, several simultaneous SCTP associations shall be supported between
MME and CBC.
Checksum calculation for SCTP shall be supported as specified in RFC 4960 [4].
The CBC shall establish the SCTP association.
The registered port number for SBc-AP is 29168.
The registered payload protocol identifier for SBc-AP is 24.
4.1.4 Services expected from signalling transport
The signalling connection shall provide in-sequence delivery of SBc-AP messages. SBc-AP shall be notified if the
signalling connection breaks.
4.2. SBc-AP functions
4.2.1 Function of SBc-AP
SBc-AP has the following function:
- Warning Message Transmission function:
This functionality provides the means to start, overwrite and stop the broadcasting of warning message in support
of the Public Warning System (PWS) messages as defined in 3GPP TS 22.268 [13] which include Commercial
Mobile Warning System (CMAS) and Earthquake and Tsunami (ETWS) messages.
ETSI
3GPP TS 29.168 version 11.5.0 Release 11 9 ETSI TS 129 168 V11.5.0 (2016-01)
4.3 SBc-AP procedure
4.3.1 General
This sub-clause describes the parameters and detailed behaviors of different procedures.
4.3.2 List of SBc-AP elementary procedure
Table 4.3.2-1 lists the SBc-AP Elementary Procedures defined as a class 1 procedures.
Table 4.3.2-1: SBc-AP class 1 elementary procedures
Elementary Initiating Message Successful Outcome Unsuccessful Outcome
Procedure
Response message Response message
Write-Replace WRITE-REPLACE WRITE-REPLACE
Warning WARNING REQUEST WARNING RESPONSE
procedure
Stop Warning STOP WARNING STOP WARNING
Procedure REQUEST RESPONSE
Table 4.3.2-2 lists the SBc-AP Elementary Procedures defined as a class 2 procedures.
Table 4.3.2-2: SBc-AP class 2 elementary procedures
Elementary Initiating Message
Procedure
Error Indication ERROR INDICATION
procedure
4.3.3 Write Replace Warning Procedure
4.3.3.1 General
The purpose of Write-Replace Warning procedure is to start, overwrite the broadcasting of warning message, as defined
in 3GPP TS 23.041 [14].
4.3.3.2 Successful Operation
MME
CBC
WRITE-REPLACE WARNING REQUEST
WRITE-REPLACE WARNING RESPONSE

Figure 4.3.3.2-1: Write-Replace Warning procedure. Successful operation.
The CBC initiates the procedure by sending a WRITE-REPLACE WARNING REQUEST message to the MME.
Upon reception of WRITE-REPLACE WARNING REQUEST message, the MME shall forward the message towards
the eNBs belonged to the tracking area as indicated in List of TAIs IE.
If none of List of TAIs IE is present in WRITE-REPLACE WARNING REQUEST message, the MME shall forward the
message towards all connected eNBs.
ETSI
3GPP TS 29.168 version 11.5.0 Release 11 10 ETSI TS 129 168 V11.5.0 (2016-01)
The MME shall return a WRITE-REPLACE WARNING RESPONSE to the CBC immediately after the reception of
the WRITE-REPLACE WARNING REQUEST message without waiting responses from eNBs.
The MME shall set the cause IE to "Message accepted" in the WRITE-REPLACE WARNING RESPONSE message.
4.3.3.3 Unsuccessful Operation

MME
CBC
WRITE-REPLACE WARNING REQUEST
WRITE-REPLACE WARNING RESPONSE

Figure 4.3.3.3-1: Write-Replace Warning procedure. Unsuccessful operation.
The CBC initiates the procedure by sending a WRITE-REPLACE WARNING REQUEST message to the MME.
If MME cannot process the received WRITE-REPLACE WARNING REQUEST message, the MME shall return a
WRITE-REPLACE WARNING RESPONSE message towards the CBC and the MME shall not forward the message
towards the eNBs belonged to the tracking area as indicated in List of TAIs IE.
The MME shall indicate a reason of failure in the cause IE.
4.3.3A  Stop Warning Procedure
4.3.3A.1 General
The purpose of Stop Warning Procedure is to stop the broadcasting of warning message.
4.3.3A.2 Successful Operation
MME
CBC
STOP WARNING REQUEST
STOP WARNING RESPONSE
Figure 4.3.3A.2-1: Stop Warning Procedure, Successful Operation.
The CBC initiates the Stop Warning Procedure by sending a STOP WARNING REQUEST message to the MME.
Upon reception of STOP WARNING REQUEST message, the MME shall forward the message towards the eNBs
belonged to the tracking area as indicated in List of TAIs IE.
If none of List of TAIs IE is present in STOP WARNING REQUEST message, the MME shall forward the message
towards all connected eNBs.
The MME shall return a STOP WARNING RESPONSE to the CBC immediately after the reception of the STOP
WARNING REQUEST message without waiting responses from eNBs.
The MME shall set the cause IE to "Message accepted" in the STOP WARNING RESPONSE message.
ETSI
3GPP TS 29.168 version 11.5.0 Release 11 11 ETSI TS 129 168 V11.5.0 (2016-01)
4.3.3A.3 Unsuccessful Operation

MME
CBC
STOP WARNING REQUEST
STOP WARNING RESPONSE
Figure 4.3.3A.3-1: Stop Warning procedure, Unsuccessful operation.
The CBC initiates the Stop Warning Procedure by sending a STOP WARNING REQUEST message to the MME.
If MME cannot process the received STOP WARNING REQUEST message, the MME shall return a STOP
WARNING RESPONSE message towards the CBC and the MME shall not forward the message towards the eNBs
belonged to the tracking area as indicated in List of TAIs IE.
The MME shall indicate a reason of failure in the cause IE.
4.3.3B Error Indication
4.3.3B.1 General
The Error Indication procedure is initiated by a node to report detected errors in one incoming message, provided they
cannot be reported by an appropriate failure message.
4.3.3B.2 Successful Operation
MME CBC
ERROR INDICATION
Figure 4.3.3B.2-1: Error Indication procedure, CBC originated. Successful operation.

MME CBC
ERROR INDICATION
Figure 4.3.3B.2-2: Error Indication procedure, MME originated. Successful operation.
When the conditions defined in subclause 4.5 are fulfilled, the Error Indication procedure is initiated by an ERROR
INDICATION message sent from the receiving node.
The ERROR INDICATION message shall contain at least either the Cause IE or the Criticality Diagnostics as indicated
in subclause 4.5.
ETSI
3GPP TS 29.168 version 11.5.0 Release 11 12 ETSI TS 129 168 V11.5.0 (2016-01)
4.3.3B.3 Abnormal Conditions
Not applicable.
4.3.4 Message functional definition and content
4.3.4.1 Message contents
4.3.4.1.1 Presence
All information elements in the message descriptions below are marked mandatory, optional or conditional according to
table 4.3.4.1.1-1.
Table 4.3.4.1.1-1: Meaning of abbreviations used in SBc-AP messages
Abbreviation Meaning
M IEs marked as Mandatory (M) shall always be included in the
message.
O IEs marked as Optional (O) may or may not be included in the
message.
C
IEs marked as Conditional (C) shall be included in a message only if
the condition is satisfied. Otherwise the IE shall not be included.

4.3.4.1.2 Criticality
Each Information Element or Group of Information Elements may have criticality information applied to it.
Following cases are possible:
Table 4.3.4.1.2-1: Meaning of content within "Criticality" column
Abbreviation Meaning
– No criticality information is applied explicitly.
YES Criticality information is applied. This is usable only for non-
repeatable IEs
GLOBAL The IE and all its repetitions together have one common criticality
information. This is usable only for repeatable IEs.
EACH
Each repetition of the IE has its own criticality information. It is not
allowed to assign different criticality values to the repetitions. This is
usable only for repeatable IEs.

4.3.4.1.3 Range
The Range column indicates the allowed number of copies of repetitive IEs/IE groups.
4.3.4.1.4 Assigned Criticality
This column provides the actual criticality information as defined in subclause 4.5.3.2, if applicable.
4.3.4.2 Warning Message Transmission Messages
4.3.4.2.1 WRITE-REPLACE WARNING REQUEST
This message is sent by the CBC to request start or overwrite of a warning message broadcast.
Direction: CBC → MME
ETSI
3GPP TS 29.168 version 11.5.0 Release 11 13 ETSI TS 129 168 V11.5.0 (2016-01)
Table 4.3.4.2.1-1: WRITE-REPLACE WARNING REQUEST message contents
IE/Group Name Presence Range IE type and Semantics Criticality Assigned
reference description Criticality
Message Type M 4.3.4.3.1 YES reject
Message Identifier M [7] YES reject
Serial Number M [7] YES reject
List of TAIs O  YES reject
>TAI List Item 1 to

>>TAI M [7]
Warning Area List O [7] YES ignore
Repetition Period M [7] YES reject
Extended Repetition O [7] YES reject
Period
Number of Broadcast M [7] YES reject
Requested
Warning Type O [7] YES ignore
Warning Security O [7] YES ignore
Information
Data Coding Scheme O [7] YES ignore
Warning Message O [7] YES ignore
Contents
OMC ID O 4.3.4.3.4 YES ignore
Concurrent Warning O [7] YES reject
Message Indicator
Table 4.3.4.2.1-2: RANGE explanation
Range bound Explanation
maxnoofTAI Maximum no. of TAI subject for warning message broadcast. Value
is 65535.
4.3.4.2.2 WRITE-REPLACE WARNING RESPONSE
This message is sent by the MME to acknowledge the CBC on the start or overwrite request of a warning message.
Direction: MME → CBC
Table 4.3.4.2.2-1: WRITE-REPLACE WARNING RESPONSE message contents
IE/Group Name Presence Range IE type and Semantics Criticality Assigned
reference description Criticality
Message Type M 4.3.4.3.1 YES reject
Message Identifier M [7] YES reject
Serial Number M [7] YES reject
Cause M 4.3.4.3.2 YES ignore
Criticality Diagnostics O 4.3.4.3.3 YES ignore

4.3.4.2.3 STOP WARNING REQUEST
This message is sent by the CBC to stop a warning message broadcast.
Direction: CBC → MME
ETSI
3GPP TS 29.168 version 11.5.0 Release 11 14 ETSI TS 129 168 V11.5.0 (2016-01)
Table 4.3.4.2.3-1: STOP WARNING REQUEST message contents
IE/Group Name Presence Range IE type and Semantics Criticality Assigned
reference description Criticality
Message Type M 4.3.4.3.1 YES reject
Message Identifier M [7] YES reject
Serial Number M [7] YES reject
List of TAIs O  YES reject
>TAI List Item 1 to

>>TAI M [7]
Warning Area List O [7] YES Ignore
OMC ID O 4.3.4.3.4 YES ignore

Table 4.3.4.2.1-2: RANGE explanation
Range bound Explanation
maxnoofTAI Maximum no. of TAI subject for warning message broadcast. Value
is 65535.
4.3.4.2.4 STOP WARNING RESPONSE
This message is sent by the MME to acknowledge the CBC on the stop request of a warning message.
Direction: MME → CBC
Table 4.3.4.2.2-1: STOP WARNING RESPONSE message contents
IE/Group Name Presence Range IE type and Semantics Criticality Assigned
reference description Criticality
Message Type M 4.3.4.3.1 YES reject
Message Identifier M [7] YES reject
Serial Number M [7] YES reject
Cause M 4.3.4.3.2 YES ignore
Criticality Diagnostics O 4.3.4.3.3 YES ignore

4.3.4.2A Management Messages
4.3.4.2A.1 ERROR INDICATION
This message is sent by both the MME and the CBC and is used to indicate that some error has been detected in the
node.
Direction : MME → CBC and CBC → MME
Table 4.3.4.2A.1-1: ERROR INDICATION message contents
Presence Range IE type and Semantics Criticality Assigned
IE/Group Name reference description Criticality
Message Type M 4.3.4.3.1 YES ignore
Cause O 4.3.4.3.2 YES ignore
Criticality Diagnostics O 4.3.4.3.3 YES ignore

4.3.4.3  Information element definition
4.3.4.3.1 Message Type
The Message Type IE uniquely identifies the message being sent. It is mandatory for all messages
ETSI
3GPP TS 29.168 version 11.5.0 Release 11 15 ETSI TS 129 168 V11.5.0 (2016-01)
Table 4.3.4.3.1-1: Message Type information element
IE/Group Name Presence Range IE type and reference Semantics description
Message Type
Assumed max no of messages
is 256.
>Procedure Code M (Write-Replace
Warning, Stop Warning
…)
>Type of Message M CHOICE
(Initiating Message,
Successful Outcome,
Unsuccessful Outcome,
…)
4.3.4.3.2 Cause
The purpose of the Cause IE is to indicate the reason for a particular event for the SBc-AP protocol.
Table 4.3.4.3.2-1: Cause information element
IE/Group Name Presence Range IE Type and Reference Semantics
Description
Cause M INTEGER (Message accepted,
Parameter not recognised, Parameter
value invalid, Valid message not
identified, Tracking area not valid,
Unrecognised message, Missing
mandatory element, MME capacity
exceeded, MME memory exceeded,
Warning broadcast not supported,
Warning broadcast not operational,
Message reference already used,
Unspecified error, Transfer syntax
error, Semantic error, Message not
compatible with receiver state,
Abstract syntax error reject, Abstract
syntax error ignore and notify,
Abstract syntax error falsely
constructed message, …)
4.3.4.3.3 Criticality Diagnostics
The Criticality Diagnostics IE is sent by the MME when parts of a received message have not been comprehended or
were missing, or if the message contained logical errors. When applicable, it contains information about which IEs were
not comprehended or were missing.
ETSI
3GPP TS 29.168 version 11.5.0 Release 11 16 ETSI TS 129 168 V11.5.0 (2016-01)
Table 4.3.4.3.3-1: Criticality Diagnostics information element
IE/Group Name Presence Range IE type and Semantics description
reference
Procedure Code O INTEGER Procedure Code is to be used if
(0.255) Criticality Diagnostics is part of
Error Indication procedure, and
not within the response
message of the same procedure
that caused the error
Triggering Message O ENUMERATED(
The Triggering Message is used
initiating
only if the Criticality Diagnostics
message,
is part of Error Indication
successful
procedure.
outcome,
unsuccessful
outcome,
outcome)
Procedure Criticality O ENUMERATED(
This Procedure Criticality is
reject, ignore,
used for reporting the Criticality
notify)
of the Triggering message
(Procedure).
Information Element 0 to
Criticality Diagnostics errors>
>IE Criticality M ENUMERATED(
The IE Criticality is used for
reject, ignore,
reporting the criticality of the
notify)
triggering IE. The value 'ignore'
shall not be used.
>IE ID M INTEGER
The IE ID of the not understood
(0.65535)
or missing IE
>Type of Error M ENUMERATED(
not understood,
missing, …)
Table 4.3.4.3.3-2: RANGE explanation
Range bound Explanation
maxnooferrors Maximum no. of IE errors allowed to be reported with a single
message. The value for maxnooferrors is 256.

4.3.4.3.4 OMC ID
The OMC ID IE indicates the identity of an Operation and Maintenance Centre to which Trace records shall be sent.
Table 4.3.4.3.4-1: OMC ID information element
IE/Group Name Presence Range IE Type and Reference Semantics
Description
OMC ID O OCTET STRING (SIZE (1.20))
Octets are coded according to 3GPP
TS 29.002 [11].
4.4  Message and information element abstract syntax
4.4.1 General
SBC-AP ASN.1 definition conforms with [8] and [9].
ETSI
3GPP TS 29.168 version 11.5.0 Release 11 17 ETSI TS 129 168 V11.5.0 (2016-01)
The ASN.1 definition specifies the structure and content of SBC-AP messages. SBC-AP messages can contain any IEs
specified in the object set definitions for that message without the order or number of occurrence being restricted by
ASN.1. However, for this version of the standard, a sending entity shall construct a SBC-AP message according to the
PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object
set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have
different IE ids):
- IEs shall be ordered (in an IE container) in the order they appear in object set definitions.
- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence
field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has
value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list)
then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an
IE container list where the list elements reside. The second part defines list elements. The IE container list
appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list
elements.
If a SBC-AP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax
Error, and the message shall be handled as defined for Abstract Syntax error in subclause 4.5.3.6.
4.4.2 Usage of protocol extension mechanism for non-standard use
The protocol extension mechanism for non-standard use may be used:
- for special operator- (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the
functionality required for a complete and high-quality specification in order to guarantee multivendor
interoperability.
- by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features
are proposed for standardisation.
The extension mechanism shall not be used for basic functionality. Such functionality shall be standardised.
4.4.3 Elementary procedure definitions
-- **************************************************************
--
-- Elementary Procedure definitions
--
-- **************************************************************

SBC-AP-PDU-Descriptions {
itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
eps-Access (21) modules (3) sbc-AP (3) version1 (1) sbc-AP-PDU-Descriptions (0)}

DEFINITIONS AUTOMATIC TAGS ::=

BEGIN
-- **************************************************************
--
-- IE parameter types from other modules.
--
-- **************************************************************

IMPORTS
Criticality,
ProcedureCode
FROM SBC-AP-CommonDataTypes
Write-Replace-Warning-Request,
Write-Replace-Warning-Response,
Stop-Warning-Request,
Stop-Warning-Response,
Error-Indication
FROM SBC-AP-PDU-Contents
id-Write-Replace-Warning,
ETSI
3GPP TS 29.168 version 11.5.0 Release 11 18 ETSI TS 129 168 V11.5.0 (2016-01)
id-Stop-Warning,
id-Error-Indication
FROM SBC-AP-Constants;
-- **************************************************************
--
-- Interface Elementary Procedure Class
--
-- **************************************************************

SBC-AP-ELEMENTARY-PROCEDURE ::= CLASS {
&InitiatingMessage  ,
&SuccessfulOutcome  OPTIONAL,
&UnsuccessfulOutcome  OPTIONAL,
&procedureCode  ProcedureCode UNIQUE,
&criticality  Criticality DEFAULT ignore
}
WITH SYNTAX {
INITIATING MESSAGE &InitiatingMessage
[SUCCESSFUL OUTCOME &SuccessfulOutcome]
[UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome]
PROCEDURE CODE  &procedureCode
[CRITICALITY  &criticality]
}
-- **************************************************************
--
-- Interface PDU Definition
--
-- **************************************************************

SBC-AP-PDU ::= CHOICE {
initiatingMessage InitiatingMessage,
successfulOutcome SuccessfulOutcome,
unsuccessfulOutcome UnsuccessfulOutcome,
...
}
InitiatingMessage ::= SEQUENCE {
procedureCode SBC-AP-ELEMENTARY-PROCEDURE.&procedureCode ({SBC-AP-ELEMENTARY-PROCEDURES}),
criticality SBC-AP-ELEMENTARY-PROCEDURE.&criticality ({SBC-AP-ELEMENTARY-
PROCEDURES}{@procedureCode}),
value SBC-AP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({SBC-AP-ELEMENTARY-
PROCEDURES}{@procedureCode})
}
SuccessfulOutcome ::= SEQUENCE {
procedureCode SBC-AP-ELEMENTARY-PROCEDURE.&procedureCode ({SBC-AP-ELEMENTARY-PROCEDURES}),
criticality SBC-AP-ELEMENTARY-PROCEDURE.&criticality ({SBC-AP-ELEMENTARY-
PROCEDURES}{@procedureCode}),
value SBC-AP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({SBC-AP-ELEMENTARY-
PROCEDURES}{@procedureCode})
}
UnsuccessfulOutcome ::= SEQUENCE {
procedureCode SBC-AP-ELEMENTARY-PROCEDURE.&procedureCode ({SBC-AP-ELEMENTARY-PROCEDURES}),
criticality SBC-AP-ELEMENTARY-PROCEDURE.&criticality ({SBC-AP-ELEMENTARY-
PROCEDURES}{@procedureCode}),
value SBC-AP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({SBC-AP-ELEMENTARY-
PROCEDURES}{@procedureCode})
}
-- ************************
...