Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 29.168  Word version:  18.0.0

Top   Top   None   None   Next
1…   4… 
1 Scope  2 References  3 Definitions and abbreviations  3.1 Definitions  3.2 Abbreviations 
...

 

1  Scope  p. 6

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), and between the Public Warning System - Inter Working Function (PWS-IWF) and the CBC.
The present document supports the following functions:
  • Warning Message Transmission function in the EPS,
  • Warning Message Transmission function in the 5GS via the PWS-IWF (see TS 23.041).
Up

2  References  p. 6

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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
RFC 8200  ( July 2017): "Internet Protocol, Version 6 (IPv6) Specification".
[3]
RFC 791  (September 1981): "Internet Protocol".
[4]
RFC 4960  (September 2007): "Stream Control Transmission Protocol".
[5]  Void
[6]  Void
[7]
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]
TS 29.002: "Mobile Application Part (MAP) specification".
[12]  Void
[13]
TS 22.268: "Public Warning System (PWS) requirements".
[14]
TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
[15]  Void
[16]
TS 23.007: "Restoration procedures".
[17]
TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[18]
TS 23.527: "5G System; Restoration procedures".
Up

3  Definitions and abbreviations  p. 7

3.1  Definitions  p. 7

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
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.
Up

3.2  Abbreviations  p. 7

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
5GC
5G Core
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
PWS
Public Warning System
PWS-IWF
PWS - Inter Working Function
SCTP
Stream Control Transmission Protocol
Up

Up   Top   ToC