Methods and apparatuses for paging during small data transmission session

Abstract

A method, system and apparatus are disclosed. A user equipment, UE, configured to communicate with a network node is provided. The UE is configured to receive a message indicating for the UE to terminate an ongoing small data transmission, SDT, procedure, terminate the SDT procedure based on the message, and after the SDT procedure has been terminated, receive a paging message.

Description

[0001] METHODS AND APPARATUSES FOR PAGING DURING SMALL DATA TRANSMISSION SESSION

[0002] TECHNICAL FIELD

[0003] The present disclosure relates to wireless communications, and in particular, to

[0004] 5 emergency paging with respect to an ongoing wireless communication small data transmission, SDT, session.

[0005] BACKGROUND

[0006] The Third Generation Partnership Project (3GPP) has developed and is developing

[0007] 10 standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes and between WDs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0008] Short Data Transmission (STD)

[0009] The Short Data Transmission (SDT) procedure enables the UE to send and receive small amounts of data while in RRC_INACTIVE without transitioning to RRC CONNECTED (see, for example, Chapter 18 of 3GPP 38.300 v!8.0.0).

[0010] 20 The procedure is started when the UE sends RRCResumeRequest and timer T319a {mslOO, ... ms4000} is started as described in 3GPP 38.331 v!8.0.0. The RRCResumeRequest may contain UL data, and further small data may be sent / received after the RRCResumeRequest. The procedure is terminated (successfully) with RRCRelease. During an SDT procedure the network / network node can transition to RRC_CONNECTED by sending RRCResume. An RSRP threshold can be configured to prevent the UE from attempting to send / receive small data in bad coverage (sdt-RSRP- Threshold).

[0011] When T319a expires, the SDT procedure may be terminated unsuccessfully and the UE goes to RRC IDLE with release cause 'RRC Resume failure'. Small data

[0012] 30 transmissions are typically performed for a very short time and cannot continue beyond T319a expiry.

[0013] During an ongoing SDT procedure, i.e., while T319a is running, the UE can receive Paging PDCCH (short message indication SI change or ETWS / CMAS indication), but the UE cannot receive Paging message on PDSCH (similar as in RRC CONNECTED)

[0014] During an ongoing SDT procedure the UE is assumed to be able to receive System Information (SI) on PDSCH (e.g. ETWS / CMAS warning messages), but further clarification in 3GPP TS 38.331 V18.0.0 may be needed.

[0015] Earthquake Tsunami Warning System (ETWS) / Commercial Mobil Alert System (CMAS)

[0016] ETWS and CMAS are warning systems, e.g., ETWS for earthquake and tsunami and CMAS for child abduction. These are regional system (e.g., ETWS in Japan and CMAS in USA) where regulatory requirements may apply.

[0017] ETWS / CMAS is an optional feature without UE capability signalling. As set out in clause 5.1 in 3GPP 38.306 V18.0.0 from 3GPP perspective, and as described in Table 1 below.

[0018] Table 1

[0019] The UE typically does not receive ETWS messages regularly, because these events are rare. But with CMAS there can be 24 hours type of warnings (e.g., child abduction or other emergency info) that is transmitted regularly. A user can opt out from certain CMAS warning types, except the presidential alert.

[0020] The network does not know if a UE is ETWS / CMAS capable, and can receive this information. Furthermore a user may opt out from receiving certain CMAS warnings, e.g. when they are sent frequently, except for a presidential alert. Thus, when the UE does not support ETWS / CMAS, or has opted out certain CMAS warnings, these dedicated transmissions may be useless

[0021] A UE supporting ETWS / CMAS may also be able to receive ETWS / CMAS when in RRC CONNECTED. The UE in RRC_CONNECTED is required to monitor the Paging PDCCH for ETWS / CMAS indication, i.e., indication that there is an ETWS / CMAS warning message on PDSCH to be received.

[0022] The warning messages can be received via system information:

[0023] • SIB6 (ETWS primary notification)

[0024] • SIB 7 (ETWS secondary notification)

[0025] • SIB8 (CMAS)

[0026] Or dedicated signalling via RRCReconfiguration message incl. dedicatedSystemlnformationDelivery.

[0027] When the UE is configured with a common search space on the active BWP in RRC_CONNECTED, then the UE receives the ETWS / CMAS warning messages by acquiring the system information on the active BWP, similar as UEs in RRC_IDLE / RRC_INACTIVE using the initial BWP to receive system information. In such case there is no need for dedicated signalling to convey the ETWS / CMAS warning messages to the UEs in RRC_CONNECTED. But in case the UE is not configured with a common search space on the active BWP, then the network has to send the ETWS / CMAS warning message(s) via dedicated signalling to the UE.

[0028] Multicast / Broadcast Service (MBS) multicast

[0029] 3GPP Rel-17 Multicast / Broadcast Service (MBS) enables the network to efficiently send the same data to a (large) group of UEs. There are two ways to convey the data to the UE: MBS broadcast and MBS multicast. MBS broadcast is supported in all RRC states. MBS multicast is supported in RRC CONNECTED (3GPP Rel-17) and RRC INACTIVE (3GPP Rel-18).

[0030] If the UE wants to receive multicast data the UE first has to join the multicast session (see 3GPP, e.g., .3GPP TS 23.247 section 7.2.1.3). The UE is then authorized and may receive the security keys to decrypt the multicast data.

[0031] After the UE has joined the multicast session the CN (e.g., core network) creates the session in RAN (e.g., UE context). After the CN has activated the session in the RAN and resources are allocated, downlink multicast transmissions can start. The CN can also deactivate the session, e.g., when there is no multicast data for some time. For the MBS session states, see 3GPP, e.g., 3GPP TS 23.247 section 4.1. In such cases, the RAN can decide to release the multicast UEs to RRC_IDLE or RRC_INACTIVE. When the session is activated again, the UEs may be (group) paged and return to RRC_CONNECTED mode to continue multicast data reception. The network includes a list of TMGIs (i.e., MBS session identities) in the Paging message, to indicate which multicast sessions are activated again.

[0032] Via UE capability signalling, the UE indicates to RAN whether it supports MBS multicast (dynamlcMultlcastPCell-r 17) or MBS multicast reception in RRC_INACTIVE (multicastlnactive-r 18).

[0033] When the UE is in RRC_INACTIVE and the MBS multicast session is activated again, the network can indicate inactiveReceptionAllowed for a TMGI in the Paging message, to indicate whether the UE can receive the session in RRC_INACTIVE or that the UE should resume to receive the session in RRC_CONNECTED.

[0034] However, exiting systems suffer from one or more problems. These problems include the following.

[0035] Problem 1: Handling of Paging message during SDT (network implementation)

[0036] When the SDT procedure is ongoing, the UE cannot receive a Paging message on PDSCH, i.e., this requires special handling of the Paging message by the network to ensure that the UE receives the Paging message.

[0037] Problem 2: ETWS / CMAS warnings sent via dedicated signalling (3GPP change)

[0038] ETWS / CMAS is an optional feature without UE capability signalling. Thus when the network sends ETWS / CMAS warnings via dedicated signalling to the UEs in RRC_CONNECTED this may cause unnecessary signalling when the UE does not support the feature, or when the UE has opted out for a certain CMAS warning type.

[0039] SUMMARY

[0040] Some embodiments advantageously provide methods, systems, and apparatuses for emergency paging with respect to an ongoing small data transmission, SDT, session. With respect to Problem 1: Handling of Paging message during SDT

[0041] • The network node sends RRCResume when receiving a Paging message for a UE in an ongoing SDT, i.e., transitions the UE to RRC CONNECTED.

[0042] • The network node sends the Paging message after RRCReject / RRCRelease when receiving a Paging message for a UE in an ongoing SDT, i.e., the UE receives the Paging message in RRC IDLE / RRC INACTIVE.

[0043] • When there is a group Paging message for a UE that has joined an MBS multicast session and the UE is in an ongoing SDT: o The UE does not support MBS multicast reception in RRC_INACTIVE, or the UE did not join the session yet, or the UE is not allowed to receive the session in RRC_INACTIVE, the network node sends RRC Resume, i.e., transitions the UE to RRC CONNECTED o Otherwise the network node sends Paging message after RRCReject / RRCRelease i.e., the UE receives the Paging message in RRC IDLE / RRC INACTIVE

[0044] With respect to Problem 2: ETWS / CMAS warnings send via dedicated signalling

[0045] • Via new UE capability signalling, the UE indicates if it supports ETWS, and the network node only sends ETWS warning message in dedicated message to UEs supporting ETWS.

[0046] • Via new UE capability signalling the UE indicates when it supports CMAS per warning type (and it has not opted out for the warning type). The network node only sends a type of CMAS warning message in a dedicated message to UEs the CMAS warning type. When the UE opts out from a CMAS warning type, the UE performs UE capability update after Detach and Attach.

[0047] The etwsAndCmasIndication is redefined or a new indication is introduced in the Short Message on Paging PDCCH: If the UE has an ongoing SDT procedure the UE terminates the procedure.

[0048] According to some embodiments, there is provided a network node configured to communicate with a user equipment (UE). The network node configured to, and / or comprising a radio interface and / or comprising processing circuitry is configured to determine to signal a paging message to the UE. The network node is configured to transmit a message to the UE, the message being configured to cause the UE to terminate an ongoing small data transmission, SDT, procedure. The network node is configured to transmit the paging message to the UE that is no longer participating in the SDT procedure.

[0049] According to some embodiments, there is provided a method implemented by a network node that is configured to communicate with a user equipment (UE). The method comprises determining to signal a paging message to the UE. The method comprises transmitting a message to the UE, the message being configured to cause the UE to terminate an ongoing small data transmission, SDT, procedure. The method comprises transmitting the paging message to the UE that is no longer participating in the SDT procedure. According to some embodiments, there is provided a user equipment (UE) configured to communicate with a network node. The UE is configured to, and / or comprising a radio interface and / or processing circuitry is configured to: receive a message indicating for the UE to terminate an ongoing small data transmission (SDT) procedure; terminate the SDT procedure based on the message; and after the SDT procedure has been terminated, receive a paging message.

[0050] According to some embodiments, there is provided a method implemented by a UE. The method comprises: receiving a message indicating for the UE to terminate an ongoing small data transmission (SDT) procedure; terminating the SDT procedure based on the message; and after the SDT procedure has been terminated, receiving a paging message.

[0051] According to some embodiments, there is provided a computer program, comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods described herein.

[0052] According to some embodiments, there is provided a computer program product comprising non transitory computer readable media having stored thereon a computer program as described above.

[0053] BRIEF DESCRIPTION OF THE DRAWINGS

[0054] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0055] FIG. 1 is a schematic diagram of an exemplary network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

[0056] FIG. 2 is a block diagram of a host computer communicating via a network node with a user equipment over an at least partially wireless connection according to some embodiments of the present disclosure;

[0057] FIG. 3 is a diagram illustrating exemplary arrangements and methods implemented in a communication system including a host computer, a network node and a user equipment for executing a client application at a user equipment according to some embodiments of the present disclosure; FIG. 4 is a flowchart of an exemplary process in a network node according to some embodiments of the present disclosure;

[0058] FIG. 5 is a flowchart of an exemplary process in a user equipment according to some embodiments of the present disclosure;

[0059] FIG. 6 is a signalling diagram illustrating an example implementation of the process of Fig.4 and the process of Fig.5.

[0060] DETAILED DESCRIPTION

[0061] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to emergency paging with respect to an ongoing small data transmission, SDT, session. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0062] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0063] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication. In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0064] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.

[0065] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can be any type of wireless device capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

[0066] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0067] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0068] Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and / or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0069] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0070] Some embodiments provide emergency paging with respect to an ongoing SDT session or transmission.

[0071] Referring now to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 1 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP-type cellular network that may support standards such as LTE and / or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipments 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.

[0072] Also, it is contemplated that a UE 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0073] The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and / or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

[0074] The communication system of FIG. 1 as a whole enables connectivity between one of the connected UEs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected UEs 22a, 22b are configured to communicate data and / or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected UE 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the UE 22a towards the host computer 24. A network node 16 is configured to include a paging unit 32 which is configured to perform one or more network node 16 functions described herein such as functions with respect to emergency paging with respect to an ongoing SDT session.

[0075] Example implementations, in accordance with an embodiment, of the UE 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 2. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and / or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and / or read from) memory 46, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memoiy) and / or optical memoiy and / or EPROM (Erasable Programmable Read-Only Memory).

[0076] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 48 and / or the host application 50 may include instructions that, when executed by the processor 44 and / or processing circuitry 42, causes the processor 44 and / or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.

[0077] The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a UE 22 connecting via an OTT connection 52 terminating at the UE 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and / or receive from the network node 16 and or the user equipment 22. The processing circuitry 42 of the host computer 24 may include an information unit 54 configured to enable the service provider to analyze, determine, store, forward, relay, transmit, receive, etc., information associated with emergency paging with respect to an ongoing SDT session.

[0078] The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the UE 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and / or through one or more intermediate networks 30 outside the communication system 10.

[0079] In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may compnse any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory). Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or processing circuitry 68, causes the processor 70 and / or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include paging unit 32 configured to perform one or more network node 16 functions as described herein such as functions with respect to emergency paging with respect to an ongoing SDT session.

[0080] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0081] The hardware 80 of the UE 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) memory 88, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0082] Thus, the UE 22 may further comprise software 90, which is stored in, for example, memory 88 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the UE 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the UE 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

[0083] The processing circuitry 84 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UE 22. The processor 86 corresponds to one or more processors 86 for performing UE 22 functions described herein. The UE 22 includes memory 88 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or processing circuitry 84, causes the processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to UE 22. For example, the processing circuitry 84 of the user equipment 22 may include a termination unit unit 34 configured to perform one or more UE 22 functions as described herein such as with respect to functions associated with emergency paging with respect to an ongoing SDT session.

[0084] In some embodiments, the inner workings of the network node 16, UE 22, and host computer 24 may be as shown in FIG. 2 and independently, the surrounding network topology may be that of FIG. 1.

[0085] In FIG. 2, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the user equipment 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the UE 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network). The wireless connection 64 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

[0086] In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and UE 22, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the UE 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.

[0087] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the UE 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and / or the network node’s 16 processing circuitry 68 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the UE 22, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the UE 22.

[0088] In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a UE 22 to a network node 16. In some embodiments, the UE 22 is configured to, and / or comprises a radio interface 82 and / or processing circuitry 84 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the network node 16, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the network node 16.

[0089] Although FIGS. 1 and 2 show various “units” such as paging unit 32, and termination unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0090] FIG. 3 shows a communication diagram of a host computer 24 communicating via a network node 16 with a UE 22 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE 22, network node 16, and host (such as host computer 24) discussed in the preceding paragraphs will now be described with reference to FIG. 3.

[0091] Embodiments of host computer 24 include hardware, such as a communication interface, processing circuitry, and memory. The host computer 24 also includes software, which is stored in or accessible by the host computer 24 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 22 connecting via an over-the-top (OTT) connection 52 extending between the UE 22 and host computer 24. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 52.

[0092] The network node 16 includes hardware enabling it to communicate with the host computer 24 and UE 22. The connection 66 may be direct or pass through a core network (like core network 14 in FIG. 1) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. The UE 22 includes hardware and software, which is stored in or accessible by UE 22 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 22 with the support of the host computer 24. In the host computer 24, an executing host application may communicate with the executing client application via the OTT connection 52 terminating at the UE 22 and host computer 24. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 52.

[0093] The OTT connection 52 may extend via a connection 66 between the host computer 24 and the network node 16 and via a wireless connection 64 between the network node 16 and the UE 22 to provide the connection between the host computer 24 and the UE 22. The connection 66 and wireless connection 64, over which the OTT connection 52 may be provided, have been drawn abstractly to illustrate the communication between the host computer 24 and the UE 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0094] As an example of transmitting data via the OTT connection 52, in Block SI 00, the host computer 24 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 22. In other embodiments, the user data is associated with a UE 22 that shares data with the host computer 24 without explicit human interaction. In step Block S 102, the host computer 24 initiates a transmission carrying the user data towards the UE 22. The host computer 24 may initiate the transmission responsive to a request transmitted by the UE 22. The request may be caused by human interaction with the UE 22 or by operation of the client application executing on the UE 22. The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in Block SI 04, the network node 16 transmits to the UE 22 the user data that was earned in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In Block SI 06, the UE 22 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 22 associated with the host application executed by the host computer 24.

[0095] In some examples, the UE 22 executes a client application which provides user data to the host computer 24. The user data may be provided in reaction or response to the data received from the host computer 24. Accordingly, in Block SI 08, the UE 22 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 22. Regardless of the specific manner in which the user data was provided, the UE 22 initiates, in Block SI 10, transmission of the user data towards the host computer 24 via the network node 16. In Block SI 12, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the UE 22 and initiates transmission of the received user data towards the host computer 24. In Block SI 14, the host computer 24 receives the user data carried in the transmission initiated by the UE 22.

[0096] One or more of the various embodiments improve the performance of OTT services provided to the UE 22 using the OTT connection 52, in which the wireless connection 64 forms the last segment. More precisely, the teachings of these embodiments may improve one or more procedures to help ensure that emergency paging messages are received when opted into, and thereby provide benefits such as increased emergency paging message reliability.

[0097] In an example scenario, factory status information may be collected and analyzed by the host computer 24. As another example, the host computer 24 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host computer 24 may collect and analyze real-time data to assist in controlling vehicle congestion (e g., controlling traffic lights). As another example, the host computer 24 may store surveillance video uploaded by a UE. As another example, the host computer 24 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host computer 24 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0098] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and UE 22, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host computer 24 and / or UE 22. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 16. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host computer 24. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while monitoring propagation times, errors, etc.

[0099] FIG. 4 is a flowchart of an exemplary process in a network node 16 according to one or more embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the paging unit 32), processor 70, radio interface 62 and / or communication interface 60. Network node 16 is configured to determine (Block SI 16) to signal a paging message to the UE 22, as described herein. Network node 16 is configured to transmit (Block SI 18) a message to the UE 22, where the message is configured to cause the UE 22 to terminate an ongoing small data transmission, SDT, procedure, as described herein. Network node 16 is configured to transmit (Block SI 20) the paging message to the UE 22 that is no longer participating in the SDT procedure, as described herein.

[0100] According to one or more embodiments, the message that causes the UE 22 to terminate the ongoing SDT procedure is one of a radio resource control, RRC, resume message, a RRC reject message, or a RRC release message.

[0101] According to one or more embodiments, the paging message is one of an Earthquake and Tsunami Warning System, ETWS, message or Commercial Mobile Alert System, CMAS, message. According to one or more embodiments, the paging message is transmitted in a physical downlink shared channel, PDSCH.

[0102] According to one or more embodiments, the paging message is transmitted in system information block, SIB, signaling.

[0103] According to one or more embodiments, the network node is configured to receive UE capability information, the UE capability information indicating whether the UE supports receiving of the paging message.

[0104] According to one or more embodiments, the network node is configured to receive a UE capability update from a second UE 22, where the UE capability update is configured to opt out the second UE from receiving the paging message, and where the second UE remains registered with the network node 16 during UE capability update.

[0105] FIG. 5 is a flowchart of an exemplary process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 84 (including the termination unit 34), processor 86, radio interface 82 and / or communication interface 60. UE 22 is configured to receive (Block SI 22) a message indicating for the UE 22 to terminate an ongoing small data transmission, SDT, procedure, as described herein. UE 22 is configured to terminate (Block S 124) the SDT procedure based on the message, as described herein. UE 22 is configured to, after the SDT procedure has been terminated, receive (Block SI 26) a paging message, as described herein.

[0106] According to one or more embodiments, the message indicating for the UE 22 to terminate the ongoing SDT procedure is one of: a radio resource control, RRC, resume message, a RRC reject message, or a RRC release message.

[0107] According to one or more embodiments, the paging message is one of an Earthquake and Tsunami Warning System, ETWS, message or Commercial Mobile Alert System, CMAS, message.

[0108] According to one or more embodiments, the paging message is received in a physical downlink shared channel, PDSCH.

[0109] According to one or more embodiments, the paging message is received in system information block, SIB, signaling.

[0110] According to one or more embodiments, the UE 22 is configured to transmit UE capability information, where the UE capability information indicates whether the UE supports receiving of the paging message. According to one or more embodiments, the UE 22 is configured to transmit a UE capability update, where the UE capability update is configured to opt out the UE from receiving the further paging messages, and where the UE remain registered with the network node 16 during UE capability update.

[0111] FIG. 6 is a signalling diagram illustrating an exemplary implementation of the processes of Figure 4 and Figure 5.

[0112] The network elements involves in the signalling diagram of Figure 6 are the Network node 610, which is configured to perform the methods / processes of Figure 4, and the user equipment 620, which is configured to perform the methods / processes of Figure 5.

[0113] The UE 620 receives from the network node 610 a message 625. The message 625 corresponds to the message received in S122 of Figure 5, and / or the message transmitted in Figure 4.

[0114] The UE 620 receives after the SDT procedure has been terminated, a paging message 635. The paging message 635 corresponds to the paging message received in S126 of Figure 5, and / or the paging message transmitted in S120 of Figure 4.

[0115] The UE 620 may transmit UE capabilities 645 to the network node 610. The UE capabilities 645 corresponds to the UE capabilities as defined with relation to the processes of Figure 4 and Figure 5.

[0116] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for emergency paging with respect to an ongoing SDT session.

[0117] Some embodiments provide emergency paging with respect to an ongoing SDT session. One or more network node 16 functions described below may be performed by one or more of processing circuitry 68, processor 70, paging unit 32, radio interface 62, etc. One or more wireless device 22 functions described herein may be performed by one or more of termination unit 34, processor 86, processing circuitry 84, radio interface 82, etc.

[0118] With respect to Problem 1: Handling of Paging message during SDT

[0119] The procedure described herein is a method that can be implemented in a RAN network node 16, such as gNB and in the UEs 22.

[0120] As described in the problem formulation, the network node 16 may receive paging requests from core network, which the network node 16 should then send forward and send Paging messages towards the UEs 22 indicated in the request from the core network. If a UE 22 has earlier started an SDT procedure and is currently having an ongoing SDT procedure (as specified in 3GPP, e.g., 3GPP TS 38.331), it may not be able to receive the paging message the network node 16 sends towards the UE 22 due to the ongoing SDT procedure. To solve this issue:

[0121] • In some embodiments, the network node 16 sends RRCResume message towards the UE 22 which is m an ongoing SDT procedure when the network node 16 has received the Paging message from the core network, or when the network node 16 otherwise identifies need to page the UE 22 or initiate communication with the UE 22 (e.g., DL data pending). This has the effect that the network node 16 is able to reach the UE 22 (as the UE 22 may not read the Paging message over PDSCH the network node 16 has sent) and is able to request the UE to move to

[0122] RRC CONNECTED mode for communication.

[0123] • In some embodiments, the network node 16 sends the Paging message after it has sent RRCReject or RRCRelease message to an UE in an ongoing SDT procedure when the network node 16 has received the Paging message. These messages have the effect of terminating the ongoing SDT procedure, after which the UE should monitor for and receive the Paging message according to the existing specifications, and where the network node 16 would send the Paging message to the UE 22 after it has sent the RRCReject or RRCRelease message.

[0124] • In some embodiments, the existing Short Message bit referring to etwsAndCmasIndication (see Table 6.5-1 from 3GPP, e.g., 3GPP TS 38.331 as reference) is used to indicate the UE that the UE needs to terminate the SDT procedure and try to acquire ETWS / CMAS information as soon as possible or that the UE stops SDT procedure and monitor and try to receive a Paging message. In one alternative, the field tells the UE that the UE is to stop the ongoing SDT procedure and stay in RRC_INACTIVE mode and acquire SIB6 and / or SIB7 and / or SIB8 after stopping the SDT procedure. In another alternative the field tells the UE that the UE is to go to RRC IDLE mode and acquire SIB6 and / or SIB7 and / or SIB8 after stopping the SDT procedure. In one alternative, the indication is repurposed or redefined to mean that the UE is to stop the SDT procedure and stay in RRC_INACTIVE mode to receive a Paging message. In yet another alternative the indication is repurposed or redefined to mean that the UE is to stop the SDT procedure and release to RRC_IDLE mode to receive a Paging message. The effect of this embodiment is that the network / network node 16 can instruct the UE 22 using Short Message to either directly acquire ETWS / CMAS messages or receive a Paging message which the UE 22 could not otherwise receive during ongoing SDT procedure. The short message is addressed using P-RNTI and sent over PDCCH thus UE 22 in ongoing SDT procedure is able to receive a Short

[0125] Message.

[0126] Table 6.5-1: Short Messages (Ref. TS 38.331 vlS.0.0) • In an alternative embodiment to above, a new bit indication is defined in the Short

[0127] Message where the indication tells the UE 22 to stop the SDT procedure, e.g. (referring to the table above):

[0128] Table 2 - Stop SDT procedure message

[0129] Similar to the above embodiments, this would make it possible for the network or network node 16 to deliver the Paging message to the UE 22 which was not possible during an ongoing SDT procedure, but where the UE 22 is still able to monitor PDCCH and thus receive the Short Messages addressed using P-RNTI.

[0130] The UE 22 behavior of the etwsAndCmasIndication remains the same when the UE 22 does not have an ongoing SDT procedure. But a UE 22 with an ongoing SDT procedure aborts the procedure (and transits to RRC_IDLE).

[0131] • In some embodiments, when the network node 16 needs to send a group Paging message for UE 22 that has joined an MBS multicast session, and the UE 22 is in an ongoing SDT procedure: o In one alternative, the UE 22 does not support MBS multicast reception in RRC_INACTIVE, or the UE 22 did not join the session yet, or the UE 22 is not allowed to receive the session in RRC_INACTIVE, and the network node 16 sends RRCResume message to request the UE 22 to move to RRC_CONNECTED state to receive the multicast data. o In another alternative, the network node 16 sends Paging message after it has sent RRCReject or RRCRelease message to the UE 22, whereafter the UE 22 follows the existing procedures upon receiving the Paging request. o In another alternative a Short Message is used either with existing fields or a new defined field to indicate to the UE 22 to stop ongoing SDT and receive the group Paging message (see above embodiments, this alternative corresponds to above descriptions on Short Message reception but for the case where the UE has joined an MBS multicast session and is in an ongoing SDT procedure).

[0132] With respect to Problem 2: ETWS / CMAS warnings send via dedicated signalling

[0133] The procedure is a method that can be implemented in a RAN network node 16, such as gNB and on UEs 22.

[0134] As explained herein, the network / network node 16, in existing systems, does not know whether a UE 22 supports reception of ETWS and / or CMAS messages. This may lead to situations where the network attempts to send ETWS / CMAS information in dedicated signaling, but the UE 22 cannot receive and / or understand the messages thus the end result is waste of radio resources. To overcome this the following embodiments can be implemented:

[0135] • In some embodiments, a new UE capability is defined, and the UE 22 signals this if it supports ETWS. The network node 16 may only send ETWS warning message in dedicated message to UEs 22 which have indicated supporting ETWS.

[0136] • In some embodiments, a new UE capability is defined and the UE 22 signals this if it supports CMAS per warning type (and it has not opted out for the warning type). The network node 16 may only send a type of CMAS warning message in dedicated message to UEs the CMAS warning type.

[0137] When the UE 22 opts out from a CMAS warning type, the UE 22 performs a UE capability update. There is currently no defined procedure to perform a capability update while staying attached or registered to the network. The following embodiments can be considered for UE capability update: o In one alternative, the UE 22 detaches from the network and attaches to the network again to provide the network with an updated list of the UE capabilities. o In another alternative, a new procedure is defined which the UE 22 initiates towards network node 16 to update its capabilities, specifically regarding the CMAS warning message types it has opted in and / or opted out of. The initiation is triggered by UE 22 changing its preferences on which CMAS message types it is interested in. o In another alternative, existing procedures are updated to allow the UE 22 to inform the network node 16 / network about capability restrictions it has. Such restrictions can specifically involve the CMAS message types the UE 22 has opted in to or opted out of. The initiation of the updated existing procedure is triggered by UE 22 changing its preferences on which CMAS message types it is interested in.

[0138] ■ One example of a procedure which can be used (with modifications) is informing the network node 16 about temporary capability restrictions as specificized for MUSIM work item during Rel-18. This procedure uses UEAssistancelnformation message to provide assistance information to the network node 16. In the new embodiment, the UE 22 uses this message to inform the network node 16 about the CMAS message types the UE 22 has opted in to or opted out of.

[0139] One or more embodiments described herein may provide one or more of the following advantages:

[0140] With respect to Problem 1: Handling of Paging message during SDT

[0141] • The reliability of Paging reception is not decreased when the UE supports SDT and is not reachable for a short while.

[0142] With respect to Problem 2: ETWS / CMAS warnings send via dedicated signalling

[0143] • avoids useless / added signalling and waste of system resources, especially when a large group of UEs needs to receive the warning message as soon as possible. Sending warning messages to UEs that do not support the feature or have opted out from receiving them, further delays the reception of the warning message to UEs that are interested to receive it, which is a problem that the present disclosure solves.

[0144] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0145] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0146] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0147] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0148] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primaiy direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0149] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination. Abbreviations that may be used in the preceding description include:

[0150] Abbreviation Explanation

[0151] CMAS Commercial Mobile Alert

[0152] ETWS Earthquake and Tsunami Warning System

[0153] SDT Short Data Transmission It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings.

[0154] Embodiments:

[0155] Embodiment Al . A network node configured to communicate with a user equipment, UE, the network node configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to: determine to signal a paging message to the UE; transmit a message to the UE, the message being configured to cause the UE to terminate an ongoing small data transmission, SDT, procedure; and transmit the paging message to the UE that is no longer participating in the SDT procedure.

[0156] Embodiment A2. The network node of Embodiment Al, wherein the message that causes the UE to terminate the ongoing SDT procedure is one of: a radio resource control, RRC, resume message; a RRC reject message; or a RRC release message.

[0157] Embodiment A3. The network node of any one of Embodiments A1-A2, wherein the paging message is one of an Earthquake and Tsunami Warning System, ETWS, message or Commercial Mobile Alert System, CMAS, message.

[0158] Embodiment A4. The network node of any one of Embodiments Al -A3, wherein the paging message is transmitted in a physical downlink shared channel, PDSCH.

[0159] Embodiment A5. The network node of any one of Embodiments A1-A3, wherein the paging message is transmitted in system information block, SIB, signaling.

[0160] Embodiment A6. The network node of any one of Embodiments A1-A5, wherein the network node is configured to receive UE capability information, the UE capability information indicating whether the UE supports receiving of the paging message. Embodiment A7. The network node of Embodiment A1-A6, wherein the network node is configured to receive a UE capability update from a second UE, the UE capability update configured to opt out the second UE from receiving the paging message, the second UE remaining registered with the network node during UE capability update.

[0161] Embodiment Bl. A method implemented by a network node that is configured to communicate with a user equipment, UE, the method comprising: determining to signal a paging message to the UE; transmitting a message to the UE, the message being configured to cause the UE to terminate an ongoing small data transmission, SDT, procedure; and transmitting the paging message to the UE that is no longer participating in the SDT procedure.

[0162] Embodiment B2. The method of Embodiment Bl, wherein the message that causes the UE to terminate the ongoing SDT procedure is one of: a radio resource control, RRC, resume message; a RRC reject message; or a RRC release message.

[0163] Embodiment B3. The method of any one of Embodiments B1-B2, wherein the paging message is one of an Earthquake and Tsunami Warning System, ETWS, message or Commercial Mobile Alert System, CMAS, message.

[0164] Embodiment B4. The method of any one of Embodiments B1-B3, wherein the paging message is transmitted in a physical downlink shared channel, PDSCH.

[0165] Embodiment B5. The method of any one of Embodiments B1-B3, wherein the paging message is transmitted in system information block, SIB, signaling.

[0166] Embodiment B6. The method of any one of Embodiments B1-B5, further comprising receiving UE capability information, the UE capability information indicating whether the UE supports receiving of the paging message. Embodiment B7. The method of Embodiment B1-B6, further comprising receiving a UE capability update from a second UE, the UE capability update configured to opt out the second UE from receiving the paging message, the second UE remaining registered with the network node during UE capability update.

[0167] Embodiment Cl. A user equipment, UE, configured to communicate with a network node, the UE configured to, and / or comprising a radio interface and / or processing circuitry configured to: receive a message indicating for the UE to terminate an ongoing small data transmission, SDT, procedure; terminate the SDT procedure based on the message; and after the SDT procedure has been terminated, receive a paging message.

[0168] Embodiment C2. The UE of Embodiment Cl, wherein the message indicating for the UE to terminate the ongoing SDT procedure is one of: a radio resource control, RRC, resume message; a RRC reject message; or a RRC release message.

[0169] Embodiment C3. The UE of any one of Embodiments C1-C2, wherein the paging message is one of an Earthquake and Tsunami Warning System, ETWS, message or Commercial Mobile Alert System, CMAS, message.

[0170] Embodiment C4. The UE of any one of Embodiments C1-C3, wherein the paging message is received in a physical downlink shared channel, PDSCH.

[0171] Embodiment C5. The UE of any one of Embodiments C1-C3, wherein the paging message is received in system information block, SIB, signaling.

[0172] Embodiment C6. The UE of any one of Embodiments C1-C5, wherein the UE is configured to transmit UE capability information, the UE capability information indicating whether the UE supports receiving of the paging message. Embodiment C7. The UE of Embodiment C1-C6, wherein the UE is configured to transmit a UE capability update, the UE capability update configured to opt out the UE from receiving the further paging messages, the UE remaining registered with the network node during UE capability update.

[0173] Embodiment DI. A method implemented in a user equipment, UE, that is configured to communicate with a network node, the method comprising: receiving a message indicating for the UE to terminate an ongoing small data transmission, SDT, procedure; terminating the SDT procedure based on the message; and after the SDT procedure has been terminated, receiving a paging message.

[0174] Embodiment D2. The method of Embodiment DI, wherein the message indicating for the UE to terminate the ongoing SDT procedure is one of: a radio resource control, RRC, resume message; a RRC reject message; or a RRC release message.

[0175] Embodiment D3. The method of any one of Embodiments D1-D2, wherein the paging message is one of an Earthquake and Tsunami Warning System, ETWS, message or Commercial Mobile Alert System, CMAS, message.

[0176] Embodiment D4. The method of any one of Embodiments D1-D3, wherein the paging message is received in a physical downlink shared channel, PDSCH.

[0177] Embodiment D5. The method of any one of Embodiments D1-D3, wherein the paging message is received in system information block, SIB, signaling.

[0178] Embodiment D6. The method of any one of Embodiments D1-D5, further comprising transmitting UE capability information, the UE capability information indicating whether the UE supports receiving of the paging message.

[0179] Embodiment D7. The method of Embodiment D1-D6, further comprising transmitting a UE capability update, the UE capability update configured to opt out the UE from receiving the further paging messages, the UE remaining registered with the network node during UE capability update.

Claims

CLAIMS1. A network node configured to communicate with a user equipment, UE, the network node configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to: determine to signal a paging message to the UE; transmit a message to the UE, the message being configured to cause the UE to terminate an ongoing small data transmission, SDT, procedure; and transmit the paging message to the UE that is no longer participating in the SDT procedure.

2. The network node of claim 1, wherein the message that causes the UE to terminate the ongoing SDT procedure is one of: a radio resource control, RRC, resume message; a RRC reject message; or a RRC release message.

3. The network node of any one of claims 1-2, wherein the paging message is one of an Earthquake and Tsunami Warning System, ETWS, message or Commercial Mobile Alert System, CMAS, message.

4. The network node of any one of claims 1-3, wherein the paging message is transmitted in a physical downlink shared channel, PDSCH.

5. The network node of any one of claims 1-3, wherein the paging message is transmitted in system information block, SIB, signaling.

6. The network node of any one of claims 1-5, wherein the network node is configured to receive UE capability information, the UE capability information indicating whether the UE supports receiving of the paging message.

7. The network node of claims 1-6, wherein the network node is configured to receive a UE capability update from a second UE, the UE capability update configured toopt out the second UE from receiving the paging message, the second UE remaining registered with the network node during UE capability update.

8. A method implemented by a network node that is configured to communicate with a user equipment, UE, the method comprising: determining to signal a paging message to the UE; transmitting a message to the UE, the message being configured to cause the UE to terminate an ongoing small data transmission, SDT, procedure; and transmitting the paging message to the UE that is no longer participating in the SDT procedure.

9. The method of claim 8, wherein the message that causes the UE to terminate the ongoing SDT procedure is one of: a radio resource control, RRC, resume message; a RRC reject message; or a RRC release message.

10. The method of any one of claims 8-9, wherein the paging message is one of an Earthquake and Tsunami Warning System, ETWS, message or Commercial Mobile Alert System, CMAS, message.

11. The method of any one of claims 8-10, wherein the paging message is transmitted in a physical downlink shared channel, PDSCEI.

12. The method of any one of claims 8-10, wherein the paging message is transmitted in system information block, SIB, signaling.

13. The method of any one of claims 8-12, further comprising receiving UE capability information, the UE capability information indicating whether the UE supports receiving of the paging message.

14. The method of claims 8-13, further comprising receiving a UE capability update from a second UE, the UE capability update configured to opt out the second UEfrom receiving the paging message, the second UE remaining registered with the network node during UE capability update.

15. A user equipment, UE, configured to communicate with a network node, the UE configured to, and / or comprising a radio interface and / or processing circuitry configured to: receive a message indicating for the UE to terminate an ongoing small data transmission, SDT, procedure; terminate the SDT procedure based on the message; and after the SDT procedure has been terminated, receive a paging message.

16. The UE of claim 15, wherein the message indicating for the UE to terminate the ongoing SDT procedure is one of: a radio resource control, RRC, resume message; a RRC reject message; or a RRC release message.

17. The UE of any one of claims 15-16, wherein the paging message is one of an Earthquake and Tsunami Warning System, ETWS, message or Commercial Mobile Alert System, CMAS, message.

18. The UE of any one of claims 15-17, wherein the paging message is received in a physical downlink shared channel, PDSCH.

19. The UE of any one of claims 15-17, wherein the paging message is received in system information block, SIB, signaling.

20. The UE of any one of claims 15-19, wherein the UE is configured to transmit UE capability information, the UE capability information indicating whether the UE supports receiving of the paging message.

21. The UE of claims 15-20, wherein the UE is configured to transmit a UE capability update, the UE capability update configured to opt out the UE from receivingthe further paging messages, the UE remaining registered with the network node during UE capability update.

22. A method implemented in a user equipment, UE, that is configured to communicate with a network node, the method comprising: receiving a message indicating for the UE to terminate an ongoing small data transmission, SDT, procedure; terminating the SDT procedure based on the message; and after the SDT procedure has been terminated, receiving a paging message.

23. The method of claim 22, wherein the message indicating for the UE to terminate the ongoing SDT procedure is one of: a radio resource control, RRC, resume message; a RRC reject message; or a RRC release message.

24. The method of any one of claims 22-23, wherein the paging message is one of an Earthquake and Tsunami Warning System, ETWS, message or Commercial Mobile Alert System, CMAS, message.

25. The method of any one of claims 22-24, wherein the paging message is received in a physical downlink shared channel, PDSCH.

26. The method of any one of claims 22-24, wherein the paging message is received in system information block, SIB, signaling.

27. The method of any one of claims 22-26, further comprising transmitting UE capability information, the UE capability information indicating whether the UE supports receiving of the paging message.

28. The method of claims 22-27, further comprising transmitting a UE capability update, the UE capability update configured to opt out the UE from receiving the further paging messages, the UE remaining registered with the network node during UE capability update.

29. A computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out a method according to any of claims 8 to 14.

30. A computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out a method according to any of claims 22 to 28.

31. A computer program product comprising non transitory computer readable media having stored thereon a computer program according to claim 29.

32. A computer program product comprising non-transitory computer readable media having stored thereon a computer program according to claim 30.

Images