Triggering of scheduling requests and random access to SDT

Abstract

The present disclosure discloses a device, method, apparatus, and computer-readable storage medium for triggering a scheduling request (SR) and random access (RA) for small data transmission (SDT). In an exemplary embodiment, a terminal device receives from a network device a configuration of one or more configured grant (CG) resources for an SDT procedure and a list of one or more data radio bearers (DRBs) associated with respective logical channels (LCHs) for which SDT is allowed via at least one of the one or more CG resources. After the terminal device starts an SDT procedure in an inactive mode, if the terminal determines that a buffer status report (BSR) is triggered, the terminal device determines whether a configuration of an SR mask should be applied to the LCH configured for SDT.

Description

[Technical field]

[0001] Exemplary embodiments of the present disclosure relate generally to the field of communications, and more particularly to a device, method, apparatus, and computer-readable storage medium for triggering a Scheduling Request (SR) and Random Access (RA) for Small Data Transmission (SDT). [Background technology]

[0002] A user equipment (UE) in an inactive state can perform SDT to reduce the signaling overhead and delays associated with transitioning from an inactive state to a connected state. Two common types of SDT are Random Access Channel (RACH)-based SDT (RACH-based SDT) and Configuration Based SDT (configuration based SDT). (composition) Grant (Grant) The UE may select the RA-SDT if the RA-SDT criteria are met, and if none of the Reference Signal Receiving Power (RSRP) of the synchronization signal block (SSB) associated with the CG resource exceeds the RSRP threshold of the CG-SDT criteria in the SDT type selection phase.

[0003] During the SDT procedure, a Scheduling Request (SR) may be triggered due to lack of UL resources. If SR resources are not configured for SDT, the UE may trigger a Random Access (RA) when a Buffer Status Report (BSR) is triggered by SDT data because SR resources are not available. Triggering of SR and RA may induce unnecessary BWP switching. Summary of the Invention

[0004] Generally, the exemplary embodiments of the present disclosure provide a device, a method, an apparatus, and a computer-readable storage medium for triggering SR and RA for an SDT.

[0005] In a first aspect, a terminal device is provided that includes at least one processor and at least one memory having computer program code, the at least one memory and the computer program code being adapted to transmit, using the at least one processor, a small data transmission (SDT) procedure from a network device. (procedure) and receiving a list of one or more data radio bearers (DRBs) associated with respective logical channels (LCHs) for which SDT over at least one of the one or more CG resources is permitted. Further, a decision to initiate an SDT procedure in an inactive mode such that a buffer status report (BSR) is triggered. (judgment, judgment) According to the method, the terminal device determines whether the configuration of the scheduling request mask should be applied to the LCH configured for the SDT.

[0006] In a second aspect, a terminal device is provided that includes at least one processor and at least one memory having computer program code configured to cause the terminal device, using the at least one processor, to receive from the network device a configuration of one or more CG resources for an SDT procedure and a list of one or more DRBs associated with each LCH for which SDT via at least one of the one or more CG resources is allowed, and further to cause the terminal device, in response to determining that a random access procedure should be initiated, to determine whether initiation of the random access procedure should be delayed.

[0007] In a third aspect, a method is provided, in which a terminal device receives from a network device a configuration of one or more CG resources for an SDT procedure and a list of one or more DRBs associated with each LCH for which SDT via at least one of the one or more CG resources is permitted. If the terminal device determines that a BSR is triggered after the terminal device initiates an SDT procedure in an inactive mode, the terminal device determines whether a configuration of a scheduling request mask should be applied to the LCH configured for the SDT.

[0008] In a fourth aspect, a method is provided, in which a terminal device receives from a network device a configuration of one or more CG resources for an SDT procedure and a list of one or more DRBs associated with each LCH for which SDT via at least one of the one or more CG resources is permitted. If the terminal device determines that a random access procedure should be initiated, the terminal device determines whether initiation of the random access procedure should be delayed.

[0009] In a fifth aspect, there is provided an apparatus comprising means for carrying out a method according to the third or fourth aspect.

[0010] In a sixth aspect, there is provided a computer readable storage medium including program instructions stored thereon which, when executed by a processor of a device, cause the device to perform a method according to the third or fourth aspect.

[0011] It should be understood that this Summary section is not intended to identify key or essential features of exemplary embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily apparent through the following description.

[0012] Some exemplary embodiments will now be described with reference to the accompanying drawings. [Brief description of the drawings]

[0013] [Figure 1] 1 illustrates an exemplary environment in which exemplary embodiments of the present disclosure may be implemented. [Diagram 2] 1 illustrates a flowchart of an example method for enhanced triggering of a scheduling request (SR), according to some example embodiments of the present disclosure. [Diagram 3] 13 shows a flowchart of an example method for triggering enhancement of random access (RA) in accordance with certain other example embodiments of the present disclosure. [Figure 4] FIG. 1 shows a simplified block diagram of a device suitable for practicing exemplary embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Throughout the drawings, the same or similar reference numbers represent the same or similar elements.

[0015] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these exemplary embodiments are merely provided for illustrative purposes, to help those skilled in the art understand and practice the present disclosure, but do not imply any limitations on the scope of the present disclosure. The disclosure described herein can be implemented in various ways other than those described below.

[0016] In the following description and claims, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs, unless otherwise defined.

[0017] As used herein, the term "terminal device" or "user equipment" (UE) refers to any terminal device capable of wireless communication with each other or with a base station. The communication may include transmitting and / or receiving wireless signals using electromagnetic signals, radio waves, infrared signals, and / or other types of signals suitable for conveying information wirelessly. In some example embodiments, the UE may be configured to transmit and / or receive information without direct human interaction. For example, the UE may transmit information to the base station on a predefined schedule, when triggered by an internal or external event, or in response to a request from the network side.

[0018] Examples of UEs include, but are not limited to, smartphones, wireless-enabled tablet computers, laptop embedded equipment (LEE), laptop mounted equipment (LME), wireless customer premises equipment (CPE), sensors, metering devices, personal wearables such as watches, and / or vehicles capable of communication. For purposes of explanation, some exemplary embodiments are described with reference to a UE as an example of a terminal device, and the terms "terminal device" and "user equipment" (UE) may be used interchangeably in the context of this disclosure.

[0019] As used herein, the term "network device" refers to a device through which a service can be provided to a terminal device in a communication network. As an example, a network device may include a base station. As used herein, the term "base station" (BS) refers to a network device through which a service can be provided to a terminal device in a communication network. A base station may include any suitable device through which a terminal device or UE can access a communication network. Examples of base stations include a repeater, an access point (AP), a transmission point (TRP), a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a new radio technology (NR) Node B (gNB), a remote radio module (RRU), a radio header (RH), a remote radio head (RRH), a low power node such as a femto, a pico, etc.

[0020] As used herein, the term "circuitry" may refer to one or more or all of the following: (a) A hardware-only circuit implementation (e.g., an implementation using only analog and / or digital circuitry); (b) combinations of hardware circuitry and software, such as (where applicable) (i) a combination of analog and / or digital hardware circuitry(s) and software / firmware, and (ii) any portion of the hardware processor(s) and software (including digital signal processor(s), software, and memory(s) that work together to cause a device, such as a mobile phone or a server, to perform various functions); and (c) Hardware circuit(s) and / or processor(s), such as microprocessor(s) or part of a microprocessor(s), that require software (e.g., firmware) for operation, but the software may not be present if it is not necessary for operation.

[0021] This definition of circuitry applies to all uses of the term in this application, including any claims. As a further example, the term circuitry, as used in this application, also encompasses an embodiment of merely a hardware circuit or processor (or processors), or a portion of a hardware circuit or processor, as well as its (or their) associated software and / or firmware. The term circuitry also encompasses, for example, a baseband or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular base station, or other computing or base station, if applicable to certain claim elements.

[0022] As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly dictates otherwise. The term "includes" and variations thereof should be interpreted as an open term meaning "including, but not limited to." The term "based on" should be interpreted as "based at least in part on." The terms "one embodiment" and "an embodiment" should be interpreted as "at least one embodiment." The term "another embodiment" should be interpreted as "at least one other embodiment." Other definitions, both explicit and implicit, may be included below.

[0023] As used herein, terms such as "first", "second", and the like may be used herein to describe various elements, but these elements need not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0024] For RA-SDT, 3rd Generation Partnership Project (3GPP) Release 17 (REL17) allows User-Plane (UP) data transmission for small data packets from INACTIVE state using uplink (UL) small data transmission for RACH-based schemes (including 2-step and 4-step RACH), e.g., Message A (MSGA) or Message 3 (MSG3). Flexible payload size is provided to be larger than the size of common control channel (CCCH) messages in Release 16 (Rel-16), which are currently possible in INACTIVE state for MSGA and MSG3 to support UP data transmission in UL. The actual payload size may depend on the network (NW) configuration. For RACH-based SDT, it supports context fetching and data forwarding (with or without anchor relocation) in INACTIVE state. For RA-SDT, it does not support Contention Free Random Access (CFRA). The separate search space is common to UEs that perform RA-SDT.

[0025] In CG-SDT, when Timing Advance (TA) is enabled, it allows transmission of UL data on pre-configured PUSCH resources by reusing configured grant type 1 and provides small data transmission via configured grant type 1 resources in INACTIVE state. Configured grant type 1 resources are configured for small data transmission in UL during INACTIVE state. UE-specific search space may be configured for UEs performing CG-SDT. After the UE starts SDT for system information changes, the UE may need to monitor paging. CG-SDT resources can be configured on either the initial BWP or a separate SDT BWP. If none of the Reference Signal Receiving Power (RSRP) of the synchronization signal block (SSB) exceeds the RSRP threshold of the CG-SDT criterion in the SDT type selection phase, the UE may select RA-SDT when the RA-SDT criterion is met.

[0026] When the UE initiates a Radio Resource Control (RRC) restart procedure from a different cell than the one where it receives the RRCRelease, the UE may release the CG-SDT resources (if stored). The Cell Radio Network Temporary Identifier (C-RNTI) previously configured during RRC_CONNECTED state may be used by the UE to monitor the Physical Downlink Control Channel (PDCCH) during the CG-SDT. The Configured Scheduling-RNTI (CS-RNTI) based dynamic retransmission mechanism may be reused for the CG-SDT. It is for further study whether the CS-RNTI is the same as the one previously configured in RRC_CONNECTED or a new CS-RNTI is provided to the UE.

[0027] For the purpose of CG resource selection, the UE may re-evaluate the SSB for subsequent CG transmissions. What happens if there is no valid SSB or if no samples of candidate beam detection are available is for further study. The CG-SDT configuration may include several parameters, which may include a new TA timer in RRC_INACTIVE, an RSRP change threshold for the TA validation mechanism in SDT, and / or an SSB RSRP threshold for beam selection (the UE selects a beam and associated CG resources for data transmission). Whether these parameters are common to multiple CG-SDT configurations or common per CG-SDT configuration is for further study.

[0028] During the SDT procedure, the UE may perform Packet Data Convergence Protocol (PDCP) re-establishment implicitly without any explicit indication of PDCP re-establishment. Whether Robust Header Compression (ROHC) continuity should be supported may be explicitly configured by the network. In the case of SDT, the UE may not support PDCP duplexing and connected mode Discontinuous Reception (DRX), but may support Power Headroom Report (PHR) function.

[0029] For SDT, Scheduling Request (SR) resources cannot be configured. In this case, when a Buffer Status Report (BSR) is triggered by SDT data, the UE may trigger a Random Access (RA) because SR resources are not available. For example, during the CG transmission phase, after the UE receives a response from the NW, the UE may trigger a legacy RACH procedure because there are no UL resources. No Media Access Control (MAC) Protocol Data Unit (PDU) reconstruction may be required. Whether RA-SDT RA resources can be used for subsequent data is a topic for further study.

[0030] As an example, the UE may initiate a RACH procedure if there are no eligible SSBs when performing SSB evaluation, when TA is disabled, and / or when SR is triggered due to lack of UL resources. If CG-SDT resources are configured on a dedicated BWP and there are no RA resources configured on the dedicated BWP, the UE may need to switch to an initial BWP to perform the RACH procedure.

[0031] For example, at the start of an RA procedure on a serving cell, after selecting a carrier for the RA procedure, for the selected carrier of this serving cell, the MAC entity of the UE may switch the active UL BWP to the BWP indicated by the initialUplinkBWP if the PRACH occasion is not configured for the active UL BWP. If the serving cell is a special cell (SpCell), the MAC entity may switch the active DL BWP to the BWP indicated by the initialDownlinkBWP. If the PRACH occasion is configured for the active UL BWP, the MAC entity may switch the active DL BWP to the DL BWP with the same bwp-Id as the active UL BWP when the serving cell is a special cell (SpCell), if the active DL BWP does not have the same bwp-Id as the active UL BWP. The MAC entity may stop the bwp-InactivityTimer associated with the active DL BWP of this serving cell, if it is running. If the serving cell is a secondary cell (SCell), the MAC entity may stop the bwp-InactivityTimer associated with the active DL BWP of the SpCell, if running. The MAC entity may perform an RA procedure for the active DL BWP of the SpCell and the active UL BWP of this serving cell.

[0032] Additionally, a UE in CONNECTED mode with grant configured may trigger SR if no SR mask is configured for the logical channel (LCH) that triggered a normal BSR. If no mask is configured, this may not be an issue in CONNECTED mode, since a dedicated SR is usually configured for CONNECTED mode. However, it may not be applicable in INACTIVE mode during SDT procedures. If SR is triggered when SR mask is set to false during INACTIVE mode, unnecessary RA procedures and further BWP switching may occur during CG-SDT procedures, even though CG-SDT resources are still available.

[0033] An exemplary embodiment of the present disclosure provides an SR and RA triggering enhancement scheme for SDT to avoid unnecessary SR and / or RA triggering and to avoid unnecessary BWP switching. In one aspect, for SR triggering enhancement, a terminal device (e.g., UE) capable of CG-SDT receives from a network device (e.g., base station) a configuration of one or more configured grant (CG) resources for an SDT procedure and a list of data radio bearers (DRBs) associated with respective logical channels (LCHs) for which SDT over at least one of the one or more CG resources is permitted. After a terminal device in an inactive mode, such as an RRC_INACTIVE mode, initiates an SDT procedure, the terminal device determines whether SDT over at least one of the one or more CG resources of the LCH that triggered the buffer status report (BSR) is permitted. If SDT of the LCH is permitted, the terminal device determines whether to apply a scheduling request (SR) mask configuration to the LCH.

[0034] In some example embodiments, if the terminal device determines that at least one of the CG resources is valid, the terminal device determines that the SR mask configuration should not be applied to the LCH. As a result, the terminal device may bypass the SR mask. Alternatively, if the SR mask is set to false in a connected mode, such as an RRC_CONNECTED mode, the terminal device may set the SR mask to true. Thus, unnecessary SR triggering during the SDT procedure may be prevented.

[0035] In another aspect, in the case of RA trigger enhancement, a terminal device capable of CG-SDT may delay the initiation of an RA procedure when the terminal device determines that an RA procedure is necessary, thereby preventing unnecessary RA triggers.

[0036] In this way, unnecessary SR and RA triggering may be prevented, thereby saving power consumption, reducing signaling overhead, and improving system efficiency.

[0037] FIG. 1 illustrates an example environment 100 in which example embodiments of the present disclosure may be practiced.

[0038] Environment 100 includes terminal device 110 and network device 120, which may be part of a communication network and may be in communication with each other. It should be understood that two devices are shown in environment 100 for illustrative purposes only, without implying any limitation to the scope of the disclosure. Any suitable number of terminal devices and network devices may be included in environment 100.

[0039] The terminal device 110 may communicate with the network device 120 or other terminal devices directly or via the network device 120 . Communications within environment 100 may be in accordance with any suitable communications standard or protocol, now in existence or later developed, such as Universal Mobile Telecommunications System (UMTS), long term evolution (LTE), LTE-Advanced (LTE-A), fifth generation New Radio (5G NR), Wireless Fidelity (Wi-Fi and Worldwide Interoperability for Microwave Access (WiMAX) standards, and may be in accordance with any suitable communications standard or protocol, e.g., Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), time division multiplexing (TDM), frequency division multiplexing (FDM), code division multiplexing (CDM), Bluetooth, ZigBee, and machine type communications. Any suitable communications technology may be employed, including mobile broadband (MTC), enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra-reliable low latency communication (URLLC), Carrier Aggregation (CA), Dual Connection (DC), and New Radio Unlicensed (NR-U) technologies.

[0040] Terminal device 110 may receive a configuration of one or more CG resources for an SDT procedure during an inactive state or mode (e.g., RRC_INACTIVE) from network device 120. Terminal device 110 further receives a list of DRBs associated with each LCH for which SDT over at least one of the one or more CG resources is allowed from network device 120. In various exemplary embodiments, terminal device 110 attempts to avoid unnecessary SR and / or RA triggers to conserve power consumption and improve system efficiency.

[0041] Some exemplary embodiments for SR trigger enhancement are described below with reference to FIG.

[0042] FIG. 2 illustrates a flowchart of an example SR trigger enhancement method 200 at a terminal device 110, according to some example embodiments of the present disclosure.

[0043] 2, in block 205, the terminal device 110 receives from the network device 120 a configuration of one or more CG resources for an SDT procedure and a list of DRBs associated with each LCH for which SDT is allowed via at least one of the one or more CG resources. The configuration of one or more CG resources may be used by the terminal device 110 in an inactive mode to initiate a connection resumption attempt for the SDT. The CG resources may be configured on a dedicated BWP or an initial BWP.

[0044] In block 210, the terminal device 110 initiates an SDT procedure. In block 215, if the terminal device 110 determines that a BSR is triggered, the terminal device 110 determines whether an SR mask configuration should be applied to the LCH configured for SDT.

[0045] For example, in some exemplary embodiments, when the terminal device 110 is in the CONNECTED mode, the terminal device 110 may receive from the network device 120 a configuration of an SR mask for the LCH or a DRB associated with the LCH for SDT. The SR mask (or SR-mask) can be set to be true or false. Traditionally, during an SDT procedure in an active mode, if SR-mask=true, SR is not triggered, and if SR-mask=false, SR is triggered. The SR-mask configuration stored from the CONNECTED mode may continue to be used in the INACTIVE mode. If the SR-mask has not been stored from the CONNECTED mode, the default value of the SR-mask is false. Thus, if SR-mask=false, an SR is triggered during the CG-SDT procedure, even though at least one of the CG-SDT resources is still available, and unnecessary RAs are triggered.

[0046] According to some example embodiments of the present disclosure, the terminal device 110 may determine whether to apply the SR mask based on whether SDT via at least one of the one or more CG resources of the LCT that triggered the BSR is allowed. If the LCH is allowed, the terminal device 110 may determine that the SR mask configuration is not applied, or alternatively, may consider it to be set to true. Otherwise, if the LCH is not allowed, the terminal device 110 may determine that the SR mask is applied, or alternatively, may consider it to be set to false. In other words, regardless of the SR mask configuration stored for the LCH, during the SDT procedure, the BSR does not trigger SR when triggered by an LCH for which SDT via at least one of the one or more CG resources is allowed, and the BSR triggers SR when triggered by an LCH for which SDT via at least one of the one or more CG resources is not allowed. If SR is then triggered, there will be no dedicated SR resource available during SDT in INACTIVE mode, resulting in an RA procedure. For example, if the terminal device 110 determines that at least one of the one or more CG resources is valid, the terminal device 110 determines that the SR mask configuration should not be applied. For example, the terminal device 110 may not consider the SR mask configuration to bypass the SR mask. Thus, even if the SR mask of the LCH is configured and stored as false during the CONNCECTED mode, the terminal device 110 does not trigger SR.

[0047] In some exemplary embodiments, the SR masks used in CONNCECTED and INACTIVE modes may be different without explicit reconfiguration. For example, terminal device 110 may set the SR mask to true for LCHs or data bearers for SDT procedures regardless of the SR mask configuration stored in CONCECTED mode.

[0048] In some example embodiments, if the LCH-triggered BSR is permitted via at least one of the CG-SDT resources, then without considering the SR mask configuration, SR is not triggered as long as there is a valid SSB in the CG-SDT. Alternatively or additionally, if the CG-SDT resource associated with the LCH-triggered BSR is not valid (e.g., there is no valid SSB associated with the available CG-SDT resource), then SR is not triggered unless there are no valid CG-SDT resources at all.

[0049] Thus, unnecessary SR triggering may be avoided during the SDT procedure, thereby saving power consumption at the terminal device 110. Furthermore, signaling overhead may be reduced and system efficiency may be improved.

[0050] As described above, during a CG-SDT procedure, if there are no eligible SSBs when performing SSB evaluation, when TA is disabled, and / or when SR is triggered due to lack of UL resources, the terminal device 110 may initiate an RA procedure. According to some example embodiments of the present disclosure, the terminal device 110 may delay initiation of the RA procedure to reduce resource consumption, increase resource utilization, and further improve system efficiency.

[0051] Some example embodiments for RA trigger enhancement are described below with reference to FIG.

[0052] FIG. 3 illustrates a flowchart of an example RA trigger enhancement method 300 at a terminal device 110, according to some example embodiments of the present disclosure.

[0053] As shown in FIG. 3, in block 305, the terminal device 110 receives from the network device 120, similar to block 205 shown in FIG. 2, a configuration of one or more CG resources for the SDT procedure and a list of DRBs associated with each LCH for which SDT via at least one of the one or more CG resources is permitted. Then, in block 310, if the terminal device 110 determines that an RA procedure should be initiated, the terminal device 110 determines whether the initiation of the RA procedure should be delayed. For example, when performing SSB evaluation, when there is no eligible SSB, when TA is disabled, and / or when SR is triggered due to lack of UL resources, the terminal device 110 determines that the RA procedure should be initiated. In this situation, the terminal device 110 determines whether the RA procedure should be delayed.

[0054] In some exemplary embodiments, if there is no eligible SSB when SSB evaluation is performed, the terminal device 110 may decide to delay the RA trigger to avoid immediately triggering beam or radio link failure recovery. This is because if there is any sudden (and short-lived) obstruction or fade, the beam or radio link failure may recover quickly. In this case, the delay may avoid unnecessary RA triggering, thereby reducing power consumption, reducing network capacity, and improving system efficiency.

[0055] In some exemplary embodiments, the RA procedure may be delayed or differentiated depending on whether the CG-SDT resource or the ongoing SDT procedure is on a dedicated BWP without RACH configuration. For example, a delay may be applied if the CG-SDT resource is configured on a dedicated BWP. If the CG-SDT runs on an initial BWP, the terminal device 110 may determine that the RA procedure is triggered immediately without delay. The RA trigger in the absence of a valid SSB in the CG-SDT may be delayed using a timer (or counter) or may be delayed up to the number of candidate beam detections (e.g., the number of samples of candidate beam detections) or the number of CG occasions to avoid unnecessary BWP switching.

[0056] When TA is disabled, as described above, the RA procedure is conventionally triggered upon expiration of a time alignment timer (TAT). In some exemplary embodiments, the RA trigger may take into account both TAT expiration and data available in the buffer of the terminal device 110. For example, when TA is disabled, if there is data to be transmitted in the buffer of the terminal device 110, the RA may be delayed. Thus, when TA becomes disabled, an RA is triggered if there is UL data available for transmission in the buffer. That is, an RA procedure is not immediately initiated when the TAT expires.

[0057] The available data in the buffer may be taken into account along with the validity of the SSB. For example, if there is no valid SSB in the CG-SDT, the terminal device 110 will not initiate an RA procedure until data to be transmitted arrives in the buffer.

[0058] In some exemplary embodiments, the terminal device 110 may delay the RA procedure until it receives an instruction to trigger the RA from the network device 120. For example, the terminal device 110 may continue the dedicated BWP unless it receives a PDCCH order from the NW side to start the RA procedure. Delaying the RA trigger may improve system efficiency by avoiding unnecessary BWP switching and recovery of beam and / or radio link failures.

[0059] FIG. 4 is a simplified block diagram of a device 400 suitable for implementing example embodiments of the present disclosure.

[0060] As shown, the device 400 includes a processor 410, a memory 420 coupled to the processor 410, a communication module 430 coupled to the processor 410, and a communication interface (not shown) coupled to the communication module 430. The memory 420 stores at least one program 440. The communication module 430 is for two-way communication, e.g., via multiple antennas. The communication interface may represent any interface necessary for communication.

[0061] The program 440 is assumed to include program instructions that, when executed by the associated processor 410, enable the device 400 to operate according to exemplary embodiments of the present disclosure, as described herein with reference to Figures 1-3. The exemplary embodiments of the present disclosure may be implemented by computer software executable by the processor 410 of the device 400, or by hardware, or by a combination of software and hardware. The processor 410 may be configured to implement various exemplary embodiments of the present disclosure.

[0062] The memory 420 can be of any type suitable for a local technical network and can be implemented using any suitable data storage technology, such as, by way of non-limiting example, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. Although only one memory 420 is shown in the device 400, there may be several physically separate memory modules in the device 400. The processor 410 can be of any type suitable for a local technical network and can include, by way of non-limiting example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 400 may have multiple processors, such as application-specific integrated circuit chips slaved in time to a clock that synchronizes the main processor.

[0063] When the device 400 functions as the terminal device 110, the processor 410 and the communication module 430 may cooperate to implement the methods 200 and 300 described above with reference to Figures 1-3. All operations and features described above with reference to Figures 1-3 are equally applicable to the device 400 and have similar effect. Details are omitted for the sake of brevity.

[0064] In general, various exemplary embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the exemplary embodiments of the present disclosure have been illustrated and described as block diagrams, flow charts, or using some other graphical depictions, it should be understood that the blocks, apparatus, systems, techniques, or methods described herein may be implemented, by way of non-limiting examples, in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controllers or other computing devices, or any combination thereof.

[0065] The present disclosure also provides at least one computer program product tangibly stored in a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions that execute on a target real or virtual processor device, such as those included in a program module, to execute the method 200 or 300 described above with reference to FIG. 1-FIG. 3. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split among program modules as desired in various exemplary embodiments. The machine-executable instructions of the program modules may be executed in a local device or in a distributed device. In a distributed device, the program modules may be located in both local and remote storage media.

[0066] The program codes for carrying out the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, a special purpose computer, or other programmable data processing apparatus such that, when executed by the processor or controller, the functions / operations defined in the flowcharts and / or block diagrams are performed. The program codes may be executed entirely on the machine, partly on the machine as a stand-alone software package, partly on the machine and partly on a remote machine, or entirely on a remote machine or server.

[0067] In the context of the present disclosure, computer program code or associated data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals and computer readable media.

[0068] The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the above. More specific examples of the computer-readable storage medium may include an electrical connection with one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0069] Furthermore, although operations are shown in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown, or sequentially, or that all of the operations shown be performed in order to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although details of certain specific implementations are included in the above discussion, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to certain exemplary embodiments. Certain features that are described in the context of separate exemplary embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple exemplary embodiments separately or in any suitable subcombination.

[0070] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the present disclosure, as defined by the appended claims, is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms for implementing the claims.

[0071] Various exemplary embodiments of the present technique have been described. In addition to or as an alternative to the above, the following examples are described. Features described in any of the following examples can be utilized with any of the other examples described herein.

[0072] In some aspects, a terminal device includes at least one processor and at least one memory having computer program code configured to cause the device, using the at least one processor, to receive from a network device a configuration of one or more configured grant resources for a small data transmission (SDT) procedure and a list of one or more data radio bearers (DRBs) associated with each logical channel for which SDT is allowed over at least one of the one or more configured grant resources, initiate an SDT procedure in an inactive mode, and determine, according to a determination that a buffer status report (BSR) is triggered, whether a scheduling request mask configuration should be applied to the logical channel configured for SDT.

[0073] In some example embodiments, in response to determining that a BSR is triggered by a logical channel for which SDT via at least one of the one or more configured grant resources is permitted, the terminal device is caused to determine that a scheduling request mask configuration should not be applied or to determine whether a scheduling request mask configuration should be applied by setting a scheduling request mask for a scheduling request of a logical channel configured for SDT to true and applying the scheduling request mask.

[0074] In some example embodiments, in response to determining that a BSR is triggered by a logical channel for which SDT over at least one of the one or more configured grant resources is not permitted, the method causes the terminal device to determine whether a scheduling request mask configuration should be applied by determining that a scheduling request mask configuration should be applied.

[0075] In some demonstrative embodiments, the configuration of one or more configured grant resources for a small data transmission (SDT) procedure is for use by a terminal device in an inactive mode to initiate a connection resumption attempt for the SDT.

[0076] In some aspects, a terminal device includes at least one processor and at least one memory having computer program code configured to cause the device, using the at least one processor, to receive from the network device a configuration of one or more configured grant resources for a small data transmission (SDT) procedure and a list of one or more data radio bearers (DRBs) associated with each logical channel for which SDT is allowed over at least one of the one or more configured grant resources, and in response to determining that a random access procedure should be initiated, determine whether initiation of the random access procedure should be delayed.

[0077] In some demonstrative embodiments, the method causes the terminal device to determine whether initiation of a random access procedure should be delayed by determining that initiation of the random access procedure should be delayed in response to at least one of an SDT procedure initiated on a dedicated bandwidth portion (BWP), disabling of a synchronization signal block (SSB) associated with the dedicated BWP in one or more configured grant resources on the dedicated BWP, or disabling of a timing advance.

[0078] In some exemplary embodiments, the terminal device is further configured to at least one of delaying initiation of the random access procedure using a timer until the number of candidate beam detections or the number of configured grant occasions, or until an instruction to initiate the random access procedure is received from the network device.

[0079] In some exemplary embodiments, the terminal device is further caused to initiate a random access procedure if there is data to be transmitted in a buffer of the terminal device when the timing advance has expired or when there is no valid SSB.

[0080] In some demonstrative embodiments, in response to an SDT procedure being initiated on an initial BWP, the terminal device is caused to determine whether initiation of the random access procedure should be delayed by determining that initiation of the random access procedure should not be delayed.

[0081] In some demonstrative embodiments, the terminal device is further configured to initiate a random access procedure based on at least one of invalidation of an SSB associated with one or more configured grant resources on the initial BWP or invalidation of a timing advance.

[0082] In some aspects, the method includes receiving, by a terminal device, from a network device, a configuration of one or more configured grant resources for a small data transmission (SDT) procedure and a list of one or more data radio bearers (DRBs) associated with respective logical channels for which SDT is allowed via at least one of the one or more configured grant resources, initiating the SDT procedure in an inactive mode, and determining, according to a determination that a buffer status report (BSR) is triggered, whether a scheduling request mask configuration should be applied to the logical channels configured for SDT.

[0083] In some demonstrative embodiments, determining whether the scheduling request mask configuration should be applied includes, in response to determining that the BSR is triggered by a logical channel for which SDT is allowed over at least one of the one or more configured grant resources, determining that the scheduling request mask configuration should not be applied or setting the scheduling request mask for the scheduling request of the logical channel configured for SDT to true and applying the scheduling request mask.

[0084] In some demonstrative embodiments, determining whether a scheduling request mask configuration should be applied includes determining that a scheduling request mask configuration should be applied in response to determining that a BSR is triggered by a logical channel for which SDT over at least one of the one or more configured grant resources is not allowed.

[0085] In some demonstrative embodiments, the configuration of one or more configured grant resources for a small data transmission (SDT) procedure is for use by a terminal device in an inactive mode to initiate a connection resumption attempt for the SDT.

[0086] In some aspects, the method includes receiving, by a terminal device, from a network device, a configuration of one or more configured grant resources for a small data transmission (SDT) procedure and a list of one or more DRBs associated with each logical channel for which SDT is allowed via at least one of the one or more configured grant resources, and determining whether initiation of the random access procedure should be delayed in response to determining that a random access procedure should be initiated.

[0087] In some demonstrative embodiments, determining whether initiation of the random access procedure should be delayed includes determining that initiation of the random access procedure should be delayed in response to at least one of an SDT procedure initiated on a dedicated bandwidth portion (BWP), disabling of a synchronization signal block (SSB) associated with the dedicated BWP in one or more configured grant resources on the dedicated BWP, or disabling of a timing advance.

[0088] In some demonstrative embodiments, the method further includes at least one of delaying initiation of the random access procedure using a timer until a number of candidate beam detections or a configured number of grant occasions, or until an instruction to initiate the random access procedure is received from the network device.

[0089] In some demonstrative embodiments, the method further includes initiating a random access procedure if there is data to be transmitted in a buffer of the terminal device when the timing advance has expired or when there is no valid SSB.

[0090] In some demonstrative embodiments, determining whether initiation of the random access procedure should be delayed includes determining that initiation of the random access procedure should not be delayed in response to an SDT procedure being initiated on the initial BWP.

[0091] In some demonstrative embodiments, the method further includes initiating a random access procedure based on at least one of invalidation of an SSB associated with one or more configured grant resources on the initial BWP or invalidation of a timing advance.

[0092] In some aspects, the apparatus includes means for receiving, by a terminal device, from a network device, a configuration of one or more configured grant resources for a small data transmission (SDT) procedure and a list of one or more data radio bearers (DRBs) associated with each logical channel for which SDT is allowed via at least one of the one or more configured grant resources, means for initiating an SDT procedure in an inactive mode, and means for determining, according to a determination that a buffer status report (BSR) is triggered, whether a scheduling request mask configuration should be applied to the logical channel configured for SDT.

[0093] In some demonstrative embodiments, the means for determining whether a scheduling request mask configuration should be applied includes, in response to determining that a BSR is triggered by a logical channel for which SDT over at least one of the one or more configured grant resources is allowed, means for determining that the scheduling request mask configuration should not be applied or means for setting the scheduling request mask for the scheduling request of the logical channel configured for SDT to true and applying the scheduling request mask.

[0094] In some demonstrative embodiments, the means for determining whether a scheduling request mask configuration should be applied includes means for determining that a scheduling request mask configuration should be applied in response to determining that a BSR is triggered by a logical channel for which SDT over at least one of the one or more configured grant resources is not allowed.

[0095] In some demonstrative embodiments, the configuration of one or more configured grant resources for a small data transmission (SDT) procedure is for use by a terminal device in an inactive mode to initiate a connection resumption attempt for SDT.

[0096] In some aspects, the apparatus includes means for receiving, by a terminal device, from a network device, a configuration of one or more configured grant resources for a small data transmission (SDT) procedure and a list of one or more DRBs associated with each logical channel for which SDT via at least one of the one or more configured grant resources is allowed, and means for determining, in response to determining that the random access procedure should be initiated, whether initiation of the random access procedure should be delayed.

[0097] In some demonstrative embodiments, the means for determining whether initiation of a random access procedure should be delayed includes means for determining that initiation of the random access procedure should be delayed in response to at least one of an SDT procedure initiated on a dedicated bandwidth portion (BWP), disabling of a synchronization signal block (SSB) associated with the dedicated BWP in one or more configured grant resources on the dedicated BWP, or disabling of a timing advance.

[0098] In some demonstrative embodiments, the apparatus further includes at least one of means for delaying initiation of the random access procedure using a timer, means for delaying initiation of the random access procedure until a number of candidate beam detections or a configured number of grant occasions, or means for delaying initiation of the random access procedure until receiving an instruction from a network device to initiate the random access procedure.

[0099] In some demonstrative embodiments, the apparatus further includes means for initiating a random access procedure if there is data to be transmitted in a buffer of the terminal device when the timing advance has expired or when there is no valid SSB.

[0100] In some demonstrative embodiments, the means for determining whether initiation of the random access procedure should be delayed includes means for determining, in response to an SDT procedure being initiated on the initial BWP, that initiation of the random access procedure should not be delayed.

[0101] In some demonstrative embodiments, the apparatus further includes means for initiating a random access procedure based on at least one of disabling an SSB associated with one or more configured grant resources on the initial BWP or disabling a timing advance in response to an SDT procedure initiated on the initial BWP.

[0102] In some aspects, a computer-readable storage medium includes program instructions stored thereon that, when executed by a processor of the device, cause the device to perform methods according to certain example embodiments of the present disclosure.

Claims

1. A terminal device for communications, comprising: receiving from a network device (120) a configuration of one or more configured grant (CG) resources for a small data transmission (SDT) procedure and a list of one or more data radio bearers (DRBs) associated with each logical channel for which SDT is allowed via said at least one of said one or more CG resources; While the CG-SDT procedure is in progress, if there is no valid SSB associated with the one or more CG-SDT resources, check whether data to be transmitted associated with at least one of the one or more DRBs is available in a buffer of the terminal device, and if data to be transmitted associated with at least one of the one or more DRBs is available in the buffer, initiate a random access procedure; The terminal device is configured to:

2. While the CG-SDT procedure is in progress, if there is no valid SSB associated with the one or more CG-SDT resources, checking whether data to be transmitted associated with at least one of the one or more DRBs is available in a buffer of the terminal device, and not initiating the random access procedure if data to be transmitted associated with at least one of the one or more DRBs is not available in the buffer; A terminal device as claimed in claim 1, configured to:

3. A terminal device according to claim 1 , configured to decide whether to delay the initiation of the random access procedure by not initiating the random access procedure.

4. determining that the random access procedure may be initiated by determining that there is no valid SSB associated with the one or more CG-SDT resources; in response to determining that the random access procedure may be initiated, determining whether to delay initiation of the random access procedure by considering available data associated with at least one of the one or more DRBs in the buffer; A terminal device according to claim 3, configured to:

5. delaying initiation of the random access procedure until data to be transmitted associated with at least one of the one or more DRBs is available in the buffer and there are no valid SSBs associated with the CG-SDT procedure. A terminal device according to claim 4, configured to:

6. determining that there is no valid SSB associated with the one or more CG-SDT resources when it is determined that the reference signal received power (RSRP) exceeds an RSRP threshold that there is no SSB associated with the one or more CG-SDT resources; A terminal device according to any one of claims 1 to 5, configured so as to

7. A terminal device according to any one of claims 1 to 6, wherein the random access procedure is different from a random access SDT (RA-SDT) procedure.

8. 1. A method comprising: receiving, at a terminal device (110), from a network device (120), a configuration of one or more configured grant (CG) resources for a small data transmission (SDT) procedure and a list of one or more data radio bearers (DRBs) associated with each logical channel for which SDT is allowed via said at least one of said one or more CG resources; While the CG-SDT procedure is in progress, If there is no valid SSB associated with the one or more CG-SDT resources, checking whether data to be transmitted associated with at least one of the one or more DRBs is available in a buffer of the terminal device, and initiating a random access procedure if data to be transmitted associated with at least one of the one or more DRBs is available in the buffer; The method comprising:

9. While the CG-SDT procedure is in progress, If there is no valid SSB associated with the one or more CG-SDT resources, checking whether data to be transmitted associated with at least one of the one or more DRBs is available in a buffer of the terminal device, and if data to be transmitted associated with at least one of the one or more DRBs is not available in the buffer, not initiating the random access procedure; The method of claim 8 further comprising:

10. determining whether to delay the initiation of the random access procedure by not initiating the random access procedure; The method according to any one of claims 8 to 9, further comprising:

11. determining that the random access procedure may be initiated by determining that there is no valid SSB associated with the one or more CG-SDT resources; in response to determining that the random access procedure may be initiated, determining whether to delay initiation of the random access procedure by considering available data associated with at least one of the one or more DRBs in the buffer; The method of claim 10 further comprising:

12. delaying initiation of the random access procedure until data to be transmitted associated with at least one of the one or more DRBs is available in the buffer and there are no valid SSBs associated with the CG-SDT procedure. The method of claim 11 further comprising:

13. determining that there is no valid SSB associated with the one or more CG-SDT resources when it is determined that a reference signal received power (RSRP) that there is no SSB associated with the one or more CG-SDT resources exceeds an RSRP threshold; The method of any one of claims 8 to 12, further comprising:

14. The method according to any one of claims 8 to 13, wherein the random access procedure is different from a random access SDT (RA-SDT) procedure.

15. A computer readable storage medium having stored thereon program instructions which, when executed by a processor of a device, cause the device to perform a method according to any one of claims 8 to 14.

Images