Method and Device for Data Transmission

Abstract

Embodiments of the present application relate to methods and devices for data transmission. In embodiments of the present application, the method includes: receiving configuration information for data transmission, where the configuration information for data transmission indicates at least one of the following: first configuration information, which indicates preconfigured bundling resources for one transport block (TB) or at least one time slot preconfigured for at least one TB; and second configuration information, which indicates 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 a user equipment (UE) is in a radio resource control (RRC)_IDLE state or an RRC_INACTIVE state.

Description

Technical Field

[0001] Embodiments of the present application generally relate to wireless communication technologies, and in particular, to methods and devices for data transmission. Background Art

[0002] A dedicated pre-configured uplink resource (D-PUR) solution for data transmission in the IDLE state has been discussed in Long Term Evolution (LTE) and has been applied to the Internet of Things (IoT). Compared with smartphone applications in a New Radio (NR) system, the services and rules are relatively simple. For a User Equipment (UE) in the Radio Resource Control (RRC)_INACTIVE state, pre-configured Physical Uplink Shared Channel (PUSCH) resources (configured grant type 1 resources) will be applied to transmit uplink small data. This configured grant type 1 is configured for a dedicated UE. However, when considering data transmission in the RRC_INACTIVE state, the NR-specific situation has not been discussed. Summary of the Invention

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

[0004] Embodiments of the present application provide a method. The method 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, which indicates pre-configured bundled resources for one Transport Block (TB) or at least one time slot pre-configured for at least one TB; and second configuration information, which indicates 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 the RRC_IDLE state or the RRC_INACTIVE state.

[0005] In an embodiment of the present application, in the case of performing the data transmission based on the first configuration information, the method may further include: configuring a counter "m" for the pre-configured bundled resources for one TB or for at least one time slot pre-configured for at least one TB; and keeping the value of the counter "m" unchanged when only a part of a configured resource occasion of the pre-configured bundled resources is used for data transmission, where the counter "m" is used to implicitly release the pre-configured bundled resources.

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

[0007] In an embodiment of the present application, when performing the data transmission based on the first configuration information, the method may further include: configuring a counter "m" for the pre-configured bundled resources of one TB or for at least one time slot of the pre-configured at least one TB; and increasing the value of the counter "m" when only a part of a configured resource occasion of the pre-configured bundled resources is used for data transmission, where the counter "m" is used to implicitly release the pre-configured bundled resources.

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

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

[0010] In an embodiment of the present application, in the case of performing the data transmission based on the first configuration information, the method may further include: configuring a plurality of timers for the preconfigured bundled resources for at least one time slot of at least one TB, where the at least one preconfigured time slot is a discontinuous time slot, and the preconfigured bundled resources are discontinuous resources; and starting each of the plurality of timers at or after the time slot of the PUSCH transmission containing the data transmission, where the timer is used to monitor the feedback of the data transmission. In an example, each timer corresponds to a part of the discontinuous resources within one cycle. In another example, each timer corresponds to each TB of the at least one TB within one cycle.

[0011] In an embodiment of the present application, the method may further include: expanding the monitoring window when the monitoring window of the timer cannot receive all PDCCHs; and receiving the lost part of the PDCCH in the expanded monitoring window.

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

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

[0014] In an embodiment of the present application, the data transmission is performed by using a PUSCH of Msg.A of a two-step RACH process not configured for the data transmission in the following cases: when the amount of data in the buffer is less than a second threshold; and / or when the MCS of the PUSCH of Msg.A is less than all MCSs of the PUSCH of Msg.A of the two-step RACH process configured for the data transmission.

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

[0016] In an embodiment of the present application, when the preconfigured bundled resources for the data transmission are not suitable for the data transmission, the data transmission is performed based on the second configuration information. Before the four-step RACH process, the data transmission is performed by a two-step RACH process.

[0017] Another embodiment of the present application provides a method. The method 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 bundled resources for one TB or at least one time slot for at least one TB; and second configuration information indicating at least one resource for data transmission during at least one RACH process; and receiving the data transmission based on the configuration information when a user equipment UE is in the RRC_IDLE state or the RRC_INACTIVE state.

[0018] In an embodiment of the present application, when receiving the data transmission based on the first configuration information, the method may further include: configuring a counter "m" for the preconfigured bundled resources for one TB or for at least one time slot for at least one TB; and keeping the value of the counter "m" unchanged when data is received only on a part of a configured resource occasion of the preconfigured bundled resources, where the counter "m" is used for implicitly releasing the preconfigured bundled resources.

[0019] In an embodiment of the present application, when receiving the data transmission based on the first configuration information, the method may further include: configuring a plurality of counters "m", where each counter "m" is for the preconfigured bundled resources of each TB in the at least one TB, where the counter "m" is used for implicitly releasing the preconfigured bundled resources. The method may further include: increasing the value of the counter "m" when transmitting a response corresponding to the preconfigured bundled resources of each TB including a case of LBT failure when the UE is in the RRC_INACTIVE state or the RRC_IDLE state.

[0020] In an embodiment of the present application, when receiving the data transmission based on the first configuration information, the method may further include: configuring a counter "m" for the pre-configured bundled resources for one TB or for at least one time slot of at least one TB; and increasing the value of the counter "m" when data is received only on a partial configured resource occasion of the pre-configured bundled resources, where the counter "m" is used to implicitly release the pre-configured bundled resources.

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

[0022] In an embodiment of the present application, in the case of receiving the data transmission based on the first configuration information, the method may further include: configuring a plurality of timers for the pre-configured bundled resources or for at least one time slot of at least one TB, where the at least one pre-configured time slot is a discontinuous time slot, and the pre-configured bundled resources are discontinuous resources, and the timers are used for the UE to monitor the feedback of the data transmission. In an example, each timer corresponds to a part of the discontinuous resources within one cycle. In another example, each timer corresponds to each TB among the at least one TB within one cycle.

[0023] In an embodiment of the present application, in the case of receiving the data transmission based on the second configuration information, the method may further include: when the RSRP of the UE is less than a first threshold, transmitting an indication for instructing the UE to perform the data transmission by using a PUSCH of Msg.A of a two-step RACH procedure not configured for the data transmission. The indication for instructing the UE to perform the data transmission by using a PUSCH of Msg.A of a two-step RACH procedure not configured for the data transmission is transmitted in the following cases: when the amount of data in the buffer is less than a second threshold; and / or when the MCS of the PUSCH of Msg.A is less than a third threshold.

[0024] In an embodiment of the present application, in the case of receiving the data transmission based on the second configuration information, the method may further include: when the RSRP of the UE is greater than the first threshold, transmitting an indication for instructing the UE to perform the data transmission by using a PUSCH of Msg.A of a two-step RACH procedure of another service configured for data transmission.

[0025] In an embodiment of the present application, an indication for instructing the UE to perform the data transmission by using a PUSCH of Msg.A for a 2-step RACH procedure of another service configured for data transmission is transmitted in the following cases: when the amount of data in the buffer is less than a second threshold; and / or when the MCS of the PUSCH of Msg.A is less than a third threshold.

[0026] In an embodiment of the present application, an indication for instructing the UE to perform the data transmission by using a PUSCH of Msg.A for a 2-step RACH procedure not configured for the data transmission is transmitted in the following cases: when the amount of data in the buffer is less than a second threshold; when and / or the MCS of the PUSCH of Msg.A is less than all MCSs of the PUSCH of Msg.A for a 2-step RACH procedure configured for the data transmission. One or more PUSCHs of Msg.A for different services configured for the data transmission are broadcast or RRC dedicated configured.

[0027] Another embodiment of the present application provides a device. The device 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 by using the at least one receiver, the at least one transmitter, and the at least one processor.

[0028] Embodiments of the present application supplement some new rules to facilitate the implementation of NR small data transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] To describe the manner in which the advantages and features of the present application can be obtained, a description of the present application is presented by reference to specific embodiments of the present application illustrated in the accompanying drawings. These drawings only depict example embodiments of the present application and should not be considered as limiting its scope.

[0030] Figure 1 Illustrate a wireless communication system according to some embodiments of the present application;

[0031] Figure 2 Illustrate a flowchart of a method for data transmission on multiple resources according to some embodiments of the present application;

[0032] Figure 3 Illustrate a device according to some embodiments of the present application; and

[0033] Figure 4Describe another device according to some other embodiments of the present application. Detailed Description of the Invention

[0034] The detailed description of the drawings is intended as a description of the preferred embodiments of the present application and is not intended to represent the only form in which the present application can be practiced. It should be understood that the same or equivalent functions can be achieved by different embodiments that are intended to be covered within the spirit and scope of the present application.

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

[0036] Figure 1 Describe a wireless communication system according to some embodiments of the present application.

[0037] As Figure 1 shown, the wireless communication system may include at least one base station (BS), at least one UE, and a core network (CN) node. Although Figure 1 a specific number of BSs and UEs are depicted therein (e.g., BS (e.g., BS 102) and UE (UE 101)), those skilled in the art will recognize that any number of BSs or UEs may be included in the wireless communication system. As Figure 1 shown, BS 102 may be distributed over a geographical area and may communicate with CN node 103 via an interface.

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

[0039] BS 102 can communicate with the CN node 103 via an interface. In some embodiments of the present application, BS 102 may also be referred to as an access point, access terminal, base station, base station 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. 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.

[0040] In an 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 an Access and Mobility Management Function (AMF) or a User Plane Function (UPF).

[0041] The wireless communication system may be compatible with any type of network capable of sending and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with a wireless communication network, a cellular phone 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.

[0042] In some embodiments of the present application, the wireless communication system is compatible with 5G New Radio of the 3GPP protocol, where BS 102 transmits data using an OFDM modulation scheme on the DL, and 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 protocols, such as WiMAX, WiFi, and other protocols.

[0043] In some embodiments of the present application, BS 102 may communicate using other communication protocols, such as the IEEE 802.11 series of wireless communication protocols. Further, in some embodiments of the present application, BS 102 may communicate on licensed spectrum, while in other embodiments, BS 102 may communicate on unlicensed spectrum. Embodiments of the present application are not intended to be limited to the implementation of any particular wireless communication system architecture or protocol. In still other embodiments of the present application, BS 102 may communicate with UE 101 using the 3GPP 5G protocol.

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

[0045] In this document, data transmission or small data transmission may mean that a UE in an inactive mode or an idle mode may transmit data to the network side (or the network) or receive data from the network side. The data transmission may include at least one of uplink (UL) data transmission and downlink (DL) data transmission. After the data transmission is completed, the inactive or idle UE may receive a suspend message or a release message from the network, and then return to the inactive or idle mode. In some other embodiments of the present application, after the data transmission is completed, the inactive or idle UE may receive a suspend message or a release message from the network, and the UE remains in the inactive or idle mode during the data transmission process. 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 not be greater than the maximum TB size that can be applied in one transmission as defined in the standard or protocol. Small data transmission is one of such scenarios.

[0046] To better understand the embodiments of the present application, the following background knowledge is now introduced.

[0047] In the 3GPP RAN2#107 meeting, the D-PUR convention for "m" is as follows:

[0048] At least the following information may be included in the PUR (re)configuration:

[0049] ■ The FFS value of not being allocated continuously for "m" times before release.

[0050] ■ The time alignment timer in the idle mode.

[0051] ■ The RSRP change threshold of the serving cell.

[0052] In the 3GPP RAN2#108 meeting, the convention for the "m" operation of PUR is as follows:

[0053] When (1) the PUR opportunity is not used when the UE is in RRC_IDLE and (2) the PUR opportunity is used in RRC_IDLE but no response is received (no explicit HARQ ACK / NACK, L1 ACK, or L2 / L3 response), the UE shall increase'm'.

[0054] RAN2 noted that the RAN1#96 agreement "After data transmission on the PUR, if the UE does not receive any information within a period of time, then the UE shall fallback to the legacy RACH / EDT procedure." conflicts with the RAN2#107 agreement. RAN2 reconfirmed the RAN2#107 agreement "The fallback after an unsuccessful D-PUR transmission is not specified, i.e., it is up to the UE implementation to decide to initiate the legacy RA, MO-EDT, or wait for the next D-PUR opportunity."

[0055] When the network does not send a response corresponding to the PUR opportunity (no explicit HARQ ACK / NACK, L1 ACK, or L2 / L3 response), the network shall increment'm'.

[0056] When the UE is in RRC_CONNECTED, do not increment'm' (neither the UE nor the eNB increments'm').

[0057] After successful communication using PUR between the UE and the eNB, reset the counter'm' to zero.

[0058] After successful communication between the UE (with a valid PUR configuration) and the eNB in RRC_CONNECTED, do not reset the counter'm' to zero.

[0059] The existing access restriction methods cited from 5.3.3.2 in TS 36.331 (except for the restriction by RSRP) apply to PUR.

[0060] If the PUR is skipped due to access restrictions (i.e., no special handling), then increment'm'.

[0061] If the PUR is skipped due to the UE being in extendedWaitTime (i.e., no special handling), then increment'm'.

[0062] The configurable values of m = {2, 4, 8, spare}.

[0063] In addition, the D-PUR agreement regarding PDCCH monitoring is as follows:

[0064] After uplink D-PUR transmission, the UE monitors the PDCCH under the control of a timer:

[0065] ■ The timer starts after D-PUR transmission.

[0066] ■ If a scheduling for D-PUR retransmission is received, the timer is restarted.

[0067] ■ If the timer expires, the UE considers the D-PUR transmission to have failed.

[0068] ■ When the D-PUR procedure ends / succeeds, the timer is stopped.

[0069] In addition, regarding the above D-PUR solution, 3GPP TS 36.321 describes the following:

[0070] After a transmission using PUR, the MAC entity shall monitor the PDCCH identified by PUR-RNTI in the PUR response window using the timer pur-ResponseWindowTimer, which starts from the subframe following the end of the transmission of the corresponding PUSCH plus 4 subframes and has a length of pur-ResponseWindowSize. When pur-ResponseWindowTimer is running, the MAC entity shall:

[0071] - If a PDCCH transmission is addressed to PUR-RNTI and contains a UL grant for retransmission:

[0072] - Restart pur-ResponseWindowTimer at the last subframe of the PUSCH transmission corresponding to the retransmission indicated by the UL grant plus 4 subframes.

[0073] Regarding the UE procedures for PUSCH transmission in NR Unlicensed (NR-U), 3GPP describes that PUSCH transmission can be dynamically scheduled by UL grants in Downlink Control Information (DCI), or the transmission can correspond to Configured Grant Type 1 or Type 2. The Configured Grant Type 1 PUSCH transmission is semi-statically configured to operate in response to receiving a higher layer parameter of configuredGrantConfig that contains rrc-ConfiguredUplinkGrant, without detecting the UL grant in DCI. After receiving the higher layer parameter configuredGrantConfig that does not contain rrc-ConfiguredUplinkGrant, according to Article 10.2 of [6, TS 38.213], the Configured Grant Type 2 PUSCH transmission is semi-persistently scheduled by effectively activating the UL grant in DCI. When Configuredgrantconfig-ToAddModList-r16 is configured, on the active BWP of the serving cell, more than one configured grant configuration of Configured Grant Type 1 and / or Configured Grant Type 2 can be active simultaneously. In this document, the expression "A and / or B" means at least one of A and B, that is, A or B, or both A and B.

[0074] In addition, in the 3GPP RAN2#108 meeting, it was agreed that for multi-transmission time interval (TTI) UL grants, in the case of a Listen-Before-Talk (LBT) failure, the UE is allowed to map the internally generated Transport Block (TB) to a different Hybrid Automatic Repeat reQuest (HARQ) process, that is, due to a failed LBT in a different HARQ process associated with a PUSCH with successful LBT, the UE can transmit the TB waiting for transmission in the HARQ process.

[0075] In 3GPP TS 38.321, regarding the LBT failure detection and recovery procedure, it describes the following: ...

[0077] For each active serving cell configured with lbt-FailureRecoveryConfig, the MAC entity shall:

[0078] 1> If an LBT failure indication has been received from the lower layer:

[0079] 2> Start or restart the lbt-FailureDetection Timer;

[0080] 2> Increment LBT_COUNTER by 1;

[0081] 2. If LBT_COUNTER >= lbt-FailureInstanceMaxCount:

[0082] 3. Trigger a consistent LBT failure for the active UL BWP in this serving cell;

[0083] 3. If this serving cell is a SpCell:

[0084] 4. If a consistent LBT failure has been triggered in all UL BWPs for the PRACH occasion on the same carrier configured with this serving cell:

[0085] 5. Indicate the consistent LBT failure to the upper layer. ...

[0087] As mentioned above, the D-PUR solution for data transmission in the idle state has been discussed in LTE and applied to the Internet of Things. However, when considering data transmission in the RRC_INACTIVE state, the NR-specific cases have not been discussed. For example, how to handle the counter "m" with 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 select the legacy PUSCH of Msg.A in the 2-step RACH procedure during the RACH procedure. These issues will be discussed below.

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

[0089] As Figure 2 shown in, 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 that indicates pre-configured bundling resources for one TB or at least one pre-configured time slot for at least one TB; and (2) second configuration information that indicates at least one resource for data transmission during at least one RACH procedure. For example, for the second configuration information, at least one resource for data transmission during the RACH procedure may be a PUSCH resource, which may be configured for one TB or at least one pre-configured time slot for at least one TB.

[0090] After receiving configuration information for data transmission from the BS, in step 220, the UE may perform operations related to data transmission based on the configuration information, which will be described in detail in the following embodiments of this application. Then, in step 230, the UE may transmit data transmission. Steps 220 and 230 may be jointly considered as performing data transmission in the UE based on the configuration information.

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

[0092] The following will describe in detail the method shown as Figure 2 in connection with various embodiments of this application regarding the above problems. In the following description, the solution performed by the UE or the BS based on the first configuration information indicating pre-configured bundled resources may also be referred to as a pre-configured resource solution, and the solution performed by the UE or the BS based on the 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.

[0093] Pre-configured resource solution

[0094] In NR and NR-U, the pre-configured resources may bundle multiple time slots for one TB or multiple TBs. Regarding the issue of how to use multi-time slot grants (in the example, the multi-time slots may be multiple transmission TTIs or multiple other time units) in NR or NR-U to handle the counter "m" (for implicitly releasing the pre-configured bundled resources), the inventors of this application believe that: the counter "m" is used to monitor whether there is data transmission, and when the value of the counter "m" continuously increases to the configured maximum value, the pre-configured uplink resources are released to avoid waste of the pre-configured uplink resources.

[0095] In the embodiments of this application, each pre-configured uplink resource introduces a single counter "m".

[0096] Specifically, for small data transmissions in the RRC_INACTIVE or RRC_IDLE state, each pre-configured uplink resource configures a counter "m". The counter "m" is used to implicitly release the pre-configured bundled resources. In the example, the counter "m" is configured for the pre-configured bundled resources of one TB. In another example, the counter "m" is configured for the pre-configured bundled resources of at least one time slot of at least one TB.

[0097] In this embodiment, when only a part of a configured resource occasion of a preconfigured bundled resource is used for data transmission, the UE will not increase the value of counter "m". That is, when only a part of a configured resource occasion of a preconfigured bundled resource is used for data transmission, the UE will keep the value of counter "m" unchanged. The part of the configured resource occasion of the preconfigured bundled resource can be a part of the resources in the time domain or a part of the resources in the frequency domain. A configured resource occasion refers to a transmission occasion of a TB in continuously configured resources, or an occasion of a cycle of configured grant (including multiple TB transmissions).

[0098] Correspondingly, when data is received only on a part of a configured resource occasion, the network (e.g., BS) will not increase the value of counter "m" because the preconfigured bundled resource is for data transmission. That is, the BS will also keep the value of counter "m" unchanged.

[0099] In another embodiment of the present application, multiple counters "m" are introduced for each TB transmission occasion. That is, for the TB transmission occasion, multiple counters "m" are configured with counter "m". In some other embodiments of the present application, for a logical channel, multiple counters "m" are configured with counter "m", or for a data radio bearer (DRB), multiple counters "m" are configured with counter "m". Counter "m" is used to implicitly release the preconfigured bundled resource.

[0100] Specifically, multiple counters "m" are configured for each TB transmission occasion, and the TB transmission occasion can be used for small data transmission in the RRC_INACTIVE or RRC_IDLE state on the preconfigured bundled uplink resources.

[0101] In this embodiment, in an example, when the preconfigured bundled resource corresponding to the TB (e.g., the preconfigured uplink resource occasion) is not used when the UE is in RRC_INACTIVE or RRC_IDLE, the UE will increase the value of counter "m". In another example, when the preconfigured bundled resource corresponding to the TB (the preconfigured uplink resource occasion) is used in RRC_INACTIVE or RRC_IDLE but no response is received (i.e., no explicit HARQ ACK / NACK, L1 ACK, or L2 / L3 response), the UE will increase the value of counter "m".

[0102] Correspondingly, when the network does not send a response corresponding to the preconfigured bundled resource corresponding to the TB (e.g., the preconfigured uplink resource occasion) (i.e., there is no explicit HARQ ACK / NACK, L1 ACK, or L2 / L3 response) (including the case of a TB with LBT failure), the network (e.g., the BS) will increase the value of the counter "m".

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

[0104] In another embodiment of the present application, each preconfigured uplink resource introduces a single counter "m".

[0105] Specifically, for small data transmissions in the RRC_INACTIVE or RRC_IDLE state, each preconfigured uplink resource configures a counter "m". The counter "m" is used to implicitly release the preconfigured bundled resource. In an example, the counter "m" is configured for the preconfigured bundled resource of one TB. In another example, the counter "m" is configured for the preconfigured bundled resource of at least one time slot of at least one TB.

[0106] In this embodiment, when only a part of a configured resource occasion of the preconfigured bundled resource is used for data transmission, the UE will increase the value of the counter "m". The part of the configured resource occasion of the preconfigured bundled resource can be a part of the resource in the time domain or a part of the resource in the frequency domain. A configured resource occasion refers to a transmission occasion of one TB in a continuously configured resource, or an occasion of one cycle of a configured grant (including multiple TB transmissions).

[0107] Correspondingly, when data is received only on a part of a configured resource occasion, the network (e.g., the BS) will increase the value of the counter "m" because the preconfigured bundled resource is for data transmission.

[0108] Regarding the issue of how to handle the timer for monitoring the PDCCH when multiple grants are allocated, the inventors of the present application believe that: According to 3GPP TS 36.321, the timer for monitoring the PDCCH (or referred to as the PDCCH monitoring timer) starts at the subframe containing the end of the corresponding PUSCH transmission plus 4 subframes. When multiple time slots (or TTIs) or bundled resources are granted, the relevant conditions for starting the timer should be specified because the current rules do not apply.

[0109] In an embodiment, a timer is configured for a pre-configured bundled resource of a TB or at least one time slot of at least one TB, and the timer is used to monitor feedback on data transmission from a receiver (network). In an example, the timer monitors the PDCCH from the network. In an example, the timer can be configured by the network for a UE. The UE starts the timer at or after the time slot containing the first of the corresponding PUSCH transmissions for data transmission. Alternatively, the UE starts the timer when / after transmitting the first of the corresponding PUSCH transmissions for data transmission. For example, the UE is configured with time slots 0, 1, 2, 3 for small data transmission. If time slot 0 can be considered as the first time slot of the PUSCH transmission, then "the UE starts the timer at the time slot containing the first of the corresponding PUSCH transmissions for data transmission" means the UE starts the timer at time slot 0; "the UE starts the timer when / after transmitting the first of the corresponding PUSCH transmissions for data transmission" means the UE starts the timer at time slot 1 (i.e., time slot 0 plus one time slot).

[0110] In addition, when the PDCCH transmits for a UE for data transmission and contains an uplink grant for retransmission, the UE restarts the timer at or after the first or last time slot of the PUSCH transmission corresponding to the retransmission indicated by the uplink grant. Here, the case of "restarting the timer later than..." means restarting the timer at the first time slot plus the configured / predefined duration / one time slot, or at the first time slot plus the round-trip time (RTT) duration.

[0111] In an example, a bundled resource is configured. After data transmission using the pre-configured uplink resources with bundling, the MAC entity will monitor the PDCCH under the control of the timer, and the timer starts at or after the time slot containing the first of the corresponding PUSCH transmission (i.e., data transmission). When the timer is running, if the PDCCH transmits for a UE for small data transmission and contains a UL grant for retransmission, then the MAC entity shall restart the timer at or after the first time slot of the PUSCH transmission corresponding to the retransmission indicated by the UL grant.

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

[0113] For the above-mentioned timer, when the monitoring window of the timer cannot receive the entire PDCCH, the UE may extend the monitoring window and receive the missing part of the PDCCH in the extended monitoring window.

[0114] For example, in a case where a timer is configured to monitor the PDCCH of multiple authorized transmissions, if the first monitoring window cannot receive all PDCCH responses due to the network obtaining the channel late, the monitoring window or the length of the monitoring timer may be extended (extended to the configured length). Once the PDCCH is transmitted, it may maintain the sequence corresponding to the uplink transmission or transmit the missing part of the response in the extended window.

[0115] In another embodiment of the present application, multiple non-consecutive time slots (or TTIs) are authorized in NR or NR-U, and multiple timers are configured for monitoring feedback of data transmission (e.g., PDCCH). Specifically, the multiple timers are configured for a preconfigured bundling resource of at least one time slot for at least one TB, the preconfigured at least one time slot is non-consecutive, and the preconfigured bundling resource is non-consecutive. In an example, each timer corresponds to a part of non-consecutive authorized resources within one cycle. A part of the non-consecutive authorized resources may correspond to a TB transmission resource or a TB transmission opportunity. In another example, each timer may correspond to each TB in at least one TB within one cycle. The timer may be configured by the network for the UE.

[0116] The UE may start each of the multiple timers at or after the time slot containing the PUSCH transmission (i.e., small data transmission).

[0117] In addition, if some of the PDCCH messages fail to be transmitted due to the expiration of the monitoring window caused by LBT failure and some of the later PDCCH messages are transmitted after obtaining the channel, then the timer can be restarted when (or after) the PDCCH within the response set is received. The network can transmit the lost PDCCH due to LBT failure after the PDCCH that obtains the channel before the expiration of the monitoring timer.

[0118] RACH-based solution

[0119] Regarding the issue of whether to allow small data transmission to select the legacy PUSCH of Msg.A in the two-step RACH procedure in NR and NR-U, the inventors of this application believe that: small data transmission can be performed through the two-step RACH. The PUSCH configuration of Msg.A in the two-step RACH procedure in the two-step RACH procedure can be a common configuration or a dedicated configuration for the UE. Considering the diversity of services that can be transmitted as small data transmission, the PUSCH configuration of Msg.A can be various; in particular, the configuration for small data transmission can be different from the legacy RACH. The legacy RACH indicates a RACH procedure in which the PUSCH is not configured for data transmission. The legacy PUSCH indicates a PUSCH that is not configured for data transmission in the legacy RACH procedure. Generally speaking, it can be assumed that the resources of the legacy PUSCH of Msg.A in the two-step RACH procedure in the two-step RACH procedure are less than the resources of the PUSCH of Msg.A in the two-step RACH procedure for small data transmission (hereinafter also referred to as the small data PUSCH of Msg.A in the two-step RACH procedure). To ensure uplink coverage, when the UE is at the edge of the cell, it is best to assemble less data in the uplink encapsulation.

[0120] In an embodiment of this application, when the RSRP of the UE is less than the first threshold (for example, threshold 1), the UE can perform data transmission by using the legacy PUSCH of Msg.A in the two-step RACH procedure. For the network, when the RSRP of the UE is less than the first threshold, the BS can transmit an indication for instructing the UE to perform data transmission by using the legacy PUSCH of Msg.A in the two-step RACH procedure.

[0121] For example, when one legacy PUSCH of Msg.A in the two-step RACH procedure and one small data PUSCH of Msg.A in the two-step RACH procedure are configured, if the UE is at the edge of the cell (for example, RSRP < threshold 1), then the UE is allowed to select the legacy PUSCH of Msg.A in the two-step RACH procedure to perform small data transmission.

[0122] In another example, at least one of the following conditions needs to be further considered: the data in the buffer of the UE 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, even if the UE is located at the cell edge (e.g., RSRP < threshold 1), if the data in the buffer of the UE > threshold 2, then the UE is not allowed to select the legacy PUSCH of Msg.A of the two-step RACH procedure to perform small data transmission.

[0123] In another embodiment of the present application, when configuring one legacy PUSCH of Msg.A of the two-step RACH procedure and multiple small data PUSCHs of Msg.A of the two-step RACH procedure, the UE is not allowed to select the legacy PUSCH of Msg.A of the two-step RACH procedure to perform small data transmission. In this case, multiple individual PUSCHs of Msg.A of the two-step RACH procedure for small data transmission are broadcast or RRC dedicated configurations. In an example, multiple individual PUSCHs of Msg.A of the two-step RACH procedure for small data transmission are used for different services.

[0124] In yet another embodiment of the present application, if the RSRP of the UE is greater than a first threshold, then the UE can perform data transmission by using the PUSCH of Msg.A of the two-step RACH procedure configured for another service for data transmission. For the network, when the RSRP of the UE is greater than the first threshold, the BS can transmit an indication for instructing the UE to perform data transmission by using the PUSCH of Msg.A of the two-step RACH procedure configured for another service for data transmission.

[0125] For example, when configuring one legacy PUSCH of Msg.A of the two-step RACH procedure and multiple small data PUSCHs of Msg.A of the two-step RACH procedure, the UE is not allowed to select the legacy PUSCH of Msg.A of the two-step RACH procedure to perform small data transmission, but if the UE is located at the cell center (e.g., RSRP > threshold 1), then the UE is allowed to select another PUSCH of Msg.A of the two-step RACH procedure, which is configured for another service for small data transmission, or is configured with fewer resources (unable to assemble all buffered data).

[0126] In another example, at least one of the following conditions needs to be further considered: data in the buffer of the UE < threshold 2; MCS < threshold 3; and MCS > threshold 4. That is, in some cases, even if the UE is located at the cell center (e.g., RSRP > threshold 1), but if the data in the buffer of the UE > threshold 2, then the UE is not allowed to select another PUSCH of Msg.A of the two-step RACH process, which is configured for another service of small data transmission or is configured with fewer resources. In this case, one or more individual PUSCHs of Msg.A of the two-step RACH process for small data transmission are broadcast or RRC dedicated configurations. In an example, multiple individual PUSCHs of Msg.A of the two-step RACH process for small data transmission are for different services.

[0127] In yet another embodiment of the present application, when configuring an existing PUSCH of Msg.A of the two-step RACH process and multiple small data PUSCHs of Msg.A of the two-step RACH process, in the case where the UE is located at the cell edge (e.g., the RSRP of the UE is less than the first threshold (threshold 1)), the UE can perform data transmission by using the existing PUSCH of Msg.A of the two-step RACH process. For the network, when the UE is located at the cell edge (e.g., the RSRP of the UE is less than the first threshold (threshold 1)), the BS can transmit an indication for instructing the UE to perform data transmission by using the existing PUSCH of Msg.A of the two-step RACH process.

[0128] In another example, at least one of the following conditions needs to be further considered: data in the buffer of the UE < threshold 2; and the MCS of the existing PUSCH of Msg.A of the two-step RACH process < the MCS of all small data PUSCHs of Msg.A of the two-step RACH process. That is, in some cases, even if the UE is located at the cell edge (e.g., the RSRP of the UE is less than the first threshold (threshold 1)), but if the data in the buffer of the UE > threshold 2, then the UE is not allowed to select the existing PUSCH of Msg.A of the two-step RACH process to perform small data transmission. In this case, one or more individual PUSCHs of Msg.A of the two-step RACH process for small data transmission are broadcast or RRC dedicated configurations. In an example, multiple individual PUSCHs of Msg.A of the two-step RACH process for small data transmission are for different services.

[0129] Although the pre-configured resource solution and the RACH-based solution are described regarding these issues, it is understood that these two solutions can be implemented according to actual needs or requirements, which are not limited to the above issues.

[0130] In an embodiment of the present application, if the UE and the network enable both a preconfigured resource solution and a RACH-based solution, and the preconfigured resource is not suitable for small data transmission, then the UE is allowed to perform small data transmission on the resources configured for the RACH-based solution.

[0131] In another embodiment of the present application, if the UE and the network enable a two-step RACH-based solution and a four-step RACH-based solution, then the UE is allowed to perform small data transmission through the two-step RACH process before the four-step RACH process. In an example, when there is a two-step RACH configuration and the configuration is suitable for data transmission, the UE performs small data transmission through the two-step RACH process before the four-step RACH process. In another example, when the two-step RACH process is allowed to perform data transmission and the UE has the ability to perform data transmission through the two-step RACH process, the UE performs small data transmission through the two-step RACH process before the four-step RACH process.

[0132] According to an embodiment of the present application, in order to implement the features of small data transmission in NR, rules for implicitly releasing preconfigured resources in NR and NR-U are proposed, and a counter for implicitly releasing resources can be configured for each preconfigured uplink resource or each TB transmission occasion. In addition, rules for monitoring the PDCCH after transmission on the preconfigured resources in NR and NR-U are proposed, and one or more timers can be configured. When multiple timers are configured, each timer corresponds to a part of the non-contiguous grant resources within a cycle. Furthermore, in order to meet the diversity of services that can be transmitted as small data transmission, if the UE is located at the cell edge, then the UE is allowed to select an old PUSCH of Msg.A to perform small data transmission.

[0133] Although the above embodiments are described in the context of NR and NR-U, it should be understood that with the development and progress of technology, the above embodiments may be applied to future technologies.

[0134] Figure 3 Describe an apparatus according to some embodiments of the present application. In some embodiments of the present application, the apparatus 300 may be the UE 101 as described in Figure 1 or other embodiments of the present application.

[0135] As Figure 3As shown, device 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, according to actual requirements, in some other embodiments of the present application, device 300 may include more computer-readable media, receivers, transmitters, and processors. 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, device 300 may further include an input device, a memory, and / or other components.

[0136] In some embodiments of the present application, the non-transitory computer-readable medium 307 may have computer-executable instructions stored thereon to cause the processor to implement a method according to an embodiment of the present application.

[0137] Figure 4 Describe another device according to some embodiments of the present application. In some embodiments of the present application, device 400 may be the BS 102 as described in Figure 1 or other embodiments of the present application.

[0138] As Figure 4 shown, device 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, according to actual requirements, in some other embodiments of the present application, device 400 may include more computer-readable media, receivers, transmitters, and processors. 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, device 400 may further include an input device, a memory, and / or other components.

[0139] In some embodiments of the present application, the non-transitory computer-readable medium 407 may have computer-executable instructions stored thereon to cause the processor to implement a method according to an embodiment of the present application.

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

[0141] Those of ordinary skill in the art will understand that the steps of the methods described in connection with the aspects disclosed herein may be embodied directly in hardware, in software modules executed by a processor, or in a combination of both. The software modules 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 methods may reside on a non-transitory computer-readable medium as one or any combination or collection of code and / or instructions that may be incorporated into a computer program product.

[0142] Although the present disclosure has been described in terms of its specific embodiments, it will be apparent that many alternatives, modifications, and variations are possible to those skilled in the art. For example, the various components of the embodiments may be interchanged, added, or replaced in other embodiments. Additionally, all elements of each figure are not necessary for the operation of the disclosed embodiments. For example, those of ordinary skill in the art of the disclosed embodiments will be able to make and use the teachings of the present disclosure by simply employing the elements of the independent technical solutions. Accordingly, the embodiments of the present disclosure as described herein are intended to be illustrative and not restrictive. Various changes may be made without departing from the spirit and scope of the present disclosure.

[0143] In this document, the term "comprises / comprising" or any other variant thereof is intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a series of elements does not include only those elements but may also include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element preceded by "a / an" or the like does not exclude the presence of additional identical elements in the process, method, article, or apparatus that comprises the element. Additionally, the term "another" is defined as at least a second or more. As used herein, the terms "comprising", "having", and the like are defined as "including".

Claims

1. A method for data transmission, comprising: Receiving configuration information for data transmission, where the configuration information for data transmission indicates at least one of the following: First configuration information, which indicates preconfigured bundling resources for one transport block (TB) or at least one time slot preconfigured for at least one TB; and Second configuration information, which indicates at least one resource for data transmission during at least one random access channel (RACH) procedure; And When a user equipment (UE) is in a radio resource control (RRC)_IDLE state or an RRC_INACTIVE state, performing the data transmission based on the configuration information; Where performing the data transmission based on the first configuration information further includes: Configuring a timer for the preconfigured bundling resources for one TB or for the at least one time slot preconfigured for at least one TB; And Starting the timer at a time slot containing the first of the corresponding PUSCH transmissions for the data transmission, Where the timer is used to monitor feedback of the data transmission.

2. The method according to claim 1, where performing the data transmission based on the first configuration information further includes: Configuring a counter "m" for the preconfigured bundling resources for one TB or for the at least one time slot preconfigured for at least one TB; And When only a part of a configured resource occasion of the preconfigured bundling resources is used for data transmission, keeping the value of the counter "m" unchanged, Where the counter "m" is used to implicitly release the preconfigured bundling resources by increasing the value of the counter "m".

3. The method according to claim 1, where performing the data transmission based on the first configuration information further includes: Configuring a plurality of counters "m", where each counter "m" is for the preconfigured bundling resources for each TB in the at least one TB, Where the counter "m" is used to implicitly release the preconfigured bundling resources by responding to one or both of the following: When the UE is in an RRC_INACTIVE state or an RRC_IDLE state, not using the preconfigured bundling resources for each TB; and Using the preconfigured bundling resources for each TB in RRC_INACTIVE or RRC_IDLE but not receiving a response, And increasing the value of the counter "m".

4. The method according to claim 1, where performing the data transmission based on the first configuration information further includes: Configuring a counter "m" for the preconfigured bundling resources for one TB or for the at least one time slot preconfigured for at least one TB; And When only a part of a configured resource occasion of the preconfigured bundling resources is used for data transmission, increasing the value of the counter "m", Where the counter "m" is used to implicitly release the preconfigured bundling resources by increasing the value of the counter "m".

5. The method according to claim 1, further comprising: When the PDCCH transmission is for the UE performing the data transmission and contains an uplink grant for retransmission, restart the timer at or after the first or last time slot of the PUSCH transmission corresponding to the retransmission indicated by the uplink grant.

6. A device for data transmission, comprising: 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; Wherein the computer-executable instructions are programmed to cause the at least one processor to implement: Receive configuration information for data transmission, wherein 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 time 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 Perform the data transmission based on the configuration information when the user equipment (UE) is in the radio resource control (RRC)_IDLE state or the RRC_INACTIVE state; Wherein to perform the data transmission based on the first configuration information, the at least one processor performs the following operations: Configure a timer for the preconfigured bundling resources for one TB or for the at least one time slot preconfigured for at least one TB; and Start the timer at or after the time slot containing the first of the corresponding PUSCH transmissions for the data transmission, wherein the timer is used to monitor the feedback of the data transmission.

7. The device according to claim 6, wherein to perform the data transmission based on the first configuration information, the at least one processor performs the following operations: Configure a plurality of counters "m", where each counter "m" is for the preconfigured bundling resources for each of the at least one TBs, Wherein the counter "m" is used to implicitly release the preconfigured bundling resources by incrementing the value of the counter "m" in response to one or both of the following: When the UE is in the RRC_INACTIVE state or the RRC_IDLE state, the preconfigured bundling resources for each TB are not used; and The preconfigured bundling resources for each TB are used in RRC_INACTIVE or RRC_IDLE but no response is received, And increasing the value of the counter "m".

8. The device according to claim 6, wherein to perform the data transmission based on the first configuration information, the at least one processor performs the following operations: Configure a counter "m" for the preconfigured bundling resources for one TB or for the at least one time slot preconfigured for at least one TB; and Increment the value of the counter "m" in response to only a portion of a configured resource occasion of the preconfigured bundling resources being used for data transmission; Wherein the counter "m" is used to implicitly release the preconfigured bundled resources by increasing the value of the counter "m".

9. The apparatus according to claim 6, wherein the at least one processor performs the following operations: In response to the PDCCH transmitting the UE for the data transmission and including an uplink grant for retransmission, restart the timer at or after the first time slot or the last time slot of the PUSCH transmission corresponding to the retransmission indicated by the uplink grant.

10. The apparatus according to claim 9, wherein the computer-executable instructions cause the at least one processor to implement: When the monitoring window of the timer cannot receive all PDCCHs, extend the monitoring window; and Receive the missing portion of the PDCCH in the extended monitoring window.

11. The apparatus according to claim 6, wherein for performing the data transmission based on the first configuration information, the at least one processor performs the following operations: Configure a plurality of timers for the preconfigured bundled resources for at least one preconfigured time slot of at least one TB, wherein the at least one preconfigured time slot is a plurality of non-consecutive time slots, and the preconfigured bundled resources are a plurality of non-consecutive resources; and Start each of the plurality of timers at or after the time slot of the PUSCH transmission including the data transmission, wherein the timer is used to monitor the feedback of the data transmission, and each timer corresponds to (i) a part of the non-consecutive resources within one cycle or (ii) each TB of the at least one TB within one cycle.

12. The apparatus according to claim 6, wherein for performing the data transmission based on the second configuration information, the at least one processor performs at least one of the following operations: When the reference signal received power (RSRP) of the UE is less than a first threshold, perform the data transmission by using a PUSCH of Msg.A of a two-step RACH procedure not configured for the data transmission; and If the reference signal received power (RSRP) of the UE is greater than the first threshold, then perform the data transmission by using a PUSCH of Msg.A of a two-step RACH procedure of another service configured for data transmission.

13. An apparatus for data transmission, comprising: 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; Wherein the computer-executable instructions are programmed to cause the at least one processor to implement: Transmit configuration information for data transmission, wherein the configuration information for data transmission indicates at least one of the following: First configuration information, which indicates preconfigured bundled resources of one transport block (TB) or at least one preconfigured time slot of 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 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; and Configuring a plurality of timers for the preconfigured bundled resources or for at least one time slot of at least one transport block (TB), wherein the preconfigured at least one time slot is a plurality of non - consecutive time slots, and the preconfigured bundled resources are a plurality of non - consecutive resources, and wherein the timers are used for the UE to monitor feedback of the data transmission.

14. The apparatus according to claim 13, wherein when receiving the data transmission based on the first configuration information, the computer - executable instructions cause the at least one processor to implement: Configuring a counter "m" for the preconfigured bundled resources of one TB or for at least one time slot of at least one TB; and When data is received only on a partial configured resource occasion of the preconfigured bundled resources, keeping the value of the counter "m" unchanged, wherein the counter "m" is used to implicitly release the preconfigured bundled resources by increasing the value of the counter "m".

15. The apparatus according to claim 13, wherein when receiving the data transmission based on the first configuration information, the computer - executable instructions cause the at least one processor to implement: Configuring a plurality of counters "m", wherein each counter "m" is for the preconfigured bundled resources of each TB in the at least one TB, wherein the counter "m" is used to implicitly release the preconfigured bundled resources by increasing the value of the counter "m" when transmitting a response corresponding to the preconfigured bundled resources of each TB including a case of LBT failure when the UE is in an RRC_INACTIVE state or an RRC_IDLE state.

16. The apparatus according to claim 13, wherein when receiving the data transmission based on the first configuration information, the computer - executable instructions cause the at least one processor to implement: Configuring a counter "m" for the preconfigured bundled resources of one TB or for at least one time slot of at least one TB; and When data is received only on a partial configured resource occasion of the preconfigured bundled resources, increasing the value of the counter "m", wherein the counter "m" is used to implicitly release the preconfigured bundled resources by increasing the value of the counter "m".

17. The apparatus according to claim 13, wherein the data transmission is received based on the first configuration information, and the computer - executable instructions cause the at least one processor to implement: When the reference signal received power (RSRP) of the UE is less than a first threshold, transmit an indication for instructing the UE to perform the data transmission by using a PUSCH of Msg.A of a two-step RACH procedure that is not configured for the data transmission; and When the reference signal received power (RSRP) of the UE is greater than the first threshold, transmit an indication for instructing the UE to perform the data transmission by using a PUSCH of Msg.A of a two-step RACH procedure configured for another service for data transmission.

Images