Wireless device, network node, and methods performed thereby, for handling a preamble

Abstract

A method, performed by a wireless device (130), for handling a preamble. The wireless device (130) operates in a wireless communications network (100). The wireless device (130) sends (504) to a network node (110) operating in the wireless communications network (100), while the wireless device (130) is in inactive state, a preamble. The preamble indicates a request for a time alignment. The preamble indicates the preamble is reserved or dedicated for requesting time alignment in inactive state.

Description

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

[0002] HANDLING A PREAMBLE

[0003] TECHNICAL FIELD

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

[0005] BACKGROUND

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

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

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

[0009] Internet of Things (loT)

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

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

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

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

[0014] Time Alignment

[0015] Having a valid UL time alignment (TA) may be understood to be needed for a UE in order to perform UL transmissions. Lack of TA may result in that UL transmissions by a UE may not be received successfully by a network node and / or that the UL transmissions produce interference with other transmissions, degrading the performance of a wireless communications network. The terms timing advance and time alignment may be used indistinctively herein.

[0016] SUMMARY

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

[0018] There is currently no efficient way to obtain and maintain time alignment for an inactive UE. To obtain a new TA, the UE needs to initiate a RA procedure. According to specifications, the UE is expected to send a msg3 containing an RRC message, e.g., RRCResumeRequest, SI request etc, see the section in the Background entitled “NR small data transmissions in inactive state”. If an RRC message is included in msg3, this causes the network and UE to perform actions which may not be needed, such as e.g., go to connected mode, initiate an SDT procedure without any data to transmit or request SI that is may not be needed, and therefore waste resources, both radio resources and processing.

[0019] It a possible approach to this problem, a UE could “cheat” and not send any RRC message, that is, the UE could just use the TA in the RAR. However, in this case, no contention resolution would be performed. This may be understood to mean that if two UEs would use the same preamble, both would think the TA was for itself, when in fact it could be for the other UE. Hence, using this technique would not be reliable. From the network side, it may be possible from NR Rel-18 to use the mobile terminated small data transfer (MT-SDT) procedure to obtain a new TA for the UE. However, this procedure also requires transmissions of RRC messages and performing tasks which are not needed for the sake of updating the TA. It is also difficult or even impossible for the gNB to determine when the UE may need an updated TA, except by using the TAT. This may be understood to mean that the gNB may trigger the UE to obtain a new TA when this timer is about to expire, but it may not know if the UE may need a new TA due to UE movement, except if Positioning SRS transmissions in RRC Inactive may be configured. But even when these may be configured, the Rel-18 procedure may require the UE to perform an MT-SDT procedure, which is not efficient.

[0020] So, it is evident there is a need for an efficient procedure for a UE in RRCJNACTIVE to request an updated TA.

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

[0022] According to the foregoing, it is an object of embodiments herein to improve the handling of obtaining a TA. The present disclosure and their embodiments may aim to provide an efficient procedure for a UE in RRCJNACTIVE to request an updated TA.

[0023] According to a first aspect of embodiments herein, the object is achieved by a method, performed by a wireless device. The method is for handling a preamble. The wireless device operates in a wireless communications network. The wireless device sends, to the network node operating in the wireless communications network, while the wireless device is in inactive state, a preamble. The preamble indicates a request for a time alignment. The preamble indicates the preamble is reserved or dedicated for requesting time alignment in inactive state.

[0024] According to a second aspect of embodiments herein, the object is achieved by a method, performed by the network node. The method is for handling the preamble. The network node operates in the wireless communications network. The network node receives from the wireless device operating in the wireless communications network, while the wireless device is in inactive state, the preamble. The preamble indicates the request for the time alignment. The preamble indicates the preamble is reserved or dedicated for requesting time alignment in inactive state.

[0025] According to a third aspect of embodiments herein, the object is achieved by the wireless device, configured to perform the method. The wireless device may be understood to be for handling the preamble. The wireless device is configured to operate in the communications system. The wireless device is configured to send, to the network node configured to operate in the wireless communications network, while the wireless device is in inactive state, the preamble. The preamble is configured to indicate the request for the time alignment. The preamble is configured to indicate the preamble is configured to be reserved or dedicated for requesting time alignment in inactive state.

[0026] According to a fourth aspect of embodiments herein, the object is achieved by the network node, configured to perform the method. The network node may be understood to be for handling the preamble. The network node is configured to operate in the communications system. The network node is configured to receive from the wireless device configured to operate in the wireless communications network, while the wireless device is configured to be in inactive state, the preamble configured to indicate the request for the time alignment. The preamble is configured to indicate the preamble is reserved or dedicated for requesting time alignment in inactive state.

[0027] By sending the reserved or dedicated preamble, the wireless device may be enabled to obtain TA updates with an efficient procedure while in inactive mode. By sending the preamble indicating the request for a time alignment and the preamble indicating the preamble is reserved or dedicated for requesting time alignment in inactive state, the wireless device may be enabled to request and then obtain the TA without the need to use RRC signalling, and therefore engage in complete RA procedure, thereby saving time, resources, and battery.

[0028] The obtained TA updates may then be used e.g., by the wireless device, to maintain TA, which may be useful to e.g., enable SRS transmissions in inactive mode, or to perform 2-step RA at the cell edge of larger cells, where a TA may be needed. Another use case where to maintain TA may be useful may be for cooperative transmissions, to enable some of the cooperating wireless devices to remain in inactive mode. If it is required that the participating wireless devices either enter connected mode or obtain time alignment according to legacy methods, the usefulness of cooperative transmissions may be smaller due to the excessive signalling needed.

[0029] Similarly, by receiving the reserved or dedicated preamble, the network node may be enabled to provide TA updates with an efficient procedure while in inactive mode. By receiving the preamble indicating the request for a time alignment and the preamble indicating the preamble is reserved or dedicated for requesting time alignment in inactive state, the network node may be enabled to receive the TA request and then provide the TA without the need to use RRC signalling, and therefore engage in complete RA procedure, thereby saving time, resources, and energy.

[0030] BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Examples of embodiments herein are described in more detail with reference to the accompanying drawings, according to the following description. Figure 1 is a schematic diagram illustrating a 4-step random access procedure, according to existing methods.

[0032] Figure 2 is a schematic diagram illustrating a two-step random access procedure, according to existing methods.

[0033] Figure 3 is a schematic diagram depicting an example of an uplink-downlink relation, according to existing methods.

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

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

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

[0037] Figure 7 is a signalling diagram depicting a non-limiting example of a method in a wireless communications network, according to embodiments herein.

[0038] Figure 8 is a signalling diagram depicting another non-limiting example of a method in a wireless communications network, according to embodiments herein.

[0039] Figure 9 is a signalling diagram depicting yet another a non-limiting example of a method in a wireless communications network, according to embodiments herein.

[0040] Figure 10 is a signalling diagram depicting an additional non-limiting example of a method in a wireless communications network, according to embodiments herein.

[0041] Figure 11 is a signalling diagram depicting a further non-limiting example of a method in a wireless communications network, according to embodiments herein.

[0042] Figure 12 is a schematic block diagram illustrating an embodiments of a wireless device, according to embodiments herein.

[0043] Figure 13 is a schematic block diagram illustrating an embodiment of a network node, according to embodiments herein.

[0044] Figure 14 is a schematic block diagram illustrating an example of a communication system 1400 in accordance with some embodiments.

[0045] Figure 15 is a schematic block diagram illustrating an example of a UE 1500 in accordance with some embodiments.

[0046] Figure 16 is a schematic block diagram illustrating an example of a network node 1600 in accordance with some embodiments.

[0047] Figure 17 is a schematic block diagram illustrating a host 1700, which may be an embodiment of the host 1416 of Figure 14, in accordance with various aspects described herein.

[0048] Figure 18 is a schematic block diagram illustrating an example of a virtualization environment 1800 in which functions implemented by some embodiments may be virtualized. Figure 19 shows a communication diagram of a host 1902 communicating via a network node 1904 with a UE 1906 over a partially wireless connection in accordance with some embodiments.

[0049] DETAILED DESCRIPTION

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

[0051] Time Alignment

[0052] Having a valid UL time alignment may be understood to be needed for a UE in order to perform UL transmissions. This may be needed both to ensure that the UL transmissions may be received successfully by the gNB, and that the UL transmissions may not interfere with other transmissions. When a UE is in connected mode, the UE may be understood to have a valid TA as long as the time alignment timer (TAT) may be running. However, for a UE in inactive mode, this may not always be the case. For example, if the UE is configured with configured grant Small Data Transmission (SDT), or configured to perform Sounding Reference Signal (SRS) transmissions in inactive, the UE may maintain the TA as long as TAT may be running and the Received Strength Received Power (RSRP) value may be within a configurable threshold. The TA may be obtained during a Random Access (RA) procedure or by receiving a timing advance Medium Access Control (MAC) Control Element (CE).

[0053] Random Access procedure

[0054] According to the 3GPP specification 38.300, v. 17.5.0, the RA procedure may be triggered by the following events: a) initial access from RRCJDLE, b) Radio Resource Control (RRC) Connection Re-establishment procedure, c) DL or UL data arrival, during RRC_CONNECTED or during RRCJNACTIVE while SDT procedure, see clause 18.0, may be ongoing, when UL synchronisation status may be "non-synchronised", d) UL data arrival, during RRC_CONNECTED or during RRCJNACTIVE while SDT procedure may be ongoing, when there may be no Physical Uplink Control CHannel (PUCCH) resources for Scheduling Request (SR) available, e) SR failure, f) request by RRC upon synchronous reconfiguration, e.g., handover, g) RRC Connection Resume procedure from RRCJNACTIVE, h) to establish time alignment for a secondary Tracking Area Group (TAG), i) request for other System Information (SI), see clause 7.3, j) beam failure recovery, k) consistent UL Listen Before Talk (LBT) failure on SpCell, I) SDT in RRCJNACTIVE, see clause 18, m) positioning purpose during RRC_CONNECTED requiring random access procedure, e.g., when timing advance may be needed for UE positioning.

[0055] As may be concluded from the foregoing, RA may be triggered to obtain a timing advance. However, this may be done only when the UE may be in connected mode. The case “to establish time alignment for a secondary TAG” may be triggered by the gNB. 4-step Random Access procedure

[0056] A 4-step approach may be used for the RA procedure, a schematic depiction of which is shown in Figure 1. In this approach, at 1 , the UE may detect synchronization signals (SSs), such as the Primary Synchronization Signal (PSS) and the Secondary Synchronization Signal (SSS), as well as the Physical Broadcast Channel (PBCH) Block, and at 2, decode the broadcasted system information, such as the Remaining Minimum SI (RMSI) and Other SI (OSI). This may be followed by at 3, transmitting a Physical Random Access Channel (PRACH) preamble (message 1) in the uplink. The gNB may at 4, reply with a Random Access Response (RAR), (message 2) which may use the RA- Radio Network Temporary Identifier (RNTI) and preamble Identifier (id) for identification. The UE may then transmit at 5, a UE identification (message 3) on Physical Uplink Shared CHannel (PUSCH) using an uplink grant, that is, an allocation of uplink transmission resources. At 6, the gNB may then transmit a Contention Resolution Message (CRM), (message 4).

[0057] The UE may transmit message 3, on PUSCH, after receiving a timing advance (TA) command in the RAR, allowing PUSCH to be received with a timing accuracy within the cyclic prefix (CP). Without this timing advance, a very large CP would be needed in order to be able to demodulate and detect PUSCH, unless the system is applied in a cell with very small distance between UE and eNB. Since NR may also support larger cells with a need for providing a timing advance to the UE, the 4-step approach may be understood to be needed for random access procedure. It may be understood that the terms timing advance and time alignment are used herein indistinctively.

[0058] In rel-15 NR, the UE may indicate, with a Synchronization Signal Block (SSB) to the gNB, in which direction the gNB may need to transmit the RAR and subsequent messages, for example, which DL beam to use. The SSB selection by the UE may be performed by comparing the Synchronization Signal (SS)-RSRP to the rsrp-ThresholdSSB.

[0059] Once the SSB may have been selected, the indication from UE to the gNB may be performed by selection of preamble and / or PRACH occasion (RO) depending on the configuration. With the use of specific preambles and / or RO, the UE may implicitly indicate the selected SSB to the gNB.

[0060] On demand SI request

[0061] A special use case for the RA procedure may be for obtaining other SI.

[0062] The first case may be the msg1 based SI request. In this case, dedicated preambles and RA resources configured in SI-RequestConfig may be used, and when the gNB may receive the preamble transmission, it may respond with an acknowledgement, e.g., preamble id, only in the RAR, and broadcast the requested system information.

[0063] The second case may be that Contention-Based Random Access (CBRA) may be used. In this case, the UE may transmit a request, RRCSystemlnfoRequest, for the wanted SI in msg3, and the gNB may respond with Contention Resolution (CR) id and a broadcast or scheduled DL transmission of the wanted SI.

[0064] 2-step Random Access procedure

[0065] The 2-step RA procedure was standardized in NR Rel-16. With the 2-step procedure, the RA may be understood to be completed in only two steps as schematically illustrated in Figure 2. The first two steps represented in Figure 2, which are unnumbered, correspond to steps 1 and 2 depicted in Figure 1.

[0066] Step 1 : The UE may send a message A (msgA) including a RA preamble together with higher layer data, such as an RRC connection request, possibly with some small payload on PUSCH, denoted “msgA PUSCH”.

[0067] Step 2: The gNB may send a response called message B, which may be described as a modified RAR, including UE identifier assignment, TA information, and contention resolution message etc. In addition, message B (msgB) may contain a higher layer part. Similar to a RAR, a msgB may contain responses to multiple msgAs, and thus to multiple UEs, but the optional higher layer part may only pertain to one of the responses, that is, to one of the msgAs / UEs. If a response in a msgB does not have an associated higher layer part, this may be sent in a separate subsequent message, e.g., an RRC message, on the Physical Downlink Shared Channel (PDSCH).

[0068] The msgA may contain a preamble transmission and a PUSCH transmission where the preamble may be mapped to the PUSCH. This may be understood to mean that when a particular preamble is selected, the preamble may imply which time and frequency and Demodulation Reference Signal (DMRS) sequence may be used for the PUSCH transmission.

[0069] The msgB may be understood as a response to msgA, and may contain contention resolution message(s), fallback indication(s) to schedule Msg3 transmission, and backoff indication.

[0070] The msgB may contain responses to multiple UEs and different kinds of information for different UEs depending on the outcome of the msgA transmission / reception, and the load on the access resources.

[0071] Upon a successful msgA reception, the gNB may include a successRAR MAC sub Protocol Data Unit (subPDU) in the response for the concerned UE, where the successRAR MAC subPDU may include a contention resolution identity, a timing advance and a Cell Radio Network Temporary Identifier (C-RNTI) allocation.

[0072] When the UE uses 2-step RA, it may apply TA=0, or a cell-specific offset, according to specifications such as 38.211 , v. 17.5.0, corresponding to the following description. Frame structure: Frames and subframes

[0073] Downlink, uplink, and sidelink transmissions may be organized into frames with =(AfmaxVf / 10())-7c=10ms duration, each consisting of ten subframes of

[0074] 7;f= = l ms duration. The number of consecutive Orthogonal Frequency Division Multiplexing (OFDM) symbols per subframe may be Wssyu^fbrame,= WsSy^bWsaatbframe' . Each frame may be divided into two equally-sized half-frames of five subframes each, with half-frame 0 consisting of subframes 0 - 4 and half-frame 1 consisting of subframes 5 - 9.

[0075] There may be one set of frames in the uplink and one set of frames in the downlink on a carrier.

[0076] Figure 3 is a schematic representation of the uplink-downlink timing relation, as depicted in Figure 4.3.1-1 of TS 38.21 1 , v 17.5.0. Uplink frame number i for transmission from the UE may start TTA before the start of the corresponding downlink frame at the UE, where:

[0077] - / VTAand NTA offsetmay be given by clause 4.2 of [5, TS 38.213, v. 17.6.0], except for msgA transmission on PUSCH where NTA= 0 may be used;

[0078] ■WTA adj°ngiven by clause 4.2 of [5, TS 38.213, v. 17.6.0] may be derived from the higher- layer parameters TACommon, TACommon Drift, and TACommon Driftvariation if configured, otherwise NyA a™n = 0;

[0079] ■ ^T adj given by clause 4.2 of [5, TS 38.213, v. 17.5.0] may be computed by the UE based on UE position and serving-satellite-ephemeris-related higher-layers parameters if configured, otherwise v- = 0.

[0080] The use of TA=0 may be understood to mean that it may only be applied in small cells or close to the base station, determined by an RSRP above a configured threshold. Using 2-step RA close to the cell edge in large cells may not be possible, since in this case, a different TA may be needed.

[0081] NR small data transmissions in Inactive state

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

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

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

[0085] Currently, MT-SDT is being introduced in Rel-18 for NR. A Rel-18 MT-SDT work item description (WID) was approved in RAN#94e in December of 2021 , and may be found in RP- 213583. The WID comprises as objectives to specify the support for paging-triggered SDT (MT- SDT) [RAN2, RAN3], particularly, the MT-SDT triggering mechanism for UEs in RRCJNACTIVE, supporting RA-SDT and CG-SDT as the UL response, and the MT-SDT procedure for initial DL data reception and subsequent UL / DL data transmissions in RRCJNACTIVE.

[0086] It may be noted that data transmission in DL within a paging message is not in scope of this Wl.

[0087] The SDT procedure in NR Rel-17 may be understood to be only for Mobile Originated (MO)-SDT, meaning that it may only be triggered by UL data transmissions. In NR Rel-18, the standardization for MT-SDT, that is, the SDT that may be triggered by DL data transmissions proceeds. Even though the traffic is downlink oriented, it may be required that the UE connects to the network, e.g., triggered by an SDT specific page from the gNB. The ways of connecting to the network, in a SDT specific way, are currently being standardized in NR Rel. 18 and may be, but may not be limited to: RA-SDT, CG-SDT, and Legacy RACH procedures, 2 / 4 step and CBRA and Contention-Free Random Access (CFRA).

[0088] The CG-SDT procedure may require that TA is maintained and accurate when the procedure is initiated. The check of whether the TA is still valid may be performed by checking the deviation of a current RSRP value against a reference RSRP value, which may have been stored when the UE obtained the TA. If the deviation is less than a threshold, the TA may be understood to be valid. A TAT may also be used to check if the TA may be valid. The TAT may need to be running for the TA to be valid. The TAT may be restarted when a new TA is obtained.

[0089] Existing methods to obtain and maintain TA may result in wasted resources, such as radio resources and processing resources, and increased latency in a wireless communications network.

[0090] Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. Embodiments herein may be generally understood to relate to time alignment maintenance for inactive wireless devices, e.g., UEs. Particularly, embodiments herein may relate to an approach that may provide methods for an inactive wireless device, e.g., UE, to obtain UL TA, without entering connected mode, and a new process to maintain a valid TA while in inactive mode.

[0091] Obtaining a new TA may be performed by a new RA procedure using a new reserved preamble, which may be configured in SI, for requesting TA. When a network node, e.g., gNB, may receive the preamble transmission, it may respond with a RAR containing a preamblejd, TA and a grant tailored to fit the UE id of the wireless device. The wireless device may then transmit a msg3 containing only the UE id and thereafter, the network node may respond by echoing the UE id to complete the contention resolution. An alternative procedure where the network node may trigger a TA update may be performed by providing a CFRA preamble in the paging message, in which case the wireless device may transmit the preamble and the may gNB respond with a RAR containing only preamble id and TA.

[0092] Maintenance of the TA may be performed by the wireless device saving the latest RSRP value the wireless device may have had when obtaining the TA as a reference RSRP. The wireless device may then be configured to check the current RSRP value at regular intervals or when certain triggers may happen, such as when reselecting to a different cell. When the current RSRP may differ from the reference RSRP more than a configured threshold, the new RA procedure may be triggered to obtain a new TA.

[0093] Embodiments herein may be used to prepare the wireless device for a 2-step RA, that is, to achieve correct TA before 2-step procedure. Embodiments herein may also be used to efficiently perform Positioning SRS transmission in inactive, and update the TA without the wireless device entering the connected mode. A third use case may be cooperative transmission, where the coordinator wireless device of a group may handle the TA updates of the inactive users in a group efficiently.

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

[0095] Figure 4 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 be a 5G system, 5G network, or Next Gen System. In other examples, the wireless communications network 100 may be a newer system with similar functionality. Yet in other examples, the wireless communications network 100 may in addition, or alternatively, 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 Licensed-Assisted Access (LAA), enhanced eLAA (eLAA), further enhanced LAA (feLAA) and / or MulteFire. Yet in other examples, the wireless communications network 100 may further support other technologies such as, for example Wideband Code Division Multiple Access (WCDMA), Universal Terrestrial Radio Access (UTRA) TDD, Global System for Mobile communications (GSM) network, GSM / Enhanced Data Rates for GSM Evolution (EDGE) Radio Access Network (GERAN) network, Ultra-Mobile Broadband (UMB), EDGE network, network comprising any combination of Radio Access Technologies (RATs) such as e.g. MultiStandard 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. The wireless communications network 100 may typically support MTC, eMTC, loT and / or NB-loT. Thus, although terminology from 5G / NR and LTE may be used in this disclosure to exemplify embodiments herein, this should not be seen as limiting the scope of the embodiments herein to only the aforementioned system.

[0096] 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 4. The network node 110 is a radio network node. That is, a transmission point such as a radio base station, for example a gNB, or any other network node with similar features capable of serving a user equipment, such as a wireless device or a machine type communication device, in the wireless communications network 100. In some examples, such as that depicted in Figure 4 b, the network node 110 may be a distributed node, and may partially perform its functions in collaboration with a virtual node 114 in a cloud 115. The network node 110 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.

[0097] The wireless communications network 100 may cover a geographical area, which in some embodiments may be divided into cell areas, wherein each cell area may be served by a radio network node, although, one radio network node may serve one or several cells. In the example of Figure 4, the network node 110 serves a cell 120. The network node 110 may be of different classes, such as, e.g., macro base station, home base station or pico base station, based on transmission power and thereby also cell size. In some examples, the network node 110 may serve receiving nodes with serving beams. The network node 100 may support one or several communication technologies, and its name may depend on the technology and terminology used.

[0098] 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 4. The wireless device 130 comprised in the wireless communications network 100 may be a wireless communication device such as a User Equipment (UE), e.g., 5G UE or nUE, 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. The wireless device 130 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 virtual network node 114 over a second link 142, e.g., a radio link or a wired link.

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

[0100] In general, the usage of “first” and / or “second” 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.

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

[0102] More specifically, the following are embodiments related to a wireless device, such as the wireless device 130, e.g., a 5G UE, nUE or a UE, and embodiments related to a network node, such as the network node 110, e.g., a gNB.

[0103] Embodiments of a method, performed by the wireless device 130, will now be described with reference to the flowchart depicted in Figure 5. The method may be understood to be for handling a preamble. The wireless device 130 operates in the wireless communications network 100. The method may be understood to be computer-implemented.

[0104] In some embodiments, the wireless communications network 100 may support at least one of: New Radio (NR), Long Term Evolution (LTE), LTE for Machines (LTE-M), enhanced Machine Type Communication (eMTC), and Narrow Band Internet of Things (NB-loT). Several embodiments are comprised herein. In some embodiments all the actions may be performed. In some embodiments, one or more actions may be performed. It should be noted that the examples herein may be not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. A non-limiting example of the method performed by the wireless device 130 is depicted in Figure 5. Some actions may be performed in a different order than that shown in Figure 5. In Figure 5, optional actions are represented with dashed lines.

[0105] Action 501

[0106] In this Action 501 , the wireless device 130 may a first indication indicating to use a preamble to request a time alignment when the wireless device 130 may be in inactive state. The preamble may indicate a request for the time alignment. The preamble may also indicate the preamble is reserved or dedicated for requesting time alignment in inactive state.

[0107] The first indication may be for example, a configuration, such as a TA request configuration.

[0108] Obtaining in this Action 501 may comprise receiving, e.g., from the network node 110, e.g., via the first link 141 , or retrieving or fetching from a memory. In particular examples, the first indication may be a configuration obtained from the network node 110 in e.g., SI.

[0109] The inactive state may be, e.g., as defined in 5G or in a younger system having equivalent functionality, e.g., 5G. The inactive state may be, for example, an RRC inactive state.

[0110] In particular examples, the first indication may comprise at least a reserved preamble from SI. In one option, the first indication may also specify RA resources, e.g. RACH occasions, that may be used. There may be, for example, one or more preambles per SSB configured for this procedure. In particular examples, a single preamble may be valid for all SSBs, configured for this procedure. Whether one or more preambles are used may be understood to be a configuration choice. In one option, the preambles may be associated with SSBs so that the wireless device 130 may then be enabled to select the reserved preamble corresponding to the SSB with the highest RSRP, or an SSB with an RSRP above a configured threshold. It should be noted that this may not need to be defined in every cell, e.g., not in small cells. Furthermore, linking preambles with SSBs may not be needed for the typical envisioned applications.

[0111] By the wireless device 130 obtaining the first indication in this Action 501 , the wireless device 130 may be enabled to then send the preamble to the network node 110 when the wireless device 130 may need to request a time alignment while being in inactive state. Since the preamble may be reserved or dedicated for requesting the time alignment in inactive state, the wireless device 130 may thereby be enabled to request the time alignment in a more efficient manner as will be explained later.

[0112] Action 502

[0113] In some examples, the request of the TA value may be triggered by the wireless device 130.

[0114] The procedure may be triggered by the wireless device 130 in different ways, e.g., when the wireless device 130 may want to have a valid TA, e.g., for use of 2-step RA in large cells.

[0115] In this Action 502, the wireless device 130 may detect one or more conditions that may trigger the sending of the preamble, as will be described in relation to Action 504.

[0116] The one or more conditions may comprise at least one of the following. According to a first option, the one or more conditions may comprise measuring a radio signal is equal to or exceeds a first threshold. The first threshold may be an RSRP threshold, such as e.g., the legacy “msgA-RSRP-ThresholdSSB" or a new threshold. In some examples, a new RSRP threshold may be defined and only wireless devices where the current RSRP may be below this threshold may trigger the TA update. This may limit the triggering to wireless devices at cell edge. It may be noted that when comparing the current RSRP value mentioned with the stored value it may be so that the new value may be monitored over a period of time to ensure that the comparison may be fairly stable. For example, TS 38.304, v. 17.5.0 uses RSRP to estimate how fast a device may be moving by measuring the variation of RSRP over a period of time, TSearchDeltaP, which may be understood to specify the time period over which the Srxlev variation may be evaluated for relaxed measurement.

[0117] According to a second option, the one or more conditions may comprise a first change in a position of the wireless device 130. That is, the request of the TA value may be triggered by the wireless device 130 detecting a change in its position.

[0118] According to a third option, the one or more conditions may comprise a second change in a strength of a downlink pathloss reference. For example, the request of the TA value may be triggered by the wireless device 130 detecting a change in RSRP of the downlink pathloss reference.

[0119] According to a fourth option, the one or more conditions may comprise a third change in a current RSRP value with respect to a latest RSRP value as saved by the wireless device 130. In some examples, the request of the TA value may be triggered by the wireless device 130 detecting changes in the current RSRP level versus a stored RSRP value, e.g., with respect to a configured threshold. According to a fifth option, the one or more conditions may comprise a fourth change in one or more reference signals. In some examples, the request of the TA value may be triggered by the wireless device 130 detecting a change in SS-RSRP of one or several SSBs.

[0120] According to a sixth option, the one or more conditions may comprise a first expiration of a first timer. For example, the request of the TA value may be triggered by the wireless device 130 detecting when the TAT may be about to expire.

[0121] According to a seventh option, the one or more conditions may comprise a second expiration of an update timer of a time alignment. For example, the request of the TA value may be triggered by the wireless device 130 detecting when a TA update timer, a new timer, may expire.

[0122] According to an eighth option, the one or more conditions may comprise re-selection to a cell having a cell size larger than a second threshold. For example, the request of the TA value may be triggered by after cell re-selection to a large cell.

[0123] In some embodiments, the wireless device (130) may maintain time alignment by saving the latest RSRP value as a reference value, and periodically determining if the current RSRP value exceeds the reference value by more than a configured third threshold.

[0124] One or a combination of the above triggers may be specified in a standard or be up to UE implementation. Especially, the combination of the first option and some subset of any of the second-seventh options may be useful.

[0125] To define a large cell, e.g., a cell where TA may not be zero everywhere or when 2-step RA with TA=0 may not be able to be used everywhere in the cell, an indication in SI may be defined.

[0126] By the wireless device 130 detecting the one or more conditions in this Action 502, e.g., the wireless device 130 may be enabled to trigger the obtention of a new TA value, and therefore to maintain TA while in inactive state, without requiring to be prompted to do so by the network node 110. For example, in legacy NR Rel-17, a UE may transmit SRS as long as the TA may be valid, e.g., as long as a current RSRP may be within a certain threshold, and the TAT may be running. A gNB may update the TA by transmitting a Timing Advance Command MAC CE. However, the gNB does not know when to do this, that is, when the RSRP may start to drift. Instead, the gNB may need to wait until the UE stops sending SRS and consider this to be a trigger of RSRP not within threshold around reference RSRP. In contrast to this scenario, according to embodiments herein, the wireless device 130 may be enabled to update the TA, using the wireless device 130 initiated TA request, before the wireless device 130 may need to stop SRS transmissions, and a continuous SRS transmissions may be performed even when the wireless device 130 may be moving. Action 503

[0127] In some examples, the request of the TA value may be triggered by the network node

[0128] 110.

[0129] In such embodiments, in this Action 503, the wireless device 130 may receive, from the network node 110, a second indication indicating to request the time alignment value.

[0130] The second indication may be, for example, a paging message. The second indication may be, for example, a new paging message containing a CFRA, dedicated to a single wireless device, preamble for TA request and an indication that the paging is for a TA update.

[0131] In one option, the first indication of Action 501 and the second indication of this Action 503 may be the same indication. In such examples, the second indication may be a configuration which may also specify RA resources, e.g., RACH occasions that may be used. In one option, the preambles may be associated with SSBs, so that the wireless device 130 may be enabled to later select the reserved preamble corresponding to the SSB with highest RSRP or an SSB with RSRP above a configured threshold, such as the first threshold.

[0132] The receiving in this Action 503 may be performed directly from the network node, e.g., via the first link 141 , or indirectly, e.g., via another wireless device. The another wireless device 130 may be, for example, a coordinating wireless device.

[0133] By the wireless device 130 receiving the second indication in this Action 503, e.g., the wireless device 130 may be enabled to trigger the obtention of a new TA value, and therefore to maintain TA while in inactive state when prompted by the network node 110 to do so, while doing it in a more efficient manner, as will be described in the next Action 504.

[0134] Action 504

[0135] In this Action 504, the wireless device 130 sends, to the network node 110 operating in the wireless communications network 100, while the wireless device 130 is in inactive state, the preamble. The preamble indicates the request for the time alignment. As stated earlier, the preamble indicates the preamble is reserved or dedicated for requesting time alignment in inactive state. That is, the inactive state in which the wireless device 130 may be when sending the preamble, e.g., RRCJnactive state.

[0136] The sending may be performed, e.g., via the first link 141.

[0137] In some embodiments, the preamble may further indicate that: a) the network node 110 is to, responsive to the sent preamble, send to the wireless device 130, a response comprising a time alignment value, and at least one of: b) the wireless device 130 is not to establish a connection with the network node 110, c) the response is not to be followed by Radio Resource Control messages from the wireless device 130 to the network node 110 before using the time alignment value that is to be received from the network node 110, and d) the network node 110 is to refrain from providing a Temporary Cell Radio Network Temporary Identifier (TC-RNTI) in the response.

[0138] In some embodiments, the preamble may be a CFRA preamble.

[0139] In some embodiments, the sending in this Action 504 of the preamble may be based on the obtained first indication in Action 504.

[0140] In some embodiments, the sending in this Action 504 of the preamble may be responsive to one of: the receiving in Action 503, from the network node 110, of the second indication indicating to request the time alignment value, and the detecting in Action 502 of the one or more conditions triggering the sending in this Action 504 of the preamble.

[0141] The sending of the preamble in this Action 504 may be triggered by the detection of the one or more conditions in Action 502. That is, the wireless device 130 may transmit the selected preamble, when the TA request may be triggered.

[0142] In some cases, where the wireless device 130 may have detected in Action 502 that it has not moved and the previous TA is still valid, the wireless device 130 may decide to not transmit the preamble, that is, to refrain from sending the preamble. In such cases, the UE may still restart the TAT.

[0143] By sending the reserved or dedicated preamble in this Action 504, the wireless device 130 may be enabled to obtain TA updates with an efficient procedure while in inactive mode. By sending the preamble indicating the request for a time alignment and the preamble indicating the preamble is reserved or dedicated for requesting time alignment in inactive state, the wireless device may be enabled to request and then obtain the TA without the need to use RRC signalling, and therefore engage in complete RA procedure, thereby saving time, resources, and battery . The obtained TA updates may be used e.g., by the wireless device 130 to maintain TA, which may be useful to enable SRS transmissions in inactive mode, or to perform 2-step RA at the cell edge of larger cells, where a TA may be needed. Another use case where to maintain TA may be useful may be for cooperative transmissions to remain in inactive mode. If it is required that the participating wireless devices either enter connected mode or obtain time alignment according to legacy methods, the usefulness of cooperative transmissions may be smaller due to the excessive signalling needed.

[0144] Action 505

[0145] In this Action 505, the wireless device 130 may receive from the network node 110 and responsive to the sent preamble, a first response comprising the time alignment value.

[0146] The receiving may be performed, e.g., via the first link 141.

[0147] The first response may be a RAR. Particularly, the first response may be a RAR of a new format. In some embodiments, the first response may not include a TC-RNTI. In other words, the first response may lack a TC-RNTI. Since the TC-RNTI may not be present in the new RAR, a new RNTI, which may be referred to herein as “TA-RNTI”, may be defined for “lean” msg3 and msg4 transmissions. The msg3 and msg4 transmissions may be lean in that there may be no RRC signaling. This RNTI may be common for the cell 120 and configured in SI. The purpose of omitting the TC-RNTI may be understood to be that it may reduce the size of the RAR, and that the TC-RNTI may be understood to not be needed. This may be understood to be different compared to e.g., when RA may be used to move the wireless device 130 to connected mode. In this case, the TC-RNTI may be converted to the C-RNTI that the wireless device 130 may use while in connected mode.

[0148] In some embodiments, the first response may not include the TC-RNTI, and the first response may further comprise at least one of the following options. According to a first option, the first response may further comprise a first identifier. The first identifier may identify the preamble. The first identifier may be a preamble id.

[0149] According to a second option, the first response may further comprise a grant having a size adapted to fit a second identifier. The second identifier may identify the wireless device 130. The second identifier may be, e.g., a UE id. Size may be understood herein as a number of bits. The second identifier may be a 40 bits Inactive Radio Network Temporary Identifier (l-RNTI), as in legacy NR, or a short id selected by the wireless device 130.

[0150] According to a third option, the first response may further comprise the grant having the size adapted to fit the second identifier, wherein the second identifier may be smaller in size than an Inactive Radio Network Temporary Identifier (l-RNTI). The size of the short id may be smaller than the l-RNTI since the importance of uniquely determining the second identifier may be understood to be small. Furthermore, the l-RNTI may be designed to be unique over a large number of cells, e.g., RAN-based Notification Area (RNA) while the new second identifier may only need to be unique within one cell during the time the RA procedure may be ongoing. That is, it may be enough to have a low probability that two wireless devices collide during the same preamble transmission.

[0151] In some embodiments, the first response may comprise at least one of: a) the first identifier identifying preamble, b) the grant having the size adapted to fit the second identifier identifying the wireless device 130, and c) the grant having the size adapted to fit the second identifier, wherein the second identifier may be smaller in size than the l-RNTI.

[0152] In some examples, the first response may comprise only the first identifier, e.g., the preamble id, and the TA.

[0153] In particular examples, the first response may comprise only the first identifier, e.g., the preamble id, the TA and the grant of the size tailored to fit the second identifier, e.g., the UE id. By receiving the first response comprising the time alignment value in this Action 504 in response to having sent the reserved or dedicated preamble, the wireless device 130 may be enabled to perform the time alignment while in inactive state and in a more efficient manner than in existing methods, since RRC signalling may be avoided, and leaner messages may be used.

[0154] Action 506

[0155] In this Action 506, the wireless device 130 may send, to the network node 110, responsive to the received first response, a first message. The first message may comprise the second identifier of the wireless device 130. The second identifier may be selected to be unique within the cell 120 served by the network node 110 where the wireless device 130 may be located, and during a time period during which a random access procedure triggered by the sending in Action 504 of the preamble may be ongoing.

[0156] The first message may be a “lean” msg 3. In particular examples, in this Action 506, the wireless device 130 may transmit the second identifier, e.g., the UE id, using the grant supplied in the new RAR in a “lean” msg 3.

[0157] In some embodiments, the first message may comprise the second identifier scrambled with a Timing Advance (TA)-Radio Network Temporary Identifier (RNTI). Scrambling may be understood as a process of modifying a data stream, e.g., by randomizing its sequence, in order to endow the data stream with beneficial properties for its transmission. Scrambling may be understood to provide interference suppression and to help a receiver to identify different transmissions, since different transmissions, from or to e.g., different wireless devices, or for different purposes, may be scrambled by different scrambling sequences.

[0158] By sending the first message to the network node 110 in this Action 506, the wireless device 130 may be enabled to provide the second identifier, e.g., the UE id, for contention resolution, that is, that only one specific wireless device may apply the TA value using a smaller message than may be required in legacy procedures.

[0159] Action 507

[0160] In this Action 507, the wireless device 130 may receive, from the network node 110, responsive to the sent first message, another message. The another message may comprise the second identifier. In other words, in this Action 507 the wireless device 130 may receive a reply from the network node 110 with a DL transmission comprising the second identifier, e.g., the UE id. This transmission may be identified by a Downlink Control Information (DCI) addressed to the TA-RNTI.

[0161] The another message may be an Msg4, e.g, a Msg4 addressed to TA-RNTI and containing the short UE id. Receiving in this Action 507 may be performed, e.g., via the first link 141.

[0162] By receiving the another message in this Action 507, the wireless device 130 may be enabled to conclude the contention resolution and therefore apply the TA that may have been supplied in the first response. Without this action, several wireless devices could erroneously use the TA in case several wireless devices had sent the same preamble simultaneously.

[0163] Action 508

[0164] In some embodiments, the wireless device 130 may, in this Action 508, use the received time alignment value. Using in this Action 508 may be understood as e.g., applying. That is, in this Action 508, the wireless device 130 may update the TA with the received TA value.

[0165] In some examples, the wireless device 130 may apply the receive TA value, that is, the new TA, and may store the current RSRP of the downlink pathloss reference.

[0166] If the contention resolution is successful, that is, if the another message received by the wireless device 130 in Action 507 contains the same second identifier, e.g., the same UE id, that the wireless device 130 transmitted in the first message, e.g., the lean msg3, the wireless device 130 may then apply in this Action 508 the new TA and store the current RSRP of the downlink pathloss reference. The wireless device 130 may then also be enabled to start or restart the TAT.

[0167] In case the contention resolution fails, the wireless device 130 may restart the procedure from Action 504. Since this procedure is typically not time critical, the wireless device 130 may be allowed to do more preamble transmissions than in legacy RA procedures. This may be achieved by not incrementing the PREAMBLE_TRANSMISSION_COUNTER at every preamble transmission or by having a different, e.g., higher, preambleTransMax for the random access procedure used for TA request.

[0168] According to the foregoing, compared to the currently specified RA procedure, embodiments herein may have the following differences compared to the normal RA procedure: a) reserved preamble for TA request, which may be specified in SI, b) RAR with smaller grant and no TC-RNTI, c) msg3 with only new short UE id, scrambled with TA-RNTI, and d) Msg4 addressed to TA-RNTI and containing the short UE id.

[0169] By using the received time alignment value in this Action 508, the wireless device 130 may be enabled to perform the time alignment while in inactive state and in a more efficient manner than in existing methods, since RRC signalling may be avoided and leaner messages may be used.

[0170] Embodiments of a method, performed by the network node 110 will now be described with reference to the flowchart depicted in Figure 6. The method may be understood to be for handling the preamble. The network node 110 operates in the wireless communications network 100. The method may be understood to be computer-implemented.

[0171] In some embodiments, the wireless communications network 100 may support at least one of: NR, LTE, LTE-M, eMTC, and NB-loT.

[0172] Several embodiments are comprised herein. In some embodiments all the actions may be performed. In some embodiments, one or more actions may be performed. It should be noted that the examples herein may be not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. A non-limiting example of the method performed by the network node 110 is depicted in Figure 6. Some actions may be performed in a different order than that shown in Figure 6. In Figure 6, optional actions are represented with dashed lines. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the wireless device 130 and will thus not be repeated here. For example, the inactive state may be the RRCJnactive state.

[0173] Action 601

[0174] In this Action 601 , the network node 110 may send, to the wireless device 130, the first indication. The first indication may indicate to use the preamble to request the time alignment when the wireless device 130 may be in inactive state.

[0175] The sending may be performed, e.g., via the first link 141.

[0176] Action 602

[0177] In this Action 602, the network node 110 may send, to the wireless device 130, the second indication indicating to request the time alignment value.

[0178] The sending may be performed, e.g., via the first link 141.

[0179] Action 603

[0180] In this Action 603, network node 110 receives from the wireless device 130 operating in the wireless communications network 100, while the wireless device 130 is in inactive state, the preamble. The preamble indicates the request for the time alignment. The preamble indicates the preamble is reserved or dedicated for requesting time alignment in inactive state.

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

[0182] In some embodiments, the preamble may further indicate that: a) the network node 110 is to, responsive to the received preamble, send to the wireless device 130, a response comprising a time alignment value, and at least one of: b) the wireless device 130 is not to establish a connection with the network node 110, c) the response is not to be followed by Radio Resource Control messages from the wireless device 130 to the network node 110 before using the time alignment value that is to be received from the network node 110, and d) the network node 110 is to refrain from providing a TC-RNTI in the response.

[0183] In some embodiments, the preamble may be a CFRA preamble.

[0184] The receiving in this Action 603 of the preamble may be based on the sent first indication in Action 601 .

[0185] In some embodiments, the receiving in this Action 603 of the preamble may be responsive to one of: a) the sending in Action 602, to the wireless device 130, of the second indication indicating to request the time alignment value, and b) the one or more conditions, detected by the wireless device 130 triggering the receiving 603 of the preamble.

[0186] In some embodiments, the one or more conditions may comprise at least one of: a) measuring the radio signal may be equal to or exceed the first threshold, b) the first change in the position of the wireless device 130, c) the second change in the strength of the downlink pathloss reference, c) the third change in the current RSRP value with respect to the latest RSRP value as saved by the wireless device 130, d) the fourth change in the one or more reference signals, e) the first expiration of the first timer, f) the second expiration of the update timer of the time alignment, and g) the re-selection to the cell having the cell size larger than the second threshold.

[0187] By receiving the reserved or dedicated preamble in this Action 603, the network node 110 may be enabled to provide TA updates with an efficient procedure while in inactive mode. By receiving the preamble indicating the request for a time alignment and the preamble indicating the preamble is reserved or dedicated for requesting time alignment in inactive state, the network node 110 may be enabled to receive the TA request and then provide the TA without the need to use RRC signalling, and therefore engage in complete RA procedure, thereby saving time, resources, and energy.

[0188] Action 604

[0189] In this Action 604, the network node 110 may send to the wireless device 130 and responsive to the received preamble, the first response comprising the time alignment value.

[0190] The sending may be performed, e.g., via the first link 141.

[0191] In some embodiments, the first response may not include the TC-RNTI, and the first response may further comprise at least one of the following options. According to the first option, the first response may further comprise the first identifier. The first identifier may identify the preamble. According to the second option, the first response may further comprise the grant having the size adapted to fit the second identifier. The second identifier may identify the wireless device 130. According to the third option, the first response may further comprise the grant having the size adapted to fit the second identifier, wherein the second identifier may be smaller in size than the l-RNTI.

[0192] In some embodiments, the first response may comprise at least one of: a) the first identifier identifying preamble, b) the grant having the size adapted to fit the second identifier identifying the wireless device 130, and c) the grant having the size adapted to fit the second identifier, wherein the second identifier may be smaller in size than the l-RNTI.

[0193] Action 605

[0194] In this Action 605, the network node 110 may receive, from the wireless device 130, responsive to the sent first response, the first message comprising the second identifier of the wireless device 130. The second identifier may be selected to be unique within the cell 120 served by the network node 110 where the wireless device 130 may be located, and during the time period during which the RA procedure triggered by receiving 605 of the preamble may be ongoing.

[0195] In some embodiments, the first message may comprise the second identifier scrambled with the TA-RNTI.

[0196] The receiving may be performed, e.g., via the first link 141.

[0197] Action 606

[0198] In this Action 606, the network node 110 may send, to the wireless device 130, responsive to the received first message, the another message. The another message may comprise the second identifier.

[0199] The sending may be performed, e.g., via the first link 141 .

[0200] Figure 7 is a signalling diagram depicting a first non-limiting example of a method in a wireless communications network 100, according to embodiments herein. In this example, the wireless device 130 is a UE, denoted “UE1” and the network node 110 is a gNB. The method depicted in the first example of Figure 7 is for an RRCJNACTIVE UE initiated TA request. In the first step, the wireless device 130, in accordance with Action 501 and Action 601 , may obtain a TA request configuration which may contain at least a reserved preamble from SI. In one option, the configuration may also specify RA resources, e.g., RACH occasions that may be used. In one option, the preambles may be associated with SSBs, so that the wireless device 130 may select the reserved preamble corresponding to the SSB with the highest RSRP or an SSB with an RSRP above a configured threshold. It may be noted that this need not be defined in every cell, e.g., not in small cells. Furthermore, linking preambles with SSBs may not be needed for the typical envisioned applications. In a second step, when the TA request may be triggered, as may be detected by the wireless device 130 in accordance with Action 502, the wireless device 130 may transmit the selected preamble in accordance with Action 504 and Action 603. In a third step, the network node 110 may respond, in accordance with Action 604 and Action 505, with a RAR of a new format, containing only preamble id, TA and grant of size tailored to fit a UE id. The UE id may be a 40 bits l-RNTI, as in legacy NR, or a short id selected by the wireless device 130. The size of the short id may be smaller than the l-RNTI since the importance of uniquely determining the UE id may be understood to be small. Furthermore, the l-RNTI may be designed to be unique over a large number of cells, e.g., RNA, while the new UE id may only need to be unique within one cell during the time the RA procedure may be ongoing. That is, it may be enough to have a low probability that two wireless devices collide during the same preamble transmission. Since the TC-RNTI is not present in the new RAR, a new RNTI, called TA-RNTI herein, may be defined for “lean” msg3 and msg4 transmissions, involving no RRC signaling. This RNTI may be common for the cell and configured in SI. As stated earlier, the purpose of omitting the TC-RNTI may be understood to be that it may reduce the size of the RAR and that the TC-RNTI may not be needed. This may be understood to be different compared to e.g., when RA may be used to move the wireless device 130 to connected mode. In this case, the TC-RNTI may be converted to the C-RNTI that the UE may use while in connected mode. In a fourth step, in accordance with Action 506 and Action 605, the UE may transmit the UE id using the grant supplied in the new RAR in a “lean” msg 3. This message may be scrambled with the TA- RNTI. The UE may transmit the UE id using the grant supplied in the new RAR in a “lean” msg 3. In a fifth step, in accordance with Action 606 and Action 507, the network node 110 may reply with a DL transmission containing the UE id. This transmission may be identified by a DCI addressed to the TA-RNTI. This step may conclude the contention resolution. In the sixth step, if the contention resolution is successful, that is, the wireless device 130 may have received the DL message containing the same UE id that the wireless device 130 may have transmitted in msg3, the wireless device 130, in accordance with Action 508, may apply the new TA and store the current RSRP of the downlink pathloss reference. At 701 , the wireless device 130 may start or restart the TAT. In case the sixth step fails, that is, in case the contention resolution fails, the wireless device 130 may restart the procedure from step 2. Since this procedure may be understood to be typically not time critical, the wireless device 130 may be allowed to perform more preamble transmissions than legacy RA procedures. This may be achieved by not incrementing the PREAMBLE_TRANSMISSION_COUNTER at every preamble transmission or by having a different (higher) preambleTransMax for the random access procedure used for TA request. AS stated earlier, compared to the currently specified RA procedure, the new procedure according to embodiments herein may be understood to have the following differences: a) reserved preamble for TA request, specified in SI, b) RAR with smaller grant and no TC-RNTI, c) msg3 with only new short UE id, scrambled with TA-RNTI, d) Msg4 addressed to TA-RNTI and containing the short UE id.

[0201] Figure 8 is a signalling diagram depicting a second non-limiting example of a method in a wireless communications network 100, according to embodiments herein. In this example, the wireless device 130 is a UE, denoted “UE1” and the network node 110 is a gNB. The method depicted in the second example of Figure 8 is for a gNB initiated TA request. In the first step, in accordance with Action 601 , Action 602 and Action 501 and Action 503, the wireless device 130 may be paged with a new paging message containing a CFRA, dedicated to a single UE, preamble for TA request and an indication that the paging is for a TA update. In one option, the configuration may also specify RA resources, e.g., RACH occasions that may be used. In one option, the preambles may be associated with SSBs so that the wireless device 130 may select the reserved preamble corresponding to the SSB with highest RSRP or an SSB with RSRP above a configured threshold. In the second step, in accordance with Action 603 and Action 504, the wireless device 130 may transmit the selected CFRA preamble. In one option, where the wireless device 130 may detect that it has not moved and the previous TA may still be valid, wireless device 130 may decide to not transmit the preamble. In this option, the UE may still restart the TAT. In a third step, in accordance with Action 604 and Action 505, the network node 110 may respond with a RAR of a new format, containing only preamble id and TA. In the fourth step, in accordance with Action 508, the wireless device 130 may apply the new TA and store the current RSRP of the downlink pathloss reference. At 801 , the wireless device 130 may then start or restart the TAT.

[0202] Figure 9 is a signalling diagram depicting a third non-limiting example of a method in a wireless communications network 100, according to embodiments herein. In this example, the wireless device 130 is a UE, denoted “UE1” and the network node 110 is a gNB. The method depicted in the third example of Figure 9 is of a first example use case of embodiments herein when applied to a 2-step RA procedure, enabling the use of 2-step RA in large cells, even at the cell border. The wireless device 130 may maintain a valid TA according to the above procedures, that is, trigger TA updates when needed or when triggered by the network node 110. In one option, the TA value may be the TA value the wireless device 130 have had in connected mode before going to inactive. Also in this case, the wireless device 130 may store a reference RSRP and start the TAT. It may be noted that the description of the steps depicted up to Action 701 corresponds to that already provided in Figure 7 and will not be repeated. At 901 , after the wireless device 130 may have stored the RSRP, the wireless device 130 may remain in inactive state. After some time may elapse, when a 2-step RA may be triggered at 902, the wireless device 130 may first check if the current TA may be valid by comparing the current RSRP value with the stored reference RSRP value and that the TAT is running at 903. If the difference is less than a threshold, the wireless device 130 may use the current TA value for the PUSCH transmission in msgA at 904, in accordance with Action 508. The wireless device 130 may then receive an MsgB from the network node 110 at 905, and at 906, update the TA again, and start the TAT once more. If the current TA is not valid according to the above, the wireless device 130 may check if the RSRP may be above the legacy “msgA-RSRP-ThresholdSSB" and if so, wireless device 130 may continue with the 2- step RA procedure using TA=0 according to legacy NR Rel. 17. It may be noted that when comparing the current RSRP value mentioned with the stored value it may be so that the new value may be monitored over a period of time to ensure that the comparison may be fairly stable.

[0203] Figure 10 is a signalling diagram depicting a fourth non-limiting example of a method in a wireless communications network 100, according to embodiments herein. In this example, the wireless device 130 is a UE, denoted “UE1” and the network node 110 is a gNB. The method depicted in the fourth example of Figure 10 is of a second use case of embodiments herein concerning Positioning SRS transmission in RRCJNACTIVE. In legacy NR Rel-17, the UE may transmit SRS as long as the TA may be valid, that is, as long as the current RSRP may be within a certain threshold, and the TAT may be running. The gNB may update the TA by transmitting a Timing Advance Command MAC CE. However, the gNB does not know when to do this, that is, when the RSRP may start to drift. Instead, the gNB may need to wait until the UE may stop sending SRS and consider this to be a trigger of the RSRP not being within threshold around a reference RSRP. With embodiments herein, the wireless device 130 may update the TA, e.g., using the TA request initiated by the wireless device 130, before the wireless device 130 may need to stop SRS transmissions and continuous SRS transmissions may be performed even for moving UEs. This is illustrated in Figure 10. In a first step, in accordance with Action 501 and Action 601 , the wireless device 130 may receive the first indication comprised in an UL SRS configuration. It may be noted, however, that the first indication may be received separately from the UL SRS configuration. The wireless device 130 may be in inactive state and save the context at 1001. At 1002, the wireless device 130 may perform SRS transmissions according to the UL SRS configuration received at 501 . Next, in accordance with Action 502, the wireless device 130 may detect one of the one or more conditions for which a TA request may be triggered. Then, in accordance with Action 504 and Action 603, the wireless device 130 may send a reserved preamble to the network node 110. Next, in accordance with Action 604 and Action 505, the network node 110 may send a new TA. Subsequently, in accordance with Action 506 and Action 605, the wireless device 130 may send an Msg3 to the network node 110 containing the UE id. The network node 110 may then send the another message comprising the UE id, in accordance with Action 606 and Action 507. Act 1003, the wireless device 130 may continue performing UL SRS transmissions. By performing the actions according to embodiments herein, the wireless device 130 may continue to use SRS transmissions in inactive state, even if the initial TA may become invalid.

[0204] Figure 11 is a signalling diagram depicting a fifth non-limiting example of a method in a wireless communications network 100, according to embodiments herein. The method depicted in the fifth example of Figure 11 is of a third use case of embodiments herein when applied to cooperative transmissions. In this example, there are three wireless devices having a description similar to the wireless device 130: a first wireless device 131 , which is a first UE, denoted “UE1”, a second wireless device 132, which is a second UE, denoted “UE2”, and a third wireless device 133, which is a third UE. The third wireless device 133 is a coordinating wireless device for the group transmissions and it is denoted “coordJJE”. The network node 110 is a gNB. In this example, embodiments herein may be used to give inactive UEs in a cooperative transmission group a new TA, which may be used when performing group SRS transmissions in Inactive, or for any cooperative UL transmission when in inactive. In the first step, at 1101 , the network node 110 may configure the the first wireless device 131 , the second wireless device 132, and the third wireless device 133 with an UL SRS configuration. Each of the first wireless device 131 and the second wireless device 132 may then go into inactive state. Next, in accordance with Action 501 , Action 503, Action 601 and Action 602, the coordinator, that is, the third wireless device 133, may be given a dedicated preamble that the first wireless device 131 , the second wireless device 132 and the third wireless device 133 may use to obtain new TAs. In the figure, the dedicated preamble is sent in a paging message, but the preamble may also be sent in an RRC message. The preamble may be understood to be dedicated for the group and the coordinator third wireless device 133 may schedule the use of the preamble between the wireless devices 130 in the group to avoid preamble collisions by transmitting a message containing the dedicated preamble id over sidelink. When the first wireless device 131 receives the SL transmission containing the dedicated preamble id in accordance with Action 501 and Action 503, the first wireless device 131 may, in accordance with Action 504 and Action 603, transmit the dedicated preamble and, in response, in accordance with Action 505 and Action 604, receive the new RAR containing the preamble id and the current or new TA. This may then be repeated for the other wireless devices in the group, such as it is depicted for the wireless device 132. At 1102, the first wireless device 131 , the second wireless device 132 and the third wireless device 133 perform a group SRS transmission. Embodiments herein may be understood to enable the use of cooperative transmissions for wireless devices in inactive state, where the participating wireless devices may obtain TA in a more efficient way than using legacy methods.

[0205] As a summarized overview of the foregoing, embodiments herein provide a scheme to enable wireless devices in inactive mode to become time aligned and maintain time alignment while remaining in inactive mode in an efficient way. Obtaining TA may be performed by a new scheme for the RA procedure where the wireless device 130 may use a reserved preamble, on cell level, or a CFRA preamble that may be supplied in a paging message. Maintenance of TA may be performed by different triggers that may make the wireless device 130 trigger RA to obtain TA.

[0206] Certain embodiments disclosed herein may provide one or more of the following technical advantage(s), which may be summarized as follows. Embodiments herein, may be understood to allow use of an efficient procedure for obtaining TA updates while in inactive mode. This may be used e.g., by the wireless device 130 to maintain TA that may be useful to enable SRS transmissions in inactive, or do 2-step RA at the cell edge of larger cells where a TA may be needed. Another use case may be where it may be useful may be for cooperative transmissions.

[0207] Figure 12 depicts an example of the arrangement that the wireless device 130 may comprise to perform the method actions described above in relation to Figure 5, and / or any of Figures 7-11. The wireless device 130 may be understood to be for handling the preamble. The wireless device 130 may be configured to operate in the communications system 100.

[0208] In some embodiments, the wireless communications network 100 may be configured to support at least one of: NR, LTE, LTE-M, eMTC, and NB-loT.

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

[0210] The wireless device 130 is configured to send, to the network node 110 configured to operate in the wireless communications network 100, while the wireless device 130 is in inactive state, the preamble. The preamble is configured to indicate the request for the time alignment. The preamble is configured to indicate the preamble is configured to be reserved or dedicated for requesting time alignment in inactive state.

[0211] In some embodiments, the preamble may be configured to further indicate that: a) the network node 110 is to, responsive to the preamble configured to be sent, send to the wireless device 130, the response configured to comprise the time alignment value, and at least one of: b) the wireless device 130 is not to establish a connection with the network node 110, c) the response is not to be followed by RRC messages from the wireless device 130 to the network node 110 before using the time alignment value that is configured to be received from the network node 110, and d) the network node 110 is to refrain from providing a TC-RNTI in the response.

[0212] In some embodiments, the preamble may be configured to be the CFRA preamble.

[0213] In some embodiments, the wireless device 130 may be further configured to receive from the network node 110 and responsive to the preamble configured to be sent, the first response configured to comprise the time alignment value.

[0214] In some embodiments, the first response may be configured to not include the TC-RNTI, and the first response may be further configured to comprise at least one of: a) the first identifier, the first identifier being configured to identify the preamble, b) the grant configured to have the size adapted to fit the second identifier, the second identifier being configured to identify the wireless device 130, and c) the grant configured to have the size adapted to fit the second identifier, wherein the second identifier may be configured to be smaller in size than the l-RNTI.

[0215] In some embodiments, the wireless device 130 may be further configured to the request may be send, to the network node 110, responsive to the first response configured to be received, the first message configured to comprise the second identifier of the wireless device 130. The second identifier may be configured to be selected to be unique a) within the cell 120 configured to be served by the network node 110 where the wireless device 130 may be configured to be located, and b) during the time period during which the RA procedure configured to be triggered by the sending of the preamble may be configured to be ongoing.

[0216] In some embodiments, the wireless device 130 may be further configured to receive, from the network node 110, responsive to the first message configured to be sent, the another message. The another message may be configured to comprise the second identifier.

[0217] In some embodiments, the first message may be configured to comprise the second identifier scrambled with the TA-RNTI.

[0218] In some embodiments, the wireless device 130 may be further configured to obtain the first indication configured to indicate to use the preamble to request the time alignment when the wireless device 130 may be in inactive state. In such embodiments, the sending of the preamble may be configured to be based on the first indication configured to be obtained. In some embodiments, the wireless device 130 may be further configured to use the time alignment value configured to be received.

[0219] In some embodiments, the sending of the preamble may be configured to be responsive to one of: a) receiving, from the network node 110, the second indication configured to indicate to request the time alignment value, and b) detecting the one or more conditions triggering the sending of the preamble.

[0220] In some embodiments, the one or more conditions may be configured to comprise at least one of: a) measuring the radio signal is equal to or exceeds the first threshold, b) the first change in the position of the wireless device 130, c) the second change in the strength of the downlink pathloss reference, d) the third change in the current RSRP value with respect to the latest RSRP value as saved by the wireless device 130, e) the fourth change in the one or more reference signals, f) the first expiration of the first timer, g) the second expiration of the update timer of the time alignment, and h) re-selection to the cell configured to have the cell size larger than the second threshold.

[0221] In some embodiments, the wireless device 130 may be configured to maintain time alignment by saving the latest RSRP value as a reference value, and periodically determining if the current RSRP value exceeds the reference value by more than a configured third threshold.

[0222] The embodiments herein in the wireless device 130 may be implemented through one or more processors, such as a processing circuitry 1201 in the wireless device 130 depicted in Figure 12, 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.

[0223] The processing circuitry 1201 may be configured to, or operable to, perform the method actions according to Figure 5.

[0224] The wireless device 130 may further comprise a memory 1202 comprising one or more memory units. The memory 1202 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.

[0225] In some embodiments, the wireless device 130 may receive information from, e.g., the network node 110, the second wireless device 132, the third wireless device 133, or another device or structure in the wireless communications network 100, through a receiving port 1203. In some embodiments, the receiving port 1203 may be, for example, connected to one or more antennas in wireless device 130. Since the receiving port 1203 may be in communication with the processing circuitry 1201 , the receiving port 1203 may then send the received information to the processing circuitry 1201. The receiving port 1203 may also be configured to receive other information.

[0226] The processing circuitry 1201 in the wireless device 130 may be further configured to transmit or send information to e.g., the network node 110, the second wireless device 132, the third wireless device 133, or another device or structure in the wireless communications network 100, through a sending port 1204, which may be in communication with the processing circuitry 1201 , and the memory 1202.

[0227] Those skilled in the art will also appreciate that the processing circuitry 1201 described above may comprise 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 processing circuitry 1201 , perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

[0228] Also, in some embodiments, the wireless device 130 may be configured to perform the actions of Figure 5 with respective units that may be implemented as one or more applications running on one or more processors such as the processing circuitry 1201.

[0229] Thus, the methods according to the embodiments described herein for the wireless device 130 may be respectively implemented by means of a computer program 1205 product, comprising instructions, i.e., software code portions, which, when executed on at least one processing circuitry 1201 , cause the at least one processing circuitry 1201 to carry out the actions described herein, as performed by the wireless device 130. The computer program 1205 product may be stored on a computer-readable storage medium 1206. The computer- readable storage medium 1206, having stored there on the computer program 1205, may comprise instructions which, when executed on at least one processing circuitry 1201 , cause the at least one processing circuitry 1201 to carry out the actions described herein, as performed by the wireless device 130. In some embodiments, the computer-readable storage medium 1206 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 1205 product may be stored on a carrier containing the computer program 1205 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 1206, 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 second wireless device 132, the third wireless device 133, or another device or 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.

[0230] In other embodiments, the wireless device 130 may also comprise a radio circuitry 1207, which may comprise e.g., the receiving port 1203 and the sending port 1204. The radio circuitry 1207 may be configured to set up and maintain at least a wireless connection with the network node 110, the second wireless device 132, the third wireless device 133, or another device or structure in the wireless communications network 100. Circuitry may be understood herein as a hardware component.

[0231] Hence, embodiments herein also relate to the wireless device 130 comprising the processing circuitry 1201 and the memory 1202, said memory 1202 containing instructions executable by said processing circuitry 1201 , whereby the wireless device 130 is operative to perform the actions described herein in relation to the wireless device 130, e.g., in Figure 5.

[0232] Figure 13 depicts an example of the arrangement that the network node 110 may comprise to perform the method actions described above in relation to Figure 6, and / or any of Figures 7-11. The network node 110 may be understood to be for handling the preamble. The network node 110 may be configured to operate in the communications system 100.

[0233] In some embodiments, the wireless communications network 100 may be configured to support at least one of: NR, LTE, LTE-M, eMTC, and NB-loT.

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

[0235] The network node 110 is configured to receive from the wireless device 130 configured to operate in the wireless communications network 100, while the wireless device 130 is configured to be in inactive state, the preamble configured to indicate the request for the time alignment. The preamble is configured to indicate the preamble is reserved or dedicated for requesting time alignment in inactive state.

[0236] In some embodiments, the preamble may be configured to further indicate that: a) the network node 110 is to, responsive to the preamble configured to be received, send to the wireless device 130, the response configured to comprise the time alignment value, and at least one of: b) the wireless device 130 is not to establish a connection with the network node 110, c) the response is not to be followed by RRC messages from the wireless device 130 to the network node 110 before using the time alignment value that is configured to be received from the network node 110, and d) the network node 110 is to refrain from providing a TC- RNTI in the response.

[0237] In some embodiments, the preamble may be configured to be the CFRA preamble.

[0238] The network node 110 may be further configured to send to the wireless device 130 and responsive to the preamble configured to be received, the first response configured to comprise the time alignment value.

[0239] In some embodiments, the first response may be configured to not include the TC-RNTI, and the first response may be further configured to comprise at least one of: a) the first identifier, the first identifier being configured to identify the preamble, b) the grant configured to have the size adapted to fit the second identifier, the second identifier being configured to identify the wireless device 130, and c) the grant configured to have the size adapted to fit the second identifier, wherein the second identifier may be configured to be smaller in size than the l-RNTI.

[0240] The network node 110 may be further configured to receive, from the wireless device 130, responsive to the first response configured to be sent, the first message configured to comprise the second identifier of the wireless device 130. The second identifier may be configured to be selected to be unique a) within the cell 120 configured to be served by the network node 110 where the wireless device 130 the configured to be located, and b) during the time period during which the RA procedure configured to be triggered by the receiving of the preamble may be configured to be ongoing.

[0241] The network node 110 may be further configured to send, to the wireless device 130, responsive to the first message configured to be received, the another message. The another message may be configured to comprise the second identifier.

[0242] In some embodiments, the first message may be configured to comprise the second identifier scrambled with the TA-RNTI.

[0243] The network node 110 may be further configured to send, to the wireless device 130, the first indication configured to indicate to use the preamble to request the time alignment when the wireless device 130 may be configured to be in inactive state. The receiving of the preamble may be configured to be based on the first indication configured to be sent. In some embodiments, the receiving of the preamble may be configured to be responsive to one of the following options. According to a first option, the receiving of the preamble may be configured to be responsive to the network node 110 sending, to the wireless device 130, the second indication configured to indicate to request the time alignment value.

[0244] According to a second option, the receiving of the preamble may be configured to be responsive to the one or more conditions, configured to be detected by the wireless device 130 triggering the receiving of the preamble.

[0245] In some embodiments, the one or more conditions may be configured to comprise at least one of: a) measuring the radio signal is equal to or exceeds the first threshold, b) the first change in the position of the wireless device 130, c) the second change in the strength of the downlink pathloss reference, d) the third change in the current RSRP value with respect to the latest RSRP value as saved by the wireless device 130, e) the fourth change in the one or more reference signals, f) the first expiration of the first timer, g) the second expiration of the update timer of the time alignment, and h) re-selection to the cell configured to have the cell size larger than the second threshold.

[0246] The embodiments herein in the network node 110 may be implemented through one or more processors, such as a processing circuitry 1301 in the network node 110 depicted in Figure 13, 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.

[0247] The processing circuitry 1301 may be configured to, or operable to, perform the method actions according to Figure 6.

[0248] The network node 110 may further comprise a memory 1302 comprising one or more memory units. The memory 1302 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.

[0249] In some embodiments, the network node 110 may receive information from, e.g., the wireless device 130, the first wireless device 131 , the second wireless device 132, the third wireless device 133, or another device or structure in the wireless communications network 100, through a receiving port 1303. In some embodiments, the receiving port 1303 may be, for example, connected to one or more antennas in network node 110. In other embodiments, the network node 110 may receive information from another structure in the wireless communications network 100 through the receiving port 1303. Since the receiving port 1303 may be in communication with the processing circuitry 1301 , the receiving port 1303 may then send the received information to the processing circuitry 1301. The receiving port 1303 may also be configured to receive other information.

[0250] The processing circuitry 1301 in the network node 110 may be further configured to transmit or send information to e.g., the wireless device 130, the first wireless device 131 , the second wireless device 132, the third wireless device 133, or another device or structure in the wireless communications network 100, through a sending port 1304, which may be in communication with the processing circuitry 1301 , and the memory 1302.

[0251] Those skilled in the art will also appreciate that the processing circuitry 1301 described above may comprise 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 processing circuitry 1301 , perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

[0252] Also, in some embodiments, the network node 110 may be configured to perform the actions of Figure 6 with respective units that may be implemented as one or more applications running on one or more processors such as the processing circuitry 1301.

[0253] Thus, the methods according to the embodiments described herein for the network node 110 may be respectively implemented by means of a computer program 1305 product, comprising instructions, i.e., software code portions, which, when executed on at least one processing circuitry 1301 , cause the at least one processing circuitry 1301 to carry out the actions described herein, as performed by the network node 110. The computer program 1305 product may be stored on a computer-readable storage medium 1306. The computer- readable storage medium 1306, having stored thereon the computer program 1305, may comprise instructions which, when executed on at least one processing circuitry 1301 , cause the at least one processing circuitry 1301 to carry out the actions described herein, as performed by the network node 110. In some embodiments, the computer-readable storage medium 1306 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 1305 product may be stored on a carrier containing the computer program 1305 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 1306, 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 first wireless device 131 , the second wireless device 132, the third wireless device 133, or another device or 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.

[0254] In other embodiments, the network node 110 may also comprise a radio circuitry 1307, which may comprise e.g., the receiving port 1303 and the sending port 1304. The radio circuitry 1307 may be configured to set up and maintain at least a wireless connection with the wireless device 130, the first wireless device 131 , the second wireless device 132, the third wireless device 133, or another device or structure in the wireless communications network 100. Circuitry may be understood herein as a hardware component.

[0255] Hence, embodiments herein also relate to the network node 110 comprising the processing circuitry 1301 and the memory 1302, said memory 1302 containing instructions executable by said processing circuitry 1301 , whereby the network node 110 is operative to perform the actions described herein in relation to the network node 110, e.g., in Figure 6.

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

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

[0258] Figure 14 shows an example of a communication system 1400 in accordance with some embodiments.

[0259] In the example, the communication system 1400, such as the wireless communications network 100, includes a telecommunication network 1402 that includes an access network 1404, such as a radio access network (RAN), and a core network 1406, which includes one or more core network nodes 1408. The access network 1404 includes one or more access network nodes, such as the network node 110. For example, network nodes 1410a and 1410b, one or more of which may be generally referred to as network nodes 1410, or any other similar 3rdGeneration Partnership Project (3GPP) access node or non-3GPP access point. The communications system 1400 comprises a plurality of wireless devices, such as the wireless device 130. In Figure 14, the plurality of wireless devices comprises UEs 1412a, 1412b, 1412c, and 1412d, one or more of which may be generally referred to as UEs 1412. The network nodes 1410 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1412a, 1412b, 1412c, and 1412d to the core network 1406 over one or more wireless connections. Any of the UEs 1412a, 1412b, 1412c, and 1412d are examples of the wireless device 130.

[0260] In relation to Figures 14, 17, and 19, which are described next, it may be understood that any UE is an example of the wireless device 130, and that any description provided for the UE 1412 or for the UE 1906 equally applies to the wireless device 130. It may be also understood that any network node is an example of the network node 110, and that any description provided for any network node 1410 or for the network node 1904 equally applies to the network node 110. It may further be understood that the communication system 1400 is an example of the wireless communication network 100, and that any description provided for the communication system 1400 equally applies to the wireless communication network 100.

[0261] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1400 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired orwireless connections. The communication system 1400 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system. The wireless device 130, exemplified in Figure 14 as the UEs 1412, may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network node 110, exemplified in Figure 14 as network nodes 1410, and other communication devices. Similarly, the network nodes 1410 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 1412 and / or with other network nodes or equipment in the telecommunication network 1402 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 1402.

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

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

[0264] As a whole, the communication system 1400 of Figure 14 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0265] In some examples, the telecommunication network 1402 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1402. For example, the telecommunications network 1402 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

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

[0267] In the example, the hub 1414 communicates with the access network 1404 to facilitate indirect communication between one or more UEs, e.g., UE 1412c and / or 1412d, and network nodes, e.g., network node 1410b. In some examples, the hub 1414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1414 may be a broadband router enabling access to the core network 1406 for the UEs. As another example, the hub 1414 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1410, or by executable code, script, process, or other instructions in the hub 1414. As another example, the hub 1414 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1414 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1414 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1414 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices. The hub 1414 may have a constant / persistent or intermittent connection to the network node 1410b. The hub 1414 may also allow for a different communication scheme and / or schedule between the hub 1414 and UEs (e.g., UE 1412c and / or 1412d) , and between the hub 1414 and the core network 1406. In other examples, the hub 1414 is connected to the core network 1406 and / or one or more UEs via a wired connection. Moreover, the hub 1414 may be configured to connect to an M2M service provider over the access network 1404 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1410 while still connected via the hub 1414 via a wired or wireless connection. In some embodiments, the hub 1414 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1410b. In other embodiments, the hub 1414 may be a non-dedicated hub -that is, a device which is capable of operating to route communications between the UEs and network node 1410b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0268] Figure 17 is a block diagram of a host 1700, which may be an embodiment of the host 1416 of Figure 14, in accordance with various aspects described herein. As used herein, the host 1700 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1700 may provide one or more services to one or more UEs.

[0269] The host 1700 includes processing circuitry 1702 that is operatively coupled via a bus 1704 to an input / output interface 1706, a network interface 1708, a power source 1710, and a memory 1712. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such that the descriptions thereof are generally applicable to the corresponding components of host 1700.

[0270] The memory 1712 may include one or more computer programs including one or more host application programs 1714 and data 1716, which may include user data, e.g., data generated by a UE for the host 1700 or data generated by the host 1700 for a UE. Embodiments of the host 1700 may utilize only a subset or all of the components shown. The host application programs 1714 may be implemented in a container-based architecture and may provide support for video codecs, (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, headsup display systems). The host application programs 1714 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1700 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 1714 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0271] Figure 19 shows a communication diagram of a host 1902 communicating via a network node 1904 with a UE 1906 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE, such as a UE 1412a of Figure QQ, network node, such as network node 1410a of Figure 14, and host, such as host 1416 of Figure 14 and / or host 1700 of Figure 17, discussed in the preceding paragraphs will now be described with reference to Figure 19.

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

[0273] The network node 1904 includes hardware enabling it to communicate with the host 1902 and UE 1906. The connection 1960 may be direct or pass through a core network (like core network 1406 of Figure 14) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0274] The UE 1906 includes hardware and software, which is stored in or accessible by UE 1906 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1906 with the support of the host 1902. In the host 1902, an executing host application may communicate with the executing client application via the OTT connection 1950 terminating at the UE 1906 and host 1902. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1950 may transfer both the request data and the user data. The UE's client application may interact with the userto generate the user data that it provides to the host application through the OTT connection 1950.

[0275] The OTT connection 1950 may extend via a connection 1960 between the host 1902 and the network node 1904 and via a wireless connection 1970 between the network node 1904 and the UE 1906 to provide the connection between the host 1902 and the UE 1906. The connection 1960 and wireless connection 1970, over which the OTT connection 1950 may be provided, have been drawn abstractly to illustrate the communication between the host 1902 and the UE 1906 via the network node 1904, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0276] As an example of transmitting data via the OTT connection 1950, in step 1908, the host 1902 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1906. In other embodiments, the user data is associated with a UE 1906 that shares data with the host 1902 without explicit human interaction. In step 1910, the host 1902 initiates a transmission carrying the user data towards the UE 1906. The host 1902 may initiate the transmission responsive to a request transmitted by the UE 1906. The request may be caused by human interaction with the UE 1906 or by operation of the client application executing on the UE 1906. The transmission may pass via the network node 1904, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1912, the network node 1904 transmits to the UE 1906 the user data that was carried in the transmission that the host 1902 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1914, the UE 1906 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1906 associated with the host application executed by the host 1902.

[0277] In some examples, the UE 1906 executes a client application which provides user data to the host 1902. The user data may be provided in reaction or response to the data received from the host 1902. Accordingly, in step 1916, the UE 1906 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 1906. Regardless of the specific manner in which the user data was provided, the UE 1906 initiates, in step 1918, transmission of the user data towards the host 1902 via the network node 1904. In step 1920, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1904 receives user data from the UE 1906 and initiates transmission of the received user data towards the host 1902. In step 1922, the host 1902 receives the user data carried in the transmission initiated by the UE 1906.

[0278] One or more of the various embodiments improve the performance of OTT services provided to the UE 1906 using the OTT connection 1950, in which the wireless connection 1970 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency, power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, improved content resolution, better responsiveness, and extended battery lifetime. In an example scenario, factory status information may be collected and analyzed by the host 1902. As another example, the host 1902 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1902 may collect and analyze real-time data to assist in controlling vehicle congestion, e.g., controlling traffic lights. As another example, the host 1902 may store surveillance video uploaded by a UE. As another example, the host 1902 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1902 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

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

[0280] Further numbered embodiments

[0281] 1 . A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform one or more of the actions described herein as performed by the network node 110.

[0282] 2. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0283] 3. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs one or more of the actions described herein as performed by the network node 110.

[0284] 4. The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.

[0285] 5. The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.

[0286] 6. A communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform one or more of the actions described herein as performed by the network node 110.

[0287] 7. The communication system of the previous embodiment, further comprising: the network node; and / or the user equipment.

[0288] 8. The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0289] 9. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform one or more of the actions described herein as performed by the network node 110.

[0290] 10. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0291] 11 . The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.

[0292] 12. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs one or more of the actions described herein as performed by the network node 110.

[0293] 13. The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

[0294] 14. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform one or more of the actions described herein as performed by the wireless device 130.

[0295] 15. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.

[0296] 16. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0297] 17. A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs one or more of the actions described herein as performed by the wireless device 130.

[0298] 18. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

[0299] 19. The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0300] 20. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to utilize user data; and a network interface configured to receipt of transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform one or more of the actions described herein as performed by the wireless device 130.

[0301] 21 . The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.

[0302] 22. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0303] 23. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs one or more of the actions described herein as performed by the wireless device 130. 24. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

[0304] 25. The method of the previous embodiments, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0305] REFERENCES

[0306] 1 . 3GPP TS 38.300 NR and NG-RAN Overall description; Stage-2 v16.1 .0

[0307] 2. 3GPP TS 38.321 Medium Access Control (MAC) protocol specification v16.1 .0

[0308] 3. 3GPP TS 38.304 User Equipment (UE) procedures in Idle mode and RRC Inactive state v16

[0309] 4. 3GPP TS 38.211 Physical channels and modulation

[0310] 5. 3GPP TS 38.213 Physical layer procedures for control

Claims

CLAIMS:

1. A method performed by a wireless device (130), the method being for handling a preamble, the wireless device (130) operating in a wireless communications network (100), and the method comprising:- sending (504) to a network node (110) operating in the wireless communications network (100), while the wireless device (130) is in inactive state, a preamble indicating a request for a time alignment, wherein the preamble indicates the preamble is reserved or dedicated for requesting time alignment in inactive state.

2. The method according to claim 1 , wherein the preamble further indicates that: a) the network node (110) is to, responsive to the sent preamble, send to the wireless device (130), a response comprising a time alignment value, and at least one of: i. the wireless device (130) is not to establish a connection with the network node (110), ii. the response is not to be followed by Radio Resource Control messages from the wireless device (130) to the network node (110) before using the time alignment value that is to be received from the network node (110), andHi. the network node (110) is to refrain from providing a Temporary Cell Radio Network Temporary Identifier, TC-RNTI, in the response.

3. The method according to any of claims 1-2, wherein the preamble is a Contention-free Random Access preamble.

4. The method according to any of claims 1-3, further comprising:- receiving (505) from the network node (110) and responsive to the sent preamble, a first response comprising a time alignment value.

5. The method according to claim 4, wherein the first response does not include a Temporary Cell Radio Network Temporary Identifier, TC-RNTI, and the first response further comprises at least one of:- a first identifier, the first identifier identifying preamble,- a grant having a size adapted to fit a second identifier, the second identifier identifying the wireless device (130), andthe grant having the size adapted to fit the second identifier, wherein the second identifier is smaller in size than an Inactive Radio Network Temporary Identifier, l-RNTI.

6. The method according to claims 4 and 5, further comprising:- sending (506), to the network node (110), responsive to the received first response, a first message comprising the second identifier of the wireless device (130), the second identifier being selected to be unique within a cell (120) served by the network node (110) where the wireless device (130) is located, and during a time period during which a random access procedure triggered by the sending (504) of the preamble is ongoing, and- receiving (507), from the network node (110), responsive to the sent first message, another message, the another message comprising the second identifier.

7. The method according to claim 6, wherein the first message comprises the second identifier scrambled with a Timing Advance, TA, -Radio Network Temporary Identifier.

8. The method according to any of claims 4-7, further comprising at least one of:- obtaining (501) a first indication indicating to use the preamble to request the time alignment when the wireless device (130) is in inactive state, and wherein the sending (504) of the preamble is based on the obtained first indication, and- using (508) the received time alignment value.

9. The method according any of claims 1-8, wherein the sending (504) of the preamble is responsive to one of:- receiving (503), from the network node (110), a second indication indicating to request the time alignment value, and- detecting (502) one or more conditions triggering the sending (504) of the preamble.

10. The method according to claim 9, wherein the one or more conditions comprise at least one of:- measuring a radio signal is equal to or exceeds a first threshold,- a first change in a position of the wireless device (130),- a second change in a strength of a downlink pathloss reference,- a third change in a current Reference Signal Received Power, RSRP, value with respect to a latest RSRP value as saved by the wireless device (130),- a fourth change in one or more reference signals,- a first expiration of a first timer,- a second expiration of an update timer of a time alignment, and- re-selection to a cell having a cell size larger than a second threshold.11 . The method according claim 10, wherein the wireless device (130) maintains time alignment by saving the latest RSRP value as a reference value, and periodically determining if the current RSRP value exceeds the reference value by more than a configured third threshold.

12. A method performed by a network node (110), the method being for handling a preamble, the network node (110) operating in a wireless communications network (100), and the method comprising:- receiving (603) from a wireless device (130) operating in the wireless communications network (100), while the wireless device (130) is in inactive state, a preamble indicating a request for a time alignment, wherein the preamble indicates the preamble is reserved or dedicated for requesting time alignment in inactive state.

13. The method according to claim 12, wherein the preamble further indicates that: a) the network node (110) is to, responsive to the received preamble, send to the wireless device (130), a response comprising a time alignment value, and at least one of: i. the wireless device (130) is not to establish a connection with the network node (110), ii. the response is not to be followed by Radio Resource Control messages from the wireless device (130) to the network node (110) before using the time alignment value that is to be received from the network node (110), andHi. the network node (110) is to refrain from providing a Temporary Cell Radio Network Temporary Identifier, TC-RNTI, in the response.

14. The method according to any of claims 12-13, wherein the preamble is a Contention- free Random Access preamble.

15. The method according to any of claims 12-14, further comprising:sending (604) to the wireless device (130) and responsive to the received preamble, a first response comprising a time alignment value.

16. The method according to claim 15, wherein the first response does not include a Temporary Cell Radio Network Temporary Identifier, TC-RNTI, and the first response further comprises at least one of:- a first identifier, the first identifier identifying the preamble,- a grant having a size adapted to fit a second identifier, the second identifier identifying the wireless device (130), and- the grant having the size adapted to fit the second identifier, wherein the second identifier is smaller in size than an Inactive Radio Network Temporary Identifier, l-RNTI.

17. The method according to claims 15 and 16, further comprising:- receiving (605), from the wireless device (130), responsive to the sent first response, a first message comprising the second identifier of the wireless device (130), the second identifier being selected to be unique within a cell (120) served by the network node (110) where the wireless device (130) is located, and during a time period during which a random access procedure triggered by the receiving (605) of the preamble is ongoing, and- sending (606), to the wireless device (130), responsive to the received first message, another message, the another message comprising the second identifier.

18. The method according to claim 17, wherein the first message comprises the second identifier scrambled with a Timing Advance, TA, -Radio Network Temporary Identifier.

19. The method according to any of claims 15-18, further comprising:- sending (601), to the wireless device (130), a first indication indicating to use the preamble to request the time alignment when the wireless device (130) is in inactive state, and wherein the receiving (603) of the preamble is based on the sent first indication.

20. The method according any of claims 12-19, wherein the receiving (603) of the preamble is responsive to one of:- sending (602), to the wireless device (130), a second indication indicating to request the time alignment value, andone or more conditions, detected by the wireless device (130) triggering the receiving (603) of the preamble.21 . The method according to claim 20, wherein the one or more conditions comprise at least one of:- measuring a radio signal is equal to or exceeds a first threshold,- a first change in a position of the wireless device (130),- a second change in a strength of a downlink pathloss reference,- a third change in a current Reference Signal Received Power, RSRP, value with respect to a latest RSRP value as saved by the wireless device (130),- a fourth change in one or more reference signals,- a first expiration of a first timer,- a second expiration of an update timer of a time alignment, and- re-selection to a cell having a cell size larger than a second threshold.

22. A wireless device (130), for handling a preamble, the wireless device (130) being configured to operate in a wireless communications network (100), and the wireless device (130) being further configured to:- send to a network node (110) configured to operate in the wireless communications network (100), while the wireless device (130) is in inactive state, a preamble configured to indicate a request for a time alignment, wherein the preamble is configured to indicate the preamble is configured to be reserved or dedicated for requesting time alignment in inactive state.

23. The wireless device (130) according to claim 22, wherein the preamble is configured to further indicate that: a) the network node (110) is to, responsive to the preamble configured to be sent, send to the wireless device (130), a response configured to comprise a time alignment value, and at least one of: i. the wireless device (130) is not to establish a connection with the network node (110), ii. the response is not to be followed by Radio Resource Control messages from the wireless device (130) to the network node (110) before using the time alignment value that is configured to be received from the network node (110), andHi. the network node (110) is to refrain from providing a Temporary Cell Radio Network Temporary Identifier, TC-RNTI, in the response.

24. The wireless device (130) according to any of claims 22-23, wherein the preamble is configured to be a Contention-free Random Access preamble.

25. The wireless device (130) according to any of claims 22-24, being further configured to:- receive from the network node (110) and responsive to the preamble configured to be sent, a first response configured to comprise a time alignment value.

26. The wireless device (130) according to claim 25, wherein the first response is configured to not include a Temporary Cell Radio Network Temporary Identifier, TC- RNTI, and the first response is further configured to comprise at least one of:- a first identifier, the first identifier being configured to identify the preamble,- a grant configured to have a size adapted to fit a second identifier, the second identifier being configured to identify the wireless device (130), and- the grant configured to have the size adapted to fit the second identifier, wherein the second identifier is configured to be smaller in size than an Inactive Radio Network Temporary Identifier, l-RNTI.

27. The wireless device (130) according to claims 25 and 26, being further configured to:- send, to the network node (110), responsive to the first response configured to be received, a first message configured to comprise the second identifier of the wireless device (130), the second identifier being configured to be selected to be unique within a cell (120) configured to be served by the network node (110) where the wireless device (130) is configured to be located, and during a time period during which a random access procedure configured to be triggered by the sending of the preamble is configured to be ongoing, and- receive, from the network node (110), responsive to the first message configured to be sent, another message, the another message being configured to comprise the second identifier.

28. The wireless device (130) according to claim 27, wherein the first message is configured to comprise the second identifier scrambled with a Timing Advance, TA,- Radio Network Temporary Identifier.

29. The wireless device (130) according to any of claims 25-28, being further configured to at least one of: obtain a first indication configured to indicate to use the preamble to request the time alignment when the wireless device (130) is in inactive state, and whereinthe sending of the preamble is configured to be based on the first indication configured to be obtained, and use the time alignment value configured to be received.

30. The wireless device (130) according any of claims 22-29, wherein the sending of the preamble is configured to be responsive to one of:- receiving, from the network node (110), a second indication configured to indicate to request the time alignment value, and- detecting one or more conditions triggering the sending of the preamble.

31. The wireless device (130) according to claim 30, wherein the one or more conditions are configured to comprise at least one of:- measuring a radio signal is equal to or exceeds a first threshold,- a first change in a position of the wireless device (130),- a second change in a strength of a downlink pathloss reference,- a third change in a current Reference Signal Received Power, RSRP, value with respect to a latest RSRP value as saved by the wireless device (130),- a fourth change in one or more reference signals,- a first expiration of a first timer,- a second expiration of an update timer of a time alignment, and- re-selection to a cell configured to have a cell size larger than a second threshold.

32. The wireless device (130) according claim 31 , wherein the wireless device (130) is configured to maintain time alignment by saving the latest RSRP value as a reference value, and periodically determining if the current RSRP value exceeds the reference value by more than a configured third threshold.

33. A network node (110), for handling a preamble, the network node (110) being configured to operate in a wireless communications network (100), and the network node (110) being further configured to:- receive from a wireless device (130) configured to operate in the wireless communications network (100), while the wireless device (130) is configured to be in inactive state, a preamble configured to indicate a request for a time alignment, wherein the preamble is configured to indicate the preamble is reserved or dedicated for requesting time alignment in inactive state.

34. The network node (110) according to claim 33, wherein the preamble is configured to further indicate that: a) the network node (110) is to, responsive to the preamble configured to be received, send to the wireless device (130), a response configured to comprise a time alignment value, and at least one of: i. the wireless device (130) is not to establish a connection with the network node (110), ii. the response is not to be followed by Radio Resource Control messages from the wireless device (130) to the network node (110) before using the time alignment value that is configured to be received from the network node (110), andHi. the network node (110) is to refrain from providing a Temporary Cell Radio Network Temporary Identifier, TC-RNTI, in the response.

35. The network node (110) according to any of claims 33-34, wherein the preamble is configured to be a Contention-free Random Access preamble.

36. The network node (110) according to any of claims 33-35, being further configured to:- send to the wireless device (130) and responsive to the preamble configured to be received, a first response configured to comprise a time alignment value.

37. The network node (110) according to claim 36, wherein the first response is configured to not include a Temporary Cell Radio Network Temporary Identifier, TC-RNTI, and the first response is further configured to comprise at least one of:- a first identifier, the first identifier being configured to identify the preamble,- a grant configured to have a size adapted to fit a second identifier, the second identifier being configured to identify the wireless device (130), and- the grant configured to have the size adapted to fit the second identifier, wherein the second identifier is configured to be smaller in size than an Inactive Radio Network Temporary Identifier, l-RNTI.

38. The network node (110) according to claims 36 and 37, being further configured to:- receive, from the wireless device (130), responsive to the first response configured to be sent, a first message configured to comprise the second identifier of the wireless device (130), the second identifier being configured to be selected to be unique within a cell (120) configured to be served by the network node (110) where the wireless device (130) is configured to be located, and during a time period during which a random access procedure configuredto be triggered by the receiving of the preamble is configured to be ongoing, and- send, to the wireless device (130), responsive to the first message configured to be received, another message, the another message being configured to comprise the second identifier.

39. The network node (110) according to claim 38, wherein the first message is configured to comprise the second identifier scrambled with a Timing Advance, TA, -Radio Network Temporary Identifier.

40. The network node (110) according to any of claims 36-39, being further configured to:- send, to the wireless device (130), a first indication configured to indicate to use the preamble to request the time alignment when the wireless device (130) is configured to be in inactive state, and wherein the receiving of the preamble is configured to be based on the first indication configured to be sent.41 . The network node (110) according any of claims 33-40, wherein the receiving of the preamble is configured to be responsive to one of:- the network node (110) sending, to the wireless device (130), a second indication configured to indicate to request the time alignment value, and- one or more conditions, configured to be detected by the wireless device (130) triggering the receiving of the preamble.

42. The network node (110) according to claim 41 , wherein the one or more conditions are configured to comprise at least one of:- measuring a radio signal is equal to or exceeds a first threshold,- a first change in a position of the wireless device (130),- a second change in a strength of a downlink pathloss reference,- a third change in a current Reference Signal Received Power, RSRP, value with respect to a latest RSRP value as saved by the wireless device (130),- a fourth change in one or more reference signals,- a first expiration of a first timer,- a second expiration of an update timer of a time alignment, and- re-selection to a cell configured to have a cell size larger than a second threshold.

Images