Network node, user equipment and methods therein for handling a small data transmission in a wireless communications network

Abstract

A method performed by a network node network node is provided. The method is for handling Small Data Transmissions between the network node and a UE in a wireless communications network is provided. The network node transmits (905) to the UE, an indication indicative of whether or not one or more SBFD resources can be utilized for at least part of Small Data Transmissions between the UE and the network node. In response to transmitting the indication to the UE, the network node communicates (906), the Small Data Transmission with the UE which Small Data Transmissions are in accordance with the information of the transmitted indication.

Description

[0001] NETWORK NODE, USER EQUIPMENT AND METHODS THEREIN FOR HANDLING A SMALL DATA TRANSMISSION IN A WIRELESS COMMUNICATIONS NETWORK

[0002] TECHNICAL FIELD

[0003] The present disclosure relates generally to a network node, a User Equipment (UE), and a method for handling a Small Data Transmission (SDT) in a wireless communications network. The present disclosure may further relate to a computer program product and a computer-readable storage medium.

[0004] BACKGROUND

[0005] In a typical wireless communications network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point, a Base Station (BS) or a radio base station (RBS), which in some networks may also be denoted, for example, a Base Station (BS), a NodeB, eNodeB (eNB), or gNodeB (gNB) as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on a radio frequency with the wireless devices within the range of the radio network node.

[0006] 3rd Generation Partnership Project (3GPP) is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet System (EPS) have been completed within the 3GPP. In 4G also called a Fourth Generation (4G) network, EPS is core network and E-UTRA is radio access network. In 5G, 5GC is core network, NR is radio access network. As a continued network evolution, the new release of 3GPP specifies a 5G network also referred to as 5G New Radio (NR) and 5G Core (5GC).

[0007] Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz.FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

[0008] Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. Fora wireless connection between a single user, such as UE, and a base station (BS), the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. The cell capacity can be increased linearly with respect to the number of antennas at the BS side. Due to that, more and more antennas are employed in BS. Such systems and / or related techniques are commonly referred to as massive MIMO.

[0009] FDD and TDD systems

[0010] Transmission and reception from a node, e.g. a terminal in a cellular system, can be multiplexed in the frequency domain or in the time domain (or combinations thereof).

[0011] Frequency Division Duplex (FDD) as illustrated to the left in Fig. 1 implies that downlink (DL) and uplink (UL) transmission take place in different, sufficiently separated, frequency bands. Time Division Duplex (TDD), as illustrated to the right in Fig 1, implies that downlink and uplink transmission take place in different, non-overlapping time slots. Thus, TDD can operate in unpaired spectrum, whereas FDD requires paired spectrum.

[0012] Typically, a structure of the transmitted signal in a communication system is organized in the form of a frame structure.

[0013] In more detail, the following two information elements (lEs) are defined in current specifications. The TDD pattern is typically configured with at least the first IE and optionally the 2nd IE:

[0014] • TDD-DL-UL-ConfigCommon (cell-specific)

[0015] • TDD-DL-UL-ConfigDedicated (UE-specific)

[0016] The first IE is cell specific (common to all UEs) and is provided by broadcast signaling. It provides the number of slots in the TDD pattern via a reference subcarrier spacing and a periodicity such that the S-slot pattern repeats every S slots. This IE allows for very flexible configuration of the pattern characterized as follows:

[0017] • A number of full downlink slots at the beginning of the pattern configured by the parameter nDownlinkSlots• A number of full uplink slots at the end of the pattern configured by the parameter nUplinkSlots

[0018] • A number of downlink (' D') symbols following the full downlink slots configured by the parameter nDownlinkSymbols

[0019] • A number of uplink (' U') symbols preceding the full downlink slots configured by the parameter nUplinkSlots

[0020] • If there is a gap between the last downlink symbol and the first uplink symbol, then all symbols in the gap are characterized as flexible ('F'). A symbol classified as 'F' can be used for downlink or uplink. A UE determines the direction in one of the following two ways:

[0021] o Detecting a DCI that schedules / triggers a DL signal / channel, e.g., PDSCH, CSI-RS or schedules / triggers an UL signal / channel, e.g. PUSCH, SRS, etc.

[0022] oBy dedicated (UE-specific) signaling of the IE TDD-DL-UL-ConfigDedicated. This parameter overrides some or all of the 'F' symbols in the pattern, thus providing a semi-static indication of whether a symbol is classified as 'D' or 'U'

[0023] • Optionally, a 2nd pattern that is concatenated to the first pattern can be configured as above. If a 2nd pattern is configured, the constraint is that the sum of the periodicities of the two patterns must evenly divide 20 ms.

[0024] Fig. 2 shows an exemplary TDD DL / UL pattern configured by TDD-DL-UL-ConfigCommon. It consists of 3 full ' D' slots, 1 full ' U' slot, with a mixed slot in between consisting of 4 ' D' symbols and 3 'U' symbols. The remaining 7 symbols in the mixed slot are classified as 'F.' In the TDD-DL-UL-ConfigCommon in Fig. 2, nrofDownlinkSlots =3, nrofUplinkSlots =1, nrofDownlinkSymbols =4, and nrofUplinkSymbols =3.

[0025] If a UE is not configured with TDD-DL-UL-ConfigDedicated, then the pattern at the top of the diagram is what it assumes. As stated above, the network can make use of the ' F' symbols flexibly, by scheduling / triggering either an uplink or a downlink signal / channel in a UE specific manner. This allows for very dynamic behavior: the direction is not known to the UE a priori; rather, the direction becomes known once the UE detects a DCI scheduling / triggering a particular DL or UL signal / channel.

[0026] In contrast, the DL / UL direction for some or all of the 'F' symbols in a particular slot can be provided to the UE in a semi-static manner by Radio Resource Control (RRC) configuring the UE with TDD-DL-UL-ConfigDedicated. The lower part of Figure 2 shows 3 exemplary configurations for overriding 'F' symbols in Slot 3. If the IE indicates 'allDownlink' or 'allUplink' for a particular slot (or slots), then all 'F' symbols in the slot are converted to either 'D' or 'U ,' respectively. If the IE indicates 'explicit,' then a number of symbols at the beginning of the slot and / or a number of symbols at the end of the slot are indicated as ' D' and 'U ,' respectively. In the example below, the first 7 and the last 5 are indicated as ' D' and 'U', which converts some of the 'F' symbols (but not all in this example) to ' D' and ' U .'Fig. 2 illustrates exemplary TDD DL / LIL pattern consisting of S = 5 slots. TDD-DL-UL-ConfigCommon configures the cell-specific pattern, and TDD-DL-UL-ConfigDedicated (if provided) UE-specifically configures the direction for some or all of the 'F' symbols in the cellspecific pattern.

[0027] The key behavior in the above is that the UE-specific IE TDD-DL-UL-ConfigDedicated can only override (i.e. , specify 'D' or 'U') for symbols that are configured as 'F' by the cellspecific IE TDD-DL-UL-ConfigCommon. In other words, a UE does not expect to have a ' D' symbol converted to ' U' or vice versa.

[0028] Subband full duplex

[0029] As described in the last section, in a conventional TDD system, entire carrier BW or all carriers in the same frequency band need to be utilizing the same DL transmission or UL reception directions. This is further illustrated in Fig. 3, which illustrates a conventional TDD carrier or carrier systems.

[0030] Fig. 4 illustrates subband full duplex (SBFD) systems. For Release (Rel)-18 evolution of the NR system, 3GPP has decided to study the technical feasibilities and potential benefits of SBFD systems. In such a system, a portion of a wide bandwidth carrier may be used for a different direction than that of the rest of the carrier. This is illustrated in the left-hand side of Fig. 4. That is, unlike a conventional TDD system as shown on the left-hand side of Fig. 3 where the entire bandwidth is used for DL transmission in the first three slots, the center portion of the SBFD carrier is used for UL reception while the rest of the carrier continues to be used for DL transmission as shown in the left-hand side of Fig. 4. Similarly, instead of utilizing all carriers for the same DL or UL directions in a conventional TDD system as shown in the right-hand side of Fig. 3, some carriers in the SBFD system can be used for a different direction than that of the other carriers as shown in the right-hand side of Fig. 4.

[0031] In the 3GPP Rel-18 study, the scope has been limited such that in SBFD operation, only gNBs transmit DL and receive UL simultaneously. An individual UE is scheduled in only one direction (DL or UL) at a time.

[0032] In RAN1 #117 RAN1 agreed to support two options for RACH configuration, a single RACH configuration and an additional RACH configuration. It was also agreed that a UE is not required to support both configurations, considering the scenarios for the different configurations are substantially different.

[0033] An agreement of RAN1 was to confirm the following working assumption: For UEs, such as SBFD-aware UEs, in Radio Resource Control (RRC) CONNECTED state, both Random Access Channel (RACH) configuration Option 1 with Alt 1-1, i.e., with the use one single RACH configuration, and only based on the existing parameters of the single RACH configuration; and RACH configuration Option 2, i.e., with the use two separate RACH configurations, including one legacy RACH configuration and one additional RACHconfiguration; are supported. Enabling both options at the same time for a UE is not supported.

[0034] - For Option 1 with Alt 1-1 , For Further Study (FFS) whether / how to reinterpret msg1-FrequencyStart in rach-ConfigCommon, RO validation rules and Synchronization Signal Block RACH Occasion (SSB-RO) mapping rules, etc.

[0035] - For Option 2, FFS the RO validation rules, SSB-RO mapping rules, whether all the parameters currently in rach-ConfigCommon are necessary to be included in the additional RACH configuration, etc.

[0036] An UE is not required to support both options.

[0037] The single RACH configuration i.e. , RACH configuration Option 1 with Alt 1-1 may provide larger RACH capacity and lower latency. The second SBFD RACH configuration i.e., RACH configuration Option 2 will provide increased coverage and range, and higher RACH capacity. Higher RACH capacity comes at the expense of increased overhead, in particular for requiring more ROs in already scarce UL resources, and adding even more ROs. In practice, a cell needs to provide both lower latency, and increased coverage and range, which is not reasonable.

[0038] Small data transmission in NR

[0039] As described in clause 18 of 3GPP TS 38.300 V 18.4.0, Small Data Transmission (SDT) is a procedure allowing data and / or signaling transmission while remaining in RRCJNACTIVE state, i.e. without transitioning to RRC_CONNECTED state. SDT is enabled on a radio bearer basis and can be initiated either by the UE in case of Mobile Originated SDT (MO-SDT) or by the network in case of Mobile Terminated SDT (MT-SDT). MO-SDT is initiated by the UE only if less than or equal to a configured amount of UL data awaits transmission across all radio bearers for which SDT is enabled, the DL RSRP is above a configured threshold, and a valid SDT resource is available as specified in clause 5.27.1 of 3GPP TS 38.321 V 18.4.0. MT-SDT is initiated by the network with an indication to the UE in a paging message when DL data awaits transmission for radio bearers configured for SDT; based on the indication, the UE initiates the MT-SDT only if the DL RSRP is above a configured threshold as specified in clause 5.27.1 of 3GPP TS 38.321 V 18.4.0. When MT-SDT is initiated by the UE, a resume cause indicating MT-SDT is included in the RRCResumeRequest / RRCResumeRequestl. Maximum duration the SDT procedure can last is dictated by a SDT failure detection timer that is configured by the network (see clause 6.2.2 of 3GPP TS 38.331 V 18.4.0. Network can enable MO-SDT, MT-SDT, or both in a cell.

[0040] SDT procedure is initiated with either a transmission over RACH (configured via system information) or over Type 1 CG resources (configured via dedicated signaling in RRCRelease). The SDT resources can be configured on initial BWP for both RACH and CG. RACH and Configured Grant (CG) resources for SDT can be configured on either or both ofNUL and SUL carriers. The CG resources for SDT are valid only within the PCell of the UE when the RRCRelease with suspend indication is received. CG resources are associated with one or multiple SSB(s). For RACH, the network can configure 2-step and / or 4-step Random Access (RA) resources for MO-SDT. When both 2-step and 4-step RA resources for MO-SDT are configured, the UE selects the RA type, e.g., according to clause 9.2.6 of 3GPP TS 38.331 V 18.4.0. If MT-SDT procedure is initiated over RACH, only the RACH resources not configured for SDT can be used by the UE. CFRA is not supported for SDT over RACH.

[0041] Once initiated, the SDT procedure is either:

[0042] - successfully completed after the UE is directed to RRCJDLE (via RRCRelease) or to continue in RRCJNACTIVE (via RRCRelease or RRCReject) or to RRC_CONNECTED (via RRCResume or RRCSetup); or

[0043] - unsuccessfully completed upon cell re-selection, expiry of the SDT failure detection timer, a MAC entity reaching a configured maximum PRACH preamble transmission threshold, an RLC entity reaching a configured maximum retransmission threshold, or integrity check failure while SDT procedure is ongoing, or expiry of SDT-specific timing alignment timer or configuredGrantTimer while SDT procedure is ongoing over CG and the UE has not received a response from the network after the initial PUSCH transmission.

[0044] Upon successful completion of the SDT procedure via an RRCRelease message including resumeindication, the UE triggers the initiation of RRC Resume procedure.

[0045] Upon unsuccessful completion of the SDT procedure, the UE transitions to RRCJDLE. For SDT, network should not send RRCReject in response to RRCResumeRequest / RRCResumeRequestl if DL data over any radio bearer configured for SDT is transmitted.

[0046] The initial PUSCH transmission during the SDT procedure includes at least the CCCH message. When using CG resources for initial SDT transmission, the UE can perform autonomous retransmission of the initial transmission if the UE does not receive confirmation from the network (dynamic UL grant or DL assignment) before a configured timer expires as specified in clause 5.4.1 of 3GPP TS 38.321 V 18.4.0. After the initial PUSCH transmission, subsequent transmissions are handled differently depending on the type of resource used to initiate the SDT procedure:

[0047] - When using CG resources, the network can schedule subsequent UL transmissions using dynamic grants or they can take place on the following CG resource occasions. The DL transmissions are scheduled using dynamic assignments. The UE can initiate subsequent UL transmission only after reception of confirmation (dynamic UL grant or DL assignment) for the initial PUSCH transmission from the network. For subsequent UL transmission, the UE cannot initiate re-transmission over a CG resource.- When using RACH resources, the network can schedule subsequent UL and DL transmissions using dynamic UL grants and DL assignments, respectively, after the completion of the RA procedure.

[0048] When SDT procedure is initiated, AS security is applied for all the radio bearers enabled for SDT as specified in clause 5.3.13.3 of 3GPP TS 38.331 V 18.4.0.

[0049] While the SDT procedure is ongoing, if data appears in a buffer of any radio bearer not enabled for SDT, the UE initiates a transmission of a non-SDT data arrival indication using U EAssistanceinformation message to the network and, if available, includes the resume cause.

[0050] While the SDT procedure is ongoing and RA procedure is triggered (e.g., upon UL data arrival as specified in clause 9.2.6 of 3GPP TS 38.331 V 18.4.0), only the RACH resources not configured for SDT can be used by the UE.

[0051] SDT procedure over CG resources can only be initiated with valid UL timing alignment. The UL timing alignment is maintained by the UE based on a SDT-specific timing alignment timer configured by the network via dedicated signalling and, for initial CG-SDT transmission, also by DL RSRP of configured number of highest ranked SSBs which are above a configured RSRP threshold. Upon expiry of the SDT-specific timing alignment timer, the CG resources are released while maintaining the CG resource configuration.

[0052] Logical channel restrictions configured by the network while in RRC_CONNECTED state and / or in RRCRelease message for radio bearers enabled for SDT, if any, are applied by the UE during SDT procedure.

[0053] The network may configure UE to apply Robust Header Compression (ROHC) continuity for SDT either when the UE initiates SDT in the PCell of the UE when the RRCRelease with suspend indication was received or when the UE initiates SDT in a cell of its RAN based notification area (RNA).

[0054] For SDT procedure over CG resources, the network may configure maximum time duration until the next valid CG occasion for initial CG-SDT transmission based on which the UE decides whether SDT procedure over CG resources can be initiated. The maximum time duration is configured per logical channel for MO-SDT and per UE for MT-SDT.

[0055] Support of SDT procedure over RACH

[0056] For SDT procedure over RACH, if the UE accesses a gNB other than the last serving gNB, the UL SDT data / signalling is buffered at the receiving gNB, and then the receiving gNB triggers the XnAP Retrieve UE Context procedure. The receiving gNB indicates SDT to the last serving gNB and the last serving gNB decides whether to relocate the UE context or not. Other SDT assistance information (e.g., single packet, multiple packets) may also be provided by the receiving gNB to help the decision of UE context relocation. If the UE is configured withthe clock quality control information, the last serving gNB performs full UE context relocation to enable the receiving gNB to provide clock quality information.

[0057] If the last serving gNB decides not to relocate the full UE context, it transfers a partial UE context containing SDT RLC context information necessary for the receiving gNB to handle SDT via the Partial UE Context Transfer procedure.

[0058] Then, in case SDT is used for user data over DRBs, UL / DL tunnels are established for DRBs configured for SDT between the receiving gNB and the last serving gNB. The PDCP PDU of UL / DL data is transferred over the tunnels, until the last serving gNB terminates the SDT session and directs the UE to continue in RRCJNACTIVE by sending the RRCRelease message.

[0059] In case SDT is used for signalling, Signaling Radio Bearer (SRB) Packet Data Convergence Protocol (PDCP) Protocol Data Units (PDUs) are transferred between the receiving gNB and the last serving gNB via the XnAP RRC Transfer procedure, until the last serving gNB terminates the SDT session and directs the UE to continue in RRCJNACTIVE by sending the RRCRelease message.

[0060] During the SDT session, in case the receiving gNB detects that no more packets are to be transmitted, or radio link problem is detected, the receiving gNB may also request to terminate the SDT session to the last serving gNB via the UE Context Retrieve Confirmation procedure.

[0061] SDT with UE context relocation

[0062] The overall procedure for SDT procedure over RACH with UE context relocation is illustrated in Fig. 5. Fig. 5 illustrates RA-based SDT with UE context relocation of 3GPP TS 38.300 V18.4.0.

[0063] 1. The UE sends an RRCResumeRequest as well as UL SDT data and / or UL SDT signalling to the Receiving gNB.

[0064] 2. The Receiving gNB identifies the Last Serving gNB using the l-RNTI and retrieves the UE context by means of Xn-AP Retrieve UE Context procedure. The Receiving gNB indicates that the UE request is for an SDT and may also provide SDT assistance information (e.g., single packet, multiple packets).

[0065] 3. The Last Serving gNB decides to relocate UE context and responds with the RETRIEVE UE CONTEXT RESPONSE message. The UL SDT data, if any, is delivered from the Receiving gNB to the UPF. In case that the Last Serving gNB has requested the AMF for CN Buffering as part of step 0 for the UE in RRC INACTIVE state with eDRX cycle longer than 10.24 seconds, reachability of the UE can be indicated to the AMF by the last serving gNB using the MT Communication Handling procedure as described in TS 23.501 [3] and TS 38.413

[0026] , otherwise, the AMF considers that the UE is reachable (i.e. , the MT Communicating Handing is deactivated) upon step 5.4-6. The Receiving gNB decides to keep UE in RRCJNACTIVE state for SDT. If loss of DL user data buffered in the Last Serving gNB shall be prevented, the Receiving gNB provides forwarding addresses via the Xn-ll ADDRESS INDICATION message. The Receiving gNB also initiates NGAP Path Switch Request procedure to establish a NG UE-associated signalling connection to the AMF. After the Path Switch Request procedure, the buffered UL NAS PDU, if any, is delivered from the Receiving gNB to the AMF. And then, the subsequent LIL / DL SDT data and / or signalling are transferred between UE and core network via the Receiving gNB.

[0066] NOTE 1 : If the UP policy received from the Last Serving gNB is different from that received in the PATH SWITCH REQUEST ACKNOWLEDGE message, the Receiving gNB may either send the UE back to RRCJDLE or move the UE to RRC_CONNECTED to update the security configuration.

[0067] 7. After the SDT transmission is terminated, the Receiving gNB generates and sends the RRCRelease message including the suspend indication to the UE to terminate the SDT procedure and continue in RRCJNACTIVE state.

[0068] NOTE 2: In case DL non-SDT data or DL non-SDT signalling arrives, or the UE assistance information (i.e. UL non-SDT data arrival indication) is received from the UE, the Receiving gNB may decide to directly send the UE to RRC_CONNECTED state by sending the RRCResume message.

[0069] NOTE 3:The Receiving gNB may decide to directly send the UE to RRC_CONNECTED state by sending the RRCResume message based on (e.g. large size of) DL SDT data or DL SDT signalling.

[0070] NOTE 4:The Receiving gNB may decide to directly send the UE to RRC_CONNECTED state by sending the RRCResume message based on the BSR received from the UE in case of uplink SDT data exceeding the data size threshold.

[0071] NOTE 5:The Receiving gNB may send the NGAP MT Communication Handling Request message to the AMF to trigger CN buffering when the UE is put again into RRCJNACTIVE state with eDRX cycle longer than 10.24 seconds.

[0072] 8. The Receiving gNB indicates to the Last Serving gNB to remove the UE context by sending the XnAP UE CONTEXT RELEASE message. The XnAP UE CONTEXT RELEASE message can be sent after step 6.

[0073] SDT without UE context relocation

[0074] The overall procedure for SDT procedure over RACH without UE context relocation is illustrated in the Fig. 6. Fig. 6 illustrates RA-based SDT without UE context relocation of 3GPP TS 38.300 V18.4.0

[0075] 1 / 2. The steps 1 / 2 are as defined in steps 1 / 2 in Fig. 5.3. The last serving gNB decides not to relocate the full UE context for SDT. In case that the Last Serving gNB has requested AMF for CN Buffering as part of step 0 for the UE in RRC INACTIVE state with eDRX cycle longer than 10.24 seconds, reachability of the UE is indicated to the AMF by the last serving gNB using the MT Communication Handling procedure as described in 5GPP TS 23.501 and 3GPP TS 38.413.

[0076] 4. The last serving gNB transfers a partial UE context including the SDT related RLC context.

[0077] 5. The receiving gNB acknowledges receiving the partial UE context and provides associated DL TNL address. The UE context is kept at the last serving gNB and the SDT related RLC context is established at the receiving gNB. Then UL / DL GTP-U tunnels are established for DRBs configured for SDT, if any, and the UL SDT data and / or signalling, if any, are forwarded to the last serving gNB, and then delivered to the core network.

[0078] NOTE 1 :The DL signalling from the last serving gNB, if any, is forwarded to the receiving gNB via the RRC TRANSFER message, for which the receiving gNB delivers it to the UE.

[0079] NOTE 1a: In case DL non-SDT data or DL non-SDT signalling arrives, or UE assistance information (i.e. UL non-SDT data arrival indication) is received from the UE, the last serving gNB terminates the SDT procedure by sending the RRCRelease message.

[0080] NOTE 1b: The last serving gNB may terminate the SDT procedure by sending the RRCRelease message based on (e.g. large size of) DL SDT data or DL SDT signalling.

[0081] 6. The receiving gNB detects the end of SDT session and sends the RETRIEVE UE CONTEXT CONFIRM message including whether this is a "normal" end of SDT transaction or a radio link problem, or large SDT volume from BSR.

[0082] 7. Upon receiving the RETRIEVE UE CONTEXT CONFIRM message and deciding to terminate the SDT, the last serving gNB responds to the receiving gNB with the RETRIEVE UE CONTEXT FAILURE message including an encapsulated RRCRelease message. The receiving gNB shall release the established partial UE context.

[0083] 8. The receiving gNB sends the RRCRelease message to the UE.

[0084] NOTE 5:The last serving gNB may terminate the SDT procedure by sending the RRCRelease message upon receiving the indication about large uplink SDT data from the BSR from the receiving gNB in step 6.

[0085] NOTE 6:The Last Serving gNB may send the NGAP MT Communication Handling Request message to the AMF to trigger CN buffering when the UE is put again into RRC NACTIVE state with eDRX cycle longer than 10.24 seconds.

[0086] 9. The UE moves to RRCJNACTIVE state if the suspend indication is included in the RRCRelease message, or the UE may initiate RRC resume procedure to transition to RRC_CONNECTED state if the resume indication is included in the RRCRelease message. Or else, the UE moves to RRC DLE state.MT-SDT with / without UE context relocation

[0087] The overall procedure for MT-SDT procedure with / without UE context relocation is illustrated in Fig. 7. Fig. 7 illustrates MT-SDT with / without UE context relocation of 3GPP TS 38.300 V18.4.0.

[0088] 1. DL user data and / or DL NAS signalling are received at the Last Serving gNB for the UE in RRCJNACTIVE state, or RAN Paging request message is received at the Last Serving gNB for the UE in RRCJNACTIVE state with long eDRX(cycle) beyond 10.24 seconds.

[0089] 2. The Last Serving gNB may send MT-SDT information to the neighbour gNBs within the RNA, via XnAP RAN PAGING message.

[0090] 3. The gNB that receives MT-SDT information within the RNA, takes into account the MT-SDT information received in the XnAP RAN PAGING message to decide whether to trigger MT-SDT Paging. The gNB which ultimately reaches the UE via the Uu Paging becomes the Receiving gNB.

[0091] NOTE 1 : In case that the Receiving gNB decides not to trigger MT-SDT paging, the above step 3 and subsequent steps are the same as Figure 9.2.2.4.2 of 3GPP TS 38.300 V18.4.0. from step 3.

[0092] 4 / 5. The UE may decide to initiate MT-SDT procedure and in this case sends an RRCResumeRequest message with an MT-SDT resume cause to the Receiving gNB.

[0093] 6. The following steps are the same as Fig. 5 or 6from step 2, except that the first SDT user data and / or NAS signalling is DL SDT data and / or DL SDT NAS signalling.

[0094] NOTE 2: In case DL non-SDT data or DL non-SDT signalling has arrived between step 2 and step 6, the Last Serving gNB should relocate the UE context to the Receiving gNB and forward the received data to the Receiving gNB.

[0095] Hence, there is a strive to improve efficiency in Small Data Transmissions.

[0096] As used herein, a SBFD aware UE may mean a UE which is capable of operating in a cell configured with SBFD feature such as that the cell and / or a network node serving the cell, e.g., a gNB, may at least partly transmit DL and receive UL simultaneously in SBFD slots and / or symbols within a carrier. A SBFD aware UE may be aware of SBFD configurations, e.g., predefined or previously configured, such that the UE has information of which slots and / or symbols are SBFD capable, e.g., where SBFD is possible, which slots and / or symbols may also be referred to as SBFD slots / symbols. However, a SBFD aware UE may not necessarily support SBFD itself. A SBFD aware UE may or may not support full duplex operation. A SBFD aware UE may be capable of operating in a cell configured with legacy DL / UL allocation, i.e., non-SBFD slots / symbols, and to be enabled to switch betweencommunicating using SBFD and communicating using legacy DL / LIL allocation, i.e., non-SBFD.

[0097] The term legacy as used herein may mean symbols and / or slots allocated using any non-SBFD feature, e.g., using TDD.

[0098] As used herein, the term “cell” may identify a location and / or coverage on which a UE is located. However, the term “cell” may also be exchanged without any loss of meaning with the terms “radio resources”, “beams”, “TCI state”, or “Tracking reference signal (TRS)”. This is just to clarify that the subject matter of embodiments herein does not target specifically a scenario where there is a cell, but rather when a UE uses a set of source radio resources and need to switch to a target set of radio resources. In such a case, radio resource can also identify a set of configurations, field, parameters, or ASN.1 structures or lEs.

[0099] Embodiments herein are applicable to any suitable UE which is SBFD aware and capable of communicating using Small Data Transmissions.

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

[0101] For SBFD, in particular for Release 19 (Rel-19), an UE such as an SBFD aware UE in a cell capable of SBFD operation may be able to perform UL transmissions in both non SBFD symbols, e.g., configured as UL or flexible by TDD-DL-UL common, and in SBFD slots / symbols, e.g., configured as DL by TDD-DL-UL common.

[0102] An USBFD aware UE may be configured with Small Data Transmissions in a cell operating with SBFD. The UE may be able to perform Small Data Transmissions when the UE transits to RRCJNACTIVE from RRC_CONNECTED. In such scenario, there are several issues to be addressed in order to support Small Data Transmissions for the SBFD aware UE in the cell operating SBFD.

[0103] Issue 1 - configured grant for Small Data Transmissions transmission (CG-Small Data Transmissionsjresources are allocated to the UE by the gNB via e.g., RRCRelease message when the UE transits to RRCJNACTIVE from RRC_CONNECTED. A question arises in how does the UE select slot / symbol type, e.g., UL slot / symbol and / or SBFD slot / symbol, for use when transmitting the Small Data Transmissions using CG-Small Data Transmissions resource.

[0104] The SBFD aware UE with Small Data Transmissions data in UL can transit from RRCJnactive to RRCJnactive CM connected. According to some embodiments herein, without waiting for the UL slot based on the TDD pattern, instead the SBFD aware UE can transmit within a SBFD slot either in the UL subband or in the UL slot.

[0105] Issue 2 - The UE may move to another gNB / cell when the UE is in RRCJNACTIVE. Upon trigger of Small Data Transmissions, a question arises in how does the new gNB, also referred to as a receiving gNB or receiving node, gain information of whether the UE is SBFDaware, such that, if the receiving gNB is operating SBFD, can assign / allocate SBFD resources to the UE for its Small Data Transmissions.

[0106] An Inactive state mobility for the SBFD aware UE can happens in several scenarios: Option 1: transit from SBFD cell to SBFD cell.

[0107] Option 2: transit from non-SBFD cell to SBFD cell.

[0108] Option 3: transit from SBFD cell to non-SBFD cell

[0109] Option 4: transit from non-SBFD cell to non-SBFD cell.

[0110] Small Data Transmissions benefits an SBFD aware UE only when SBFD aware UE moves to the SBFD capable gNB, here for issue 2 only applicable when the receiving gNB is SBFD capable. For issue 2, there may be other means to address the issue, e.g., the UE sends an indication i.e. , whether the UE is SBFD aware via Msg1 or Msg3 during the RACH procedure initiated for Small Data Transmissions. However, Msg1 based option may require a PRACH preamble resources to be split for different features, e.g., RedCap, Small Data Transmissions etc for early indication purpose, which would result into fragmentation of PRACH preambles, leading to RACH performance drop. Msg3 based option may require an indication to be included in a MAC sub header or a MAC CE, which means either MAC header format needs to be updated or additional / separate logical channel identities (LCH IDs) need to be defined for the indication. Such an approach may result in large changes to standards or specifications, and it has therefore been concluded as part of developing embodiments herein that it is therefore more suitable to find a solution by other options e.g., a network based option. Another means may be to rely on an RO type which the UE used, the gNB may identify whether the UE is SBFD aware. However, this option may depend on the RACH configuration, If the configurations assign the UE with different legacy and SBFD RO positions, the serving cell may accordingly determine whether the UE is SBFD-aware. The solution may then be invalid if a legacy RO position is assigned to the SBFD-aware UE. Legacy RO in this context may mean only UL slot according to a TDD pattern. SBFD RO slot may mean a DL slot where a UE uses a portion of DL bandwidth to perform UL transmission and / or where a network node such as a gNB may perform both DL transmissions and UL receptions in the same slot, using different bandwidth portion..

[0111] SUMMARY

[0112] Therefore, as part of developing embodiments herein, it has been found necessary to study the above issues and develop corresponding solutions.

[0113] An object of embodiments herein is to improve handling of Small Data Transmissions in a wireless communications network.According to a first aspect of embodiments herein the object is achieved by a method performed by a network node network node for handling Small Data Transmissions between the network node and a UE in a wireless communications network is provided. The network node transmits to the UE, an indication indicative of whether or not one or more SBFD resources can be utilized for at least part of Small Data Transmissions between the UE and the network node. In response to transmitting the indication to the UE, the network node communicates (906), the Small Data Transmission with the UE which Small Data Transmissions are in accordance with the information of the transmitted indication.

[0114] According to a second aspect of embodiments herein the object is achieved by a method performed by a UE for handling Small Data Transmissions between a network node and the UE in a wireless communications network is provided. The UE receives from the network node, an indication indicative of whether or not one or more SBFD resources can be utilized for at least part of Small Data Transmissions between the UE and the network node. In response to receiving the indication to the UE, the UE communicates the Small Data Transmission with the network node. The Small Data Transmissions are in accordance with the information of the received indication.

[0115] According to a third aspect of embodiments herein the object is achieved by a network node configured to handle Small Data Transmissions between the network node and a UE in a wireless communications network is provided. The network node is configured to transmit to the UE, an indication indicative of whether or not one or more SBFD resources can be utilized for at least part of Small Data Transmissions between the UE and the network node. The network node is further configured to, in response to transmitting the indication to the UE, communicating the Small Data Transmission with the UE which Small Data Transmissions are in accordance with the information of the transmitted indication.

[0116] According to a fourth aspect of embodiments herein the object is achieved by a UE configured to handle Small Data Transmissions between a network node and the UE in a wireless communications network is provided. The UE is configured to receive from the network node, an indication indicative of whether or not one or more SBFD resources can be utilized for at least part of Small Data Transmissions between the UE and the network node. The UE is further configured to, in response to receiving the indication to the UE, communicate the Small Data Transmission with the network node. The Small Data Transmissions are in accordance with the information of the received indication.

[0117] In some particular embodiments, the indication may indicate whether or not one or more SBFD resources shall be utilized for at least part of Small Data Transmissions between the UE and the network node.

[0118] According to further aspects, computer program products comprising instructions, which,when executed on at least one processor, cause the at least one processor to carry out the method of the first and second aspects are provided.

[0119] According to further aspects, computer-readable storage mediums, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the first and second aspects are provided.

[0120] Additionally or alternatively, the object is achieved by any or both of:

[0121] - a gNB indication, e.g., the indicator above, transmitted to an SBFD aware UE, e.g., the UE above, via dedicated RRC signaling, MAC CE or L1 signaling, e.g., DCI on PDCCH, where the indication indicates whether to use UL transmission occasions in SBFD slot / symbol and / or UL slot / symbol for the CG-SDT transmission; and

[0122] - a gNB indication, e.g., the indicator above, transmitted to the SBFD aware UE, e.g., the UE above, for Random Access SDT (RA-SDT) resources, based on information provided from other gNBs.

[0123] Since, indication is provided to the UE, indicative of whether or not one or more SBFD resources can be utilized for at least part of Small Data Transmissions between the UE and the network node, the UE can efficiently communicate using Small Data Transmissions, and where applicable and suitable, utilized SBFD, thereby improving efficiency of the wireless communications network.

[0124] Embodiments herein may improve on efficiency of the wireless communications network by further exploring use of SBFD, which may be more efficient than TDD communication. Embodiments herein may benefit UEs, such as SBFD aware UEs, for connected mode UL coverage enhancement, but may also provide benefits for Inactive mode SDT transmission such as for both or either of CG-SDT and RA-based SDT.

[0125] BRIEF DESCRIPTION OF THE DRAWINGS

[0126] Examples of embodiments herein are described in more detail with reference to attached drawings in which:

[0127] Figure 1 is a schematic block diagram illustrating Prior Art.

[0128] Figure 2 is a schematic block diagram illustrating Prior Art.

[0129] Figure 3 is a schematic block diagram illustrating Prior Art.

[0130] Figure 4 is a schematic block diagram illustrating Prior Art.

[0131] Figure 5 is a sequence diagram illustrating Prior Art.

[0132] Figure 6 is a sequence diagram illustrating Prior Art.

[0133] Figure 7 is a sequence diagram illustrating Prior Art.

[0134] Figure 8 is a schematic block diagram illustrating embodiments of a communications

[0135] network.Figure 9 is a flowchart depicting an embodiment of a method in a network node.

[0136] Figure 10 is a flowchart depicting an embodiment of a method in a UE.

[0137] Figure 11 is a sequence diagram illustrating embodiments herein.

[0138] Figure 12 is a sequence diagram illustrating embodiments herein.

[0139] Figure 13 is a sequence diagram illustrating embodiments herein.

[0140] Figure 14 is a generalized block diagram of embodiments of a network node.

[0141] Figure 15 is a generalized block diagram of embodiments of a UE.

[0142] Figure 16 schematically illustrates embodiments of a communication system.

[0143] Figure 17 schematically illustrates embodiments of a communication system.

[0144] Figure 18 is a generalized block diagram of embodiments of a wireless device.

[0145] Figure 19 is a generalized block diagram of embodiments of a network node.

[0146] Figure 20 is a generalized block diagram of embodiments of a virtualization environment.

[0147] DETAILED DESCRIPTION

[0148] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0149] Embodiments herein relate to wireless communications networks in general, and are particularly applicable for telecommunications networks. Fig. 8 is a schematic overview depicting a wireless communications network 100. While some particular aspects are discussed below, the wireless communications network 100 may be any suitable network, even a network using wired technology. The wireless communications network 100 may comprise one or more RANs and one or more CNs. The wireless communications network 100 may be a 5G system, or a newer system supporting similar and / or different functionality, for example, a Sixth Generation (6G) system. In some examples, the wireless communications network may support, additionally or alternatively, a Long-Term Evolution (LTE) network and may support other technologies such as LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LTE Half-Duplex Frequency Division Duplex (HD-FDD), and LTE operating in an unlicensed band. The wireless communications network 100 may also support other technologies, such as Wideband Code Division Multiple Access (WCDMA), Universal Mobile Telecommunications System Terrestrial Radio Access (UTRA) TDD, Global System for Mobile communications (GSM) network, GSM / Enhanced Data Rate for GSM Evolution (EDGE) Radio Access Network (GERAN) network, Ultra-Mobile Broadband (UMB), EDGE network, network comprising any combination of Radio Access Technologies (RATs) such as e.g. Multi-Standard Radio (MSR) base stations, multi-RAT base stations etc., any 3rd Generation Partnership Project (3GPP) cellular network, Wireless Local Area Network / s (WLAN) or WiFi network / s, Worldwide Interoperability for Microwave Access (WiMax), IEEE903.15.4-based low-power short-range networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LowPAN), Zigbee, Z-Wave, Bluetooth Low Energy (BLE), or any cellular network or system. The telecommunications system may for example support a Low Power Wide Area Network (LPWAN). LPWAN technologies may comprise Long Range physical layer protocol (LoRa), Haystack, SigFox, LTE-M, and Narrow-Band loT (NB-loT).

[0150] A number of radio network nodes may operate in the wireless communications network 100. Radio network nodes may provide radio coverage in a number of cells which may also be referred to as a beam or a beam group of beams. Radio network nodes as used herein may be any of a NG-RAN node, a transmission and reception point e.g. a base station, a radio access network node such as a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), a gNB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a network controlled repeater or any other network unit capable of communicating with a wireless device within the service area served by the radio network node depending e.g. on the first radio access technology and terminology used. Radio network nodes as used herein may be referred to as serving radio network nodes and communicates with one or more UEs with Downlink (DL) transmissions and Uplink (UL) transmissions from the one or more UEs.

[0151] In some examples, the wireless communications network 100 may comprise an access network, such as a radio access network (RAN), and / or a core network (CN), which may include one or more core network nodes. The access network may include one or more access network nodes, e.g., which may be radio network nodes as described above, or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points.

[0152] Moreover, as will be appreciated by those of skill in the art, a radio network node or a core network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that radio network nodes and / or core network nodes may include disaggregated implementations or portions thereof.

[0153] In some embodiments, the wireless communications network may include one or more Open-RAN (ORAN) network nodes. An ORAN network node may be understood as a node in the telecommunications network that may support an ORAN specification, e.g., a specification published by the O-RAN Alliance, or any similar organization, and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunications network, including one or more network nodes and / or core network nodes.Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (0-Dll), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller, near-real time or non-real time, hosting software or software plug-ins, such as a near-real time control application, e.g., xApp, or a non-real time control application, e.g., rApp, or any combination thereof, the adjective “open” designating support of an ORAN specification. ORAN network nodes may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment, in which one or more network functions may be virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies.

[0154] Radio network nodes as used herein may facilitate direct or indirect connection of one or more UEs such as by connecting the one or more UEs to the ON over one or more wireless connections or wired connections.

[0155] In the wireless communications network 100, one or more wireless devices operate, such as one or more UEs, in particular a UE 120. The one or more UEs such as the UE 120 may respectively also be known as a e.g., device, wireless device, mobile terminal, wireless terminal and / or mobile station, mobile telephone, cellular telephone, or laptop with wireless capability, an Internet of Things (loT) device, or a Customer Premises Equipment (CPE), just to mention some further examples. The one or more UEs may for example be, portable, pocket-storable, hand-held, computer-comprised, or a vehicle-mounted mobile device, enabled to communicate voice and / or data, via a RAN, with another entity, such as a server, a laptop, a Personal Digital Assistant (PDA), or a tablet, a Machine-to-Machine (M2M) device, an Internet of Things (loT) device, e.g., a sensor or a camera, a device equipped with a wireless interface, such as a printer or a file storage device, modem, Laptop Embedded Equipped (LEE), Laptop Mounted Equipment (LME), USB dongles, CPE or any other radio network unit capable of communicating over a radio link in the wireless communications network 100. The one or more UEs such as the UE 120 may be wireless, i.e. , it may be enabled to communicate wirelessly in the wireless communications network 100 and, in some particular examples, may be able support transmission using beamforming. The communication may be performed e.g., between two devices, between a device and a radio network node, and / or between a device and a server. The communication may be performed e.g., via a RAN and possibly one or more CNs, comprised, respectively, within the wireless communications network 100.In the wireless communications network 100 one or more network nodes operate such as the network node 110. The network node 110 may in particular be a radio network node as described above, such as a gNB or any 6G-corresponding network node, but may also be a CN node, ORAN node, or even a UE.

[0156] The network node 110 and the UE 120 may communicate over a cell 50. As indicated above, the cell 50 may, besides representing a cell, may also represent any other suitable radio communication between the UE 120 and the network node 110, in particular where Small Data Transmissions and SBFD may be applicable.

[0157] Additionally, in some embodiments herein, a last serving network node 111, may represent a network node that most recently served, e.g., was in communication with, the UE 120. The last serving network node 111 may in particular be a radio network node as described above, such as a gNB or any 6G-corresponding network node, but may also be a CN node, ORAN node, or even a UE.

[0158] Methods herein may be performed by the network node 110 and / or in the UE 120. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in a cloud resource 190 such as a server as shown in Fig. 8, may be used for performing or partly performing the methods herein.

[0159] The above-described issue is addressed in a number of embodiments, some of which may be seen as alternatives, while some may be used in combination. Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. 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.

[0160] Fig. 9 illustrates example embodiments of a method performed by the network node 110 for handling Small Data Transmissions between the network node 110 and the UE 120 in the wireless communications network 100. The method may comprise any one or more of the following Actions. Optional Actions may be represented by dashed boxes in Fig. 9.

[0161] In Actions below, Small Data Transmission (SDT) may be discussed in plural to indicate that one or more Small Data Transmissions may take place. However, the below Actions are also applicable to only a singular Small Data Transmission.

[0162] Action 901. In some embodiments, the network node 110 transmits a paging message to the UE 120. The paging message may be arranged to trigger the UE 120 to transmit an RRC resume request message to the network node 110.

[0163] Action 902. In some embodiments, the network node 110 receives an RRC resume request message from the UE 120.Action 903. In some embodiments the network node 110 obtains capability information indicative of whether or not the UE 120 is capable of communicating in a cell configured to at least partly provide communication using SBFD resources.

[0164] Obtaining the capability information may be performed in response to detecting that the network node 110 was not the last serving network node 111 for the UE 120.

[0165] Obtaining the capability information may comprise receiving the capability information from the last serving network node 111 of the UE 120.

[0166] Obtaining the capability information may comprise retrieving a partial or full UE context of the UE 120 from the last serving network node 111 of the UE 120.

[0167] The capability information may be based on the partial or full UE context, e.g., established on a basis thereof.

[0168] Action 904. In some embodiments the network node 110 allocates the one or more SBFD resources for the UE 120 based on the capability information.

[0169] Action 905. The network node 110 transmits to the UE 120, an indication indicative of whether or not one or more SBFD resources can be utilized for at least part of Small Data Transmissions between the UE 120 and the network node 110.

[0170] The indication may be indicative of one or more resources which can be utilized for at least part of the Small Data Transmissions. In other words, the indication may indicate just the type of resources that can or shall be used, e.g., SBFD or not, and optionally, the indication may indicate, directly or indirectly, which one or more resources that can or shall be used, such as the one or more SBFD resources.

[0171] The indication may be indicative of one or more resources which shall be utilized for at least part of the Small Data Transmissions.

[0172] The indication may be indicative of whether or not at least one of the one or more SBFD resources shall be utilized for at least part of the Small Data Transmissions.

[0173] As used herein at least part of the Small Data Transmissions may be all of the Small Data Transmissions or for a limited part of the Small Data Transmissions between the UE 120 and the network node 110.

[0174] In some embodiments, the Small Data Transmissions are arranged for utilizing CG-SDT. Additionally or alternatively, the Small Data Transmissions are arranged for utilizing RA-SDT. In other words, Small Data Transmissions of embodiments herein may relate to CG-SDT and / or RA-SDT. Accordingly CG-SDT and / or RA-SDT may, based on embodiments herein, be enabled to utilize SBFD.

[0175] Transmitting the indication to the UE 120 may be performed in response to receiving the RRC resume request message from the UE 120, e.g., as in Action 902.

[0176] In some embodiments, the indication is based on the capability information, e.g., as obtained in Action 903.In some embodiments herein, the one or more SBFD resources comprise one or more time domain resources and / or wherein the one or more SBFD resources comprise one or more frequency domain resources.

[0177] Action 906. In some embodiments, the network node 110 communicates Small Data Transmissions with the UE 120. Communicating as used herein may mean receiving and / or transmitting, in particular receiving. The communication may be performed in response to transmitting the indication to the UE 120. The Small Data Transmissions may be in accordance with the information of the transmitted indication.

[0178] Fig. 10 illustrates example embodiments of a method performed by the UE 120 for handling Small Data Transmissions between the network node 110 and the UE 120 in the wireless communications network 100. The method may comprise any one or more of the following Actions. Optional Actions may be represented by dashed boxes in Fig. 10. Features of above mentioned Actions of Fig. 9 may apply to the below mentioned Actions, and vice versa.

[0179] In Actions below, Small Data Transmission (SDT) may be discussed in plural to indicate that one or more Small Data Transmissions may take place. However, the below Actions below are also applicable to only a singular Small Data Transmission.

[0180] Action 1001. In some embodiments, the UE 120 receives a paging message from the network node 110.

[0181] Action 1002. In some embodiments, the UE 120 transmits an RRC resume request message to the network node 110.

[0182] The paging message of Action 1001 may trigger the UE 120 to transmit the RRC resume request message to the network node 110.

[0183] Action 1003. The UE 120 receives an indication indicative of whether or not one or more SBFD resources can be utilized for at least part of Small Data Transmissions between the UE 120 and the network node 110, e.g., as transmitted by Action 905.

[0184] The indication may be indicative of one or more resources which can be utilized for at least part of the Small Data Transmissions.

[0185] The indication may be indicative of one or more resources which shall be utilized for at least part of the Small Data Transmissions.

[0186] The indication may be indicative of whether or not at least one of the one or more SBFD resources shall be utilized for at least part of the Small Data Transmissions.

[0187] The one or more SBFD resources may comprise one or more time domain resources. The one or more SBFD resources may comprise one or more frequency domain resources.

[0188] The indication may be received in response to the transmitting the RRC resume request message, e.g., as in Action 1002.Action 1004. In some embodiments, the UE 120 communicates Small Data Transmissions with the network node 110. Communicating as used herein may mean receiving and / or transmitting, in particular transmitting. The communication may be performed in response to receiving the indication to the UE 120. The Small Data Transmissions may be in accordance with the information of the transmitted indication.

[0189] In some embodiments, the Small Data Transmissions are arranged for utilizing CG-SDT. Additionally or alternatively, the Small Data Transmissions are arranged for utilizing RA-SDT. In other words, Small Data Transmissions of embodiments herein may relate to CG-SDT and / or RA-SDT. Accordingly CG-SDT and / or RA-SDT may, based on embodiments herein, be enabled to utilize SBFD.

[0190] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0191] For below embodiments, the gNB or receiving gNB may represent the network node 110. However, any other suitable types of network nodes than gNB may apply, as discussed above with respect to Fig. 8. For below embodiments, when a UE is mentioned, it may be the UE 120. The UE 120 may in particular be a SBFD aware UE. For below embodiments, any one or more indications may be, or may be part of, the indication as communicated in Action 905 and / or Action 1003.

[0192] Group A Embodiments -CG-SDT

[0193] In some embodiments, the gNB signals an indicator, also referred to as indication, a CG resource type which the UE 120 shall use for SDT. The indicator may be received via dedicated RRC signaling, MAC CE or L1 signaling (e.g., DCI on PDCCH). The CG resource type may indicate be whether or not SBFD can be used for the SDT.

[0194] In some embodiments, the gNB uses an RRCRelease message to signal the indicator to the UE 120 . The message may be sent to the UE 120 when the UE 120 transits from RRC_CONNECTED to RRCJNACTIVE.

[0195] In some embodiments, the gNB uses a RRCReconfiguration message to signal the indicator to the UE 120 when the UE is in RRC_CONNECTED.

[0196] In some embodiments, the gNB uses a RRC signaling, e.g., for triggering handover, e.g., also referred to as Handovercommand, or RRCReconfigurationwithSync, to signal the indicator to the UE 120 when the UE 120 is in RRC_CONNECTED. The RRC signaling may include one or more CG resources which the UE 120 may use for its UL transmission during a handover procedure.In some embodiments, the gNB may configure different and / or separate CG resources for UL slots / symbols and SBFD slots / symbols respectively. For the latter, the configured CG resources may be limited to UL Subband, e.g., configured by SBFD T / F configuration for UL transmissions during SBFD slots / symbols.

[0197] In some embodiments, the indicator may indicate at least one of the below:

[0198] - Alt. 1 - UL slot / symbol, e.g., UL symbol or flexible symbol may be configured according to a TDD pattern such as configured by tdd-UL-DL-ConfigurationCommon, but may be scheduled as an UL slot by the gNB. In this example, the UE 120 may only use CG resources to perform SDT transmission during UL slot / symbol periods.

[0199] - Alt. 2 - SBFD slot / symbol, e.g., SBFD symbols may be configured as downlink and SBFD symbols may be configured as flexible by tdd-UL-DL-ConfigurationCommon. In this example, the UE 120 may only use CG resources to perform SDT during SBFD slot / symbol periods. Additionally or alternatively, the UE 120 may only use the CG resources, e.g., limited to UL subband in frequency if the CG resources span both UL subband and DL subband(s), to perform SDT transmission during SBFD slot / symbol periods.

[0200] - Alt. 3 -Across SBFD slots / symbols and UL slots / symbols. In this example, the UE 120 may use CG resources to perform SDT transmission across SBFD slots / symbols and UL slots / symbols.

[0201] - Alt. 4 -both SBFD slots / symbols and UL slots / symbols. In this example, the UE 120 may use CG resources during SBFD slots / symbols or UL slots / symbols whichever is available. In this example, the gNB may additionally signal a priority order indicating that the UE 120 shall use the CG resources in SBFD slot / symbol first or the CG resources in UL slot / symbol. The UE 120 may then use the prioritized CG resources first, e.g., CG resources in SBFD slot / symbol or UL slot / symbol, and use the other type of CG resources, e.g., CG resources in UL slot / symbol or SBFD slot / symbol, when the prioritized CG resources are used up.

[0202] In some embodiments, the gNB doesn’t configure / signal the indicator on CG resources to the UE. In these embodiments, it may be up to the UE implementation on how to choose CG resources to perform SDT transmission. The UE 120 may choose the CG resources according to one of the Alternatives as described in the above embodiment.

[0203] In some embodiments, the UE 120 may have the information of the TDD pattern (configured by tdd-UL-DL-ConfigurationCommon). In some of these embodiments, the UE 120 may only use the UL slot to transmit the CG-SDT data.In some embodiments, the UE 120 have the information of the TDD pattern (configured by tdd-UL-DL-ConfigurationCommon). In some of these embodiments, the UE 120 may use both the UL slot and flexible slot to transmit the CG-SDT data.

[0204] Group B Embodiments - on RA-SDT

[0205] Various embodiments on how the UE 120 performs MO-SDT transmission / procedure and MT-SDT procedure using SBFD resources over RACH are described herein.

[0206] For below embodiments, the last serving gNB may represent the last serving network node 111. However, any other suitable types of network nodes than gNB may apply, as discussed above with respect to Fig. 8.

[0207] In some embodiments, for MO-SDT procedure over RACH, when the UE 120 accesses a gNB other than the last serving gNB, the UL SDT data / signalling may be buffered at the receiving gNB, and then the receiving gNB may trigger an XnAP Retrieve UE Context procedure. The receiving gNB may indicate SDT to the last serving gNB and the last serving gNB may decide whether to relocate the UE context or not.

[0208] Regardless of whether the last serving gNB decides to relocate the full UE context, as long as the receiving gNB is SBFD capable, the last serving gNB may transfer the information on whether the UE is SBFD aware to the receiving gNB. Based on the information, the receiving gNB can determine how to allocate resources to the UE’s SDT data transmission. If the information indicates that the UE is SBFD aware, the receiving gNB may allocate SBFD PUSCH resources, e.g., as part of action 904, such as PUSCH resources may be allocated in UL subband during SBFD symbols / slots in time to the UE 120 for its subsequent UL SDT data transmission. If the information indicates that the UE 120 is not SBFD aware, the receiving gNB may allocate legacy PUSCH resources such as PUSCH resources allocated during UL symbols / slots in time to the UE for its subsequent UL SDT data transmission.

[0209] Upon reception of the PUSCH resources, the UE 120 may perform subsequent SDT transmissions accordingly, e.g., as in actions 906, 1004.

[0210] If the information provided by the last serving gNB on whether the UE is SBFD aware is absent, the receiving gNB may, by default, allocate legacy PUSCH resources, such as PUSCH resources allocated during UL symbols / slots in time to the UE 120 for its subsequent UL SDT data transmission.

[0211] Fig. 11 illustrates an overall example procedure for an SDT procedure over RACH without UE context relocation. The information on the SBFD awareness in Step 4 may be the additional information which the last serving gNB sends to Receiving gNB.

[0212] Step 0. The UE 120 may be in the state RRC INACTIVE CM CONNECTED.

[0213] Steps 1 / 2. The steps 1 / 2 are as defined in steps 1 / 2 in Fig. 5Step 3. The last serving gNB decides not to relocate the full UE context for SDT. In case that the Last Serving gNB has requested AMF for CN Buffering as part of step 0 for the UE 120 in RRC INACTIVE state with eDRX cycle longer than 10.24 seconds, reachability of the UE 120 is indicated to the AMF by the last serving gNB using an MT Communication Handling procedure as described in 3GPP TS 23.501 and 3GPP TS 38.413.

[0214] Step 4. The last serving gNB transfers a partial UE context including the SDT related RLC context. The last serving gNB may also transfer information on the UE’s SBFD awareness to the receiving gNB.

[0215] Step 5. The receiving gNB acknowledges receiving the partial UE context and provides associated DL TNL address. The UE context may be kept at the last serving gNB and the SDT related RLC context is established at the receiving gNB. Then UL / DL GTP-U tunnels may be established for Data Radio Bearers (DRBs) configured for SDT, if any, and the UL SDT data and / or signalling, if any, may be forwarded to the last serving gNB, and then delivered to the core network of the wireless communications network 100. The receiving gNB may account for information on whether the UE 120 is SBFD aware, and may accordingly determine whether to allocate SBFD PUSCH resources to the UE 120.

[0216] NOTE 1 :The DL signalling from the last serving gNB, if any, is forwarded to the receiving gNB via the RRC TRANSFER message, for which the receiving gNB delivers it to the UE.

[0217] NOTE 1a: In case DL non-SDT data or DL non-SDT signalling arrives, or UE assistance information (i.e. UL non-SDT data arrival indication) is received from the UE, the last serving gNB terminates the SDT procedure by sending the RRCRelease message.

[0218] NOTE 1b: The last serving gNB may terminate the SDT procedure by sending the RRCRelease message based on (e.g. large size of) DL SDT data or DL SDT signalling.

[0219] Step 6. The receiving gNB detects the end of SDT session and sends the RETRIEVE UE CONTEXT CONFIRM message including whether this is a "normal" end of SDT transaction or a radio link problem, or large SDT volume from BSR.

[0220] Step 7. Upon receiving the RETRIEVE UE CONTEXT CONFIRM message and deciding to terminate the SDT, the last serving gNB responds to the receiving gNB with the RETRIEVE UE CONTEXT FAILURE message including an encapsulated RRCRelease message. The receiving gNB shall release the established partial UE context.

[0221] Step 8. The receiving gNB sends the RRCRelease message to the UE.

[0222] NOTE 5:The last serving gNB may terminate the SDT procedure by sending the RRCRelease message upon receiving the indication about large uplink SDT data from the BSR from the receiving gNB in step 6.

[0223] NOTE 6:The Last Serving gNB may send the NGAP MT Communication Handling Request message to the AMF to trigger CN buffering when the UE is put again into RRC NACTIVE state with eDRX cycle longer than 10.24 seconds.Step 9. The UE moves to RRCJNACTIVE state if the suspend indication is included in the RRCRelease message, or the UE may initiate RRC resume procedure to transition to RRC_CONNECTED state if the resume indication is included in the RRCRelease message. Or else, the UE moves to RRCJDLE state.

[0224] Fig. 12 illustrates an overall example procedure for SDT procedure over RACH with UE context relocation. In particular, step 3 may comprise additional information which the last serving gNB sends to Receiving gNB.

[0225] Step 0. The UE 120 may be in the state RRC INACTIVE CM CONNECTED.

[0226] Step 1. The UE 120 sends an RRCResumeRequest as well as UL SDT data and / or UL SDT signalling to the Receiving gNB.

[0227] Step 2. The Receiving gNB identifies the Last Serving gNB using the l-RNTI and retrieves the UE context by means of Xn-AP Retrieve UE Context procedure. The Receiving gNB indicates that the UE request is for an SDT and may also provide SDT assistance information (e.g., single packet, multiple packets).

[0228] Step 3. The Last Serving gNB decides to relocate UE context and responds with the RETRIEVE UE CONTEXT RESPONSE message. The last serving gNB may respond with the information on the UE’s SBFD awareness to the UE. The UL SDT data, if any, is delivered from the Receiving gNB to the UPF. In case that the Last Serving gNB has requested the AMF for CN Buffering as part of step 0 for the UE in RRC INACTIVE state with eDRX cycle longer than 10.24 seconds, reachability of the UE can be indicated to the AMF by the last serving gNB using the MT Communication Handling procedure as described in 3GPP TS 23.501 and 3GPP TS 38.413., otherwise, if the AMF considers that the UE is reachable, the MT Communicating Handing may be deactivated upon step 5.

[0229] Steps 4-6. The Receiving gNB decides to keep UE 120 in RRCJNACTIVE state for SDT. Loss of DL user data buffered in the Last Serving gNB may be prevented. The Receiving gNB provides forwarding addresses via the Xn-U ADDRESS INDICATION message. The Receiving gNB also initiates NGAP Path Switch Request procedure to establish a NG UE-associated signalling connection to the AMF. After the Path Switch Request procedure, the buffered UL NAS PDU, if any, is delivered from the Receiving gNB to the AMF. And then, the subsequent UL / DL SDT data and / or signalling are transferred between UE and core network via the Receiving gNB. The receiving gNB also takes into account information on whether the UE is SBFD aware, determines whether to allocate SBFD PUSCH resources to the UE NOTE 1 : If the UP policy received from the Last Serving gNB is different from that received in the PATH SWITCH REQUEST ACKNOWLEDGE message, the Receiving gNB may either send the UE back to RRC DLE or move the UE to RRC_CONNECTED to update the security configuration.Step 7. After SDT transmission is terminated, the Receiving gNB generates and sends the RRCRelease message including the suspend indication to the UE to terminate the SDT procedure and continue in RRCJNACTIVE state.

[0230] NOTE 2: In case DL non-SDT data or DL non-SDT signalling arrives, or the UE assistance information e.g., UL non-SDT data arrival indication, is received from the UE 120, the Receiving gNB may decide to directly send the UE to RRC_CONNECTED state by sending the RRCResume message.

[0231] NOTE 3:The Receiving gNB may decide to directly send the UE to RRC_CONNECTED state by sending the RRCResume message based on (e.g. large size of) DL SDT data or DL SDT signalling.

[0232] NOTE 4:The Receiving gNB may decide to directly send the UE to RRC_CONNECTED state by sending the RRCResume message based on the BSR received from the UE in case of uplink SDT data exceeding the data size threshold.

[0233] NOTE 5:The Receiving gNB may send the NGAP MT Communication Handling Request message to the AMF to trigger CN buffering when the UE is put again into RRCJNACTIVE state with eDRX cycle longer than 10.24 seconds.

[0234] 8. The Receiving gNB indicates to the Last Serving gNB to remove the UE context by sending the XnAP UE CONTEXT RELEASE message. The XnAP UE CONTEXT RELEASE message can be sent after step 6.

[0235] In some embodiments, when DL user data and / or DL NAS signalling are received at the Last Serving gNB for the UE 120 in RRCJNACTIVE state, and / or a RAN Paging request message is received at the Last Serving gNB for the UE 120 in RRCJNACTIVE state with long eDRX(cycle) beyond 10.24 seconds, the Last Serving gNB may send MT-SDT information and the information on whether the UE is SBFD aware to the neighbour gNBs within the RNA, via XnAP RAN PAGING message. The network node such as a gNB, e.g., the network node 110, that receives MT-SDT information within the RAN, may take into account the MT-SDT information received in the XnAP RAN PAGING message to decide whether to trigger MT-SDT Paging. The gNB which ultimately reaches the UE 120 via the Uu Paging becomes the Receiving gNB.

[0236] Upon reception of the paging, the UE 120 may decide to initiate MT-SDT procedure, e.g., to send an RRCResumeRequest message with an MT-SDT resume cause to the Receiving gNB, e.g., as part of Action 1002. During the MT-SDT procedure, the receiving gNB may determine how to allocate resources to the UE’s SDT data transmission, e.g., as in Action 904. If the information indicates that the UE is SBFD aware, the receiving gNB may allocate SBFD PUSCH resources, e.g., PUSCH resources allocated in UL subband during SBFD symbols / slots in time to the UE 120 for its subsequent UL SDT data transmission. If theinformation indicates that the UE is not SBFD aware, the receiving gNB may allocate legacy PLISCH resources, e.g., PLISCH resources allocated during UL symbols / slots in time to the UE for its subsequent UL SDT data transmission.

[0237] Upon reception of the PUSCH resources, the UE 120 may perform subsequent SDT transmissions accordingly, e.g., as in Action 1004.

[0238] An example MT-SDT procedure is illustrated in Fig 13. Step 2 may in particular comprise information which the last serving gNB sends to Receiving gNB.

[0239] Step 1. DL user data and / or DL NAS signalling are received at the Last Serving gNB for the UE 120 in RRCJNACTIVE state, and / or a RAN Paging request message is received at the Last Serving gNB for the UE 120 in RRCJNACTIVE state with long eDRX(cycle) beyond 10.24 seconds.

[0240] Step 2. The Last Serving gNB may send MT-SDT information and the information on whether the UE 120 is SBFD aware or not to the neighbour gNBs within the RNA, via XnAP RAN PAGING message.

[0241] Step 3. The gNB that receives MT-SDT information within the RNA, may account for MT-SDT information received in the XnAP RAN PAGING message to decide whether to trigger MT-SDT Paging. The gNB may also into account information on whether the UE 120 is SBFD aware, when determining whether to allocate SBFD PUSCH resources to the UE 120. The gNB which ultimately reaches the UE via the Uu Paging becomes the Receiving gNB.

[0242] NOTE 1 : In case that the Receiving gNB decides not to trigger MT-SDT paging, the above step 3 and subsequent steps are the same as Fig. 7 from step 3.

[0243] Steps 4 / 5. The UE 120 may decide to initiate MT-SDT procedure and in this case sends an RRCResumeRequest message with an MT-SDT resume cause to the Receiving gNB.

[0244] Steps 6. The following steps are the same as Figs 5-6 from step 2, except that the first SDT user data and / or NAS signalling is DL SDT data and / or DL SDT NAS signalling.

[0245] NOTE 2: In case DL non-SDT data or DL non-SDT signalling has arrived between step 2 and step 6, the Last Serving gNB should relocate the UE context to the Receiving gNB and forward the received data to the Receiving gNB.

[0246] Fig. 14 illustrates an example of the arrangement that the network node 110 may comprise to perform the method described in Fig. 9. The network node 110 may be understood to be configured to handle Small Data Transmission of embodiments herein. As discussed above, the network node 110 may be configured to operate in the wireless communications network 100.

[0247] Several embodiments are comprised herein. It should be noted that the examples and embodiments herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description.

[0248] Components from one embodiment may be tacitly assumed to be present in anotherembodiment 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 network node 110 and will thus not be repeated here to simplify the description.

[0249] The network node 110 may comprise an input and output interface 1410 configured to communicate with any suitable. The input and output interface 1410 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0250] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 1411 of a processing circuitry in the network node 110 depicted in Fig. 14, together with computer program code for performing the functions and actions of the embodiments herein. 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.

[0251] The network node 110 is configured to handle Small Data Transmission, between the network node 110 and the UE 120 in the wireless communications network 100. The network node 110 is configured to, transmit to the UE 120, an indication indicative of whether or not one or more SBFD resources can be utilized for at least part of a Small Data Transmission between the UE 120 and the network node 110.

[0252] In some embodiments, the indication is further indicative of one or more resources which can be utilized for at least part of the Small Data Transmission.

[0253] In some embodiments, the indication is further indicative of one or more resources which shall be utilized for at least part of the Small Data T ransmission and / or wherein the indication is further indicative of whether or not at least one of the one or more SBFD resources shall be utilized for at least part of the Small Data Transmission.

[0254] In some embodiments, the network node 110 is configured to: in response to transmitting the indication to the UE 120, communicate, e.g., receive, Small Data Transmission with the UE 120.

[0255] In some embodiments, wherein the Small Data Transmission is arranged for utilizing CG-SDT, and / or wherein the Small Data Transmission is arranged for utilizing RA-SDT.

[0256] In some embodiments, the network node 110 is further configured to: obtain capability information indicative of whether or not the UE 120 is capable of communicating in a cellconfigured to at least partly provide communication using SBFD resources. The indication may be based on the capability information.

[0257] In some embodiments, the network node 110 is configured to obtaining the capability information in response to detecting that the network node 110 was not the last serving network node 111 for the UE 120.

[0258] In some embodiments, the network node 110 is configured to obtain the capability information by receiving the capability information from the last serving network node 111 of the UE 120 or by retrieving a partial or full UE context of the UE 120 from the last serving network node 111 of the UE 120. The capability information may be based on the partial or full UE context.

[0259] In some embodiments, the network node 110 is configured to, based on the capability information, allocate the one or more SBFD resources for the UE 120.

[0260] In some embodiments, the network node 110 is configured to transmit the indication to the UE 120 in response to receiving an RRC resume request message from the UE 120.

[0261] In some embodiments, the network node 110 is configured to transmit a paging message to the UE 120. The paging message may be arranged to trigger the UE 120 to transmit an RRC resume request message to the network node 110.

[0262] In some embodiments, the one or more SBFD resources comprise one or more time domain resources.

[0263] In some embodiments, the one or more SBFD resources comprise one or more frequency domain resources.

[0264] The network node 110 may further comprise respective a memory 1412 comprising one or more memory units. The memory 1412 comprises instructions executable by the processor 1411 in the network node 110.

[0265] The memory 1412 is arranged to be used to store instructions, data, configurations, packets, resources, indications, timers, rules, allocations, and applications to perform the methods herein when being executed in the network node 110.

[0266] In some embodiments, a computer program 1413 comprises instructions, which when executed by the at least one processor 1411, cause the at least one processor 1411 of the network node 110 to perform the actions above.

[0267] In some embodiments, a respective carrier 1414 comprises the respective computer program 1413, wherein the carrier 1414 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0268] The network node 110 may be configured to operate in the wireless communications network 100. The network node 110 may comprise the processor 1411 and the memory 1412,said memory 1412 comprising instructions executable by said processor 1411 whereby said network node 110 is operative to perform any of the methods herein.

[0269] In some embodiments, a computer program product, e.g., the computer program 1413, may comprise instructions, which, when executed on at least one processor such as the processor 1411, cause the at least one processor to carry out the method according to any of the above-mentioned embodiments.

[0270] In some embodiments, a computer-readable storage medium, e.g., the carrier 1414, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, such as the processor 1411, cause the at least one processor to carry out the method according to any of the above-mentioned embodiments.

[0271] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single applicationspecific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.

[0272] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

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

[0274] Fig. 15 illustrates an example of the arrangement that the UE 120 may comprise to perform the method described in Fig. 10. The UE 120 may be understood to be configured to handle Small Data Transmission of embodiments herein. As discussed above, the UE 120 may be configured to operate in the wireless communications network 100.

[0275] Several embodiments are comprised herein. It should be noted that the examples and embodiments herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description.

[0276] 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 UE 120 and will thus not be repeated here to simplify the description.

[0277] The UE 120 may comprise an input and output interface 1510 configured to communicate with any suitable. The input and output interface 1510 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0278] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 1511 of a processing circuitry in the UE 120 depicted in Fig. 15, together with computer program code for performing the functions and actions of the embodiments herein. 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 UE 120. 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 UE 120.

[0279] The UE 120 is configured to handle Small Data Transmission between the network node 110 and the UE 120 in the wireless communications network 100.

[0280] The UE 120 is configured to receive from the network node 110, an indication indicative of whether or not one or more SBFD resources can be utilized for at least part of a Small Data Transmission between the UE 120 and the network node 110.

[0281] In some embodiments, the indication is indicative of one or more resources which can be utilized for at least part of the Small Data Transmission.In some embodiments, the indication is indicative of one or more resources which shall be utilized for at least part of the Small Data Transmission.

[0282] In some embodiments, the indication is indicative of whether or not at least one of the one or more SBFD resources shall be utilized for at least part of the Small Data Transmission.

[0283] In some embodiments, the UE 120 is configured to: in response to receiving the indication to the UE 120, communicate Small Data the Transmission with the network node 110.

[0284] In some embodiments, the Small Data Transmission is arranged for utilizing CG-SDT. In some embodiments, the Small Data Transmission is arranged for utilizing RA-SDT. In some embodiments, the UE 120 is configured to transmit an RRC resume request message to the network node 110. In some embodiments, the UE is configured to, in response to the transmitted RRC resume request message, receive the indication.

[0285] In some embodiments, the UE 120 is configured to receive a paging message from the network node 110. In some embodiments, the paging message triggers the UE 120 to transmit an RRC resume request message to the network node 110.

[0286] In some embodiments, the one or more SBFD resources comprise one or more time domain resources.

[0287] In some embodiments, the one or more SBFD resources comprise one or more frequency domain resources.

[0288] The UE 120 may further comprise respective a memory 1512 comprising one or more memory units. The memory 1512 comprises instructions executable by the processor 1511 in the UE 120.

[0289] The memory 1512 is arranged to be used to store instructions, data, configurations, packets, resources, indications, timers, rules, allocations, and applications to perform the methods herein when being executed in the UE 120.

[0290] In some embodiments, a computer program 1513 comprises instructions, which when executed by the at least one processor 1511, cause the at least one processor 1511 of the UE 120 to perform the actions above.

[0291] In some embodiments, a respective carrier 1514 comprises the respective computer program 1513, wherein the carrier 1514 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0292] The UE 120 may be configured to operate in the wireless communications network 100. The UE 120 may comprise the processor 1511 and the memory 1512, said memory 1512 comprising instructions executable by said processor 1511 whereby said UE 120 is operative to perform any of the methods herein.In some embodiments, a computer program product, e.g., the computer program 1513, may comprise instructions, which, when executed on at least one processor such as the processor 1511, cause the at least one processor to carry out the method according to any of the above-mentioned embodiments.

[0293] In some embodiments, a computer-readable storage medium, e.g., the carrier 1514, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, such as the processor 1511, cause the at least one processor to carry out the method according to any of the above-mentioned embodiments.

[0294] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single applicationspecific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.

[0295] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

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

[0297] Fig. 16 shows an example of a communication system QQ100 in accordance with some embodiments. The communication system QQ100 may be the wireless communications system 100.

[0298] In the example, the communication system QQ100 includes a telecommunications network QQ102, e.g., the wireless communications network 100, that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108.The access network QQ104 includes one or more access network nodes or base stations of various types, access network nodes QQ110A and QQ110B are depicted (which may be collectively referred to as network nodes QQ110, e.g., the network node 110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network QQ104 may include more than one access network technology. The network nodes QQ110 of access network QQ104 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), e.g., the UE 120, such as by connecting UEs QQ112A, QQ112B, QQ112C, and QQ112D (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

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

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

[0301] The network nodes QQ110 facilitate direct or indirect connection of one or more UEs QQ112 to the core network QQ106 over one or more wireless connections. 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 QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

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

[0303] In the depicted example, the core network QQ106 connects elements of the access network QQ104 (e.g., one or more of the network nodes QQ110) to one or more host computing systems, such as host QQ116. 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 QQ106 includes one or more core network nodes (e.g., core network node QQ108) of various types, one or more of which may be generally referred to as network nodes QQ108. Network nodes QQ108 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (ALISF), 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).

[0304] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunications network QQ102. The host QQ116 may be operated by the service provider or on behalf of the service provider. The host QQ116 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.

[0305] As a whole, the communication system QQ100 of Fig. 16 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system QQ100 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);

[0306] 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) 903.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system QQ100 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system QQ100 supporting different standards, protocols, or rule sets.

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

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

[0309] In some examples, one or more of the UEs QQ112 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 QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi-RAT or multistandard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0310] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112C and / or QQ112D) and network nodes (e.g., network node QQ110B). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one ormore actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114.

[0311] As another example, the hub QQ114 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 QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0312] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110B. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112C and / or QQ112D), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection.

[0313] Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 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 QQ110B. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0314] Fig. 17 is another example of a communication system QQ200 according to some embodiments. As used herein, the communication system QQ200 includes multiple access points (APs) QQ210 (with four exemplary APs QQ210A, QQ210B, QQ210C, and QQ210D being depicted) and multiple wireless devices, referred to in the context of communication system QQ200 as stations (STAs) QQ212 (referred to individually as STA QQ212A, STA QQ212B, STA QQ212C, STA QQ212D, and STA QQ212E). STA QQ212A is served by AP QQ210A in a first basic service set (BSS) QQ220A. STA QQ210B and STA QQ210C are served by AP QQ210B in a second BSS, BSS QQ220B. STA QQ212D is served by AP QQ210C in a third BSS, BSS QQ220C. STA QQ212E is served by AP QQ210D in a fourth BSS, BSS QQ220D. Stations QQ212 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gamingdevices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations QQ212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

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

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

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

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

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

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

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

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

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

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

[0325] The processing circuitry QQ302 may be configured to communicate with an access network or other network via or using the communication interface QQ312. The communication interface QQ312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ322. The communication interface QQ312 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter QQ318 and / or a receiver QQ320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).

[0326] Moreover, the transmitter QQ318 and receiver QQ320 may be coupled to one or more antennas (e.g., antenna QQ322) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0327] In the illustrated embodiment, communication functions of the communication interface QQ312 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 903.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 903.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.In particular embodiments, wireless device QQ300 may provide an output of data captured via a sensor, through its communication interface QQ312, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device QQ300 can be communicated through a wireless connection to a network node via another wireless device QQ300. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

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

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

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

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

[0332] Fig. 19 shows a network node QQ400 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node QQ400 may be configured to operate in communication system QQ100 of Fig.16, like network nodes QQ108 or QQ110, or in communication system QQ200 of Fig.17, like an AP QQ210 or a station QQ212. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

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

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

[0335] In particular embodiments, network node QQ400 includes a processing circuitry QQ402, a memory QQ404, a communication interface QQ406, and a power source QQ408. In general, in a particular embodiment of network node QQ400, processing circuitry QQ402, memory QQ404, communication interface QQ406, and power source QQ408 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node QQ400.

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

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

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

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

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

[0341] In certain alternative embodiments, network node QQ400 may be capable of wireless communication but does not include separate radio front-end circuitry QQ418, instead, the processing circuitry QQ402 includes radio front-end circuitry and is connected to the antenna QQ410. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ412 is part of the communication interface QQ406. In still other embodiments, the communication interface QQ406 includes one or more ports or terminals QQ416, the radio front-end circuitry QQ418, and the RF transceiver circuitry QQ412, as part of a radio unit (not shown), and the communication interface QQ406 communicates with the baseband processing circuitry QQ414, which is part of a digital unit (not shown).

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

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

[0344] The power source QQ408 provides power to the various components of network node QQ400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ400 with power for performing the functionality described herein. For example, the network node QQ400 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ408. As a further example, the power source QQ408 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.Embodiments of the network node QQ400 may include additional components beyond those shown in Fig. 18 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ400 may include user interface equipment to allow input of information into the network node QQ400 and to allow output of information from the network node QQ400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ400.

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

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

[0347] Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM QQ508A and VM QQ508B (which may be collectively referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to one or more of the VMs QQ508.The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

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

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

[0350] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein.

[0351] Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or moreoperations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

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

[0353] When using the word "comprise" or “comprising”, it shall be interpreted as non- limiting, i.e. , meaning "consist at least of".

[0354] The embodiments herein are not limited to the above-described preferred embodiments. Various alternatives, modifications and equivalents may be used. Therefore, the above embodiments should not be taken as limiting the scope of the invention.

[0355] 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 otherembodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0356] 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.

[0357] Any of the terms processor and circuitry may be understood herein as a hardware component.

[0358] As used herein, the expression “in some embodiments” has been used to indicate that the features of the embodiment described may be combined with any other embodiment or example disclosed herein.

[0359] As used herein, the expression “in some examples” has been used to indicate that the features of the example described may be combined with any other embodiment or example disclosed herein.

[0360] Below follows a list of Embodiments which may be combined with any examples or embodiments above.

[0361] Embodiment 1. A method performed by a network node 110 for handling Small Data Transmission between the network node 110 and a User Equipment, UE, 120 in a wireless communications network 100, the method comprising:

[0362] - transmitting 905 to the UE 120, an indication indicative of whether or not one or more Subband Full Duplex, SBFD, resources can be utilized for at least part of a Small Data Transmission between the UE 120 and the network node 110.

[0363] Embodiment 2. The method of Embodiment 1 , wherein the indication is further indicative of one or more resources which can be utilized for at least part of the Small Data Transmission.

[0364] Embodiment 3. The method of Embodiment 1 or 2, wherein the indication is further indicative of one or more resources which shall be utilized for at least part of the Small Data Transmission and / or wherein the indication is further indicative of whether or not at least one of the one or more SBFD resources shall be utilized for at least part of the Small Data Transmission.Embodiment 4. The method of any of Embodiments 1-3, wherein the method further comprises:

[0365] in response to transmitting the indicator, also referred to as indication, to the UE 120, communicating 906, e.g., receiving, the Small Data Transmission with the UE 120.

[0366] Embodiment 5. The method of any of Embodiments 1-4, wherein the Small Data Transmission is arranged for utilizing Configured Grant, CG, SDT, CG-SDT, and / or wherein the Small Data Transmission is arranged for utilizing Random Access, RA, SDT, RA-SDT.

[0367] Embodiment 6. The method of any of Embodiments 1-5, further comprising:

[0368] obtaining 903 capability information indicative of whether or not the UE 120 is capable of communicating in a cell configured to at least partly provide communication using SBFD resources.

[0369] Embodiment 7. The method of Embodiment 6, wherein obtaining the capability information is performed in response to detecting that the network node 110 was not the last serving network node 111 for the UE 120.

[0370] Embodiment 8. The method of Embodiment 6 or 7, wherein obtaining the capability information comprises receiving the capability information from the last serving network node 111 of the UE 120 or retrieving a partial or full UE context of the UE 120 from the last serving network node 111 of the UE 120, and wherein the capability information is based on the partial or full UE context.

[0371] Embodiment 9. The method of any of Embodiments 6-8, further comprising, based on the capability information, allocating 904 the one or more SBFD resources for the UE 120.

[0372] Embodiment 10. The method of any of Embodiments 1-9, wherein transmitting the indicator to the UE 120 is performed in response to receiving 902 an RRC resume request message from the UE 120.

[0373] Embodiment 11. The method of any of Embodiments 1-10, wherein the method comprises transmitting 901 a paging message to the UE 120, wherein the paging message is arranged to trigger the UE 120 to transmit an RRC resume request message to the network node 110.Embodiment 12. The method of any of Embodiments 1-11, wherein the one or more SBFD resources comprise one or more time domain resources and / or wherein the one or more SBFD resources comprise one or more frequency domain resources.

[0374] Embodiment 13. A method performed by a User Equipment, UE, 120 for handling Small Data Transmission, between a network node 110 and the UE 120 in a wireless communications network 100, the method comprising:

[0375] receiving 1003 from the network node 110, an indication indicative of whether or not one or more Subband Full Duplex, SBFD, resources can be utilized for at least part of a Small Data Transmission between the UE 120 and the network node 110.

[0376] Embodiment 14. The method of Embodiment 13, wherein the indication is further indicative of one or more resources which can be utilized for at least part of the Small Data Transmission.

[0377] Embodiment 15. The method of Embodiment 13 or 14, wherein the indication is further indicative of one or more resources which shall be utilized for at least part of the Small Data Transmission and / or wherein the indication is further indicative of whether or not at least one of the one or more SBFD resources shall be utilized for at least part of the Small Data Transmission.

[0378] Embodiment 16. The method of any of Embodiments 13-15, wherein the method further comprises:

[0379] in response to receiving the indicator to the UE 120, communicating 1004, e.g., transmitting, the Small Data Transmission with the network node 110.

[0380] Embodiment 17. The method of any of Embodiments 13-16, wherein the Small Data Transmission is arranged for utilizing Configured Grant, CG, SDT, CG-SDT, and / or wherein the Small Data Transmission is arranged for utilizing Random Access, RA, SDT, RA-SDT.

[0381] Embodiment 18. The method of any of Embodiments 13-17, further comprising, transmitting 1002 an RRC resume request message to the network node 110, and in response to the transmitted RRC resume request message, receiving 1003 the indicator.Embodiment 19. The method of any of Embodiments 13-18, wherein the method comprises receiving 1001 a paging message from the network node 110, wherein the paging message triggers the UE 120 to transmit 1002 an RRC resume request message to the network node 110.

[0382] Embodiment 20. The method of any of Embodiments 13-19, wherein the one or more SBFD resources comprise one or more time domain resources and / or wherein the one or more SBFD resources comprise one or more frequency domain resources.

[0383] Embodiment 21. A network node 110 configured to handle Small Data Transmission, between the network node 110 and a User Equipment, UE, 120 in a wireless communications network 100, wherein the network node 110 is configured to:

[0384] - transmit to the UE 120, an indication indicative of whether or not one or more Subband Full Duplex, SBFD, resources can be utilized for at least part of a Small Data Transmission between the UE 120 and the network node 110.

[0385] Embodiment 22. The network node 110 of Embodiment 21, wherein the indication is further indicative of one or more resources which can be utilized for at least part of the Small Data Transmission.

[0386] Embodiment 23. The network node 110 of Embodiment 21 or 22, wherein the indication is further indicative of one or more resources which shall be utilized for at least part of the Small Data Transmission and / or wherein the indication is further indicative of whether or not at least one of the one or more SBFD resources shall be utilized for at least part of the Small Data T ransmission.

[0387] Embodiment 24. The network node 110 of any of Embodiments 21-23, wherein the network node 110 further configured to:

[0388] in response to transmitting the indicator to the UE 120, communicate, e.g., receive, Small Data Transmission with the UE 120.

[0389] Embodiment 25. The network node 110 of any of Embodiments 21-24, wherein the Small Data Transmission is arranged for utilizing Configured Grant, CG, SDT, CG-SDT, and / or wherein the Small Data Transmission is arranged for utilizing Random Access, RA, SDT, RA-SDT.Embodiment 26. The network node 110 of any of Embodiments 21-25, further configured to:

[0390] obtain capability information indicative of whether or not the UE 120 is capable of communicating in a cell configured to at least partly provide communication using SBFD resources, and wherein the indicator is based on the capability information

[0391] Embodiment 27. The network node 110 of Embodiment 26 configured to obtaining the capability information in response to detecting that the network node 110 was not the last serving network node 111 for the UE 120.

[0392] Embodiment 28. The network node 110 of Embodiment 26 or 27 configured to obtain the capability information by receiving the capability information from the last serving network node 111 of the UE 120 or by retrieving a partial or full UE context of the UE 120 from the last serving network node 111 of the UE 120, and wherein capability information is based on the partial or full UE context.

[0393] Embodiment 29. The network node 110 of any of Embodiments 26-28, configured to, based on the capability information, allocate the one or more SBFD resources for the UE 120.

[0394] Embodiment 30. The network node 110 of any of Embodiments 21-29 configured to transmit the indicator to the UE 120 in response to receiving an RRC resume request message from the UE 120.

[0395] Embodiment 31. The network node 110 of any of Embodiments 21-30, wherein the network node 110 is configured to transmit a paging message to the UE 120, wherein the paging message is arranged to trigger the UE 120 to transmit an RRC resume request message to the network node 110.

[0396] Embodiment 32. The network node 110 of any of Embodiments 21-31, wherein the one or more SBFD resources comprise one or more time domain resources and / or wherein the one or more SBFD resources comprise one or more frequency domain resources.

[0397] Embodiment 33. A user equipment, UE, 120 configured to handle Small Data Transmission between a network node 110 and the UE 120 in a wireless communications network 100, wherein the UE 120 is configured to:receive from the network node 110, an indication indicative of whether or not one or more Subband Full Duplex, SBFD, resources can be utilized for at least part of a Small Data Transmission between the UE 120 and the network node 110.

[0398] Embodiment 34. The UE 120 of Embodiment 3, wherein the indication is further indicative of one or more resources which can be utilized for at least part of the Small Data Transmission.

[0399] Embodiment 35. The UE 120 of Embodiment 33 or 34, wherein the indication is further indicative of one or more resources which shall be utilized for at least part of the Small Data Transmission and / or wherein the indication is further indicative of whether or not at least one of the one or more SBFD resources shall be utilized for at least part of the Small Data Transmission.

[0400] Embodiment 36. The UE 120 of any of Embodiments 33-35, wherein the UE 120 is configured to:

[0401] in response to receiving the indicator to the UE 120, communicate Small Data the Transmission with the network node 110.

[0402] Embodiment 37. The UE 120 of any of Embodiments 33-36, wherein the Small Data Transmission is arranged for utilizing Configured Grant, CG, SDT, CG-SDT, and / or wherein the Small Data Transmission is arranged for utilizing Random Access, RA, SDT, RA-SDT.

[0403] Embodiment 38. The UE 120 of any of Embodiments 33-37, further configured to transmit an RRC resume request message to the network node 110, and in response to the transmitted RRC resume request message, receive the indicator.

[0404] Embodiment 39. The UE 120 of any of Embodiments 33-38, wherein the UE 120 is configured to receive a paging message from the network node 110, wherein the paging message triggers the UE 120 to transmit an RRC resume request message to the network node 110.

[0405] Embodiment 40. The UE 120 of any of Embodiments 33-39, wherein the one or more SBFD resources comprise one or more time domain resources and / or wherein the one or more SBFD resources comprise one or more frequency domain resources.Embodiment 41. A computer program product 1413 comprising instructions, which, when executed on at least one processor 1411, cause the at least one processor to carry out the method according to any of Embodiments 1-12.

[0406] Embodiment 42. A computer-readable storage medium 1414, having stored thereon a computer program product 1413 comprising instructions which, when executed on at least one processor 1411, cause the at least one processor to carry out the method according to any of Embodiments 1-12.

[0407] Embodiment 43. A computer program product 1513 comprising instructions, which, when executed on at least one processor 1511, cause the at least one processor to carry out the method according to any of Embodiments 13-20.

[0408] Embodiment 44. A computer-readable storage medium 1514, having stored thereon a computer program product 1513 comprising instructions which, when executed on at least one processor 1511, cause the at least one processor to carry out the method according to any of Embodiments 13-20.

Claims

59CLAIMS1. A method performed by a network node (110) for handling Small Data Transmission between the network node (110) and a User Equipment, UE, (120) in a wireless communications network (100), the method comprising:transmitting (905) to the UE (120), an indication indicative of whether or not one or more Subband Full Duplex, SBFD, resources can be utilized for at least part of a Small Data Transmission between the UE (120) and the network node (110), and in response to transmitting the indication to the UE (120), communicating (906), the Small Data Transmission with the UE (120), which Small Data Transmissions are in accordance with the information of the transmitted indication.

2. The method of claim 1 , wherein the indication is further indicative of one or more resources which can be utilized for at least part of the Small Data Transmission.

3. The method of claim 1 or 2, wherein the indication is further indicative of one or more resources which shall be utilized for at least part of the Small Data Transmission and / or wherein the indication is further indicative of whether or not at least one of the one or more SBFD resources shall be utilized for at least part of the Small Data Transmission.

4. The method of any of the claims 1-3, wherein the Small Data Transmission is arranged for utilizing Configured Grant, CG, SDT, CG-SDT, and / or wherein the Small Data Transmission is arranged for utilizing Random Access, RA, SDT, RA-SDT.

5. The method of any of the claims 1-4, further comprising:obtaining (903) capability information indicative of whether or not the UE (120) is capable of communicating in a cell configured to at least partly provide communication using SBFD resources.

6. The method of claim 5, wherein obtaining the capability information is performed in response to detecting that the network node (110) was not the last serving network node (111) for the UE (120).

7. The method of claim 5 or 6, wherein obtaining the capability information comprises receiving the capability information from the last serving network node (111) of the UE (120) or retrieving a partial or full UE context of the UE (120) from the last serving60network node (111) of the UE (120), and wherein the capability information is based on the partial or full UE context.

8. The method of any of the claims 5-7, further comprising, based on the capability information, allocating (904) the one or more SBFD resources for the UE (120).

9. The method of any of the claims 1-8, wherein transmitting the indication to the UE (120) is performed in response to receiving 902 an RRC resume request message from the UE (120).

10. The method of any of the claims 1-9, wherein the method comprises transmitting (901) a paging message to the UE (120), wherein the paging message is arranged to trigger the UE (120) to transmit an RRC resume request message to the network node (110).

11. The method of any of the claims 1-10, wherein the one or more SBFD resources comprise one or more time domain resources and / or wherein the one or more SBFD resources comprise one or more frequency domain resources.

12. A method performed by a User Equipment, UE, (120) for handling Small Data Transmission, between a network node (110) and the UE (120) in a wireless communications network (100), the method comprising:receiving (1003) from the network node (110), an indication indicative of whether or not one or more Subband Full Duplex, SBFD, resources can be utilized for at least part of a Small Data Transmission between the UE (120) and the network node (110), in response to receiving the indication to the UE (120), communicating (1004), the Small Data Transmission with the network node (110), which Small Data Transmissions are in accordance with the information of the received indication.

13. The method of claim 12, wherein the indication is further indicative of one or more resources which can be utilized for at least part of the Small Data Transmission.

14. The method of claim 12 or 13, wherein the indication is further indicative of one or more resources which shall be utilized for at least part of the Small Data Transmission and / or wherein the indication is further indicative of whether or not at least one of the one or more SBFD resources shall be utilized for at least part of the Small Data Transmission.6115. The method of any of the claims 12-14, wherein the Small Data Transmission is arranged for utilizing Configured Grant, CG, SDT, CG-SDT, and / or wherein the Small Data Transmission is arranged for utilizing Random Access, RA, SDT, RA-SDT.

16. The method of any of the claims 12-15, further comprising, transmitting (1002) an RRC resume request message to the network node (110), and in response to the transmitted RRC resume request message, receiving (1003) the indication.

17. The method of any of the claims 12-16, wherein the method comprises receiving (1001) a paging message from the network node (110), wherein the paging message triggers the UE (120) to transmit (1002) an RRC resume request message to the network node (110).

18. The method of any of the claims 12-17, wherein the one or more SBFD resources comprise one or more time domain resources and / or wherein the one or more SBFD resources comprise one or more frequency domain resources.

19. A network node (110) configured to handle Small Data Transmission, between the network node (110) and a User Equipment, UE, (120) in a wireless communications network (100), wherein the network node (110) is configured to:transmit to the UE (120), an indication indicative of whether or not one or more Subband Full Duplex, SBFD, resources can be utilized for at least part of a Small Data Transmission between the UE (120) and the network node (110), andin response to transmitting the indication to the UE (120), communicate the Small Data Transmission with the UE (120), which Small Data Transmissions are in accordance with the information of the transmitted indication.

20. The network node (110) of claim 19, wherein the indication is further indicative of one or more resources which can be utilized for at least part of the Small Data Transmission.

21. The network node (110) of claim 19 or 20, wherein the indication is further indicative of one or more resources which shall be utilized for at least part of the Small Data Transmission and / or wherein the indication is further indicative of whether or not at least one of the one or more SBFD resources shall be utilized for at least part of the Small Data Transmission.6222. The network node (110) of any of the claims 19-21, wherein the Small Data Transmission is arranged for utilizing Configured Grant, CG, SDT, CG-SDT, and / or wherein the Small Data Transmission is arranged for utilizing Random Access, RA, SDT, RA-SDT.

23. The network node (110) of any of the claims 19-22, further configured to:obtain capability information indicative of whether or not the UE (120) is capable of communicating in a cell configured to at least partly provide communication using SBFD resources, and wherein the indication is based on the capability information24. The network node (110) of claim 23 configured to obtain the capability information in response to detecting that the network node (110) was not the last serving network node (111) for the UE (120).

25. The network node (110) of claim 23 or 24 configured to obtain the capability information by receiving the capability information from the last serving network node (111) of the UE (120) or by retrieving a partial or full UE context of the UE (120) from the last serving network node (111) of the UE (120), and wherein capability information is based on the partial or full UE context.

26. The network node (110) of any of the claims 23-25, configured to, based on the capability information, allocate the one or more SBFD resources for the UE (120).

27. The network node (110) of any of the claims 19-26 configured to transmit the indication to the UE (120) in response to receiving an RRC resume request message from the UE (120).

28. The network node (110) of any of the claims 19-27, wherein the network node (110) is configured to transmit a paging message to the UE (120), wherein the paging message is arranged to trigger the UE (120) to transmit an RRC resume request message to the network node (110).

29. The network node (110) of any of the claims 19-28, wherein the one or more SBFD resources comprise one or more time domain resources and / or wherein the one or more SBFD resources comprise one or more frequency domain resources.6330. A user equipment, UE, (120) configured to handle Small Data Transmission between a network node (110) and the UE (120) in a wireless communications network (100), wherein the UE (120) is configured to:receive from the network node (110), an indication indicative of whether or not one or more Subband Full Duplex, SBFD, resources can be utilized for at least part of a Small Data Transmission between the UE (120) and the network node (110), and in response to receiving the indication to the UE (120), communicate the Small Data Transmission with the network node (110), which Small Data Transmissions are in accordance with the information of the received indication.

31. The UE (120) of claim 30, wherein the indication is further indicative of one or more resources which can be utilized for at least part of the Small Data Transmission.

32. The UE (120) of claim 30 or 31 , wherein the indication is further indicative of one or more resources which shall be utilized for at least part of the Small Data Transmission and / or wherein the indication is further indicative of whether or not at least one of the one or more SBFD resources shall be utilized for at least part of the Small Data Transmission.

33. The UE (120) of any of the claims 30-32, wherein the Small Data Transmission is arranged for utilizing Configured Grant, CG, SDT, CG-SDT, and / or wherein the Small Data Transmission is arranged for utilizing Random Access, RA, SDT, RA-SDT.

34. The UE (120) of any of the claims 30-33, further configured to transmit an RRC resume request message to the network node (110), and in response to the transmitted RRC resume request message, receive the indication.

35. The UE (120) of any of the claims 30-34, wherein the UE (120) is configured to receive a paging message from the network node (110), wherein the paging message triggers the UE (120) to transmit an RRC resume request message to the network node (110).

36. The UE (120) of any of Claims 30-35, wherein the one or more SBFD resources comprise one or more time domain resources and / or wherein the one or more SBFD resources comprise one or more frequency domain resources.

37. A computer program product (1413) comprising instructions, which, when executed on at least one processor (1411), cause the at least one processor to carry out the method according to any of the claims 1-11.

38. A computer-readable storage medium (1414), having stored thereon a computer program product (1413) comprising instructions which, when executed on at least one processor (1411), cause the at least one processor to carry out the method according to any of the claims 1-11.

39. A computer program product (1513) comprising instructions, which, when executed on at least one processor (1511), cause the at least one processor to carry out the method according to any of the claims 12-18.

40. A computer-readable storage medium (1514), having stored thereon a computer program product (1513) comprising instructions which, when executed on at least one processor (1511), cause the at least one processor to carry out the method according to any of the claims 12-18.

Images