hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
4131cd5fefdadf4075e3ec0993ed8fe4
|
34.901
|
11 Accuracy of Continuous Distributions
|
As stated in clause 9.2, the negative binomial distributions can be approximated by m-Erlang distribution. In this Appendix, we will discuss about how good this approximation is.
For continuous distributions, Equation (1’) and (2’) determine early Pass/Fail thresholds, and these can be transformed to more specific forms shown below by presuming m-Erlang distribution.
There is no explicit way to know Rth from D , but is a continuous function, so Newton method can be employed to find Rth .
The Early Pass/Fail criteria obtained this way are compared with those from negative binomial distributions in Figure 11‑1 through Figure 11‑3.
For the first two cases (Figure 11‑1and Figure 11‑2), the two approaches show a good agreement. However, in Figure 11‑3, there is a significant difference between them. This difference results in a significant difference in the test time as shown in Figure 11‑4. The difference is largest for a marginal UEs (r ~ 0.124).
Figure 11‑1: Comparison of Early Pass/Fail Criteria for BER Measurement (R0 = 0.001, F = 0.002)
Figure 11‑2: Comparison of Early Pass/Fail Criteria for BLER Measurement (R0 = 0.01, F = 0.01)
Figure 11‑3: Comparison of Early Pass/Fail Criteria for RRM Delay Measurement (R0 = 0.1, F = 0.05)
Figure 11‑4: Comparison of Test Time (R0 = 0.1, F = 0.05)
Annex A:
Change history
T Meeting
Doc-1st-Level
CR
Rev
Subject
Cat
Version-Current
Version-New
Doc-2nd-Level
TP-20
Approval of the report
2.0.1
3.0.0
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
1 Scope
|
The present document provides an overview and overall description of the LTE-based 5G terrestrial broadcast comprising:
- a service delivering Free To Air content [2];
- a radio network comprising only MBMS-dedicated cells or FeMBMS/Unicast-mixed cells [3] as transmitters; and
- Receive Only Mode (ROM) devices and UEs supporting FeMBMS [4] as receivers.
Details of the radio interface protocols and procedures are specified in companion specifications of the 36 series.
This document is a 'living' document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
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] 3GPP TS 22.101: "Service aspects; Service principles".
[3] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN)".
[4] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description".
[5] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[6] 3GPP TS 36.331: "Radio Resource Control (RRC) Protocol".
[7] 3GPP TS 24.116: "Stage 3 aspects of system architecture enhancements for TV services".
[8] 3GPP TS 36.211: "E-UTRA; Physical Channels and Modulation".
[9] 3GPP TR 36.776: " Study on LTE-based 5G terrestrial broadcast".
[10] 3GPP TR 38.913: "Study on scenarios and requirements for next generation access technologies".
[11] 3GPP TR 36.440: " General aspects and principles for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN".
[12] 3GPP TS 24.117: "TV service configuration Management Object (MO)".
[13] 3GPP TS 36.213: "E-UTRA; Physical layer procedures".
[14] 3GPP TS 36.304: "E-UTRA; Procedures in idle mode".
[15] 3GPP TS 36.133: "E-UTRA; Requirements for support of radio resource management".
[16] 3GPP TS 36.321: "E-UTRA; MAC protocol specification".
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
3 Definitions, symbols and abbreviations
| |
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
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].
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
3.2 Symbols
|
For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
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].
DRX Discontinuous reception
eMBMS Evolved MBMS
FeMBMS Further enhanced MBMS
HPHT High power high tower
ISD Inter-site distance
LPLT Low power low tower
MPMT Medium power medium tower
NAS Non-access startumstratum
MBMS Multimedia Broadcast/Multicast System
MBSFN Multicast/Broadcast Single Frequency Network
MNO Mobile Network Operator
NR New RadioPBCH Physical Broadcast Channel
PDSCH Physical Downlink Shared Channel
PSS Primary synchronization signal
RAT Radio Access TechnologyROM Receive only mode
RRC Radio Resource Control
RRM Radio resource management
SC-PTM Single Cell Point To Multipoint
SSS Secondary synchronization signal
TV Television
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
4 Introduction
|
<Definition of LTE-based 5G broadcast: Dedicated network, ROM devices>
<Motivation>
<Use cases>
<Quick overview of the Rel.14 and Rel.16 work>
<Network scenarios: LPLT, MPMT, HPHT>
<Receiver types: rooftop, car-mounted,…>
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
4.1 General
|
The main aspects of the LTE-based 5G terrestrial broadcast described in this specification are:
- radio network comprising only MBMS-dedicated cells or FeMBMS/Unicast-mixed cells [3] as transmitters; and
- ROM devices and UEs supporting FeMBMS [4] as receivers.
NOTE: ROM devices support only ROM service [5]. ROM service uses one of the reserved TMGI values [7].
MBMS-dedicated cells support only MBMS transmission and do not support uplink transmission. MBSFN subframes of a MBMS-dedicated cell does not have control region and can therefore be 100% allocated to MBMS. Non-MBSFN subframes, also called Cell Acquisition Subframes (CAS), which have the control region, are used for transmission of the system acquisition signals (PSS/SSS), PDCCH, and system information on PBCH and PDSCH. CAS are transmitted with periodicity of 40ms and use subframes with f = 15 kHz. PBCH of a MBMS-dedicated cell uses a different scrambling sequence initialization than PBCH of a non-MBMS-dedicated cell, which prevents UEs not supporting MBMS-dedicated cell from camping on it. For more information about MBMS-dedicated cell see 3GPP TS 36.300 [3].
ROM devices support MBMS transmission but do not support uplink transmission. ROM devices may not have USIM. As such, ROM devices do not support two-way signalling procedures with the network, including connection establishment procedures and security procedures. ROM devices only support the idle mode. Not all idle mode procedures are supported, as described in subclause 7.3. For more details on ROM devices see clause 7, 3GPP TS 36.300 [3] subclause 15.11, 3GPP TS 23.246 [4] Annex D and 3GPP TS 24.116 [7] clause 4.
NOTE 1: As a matter of implementation, a cellular device can host a ROM device and a traditional UE capable of unicast. Such device is further described in 3GPP TS 36.246 [4] Annex E and called ROM device with independent unicast. The co-hosted UE is connected to a different cell from the MBMS-dedicated cell serving the co-hosted ROM device. If the co-hosted UE and ROM device share baseband resources, the co-hosted UE can use MBMSInterestIndication signalling procedure, specified in TS 36.331 [6], to inform the serving RAN about the baseband resources occupied by the co-hosted ROM device and therefore not available for unicast.
NOTE 2: There may be awareness at the application layer of the ROM device with independent unicast. How this awareness is created is outside of the scope of specifications.
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
4.2 Use cases and requirements
|
In Release 14, the use cases and scenarios for eMBMS services based on LTE have been expanded to include terrestrial broadcasting (the feature also referred to as "EnTV"). This included new requirements:
- network dedicated to TV broadcast via eMBMS;
- SFN deployments with ISD significantly larger than a typical ISD associated with legacy cellular deployments;
- support for ROM device.
NOTE: At the upper layers, the requirements included the support for Free to Air service [2] and for eMBMS network sharing [4].
In Release 16, gap analysis documented in TR 36.776 [9] compared the Release 14 LTE terrestrial broadcasting capabilities with the requirements for 5G dedicated broadcast networks in TR 38.913 [10]. As a result of this analysis, the following two requirements were deemed unfulfilled by Release 14 LTE eMBMS:
1. Support for service over large geographic area, including SFN with ISD > 100km;
2. Support for mobility scenarios including speeds of up to 250 km/h.
In relation to the first requirement, the new ISD of 125 km, referred to as HPHT network, with omni-directional transmitters was defined. The following two ISD were also included in the evaluation:
- 15 km, referred to as LPLT network with sectorized cells;
- 50 km, referred to as MPMT network with omni-directional transmitters.
The first requirement is associated with receivers with high-gain rooftop directional antennas, low mobility and a predominantly line-of-sight channel.
The second requirement is associated with receivers in cars, with external omni-directional antennas.
In addition to the above two requirements, a third requirement was added related to improving the CAS reception for both large ISD and high mobility scenarios.
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
4.3 Enhancements targeting LTE terrestrial broadcast
|
In Release 14, the following key RAN enhancements were made to the specifications to enable LTE terrestrial broadcast:
- MBMS-dedicated cell [3];
- MBSFN subframes using f = 1.25 kHz [8];
- New information blocks on PBCH and PDSCH of CAS [3], [6]:
- MIB-MBMS is transmitted with a 40ms periodicity and updated every 160 msMIB-MBMS with a 40ms periodicity, containing resource allocation for SIB1-MBMS on PDSCH; and
- SIB1-MBMS is transmitted with an 80ms periodicity and updated every 160 msSIB1-MBMS, with an 80ms periodicity, containing information relevant for receiving MBMS service and, optionally, the scheduling of other system information blocks;
- MBMSInterestIndication RRC signalling procedure (see subclause 4.1).
NOTE: For upper layer enhancements, see 3GPP TS 23.246 [4] Annex D and E, 3GPP TS 24.116 [7], 3GPP TS 24.117 [12] and 3GPP TS 26.346 [5] (ROM service aspects).
In Release 16, the following RAN enhancements were made to address the use cases described in subclause 4.2:
- Transmission using f = 0.37 kHz, the cyclic prefix duration of 300µs and the symbol duration of 3ms, for the support of large ISD;
- Subframes using f = 2.5 kHz, the cyclic prefix duration of 100µs and the symbol duration of 0.5ms, for the support of high mobility;
- PDCCH enhancements:
- CFI indication in MIB [6] to avoid the need to decode PCFICH;
- New aggregation level 16; and
- Repetition of PBCH within the CAS to increase PBCH robustness.
Editor’s note: Further Rel.16 enhancements may be added to the list.
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
5 Architecture
| |
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
5.1 General
| |
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
5.2 Network elements
| |
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
5.3 Interfaces
| |
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
5.4 Protocol stack
|
The network architecture for LTE-based 5G terrestrial broadcast is described in 3GPP TS 36.300 [3] subclause 15.1.1, with the exception that only:
- ROM reception via MBMS-dedicated cell; or
- MBMS reception via FeMBMS/Unicast-mixed cell
is supported.
RAN interfaces for LTE-based 5G terrestrial broadcast are described in 3GPP TS 36.300 [3] subclause 15.1.1 and in 3GPP TS 36.440 [11]. In case of a MBMS-dedicated cell, the counting procedure is not supported by the eNB.
User plane and control plane protocol stack for LTE-based 5G terrestrial broadcast is described in 3GPP TS 36.300 [3] subclause 15.1.2 and subclause 15.1.3, respectively.
NOTE: For upper layer architecture, see 3GPP TS 23.246 [4].
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
6 Protocol aspects
| |
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
6.1 Physical layerFrame structure and numerologies
| |
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
6.1.1 Frame structure and numerologies
|
6.1.2 Channels and signalsOnly frame structure type 1 is supported. All numerologies specified in 3GPP TS 36.211 [8] are supported. For subframes using f other than 0.370 kHz, the frame structure is according to Figure 6.1-1. For transmissions using f = 0.370 kHz, the frame structure is shown in Figure 6.1-2.
Figure 6.1-1: Frame structure type 1 for subframes not using f = 0.370 kHz
Figure 6.1-2: Frame structure type 1 for transmissions using f = 0.370 kHz
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
6.2 MBMS Transmission
|
MBMS transmission is performed according to 3GPP TS 36.300 [3] subclause 15.3.3.
MCCH configuration and scheduling is performed according to 3GPP TS 36.300 [3] subclause 15.3.5 and 3GPP TS 36.331 [6] subclause 5.8.1. In case of a MBMS-dedicated cell, the MBMS counting configuration is not supported.
MCCH information acquisition is performed according to 3GPP TS 36.300 [3] subclause 15.3.5 and 3GPP TS 36.331 [6] subclause 5.8.2. In case of a MBMS-dedicated cell, only RRC_IDLE is supported.
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
6.1.3 Physical layer procedures
| |
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
6.32 MAC Layer
|
<BCH and MCH aspects only>MAC layer supports only:
- BCH reception for BCCH;
- DL-SCH reception for BCCH; and
- MCH reception for MCCH/MTCH.
BCH reception and DL-SCH reception in the MAC layer use transparent MAC [16], i.e. single MAC PDU per TTI with no headers. HARQ entity uses the dedicated broadcast HARQ process, defined in [16].
MCH reception in the MAC layer is specified in 3GPP TS 36.321 [16] subclause 5.12 and in 3GPP TS 36.300 [3] subclause 15.3.3.
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
6.43 RLC layer
|
BCCH uses the RLC-TM mode.
MTCH and MCCH use the RLC-UM mode. RLC operation for MTCH and MCCH is described in 3GPP TS 36.300 [3] subclause 15.3.3.
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
6.54 RRC layer
|
RRC layer supports only:
- System information reception (see 3GPP TS 36.331 [6] subclause 5.2) in MBMS-dedicated cell; and
- MBMS reception (see 3GPP TS 36.331 [6] subclause 5.8) in MBMS-dedicated cell and in FeMBMS/Unicast-mixed cell.
For system information reception, the following applies:
- only BCCH-BCH-Message-MBMS and BCCH-DL-SCH-Message-MBMS message class is supported;
- acquisition of system information messages is performed according to 3GPP TS 36.331 [6] subclause 5.2.3b.
For MBMS reception, the following applies:
- MBMS counting procedure and MBMS interest indication procedure are not supported.
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
6.5 Idle mode
| |
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
7 ROM aspects
| |
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
7.1 General
|
Since a ROM device does not support uplink transmission or two-way signalling procedures, and does not comprise USIM, it cannot support all the physical layer procedures of the conventional UE. By the same token, only a subset of idle mode procedures and RRM requirements applicable to a conventional UE will be supported. The following subsections provide an overview of the physical layer and idle mode procedures and the RRM requirements applicable to a ROM device.
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
7.2 Physical layer procedures
|
ROM device only supports the following physical layer procedures specified in 3GPP TS 36.213 [13]:
- Cell search;
- Timing synchronization;
- PDSCH procedures;
- PDCCH assignment procedure;
- PMCH procedures; and
- Assumptions independent on physical channels (clause 12) related to MBMS-dedicated cell.
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
7.3 Idle mode procedures
|
ROM device only supports the following idle mode procedures specified in 3GPP TS 36.304 [14]:
- Cell selection; and
- Cell reselection.
PLMN prioritization for cell reselection is specified in 3GPP TS 36.304 [14] subclause 5.2.4.1.
NOTE: NAS layer PLMN selection does not apply to ROM device. PLMN selection for ROM device is specified in 3GPP TS 24.116 [7].
Editor’s note: FFS is further clarifications are needed, e.g. not all the idle mode states are supported.
ROM device does not support DRX.
|
d832899f12f9cb7303ee0f37d0629dd2
|
36.276
|
7.4 RRM requirements
|
ROM device only supports the following requirements specified in 3GPP TS 36.133 [15]:
- Cell selection; and
- Cell reselection, except for:
- IRAT reselection;
- paging-related requirements; and
- CSG cell-related requirements.
Appendix Upper layer aspects
Pointers only
<Transparent mode>
<Service and session configuration>
<Network and service selection>
Annex <X>:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2019-08
RAN1#97
R1- 1908844
Skeleton TR
0.0.1
2019-11
RAN1#99
R1-1913483
Added technical content to all clauses. Incorporated technical and editorial the comments received in the meeting
0.1.0
2019-11
RAN1#99
R1-191xxxx
Endorsed with minor changes agreed in RAN1#99
0.2.0
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
1 Scope
|
The present document describes new use cases and potential requirements applicable to Public Warning Services for
- UEs with diverse form-factors whose user interface is different from the conventional mobile phones; and
- UEs that are defined by applying 3GPP system to non-ICT industry businesses (e.g. vehicles or machines such as IoT devices or robots) and have the different UE role from what 3GPP has traditionally assumed.
In addition, it considers the improvement of the understandability of the PWS message e.g. displaying language independent or graphical content to users, especially foreigners who might not understand the language used in the text or people with physical disability who may be sight impaired and unable to read the text. So it deals with user interface related potential requirements to address the presentation of the warning message considering circumstances such as language being used (e.g. international roaming scenario where the user does not understand the local language) or users with disability (e.g. people with vision impairment).
The present document does not cover use cases or potential requirements for US WEA and Japan ETWS so the results of this document are not applicable for US and Japan. This document considers national variants of EU-Alert and KPAS related service scenarios and potential requirements.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
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] 3GPP TS 22.268: "Public Warning System (PWS) requirements"
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
3 Definitions, symbols and abbreviations
|
Delete from the above heading those words which are not applicable.
Clause numbering depends on applicability and should be renumbered accordingly.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
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].
Definition format (Normal)
<defined term>: <definition>.
example: text used to clarify abstract rules by applying them literally.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
3.2 Symbols
|
For the purposes of the present document, the following symbols apply:
Symbol format (EW)
<symbol> <Explanation>
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
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].
Abbreviation format (EW)
<ACRONYM> <Explanation>
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
4 Overview
|
This clause provides a high-level overview of the feature that includes:
- description of feature
- benefit(s) the feature provide to the operator, end user, etc
- any other (background) information that helps the reader understand the feature
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5 Use cases for UEs with different or no user interface or with different UE roles
| |
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.1 Use case: UEs with no user interface over direct network connection
| |
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.1.1 Description
|
This use case describes a scenario where UEs with no user interface that are not intended for human type communication are connected to a 3GPP network and receive a PWS message when a disaster occurs. Those UEs with no user interface take pre-defined actions (e.g. shutting down air condition when an earthquake occurs to prevent fire) to minimize damages caused by disasters or protect human.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.1.2 Pre-conditions
|
UEs with no user interface are subscribed to operator’s 3GPP network.
UEs with no user interface are connected to the 3GPP network.
UEs with no user interface monitor the 3GPP network for public warning alarms.
Pre-defined actions or procedures are stored on the UEs with no user interface and can be executed based upon the information in the content of the PWS message about the event or the disaster.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.1.3 Service Flows
|
UEs with no user interface are deployed to manage home appliances such as powering them on and off .
An earthquake suddenly occurs in the area where UEs with no user interface are located and because of the earthquake, a PWS message is broadcast to UEs with no user interface.
UEs with no user interface take pre-defined actions or procedures about the earthquake that is notified by the PWS message.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.1.4 Post-conditions
|
UEs with no user interface take pre-defined actions (e.g. power off) in time that made home appliances less damaged from the earthquake.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.1.5 Potential Impacts or Interactions with Existing Services/Features
|
None identified
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.1.6 Potential Requirements
|
The 3GPP system shall enable the content of a PWS message to include information that can be mapped to an event or a disaster and is identifiable by the UEs with no user interface per event or disaster.
NOTE: The information included in the content of a PWS message may be an identifier of an event or a disaster.
UEs with no user interface shall be able to support the reception of a PWS message broadcast from the 3GPP network.
NOTE: Pre-defined procedures contained in the UE with no user interface may be specified by a device manufacturer or regional regulatory requirement in order to have UEs with no user interface take such pre-defined procedures once receiving a PWS message.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.2 Use case: Remote UEs with no user interface over indirect network connection
| |
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.2.1 Description
|
This use case describes a scenario where remote UEs with no user interface that are not intended for human type communication are connected to 3GPP network via relay UE in coverage of 3GPP network and receive a PWS message via relay UE when a disaster occurs. Those remote UEs with no user interface take pre-defined actions (e.g. shutting down the heater to prevent fire when an earthquake occurs) to minimize damages caused by disasters or protect human.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.2.2 Pre-conditions
|
A relay UE is connected to the 3GPP network and remote UEs with no user interface are in indirect network connection.
Pre-defined actions or procedures are stored on the remote UEs with no user interface and can be executed based upon the information in the content of the PWS message which is transmitted by the relay UE about the event or the disaster.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.2.3 Service Flows
|
Remote UEs with no user interface are deployed to control machines in a factory and are connected to 3GPP network via a relay UE.
An earthquake suddenly occurs close to the factory and the relay UE receives a PWS message.
The relay UE receives a PWS message, and unconditionally forwards the PWS message to the remote UEs with no user interface.
The remote UEs with no user interface take pre-defined actions or procedures about the earthquake that is based upon the information transmitted by the relay UE.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.2.4 Post-conditions
|
Remote UEs with no user interface take pre-defined actions (e.g. shut off the power) in time that made machines in the factory less damaged from the earthquake.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.2.5 Potential Impacts or Interactions with Existing Services/Features
|
None identified
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.2.6 Potential Requirements
|
The remoteUE with no user interface shall be able to support the reception of the information that is related to an event or a disaster notified by PWS message and is transmitted from the relay UE.
NOTE: Subject to regional regulatory requirements and the intended function of the UE (e.g. IoT) which does not have a user interface, the UE may either:
1. Ignore PWS message, or
2. Take actions consistent with the UE function (e.g. IoT) in response to specific PWS messages. An example could be to shut down machinery, or
3. Use alternative alerting mode of user alerting consistent with the UE function (e.g. building alarm system) based on the content of the PWS message.
The remote UE with no user interface shall automatically suppress duplicated notifications. A duplicate is a repetition of a same notification as determined by unique parameters.
The relay UE shall be capable of unconditionally forwarding the PWS message broadcast to areas where remote UEs with no user interface and the relay UE are located without modification on the PWS message received from the network.
For remote UEs receiving PWS message, the relay UE shall relay all PWS messages received from the network without modifications. The remote UE shall perform the duplicate PWS message detection.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.3 Use case: relay UE for indirect network connection of remote UEs
| |
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.3.1 Description
|
This use case describes a scenario where a relay UE that provides an indirect network connection to remote UEs transmits a PWS message to the remote UEs as they are located in an area where the PWS message is broadcast from the 3GPP network.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.3.2 Pre-conditions
|
Bob and Mary go out to the sea by taking their yacht where there is a relay UE on the deck of the yacht to provide indirect network connection to remote UEs inside the steel cabin of the yacht.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.3.3 Service Flows
|
The PWS message is broadcast and the relay UE receives the PWS message notifying that a storm is coming to the area where the yacht is located while Bob and Mary sleep in the steel cabin of the yacht.
The UEs that Bob and Mary have with them could not receive the PWS message directly because the UEs are located inside the steel cabin of the yacht but the relay UE forwards the PWS message to the UEs of Bob and Mary.
The UEs of Bob and Mary receive the PWS message and alarm Bob and Mary about the storm.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.3.4 Post-conditions
|
Bob and Mary woke up due to the warning alarm from the UEs that they have with them inside the cabin and come back to the port before the storm arrives at the area where they are.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.3.5 Potential Impacts or Interactions with Existing Services/Features
|
None identified
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.3.6 Potential Requirements
|
The relay UE shall have the capability of forwarding an incoming PWS message to remote UEs.
A remote UE shall be able to support monitoring PWS messages which are received both directly from the 3GPP network and indirectly via the relay UE.
When a remote UE receives a PWS message transmitted via a relay UE, the remote UE shall carry out the same procedure as specified in 3GPP TS 22.268 [2] for the PWS-UE receiving the PWS message broadcast from the 3GPP network.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.4 Use case: UE with different user interface
| |
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.4.1 Description
|
This use case describes a scenario where the user interface of the mobile device is different from the conventional user interface of the mobile phone, e.g. augmented reality based user interface or hologram based user interface.
Because the network functionalities to broadcast a PWS message need to be kept as unchanged as what is currently specified in 3GPP TS 22.268, such mobile devices with different user interface take the procedure that may be specified by regional regulatory requirements or a device manufacturer if the regional regulatory requirements do not exist for such devices, e.g. displaying the content that is stored in the device and is mapped to a warning event that is extractable from the PWS message broadcast from the network.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.4.2 Pre-conditions
|
The UE with different user interface (e.g. augmented reality based or hologram based user interface) are connected to 3GPP system.
A warning event or disaster is identifiable from information that can be extracted from the PWS message.
Pre-defined content or procedure is mapped in the UE with different user interface to the warning event or disaster
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.4.3 Service Flows
|
Sally is on holidays in Seoul and her device, a UE with user interface that is different from the conventional user interface of a mobile device (e.g. augmented based or hologram based user interface), helps her find a good restaurant at Gangnam area.
Suddenly an earthquake occurs near Seoul so a PWS message is broadcast to cities in Gyeonggi-do Province as well as Seoul.
Sally’s device receives the text based PWS message broadcast from the network.
Sally’s device recognizes the warning event, i.e. the earthquake that is extracted from the PWS message and the device notifies Sally to leave the restaurant.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.4.4 Post-conditions
|
Sally recognized in time about the earthquake occurred thanks to the notification of the device and not by the text-based public warning message itself.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.4.5 Potential Impacts or Interactions with Existing Services/Features
|
None identified
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
5.4.6 Potential Requirements
|
The UE with a different user interface (i.e. a user interface that is not capable of displaying a text-based content) shall be able to support the reception of a PWS message broadcast from the 3GPP network.
The UE with a different user interface shall be able to support the extraction of the information on the type of a notified event or disaster from the received PWS message.
NOTE 1: The information extractable from the received PWS message may be an identifier of an event or a disaster.
NOTE 2: Pre-defined procedures contained in the UE with a different user interface may be specified by a device manufacturer or regional regulatory requirement in order to have the UE with a different user interface carry out such pre-defined procedures once receiving a PWS message and extracting the information on the type of a notified event or disaster.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
6 Considerations
| |
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
6.1 Considerations on the improvement of the understandability of the PWS message
| |
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
6.1.1 Constraints inherent in the language-based and text-based PWS message
|
3GPP specified the requirements for Public Warning System in 3GPP TS 22.268 from 3GPP Release 8 onwards in order to let mobile users receive text-based PWS messages. Language-related requirements described in 3GPP TS 22.268 are as follows.
NOTE 1: Requirements described in the section 5 (Earthquake and Tsunami Warning System) and the section 6 (CMAS-Specific Requirements) of 3GPP TS 22.268 are not included to analyse constraints inherent in the language-based and text-based PWS message.
NOTE 2: Constraints identified in this section might not be applicable for US WEA and Japan ETWS so such clarification needs to be added later after proposed texts are agreed.
In the section 4.2 ‘High level general requirements for Warning Notification delivery’,
- PWS shall only be required to broadcast Warning Notifications in languages as prescribed by regulatory requirements.
In the section 4.3 ‘Warning Notification Content’,
- PWS shall not modify or translate the Warning Notification content specified by the Warning Notification Provider.
In the section 4.5 ‘Support of Warning Notification Providers’,
- PLMN operators shall, at a minimum, be able to support the following functionalities through interaction with Warning Notification Providers:
Activation of Warning Notification delivery
- It shall be possible for multiple Warning Notifications to be activated concurrently from one or more Warning Notification Providers.
In the section 4.6.1 ‘General Requirements’ from the section 4.6 ‘PWS-UE Requirements’,
- PWS-UEs shall only be required to receive and present Warning Notifications in languages as presented by the Warning Notification Provider. Regional/regulatory requirements may require the Warning Notifications to be broadcast in multiple languages.
- There shall be no requirement for language translation in the operator’s network or the UE.
- The PWS-UE shall automatically suppress duplicate notifications. A duplicate is a repetition of a previous notification as determined by unique parameters.
- PWS-UE shall be able to support concurrent reception of multiple Warning Notifications.
In the section 4.6.4 ‘Enabling and disabling of Warning Notifications’ from the section 4.6 ‘PWS-UE Requirements’,
- It shall be possible for users to disable (e.g., opt-out) presentation of some or all of the Warning Notifications, subject to regulatory requirements and/or operator policy. The user shall be able to select PWS-UE enabling/disabling options via the User Interface to disable, or later enable, the PWS-UE behavior in response to some or all Warning Notifications. Depending on the regional/regulatory requirements, the user shall be able to receive Warning Notifications in one or more selected languages.
In the section 7.2 ‘Additional PWS Requirements Specific to EU-ALERT,
- EU-ALERT shall support Warning Notifications in various languages. To support international roaming, it is expected that countries adopting EU-ALERT use the same Message Identifier for Warning Notifications in the local language. If Warning Notifications are broadcast in other languages besides the local language, then the Message Identifier for such Warning Notifications are expected to be the same across the countries adopting EU-ALERT.
Based on the requirements above, any user with a mobile device is supposed to receive the text-based PWS message in languages as prescribed by regulatory requirements no matter whether there is any constraint inherent in users that makes users unable to understand such message (e.g. users who do not know the language used in the PWS message such as migrants or international travellers, or users with disabilities such as vision impairment).
In addition, as the connected society is moving to the 5G era, diverse new types of mobile devices are expected to help users with disabilities overcome their difficulties for the convenience in their lives. This means that more and more mobile users with disabilities will make use of mobile devices. Further on, the number of mobile users who internationally travel or live in other countries than their mother country without knowledge of the local languages is also anticipated to rise more and more.
Therefore, additional potential requirements are necessary to be identified to address the presentation of the PWS message considering circumstances such as language being used (e.g. international roaming scenario where the user does not understand the local language) or users with disabilities (e.g. people with vision impairment).
Following consideration needs to be taken into account as well when additional potential requirements are identified for such mobile users under the current network procedure
- The size of the additional content included in the PWS message shall be constrained by the existing PWS system for any content intended for mobile users with disabilities.
- Considering the PWS message is broadcast to mobile users, specific contents dedicated to some mobile users with any disability are impossible to notify them individually that an event or a disaster happens.
- Device manufacturers should extend accessibility support to apply to PWS message presentation as well.
Editor’s Note: Depending on regional regulatory requirements, additional considerations on alternative presentation forms or style to alert people who are not able to understand text-based PWS messages needs to be added.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
6.1.2 Potential requirements proposed for the improvement of the understandability of the PWS message
|
For mobile users with disabilities, the user interface of UEs that are used by them is extended by UE accessibility functions. The most effective presentation of the warning indication may be different from what is normally defined for mobile users without disabilities. Considering such difference, following potential requirements are proposed in order to improve the comprehension of the PWS message.
• The UE with a user interface providing accessibility extensions to mobile users with disabilities shall be able to support the reception of a PWS message broadcast from the 3GPP network.
• The UE with a user interface providing accessibility extensions to mobile users with disabilities shall be able to support the extraction of the information on the type of a PWS notified event or disaster from the received PWS message.
NOTE 1: The information extractable from the received PWS message content may be an identifier of the type of an event or a disaster.
NOTE 2: Subject to regional regulatory requirements the UE may use alternative alerting modes for user alerting consistent with UE accessibility extensions and based on the content of the PWS message.
For mobile users who are in a region whose local language they do not know, the following potential requirements are proposed in order to improve the understandability of the PWS message.
• The content of a PWS message shall be able to include language-independent content (e.g. pictogram or symbolic icon representing an event or a disaster) and to be identifiable per event or disaster.
• The UE shall support the presentation of language-independent content defined by regional regulatory requirements contained in a PWS message content.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
6.2 Considerations on existing PWS requirements for UEs with different or no user interface or with different UE roles
| |
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
6.2.1 Applicability review of existing PWS requirements
|
UEs with different or no user interface or with different UE roles didn’t exist when existing PWS requirements were specified in 3GPP TS 22.268 [2] so some of existing PWS requirements might not be applicable and need to be revised or to add some additional requirements for UEs with different or no user interface or with different UE roles. Table 1, Table 2 and Table 3 show which existing PWS requirements are applicable or need to be revisited for UEs with different or no user interface or with different UEs.
Table 1: General PWS requirements applicable for UEs with different UI, with no UI and with different role
Existing requirements in the section 4 of 3GPP TS 22.268 [2]
UEs with different UI
UEs with no UI
UEs with different role
4.2 High level general requirements for Warning Notification delivery
PWS shall be able to broadcast Warning Notifications to multiple users simultaneously with no acknowledgement required.
Applicable
Applicable
Applicable
PWS shall be able to support concurrent broadcast of multiple Warning Notifications.
Applicable
Applicable
Applicable
Warning Notifications shall be broadcast to a Notification Area which is based on the geographical information as specified by the Warning Notification Provider.
Applicable
Applicable
Applicable
PWS capable UEs (PWS-UE) in idle mode shall be capable of receiving broadcasted Warning Notifications.
NOTE: A bandwidth reduced low complexity UE or a UE supporting eDRX may not support all requirements for PWS, including ETWS, CMAS, EU-Alert and KPAS.
Applicable
Applicable
Applicable
PWS shall only be required to broadcast Warning Notifications in languages as prescribed by regulatory requirements.
Applicable
Applicable
Applicable
Warning Notifications are processed by PWS on a first in, first out basis, subject to regulatory requirements.
Applicable
Applicable
Applicable
Reception and presentation of Warning Notifications to the user shall not pre-empt an active voice or data session.
Applicable
Applicable
Applicable
Warning Notifications shall be limited to those emergencies where life or property is at imminent risk, and some responsive action should be taken.
NOTE: This requirement does not prohibit the use of the operator’s network (i.e. broadcast technology) implemented for Warning Notifications to be used for commercial services.
Applicable
Applicable
Applicable
4.3 Warning Notification Content
PWS shall not modify or translate the Warning Notification content specified by the Warning Notification Provider.
Applicable
Applicable
Applicable
Warning Notifications should not contain anything that would drive immediate and debilitating traffic loads into the PLMN (i.e., URLs or dialable numbers).
Applicable
Applicable
Applicable
4.4 Granularity of the distribution
Based on the geographical information indicated by the Warning Notification Provider, it shall be possible for the PLMN operators to define the Notification Area based on their network configuration of the area coverage such as distribution of cells, Node Bs, RNCs, etc.
Applicable
Applicable
Applicable
4.5 Support of Warning Notification Providers
PLMN operators shall, at a minimum, be able to support the following functionalities through interaction with Warning Notification Providers:
Applicable
Applicable
Applicable
- Activation of Warning Notification delivery
It shall be possible for multiple Warning Notifications to be activated concurrently from one or more Warning Notification Providers.
Applicable
Applicable
Applicable
- Cancellation of Warning Notification delivery
A cancellation is a command from the Warning Notification Provider to stop dissemination of a specific Warning Notification.
Applicable
Applicable
Applicable
- Updating of Warning Notification delivery
Warning Notification Providers update a previous Warning Notification to provide new instructions/information to the PLMN operator. When the Warning Notification Provider updates a previous Warning Notification they provide an identifier that allows the PLMN operator to associate the updated Warning Notification with the previous Warning Notification.
Applicable
Applicable
Applicable
Additional functionality may be required based on regulatory or operator policy requirements.
Applicable
Applicable
Applicable
4.6 PWS-UE Requirements
4.6.1 General Requirements
PWS-UEs shall only be required to receive and present Warning Notifications in languages as presented by the Warning Notification Provider. Regional/regulatory requirements may require the Warning Notifications to be broadcast in multiple languages.
Applicable
Applicable
Applicable
There shall be no requirement for language translation in the operator’s network or the UE.
Applicable
Applicable
Applicable
It shall be possible for the Warning Notification to be displayed on the PWS-UE upon reception and without any user interaction.
Applicable
Applicable
Applicable
It shall be possible for users to configure the behavior of a PWS-UE with regard to Warning Notification alerting and should allow at least volume adjustment.
Applicable
Applicable
Applicable
The PWS-UE shall support a dedicated alerting indication (audio attention signal and a dedicated vibration cadence) and be distinct from any other device alerts and restricted to use for Warning Notification purposes. The User Interface shall support the ability for the user to suppress the dedicated audio attention signal and/or the dedicated vibration cadence when a Warning Notification is received.
Need to be revisited
Need to be revisited
Applicable
The alerting indication for a specific Warning Notification shall continue until suppressed by users' manual operation (e.g. by pushing keys). The frequency and duration of the continued alerting indication is mobile device implementation specific. This shall not suppress the alerting indication for subsequent Warning Notifications.
Applicable
Need to be revisited
Applicable
The PWS-UE shall automatically suppress duplicate notifications. A duplicate is a repetition of a previous notification as determined by unique parameters.
Applicable
Applicable
Applicable
The PWS-UE shall not support any capabilities to forward received Warning Notifications, to reply to received Warning Notifications, or to copy and paste the content of Warning Notifications.
Applicable
Applicable
Need to be newly specified for e.g. relay UE
PWS-UEs should have the ability to present previously displayed Warning Notifications if requested by the user.
Applicable
Applicable
Applicable
PWS-UE shall be able to support concurrent reception of multiple Warning Notifications.
Applicable
Applicable
Applicable
4.6.2 Support of non-Warning Notification capable UEs
Support of non-Warning Notification capable UEs is subject to regulatory requirements and/or operator's policy.
Applicable
Applicable
Applicable
4.6.3 Battery Life of PWS-UE
Battery life of the PWS-UE shall not be significantly reduced by PWS.
Applicable
Applicable
Applicable
4.6.4 Enabling and disabling of Warning Notifications
The PWS-UE shall be configured to receive all Warning Notifications.
Applicable
Applicable
Applicable
It shall be possible for users to disable (e.g., opt-out) presentation of some or all of the Warning Notifications, subject to regulatory requirements and/or operator policy. The user shall be able to select PWS-UE enabling/disabling options via the User Interface to disable, or later enable, the PWS-UE behavior in response to some or all Warning Notifications. Depending on the regional/regulatory requirements, the user shall be able to receive Warning Notifications in one or more selected languages.
Applicable
Applicable
Applicable
Where regional or national regulations allow, the HPLMN operator shall be able to instruct the PWS-UE to ignore all Warning Notifications in the HPLMN and in PLMNs equivalent to it, by means of a setting on the USIM.
Applicable
Applicable
Applicable
Where regional or national regulations pertaining to a VPLMN allow, the HPLMN operator shall be able to instruct the PWS-UE to ignore all Warning Notifications that are received whilst in this VPLMN, by means of a setting on the USIM, when the integrity of Warning Notifications in this VPLMN is known by the HPLMN operator to be compromised. This setting need not distinguish VPLMNs.
Applicable
Applicable
Applicable
Subject to regional or national regulations, a PWS-UE in limited service state shall be able to receive and display Warning Notifications.
NOTE 1: Non-existing or empty USIM data files results in all Warning Notifications being presented to the PWS application.
Applicable
Applicable
Applicable
4.7 Roaming Requirements
It shall be possible for PWS-UEs that are enabled for Warning Notifications in the HPLMN to receive Warning Notifications from the VPLMN supporting PWS when roaming.
Applicable
Applicable
Applicable
A PWS-UE that does not support the PWS requirements of the VPLMN’s PWS service may not receive Warning Notifications from that VPLMN.
NOTE: See section 4.9 for roaming impacts to PWS due to regional regulatory requirements.
Applicable
Applicable
Applicable
4.8 Security Requirements
PWS shall only broadcast Warning Notifications that come from an authenticated authorized source.
Applicable
Applicable
Applicable
The following requirements only apply when not roaming internationally:
- When required by regional or national regulations, the integrity of the Warning Notification shall be protected. If no such regulatory requirement exists, there shall be no integrity protection of Warning Notifications, and all Warning Notifications shall be presented to the PWS application on the PWS-UE.
- When required by regional or national regulations, the PWS shall protect against false Warning Notification messages. If no such regulatory requirement exists, there shall be no protection against false Warning Notifications, and all Warning Notifications shall be presented to the PWS application on the PWS-UE.
NOTE 1: These requirements are subject to regulatory policies.
NOTE 2: The authentication and authorisation of the source are outside the scope of 3GPP Specifications.
Applicable
Applicable
Applicable
4.9 Regulatory Requirements
The PWS offered by a PLMN may be subject to PWS regional regulatory requirements and thus, the PWS offered may differ from PLMN to PLMN as well as from region to region within a PLMN.
Applicable
Applicable
Applicable
Table 2: EU-ALERT specific requirements applicable for UEs with no or different user interfaces or UEs with different role
Existing requirements in the section 7 of 3GPP TS 22.268 [2]
UEs with different UI
UEs with no UI
UEs with different role
7.2 Additional PWS Requirements Specific to EU-ALERT
EU-ALERT shall support three types of Warning Notifications: Alert messages to warn citizens of an imminent emergency situation, Advisory messages of lesser urgency, and Amber alerts.
Applicable
Applicable
Applicable
The Alert messages shall be supported with three levels of severity. EU-Alert level 1 shall have no opt-out; levels 2 and 3 shall allow opt-out by the user. All levels of EU-ALERT messages shall be associated with a dedicated alerting indication.
NOTE: EU-Alert level 1 is compatible with the Presidential Alert in CMAS. EU-Alert level 2 is compatible with CMAS Extreme Alerts and EU-Alert level 3 is compatible with CMAS Severe Alert.
Applicable
Applicable
Applicable
The Advisory messages have only one level. Advisory messages shall not be associated with any dedicated alerting indication.
Applicable
Applicable
Applicable
Depending on national requirements, Amber alerts may need to be broadcast as part of the EU-ALERT service. Amber alerts shall not be associated with any dedicated alerting indication.
Applicable
Applicable
Applicable
EU-ALERT shall support Warning Notifications in various languages. To support international roaming, it is expected that countries adopting EU-ALERT use the same Message Identifier for Warning Notifications in the local language. If Warning Notifications are broadcast in other languages besides the local language, then the Message Identifier for such Warning Notifications are expected to be the same across the countries adopting EU-ALERT.
Applicable
Applicable
Applicable
EU-ALERT shall be supported on GERAN, UTRAN and E-UTRAN radio access technologies.
Applicable
Applicable
Applicable
Table 3: KPAS specific requirements applicable for UEs with no or different user interfaces or UEs with different role
Existing requirements in the section 8 of 3GPP TS 22.268 [2]
UEs with different UI
UEs with no UI
UEs with different role
8.1 Introduction to Korean Public Alert System
the system supporting Korean Public Alert System (KPAS) shall transmit the public alert message with high priority in order to provide up-to-date information on emergency situations. (e.g. In Tsunami situation, it is recommended to deliver message between CBC and UE in several seconds.).
Applicable
Applicable
Applicable
8.2 Additional PWS Requirements Specific to Korean Public Alert System (KPAS)
Two classes of Warning Notification shall be supported; class 0 & class 1.
Applicable
Applicable
Applicable
The classes are differentiated per opt-out function. Class 0 shall have no opt-out and class 1 shall allow opt-out by the user.
Applicable
Applicable
Applicable
The characteristics of the Warning Notification shall follow the requirements specified in clause 4.
Applicable
Applicable
Applicable
The current implementation requirement is for the message of up to 180Bytes (90 Korean Characters) text.
Applicable
Applicable
Applicable
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
6.2.2 Proposals on existing PWS requirements
|
Proposed texts are given in Table 4 in order to make existing PWS requirements with proposed texts applicable for UEs with different or no user interface or with different role as well as for legacy UEs with the conventional user interface that 3GPP assumed when these existing PWS requirements were specified in 3GPP TS 22.268 [2].
NOTE: Proposed texts for general PWS requirements described in the section 4 of 3GPP TS 22.268 [2] do not take into account US WEA and Japan ETWS so such clarification needs to be added later once proposed texts are agreed.
Table 4: Proposed texts on general PWS requirements applicable for UEs with different UI, with no UI and with different role
Existing requirements in the section 4 of 3GPP TS 22.268
UEs with different UI
UEs with no UI
UEs with different role
4.6 PWS-UE Requirements
4.6.1 General Requirements
The PWS-UE shall support a dedicated alerting indication (audio attention signal and a dedicated vibration cadence) and be distinct from any other device alerts and restricted to use for Warning Notification purposes. The User Interface shall support the ability for the user to suppress the dedicated audio attention signal and/or the dedicated vibration cadence when a Warning Notification is received.
Need to be revisited
Need to be revisited
Applicable
Proposed texts:
The PWS-UE shall support a dedicated alerting indication (audio attention signal and a dedicated vibration cadence) and be distinct from any other device alerts and restricted to use for Warning Notification purposes. The User Interface shall support the ability for the user to suppress the dedicated audio attention signal and/or the dedicated vibration cadence when a Warning Notification is received.
NOTE: In case of a PWS-UE that does not have a user interface or has a user interface that is not able to support a dedicated alerting indication, modification of this requirements needs to consider several factors:
1. Recent regulations
2. Intended functions for devices (e.g. IoT)
3. Device’s support for the alerting indication (audio attention signal and a dedicated vibration cadence) or alternative alert indications
The alerting indication for a specific Warning Notification shall continue until suppressed by users' manual operation (e.g. by pushing keys). The frequency and duration of the continued alerting indication is mobile device implementation specific. This shall not suppress the alerting indication for subsequent Warning Notifications.
Applicable
Need to be revisited
Applicable
Proposed texts:
The alerting indication for a specific Warning Notification shall continue until suppressed by users' manual operation (e.g. by pushing keys). The frequency and duration of the continued alerting indication is mobile device implementation specific. This shall not suppress the alerting indication for subsequent Warning Notifications.
NOTE: In case of a PWS-UE with no user interface, modification of this requirements needs to consider several factors:
1. Recent regulations
2. Intended functions for devices (e.g. IoT)
3.Device’s support for the suppression of Warning Notification
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
7 Potential Requirements
|
Text to be provided.
|
2e4def7229d8545d814f4132a20a55ee
|
22.969
|
8 Conclusion and Recommendations
|
Text to be provided.
Annex <A>:
<Annex title>
Annexes are only to be used where appropriate:
Annexes are labelled A, B, C, etc. and are "informative"(3GPP TRs are informative documents by nature).
Annex <X>:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2016-11
SA1#76
S1-163232
TR Skeleton
0.0.0
2016-11
SA1#76
S1-163394
Addition of the scope
0.1.0
2017-02
SA1#77
S1-171451
Inclusion of:
Use case on UEs with no user interface over direct network connection (S1-171448)
Use case on UEs with no user interface over indirect network connection (S1-171449)
Use case on relay UE for indirect network connection of remote UEs (S1-171450)
Use case on UE with different user interface (S1-171451)
0.2.0
2017-05
SA1#78
S1-172066
Inclusion of:
Potential requirements in the section 5.1.6 (S1-172060)
Potential requirements in the section 5.2.6 (S1-172355)
Potential requirements in the section 5.4.6 (S1-172062)
Consideration on the improvement of the understandability of the PWS message (S1-172356)
Considerations on existing PWS requirements for UEs with different or no user interface or with different UE roles (S1-172357)
MCC NOTE: WRONGLY MENTIONED AS “v.1.0.0” in S1-172066
0.3.0
2017-06
SA#76
SP-170452
MCC Clean-up for presentation to SA
1.0.0
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
1 Scope
|
The present document specifies the Information Model definitions and Solution Set definitions for 5G Core Network (5GC) network resource model, to fulfil the requirements identified in 3GPP TS 28.542 [2].
The Information Model definitions define the semantics and behaviour of information object class attributes and relations visible on the management interfaces in a protocol and technology neutral way. And Solution Set definitions define one or more solution set(s) with specific protocol(s) according to the Information Model definitions
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
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] 3GPP TS 28.542: "Management and orchestration of networks and network slicing; 5G Core Network (5GC) Network Resource Model (NRM); Stage 1".
[3] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[4] 3GPP TS 23.003: "Numbering, Addressing and Identification".
[5] 3GPP TS 28.541: "Management and orchestration of networks and network slicing; NR and NG-RAN Network Resource Model (NRM); Stage 2 and stage 3".
[6] 3GPP TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[7] 3GPP TS 28.702: "Core Network (CN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)".
[8] 3GPP TS 28.708: "Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)”.
[9] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS); Stage 2".
[10] 3GPP TS 29.510: "5G system; Network Function Repository Services; Stage 3".
[11] 3GPP TS 29.531: "5G System; Network Slice Selection Services Stage 3".
[12] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[13] 3GPP TS 32.152: "Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire".
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
3 Definitions and abbreviations
| |
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
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. For terms and definitions not found here, please refer to 3GPP TS 28.542 [2]. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1] and 3GPP TS 28.542 [2].
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
3.2 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] and 3GPP TS 28.542 [2].
JSON JavaScript Object Notation
4 Information Model
4.1 Imported and associated information entities
Label reference
Local label
TS 28.622 [6], information object class, SubNetwork
SubNetwork
TS 28.622 [6], information object class, ManagedElement
ManagedElement
TS 28.622 [6], information object class, ManagedFunction
ManagedFunction
TS 28.622 [6], information object class, EP_RP
EP_RP
TS 28.541 [5], information object class, GNBFunction
GNBFunction
TS 28.541 [5], information object class, GNBCUFunction
GNBCUFunction
TS 28.541 [5], information object class, GNBCUCPFunction
GNBCUCPFunction
TS 28.541 [5], information object class, GNBCUUPFunction
GNBCUUPFunction
TS 28.541 [5], information object class, NGENBFunction
NGENBFunction
TS 28.708 [8], information object class, ServingGWFunction
ServingGWFunction
TS 28.702 [7], information object class, SmsIwmscFunction
SmsIwmscFunction
TS 28.702 [7], information object class, SmsGmscFunction
SmsGmscFunction
TS 28.702 [7], information object class, GmlcFunction
GmlcFunction
TS 32.152 [13], stereotype, <<ProxyClass>>
<<ProxyClass>>
4.2 Class diagram
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.2.1 Class diagram of 5GC NFs
| |
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.2.1.1 Relationships
|
This clause depicts the set of classes (e.g. IOCs) that encapsulates the information relevant for NRM of 5GC NFs definitions. This clause provides the overview of the relationships of relevant classes in UML. Subsequent clauses provide more detailed specification of various aspects of these classes.
The Figure 4.2.1.1-1 shows the 5GC NF NRM containment/naming relationship.
Figure 4.2.1.1-1: 5GC NRF containment/naming relationship
The Figure 4.2.1.1-2 shows the transport view of AMF NRM.
Figure 4.2.1.1-2: Transport view of AMF NRM
The Figure 4.2.1.1-3 shows the transport view of SMF NRM.
Figure 4.2.1.1-3: Transport view of SMF NRM
The Figure 4.2.1.1-4 shows the transport view of UPF NRM.
Figure 4.2.1.1-4: Transport view of UPF NRM
The Figure 4.2.1.1-5 shows the transport view of N3IWF NRM.
Figure 4.2.1.1-5: Transport view of N3IWF NRM
The Figure 4.2.1.1-6 shows the transport view of PCF NRM.
Figure 4.2.1.1-6: Transport view of PCF NRM
The Figure 4.2.1.1-7 shows the transport view of AUSF NRM.
Figure 4.2.1.1-7: Transport view of AUSF NRM
The Figure 4.2.1.1-8 shows the transport view of UDM NRM.
Figure 4.2.1.1-8: Transport view of UDM NRM
The Figure 4.2.1.1-9 shows the transport view of UDR NRM.
Figure 4.2.1.1-9: Transport view of UDR NRM
The Figure 4.2.1.1-10 shows the transport view of UDSF NRM.
Figure 4.2.1.1-10: Transport view of UDSF NRM
The Figure 4.2.1.1-11 shows the transport view of NWDAF NRM.
Figure 4.2.1.1-11: Transport view of NWDAF NRM
The Figure 4.2.1.1-12 shows the transport view of NRF NRM.
Figure 4.2.1.1-12: Transport view of NRF NRM
The Figure 4.2.1.1-13 shows the transport view of NSSF NRM.
Figure 4.2.1.1-13: Transport view of NSSF NRM
The Figure 4.2.1.1-14 shows the transport view of SMSF NRM.
Figure 4.2.1.1-14: Transport view of SMSF NRM
The Figure 4.2.1.1-15 shows the transport view of 5G location service related NRM.
Figure 4.2.1.1-15: Transport view of LMF NRM
The Figure 4.2.1.1-16 shows the transport view of 5G-EIR NRM.
Figure 4.2.1.1-16: Transport view of 5G-EIR NRM
The Figure 4.2.1.1-17 shows the transport view of SEPP NRM.
Figure 4.2.1.1-17: Transport view of SEPP NRM
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.2.1.2 Inheritance
|
This clause depicts the inheritance relationships that exist between IOCs.
Figure 4.2.1.2-1 shows the inheritance hierarchy from IOC ManagedFunction related to the 5GC NF NRM.
Figure 4.2.1.2-1: Inheritance hierarchy from IOC ManagedFunction related to the 5GC NF NRM
Figure 4.2.1.2-2 shows the inheritance hierarchy from IOC EP_RP related to 5GC NF NRM.
Figure 4.2.1.2-2: Inheritance hierarchy from IOC EP_RP related to the 5GC NF NRM
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.2.2 Class diagram of AMF Region/AMF Set
| |
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.2.2.1 Relationships
|
This clause depicts the set of classes (e.g. IOCs) that encapsulates the information relevant for NRM of AMF Region/AMF Set definitions. This clause provides the overview of the relationships of relevant classes in UML. Subsequent clauses provide more detailed specification of various aspects of these classes.
The Figure 4.2.2.1-1 shows the AMF Region/AMF Set NRM containment/naming relationship.
Figure 4.2.2.1-1: AMF Region/AMF Set NRM
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.2.2.2 Inheritance
|
This clause depicts the inheritance relationships that exist between IOCs.
Figure 4.2.2.2-1 shows the inheritance hierarchy from IOC ManagedFunction related to the AMF Region/AMF Set NRM.
Figure 4.2.2.2-1: AMF Region/AMF Set Inheritance
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.3 Class definitions
| |
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.3.1 AMFFunction
| |
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.3.1.1 Definition
|
This IOC represents the AMF functionality in 5GC. For more information about the AMF, see 3GPP TS 23.501 [3].
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.3.1.2 Attributes
|
Attribute name
Support Qualifier
isReadable
isWritable
isInvariant
isNotifyable
pLMNIdList
M
M
M
-
M
aMFIdentifier
M
M
M
-
M
sBIFQDN
M
M
M
-
M
sBIServiceList
M
M
-
-
M
weightFactor
M
M
M
-
M
nSSAI
CM
M
-
-
M
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.3.1.3 Attribute constraints
|
Name
Definition
nSSAI CM Support Qualifier
The condition is “network slicing feature is supported”.
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.3.2 SMFFunction
| |
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.3.2.1 Definition
|
This IOC represents the SMF function in 5GC. For more information about the SMF, see 3GPP TS 23.501 [3].
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.3.2.2 Attributes
|
Attribute name
Support Qualifier
isReadable
isWritable
isInvariant
isNotifyable
pLMNIdList
M
M
M
-
M
tAClist
M
M
M
-
M
sBIFQDN
M
M
M
-
M
sBIServiceList
M
M
-
-
M
nSSAI
CM
M
M
-
M
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.3.2.3 Attribute constraints
|
Name
Definition
nSSAI CM Support Qualifier
The condition is “network slicing feature is supported”.
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.3.3 UPFFunction
| |
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.3.3.1 Definition
|
This IOC represents the UPF function in 5GC. For more information about the UPF, see 3GPP TS 23.501 [3].
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.3.3.2 Attributes
|
Attribute name
Support Qualifier
isReadable
isWritable
isInvariant
isNotifyable
pLMNIdList
M
M
M
-
M
tAClist
M
M
M
-
M
nSSAI
CM
M
M
-
M
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.3.3.3 Attribute constraints
|
Name
Definition
nSSAI CM Support Qualifier
The condition is “network slicing feature is supported”.
|
d3ac8d6aa3347ad7b01f9ee2550c87ae
|
28.543
|
4.3.4 N3IWFFunction
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.