Method and apparatus for public warning system delivery

The method and apparatus for managing PWS notification delivery status in NB-IoT UE optimize RRC mode transitions, improving network performance and user experience by ensuring timely delivery and handling urgent services.

WO2026234193A1PCT designated stage Publication Date: 2026-11-12TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2026/063312
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-07
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing solutions for public warning system (PWS) notifications in NB-IoT user equipment (UE) fail to support delivery in RRC connected mode, leading to inefficient switching between RRC modes and potential impact on network performance and user experience.

Method used

A method and apparatus for NB-IoT UE and network nodes to determine and manage PWS notification delivery status, allowing proper actions based on this information to optimize RRC mode transitions and prioritize urgent services.

Benefits of technology

Enhances network performance and user experience by reducing unnecessary RRC mode switches and ensuring timely delivery of PWS notifications while allowing simultaneous handling of urgent traffic.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2026063312_12112026_PF_FP_ABST
    Figure EP2026063312_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Various embodiments of the present disclosure provide a method for public warning system (PWS) delivery. The method which may be performed by a terminal device comprises: determining information about a PWS notification. The information about the PWS notification may indicate whether the PWS notification is being delivered, and / or whether the terminal device is receiving or needs to receive the PWS notification, and / or whether the reception of the PWS notification by the terminal device is completed or terminated. In accordance with an exemplary embodiment, the method further comprises: performing one or more actions, based at least in part on the information about the PWS notification.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD AND APPARATUS FOR PUBLIC WARNING SYSTEM DELIVERYTECHNICAL FIELD

[0001] The present disclosure generally relates to communication networks, and more specifically, to a method and apparatus for public warning system (PWS) delivery.BACKGROUND

[0002] This section introduces aspects that may facilitate a better understanding of the disclosure. Accordingly, the statements of this section are to be read in this light and are not to be understood as admissions about what is in the prior art or what is not in the prior art.

[0003] In the 3rd generation partnership project (3GPP), the fifth generation system (5GS) is a new generation’s radio access technology intended to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC), narrow band Internet of things (NB-IoT) and massive machine type communication (mMTC). 5G networks may include the new radio (NR) access stratum (AS) interface and the 5G core network (5GC). The NR physical and higher layers may reuse parts of the long-term evolution (LTE) specification, and optionally introduce one or more additional components when being motivated by the new use cases. There has been a lot of discussions in 3GPP in the last few years on how to specify technologies to cover / address use cases for machine-to-machine (M2M) and / or Internet of things (loT). In 3GPP Release 13, enhancements to support machine-type communication (MTC) were specified by introducing new UE categories Ml (Cat-Mi) and NB1 (Cat-NBl) to support reduced maximum bandwidth of up to 6 physical resource blocks (PRBs) in enhanced MTC (eMTC) work item and narrowband carrier in NB-IoT work item specifying a new radio interface, respectively.SUMMARY

[0004] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0005] PWS is an umbrella term covering the earthquake and tsunami warning system (ETWS), the commercial mobile alert system (CMAS), European public warning system (EU-ALERT), and the Korean public alert system (KPAS). According to the existing solutions, a NB-IoT user equipment (UE) is released to radio resource control (RRC) idle mode to receive a PWS notification, and it may not be supported for the NB-IoT UE in RRC connected mode to receive the PWS notification. In thiscase, the NB-IoT UE may switch between the RRC connected mode and the RRC idle mode back and forth to receive the PWS notification and other types of traffic data. It may also be possible for the NB-IoT UE to stay in the RRC idle mode inappropriately (e.g., when the NB-IoT UE no longer needs to receive the PWS notification, or when the NB-IoT UE has some urgent services while the PWS notification is not time critical, etc.) and fail to enter the RRC connected mode in time. Thus, it may be desirable to improve operation configurations at UE side and / or network (NW) side during delivery of a PWS notification.

[0006] Various exemplary embodiments of the present disclosure propose a solution for PWS delivery, which can enable a terminal device (e.g., a UE, etc.) and / or a network node (e.g., an access network node, a core network node, etc.) to take one or more proper actions based at least in part on delivery and / or reception status of the PWS notification, so as to reduce the potential adverse effects on network performance and user experience due to delivery / reception of the PWS notification.

[0007] According to a first aspect of the present disclosure, there is provided a method performed by a terminal device (e.g., a UE such as a NB-IoT UE, etc.). The method comprises: determining information about a PWS notification. The information about the PWS notification may indicate whether the PWS notification is being delivered, and / or whether the terminal device is receiving or needs to receive the PWS notification, and / or whether the reception of the PWS notification by the terminal device is completed or terminated. In accordance with an exemplary embodiment, the method further comprises: performing one or more actions, based at least in part on the information about the PWS notification.

[0008] According to a second aspect of the present disclosure, there is provided an apparatus which may be implemented as a terminal device. The apparatus may comprise processing circuitry and one or more memories storing computer program codes. The one or more memories and the computer program codes may be configured to, with the processing circuitry, cause the apparatus at least to perform any step of the method according to the first aspect of the present disclosure.

[0009] According to a third aspect of the present disclosure, there is provided computer-readable medium comprising instructions that, when executed by processing circuitry, may cause the processing circuitry to carry out any step of the method according to the first aspect of the present disclosure.

[0010] According to a fourth aspect of the present disclosure, there is provided a method performed by a first network node (e.g., an access network node, etc.). The method comprises: obtaining information about a PWS notification. The information about the PWS notification may indicate whether the PWS notification is being delivered, and / or whether a terminal device is receiving or needs to receive the PWS notification, and / or whether the reception of the PWSnotification by the terminal device is completed or terminated. In accordance with an exemplary embodiment, the method further comprises: performing one or more actions, based at least in part on the information about the PWS notification.

[0011] According to a fifth aspect of the present disclosure, there is provided an apparatus which may be implemented as a first network node. The apparatus may comprise processing circuitry and one or more memories storing computer program codes. The one or more memories and the computer program codes may be configured to, with the processing circuitry, cause the apparatus at least to perform any step of the method according to the fourth aspect of the present disclosure.

[0012] According to a sixth aspect of the present disclosure, there is provided computer-readable medium comprising instructions that, when executed by processing circuitry, may cause the processing circuitry to carry out any step of the method according to the fourth aspect of the present disclosure.

[0013] According to a seventh aspect of the present disclosure, there is provided a method performed by a second network node (e.g., a core network node, etc.). The method comprises: receiving at least part of information about a PWS notification from a first network node. The information about the PWS notification may indicate whether the PWS notification is being delivered, and / or whether a terminal device is receiving or needs to receive the PW S notification, and / or whether the reception of the PWS notification by the terminal device is completed or terminated. In accordance with an exemplary embodiment, the method further comprises: performing one or more actions, based at least in part on the information about the PWS notification.

[0014] According to an eighth aspect of the present disclosure, there is provided an apparatus which may be implemented as a second network node. The apparatus may comprise processing circuitry and one or more memories storing computer program codes. The one or more memories and the computer program codes may be configured to, with the processing circuitry, cause the apparatus at least to perform any step of the method according to the seventh aspect of the present disclosure.

[0015] According to a ninth aspect of the present disclosure, there is provided computer-readable medium comprising instructions that, when executed by processing circuitry, may cause the processing circuitry to carry out any step of the method according to the seventh aspect of the present disclosure.

[0016] According to a tenth aspect of the present disclosure, there is provided a computer program product comprising instructions that, when executed by processing circuitry, may cause the processing circuitry to any step of the method according to the first or fourth or seventh aspect of the present disclosure.

[0017] According to an eleventh aspect of the present disclosure, there is provided acommunication system comprising the terminal device according to the second aspect of the present disclosure, the first network node according to the fifth aspect of the present disclosure, and the second network node according to the eighth aspect of the present disclosure.BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The disclosure itself, the preferable mode of use and further objectives are best understood by reference to the following detailed description of the embodiments when read in conjunction with the accompanying drawings, in which:

[0019] Fig.l is a flowchart illustrating a method according to an embodiment of the present disclosure;

[0020] Fig.2 is a flowchart illustrating a method according to another embodiment of the present disclosure;

[0021] Fig.3 is a flowchart illustrating a method according to yet another embodiment of the present disclosure;

[0022] Fig.4 is a block diagram illustrating an apparatus according to an embodiment of the present disclosure;

[0023] Fig.5 shows an example of a communication system in accordance with some embodiments;

[0024] Fig.6 shows another example of a communication system in accordance with some embodiments;

[0025] Fig.7 shows a wireless device in accordance with some embodiments;

[0026] Fig.8 shows a network node in accordance with some embodiments; and

[0027] Fig.9 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.DETAILED DESCRIPTION

[0028] The embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only for the purpose of enabling those skilled persons in the art to better understand and thus implement the present disclosure, rather than suggesting any limitations on the scope of the present disclosure. Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present disclosure should be or are in any single embodiment of the disclosure. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure.Furthermore, the described features, advantages, and characteristics of the disclosure may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the disclosure.

[0029] As used herein, the term “network” refers to a network following any suitable communication standards such as new radio (NR), long term evolution (LTE), LTE-Advanced, wideband code division multiple access (WCDMA), high-speed packet access (HSPA), code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency-division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), non-terrestrial network (NTN) and so on. Furthermore, the communications between a terminal device and a network node in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the communication protocols as defined by a standard organization such as 3GPP. For example, the communication protocols may comprise the first generation (1G), 2G, 3G, 4G, 4.5G, 5G, 6G communication protocols, and / or any other protocols either currently known or to be developed in the future.

[0030] The term “network node” or “network device” or “network function” refers to any suitable apparatus or function which can be implemented in a network entity (physical or virtual) of a communication network. For example, the network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g. on a cloud infrastructure.

[0031] The network node may comprise a network device in a communication network via which a terminal device accesses to the network and receives services therefrom. The network node may refer to a base station (BS), an access point (AP), a multi-cell / multicast coordination entity (MCE), a controller or any other suitable device in a wireless communication network. The BS may be, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a next generation NodeB (gNodeB or gNB), a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, a low power node such as a femto, a pico, a wireless access backhaul (WAB) node, and so forth.

[0032] Yet further examples of the network node comprise multi-standard radio (MSR) radio equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, positioning nodes and / or the like. More generally, however, the network node may represent any suitable device (or group of devices) capable, configured, arranged, and / or operable to enable and / orprovide a terminal device access to a wireless communication network or to provide some service to a terminal device that has accessed to the wireless communication network.

[0033] The term “terminal device” refers to any end device that can access a communication network and receive services therefrom. By way of example and not limitation, the terminal device may refer to a mobile terminal, a user equipment (UE), or other suitable devices. The UE may be, for example, a subscriber station, a portable subscriber station, a mobile station (MS) or an access terminal (AT). The terminal device may include, but not limited to, portable computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, a mobile phone, a cellular phone, a smart phone, a tablet, a wearable device, a personal digital assistant (PDA), a vehicle, and the like.

[0034] As yet another specific example, in an Internet of things (loT) scenario, a terminal device may also be called an loT device and represent a machine or other device that performs monitoring, sensing and / or measurements etc., and transmits the results of such monitoring, sensing and / or measurements etc. to another terminal device and / or a network equipment. The terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3rd generation partnership project (3GPP) context be referred to as a machine-type communication (MTC) device.

[0035] As one particular example, the terminal device may be a UE implementing the 3GPP narrow band Internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances, e.g., refrigerators, televisions, personal wearables such as watches etc. In other scenarios, a terminal device may represent a vehicle or other equipment, for example, a medical instrument that is capable of monitoring, sensing and / or reporting etc. on its operational status or other functions associated with its operation.

[0036] As used herein, the terms “first”, “second” and so forth refer to different elements. The singular forms “a” and “an” are intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms “comprises”, “comprising”, “has”, “having”, “includes” and / or “including” as used herein, specify the presence of stated features, elements, and / or components and the like, but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof. The term “based on” is to be read as “based at least in part on”. The term “one embodiment” and “an embodiment” are to be read as “at least one embodiment”. The term “another embodiment” is to be read as “at least one other embodiment”. Other definitions, explicit and implicit, may be included below.

[0037] At the 3GPP radio access network (RAN)#70 meeting, a new Release 13 work item named NB-IoT is approved. The objective of the new loT related work items approved for Release 13 is tospecify a radio access for cellular loT that addresses improved indoor coverage, support for massive number of low throughput devices, not sensitive to delay, ultra-low device cost, low device energy consumption and (optimized) network architecture.

[0038] NB-IoT can be described as a narrowband version of LTE. Similar to eMTC, NB-IoT makes use of increased acquisition times and time repetitions to extend the system coverage. The repetitions can be seen as a third level of retransmissions added at the physical layer as a complement to those at medium access control (MAC) hybrid automatic repeat request (HARQ) and radio link control (RLC) automatic repeat request (ARQ). A NB-IoT downlink carrier is defined by 12 orthogonal frequency-division multiplexing (OFDM) sub-carriers, each of 15 kHz, giving a total baseband bandwidth of 180 kHz. When multiple carriers are configured, several 180 kHz carriers can be used, e.g., for increasing the system capacity, inter-cell interference coordination, load balancing, etc. This design may give NB-IoT a high deployment flexibility. When receiving a RRCConnectionRelease message, a NB-IoT UE may delay releasing the RRC connection for 10 seconds.

[0039] For use cases of PWS, an ETWS primary / secondary notification and a CMAS notification may be delivered in system information blocks (SIBs) while an indication of ETWS / CMAS notification delivery may be indicated in a paging message or downlink control information (DCI) using a direct indication. Before acquiring the SIBs delivering the ETWS / CMAS notification, a UE may first need to read SIB1 to obtain the scheduling information of those SIBs.

[0040] Segmentation can be applied for the delivery of an ETWS secondary notification and a CMAS notification. The segmentation may be fixed for transmission of a given ETWS secondary notification and a CMAS notification within a cell (e.g., the same segment size for a given segment with the same messageidentifier, serialNumber and warningMessageSegmentNumber). A universal mobile telecommunications system (UMTS) terrestrial radio access network (UTRAN) may not interleave transmissions of CMAS notifications, e.g., all segments of a given CMAS notification transmission are transmitted prior to those of another CMAS notification.

[0041] Upon entering a cell during RRC IDLE, following successful handover or upon connection re-establishment, a UE may discard any previously buffered wamingMessageSegment. If either the received value of messageidentifier or of serialNumber or of both are different from the current (stored) values of messageidentifier and serialNumber, the UE may also discard any previously buffered wamingMessageSegment.

[0042] To benefit from the strong mobile ecosystem and economy of scale, the satellite network based on the terrestrial wireless access technologies including LTE and NR for satellite networks, is being specified in the 3 GPP standard.

[0043] In 3GPP Release 15, the first release of the 5G system (5GS) is specified. As a new generation’s communication technology, the 5GS may be intended to serve use cases such as eMBB, URLLC, mMTC and etc. In Release 15, 3GPP also started the work to prepare NR for operation in an NTN. The work was performed within the study item “NR to support Non-Terrestrial Networks” and resulted in 3GPP technical report (TR) 38.811 V15.4.0. In 3GPP Release 16, the work to prepare NR for operation in an NTN network continues with the study item “Solutions for NR to support Non-Terrestrial Network”, as described in 3GPP TR 38.821 V16.2.0. In parallel, the interest to adapt LTE for operation in NTN is growing. As a consequence, 3GPP introduced support for NTN in both LTE and NR in Release 17 (e.g., 3GPP RP -221806 “Revised WID on loT NTN enhancements” and RP -220208 “Solutions for NR to support non-terrestrial networks (NTN)”). After the basic functionality was established, NTN enhancements continued in Release 18 for both LTE and NR (e.g., 3GPP RP -223519 “Revised WID on loT NTN enhancements” and RP-223534 “Revised WID: NR NTN (Non-Terrestrial Networks) enhancements”).

[0044] A satellite radio access network may usually include the following components:A satellite that refers to a space-borne platform.An earth-based gateway that connects the satellite to a base station or a core network, depending on the choice of architecture.A feeder link that refers to the link between a gateway and a satellite.An access link, or service link, that refers to the link between a satellite and a UE.

[0045] A communication satellite may typically generate several beams over a given area. The footprint of a beam is usually in an elliptic shape, which has been traditionally considered as a cell (but a cell consisting of multiple beams may not be precluded). The footprint of a beam is also often referred to as a spotbeam. Three types of beams or cells may be supported in an NTN:Earth-fixed beams / cells: provisioned by beam(s) continuously covering the same geographical areas all the time (e.g., in the case of geostationary earth orbit (GEO) satellites).Quasi -Earth-fixed beams / cells: provisioned by beam(s) covering a geographic area for a limited period and a different geographic area during another period (e.g., in the case of non-geostationary orbit (NGSO) satellites generating steerable beams).Earth-moving beams / cells: provisioned by beam(s) whose coverage area slides over the earth surface (e.g., in the case of NGSO satellites generating fixed or non-steerable beams).

[0046] Due to the special operating conditions in an NTN, the system information broadcasted in an NTN cell may need to include NTN-specific information. To serve this purpose, a new SIB (SIB 19) may be introduced in an NR NTN, which contains the NTN-specific information. In an loT NTN, theNTN-specific information may be provided in SIB31 and SIB32, while t-Service may be indicated in SIB3 (SIB3-NB in NB-IoT), e.g., as described in 3GPP technical specification (TS) 36.331 V18.4.0. t-Service may indicate time information on when an NTN quasi-Earth fixed cell is going to stop serving the area it is currently covering, while t-ServiceStart may indicate time information on when the incoming satellite is going to start serving the area for quasi-earth fixed cell. The tle-Ephemeri sParam eters may provide the satellite orbital parameters based on the two-line element (TLE) set format for estimating in-coverage and out-of-coverage periods for a satellite with earth moving cell(s).

[0047] The standardization of NTN technologies continues in 3 GPP with another two work items (3GPP RP -234077 “New WID: Non-Terrestrial Networks (NTN) for Internet of Things (loT) Phase 3” and RP-234078 “New WID: Non-Terrestrial Networks (NTN) for NR Phase 3”) for LTE and NR, respectively. The justification for these enhancements is the necessities of the commercial deployments that are ongoing at the moment of writing. Based on real deployment or deployment plans, further evolution of NR and loT NTN may be required.

[0048] Among the objectives included in the loT NTN Release 19 work item description (WID), the present disclosure is related to supporting broadcast of PWS messages for NB-IoT re-using the LTE mechanisms, and for a NB-IoT UE in RRC connected mode, not supporting PWS indication / notifications in paging, direct indication, and system information.

[0049] In 3GPP RAN2#130, it is agreed that the network may release a NB-IoT UE in an RRC connected mode to an RRC idle mode to receive a PWS notification, in case that the NB-IoT UE reports the capability to receive the PWS notification in the RRC idle mode. This may imply that for the NB-IoT UE in the RRC connected mode, receiving the PWS notification may not be supported.

[0050] With such mechanism it may happen that a NB-IoT UE is released to an RRC idle mode to receive a PWS notification, and then the NB-IoT UE may be triggered by its higher layer or the core network (CN) (note that a CN node serving the NB-IoT UE may be different from a CN node distributing the PWS notification) to enter an RRC connected mode again, and again released to the RRC idle mode, and so forth, which may be undesired.

[0051] On the other hand, in case that the NB-IoT UE already receives all the warning message (segments), or the PWS delivery is completed / terminated, or the NB-IoT UE is out of a PWS service area and is not required to receive the PWS notification, it may be unnecessary to keep the NB-IoT UE in the RRC idle mode.

[0052] Moreover, for some urgent service / traffic such as emergent call, it may not be suitable to release a NB-IoT UE to an RRC idle mode to receive a PWS notification, especially if the PWS notification is not time critical (e.g., CMAS, etc.).

[0053] In order to address one or more issues described above, various exemplary embodiments of the present disclosure propose solutions to enable a UE (e.g., a NB-IoT UE, etc.) to determine whether a PWS notification is still being delivered / needs to be received, and exchange PWS delivery / reception status information between a UE and a NW and / or between different layers of the UE. Based on such information, the NW and the UE can take proper actions to avoid undesired RRC connection establishment.

[0054] The proposed solutions provide one or more criteria for a UE to determine whether a PW S notification is still being delivered or the PWS notification delivery is completed / terminated. In an embodiment, the UE’s AS layer may inform the PWS notification delivery / reception status to its higher layer. In another embodiment, the (AS layer of the) UE may stop receiving the PWS notification when the UE determines that it is out of a PWS service area, and inform this to the higher layer. In another embodiment, the higher layer of the UE may not pass a service request or may postpone passing the service request to the AS layer if there is any PWS notification being delivered / received, or the higher layer of the UE may inform the AS layer and / or the CN that the service request may need to be prioritized over (certain type(s) of) PWS notification(s). In another embodiment, the UE’s AS layer may not initiate RRC connection establishment or may postpone initiating RRC connection establishment to transmit the service request received from the higher layer when receiving the PWS notification, unless the service request is prioritized over the PWS notification. In another embodiment, an access network node (e.g., an eNB, etc.) may inform a cause of releasing the UE (e.g., to receive PWS notification(s), etc.) and / or the PWS notification delivery status to a core network node (e.g., an MME, etc.). In another embodiment, the core network node such as an MME may postpone sending a paging request (for a UE) triggered by downlink (DL) traffic when the PWS notification(s) are being delivered (or received by the UE). In another embodiment, the access network node such as an eNB may postpone sending a paging message (to a UE) triggered by DL traffic when the PWS notification(s) are being delivered (or received by the UE). In another embodiment, the postponing may not be performed by the core network node and / or the access network node if the DL traffic is prioritized over the PWS notification.

[0055] Many advantages may be achieved by applying the proposed solutions. For example, it may be possible for a UE (e.g., a NB-IoT UE, etc.) to avoid switching between an RRC connected mode and an RRC idle mode back and forth when a PWS notification is delivered. In addition, the UE can enter the RRC connected mode in time when the PWS delivery is completed / terminated or the UE is not required to receive the PWS notification. Moreover, the UE may be allowed to stay in / enter the RRC connected mode to transmit / receive emergent service / traffic data if the PWS notification is not time critical. All these can ensure that the system performance and end userexperience may not be badly impacted by the introduction of PWS notification reception in NB-IoT.

[0056] More details of the proposed solutions of the present disclosure will be described below in connection with various exemplary embodiments. Some exemplary embodiments are described mainly in terms of LTE based NB-IoT NTNs, but they are equally applicable in an NTN based on LTE-M or NR technology. The term “NTN” used herein may, depending on the context, refer to either or both of NR NTN and loT NTN, and sometimes the term “NTN” may be used to refer to only loT NTN.

[0057] The term “network” used herein may refer to a network node, which typically may be a gNB (e.g., in a NR based NTN) or an eNB (e.g., in an LTE based NTN, such as an loT NTN), but may also be a base station or an access point in another type of network based on communication via satellites or high altitude platform system (HAPS), or any other network node (in a network involving satellites or HAPS) with the ability to directly or indirectly communicate with a UE. More specifically, when the term “network” is used and the network is said to do something in relation to a UE, e.g., receive something from a UE or transmit something to a UE or configure a UE with some configuration, this may refer to a network node, typically an eNB or a gNB, etc.

[0058] The terms information element (IE), parameter, field parameter, and field may be used interchangeably in this document. Parameters / IEs / fields used in abstract syntax notation one (ASN.l) code as well as in procedural text in the 3GPP RRC specification for 5G / NR, i.e., 3GPP TS 38.331 VI 8.0.0, are often named with a suffix indicating the number of the release of the 3GPP standard the parameter / IE / field was introduced in (e.g., the suffix “-rl7” for a parameter / IE / field introduced in Release 17 of the 3GPP standard). Parameters / IEs / fields following this naming convention are typically referred to both with and without the suffix, where the name including the suffix is used in the ASN.l code (and thus defines the formal name from the ASN.l compiler’s perspective), while the name without the suffix is used in running text, e.g., in field descriptions and procedural text. Relevant examples may include the parameters / IEs / fields such as tl-Threshold-rl7 / tl -Threshold and t-Service-rl7 / t-Service. It can be appreciated that both name variants may occur for various parameters / IEs / fields.

[0059] In some exemplary embodiments, (NB-IoT) SIB for delivering ETWS primary notification is denoted ETWS primary SIB(-NB), (NB-IoT) SIB for delivering ETWS secondary notification is denoted ETWS secondary SIB(-NB), and (NB-IoT) SIB for delivering CMAS notification is denoted CMAS SIB(-NB).

[0060] In some exemplary embodiments, a PWS notification may refer to an ETWS primary notification and / or an ETWS secondary notification and / or a CMAS notification. The embodiments may be equally applied to other kinds of PWS notification such as the EU-ALERT, the KPAS, etc.,and in general (higher layer) information delivered in SIB(s).

[0061] It can be appreciated that although some exemplary embodiments are described for a NB-loT UE capable of receiving a PWS notification in anRRC idle mode, they also can be equally applied to other types of UEs which are only capable of receiving a PWS notification or certain DL transmission(s) in an RRC idle mode or RRC inactive mode.

[0062] In accordance with an exemplary embodiment, a NB-IoT UE (e.g., via the AS layer of the NB-IoT UE) may determine that a PWS notification is being delivered (in a serving cell) which the NB-IoT UE may need to receive, if one or more of the following conditions are met:(the latest received) SIB1 includes scheduling information of a PWS SIB (e.g., ETWS primary SIB-NB, ETWS secondary SIB-NB or CMAS SIB-NB) for delivering the PWS notification.It receives a paging message or DCI (using direct indication) indicating that there is a PWS notification being delivered.The time that has passed since the last time it received the PWS notification is no more than X seconds, where X may be configured by the NW, hardcoded in the specification or up to UE implementation (in practice X is not less than PWS SIB periodicity). It has not received all the warningMessageSegments if the PWS notification is segmented. It is not informed by the NW (e.g., the serving cell) that the delivery of the PWS notification is terminated.

[0063] In accordance with an exemplary embodiment, the (AS layer of the) NB-IoT UE may determine that a PWS notification is not delivered or the delivery of the PWS notification is completed / terminated (in the serving cell) or it no more needs to receive the PWS notification, if one or more of the following conditions are met:(the latest received) SIB1 does not include scheduling information of the PWS SIB for delivering the PWS notification.It does not receive a paging message or DCI (using direct indication) indicating that there is a PWS notification being delivered.The time that has passed since the last time it received the PWS notification is more than Y seconds, where Y may be configured by the NW, hardcoded in the specification or up to UE implementation (in practice Y is not smaller than X).It has received all the warningMessageSegments if the PWS notification is segmented. It is informed by the NW (e.g., the serving cell) that the delivery of the PWS notification is terminated. The NW may inform this in an existing SIB (e.g., the PWS SIB delivering the PWS notification) or a new SIB. In the latter case, the new SIB may also include themessageidentifier and optionally the serialNumber of the PWS notification.

[0064] In accordance with an exemplary embodiment, based on the determination, the AS layer of the NB-IoT UE may inform PWS status information to its higher layer, e.g., including but not limited to one or more ofWhether there are PWS notification(s) being delivered.Whether there are PWS notification(s) being received by the AS layer.If there are PWS notification(s) being delivered / received, the type of the PWS notification(s) (e.g., time critical or non-time critical, and / or whether it is an ETWS primary notification, an ETWS secondary notification or a CMAS notification) and / or the messageldentifier / serialNumber of the PWS notification(s).

[0065] Optionally, the AS layer of the NB-IoT UE may only perform the informing as described above when powering on or the delivery / reception status of PWS notification(s) are changed.

[0066] In accordance with an exemplary embodiment, the UE’s AS layer may inform its higher layer of whether it is in the PWS service area (if present in the PWS SIB) of the PWS notification being delivered. To facilitate this, in case segmentation is applied for the PWS delivery, the relevant PWS SIB may deliver the warning area segments (e.g., WarningAreaCoordinatesSegment) first, and when the UE’s AS layer has received sufficient number of warning area segments to determine whether the UE is in the PWS service area, the AS layer can inform the determination result to the higher layer. In an embodiment, such informing may only be performed when the UE determines itself to be outside of the PWS service area (meanwhile the AS layer of the UE may stop receiving the PWS notification).

[0067] In accordance with an exemplary embodiment, based on the above mentioned PWS status information received from the AS layer, the higher layer of the UE may take one or more of the following actions:Postpone passing or does not pass a service request (which may trigger the AS layer to set up RRC connection and enter an RRC connected mode) to the AS layer, if there is any PWS notification being delivered / received and the UE is inside the corresponding PWS service area (and / or the higher layer is not informed that the UE is outside of the corresponding PWS service area).When passing the service request to the AS layer, also inform the AS layer that the service request is prioritized over (certain type(s) of) PWS notification(s).When sending the service request to the CN, also inform the CN that the service request is prioritized over (certain type(s) of) PWS notification(s).

[0068] In accordance with an exemplary embodiment, the AS layer of the UE may take one ormore of the following actions if there is any PWS notification being delivered / received: Postpone initiating or does not initiate RRC connection establishment to transmit a service request, unless the higher layer indicates that the service request is prioritized over (certain type(s) of) PWS notification(s) and there are no PWS notification(s) other than the indicated one(s) being delivered / received.In case that the AS layer determines to initiate random access and RRC connection establishment based on the higher layer indication, it may inform an eNB (e.g., in RRCConnectionRequest) of whether its PWS reception is completed and / or whether it prioritizes uplink (UL) transmission over (certain type(s) of) PWS notification(s). In an embodiment, the eNB may only release the UE to an RRC idle mode if there are PWS notification(s) other than the informed one(s) being delivered.Inform the higher layer that the service request may not be transmitted for a certain time or until being informed by the AS layer that the transmission can be made.Prioritize PWS notification reception over early data transmission (EDT) if they are (partially) overlapped in time.

[0069] In accordance with an exemplary embodiment, when an eNB releases a NB-IoT UE to an RRC idle mode to receive PWS notification(s) (the eNB may be denoted releasing eNB), it may inform some PWS status information to the CN (e.g., to a CN node such as an MME serving the UE), e.g., including but not limited to one or more of:The cause of the release, i.e., to receive PWS notification(s) in an RRC idle mode. The type of the PWS notification(s) being delivered or to be received by the UE (e.g., time critical or non-time critical, and / or whether it is an ETWS primary notification, an ETWS secondary notification or a CMAS notification).The messageldentifier / serialNumber of the PWS notification(s) being delivered or to be received by the UE.

[0070] In accordance with an exemplary embodiment, the eNB may update the MME about the PWS status information indicating the PWS notification delivery status, when there are new PWS notification(s) being delivered or ongoing PWS notification delivery is completed / terminated.

[0071] In accordance with an exemplary embodiment, when the MME receives a DL data notification for the UE, e.g., from a packet gateway / serving gateway (PGW / SGW), it may perform one or more of the following actions:Postpone sending a paging request for the UE over SI interface for a certain time or until being notified by the releasing eNB that delivery of the PWS notification(s) is completed / terminated.Postpone sending the paging request for the UE to all the eNBs where the PWS notification(s) are being delivered.Only postpone sending the paging request for the UE to the releasing eNB.

[0072] In accordance with an exemplary embodiment, the MME may still send the paging request for the UE as in the legacy network without knowing / considering the cause of the release, while the eNBs, when receiving the paging request for the UE, may postpone sending the paging message to the UE for a certain time or until delivery of the PWS notification(s) is completed / terminated. In an embodiment, only the releasing eNB postpones the sending (potentially only in the cell where the UE is released to the RRC idle mode).

[0073] In accordance with an exemplary embodiment, a DL data notification may indicate (e.g., in a new field or by extending an existing field such as paging policy indication, etc.) whether the DL data for the UE need to be prioritized over (certain type(s) of) PWS notification(s). The MME may take this into account when determining whether to postpone sending the paging request for the UE over SI interface. For example, the MME may only postpone the sending if there are PWS notification(s) prioritized over the DL data being delivered. In an embodiment, the MME may not postpone sending the paging request but indicate in the paging request (e.g., in a new field or by extending an existing field such as paging cause, etc.) whether the paging request for the UE need to be prioritized over (certain type(s) of) PWS notification(s). The eNBs may take this into account when determining whether to postpone sending the paging message to the UE, e.g., the sending may be only postponed if there are PWS notification(s) prioritized over the paging request being delivered. In an embodiment, when a UE enters an RRC connected mode, its serving eNB may only release the UE to an RRC idle mode if there are PWS notification(s) prioritized over the paging request which triggers the UE to enter the RRC connected mode being delivered.

[0074] In accordance with an exemplary embodiment, the eNB may not postpone sending the paging message triggered by the DL traffic to the UE even there are PWS notification(s) being delivered, if mobile terminated (MT) EDT can be applied to deliver the DL traffic which may not require the UE to switch to the RRC connected mode.

[0075] It can be appreciated that the names, representations and values of the information elements / parameters / attributes used herein are exemplary, and other names, representations and values may also be used to indicate the same or similar information and may also be applicable to various exemplary embodiments according to the present disclosure.

[0076] It is noted that some embodiments of the present disclosure are mainly described in relation to 4G / LTE and 5G / NR specifications being used as non-limiting examples for certain exemplary network configurations and system deployments. As such, the description of exemplary embodimentsgiven herein specifically refers to terminology which is directly related thereto. Such terminology is only used in the context of the presented non-limiting examples and embodiments, and does naturally not limit the present disclosure in any way. Rather, any other system configuration or radio technologies may equally be utilized as long as exemplary embodiments described herein are applicable.

[0077] Fig.l is a flowchart illustrating a method 100 according to some embodiments of the present disclosure. The method 100 illustrated in Fig.1 may be performed by a terminal device (e.g., a UE such as a NB-IoT UE, a mobile station, a subscriber device, etc.) or an apparatus communicatively coupled to the terminal device. In accordance with an exemplary embodiment, the terminal device may be configured to communicate with a network node (e.g., a network node in a 5G / NR network, etc.) to obtain network services.

[0078] According to the exemplary method 100 illustrated in Fig.l, the terminal device may determine information about a PWS notification, as shown in block 102. The information about the PWS notification may indicate whether the PWS notification is being delivered, and / or whether the terminal device is receiving or needs to receive the PWS notification, and / or whether the reception of the PWS notification by the terminal device is completed or terminated. In accordance with an exemplary embodiment, the terminal device may perform one or more actions, based at least in part on the information about the PWS notification, as shown in block 104. In an embodiment, the one or more actions performed by the terminal device may comprise determining whether to transmit a service message (e.g., a service request, etc.), and / or determining whether to postpone transmitting the service message, etc.

[0079] In accordance with an exemplary embodiment, the information about the PWS notification may indicate that the PWS notification is being delivered, and / or that the terminal device is receiving or needs to receive the PWS notification, and / or that the reception of the PWS notification by the terminal device is not completed or terminated, in response to one or more ofthe terminal device receiving scheduling information of a PWS system information block, SIB, for delivering the PWS notification;the terminal device receiving a paging message and / or DCI, which indicates that the PWS notification is being delivered;a time elapsed since the last reception of the PWS notification by the terminal device is less than or equal to a first threshold (e.g., X seconds, etc.);the terminal device having not received all of warning message segments for the PWS notification; andorthe terminal device being not informed of that the delivery of the PWS notification iscompleted or terminated.

[0080] In accordance with an exemplary embodiment, the information about the PWS notification may indicate that the PWS notification is not being delivered, and / or that the terminal device is not receiving or needs not to receive the PWS notification, and / or that the reception of the PWS notification by the terminal device is completed or terminated, in response to one or more of:the terminal device receiving no scheduling information of a PWS SIB for delivering the PWS notification;the terminal device receiving no paging message and / or DCI, which indicates that the PWS notification is being delivered;a time elapsed since the last PWS notification received by the terminal device is equal to or more than a second threshold (e.g., Y seconds, etc.);the terminal device having received all of warning message segments for the PWS notification; andorthe terminal device being informed of that the delivery of the PWS notification is completed or terminated.

[0081] In accordance with an exemplary embodiment, the information about the PWS notification may be determined by a first layer of the terminal device. In an embodiment, the first layer may comprise an AS layer.

[0082] In accordance with an exemplary embodiment, the one or more actions performed by the terminal device may comprise: transmitting, by the first layer of the terminal device, first information to a second layer higher than the first layer of the terminal device. In an embodiment, the first information may indicate one or more of:whether the PWS notification is being delivered;whether the terminal device is receiving or needs to receive the PWS notification; whether the reception of the PWS notification by the terminal device is completed or terminated;a type of the PWS notification and / or a message identifier of the PWS notification and / or a serial number of the PWS notification, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification; andorwhether the terminal device is in a PWS service area of the PWS notification.

[0083] In accordance with an exemplary embodiment, the one or more actions performed by the terminal device may further comprise: determining, by the second layer of the terminal device, not to transmit a service message (e.g., a service request, etc.) to the first layer of the terminal device, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notificationand / or the reception of the PWS notification by the terminal device is not completed or terminated, and when the PWS notification is prioritized over the service message.

[0084] In accordance with an exemplary embodiment, the one or more actions performed by the terminal device may further comprise: determining, by the second layer of the terminal device, to postpone transmitting the service message to the first layer of the terminal device, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, and when the PWS notification is prioritized over the service message.

[0085] In accordance with an exemplary embodiment, the one or more actions performed by the terminal device may further comprise: determining, by the second layer of the terminal device, to transmit the service message to the first layer of the terminal device, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, but the service message is prioritized over the PWS notification.

[0086] In accordance with an exemplary embodiment, the one or more actions performed by the terminal device may further comprise: determining, by the second layer of the terminal device, to transmit the service message to the first layer of the terminal device, when the PWS notification is not being delivered and / or the terminal device is not receiving the PWS notification and / or the reception of the PWS notification by the terminal device is completed or terminated.

[0087] In accordance with an exemplary embodiment, when the second layer of the terminal device determines to transmit the service message to the first layer of the terminal device, the one or more actions performed by the terminal device may further comprise: transmitting, by the second layer of the terminal device, second information to the first layer of the terminal device. In an embodiment, the second information may indicate that the service message is prioritized over one or more PWS notifications.

[0088] In accordance with an exemplary embodiment, the one or more actions performed by the terminal device may further comprise: determining, by the first layer of the terminal device, not to initiate RRC connection establishment to transmit a service message (e.g., a service request, etc.), when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, and when the PWS notification is prioritized over the service message.

[0089] In accordance with an exemplary embodiment, the one or more actions performed by the terminal device may further comprise: determining, by the first layer of the terminal device, to postpone initiating the RRC connection establishment to transmit the service message, when the PWSnotification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, and when the PWS notification is prioritized over the service message.

[0090] In accordance with an exemplary embodiment, the one or more actions performed by the terminal device may further comprise: determining, by the first layer of the terminal device, not to initiate the RRC connection establishment to transmit the service message, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, and when the service message is prioritized over the PWS notification but one or more other PWS notifications prioritized over the service message are being delivered to the terminal device or received by the terminal device.

[0091] In accordance with an exemplary embodiment, the one or more actions performed by the terminal device may further comprise: determining, by the first layer of the terminal device, to postpone initiating the RRC connection establishment to transmit the service message, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, and when the service message is prioritized over the PWS notification but the one or more other PWS notifications prioritized over the service message are being delivered to the terminal device or received by the terminal device.

[0092] In accordance with an exemplary embodiment, the one or more actions performed by the terminal device may further comprise: determining, by the first layer of the terminal device, to initiate the RRC connection establishment to transmit the service message, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, but the service message is prioritized over the PWS notification and no other PWS notifications prioritized over the service message are being delivered to the terminal device or received by the terminal device.

[0093] In accordance with an exemplary embodiment, the one or more actions performed by the terminal device may further comprise: determining, by the first layer of the terminal device, to initiate the RRC connection establishment to transmit the service message, when the PWS notification is not being delivered and / or the terminal device is not receiving the PWS notification and / or the reception of the PWS notification by the terminal device is completed or terminated.

[0094] In accordance with an exemplary embodiment, when the first layer of the terminal device determines to initiate the RRC connection establishment to transmit the service message, the one or more actions performed by the terminal device may further comprise: transmitting third information to a first network node. In an embodiment, the third information may indicate whether the receptionof the PWS notification by the terminal device is completed or terminated, and / or whether UL transmission of the terminal device is prioritized over one or more PWS notifications.

[0095] In accordance with an exemplary embodiment, when the first layer of the terminal device determines to postpone initiating or not to initiate the RRC connection establishment to transmit the service message, the one or more actions performed by the terminal device may further comprise one or more of: transmitting, by the first layer of the terminal device, fourth information to the second layer of the terminal device, where the fourth information may indicate that it is not allowed to transmit the service message for a period of time; and-a prioritizing, by the first layer of the terminal device, PWS notification reception over EDT, when the PWS notification reception and the EDT are at least partially overlapped in time.

[0096] In accordance with an exemplary embodiment, when a service message is transmitted by the terminal device towards a second network node, the one or more actions performed by the terminal device may further comprise: transmitting, towards the second network node, information indicating that the service message is prioritized over one or more PWS notifications.

[0097] In accordance with an exemplary embodiment, when the terminal device is outside of a PWS service area of the PWS notification, and when the reception of the PWS notification by the terminal device is not completed or terminated, the one or more actions performed by the terminal device may further comprise: stopping receiving the PWS notification.

[0098] In accordance with an exemplary embodiment, the first network node may comprise an access network node (e.g., an eNB, etc.). In accordance with another exemplary embodiment, the second network node may comprise a core network node (e.g., an MME, etc.).

[0099] Fig.2 is a flowchart illustrating a method 200 according to some embodiments of the present disclosure. The method 200 illustrated in Fig.2 may be performed a first network node (e.g., an access network node such as a base station, an access point, etc.) or an apparatus communicatively coupled to the first network node. In accordance with an exemplary embodiment, the first network node may be configured to provide network services to one or more terminal devices and optionally facilitate communications between the one or more terminal devices and a core network node.

[0100] According to the exemplary method 200 illustrated in Fig.2, the first network node may obtain information about a PWS notification, as shown in block 202. The information about the PWS notification may indicate whether the PWS notification is being delivered, and / or whether a terminal device (e.g., the terminal device as described with respect to Fig.1) is receiving or needs to receive the PWS notification, and / or whether the reception of the PWS notification by the terminal device is completed or terminated. In accordance with an exemplary embodiment, the first network node may perform one or more actions, based at least in part on the information about the PWS notification, asshown in block 204. In an embodiment, the one or more actions performed by the first network node may comprise determining whether to transmit a paging message (e.g., a paging request, etc.) for the terminal device, and / or determining whether to postpone transmitting the paging message, etc.

[0101] In accordance with an exemplary embodiment, the first network node may obtain at least part of the information about the PWS notification by: receiving, from the terminal device, information indicates whether the reception of the PWS notification by the terminal device is completed or terminated, and / or whether UL transmission of the terminal device is prioritized over one or more PWS notifications.

[0102] In accordance with an exemplary embodiment, when the terminal device needs to receive the PWS notification, the one or more actions performed by the first network node may comprise: releasing the terminal device to an RRC idle mode or an RRC inactive mode to receive the PWS notification.

[0103] In accordance with an exemplary embodiment, the PWS notification may be prioritized over a message which triggers the terminal device to enter an RRC connected mode.

[0104] In accordance with an exemplary embodiment, when the first network node releases the terminal device to an RRC idle mode or an RRC inactive mode to receive the PWS notification, the one or more actions performed by the first network node may comprise transmitting, to a second network node, information which may indicate one or more of: a cause of releasing the terminal device to the RRC idle mode or the RRC inactive mode; and-or a type and / or a message identifier and / or a serial number of the PWS notification which is being delivered to the terminal device or being received by the terminal device or to be received by the terminal device.

[0105] In accordance with an exemplary embodiment, the one or more actions performed by the first network node may comprise one or more of: transmitting at least part of the information about the PWS notification to a second network node (e.g., a core network node such as an MME, etc.); and or updating the at least part of the information about the PWS notification at the second network node, when delivery status of the PWS notification changes.

[0106] In accordance with an exemplary embodiment, the first network node may receive a paging message (e.g., a paging request, etc.) for the terminal device from a second network node. In an embodiment, the paging message may include information indicating whether the page message is prioritized over one or more PWS notifications.

[0107] In accordance with an exemplary embodiment, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, and when the first network node receives a paging message for the terminal device from a second network node, the one or moreactions performed by the first network node may comprise: determining whether to postpone transmitting the paging message to the terminal device for a period of time or until delivery of the PWS notification is completed or terminated.

[0108] In accordance with an exemplary embodiment, when the PWS notification is prioritized over the page message, the first network node may determine to postpone transmitting the paging message to the terminal device.

[0109] In accordance with an exemplary embodiment, when the page message is prioritized over the PWS notification and / or when MT EDT is applicable to delivery of DL transmission of the terminal device, the first network node may determine not to postpone transmitting the paging message to the terminal device.

[0110] Fig.3 is a flowchart illustrating a method 300 according to some embodiments of the present disclosure. The method 300 illustrated in Fig.3 may be performed a second network node (e.g., a core network node such as an MME, etc.) or an apparatus communicatively coupled to the second network node. In accordance with an exemplary embodiment, the second network node may be configured to provide network functions and application services to one or more terminal devices, e.g., via one or more access network nodes.

[0111] According to the exemplary method 300 illustrated in Fig.3, the second network node may receive at least part of information about a PWS notification from a first network node (e.g., the first network node as described with respect to Fig.2), as shown in block 302. The information about the PWS notification may indicate whether the PWS notification is being delivered, and / or whether a terminal device (e.g., the terminal device as described with respect to Fig.1) is receiving or needs to receive the PWS notification, and / or whether the reception of the PWS notification by the terminal device is completed or terminated. In accordance with an exemplary embodiment, the second network node may perform one or more actions, based at least in part on the information about the PWS notification, as shown in block 304. In an embodiment, the one or more actions performed by the second network node may comprise determining whether to transmit a paging message (e.g., a paging request, etc.) for the terminal device, and / or determining whether to postpone transmitting the paging message, etc.

[0112] In accordance with an exemplary embodiment, when delivery status of the PWS notification changes, the at least part of the information about the PWS notification may be received by the second network node from the first network node.

[0113] In accordance with an exemplary embodiment, when the terminal device is released to an RRC idle mode or an RRC inactive mode to receive the PWS notification, the one or more actions performed by the second network node may comprise receiving, from the first network node,information which may indicate one or more of: a cause of releasing the terminal device to the RRC idle mode or the RRC inactive mode; and-or a type and / or a message identifier and / or a serial number of the PWS notification which is being delivered to the terminal device or being received by the terminal device or to be received by the terminal device.

[0114] In accordance with an exemplary embodiment, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, and when the second network node receives a DL data notification for the terminal device, the one or more actions performed by the second network node may comprise: determining whether to postpone transmitting a paging message (e.g., a paging request, etc.) for the terminal device.

[0115] In accordance with an exemplary embodiment, the DL data notification for the terminal device may include information indicating whether the PWS notification is prioritized over DL data for the terminal device.

[0116] In accordance with an exemplary embodiment, when the PWS notification is prioritized over DL data for the terminal device, the second network node may determine to postpone transmitting the paging message for the terminal device.

[0117] In accordance with an exemplary embodiment, when the second network node determines to postpone transmitting the paging message for the terminal device, the one or more actions performed by the second network node may comprise one or more of: postponing transmitting the paging message for the terminal device over SI interface for a period of time or until delivery of the PWS notification is completed or terminated; and~or_postponing transmitting the paging message for the terminal device to the first network node or all network nodes which serve an area where the PWS notification is being delivered.

[0118] In accordance with an exemplary embodiment, when DL data for the terminal device is prioritized over the PWS notification, the second network node may determine not to postpone transmitting the paging message for the terminal device.

[0119] In accordance with an exemplary embodiment, when the second network node determines not to postpone transmitting the paging message for the terminal device, the one or more actions performed by the second network node may comprise: transmitting the paging message for the terminal device to one or more network nodes including the first network node.

[0120] In accordance with an exemplary embodiment, the paging message may include information which may indicate whether the page message is prioritized over one or more PWS notifications.

[0121] The various blocks shown in Fig.1, Fig.2 and Fig.3 may be viewed as method steps, and / oras operations that result from operation of computer program code, and / or as a plurality of coupled logic circuit elements constructed to carry out the associated function(s). The schematic flow chart diagrams described above are generally set forth as logical flow chart diagrams. As such, the depicted order and labeled steps are indicative of specific embodiments of the presented methods. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated methods. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown.

[0122] Fig.4 is a block diagram illustrating an apparatus 400 according to various embodiments of the present disclosure. As shown in Fig.4, the apparatus 400 may comprise one or more processors such as processing circuitry 401 and one or more memories such as memory 402 storing computer program codes 403. The memory 402 may be non-transitory machine / processor / computer readable storage medium. In accordance with some exemplary embodiments, the apparatus 400 may be implemented as an integrated circuit chip or module that can be plugged or installed into a terminal device as described with respect to Fig.1, or a first network node as described with respect to Fig.2, or a second network node as described with respect to Fig.3. In such cases, the apparatus 400 may be implemented as a terminal device as described with respect to Fig.1, or a first network node as described with respect to Fig.2, or a second network node as described with respect to Fig.3.

[0123] In some implementations, the one or more memories 402 and the computer program codes 403 may be configured to, with the processing circuitry 401, cause the apparatus 400 at least to perform any operation of the method as described in connection with Fig.1. In other implementations, the one or more memories 402 and the computer program codes 403 may be configured to, with the processing circuitry 401, cause the apparatus 400 at least to perform any operation of the method as described in connection with Fig.2. In other implementations, the one or more memories 402 and the computer program codes 403 may be configured to, with the processing circuitry 401, cause the apparatus 400 at least to perform any operation of the method as described in connection with Fig.3. Alternatively or additionally, the one or more memories 402 and the computer program codes 403 may be configured to, with the processing circuitry 401, cause the apparatus 400 at least to perform more or less operations to implement the proposed methods according to the exemplary embodiments of the present disclosure.

[0124] Fig.5 shows an example of a communication system 500 in accordance with some embodiments.

[0125] In the example, the communication system 500 includes a telecommunications network 502 that includes an access network 504, such as a radio access network (RAN), and a core network 506, which includes one or more core network nodes 508. The access network 504 includes one ormore access network nodes or base stations of various types, access network nodes 510A and 51 OB are depicted (which may be collectively referred to as network nodes 510), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 504 may include more than one access network technology. The network nodes 510 of access network 504 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 512A, 512B, 512C, and 512D (one or more of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections.

[0126] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 502 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 502 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 502, including one or more access network nodes 510 and / or core network nodes 508.

[0127] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.

[0128] The network nodes 510 facilitate direct or indirect connection of one or more UEs 512 to the core network 506 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagneticwaves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 500 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 500 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0129] The UEs 512 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 510 and other communication devices. Similarly, the network nodes 508, 510 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 502) with the UEs 512 and / or with other network nodes or equipment in the telecommunications network 502 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 502. More specifically, UEs 512 may send messages, data, and / or other signals to network nodes 508, 510 or other elements of the telecommunications network 502 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 508, 510 may send messages, data, and other signals to UEs 512, other network nodes 508, 510, and other devices in telecommunications network 502 directly or indirectly. As one specific example, a core network node 508 may transmit a particular message to a UE 512 by transmitting the message to an access network node 510 that will then transmit the message to the intended UE 512. Similarly, a core network node 508 may receive a particular message from a UE 512 by receiving the message from an access network node 510 that itself received the message from the UE 512.

[0130] In the depicted example, the core network 506 connects elements of the access network 504 (e.g., one or more of the network nodes 510) to one or more host computing systems, such as host 516. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 506 includes one or more core network nodes (e.g., core network node 508) of various types, one or more of which may be generally referred to as network nodes 508. Network nodes 508 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 508.Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0131] The host 516 may be under the ownership or control of a service provider other than an operator or provider of the access network 504 and / or the telecommunications network 502. The host 516 may be operated by the service provider or on behalf of the service provider. The host 516 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0132] As a whole, the communication system 500 of Fig.5 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 500 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 500 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 500 supporting different standards, protocols, or rule sets.

[0133] As one example, in certain embodiments, access network 504 may contain some access network nodes 510 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 510 support (or the same access network nodes 510 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 502 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 504 and / or a corenetwork 506 that supports multiple different standard generations or may include multiple access networks 504 and / or multiple core networks 506 with individual networks 504, 506 supporting different standard generations.

[0134] Telecommunications network 502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 502. For example, the telecommunications network 502 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0135] In some examples, one or more of the UEs 512 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 504. Additionally, a UE may be configured for operating in single- or multi -RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi -radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0136] In the example, the hub 514 communicates with the access network 504 to facilitate indirect communication between one or more UEs (e.g., UE 512C and / or 512D) and network nodes (e.g., network node 510B). In some examples, the hub 514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 514 may be a broadband router enabling access to the core network 506 for the UEs. As another example, the hub 514 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 510, or by executable code, script, process, or other instructions in the hub 514.

[0137] As another example, the hub 514 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 514 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 514 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 514 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0138] The hub 514 may have a constant / persistent or intermittent connection to the network node510B. The hub 514 may also allow for a different communication scheme and / or schedule between the hub 514 and UEs (e.g., UE 512C and / or 512D), and between the hub 514 and the core network 506. In other examples, the hub 514 is connected to the core network 506 and / or one or more UEs via a wired connection. Moreover, the hub 514 may be configured to connect to an M2M service provider over the access network 504 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 510 while still connected via the hub 514 via a wired or wireless connection. In some embodiments, the hub 514 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 510B. In other embodiments, the hub 514 may be a non-dedicated hub -that is, a device which is capable of operating to route communications between the UEs and network node 51 OB, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0139] Fig.6 is another example of a communication system 600 according to some embodiments. As used herein, the communication system 600 includes multiple access points (APs) 610 (with four exemplary APs 610A, 610B, 610C, and 610D being depicted) and multiple wireless devices, referred to in the context of communication system 600 as stations (STAs) 612 (referred to individually as STA 612A, STA 612B, STA 612C, STA 612D, and STA 612E). STA 612A is served by AP 610A in a first basic service set (BSS) 620 A. STA 610B and STA 610C are served by AP 610B in a second BSS, BSS 620B. STA 612D is served by AP 610C in a third BSS, BSS 620C. STA 612E is served by AP 610D in a fourth BSS, BSS 620D. Stations 612 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 612 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0140] Each of STAs 612 may connect through a radio link to one of APs 610. For example, depending on location or channel conditions experienced by a given STA 612, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0141] Each AP 610 may provide data connectivity to STAs 612 connected to a particular AP 610. As illustrated, APs 610 may be connected to a data network 630. In this way, APs 610 may alsoprovide data connectivity between STAs 612 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 612 and its serving AP 610 may be used for providing various kinds of services to STA 612, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 612 and / or on a device linked to STA 612. By way of example, Fig.6 illustrates an application service platform 632 provided in data network 630. The application(s) executed on STA 612 and / or on one or more other devices linked to STA 612 may use the radio link for data communication with one or more other STA 612 and / or the application service platform 632, thereby enabling utilization of the corresponding service(s) at STA 612.

[0142] Fig.7 shows a wireless device 700, which may be configured to operate in communication system 500 of Fig.5 or in communication system 600 of Fig.6. The wireless device 700 may be alternatively referred to as a UE 700, like a UE 512 within the context of communication system 500, or as a station (STA) 700 or as a non-access-point station (non-AP STA) 700, like a STA 612 within the context of the communication system 600, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptopmounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0143] A wireless device 700 may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 700 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 700 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 700 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smartpower meter).

[0144] In particular embodiments, wireless device 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input / output interface 706, a power source 708, a memory 710, a communication interface 712, and / or any other component, or any combination thereof. Certain embodiments of wireless device 700 may include all or a subset of the components shown in Fig.7. The level of integration between the components may vary from one embodiment of wireless device 700 to another. In general, in a particular embodiment of wireless device 700, processing circuitry 702, input / output interface 706, power source 708, memory 710, and communication interface 712 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 700. Further, certain embodiments of wireless devices 700 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0145] The processing circuitry 702 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 710. The processing circuitry 702 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 702 may include multiple central processing units (CPUs).

[0146] In the example, the input / output interface 706 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 700. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0147] In some embodiments, the power source 708 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 708 may further include power circuitry for delivering power from the power source 708 itself, and / or an external power source, to the various parts of wireless device 700 via input circuitry or an interface such as an electrical power cable. Power source 708 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 700 to which power is supplied.

[0148] The memory 710 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 710 includes one or more programs 714, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 716. The memory 710 may store, for use by wireless device 700, any of a variety of various operating systems or combinations of operating systems.

[0149] The memory 710 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 710 may allow wireless device 700 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 710, which may be or comprise a device-readable storage medium.

[0150] The processing circuitry 702 may be configured to communicate with an access network or other network via or using the communication interface 712. The communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722. The communication interface 712 may include one or more transceiversused to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 718 and / or a receiver 720 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0151] In the illustrated embodiment, communication functions of the communication interface 712 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, locationbased communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0152] In particular embodiments, wireless device 700 may provide an output of data captured via a sensor, through its communication interface 712, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 700 can be communicated through a wireless connection to a network node via another wireless device 700. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0153] As another example, wireless device 700 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 700 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0154] Wireless device 700, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to,wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 700 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 700 shown in Fig.7.

[0155] As yet another specific example, in an loT scenario, wireless device 700 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 700 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 700 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 700 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0156] In practice, any number of wireless devices 700 may be used together with respect to a single use case. For example, a first wireless device 700 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 700 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 700 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 700 can also include more than one of the functionalities described above. For example, wireless device 700 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0157] Fig.8 shows a network node 800 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in atelecommunications network. In accordance with respective embodiments, network node 800 may be configured to operate in communication system 500 of Fig.5, like network nodes 508 or 510, or in communication system 600 of Fig.6, like an AP 610 or a station 612. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0158] Network nodes 800 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 800 may be a relay node or a relay donor node controlling a relay. Network nodes 800 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0159] Other examples of network nodes 800 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0160] In particular embodiments, network node 800 includes a processing circuitry 802, a memory 804, a communication interface 806, and a power source 808. In general, in a particular embodiment of network node 800, processing circuitry 802, memory 804, communication interface 806, and power source 808 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 800.

[0161] The network node 800 may be composed of multiple distinct network entities (e.g., a NodeB entity and an RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 800 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 800 may be configured to supportmultiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 804 or portions of memory 804 for different RATs) and some components may be reused (e.g., a same antenna 810 may be shared by different RATs). The network node 800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 800, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 800.

[0162] The processing circuitry 802 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 804, to provide network node 800 functionality.

[0163] In some embodiments, the processing circuitry 802 includes a system on a chip (SOC). In some embodiments, the processing circuitry 802 includes one or more of radio frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814. In some embodiments, the RF transceiver circuitry 812 and the baseband processing circuitry 814 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 812 and baseband processing circuitry 814 may be on the same chip or set of chips, boards, or units.

[0164] The memory 804 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 802. The memory 804 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 802 and utilized by the network node 800. The memory 804 may be used to store any calculations made by the processing circuitry 802 and / or any data received via the communication interface 806. In some embodiments, the processing circuitry 802 and memory 804is integrated.

[0165] The communication interface 806 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 806 comprises port(s) / terminal(s) 816 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 800 may be capable of wireless communication and communication interface 806 may also include radio front-end circuitry 818 that may be coupled to, or in certain embodiments a part of, an antenna 810. Particular embodiments of radio front-end circuitry 818 include filter(s) 820 and amplifier(s) 822. The radio front-end circuitry 818 may be connected to an antenna 810 and processing circuitry 802. The radio front-end circuitry may be configured to condition signals communicated between antenna 810 and processing circuitry 802. The radio front-end circuitry 818 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 818 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 820 and / or amplifiers 822. The radio signal(s) may then be transmitted via the antenna 810. Similarly, when receiving data, the antenna 810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 818. The digital data may be passed to the processing circuitry 802. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0166] In certain alternative embodiments, network node 800 may be capable of wireless communication but does not include separate radio front-end circuitry 818, instead, the processing circuitry 802 includes radio front-end circuitry and is connected to the antenna 810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 812 is part of the communication interface 806. In still other embodiments, the communication interface 806 includes one or more ports or terminals 816, the radio front-end circuitry 818, and the RF transceiver circuitry 812, as part of a radio unit (not shown), and the communication interface 806 communicates with the baseband processing circuitry 814, which is part of a digital unit (not shown).

[0167] The antenna 810 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 810 may be coupled to the radio front-end circuitry 818 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 810 is separate from the network node 800 and connectable to the network node 800 through one or more interfaces or ports.

[0168] The antenna 810, communication interface 806, and / or the processing circuitry 802 may be configured to perform some or all of the receiving operations and / or obtaining operations describedherein as being performed by the network node 800. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 810, the communication interface 806, and / or the processing circuitry 802 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 800. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0169] The power source 808 provides power to the various components of network node 800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 808 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 800 with power for performing the functionality described herein. For example, the network node 800 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 808. As a further example, the power source 808 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0170] Embodiments of the network node 800 may include additional components beyond those shown in Fig.8 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 800 may include user interface equipment to allow input of information into the network node 800 and to allow output of information from the network node 800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 800.

[0171] Fig.9 is a block diagram illustrating a virtualization environment 900 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 900 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In someembodiments, the virtualization environment 900 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0172] Applications 902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 900 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0173] Hardware 904 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 908A and VM 908B (which may be collectively referred to as VMs 908), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 906 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 908.

[0174] The VMs 908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 906. Different embodiments of the instance of a virtual appliance 902 may be implemented on one or more of VMs 908, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0175] In the context of NFV, each of the VMs 908 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 908, and that part of hardware 904 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 908 on top of the hardware 904 and corresponds to an application 902.

[0176] Hardware 904 may be implemented in a standalone network node with generic or specific components. Hardware 904 may implement some functions via virtualization. Alternatively, hardware 904 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 910, which,among others, oversees lifecycle management of applications 902. In some embodiments, hardware 904 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 912 which may alternatively be used for communication between hardware nodes and radio units.

[0177] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0178] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits providedby such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0179] In general, the various exemplary embodiments may be implemented in hardware or special purpose chips, circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto. While various aspects of the exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0180] As such, it should be appreciated that at least some aspects of the exemplary embodiments of the disclosure may be practiced in various components such as integrated circuit chips and modules. It should thus be appreciated that the exemplary embodiments of this disclosure may be realized in an apparatus that is embodied as an integrated circuit, where the integrated circuit may comprise circuitry (as well as possibly firmware) for embodying at least one or more of a data processor, a digital signal processor, baseband circuitry and radio frequency circuitry that are configurable so as to operate in accordance with the exemplary embodiments of this disclosure.

[0181] It should be appreciated that at least some aspects of the exemplary embodiments of the disclosure may be embodied in computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device. The computer executable instructions may be stored on a computer readable medium such as a hard disk, optical disk, removable storage media, solid state memory, random access memory (RAM), etc. As will be appreciated by one of skill in the art, the function of the program modules may be combined or distributed as desired in various embodiments. In addition, the function may be embodied in whole or partly in firmware or hardware equivalents such as integrated circuits, FPGAs, and the like.

[0182] The present disclosure includes any novel feature or combination of features disclosed herein either explicitly or any generalization thereof. Various modifications and adaptations to the foregoing exemplary embodiments of this disclosure may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanyingdrawings. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of this disclosure.

Claims

CLAIMSWhat is claimed is:

1. A method (100) performed by a terminal device, comprising:determining (102) information about a public warning system, PWS, notification, wherein the information about the PWS notification indicates whether the PWS notification is being delivered, and / or whether the terminal device is receiving or needs to receive the PWS notification, and / or whether the reception of the PWS notification by the terminal device is completed or terminated; and performing (104) one or more actions, based at least in part on the information about the PWS notification.

2. The method according to claim 1, wherein the information about the PWS notification indicates that the PWS notification is being delivered, and / or that the terminal device is receiving or needs to receive the PWS notification, and / or that the reception of the PWS notification by the terminal device is not completed or terminated, in response to one or more of:the terminal device receiving scheduling information of a PWS system information block, SIB, for delivering the PWS notification;the terminal device receiving a paging message and / or downlink control information, DCI, which indicates that the PWS notification is being delivered;a time elapsed since the last reception of the PWS notification by the terminal device is less than or equal to a first threshold;the terminal device having not received all of warning message segments for the PWS notification; andorthe terminal device being not informed of that the delivery of the PWS notification is completed or terminated.

3. The method according to claim 1 or 2, wherein the information about the PWS notification indicates that the PWS notification is not being delivered, and / or that the terminal device is not receiving or needs not to receive the PWS notification, and / or that the reception of the PWS notification by the terminal device is completed or terminated, in response to one or more of:the terminal device receiving no scheduling information of a PWS SIB for delivering the PWS notification;the terminal device receiving no paging message and / or DCI which indicates that the PWS notification is being delivered;a time elapsed since the last PWS notification received by the terminal device is equal to or more than a second threshold;the terminal device having received all of warning message segments for the PWS notification; andorthe terminal device being informed of that the delivery of the PWS notification is completed or terminated.

4. The method according to any of claims 1-3, wherein the information about the PWS notification is determined by a first layer of the terminal device, and wherein the first layer comprises an access stratum, AS, layer.

5. The method according to claim 4, wherein the one or more actions performed by the terminal device comprise:transmitting, by the first layer of the terminal device, first information to a second layer higher than the first layer of the terminal device, wherein the first information indicates one or more of whether the PWS notification is being delivered;whether the terminal device is receiving or needs to receive the PWS notification; whether the reception of the PWS notification by the terminal device is completed or terminated;a type of the PWS notification and / or a message identifier of the PWS notification and / or a serial number of the PWS notification, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification; andorwhether the terminal device is in a PWS service area of the PWS notification.

6. The method according to claim 5, wherein the one or more actions performed by the terminal device further comprise:determining, by the second layer of the terminal device, not to transmit a service message to the first layer of the terminal device, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, and when the PWS notification is prioritized over the service message; ordetermining, by the second layer of the terminal device, to postpone transmitting the service message to the first layer of the terminal device, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by44the terminal device is not completed or terminated, and when the PWS notification is prioritized over the service message; ordetermining, by the second layer of the terminal device, to transmit the service message to the first layer of the terminal device, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, but the service message is prioritized over the PW S notification; ordetermining, by the second layer of the terminal device, to transmit the service message to the first layer of the terminal device, when the PW S notification is not being delivered and / or the terminal device is not receiving the PWS notification and / or the reception of the PWS notification by the terminal device is completed or terminated.

7. The method according to claim 6, wherein when the second layer of the terminal device determines to transmit the service message to the first layer of the terminal device, the one or more actions performed by the terminal device further comprise:transmitting, by the second layer of the terminal device, second information to the first layer of the terminal device, wherein the second information indicates that the service message is prioritized over one or more PWS notifications.

8. The method according to any of claims 4-7, wherein the one or more actions performed by the terminal device further comprise:determining, by the first layer of the terminal device, not to initiate radio resource control, RRC, connection establishment to transmit a service message, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, and when the PWS notification is prioritized over the service message; ordetermining, by the first layer of the terminal device, to postpone initiating the RRC connection establishment to transmit the service message, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, and when the PWS notification is prioritized over the service message; ordetermining, by the first layer of the terminal device, not to initiate the RRC connection establishment to transmit the service message, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by45the terminal device is not completed or terminated, and when the service message is prioritized over the PWS notification but one or more other PWS notifications prioritized over the service message are being delivered to the terminal device or received by the terminal device; ordetermining, by the first layer of the terminal device, to postpone initiating the RRC connection establishment to transmit the service message, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, and when the service message is prioritized over the PWS notification but the one or more other PWS notifications prioritized over the service message are being delivered to the terminal device or received by the terminal device; ordetermining, by the first layer of the terminal device, to initiate the RRC connection establishment to transmit the service message, when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, but the service message is prioritized over the PWS notification and no other PWS notifications prioritized over the service message are being delivered to the terminal device or received by the terminal device; ordetermining, by the first layer of the terminal device, to initiate the RRC connection establishment to transmit the service message, when the PWS notification is not being delivered and / or the terminal device is not receiving the PWS notification and / or the reception of the PWS notification by the terminal device is completed or terminated.

9. The method according to claim 8, wherein when the first layer of the terminal device determines to initiate the RRC connection establishment to transmit the service message, the one or more actions performed by the terminal device further comprise:transmitting third information to a first network node, wherein the third information indicates whether the reception of the PWS notification by the terminal device is completed or terminated, and / or whether uplink, UL, transmission of the terminal device is prioritized over one or more PWS notifications.

10. The method according to claim 8 or 9, wherein when the first layer of the terminal device determines to postpone initiating or not to initiate the RRC connection establishment to transmit the service message, the one or more actions performed by the terminal device further comprise one or more oftransmitting, by the first layer of the terminal device, fourth information to the second layer of the terminal device, wherein the fourth information indicates that it is not allowed to transmit the service message for a period of time; andorprioritizing, by the first layer of the terminal device, PWS notification reception over early data transmission, EDT, when the PWS notification reception and the EDT are at least partially overlapped in time.

11. The method according to any of claims 1-10, wherein when a service message is transmitted by the terminal device towards a second network node, the one or more actions performed by the terminal device further comprise:transmitting, towards the second network node, information indicating that the service message is prioritized over one or more PWS notifications.

12. The method according to any of claims 1-11, wherein when the terminal device is outside of a PWS service area of the PWS notification, and when the reception of the PWS notification by the terminal device is not completed or terminated, the one or more actions performed by the terminal device further comprise:stopping receiving the PWS notification.

13. The method according to any of claims 1-12, wherein the first network node comprises an access network node, and / or the second network node comprises a core network node.

14. A method (200) performed by a first network node, comprising:obtaining (202) information about a public warning system, PWS, notification, wherein the information about the PWS notification indicates whether the PWS notification is being delivered, and / or whether a terminal device is receiving or needs to receive the PW S notification, and / or whether the reception of the PWS notification by the terminal device is completed or terminated; and performing (204) one or more actions, based at least in part on the information about the PWS notification.

15. The method according to claim 14, wherein the first network node obtains at least part of the information about the PWS notification by:receiving, from the terminal device, information indicates whether the reception of the PWS notification by the terminal device is completed or terminated, and / or whether uplink, UL, transmission of the terminal device is prioritized over one or more PWS notifications.

16. The method according to claim 14 or 15, wherein when the terminal device needs to receive the PWS notification, the one or more actions performed by the first network node comprise:releasing the terminal device to a radio resource control, RRC, idle mode or an RRC inactive mode to receive the PWS notification.

17. The method according to claim 16, wherein the PWS notification is prioritized over a message which triggers the terminal device to enter an RRC connected mode.

18. The method according to any of claims 14-17, wherein when the first network node releases the terminal device to an RRC idle mode or an RRC inactive mode to receive the PWS notification, the one or more actions performed by the first network node comprise:transmitting, to a second network node, information which indicates one or more of:a cause of releasing the terminal device to the RRC idle mode or the RRC inactive mode; andora type and / or a message identifier and / or a serial number of the PWS notification which is being delivered to the terminal device or being received by the terminal device or to be received by the terminal device.

19. The method according to any of claims 14-18, wherein the one or more actions performed by the first network node comprise one or more of:transmitting at least part of the information about the PWS notification to a second network node; andorupdating the at least part of the information about the PWS notification at the second network node, when delivery status of the PWS notification changes.

20. The method according to any of claims 14-19, further comprising:receiving a paging message for the terminal device from a second network node, wherein the paging message includes information indicating whether the page message is prioritized over one or more PWS notifications.4821. The method according to any of claims 14-20, wherein when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, and when the first network node receives a paging message for the terminal device from a second network node, the one or more actions performed by the first network node comprise:determining whether to postpone transmitting the paging message to the terminal device for a period of time or until delivery of the PWS notification is completed or terminated.

22. The method according to claim 21, wherein when the PWS notification is prioritized over the page message, the first network node determines to postpone transmitting the paging message to the terminal device; and / orwherein when the page message is prioritized over the PWS notification and / or when mobile terminated, MT, early data transmission, EDT, is applicable to delivery of downlink, DL, transmission of the terminal device, the first network node determines not to postpone transmitting the paging message to the terminal device.

23. The method according to any of claims 14-22, wherein the first network node comprises an access network node, and / or the second network node comprises a core network node.

24. A method (300) performed by a second network node, comprising:receiving (302) at least part of information about a public warning system, PWS, notification from a first network node, wherein the information about the PWS notification indicates whether the PWS notification is being delivered, and / or whether a terminal device is receiving or needs to receive the PWS notification, and / or whether the reception of the PWS notification by the terminal device is completed or terminated; andperforming (304) one or more actions, based at least in part on the information about the PWS notification.

25. The method according to claim 24, wherein when delivery status of the PWS notification changes, the at least part of the information about the PWS notification is received by the second network node from the first network node.

26. The method according to claim 24 or 25, wherein when the terminal device is released to a radio resource control, RRC, idle mode or an RRC inactive mode to receive the PWS notification, the one49or more actions performed by the second network node comprise:receiving, from the first network node, information which indicates one or more ofa cause of releasing the terminal device to the RRC idle mode or the RRC inactive mode; andora type and / or a message identifier and / or a serial number of the PWS notification which is being delivered to the terminal device or being received by the terminal device or to be received by the terminal device.

27. The method according to any of claims 24-26, wherein when the PWS notification is being delivered and / or the terminal device is receiving the PWS notification and / or the reception of the PWS notification by the terminal device is not completed or terminated, and when the second network node receives a downlink, DL, data notification for the terminal device, the one or more actions performed by the second network node comprise:determining whether to postpone transmitting a paging message for the terminal device.

28. The method according to claim 27, wherein the DL data notification for the terminal device includes information indicating whether the PWS notification is prioritized over DL data for the terminal device.

29. The method according to claim 27 or 28, wherein when the PWS notification is prioritized over DL data for the terminal device, the second network node determines to postpone transmitting the paging message for the terminal device.

30. The method according to any of claims 27-29, wherein when the second network node determines to postpone transmitting the paging message for the terminal device, the one or more actions performed by the second network node comprise one or more of:postponing transmitting the paging message for the terminal device over SI interface for a period of time or until delivery of the PWS notification is completed or terminated; andor postponing transmitting the paging message for the terminal device to the first network node or all network nodes which serve an area where the PWS notification is being delivered.

31. The method according to any of claims 27-30, wherein when DL data for the terminal device is prioritized over the PWS notification, the second network node determines not to postpone transmitting the paging message for the terminal device.5032. The method according to any of claims 27-31, wherein when the second network node determines not to postpone transmitting the paging message for the terminal device, the one or more actions performed by the second network node comprise:transmitting the paging message for the terminal device to one or more network nodes including the first network node.

33. The method according to claim 32, wherein the paging message includes information which indicates whether the page message is prioritized over one or more PWS notifications.

34. The method according to any of claims 24-33, wherein the first network node comprises an access network node, and / or the second network node comprises a core network node.

35. A terminal device (400), comprising processing circuitry (401) and one or more memories (402) storing computer program codes (403), the one or more memories (402) and the computer program codes (403) configured to, with the processing circuitry (401), cause the terminal device (400) at least to:determine information about a public warning system, PWS, notification, wherein the information about the PWS notification indicates whether the PWS notification is being delivered, and / or whether the terminal device is receiving or needs to receive the PWS notification, and / or whether the reception of the PWS notification by the terminal device is completed or terminated; and perform one or more actions, based at least in part on the information about the PWS notification.

36. The terminal device according to claim 35, wherein the one or more memories and the computer program codes are configured to, with the processing circuitry, cause the terminal device to perform the method according to any one of claims 2-13.

37. A first network node (400), comprising processing circuitry (401) and one or more memories (402) storing computer program codes (403), the one or more memories (402) and the computer program codes (403) configured to, with the processing circuitry (401), cause the first network node (400) at least to:obtain information about a public warning system, PWS, notification, wherein the information about the PWS notification indicates whether the PWS notification is being delivered, and / or whether51a terminal device is receiving or needs to receive the PWS notification, and / or whether the reception of the PWS notification by the terminal device is completed or terminated; andperform one or more actions, based at least in part on the information about the PWS notification.

38. The first network node according to claim 37, wherein the one or more memories and the computer program codes are configured to, with the processing circuitry, cause the first network node to perform the method according to any one of claims 15-23.

39. A second network node (400), comprising processing circuitry (401) and one or more memories (402) storing computer program codes (403), the one or more memories (402) and the computer program codes (403) configured to, with the processing circuitry (401), cause the second network node (400) at least to:receive at least part of information about a public warning system, PWS, notification from a first network node, wherein the information about the PWS notification indicates whether the PWS notification is being delivered, and / or whether a terminal device is receiving or needs to receive the PWS notification, and / or whether the reception of the PWS notification by the terminal device is completed or terminated; andperform one or more actions, based at least in part on the information about the PWS notification.

40. The second network node according to claim 39, wherein the one or more memories and the computer program codes are configured to, with the processing circuitry, cause the second network node to perform the method according to any one of claims 25-34.

41. A computer-readable medium comprising instructions that, when executed by processing circuitry (401), cause the processing circuitry (401) to carry out the method according to any one of claims 1-34.

42. A computer program product, comprising instructions that, when executed by processing circuitry (401), cause the processing circuitry (401) to carry out the method according to any one of claims 1-34.

43. A communication system comprising the terminal device according to any of claims 35-36, the first network node according to any of claims 37-38, and the second network node according to any of claims 39-40.52