Method and apparatus for data transmission - Patents.com

Abstract

[0010] In one embodiment of the present application, the method includes receiving configuration information for data transmission, the configuration information for data transmission indicating at least one of the following: first configuration information indicating preconfigured bundling resources for one transport block (TB) or at least one preconfigured slot for at least one TB; and second configuration information indicating at least one resource for data transmission during at least one random access channel (RACH) procedure; and performing data transmission based on the configuration information when a user equipment (UE) is in a radio resource control (RRC)_IDLE state or an RRC_INACTIVE state.

Description

[Technical field]

[0001] TECHNICAL FIELD Embodiments of the present application relate generally to wireless communication technologies, and more particularly to a method and apparatus for data transmission. [Background technology]

[0002] A dedicated pre-configured uplink resource (D-PUR) solution for data transmission in IDLE state has been discussed in Long Term Evolution (LTE) and applied to the Internet of Things (IoT). Both the traffic and rules are relatively simple compared to smartphone applications in New Radio (NR) systems. For user equipment (UE) in Radio Resource Control (RRC)_INACTIVE state, pre-configured physical uplink shared channel (PUSCH) resources (configuration grant type 1 resources) are applied to transmit uplink small data. This configuration grant type 1 is configured for dedicated UEs. However, NR-specific cases have not been discussed when considering data transmission in RRC_INACTIVE state. Summary of the Invention [Means for solving the problem]

[0003] Embodiments of the present application provide a method and apparatus for data transmission, for example, in an RRC_IDLE state or an RRC_INACTIVATE state.

[0004] An embodiment of the present application provides a method, which may include: receiving configuration information for data transmission, where the configuration information for data transmission indicates at least one of the following: first configuration information indicating preconfigured bundling resources for one transport block (TB) or at least one slot preconfigured for at least one TB, and second configuration information indicating at least one resource for data transmission during at least one Random Access Channel (RACH) procedure; and performing data transmission based on the configuration information when the UE is in an RRC_IDLE state or an RRC_INACTIVE state.

[0005] In one embodiment of the present application, when performing data transmission based on the first configuration information, the method may further include: configuring one counter “m” for preconfigured bundling resources for one TB or at least one preconfigured slot for at least one TB; and leaving the value of counter “m” unchanged when only a portion of one configured resource opportunity for the preconfigured bundling resource is used for data transmission, and counter “m” is used to implicitly release the preconfigured bundling resource.

[0006] In one embodiment of the present application, when performing data transmission based on the first configuration information, the method may further include configuring a plurality of counters "m" with each counter "m" for pre-configured bundling resources for each TB of the at least one TB, where the counter "m" is used to implicitly release the pre-configured bundling resources. In one example, the method may further include increasing a value of the counter "m" when the pre-configured bundling resources for each TB are not used while the UE is in an RRC_INACTIVE or RRC_IDLE state. In another example, the method may further include increasing a value of the counter "m" when the pre-configured bundling resources for each TB are used but no response is received in RRC_INACTIVE or RRC_IDLE.

[0007] In one embodiment of the present application, when performing data transmission based on the first configuration information, the method may further include: configuring one counter “m” for preconfigured bundling resources for one TB or at least one preconfigured slot for at least one TB; and when only a portion of one configured resource opportunity for the preconfigured bundling resource is used for data transmission, increasing a value of the counter “m”, where the counter “m” is used to implicitly release the preconfigured bundling resource.

[0008] In one embodiment of the present application, when performing data transmission based on the first configuration information, the method may further include: configuring one timer for preconfigured bundling resources for one TB or at least one preconfigured slot for the at least one TB; and starting the timer at or after the slot including a start of a corresponding PUSCH transmission for the data transmission, where the timer is used to monitor feedback for the data transmission.

[0009] In one embodiment of the present application, the method may further include, when the PDCCH transmission is for a UE having a data transmission and includes an uplink grant for a retransmission, restarting the timer at or after the first or last slot of a PUSCH transmission corresponding to the retransmission indicated by the uplink grant.

[0010] In one embodiment of the present application, when performing data transmission based on the first configuration information, the method may further include: configuring a plurality of timers for preconfigured bundling resources for at least one preconfigured slot for at least one TB, where the preconfigured at least one slot is a non-contiguous slot and the preconfigured bundling resources are non-contiguous resources; and starting each timer of the plurality of timers at or after a slot including a PUSCH transmission of the data transmission, where the timers are used to monitor feedback for the data transmission. In one example, each timer corresponds to a portion of the non-contiguous resources in one cycle. In another example, each timer corresponds to each TB of the at least one TB in one cycle.

[0011] In one embodiment of the present application, the method may further include extending a monitoring window of the timer when the monitoring window cannot receive all the PDCCHs, and receiving the missing portion of the PDCCHs in the extended monitoring window.

[0012] In one embodiment of the present application, the step of performing data transmission based on the second configuration information may further include performing data transmission by using a PUSCH of Msg.A of a two-stage RACH procedure that is not configured for data transmission when a reference signal received power (RSRP) of the UE is smaller than a first threshold, and performing data transmission by using a PUSCH of Msg.A of a two-stage RACH procedure that is not configured for data transmission when an amount of data in the buffer is smaller than a second threshold and / or a modulation and coding scheme (MCS) of the PUSCH of Msg.A is smaller than a third threshold.

[0013] In one embodiment of the present application, the step of performing data transmission based on the second configuration information may further include performing data transmission by using a PUSCH of Msg.A of a two-stage RACH procedure configured for another traffic of the data transmission when a reference signal received power (RSRP) of the UE is greater than a first threshold, and performing data transmission by using a PUSCH of Msg.A of a two-stage RACH procedure configured for another traffic of the data transmission when an amount of data in the buffer is smaller than a second threshold and / or an MCS of the PUSCH of Msg.A is smaller than a third threshold.

[0014] In one embodiment of the present application, when the amount of data in the buffer is smaller than a second threshold and / or the MCS of the PUSCH of Msg. A is smaller than all of the MCSs of the PUSCHs of Msg. A of the two-stage RACH procedure that are configured for data transmission, data transmission is performed by using the PUSCH of Msg. A of the two-stage RACH procedure that is not configured for data transmission.

[0015] In one embodiment of the present application, one or more PUSCHs of Msg. A for different traffic configured for data transmission are broadcast or configured for RRC only.

[0016] In one embodiment of the present application, the data transmission is performed based on the second configuration information when the pre-configured bundling resources for the data transmission are not suitable for the data transmission. The data transmission is performed by a two-stage RACH procedure prior to the four-stage RACH procedure.

[0017] Another embodiment of the present application provides a method, which may include: transmitting configuration information for data transmission, where the configuration information for data transmission indicates at least one of the following: first configuration information indicating preconfigured bundling resources for one TB or at least one preconfigured slot for at least one TB, and second configuration information indicating at least one resource for data transmission during at least one RACH procedure; and receiving a data transmission based on the configuration information when a user equipment (UE) is in an RRC_IDLE state or an RRC_INACTIVE state.

[0018] In one embodiment of the present application, when receiving a data transmission based on the first configuration information, the method may further include configuring one counter “m” for preconfigured bundling resources for one TB or at least one preconfigured slot for at least one TB, and leaving the value of counter “m” unchanged when data is received on only a portion of the one configured resource opportunity for the preconfigured bundling resource, where counter “m” is used to implicitly release the preconfigured bundling resource.

[0019] In one embodiment of the present application, when receiving a data transmission based on the first configuration information, the method may further include configuring a plurality of counters "m", with each counter "m" for a pre-configured bundling resource for each TB of the at least one TB, where the counter "m" is used to implicitly release the pre-configured bundling resource. The method may further include increasing a value of the counter "m" when a response corresponding to the pre-configured bundling resource for each TB, including in the case of an LBT failure, is transmitted while the UE is in an RRC_INACTIVE or RRC_IDLE state.

[0020] In one embodiment of the present application, when receiving a data transmission based on the first configuration information, the method may further include configuring one counter "m" for preconfigured bundling resources for one TB or at least one slot preconfigured for at least one TB, and increasing a value of counter "m" when data is received on only a portion of the one configured resource opportunity for the preconfigured bundling resource, where counter "m" is used to implicitly release the preconfigured bundling resource.

[0021] In one embodiment of the present application, when receiving a data transmission based on the first configuration information, the method may further include configuring one timer for pre-configured bundling resources for one TB or at least one pre-configured slot for the at least one TB, where the timer is used by the UE to monitor feedback about the data transmission.

[0022] In one embodiment of the present application, when receiving data transmission based on the first configuration information, the method may further include configuring a plurality of timers for preconfigured bundling resources for at least one preconfigured slot for at least one TB, where the preconfigured at least one slot is a non-contiguous slot and the preconfigured bundling resources are non-contiguous resources, and the timers are used by the UE to monitor feedback on the data transmission. In one example, each timer corresponds to a portion of the non-contiguous resources in one cycle. In another example, each timer corresponds to each TB of the at least one TB in one cycle.

[0023] In one embodiment of the present application, when receiving data transmission based on the second configuration information, the method may further include: sending an instruction to the UE to indicate that the data transmission is to be performed by using the PUSCH of Msg.A of the two-stage RACH procedure that is not configured for data transmission when the RSRP of the UE is smaller than a first threshold value; and sending an instruction to indicate the UE to perform the data transmission by using the PUSCH of Msg.A of the two-stage RACH procedure that is not configured for data transmission when the amount of data in the buffer is smaller than a second threshold value and / or the MCS of the PUSCH of Msg.A is smaller than a third threshold value.

[0024] In one embodiment of the present application, when receiving a data transmission based on the second configuration information, the method may further include a step of sending an instruction to the UE to indicate that the data transmission is to be performed by using a PUSCH of Msg. A of a two-stage RACH procedure configured for another traffic of the data transmission when the RSRP of the UE is greater than the first threshold.

[0025] In one embodiment of the present application, when the amount of data in the buffer is smaller than a second threshold and / or the MCS of the PUSCH of Msg.A is smaller than a third threshold, an instruction is sent to indicate to the UE to perform data transmission by using the PUSCH of Msg.A of a two-stage RACH procedure configured for another traffic of the data transmission.

[0026] In one embodiment of the present application, when the amount of data in the buffer is smaller than a second threshold and / or the MCS of the PUSCH of Msg.A is smaller than all of the MCSs of the PUSCHs of Msg.A of the two-stage RACH procedure configured for data transmission, an indication is sent to indicate to the UE to perform data transmission by using the PUSCH of Msg.A of the two-stage RACH procedure that is not configured for data transmission. One or more PUSCHs of Msg.A for different traffic configured for data transmission are broadcast or configured for RRC only.

[0027] Another embodiment of the present application provides an apparatus. The apparatus may include at least one non-transitory computer-readable medium having computer-executable instructions stored therein, at least one receiver, at least one transmitter, and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiver, and the at least one transmitter. The computer-executable instructions are programmed to implement the above method with the at least one receiver, the at least one transmitter, and the at least one processor.

[0028] The embodiments of the present application complement several new rules to facilitate the implementation of NR small data transmissions.

[0029] To describe how the advantages and features of the present application may be obtained, a description of the application will be given by reference to specific embodiments thereof that are illustrated in the accompanying drawings, which illustrate only exemplary embodiments of the present application and are therefore not to be considered as limiting its scope. [Brief description of the drawings]

[0030] [Figure 1] FIG. 1 illustrates a wireless communication system in accordance with some embodiments of the present application. [Diagram 2] 1 is a flowchart of a method for data transmission over multiple resources according to some embodiments of the present application. [Diagram 3] FIG. 1 illustrates an apparatus according to some embodiments of the present application. [Figure 4] FIG. 13 illustrates another apparatus according to some other embodiments of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0031] The detailed description of the accompanying drawings is intended as an illustration of a preferred embodiment of the present application, and is not intended to represent the only form in which the present application may be practiced. It is to be understood that the same or equivalent functions may be accomplished by different embodiments that are intended to be encompassed within the spirit and scope of the present application.

[0032] Reference will now be made in detail to several embodiments of the present application, examples of which are illustrated in the accompanying drawings.

[0033] FIG. 1 illustrates a wireless communication system according to some embodiments of the present application.

[0034] As shown in Figure 1, the wireless communication system may include at least one base station (BS), at least one UE, and a core network (CN) node. Although a particular number of BSs and UEs, e.g., a BS (e.g., BS 102) and a UE (UE 101), are illustrated in Figure 1, one skilled in the art will recognize that any number of BSs and UEs may be included in the wireless communication system. As shown in Figure 1, the BSs 102 may be distributed across a geographic region and may communicate with the CN node 103 via an interface.

[0035] The UE 101 may be a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart television (e.g., a television connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle-mounted computer, a network device (e.g., a router, a switch, and a modem). According to an embodiment of the present application, the UE 101 may be a portable wireless communication device, a smartphone, a cellular phone, a flip phone, a device with a subscriber identity module, a personal computer, a selective call receiver, or any other device capable of transmitting and receiving communication signals over a wireless network. In some embodiments of the present application, the UE 101 may be a wearable device such as a smart watch, a fitness band, an optical head-mounted display, etc. Additionally, the UE 101 may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or may be described using other terms used in the art.

[0036] The BS 102 may communicate with the CN node 103 via an interface. In some embodiments of the present application, the BS 102 may also be referred to as an access point, access terminal, base, base unit, macro cell, Node B, evolved Node B (eNB), gNB, Home Node B, relay node, or device, or described using other terms used in the art. The BS 102 is generally part of a radio access network, which may include one or more controllers communicatively coupled to one or more corresponding BSs.

[0037] In one example, the CN node 103 may be a mobility management entity (MME) or a serving gateway (S-GW). In another embodiment of the present application, the CN node 103 may include a mobility management function (AMF) or a user plane function (UPF).

[0038] The wireless communication system may be compatible with any type of network capable of transmitting and receiving wireless communication signals. For example, the wireless communication system 100 may be compatible with a wireless communication network, a cellular telephone network, a time division multiple access (TDMA)-based network, a code division multiple access (CDMA)-based network, an orthogonal frequency division multiple access (OFDMA)-based network, an LTE network, a 3rd Generation Partnership Project (3GPP)-based network, a 3GPP 5G network, a satellite communication network, a high altitude platform network, and / or other communication networks.

[0039] In some embodiments of the present application, the wireless communication system is compatible with 3GPP protocol 5G New Radio, where the BS 102 transmits data using an OFDM modulation scheme on the DL and the UE 101 transmits data using a Single Carrier Frequency Division Multiple Access (SC-FDMA) or OFDM scheme on the UL. However, more generally, the wireless communication system may implement some other open or proprietary communication protocol, e.g., WiMAX, WiFi, among other protocols.

[0040] In some embodiments of the present application, the BS 102 may communicate using other communication protocols, such as the IEEE 802.11 family of wireless communication protocols. Additionally, in some embodiments of the present application, the BS 102 may communicate over a licensed spectrum, while in other embodiments, the BS 102 may communicate over an unlicensed spectrum. The embodiments of the present application are not intended to be limited to any particular wireless communication system architecture or protocol implementation. In further embodiments of the present application, the BS 102 may communicate with the UE 101 using 3GPP 5G protocols.

[0041] In one example, the UE 101 is in IDLE mode or RRC_INACTIVE state. When performing small data transmission, the UE 101 connects to the BS 102, and the BS 102 transmits the small data to the CN node 103 via an interface.

[0042] In this specification, data transmission or small data transmission may mean that a UE in an inactive or idle mode can transmit data to or receive data from the network side. The data transmission may include at least one of an uplink (UL) data transmission and a downlink (DL) data transmission. After completion of the data transmission, the inactive or idle UE may receive a suspend message or a release message from the network and then return to an inactive or idle mode. In some other embodiments of the present application, after completion of the data transmission, the inactive or idle UE may receive a suspend message or a release message from the network, and the UE may still remain in an inactive or idle mode during the data transmission procedure. In some embodiments of the present application, the suspend message or the release message is an RRC message. In some embodiments of the present application, the data size in such data transmission may be as large as the maximum TB size that may be applied in one transmission as defined in a standard or protocol. Small data transmission is one of such scenarios.

[0043] In order to better understand the embodiments of the present application, the following background information is now introduced.

[0044] At the 3GPP RAN2#107 meeting, the D-PUR agreement regarding "m" was reached as follows: At least the following information may be included in the PUR (re)configuration: "m" consecutive missed allocations before freeing, FFS value. -Time consistency timer for idle mode. ·RSRP change threshold for the serving cell.

[0045] At the 3GPP RAN2#108 meeting, the following agreement was reached regarding the "m" calculation of PUR: →The UE shall increment "m" when (1) a PUR opportunity is not used while the UE is in RRC_IDLE, and (2) a PUR opportunity is used in RRC_IDLE but no response is received (either an explicit HARQ ACK / NACK, an L1 ACK or an L2 / L3 response). →RAN2 notes that RAN1#96 agreement "If after a data transmission on PUR nothing is received by the UE for a certain time period, the UE shall fall back to the legacy RACH / EDT procedure" contradicts RAN2#107 agreement. RAN2 reaffirms RAN2#107 agreement "Fallback after unsuccessful D-PUR transmission is not specified, i.e. it is up to the UE implementation to initiate legacy RA, MO-EDT or wait for the next D-PUR opportunity." → The network shall increment “m” when no response (either an explicit HARQ ACK / NACK, L1 ACK or L2 / L3 response) corresponding to a PUR opportunity is sent by the network. → "m" is not incremented (either by the UE or the eNB) while the UE is RRC_CONNECTED. After successful communication between the UE and the eNB using →PUR, the counter “m” is reset to zero. After successful communication between the UE (with a valid PUR configuration) and the eNB in ​​→RRC_CONNECTED, the counter 'm' is not reset to zero. → Except for restrictions per RSRP, the existing access restriction methods referred to in 5.3.3.2 of TS 36.331 are applicable to PUR. →If the PUR is skipped due to access restrictions (i.e., no special processing), "m" is incremented. → If PUR is skipped due to the UE being in extendedWaitTime (i.e., no special processing), then "m" is incremented. → Configurable values ​​of m = {2, 4, 8, spare}.

[0046] Additionally, the D-PUR agreement on PDCCH monitoring is as follows: → After uplink D-PUR transmission, the UE monitors the PDCCH under timer control: The timer starts after the D-PUR is sent. · If a D-PUR retransmission schedule is received, the timer is restarted. If the timer expires, the UE shall consider the D-PUR transmission to have failed. When the D-PUR procedure is finished / successful, the timer is stopped.

[0047] Furthermore, with regard to the above D-PUR solution, 3GPP TS 36.321 states: After a transmission using PUR, the MAC entity shall monitor the PDCCH identified by the PUR-RNTI in the PUR response window using a timer pur-ResponseWindowTimer, which starts in the subframe containing the end of the corresponding PUSCH transmission +4 subframes and has length pur-ResponseWindowSize. While the pur-ResponseWindowTimer is running, the MAC entity shall: - If the PDCCH transmission is addressed to PUR-RNTI and contains an UL grant for retransmission: - Restart the pur-ResponseWindowTimer at the last subframe + 4 subframes of the PUSCH transmission corresponding to the retransmission indicated by the UL grant.

[0048] Regarding UE procedures for transmitting PUSCH in NR-Unlicensed (NR-U), 3GPP states: PUSCH transmissions can be dynamically scheduled by an UL grant in the downlink control information (DCI) or the transmissions can correspond to configured grant type 1 or type 2. Configured grant type 1 PUSCH transmissions are semi-statically configured to operate in response to receiving high (or upper) layer parameters of configuredGrantConfig including rrc-ConfiguredUplinkGrant without detection of an UL grant in DCI. Configured grant type 2 PUSCH transmissions are semi-persistently scheduled by an UL grant in a valid activation DCI according to clause 10.2 of [6, TS 38.213] after receiving higher layer parameters configuredGrantConfig without rrc-ConfiguredUplinkGrant. When ConfiguredGrantConfig-ToAddModList-r16 is configured, two or more configuration grant configurations of configuration grant type 1 and / or configuration grant type 2 may be active simultaneously on the active BWP of the serving cell. In this specification, the expression "A and / or B" means at least one of A and B, i.e., A, or B, or both A and B.

[0049] Furthermore, in the 3GPP RAN2#108 meeting, it has been agreed that: In case of multi-transmission time interval (TTI) UL grant, the UE is allowed to internally map generated TBs to different Hybrid Automatic Repeat Request (HARQ) processes in case of Listen Before Transmission (LBT) failure, i.e., the UE may transmit a TB whose transmission in a HARQ process is pending due to LBT failure in a different HARQ process associated with a PUSCH where the LBT was successful.

[0050] 3GPP TS 38.321 describes the following regarding LBT failure detection and recovery procedures. … For each activated serving cell configured in the lbt-FailureRecoveryConfig, the MAC entity shall do the following: 1>If an LBT failure indication is received from lower layers: 2>Start or resume lbt-FailureDetectionTimer; 2>Increment LBT_COUNTER by 1; 2> If LBT_COUNTER ≥ lbt-FailureInstanceMaxCount: 3> trigger consistent LBT failure for active UL BWP in this serving cell; 3> If this serving cell is an SpCell: 4> If consistent LBT failures are triggered in all UL BWPs configured with PRACH opportunities on the same carrier in this serving cell: 5>Indicate consistent LBT failure to higher layers. …

[0051] As mentioned above, D-PUR solutions for data transmission in IDLE state have been discussed in LTE and applied to IoT. However, NR-specific cases have not been discussed when considering data transmission in RRC_INACTIVE state. For example, how to handle counter "m" in the presence of multi-slot grants in NR or NR-U spectrum, how to handle the timer for monitoring PDCCH when multiple grants are allocated, and whether to allow small data transmission to choose legacy PUSCH in Msg.A of two-stage RACH procedure in RACH procedure. These issues are discussed below.

[0052] 2 shows a flowchart of a method for data transmission on multiple resources according to some embodiments of the present application. The method of FIG. 2 is performed between a BS (e.g., BS 102 in FIG. 1) and a UE (e.g., UE 101 in FIG. 1). In the description of the present application, data transmission may also refer to small data transmission, and the UE is in an RRC_IDLE state or an RRC_INACTIVE state.

[0053] As shown in Figure 2, in step 210, the BS transmits configuration information for data transmission. For example, the configuration information for data transmission indicates at least one of the following: (1) first configuration information indicating preconfigured bundling resources for one TB or at least one preconfigured slot for at least one TB, and (2) second configuration information indicating at least one resource for data transmission during at least one RACH procedure. For example, in the case of the second configuration information, the at least one resource for data transmission during the RACH procedure may be a PUSCH resource that may be configured for one TB or at least one preconfigured slot for at least one TB.

[0054] After receiving the configuration information for data transmission from the BS, in step 220, the UE may perform related operations of data transmission based on the configuration information, which will be described in detail with respect to the following embodiments of the present application. Then, in step 230, the UE may transmit data transmission. Steps 220 and 230 together can be regarded as performing data transmission based on the configuration information in the UE.

[0055] In step 240, the BS may receive a data transmission based on the configuration information and perform operations related to the data transmission, which will be described in detail with respect to the following embodiments of the present application.

[0056] In the following, methods for the above described problem as illustrated in Fig. 2 for various embodiments of the present application are described in detail. In the following description, a solution performed by a UE or a BS based on first configuration information indicating preconfigured bundling resources may also be referred to as a preconfigured resource solution, and a solution performed by a UE or a BS based on second configuration information indicating at least one resource for data transmission during at least one RACH procedure may also be referred to as a RACH-based solution.

[0057] Pre-configured resource solutions In NR and NR-U, the preconfigured resources can be bundling for one TB or multiple slots for multiple TBs. Regarding the issue of how to handle counter "m" (used to implicitly release preconfigured bundling resources) in the presence of a multi-slot grant in NR or NR-U (in one example, multiple slots can be multiple transmission TTIs or multiple other time units), the inventors of the present application believe that counter "m" is used to avoid wasting preconfigured uplink resources by monitoring whether there is a data transmission and releasing the preconfigured uplink resources when the value of counter "m" increases continuously up to a configured maximum value.

[0058] In one embodiment of the present application, a single counter "m" is introduced, one per pre-configured uplink resource.

[0059] Specifically, one counter "m" is configured for each pre-configured uplink resource for small data transmission in RRC_INACTIVE or RRC_IDLE state. Counter "m" is used to implicitly release the pre-configured bundling resource. In one example, counter "m" is configured for pre-configured bundling resources for one TB. In another example, counter "m" is configured for pre-configured bundling resources for at least one slot pre-configured for at least one TB.

[0060] In this embodiment, the UE does not increase the value of counter "m" when only a portion of one configured resource opportunity for the preconfigured bundling resource is used for data transmission. That is, the UE leaves the value of counter "m" unchanged when only a portion of one configured resource opportunity for the preconfigured bundling resource is used for data transmission. The portion of the configured resource opportunity for the preconfigured bundling resource may be a portion of the resource in the time domain or a portion of the resource in the frequency domain. One configured resource opportunity refers to one transmission opportunity of one TB in continuously configured resources or one opportunity of one cycle (including multiple TB transmission) of the configuration grant.

[0061] Correspondingly, the network, e.g., the BS, does not increment the value of counter "m" when data is received on only a portion of one configured resource opportunity for the pre-configured bundling resource used for data transmission, i.e., the BS also leaves the value of counter "m" unchanged.

[0062] In another embodiment of the present application, multiple counters "m" per TB transmission opportunity are introduced. That is, the multiple counters "m" consist of counters "m" for TB transmission opportunities. In some other embodiments of the present application, the multiple counters "m" consist of counters "m" for logical channels, or the multiple counters "m" consist of counters "m" for data radio bearers (DRBs). Counter "m" is used to implicitly release pre-configured bundling resources.

[0063] Specifically, a number of counters "m" are configured for each TB transmission opportunity that may be transmitted as a small data transmission in RRC_INACTIVE or RRC_IDLE state on the pre-configured bundling uplink resources.

[0064] In this embodiment, in one example, the UE increases the value of counter "m" when a pre-configured bundling resource (such as a pre-configured uplink resource opportunity) corresponding to TB is not used while the UE is RRC_INACTIVE or RRC_IDLE. In another example, the UE increases the value of counter "m" when a pre-configured bundling resource (pre-configured uplink resource opportunity) corresponding to TB is used in RRC_INACTIVE or RRC_IDLE but no response is received (i.e., neither an explicit HARQ ACK / NACK, L1 ACK, or L2 / L3 response).

[0065] Correspondingly, the network, e.g., the BS, increases the value of the counter "m" when no response (i.e., neither an explicit HARQ ACK / NACK, an L1 ACK, or an L2 / L3 response) corresponding to a pre-configured bundling resource (such as a pre-configured uplink resource opportunity) corresponding to the TB is sent by the network, including in the case of an LBT failure.

[0066] Furthermore, when the value of counter "m" reaches a threshold or maximum value (configured by the network), an RRC reconfiguration may be triggered.

[0067] In yet another embodiment of the present application, a single counter "m" is introduced, one per pre-configured uplink resource.

[0068] Specifically, one counter "m" is configured for each pre-configured uplink resource for small data transmission in RRC_INACTIVE or RRC_IDLE state. Counter "m" is used to implicitly release the pre-configured bundling resource. In one example, counter "m" is configured for pre-configured bundling resources for one TB. In another example, counter "m" is configured for pre-configured bundling resources for at least one slot pre-configured for at least one TB.

[0069] In this embodiment, the UE increases the value of the counter "m" when only a portion of one configured resource opportunity for the pre-configured bundling resource is used for data transmission. The portion of the configured resource opportunity for the pre-configured bundling resource may be a portion of the resource in the time domain or a portion of the resource in the frequency domain. One configured resource opportunity refers to one transmission opportunity of one TB in a contiguous configured resource or one opportunity of one cycle (including multiple TB transmission) of the configuration grant.

[0070] Correspondingly, the network, e.g., the BS, increases the value of a counter “m” when data is received on only a portion of one configured resource opportunity for the pre-configured bundling resource used for data transmission.

[0071] Regarding the question of how to handle the timer for monitoring the PDCCH when multiple grants are allocated, the inventors of the present application consider that according to 3GPP TS 36.321, the timer for monitoring the PDCCH (or called the PDCCH monitoring timer) is started in the subframe containing the end of the corresponding PUSCH transmission + 4 subframes. When multiple slots (or TTIs) or bundling resources are allowed, the relevant conditions for timer start must be specified, since the current rules are not applicable.

[0072] In one embodiment, one timer is configured for pre-configured bundling resources for one TB or at least one pre-configured slot for at least one TB, and the timer is used to monitor feedback about data transmission from the receiver (network). In one example, the timer monitors the PDCCH from the network. In one example, the timer may be configured by the network for the UE. The UE starts the timer at or after the slot including the first of the corresponding PUSCH transmission for the data transmission. Or, the UE starts the timer when / after the first of the corresponding PUSCH transmission for the data transmission is transmitted. For example, the UE is configured with slot 0, slot 1, slot 2, slot 3 for small data transmission. Slot 0 may be considered as the first slot of the PUSCH transmission, then "the UE starts the timer at the slot including the first of the corresponding PUSCH transmission for the data transmission" means that the UE starts the timer at slot 0, and "the UE starts the timer when / after the first of the corresponding PUSCH transmission for the data transmission is transmitted" means that the UE starts the timer at slot 1 (i.e., slot 0 + 1 slot).

[0073] Furthermore, the UE restarts the timer at or after the first slot or last slot of the PUSCH transmission corresponding to the retransmission indicated by the uplink grant when the PDCCH transmission is for a UE with data transmission and includes an uplink grant for retransmission. The case "restart the timer after" here means restarting the timer at the first slot + configured / predefined duration / one slot or at the first slot + round trip time (RTT) duration.

[0074] In one example, bundling resources are configured. After a data transmission using the pre-configured uplink resources configured with bundling, the MAC entity monitors the PDCCH under the control of a timer that starts at or after the slot containing the beginning of the corresponding PUSCH transmission (i.e., data transmission). While the timer is running, if the PDCCH transmission is for a UE with a small data transmission and contains a UL grant for retransmission, the MAC entity shall restart the timer at or after the first slot of the PUSCH transmission corresponding to the retransmission indicated by the UL grant.

[0075] In another example, multiple consecutive slots (or TTIs) are allowed in NR or NR-U. After a transmission using pre-configured uplink resources consisting of multiple slots (or TTIs), the MAC entity shall monitor the PDCCH under the control of a timer that starts at or after the slot containing the first (or last) of the corresponding PUSCH transmission. While the timer is running, if the PDCCH transmission is for a UE with a small data transmission and contains an UL grant for retransmission, the MAC entity shall restart the timer at or after the first (last) slot of the PUSCH transmission corresponding to the retransmission indicated by the UL grant. The PUSCH transmission is a small data transmission.

[0076] For the above timer, when the monitoring window is not able to receive the entire PDCCH, the UE may extend the monitoring window of the timer and receive the missing part of the PDCCH in the extended monitoring window.

[0077] For example, if one timer is configured to monitor the PDCCH for transmission of multiple grants, the monitoring window or monitoring timer length may be extended (to the configured length) if the first monitoring window is unable to receive all PDCCH responses because the network acquired the channel late. When the PDCCH is transmitted, it may maintain a sequence corresponding to the uplink transmission, or the missing part of the response may be transmitted in the extended window.

[0078] In another embodiment of the present application, multiple non-contiguous slots (or TTIs) are allowed in NR or NR-U, and multiple timers are configured to monitor feedback for data transmission (e.g., PDCCH). Specifically, multiple timers are configured for preconfigured bundling resources for at least one preconfigured slot for at least one TB, where the preconfigured at least one slot is non-contiguous and the preconfigured bundling resources are non-contiguous. In one example, each timer corresponds to a portion of the non-contiguous allowed resources in one cycle. The portion of the non-contiguous allowed resources can correspond to a TB transmission resource or a TB transmission opportunity. In another example, each timer may correspond to each TB of the at least one TB in one cycle. The timers may be configured by the network for the UE.

[0079] The UE may start each timer of the multiple timers that starts at or after the slot that includes the PUSCH transmission (ie, the small data transmission).

[0080] Furthermore, if some of the PDCCH messages fail to be transmitted due to expiration of the monitoring window resulting from an LBT failure, while some of the subsequent PDCCH messages are transmitted after acquiring the channel, the timer may be restarted upon (or after) receiving a PDCCH in the response set. The network may transmit the PDCCH that was missed due to the LBT failure followed by the PDCCH that acquires the channel before the monitoring timer expires.

[0081] RACH-based Solutions Regarding the question of whether small data transmission is allowed to choose the legacy PUSCH of Msg.A of the two-stage RACH procedure in the RACH procedure in NR and NR-U, the inventors of the present application believe that small data transmission can be performed by the two-stage RACH. The PUSCH configuration of Msg.A of the two-stage RACH procedure in the RACH procedure can be a common configuration or a dedicated configuration for UEs. Given the diversity of traffic that can be transmitted as small data transmission, the PUSCH configuration of Msg.A may vary, and in particular, the configuration for small data transmission may be different from the legacy RACH. The legacy RACH refers to a RACH procedure in which the PUSCH is not configured for data transmission. The legacy PUSCH refers to a PUSCH that is not configured for data transmission in the legacy RACH procedure. In general, it may be assumed that the resources for the legacy PUSCH of Msg.A of the two-stage RACH procedure in the RACH procedure are less than the resources for the PUSCH of Msg.A of the two-stage RACH procedure for small data transmission in the RACH procedure (hereinafter also referred to as the small data PUSCH of Msg.A of the two-stage RACH procedure). In order to ensure uplink coverage, it is better to assemble less data into an uplink package when the UE is at the edge of the cell.

[0082] In one embodiment of the present application, the UE may perform data transmission by using the legacy PUSCH of Msg.A of the two-stage RACH procedure when the RSRP of the UE is smaller than a first threshold, for example, threshold 1. In the case of a network, the BS may send an indication to the UE to indicate that the UE performs data transmission by using the legacy PUSCH of Msg.A of the two-stage RACH procedure when the RSRP of the UE is smaller than the first threshold.

[0083] For example, when one legacy PUSCH of Msg. A of the two-stage RACH procedure and one small data PUSCH of Msg. A of the two-stage RACH procedure are configured, the UE is allowed to select the legacy PUSCH of Msg. A of the two-stage RACH procedure to perform small data transmission when the UE is located at a cell edge, e.g., RSRP<threshold 1.

[0084] In another example, at least one of the following conditions needs to be further considered: the data in the UE's buffer is less than a second threshold, e.g., threshold 2; the modulation and coding scheme (MCS) is less than a third threshold, e.g., threshold 3; and the MCS is greater than a fourth threshold, e.g., threshold 4. That is, in some cases, if the UE is located at a cell edge (e.g., RSRP<threshold 1) but the data in the UE's buffer>threshold 2, the UE is not allowed to choose the legacy PUSCH of Msg.A of the two-stage RACH procedure to perform small data transmission.

[0085] In another embodiment of the present application, when one legacy PUSCH of Msg.A of the two-stage RACH procedure and multiple small data PUSCHs of Msg.A of the two-stage RACH procedure are configured, the UE is not allowed to select the legacy PUSCH of Msg.A of the two-stage RACH procedure to perform small data transmission. In this case, multiple separate PUSCHs of Msg.A of the two-stage RACH procedure for small data transmission are broadcast or configured for RRC only. In one example, the multiple separate PUSCHs of Msg.A of the two-stage RACH procedure for small data transmission are for different traffic.

[0086] In yet another embodiment of the present application, the UE may perform data transmission by using the PUSCH of Msg.A of the two-stage RACH procedure configured for another traffic of the data transmission when the RSRP of the UE is greater than a first threshold. In the case of a network, the BS may send an indication to the UE to indicate that the UE performs data transmission by using the PUSCH of Msg.A of the two-stage RACH procedure configured for another traffic of the data transmission when the RSRP of the UE is greater than a first threshold.

[0087] For example, when one legacy PUSCH of Msg. A of a two-stage RACH procedure and multiple small data PUSCHs of Msg. A of a two-stage RACH procedure are configured, the UE is not allowed to select the legacy PUSCH of Msg. A of a two-stage RACH procedure to perform small data transmission if the UE is located at a cell center, e.g., RSRP>threshold 1, but is allowed to select another PUSCH of Msg. A of a two-stage RACH procedure that is configured for another traffic of small data transmission or that is configured with fewer resources (not able to assemble all buffered data).

[0088] In another example, at least one of the following conditions should be further considered: data in UE's buffer<threshold 2, MCS<threshold 3, and MCS>threshold 4. That is, in some cases, if the UE is located at a cell center, e.g., RSRP>threshold 1, but data in UE's buffer>threshold 2, the UE is not allowed to choose another PUSCH of Msg.A of the two-stage RACH procedure configured for another traffic of small data transmission or configured with less resources. In this case, one or more separate PUSCHs of Msg.A of the two-stage RACH procedure for small data transmission are broadcast or configured for RRC only. In one example, the multiple separate PUSCHs of Msg.A of the two-stage RACH procedure for small data transmission are for different traffic.

[0089] In yet another embodiment of the present application, when one legacy PUSCH of Msg.A of the two-stage RACH procedure and multiple small data PUSCHs of Msg.A of the two-stage RACH procedure are configured, the UE may perform data transmission by using the legacy PUSCH of Msg.A of the two-stage RACH procedure when the UE is located at the cell edge, e.g., the RSRP of the UE is smaller than a first threshold (threshold 1). In the case of a network, the BS may send an indication to the UE to indicate that the UE performs data transmission by using the legacy PUSCH of Msg.A of the two-stage RACH procedure when the UE is located at the cell edge, e.g., the RSRP of the UE is smaller than a first threshold (threshold 1).

[0090] In another example, at least one of the following conditions should be further considered: data in the UE's buffer<threshold 2, and MCS of the legacy PUSCH of Msg.A of the two-stage RACH procedure<MCS of the small data PUSCH of Msg.A of the two-stage RACH procedure. That is, in some cases, when the UE is located at the cell edge, for example, the RSRP of the UE is smaller than the first threshold (threshold 1), but the data in the UE's buffer>threshold 2, the UE is not allowed to select the legacy PUSCH of Msg.A of the two-stage RACH procedure to perform small data transmission. In this case, one or more separate PUSCHs of Msg.A of the two-stage RACH procedure for small data transmission are broadcast or configured for RRC only. In one example, the multiple separate PUSCHs of Msg.A of the two-stage RACH procedure for small data transmission are for different traffic.

[0091] Regarding the problem, a pre-configured resource solution and a RACH-based solution are described, but it should be understood that the two solutions may be implemented according to actual needs or requirements, which are not limited to the problem described above.

[0092] In one embodiment of the present application, both the pre-configured resource solution and the RACH-based solution are enabled by the UE and the network, and if the pre-configured resources are not suitable for small data transmission, the UE is allowed to perform small data transmission on resources configured for the RACH-based solution.

[0093] In another embodiment of the present application, when the two-stage RACH-based solution and the four-stage RACH-based solution are enabled by the UE and the network, the UE is permitted to perform small data transmission by the two-stage RACH procedure prior to the four-stage RACH procedure. In one example, the UE performs small data transmission by the two-stage RACH procedure prior to the four-stage RACH procedure when there is a two-stage RACH configuration and the configuration is suitable for data transmission. In another example, the UE performs small data transmission by the two-stage RACH procedure prior to the four-stage RACH procedure when the two-stage RACH procedure is permitted to perform data transmission and the UE has the capability of data transmission by the two-stage RACH procedure.

[0094] According to an embodiment of the present application, to realize the feature of small data transmission in NR, a rule for implicitly releasing preconfigured resources in NR and NR-U is proposed, and a counter for implicitly releasing resources may be configured for each preconfigured uplink resource or for each TB transmission opportunity. In addition, a rule for monitoring PDCCH after transmission on preconfigured resources in NR and NR-U is proposed, and one or more timers may be configured. When multiple timers are configured, each timer corresponds to a portion of non-consecutive granted resources in one cycle. Furthermore, to meet the diversity of traffic that may be transmitted as small data transmission, the UE is allowed to choose the legacy PUSCH of Msg.A to perform small data transmission when the UE is located at a cell edge.

[0095] Although the above embodiments are described for NR and NR-U, it should be understood that as technologies develop and evolve, the above embodiments may be applied to future technologies.

[0096] 3 illustrates an apparatus according to some embodiments of the present application. In some embodiments of the present application, the apparatus 300 may be a UE 101 as shown in FIG. 1 or other embodiments of the present application.

[0097] As shown in FIG. 3, the apparatus 300 may include a receiver 301, a transmitter 303, a processor 305, and a non-transitory computer-readable medium 307. The non-transitory computer-readable medium 307 has computer-executable instructions stored therein. The processor 305 is configured to be coupled to the non-transitory computer-readable medium 307, the receiver 301, and the transmitter 303. It is contemplated that the apparatus 300 may include more computer-readable media, receivers, transmitters, and processors according to practical requirements in some other embodiments of the present application. In some embodiments of the present application, the receiver 301 and the transmitter 303 are integrated into a single device, such as a transceiver. In certain embodiments, the apparatus 300 may further include an input device, a memory, and / or other components.

[0098] In some embodiments of the present application, the non-transitory computer-readable medium 307 may have computer-executable instructions stored thereon for causing a processor to implement methods according to embodiments of the present application.

[0099] 4 illustrates another apparatus according to some embodiments of the present application. In some embodiments of the present application, the apparatus 400 may be a BS 102 as shown in FIG. 1 or other embodiments of the present application.

[0100] As shown in FIG. 4, the apparatus 400 may include a receiver 401, a transmitter 403, a processor 405, and a non-transitory computer-readable medium 407. The non-transitory computer-readable medium 407 has computer-executable instructions stored therein. The processor 405 is configured to be coupled to the non-transitory computer-readable medium 407, the receiver 401, and the transmitter 403. It is contemplated that the apparatus 400 may include more computer-readable media, receivers, transmitters, and processors according to practical requirements in some other embodiments of the present application. In some embodiments of the present application, the receiver 401 and the transmitter 403 are integrated into a single device, such as a transceiver. In certain embodiments, the apparatus 400 may further include an input device, a memory, and / or other components.

[0101] In some embodiments of the present application, the non-transitory computer-readable medium 407 may have computer-executable instructions stored thereon for causing a processor to implement methods according to embodiments of the present application.

[0102] Those skilled in the art should understand that as technology develops and evolves, the terms described in the present application may change, and should not affect or limit the principles and spirit of the present application.

[0103] Those skilled in the art will appreciate that the steps of the methods described with respect to the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In addition, in some aspects, the steps of the method may reside as one or any combination or set of codes and / or instructions on a non-transitory computer-readable medium, which may be incorporated into a computer program product.

[0104] Although the present disclosure has been described with its specific embodiments, it is apparent that many alternatives, modifications, and variations may be apparent to those skilled in the art. For example, various components of the embodiments may be exchanged, added, or substituted in other embodiments. Also, not all elements of each figure are necessary for the operation of the disclosed embodiments. For example, a person skilled in the art of the disclosed embodiments will be able to make and use the teachings of the present disclosure by simply using the elements of the independent claims. Thus, the embodiments of the present disclosure described herein are intended to be illustrative, not limiting. Various changes may be made without departing from the spirit and scope of the present disclosure.

[0105] In this document, the terms "comprises", "comprising" or any other variations thereof are intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus that includes a list of elements does not include only those elements, but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element preceded by "a", "an", etc. does not, without further constraints, preclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element. Also, the term "another" is defined as at least a second or more. Terms such as "including", "having", etc., as used herein, are defined as "comprising". [Explanation of symbols]

[0106] 101UE 102 BS 103 CN nodes 300 equipment 301 Receiver 303 Transmitter 305 Processor 307 Non-transitory computer-readable medium 400 equipment 401 Receiver 403 Transmitter 405 Processor 407 Non-transitory computer-readable medium

Claims

1. A method for data transmission performed by a user equipment (UE), comprising: receiving configuration information for data transmission, said configuration information for data transmission comprising: First configuration information indicating preconfigured bundling resources for one transport block (TB) or at least one preconfigured slot for at least one TB; and second configuration information indicating at least one resource for data transmission during at least one random access channel (RACH) procedure; and performing the data transmission based on the configuration information when the UE is in a Radio Resource Control (RRC)_IDLE state or an RRC_INACTIVE state; Including, performing the data transmission based on the first configuration information, configuring one timer for the preconfigured bundling resources for one TB or the preconfigured at least one slot for at least one TB; starting the timer at a slot that includes a start of a corresponding PUSCH transmission for the data transmission; Further comprising: the timer is used to monitor feedback about the data transmission; performing the data transmission based on the second configuration information, The method further comprising performing a data transmission when the preconfigured bundling resources for the data transmission are not suitable for the data transmission.

2. performing the data transmission based on the first configuration information, configuring one counter "m" for the preconfigured bundling resources for one TB or for the preconfigured at least one slot for at least one TB; leaving the value of the counter "m" unchanged when only a portion of a configured resource opportunity for the pre-configured bundling resource is used for data transmission. Further comprising: the counter "m" is used to implicitly release the pre-configured bundling resources by incrementing the value of the counter "m"; The method of claim 1.

3. performing the data transmission based on the first configuration information, configuring a plurality of counters "m", with each counter "m" for the pre-configured bundling resources for each TB of the at least one TB; The counter "m" is The pre-configured bundling resources for each TB are not used while the UE is in an RRC_INACTIVE or RRC_IDLE state; and The pre-configured bundling resources for each TB are used in RRC_INACTIVE or RRC_IDLE, but no response is received. used to implicitly release the pre-configured bundling resources by increasing the value of the counter "m" in response to one or both of The method of claim 1.

4. performing the data transmission based on the first configuration information, configuring one counter "m" for the preconfigured bundling resources for one TB or for the preconfigured at least one slot for at least one TB; incrementing a value of the counter "m" when only a portion of one configured resource opportunity for the pre-configured bundling resource is used for data transmission; Further comprising: the counter "m" is used to implicitly release the pre-configured bundling resources by incrementing the value of the counter "m"; The method of claim 1.

5. when a PDCCH transmission is for the UE having the data transmission and includes an uplink grant for a retransmission, restarting the timer at or after a first slot or a last slot of a PUSCH transmission corresponding to a retransmission indicated by the uplink grant. The method of claim 1, further comprising:

6. An apparatus for transmitting data, comprising: at least one non-transitory computer-readable medium having computer-executable instructions stored therein; At least one receiver; At least one transmitter; at least one processor coupled to the at least one non-transitory computer readable medium, the at least one receiver, and the at least one transmitter; Equipped with The computer-executable instructions may be configured to cause the at least one processor to: receiving configuration information for data transmission, the configuration information for data transmission comprising: First configuration information indicating preconfigured bundling resources for one transport block (TB) or at least one preconfigured slot for at least one TB; and second configuration information indicating at least one resource for data transmission during at least one random access channel (RACH) procedure; receiving, indicating at least one of: performing the data transmission based on the configuration information when a user equipment (UE) is in a radio resource control (RRC)_IDLE state or an RRC_INACTIVE state; Run the command, To perform the data transmission based on the first configuration information, the at least one processor: Configuring one timer for the preconfigured bundling resource for one TB or the preconfigured at least one slot for at least one TB; starting the timer at a slot that includes a start of a corresponding PUSCH transmission for the data transmission; the timer is used to monitor feedback about the data transmission; To perform the data transmission based on the second configuration information, the at least one processor: performing a data transmission when the preconfigured bundling resources for the data transmission are not suitable for the data transmission. Device.

7. The method of claim 6, further comprising: configuring a plurality of counters "m", with each counter "m" for the pre-configured bundling resources for each TB of the at least one TB; The counter "m" is The pre-configured bundling resources for each TB are not used while the UE is in an RRC_INACTIVE or RRC_IDLE state; and The pre-configured bundling resources for each TB are used in RRC_INACTIVE or RRC_IDLE, but no response is received. used to implicitly release the pre-configured bundling resources by increasing the value of the counter "m" in response to one or both of 7. The apparatus of claim 6.

8. The method of claim 7, further comprising: configure one counter “m” for the preconfigured bundling resources for one TB or for the preconfigured at least one slot for at least one TB; incrementing a value of the counter "m" in response to only a portion of a configured resource opportunity for the pre-configured bundling resource being used for data transmission; the counter "m" is used to implicitly release the pre-configured bundling resources by incrementing the value of the counter "m"; 7. The apparatus of claim 6.

9. The at least one processor, 7. The apparatus of claim 6, in response to a PDCCH transmission being for the UE having the data transmission and including an uplink grant for retransmission, restarting the timer at or after a first or last slot of a PUSCH transmission corresponding to the retransmission indicated by the uplink grant.

10. The computer-executable instructions for causing the at least one processor to: extending a monitoring window of the timer when the monitoring window is not able to receive all the PDCCHs; receiving the missing portion of the PDCCH in an extended monitoring window; The apparatus of claim 9 , 11. To perform the data transmission based on the first configuration information, the at least one processor further comprises: configuring a plurality of timers for the preconfigured bundling resources for the preconfigured at least one slot for at least one TB, where the preconfigured at least one slot is a plurality of non-contiguous slots and the preconfigured bundling resources is a plurality of non-contiguous resources; starting each timer of the plurality of timers at or after a slot including a PUSCH transmission of the data transmission; Run the timer is used to monitor feedback about the data transmission; 7. The apparatus of claim 6, wherein each timer corresponds to either (i) a portion of the plurality of non-contiguous resources in one cycle, or (ii) each TB of the at least one TB in one cycle.

12. To perform the data transmission based on the second configuration information, the at least one processor: performing the data transmission by using a PUSCH of a Msg. A of a two-stage RACH procedure that is not configured for the data transmission when a reference signal received power (RSRP) of the UE is less than a first threshold; and When a reference signal received power (RSRP) of the UE is greater than a first threshold, performing the data transmission by using a PUSCH of Msg. A of a two-stage RACH procedure configured for another traffic of the data transmission. The apparatus of claim 6 , further comprising:

13. An apparatus for transmitting data, comprising: at least one non-transitory computer-readable medium having computer-executable instructions stored therein; At least one receiver; At least one transmitter; at least one processor coupled to the at least one non-transitory computer readable medium, the at least one receiver, and the at least one transmitter; Equipped with The computer-executable instructions may be configured to cause the at least one processor to: Transmitting configuration information for data transmission, wherein the configuration information for data transmission comprises the following: First configuration information indicating preconfigured bundling resources for one transport block (TB) or at least one preconfigured slot for at least one TB; and second configuration information indicating at least one resource for data transmission during at least one random access channel (RACH) procedure; and transmitting, receiving the data transmission based on the configuration information when a user equipment (UE) is in a Radio Resource Control (RRC)_IDLE state or an RRC_INACTIVE state; configuring a plurality of timers for the preconfigured bundling resources or for the preconfigured at least one slot for at least one TB; Run the command, the preconfigured at least one slot is a plurality of non-contiguous slots, and the preconfigured bundling resources are a plurality of non-contiguous resources; Each timer of the plurality of timers is used by the UE to monitor feedback about the data transmission; to receive the data transmission based on the second configuration information, the at least one processor: receiving a data transmission when the preconfigured bundling resources for the data transmission are not suitable for the data transmission; Device.

14. The computer-executable instructions for, when receiving the data transmission based on the first configuration information, causing the at least one processor to: configuring a counter "m" for the preconfigured bundling resources for one TB or for the preconfigured at least one slot for at least one TB; leaving the value of the counter "m" unchanged when data is received on only a portion of a configured resource opportunity for the pre-configured bundling resource; Run the command, the counter "m" is used to implicitly release the pre-configured bundling resources by incrementing the value of the counter "m"; 14. The apparatus of claim 13.

15. The method of claim 1, wherein the computer-executable instructions, when receiving the data transmission based on the first configuration information, cause the at least one processor to: configuring a plurality of counters "m", with each counter "m" for the preconfigured bundling resources for each TB of the at least one TB; Run the command, 14. The apparatus of claim 13, wherein the counter "m" is used to implicitly release the pre-configured bundling resources by increasing a value of the counter "m" when a response corresponding to the pre-configured bundling resources for each TB including in the case of LBT failure is transmitted while the UE is in an RRC_INACTIVE or RRC_IDLE state.

16. The method of claim 1, wherein the computer-executable instructions, when receiving the data transmission based on the first configuration information, cause the at least one processor to: configuring a counter "m" for the preconfigured bundling resources for one TB or for the preconfigured at least one slot for at least one TB; incrementing a value of the counter "m" when data is received on only a portion of a configured resource opportunity for the pre-configured bundling resource; Run the command, the counter "m" is used to implicitly release the pre-configured bundling resources by incrementing the value of the counter "m"; 14. The apparatus of claim 13.

17. The data transmission is received based on the second configuration information; The computer-executable instructions may be configured to cause the at least one processor to: sending an indication to the UE to indicate that the data transmission is to be performed by using a PUSCH of Msg. A of a two-stage RACH procedure that is not configured for the data transmission when a reference signal received power (RSRP) of the UE is less than a first threshold; and When a reference signal received power (RSRP) of the UE is greater than a first threshold, sending an instruction to the UE to indicate that the data transmission is to be performed by using a PUSCH of Msg. A of a two-stage RACH procedure configured for another traffic of a data transmission. The apparatus of claim 13 , further comprising:

Images