Scheduling request and random access trigger for sdt

Abstract

To provide a device, method, apparatus, and computer-readable storage medium for triggering a scheduling request (SR) and random access (RA) for small data transmission (SDT).SOLUTION: In a system, a terminal device receives, from a network device, a configuration of one or more configured grant (CG) resources for the SDT procedure, and a list of one or more data radio bearers (DRB) associated with each logical channel (LCH) for which SDT via at least one of the one or more CG resources is permitted. After the terminal device initiates the SDT procedure in an inactive mode and determines that a buffer status report (BSR) is triggered, the terminal device determines whether the SR mask configuration should be applied to the LCH configured for the SDT.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] Exemplary embodiments of the present disclosure generally relate to the field of communications, and more particularly, to devices, methods, apparatuses, and computer-readable storage media for triggering scheduling requests (SRs) and random access (RA) for small data transmission (SDT).

Background Art

[0002] A user equipment (UE) in an inactive state can perform SDT to reduce signaling overhead and latency by transitioning from the inactive state to a connected state. Two general types of SDT include random access channel (RACH)-based SDT (RACH-based SDT) and configured grant-based SDT (CG-SDT). In the case of CG-SDT, one or more CG resources can be configured either in an initial bandwidth part (BWP) or in a separate SDT BWP. If none of the reference signal receiving power (RSRP) of the synchronization signal block (SSB) associated with the CG resource exceeds the CG-SDT reference RSRP threshold during the SDT type selection phase, the UE can select RA-SDT when the RA-SDT criteria are met.

[0003] During the SDT procedure, a scheduling request (SR) can be triggered due to a lack of UL resources. If SR resources are not configured for SDT, when a buffer status report (BSR) is triggered by SDT data, the UE may trigger random access (RA) because the SR resources are not available. Triggering of SR and RA can induce unnecessary BWP switching.

Summary of the Invention

[0004] Generally, exemplary embodiments of the present disclosure provide a device, method, apparatus, and computer-readable storage medium for triggering SR and RA for 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 are configured to cause the at least one processor to receive, from a network device, 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 (LCH) for which SDT is permitted via at least one of the one or more CG resources. Further, the terminal device is configured to start an SDT procedure in a non-active mode and determine whether a configuration of a scheduling request mask should be applied to an LCH configured for SDT according to a determination that a buffer status report (BSR) is triggered.

[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. The at least one memory and the computer program code are configured to cause the at least one processor to receive, 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 is permitted via at least one of the one or more CG resources. Further, in response to a determination that a random access procedure should be started, the terminal device is configured to determine whether the start of the random access procedure should be delayed.

[0007] In a third aspect, a method is provided. In the method, 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 is permitted via at least one of the one or more CG resources. When the terminal determines that a BSR is triggered after the terminal device starts an SDT procedure in an inactive mode, the terminal device determines whether a configuration of a scheduling request mask should be applied to an LCH configured for SDT.

[0008] In a fourth aspect, a method is provided. In the method, 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 is permitted via at least one of the one or more CG resources. When the terminal device determines that a random access procedure should be started, the terminal device determines whether the start of the random access procedure should be delayed.

[0009] In a fifth aspect, an apparatus is provided that includes means for performing the method according to the third or fourth aspect.

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

[0011] It should be understood that the summary section of the invention 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] Next, several exemplary embodiments will be described with reference to the accompanying drawings.

Brief Description of the Drawings

[0013]

Figure 1

Figure 2

Figure 3

Figure 4

Modes for Carrying Out the Invention

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

[0015] Next, the principles of the present disclosure will be described with reference to some exemplary embodiments. These exemplary embodiments are merely described for illustrative purposes and are useful for those skilled in the art to understand and implement the present disclosure, but it should be understood that they do not suggest any limitation 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 shall have the same meaning as commonly understood by one of ordinary skill in the technical field to which the present disclosure pertains, 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 transmitting information wirelessly. In some exemplary 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 at a predetermined schedule when triggered by an internal event or an 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 premise equipment (CPE), sensors, metering devices, personal wearables such as wristwatches, and / or vehicles capable of communication. For purposes of explanation, some exemplary embodiments are described with reference to the 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 the present disclosure.

[0019] As used herein, the term "network device" refers to a device through which services can be provided to terminal devices within a communication network. By way of example, the network device may include a base station. As used herein, the term "base station" (BS) refers to a network device through which services can be provided to terminal devices within a communication network. The base station may include any suitable device through which a terminal device or UE can access the communication network. Examples of base stations include repeaters, access points (APs), transmission points (TRPs), Node Bs (NodeB or NB), evolved Node Bs (eNodeB or eNB), new radio technology (NR) Node Bs (gNB), remote radio units (RRUs), radio headers (RHs), remote radio heads (RRHs), low-power nodes such as femtos, picos, etc.

[0020] As used herein, the term "circuit" may refer to one or more or all of the following: (a) A circuit implementation of only hardware (such as an implementation with only analog and / or digital circuits), (b) A combination of a hardware circuit and software, for example (where applicable), (i) a combination of an analog and / or digital hardware circuit(s) and software / firmware, and (ii) any part of a hardware processor(s) and software (including a digital signal processor(s), software, and memory(ies) that cooperate to cause a device such as a mobile phone or a server to perform various functions), and (c) A hardware circuit(s) that requires software (such as firmware) to operate, and / or a processor(s) such as a microprocessor(s) or a part of a microprocessor(s), but the software may not be present if it is not necessary for operation.

[0021] This definition of a circuit applies to all uses of this term in this application, including any claims. As a further example, the term "circuit" as used in this application includes a mere hardware circuit or processor(s) (or multiple processors), or a part of a hardware circuit or processor, and an embodiment of the software and / or firmware associated therewith (or therewith). The term "circuit" also includes, for example, a baseband integrated circuit or a processor integrated circuit for a mobile device, or a similar integrated circuit within a server, a cellular base station, or other computing or base station, when applicable to an element of a particular claim.

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

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

[0024] In the case of RA-SDT, in the 3rd Generation Partnership Project (3GPP) Release 17 (REL17), uplink (UL) small data transmission for RACH-based schemes (including 2-step and 4-step RACH) is used to enable User-Plane (UP) data transmission for small data packets from the INACTIVE state, for example, using Message A (MSGA) or Message 3 (MSG3). The size of the flexible payload is provided to be larger than the size of the common control channel (CCCH) messages in Release 16 (Rel-16), which is currently possible in the INACTIVE state for MSGA and MSG3 to support UP data transmission in the UL. The actual payload size may depend on the network (NW) configuration. In the case of RACH-based SDT, fetching of context and transfer of data in the INACTIVE state (regardless of the presence or absence of anchor relocation) are supported. In the case of RA-SDT, contention-free random access (CFRA) is not supported. A separate search space is common to UEs executing RA-SDT.

[0025] In CG-SDT, when timing advance (TA) is valid, UL data transmission on pre-configured PUSCH resources is permitted by reusing the configured grant type 1, and small data transmission is provided via the grant type 1 resources configured in the INACTIVE state. The configured grant type 1 resources are configured for small data transmission on UL during the INACTIVE state. A UE-specific search space may be configured for the UE that performs CG-SDT. After the UE starts SDT for system information change, the UE may need to monitor paging. The CG-SDT resources can be configured either on the initial BWP or on a separate SDT BWP. If neither of the reference signal receiving power (RSRP) of the synchronization signal block (SSB) exceeds the CG-SDT reference RSRP threshold in the selection phase of the SDT type, the UE may select RA-SDT if the RA-SDT criteria are met.

[0026] If the UE starts the Radio Resource Control (RRC) resume procedure from a cell different from the cell where it receives RRCRelease, the UE may release the CG-SDT resources (if stored). During the RRC_CONNECTED state, the UE may monitor the Physical Downlink Control Channel (PDCCH) in the CG-SDT using the Cell Radio Network Temporary Identifier (C-RNTI) previously configured for the UE. The dynamic retransmission mechanism based on the Configured Scheduling-RNTI (CS-RNTI) can be reused for the CG-SDT. 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 is a further issue for consideration.

[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 samples for candidate beam detection are not available is a further issue for consideration. 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 validity confirmation mechanism in the SDT, and / or an SSB RSRP threshold for beam selection (for the UE to select a beam and associated CG resources for data transmission). Whether these parameters are common to multiple CG-SDT configurations or are common for each CG-SDT configuration is a further issue for consideration.

[0028] During the SDT procedure, the UE may implicitly perform Packet Data Convergence Protocol (PDCP) re-establishment without explicitly indicating an indication of PDCP re-establishment. Whether to support Robust Header Compression (ROHC) continuity may be explicitly configured by the network. In the case of SDT, PDCP duplication and discontinuous reception (DRX) in the connected mode cannot be supported, but the Power Headroom Report (PHR) function can be supported.

[0029] In the case of SDT, the scheduling request (SR) resources cannot be configured. In this case, when the buffer status report (BSR) is triggered by SDT data, since the SR resources are not available, the UE may trigger random access (RA). For example, during the CG transmission phase, after the UE receives a response from the NW, since there are no UL resources, the UE may trigger the legacy RACH procedure. Reconstruction of the media access control (MAC) protocol data unit (PDU) may not be required. Whether the RA-SDT RA resources can be used for subsequent data is a further research issue.

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

[0031] For example, at the start of the RA procedure on a serving cell, after selecting a carrier for the RA procedure, for the selected carrier of this serving cell, if the PRACH occasion is not configured for the active UL BWP, the UE's MAC entity may switch the active UL BWP to the BWP indicated by initialUplinkBWP. If the serving cell is a special cell (SpCell), the MAC entity may switch the active DL BWP to the BWP indicated by initialDownlinkBWP. If the PRACH occasion is configured for the active UL BWP, when the serving cell is a special cell (SpCell) and the active DL BWP does not have the same bwp-Id as the active UL BWP, the MAC entity may switch the active DL BWP to a DL BWP having 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 it is running. The MAC entity may execute the RA procedure on the active DL BWP of the SpCell and the active UL BWP of this serving cell.

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

[0033] Exemplary embodiments of the present disclosure provide a trigger enhancement scheme for SR and RA for SDT to avoid unnecessary SR and / or RA triggers and avoid unnecessary BWP switching. In one aspect, in the case of SR trigger enhancement, a terminal device (such as a UE) capable of CG-SDT receives a configuration of one or more configured grant (CG) resources for the SDT procedure from a network device (such as a base station), and a list of data radio bearers (DRBs) associated with each logical channel (LCH) for which SDT is permitted via at least one of the one or more CG resources. After a terminal device in an inactive mode, such as the RRC_INACTIVE mode, starts the SDT procedure, the terminal device determines whether SDT via at least one of the one or more CG resources is permitted for the LCH that triggered the buffer status report (BSR). If SDT for the LCH is permitted, the terminal device determines whether to apply the configuration of the scheduling request (SR) mask to the LCH.

[0034] In some exemplary embodiments, if the terminal device determines that at least one of the CG resources is valid, the terminal device determines that the configuration of the SR mask 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 the RRC_CONNECTED mode, the terminal device may set the SR mask to true. Thus, unnecessary SR triggers during the SDT procedure can be prevented.

[0035] In another aspect, in the case of RA trigger enhancement, a terminal device capable of CG-SDT delays the start of the RA procedure when the terminal device determines that the RA procedure is necessary. Therefore, unnecessary RA triggers can also be prevented.

[0036] In this way, by preventing unnecessary SR and RA triggers, power consumption can be saved, signaling overhead can be reduced, and system efficiency can be improved.

[0037] FIG. 1 shows an exemplary environment 100 in which exemplary embodiments of the present disclosure may be implemented.

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

[0039] The terminal device 110 can communicate directly with the network device 120 or other terminal devices, or via the network device 120. Communication within the environment 100 can comply with any suitable communication standard or protocol that already exists or will be developed in the future, such as the Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Fifth Generation New Radio (5G NR), the worldwide interoperability of Wireless Fidelity (Wi-Fi) and Worldwide Interoperability for Microwave Access (WiMAX) standards, and can adopt any suitable communication technology, including, for example, 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 Communication (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) technology.

[0040] The terminal device 110 can receive from the network device 120 a configuration of one or more CG resources for an SDT procedure in an inactive state or mode (such as RRC_INACTIVE). The terminal device 110 further receives from the network device 120 a list of DRBs associated with each LCH for which SDT is permitted via at least one of the one or more CG resources. In various exemplary embodiments, the terminal device 110 attempts to avoid unnecessary SR and / or RA triggers in order to save power consumption and improve system efficiency.

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

[0042] FIG. 2 shows a flowchart of an exemplary SR trigger enhancement method 200 in a terminal device 110 according to some exemplary embodiments of the present disclosure.

[0043] As shown in FIG. 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 permitted via at least one of the one or more CG resources. The configuration of the one or more CG resources can be used by the terminal device 110 in an inactive mode to initiate a connection re-establishment attempt for SDT. The CG resources can 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 the 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. Conventionally, during the SDT procedure in the active mode, when SR-mask = true, SR is not triggered, and when SR-mask = false, SR is triggered. The SR-mask configuration stored from the CONNECTED mode can continue to be used even in the INACTIVE mode. If the SR-mask is not stored from the CONNECTED mode, the default value of the SR-mask is false. Therefore, when SR-mask = false, SR is triggered during the CG-SDT procedure, and unnecessary RAs are triggered even though at least one of the CG-SDT resources is still available.

[0046] According to some exemplary embodiments of the present disclosure, the terminal device 110 may determine whether to apply an SR mask based on whether SDT via at least one of one or more CG resources of the LCT that triggered the BSR is permitted. If LCH is permitted, the terminal device 110 may determine that the configuration of the SR mask is not applied, or alternatively, may consider it as set to true. Otherwise, if LCH is not permitted, the terminal device 110 may determine that the SR mask is applied, or alternatively, may consider it as set to false. In other words, regardless of the SR mask configuration stored for LCH, during the SDT procedure, the BSR does not trigger SR when triggered by an LCH for which SDT via at least one of one or more CG resources is permitted, and the BSR triggers SR when triggered by an LCH for which SDT via at least one of one or more CG resources is not permitted. Then, when SR is triggered, since there is no dedicated SR resource available during SDT in the INACTIVE mode, it becomes the RA procedure. For example, if the terminal device 110 determines that at least one of one or more CG resources is valid, the terminal device 110 determines that the configuration of the SR mask should not be applied. For example, the terminal device 110 may not consider the configuration of the SR mask for bypassing the SR mask. Therefore, even if the SR mask of 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 the CONNCECTED mode and the INACTIVE mode may be different without explicit reconfiguration. For example, the terminal device 110 may set the SR mask to true for LCH or the data bearer for the SDT procedure regardless of the SR mask configuration stored in the CONCECTED mode.

[0048] In some exemplary embodiments, when the BSR triggered by the LCH is permitted via at least one of the CG-SDT resources, the SR is not triggered as long as there is a valid SSB for the CG-SDT without considering the SR mask configuration. Alternatively or additionally, when the CG-SDT resources associated with the BSR triggered by the LCH are not valid (for example, when there is no valid SSB associated with the available CG-SDT resources), the SR is not triggered, except when there are no valid CG-SDT resources at all.

[0049] Therefore, during the SDT procedure, in order to avoid unnecessary SR triggers, the power consumption at the terminal device 110 can be saved. Furthermore, the signaling overhead can be reduced and the system efficiency can be improved.

[0050] As described above, during the CG-SDT procedure, when performing the SSB evaluation, when the TA is invalid, and / or when the SR is triggered due to the lack of UL resources, if there is no qualified SSB, the RA procedure can be started. According to some exemplary embodiments of the present disclosure, if the terminal device 110 delays the start of the RA procedure, the resource consumption is reduced, the resource utilization rate is increased, and the system efficiency is further improved.

[0051] Some exemplary embodiments for RA trigger enhancement will be described below with reference to FIG. 3.

[0052] FIG. 3 shows a flowchart of an exemplary RA trigger enhancement method 300 at the terminal device 110 according to some exemplary 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 the RA procedure should be started, the terminal device 110 determines whether the start of the RA procedure should be delayed. For example, when performing SSB evaluation, when TA is invalid, and / or when SR is triggered due to insufficient UL resources, if there is no qualified SSB, the terminal device 110 determines that the RA procedure should be started. In this situation, the terminal device 110 determines whether to delay the RA procedure.

[0054] In some exemplary embodiments, when there is no qualified SSB when performing SSB evaluation, the terminal device 110 may determine to delay the RA trigger to avoid immediately triggering beam or radio link failure recovery. This is because if there is some sudden (and short-term) obstacle or fade, the beam failure or radio link failure may be recovered immediately. In this case, the delay can avoid unnecessary RA triggers, thereby reducing power consumption, reducing network capacity, and improving system efficiency.

[0055] In some exemplary embodiments, the RA procedure may be delayed or differentiated according to whether the CG-SDT resource or the ongoing SDT procedure is on a dedicated BWP without RACH configuration. For example, when the CG-SDT resource is configured on a dedicated BWP, a delay may be applied. When the CG-SDT is executed on the initial BWP, the terminal device 110 may determine that the RA procedure is triggered immediately without delay. The RA trigger in the case where there is no valid SSB for CG-SDT may be delayed using a timer (or counter) to avoid unnecessary BWP switching, or may be delayed until the number of candidate beam detections (e.g., the number of samples of candidate beam detections) or the number of CG occasions.

[0056] As described above, when TA is invalid, conventionally, the RA procedure is triggered when the time alignment timer (TAT) expires. In some exemplary embodiments, the RA trigger may consider both the TAT expiration and the data available in the buffer of the terminal device 110. For example, when there is data to be transmitted to the buffer of the terminal device 110 when TA is invalid, RA may be delayed. Therefore, when TA becomes invalid and there is UL data available for transmission in the buffer, RA is triggered. That is, when the TAT expires, the RA procedure is not immediately started.

[0057] The available data in the buffer may be considered together with the validity of the SSB. For example, when there is no valid SSB for CG-SDT, the terminal device 110 does not start the RA procedure until the data to be transmitted arrives at the buffer.

[0058] In some exemplary embodiments, the terminal device 110 may delay the RA procedure until it receives an RA trigger instruction from the network device 120. For example, the terminal device 110 may continue with the dedicated BWP unless it receives a PDCCH order from the NW side to start the RA procedure. By delaying the RA trigger, unnecessary BWP switching and recovery of beams and / or radio link failures can be avoided, thereby improving system efficiency.

[0059] FIG. 4 is a simplified block diagram of a device 400 suitable for implementing an exemplary embodiment 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 bidirectional communication, for example via a plurality of antennas. The communication interface may represent any interface required for communication.

[0061] When the program 440 is executed by the associated processor 410, as described herein with reference to FIGS. 1-3, it is assumed to include program instructions that enable the device 400 to operate in accordance with an exemplary embodiment of the present disclosure. The exemplary embodiments herein 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] 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 for device 400, device 400 may have several physically distinct memory modules. 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 dedicated computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 400 may have multiple processors, such as an application-specific integrated circuit chip that is time-slaved to a clock that synchronizes the main processor.

[0063] When device 400 functions as terminal device 110, processor 410 and communication module 430 can cooperate to implement methods 200 and 300 described above with reference to FIGS. 1-3. All operations and features described above with reference to FIGS. 1-3 are equally applicable to device 400 and have similar effects. For simplicity, details are omitted.

[0064] In general, the various exemplary embodiments of the present disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, a microprocessor, or other computing device. The various aspects of the exemplary embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical description, but the blocks, devices, systems, techniques, or methods described herein can be implemented, by way of non-limiting example, in hardware, software, firmware, special-purpose circuitry or logic, general-purpose hardware or a controller or other computing device, or any combination thereof.

[0065] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions that are executed on a device, such as a physical processor or a virtual processor, that are included in a program module to perform the method 200 or 300 described above with reference to FIGS. 1-3. In general, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc. that perform a particular task or implement a particular abstract data type. The functions of the program modules may be combined or divided among the program modules as desired in the various exemplary embodiments. The machine-executable instructions of the program modules can be executed within a local device or within a distributed device. In a distributed device, the program modules can be located on both local and remote storage media.

[0066] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or a controller of a general-purpose computer, a dedicated computer, or other programmable data processing devices, so that when the program code is executed by the processor or the controller, the functions / operations defined in the flowchart and / or block diagram are executed. The program code may be executed entirely on a machine, may be executed partially on a machine as a stand-alone software package, may be executed partially on a machine and partially on a remote machine, or may be executed entirely on a remote machine or server.

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

[0068] The computer-readable medium can 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 having 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 disc read-only memory (CD-ROM), a digital versatile disc (DVD), an optical storage device, a magnetic storage device, or any suitable combination of the above.

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

[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 disclosure defined by the appended claims is not necessarily limited to the specific features or acts described above. Rather, the above specific features and acts are disclosed as exemplary 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 used in combination with any of the other examples described herein.

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

[0073] In some exemplary 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 the 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 exemplary embodiments, in response to determining that a BSR is triggered by a logical channel for which SDT via at least one of one or more configured grant resources is not permitted, the terminal device is caused to determine whether the configuration of the scheduling request mask should be applied by determining that the configuration of the scheduling request mask should be applied.

[0075] In some exemplary 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 re-establishment attempt for SDT.

[0076] In some aspects, a terminal device 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 configured to cause 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 via at least one of the one or more configured grant resources is permitted, and to determine whether the initiation of a random access procedure should be delayed in response to determining that the random access procedure should be initiated.

[0077] In some exemplary embodiments, the terminal device is caused to determine whether the start of the random access procedure should be delayed by determining that the start of the random access procedure should be delayed in response to at least one of an SDT procedure started on a dedicated bandwidth part (BWP), invalidation of a synchronization signal block (SSB) associated with the dedicated BWP in one or more configured grant resources on the dedicated BWP, or invalidation of the timing advance.

[0078] In some exemplary embodiments, the terminal device is further caused to delay the start of the random access procedure using a timer for at least one of up to the number of candidate beam detections or configured grant occasions, or until receiving an instruction from the network device to start the random access procedure.

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

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

[0081] In some exemplary embodiments, the terminal device is further caused to start the 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 the timing advance.

[0082] In some aspects, the method comprises the terminal device receiving, 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 permitted via at least one of the one or more configured grant resources; starting the SDT procedure in an inactive mode; and determining whether a configuration of a scheduling request mask should be applied to the logical channels configured for SDT according to a determination that a buffer status report (BSR) is triggered.

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

[0084] In some exemplary embodiments, determining whether a configuration of a scheduling request mask should be applied comprises, in response to determining that a BSR is triggered by a logical channel for which SDT is not permitted, determining that the configuration of the scheduling request mask should be applied.

[0085] In some exemplary 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 resume attempt for 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 permitted via at least one of the one or more configured grant resources, and determining whether the start of a random access procedure should be delayed in response to determining that the random access procedure should be started.

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

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

[0089] In some exemplary embodiments, the method further includes starting a random access procedure when the timing advance expires, or when there is no valid SSB, and there is data to be transmitted in the buffer of the terminal device.

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

[0091] In some exemplary embodiments, the method further includes starting 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 the 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 permitted via at least one of the one or more configured grant resources; means for starting the SDT procedure in a non-active mode; and means for determining whether a configuration of a scheduling request mask should be applied to the logical channels configured for SDT in accordance with a determination that a buffer status report (BSR) is triggered.

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

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

[0095] In some exemplary 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 resume attempt for the 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 is permitted via at least one of the one or more configured grant resources, and means for determining whether the start of a random access procedure should be delayed in response to determining that the random access procedure should be started.

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

[0098] In some exemplary embodiments, the apparatus further includes at least one of means for delaying the start of the random access procedure using a timer, means for delaying the start of the random access procedure until a candidate beam detection count or a configured grant occasion count, or means for delaying the start of the random access procedure until receiving an instruction to start the random access procedure from the network device.

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

[0100] In some exemplary embodiments, the means for determining whether the start of a random access procedure should be delayed includes means for determining that the start of the random access procedure should not be delayed in response to an SDT procedure started on an initial BWP.

[0101] In some exemplary embodiments, the apparatus further includes means for starting 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 started 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 a device, cause the device to perform a method according to some exemplary embodiments of the present disclosure.

Claims

1. A terminal device, including at least one processor, and at least one memory having computer program code, wherein the at least one memory and the computer program code are configured to cause the terminal 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 via at least one of the one or more configured grant resources is permitted; to initiate the SDT procedure in a non-active mode; to determine whether a configuration of a scheduling request mask should be applied to a logical channel configured for SDT in response to a determination that a buffer status report (BSR) is triggered; The terminal device configured to perform the above.

2. In response to determining that the 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 according to claim 1 is caused to determine whether the configuration of the scheduling request mask should not be applied, or to set the scheduling request mask for scheduling requests of the logical channel configured for SDT to true and apply the scheduling request mask. to determine whether it should be applied in the above manner. The terminal device according to claim 1, wherein the terminal device is caused to perform the above.

3. In response to determining that the BSR is triggered by a logical channel for which SDT via at least one of the one or more configured grant resources is not permitted, the terminal device according to claim 1 is caused to determine that the configuration of the scheduling request mask should be applied. The terminal device according to claim 1, which causes the terminal device to determine whether it should be applied by

4. The configuration of the one or more configured grant resources for the small data transmission (SDT) procedure is for use by the terminal device in the inactive mode to initiate a connection resumption attempt for the SDT, the terminal device according to claim 1.

5. A terminal device, At least one processor, At least one memory having computer program code, Including, The at least one memory and the computer program code use the at least one processor to cause the terminal device 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 DRBs associated with each logical channel for which SDT via the at least one of the one or more configured grant resources is permitted, Determine whether the start of the random access procedure should be delayed in response to determining that the random access procedure should be started, The terminal device configured to perform.

6. The start of the random access procedure, The SDT procedure started on a dedicated bandwidth part (BWP), Invalidation of a synchronization signal block (SSB) associated with the dedicated BWP within the one or more configured grant resources on the dedicated BWP, or Invalidation of timing advance, In response to at least one of which, determine that the start of the random access procedure should be delayed, The terminal device according to claim 5, which causes the terminal device to determine whether it should be delayed by

7. Delaying the start of the random access procedure using a timer until the number of candidate beam detections or the number of configured grant occasions, or until receiving an instruction from the network device to start the random access procedure, The terminal device according to claim 6, further causing at least one of them to be performed by the terminal device.

8. The terminal device according to claim 6, further causing the terminal device to start the random access procedure when the timing advance has expired or when there is no valid SSB and there is data transmitted in the buffer of the terminal device.

9. The determination of whether the start of the random access procedure should be delayed by responding to the start of the SDT procedure started on the initial BWP and determining that the start of the random access procedure should not be delayed, is performed by the terminal device, the terminal device according to claim 5.

10. The terminal device according to claim 9, further causing the terminal device to start the random access procedure based on at least one of the invalidation of the SSB associated with the one or more configured grant resources on the initial BWP or the invalidation of the timing advance.

11. A method comprising: 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 via at least one of the one or more configured grant resources is permitted; starting the SDT procedure in a non-active mode; determining whether a configuration of a scheduling request mask should be applied to the logical channels configured for SDT in response to a determination that a buffer status report (BSR) is triggered; The method, comprising.

12. Determining whether the configuration of the scheduling request mask should be applied in response to determining that the BSR is triggered by a logical channel for which SDT via at least one of the one or more configured grant resources is permitted; Determining that the configuration of the scheduling request mask 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. The method according to claim 11, comprising.

13. Determining whether the configuration of the scheduling request mask should be applied is In response to determining that the BSR is triggered by a logical channel for which SDT via at least one of the one or more configured grant resources is not permitted, determining that the configuration of the scheduling request mask should be applied. The method according to claim 11, comprising.

14. The configuration of the one or more configured grant resources for the small data transmission (SDT) procedure is for use by the terminal device in the inactive mode to initiate a connection resume attempt for the SDT. The method according to claim 11.

15. A method comprising: 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 permitted; Determining whether the start of the random access procedure should be delayed in response to determining that the random access procedure should be started; The method, comprising.

16. Determining whether the start of the random access procedure should be delayed is The SDT procedure started on a dedicated bandwidth part (BWP), Invalidation of a synchronization signal block (SSB) associated with the dedicated BWP within the one or more configured grant resources on the dedicated BWP, or Invalidation of timing advance, In response to at least one of: The method according to claim 15, comprising determining that the start of the random access procedure should be delayed.

17. Delaying the start of the random access procedure using a timer until a candidate beam detection number or a configured grant occasion number, or until receiving an instruction from the network device to start the random access procedure. The method according to claim 16, further comprising at least one of the above.

18. The method according to claim 16, further comprising starting the random access procedure when the timing advance expires or when there is no valid SSB and there is data to be transmitted in the buffer of the terminal device.

19. Determining whether the start of the random access procedure should be delayed includes Determining, in response to the SDT procedure started on the initial BWP, that the start of the random access procedure should not be delayed. The method according to claim 15.

20. The method according to claim 19, further comprising starting the random access procedure based on at least one of disabling the SSB associated with the one or more configured grant resources on the initial BWP or disabling the timing advance.

21. An apparatus, comprising: Means for receiving 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 via at least one of the one or more configured grant resources is permitted; Means for starting the SDT procedure in a non-active mode; Means for determining whether a configuration of a scheduling request mask should be applied to a logical channel configured for SDT according to a determination that a buffer status report (BSR) is triggered; The apparatus comprising the above.

22. An apparatus, comprising: Means for receiving, 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 via at least one of the one or more configured grant resources is permitted; Means for determining whether the start of the random access procedure should be delayed in response to determining that the random access procedure should be started; The apparatus comprising the above.

23. A computer-readable storage medium comprising program instructions which, when stored on the computer-readable storage medium and executed by a processor of a device, cause the device to perform the method according to any one of claims 11 to 14.

24. A computer-readable storage medium comprising program instructions which, when stored on the computer-readable storage medium and executed by a processor of a device, cause the device to perform the method according to any one of claims 15 to 20.

Images