[go: up one dir, main page]

EP4523488A1 - Dispositif sans fil, noeud de réseau et procédés exécutés par ces derniers, destinés à traiter une transmission de liaison montante - Google Patents

Dispositif sans fil, noeud de réseau et procédés exécutés par ces derniers, destinés à traiter une transmission de liaison montante

Info

Publication number
EP4523488A1
EP4523488A1 EP23724060.1A EP23724060A EP4523488A1 EP 4523488 A1 EP4523488 A1 EP 4523488A1 EP 23724060 A EP23724060 A EP 23724060A EP 4523488 A1 EP4523488 A1 EP 4523488A1
Authority
EP
European Patent Office
Prior art keywords
indication
wireless device
network node
resources
procedure
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP23724060.1A
Other languages
German (de)
English (en)
Inventor
Andreas HÖGLUND
Luca FELTRIN
Dung PHAM VAN
Jan Christoffersson
Henrik Enbuske
Revathy Narayanan
Emre YAVUZ
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP4523488A1 publication Critical patent/EP4523488A1/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • H04W72/512—Allocation or scheduling criteria for wireless resources based on terminal or device properties for low-latency requirements, e.g. URLLC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H04W74/0838—Random access procedures, e.g. with 4-step access using contention-free random access [CFRA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • 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.
  • 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.
  • RAN Radio Access 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.
  • 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...
  • 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.
  • 3GPP 3rd Generation Partnership Project
  • LTE Long Term Evolution
  • base stations which may be referred to as eNodeBs or even eNBs, may be directly connected to one or more core networks.
  • 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.
  • NR New Radio Interface
  • 5G-UTRA Fifth Generation
  • CN Fifth Generation
  • NG Next Generation
  • NGC Next Generation
  • 5G Core 5G Core
  • NG Next Generation
  • NG Next Generation
  • RAN Radio Access Network
  • 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.
  • 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.
  • devices may collect data with the help of various existing technologies and then autonomously flow the data between other devices.
  • MTC Machine Type Communication
  • LoT Internet of Things
  • 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.
  • RA-SDT random access based SDT
  • CG-SDT configured grant 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.
  • RRC Radio Resource Control
  • 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.
  • TA Timing Advance
  • NR Small Data Transmission SDT
  • MBB Mobile BroadBand
  • loT 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).
  • EDT Early Data Transmission
  • PUR Preconfigured Uplink Resources
  • 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.
  • MBB Mobile BroadBand
  • loT control-plane optimization ‘Data over Non-Access Stratum (NAS)’, or Data over Non-Access Stratum (DoNAS)
  • 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.
  • MT-SDT Mobile Terminated Small Data Transmission
  • RAN#94e Dec 2021
  • 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.
  • MT-SDT paging-triggered SDT
  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • the wireless device 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.
  • Embodiments herein may be understood to enable the ‘Data in Msg4’ approach for NR, and also to further reduce the signaling overhead.
  • Figure 1 is a schematic diagram depicting an example of a wireless communications network, according to embodiments herein.
  • Figure 2 is a flowchart depicting a method in a wireless device, according to embodiments herein.
  • Figure 3 is a flowchart depicting a method in a network node, according to embodiments herein.
  • Figure 4 is a schematic diagram illustrating a non-limiting example of methods disclosed herein, according to some examples.
  • Figure 5 is a schematic block diagram illustrating two embodiments, in panel a) and panel b), of a wireless device, according to embodiments herein.
  • Figure 6 is a schematic block diagram illustrating two embodiments, in panel a) and panel b), of a network node, according to embodiments herein.
  • Figure 7 is a flowchart depicting a method in a wireless device, according to examples related to embodiments herein.
  • Figure 8 is a flowchart depicting a method in a network node, according to examples related to embodiments herein.
  • Figure 9 is a schematic block diagram illustrating a telecommunication network connected via an intermediate network to a host computer, according to embodiments herein.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • CFRA contention-free random access
  • RNTI MT-Radio Network Temporary Identifier
  • UL Uplink
  • 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.
  • 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.
  • LTE Long-Term Evolution
  • LTE-M LTE Frequency Division Duplex
  • TDD Time Division Duplex
  • HD-FDD LTE Half-Duplex Frequency Division Duplex
  • LAA LTE License-Assisted Access
  • eLAA enhanced LAA
  • feLAA further enhanced
  • MulteFire MulteFire.
  • 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.
  • RATs Radio Access Technologies
  • MSR Multi-Standard Radio
  • 3GPP 3rd Generation Partnership Project
  • WiFi networks Worldwide Interoperability for Microwave Access (WiMax)
  • WiMax Worldwide Interoperability for Microwave Access
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • UE 5G User Equipment
  • 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.
  • 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.
  • 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.
  • a wireless device such as the wireless device 130, e.g., a 5G UE, nllE or a UE
  • a network node such as the network node 110, e.g., a gNB.
  • 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.
  • 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.
  • the wireless communications network 100 may support New Radio (NR). In some embodiments, the wireless communications network 100 operates on NR.
  • NR New Radio
  • 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.
  • the wireless device 130 receives a first indication.
  • 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’,
  • 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.
  • the first indication indicates the wireless device 130 is being paged, and a mobile terminated small data transmission (MT-SDT) procedure is being used.
  • MT-SDT mobile terminated small data transmission
  • the first indication may be, e.g., a paging message.
  • 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.
  • the additional indication may be multi-bit.
  • 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.
  • DRB data radio bearer
  • QoS Quality of Service
  • PDU Protocol Data Unit
  • 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.
  • 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.
  • a new RNTI e.g., MT-RNTI
  • 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.
  • 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 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.
  • RAR Random Access Response
  • 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.
  • C-RNTI UE-specific Cell RNTI
  • 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.
  • 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.
  • 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.
  • 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.
  • the wireless device 130 sends a second indication.
  • the sending in this Action 202 is to the network node 110.
  • 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 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.
  • the preamble may be a contention free random access (CFRA) procedure preamble.
  • the preamble may be comprised in the received first indication.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the one or more first conditions may comprise that the preamble may be to be used iii) within determined time resources, e.g., slots.
  • 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.
  • 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.
  • the wireless device 130 may continue to use Contention-Based Random Access (CBRA) preambles in case it may not receive a RAR.
  • the preamble transmission counter may be reset to zero when the wireless device 130 may start to use CBRA preambles after using CFRA.
  • the preamble transmission counter may not be reset after using CFRA.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the wireless device 130 may trigger the RA procedure using contention free resources which may ensure that no collision may occur with other UEs.
  • the wireless device 130 may send a third indication.
  • the sending in this Action 203 may be to the network node 110.
  • the sending in this Action 203 may be, e.g., transmitting, and may be performed, e.g., via the first link 141.
  • 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.
  • the third indication may be, e.g., a Msg 3 in the RA procedure.
  • the legacy Random Access 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.
  • RA Random Access
  • the request to resume the RRC procedure may be, e.g., an RRCResumeRequest.
  • RRC resumption of the wireless device 130 e.g., UE RRC resumption
  • the receiving in this Action 204 is while the wireless device 130 is in inactive state and after having sent the preamble.
  • 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.
  • the downlink transmission comprises data.
  • a size of the data is under a threshold.
  • the data may be “Small Data”.
  • the data may be configured for SDT.
  • the downlink transmission of the data under the threshold, wherein the downlink data may be mobile terminated may be e.g., MT-SDT.
  • the downlink transmission may be received in a fourth indication.
  • the fourth indication may be received in response to the sent third indication.
  • the fourth indication may be, e.g., a Msg 4 in the RA procedure.
  • 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.
  • the wireless device 130 may resume one or more resources.
  • the one or more resources may comprise, e.g., one or more radio bearers, e.g., data radio bearers.
  • 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; 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.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • the resuming in this Action 205 may comprise an RRC resumption.
  • the wireless device 130 may resume the RRC connection.
  • 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.
  • DRB SDT Data Radio Bearer
  • 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.
  • 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
  • lower layers indicate that conditions for initiating SDT as specified in TS 38.321 [3] are fulfilled.
  • a UE in RRC INACTIVE initiates the resume procedure for MT-SDT when all of the following conditions are fulfilled:
  • SIB1 includes mtSdt-ConfigCommon', and
  • 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..
  • 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.
  • the UE Upon initiation of the procedure, the UE shall:
  • NG-RAN Next Generation Radio Access Network
  • the UE shall set the contents of RRCResumeRequest or RRCResumeRequestl message as follows:
  • 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.
  • 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.
  • SDU Service Data Unit
  • 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.
  • 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.
  • the additional indication may be multi-bit.
  • 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.
  • DRB data radio bearer
  • QoS Quality of Service
  • PDU Protocol Data Unit
  • 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.
  • MAC Medium Access Control
  • CE Medium Access Control Element
  • 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.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • DRBs data radio bearers
  • RRCResumeRequest/RRCResumeRequestl 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 .
  • DRBs may be resumed and their respective PDCP and RLC entities may be re-established at the transmission of RRCResumeRequest/RRCResumeRequestl .
  • RRCResumeRequest/RRCResumeRequestl 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.
  • the wireless device 130 may send a fifth indication.
  • the sending in this Action 206 may be to the network node 110.
  • the sending in this Action 206 may be, e.g., transmitting, and may be performed, e.g., via the first link 141.
  • 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.
  • 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.
  • 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.
  • TA timing advance
  • Arrival of new UL data at the wireless device 130 may generate a buffer status report (BSR).
  • 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.
  • the set of resources may be obtained by the wireless device 130 in a configuration
  • the set of resources may be indicated to the wireless device 130, e.g., with an index
  • 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
  • the set of resources may comprise second periodic resources on a physical uplink control channel (PUCCH)
  • the second periodic resources may be to be used with one or more third conditions.
  • 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.
  • 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.
  • 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.
  • RRC message e.g., RRCRelease
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the wireless device 130 may finally send the UL data multiplexed with RLC status report, or a new PDCP control PDU.
  • 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.
  • 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.
  • 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.
  • both the UE-specific RNTI and potentially also the CFRA preamble may be 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.
  • the wireless device 130 may transmit the CFRA preamble and the network node 110 may respond with an UL grant.
  • 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.
  • the wireless communications network 100 may support New Radio (NR). In some embodiments, the wireless communications network 100 operates on NR.
  • NR New Radio
  • 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.
  • 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.
  • the receiving in this Action 301 may be performed, e.g., via the first link 141.
  • the receiving in this Action 301 may be, e.g., while the wireless device 130 may be in inactive state.
  • 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.
  • a connected state e.g., CM_CONNECTED
  • the CN e.g., the another network node 120, for example, a User Plane Function (UPF) node
  • UPF User Plane Function
  • 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.
  • the network node 110 e.g., last serving gNB
  • 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.
  • 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.
  • 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).
  • MT-SDT mobile terminated small data transmission procedure
  • the network node 110 may determine whether or not to trigger the sending of the received downlink data to the wireless device 130.
  • Determining may comprise, calculating, deriving.
  • 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.
  • NW Network
  • the determining in this Action 302 may be based on the received downlink data.
  • the network node 110 sends the first indication.
  • the sending in this Action 303 is to the wireless device 130 operating in the wireless communications network 100.
  • the sending in this Action 303 may be performed, e.g., via the first link 141.
  • the sending in this Action 303 is while the wireless device 130 is in inactive state.
  • the first indication indicates the wireless device 130 is being paged, and the MT-SDT procedure is being used.
  • the first indication further comprises the additional indication of the mobile terminated procedure, e.g., MT-indication.
  • 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.
  • the additional indication may be multi-bit
  • 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.
  • the network node 110 receives the second indication.
  • the receiving in this Action 304 is from the wireless device 130.
  • the receiving in this Action 304 may be performed, e.g., via the first link 141.
  • the receiving in this Action 304 is while the wireless device 130 is in inactive state and in response to the sent first indication.
  • the second indication comprises the preamble corresponding to the random access procedure.
  • the preamble may be the contention free random access procedure preamble
  • the preamble may be comprised in the sent first indication
  • 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.
  • the network node 110 may receive the third indication.
  • the receiving in this Action 305 may be performed, e.g., via the first link 141.
  • 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.
  • the third indication may indicate the request to resume the radio resource control procedure with the network node 110.
  • the legacy Random Access 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.
  • the network node 110 sends the downlink transmission.
  • the sending in this Action 306 is to the wireless device 130.
  • the sending in this Action 306 may be performed, e.g., via the first link 141.
  • 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.
  • the sending in this Action 306 is performed, e.g., after having received the preamble.
  • the downlink transmission comprises the data.
  • the size of the data is under the threshold.
  • the data may be “Small Data”.
  • the downlink transmission of the data under the threshold, wherein the downlink data may be mobile terminated may be e.g., MT-SDT.
  • the downlink transmission may be sent in the fourth indication.
  • the fourth indication may be sent in response to the received third indication.
  • the sending in Action 306 of the downlink transmission may be based on the result of the determination of Action 302.
  • the network node 110 may resume the one or more resources.
  • 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.
  • the one or more resources 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.
  • the network node 110 may receive the fifth indication.
  • the receiving in this Action 308 may be from the wireless device 130.
  • the receiving in this Action 308 may be performed, e.g., via the first link 141.
  • 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.
  • 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.
  • 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.
  • PKISCH physical uplink shared channel
  • PLICCH physical uplink control channel
  • 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.
  • the signaling procedure for the MT-SDT approach ‘Data in Msg4’ for NR, according to embodiments herein, may be as outlined in Figure 4.
  • the wireless device 130 is a UE
  • the network node 110 is a gNB
  • the another node 120 is a UPF.
  • the legacy Random Access 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.
  • 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.
  • the network node 110 receives the DL data from the another node 120.
  • 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.
  • 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.
  • CFRA contention-free random access
  • 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.
  • a new RNTI e.g., MT-RNTI
  • 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.
  • 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.
  • C-RNTI UE-specific Cell RNTI
  • 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.
  • the network node 110 may send a RA response in PDCCH and PUSCH.
  • RRC resumption may be initiated.
  • 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.
  • 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.
  • 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.
  • embodiments disclosed herein may provide enhancements of the MT-SDT ‘Data in Msg4’ approach for NR, e.g., compared to LTE MT-EDT.
  • Embodiments herein may be understood to enable the ‘Data in Msg4’ approach for NR, and also to further reduce the signaling overhead.
  • 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.
  • 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.
  • the wireless communications network 100 may be configured to operate on NR.
  • the legacy Random Access 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.
  • RA Random Access
  • 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.
  • 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.
  • 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.
  • the preamble may be configured to be the contention free random access procedure preamble.
  • the preamble may be configured to be comprised in the first indication configured to be received.
  • 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.
  • 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.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Other units 504 may be comprised in the wireless device 130.
  • 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.
  • 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.
  • 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.
  • the receiving port 507 may be, for example, connected to one or more antennas in wireless device 130.
  • 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.
  • 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.
  • 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.
  • 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).
  • ASIC Application-Specific Integrated Circuit
  • SoC System-on-a-Chip
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the wireless communications network 100 may be configured to operate on NR.
  • the legacy Random Access 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.
  • RA Random Access
  • 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.
  • 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.
  • 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.
  • the preamble may be configured to be the contention free random access procedure preamble.
  • the preamble may be configured to be comprised in the first indication configured to be sent.
  • the preamble may be configured to be to be used with the one or more first conditions.
  • 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.
  • 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.
  • Other units 605 may be comprised in the network node 110.
  • 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.
  • 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.
  • 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.
  • the receiving port 608 may be, for example, connected to one or more antennas in network node 110.
  • 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.
  • 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.
  • 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).
  • ASIC Application-Specific Integrated Circuit
  • SoC System-on-a-Chip
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the wireless device 130 examples relate to Figure 7, Figure 4, Figure 5 and Figures 9-
  • 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.
  • the wireless communications network 100 may support New Radio (NR).
  • NR New Radio
  • 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.
  • optional actions in some examples may be represented with dashed lines.
  • the actions may be performed in a different order than that depicted Figure 7.
  • 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.
  • 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.
  • the first indication may indicate at least one of:
  • the wireless device 130 may be being paged
  • -a mobile terminated small data transmission procedure e.g., MT-SDT, may be being used.
  • the first indication may be, e.g., a paging message.
  • 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.
  • the sending in this Action 202 may be to the network node 110.
  • 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.
  • 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.
  • At least one of the following may apply:
  • the preamble may be a contention free random access procedure preamble
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • the downlink transmission may comprise data.
  • the size of the data may be under a threshold.
  • the data may be “Small Data”.
  • the downlink transmission of the data under the threshold, wherein the downlink data may be mobile terminated may be e.g., MT-SDT.
  • 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.
  • the sending in this Action 203 may be to the network node 110.
  • the sending in this Action 203 may be, e.g., transmitting, and may be performed, e.g., via the first link 141.
  • 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.
  • 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.
  • the request to resume the RRC procedure may be, e.g., an RRCResumeRequest.
  • the fourth indication may be, e.g., a Msg. 4 in the RA procedure.
  • the third indication may be sent after having received a response, e.g., Msg2, from the network node 110 to the sent second indication.
  • 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.
  • the resuming in this Action 205 may comprise an RRC resumption.
  • the one or more resources may comprise, e.g., one or more radio bearers, e.g., data radio bearers.
  • the one or more resources 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.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • 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.
  • the sending in this Action 206 may be to the network node 110.
  • 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.
  • 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.
  • 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.
  • the first indication may further comprise at least one of:
  • the additional indication may be multi-bit
  • 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
  • DRB data radio bearer
  • QoS Quality of Service
  • PDU Protocol Data Unit
  • the wireless device 130 may:
  • 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.
  • 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.
  • 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.
  • the wireless device 130 may comprise an arrangement as shown in Figure 5 or in Figure 10.
  • the network node 110 examples relate to Figure 8, Figure 4, Figure 6 and Figures 9-14.
  • 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.
  • the wireless communications network 100 may support New Radio (NR).
  • NR New Radio
  • 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.
  • data may be “Small Data”.
  • 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.
  • the sending in this Action 303 may be to the wireless device 130 operating in the wireless communications network 100.
  • 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.
  • the first indication may indicate at least one of:
  • the wireless device 130 may be being paged
  • 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.
  • the receiving in this Action 304 may be from the wireless device 130.
  • the receiving in this Action 304 may be performed, e.g., via the first link 141.
  • 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.
  • the second indication may comprise the preamble corresponding to the random access procedure.
  • 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.
  • the sending in this Action 306 may be to the wireless device 130.
  • the sending in this Action 306 may be performed, e.g., via the first link 141.
  • 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.
  • the sending in this Action 306 may be performed, e.g., after having received the preamble.
  • the downlink transmission may comprise the data.
  • the size of the data may be under the threshold.
  • the data may be “Small Data”.
  • the downlink transmission of the data under the threshold, wherein the downlink data may be mobile terminated may be e.g., MT-SDT.
  • At least one of the following may apply:
  • the preamble may be the contention free random access procedure preamble
  • the preamble may be comprised in the sent first indication
  • 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.
  • 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.
  • the receiving in this Action 305 may be from the wireless device 130.
  • the receiving in this Action 305 may be performed, e.g., via the first link 141.
  • 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.
  • 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.
  • the third indication may be received after having sent a response, e.g., Msg2, to the wireless device (130), to the sent second indication.
  • a response e.g., Msg2
  • 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.
  • the resuming in this Action 307 may comprise an RRC resumption.
  • the one or more resources may comprise, e.g., one or more radio bearers, e.g., data radio bearers.
  • the one or more resources 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the first indication may further comprise at least one of:
  • 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 determining in this Action 302 may be based on the received downlink data.
  • the sending in Action 306 of the downlink transmission may be based on the result of the determination.
  • Other units 605 may be comprised in the network node 110.
  • 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.
  • 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.
  • the network node 110 may comprise an arrangement as shown in Figure 6 or in Figure
  • 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:
  • Example 2 The method according to example 1, wherein at least one of:
  • the preamble is a contention free random access procedure preamble
  • 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.
  • 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:
  • Example 4 The method according to examples 3, wherein the method further comprises at least one of:
  • 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
  • the network node (110) 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.
  • 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:
  • an additional indication of a mobile terminated procedure e.g., MT-indication
  • the additional indication is multi-bit
  • 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.
  • 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.
  • 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.
  • 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
  • MT-SDT mobile terminated small data transmission procedure
  • Example 10 The method according to example 9, wherein at least one of:
  • the preamble is a contention free random access procedure preamble
  • 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).
  • 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
  • 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
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • the wireless device (130) receives (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.
  • 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:
  • an additional indication of a mobile terminated procedure e.g., MT-indication
  • the additional indication is multi-bit
  • 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.
  • 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.
  • 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.
  • 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.
  • Example 17 The method according to any of examples 9-16, wherein the method further comprises:
  • 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.
  • FIG. 9 Telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the wireless device 130 embodiments relate to Figure 2, Figure 4, Figure 5 and Figures 9-14.
  • 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.
  • 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.
  • 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.
  • the wireless device 130 may comprise an arrangement as shown in Figure 5 or in Figure 10.
  • the network node 110 embodiments relate to Figure 3, Figure 4, Figure 6 and Figures 9-14.
  • 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.
  • 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.
  • 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.
  • the network node 110 may comprise an arrangement as shown in Figure 6 or in Figure
  • Figure 11 Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments
  • FIG 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.
  • the host computer provides user data.
  • substep 1111 (which may be optional) of step 1110, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 1130 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.
  • step 1140 the UE executes a client application associated with the host application executed by the host computer.
  • Figure 12 Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments
  • FIG. 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.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • 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.
  • step 1230 (which may be optional), the UE receives the user data carried in the transmission.
  • Figure 13 Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments
  • 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.
  • Figure 14 Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments
  • FIG 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.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step 1430 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • 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.
  • 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.
  • 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.
  • UE user equipment
  • 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.
  • 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.
  • 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.
  • a user equipment 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.
  • 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.
  • UE user equipment
  • UE user equipment
  • 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.
  • UE user equipment
  • a user equipment 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.
  • 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.
  • UE user equipment
  • 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.
  • 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.
  • UE user equipment
  • 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.
  • UE user equipment
  • 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.
  • UE user equipment
  • the communication system of embodiment 65 further including the base station.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Procédé, mis en œuvre par un dispositif sans fil (130), permettant de traiter une transmission de liaison descendante dans un réseau de communication sans fil (100). Le dispositif sans fil (130) reçoit (201), pendant un état inactif, une première indication en provenance d'un nœud de réseau (110) indiquant que le dispositif sans fil (130) est radiorecherché, et une procédure de transmission de petite quantité de données à destination mobile est utilisée. La première indication comprend en outre une indication supplémentaire d'une procédure à destination mobile. L'indication supplémentaire indique en outre une ou plusieurs ressources pour la procédure MT-SDT que le dispositif sans fil (130) doit reprendre, comprenant un ou plusieurs supports radio. Le dispositif sans fil (130) envoie (202), au nœud de réseau (110), pendant un état inactif et en réponse à la première indication, une seconde indication comprenant un préambule. Le dispositif sans fil (130) reçoit ensuite (204), pendant un état inactif et après avoir envoyé le préambule, une transmission de liaison descendante en provenance du nœud de réseau (110). La transmission de liaison descendante comprend des données d'une taille inférieure à un seuil.
EP23724060.1A 2022-05-09 2023-05-05 Dispositif sans fil, noeud de réseau et procédés exécutés par ces derniers, destinés à traiter une transmission de liaison montante Pending EP4523488A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263364355P 2022-05-09 2022-05-09
PCT/SE2023/050445 WO2023219547A1 (fr) 2022-05-09 2023-05-05 Dispositif sans fil, nœud de réseau et procédés exécutés par ces derniers, destinés à traiter une transmission de liaison montante

Publications (1)

Publication Number Publication Date
EP4523488A1 true EP4523488A1 (fr) 2025-03-19

Family

ID=86383107

Family Applications (1)

Application Number Title Priority Date Filing Date
EP23724060.1A Pending EP4523488A1 (fr) 2022-05-09 2023-05-05 Dispositif sans fil, noeud de réseau et procédés exécutés par ces derniers, destinés à traiter une transmission de liaison montante

Country Status (2)

Country Link
EP (1) EP4523488A1 (fr)
WO (1) WO2023219547A1 (fr)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021031112A1 (fr) * 2019-08-20 2021-02-25 Qualcomm Incorporated Radiomessagerie pour la réception de petites données à terminaison mobile en mode veille et/ou inactif
EP4626133A3 (fr) * 2020-09-24 2025-11-26 Peninsula Technologies, LLC Message de libération dans une procédure de transmission de petites données
CN116686380B (zh) * 2020-10-21 2025-03-11 欧芬诺有限责任公司 小数据传输程序的下行链路数据

Also Published As

Publication number Publication date
WO2023219547A1 (fr) 2023-11-16

Similar Documents

Publication Publication Date Title
EP4265037A1 (fr) Dispositif sans fil, noeud de réseau et procédés mis en oeuvre par ces derniers pour gérer une transmission de données
JP2023529965A (ja) 電力効率的状態におけるデータ伝送
EP3949654B1 (fr) Indication de réponse d'équipement utilisateur à une transmission de données précoce
US12477419B2 (en) Method and user equipment for communication with a wireless network for handling multiple bandwidth parts, BWP
EP4205490B1 (fr) Dispositif sans fil, premier noeud de réseau et procédés réalisés par celui-ci pour gérer une communication en liaison montante vers un noeud de réseau
WO2023035860A1 (fr) Procédé et appareil de radiomessagerie
EP4229903B1 (fr) Dispositif sans fil, noeud de réseau et procédés exécutés par le dispositif sans fil et destinés à traiter une transmission en liaison montante
US12408204B2 (en) User equipment, network node, and methods performed thereby, for handling first information
EP4240098B1 (fr) Procédés et appareils de transmission de données
CN117280838A (zh) 用户设备、无线电网络节点以及在无线通信网络中执行的方法
US20240389152A1 (en) First Wireless Device, Network Node, and Methods Performed Thereby, for Handling Access to a Wireless Communications Network
EP3964015B1 (fr) Réduction de puissance (back-off) pour une procédure 2-step-ra
US20250301463A1 (en) Ue, network node and methods for handling cg-sdt resources
US20250056618A1 (en) Ue, network node and methods for handling uplink access procedures in a communications system
US20210045161A1 (en) Methods providing early redirection in wireless devices
EP4523488A1 (fr) Dispositif sans fil, noeud de réseau et procédés exécutés par ces derniers, destinés à traiter une transmission de liaison montante
WO2023004756A1 (fr) Procédé et appareil d'accès aléatoire, dispositif, et support de stockage
US20250167934A1 (en) Wireless Device, Network Node, and Methods Performed Thereby, for Handling Transmission
US20250071848A1 (en) Wireless Device, Network Node and Methods Performed Thereby for Handling Transmission of Data
WO2025014403A1 (fr) Dispositif sans fil, nœud de réseau et procédés exécutés par ceux-ci, pour gérer un préambule
WO2025058547A1 (fr) Dispositif sans fil, nœud de réseau, et procédés exécutés par ceux-ci pour gérer un échange de données
OA20521A (en) Transmit power allocation technique

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20240714

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)