Wireless device, network node, and methods performed thereby, for handling downlink transmission

Abstract

A method, performed by a wireless device (130), for handling downlink transmission in a wireless communications network (100). The wireless device (130) receives (201), while in inactive state, a first indication from a network node (110) indicating the wireless device (130) is paged, and a mobile terminated small data transmission procedure is used. The first indication further comprises an additional indication of a mobile terminated procedure. The additional indication further indicates one or more resources for the MT-SDT procedure the wireless device (130) is to resume, comprising one or more radio bearers. The wireless device (130) sends (202), to the network node (110), while in inactive state and in response to the first indication, a second indication comprising a preamble. The wireless device (130) then receives (204), while in inactive state and after having sent the preamble, a downlink transmission from the network node (110). The downlink transmission comprises data of a size under a threshold.

Description

[0001] WIRELESS DEVICE, NETWORK NODE, AND METHODS PERFORMED THEREBY, FOR

[0002] HANDLING DOWNLINK TRANSMISSION

[0003] TECHNICAL FIELD

[0004] The present disclosure relates generally to a wireless device and methods performed thereby for handling downlink transmission. The present disclosure further relates generally to a network node and methods performed thereby, for handling the downlink transmission.

[0005] BACKGROUND

[0006] Wireless devices within a wireless communications network may be e.g., User Equipments (UEs), stations (STAs), mobile terminals, wireless terminals, terminals, and / or Mobile Stations (MS). Wireless devices are enabled to communicate wirelessly in a cellular communications network or wireless communication network, sometimes also referred to as a cellular radio system, cellular system, or cellular network. The communication may be performed e.g., between two wireless devices, between a wireless device and a regular telephone and / or between a wireless device and a server via a Radio Access Network (RAN) and possibly one or more core networks, comprised within the wireless communications network. Wireless devices may further be referred to as mobile telephones, cellular telephones, laptops, or tablets with wireless capability, just to mention some further examples. The wireless devices in the present context may be, for example, portable, pocket-storable, hand-held, computer-comprised, or vehicle-mounted mobile devices, enabled to communicate voice and / or data, via the RAN, with another entity, such as another terminal or a server.

[0007] The wireless communications network covers a geographical area which may be divided into cell areas, each cell area being served by a network node, which may be an access node such as a radio network node, radio node or a base station, e.g., a Radio Base Station (RBS), which sometimes may be referred to as e.g., gNB, evolved Node B (“eNB”), “eNodeB”, “NodeB”, “B node”, Transmission Point (TP), or BTS (Base Transceiver Station), depending on the technology and terminology used. The base stations may be of different classes such as e.g., Wide Area Base Stations, Medium Range Base Stations, Local Area Base Stations, Home Base Stations, pico base stations, etc... , based on transmission power and thereby also cell size. A cell is the geographical area where radio coverage is provided by the base station or radio node at a base station site, or radio node site, respectively. One base station, situated on the base station site, may serve one or several cells. Further, each base station may support one or several communication technologies. The base stations communicate over the air interface operating on radio frequencies with the terminals within range of the base stations. The wireless communications network may also be a non-cellular system, comprising network nodes which may serve receiving nodes, such as wireless devices, with serving beams. In 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE), base stations, which may be referred to as eNodeBs or even eNBs, may be directly connected to one or more core networks. In the context of this disclosure, the expression Downlink (DL) may be used for the transmission path from the base station to the wireless device. The expression Uplink (UL) may be used for the transmission path in the opposite direction i.e., from the wireless device to the base station.

[0008] The standardization organization 3GPP is currently in the process of specifying a New Radio Interface called NR or 5G-UTRA, as well as a Fifth Generation (5G) Packet Core Network (CN), which may be referred to as Next Generation (NG) Core Network, abbreviated as NG-CN, NGC, 5G CN or 5G Core (5GC). NG may be understood to refer to the interface / reference point between the Radio Access Network (RAN) and the CN in 5G / NR. In a 5G System (5GS), a radio base station in NR may be referred to as a gNB or 5G Node B. An NR UE may be referred to as an nUE.

[0009] Internet of Things (loT)

[0010] The Internet of Things (loT) may be understood as an internetworking of communication devices, e.g., physical devices, vehicles, which may also be referred to as "connected devices" and "smart devices", buildings and other items — embedded with electronics, software, sensors, actuators, and network connectivity that may enable these objects to collect and exchange data. The loT may allow objects to be sensed and / or controlled remotely across an existing network infrastructure.

[0011] "Things," in the loT sense, may refer to a wide variety of devices such as heart monitoring implants, biochip transponders on farm animals, electric clams in coastal waters, automobiles with built-in sensors, DNA analysis devices for environmental / food / pathogen monitoring, or field operation devices that may assist firefighters in search and rescue operations, home automation devices such as the control and automation of lighting, heating, e.g. a “smart” thermostat, ventilation, air conditioning, and appliances such as washer, dryers, ovens, refrigerators or freezers that may use telecommunications for remote monitoring. These devices may collect data with the help of various existing technologies and then autonomously flow the data between other devices.

[0012] It is expected that in a near future, the population of loT devices will be very large. Various predictions exist, among which one assumes that there will be >60000 devices per square kilometer, and another assumes that there will be 1000000 devices per square kilometer. A large fraction of these devices are expected to be stationary, e.g., gas and electricity meters, vending machines, etc. Machine Type Communication (MTC)

[0013] Machine Type Communication (MTC) has in recent years, especially in the context of the Internet of Things (loT), shown to be a growing segment for cellular technologies. An MTC device may be a communication device, typically a wireless communication device or simply user equipment, that is a self and / or automatically controlled unattended machine and that is typically not associated with an active human user in order to generate data traffic. An MTC device may be typically simpler, and typically associated with a more specific application or purpose, than, and in contrast to, a conventional mobile phone or smart phone. MTC involves communication in a wireless communication network to and / or from MTC devices, which communication typically may be of quite different nature and with other requirements than communication associated with e.g., conventional mobile phones and smart phones. In the context of and growth of the loT, it is evident that MTC traffic will be increasing and thus needs to be increasingly supported in wireless communication systems.

[0014] NR small data transmissions in Inactive state

[0015] In Rel-17, mobile originated small data transmission (MO-SDT) was introduced for New Radio (NR) to reduce the signaling overhead for small uplink data payloads, see RP-200954 ‘New Work Item on NR small data transmissions in INACTIVE state’. Two solutions were introduced, random access based SDT (RA-SDT) and configured grant SDT (CG-SDT). RA-SDT may be understood to mean that either legacy 4-step Random Access CHannel (RACH), or 2-step RACH procedure may be used as a baseline, but that a user-plane data payload may be appended, multiplexed with the RRCResumeRequest message, in Msg3, or MsgA. CG-SDT may be understood to mean that the UEs may be configured via Radio Resource Control (RRC) to have periodic CG-SDT occasions which may, contention-free, be used for uplink transmission. In this way, Msg1 and Msg2 may be omitted, but it may be a requirement that the UE has a valid Timing Advance (TA) and is uplink synchronized to be able to use the resources for transmission.

[0016] For NarrowBand loT (NB-loT) and LTE-M, similar signaling optimizations for small data have been introduced through Rel-15 Early Data Transmission (EDT) and Rel-16 Preconfigured Uplink Resources (PUR). The main differences for the NR Small Data Transmission (SDT) solutions may be understood to be that the Rel-17 NR Small Data may be only to be supported for RRC INACTIVE state, may include also 2-step RACH based small data, that it may be supported by any NR UE, e.g., also Mobile BroadBand (MBB) UEs and not limited to loT UEs, and may support transmission of subsequent data, e.g., larger payload sizes which may require more than one transmission.

[0017] For LTE, support for mobile terminate (MT) was later introduced in Rel-16, that is, supporting transmissions of small data payloads in the downlink. Several solutions were considered: ‘Data in paging’, multiple versions, ‘Data in Msg2’, and ‘Data in Msg4’, see overview in RAN2 email discussion R2-1901143 from RAN2#105. ‘Data in paging’ was first ruled out, see meeting report R2-1903001 , and later ‘Data in Msg2’ was ruled out, see UP MT-EDT email discussion outcome in R2-1910420, and meeting report in R2-1912001 , and therefore ‘Data in Msg4’ was specified as the LTE solution. Note that for NB-loT and LTE Machine (LTE-M), different approaches were introduced for the loT control-plane optimization, ‘Data over Non-Access Stratum (NAS)’, or Data over Non-Access Stratum (DoNAS), and loT user-plane optimizations, e.g., RRC suspend / resume, Control Plane (CP)-EDT and User Plane (UP)-EDT, respectively, and that the NR approaches resemble the UP-EDT.

[0018] Currently, Mobile Terminated Small Data Transmission (MT-SDT) is being introduced in Rel-18 for NR. A Rel-18 MT-SDT work item description (WID) was approved in RAN#94e (Dec 2021) and may be found in RP-213583. The WID contains the following objectives: to specify the support for paging-triggered SDT (MT-SDT) [RAN2, RAN3], particularly MT-SDT triggering mechanism for UEs in RRCJNACTIVE, supporting RA-SDT and CG-SDT as the UL response, and MT-SDT procedure for initial DL data reception and subsequent UL / DL data transmissions in RRC NACTIVE. It may be noted that data transmission in DL within paging message is not in scope of this Wl.

[0019] In spite of its benefits, existing methods to perform Small Data transmissions may, under some circumstances not be applicable, or provide worse performance than legacy procedures, e.g., resulting in signalling overhead.

[0020] SUMMARY

[0021] As part of the development of embodiments herein, one or more challenges with the existing technology will first be identified and discussed.

[0022] Due to difference between NR and LTE, and difference between EDT and SDT, e.g., support only in RRCJNACTIVE, subsequent data transmission, etc., the LTE MT-EDT approach may not work for NR as is, and modifications may be required. Further, for the same reasons, several optimizations may be possible.

[0023] Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges.

[0024] It is therefore an object of embodiments herein to improve the handling of downlink transmission in a wireless communications network.

[0025] According to a first aspect of embodiments herein, the object is achieved by a method, performed by a wireless device. The method is for handling downlink transmission. The first wireless device operates in a wireless communications network. The wireless device receives, while the wireless device is in inactive state, a first indication from a network node. The network node operates in the wireless communications network. The first indication indicates the wireless device is being paged, and a mobile terminated small data transmission (MT-SDT) procedure is being used. The first indication further comprises an additional indication of a mobile terminated procedure. The additional indication further indicates one or more resources for the MT-SDT procedure the wireless device is to resume. The one or more resources comprise one or more radio bearers. The wireless device sends, to the network node, while the wireless device is in inactive state and in response to the received first indication, a second indication. The second indication comprises a preamble corresponding to a random access procedure. The wireless device then receives, while the wireless device is in inactive state and after having sent the preamble, a downlink transmission from the network node. The downlink transmission comprises data. A size of the data is under a threshold.

[0026] According to a second aspect of embodiments herein, the object is achieved by a method, performed by the network node. The method is for handling the downlink transmission. The network node operates in the wireless communications network. The network node sends, while the wireless device is in inactive state, the first indication to the wireless device operating in the wireless communications network. The first indication indicates the wireless device is being paged, and the MT-SDT procedure is being used. The first indication further comprises the additional indication of the mobile terminated procedure. The additional indication further indicates the one or more resources for the MT-SDT procedure the wireless device is to resume. The one or more resources comprise the one or more radio bearers.

[0027] According to a third aspect of embodiments herein, the object is achieved by the first wireless device. The wireless device may be understood to be for handling the downlink transmission. The wireless device is configured to operate in the wireless communications network. The wireless device is further configured to receive, while the wireless device is in inactive state, the first indication from the network node configured to operate in the wireless communications network. The first indication is configured to indicate the wireless device is being paged, and the MT-SDT procedure is being used. The first indication is further configured to comprise the additional indication of the mobile terminated procedure. The additional indication is further configured to indicate the one or more resources for the MT-SDT procedure the wireless device is to resume. The one or more resources are configured to comprise the one or more radio bearers. The wireless device is also configured to send, to the network node, while the wireless device is in inactive state and in response to the received first indication, the second indication. The second indication is configured to comprise the preamble corresponding to the random access procedure. The wireless device is further configured to receive, while the wireless device is in inactive state and after having sent the preamble, the downlink transmission from the network node. The downlink transmission is configured to comprise the data. The size of the data is configured to be under the threshold.

[0028] According to a fourth aspect of embodiments herein, the object is achieved by the network node. The network node may be understood to be for handling the downlink transmission. The network node is configured to operate in the wireless communications network. The network node is configured to send, while the wireless device is in inactive state, the first indication to the wireless device configured to operate in the wireless communications network. The first indication is configured to indicate the wireless device is being paged, and the MT-SDT is being used. The first indication is further configured to comprise the additional indication of the mobile terminated procedure. The additional indication is further configured to indicate the one or more resources for the MT-SDT procedure the wireless device is to resume. The one or more resources are configured to comprise the one or more radio bearers. The network node is also configured to receive, from the wireless device, while the wireless device is in inactive state and in response to the sent first indication, the second indication. The second indication is configured to comprise the preamble corresponding to the random access procedure. The network node is further configured to send, while the wireless device is in inactive state and after having received the preamble, the downlink transmission to the wireless device. The downlink transmission is configured to comprise data. The size of the data is configured to be under the threshold.

[0029] By the wireless device receiving the first indication from the network node indicating MT- SDT is being used, and the one or more resources for the MT-SDT procedure the wireless device is to resume, while the wireless device is in inactive state, the wireless device may be enabled to then receive the mobile terminated small data transmission in inactive state, thereby avoiding a need to go into a connected state and thereby saving signalling, energy and time resources. Furthermore, by the wireless device specifically receiving the first indication indicating the one or more resources for the MT-SDT procedure the wireless device is to resume, the wireless device may be enabled to perform the resumption of resources in a more efficient manner, involving less processing than e.g., LTE, as the wireless device may be enabled to refrain from resuming e.g., all data radio bearers, and may only resume the resources for MT-SDT.

[0030] By the wireless device sending the second indication to the network node while the wireless device is in inactive state, the second indication comprising the preamble, the wireless device may trigger the RA procedure and may thereby be enabled to then receive the mobile terminated small data transmission in inactive state, thereby avoiding a need to go into a connected state and thereby saving signalling and time resources.

[0031] By the wireless device receiving the downlink transmission from the network node while the wireless device is in inactive state, the wireless device is enabled to receive the mobile terminated small data transmission in inactive state, thereby avoiding a need to go into a connected state and thereby saving signalling and time resources.

[0032] Embodiments herein, may be understood to enable the ‘Data in Msg4’ approach for NR, and also to further reduce the signaling overhead. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Examples of embodiments herein are described in more detail with reference to the accompanying drawings, according to the following description.

[0034] Figure 1 is a schematic diagram depicting an example of a wireless communications network, according to embodiments herein.

[0035] Figure 2 is a flowchart depicting a method in a wireless device, according to embodiments herein.

[0036] Figure 3 is a flowchart depicting a method in a network node, according to embodiments herein.

[0037] Figure 4 is a schematic diagram illustrating a non-limiting example of methods disclosed herein, according to some examples.

[0038] Figure 5 is a schematic block diagram illustrating two embodiments, in panel a) and panel b), of a wireless device, according to embodiments herein.

[0039] Figure 6 is a schematic block diagram illustrating two embodiments, in panel a) and panel b), of a network node, according to embodiments herein.

[0040] Figure 7 is a flowchart depicting a method in a wireless device, according to examples related to embodiments herein.

[0041] Figure 8 is a flowchart depicting a method in a network node, according to examples related to embodiments herein.

[0042] Figure 9 is a schematic block diagram illustrating a telecommunication network connected via an intermediate network to a host computer, according to embodiments herein.

[0043] Figure 10 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to embodiments herein.

[0044] Figure 11 is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment, according to embodiments herein.

[0045] Figure 12 is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment, according to embodiments herein.

[0046] Figure 13 is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment, according to embodiments herein.

[0047] Figure 14 is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment, according to embodiments herein. DETAILED DESCRIPTION

[0048] Certain aspects of the present disclosure and their embodiments may provide solutions to the challenges discussed in the Summary section or other challenges. Embodiments herein may be generally understood to relate to different aspects of enabling MT-SDT, particularly, adaptations for ‘Data in Msg4’. Embodiments herein may be understood to provide methods to enable the support of MT-SDT ‘Data in Msg4’ approach for NR and further to optimize the procedure.

[0049] Examples of embodiments herein may comprise aspects of MT-SDT triggering in gNB, contention-free random access (CFRA) preamble allocation and validity, MT-Radio Network Temporary Identifier (RNTI), RRC connection resumption, and enhancement to better support application-layer response in the Uplink (UL).

[0050] Some of the embodiments contemplated will now be described more fully hereinafter with reference to the accompanying drawings, in which examples are shown. In this section, the embodiments herein will be illustrated in more detail by a number of exemplary embodiments. Other embodiments, however, are contained within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. It should be noted that the exemplary embodiments herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments.

[0051] Figure 1 depicts two non-limiting examples, in panel a) and panel b), respectively, of a wireless network or wireless communications network 100, sometimes also referred to as a wireless communications system, cellular radio system, or cellular network, in which embodiments herein may be implemented. The wireless communications network 100 may typically be support MTC, eMTC, loT and / or NB-loT. The wireless communications network 100 may be a 5G system, 5G network, or Next Gen System or network. In other examples, the wireless communications network 100 may in addition, support other technologies such as, for example, Long-Term Evolution (LTE), e.g., LTE-M, LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LTE Half-Duplex Frequency Division Duplex (HD-FDD), LTE operating in an unlicensed band, such as LTE License-Assisted Access (LAA), enhanced LAA (eLAA), further enhanced (feLAA) and / or MulteFire. Yet in other examples, the wireless communications network 100 may further support other technologies such as, for example Wideband Code Division Multiple Access (WCDMA), Universal Terrestrial Radio Access (UTRA) TDD, Global System for Mobile communications (GSM) network, GSM / Enhanced Data Rates for GSM Evolution (EDGE) Radio Access Network (GERAN) network, Ultra-Mobile Broadband (UMB), EDGE network, network comprising any combination of Radio Access Technologies (RATs) such as e.g. Multi-Standard Radio (MSR) base stations, multi-RAT base stations etc., any 3rd Generation Partnership Project (3GPP) cellular network, WiFi networks, Worldwide Interoperability for Microwave Access (WiMax), or any cellular network or system. Thus, although terminology from 5G / NR and LTE may be used in this disclosure to exemplify embodiments herein, this should not be seen as limiting the scope of the embodiments herein to only the aforementioned system.

[0052] The wireless communications network 100 may comprise a plurality of network nodes, whereof a network node 110 is depicted in the non-limiting example of Figure 1. The network node 110 is a radio network node. That is, a transmission point such as a radio base station, for example a gNB, or any other network node with similar features capable of serving a user equipment, such as a wireless device or a machine type communication device, in the wireless communications network 100. In some examples, such as that depicted in Figure 1 b, the network node 110 may be a distributed node, and may partially perform its functions in collaboration with a virtual node in a cloud 115.

[0053] The wireless communications network 100 may cover a geographical area, which in some embodiments may be divided into cell areas, wherein each cell area may be served by a radio network node, although, one radio network node may serve one or several cells. In the example of Figure 1 , the network node 110 serves a cell 116. The network node 110 may be of different classes, such as, e.g., macro base station, home base station or pico base station, based on transmission power and thereby also cell size. In some examples, the network node 110 may serve receiving nodes with serving beams. The radio network node may support one or several communication technologies, and its name may depend on the technology and terminology used. Any of the radio network nodes that may be comprised in the communications network 100 may be directly connected to one or more core networks, e.g., to one or more network nodes in the one or more core networks, such as another network node 120. The another network node 120 may, for example be a core network node operating in the wireless communications network 100 and managing a user plane, such as, for example, a UPF.

[0054] A plurality of wireless devices may be located in the wireless communication network 100, whereof a wireless device 130, is depicted in the non-limiting example of Figure 1. The wireless device 130 comprised in the wireless communications network 100 may be a wireless communication device such as a 5G User Equipment (UE) or nUE, or a UE, which may also be known as e.g., mobile terminal, wireless terminal and / or mobile station, a mobile telephone, cellular telephone, or laptop with wireless capability, just to mention some further examples. Any of the wireless devices comprised in the wireless communications network 100 may be, for example, portable, pocket-storable, hand-held, computer-comprised, or a vehicle-mounted mobile device, enabled to communicate voice and / or data, via the RAN, with another entity, such as a server, a laptop, a Personal Digital Assistant (PDA), or a tablet, Machine-to-Machine (M2M) device, a sensor, loT device, NB-loT device, device equipped with a wireless interface, such as a printer or a file storage device, modem, or any other radio network unit capable of communicating over a radio link in a communications system. The wireless device 130 comprised in the wireless communications network 100 may be enabled to communicate wirelessly in the wireless communications network 100. The communication may be performed e.g., via a RAN, and possibly the one or more core networks, which may be comprised within the wireless communications network 100.

[0055] The wireless device 130 may be configured to communicate within the wireless communications network 100 with the network node 110 over a first link 141 , e.g., a radio link. The network node 110 may be configured to communicate within the wireless communications network 100 with the another node 120 over a second link 142, e.g., a radio link or a wired link.

[0056] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0057] In general, the usage of “first”, “second”, “third”, “fourth” and / or “fifth” herein may be understood to be an arbitrary way to denote different elements or entities, and may be understood to not confer a cumulative or chronological character to the nouns they modify, unless otherwise noted, based on context.

[0058] Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments.

[0059] More specifically, the following are embodiments related to a wireless device, such as the wireless device 130, e.g., a 5G UE, nllE or a UE, and embodiments related to a network node, such as the network node 110, e.g., a gNB. In the following description, any reference to a / the UE, or simply “UE” may be understood to equally refer the wireless device 130; any reference to a / the gNB, a / the last serving gNB, a / the anchor gNB, a / the paging gNB and / or a / the network may be understood to equally refer to the network node 110; any reference to a / the CN, a / the UPF and / or a / the UPF node may be understood to equally refer to the another network node 120; any reference to a / the cell may be understood to equally refer to the cell 116.

[0060] Embodiments of a method, performed by a wireless device, such as the wireless device 130, will now be described with reference to the flowchart depicted in Figure 2. The method may be understood to be for handling downlink transmission from a network node, such as the network node 110. The wireless device 130 operates in a wireless communications network, such as the wireless communications network 100.

[0061] In some embodiments, the wireless communications network 100 may support New Radio (NR). In some embodiments, the wireless communications network 100 operates on NR.

[0062] Several embodiments are comprised herein. The method may comprise three or more of the following actions. Particularly, Action 201 , Action 202 and Action 204 are performed. In some embodiments, all the actions may be performed. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. All possible combinations are not described to simplify the description. A non-limiting example of the method performed by the wireless device 130 is depicted in Figure 2. In Figure 2, optional actions in some embodiments are represented with dashed lines. In some embodiments, the actions may be performed in a different order than that depicted Figure 2. See for example, the description of Action 205. In describing the actions of Figure 2, references may be made to the non-limiting example of the method of Figure 4.

[0063] Procedure enhancements, RAN2 related, are described below, with specific examples in the sections with underlined headings.

[0064] Action 201

[0065] In this Action 201 , the wireless device 130 receives a first indication.

[0066] The receiving in this Action 201 is from the network node 110 operating in the wireless communications network 100. The network node 110 may be, e.g., a gNB, e.g., ‘last serving gNB’ or ‘paging gNB’,

[0067] The receiving in this Action 201 may be performed, e.g., via the first link 141. The receiving in this Action 201 is while the wireless device 130 is in inactive state. The inactive state may be, e.g., RRCJNACTIVE state.

[0068] The first indication indicates the wireless device 130 is being paged, and a mobile terminated small data transmission (MT-SDT) procedure is being used.

[0069] The first indication may be, e.g., a paging message.

[0070] The first indication further comprises an additional indication of a mobile terminated procedure, e.g., MT-indication. The additional indication further indicates one or more resources for the MT-SDT procedure the wireless device 130 is to resume. The one or more resources comprise one or more radio bearers.

[0071] In some embodiments, at least one of the following may apply. In some embodiments, the additional indication may be multi-bit. In some examples, the one or more resources the wireless device 130 may be to resume may comprise at least one of: data radio bearer (DRB), Quality of Service (QoS) flow, Protocol Data Unit (PDU) session or configuration, e.g., MT-SDT configuration.

[0072] In some examples, the wireless device 130 may obtain a temporary identifier for the wireless device 130 in the wireless communications network 100, e.g., RNTI. The temporary identifier may be specific for a mobile terminated data transmission procedure, e.g., MT-RNTI.

[0073] The temporary identifier may be comprised in one of: the received first indication, and a configuration for a mobile terminated small data transmission, e.g., MT-SDT procedure.

[0074] MT-RNTI

[0075] In one example, a new RNTI, e.g., MT-RNTI, may be provided to the wireless device 130 in paging in this Action 201 , e.g., in step 1 in Figure 4, for use in the subsequent RA procedure. Alternatively, the new RNTI may be provided to the wireless device 130 as part of the MT-SDT configuration. Providing the wireless device 130 with a CFRA preamble, see below, may be a pre-requisite of this example, since the network node 110 may use the MT-RNTI for the RA response to both limit the negative impact on legacy UEs, and to the MT-SDT wireless device 130 itself, e.g., spare the wireless device 130 from unnecessary reception and processing of DL transmissions in the Random Access Response (RAR) window, and at this point, the wireless device 130 may be identified only from the RA preamble.

[0076] The MT-RNTI may either be UE-specific or common to all MT-SDT UEs, but for the ‘Data in Msg4’ approach, there may be no or little motivation not to have a UE-specific MT-RNTI. This since contention may be resolved by step 5 in Figure 4, the wireless device 130 may, as of the legacy procedure, have a UE-specific Cell RNTI (C-RNTI) by that time for retransmission of the DL data and dedicated addressing of the wireless device 130.

[0077] Contention-free random access preamble allocation

[0078] In some examples, as part of the procedure, a contention-free random access (CFRA) preamble may be provided to the wireless device 130, e.g., a UE, in the paging message in this Action 201 , e.g., step 1 in Figure 4. This may be understood to strictly not be needed for UE identification and matching the paging to the subsequent RA attempt, this since, in RRCJNACTIVE, the full 40 bit l-RNTI identifier may be used in paging, and either full l-RNTI or the short 24 bit l-RNTI may be used in the RRCResumeRequest. However, the use of a CFRA preamble may ensure a collision free Random Access (RA), which may be understood to be beneficial. The use of a CFRA may also be beneficial in case of UE identification issues when the short l-RNTI may be used in the RRCResumeRequest.

[0079] Examples of the use of CFRA preamble will be provided in the next Action 202.

[0080] By, in this Action 201, the wireless device 130 receiving the first indication from the network node 110 indicating MT-SDT is being used, and the one or more resources for the MT- SDT procedure the wireless device 130 is to resume, while the wireless device 130 is in inactive state, the wireless device 130 may be enabled to then receive the mobile terminated small data transmission in inactive state, thereby avoiding a need to go into a connected state and thereby saving signalling, energy and time resources. Furthermore, by, in this Action 201 , the wireless device 130 specifically receiving the first indication indicating the one or more resources for the MT-SDT procedure the wireless device 130 is to resume, the wireless device 130 may be enabled to perform the resumption of resources in a more efficient manner, involving less processing than e.g., LTE, as the wireless device 130 may be enabled to refrain from resuming e.g., all data radio bearers, and may only resume the resources for MT-SDT.

[0081] By obtaining the CFRA preamble from the network node 110, the wireless device 130 may be enabled to then transmit it to the network node 110, and in turn, enabled the network node 110 to know, when it may receive it, who sent it. The network node 110 may then be enabled to reply using the MT-RNTI, since this specific wireless device 130 may be the only one who may receive the transmission to the MT-RNTI. All other wireless devices may listen for the RA-RNTI. The RA-RNTI may be used to respond to all UEs who may perform CBRA, and all these may decode messages to RA-RNTI, and many of them may discover that the message was intended for another wireless device.

[0082] By obtaining the MT-RNTI, reduced processing may be also enabled, compared to if MT- RNTI were not to be used, e.g., compared to if RA-RNTI were to be used.

[0083] Action 202

[0084] In this Action 202, the wireless device 130 sends a second indication. The sending in this Action 202 is to the network node 110.

[0085] The sending in this Action 202 may be, e.g., transmitting, and may be performed, e.g., via the first link 141.

[0086] The sending in this Action 202 is while the wireless device 130 is in inactive state and in response to the received first indication. The second indication comprises a preamble corresponding to a random access procedure. The second indication may be e.g., a Msg. 1 in a RA procedure.

[0087] In some embodiments, at least one of the following may apply. In some examples, the preamble may be a contention free random access (CFRA) procedure preamble. In some examples, as explained earlier, the preamble may be comprised in the received first indication. In some examples, the preamble may be to be used with one or more first conditions. The one or more first conditions may comprise at least one of the following.

[0088] According to a first option, the one or more first conditions may comprise that the preamble may be to be used with i) one or more timers obtained by the wireless device 130.

[0089] In one example, a timer may be provided to the wireless device 130, e.g., pre-determined or configured as part of the MT-SDT configuration, for the use of the CFRA preamble and, at expiration of the timer, the wireless device 130 may no longer be allowed to use the CFRA preamble. The motivation may be understood to be that the preamble space may be understood to be of limited size, and it may therefore be costly to allocate a CFRA preamble to the wireless device 130 long-term.

[0090] According to a second option, the one or more first conditions may comprise that the preamble may be to be used ii) a maximum number of times, e.g., N. That is, the maximum number of times the wireless device 130 may be allowed to use the preamble. In one example, a counter N may be configured for the wireless device 130, e.g., pre-determined or configured as part of the MT-SDT configuration, and the wireless device 130 may be only allowed for use the CFRA preamble N times after the MT-indication and the preamble may have been received in paging.

[0091] According to a third option, the one or more first conditions may comprise that the preamble may be to be used iii) within determined time resources, e.g., slots. In a different example, the use of CFRA preambles for a UE such as the wireless device 130 may be restricted to a few pre-determined slots. This may allow several UEs to share the same CFRA preamble in some pre-determined time- example slots in a time multiplexed fashion.

[0092] According to a fourth option, the one or more first conditions may comprise that the preamble may be to be used iv) as long as the wireless device 130 may fail to receive a response from the network node 110 to the sent second indication, e.g., as long as the wireless device 130 may fail to receive a Msg 2 or RAR from the network node 110 in the RA procedure. In one example, when the condition for using CFRA preambles may have expired, the wireless device 130 may continue to use Contention-Based Random Access (CBRA) preambles in case it may not receive a RAR. In one example, the preamble transmission counter may be reset to zero when the wireless device 130 may start to use CBRA preambles after using CFRA. In another example, the preamble transmission counter may not be reset after using CFRA. According to a fifth option, the one or more first conditions may comprise that the preamble may be to be used v) only in response to the first indication, with the proviso the first indication may comprise a further indication for mobile terminated data transmission / a mobile terminated data transmission procedure, e.g., an MT indication. In one example, the wireless device 130 may be only allowed to use the CFRA preamble in the response to the paging with MT-indication, and not for any other purpose. It may be understood that in some examples, the additional indication may be the same as the further indication.

[0093] According to a sixth option, the one or more first conditions may comprise that the preamble may be to be used vi) as long as the mobile terminated small data transmission procedure may not have finalized.

[0094] According to a seventh option, the one or more first conditions may comprise that the preamble may be to be used vii) as long as the wireless device 130 may not have received a radio resource control release request from the network node 110.

[0095] Any of the above may further be combined with the condition that the MT-SDT procedure may not have been finalized, e.g., the wireless device 130 may be allowed to use the CFRA preamble until the expiration of the configured timer, or reception of the RRCRelease in step 5, or something else which may terminate the MT-SDT procedure, whichever may be earlier.

[0096] As long as may be understood as, e.g., “with the proviso that”.

[0097] By, in this Action 202, sending the second indication to the network node 110 while the wireless device 130 is in inactive state, the second indication comprising the preamble, the wireless device 130 may trigger the RA procedure and may thereby be enabled to then receive the mobile terminated small data transmission in inactive state, thereby avoiding a need to go into a connected state and thereby saving signalling and time resources.

[0098] By the wireless device 130 sending the second indication comprising the CFRA preamble to the network node 110 while the wireless device 130 is in inactive state, the wireless device may trigger the RA procedure using contention free resources which may ensure that no collision may occur with other UEs.

[0099] Action 203

[0100] In this Action 203, the wireless device 130 may send a third indication. The sending in this Action 203 may be to the network node 110.

[0101] The sending in this Action 203 may be, e.g., transmitting, and may be performed, e.g., via the first link 141.

[0102] The sending in this Action 203 may be performed, after the sending 202 of the preamble, and before the receiving of the downlink transmission, which will be described in the next Action 204. The third indication may indicate a request to resume a radio resource control procedure with the network node 110.

[0103] The third indication may be, e.g., a Msg 3 in the RA procedure.

[0104] In some examples of embodiments herein, the legacy Random Access (RA) may be assumed to be used as the uplink response, and not RA-SDT or CG-SDT, as mandated by the MT-SDT WID for the following reasons: 1) the wireless device 130 uplink buffer may be typically empty and a larger Msg3 UL grant may lead to waste of resources, 2) the use of MT- SDT may be understood to not be limited to cells which may support RA-SDT or CG-SDT, 3) it was the approach used for LTE MT-EDT.

[0105] The request to resume the RRC procedure may be, e.g., an RRCResumeRequest.

[0106] The third indication may be sent after having received a response, e.g., Msg2, from the network node 110 to the sent second indication.

[0107] For additional description of the RRC resumption, see the section “RRC resumption of the wireless device 130 e.g., UE RRC resumption” in the description of Action 205.

[0108] Action 204

[0109] In this Action 204, the wireless device 130 receives a downlink transmission.

[0110] The receiving in this Action 204 is while the wireless device 130 is in inactive state and after having sent the preamble.

[0111] The receiving in this Action 204 is from the network node 110. The receiving in this Action 204 may be performed, e.g., via the first link 141.

[0112] The downlink transmission comprises data. A size of the data is under a threshold. In some examples, the data may be “Small Data”. In other words, the data may be configured for SDT. Particularly, the downlink transmission of the data under the threshold, wherein the downlink data may be mobile terminated, may be e.g., MT-SDT.

[0113] The downlink transmission may be received in a fourth indication. The fourth indication may be received in response to the sent third indication.

[0114] The fourth indication may be, e.g., a Msg 4 in the RA procedure.

[0115] By, in this Action 204, the wireless device 130 receiving the downlink transmission from the network node 110 while the wireless device 130 is in inactive state, the wireless device 130 is enabled to receive the mobile terminated small data transmission in inactive state, thereby avoiding a need to go into a connected state and thereby saving signalling and time resources.

[0116] Action 205

[0117] In this Action 205, the wireless device 130 may resume one or more resources.

[0118] The one or more resources may comprise, e.g., one or more radio bearers, e.g., data radio bearers. For example, the one or more resources, e.g., data radio bearers, may be for a mobile terminated small data transmission procedure.

[0119] The resuming in this Action 205 may be performed one of: i) after sending the third indication, ii) after receiving the fourth indication; wherein the fourth indication may indicate resumption of the radio resource control procedure, and iii) together with a re-establishment of Packet Data Convergence Protocol (PDCP) and Radio Link Control (RLC) entities.

[0120] The resuming in this Action 205 may comprise an RRC resumption.

[0121] RRC resumption of the wireless device 130 e.g., UE RRC resumption

[0122] There may be two alternatives for when the wireless device 130 may resume the RRC connection. Note that, since here the legacy RA procedure may be assumed to be used, a new condition in the procedure text may need to be added stating that the if the wireless device 130, e.g., the UE, triggered RA due to MT-SDT, e.g., an MT-indication was received in the paging message, the wireless device 130 may need to prepare for DL data transmission in Msg4 and resume the SDT Data Radio Bearer (DRB) accordingly. In NR for legacy RRC resume, that is, without Rel-17 Mobile Originated SDT (MO-SDT), the radio bearers may be fully resumed at first after the reception of RRCResume message, that is, “Msg4”. It may be noted that, with regards to the MT-indication itself, a similar MT-indication in paging may be used for LTE MT-EDT.

[0123] In a first alternative, the DRB for which MT-SDT may be configured may be resumed, according to this Action 205, at the transmission of RRCResumeRequest, that is, in “Msg3” or step 4 in Figure 4, together with Action 203. That is, even though the legacy RA procedure may be triggered, the radio bearers may be resumed at the transmission of RRCResumeRequest together with Action 203, that is, in “Msg3”, as for Rel-17 MO-SDT. See a non-limiting example of procedure text modifications to TS 38.331 , v. 17.0.0 below (changes underlined): 1> sdt-Config is configured; andl> all the pending data in UL is mapped to the radio bearers configured for SDT; and

[0124] 1> lower layers indicate that conditions for initiating SDT as specified in TS 38.321 [3] are fulfilled.

[0125] 5.3.13.1c Conditions for initiating MT-SDT

[0126] A UE in RRC INACTIVE initiates the resume procedure for MT-SDT when all of the following conditions are fulfilled:

[0127] 1> the upper layers request resumption of RRC connection; and

[0128] 1> SIB1 includes mtSdt-ConfigCommon', and

[0129] 1> mtSdt-Config is configured; and

[0130] 1> MT-indication was received in the paging message which triggered the RRC resumption request.

[0131] 5.3.13.2 Initiation

[0132] The UE initiates the procedure when upper layers or AS (when responding to RAN paging, upon triggering RNA updates while the UE is in RRC INACTIVE, for NR sidelink communication / V2X sidelink communication as specified in sub-clause 5.3.13.1a) requests the resume of a suspended RRC connection or for initiating SDT as specified in sub-clause 5.3.13.1b..

[0133] The UE shall ensure having valid and up to date essential system information as specified in clause 5.2.2.2 before initiating this procedure.

[0134] Upon initiation of the procedure, the UE shall:

[0135] 1> if the resumption of the RRC connection is triggered by response to Next Generation Radio Access Network (NG-RAN) paging:

[0136] <text omitted>

[0137] 1> apply the CCCH configuration as specified in 9.1.1.2;

[0138] 1> apply the timeAlignmentTimerCommon included in SIBP,

[0139] 1> if sdt-MAC-PHY-CG-Config is configured:

[0140] 2> if the resume procedure is initiated in a cell that is different to the PCell in which the UE received the stored sdt-MAC-PHY-CG-Config'.

[0141] 3> release the stored sdt-MAC-PHY-CG-Config',

[0142] 1> if conditions for initiating SDT in accordance with 5.3.13.1b are fulfilled: 2> consider the resume procedure is initiated for SDT;

[0143] 2> start timer T319a;

[0144] 1> if conditions for initiating MT-SDT in accordance with 5,3.13,1c are fulfilled:

[0145] 2> consider the resume procedure is initiated for MT-SDT;

[0146] 2> start timer T319b;

[0147] 1> else:

[0148] 2> start timer T319;

[0149] 2> instruct the MAC entity to consider the cg-SDT-TimeAlignmentTimer as expired, if it is running;

[0150] 1> set the variable pendingRNA-Update to false',

[0151] 1> initiate transmission of the RRCResumeRequest message or RRCResumeRequestl in accordance with 5.3.13.3.

[0152] 5.3.13.3 Actions related to transmission of RRCResumeRequest or RRCResumeRequestl message

[0153] The UE shall set the contents of RRCResumeRequest or RRCResumeRequestl message as follows:

[0154] 1> if field useFullResumelD is signalled in SIB1 :

[0155] <text omited>

[0156] 1> re-establish PDCP entities for SRB1;

[0157] 1> resume SRB1;

[0158] 1> if the resume procedure is initiated for SDT or for MT-SDT:

[0159] 2> for each radio bearer that is configured for SDT or for MT-SDT:

[0160] 3> restore the configuration associated with the RLC bearers of masterCellGroup and pdcp-Config from the UE Inactive AS context;

[0161] 3> re-establish PDCP entity for the radio bearer without triggering PDCP status report;

[0162] 2> resume all the radio bearers that are configured for SDT or for MT-SDT;

[0163] 1> submit the selected message RRCResumeRequest or RRCResumeRequestl for transmission to lower layers.

[0164] NOTE 2: Only DRBs with previously configured UP ciphering shall resume ciphering.

[0165] In a second alternative, the radio bearers may be resumed, according to this Action 205, at first after RRCResume that is, at “Msg4” reception, as depicted in the non-limiting example of Figure 4. In this case, the wireless device 130 may need to store the data Service Data Unit (SDU) on the DRB until the resumption may have been completed before it may process it.

[0166] Rel-17 MO-SDT may be configured per DRB, and in case the same approach is used for MT- SDT in Rel-18, there may, related to the above, be of interest to have a multi-bit MT-indication in paging to indicate to the wireless device 130 which DRB, QoS flow, or PDU session, or MT-SDT configuration the wireless device 130 may need to resume and which the MT-indication may be associated to. For example, a 2-bit MT-indication may point a configuration index for an MT-SDT configuration the wireless device 130 may have previously been configured with.

[0167] In some examples, at least one of the following may apply. In some examples, the additional indication may be multi-bit. In some examples, the one or more resources the wireless device 130 may be to resume may comprise at least one of: e.g., data radio bearer (DRB), Quality of Service (QoS) flow, Protocol Data Unit (PDU) session or configuration, e.g., MT-SDT configuration.

[0168] In the second alternative above related to embodiments herein, no MT-indication may need to be included at all. That is, if the wireless device 130 detects a data payload multiplexed with the RRCResume / RRCRelease, e.g., “Msg4” in legacy RA, and step 5 in Figure 4, this may act as an implicit MT-indication, the wireless device 130 may store the data SDU, resume the DRB according the information in the SDU header in this Action 205, alternatively using a new indication, e.g., RRC extension, Medium Access Control (MAC) Control Element (CE), etc. to then be able to process the DL data.

[0169] In another alternative example related to embodiments herein, all radio bearers that may be configured for SDT and / or MT-SDT may always be resumed, and their respective Packet Data Convergence Protocol (PDCP) and Radio Link Control (RLC) entities may be re-established at the transmission of RRCResumeRequest / RRCResumeRequestl . In this case, there may be no need for MT-indication.

[0170] Yet in another alternative example, all data radio bearers (DRBs) may be resumed and their respective PDCP and RLC entities may be re-established at the transmission of RRCResumeRequest / RRCResumeRequestl . In this case, not only DRBs configured for SDT / MT-SDT but also other DRBs may be ready for data transmission in Msg4. Therefore, there may even be no need to configure a DRB for MT-SDT.

[0171] Action 206

[0172] In this Action 206, the wireless device 130 may send a fifth indication.

[0173] The sending in this Action 206 may be to the network node 110.

[0174] The sending in this Action 206 may be, e.g., transmitting, and may be performed, e.g., via the first link 141.

[0175] The fifth indication may be in response to the downlink transmission, e.g., the received data. The sending in this Action 206 of the fifth indication may be optionally based on the resumed one or more resources, e.g., one or more radio bearers. The fifth indication may be e.g., HARQ information.

[0176] Enhanced support for application-layer response in uplink

[0177] A drawback with the ‘Data in Msg4’ approach may be that it may be terminated by the transmission of the DL data, e.g., step 5 in Figure 4. If the DL data triggers a response in UL on the application layer, e.g., the service response, which may typically have a delay of several 100 ms, the wireless device 130 may need to again trigger a RA procedure, which may not be optimal, e.g., scheduling request (SR) when there may be no available Physical Uplink Control CHannel (PUCCH) resources, the wireless device 130 may have already obtained a timing advance (TA), and therefore at least the preamble transmission in “Msg1” and Random Access Response (RAR) in “Msg2” may be unnecessary. The following part of this section lists potential approaches to this problem. Arrival of new UL data at the wireless device 130 may generate a buffer status report (BSR).

[0178] In some embodiments, the sending in Action 206 of the fifth indication may be performed based on a set of resources obtained by the wireless device 130, e.g., from the network node 110. In some examples, e.g., some of such examples, at least one of the following may apply: i) the set of resources may be obtained by the wireless device 130 in a configuration, ii) the set of resources may be indicated to the wireless device 130, e.g., with an index, iii) the fifth indication may comprise a buffer status report (BSR), iv) the set of resources may comprise first periodic resources on a physical uplink shared channel (PUSCH), v) the first periodic resources may be to be used with one or more second conditions, vi) the set of resources may comprise second periodic resources on a physical uplink control channel (PUCCH) and vii) the second periodic resources may be to be used with one or more third conditions.

[0179] In one example, the wireless device 130 may be provided with periodic PUSCH resources for transmission of the BSR. The one or more second conditions may be, e.g., that the PUSCH resources may be valid for a certain amount of time, e.g., their use may be allowed before the expiration of a pre-determined or configured timer, or a number of occasions, counter predetermined or configured. Further, a time gap may be defined, pre-determined or configured, between the MT-SDT DL data transmission that is, Action 205, e.g., step 5 in Figure 4, and the first periodic PLISCH resource. In one alternative, a time limited CG-SDT configuration may be used for this purpose. The configuration may be provided as part of the RRC message, e.g., RRCRelease, transmitted in Msg 4, or in paging message that may indicate MT-SDT explicitly or implicitly, or in Msg 2 if the network may identify that the wireless device 130, which may have transmitted Msg 1 , may intend to establish connection for MT-SDT.

[0180] In another example, the wireless device 130 may be provided with PLICCH resources, or scheduling request (SR) configuration. The one or more third conditions may be, e.g., that the PLICCH resources or SR configuration may be, valid for a certain amount of time, e.g., their use may be allowed before the expiration of a pre-determined or configured timer, or a number of occasions, e.g., the counter may be pre-determined or configured. In case of UL data arrival, the wireless device 130 may use the PLICCH resources to transmit SR to the network node 110, e.g., a gNB, and the network node 110 may then provide an UL-grant to the wireless device 130. Similar to legacy operation in RRC_CONNECTED, the wireless device 130 may be configured with a new SR configuration for use after the DL data delivery in MT-SDT procedure, Action 205, e.g., step 5 in Figure 4. Typically, PLICCH resources may be more infrequent in time, and may have a delay in the start matching the shortest expected latency for application-layer UL response. In one example, the PUCCH resources may be UE-specific, in which case it may be clear to the Action 205, e.g., which UE may transmit the SR. In another example, the PUCCH resources may be common, e.g., shared by all MT-SDT UEs, and a PUCCH configuration index may be provided to the wireless device 130 dynamically in the paging message, Action 201 , e.g., step 1 in Figure 4. For the examples above, the configuration may be provided as part of the RRC message, e.g., RRCRelease, transmitted in Msg 4, or in the paging message that may indicate MT-SDT explicitly or implicitly, or in Msg 2 if the network may identify that the wireless device 130, which may have transmitted Msg 1 may intend to establish connection for MT-SDT.

[0181] The request to release the connection may be e.g., an RRC Release request. The request to release may be comprised in the fourth indication.

[0182] In a related example, the wireless device 130 may finally send the UL data multiplexed with RLC status report, or a new PDCP control PDU. Once the wireless device 130 may send a BSR to indicate an application layer acknowledgement, the network node 110 may allocate a slightly larger UL grant which may optionally multiplex the UL data along with RLC status report or PDCP control PDU.

[0183] In some embodiments, after having received the downlink transmission from the network node 110, the wireless device 130 may fail to receive a request to release a connection to the network node 110, and may initiate a random access procedure with the network node 110 using one of the preamble and the temporary identifier, to receive an uplink grant.

[0184] In one example, the procedure may not be ended by the network node 110 response to Msg 3, that is, by “Msg 4”, e.g., the network node 110 may send the DL data but may not send the RRCRelease. In this case, both the UE-specific RNTI and potentially also the CFRA preamble may be valid. In case the UE-specific RNTI is valid, the wireless device 130 may initiate a RA procedure by sending a Msg 3 containing the UE-specific RNTI and a BSR to request an UL grant. In another example, when the CFRA preamble is still valid, e.g., it may be specified that it may be useable by the wireless device 130 until RRCRelease message reception, or the expiration of a timer, see above, the wireless device 130 may transmit the CFRA preamble and the network node 110 may respond with an UL grant.

[0185] Embodiments of a method, performed by a network node, such as the network node 110, will now be described with reference to the flowchart depicted in Figure 3. The method may be understood to be for handling downlink transmission, e.g., to a wireless device, such as the wireless device 130. The network node 110 operates in a wireless communications network, such as the wireless communications network 100.

[0186] In some embodiments, the wireless communications network 100 may support New Radio (NR). In some embodiments, the wireless communications network 100 operates on NR.

[0187] Several embodiments are comprised herein. The method comprises three or more of the following actions. Particularly, Action 303, Action 304 and Action 306 are performed. In some embodiments, all the actions may be performed. One or more embodiments may be combined, where applicable. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. All possible combinations are not described to simplify the description. A non-limiting example of the method performed by the network node 110 is depicted in Figure 3. In Figure 3, optional actions in some embodiments may be represented with dashed lines. In some embodiments, the actions may be performed in a different order than that depicted Figure 3.

[0188] The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the wireless device 130 and will thus not be repeated here to simplify the description. For example, data may be “Small Data”.

[0189] Action 301

[0190] In this Action 301, the network node 110 may receive the downlink data. The receiving in this Action 301 may be from the another network node 120 operating in the wireless communications network 100.

[0191] The receiving in this Action 301 may be performed, e.g., via the first link 141.

[0192] The receiving in this Action 301 may be, e.g., while the wireless device 130 may be in inactive state.

[0193] MT-SDT triggering

[0194] Unlike for LTE MT-EDT, the wireless device 130 may always be in RRCJNACTIVE state for NR MT-SDT. Therefore, the wireless device 130 may be in a connected state, e.g., CM_CONNECTED, from the CN point of view, and the CN, e.g., the another network node 120, for example, a User Plane Function (UPF) node, may forward any Downlink (DL) data to the last serving network node, such as, the network node 110, e.g., a gNB, e.g., anchor gNB. Unlike in MT-EDT, no MT-SDT / EDT indication may therefore be needed to be provided to the network node 110, e.g., last serving gNB, by the another network node 120, e.g., the UPF, the DL data may just be sent down to the network node 110, and it may be up to the network node 110, e.g., ‘last serving gNB’ or ‘paging gNB’, to, based on the size of the DL data, determine to use MT- SDT procedure or not.

[0195] In some examples, the wireless device 130 may be provided, by the network node 110, with the temporary identifier for the wireless device 130 in the wireless communications network 100, e.g., RNTI. The temporary identifier may be specific for the mobile terminated data transmission procedure, e.g., MT-RNTI.

[0196] The temporary identifier may be comprised in one of: a) the sent first indication, and b) the configuration for the mobile terminated small data transmission procedure (MT-SDT).

[0197] Action 302

[0198] In this Action 302, the network node 110 may determine whether or not to trigger the sending of the received downlink data to the wireless device 130.

[0199] Determining may comprise, calculating, deriving.

[0200] The determining in this Action 302 may comprise e.g., determining whether or not to use the mobile terminated small data transmission, e.g., MT-SDT, procedure. This may likely be up to Network (NW) implementation, and the network node 110 may base the decision on information such as: the size of the DL data, wireless device 130 support for MT-SDT, if the wireless device 130 is configured for MT-SDT, MT-SDT support in the network node 110 / cell, the number of previous paging attempts to the wireless device 130, if paging is from ‘last serving gNB’ or ‘neighbor gNB’, if subsequent data is expected, if an application-layer uplink response is expected, UE type or capabilities, etc.

[0201] The determining in this Action 302 may be based on the received downlink data. Action 303

[0202] In some embodiments, in this Action 303, the network node 110 sends the first indication.

[0203] The sending in this Action 303 is to the wireless device 130 operating in the wireless communications network 100.

[0204] The sending in this Action 303 may be performed, e.g., via the first link 141.

[0205] The sending in this Action 303 is while the wireless device 130 is in inactive state.

[0206] The first indication indicates the wireless device 130 is being paged, and the MT-SDT procedure is being used.

[0207] The first indication further comprises the additional indication of the mobile terminated procedure, e.g., MT-indication.

[0208] The additional indication further indicates the one or more resources for the MT-SDT procedure the wireless device 130 is to resume. The one or more resources comprise the one or more radio bearers.

[0209] In some examples, at least one of the following may apply: i) the additional indication may be multi-bit, and the one or more resources the wireless device 130 may be to resume may comprise at least one of: DRB, QoS flow, PDU session, or configuration, e.g., MT-SDT configuration.

[0210] Action 304

[0211] In this Action 304, the network node 110 receives the second indication.

[0212] The receiving in this Action 304 is from the wireless device 130.

[0213] The receiving in this Action 304 may be performed, e.g., via the first link 141.

[0214] The receiving in this Action 304 is while the wireless device 130 is in inactive state and in response to the sent first indication.

[0215] The second indication comprises the preamble corresponding to the random access procedure.

[0216] In some embodiments, at least one of the following may apply: a) the preamble may be the contention free random access procedure preamble, b) the preamble may be comprised in the sent first indication, c) the preamble may be to be used with the one or more first conditions; the one or more first conditions may comprise at least one of: i) the one or more timers provided to the wireless device 130, ii) the maximum number of times, iii) within the determined time resources, e.g., slots, iv) as long as the wireless device 130 may fail to receive a response from the network node 110 to the received second indication, v) only in response to the first indication, with the proviso the first indication may comprise the further indication indicating mobile terminated data transmission / a mobile terminated data transmission procedure, vi) as long as the mobile terminated small data transmission procedure may not have finalized, and vii) as long as the wireless device 130 may not have received the radio resource control release request from the network node 110.

[0217] Action 305

[0218] In this Action 305, the network node 110 may receive the third indication.

[0219] The receiving in this Action 305 may be from the wireless device 130.

[0220] The receiving in this Action 305 may be performed, e.g., via the first link 141.

[0221] The receiving in this Action 305 may be performed, after the receiving 304 of the preamble, and before the sending 306 of the downlink transmission.

[0222] The third indication may indicate the request to resume the radio resource control procedure with the network node 110.

[0223] The third indication may be received after having sent a response, e.g., Msg2, to the wireless device 130, to the sent second indication.

[0224] As stated earlier, in some examples of embodiments herein, the legacy Random Access (RA) may be assumed to be used as the uplink response, and not RA-SDT or CG-SDT, as mandated by the MT-SDT WID. Procedure enhancements, RAN2 related, are described above.

[0225] Action 306

[0226] In this Action 306, the network node 110 sends the downlink transmission.

[0227] The sending in this Action 306 is to the wireless device 130.

[0228] The sending in this Action 306 may be performed, e.g., via the first link 141.

[0229] The sending in this Action 306 is performed while the wireless device 130 is in inactive state. The inactive state may be, e.g., RRCJNACTIVE state.

[0230] The sending in this Action 306 is performed, e.g., after having received the preamble.

[0231] The downlink transmission comprises the data. The size of the data is under the threshold. In some examples, the data may be “Small Data”. Particularly, the downlink transmission of the data under the threshold, wherein the downlink data may be mobile terminated, may be e.g., MT-SDT.

[0232] The downlink transmission may be sent in the fourth indication. The fourth indication may be sent in response to the received third indication.

[0233] The sending in Action 306 of the downlink transmission may be based on the result of the determination of Action 302.

[0234] Action 307

[0235] In this Action 307, the network node 110 may resume the one or more resources.

[0236] The resuming in this Action 307 may comprise the RRC resumption. The one or more resources may comprise, e.g., the one or more radio bearers, e.g., data radio bearers.

[0237] For example, the one or more resources, e.g., data radio bearers, may be for the mobile terminated small data transmission procedure. The resuming in this Action 307 may be performed one of: i) after receiving the third indication, ii) after sending the fourth indication; the fourth indication may indicate resumption of the radio resource control procedure, and iii) together with the re-establishment of PDCP and RLC entities.

[0238] Action 308

[0239] In this Action 308, the network node 110 may receive the fifth indication.

[0240] The receiving in this Action 308 may be from the wireless device 130.

[0241] The receiving in this Action 308 may be performed, e.g., via the first link 141.

[0242] The fifth indication may be in response to the downlink transmission, e.g., the sent data. The receiving in this Action 308 of the fifth indication may be optionally based on the resumed one or more resources, e.g., one or more radio bearers. The fifth indication may be e.g., HARQ information.

[0243] In some embodiments, the receiving 308 of the fifth indication may be performed based on the set of resources provided to the wireless device 130, e.g., by the network node 110. In some examples, e.g., some of such examples, at least one of the following may apply: i) the set of resources may be provided to the wireless device 130 in the configuration, ii) the set of resources may be indicated to the wireless device 130, e.g., with the index, iii) the fifth indication may comprise the buffer status report, iv) the set of resources may comprise the first periodic resources on the physical uplink shared channel (PLISCH), v) the first periodic resources may be to be used with the one or more second conditions, vi) the set of resources may comprise the second periodic resources on the physical uplink control channel (PLICCH), and, vii) the second periodic resources may be to be used with the one or more third conditions.

[0244] In some embodiments, after having sent the downlink transmission to the wireless device 130, the network node 110 may refrain from sending to the wireless device 130 the request to release the connection to the network node 110, and the network node 110 may receive the request from the wireless device 130 to initiate the random access procedure with the network node 110 using the one of the preamble and the temporary identifier, to receive the uplink grant.

[0245] Some embodiments herein will now be further described with some non-limiting examples, which may be combined with the embodiments just described.

[0246] The signaling procedure for the MT-SDT approach ‘Data in Msg4’ for NR, according to embodiments herein, may be as outlined in Figure 4. In the non-limiting example of Figure 4, the wireless device 130 is a UE, the network node 110 is a gNB, and the another node 120 is a UPF. Herein, the legacy Random Access (RA) may be assumed to be used as the uplink response, and not RA-SDT or CG-SDT, as mandated by the MT-SDT WID for the following reasons: 1) the UE uplink buffer may be typically empty and a larger Msg3 UL grant may lead to waste of resources, 2) the use of MT-SDT may be understood to not be limited to cells which may support RA-SDT or CG-SDT, 3) it was the approach used for LTE MT-EDT. Unlike for LTE MT-EDT, the UE may always be in RRCJNACTIVE state for NR MT-SDT. Therefore, the UE may be in a connected state, e.g., CM_CONNECTED, from the CN point of view, and the CN, e.g., a User Plane Function (UPF) node, may forward any Downlink (DL) data to the last serving gNB, e.g., anchor gNB. After data may arrive at the another network node 120, in accordance with Action, 301 , the network node 110 receives the DL data from the another node 120. Unlike in MT-EDT, no MT-SDT / EDT indication may therefore be needed to be provided to the last serving gNB by the UPF, the DL data may just be sent down to the gNB, and it may be up to the gNB, e.g., ‘last serving gNB’ or ‘paging gNB’, to, based on the size of the DL data, determine, according to Action 302, to use MT-SDT procedure or not. As part of the procedure, a contention-free random access (CFRA) preamble may be provided to the UE in a paging message according to Action 303 and Action 201 , e.g., step 1 in Figure 4. Paging may be sent in the Physical Downlink Control Channel (PDCCH), a paging message may be sent in the Physical Downlink Shared Channel, comprising a paging record and an MT indication. In one example, a new RNTI, e.g., MT-RNTI, may be provided to the UE in paging, e.g., in step 1 in Figure 4, for use in the subsequent RA procedure. The MT-RNTI may either be UE-specific or common to all MT-SDT UEs, but for the ‘Data in Msg4’ approach, there may be no or little motivation not to have a UE-specific MT-RNTI. This since contention may be resolved by step 5 in Figure 4, the UE may, as of the legacy procedure, have a UE-specific Cell RNTI (C-RNTI) by that time for retransmission of the DL data and dedicated addressing of the UE. In Step 2, according to Action 304 and Action 202, the network node 110 may receive the second indication from the wireless device 130 comprising the RA / CFRA preamble, according to a non- SDT procedure ,e.g., RA-SDT resources may be not used. At Step 3, in response to the received second indication, the network node 110 may send a RA response in PDCCH and PUSCH. Next, RRC resumption may be initiated. At Step 4, in accordance with Action 203 and Action 305, the wireless device 130 may send an RRCResumeRequest in PUSCH to the network node 110, in “Msg3” or step 4 in Figure 4. Even though the legacy RA procedure may be triggered, the radio bearers may be resumed at the transmission of RRCResumeRequest, that is, in “Msg3”. The wireless device 130 may then receive a HARQ Ack from the network node 110 in response. At Step 5, in accordance with Action 204 and Action 306, the wireless device 130 may detect a data payload multiplexed with the RRCResume / RRCRelease, e.g., “Msg4” in legacy RA, and step 5 in Figure 4, this may act as an implicit MT-indication, the UE may store the data SDU, resume the DRB according the information in the SDU header in agreement with Action 205 and 307, alternatively using a new indication, e.g., RRC extension, Medium Access Control (MAC) Control Element (CE), etc. to then be able to process the DL data. The RRCRelease and the DL data may be received in the PDSCH. PDCCH may indicate the format and time / frequency resources that may be used for the data carried by the PDSCH. Next, according to Action 206 and Action 308, the wireless device 130 may send a HARQ Ack to the network node 110. Other details or alternative examples of the method depicted in Figure 4 have already been provided in the description of Figure 2 and Figure 3.

[0247] As a summarized overview of the foregoing, embodiments disclosed herein may provide enhancements of the MT-SDT ‘Data in Msg4’ approach for NR, e.g., compared to LTE MT-EDT.

[0248] Certain embodiments disclosed herein may provide one or more of the following technical advantage(s), which may be summarized as follows. Embodiments herein, may be understood to enable the ‘Data in Msg4’ approach for NR, and also to further reduce the signaling overhead.

[0249] Figure 5 depicts two different examples in panels a) and b), respectively, of the arrangement that the wireless device 130 may comprise to perform the method actions described above in relation to Figure 2 and / or Figure 4. In some embodiments, the wireless device 130 may comprise the following arrangement depicted in Figure 5a. The wireless device 130 may be understood to be for handling the downlink transmission. The wireless device 130 is configured to operate in the wireless communications network 100.

[0250] In some embodiments, the wireless communications network 100 may be configured to operate on NR.

[0251] Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the wireless device 130, and will thus not be repeated here. For example, the in some embodiments, data may be “Small Data”.

[0252] As stated earlier, herein, the legacy Random Access (RA) may be assumed to be configured to be used as the uplink response, and not RA-SDT or CG-SDT, as mandated by the MT-SDT WID for the following reasons: 1) the wireless device 130 uplink buffer may be typically empty and a larger Msg3 UL grant may lead to waste of resources, 2) the use of MT- SDT may be understood to not be limited to cells which may support RA-SDT or CG-SDT, 3) it was the approach used for LTE MT-EDT.

[0253] In Figure 5, optional units are indicated with dashed boxes.

[0254] The wireless device 130 is configured to perform the receiving in Action 201 , e.g., by means of a receiving unit 501 within the wireless device 130, configured to receive, while the wireless device 130 is in inactive state, the first indication from the network node 110 configured to operate in the wireless communications network 100. The first indication is configured to indicate the wireless device 130 is being paged, and the MT-SDT procedure is being used. The first indication is further configured to comprise the additional indication of the mobile terminated procedure. The additional indication is further configured to indicate the one or more resources for the MT-SDT procedure the wireless device 130 is to resume. The one or more resources are configured to comprise the one or more radio bearers.

[0255] The wireless device 130 is configured to perform the sending in Action 202, e.g., by means of a sending unit 502 within the wireless device 130, configured to send, to the network node 110, while the wireless device 130 is in inactive state and in response to the received first indication, the second indication. The second indication is configured to comprise the preamble corresponding to the random access procedure.

[0256] The wireless device 130 is also configured to perform the receiving in Action 204, e.g., by means of the receiving unit 501 , configured to receive, while the wireless device 130 is in inactive state and after having sent the preamble, the downlink transmission from the network node 110. The downlink transmission is configured to comprise data. The size of the data is configured to be under the wireless communications network 100 is configured to operate on New Radio, NR threshold.

[0257] In some embodiments, one of the following options may apply. According to a first option, the preamble may be configured to be the contention free random access procedure preamble. According to a second option, the preamble may be configured to be comprised in the first indication configured to be received. According to a third option, the preamble may be configured to be to be used with the one or more first conditions. The one or more first conditions may be configured to comprise at least one of: i) the one or more timers configured to be obtained by the wireless device 130, ii) the maximum number of times, iii) within determined time resources, iv) as long as the wireless device 130 fails to receive the response from the network node 110 to the second indication configured to be sent, v) only in response to the first indication, with the proviso the first indication is configured to comprise the further indication indicating mobile terminated data transmission / a mobile terminated data transmission procedure, vi) as long as the mobile terminated small data transmission procedure has not finalized, and vii) as long as the wireless device 130 has not received the radio resource control release request from the network node 110. The wireless device 130 may be configured to perform the sending in Action 203, e.g., by means of the sending unit 502 within the wireless device 130, configured to, after the sending of the preamble, and before the receiving of the downlink transmission, send the third indication to the network node 110. The third indication may be configured to indicate the request to resume the radio resource control procedure with the network node 110. The downlink transmission may be configured to be received in the fourth indication configured to be received in response to the third indication configured to be sent.

[0258] The wireless device 130 may be configured to perform the resuming of Action 205, e.g., by means of a resuming unit 503 within the wireless device 130, configured to resume the one or more resources. The resuming may be configured to be performed one of: i) after sending the third indication, ii) after receiving the fourth indication, the fourth indication being configured to indicate resumption of the radio resource control procedure, and iii) together with the reestablishment of Packet Data Convergence Protocol (PDCP), and Radio Link Control (RLC), entities.

[0259] The wireless device 130 may be configured to perform the sending in Action 206, e.g., by means of the sending unit 502, configured to send the fifth indication to the network node 110. The fifth indication may be configured to be in response to the downlink transmission. The sending of the fifth indication may be optionally configured to be based on the one or more resources configured to be resumed.

[0260] In some embodiments, wherein the wireless device 130 may be configured to obtain the temporary identifier for the wireless device 130 in the wireless communications network 100, the temporary identifier being configured to be specific for the mobile terminated data transmission procedure, the temporary identifier may be configured to be comprised in one of: a) the first indication configured to be received, and b) the configuration for the mobile terminated small data transmission procedure.

[0261] In some embodiments at least one of the following may apply: a) the additional indication may be configured to be multi-bit, and b) the one or more resources the wireless device 130 may be configured to resume may be configured to comprise at least one of: DRB, QoS flow, Protocol Data Unit, PDU session, or configuration.

[0262] In some embodiments, the sending of the fifth indication may be configured to be performed based on the set of resources configured to be obtained by the wireless device 130, and at least one of the following may apply: i) the set of resources may be configured to be obtained by the wireless device 130 in a configuration, ii) the set of resources may be configured to be indicated to the wireless device 130, iii) the fifth indication may be configured to comprise the buffer status report, iv) the set of resources may be configured to comprise the first periodic resources on the PUSCH, v) the first periodic resources may be configured to be used with the one or more second conditions, vi) the set of resources may be configured to comprise the second periodic resources on the PLICCH, and vii) the second periodic resources may be configured to be used with the one or more third conditions.

[0263] In some embodiments, the wireless device 130 may be further configured to, with the proviso that, after having received the downlink transmission from the network node 110 the wireless device 130 fails to receive the request to release the connection to the network node 110, initiate the random access procedure with the network node 110 using one of the preamble and the temporary identifier, to receive the uplink grant.

[0264] Other units 504 may be comprised in the wireless device 130.

[0265] The embodiments herein in the wireless device 130 may be implemented through one or more processors, such as a processor 505 in the wireless device 130 depicted in Figure 5a, together with computer program code for performing the functions and actions of the embodiments herein. A processor, as used herein, may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the wireless device 130. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the wireless device 130.

[0266] The wireless device 130 may further comprise a memory 506 comprising one or more memory units. The memory 506 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the wireless device 130.

[0267] In some embodiments, the wireless device 130 may receive information from, e.g., the network node 110 or the another network node 120, through a receiving port 507. In some embodiments, the receiving port 507 may be, for example, connected to one or more antennas in wireless device 130. In other embodiments, the wireless device 130 may receive information from another structure in the wireless communications network 100 through the receiving port 507. Since the receiving port 507 may be in communication with the processor 505, the receiving port 507 may then send the received information to the processor 505. The receiving port 507 may also be configured to receive other information.

[0268] The processor 505 in the wireless device 130 may be further configured to transmit or send information to e.g., the network node 110, the another network node 120 and / or another structure in the wireless communications network 100, through a sending port 508, which may be in communication with the processor 505, and the memory 506.

[0269] Those skilled in the art will also appreciate that the different units 501-504 described above may refer to a combination of analog and digital modules, and / or one or more processors configured with software and / or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processor 505, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

[0270] Also, in some embodiments, the different units 501-504 described above may be implemented as one or more applications running on one or more processors such as the processor 505.

[0271] Thus, the methods according to the embodiments described herein for the wireless device 130 may be respectively implemented by means of a computer program 509 product, comprising instructions, i.e., software code portions, which, when executed on at least one processor 505, cause the at least one processor 505 to carry out the actions described herein, as performed by the wireless device 130. The computer program 509 product may be stored on a computer-readable storage medium 510. The computer-readable storage medium 510, having stored thereon the computer program 509, may comprise instructions which, when executed on at least one processor 505, cause the at least one processor 505 to carry out the actions described herein, as performed by the wireless device 130. In some embodiments, the computer-readable storage medium 510 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 509 product may be stored on a carrier containing the computer program 509 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 510, as described above.

[0272] The wireless device 130 may comprise a communication interface configured to facilitate communications between the wireless device 130 and other nodes or devices, e.g., the network node 110, the another network node 120 and / or another structure in the wireless communications network 100. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

[0273] In other embodiments, the wireless device 130 may comprise the following arrangement depicted in Figure 5b. The wireless device 130 may comprise a processing circuitry 505, e.g., one or more processors such as the processor 505, in the wireless device 130 and the memory 506. The wireless device 130 may also comprise a radio circuitry 511, which may comprise e.g., the receiving port 507 and the sending port 508. The processing circuitry 511 may be configured to, or operable to, perform the method actions according to Figure 2 and / or Figure 4, in a similar manner as that described in relation to Figure 5a. The radio circuitry 511 may be configured to set up and maintain at least a wireless connection with the network node 110, the another network node 120 or another structure in the wireless communications network 100. Circuitry may be understood herein as a hardware component.

[0274] Hence, embodiments herein also relate to the wireless device 130 comprising the processing circuitry 505 and the memory 506, said memory 506 containing instructions executable by said processing circuitry 505, whereby the wireless device 130 is operative to perform the actions described herein in relation to the wireless device 130, e.g., in Figure 2 and / or Figure 4.

[0275] Figure 6 depicts two different examples in panels a) and b), respectively, of the arrangement that the network node 110 may comprise to perform the method actions described above in relation to Figure 3 and / or Figure 4. In some embodiments, the network node 110 may comprise the following arrangement depicted in Figure 6a. The network node 110 may be understood to be for handling the downlink transmission. The network node 110 is configured to operate in the wireless communications network 100.

[0276] In some embodiments, the wireless communications network 100 may be configured to operate on NR.

[0277] Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the wireless device 130 and will thus not be repeated here. For example, the in some embodiments, data may be “Small Data”.

[0278] As stated earlier, herein, the legacy Random Access (RA) may be assumed to be configured to be used as the uplink response, and not RA-SDT or CG-SDT, as mandated by the MT-SDT WID for the following reasons: 1) the wireless device 130 uplink buffer may be typically empty and a larger Msg3 UL grant may lead to waste of resources, 2) the use of MT- SDT may be understood to not be limited to cells which may support RA-SDT or CG-SDT, 3) it was the approach used for LTE MT-EDT.

[0279] In Figure 6, optional modules are indicated with dashed boxes.

[0280] In Figure 6, optional units are indicated with dashed boxes.

[0281] The network node 110 is configured to perform the sending in Action 303, e.g., by means of a sending unit 601 within the network node 110, configured to send, while the wireless device 130 is in inactive state, the first indication to the wireless device 130 configured to operate in the wireless communications network 100. The first indication is configured to indicate the wireless device 130 is being paged, and the MT-SDT procedure is being used. The first indication is further configured to comprise the additional indication of the mobile terminated procedure. The additional indication is further configured to indicate the one or more resources for the MT-SDT procedure the wireless device 130 is to resume. The one or more resources are configured to comprise the one or more radio bearers.

[0282] The network node 110 is configured to perform the receiving in Action 304, e.g., by means of a receiving unit 602 within the network node 110, configured to receive, from the wireless device 130, while the wireless device 130 is in inactive state and in response to the sent first indication, the second indication. The second indication is configured to comprise the preamble corresponding to the random access procedure.

[0283] The network node 110 is configured to perform the sending in Action 306, e.g., by means of the sending unit 601 within the network node 110, configured to send, while the wireless device 130 is in inactive state and after having received the preamble, the downlink transmission to the wireless device 130. The downlink transmission is configured to comprise the data. The size of the data is configured to be under the threshold.

[0284] According to a first option, the preamble may be configured to be the contention free random access procedure preamble. According to a second option, the preamble may be configured to be comprised in the first indication configured to be sent. According to a third option, the preamble may be configured to be to be used with the one or more first conditions. The one or more first conditions may be configured to comprise at least one of: i) the one or more timers configured to be provided to the wireless device 130, ii) the maximum number of times, iii) within determined time resources, iv) as long as the wireless device 130 fails to receive the response from the network node 110 to the second indication configured to be received, v) only in response to the first indication, with the proviso the first indication is configured to comprise the further indication indicating mobile terminated data transmission / a mobile terminated data transmission procedure, vi) as long as the mobile terminated small data transmission procedure has not finalized, and vii) as long as the wireless device 130 has not received the radio resource control release request from the network node 110.

[0285] The network node 110 may be configured to perform the receiving in Action 305, e.g., by means of the receiving unit 602, configured to, after the receiving of the preamble, and before the sending of the downlink transmission, receive the third indication from the wireless device 130. The third indication may be configured to indicate the request to resume the radio resource control procedure with the network node 110. The downlink transmission may be configured to be sent in the fourth indication configured to be sent in response to the third indication configured to be received.

[0286] In some embodiments, the network node 110 may be further configured to at least one of the following two options. In some embodiments, the network node 110 may be further configured to perform the resuming in Action 307, e.g., by means of a resuming unit 603, configured to resume the one or more resources. The resuming may be configured to be performed one of: i) after receiving the third indication, ii) after sending the fourth indication, the fourth indication being configured to indicate resumption of the radio resource control procedure, and iii) together with the reestablishment of PDCP and RLC entities.

[0287] In some embodiments, the network node 110 may be configured to perform the receiving in Action 308, e.g., by means of the receiving unit 602, configured to receive the fifth indication from the wireless device 130. The fifth indication may be configured to be in response to the downlink transmission. The receiving of the fifth indication may be configured to be optionally based on the one or more resources configured to be resumed.

[0288] In some embodiments, wherein the wireless device 130 may be configured to be provided, by the network node 110, with the temporary identifier for the wireless device 130 in the wireless communications network 100, the temporary identifier being configured to be specific for the mobile terminated data transmission procedure, the temporary identifier may be configured to be comprised in one of: a) the first indication configured to be sent, and b) the configuration for the mobile terminated small data transmission procedure.

[0289] In some embodiments, at least one of the following may apply: a) the additional indication may be configured to be multi-bit, and b) the one or more resources the wireless device 130 may be configured to resume may be configured to comprise at least one of: DRB, QoS flow, Protocol Data Unit, PDU session, or configuration.

[0290] In some embodiments, the receiving of the fifth indication may be configured to be performed based on the set of resources configured to be provided to the wireless device 130, and at least one of the following may apply: i) the set of resources may be configured to be provided to the wireless device 130 in a configuration, ii) the set of resources may be configured to be indicated to the wireless device 130, iii) the fifth indication may be configured to comprise the buffer status report, iv) the set of resources may be configured to comprise the first periodic resources on the PUSCH, v) the first periodic resources may be configured to be used with the one or more second conditions, vi) the set of resources may be configured to comprise the second periodic resources on the PUCCH, and vii) the second periodic resources may be configured to be used with the one or more third conditions.

[0291] In some embodiments, the wireless device 130 may be further configured to, with the proviso that, after having received the downlink transmission from the network node 110 the wireless device 130 fails to receive the request to release the connection to the network node 110, initiate the random access procedure with the network node 110 using one of the preamble and the temporary identifier, to receive the uplink grant. In some embodiments, after having sent the downlink transmission to the wireless device 130, the network node 110 may be configured to refrain from sending to the wireless device 130 the request to release the connection to the network node 110, and the network node 110 may be configured to receive a request from the wireless device 130 to initiate a random access procedure with the network node 110 using one of the preamble and the temporary identifier, to receive the uplink grant.

[0292] The network node 110 may be configured to perform the receiving in Action 301, e.g., by means of the receiving unit 602, configured to receive the downlink data from the another network node 120 configured to operate in the wireless communications network 100.

[0293] The network node 110 may be configured to perform the determining in Action 302, e.g., by means of a determining unit 604, configured to determine, based on the received downlink data, whether or not to trigger the sending of the received downlink data to the wireless device 130, and the sending of the downlink transmission may be configured to be based on the result of the determination.

[0294] Other units 605 may be comprised in the network node 110.

[0295] The embodiments herein in the network node 110 may be implemented through one or more processors, such as a processor 606 in the network node 110 depicted in Figure 6a, together with computer program code for performing the functions and actions of the embodiments herein. A processor, as used herein, may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the network node 110. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the network node 110.

[0296] The network node 110 may further comprise a memory 607 comprising one or more memory units. The memory 607 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the network node 110.

[0297] In some embodiments, the network node 110 may receive information from, e.g., the wireless device 130 and / or the another network node 120, through a receiving port 608. In some embodiments, the receiving port 608 may be, for example, connected to one or more antennas in network node 110. In other embodiments, the network node 110 may receive information from another structure in the wireless communications network 100 through the receiving port 608. Since the receiving port 608 may be in communication with the processor 606, the receiving port 608 may then send the received information to the processor 606. The receiving port 608 may also be configured to receive other information. The processor 606 in the network node 110 may be further configured to transmit or send information to e.g., the wireless device 130, the another network node 120, and / or another structure in the wireless communications network 100, through a sending port 609, which may be in communication with the processor 606, and the memory 607.

[0298] Those skilled in the art will also appreciate that the different units 601-605 described above may refer to a combination of analog and digital modules, and / or one or more processors configured with software and / or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processor 606, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

[0299] Also, in some embodiments, the different units 601-605 described above may be implemented as one or more applications running on one or more processors such as the processor 606.

[0300] Thus, the methods according to the embodiments described herein for the network node 110 may be respectively implemented by means of a computer program 610 product, comprising instructions, i.e. , software code portions, which, when executed on at least one processor 606, cause the at least one processor 606 to carry out the actions described herein, as performed by the network node 110. The computer program 610 product may be stored on a computer-readable storage medium 611. The computer-readable storage medium 611, having stored thereon the computer program 610, may comprise instructions which, when executed on at least one processor 606, cause the at least one processor 606 to carry out the actions described herein, as performed by the network node 110. In some embodiments, the computer-readable storage medium 611 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 610 product may be stored on a carrier containing the computer program 610 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 611, as described above.

[0301] The network node 110 may comprise a communication interface configured to facilitate communications between the network node 110 and other nodes or devices, e.g., the wireless device 130, the another network node 120, and / or another structure in the wireless communications network 100. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

[0302] In other embodiments, the network node 110 may comprise the following arrangement depicted in Figure 6b. The network node 110 may comprise a processing circuitry 606, e.g., one or more processors such as the processor 606, in the network node 110 and the memory 607. The network node 110 may also comprise a radio circuitry 612, which may comprise e.g., the receiving port 608 and the sending port 609. The processing circuitry 606 may be configured to, or operable to, perform the method actions according to Figure 3 and / or Figure 4, in a similar manner as that described in relation to Figure 6a. The radio circuitry 612 may be configured to set up and maintain at least a wireless connection with the wireless device 130, and / or another structure in the wireless communications network 100. Circuitry may be understood herein as a hardware component.

[0303] Hence, embodiments herein also relate to the network node 110 comprising the processing circuitry 606 and the memory 607, said memory 607 containing instructions executable by said processing circuitry 606, whereby the network node 110 is operative to perform the actions described herein in relation to the network node 110, e.g., in Figure 3, and / or Figure 4.

[0304] Embodiments herein may be related to Small Data Transmissions, Inactive state, SDT, Configured Grant, Random Access, MT-SDT, EDT, RA-SDT, and / or CG-SDT.

[0305] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0306] As used herein, the expression “at least one of:” followed by a list of alternatives separated by commas, and wherein the last alternative is preceded by the “and” term, may be understood to mean that only one of the list of alternatives may apply, more than one of the list of alternatives may apply or all of the list of alternatives may apply. This expression may be understood to be equivalent to the expression “at least one of:” followed by a list of alternatives separated by commas, and wherein the last alternative is preceded by the “or” term.

[0307] Examples related to embodiments herein:

[0308] The following are examples related to embodiments herein: The wireless device 130 examples relate to Figure 7, Figure 4, Figure 5 and Figures 9-

[0309] 14.

[0310] A method, performed by a wireless device, such as the wireless device 130 is described herein. The method may be understood to be for handling downlink transmission to a network node, such as the network node 110. The wireless device 130 may be operating in a wireless communications network, such as the wireless communications network 100.

[0311] In some examples, the wireless communications network 100 may support New Radio (NR).

[0312] The method may comprise one or more of the following actions. In some examples, all the actions may be performed. One or more examples may be combined, where applicable. Components from one example may be tacitly assumed to be present in another example and it will be obvious to a person skilled in the art how those components may be used in the other exemplary examples. All possible combinations are not described to simplify the description. A non-limiting example of the method performed by the wireless device 130 is depicted in Figure 7. In Figure 7, optional actions in some examples may be represented with dashed lines. In some examples, the actions may be performed in a different order than that depicted Figure 7. o Receiving 201 a first indication. The wireless device 130 may be configured to perform the receiving in this Action 201, e.g., by means of a receiving unit 501 within the wireless device 130, configured to perform this action.

[0313] The receiving in this Action 201 may be from the network node 110 operating in the wireless communications network 100.

[0314] The receiving in this Action 201 may be performed, e.g., via the first link 141.

[0315] The receiving in this Action 201 may be performed while the wireless device 130 may be in inactive state. The inactive state may be, e.g., RRCJNACTIVE state.

[0316] The first indication may indicate at least one of:

[0317] - the wireless device 130 may be being paged,

[0318] -a mobile terminated small data transmission procedure, e.g., MT-SDT, may be being used.

[0319] The first indication may be, e.g., a paging message. o Sending 202 a second indication. The wireless device 130 may be configured to perform the sending in this Action 202, e.g., by means of a sending unit 502 within the wireless device 130, configured to perform this action.

[0320] The sending in this Action 202 may be to the network node 110.

[0321] The sending in this Action 202 may be, e.g., transmitting, and may be performed, e.g., via the first link 141. The sending in this Action 202 may be, e.g., while the wireless device 130 may be in inactive state and in response to the received first indication.

[0322] The second indication may comprise a preamble corresponding to a random access procedure. The second indication may be e.g., a Msg. 1 in a RA procedure.

[0323] In some examples, at least one of the following may apply:

[0324] - the preamble may be a contention free random access procedure preamble,

[0325] - the preamble may be comprised in the received first indication,

[0326] - the preamble may be to be used with one or more first conditions; the one or more first conditions may comprise at least one of: i. one or more timers obtained by the wireless device 130, ii. a maximum number of times, e.g., N, iii. within determined time resources, e.g., slots, iv. as long as the wireless device 130 may fail to receive a response from the network node 110 to the sent second indication, e.g., as long as the wireless device 130 may fail to receive a Msg. 2 or RAR from the network node 110 in the RA procedure, v. only in response to the first indication, with the proviso the first indication may comprise a further indication for mobile terminated data transmission / a mobile terminated data transmission procedure, e.g., and MT indication, vi. as long as the mobile terminated small data transmission procedure may not have finalized, and vii. as long as the wireless device 130 may not have received a radio resource control release request from the network node 110.

[0327] As long as may be understood as, e.g., “with the proviso that”. o Receiving 204 a downlink transmission. The wireless device 130 may be configured to perform the receiving in this Action 204, e.g., by means of the receiving unit 501, configured to perform this action.

[0328] The receiving in this Action 204 may be, e.g., while the wireless device 130 may be in inactive state and, e.g., after having sent the preamble.

[0329] The receiving in this Action 204 may be from the network node 110.

[0330] The downlink transmission may comprise data. The size of the data may be under a threshold. In some examples, the data may be “Small Data”. Particularly, the downlink transmission of the data under the threshold, wherein the downlink data may be mobile terminated, may be e.g., MT-SDT. o Sending 203 a third indication. The wireless device 130 may be configured to perform the sending in this Action 203, e.g., by means of the sending unit 502 within the wireless device 130, configured to perform this action.

[0331] The sending in this Action 203 may be to the network node 110.

[0332] The sending in this Action 203 may be, e.g., transmitting, and may be performed, e.g., via the first link 141.

[0333] The sending in this Action 203 may be performed, after the sending 202 of the preamble, and before the receiving 204 of the downlink transmission.

[0334] The third indication may indicate a request to resume a radio resource control procedure with the network node 110. The downlink transmission may be received in a fourth indication. The fourth indication may be received in response to the sent third indication.

[0335] The third indication may be, e.g., a Msg 3 in the RA procedure.

[0336] The request to resume the RRC procedure may be, e.g., an RRCResumeRequest.

[0337] The fourth indication may be, e.g., a Msg. 4 in the RA procedure.

[0338] The third indication may be sent after having received a response, e.g., Msg2, from the network node 110 to the sent second indication.

[0339] In some examples, the method may further comprise one or more of the following actions: o Resuming 205 one or more resources. The wireless device 130 may be configured to perform the resuming of this Action 205, e.g., by means of a resuming unit 503 within the wireless device 130, configured to perform this action.

[0340] The resuming in this Action 205 may comprise an RRC resumption.

[0341] The one or more resources may comprise, e.g., one or more radio bearers, e.g., data radio bearers.

[0342] For example, the one or more resources, e.g., data radio bearers, may be for a mobile terminated small data transmission procedure. The resuming in this Action 205 may be performed one of: i. after sending the third indication, ii. after receiving the fourth indication; the fourth indication may indicate resumption of the radio resource control procedure, and iii. together with a re-establishment of Packet Data Convergence Protocol (PDCP) and Radio Link Control (RLC) entities. o Sending 206 a fifth indication. The wireless device 130 may be configured to perform the sending in this Action 206, e.g., by means of the sending unit 502, configured to perform this action.

[0343] The sending in this Action 206 may be to the network node 110.

[0344] The fifth indication may be in response to the downlink transmission, e.g., the received data. The sending in this Action 206 of the fifth indication may be optionally based on the resumed one or more resources, e.g., one or more radio bearers. The fifth indication may be e.g., HARQ information.

[0345] In some examples, the wireless device 130 may obtain a temporary identifier for the wireless device 130 in the wireless communications network 100, e.g., RNTI. The temporary identifier may be specific for a mobile terminated data transmission procedure, e.g., MT-RNTI.

[0346] The temporary identifier may be comprised in one of: the received first indication, and a configuration for a mobile terminated small data transmission procedure, e.g., MT- SDT.

[0347] In some examples, the first indication may further comprise at least one of:

[0348] - an additional indication of a mobile terminated procedure, e.g., MT-indication,

[0349] - the additional indication, wherein the additional indication may be multi-bit,

[0350] - the multi-bit additional indication, indicating one or more resources to resume, e.g., data radio bearer (DRB), Quality of Service (QoS) flow, Protocol Data Unit (PDU) session, MT- SDT configuration, and

[0351] - the additional indication, wherein the additional indication may further indicate one or more resources the wireless device 130 may be to resume, e.g., DRB, QoS flow, PDU session, or configuration, e.g., MT-SDT configuration.

[0352] In some examples, the sending 206 of the fifth indication may be performed based on a set of resources obtained by the wireless device 130. In some examples, e.g., some of such examples, at least one of the following may apply: i. the set of resources may be obtained by the wireless device 130 in a configuration, ii. the set of resources may be indicated to the wireless device 130, e.g., with an index, iii. the fifth indication may a buffer status report (BSR), iv. the set of resources may comprise first periodic resources on a physical uplink shared channel (PUSCH), v. the first periodic resources may be to be used with one or more second conditions, vi. the set of resources may comprise second periodic resources on a physical uplink control channel (PUCCH) and vii.the second periodic resources may be to be used with one or more second conditions.

[0353] In some examples, after having received the downlink transmission from the network node 110, the wireless device 130 may:

[0354] - fail to receive a request to release a connection to the network node 110, and

[0355] - initiate a random access procedure with the network node 110 using one of the preamble and the temporary identifier, to receive an uplink grant.

[0356] The request to release the connection may be e.g., an RRC Release request. The request to release may be comprised in the fourth indication. Other units 504 may be comprised in the wireless device 130.

[0357] The wireless device 130 may also be configured to communicate user data with a host application unit in a host computer 1010, e.g., via another link such as 1060.

[0358] In Figure 5, optional units are indicated with dashed boxes.

[0359] The wireless device 130 may comprise an interface unit to facilitate communications between the wireless device 130 and other nodes or devices, e.g., the network node 110, the another network node 120, the host computer 1010, or any of the other nodes. In some particular examples, the interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

[0360] The wireless device 130 may comprise an arrangement as shown in Figure 5 or in Figure 10.

[0361] The network node 110 examples relate to Figure 8, Figure 4, Figure 6 and Figures 9-14.

[0362] A method, performed by a network node, such as the network node 110 is described herein. The method may be understood to be for handling downlink transmission, e.g., to a wireless device, such as the wireless device 130. The network node 110 may be operating in a wireless communications network, such as the wireless communications network 100.

[0363] In some examples, the wireless communications network 100 may support New Radio (NR).

[0364] The first method may comprise one or more of the following actions. In some examples, all the actions may be performed. One or more examples may be combined, where applicable. Components from one example may be tacitly assumed to be present in another example and it will be obvious to a person skilled in the art how those components may be used in the other exemplary examples. All possible combinations are not described to simplify the description. A non-limiting example of the method performed by the network node 110 is depicted in Figure 8. In Figure 8, optional actions in some examples may be represented with dashed lines. In some examples, the actions may be performed in a different order than that depicted Figure 8.

[0365] The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the wireless device 130 and will thus not be repeated here to simplify the description. For example, data may be “Small Data”. o Sending 303 the first indication. The network node 110 may be configured to perform the sending in this Action 303, e.g., by means of a sending unit 601 within the network node 110, configured to perform this action.

[0366] The sending in this Action 303 may be to the wireless device 130 operating in the wireless communications network 100.

[0367] The sending in this Action 303 may be performed, e.g., via the first link 141. The sending in this Action 303 may be, e.g., while the wireless device 130 may be in inactive state.

[0368] The first indication may indicate at least one of:

[0369] - the wireless device 130 may be being paged,

[0370] -a mobile terminated small data transmission procedure, e.g., MT-SDT, may be being used. o Receiving 304 the second indication. The network node 110 may be configured to perform the receiving in this Action 304, e.g., by means of a receiving unit 602 within the network node 110, configured to perform this action.

[0371] The receiving in this Action 304 may be from the wireless device 130.

[0372] The receiving in this Action 304 may be performed, e.g., via the first link 141.

[0373] The receiving in this Action 304 may be, e.g., while the wireless device 130 may be in inactive state; The receiving in this Action 304 may be, e.g., in response to the sent first indication.

[0374] The second indication may comprise the preamble corresponding to the random access procedure. o Sending 306 the downlink transmission. The network node 110 may be configured to perform the sending in this Action 306, e.g., by means of the sending unit 601 within the network node 110, configured to perform this action.

[0375] The sending in this Action 306 may be to the wireless device 130.

[0376] The sending in this Action 306 may be performed, e.g., via the first link 141.

[0377] The sending in this Action 306 may be performed while the wireless device 130 may be in inactive state. The inactive state may be, e.g., RRCJNACTIVE state.

[0378] The sending in this Action 306 may be performed, e.g., after having received the preamble.

[0379] The downlink transmission may comprise the data. The size of the data may be under the threshold. In some examples, the data may be “Small Data”. Particularly, the downlink transmission of the data under the threshold, wherein the downlink data may be mobile terminated, may be e.g., MT-SDT.

[0380] In some examples, at least one of the following may apply:

[0381] - the preamble may be the contention free random access procedure preamble,

[0382] - the preamble may be comprised in the sent first indication,

[0383] - the preamble may be to be used with the one or more first conditions; the one or more first conditions may comprise at least one of: viii. the one or more timers provided to the wireless device 130, ix. the maximum number of times, x. within the determined time resources, e.g., slots, xi. as long as the wireless device 130 may fail to receive a response from the network node 110 to the received second indication, xii. only in response to the first indication, with the proviso the first indication may comprise a further indication for mobile terminated data transmission / a mobile terminated data transmission procedure, xiii. as long as the mobile terminated small data transmission procedure may not have finalized, and xiv. as long as the wireless device 130 may not have received a radio resource control release request from the network node 110. o Receiving 305 the third indication. The network node 110 may be configured to perform the receiving in this Action 305, e.g., by means of the receiving unit 602, configured to perform this action.

[0384] The receiving in this Action 305 may be from the wireless device 130.

[0385] The receiving in this Action 305 may be performed, e.g., via the first link 141.

[0386] The receiving in this Action 305 may be performed, after the receiving 304 of the preamble, and before the sending 306 of the downlink transmission.

[0387] The third indication may indicate the request to resume the radio resource control procedure with the network node 110. The downlink transmission may be sent in the fourth indication. The fourth indication may be sent in response to the received third indication.

[0388] The third indication may be received after having sent a response, e.g., Msg2, to the wireless device (130), to the sent second indication. o Resuming 307, one or more resources. The network node 110 may be configured to perform the resuming in this Action 307, e.g., by means of a resuming unit 603, configured to perform this action.

[0389] The resuming in this Action 307 may comprise an RRC resumption.

[0390] The one or more resources may comprise, e.g., one or more radio bearers, e.g., data radio bearers.

[0391] For example, the one or more resources, e.g., data radio bearers, may be for the mobile terminated small data transmission procedure. The resuming in this Action 307 may be performed one of: i. after receiving the third indication, ii. after sending the fourth indication; the fourth indication may indicate resumption of the radio resource control procedure, and iii. together with the re-establishment of PDCP and RLC entities. o Receiving 308 the fifth indication. The network node 110 may be configured to perform the receiving in this Action 308, e.g., by means of the receiving unit 602, configured to perform this action. The receiving in this Action 308 may be from the wireless device 130.

[0392] The receiving in this Action 308 may be performed, e.g., via the first link 141.

[0393] The fifth indication may be in response to the downlink transmission, e.g., the sent data. The receiving in this Action 308 of the fifth indication may be optionally based on the resumed one or more resources, e.g., one or more radio bearers. The fifth indication may be e.g., HARQ information.

[0394] In some examples, the wireless device 130 may be provided, e.g., by the network node 110, with the temporary identifier for the wireless device 130 in the wireless communications network 100, e.g., RNTI. The temporary identifier may be specific for the mobile terminated data transmission procedure, e.g., MT-RNTI.

[0395] The temporary identifier may be comprised in one of: the sent first indication, and the configuration for the mobile terminated small data transmission procedure, e.g., MT-SDT.

[0396] In some examples, the first indication may further comprise at least one of:

[0397] - the additional indication of the mobile terminated procedure, e.g., MT-indication,

[0398] - the additional indication; the additional indication may be multi-bit,

[0399] - the multi-bit additional indication; the additional indication may further indicate the one or more resources the wireless device 130 may be to resume, e.g., DRB, QoS flow, PDU session, or configuration, e.g., MT-SDT configuration, and

[0400] - the additional indication; the additional indication may further indicate one or more resources the wireless device 130 may be to resume, e.g., DRB, QoS flow, PDU session, or configuration, e.g., MT-SDT configuration.

[0401] In some examples, the receiving 308 of the fifth indication may be performed based on a set of resources provided to the wireless device 130, e.g., by the network node 110. In some examples, e.g., some of such examples, at least one of the following may apply: i. the set of resources may be provided to the wireless device 130 in a configuration, ii. the set of resources may be indicated to the wireless device 130, e.g., with an index, iii. the fifth indication may the buffer status report, iv. the set of resources may comprise the first periodic resources on the physical uplink shared channel, PUSCH, v. the first periodic resources may be to be used with the one or more second conditions, vi. the set of resources may comprise the second periodic resources on the physical uplink control channel, PUCCH, and vii.the second periodic resources may be to be used with the one or more second conditions. In some examples, after having sent the downlink transmission to the wireless device 130 may:

[0402] - the network node 110 may refrain from sending to the wireless device 130 the request to release the connection to the network node 110, and

[0403] - the network node 110 may receive the request from the wireless device 130 to initiate the random access procedure with the network node 110 using the one of the preamble and the temporary identifier, to receive the uplink grant. o Receiving 301 the downlink data. The network node 110 may be configured to perform the receiving in this Action 301, e.g., by means of the receiving unit 602, configured to perform this action.

[0404] The receiving in this Action 301 may be from the another network node 120 operating in the wireless communications network 100.

[0405] The receiving in this Action 301 may be performed, e.g., via the first link 141.

[0406] The receiving in this Action 301 may be, e.g., while the wireless device 130 may be in inactive state. o Determining 302 whether or not to trigger the sending of the received downlink data to the wireless device 130. The network node 110 may be configured to perform the determining in this Action 302, e.g., by means of a determining unit 604, configured to perform this action.

[0407] Determining may comprise, calculating, deriving.

[0408] The determining in this Action 302 may comprise e.g., determining whether or not to use the mobile terminated small data transmission procedure e.g., MT-SDT.

[0409] The determining in this Action 302 may be based on the received downlink data.

[0410] The sending in Action 306 of the downlink transmission may be based on the result of the determination.

[0411] Other units 605 may be comprised in the network node 110.

[0412] The network node 110 may also be configured to communicate user data with a host application unit in a host computer 1010, e.g., via another link such as 1060.

[0413] In Figure 6, optional units are indicated with dashed boxes.

[0414] The network node 110 may comprise an interface unit to facilitate communications between the network node 110 and other nodes or devices, e.g., the wireless device 130, the another node 120, the host computer 1010, or any of the other nodes. In some particular examples, the interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

[0415] The network node 110 may comprise an arrangement as shown in Figure 6 or in Figure

[0416] 10. The following are selected examples related to embodiments herein:

[0417] Example 1. A method performed by a wireless device (130), the method being for handling downlink transmission, the wireless device (130) operating in a wireless communications network (100), and the method comprising:

[0418] - receiving (201), while the wireless device (130) is in inactive state, a first indication from a network node (110) operating in the wireless communications network (100), the first indication indicating at least one of: the wireless device (130) is being paged, and a mobile terminated small data transmission procedure, e.g., MT-SDT, is being used,

[0419] - sending (202), to the network node (110), while the wireless device (130) is in inactive state and in response to the received first indication, a second indication, the second indication comprising a preamble corresponding to a random access procedure, and

[0420] - receiving (204), while the wireless device (130) is in inactive state and after having sent the preamble, a downlink transmission from the network node (110), the downlink transmission comprising data, wherein the size of the data is under a threshold.

[0421] Example 2. The method according to example 1, wherein at least one of:

[0422] - the preamble is a contention free random access procedure preamble,

[0423] - the preamble is comprised in the received first indication,

[0424] - the preamble is to be used with one or more first conditions, the one or more first conditions comprising at least one of: i. one or more timers obtained by the wireless device (130), ii. a maximum number of times, iii. within determined time resources, e.g., slots, iv. as long as the wireless device (130) fails to receive a response from the network node (110) to the sent second indication, v. only in response to the first indication, with the proviso the first indication comprises a further indication indicating mobile terminated data transmission / a mobile terminated data transmission procedure, vi. as long as a mobile terminated small data transmission procedure has not finalized, and vii. as long as the wireless device (130) has not received a radio resource control release request from the network node (110). Example 3. The method according to any of examples 1-2, further comprising, after the sending (202) of the preamble, and before the receiving (204) of the downlink transmission:

[0425] - sending (203) a third indication to the network node (110), the third indication indicating a request to resume a radio resource control procedure with the network node (110), and wherein the downlink transmission is received in a fourth indication received in response to the sent third indication.

[0426] Example 4. The method according to examples 3, wherein the method further comprises at least one of:

[0427] - resuming (205) one or more resources, e.g., one or more radio bearers, e.g., data radio bearers, e.g., the one or more resources, e.g., data radio bearers, being for a mobile terminated small data transmission procedure, wherein the resuming (205) is performed one of: i. after sending the third indication, ii. after receiving the fourth indication, the fourth indication indicating resumption of the radio resource control procedure, and iii. together with a re-establishment of Packet Data Convergence Protocol, PDCP, and Radio Link Control, RLC, entities, and

[0428] - sending (206) a fifth indication to the network node (110), the fifth indication being in response to the downlink transmission, e.g., the received data, wherein the sending (206) of the fifth indication is optionally based on the resumed one or more resources, e.g., one or more radio bearers.

[0429] Example 5. The method according to any of examples 1-4, wherein the wireless device (130) obtains a temporary identifier for the wireless device (130) in the wireless communications network (100), e.g., RNTI, the temporary identifier being specific for a mobile terminated data transmission procedure, e.g., MT-RNTI, the temporary identifier being comprised in one of:

[0430] - the received first indication, and

[0431] - a configuration for a mobile terminated small data transmission procedure.

[0432] Example 6. The method according to any of examples 1-5, wherein the first indication further comprises at least one of:

[0433] - an additional indication of a mobile terminated procedure, e.g., MT-indication,

[0434] - the additional indication, wherein the additional indication is multi-bit,

[0435] - the additional indication, wherein the additional indication further indicates one or more resources the wireless device (130) is to resume, e.g., data radio bearer, DRB, Quality of Service, QoS, flow, Protocol Data Unit, PDU, session, or configuration, e.g., MT-SDT configuration.

[0436] Example 7. The method according to example 4 and any of examples 5-6, wherein the sending (206) of the fifth indication is performed based on a set of resources obtained by the wireless device (130), and wherein at least one of: i. the set of resources are obtained by the wireless device (130) in a configuration, ii. the set of resources are indicated to the wireless device (130), e.g., with an index, iii. the fifth indication comprises a buffer status report, iv. the set of resources comprise first periodic resources on a physical uplink shared channel, PUSCH, v. the first periodic resources are to be used with one or more second conditions, vi. the set of resources comprise second periodic resources on a physical uplink control channel, PUCCH, and vii. the second periodic resources are to be used with one or more second conditions.

[0437] Example 8. The method according to example 5 and any of examples 3-4, after having received the downlink transmission from the network node (110), the wireless device (130):

[0438] - fails to receive a request to release a connection to the network node (110), and

[0439] - initiates a random access procedure with the network node (110) using one of the preamble and the temporary identifier, to receive an uplink grant.

[0440] Example 9. A method performed by a network node (110), the method being for handling downlink transmission, the network node (110) operating in a wireless communications network (100), and the method comprising:

[0441] - sending (303), while the wireless device (130) is in inactive state, a first indication to the wireless device (130) operating in the wireless communications network (100), the first indication indicating at least one of: the wireless device (130) is being paged, and a mobile terminated small data transmission procedure, e.g., MT-SDT, is being used, and

[0442] - receiving (304), from the wireless device (130), while the wireless device (130) is in inactive state and in response to the sent first indication, a second indication, the second indication comprising a preamble corresponding to a random access procedure, and

[0443] - sending (306), while the wireless device (130) is in inactive state and after having received the preamble, a downlink transmission to the wireless device (130), the downlink transmission comprising data, wherein the size of the data is under a threshold.

[0444] Example 10. The method according to example 9, wherein at least one of:

[0445] - the preamble is a contention free random access procedure preamble,

[0446] - the preamble is comprised in the sent first indication,

[0447] - the preamble is to be used with one or more first conditions, the one or more first conditions comprising at least one of: i. one or more timers provided to the wireless device (130), ii. a maximum number of times, iii. within determined time resources, e.g., slots, iv. as long as the wireless device (130) fails to receive a response from the network node (110) to the received second indication, v. only in response to the first indication, with the proviso the first indication comprises a further indication indicating mobile terminated data transmission / a mobile terminated data transmission procedure, vi. as long as a mobile terminated small data transmission procedure has not finalized, and vii. as long as the wireless device (130) has not received a radio resource control release request from the network node (110).

[0448] Example 11. The method according to any of examples 9-10, further comprising, after the receiving (304) of the preamble, and before the sending (306) of the downlink transmission:

[0449] - receiving (305) a third indication from the wireless device (130), the third indication indicating a request to resume a radio resource control procedure with the network node (110), and wherein the downlink transmission is sent in a fourth indication sent in response to the received third indication.

[0450] Example 12. The method according to examples 11, wherein the method further comprises at least one of: resuming (307) one or more resources, e.g., one or more radio bearers, e.g., data radio bearers, e.g., the one or more resources, e.g., data radio bearers, being for a mobile terminated small data transmission procedure, wherein the resuming (307) is performed one of: i. after receiving the third indication, ii. after sending the fourth indication, the fourth indication indicating resumption of the radio resource control procedure, and iii. together with a re-establishment of Packet Data Convergence Protocol, PDCP, and Radio Link Control, RLC, entities, and

[0451] - receiving (308) a fifth indication from the wireless device (130), the fifth indication being in response to the downlink transmission, e.g., the sent data, wherein the receiving (308) of the fifth indication is optionally based on the resumed one or more resources, e.g., one or more radio bearers.

[0452] Example 13. The method according to any of examples 9-12, wherein the wireless device (130) is provided, e.g., by the network node (110), with a temporary identifier for the wireless device (130) in the wireless communications network (100), e.g., RNTI, the temporary identifier being specific for a mobile terminated data transmission procedure, e.g., MT-RNTI, the temporary identifier being comprised in one of:

[0453] - the sent first indication, and

[0454] - a configuration for a mobile terminated small data transmission procedure.

[0455] Example 14. The method according to any of examples 9-13, wherein the first indication further comprises at least one of:

[0456] - an additional indication of a mobile terminated procedure, e.g., MT-indication,

[0457] - the additional indication, wherein the additional indication is multi-bit,

[0458] - the additional indication, wherein the additional indication further indicates one or more resources the wireless device (130) is to resume, e.g., data radio bearer, DRB, Quality of Service, QoS, flow, Protocol Data Unit, PDU, session, or configuration, e.g., MT-SDT configuration.

[0459] Example 15. The method according to example 12 and any of examples 13-14, wherein the receiving (308) of the fifth indication is performed based on a set of resources provided to the wireless device (130), e.g., by the network node (110), and wherein at least one of: i. the set of resources are provided to the wireless device (130) in a configuration, ii. the set of resources are indicated to the wireless device (130), e.g., with an index, iii. the fifth indication comprises a buffer status report, iv. the set of resources comprise first periodic resources on a physical uplink shared channel, PLISCH, v. the first periodic resources are to be used with one or more second conditions, vi. the set of resources comprise second periodic resources on a physical uplink control channel, PLICCH, and vii. the second periodic resources are to be used with one or more second conditions.

[0460] Example 16. The method according to example 13 and any of examples 14-15, wherein after having sent the downlink transmission to the wireless device (130):

[0461] - the network node (110) refrains from sending to the wireless device (130) a request to release a connection to the network node (110), and

[0462] - the network node (110) receives a request from the wireless device (130) to initiate a random access procedure with the network node (110) using one of the preamble and the temporary identifier, to receive an uplink grant.

[0463] Example 17. The method according to any of examples 9-16, wherein the method further comprises:

[0464] - receiving (301) the downlink data from another network node (120) operating in the wireless communications network (100), and

[0465] - determining (302), based on the received downlink data, whether or not to trigger the sending of the received downlink data to the wireless device (130), e.g., determining whether or not to use the mobile terminated small data transmission procedure e.g., MT-SDT, and wherein the sending (306) of the downlink transmission is based on a result of the determination.

[0466] Further Extensions And Variations

[0467] Figure 9: Telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments

[0468] With reference to Figure 9, in accordance with an embodiment, a communication system includes telecommunication network 910 such as the wireless communications network 100, for example, a 3GPP-type cellular network, which comprises access network 911 , such as a radio access network, and core network 914. Access network 911 comprises a plurality of network nodes such as the network node 110. For example, base stations 912a, 912b, 912c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 913a, 913b, 913c. Each base station 912a, 912b, 912c is connectable to core network 914 over a wired or wireless connection 915. A plurality of user equipments, such as the wireless device 130 are comprised in the wireless communications network 100. In Figure 9, a first UE 991 located in coverage area 913c is configured to wirelessly connect to, or be paged by, the corresponding base station 912c. A second UE 992 in coverage area 913a is wirelessly connectable to the corresponding base station 912a. While a plurality of UEs 991 , 992 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 base station 912. Any of the UEs 991 , 992 are examples of the wireless device 130.

[0469] Telecommunication network 910 is itself connected to host computer 930, 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. Host computer 930 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. Connections 921 and 922 between telecommunication network 910 and host computer 930 may extend directly from core network 914 to host computer 930 or may go via an optional intermediate network 920. Intermediate network 920 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 920, if any, may be a backbone network or the Internet; in particular, intermediate network 920 may comprise two or more sub-networks (not shown).

[0470] The communication system of Figure 9 as a whole enables connectivity between the connected UEs 991 , 992 and host computer 930. The connectivity may be described as an over- the-top (OTT) connection 950. Host computer 930 and the connected UEs 991 , 992 are configured to communicate data and / or signaling via OTT connection 950, using access network 911 , core network 914, any intermediate network 920 and possible further infrastructure (not shown) as intermediaries. OTT connection 950 may be transparent in the sense that the participating communication devices through which OTT connection 950 passes are unaware of routing of uplink and downlink communications. For example, base station 912 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 930 to be forwarded (e.g., handed over) to a connected UE 991. Similarly, base station 912 need not be aware of the future routing of an outgoing uplink communication originating from the UE 991 towards the host computer 930.

[0471] In relation to Figures 10, 11 , 12, 13, and 14, which are described next, it may be understood that a UE is an example of the wireless device 130, and that any description provided for the UE equally applies to the wireless device 130. It may be also understood that the base station is an example of the network node 110, and that any description provided for the base station equally applies to the network node 110. Figure 10: Host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments

[0472] Example implementations, in accordance with an embodiment, of the wireless device 130, e.g., a UE, the network node 110, e.g., a base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 10. In communication system 1000, such as the wireless communications network 100, host computer 1010 comprises hardware 1015 including communication interface 1016 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1000. Host computer 1010 further comprises processing circuitry 1018, which may have storage and / or processing capabilities. In particular, processing circuitry 1018 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 1010 further comprises software 1011 , which is stored in or accessible by host computer 1010 and executable by processing circuitry 1018. Software 1011 includes host application 1012. Host application 1012 may be operable to provide a service to a remote user, such as UE 1030 connecting via OTT connection 1050 terminating at UE 1030 and host computer 1010. In providing the service to the remote user, host application 1012 may provide user data which is transmitted using OTT connection 1050.

[0473] Communication system 1000 further includes the network node 110, exemplified in Figure 10 as a base station 1020 provided in a telecommunication system and comprising hardware 1025 enabling it to communicate with host computer 1010 and with UE 1030. Hardware 1025 may include communication interface 1026 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1000, as well as radio interface 1027 for setting up and maintaining at least wireless connection 1070 with the wireless device 130, exemplified in Figure 10 as a UE 1030 located in a coverage area (not shown in Figure 10) served by base station 1020. Communication interface 1026 may be configured to facilitate connection 1060 to host computer 1010. Connection 1060 may be direct or it may pass through a core network (not shown in Figure 10) of the telecommunication system and / or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 1025 of base station 1020 further includes processing circuitry 1028, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 1020 further has software 1021 stored internally or accessible via an external connection.

[0474] Communication system 1000 further includes UE 1030 already referred to. Its hardware 1035 may include radio interface 1037 configured to set up and maintain wireless connection 1070 with a base station serving a coverage area in which UE 1030 is currently located. Hardware 1035 of UE 1030 further includes processing circuitry 1038, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 1030 further comprises software 1031 , which is stored in or accessible by UE 1030 and executable by processing circuitry 1038. Software 1031 includes client application 1032. Client application 1032 may be operable to provide a service to a human or non-human user via UE 1030, with the support of host computer 1010. In host computer 1010, an executing host application 1012 may communicate with the executing client application 1032 via OTT connection 1050 terminating at UE 1030 and host computer 1010. In providing the service to the user, client application 1032 may receive request data from host application 1012 and provide user data in response to the request data. OTT connection 1050 may transfer both the request data and the user data. Client application 1032 may interact with the user to generate the user data that it provides.

[0475] It is noted that host computer 1010, base station 1020 and UE 1030 illustrated in Figure 10 may be similar or identical to host computer 930, one of base stations 912a, 912b, 912c and one of UEs 991 , 992 of Figure 9, respectively. This is to say, the inner workings of these entities may be as shown in Figure 10 and independently, the surrounding network topology may be that of Figure 9.

[0476] In Figure 10, OTT connection 1050 has been drawn abstractly to illustrate the communication between host computer 1010 and UE 1030 via base station 1020, 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 UE 1030 or from the service provider operating host computer 1010, or both. While OTT connection 1050 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).

[0477] Wireless connection 1070 between UE 1030 and base station 1020 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 UE 1030 using OTT connection 1050, in which wireless connection 1070 forms the last segment. More precisely, the teachings of these embodiments may improve the latency, signalling overhead, and service interruption and thereby provide benefits such as reduced user waiting time, better responsiveness and extended battery lifetime.

[0478] 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 OTT connection 1050 between host computer 1010 and UE 1030, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring OTT connection 1050 may be implemented in software 1011 and hardware 1015 of host computer 1010 or in software 1031 and hardware 1035 of UE 1030, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 1050 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 1011 , 1031 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 1050 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 1020, and it may be unknown or imperceptible to base station 1020. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 1010’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 1011 and 1031 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 1050 while it monitors propagation times, errors etc.

[0479] The wireless device 130 embodiments relate to Figure 2, Figure 4, Figure 5 and Figures 9-14.

[0480] The wireless device 130 may also be configured to communicate user data with a host application unit in a host computer 1010, e.g., via another link such as 1060.

[0481] The wireless device 130 may comprise an interface unit to facilitate communications between the wireless device 130 and other nodes or devices, e.g., the network node 110, the another network node 120, the host computer 1010, or any of the other nodes. In some particular examples, the interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

[0482] The wireless device 130 may comprise an arrangement as shown in Figure 5 or in Figure 10.

[0483] The network node 110 embodiments relate to Figure 3, Figure 4, Figure 6 and Figures 9-14.

[0484] The network node 110 may also be configured to communicate user data with a host application unit in a host computer 1010, e.g., via another link such as 1060.

[0485] The network node 110 may comprise an interface unit to facilitate communications between the network node 110 and other nodes or devices, e.g., the wireless device 130, the another node 120, the host computer 1010, or any of the other nodes. In some particular examples, the interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

[0486] The network node 110 may comprise an arrangement as shown in Figure 6 or in Figure

[0487] 10. Figure 11 : Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

[0488] Figure 11 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 9 and 10. For simplicity of the present disclosure, only drawing references to Figure 11 will be included in this section. In step 1110, the host computer provides user data. In substep 1111 (which may be optional) of step 1110, the host computer provides the user data by executing a host application. In step 1120, the host computer initiates a transmission carrying the user data to the UE. In step 1130 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1140 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0489] Figure 12: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

[0490] Figure 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 9 and 10. For simplicity of the present disclosure, only drawing references to Figure 12 will be included in this section. In step 1210 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 1220, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1230 (which may be optional), the UE receives the user data carried in the transmission.

[0491] Figure 13: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

[0492] Figure 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 9 and 10. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section. In step 1310 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1320, the UE provides user data. In substep 1321 (which may be optional) of step 1320, the UE provides the user data by executing a client application. In substep 1311 (which may be optional) of step 1310, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 1330 (which may be optional), transmission of the user data to the host computer. In step 1340 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0493] Figure 14: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

[0494] Figure 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 9 and 10. For simplicity of the present disclosure, only drawing references to Figure 14 will be included in this section. In step 1410 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 1420 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1430 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0495] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0496] The term unit may have conventional meaning in the field of electronics, electrical devices and / or electronic devices and may include, for example, electrical and / or electronic circuitry, devices, modules, processors, memories, logic solid state and / or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and / or displaying functions, and so on, as such as those that are described herein.

[0497] Further numbered embodiments

[0498] I . A base station configured to communicate with a user equipment (UE), the base station comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the network node 110.

[0499] 5. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform one or more of the actions described herein as performed by the network node 110.

[0500] 6. The communication system of embodiment 5, further including the base station.

[0501] 7. The communication system of embodiment 6, further including the UE, wherein the UE is configured to communicate with the base station.

[0502] 8. The communication system of embodiment 7, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.

[0503] I I. A method implemented in a base station, comprising one or more of the actions described herein as performed by the network node 110.

[0504] 15. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs one or more of the actions described herein as performed by the network node 110. 16. The method of embodiment 15, further comprising: at the base station, transmitting the user data.

[0505] 17. The method of embodiment 16, wherein the user data is provided at the host computer by executing a host application, the method further comprising: at the UE, executing a client application associated with the host application.

[0506] 21. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the wireless device 130.

[0507] 25. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform one or more of the actions described herein as performed by the wireless device 130.

[0508] 26. The communication system of embodiment 25, further including the UE.

[0509] 27. The communication system of embodiment 26, wherein the cellular network further includes a base station configured to communicate with the UE.

[0510] 28. The communication system of embodiment 26 or 27, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.

[0511] 31. A method implemented in a user equipment (UE), comprising one or more of the actions described herein as performed by the wireless device 130.

[0512] 35. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs one or more of the actions described herein as performed by the wireless device 130.

[0513] 36. The method of embodiment 35, further comprising: at the UE, receiving the user data from the base station.

[0514] 41. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the wireless device 130.

[0515] 45. A communication system including a host computer comprising: a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to: perform one or more of the actions described herein as performed by the wireless device 130.

[0516] 46. The communication system of embodiment 45, further including the UE.

[0517] 47. The communication system of embodiment 46, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

[0518] 48. The communication system of embodiment 46 or 47, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

[0519] 49. The communication system of embodiment 46 or 47, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data. 51. A method implemented in a user equipment (UE), comprising one or more of the actions described herein as performed by the wireless device 130.

[0520] 52. The method of embodiment 51 , further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the base station.

[0521] 55. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs one or more of the actions described herein as performed by the wireless device 130.

[0522] 56. The method of embodiment 55, further comprising: at the UE, providing the user data to the base station.

[0523] 57. The method of embodiment 56, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.

[0524] 58. The method of embodiment 56, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.

[0525] 61. A base station configured to communicate with a user equipment (UE), the base station comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the network node 110.

[0526] 65. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform one or more of the actions described herein as performed by the network node 110. 66. The communication system of embodiment 65, further including the base station.

[0527] 67. The communication system of embodiment 66, further including the UE, wherein the UE is configured to communicate with the base station.

[0528] 68. The communication system of embodiment 67, wherein: the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

[0529] 71. A method implemented in a base station, comprising one or more of the actions described herein as performed by the network node 110.

[0530] 75. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs one or more of the actions described herein as performed by the wireless device 130.

[0531] 76. The method of embodiment 75, further comprising: at the base station, receiving the user data from the UE.

[0532] 77. The method of embodiment 76, further comprising: at the base station, initiating a transmission of the received user data to the host computer.

Claims

CLAIMS:1 . A method performed by a wireless device (130), the method being for handling downlink transmission, the wireless device (130) operating in a wireless communications network (100), and the method comprising:- receiving (201), while the wireless device (130) is in inactive state, a first indication from a network node (110) operating in the wireless communications network (100), the first indication indicating the wireless device (130) is being paged, and a mobile terminated small data transmission, MT-SDT, procedure is being used, wherein the first indication further comprises an additional indication of a mobile terminated procedure, wherein the additional indication further indicates one or more resources for the MT-SDT procedure the wireless device (130) is to resume, wherein the one or more resources comprise one or more radio bearers,- sending (202), to the network node (110), while the wireless device (130) is in inactive state and in response to the received first indication, a second indication, the second indication comprising a preamble corresponding to a random access procedure, and- receiving (204), while the wireless device (130) is in inactive state and after having sent the preamble, a downlink transmission from the network node (110), the downlink transmission comprising data, wherein a size of the data is under a threshold.

2. The method according to claim 1 , wherein at least one of:- the preamble is a contention free random access procedure preamble,- the preamble is comprised in the received first indication,- the preamble is to be used with one or more first conditions, the one or more first conditions comprising at least one of: i. one or more timers obtained by the wireless device (130), ii. a maximum number of times, iii. within determined time resources, iv. as long as the wireless device (130) fails to receive a response from the network node (110) to the sent second indication, v. only in response to the first indication, with the proviso the first indication comprises a further indication indicating mobile terminated data transmission / a mobile terminated data transmission procedure,vi. as long as a mobile terminated small data transmission procedure has not finalized, and vii. as long as the wireless device (130) has not received a radio resource control release request from the network node (110).

3. The method according to any of claims 1-2, further comprising, after the sending (202) of the preamble, and before the receiving (204) of the downlink transmission:- sending (203) a third indication to the network node (110), the third indication indicating a request to resume a radio resource control procedure with the network node (110), and wherein the downlink transmission is received in a fourth indication received in response to the sent third indication.

4. The method according to claims 3, wherein the method further comprises at least one of:- resuming (205) the one or more resources, wherein the resuming (205) is performed one of: i. after sending the third indication, ii. after receiving the fourth indication, the fourth indication indicating resumption of the radio resource control procedure, and iii. together with a re-establishment of Packet Data Convergence Protocol, PDCP, and Radio Link Control, RLC, entities, and- sending (206) a fifth indication to the network node (110), the fifth indication being in response to the downlink transmission, wherein the sending (206) of the fifth indication is optionally based on the resumed one or more resources.

5. The method according to any of claims 1-4, wherein the wireless device (130) obtains a temporary identifier for the wireless device (130) in the wireless communications network (100), the temporary identifier being specific for a mobile terminated data transmission procedure, the temporary identifier being comprised in one of:- the received first indication, and- a configuration for a mobile terminated small data transmission procedure.

6. The method according to any of claims 1-5, wherein at least one of:- the additional indication is multi-bit,- the one or more resources the wireless device (130) is to resume comprise at least one of: data radio bearer, DRB, Quality of Service, QoS, flow, Protocol Data Unit, PDU, session, or configuration, and- the wireless communications network (100) operates on New Radio, NR.The method according to claim 4 and any of claims 5-6, wherein the sending (206) of the fifth indication is performed based on a set of resources obtained by the wireless device (130), and wherein at least one of: i. the set of resources are obtained by the wireless device (130) in a configuration, ii. the set of resources are indicated to the wireless device (130), iii. the fifth indication comprises a buffer status report, iv. the set of resources comprise first periodic resources on a physical uplink shared channel, PLISCH, v. the first periodic resources are to be used with one or more second conditions, vi. the set of resources comprise second periodic resources on a physical uplink control channel, PLICCH, and vii. the second periodic resources are to be used with one or more third conditions. The method according to claim 5 and any of claims 3-4, after having received the downlink transmission from the network node (110), the wireless device (130):- fails to receive a request to release a connection to the network node (110), and- initiates a random access procedure with the network node (110) using one of the preamble and the temporary identifier, to receive an uplink grant. The method according to any of claims 1-8, wherein the wireless communications network (100) operates on New Radio, NR. A method performed by a network node (110), the method being for handling downlink transmission, the network node (110) operating in a wireless communications network (100), and the method comprising:- sending (303), while the wireless device (130) is in inactive state, a first indication to the wireless device (130) operating in the wireless communications network (100), the first indication indicating the wireless device (130) is being paged, and a mobile terminated small data transmission, MT-SDT, procedure is being used, wherein the first indication further comprises an additional indication of a mobile terminated procedure,wherein the additional indication further indicates one or more resources for the MT-SDT procedure the wireless device (130) is to resume, wherein the one or more resources comprise one or more radio bearers,- receiving (304), from the wireless device (130), while the wireless device (130) is in inactive state and in response to the sent first indication, a second indication, the second indication comprising a preamble corresponding to a random access procedure, and- sending (306), while the wireless device (130) is in inactive state and after having received the preamble, a downlink transmission to the wireless device (130), the downlink transmission comprising data, wherein a size of the data is under a threshold. The method according to claim 10, wherein at least one of:- the preamble is a contention free random access procedure preamble,- the preamble is comprised in the sent first indication,- the preamble is to be used with one or more first conditions, the one or more first conditions comprising at least one of: i. one or more timers provided to the wireless device (130), ii. a maximum number of times, iii. within determined time resources, iv. as long as the wireless device (130) fails to receive a response from the network node (110) to the received second indication, v. only in response to the first indication, with the proviso the first indication comprises a further indication indicating mobile terminated data transmission / a mobile terminated data transmission procedure, vi. as long as a mobile terminated small data transmission procedure has not finalized, and vii. as long as the wireless device (130) has not received a radio resource control release request from the network node (110). The method according to any of claims 10-11, further comprising, after the receiving (304) of the preamble, and before the sending (306) of the downlink transmission:- receiving (305) a third indication from the wireless device (130), the third indication indicating a request to resume a radio resource control procedure with the network node (110), and wherein the downlink transmission is sent in a fourth indication sent in response to the received third indication.The method according to claims 12, wherein the method further comprises at least one of:- resuming (307) the one or more resources, wherein the resuming (307) is performed one of: i. after receiving the third indication, ii. after sending the fourth indication, the fourth indication indicating resumption of the radio resource control procedure, and iii. together with a re-establishment of Packet Data Convergence Protocol, PDCP, and Radio Link Control, RLC, entities, and- receiving (308) a fifth indication from the wireless device (130), the fifth indication being in response to the downlink transmission, wherein the receiving (308) of the fifth indication is optionally based on the resumed one or more resources. The method according to any of claims 10-13, wherein the wireless device (130) is provided, by the network node (110), with a temporary identifier for the wireless device (130) in the wireless communications network (100), the temporary identifier being specific for a mobile terminated data transmission procedure the temporary identifier being comprised in one of:- the sent first indication, and- a configuration for a mobile terminated small data transmission procedure. The method according to any of claims 10-14, wherein at least one of:- the additional indication is multi-bit, and- the one or more resources the wireless device (130) is to resume comprise at least one of: data radio bearer, DRB, Quality of Service, QoS, flow, Protocol Data Unit, PDU, session, or configuration. The method according to claim 13 and any of claims 14-15, wherein the receiving (308) of the fifth indication is performed based on a set of resources provided to the wireless device (130), and wherein at least one of: i. the set of resources are provided to the wireless device (130) in a configuration, ii. the set of resources are indicated to the wireless device (130), iii. the fifth indication comprises a buffer status report, iv. the set of resources comprise first periodic resources on a physical uplink shared channel, PUSCH,v. the first periodic resources are to be used with one or more second conditions, vi. the set of resources comprise second periodic resources on a physical uplink control channel, PLICCH, and vii. the second periodic resources are to be used with one or more third conditions. The method according to claim 14 and any of claims 15-16, wherein after having sent the downlink transmission to the wireless device (130):- the network node (110) refrains from sending to the wireless device (130) a request to release a connection to the network node (110), and- the network node (110) receives a request from the wireless device (130) to initiate a random access procedure with the network node (110) using one of the preamble and the temporary identifier, to receive an uplink grant. The method according to any of claims 10-17, wherein the method further comprises:- receiving (301) the downlink data from another network node (120) operating in the wireless communications network (100), and- determining (302), based on the received downlink data, whether or not to trigger the sending of the received downlink data to the wireless device (130), and wherein the sending (306) of the downlink transmission is based on a result of the determination. The method according to any of claims 10-18, wherein the wireless communications network (100) operates on New Radio, NR. A wireless device (130), for handling downlink transmission, the wireless device (130) being configured to operate in a wireless communications network (100), and the wireless device (130) being further configured to:- receive, while the wireless device (130) is in inactive state, a first indication from a network node (110) configured to operate in the wireless communications network (100), the first indication being configured to indicate the wireless device (130) is being paged, and a mobile terminated small data transmission, MT-SDT, procedure is being used, wherein the first indication is further configured to comprise an additional indication of a mobile terminated procedure, wherein the additional indication is further configured to indicate one or more resources for the MT-SDT procedure the wireless device (130) is to resume,wherein the one or more resources are configured to comprise one or more radio bearers,- send, to the network node (110), while the wireless device (130) is in inactive state and in response to the received first indication, a second indication, the second indication being configured to comprise a preamble corresponding to a random access procedure, and- receive, while the wireless device (130) is in inactive state and after having sent the preamble, a downlink transmission from the network node (110), the downlink transmission being configured to comprise data, wherein a size of the data is configured to be under a threshold. The wireless device (130) according to claim 20, wherein at least one of:- the preamble is configured to be a contention free random access procedure preamble,- the preamble is configured to be comprised in the first indication configured to be received,- the preamble is configured to be to be used with one or more first conditions, the one or more first conditions being configured to comprise at least one of: i. one or more timers configured to be obtained by the wireless device (130), ii. a maximum number of times, iii. within determined time resources, iv. as long as the wireless device (130) fails to receive a response from the network node (110) to the second indication configured to be sent, v. only in response to the first indication, with the proviso the first indication is configured to comprise a further indication indicating mobile terminated data transmission / a mobile terminated data transmission procedure, vi. as long as a mobile terminated small data transmission procedure has not finalized, and vii. as long as the wireless device (130) has not received a radio resource control release request from the network node (110). The wireless device (130) according to any of claims 20-21, being further configured to, after the sending of the preamble, and before the receiving of the downlink transmission:- send a third indication to the network node (110), the third indication being configured to indicate a request to resume a radio resource control procedure with the network node (110), and wherein the downlink transmission is configuredto be received in a fourth indication configured to be received in response to the third indication configured to be sent. The wireless device (130) according to claims 22, wherein the wireless device (130) is further configured to at least one of:- resume the one or more resources, wherein the resuming is configured to be performed one of: i. after sending the third indication, ii. after receiving the fourth indication, the fourth indication being configured to indicate resumption of the radio resource control procedure, and iii. together with a re-establishment of Packet Data Convergence Protocol, PDCP, and Radio Link Control, RLC, entities, and- send a fifth indication to the network node (110), the fifth indication being configured to be in response to the downlink transmission, wherein the sending of the fifth indication is optionally configured to be based on the one or more resources configured to be resumed. The wireless device (130) according to any of claims 20-23, wherein the wireless device (130) is configured to obtain a temporary identifier for the wireless device (130) in the wireless communications network (100), the temporary identifier being configured to be specific for a mobile terminated data transmission procedure, the temporary identifier being configured to be comprised in one of:- the first indication configured to be received, and- a configuration for a mobile terminated small data transmission procedure. The wireless device (130) according to any of claims 20-24, wherein at least one of:- the additional indication is configured to be multi-bit, and- the one or more resources the wireless device (130) is configured to resume are configured to comprise at least one of: data radio bearer, DRB, Quality of Service, QoS, flow, Protocol Data Unit, PDU, session, or configuration. The wireless device (130) according to claim 23 and any of claims 24-25, wherein the sending of the fifth indication is configured to be performed based on a set of resources configured to be obtained by the wireless device (130), and wherein at least one of: i. the set of resources are configured to be obtained by the wireless device (130) in a configuration,ii. the set of resources are configured to be indicated to the wireless device (130), iii. the fifth indication is configured to comprise a buffer status report, iv. the set of resources are configured to comprise first periodic resources on a physical uplink shared channel, PLISCH, v. the first periodic resources are configured to be used with one or more second conditions, vi. the set of resources are configured to comprise second periodic resources on a physical uplink control channel, PLICCH, and vii. the second periodic resources are configured to be used with one or more third conditions. The wireless device (130) according to claim 24 and any of claims 22-23, the wireless device (130) is further configured to, with the proviso that, after having received the downlink transmission from the network node (110):- the wireless device (130) fails to receive a request to release a connection to the network node (110),- initiate a random access procedure with the network node (110) using one of the preamble and the temporary identifier, to receive an uplink grant. The wireless device (130) according to any of claims 20-27, wherein the wireless communications network (100) is configured to operate on New Radio, NR. A network node (110), for handling downlink transmission, the network node (110) being configured to operate in a wireless communications network (100), and the network node (110) being further configured to:- send, while the wireless device (130) is in inactive state, a first indication to the wireless device (130) configured to operate in the wireless communications network (100), the first indication being configured to indicate the wireless device (130) is being paged, and a mobile terminated small data transmission, MT-SDT, procedure is being used, wherein the first indication is further configured to comprise an additional indication of a mobile terminated procedure, wherein the additional indication is further configured to indicate one or more resources for the MT-SDT procedure the wireless device (130) is to resume, wherein the one or more resources are configured to comprise one or more radio bearers,- receive, from the wireless device (130), while the wireless device (130) is in inactive state and in response to the sent first indication, a second indication, the second indication being configured to comprise a preamble corresponding to a random access procedure, and- send, while the wireless device (130) is in inactive state and after having received the preamble, a downlink transmission to the wireless device (130), the downlink transmission being configured to comprise data, wherein a size of the data is configured to be under a threshold. The network node (110) according to claim 29, wherein at least one of:- the preamble is configured to be a contention free random access procedure preamble,- the preamble is configured to be comprised in the first indication configured to be sent,- the preamble is configured to be to be used with one or more first conditions, the one or more first conditions being configured to comprise at least one of: i. one or more timers configured to be provided to the wireless device (130), ii. a maximum number of times, iii. within determined time resources, iv. as long as the wireless device (130) fails to receive a response from the network node (110) to the second indication configured to be received, v. only in response to the first indication, with the proviso the first indication comprises a further indication indicating mobile terminated data transmission / a mobile terminated data transmission procedure, vi. as long as a mobile terminated small data transmission procedure has not finalized, and vii. as long as the wireless device (130) has not received a radio resource control release request from the network node (110). The network node (110) according to any of claims 29-30, being further configured to, after the receiving of the preamble, and before the sending of the downlink transmission:- receive a third indication from the wireless device (130), the third indication being configured to indicate a request to resume a radio resource control procedure with the network node (110), and wherein the downlink transmission is configured to be sent in a fourth indication configured to be sent in response to the third indication configured to be received.

32. The network node (110) according to claims 31 , wherein the network node (110) is further configured to at least one of:- resume the one or more resources, wherein the resuming is configured to be performed one of: i. after receiving the third indication, ii. after sending the fourth indication, the fourth indication being configured to indicate resumption of the radio resource control procedure, and iii. together with a re-establishment of Packet Data Convergence Protocol, PDCP, and Radio Link Control, RLC, entities, and- receive a fifth indication from the wireless device (130), the fifth indication being configured to be in response to the downlink transmission, wherein the receiving of the fifth indication is configured to be optionally based on the one or more resources configured to be resumed.

33. The network node (110) according to any of claims 29-32, wherein the wireless device (130) is being configured to be provided, by the network node (110), with a temporary identifier for the wireless device (130) in the wireless communications network (100), the temporary identifier being configured to be specific for a mobile terminated data transmission procedure, the temporary identifier being configured to be comprised in one of:- the first indication configured to be sent, and- a configuration for a mobile terminated small data transmission procedure.

34. The network node (110) according to any of claims 29-33, wherein at least one of:- the additional indication is configured to be multi-bit, and- the one or more resources the wireless device (130) is configured to resume are configured to comprise at least one of: data radio bearer, DRB, Quality of Service, QoS, flow, Protocol Data Unit, PDU, session, or configuration.

35. The network node (110) according to claim 32 and any of claims 33-34, wherein the receiving of the fifth indication is configured to be performed based on a set of resources configured to be provided to the wireless device (130), and wherein at least one of: i. the set of resources are configured to be provided to the wireless device (130) in a configuration, ii. the set of resources are configured to be indicated to the wireless device (130), iii. the fifth indication is configured to comprise a buffer status report,iv. the set of resources are configured to comprise first periodic resources on a physical uplink shared channel, PLISCH, v. the first periodic resources are configured to be used with one or more second conditions, vi. the set of resources are configured to comprise second periodic resources on a physical uplink control channel, PLICCH, and vii. the second periodic resources are configured to be used with one or more third conditions. The network node (110) according to claim 33 and any of claims 34-35, wherein after having sent the downlink transmission to the wireless device (130):- the network node (110) is configured to refrain from sending to the wireless device (130) a request to release a connection to the network node (110), and- the network node (110) is configured to receive a request from the wireless device (130) to initiate a random access procedure with the network node (110) using one of the preamble and the temporary identifier, to receive an uplink grant. The network node (110) according to any of claims 29-36, wherein the network node (110) is further configured to:- receive the downlink data from another network node (120) configured to operate in the wireless communications network (100), and- determine, based on the received downlink data, whether or not to trigger the sending of the received downlink data to the wireless device (130), and wherein the sending of the downlink transmission is configured to be based on a result of the determination. The network node (110) according to any of claims 29-37, wherein the wireless communications network (100) is configured to operate on New Radio, NR.

Images