name: ETWS
full_form: Earthquake and Tsunami Warning System
context: System Information between BSSs, so that NACC can work across BSS boundaries. Currently, there are procedures defined on the Gb and Gn interfaces to enable signalling of GERAN SI/PSI between BSSs. This RAN Information Management (RIM) mechanism was defined initially for the use of NACC, although in a manner that could be extended for applications other than NACC. It consists of the following messages: - RAN INFORMATION REQUEST - from Source BSS to Target BSS â requests GERAN SI/PSI. - RAN INFORMATION â from target BSS to source BSS â analogous to the Information Exchange over Iur and includes GERAN SI/PSI for one or more GERAN cells. - RAN INFORMATION ACKNOWLEDGE â from Source BSS to Target BSS. - RAN INFORMATION ERROR - to inform about e.g. message syntax errors. In Release 5, TSG RAN approved the provision of the GERAN (P)SI messages in the CELL CHANGE ORDER FROM UTRAN message. In order for this feature to work successfully, a standardised method is required to signal relevant GERAN
description: The Earthquake and Tsunami Warning System (ETWS) is a service provided by the network to user equipment (UE) in limited service mode. It allows for the reception of emergency alerts and notifications related to earthquakes and tsunamis, along with other services such as emergency calls and Commercial Mobile Alert Service (CMAS). The ETWS is supported on acceptable cells that meet specific requirements, enabling UEs to camp on these cells and receive critical warnings.
explanation: The context describes ETWS as a service offered by the network to user equipment. It provides alerts and notifications related to earthquakes and tsunamis, placing it within the category of a telecommunications service.
section_title: 4.3	Service type in Idle and Connected Mode
biotag_Context: B-Message,I-Message,O,O,O,O,B-Procedure,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,B-Network,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,B-Network,O,O,B-Network,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,B-Network,O,O,B-Network,O,B-Message,O,O,O,B-Network Function,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,B-Organization,B-Network,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network
biotag_Description: O,B-Service,I-Service,I-Service,I-Service,I-Service,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,I-Service,I-Service,I-Service,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O