Patent Description:
A radio resource control (RRC)_INACTIVE state (namely, an inactive state) is a new RRC state introduced in a new radio (NR) system from the perspective of power saving.

Small data transmission (SDT) is introduced in release <NUM> (R17), and an SDT procedure corresponding to the SDT is a data transmission procedure in the inactive state. By means of the SDT procedure, a terminal device does not have to enter an RRC_CONNECTED state (namely, a connected state), and can complete data transmission in the inactive state, which can reduce power consumption and overhead of the terminal device.

Regarding how to configure a bandwidth for performing an SDT procedure, no solution has yet been proposed in the related art.

<NPL> relates to RACH-based Small Data Transmission, which has "Proposal. RAN2 discuss to provide a separate BWP that can be used for RACH-based SDT in RRC INACTIVE.

<NPL> relates to "RACH configuration for Small Data Transmission", which has the following options: "Option <NUM>: RACH based SDT is always performed on initial BWP, Option <NUM>: The BWP for RACH based SDT is configurable.

Implementations of the disclosure provide methods and devices for data transmission.

A terminal device can perform a random access channel (RACH)-based small data transmission (SDT) procedure on a target bandwidth determined.

The terminal device firstly determines the target bandwidth before performing the RACH-based SDT procedure, and then performs the RACH-based SDT procedure on the target bandwidth, which provides a way for determining a bandwidth used for performing an SDT procedure.

In order to describe more clearly technical solutions of implementations of the disclosure, the following will give a brief introduction to the accompanying drawings used for describing the implementations. Apparently, the accompanying drawings described below are merely some implementations of the disclosure. Based on these drawings, those of ordinary skill in the art can also obtain other drawings without creative effort.

In order to make purposes, technical solutions, and advantages of the disclosure clearer, the following will further elaborate implementations of the disclosure with reference to the accompanying drawings.

Firstly, a brief introduction will be given to terms involved in implementations of the disclosure.

In new radio (NR), a new RRC state, namely an RRC_INACTIVE state, has been defined in order to reduce air interface signaling, recover radio connections quickly, and recover data services quickly.

RRC_INACTIVE state (i.e., inactive state): Mobility is based on cell selection and reselection of a terminal device. There is a connection between a core network (CN) and NR. A user equipment (UE) access context exists in a network device. Paging is triggered by a radio access network (RAN), a RAN-based paging area is managed by the RAN, and the network device knows that a location of the terminal device is based on a RAN-based paging area level.

BWP is a concept introduced in NR. BWP is defined as an access bandwidth smaller than each of a system bandwidth of a cell and a terminal capability, and all reception and transmission operations of the terminal device can be performed on the small bandwidth, thereby realizing a terminal operation with higher flexibility, higher efficiency, and lower power consumption. Exemplarily, as illustrated in <FIG>, the terminal device can flexibly select among BWPs with different bandwidths according to service requirements.

In a downlink (DL) direction, the terminal device is configured with up to four DL BWPs, and only one DL BWP can be activated at one time, where the terminal device can receive a DL channel on the activated DL BWP. In an uplink (UL) direction, the terminal device is configured with up to four UL BWPs, and only one UL BWP can be activated at one time, where the terminal device can receive an UL channel on the activated UL BWP. If the terminal device is configured with a supplementary uplink (SUL) carrier, the terminal device can be additionally configured with four UL BWPs, and only one UL BWP can be activated at one time, where the terminal device can receive an UL channel on the activated UL BWP.

With regard to a DL BWP, each DL BWP at least has one control resource set (CORESET), where the CORESET is used for physical downlink control channel (PDCCH) reception and detection, i.e., the CORESET is a time-frequency range for the terminal device to search for a PDCCH.

In a DL BWP, a CORESET can occupy consecutive or nonconsecutive frequency-domain resources. The network device can indicate, via a bitmap in RRC signaling, a physical resource block (PRB) occupied by the CORESET in the DL BWP, where each bit in the bitmap indicates a resource block (RB) group containing six RBs.

In addition, a duration parameter in a CORESET configuration is used for indicating a time-domain length of the CORESET. Since the CORESET itself does not have time location information, the CORESET defines a time-domain region which is not fixed and can float in time location and is determined by the duration parameter. Therefore, the network device needs to configure a search space to further indicate a time-domain region in which the terminal device can receive a PDCCH.

The UL BWP and the DL BWP above are terminal-dedicated BWPs (namely, UE-dedicated BWPs) configured by using dedicated RRC signaling. In addition, the terminal device is further configured with an initial UL BWP and an initial DL BWP. Before entering the connected state, the terminal device operates on the initial UL BWP or the initial DL BWP.

An initial UL BWP is configured in a system information block <NUM> (SIB1), and on the initial UL BWP, the terminal device completes transmission of a preamble, a message <NUM> (Msg3), or a message A (MsgA) during an initial random access procedure.

The initial DL BWP has a CORESET#<NUM>, where the CORESET#<NUM> is used for scheduling an SIB1, other system information (OSI), or physical downlink shared channel (PDSCH) information in an initial random access procedure such as message <NUM> (Msg2) or message <NUM> (Msg4). A method for the terminal device to determine a CORESET#<NUM> in an initial DL BWP is as follows. After cell search is completed, the terminal device obtains a synchronization signal block (SSB) from a network-device side, determines a frequency-domain location of the SSB, then determines, based on a physical broadcast channel (PBCH) in the SSB, a frequency offset value of a CORESET#<NUM> relative to the SSB, and thus determines the CORESET#<NUM> based on the frequency location of the SSB and the frequency offset value of the CORESET#<NUM> relative to the SSB.

Two ways for determining the initial DL BWP are supported in the standard. In a first way, if the initial DL BWP is not configured by higher-layer signaling, the terminal device takes a frequency domain range of the CORESET#<NUM> as a bandwidth of the initial DL BWP. In a second way, if the initial DL BWP is configured by higher-layer signaling (for example, SIB1), the initial DL BWP is determined according to a configuration of the higher-layer signaling. By separately configuring the initial DL BWP, operations such as serving-cell addition and cell handover can be better supported, and on the other hand, a large bandwidth operation of the terminal device can be supported.

As illustrated in <FIG>, for the case where an initial DL BWP is separately configured, in a random access procedure, the terminal device receives, on a CORESET#<NUM>, a DL message transmitted by the network device, such as a random access response (RAR), a contention resolution message, and an RRC setup message (namely, RRCSetup) or an RRC release message (namely, RRCRelease) or an RRC reestablishment message (namely, RRCReestablishment). After the RRCSetup or the RRCRelease or the RRCReestablishment is received, the terminal device operates on the initial DL BWP.

SDT is a data transmission mode configured for the terminal device in the inactive state. By means of an SDT procedure, the terminal device can complete data transmission without entering the connected state, thereby reducing power consumption and overhead of the terminal device.

Optionally, the SDT procedure includes a configured grant (CG)-based SDT procedure and a random access channel (RACH)-based SDT procedure.

Regarding how to configure a bandwidth for executing an SDT procedure, the following solutions are provided in the disclosure.

<FIG> is a block diagram of a communication system provided in an exemplary implementation of the disclosure. The communication system may include an access network <NUM> and a terminal device <NUM>.

The access network <NUM> includes multiple network devices <NUM>. The network device <NUM> can be a base station. The base station is an apparatus that is deployed in the access network and used to provide wireless communication functions for the terminal. The base station can include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems using different radio access technologies, a device with functions of the base station may be in different names. For example, in a long-term evolution (LTE) system, the base station is called eNodeB or eNB. In a <NUM>th generation (<NUM>) NR-based access to unlicensed spectrum (NR-U) system, the base station is called gNodeB or gNB. With evolution of communication technology, the term "base station" may change. For the convenience of illustration of implementations of the disclosure, the devices that can provide wireless communication functions for the terminal device <NUM> are collectively referred to as "network device".

The terminal device <NUM> can include various devices with wireless communication functions such as handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, as well as various forms of UEs, mobile stations (MS), terminal devices, etc. For the convenience of illustration, the above devices are collectively referred to as "terminal". The network device <NUM> and the terminal device <NUM> can communicate with each other with aid of an air-interface technology, such as a UE-universal mobile telecommunication system (UMTS) terrestrial radio access network (UE-UTRAN, Uu) interface. Optionally, the terminal device <NUM> supports an SDT procedure in the inactive state.

Technical solutions of implementations of the disclosure are applicable to various communication systems, for example, a global system of mobile communication (GSM), a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) system, a general packet radio service (GPRS), an LTE system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, an advanced LTE (LTE-A) system, an NR system, an evolved system of an NR system, an LTE-based access to unlicensed spectrum (LTE-U) system, an NR-U system, a universal mobile telecommunication system (UMTS), a worldwide interoperability for microwave access (WiMAX) communication system, a wireless local area network (WLAN), a wireless fidelity (WiFi), a next-generation communication system, or other communication systems.

Generally speaking, a conventional communication system generally supports a limited quantity of connections and therefore is easy to implement. However, with development of communication technology, a mobile communication system will not only support conventional communication but also support, for example, device to device (D2D) communication, machine to machine (M2M) communication, machine type communication (MTC), vehicle to vehicle (V2V) communication, or vehicle to everything (V2X) system, etc. Implementations of the disclosure can also be applied to these communication systems.

<FIG> is a flowchart of a method for data transmission provided in an exemplary implementation of the disclosure. The method can be applied to the communication system illustrated in <FIG>. The method includes the following.

Step <NUM>, a terminal device determines a target bandwidth used for a RACH-based SDT procedure.

Before performing the RACH-based SDT procedure, the terminal device determines the target bandwidth used for the RACH-based SDT procedure. Optionally, the target bandwidth includes a target bandwidth used for UL and a target bandwidth used for DL.

Optionally, by receiving higher-layer signaling, such as SIB1, transmitted by a network device, the terminal device can determine, according to a configuration of the higher-layer signaling, the target bandwidth used for the RACH-based SDT procedure.

The SDT procedure is a data transmission procedure in an inactive state of the terminal device.

SDT is a data transmission mode configured for the terminal device in the inactive state, and there is no need for RRC connection establishment between the terminal device and the network device. For a terminal device with low data volume and low transmission frequency, if data transmission is performed only after an RRC connection with the network device is resumed through a connection resume procedure, the terminal device needs to return to the inactive state after data transmission is completed, and as a result, power consumption of the terminal device will be high. By performing an SDT procedure in the inactive state, the terminal device can be exempt from RRC state transition, thereby reducing power consumption of the terminal device.

Optionally, the SDT procedure includes a CG-based SDT procedure and a RACH-based SDT procedure. In implementations of the disclosure, the RACH-based SDT procedure is taken as an example. The RACH-based SDT procedure may be a <NUM>-step RACH-based SDT procedure, or may be a <NUM>-step RACH-based SDT procedure, and implementations of the disclosure are not limited in this regard.

Step <NUM>, the terminal device performs the RACH-based SDT procedure with the network device on the target bandwidth.

After determining the target bandwidth, the terminal device perform the RACH-based SDT procedure with the network device on the target bandwidth.

Optionally, the target bandwidth includes a target bandwidth used for UL and a target bandwidth used for DL. The terminal device performs UL transmission on the target bandwidth used for UL, and the network device performs UL reception on the target bandwidth used for UL. The terminal device performs DL reception on the target bandwidth used for DL, and the network device performs DL transmission on the target bandwidth used for DL.

As can be seen, according to the method provided in implementations of the disclosure, the terminal device firstly determines the target bandwidth before performing the RACH-based SDT procedure, and then performs the RACH-based SDT procedure on the target bandwidth, which provides a way for determining a bandwidth used for performing an SDT procedure.

In the optional implementation based on <FIG>, there are two different schemes with regard to the target bandwidth.

The initial UL BWP and the initial DL BWP are operation bandwidths determined by the terminal device during an initial access procedure.

In other words, the terminal device determines the initial UL BWP and the initial DL BWP during the initial access procedure, and performs the RACH-based SDT procedure with the network device on the initial UL BWP and the initial DL BWP.

<NUM>) The target bandwidth includes a first UL BWP and a first DL BWP.

The first UL BWP and the first DL BWP are BWPs configured for the terminal device and dedicated for the RACH-based SDT procedure.

In other words, the first UL BWP and the first DL BWP are introduced for the RACH-based SDT procedure, and the terminal device performs the RACH-based SDT procedure with the network device on the first UL BWP and the first DL BWP that are newly introduced.

The above two different schemes with regard to the target bandwidth will be respectively exemplified below.

Based on the optional implementation illustrated in <FIG>, refer to <FIG>, which is a flowchart of a method for data transmission provided in an exemplary implementation of the disclosure. The method can be applied to the communication system illustrated in <FIG>. The method includes the following.

Step <NUM>, the terminal device determines the initial UL BWP and the initial DL BWP as the target bandwidth, where the initial DL BWP has a CORESET#<NUM>.

The initial UL BWP and the initial DL BWP are operation bandwidths determined by the terminal device during an initial access procedure. The CORESET#<NUM> is a control resource set used for carrying scheduling information of SIB1(where SIB1 is also referred to as remaining minimum system information (RMSI)). As illustrated in <FIG>, the initial DL BWP has the CORESET#<NUM>.

Optionally, the initial UL BWP and the initial DL BWP are determined based on an SIB <NUM> scheduled by the CORESET#<NUM>. That is, after determining the CORESET#<NUM>, the terminal device receives the SIB1 scheduled by the CORESET#<NUM>, and determines the initial UL BWP and the initial DL BWP based on the SIB1.

Optionally, the terminal device determines the CORESET#<NUM> as follows. After cell search is completed, the terminal device obtains an SSB from a network-device side, determines a frequency-domain location of the SSB, then determines, based on a PBCH in the SSB, a frequency offset value of the CORESET#<NUM> relative to the SSB, and thus determines the CORESET#<NUM> based on the frequency location of the SSB and the frequency offset value of the CORESET#<NUM> relative to the SSB.

In the current invention, the RACH-based SDT comprises a <NUM>-step RACH-based STD. Optionally, the RACH-based SDT procedure includes a <NUM>-step RACH-based SDT procedure and a <NUM>-step RACH-based SDT procedure.

Optionally, the terminal device transmits to the network device on the initial UL BWP at least one of a preamble, a Msg3, a Msg3 retransmission, or an UL transmission dynamically scheduled by the network device. Accordingly, the network device receives, on the initial UL BWP, at least one of the preamble, the Msg3, the Msg3 retransmission, or the UL transmission dynamically scheduled by the network device transmitted by the terminal device.

In the current invention, the terminal device receives, on the CORESET#<NUM> in the initial DL BWP, at least one of an RAR, a Msg3 retransmission indication, or a Msg4. Accordingly, the network device transmits to the terminal device on the CORESET#<NUM> in the initial DL BWP at least one of the RAR, the Msg3 retransmission indication, or the Msg4.

It can be understood that, after transmission of the Msg4 is completed, the terminal device stays in the inactive state, and the terminal device and the network device can perform continuous UL transmission or DL transmission. In order to receive an UL scheduling or a DL scheduling required for the continuous UL transmission or DL transmission, the bandwidth can be switched from the CORESET#<NUM> to a larger bandwidth.

In a possible implementation, if the Msg4 includes a contention resolution message and does not include an RRC release message, the terminal device receives a resource scheduling on the initial DL BWP, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling. Accordingly, if the Msg4 includes the contention resolution message and does not include the RRC release message, the network device transmits the resource scheduling on the initial DL BWP, where the resource scheduling includes at least one of the UL scheduling or the DL scheduling.

That is, if the Msg4 indicates that contention resolution has been completed and does not indicate termination of the SDT procedure, the terminal device switches from the CORESET#<NUM> to the initial DL BWP with a larger bandwidth, so as to receive a subsequent resource scheduling.

In another possible implementation, the initial DL BWP further has a first CORESET and/or a first search space, where the first CORESET is a CORESET configured for the terminal device in the initial DL BWP, and the first search space is a search space configured for the terminal device in the initial DL BWP.

If the Msg4 includes a contention resolution message and does not include an RRC release message, the terminal device receives a resource scheduling on the first CORESET and/or the first search space, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling. Accordingly, if the Msg4 includes the contention resolution message and does not include the RRC release message, the network device transmits the resource scheduling on the first CORESET and/or the first search space, where the resource scheduling includes at least one of the UL scheduling or the DL scheduling.

In other words, the network device configures for the terminal device the first CORESET dedicated for the SDT procedure, or the network device configures for the terminal device the first search space dedicated for the SDT procedure, or the network device configures for the terminal device the first CORESET and the first search space dedicated for the SDT procedure. If the Msg4 indicates that contention resolution has been completed and does not indicate termination of the SDT procedure, the terminal device switches from the CORESET#<NUM> to the first CORESET and/or the first search space with a larger bandwidth, so as to receive a subsequent resource scheduling.

Optionally, the first CORESET and/or the first search space is determined based on the SIB1 scheduled by the CORESET#<NUM>. In other words, after determining the CORESET#<NUM>, the terminal device receives the SIB1 scheduled by the CORESET#<NUM>, and determines the first CORESET, or the first search space, or both the first CORESET and the first search space according to the SIB1 in addition to determining the initial UL BWP and the initial DL BWP according to the SIB <NUM>.

Optionally, the UL scheduling and the DL scheduling belong to the same RACH-based SDT procedure.

Exemplarily, as illustrated in <FIG>, the <NUM>-step RACH-based SDT procedure between the terminal device and the network device includes the following.

S11, the terminal device transmits a preamble on the initial UL BWP.

Accordingly, the network device receives the preamble on the initial UL BWP.

S12, the network device transmits an RAR on the CORESET#<NUM>.

Accordingly, the terminal device receives the RAR on the CORESET#<NUM>.

S13, the terminal device transmits a Msg3 on the initial UL BWP.

Accordingly, the network device receives the Msg3 on the initial UL BWP.

Optionally, the Msg3 includes an RRC message and UL data.

S14, the network device transmits a Msg4 on the CORESET#<NUM>.

Accordingly, the terminal device receives the Msg4 on the CORESET#<NUM>.

Optionally, the Msg4 includes a contention resolution message, but does not include an RRC release message.

S15, the network device transmits an UL scheduling on the initial DL BWP.

Accordingly, the terminal device receives the UL scheduling on the initial DL BWP.

In another implementation, the network device transmits the UL scheduling on the first CORESET and/or the first search space. Accordingly, the terminal device receives the UL scheduling on the first CORESET and/or the first search space.

S16, the network device transmits a DL scheduling on the initial DL BWP.

Accordingly, the terminal device receives the DL scheduling on the initial DL BWP.

In another implementation, the network device transmits the DL scheduling on the first CORESET and/or the first search space. Accordingly, the terminal device receives the DL scheduling on the first CORESET and/or the first search space.

The terminal device performs a <NUM>-step RACH-based SDT procedure with the network device on the target bandwidth.

Optionally, the terminal device transmits to the network device on the initial UL BWP at least one of a preamble, a MsgA payload, a Msg3, a Msg3 retransmission, or an UL transmission dynamically scheduled by the network device. Accordingly, the network device receives, on the initial UL BWP, at least one of the preamble, the MsgA payload, the Msg3, the Msg3 retransmission, or the UL transmission dynamically scheduled by the network device transmitted by the terminal device.

Optionally, the terminal device receives, on the CORESET#<NUM> in the initial DL BWP, at least one of an RAR, a Msg3 retransmission indication, a Msg4, or a message B (MsgB) transmitted by the network device. Accordingly, the network device transmits to the terminal device on the CORESET#<NUM> in the initial DL BWP at least one of the RAR, the Msg3 retransmission indication, the Msg4, or the MsgB.

It can be understood that, in a <NUM>-step RACH, if the network device only receives the preamble transmitted by the terminal device but failed to receive the MsgA payload, the network device will transmit the RAR to the terminal device. After receiving the RAR, the terminal device transmits the Msg3 to the network device. If the network device successfully receives the Msg3, the network device will feed back the Msg4 to the terminal device. If the network device successfully receives the preamble and the MsgA payload transmitted by the terminal device, the network device will feed back the MsgB to the terminal device. After transmission of the Msg4 or the MsgB is completed, the terminal device stays in the inactive state, and the terminal device and the network device can perform continuous UL transmission or DL transmission. In order to receive an UL scheduling or a DL scheduling required for the continuous UL transmission or DL transmission, the bandwidth can be switched from the CORESET#<NUM> to a larger bandwidth.

In a possible implementation, if the MsgB includes a contention resolution message and does not include an RRC release message, the terminal device receives a resource scheduling on the initial DL BWP, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling. Alternatively, if the Msg4 includes a contention resolution message and does not include an RRC release message, the terminal device receives a resource scheduling on the initial DL BWP, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling. Accordingly, if the MsgB includes the contention resolution message and does not include the RRC release message, the network device transmits the resource scheduling on the initial DL BWP, where the resource scheduling includes at least one of the UL scheduling or the DL scheduling. Alternatively, if the Msg4 includes the contention resolution message and does not include the RRC release message, the network device transmits the resource scheduling on the initial DL BWP, where the resource scheduling includes at least one of the UL scheduling or the DL scheduling.

That is, if the Msg4 or the MsgB indicates that contention resolution has been completed and does not indicate termination of the SDT procedure, the terminal device switches from the CORESET#<NUM> to the initial DL BWP with a larger bandwidth, so as to receive a subsequent resource scheduling.

If the MsgB includes a contention resolution message and does not include an RRC release message, the terminal device receives a resource scheduling on the first CORESET and/or the first search space, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling. Alternatively, if the Msg4 includes a contention resolution message and does not include an RRC release message, the terminal device receives a resource scheduling on the first CORESET and/or the first search space, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling. Accordingly, if the MsgB includes the contention resolution message and does not include the RRC release message, the network device transmits the resource scheduling on the first CORESET and/or the first search space, where the resource scheduling includes at least one of the UL scheduling or the DL scheduling. Alternatively, if the Msg4 includes the contention resolution message and does not include the RRC release message, the network device transmits the resource scheduling on the first CORESET and/or the first search space, where the resource scheduling includes at least one of the UL scheduling or the DL scheduling.

In other words, the network device configures for the terminal device the first CORESET dedicated for the SDT procedure, or the network device configures for the terminal device the first search space dedicated for the SDT procedure, or the network device configures for the terminal device the first CORESET and the first search space dedicated for the SDT procedure. If the Msg4 or the MsgB indicates that contention resolution has been completed and does not indicate termination of the SDT procedure, the terminal device switches from the CORESET#<NUM> to the first CORESET and/or the first search space with a larger bandwidth, so as to receive a subsequent resource scheduling.

Optionally, the first CORESET and/or the first search space is determined based on the SIB1 scheduled by the CORESET#<NUM>. In other words, after determining the CORESET#<NUM>, the terminal device receives the SIB1 scheduled by the CORESET#<NUM>, and determines the first CORESET, or the first search space, or both the first CORESET and the first search space according to the SIB1 in addition to determining the initial UL BWP and the initial DL BWP according to the SIB1.

Exemplarily, as illustrated in <FIG>, a <NUM>-step RACH-based SDT procedure between the terminal device and the network device includes the following.

S21, the terminal device transmits a preamble and a MsgA payload on the initial UL BWP.

Accordingly, the network device receives the preamble and the MsgA payload on the initial UL BWP.

Optionally, the MsgA payload includes an RRC message and UL data.

S22, the network device transmits a MsgB on the CORESET#<NUM>.

Accordingly, the terminal device receives the MsgB on the CORESET#<NUM>.

Optionally, the MsgB includes a contention resolution message and does not include an RRC release message.

S23, the network device transmits an UL scheduling on the initial DL BWP.

S24, the network device transmits a DL scheduling on the initial DL BWP.

Exemplarily, as illustrated in <FIG>, a <NUM>-step RACH-based SDT procedure between the terminal device and the network device includes the following,.

S31, the terminal device transmits a preamble and a MsgA payload on the initial UL BWP.

Accordingly, the network device only receives the preamble on the initial UL BWP, but failed to receive the MsgA payload.

S32, the network device transmits an RAR on the CORESET#<NUM>.

S33, the terminal device transmits a Msg3 on the initial UL BWP.

S34, the network device transmits a Msg4 on the CORESET#<NUM>.

Optionally, the Msg4 includes a contention resolution message and does not include an RRC release message.

S35, the network device transmits an UL scheduling on the initial DL BWP.

S36, the network device transmits a DL scheduling on the initial DL BWP.

As can be seen, according to the method provided in the implementation, for a RACH-based SDT procedure, the terminal device can first implement a random access procedure on the initial UL BWP and the CORESET#<NUM> in the initial DL BWP, and then switch from the CORESET#<NUM> to the initial DL BWP with a larger bandwidth or switch from the CORESET#<NUM> to the first CORESET and/or the first search space with a larger bandwidth, which can facilitate subsequent UL and DL scheduling as well as UL and DL transmission, thereby improving data transmission capability in an SDT procedure.

<NUM>) The target bandwidth includes the first UL BWP and the first DL BWP.

Step <NUM>, the terminal device determines the first UL BWP and the first DL BWP as the target bandwidth.

The first UL BWP and the first DL BWP are BWPs configured for the terminal device and dedicated for the RACH-based SDT procedure. Optionally, the first DL BWP has a CORESET#<NUM>.

Optionally, the first UL BWP and the first DL BWP are determined based on an SIB <NUM> scheduled by the CORESET#<NUM>. In other words, after determining the CORESET#<NUM>, the terminal device receives the SIB1 scheduled by the CORESET#<NUM>, and determines the first UL BWP and the first DL BWP based on the SIB1.

Optionally, the RACH-based SDT procedure includes a <NUM>-step RACH-based SDT procedure and a <NUM>-step RACH-based SDT procedure.

Optionally, the terminal device transmits to the network device on the first UL BWP at least one of a preamble, a Msg3, a Msg3 retransmission, or an UL transmission dynamically scheduled by the network device. Accordingly, the network device receives, on the first UL BWP, at least one of the preamble, the Msg3, the Msg3 retransmission, or the UL transmission dynamically scheduled by the network device transmitted by the terminal device.

Optionally, the terminal device receives, on the first DL BWP, at least one of an RAR, a Msg3 retransmission indication, an UL scheduling, a DL scheduling, or a Msg4 transmitted by the network device. Accordingly, the network device transmits to the terminal device on the first DL BWP at least one of the RAR, the Msg3 retransmission indication, the UL scheduling, the DL scheduling, or the Msg4.

S41, the terminal device transmits a preamble on the first UL BWP.

Accordingly, the network device receives the preamble on the first UL BWP.

S42, the network device transmits an RAR on the first DL BWP.

Accordingly, the terminal device receives the RAR on the first DL BWP.

S43, the terminal device transmits a Msg3 on the first UL BWP.

Accordingly, the network device receives the Msg3 on the first UL BWP.

S44, the network device transmits a Msg4 on the first DL BWP.

Accordingly, the terminal device receives the Msg4 on the first DL BWP.

S45, the network device transmits an UL scheduling on the first DL BWP.

Accordingly, the terminal device receives the UL scheduling on the first DL BWP.

S46, the network device transmits a DL scheduling on the first DL BWP.

Accordingly, the terminal device receives the DL scheduling on the first DL BWP.

Optionally, the terminal device transmits to the network device on the first UL BWP at least one of a preamble, a MsgA payload, a Msg3, a Msg3 retransmission, or an UL transmission dynamically scheduled by the network device. Accordingly, the network device receives, on the first UL BWP, at least one of the preamble, the MsgA payload, the Msg3, the Msg3 retransmission, or the UL transmission dynamically scheduled by the network device transmitted by the terminal device.

Optionally, the terminal device receives, on the first DL BWP, at least one of an RAR, a Msg3 retransmission indication, a Msg4, an UL scheduling, a DL scheduling, or a MsgB transmitted by the network device. Accordingly, the network device transmits to the terminal device on the first DL BWP at least one of the RAR, the Msg3 retransmission indication, the Msg4, the UL scheduling, the DL scheduling, or the MsgB.

S51, the terminal device transmits a preamble and a MsgA payload on the first UL BWP.

Accordingly, the network device receives the preamble and the MsgA payload on the first UL BWP.

S52, the network device transmits a MsgB on the first DL BWP.

Accordingly, the terminal device receives the MsgB on the first DL BWP.

S53, the network device transmits an UL scheduling on the first DL BWP.

S54, the network device transmits a DL scheduling on the first DL BWP.

S61, the terminal device transmits a preamble and a MsgA payload on the first UL BWP.

Accordingly, the network device only receives the preamble on the first UL BWP, but failed to receive the MsgA payload.

S62, the network device transmits an RAR on the first DL BWP.

S63, the terminal device transmits a Msg3 on the first UL BWP.

S64, the network device transmits a Msg4 on the first DL BWP.

S65, the network device transmits an UL scheduling on the first DL BWP.

S66, the network device transmits a DL scheduling on the first DL BWP.

As can be seen, according to the method provided in the implementation, the first UL BWP and the first DL BWP are dedicatedly configured for a RACH-based SDT procedure, so that the terminal device and the network device can implement the RACH-based SDT procedure on the first UL BWP and the first DL BWP.

It should be noted that, the foregoing method implementations may be implemented separately or in combination, and the disclosure is not limited in this regard.

In each of the foregoing implementations, steps executed by the terminal device may be separately implemented as a method for data transmission at a terminal-device side, and steps executed by the network device may be separately implemented as a method for data transmission at a network-device side.

<FIG> is a structural block diagram of an apparatus for data transmission provided in an exemplary implementation of the disclosure. The apparatus may be implemented as a terminal device or a part of the terminal device. The apparatus includes a bandwidth determining module <NUM> and a transmitting module <NUM>. The bandwidth determining module <NUM> is configured to determine a target bandwidth used for a RACH-based SDT procedure. The transmitting module <NUM> is configured to perform the RACH-based SDT procedure with a network device on the target bandwidth, where the SDT procedure is a data transmission procedure in an inactive state of the terminal device.

In an optional implementation, the bandwidth determining module <NUM> is configured to determine an initial UL BWP and an initial DL BWP as the target bandwidth, where the initial DL BWP has a CORESET#<NUM>.

In an optional implementation, the RACH includes a <NUM>-step RACH, and the transmitting module <NUM> is configured to transmit to the network device on the initial UL BWP at least one of a preamble, a Msg3, a Msg3 retransmission, or an UL transmission dynamically scheduled by the network device.

In an optional implementation, the RACH includes a <NUM>-step RACH, and the transmitting module <NUM> is configured to receive, on the CORESET#<NUM> in the initial DL BWP, at least one of an RAR, a Msg3 retransmission indication, or a Msg4 transmitted by the network device.

In an optional implementation, the transmitting module <NUM> is configured to receive a resource scheduling on the initial DL BWP when the Msg4 includes a contention resolution message and does not include a radio resource control (RRC) release message, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling.

In an optional implementation, the initial DL BWP further has a first CORESET and/or a first search space, where the first CORESET is a CORESET configured for the terminal device in the initial DL BWP, and the first search space is a search space configured for the terminal device in the initial DL BWP. The transmitting module <NUM> is configured to receive a resource scheduling on the first CORESET and/or the first search space when the Msg4 includes a contention resolution message and does not include an RRC release message, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling.

In an optional implementation, the RACH includes a <NUM>-step RACH, and the transmitting module <NUM> is configured to transmit to the network device on the initial UL BWP at least one of a preamble, a MsgA payload, a Msg3, a Msg3 retransmission, or an UL transmission dynamically scheduled by the network device.

In an optional implementation, the RACH includes a <NUM>-step RACH, and the transmitting module <NUM> is configured to receive, on the CORESET#<NUM> in the initial DL BWP, at least one of an RAR, a Msg3 retransmission indication, a Msg4, or a MsgB transmitted by the network device.

In an optional implementation, the transmitting module <NUM> is configured to receive a resource scheduling on the initial DL BWP when the MsgB includes a contention resolution message and does not include an RRC release message, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling; or receive a resource scheduling on the initial DL BWP when the Msg4 includes a contention resolution message and does not includes an RRC release message, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling.

In an optional implementation, the initial DL BWP further has a first CORESET and/or a first search space, where the first CORESET is a CORESET configured for the terminal device in the initial DL BWP, and the first search space is a search space configured for the terminal device in the initial DL BWP. The transmitting module <NUM> is configured to receive a resource scheduling on the first CORESET and/or the first search space when the MsgB includes a contention resolution message and does not include an RRC release message, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling; or receive a resource scheduling on the first CORESET and/or the first search space when the Msg4 includes a contention resolution message and does not include an RRC release message, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling.

In an optional implementation, the UL scheduling and the DL scheduling belong to the same RACH-based SDT procedure.

In an optional implementation, the first CORESET and/or the first search space is determined based on an SIB1 scheduled by the CORESET#<NUM>.

In an optional implementation, the initial UL BWP and the initial DL BWP are determined based on the SIB1 scheduled by the CORESET#<NUM>.

In an optional implementation, the bandwidth determining module <NUM> is configured to determine a first UL BWP and a first DL BWP as the target bandwidth, where the first UL BWP and the first DL BWP are BWPs configured for the terminal device and dedicated for the RACH-based SDT procedure.

In an optional implementation, the RACH includes a <NUM>-step RACH, and the transmitting module <NUM> is configured to transmit to the network device on the first UL BWP at least one of a preamble, a Msg3, a Msg3 retransmission, or an UL transmission dynamically scheduled by the network device.

In an optional implementation, the RACH includes a <NUM>-step RACH, and the transmitting module <NUM> is configured to receive, on the first DL BWP, at least one of an RAR, a Msg3 retransmission indication, an UL scheduling, a DL scheduling, or a Msg4 transmitted by the network device.

In an optional implementation, the RACH includes a <NUM>-step RACH, and the transmitting module <NUM> is configured to transmit to the network device on the first UL BWP at least one of a preamble, a MsgA payload, a Msg3, a Msg3 retransmission, or an UL transmission dynamically scheduled by the network device.

In an optional implementation, the RACH includes a <NUM>-step RACH, and the transmitting module <NUM> is configured to receive, on the first DL BWP, at least one of an RAR, a Msg3 retransmission indication, a Msg4, an UL scheduling, a DL scheduling, or a MsgB transmitted by the network device.

In an optional implementation, the first UL BWP and the first DL BWP are determined based on an SIB1 scheduled by a CORESET#<NUM>.

<FIG> is a structural block diagram of an apparatus for data transmission provided in an exemplary implementation of the disclosure. The apparatus may be implemented as a network device or a part of the network device. The apparatus includes a transmitting module <NUM>. The transmitting module <NUM> is configured to perform a RACH-based SDT procedure with a terminal device on a target bandwidth, where the SDT procedure is a data transmission procedure in an inactive state of the terminal device.

In an optional implementation, the target bandwidth includes an initial UL BWP and an initial DL BWP, and the initial DL BWP has a CORESET#<NUM>.

In an optional implementation, the RACH includes a <NUM>-step RACH, and the transmitting module <NUM> is configured to receive, on the initial UL BWP, at least one of a preamble, a Msg3, a Msg3 retransmission, or an UL transmission dynamically scheduled by the network device transmitted by the terminal device.

In an optional implementation, the RACH includes a <NUM>-step RACH, and the transmitting module <NUM> is configured to transmit to the terminal device on the CORESET#<NUM> in the initial DL BWP at least one of an RAR, a Msg3 retransmission indication, or a message <NUM> (Msg4).

In an optional implementation, the transmitting module <NUM> is configured to transmit a resource scheduling on the initial DL BWP when the Msg4 includes a contention resolution message and does not include a radio resource control (RRC) release message, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling.

In an optional implementation, the initial DL BWP further has a first CORESET and/or a first search space, where the first CORESET is a CORESET configured for the terminal device in the initial DL BWP, and the first search space is a search space configured for the terminal device in the initial DL BWP. The transmitting module <NUM> is configured to transmit a resource scheduling on the first CORESET and/or the first search space when the Msg4 includes a contention resolution message and does not include an RRC release message, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling.

In an optional implementation, the RACH includes a <NUM>-step RACH, and the transmitting module <NUM> is configured to receive, on the initial UL BWP, at least one of a preamble, a MsgA payload, a Msg3, a Msg3 retransmission, or an UL transmission dynamically scheduled by the network device transmitted by the terminal device.

In an optional implementation, the RACH includes a <NUM>-step RACH, and the transmitting module <NUM> is configured to transmit to the terminal device on the CORESET#<NUM> in the initial DL BWP at least one of an RAR, a Msg3 retransmission indication, a Msg4, or a MsgB.

In an optional implementation, the transmitting module <NUM> is configured to transmit a resource scheduling on the initial DL BWP when the MsgB includes a contention resolution message and does not include an RRC release message, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling; or transmit a resource scheduling on the initial DL BWP when the Msg4 includes a contention resolution message and does not includes an RRC release message, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling.

In an optional implementation, the initial DL BWP further has a first CORESET and/or a first search space, where the first CORESET is a CORESET configured for the terminal device in the initial DL BWP, and the first search space is a search space configured for the terminal device in the initial DL BWP. The transmitting module <NUM> is configured to transmit a resource scheduling on the first CORESET and/or the first search space when the MsgB includes a contention resolution message and does not include an RRC release message, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling; or transmit a resource scheduling on the first CORESET and/or the first search space when the Msg4 includes a contention resolution message and does not include an RRC release message, where the resource scheduling includes at least one of an UL scheduling or a DL scheduling.

In an optional implementation, the target bandwidth includes a first UL BWP and a first DL BWP, and the first UL BWP and the first DL BWP are BWPs configured for the terminal device and dedicated for the RACH-based SDT procedure.

In an optional implementation, the RACH includes a <NUM>-step RACH, and the transmitting module <NUM> is configured to receive, on the first UL BWP, at least one of a preamble, a Msg3, a Msg3 retransmission, or an UL transmission dynamically scheduled by the network device transmitted by the terminal device.

In an optional implementation, the RACH includes a <NUM>-step RACH, and the transmitting module <NUM> is configured to transmit to the terminal device on the first DL BWP at least one of an RAR, a Msg3 retransmission indication, an UL scheduling, a DL scheduling, or a Msg4.

In an optional implementation, the RACH includes a <NUM>-step RACH, and the transmitting module <NUM> is configured to receive, on the first UL BWP, at least one of a preamble, a MsgA payload, a Msg3, a Msg3 retransmission, or an UL transmission dynamically scheduled by the network device transmitted by the terminal device.

In an optional implementation, the RACH includes a <NUM>-step RACH, and the transmitting module <NUM> is configured to transmit to the terminal device on the first DL BWP at least one of an RAR, a Msg3 retransmission indication, a Msg4, an UL scheduling, a DL scheduling, or a MsgB.

<FIG> is a schematic structural diagram of a communication device (a terminal device or a network device) provided in an exemplary implementation of the disclosure. The communication device includes a processor <NUM>, a receiver <NUM>, a transmitter <NUM>, a memory <NUM>, and a bus <NUM>.

The processor <NUM> includes one or more processing cores, and the processor <NUM> executes various function applications and information processing by running software programs and modules.

The receiver <NUM> and the transmitter <NUM> may be implemented as a communication assembly, where the communication assembly may be a communication chip.

The memory <NUM> is coupled with the processor <NUM> through the bus <NUM>.

The memory <NUM> may be configured to store at least one instruction. The processor <NUM> is configured to execute the at least one instruction to implement various steps in the foregoing method implementations.

In addition, the memory <NUM> may be implemented by any type of volatile or nonvolatile storage device or combination thereof. The volatile or non-volatile storage device includes, but is not limited to, a magnetic disk or an optical disk, an electrically-erasable programmable read only memory (EEPROM), an erasable programmable ROM (EPROM), a static random access memory (SRAM), a ROM, a magnetic memory, a flash memory, a PROM.

When a computer device is implemented as a terminal device, a processor and a transceiver in the computer device involved in implementations of the disclosure can execute the steps performed by the terminal device in the method illustrated in any one of <FIG> described above, which will not be repeated herein.

In a possible implementation, the computer device is implemented as a terminal device. The processor is configured to determine a target bandwidth used for a RACH-based SDT procedure. The transceiver is configured to perform the RACH-based SDT procedure with a network device on the target bandwidth, where the SDT procedure is a data transmission procedure in an inactive state of the terminal device.

When a computer device is implemented as a network device, a processor and a transceiver in the computer device involved in implementations of the disclosure can execute the steps performed by the network device in the method illustrated in any one of <FIG> described above, which will not be repeated herein.

In a possible implementation, the computer device is implemented as a network device. The transceiver is configured to perform a RACH-based SDT procedure with a terminal device on a target bandwidth, where the SDT procedure is a data transmission procedure in an inactive state of the terminal device.

In an exemplary implementation, a computer-readable storage medium is further provided. The computer-readable storage medium is configured to store at least one instruction, at least one program, a code set, or an instruction set which is loaded and executed by a processor to implement the method for data transmission that is executed by the communication device and provided in the foregoing method implementations.

In an exemplary implementation, a chip is further provided. The chip includes a programmable logic circuit or a program instruction. The chip, when run on the computer device, is configured to implement the method for data transmission described in the above aspects.

In an exemplary implementation, a computer program product is further provided. The computer program product, when executed on a processor of the computer device, is operable with the computer device to implement the method for data transmission described in the above aspects.

Those of ordinary skill in the art may understand that all or some of the steps of the foregoing implementations may be implemented by hardware, and may also be implemented by a program instructing relevant hardware. The program may be stored in a computer-readable storage medium. The storage medium may be a ROM, a magnetic disk, or an optical disk.

Claim 1:
A method for data transmission, being applied to a terminal device and comprising:
determining an initial uplink -UL- bandwidth part -BWP- and an initial downlink -DL- BWP as a target bandwidth used for a random access channel - RACH-based small data transmission -SDT- procedure, wherein the initial DL BWP has a control resource set #<NUM> -CORESET#<NUM>-, wherein the RACH comprises a <NUM>-step RACH; and
performing (<NUM>) the RACH-based SDT procedure with a network device on the target bandwidth, the performing (<NUM>) comprising:
receiving, on the CORESET#<NUM> in the initial DL BWP, at least one of a random access response -RAR-, a Msg3 retransmission indication, or a message <NUM> - Msg4- transmitted by the network device, wherein the SDT procedure is a data transmission procedure in an inactive state of the terminal device.