Electronic device and method for transmitting warning message in wireless communication system

Abstract

An electronic device may comprise a memory that stores instructions, and at least one processor. The instructions, when executed by the at least one processor, may cause the electronic device to: receive a first request message for broadcasting a first warning message of system information for a public warning system; in response to the first request message, transmit first segments of the first warning message on a cell during a first transmission period corresponding to two modification periods; on the basis of receiving a second request message for broadcasting a second warning message of the system information in the first transmission period, determine whether or not all available system information windows are in use; if all the available SI windows are in use, store the second warning message in a buffer; and after all the first segments of the first warning message are transmitted, transmit second segments of the second warning message on the cell during a second transmission period corresponding to the two modification periods.

Description

Electronic device and method for transmitting warning messages in a wireless communication system

[0001] The present disclosure relates to a wireless communication system. More specifically, the present disclosure relates to an electronic device and method for transmitting an alert message in a wireless communication system.

[0002] When a disaster occurs, information about the disaster and response measures can be provided to users to minimize damage to life and property. To provide users with disaster information and response measures, the 3rd Generation Partnership Project (3GPP) defined a public warning system (PWS).

[0003] The above information may be provided as background art to aid in understanding the present disclosure. No claim or determination is made as to whether any of the above is applicable as prior art related to the present disclosure.

[0004] In embodiments, an electronic device is provided. The electronic device may include a memory storing instructions and at least one processor. The instructions, when executed by the at least one processor, may cause the electronic device to receive a first request message for broadcasting a first warning message of system information for a public warning system (PWS), and, in response to the first request message, transmit first segments of the first warning message on a cell during a first transmission period corresponding to two modification periods, and, based on receiving a second request message for broadcasting a second warning message of the system information in the first transmission period, determine whether all available system information (SI) windows are in use, and, if all available SI windows are in use, store the second warning message in a buffer, and, after all the first segments of the first warning message have been transmitted, transmit second segments of the second warning message on the cell during a second transmission period corresponding to the two modification periods.

[0005] In embodiments, an electronic device is provided. The electronic device may include a memory storing instructions, and at least one processor. The instructions, when executed by the at least one processor, may cause the electronic device to receive a first request message for broadcasting a first warning message of system information for a public warning system (PWS), receive a second request message for broadcasting a second warning message of the system information for the PWS, and, if the first warning message corresponds to a first ongoing warning message on a cell, transmit the first warning message and at least one repetitive warning message corresponding to the first warning message on the cell during a first transmission period, and, after both the first warning message and the at least one repetitive warning message are transmitted, transmit second segments of the second warning message on the cell during a second transmission period subsequent to the first transmission period. Each message of the first warning message and the at least one repetitive warning message corresponding to the first warning message may include identical first segments.

[0006] In embodiments, an electronic device is provided. The electronic device may include a memory storing instructions, and at least one processor. The instructions, when executed by the at least one processor, may cause the electronic device to receive a first request message for broadcasting a first warning message of system information for a public warning system (PWS), receive a second request message for broadcasting a second warning message of the system information for the PWS, transmit, on the cell, repeated segments corresponding to a reference segment among first segments of the first warning message when the first warning message corresponds to a first ongoing warning message on a cell, transmit, on the cell, the first segments of the first warning message after transmitting the repeated segments, and transmit, on the cell, the second segments of the second warning message after both the repeated segments and the first segments of the first warning message have been transmitted.

[0007] Figure 1 shows a wireless communication system.

[0008] Figure 2a shows an example of function split according to a communication protocol.

[0009] Figure 2b shows an example of components of an electronic device.

[0010] Figure 3 shows an example of a resource structure in the time domain and frequency domain.

[0011] Figure 4 shows examples of channels in a communication standard.

[0012] Figure 5a shows an example of signaling for transmitting system information for a public warning system (PWS).

[0013] Figure 5b shows examples of system information for a public warning system (PWS).

[0014] Figure 6a shows an example of an alert request procedure in the F1 interface.

[0015] Figure 6b shows examples of warning messages, segments, and configuration parameters in the F1 interface.

[0016] Figures 7a and 7b illustrate examples of signaling for transmitting a single warning message.

[0017] Figures 8a and 8b illustrate examples of signaling for transmitting multiple warning messages.

[0018] Figures 9a and 9b illustrate examples of transmission of warning messages according to overlapping scheduling.

[0019] Figure 10 shows an example of transmission of warning messages according to non-overlapping scheduling.

[0020] Figure 11 shows an example of transmission of warning messages according to non-overlapping scheduling using a concurrent warning buffer.

[0021] Figure 12 shows an example of transmission of warning messages according to non-overlapping scheduling using repetition of warning messages.

[0022] Figure 13 shows an example of transmission of warning messages according to non-overlapping scheduling using segment repetition.

[0023] Figure 14 illustrates the operation of an electronic device for non-overlapping scheduling using a concurrent warning buffer.

[0024] Figure 15 illustrates the operation of an electronic device for non-overlapping scheduling using repetition of warning messages.

[0025] Figure 16 illustrates the operation of an electronic device for non-overlapping scheduling using segment repetition.

[0026] Figure 17 shows examples of non-overlapping scheduling.

[0027] Figure 18 illustrates an example of components of an electronic device for non-overlapping scheduling.

[0028] The terms used in this disclosure are used only to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by those of ordinary skill in the art described in this disclosure. Terms defined in general dictionaries among the terms used in this disclosure may be interpreted as having the same or similar meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure.

[0029] The various embodiments of the present disclosure described below illustrate a hardware-based approach as an example. However, since the various embodiments of the present disclosure include techniques utilizing both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.

[0030] In the following description, terms referring to signals (e.g., signal, information, message, signaling), terms referring to data types (e.g., list, set, subset), terms for operational states (e.g., step, operation, procedure), terms referring to data (e.g., packet, user stream, information, bit, symbol, codeword), terms referring to resources (e.g., symbol, slot, subframe, radio frame, subcarrier, resource element (RE), resource block (RB), bandwidth part (BWP), occasion), terms referring to channels, terms referring to network entities (e.g., node, network entity, entity, unit), terms referring to components of devices, etc. are examples for convenience of description. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used.

[0031] In the following description, terms referring to signals (e.g., signal, information, message, signaling), terms referring to resources (e.g., symbol, slot, subframe, radio frame, subcarrier, resource element (RE), resource block (RB), bandwidth part (BWP), occasion), terms for operational states (e.g., step, operation, procedure), terms referring to data (e.g., packet, user stream, information, bit, symbol, codeword), terms referring to channels, terms referring to network entities, terms referring to components of devices, etc. are examples for convenience of description. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used.

[0032] In addition, in the present disclosure, expressions such as "more than" or "less than" may be used to determine whether a specific condition is satisfied or fulfilled, but this is merely a description for expressing an example and does not exclude descriptions such as "more than" or "less than." A condition described as "more than" may be replaced with "more than," a condition described as "less than" may be replaced with "less than," and a condition described as "more than and less than" may be replaced with "more than and less than." In addition, hereinafter, "A" to "B" mean at least one of elements from A (including A) to B (including B). hereinafter, "C" and / or "D" mean at least one of "C" or "D," that is, including {"C", "D", "C" and "D"}.

[0033] Although the present disclosure describes various embodiments using terms used in some communication standards (e.g., 3rd Generation Partnership Project (3GPP), European Telecommunications Standards Institute (ETSI), extensible radio access network (xRAN), open-radio access network (O-RAN), etc.), these are merely examples for explanation. The various embodiments of the present disclosure can be easily modified and applied to other communication systems.

[0034] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0035] Figure 1 shows a wireless communication system.

[0036] Referring to FIG. 1, FIG. 1 illustrates a base station (110) and a terminal (120) as some of the nodes utilizing a wireless channel in a wireless communication system. Although FIG. 1 illustrates only one base station, the wireless communication system may further include other base stations identical or similar to the base station (110).

[0037] The base station (110) is a network infrastructure that provides wireless access to the terminal (120). The base station (110) has coverage defined based on the distance at which a signal can be transmitted. In addition to the base station, the base station (110) may be referred to as an 'access point (AP)', 'eNodeB (eNB)', '5th generation node', 'next generation nodeB (gNB)', 'wireless point', 'transmission / reception point (TRP)', or other terms having equivalent technical meanings.

[0038] The terminal (120) is a device used by a user and communicates with the base station (110) via a wireless channel. The link from the base station (110) to the terminal (120) is referred to as a downlink (DL), and the link from the terminal (120) to the base station (110) is referred to as an uplink (UL). In addition, although not shown in FIG. 1, the terminal (120) and another terminal may communicate with each other via a wireless channel. In this case, the link between the terminal (120) and another terminal (device-to-device link, D2D) is referred to as a sidelink, and the sidelink may be used interchangeably with the PC5 interface. In some other embodiments, the terminal (120) may be operated without the involvement of a user. In one embodiment, the terminal (120) is a device that performs machine type communication (MTC) and may not be carried by the user. Additionally, according to one embodiment, the terminal (120) may be an MTC UE or an NB (narrowband)-IoT (internet of things) device.

[0039] The terminal (120) may be referred to as a terminal, or other terms such as 'user equipment (UE),' 'customer premises equipment (CPE),' 'mobile station,' 'subscriber station,' 'remote terminal,' 'wireless terminal,' 'electronic device,' or 'user device,' or other terms having equivalent technical meanings.

[0040] The base station (110) and the terminal (120) can perform beamforming. The base station (110) and the terminal (120) can transmit and receive wireless signals in a relatively low frequency band (e.g., FR 1 (frequency range 1) of NR). In addition, the base station (110) and the terminal (120) can transmit and receive wireless signals in a relatively high frequency band (e.g., FR 2 (or, FR 2-1, FR 2-2, FR 2-3), FR 3 of NR), millimeter wave (mmWave) band (e.g., 28 GHz, 30 GHz, 38 GHz, 60 GHz)). To improve channel gain, the base station (110) and the terminal (120) can perform beamforming. Here, the beamforming can include transmission beamforming and reception beamforming. The base station (110) and the terminal (120) can impart directionality to the transmitted or received signal. To this end, the base station (110) and the terminal (120) can select serving beams through a beam search or beam management procedure. After the serving beams are selected, subsequent communication can be performed through resources that have a QCL relationship with the resource that transmitted the serving beams.

[0041] If large-scale characteristics of a channel carrying a symbol on a first antenna port can be inferred from a channel carrying a symbol on a second antenna port, the first antenna port and the second antenna port can be evaluated to have a QCL relationship. For example, the large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, average gain, average delay, and a spatial receiver parameter.

[0042] Although both the base station (110) and the terminal (120) are described as performing beamforming in FIG. 1, the embodiments of the present disclosure are not necessarily limited thereto. In some embodiments, the terminal may or may not perform beamforming. Furthermore, the base station may or may not perform beamforming. That is, either only one of the base station and the terminal may perform beamforming, or neither the base station nor the terminal may perform beamforming.

[0043] In the present disclosure, a beam refers to a spatial flow of a signal in a wireless channel, and is formed by one or more antennas (or antenna elements), and this forming process may be referred to as beamforming. Beamforming may include at least one of analog beamforming and digital beamforming (e.g., precoding). Reference signals transmitted based on beamforming may include, for example, a demodulation-reference signal (DM-RS), a channel state information-reference signal (CSI-RS), a synchronization signal / physical broadcast channel (SS / PBCH), and a sounding reference signal (SRS). In addition, as a configuration for each reference signal, an IE such as a CSI-RS resource or an SRS-resource may be used, and this configuration may include information associated with the beam. Information associated with a beam may mean whether the configuration (e.g., a CSI-RS resource) uses the same spatial domain filter as another configuration (e.g., another CSI-RS resource within the same CSI-RS resource set) or a different spatial domain filter, or whether it is quasi-co-located (QCL) with a reference signal, and if so, what type it is (e.g., QCL type A, B, C, D).

[0044] Figure 2a illustrates an example of function split according to a communication protocol. A base station (e.g., base station (110)) may operate as an eNB or gNB depending on the radio access technology (RAT) provided. For example, the base station may be referred to as an NG-RAN node. The base station may be implemented in a distributed deployment according to a centralized unit (CU) configured to perform functions of upper layers of an access network (e.g., packet data convergence protocol (PDCP), radio resource control (RRC)) and a distributed unit (DU) configured to perform functions of lower layers.

[0045] Referring to FIG. 2a, a CU (210) may be connected to one or more DUs (e.g., DU (220)) and may be responsible for functions of a higher layer than the DU. For example, the CU (210) may be responsible for functions of a radio resource control (RRC) layer (211) and a packet data convergence protocol (PDCP) layer (212). The CU (210) may transmit or receive messages to or from the DU (220) via an F1 interface. The DU (220) may be responsible for functions of a radio link control (RLC) layer (221), a media access control (MAC) layer (222), and a physical (PHY) layer (223).

[0046] The main functions of the RRC layer (212) may include some of the following functions.

[0047] - Broadcasting of AS (Access Stratum) and NAS-related system information

[0048] - Paging initiated by 5GC (5G Core) or NG-RAN (Next Generation-Radio Access network)

[0049] - Establishment, maintenance and release of RRC connection between UE and NG-RAN, including control over RLC, MAC and PHY, specifically:

[0050] - Adding, modifying, and disabling carrier aggregation

[0051] - Add, modify and disable dual connectivity between NR or E-UTRA and NR.

[0052] - Security features including key management;

[0053] - Setup, configuration, maintenance, and release of SRB (Signaling Radio Bearer) and DRB (Data Radio Bearer).

[0054] - Movement features including:

[0055] - Handover and context transfer;

[0056] - UE cell selection and reselection and cell selection and reselection control;

[0057] - Inter-RAT mobility.

[0058] - QoS (quality of service) management function;

[0059] - UE measurement reporting and reporting control;

[0060] - Detection and recovery of radio link failures

[0061] - Sending messages from / to UE to / from NAS.

[0062] The main functions of the PDCP layer (213) may include some of the following functions.

[0063] - Header compression and decompression (ROHC only)

[0064] - User data transfer function

[0065] - In-sequence delivery of upper layer PDUs

[0066] - Out-of-sequence delivery of upper layer PDUs

[0067] - PDCP PDU reordering for reception

[0068] - Duplicate detection of lower layer SDUs

[0069] - Retransmission function (Retransmission of PDCP SDUs)

[0070] - Encryption and decryption functions (Ciphering and deciphering)

[0071] - Timer-based SDU discard in uplink.

[0072] The main functions of the RLC layer (221) may include some of the following functions.

[0073] - Data transfer function (Transfer of upper layer PDUs)

[0074] - In-sequence delivery of upper layer PDUs

[0075] - Out-of-sequence delivery of upper layer PDUs

[0076] - ARQ function (Error Correction through ARQ)

[0077] - Concatenation, segmentation and reassembly of RLC SDUs

[0078] - Re-segmentation of RLC data PDUs

[0079] - Reordering of RLC data PDUs

[0080] - Duplicate detection function

[0081] - Protocol error detection

[0082] - RLC SDU discard function

[0083] - RLC re-establishment function

[0084] The MAC layer (222) can be connected to multiple RLC layer devices configured in one terminal, and the main functions of the MAC can include some of the following functions.

[0085] - Mapping function (Mapping between logical channels and transport channels)

[0086] - Multiplexing / demultiplexing of MAC SDUs

[0087] - Scheduling information reporting function

[0088] - HARQ function (Error correction through HARQ)

[0089] - Priority handling between logical channels of one UE

[0090] - Priority handling between UEs by means of dynamic scheduling

[0091] - MBMS service identification function

[0092] - Transport format selection function

[0093] - Padding function

[0094] DU (220) can perform an operation of channel coding and modulating upper layer data through a physical layer (223), converting it into an OFDM symbol and transmitting it through a wireless channel, or demodulating and channel decoding an OFDM symbol received through a wireless channel and transmitting it to a higher layer.

[0095] Although DU (220) is illustrated as being in charge of the physical layer (223) in FIG. 2A, embodiments of the present disclosure are not limited thereto. Depending on an implementation example, DU (220) may perform some functions (high PHY) of the physical layer (223), and an RU connected to DU (220) may be in charge of the remaining functions (low PHY) of the physical layer (223). In addition, as an example, DU (digital unit) may be included in DU (distributed unit) (220) depending on the implementation of distributed deployment of the base station. As a non-limiting example, DU (digital unit) may represent an entity including CU and DU (distributed unit) in a structure in which CU, DU (distributed unit), and RU are arranged in that order. Hereinafter, unless otherwise defined, the operations of CU (210) and DU (220) are described, but various embodiments of the present disclosure can be applied to both a base station arrangement including a CU or an arrangement in which a DU is directly connected to a core network (i.e., a base station in which the CU and DU are integrated into one entity (e.g., an NG-RAN node)).

[0096] Fig. 2b illustrates examples of components of an electronic device (e.g., a base station (110), a DU (220)). The configuration illustrated in Fig. 2b can be understood as a configuration of a base station (110) or a DU (220) that is a part of the base station (110). Terms such as "...unit" and "...unit" used hereinafter mean a unit that processes at least one function or operation, and this can be implemented by hardware, software, or a combination of hardware and software.

[0097] Referring to FIG. 2b, the DU (220) may include an RRC management unit (230) and a MAC scheduler (240). The RRC management unit (230) may be configured to manage messages of an RRC layer (e.g., an RRC layer (211)). The DU (220) may receive messages of the RRC layer (e.g., a system information (SI) message, a SIB1 message) from the CU (210). For example, the DU (220) may receive messages of the RRC layer from the CU (210) via an F1 interface. The RRC management unit (230) may provide messages of the RRC layer or information included in the messages to the MAC scheduler (240).

[0098] The MAC scheduler (240) can obtain the message of the RRC layer or information included in the message. The MAC scheduler (240) can schedule the message of the RRC layer. For example, the MAC scheduler (240) can determine which SI message to transmit in a specific section according to a specified period (e.g., the period of the SI message). The MAC scheduler (240) can schedule other messages (e.g., SI messages) according to information in the message of the RRC layer (e.g., scheduling information of SIBs).

[0099] Figure 3 illustrates an example of a resource structure in the time and frequency domains. Figure 3 illustrates the basic structure of the time-frequency domain, which is a radio resource domain in which data or control channels are transmitted in the downlink or uplink.

[0100] Referring to Figure 3, the horizontal axis represents the time domain and the vertical axis represents the frequency domain. The minimum transmission unit in the time domain is an OFDM (orthogonal frequency division multiplexing) symbol, N symbA set of OFDM symbols (302) constitutes one slot (306). The length of a subframe is defined as 1 ms, and the length of a radio frame (314) is defined as 10 ms. The minimum transmission unit in the frequency domain may be a subcarrier.

[0101] The basic unit of resources in the time-frequency domain is a resource element (RE) (312), which can be represented by an OFDM symbol index and a subcarrier index. A resource block may include multiple resource elements. In the LTE system, a resource block (RB) (or physical resource block (PRB)) is N in the time domain. symb N consecutive OFDM symbols and frequency domain SC RB are defined as N consecutive subcarriers. In the NR system, a resource block (RB) (308) is defined as N in the frequency domain. SC RB can be defined as N consecutive subcarriers (310). In a wireless access network, the bandwidth constituting the resource grid is N RB DL Dog or N RB UL It may include RBs (304) of N RB DL represents the number of RBs corresponding to the downlink bandwidth, and N RB UL represents the number of RBs corresponding to the uplink bandwidth. One RB (308) is N on the frequency axis. SC RB It contains REs (312). In general, the minimum transmission unit of data is RB and the number of subcarriers is N. SC RB=12. The frequency domain may include common resource blocks (CRBs). Physical resource blocks (PRBs) may be defined in the bandwidth part (BWP) of the frequency domain. The CRB and PRB numbers may be determined based on the subcarrier spacing. The data rate may increase in proportion to the number of RBs scheduled to the terminal.

[0102] In the NR system, in the case of a frequency division duplex (FDD) system that operates the downlink and uplink by frequency division, the downlink transmission bandwidth and the uplink transmission bandwidth may be different. The channel bandwidth represents the radio frequency (RF) bandwidth corresponding to the system transmission bandwidth. [Table 1] shows part of the correspondence between the system transmission bandwidth, subcarrier spacing (SCS), and channel bandwidth defined in the NR system in a frequency band lower than x GHz (e.g., frequency range (FR) 1 (310 MHz to 7125 MHz)). And [Table 2] shows part of the correspondence between the transmission bandwidth, subcarrier spacing, and channel bandwidth defined in the NR system in a frequency band higher than y GHz (e.g., FR2 (24250 MHz - 52600 MHz) or FR2-2 (52600 MHz to 71000 MHz)). For example, an NR system with a 100 MHz channel bandwidth and a 30 kHz subcarrier spacing has a transmission bandwidth of 273 RBs. In [Table 1] and [Table 2], N / A may be a bandwidth-subcarrier combination not supported by the NR system.

[0103] Channel bandwidth [MHz] SCS 5 10 20 50 80 100 Transmission bandwidth configuration N RB15kHz2552106207N / AN / A30kHz11245113321727360kHzN / A112465107135

[0104] Channel bandwidth [MHz] SCS50100200400 Transmission bandwidth configuration N RB 60kHz66132264N / A120kHz3266132264

[0105] Figure 4 illustrates examples of channels in a communication standard. The channels may include a physical channel (410), a transport channel (420), and a logical channel (430), depending on the layers defined in the communication standard.

[0106] Referring to FIG. 4, a physical channel (410) may provide functions (e.g., channel coding, HARQ processing, modulation, multi-antenna processing, resource mapping) necessary for generating physical signals at the physical layer. At the physical layer, physical signals are modulated using OFDM and may be transmitted in a wireless environment via time-frequency resources (e.g., resources of the resource grid of FIG. 3).

[0107] In downlink transmission, a physical channel (410) may include at least one of a physical broadcast channel (PBCH), a physical downlink shared channel (PDSCH), or a physical downlink control channel (PDCCH). The PDCCH may be used to carry downlink control information (DCI). Generally, downlink data refers to symbols transmitted through the PDSCH, and a downlink control signal may include symbols transmitted through the PDCCH. In addition, in the downlink, in addition to the channels illustrated in FIG. 4, a synchronization signal (e.g., a primary synchronization signal (PSS), a secondary synchronization signal (SSS)) and an SS / PBCH block including a broadcast signal (e.g., a PBCH)) may be transmitted for synchronization. In addition, in the downlink, a channel state information-reference signal (CSI-RS) for obtaining measurement or channel information, a demodulation reference signal (DMRS) for channel estimation and demodulation, and a phase tracking reference signal (PTRS) may be transmitted in the downlink.

[0108] In uplink transmission, the physical channel (410) may include at least one of a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), or a physical random access channel (PRACH). The PUSCH or PUCCH may be used to carry uplink control information (UCI). Generally, uplink data refers to symbols transmitted through the PUSCH, and the uplink control signal may include symbols corresponding to the UCI. For example, the UCI may include at least one of a scheduling request (SR), a hybrid automatic request (HARQ)-acknowledge (ACK) bit(s), or channel state information (CSI). In addition, in the uplink, in addition to the channels illustrated in FIG. 4, a DMRS and a PTRS for channel estimation and demodulation may be transmitted in the downlink for channel estimation.

[0109] The transmission channel (420) connects the physical layer and the medium access channel (MAC) layer located at an upper level of the physical layer, and can be classified according to how data is transmitted through the wireless interface. In the downlink, the transmission channel (420) may include at least one of a paging channel (PCH) for paging, a broadcast channel (BCH) for broadcasting system information, or a downlink shared channel (DL-SCH) for transmitting downlink data. In the uplink, the transmission channel (420) may include at least one of a random access channel (RACH) for transmitting a random access preamble or an uplink shared channel (UL-SCH) for transmitting downlink data.

[0110] The logical channel (430) is located above the transport channel and is mapped to the transport channel (420). The logical channel (430) can be divided into a control channel for transmitting control region information and a traffic channel for transmitting user region information. The control channel of the logical channel (430) can include at least one of a paging control channel (PCCH), a broadcast control channel (BCCH), a common control channel (CCCH), or a dedicated control channel (DCCH). The traffic channel of the logical channel (430) can include a dedicated traffic channel (DTCH).

[0111] Figure 5a illustrates an example of signaling for transmitting system information for a public warning system (PWS). 3GPP defines public warning systems (PWS).

[0112] NRs connected to 5GC can support PWS through system information broadcasting. The base station (110) or DU (220) can not only schedule and broadcast warning messages, but also paging UEs to indicate that a warning message is being broadcast. For example, PWS can be classified as follows:

[0113] - ETWS (Earthquake and Tsunami Warning System): ETWS is a public warning system developed to meet regulatory requirements for warning notifications related to earthquake and / or tsunami events. ETWS warning notifications can be either primary notifications (simple notifications) (e.g., SIB 6 in 3GPP NR) or secondary notifications (providing detailed information) (e.g., SIB 7 in 3GPP NR).

[0114] - CMAS (Commercial Mobile Alert System): CMAS is a public alert system developed to deliver multiple concurrent alerts. CMAS alerts can be provided by predefined system information (e.g., SIB 8 of 3GPP NR).

[0115] Different SIBs can be defined for ETWS 1st notification, ETWS 2nd notification, and CMAS notification. Paging is used to notify the UE about ETWS indications and CMAS indications. The UE can monitor ETWS indications and / or CMAS indications in its own paging opportunities for RRC_IDLE and RRC_INACTIVE. The UE can monitor ETWS indications and / or CMAS indications in all paging situations for RRC_CONNECTED. The paging can trigger the acquisition of system information, where the acquisition of system information is not delayed until the next modification period.

[0116] Referring to FIG. 5A, in operation (501), the CBE (510) may transmit an emergency broadcast request message to the CBCF / PWS-IWF (520). In operation (503), the CBCF / PWS-IWF (520) may transmit an alert request message to the AMF (530). In operation (505), the AMF (530) may transmit an alert response message to the CBCF / PWS-IWF (520). In operation (507), the CBCF / PWS-IWF (520) may transmit an emergency broadcast response message to the CBE (510).

[0117] In operation (511), the AMF (530) may transmit a warning request message to the base station (110) (e.g., an NG-RAN node). For example, the AMF (530) may transmit the warning request message to the base station (110) via the N2 interface. The warning request message may be a 'WRITE-REPLACE WARNING REQUEST' message. The warning request message may be used to request the start of broadcasting or overwriting of the warning message. For example, the warning request message may have the following format.

[0118] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeM9.3.1.1YESrejectMessage IdentifierM9.3.1.35YESrejectSerial NumberM9.3.1.36YESrejectWarning Area ListO9.3.1.37YESignoreRepetition PeriodM9.3.1.49YESrejectNumber of Broadcasts RequestedM9.3.1.38YESrejectWarning TypeO9.3.1.39YESignoreWarning Security InformationOOCTET STRING (SIZE(50))This IE is not used in the specification. If received, the IE is ignored.YESignoreData Coding SchemeO9.3.1.41YESignoreWarning Message ContentsO9.3.1.42YESignoreConcurrent Warning Message IndicatorO9.3.1.46YESrejectWarning Area CoordinatesO9.3.1.112YESignore

[0119] 'Message Type' indicates the message type of the warning request message. 'Message Identifier' indicates the identifier of the warning message. 'Serial Number' indicates a message specified from the source and type indicated by the 'Message Identifier'. 'Warning Area List' indicates a list of areas in which the warning message needs to be broadcast (or canceled). 'Number of Broadcasts Requested' indicates the number of times the warning message will be broadcast. 'Warning Type' indicates the type of disaster. 'Message Type' indicates the message type of the warning message. 'Data Coding Scheme' indicates the alphabet or coding applied to the characters of the warning message. 'Data Coding Scheme' indicates the alphabet or coding applied to the characters of the warning message. 'Warning Message Contents' indicates user information (e.g., warning contents of the warning message). 'Concurrent Warning Message Indicator' indicates that the received warning message is a new message scheduled to be broadcast simultaneously with another ongoing warning message broadcast. 'Warning Area Coordinates' indicates the coordinates of the warning area affected by the warning message.

[0120] In operation (513), the base station (110) may transmit an alert response message to the AMF (530).

[0121] In operation (521), the base station (110) may broadcast a system information block (SIB) 1 message. The SIB 1 message may include scheduling information of one or more SI messages. Each SI message of the one or more SI messages may include at least one SIB different from SIB 1. For example, the SIB 1 message may include scheduling information of system information for PWS. Since the base station (110) has received an alert request message from the AMF (530), it may trigger broadcasting of an alert message on the cell. Since the alert message includes system information (e.g., SIB 6, SIB 7, SIB 8), the base station (110) may broadcast the SIB 1 message to inform a terminal (e.g., terminal 120) on the cell of scheduling. The SIB 1 message may be broadcasted through BCCH and PDSCH. The specific format for the above SIB 1 message is described in detail through FIG. 5b.

[0122] In operation (531), the base station (110) may transmit a notification message. The notification message may be used to indicate in advance that system information for the PWS is provided. In one embodiment, the notification message may be a short message. The short message may be transmitted on the PDCCH via a paging-radio network temporary identity (P-RNTI). A detailed description of the short message is provided with reference to FIG. 5B.

[0123] In operation (533), the base station (110) may broadcast an alert message. The alert message may include system information for PWS. For example, the alert message may be SIB 6 for the first notification of ETWS. For example, the alert message may be SIB 7 for the second notification of ETWS. For example, the alert message may be SIB 8 for the notification of CMAS. The alert message including the system information for PWS may be broadcast via BCCH and PDSCH. Specific information (e.g., information element (IE)) included in the system information for PWS is described in detail with reference to FIG. 5b.

[0124] Figure 5b shows examples of system information for a public warning system (PWS).

[0125] Referring to FIG. 5b, the SIB 1 message (571) may include scheduling information for one or more SI messages. For example, the scheduling information may have the following format.

[0126] -SI-SchedulingInfoThe IESI-SchedulingInfocontains information needed for acquisition of SI messages.SI-SchedulingInfoinformation element-- ASN1START-- TAG-SI-SCHEDULINGINFO-STARTSI-SchedulingInfo ::= SEQUENCE {schedulingInfoList SEQUENCE (SIZE (1..maxSI-Message)) OF SchedulingInfo,si-WindowLength ENUMERATED {s5, s10, s20, s40, s80, s160, s320, s640, s1280},si-RequestConfig SI-RequestConfig OPTIONAL, -- Cond MSG-1si-RequestConfigSUL SI-RequestConfig OPTIONAL, -- Cond SUL-MSG-1systemInformationAreaID BIT STRING (SIZE (24)) OPTIONAL, -- Need R...}SchedulingInfo ::= SEQUENCE {si-BroadcastStatus ENUMERATED {broadcasting, notBroadcasting},si-Periodicity ENUMERATED {rf8, rf16, rf32, rf64, rf128, rf256, rf512},sib-MappingInfo SIB-Mapping}SIB-Mapping ::= SEQUENCE (SIZE (1..maxSIB)) OF SIB-TypeInfoSIB-TypeInfo ::= SEQUENCE {type ENUMERATED {sibType2, sibType3, sibType4, sibType5, sibType6, sibType7, sibType8, sibType9,sibType10-v1610, sibType11-v1610, sibType12-v1610, sibType13-v1610, sibType14-v1610,spare3, spare2, spare1,...},valueTag INTEGER (0..31) OPTIONAL, -- Cond SIB-TYPEareaScope ENUMERATED {true} OPTIONAL -- Need S}-- TAG-SI-SCHEDULINGINFO-STOP-- ASN1STOP.

[0127] The above scheduling information is configured for each SI message, and the scheduling information may include a period for each SI message (e.g., 'si-Periodicity' IE) and mapping information (e.g., 'sib-MappingInfo' IE). The mapping information may include one or more SIBs. The mapping information indicates the type of the corresponding SIB, and the type may be SIB 6, SIB 7, and / or SIB 8.

[0128] The short message (581) is provided through the field of the DCI (downlink control information) of the PDCCH, and the bits of the field (e.g., 3 bits) can represent the following information. For example, the bits can represent 2.

[0129] BitShort Message1systemInfoModificationIf set to 1: indication of a BCCH modification other than SIB6, SIB7 and SIB8.2etwsAndCmasIndicationIf set to 1: indication of an ETWS primary notification and / or an ETWS secondary notification and / or a CMAS notification.3stopPagingMonitoringThis bit can be used for only operation with shared spectrum channel access and if nrofPDCCH-MonitoringOccasionPerSSB-InPO is present.If set to 1: indication that the UE may stop monitoring PDCCH occasion(s) for paging in this Paging Occasion as specified in TS 38.304

[0020] , clause 7.1.4 - 8Not used in this release of the specification, and shall be ignored by UE if received.

[0130] SIB 6 (583a) may include an ETWS primary notification. SIB 6 (583a) may include a message identifier (e.g., 'messageIdentifier' IE), a serial number (e.g., 'serialNumber' IE), and a warning type (e.g., 'warningType' IE). For a description of each piece of information, the IEs in Table 3 may be referenced. In the present disclosure, the same warning message means that the value of the message identifier and the value of the serial number are the same.

[0131] SIB 7 (583a) may include ETWS secondary notification. SIB 7 (583b) may include a message identifier (e.g., 'messageIdentifier' IE), a serial number (e.g., 'serialNumber' IE), and a coding scheme (e.g., 'dataCodingScheme'). For a description of each piece of information, reference may be made to the IEs in Table 3. SIB 7 (583b) may include a segment of the warning message (e.g., 'warningMessageSegment'), a segment type indicating whether the segment is the last segment (e.g., 'warningMessageSegmentType' IE), and a segment number (hereinafter, referred to as a segment number) (e.g., 'warningMessageSegmentNumber' IE). If the payload size of the warning message exceeds the maximum payload size, the warning message may be divided into multiple segments and transmitted. One segment of the above warning message may be transmitted via one SIB 7 (583b).

[0132] SIB 8 (583c) may include a CMAS notification. SIB 8 (583c) may include a message identifier (e.g., 'messageIdentifier' IE), a serial number (e.g., 'serialNumber' IE), and a coding scheme (e.g., 'dataCodingScheme'). For a description of each piece of information, reference may be made to the IEs in Table 3. SIB 7 (583b) may include a segment of the warning message (e.g., 'warningMessageSegment'), a segment type indicating whether the segment is the last segment (e.g., 'warningMessageSegmentType' IE), a number of the segment (hereinafter, referred to as a segment number) (e.g., 'warningMessageSegmentNumber' IE), and a segment of a geographical area in which the segment is valid (e.g., 'warningAreaCoordinatesSegment' IE). If the payload size of the warning message exceeds the maximum payload size, the warning message may be divided into multiple segments and transmitted. One segment of the warning message may be transmitted through one SIB 8 (583c). For example, if the maximum payload size available for each MCS (modulation and coding scheme) of the warning message (e.g., SIB 8 (583c)) is greater than the maximum payload size, the warning message may be divided into segments within the maximum payload size. Depending on how the segments are transmitted, the delay in receiving the warning message at the terminal (120) may vary.

[0133] Fig. 6a illustrates an example of an alert request procedure in the F1 interface. The base station (110) of Fig. 5a may be replaced with a CU (210) and a DU (220). The CU (210) may receive an alert request message from the AMF (530). The DU (220) may transmit a SIB 1 message (e.g., SIB message (571)), a notification message (e.g., short message (581)), and / or an alert message (e.g., SIB 6 (583a), SIB 7 (583b), SIB 8 (583c)) to the terminal (120).

[0134] Referring to FIG. 6A, in operation (601), the CU (210) may transmit a warning request message (e.g., a 'WRITE-REPLACE WARNING REQUEST' message) to the DU (220). The CU (210) may initiate a procedure by transmitting the warning request message to the DU (220). The DU (220) that receives the warning request message may prioritize resources for processing the warning message.

[0135] In operation (603), the DU (220) may transmit a warning response message (e.g., a 'WRITE-REPLACE WARNING RESPONSE' message) to the CU (210). By transmitting the warning response message to the CU (210), the DU (220) may provide confirmation of the warning request message. As a non-limiting example, the DU (220) may include information in the warning response message indicating that the UE requires transmission of dedicated system information for a UE that cannot receive system information through broadcast.

[0136] The above warning request message may have the following format, for example:

[0137] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeM9.3.1.1YESrejectTransaction IDM9.3.1.23YESrejectPWS System InformationM9.3.1.58This IE includes the system information for public warning, as defined in TS 38.331 [8].YESrejectRepetition PeriodM9.3.1.59YESrejectNumber of Broadcasts RequestedM9.3.1.60YESrejectCell To Be Broadcast List0..1YESreject>Cell to Be Broadcast Item IEs1.. <maxcellingnbdu>EACHreject>>NR CGIM9.3.1.12-

[0138] 'Message Type' indicates the message type of the warning request message of operation (601). 'Transaction ID' indicates an identifier for identifying the procedure of the warning request message. 'PWS System Information' indicates system information for PWS. The specific format of the system information is described in Table 6 below. 'Repetition Period' indicates the cycle of the warning message to be broadcast. For example, the cycle may be 1 second or more or 2 seconds or more. 17 -Can be specified for less than 1 second. 'Number of Broadcasts Requested' indicates the number of times the above warning message will be broadcast. 'Cell To Be Broadcast List' indicates information about the cells that require broadcasting, and the cells can be specified via a global identifier (e.g., cell global identity (CGI)).

[0139] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalitySIB typeMINTEGER (6..8, ...)Indicates a certain SIB block for public warning message, e.g. 6 means sibType6, 7 for sibType7, etc.-SIB messageMOCTET STRINGSIB message for public warning, as defined in TS 38.331 [8].-Notification InformationOYESignore>Message IdentifierM9.3.1.81->Serial NumberM9.3.1.82-Additional SIB Message ListO9.3.1.86Additional SIB messages containing different segments of a public warning message if segmentation is applied, as defined in TS 38.331 [8].Yesreject

[0140] 'SIB type' indicates the type of SIB, and represents SIB 6 (583a), SIB 7 (583b), or SIB 8 (583c). 'SIB message' indicates an alert message used for public alert. 'Message Identifier' of 'Notification Information' indicates an identifier of the alert message. 'Serial Number' of 'Notification Information' indicates a message specified from the source and type indicated by 'Message Identifier'. 'Additional SIB Message List' IE indicates the remaining segment(s) other than one segment of the alert message indicated by 'SIB message' when the alert message is divided into multiple segments due to the size of the message. The remaining segment(s) may be referred to as an additional SIB message. The additional SIB message may be associated with the same message identifier and serial number as one segment of the alert message.

[0141] Figure 6b illustrates examples of warning messages, segments, and configuration parameters in the F1 interface. Building on the description in Figure 6a, Figure 6b illustrates specific examples of warning messages.

[0142] Referring to FIG. 6b, CU (210) may transmit an alert request message to DU (220). The alert request message may include a message identifier (e.g., message ID = 4370) and a serial number (e.g., Serial Number = 23568). The message identifier and the serial number may specify one alert message. In the present disclosure, the first alert message and the second alert message are the same alert message when the message identifier of the first alert message is the same as the message identifier of the second alert message, and the serial number of the first alert message is the same as the serial number of the second alert message. The alert request message may be used to set a cycle (e.g., 'repetition period' IE = 60) of the alert message to be broadcast to DU (220). For example, DU (220) may repeatedly transmit the alert request message every 60 seconds. The above warning request message indicates the number of times the warning message will be broadcast (e.g., 'Number of Broadcasts Requested' IE=2). For example, DU (220) may broadcast the warning message twice.

[0143] Let's assume that the above warning message is divided into four segments (e.g., a first segment, a second segment, a third segment, and a fourth segment). The DU (220) can transmit the four segments twice. The DU (220) can transmit a total of eight segments. The DU (220) can transmit the segments in the following order: a first segment (#1), a second segment (#1), a third segment (#1), and a fourth segment (#1), a first segment (#2), a second segment (#2), a third segment (#2), and a fourth segment (#2). The interval between the first segment (#1) and the first segment (#2) can be 60 seconds. The UE (e.g., terminal (120)) can receive the four segments twice. The UE can receive a total of eight segments. The UE can receive the segments in the following order: first segment (#1), second segment (#1), third segment (#1), and fourth segment (#1), first segment (#2), second segment (#2), third segment (#2), and fourth segment (#2).

[0144] Figures 7a and 7b illustrate examples of signaling for transmitting a single warning message. Like reference numbers may refer to like descriptions. Each MP represents a modification period.

[0145] Referring to FIG. 7A, in operation (511), the AMF (530) may transmit a warning request message to the base station (110) (e.g., an NG-RAN node). For example, the AMF (530) may transmit the warning request message to the base station (110) via the N2 interface. The warning request message may be a 'WRITE-REPLACE WARNING REQUEST' message. For the warning request message, Table 3 may be referred to. In operation (513), the base station (110) may transmit a warning response message to the AMF (530). In operation (601), the CU (210) may transmit a warning message (e.g., a 'WRITE-REPLACE WARNING REQUEST' message) to the DU (220). For the warning request message, Table 6 may be referred to. In operation (603), the DU (220) may transmit a warning response message (e.g., a 'WRITE-REPLACE WARNING RESPONSE' message) to the CU (210).

[0146] In operation (701), the DU (220) (e.g., the RRC management unit (230)) may generate scheduling information for a warning message. The RRC management unit (230) may provide the scheduling information to the MAC scheduler (240).

[0147] In operation (703), the DU (220) (e.g., RRC management unit (230)) may provide the scheduling information to the MAC scheduler (240) through a request message. The request message is transmitted within the DU (220) and may include all segments of the warning message.

[0148] In operation (720), DU (220) (e.g., MAC scheduler (240)) may transmit an alert message and a SIB 1 message. DU (220) may broadcast the alert message and the SIB 1 message on the cell. MAC scheduler (240) may schedule segments of the alert message. MAC scheduler (240) may generate an SIB 1 message including scheduling information for the segments of the alert message. MAC scheduler (240) may control the segments of the alert message and the SIB 1 message to be broadcast. Broadcasting of the alert message and the SIB 1 message is described in detail with reference to FIG. 7B.

[0149] In operation (731), the DU (220) (e.g., MAC scheduler (240)) may provide a response message to the RRC management unit (230).

[0150] In operation (741), the DU (220) (e.g., MAC scheduler (240)) may generate scheduling information. For example, if transmission for an alert message has been performed, the scheduling information may not include scheduling information for system information (e.g., SIB 8) related to the alert message.

[0151] In operation (743), the DU (220) (e.g., MAC scheduler (240)) may provide a request message. Since the transmission of the warning message has been completed, the request message may not contain information about any event.

[0152] In operation (745), DU (220) (e.g., MAC scheduler (240)) may transmit a SIB 1 message.

[0153] Referring to FIG. 7B, the SIB 1 message may be transmitted periodically. For example, at the first point (771), the SIB 1 message may be transmitted due to a system modification. The DU (220) may receive an alert request message (e.g., the alert request message of operation (601)). The RRC management unit (230) of the DU (220) may reconfigure the scheduling information of SIB1 in response to the alert request message. For example, the alert request message may indicate a CMAS notification. The RRC management unit (230) of the DU (220) may obtain an alert message (e.g., an SI message including SIB 8) included in the alert request message. The RRC management unit (230) may modify the SIB 1 message to include scheduling information for the alert message. The RRC management unit (230) may provide the modified SIB 1 message and the warning message to the MAC scheduler (240). The RRC management unit (230) may repeatedly provide the modified SIB 1 message and the warning message during a modification period (750). The RRC management unit (230) may transmit a short message (e.g., short message (581)) to indicate CMAS notification through the MAC scheduler (240). For example, the short message (581) may be transmitted in a paging manner during the modification period (750).

[0154] The MAC scheduler (240) may broadcast the modified SIB 1 message and the warning message on the cell during a designated period (760) (e.g., a period corresponding to twice the modification period (750), i.e., 2MP). Unlike other system information, system information for PWS may be obtained from the current modification period, not the next modification period. Therefore, warning messages may be repeatedly transmitted during a time interval corresponding to two modification periods. For example, the designated transmission period (760) may be twice the modification period (750). At a second point (773), the MAC scheduler (240) may schedule the modified SIB 1 message and the warning message together. After the warning messages are broadcast during the designated period (750), the MAC scheduler (240) may modify the SIB 1 message again. At a third point (775), the SIB 1 message may be transmitted due to system modification.

[0155] Figures 8a and 8b illustrate examples of signaling for transmitting multiple warning messages. Like reference numerals may indicate like descriptions. The multiple warning messages may include a first warning message and a second warning message. Each MP represents a modification period.

[0156] Referring to FIG. 8A, in operation (511), the AMF (530) may transmit a first warning request message (e.g., WARNING REQUEST #1) to the base station (110) (e.g., an NG-RAN node). For example, the AMF (530) may transmit the first warning request message to the base station (110) via the N2 interface. The first warning request message may be a 'WRITE-REPLACE WARNING REQUEST' message. For the first warning request message, Table 3 may be referred to. In operation (513), the base station (110) may transmit a first warning response message (e.g., WARNING RESPONSE #1) to the AMF (530). In operation (601), the CU (210) may transmit a first warning message (e.g., 'WRITE-REPLACE WARNING REQUEST #1' message) to the DU (220). For the first warning request message, Table 6 may be referred to. In operation (603), the DU (220) may transmit a first warning response message (e.g., a 'WRITE-REPLACE WARNING RESPONSE #1' message) to the CU (210). The first warning request message may include the first warning message.

[0157] In operation (703), the DU (220) (e.g., RRC management unit (230)) may provide the scheduling information to the MAC scheduler (240) through a request message (#1). The request message is transmitted within the DU (220) and may include all of the first segments of the first warning message.

[0158] In operation (720), the DU (220) (e.g., MAC scheduler (240)) may transmit the first warning message and the SIB 1 message. The broadcasting of the first warning message and the SIB 1 message is described in detail through FIG. 8b.

[0159] In operation (803), the AMF (530) may transmit a second warning request message (e.g., WARNING REQUEST #2) to the base station (110) (e.g., an NG-RAN node). For example, the AMF (530) may transmit the second warning request message to the base station (110) via the N2 interface. The second warning request message may be a 'WRITE-REPLACE WARNING REQUEST' message. For the second warning request message, Table 3 may be referred to. In operation (805), the base station (110) may transmit a second warning response message (e.g., WARNING RESPONSE #2) to the AMF (530). In operation (813), the CU (210) may transmit a second warning message (e.g., 'WRITE-REPLACE WARNING REQUEST #2' message) to the DU (220). For the second warning request message, Table 6 may be referred to. In operation (815), the DU (220) may transmit a second warning response message (e.g., a 'WRITE-REPLACE WARNING RESPONSE #2' message) to the CU (210). The second warning request message may include a second warning message.

[0160] In operation (831), the DU (220) (e.g., RRC management unit (230)) may provide the scheduling information to the MAC scheduler (240) through a request message (#1, #2). The request message is transmitted within the DU (220) and may include both the first segments of the first warning message and the second segments of the second warning message.

[0161] In operation (850), the DU (220) (e.g., the MAC scheduler (240)) may transmit the first warning message, the second warning message, and the SIB 1 message. The SIB 1 message may include scheduling information for not only the first warning message but also the second warning message. The broadcasting of the first warning message, the second warning message, and the SIB 1 message is described in detail through FIG. 8B.

[0162] In operation (731), the DU (220) (e.g., MAC scheduler (240)) may provide a response message (#1) to the RRC management unit (230). The response message may indicate that the broadcast of the first warning message is completed.

[0163] In operation (833), the DU (220) (e.g., RRC management unit (230)) may provide the scheduling information to the MAC scheduler (240) in a request message (#2). The request message may include the second segments of the second warning message.

[0164] In operation (860), the DU (220) (e.g., the MAC scheduler (240)) may transmit the second warning message and the SIB 1 message. The SIB 1 message may include scheduling information for the second warning message. Meanwhile, since the transmission of the first warning message has been completed, the SIB 1 message may not include scheduling information for the first warning message. The broadcast of the second warning message and the SIB 1 message is described in detail through FIG. 8b.

[0165] In operation (835), the DU (220) (e.g., the MAC scheduler (240)) may provide a response message (#2) to the RRC management unit (230). The response message may indicate that the broadcast of the second warning message is completed.

[0166] In operation (837), the DU (220) (e.g., MAC scheduler (240)) may provide a request message. Since the transmission of the first warning message and the second warning message has been completed, the request message may not include information about any event.

[0167] In operation (845), DU (220) (e.g., MAC scheduler (240)) may transmit a SIB 1 message.

[0168] Referring to FIG. 8B, the SIB 1 message may be transmitted periodically. The DU (220) (e.g., the RRC management unit (230)) may receive a first alert request message. The first alert request message may include segments of the first alert message (861). For example, the alert request message may indicate a CMAS notification. The RRC management unit (230) may modify the SIB 1 message to include scheduling information for the alert message. The RRC management unit (230) may provide the modified SIB 1 message and the first alert message (861) (or the first segments of the first alert message (861)) to the MAC scheduler (240). The RRC management unit (230) may repeatedly provide the modified SIB 1 message and the first alert message (861) during a modification period (871). The RRC management unit (230) may provide a short message (e.g., short message (581)) to indicate CMAS notification. The MAC scheduler (240) may be configured to broadcast the modified SIB 1 message and the first alert message (861) on the cell during the first transmission period (881). Unlike other system information, system information for PWS may be obtained from the current modification period, not the next modification period. Accordingly, alert messages associated with the first alert message (861) may be repeatedly transmitted during a time interval corresponding to two modification periods. For example, the first transmission period (881) may be twice the duration of the modification period (871).

[0169] The DU (220) (e.g., the RRC management unit (230)) may receive a second alert request message. The second alert request message may include segments of the second alert message (862). The RRC management unit (230) may repeatedly provide the modified SIB 1 message and the second alert message during a modification period (872). The RRC management unit (230) may provide a short message (e.g., short message (582)) to indicate CMAS notification. The MAC scheduler (240) may be configured to broadcast the modified SIB 1 message and the second alert message (862) on the cell during a second transmission period (882). Similar to the first alert message (861), alert messages associated with the second alert message (862) may be repeatedly transmitted during a time interval corresponding to two modification periods. For example, the second transmission period (882) may be twice the modification period (872).

[0170] Depending on the transmission period of the MAC scheduler (240) (e.g., the first transmission period (881), the second transmission period (882)), various system information may be broadcast. For example, during the first section (891) of the first transmission period (881), an SIB 1 message including scheduling information for the first alert message (861) and the first alert message (861) may be broadcast. The SIB 1 message may include related parameters of SIB 1 (e.g., access-related information, cell selection-related information). The SIB 1 message may include scheduling information of other system information. For example, the SIB 1 message may include scheduling information of SIB8 for the first alert message (861). The L3 layer management module (e.g., RRC management unit (230)) can transmit warning-related system information (891a) (WarningSiReq) (e.g., SIB1 message and first warning message (861)) to the L2 layer management module (e.g., MAC scheduler (240)).

[0171] For example, during a second period (892) within a time interval where a first transmission period (881) and a second transmission period (882) overlap, an SIB1 message including scheduling information for a first alert message (861) and a second alert message (862), a first alert message (861), and a second alert message (862) may be broadcast. The SIB 1 message may include relevant parameters of SIB 1 (e.g., access-related information, cell selection-related information). The SIB 1 message may include scheduling information of other system information. For example, the SIB 1 message may include scheduling information of SIB8 for the first alert message (861) and scheduling information of SIB8 for the second alert message (862). An L3 layer management module (e.g., RRC management unit (230)) may provide warning-related system information (892a) (WarningSiReq) (e.g., SIB1 message, first warning message (861), and second warning message (862)) to an L2 layer management module (e.g., MAC scheduler (240)).

[0172] For example, during the third period (893) of the second transmission period (882), a SIB1 message including scheduling information for a second warning message (862) and a second warning message (862) may be broadcast. The SIB 1 message may include relevant parameters of SIB 1 (e.g., access-related information, cell selection-related information). The SIB 1 message may include scheduling information of other system information. For example, the SIB 1 message may include scheduling information of SIB8 for the second warning message (862). An L3 layer management module (e.g., RRC management unit (230)) may provide warning-related system information (893a) (WarningSiReq) (e.g., SIB1 message and second warning message (862)) to an L2 layer management module (e.g., MAC scheduler (240)). Meanwhile, an ACK (891b) (WarningSiReq_ACK) for the first warning message (861) broadcast during the first transmission period (881) corresponding to about 2 MP may be provided from an L2 layer management module (e.g., MAC scheduler (240)) to an L3 layer management module (e.g., RRC management unit (230)).

[0173] For example, during the fourth segment (894), a SIB1 message may be broadcast. The SIB 1 message may include relevant parameters of SIB 1 (e.g., access-related information, cell selection-related information). At that point, the SIB 1 message may not include scheduling information of other system information. For example, the SIB 1 message may include scheduling information of SIB8 for the second warning message (862). The L3 layer management module (e.g., RRC management unit (230)) may provide system information (894a) (WarningSiReq) (e.g., SIB1 message) to the L2 layer management module (e.g., MAC scheduler (240)). Meanwhile, an ACK (892b) (WarningSiReq_ACK) for a second warning message (862) broadcast during a second transmission period (882) corresponding to approximately 2 MP may be provided from an L2 layer management module (e.g., MAC scheduler (240)) to an L3 layer management module (e.g., RRC management unit (230)).

[0174] When the base station (110) (or DU (220)) receives a warning request message, if there is no warning procedure in progress for the corresponding warning area, it may be configured to broadcast a warning message of the received warning request message. If there is a warning message in progress in the warning area, the warning message in progress (hereinafter, “pending warning message”) may be compared with the warning message of the received warning request message (hereinafter, “new warning message”). If the message identifier of the pending warning message and the message identifier of the new warning message are the same, and the serial number of the pending warning message and the serial number of the new warning message are the same, the base station (110) (or DU (220)) may ignore the new warning message. Here, the base station (110) (or DU (220)) can transmit an alert response message (e.g., alert response message of operation (513)) including broadcast completion information (e.g., 'Broadcast Completed Area List' IE) of AMF (e.g., AMF (530)). The alert response message can be associated with the new alert message. If the message identifier of the pending alert message and the message identifier of the new alert message are different, or the serial number of the pending alert message and the serial number of the new alert message are different, the pending alert message can be recognized as being different from the new alert message. The base station (110) (or DU (220)) can identify the 'Concurrent Warning Message Indicator'. For example, if there is no 'Concurrent Warning Message Indicator', the base station (110) (or CU (210)) can ignore the alert request message.For another example, if there is a 'Concurrent Warning Message Indicator', the base station (110) can schedule to broadcast the new warning message in the area. For example, the CU (210) can request the DU (220) to broadcast the new warning message through the warning procedure illustrated in FIGS. 6A and 6B. The DU (220) can configure scheduling information to schedule the pending warning message and the new warning message together. As the scheduling information changes, the SIB 1 message can be modified. The DU (220) can broadcast not only the modified SIB 1 message, but also the pending warning message and the new warning message together.

[0175] Figures 9a and 9b illustrate examples of transmission of warning messages according to overlapping scheduling. When a warning message divided into multiple segments is received, the base station (110) (e.g., DU (220)) can transmit the segments according to the number of SI windows. The SI window represents a time window in which SIBs can be transmitted, and the number of SI windows can correspond to a value obtained by dividing the smallest period value among the periods of SI messages (e.g., 'si-Periodicity' IE in Table 4) by the SI window length (e.g., 'si-WindowLength' IE in Table 4). For example, in an NR cell, assume that the SCS is 15 kHz. If the SI window length is 40 slots (e.g., 'si-WindowLength' IE is set to 's40'), the SI window length is 40 ms. If the smallest period value is 160 ms, the number of available SI windows is 4. Warning messages can be provided for concurrent broadcast.

[0176] Referring to FIG. 9A, mapping information (900) indicates a mapping relationship between warning messages of SIB 8 in SIB 1 message. For example, the warning messages may include a first warning message (SIB 8 #A), a second warning message (SIB 8 #B), a third warning message (SIB 8 #C), and a fourth warning message (SIB 8 #D). Each warning message may include four segments. One segment of the warning message may be understood as one SIB (or an SI message including the SIB). Therefore, mapping information (900) may include scheduling information for a total of 16 SIBs.

[0177] A segment of an alert message may be repeatedly transmitted within a single SI window. For example, the segment may be repeatedly transmitted over four radio frames (e.g., 10 ms). The segment may be transmitted in each of the fourth and ninth slots in each radio frame. For example, a first SIB period (911) may include four available SI windows (915). For example, the first SIB period (911) may be 160 ms, and the length of each of the SI windows (915) may be approximately 40 ms. In each of the four available SI windows (915), a segment may be transmitted. Within the first SIB cycle (911), a first segment of the first segments of the first alert message, a first segment of the second segments of the second alert message, a first segment of the third segments of the third alert message, and a first segment of the fourth segments of the fourth alert message may be sequentially transmitted through the four available SI windows (915). Within the second SIB cycle (912), a second segment of the first segments of the first alert message, a second segment of the second segments of the second alert message, a second segment of the third segments of the third alert message, and a second segment of the fourth segments of the fourth alert message may be sequentially transmitted through the four available SI windows (915).

[0178] Referring to Fig. 9b, a situation is described where DU (220) transmits warning messages to terminal (120) in the manner of Fig. 9a. Transmitting segments in the manner of Fig. 9a increases resource efficiency in terms of maximizing the use of available SI windows, but may also result in a problem where the terminal (120) fails to properly receive warning messages.

[0179] DU (220) can obtain a first alert message (SIB8 #A), a second alert message (SIB8 #B), and a third alert message (SIB8 #C). DU (220) can first transmit the first alert message to terminal (120). The first alert message can include four first segments. DU (220) can transmit one of the first segments every SIB cycle (940) (e.g., 1280 ms). Terminal (120) can be in an idle state (e.g., RRC IDLE). Terminal (120) can periodically monitor paging according to a paging cycle (920) (e.g., 2560 ms). The terminal (120) can check whether paging is received from the DU (220) (or the base station (110)), and if paging is not received, it can enter the idle state again. For example, according to the paging cycle (920), paging occasions (e.g., paging occasion (970a), paging occasion (970b), paging occasion (970c), paging occasion (970d), paging occasion (970e), paging occasion (970f), paging occasion (970g), paging occasion (970h), paging occasion (970i), paging occasion (970j), paging occasion (970k), paging occasion (970l)) in which the terminal (120) attempts paging can be set to the terminal (120). If segments of a warning message are simply broadcast for the duration of the modification period (930), a terminal (120) that has not yet received a paging message may not receive the first segment and the second segment of the first segment of the first warning message prior to the paging occasion (970a). Due to the unreceived segments (980) of the first warning message, it is difficult for the terminal (120) to obtain information about a disaster notification text corresponding to the complete first warning message.However, the terminal (120) can expect to receive the first segment and the second segment among the first segments of the first warning message in the next cycle.

[0180] The DU (220) may transmit a second warning message to the terminal (120). The second warning message may include four second segments. The DU (220) may transmit one of the second segments every SIB period (940) (e.g., 1280 ms). The terminal (120) may be in an active state (e.g., RRC CONNECTED) due to the first warning message. The terminal (120) may receive segments of the warning message for a transmission period (950) corresponding to two modification periods per warning message. When all segments are received for each warning message, the terminal (120) may display the corresponding warning message to the user through a display. For example, the terminal (120) that has received all first segments of the first warning message (SIB8 #A) may display a text message corresponding to the first warning message (SIB8 #A) to the user through a display. However, as illustrated in FIG. 9B, when the first warning message (SIB8 #A), the second warning message (SIB8 #B), and the third warning message (SIB8 #C) are scheduled and transmitted together, the terminal (120) may not be able to reassemble the warning messages in units of the warning messages even if it receives all of the segments (990) of each warning message. If the reassembly fails, the DU (220) may delete the pending segments. In a specific case, the DU (220) may discard at least some of the first segments of the first warning message, at least some of the second segments of the second warning message, and at least some of the third segments of the third warning message. Due to the failure and / or discarding of the reassembly, the terminal (120) may not be able to display a text message corresponding to the complete warning message to the user.

[0181] Fig. 10 illustrates an example of transmitting warning messages according to non-overlapping scheduling. To address and alleviate the issues described in Figs. 9a and 9b, embodiments of the present disclosure describe a method for transmitting warning messages using non-overlapping scheduling. Here, non-overlapping scheduling refers to scheduling in which intervals in which different warning messages are scheduled do not overlap with each other. Here, two warning messages are different in that the message identifier and serial number of one warning message are different from the message identifier and serial number of the other warning message.

[0182] Referring to FIG. 10, mapping information (1000) represents a mapping relationship between warning messages of SIB 8 in an SIB 1 message. For example, the warning messages may include a first warning message (SIB 8 #A), a second warning message (SIB 8 #B), a third warning message (SIB 8 #C), and a fourth warning message (SIB 8 #D). Each warning message may include four segments. Mapping information (1000) may include scheduling information for segments of the first warning message (SIB 8 #A). Accordingly, mapping information (1000) may include scheduling information for a total of four SIBs (e.g., SIB 8s). For example, the first SIB period (911) may include four available SI windows. In each of the four available SI windows, one segment may be transmitted. Within the first SIB cycle (911), the first segment of the first segments of the first alert message may be transmitted through the four available SI windows. Since the transmission of the first alert message is in progress, the remaining three available SI windows are not used for transmission of other alert messages (e.g., the second alert message, the third alert message, and the fourth alert message). Within the second SIB cycle (912), the second segment of the first segments of the first alert message may be transmitted through the four available SI windows. According to the non-overlapping scheduling, the remaining three available SI windows within the second SIB cycle (912) may not be used.

[0183] According to the non-overlapping scheduling, the terminal (120) can receive segments of different warning messages according to the order of the warning messages. For example, the terminal (120) can receive all first segments of the first warning message and then receive the second segments of the second warning message. Since the segments of different warning messages are not mixed in the terminal (120), the terminal (120) can obtain a complete warning message through reassembly. Hereinafter, a method for more efficiently transmitting segments of warning messages using the non-overlapping scheduling is described with reference to FIGS. 11 to 13.

[0184] Figure 11 shows an example of transmission of warning messages according to non-overlapping scheduling using a concurrent warning buffer.

[0185] Referring to FIG. 11, the DU (220) can obtain a first warning message (SIB8 #A), a second warning message (SIB8 #B), and a third warning message (SIB8 #C). The DU (220) can first transmit the first warning message to the terminal (120). The first warning message can include four first segments. The DU (220) can transmit one of the first segments every SIB cycle (940) (e.g., 1280 ms). The terminal (120) can be in an idle state (e.g., RRC IDLE). The terminal (120) can periodically monitor paging according to a paging cycle (920) (e.g., 2560 ms). The terminal (120) can check whether paging is received from the DU (220) (or the base station (110)), and if paging is not received, it can enter the idle state again. For example, according to the paging cycle (920), paging occasions (e.g., paging occasion (970a), paging occasion (970b), paging occasion (970c), paging occasion (970d), paging occasion (970e), paging occasion (970f), paging occasion (970g), paging occasion (970h), paging occasion (970i), paging occasion (970j), paging occasion (970k), paging occasion (970l)) on which the terminal (120) attempts paging can be set to the terminal (120). If segments of the warning message are simply broadcast for the duration of the modification period (930), a terminal (120) that has not yet received the paging message may not receive the first and second segments of the first segments of the first warning message prior to the paging occasion (970a). In one embodiment, the DU (220) may repeatedly transmit the first segments of the first warning message for a duration longer than the paging cycle (920).For example, the DU (220) can repeatedly transmit the first segments of the first warning message for two corresponding transmission periods of the modification period. The modification period can be set to an integer multiple (e.g., 2 times, 4 times) of a default paging cycle (e.g., paging cycle (920)). Accordingly, if each of the first segments of the first warning message is transmitted according to the SIB cycle (940) during two modification periods, the terminal (120) can receive all of the first segments of the first warning message.

[0186] In response to receiving a request to broadcast a second alert message, the DU (220) may determine whether at least one condition is met. In one embodiment, the DU (220) may determine whether there is space remaining in the simultaneous alert buffer. Only if there is space remaining in the simultaneous alert buffer, the DU (220) may utilize the synchronous alert buffer. In one embodiment, the DU (220) may determine whether all available SI windows are in use within the SIB cycle (940). For example, if all of the available SI windows are in use by at least some of the other SIBs (e.g., SIB 2, SIB 3, SIB 4, SIB 5, SIB 6, SIB 7, SIB 8), the synchronous alert buffer may be utilized. If there is an unused SI window among the available SI windows, the DU (220) may transmit one segment of the second segments of the second warning message through the SI window. In one embodiment, the DU (220) may determine whether there is a warning message currently being transmitted. If there is a warning message that is being broadcast periodically (e.g., the first warning message), the DU (220) may postpone transmission of the second warning message for non-overlapping scheduling. By satisfying at least one of the conditions described above, the DU (220) may determine whether to store the second warning message in the concurrent warning buffer.

[0187] For example, the DU (220) can store the second warning message in the first buffer (1111). The first buffer (1111) can be used as a concurrent warning buffer. The DU (220) can identify that the first buffer (1111) is empty. The DU (220) can identify that at least some of the first segments of the first warning message have been transmitted and at least some of the other segments are scheduled to be transmitted. In other words, since the first transmission period of the first warning message is in progress, the DU (220) can store the acquired second warning message (e.g., acquired from the CU (210) or the AMF (530)) in the first buffer (1111). Thereafter, when the first transmission period of the first warning message is completed, the DU (220) can transmit the second warning message. The DU (220) can transmit the second warning message during the second transmission period (1152). The DU (220) may repeatedly transmit the second segments of the second warning message during a second transmission period (1152). For example, the second transmission period (1152) may correspond to twice the modification period. Even if the terminal (120) does not receive the first segment and the second segment of the second warning message transmitted before the paging occasion (970f), it may receive the first segment and the second segment of the second warning message in the next cycle after the paging occasion (970f).

[0188] For example, DU (220) can store a second warning message and a third storage message in the second buffer (1112). DU (220) can identify that there is available space in the second buffer (1112). The second buffer (1112) can be used as a simultaneous warning buffer. The second buffer (1112) can be the same as or different from the first buffer (1111).

[0189] The DU (220) can identify that at least some of the second segments (or first segments) of the second warning message (or the first warning message) have been transmitted and at least some of the other segments are scheduled to be transmitted. In other words, since the second transmission period of the second warning message is in progress, the DU (220) can store the acquired third warning message (e.g., acquired from the CU (210) or the AMF (530)) in the second buffer (1112). Thereafter, when the second transmission period (1152) of the second warning message is completed, the DU (220) can transmit the third warning message. The DU (220) can transmit the third warning message during the third transmission period (1153). The DU (220) can repeatedly transmit the third segments of the third warning message during the third transmission period (1153). For example, the third transmission period (1153) may correspond to twice the modification period. Even if the terminal (120) does not receive the first segment and the second segment of the third warning message transmitted before the paging occasion (970i), it may receive the first segment and the second segment of the third warning message in the next cycle after the paging occasion (970i). The terminal (120) may not receive the first segment and the second segment (1171) of the first segments. The terminal (120) may receive all of the first segments (1161). The terminal (120) may not receive the first segment and the second segment (1172) of the second segments. The terminal (120) may receive all of the second segments (1162). The terminal (120) may not receive the first segment and the second segment (1173) of the third segments. The terminal (120) may receive all of the third segments (1163). The terminal (120) may receive all segments of the warning messages provided from the DU (220) during the reception period (1170).

[0190] Figure 12 shows an example of transmission of warning messages according to non-overlapping scheduling using repetition of warning messages.

[0191] Referring to FIG. 12, the DU (220) can obtain a first warning message (SIB8 #A), a second warning message (SIB8 #B), and a third warning message (SIB8 #C). The DU (220) can first transmit the first warning message to the terminal (120). The first warning message can include four first segments. The DU (220) can transmit one of the first segments every SIB cycle (940) (e.g., 1280 ms). The terminal (120) can be in an idle state (e.g., RRC IDLE). The terminal (120) can periodically monitor paging according to a paging cycle (920) (e.g., 2560 ms). The terminal (120) can check whether paging is received from the DU (220) (or the base station (110)), and if paging is not received, it can enter the idle state again. For example, according to the paging cycle (920), paging occasions (e.g., paging occasion (970a), paging occasion (970b), paging occasion (970c), paging occasion (970d), paging occasion (970e), paging occasion (970f), paging occasion (970g), paging occasion (970h), paging occasion (970i), paging occasion (970j), paging occasion (970k), paging occasion (970l)) on which the terminal (120) attempts paging can be set to the terminal (120). A terminal (120) that has not yet received a paging message may not receive the first segment and the second segment among the first segments of the first warning message prior to the paging occasion (970a).

[0192] Repeating warning messages for a transmission period longer than the terminal's paging cycle, for example, corresponding to two revision periods, may incur more overhead than retransmitting segments of missed warning messages. To reduce this overhead, according to embodiments, the DU (220) may repeatedly transmit the first warning message. For example, the DU (220) may repeatedly transmit the first warning message once more and transmit other warning messages within the transmission period (e.g., corresponding to two revision periods). Warning messages may be repeatedly transmitted for a period corresponding to up to two revision periods for each warning message. By repeatedly transmitting the first requested warning message (e.g., the first warning message), the DU (220) may re-provision the terminal (120) with segments missed due to late paging. In the present disclosure, when a warning request message of a warning message is received, if there is no ongoing broadcast warning message for the warning area associated with the warning message, the warning message may be understood as the first generated warning message. As a non-limiting example, the warning message may represent the first requested warning message within a specified time period. As a non-limiting example, the first warning message may also be the requested warning message if there is no pending broadcast warning message in the corresponding cell. By transmitting warning messages according to a non-overlapping schedule, as well as repeating the first requested warning message, problems due to reconfiguration failure can be alleviated. After the transmission of the repeated first warning messages (e.g., including the original first warning message and the repeated warning messages corresponding to the copies of the first warning message) is completed, the DU (220) can transmit the second segments of the second warning message, which is the next warning message.

[0193] For example, DU (220) can transmit a first warning message during a first transmission period (1251). DU (220) can transmit the first segments of the first warning message during the first transmission period (1251). Since the first warning message is the first requested warning message (or initial warning message), DU (220) can repeatedly transmit the first warning message. If one repetition is performed, DU (220) can transmit the first segments of the first warning message and then transmit the first segments of the first warning message again. For example, DU (220) can transmit a second warning message during a second transmission period (1252). DU (220) can transmit the second segments of the second warning message during the second transmission period (1252). Meanwhile, if the transmission of the second warning message is completed by transmitting the second segments once, the DU (220) can immediately trigger the transmission of the third warning message. The DU (220) can transmit the third warning message during the third transmission period (1253). The DU (220) can transmit the third segments of the third warning message during the third transmission period (1253). The terminal (120) may not receive the first segment and the second segment (1271) of the first segments. The terminal (120) may receive all of the first segments (1261). The terminal (120) may receive all of the second segments (1262). The terminal (120) may receive all of the third segments (1263). The terminal (120) can receive all segments of warning messages provided from the DU (220) during the receiving section (1270).

[0194] In FIG. 12, an example of repeating the first requested warning message once is described, but such repetition is only an example and does not limit the embodiments of the present disclosure. According to one embodiment, the DU (220) can repeatedly transmit the specified warning message a specified number of times. The specified number of times may be a predetermined number. For example, the specified number of times may be 2. In another example, the specified number of times may be 4. In addition to the existing warning message, the DU (220) can additionally transmit the warning messages up to the specified number of times. The purpose of repeating the initial warning message is to ensure that there are no segments that the terminal (120) cannot receive due to the paging cycle. Therefore, the specified number of times may be determined so that at least one of the minimum warning message segments can be received within the paging cycle. The specified number of times may be determined based on the paging cycle, the SIB period, and the number of segments in the warning message. For example, the specified number of times can be obtained by applying a ceiling function to the product of the number of segments in the warning message and the SIB period divided by the paging cycle.

[0195] Figure 13 shows an example of transmission of warning messages according to non-overlapping scheduling using segment repetition.

[0196] Referring to FIG. 13, the DU (220) can obtain a first warning message (SIB8 #A), a second warning message (SIB8 #B), and a third warning message (SIB8 #C). The DU (220) can first transmit the first warning message to the terminal (120). The first warning message can include four first segments. The DU (220) can transmit one of the first segments every SIB cycle (940) (e.g., 1280 ms). The terminal (120) can be in an idle state (e.g., RRC IDLE). The terminal (120) can periodically monitor paging according to a paging cycle (920) (e.g., 2560 ms). The terminal (120) can check whether paging is received from the DU (220) (or the base station (110)), and if paging is not received, it can enter the idle state again. For example, according to the paging cycle (920), paging occasions (e.g., paging occasion (970a), paging occasion (970b), paging occasion (970c), paging occasion (970d), paging occasion (970e), paging occasion (970f), paging occasion (970g), paging occasion (970h), paging occasion (970i), paging occasion (970j), paging occasion (970k), paging occasion (970l)) on which the terminal (120) attempts paging can be set to the terminal (120). A terminal (120) that has not yet received a paging message may not receive the first segment and the second segment among the first segments of the first warning message prior to the paging occasion (970a).

[0197] Repeating warning messages for a transmission period longer than the terminal's paging cycle, for example, corresponding to two revision periods, may incur more overhead than retransmitting segments of missed warning messages. To reduce this overhead, according to embodiments, the DU (220) may repeatedly transmit at least one segment of the first warning message. For example, the DU (220) may transmit the first transmitted segment of the first warning message a number of times more than the number of repetitions. Thereafter, the DU (220) may transmit other warning messages within the transmission period (e.g., corresponding to two revision periods). Warning messages may be repeatedly transmitted for a period corresponding to up to two revision periods for each warning message. By repeatedly transmitting at least one segment of the first requested warning message (e.g., the first warning message), the DU (220) may re-provision the missed segments due to late paging to the terminal (120). In the present disclosure, when an alert request message for an alert message is received, if there are no ongoing broadcast alert messages for the alert area associated with the alert message, the alert message may be understood as the first alert message that has occurred. As a non-limiting example, the alert message may indicate the first alert message requested within a specified time period. As a non-limiting example, the first requested alert message may also be the requested alert message if there are no pending broadcast alert messages in the corresponding cell.

[0198] In one embodiment, the DU (220) may determine a reference segment of the first requested warning message (hereinafter, referred to as the initial warning message). The reference segment refers to a reference segment to be repeatedly transmitted. Hereinafter, one reference segment is exemplified, but embodiments of the present disclosure are not limited thereto. As a non-limiting example, multiple reference segments may be defined and the multiple reference segments may be repeatedly transmitted. For example, the DU (220) may determine the segment with the lowest segment number among the segments of the warning message as the reference segment. As another example, the DU (220) may determine the segment whose segment type is not the last segment among the segments of the warning message as the reference segment. As yet another example, the DU (220) may determine the segment that is requested first among the segments of the warning message as the reference segment.

[0199] In one embodiment, the DU (220) may determine the number of repetitions of the reference segment. The DU (220) may additionally transmit the reference segments equal to the number of repetitions before transmitting the existing warning message. The purpose of repeating the reference segments of the initial warning message is to ensure that there are no segments that the terminal (120) cannot receive due to the paging cycle. Therefore, the number of repetitions may be determined so that a minimum number of segments can be received within the paging cycle. The number of repetitions may be determined based on the paging cycle and the SIB period. For example, the number of repetitions may be obtained by applying a ceiling function to the value obtained by dividing the paging cycle by the SIB period. For example, if the paging cycle is 2560 ms (milliseconds) and the SIB period is 1280 ms, the number of repetitions of the reference segment may be 2. By transmitting only the reference segment repeatedly rather than repeating the entire first warning message, which is the initial warning message, the reception interval for obtaining all warning messages can be reduced.

[0200] For example, DU (220) can transmit a first warning message during a first transmission period (1351). DU (220) can transmit first segments of the first warning message during the first transmission period (1351). Since the first warning message is the first requested warning message (i.e., the initial warning message), DU (220) can repeatedly transmit a reference segment among the first segments of the first warning message. If one repetition is performed, DU (220) can transmit the first segments of the first warning message after transmitting the reference segment. For example, DU (220) can transmit a second warning message during a second transmission period (1352). DU (220) can transmit the second segments of the second warning message during the second transmission period (1352). Meanwhile, if the transmission of the second warning message is completed by transmitting the second segments once, the DU (220) can immediately trigger the transmission of the third warning message. The DU (220) can transmit the third warning message during the third transmission period (1353). The DU (220) can transmit the third segments of the third warning message during the third transmission period (1353). The terminal (120) may not receive the first segment and the second segment (1371) of the first segments. The terminal (120) may receive all of the first segments (1361). The terminal (120) may receive all of the second segments (1362). The terminal (120) may receive all of the third segments (1363). The terminal (120) can receive all segments of warning messages provided from the DU (220) during the receiving section (1370).

[0201] FIG. 14 illustrates the operation of an electronic device (e.g., a base station (110), a DU (220)) for non-overlapping scheduling using a simultaneous warning buffer. For the operations of FIG. 14, the timing diagram of FIG. 11 may be referred to.

[0202] Referring to FIG. 14, in operation (1401), the electronic device may receive a first request message for broadcasting a first alert message of system information for PWS. The system information for PWS may include SIB 6 for ETWS notification, SIB 7 for ETWS notification, and / or SIB 8 for CMAS notification. The first request message may be an alert request message for the first alert message. For example, when the electronic device is a base station (110), the first request message may correspond to an alert request message received from an AMF (e.g., an alert request message of Table 3). For example, when the electronic device is a DU (220), the first request message may correspond to an alert request message received from a CU (210) (e.g., an alert request message of Table 6).

[0203] In operation (1403), the electronic device may transmit the first segments of the first warning message during a first transmission period. For example, the first transmission period may correspond to twice the modification period indicated in the SIB 1 message associated with the first warning message. The modification period may correspond to the product of the coefficient of the SIB 1 message and the basic paging cycle.

[0204] In operation (1405), the electronic device may receive a second request message for broadcasting a second alert message of system information for PWS within a first transmission period. The system information for PWS may include SIB 6 for ETWS notification, SIB 7 for ETWS notification, and / or SIB 8 for CMAS notification. The second request message may be an alert request message for the second alert message. For example, when the electronic device is a base station (110), the second request message may correspond to an alert request message received from an AMF (e.g., an alert request message of Table 3). For example, when the electronic device is a DU (220), the second request message may correspond to an alert request message received from a CU (210) (e.g., an alert request message of Table 6).

[0205] In operation (1407), the electronic device may store a second warning message in a buffer if all available SI windows are in use. The buffer may be a concurrent warning buffer. The electronic device may store second segments of the second warning message in the buffer.

[0206] In operation (1409), the electronic device may transmit second segments of the second alert message during a second transmission period after the first segments of the first alert message are transmitted. The electronic device may identify the second segments of the second alert message stored in the buffer. The electronic device may transmit the second segments during a second transmission period. For example, the second transmission period may correspond to twice the modification period indicated in an SIB 1 message associated with the second alert message. The modification period may correspond to the product of a coefficient of the SIB 1 message and a basic paging cycle.

[0207] FIG. 15 illustrates the operation of an electronic device (e.g., a base station (110), a DU (220)) for non-overlapping scheduling using repetition of warning messages. For the operations of FIG. 15, the timing diagram of FIG. 12 may be referred to.

[0208] Referring to FIG. 15, in operation (1501), the electronic device may receive a first request message for broadcasting a first warning message of system information for PWS. The system information for PWS may include SIB 6 for ETWS notification, SIB 7 for ETWS notification, and / or SIB 8 for CMAS notification. The first request message may be an alert request message for the first warning message.

[0209] In operation (1503), the electronic device may receive a second request message for broadcasting a second alert message of system information for PWS. The system information for PWS may include SIB 6 for ETWS notification, SIB 7 for ETWS notification, and / or SIB 8 for CMAS notification. The second request message may be an alert request message for the second alert message.

[0210] In operation (1505), if the first warning message is a first warning message, the electronic device may transmit a first warning message and at least one repeat warning message during a first transmission period. The first warning message may represent a first warning message. The first warning message may be understood as a first generated warning message when there is no ongoing broadcast warning procedure in the corresponding warning area. For example, the first warning message may represent a first requested warning message within a specified time period. For example, the first warning message may be a requested warning message when there is no pending broadcast warning message in the corresponding cell. The electronic device may identify the first warning message as the first warning message. The electronic device may copy the first warning message. Each segment of the at least one repeat warning message may be identical to the first segments of the first warning message. The electronic device may generate at least one repeat warning message corresponding to the first warning message. In one embodiment, the number of said at least one repetitive warning message may be determined based on a paging cycle set via the corresponding system information, a SIB period indicated by the SIB 1 message, and the number of segments in the initial warning message. In another embodiment, the number of said at least one repetitive warning message may be fixed. For example, the number of said at least one repetitive warning message may be 1.

[0211] In operation (1507), the electronic device may transmit second segments of the second warning message during a second transmission period. The second transmission period may be set to be less than two modification periods. The electronic device may transmit the second segments of the second warning message after transmitting both the first warning message and the at least one repeat warning message.

[0212] FIG. 16 illustrates the operation of an electronic device (e.g., a base station (110), a DU (220)) for non-overlapping scheduling using segment repetition. For the operations of FIG. 16, the timing diagram of FIG. 13 may be referred to.

[0213] Referring to FIG. 16, in operation (1601), the electronic device may receive a first request message for broadcasting a first warning message of system information for PWS. The system information for PWS may include SIB 6 for ETWS notification, SIB 7 for ETWS notification, and / or SIB 8 for CMAS notification. The first request message may be an alert request message for the first warning message.

[0214] In operation (1603), the electronic device may receive a second request message for broadcasting a second alert message of system information for PWS. The system information for PWS may include SIB 6 for ETWS notification, SIB 7 for ETWS notification, and / or SIB 8 for CMAS notification. The second request message may be an alert request message for the second alert message.

[0215] In operation (1605), the electronic device may transmit repeated segments corresponding to a reference segment among the first segments of the first warning message. The electronic device may determine a reference segment of the first requested warning message (hereinafter, referred to as the initial warning message). For example, the electronic device may determine a segment with a lowest segment number among the segments of the warning message as the reference segment. As another example, the electronic device may determine a segment whose segment type is not the last segment among the segments of the warning message as the reference segment. As yet another example, the electronic device may determine a segment that is requested first among the segments of the warning message as the reference segment. The electronic device may determine a repetition number of the reference segment. Before transmitting the existing warning message, the electronic device may additionally transmit the reference segments equal to the repetition number. The purpose of repeating the reference segments of the initial warning message is to ensure that no segments are not received by the terminal (120) due to the paging cycle. Therefore, the number of repetitions can be determined so that a minimum number of segments can be received within the paging cycle. The number of repetitions can be determined based on the paging cycle and the SIB period. Each of the repeated segments can contain the same content as the reference segment.

[0216] In operation (1607), the electronic device may transmit the first segments of the first warning message after transmitting the repeat segments.

[0217] In operation (1609), the electronic device may transmit second segments of a second warning message after transmitting the first segments.

[0218] Various scheduling techniques using non-overlapping scheduling are described through FIGS. 11 to 16. One of the techniques described above may be fixedly used by an operator, or at least two or more of the techniques described above may be dynamically switched. According to one embodiment, an operator in charge of a scheduler for system information may manually configure one of the techniques described above. According to another embodiment, a scheduling device (e.g., a base station (110), a DU (220)) may adaptively configure a scheduling technique among the techniques described above, based on the operator's settings. For example, the DU may select a scheduling technique to apply among the techniques described above based on a key performance indicator (KPI) (e.g., a warning message transmission success rate, delay, MCS, and throughput). The DU may perform scheduling according to the selected scheduling technique.

[0219] Figure 17 illustrates examples of non-overlapping scheduling. Figure 17 illustrates a comparison between a technique (1710) that schedules segments of warning messages in a round-robin manner and a technique (1720) that repeatedly transmits reference segments of the initial warning message (e.g., the first warning message). Both the first technique (1710) and the second technique (1720) utilize a non-overlapping scheduling scheme.

[0220] Referring to FIG. 17, the DU (220) can obtain a first warning message (SIB8 #A), a second warning message (SIB8 #B), and a third warning message (SIB8 #C). According to the first technique (1710), the terminal (120) can receive segments of the first warning message during a modification period, and can receive segments of the second warning message in the next modification period. If the warning message is repeatedly changed and transmitted in this way at fixed time intervals, the terminal (120) may not receive some segments of the initial warning message due to late paging. The terminal (120) can receive the missed segments in a later time interval. The terminal (120) can receive segments of the first warning message (SIB8 #A), the second warning message (SIB8 #B), and the third warning message (SIB8 #C) during the first reception period (1711).

[0221] According to the second technique (1720), the DU (220) may first transmit the first warning message to the terminal (120). The DU (220) may determine the reference segment of the first requested warning message (hereinafter, the initial warning message). The DU (220) may determine the number of repetitions of the reference segment. The DU (220) may transmit the first warning message during the first transmission period (1351). The DU (220) may transmit the first segments of the first warning message during the first transmission period (1351). Since the first warning message is the first requested warning message (i.e., the initial warning message), the DU (220) may repeatedly transmit the reference segment among the first segments of the first warning message. For example, the DU (220) may repeat the reference segments twice. Thereafter, the DU (220) can transmit the first segments of the first warning message. After transmitting the first segments, the DU (220) can transmit the second segments of the second warning message. After transmitting the second segments, the DU (220) can transmit the third segments of the third warning message. Thereafter, the terminal can retransmit the warning messages according to the cycle (1730) of the warning message to be broadcast (e.g., 'repetition period' IE = 40). The terminal (120) can receive segments of the first warning message (SIB8 #A), the second warning message (SIB8 #B), and the third warning message (SIB8 #C) during the second reception period (1721). The scheduling advantage of the second technique (1720) can be confirmed by shortening the second reception interval (1721) compared to the first reception interval (1711). Furthermore, the second technique (1720) can provide higher resource efficiency than the first technique (1710). For example, in the first technique (1710), the round-robin method may result in repeated transmission of unnecessary segments.On the other hand, since the second technique (1720) only repeatedly schedules some segments at the requested time, unnecessary scheduling on the wireless channel can be reduced compared to the first technique (1710). In addition, as described in Fig. 6b, considering the periodic transmission of each warning message (e.g., 'repetition period' IE), it can be confirmed that the second technique (1720) is a method that conforms to the intent of the standard more than the first technique (1710).

[0222] Fig. 18 illustrates an example of components of an electronic device for non-overlapping scheduling. The configuration illustrated in Fig. 18 can be understood as a configuration of a network entity (e.g., DU (220)) that functions as at least a part of a base station (e.g., base station (110)). Terms such as "...unit" and "...unit" used hereinafter mean a unit that processes at least one function or operation, and this can be implemented by hardware, software, or a combination of hardware and software.

[0223] Referring to FIG. 18, the electronic device (1800) may include a transceiver (1810), a memory (1820), and a processor (1830).

[0224] The transceiver (1810) may perform functions for transmitting and receiving signals in a wired communication environment. The transceiver (1810) may include a wired interface for controlling direct connections between devices via a transmission medium (e.g., copper wire, optical fiber). For example, the transceiver (1810) may transmit electrical signals to other devices via copper wire, or perform conversion between electrical signals and optical signals. The DU (220) may communicate with a centralized unit (CU) (e.g., CU (210)) via the transceiver (1810). The transceiver (1810) may also perform functions for transmitting and receiving signals in a wireless communication environment. For example, the transceiver (1810) may perform a conversion function between a baseband signal and a bitstream according to the physical layer specifications of the system. For example, when transmitting data, the transceiver (1810) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the transceiver (1810) restores a reception bit stream by demodulating and decoding a baseband signal. In addition, the transceiver (1810) may include multiple transmission and reception paths. According to an implementation example, the electronic device (1810) may perform communication with a UE (e.g., terminal (120)) directly through a wireless access network as a DU (220) or may perform communication with a UE (e.g., terminal (120)) through a radio unit (RU).

[0225] The transceiver (1810) transmits and receives signals as described above. Accordingly, all or part of the transceiver (1810) may be referred to as a "communication unit," a "transmitter," a "receiver," or a "transmitter-receiver unit." Furthermore, in the following description, transmission and reception performed via a wireless channel are used to mean that processing as described above is performed by the transceiver (1810). Although only the transceiver (1810) is illustrated in FIG. 18, the electronic device (1800) may include two or more transceivers according to other implementation examples.

[0226] Although not shown in FIG. 18, the transceiver (1810) may further include a backhaul transceiver for connecting to a core network or other base stations. For example, the electronic device (1800) may operate as a RAN node including a CU (210). The backhaul transceiver may provide an interface for communicating with other nodes within the network (e.g., other RAN nodes, eNBs, gNBs). That is, the backhaul transceiver converts a bit stream transmitted from a base station to another node, such as another access node, another base station, an upper node, a core network, etc., into a physical signal, and converts a physical signal received from another node into a bit stream.

[0227] The memory (1820) stores data such as basic programs, application programs, and setting information for the operation of the electronic device (1800). The memory (1820) may be referred to as a storage unit. The memory (1820) may be configured as volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. In addition, the memory (1820) may provide stored data upon request of the processor (1830). The memory (1820) is a functional component and represents a storage space. For example, the memory (1820) may be understood not only to represent a memory (e.g., a hard disk, flash memory, RAM) arranged as a component within the electronic device (1800), but also to represent a space for storing instructions and / or programs.

[0228] The processor (1830) controls the overall operations of the electronic device (1800). The processor (1880) may be referred to as a control unit. For example, the processor (1830) transmits and receives signals via the transceiver (1810) (or via the backhaul communication unit). In addition, the processor (1830) records and reads data from the memory (1820). In addition, the processor (1830) may perform functions of the protocol stack required by the communication standard (e.g., functions according to the protocol of FIG. 2A and functions of FIG. 2B). Although only the processor (1830) is illustrated in FIG. 18, the electronic device (1800) may include two or more processors according to other implementation examples.

[0229] The configuration of the electronic device (1800) illustrated in FIG. 18 is merely an example, and the components of the electronic device performing the embodiments of the present disclosure are not limited to the configuration illustrated in FIG. 18. In some embodiments, some configurations may be added, deleted, or changed.

[0230] In embodiments, an electronic device (e.g., a distributed unit (DU)) is provided. The electronic device may include a memory for storing instructions, and at least one processor. The instructions, when executed by the at least one processor, may cause the electronic device to receive a first request message for broadcasting a first warning message of system information for a public warning system (PWS), and, in response to the first request message, transmit first segments of the first warning message on a cell during a first transmission period corresponding to two modification periods, and, based on receiving a second request message for broadcasting a second warning message of the system information in the first transmission period, determine whether all available system information (SI) windows are in use, and, if all available SI windows are in use, store the second warning message in a buffer, and, after all the first segments of the first warning message have been transmitted, transmit second segments of the second warning message on the cell during a second transmission period corresponding to the two modification periods.

[0231] In one embodiment, the instructions, when executed by the at least one processor, may cause the electronic device to transmit, in response to the first request message, a first system information block (SIB) 1 message over the cell, wherein the first SIB 1 message includes scheduling information of the first segments of the first alert message, and to transmit, in response to the second request message, a second SIB 1 message over the cell, wherein the second alert message includes scheduling information of the first segments of the first alert message and scheduling information of the second segments of the second alert message. The second alert message may be instructed for concurrent broadcast with the broadcast of another ongoing alert message.

[0232] In one embodiment, the first request message may include a message identifier of the first alert message, a serial number of the first alert message, the first segments of the first alert message, a number of requested broadcasts, a repetition period, and a cell global identifier (CGI) for indicating the cell. The second request message may include a message identifier of the second alert message, a serial number of the second alert message, the second segments of the second alert message, a number of requested broadcasts, a repetition period, and the cell global identifier (CGI).

[0233] In one embodiment, the system information for the PWS may include system information block (SIB) 6 for earthquake and tsunami warning service (ETWS) primary notification, SIB 7 for ETWS secondary notification, or SIB 8 for commercial mobile alert service (CMAS).

[0234] According to one embodiment, the instructions, when executed by the at least one processor, may cause the electronic device to transmit, during the at least one SI window among the available SI windows, at least one of the second segments of the second alert message on the cell if the at least one SI window is not in use.

[0235] In one embodiment, the instructions, when executed by the at least one processor, cause the electronic device to, in response to receiving a third request message for broadcasting a third warning message of the system information in the second transmission period, determine whether all available SI windows are in use, and if all available SI windows are in use, store the third warning message in the buffer, and transmit third segments of the third warning message on the cell during a third transmission period corresponding to the two modification periods after all second segments of the second warning message have been transmitted.

[0236] In embodiments, an electronic device (e.g., a distributed unit (DU)) is provided. The electronic device may include a memory storing instructions, and at least one processor. The instructions, when executed by the at least one processor, may cause the electronic device to receive a first request message for broadcasting a first warning message of system information for a public warning system (PWS), receive a second request message for broadcasting a second warning message of the system information for the PWS, transmit the first warning message and at least one repeat warning message corresponding to the first warning message on the cell during a first transmission period when the first warning message corresponds to a first ongoing warning message on the cell, and transmit second segments of the second warning message on the cell during a second transmission period following the first transmission period after both the first warning message and the at least one repeat warning message are transmitted. Each message of the first warning message and at least one repeat warning message corresponding to the first warning message may include identical first segments.

[0237] In one embodiment, the instructions, when executed by the at least one processor, cause the electronic device to, when receiving the first request message, identify whether a broadcast procedure of an alert message is in progress, and if the broadcast procedure of the alert message is not in progress, determine a number of repetitions for the first alert message, wherein the number of repetitions may represent a number of messages of the first alert message and the at least one repeated alert message.

[0238] According to one embodiment, the number of repetitions corresponding to the number of messages of the first warning message and the at least one repeat warning message may be determined based on the number of first segments in the first warning message, a paging cycle, and a period of a system information (SI) message for the first warning message.

[0239] In one embodiment, the first transmission period may be less than or equal to twice the modification period for the first warning message, and the second transmission period may be less than or equal to twice the modification period for the second warning message.

[0240] In one embodiment, the instructions, when executed by the at least one processor, may cause the electronic device to transmit, in response to the first request message, a first system information block (SIB) 1 message over the cell, wherein the first SIB 1 message includes scheduling information of the first segments of the first alert message, and to transmit, in response to the second request message, a second SIB 1 message over the cell, wherein the second SIB 1 message includes scheduling information of the first segments of the first alert message and scheduling information of the second segments of the second alert message. The second alert message may be instructed for concurrent broadcast with the broadcast of another ongoing alert message.

[0241] In one embodiment, the system information for the PWS may include system information block (SIB) 6 for earthquake and tsunami warning service (ETWS) primary notification, SIB 7 for ETWS secondary notification, or SIB 8 for commercial mobile alert service (CMAS).

[0242] In one embodiment, the first request message may include a message identifier of the first alert message, a serial number of the first alert message, the first segments of the first alert message, a number of requested broadcasts, a repetition period, and a cell global identifier (CGI) for indicating the cell. The second request message may include a message identifier of the second alert message, a serial number of the second alert message, the second segments of the second alert message, a number of requested broadcasts, a repetition period, and the cell global identifier (CGI).

[0243] In embodiments, an electronic device (e.g., a distributed unit (DU)) is provided. The electronic device may include a memory for storing instructions, and at least one processor. The instructions, when executed by the at least one processor, may cause the electronic device to receive a first request message for broadcasting a first warning message of system information for a public warning system (PWS), receive a second request message for broadcasting a second warning message of the system information for the PWS, transmit, on the cell, repeat segments corresponding to a reference segment among first segments of the first warning message when the first warning message corresponds to a first ongoing warning message on the cell, transmit, after transmitting the repeat segments, the first segments of the first warning message on the cell, and transmit, after both the repeat segments and the first segments of the first warning message are transmitted, the second segments of the second warning message on the cell.

[0244] In one embodiment, the instructions, when executed by the at least one processor, may cause the electronic device to identify whether a broadcast procedure of an alert message is in progress when receiving the first request message, and if the broadcast procedure of the alert message is not in progress, determine the number of repeat segments.

[0245] In one embodiment, the number of repeating segments may be determined based on a paging cycle and a period of a system information (SI) message for the first warning message.

[0246] In one embodiment, the reference segment may be the segment number that is earliest among the first segments of the first warning message. For example, the reference segment may correspond to the earliest segment number among the segment numbers of the first segments of the first warning message.

[0247] In one embodiment, the reference segment may be scheduled to be transmitted first among the first segments of the first warning message.

[0248] In one embodiment, the system information for the PWS may include system information block (SIB) 6 for earthquake and tsunami warning service (ETWS) primary notification, SIB 7 for ETWS secondary notification, or SIB 8 for commercial mobile alert service (CMAS).

[0249] In one embodiment, the first request message may include a message identifier of the first alert message, a serial number of the first alert message, the first segments of the first alert message, a number of requested broadcasts, a repetition period, and a cell global identifier (CGI) for indicating the cell. The second request message may include a message identifier of the second alert message, a serial number of the second alert message, the second segments of the second alert message, a number of requested broadcasts, a repetition period, and the cell global identifier (CGI).

[0250] For one or more embodiments, at least one of the components described in one or more of the preceding drawings may be configured to perform one or more operations, techniques, processes, and / or methods as described herein. For example, a processor (e.g., a baseband processor) described herein with respect to one or more of the preceding drawings may be configured to operate according to one or more examples described herein. For another example, circuitry associated with a user equipment (UE), a base station, a network element, and the like, as described above with respect to one or more of the preceding drawings, may be configured to operate according to one or more examples described herein.

[0251] Any of the embodiments described above may be combined with any other embodiment (or combination of embodiments) unless explicitly stated otherwise. The foregoing description of one or more implementations provides examples and descriptions, but is not intended to be exhaustive or limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be learned from practicing various embodiments.

[0252] The various embodiments of this document and the terminology used therein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the items, unless the context clearly indicates otherwise. In this document, each of the phrases "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "at least one of A, B, and C", and "at least one of A, B, or C" can include any one of the items listed together in the corresponding phrase among those phrases, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used merely to distinguish one component from another, and do not limit the components in any other respect (e.g., importance or order). When a component (e.g., a first component) is referred to as "coupled" or "connected" to another component (e.g., a second component), with or without the terms "functionally" or "communicatively," it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.

[0253] The term "module" used in various embodiments of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be an integral component, or a minimum unit or part of such a component that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0254] Various embodiments of the present document may be implemented as software including one or more instructions stored in a storage medium (e.g., memory (1820)) readable by a machine (e.g., DU (220), an electronic device operating as DU (220)). For example, a processor (e.g., processor (1830)) of the machine (e.g., DU (220), an electronic device operating as DU (220)) may call at least one instruction among the one or more instructions stored from the storage medium and execute it. This enables the machine to operate to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' simply means that the storage medium is a tangible device and does not contain signals (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently or temporarily on the storage medium.

[0255] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0256] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure. The one or more programs may be provided as a computer program product. The computer program product may be traded between a seller and a buyer as a commodity. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play Store™) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created in a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

[0257] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

[0258] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.

[0259] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0260] According to embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., modules or programs) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

[0261] Meanwhile, although the detailed description of the present disclosure has described specific embodiments, it is obvious that various modifications are possible within the scope of the present disclosure.< / maxcellingnbdu>

Claims

1. In electronic devices, Memory for storing instructions; and comprising at least one processor, The above instructions, when executed by the at least one processor, cause the electronic device to: Receive a first request message for broadcasting a first warning message of system information for a public warning system (PWS), In response to the first request message, the first segments of the first warning message are transmitted over the cell during a first transmission period corresponding to two modification periods, Based on receiving a second request message for broadcasting a second warning message of the system information in the first transmission period, determining whether all available system information (SI) windows are in use; If all of the above available SI windows are in use, store the second warning message in the buffer, After all of the first segments of the first warning message have been transmitted, causing the second segments of the second warning message to be transmitted on the cell during a second transmission period corresponding to the two modification periods. Electronic devices.

2. In claim 1, The above instructions, when executed by the at least one processor, cause the electronic device to: In response to the first request message, a first SIB (system information block) 1 message including scheduling information of the first segments of the first warning message is transmitted on the cell, In response to the second request message, cause a second SIB 1 message to be transmitted on the cell, the second SIB 1 message including scheduling information of the first segments of the first warning message and scheduling information of the second segments of the second warning message; The above second warning message is directed for concurrent broadcast with the broadcast of other ongoing warning messages. Electronic devices.

3. In claim 2, The first request message includes a message identifier of the first warning message, a serial number of the first warning message, the first segments of the first warning message, the number of requested broadcasts, a repetition period, and a cell global identifier (CGI) for indicating the cell. The second request message comprises a message identifier of the second warning message, a serial number of the second warning message, the second segments of the second warning message, the number of requested broadcasts, a repetition period, and the cell global identifier (CGI). Electronic devices.

4. In claim 1, The system information for the above PWS includes SIB (system information block) 6 for ETWS (earthquake and tsunami warning service) primary notification, SIB 7 for ETWS secondary notification, or SIB 8 for CMAS (commercial mobile alert service). Electronic devices.

5. In claim 1, The instructions, when executed by the at least one processor, cause the electronic device to transmit, during the at least one SI window among the available SI windows, at least one of the second segments of the second warning message on the cell. Electronic devices.

6. In claim 1, The above instructions, when executed by the at least one processor, cause the electronic device to: In response to receiving a third request message for broadcasting a third warning message of said system information in said second transmission period, determining whether all of said available SI windows are in use; If all of the above available SI windows are in use, store the third warning message in the buffer, After all of the second segments of the second warning message have been transmitted, causing the third segments of the third warning message to be transmitted on the cell during a third transmission period corresponding to the two modification periods. Electronic devices.

7. In electronic devices, Memory for storing instructions; and comprising at least one processor, The above instructions, when executed by the at least one processor, cause the electronic device to: Receive a first request message for broadcasting a first warning message of system information for a public warning system (PWS), Receive a second request message for broadcasting a second warning message of the above system information for the above PWS, If the first warning message corresponds to a first ongoing warning message on the cell, the first warning message and at least one repeat warning message corresponding to the first warning message are transmitted on the cell during a first transmission period, After both the first warning message and the at least one repeat warning message are transmitted, causing second segments of the second warning message to be transmitted on the cell during a second transmission period following the first transmission period; Each message of the first warning message and at least one repeat warning message corresponding to the first warning message comprises identical first segments, Electronic devices.

8. In claim 7, The above instructions, when executed by the at least one processor, cause the electronic device to: When receiving the above first request message, identify whether the broadcast procedure of the warning message is in progress, If the broadcast procedure of the above warning message is not in progress, causing the number of repetitions for the above first warning message to be determined, The above repetition count represents the number of messages of the first warning message and the at least one repetition warning message. Electronic devices.

9. In claim 7, The number of repetitions corresponding to the number of messages of the first warning message and the at least one repeat warning message is determined based on the number of the first segments in the first warning message, the paging cycle, and the period of the SI (system information) message for the first warning message. Electronic devices.

10. In claim 7, The above first transmission period is less than or equal to twice the modification period for the above first warning message, The second transmission period is less than or equal to twice the modification period for the second warning message. Electronic devices.

11. In claim 7, The above instructions, when executed by the at least one processor, cause the electronic device to: In response to the first request message, a first SIB (system information block) 1 message including scheduling information of the first segments of the first warning message is transmitted on the cell, In response to the second request message, cause a second SIB 1 message to be transmitted on the cell, the second SIB 1 message including scheduling information of the first segments of the first warning message and scheduling information of the second segments of the second warning message; The above second warning message is directed for concurrent broadcast with the broadcast of other ongoing warning messages. Electronic devices.

12. In claim 7, The system information for the above PWS includes SIB (system information block) 6 for ETWS (earthquake and tsunami warning service) primary notification, SIB 7 for ETWS secondary notification, or SIB 8 for CMAS (commercial mobile alert service). Electronic devices.

13. In claim 7, The first request message includes a message identifier of the first warning message, a serial number of the first warning message, the first segments of the first warning message, the number of requested broadcasts, a repetition period, and a cell global identifier (CGI) for indicating the cell. The second request message comprises a message identifier of the second warning message, a serial number of the second warning message, the second segments of the second warning message, the number of requested broadcasts, a repetition period, and the cell global identifier (CGI). Electronic devices.

14. In electronic devices, Memory for storing instructions; and comprising at least one processor, The above instructions, when executed by the at least one processor, cause the electronic device to: Receive a first request message for broadcasting a first warning message of system information for a public warning system (PWS), Receive a second request message for broadcasting a second warning message of the above system information for the above PWS, If the first warning message corresponds to the first ongoing warning message on the cell, repeat segments corresponding to the reference segment among the first segments of the first warning message are transmitted on the cell, After transmitting the above repetition segments, the first segments of the first warning message are transmitted on the cell, After all of the above repetition segments and the above first segments of the above first warning message have been transmitted, causing the second segments of the above second warning message to be transmitted on the cell. Electronic devices.

15. In a method performed by an electronic device, The electronic device is an electronic device according to any one of claims 1 to 14, The method comprises operations configured to be performed by an electronic device according to any one of claims 1 to 14. method.

Images