Tech-invite3GPPspaceIETF RFCsSIP

Content for  TR 23.828  Word version:  8.0.0

Top   Top   None   None   Next
1…   5…


1  Scopep. 5

The present document is a temporary architectural solution placeholder for Earthquake and Tsunami Warning System (ETWS). This document is to present various architecture and function approaches for 3GPP networks (i.e. GERAN, UTRAN, and LTE) based on the ETWS requirements described in TS 22.168.

2  Referencesp. 5

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.
TR 21.905: "3G Vocabulary".
TS 22.168: "Earthquake and Tsunami Warning System (ETWS) Requirements; Stage 1".
TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
TS 25.331: "RRC Protocol Specification".
TR 25.925: "Radio Interface for Broadcast/Multicast Services".
TR 25.419: "UTRAN Iu interface: Service Area Broadcast Protocol SABP".
TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description".
TS 22.042: "Network Identity and Time Zone (NITZ) service description; Stage 1".
TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
TS 23.003: "Numbering, addressing and identification".
TS 23.048: "Security mechanisms for the (U)SIM application toolkit; Stage 2".

3  Definitions and abbreviationsp. 5

3.1  Definitionsp. 5

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.
Primary Notification:
is information which is used specifically in Earthquake and Tsunami Warning System in order to notify users about the most urgent event in seconds rather than minutes, such as imminent occurrence of Earthquake.
Secondary Notification:
is information which is used specifically in Earthquake and Tsunami Warning System in order to notify users supplementary information that is of lesser urgency such as instructions on what to do / where to get help, for example, map to refuge facilities, time table of food distribution .These information, in general, would be issued by local government.

3.3  Abbreviationsp. 6

For the purposes of the present document, the abbreviations given in TR 21.905 apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

4  Overview of ETWSp. 6

4.1  Generalp. 6

4.2  Technical requirementsp. 6

The following technical requirements are identified:
  • The primary Notification shall be delivered within 4 seconds from the presentation of the information to the PLMN to the UE in the Notification Area. This may require the introduction of additional capabilities to current messaging services
  • Based on the geographical information indicated by the Warning Notification Provider, the network operator shall have the capability to select the Notification Areas on their network configuration such as distribution of cells, Node Bs, and RNCs. At least NodeB level granularity shall be achieved.
  • Primary Notification shall support at least three types of emergency indications: Earthquake, Tsunami, and Testing.
  • Primary Notification and Secondary Notification shall support indications of UE behaviour. Specification on the number of UE behaviours and types of UE behaviour is FFS.
  • A security mechanism shall be provided to mitigate threats of duplicate or false ETWS messages.
  • The solution shall attempt to minimize the impact to the UE battery life.

4.3  Architectural considerationsp. 6

Following architectural considerations are identified:
  • Network operator may deploy multiple radio access technologies e.g. both GERAN and UTRAN or LTE and UTRAN; consequently, the consideration is how the warning notification can be sent to users with different messaging service centres (e.g. CBC for CBS and BM-SC for MBMS).

Up   Top   ToC