Data transmission method and device, communication equipment and storage medium

By determining the target bandwidth in the terminal device and performing small data transmission on it, the problem of insufficient configuration of small data transmission bandwidth in the prior art is solved, efficient data transmission in the inactive state is achieved, and the power consumption of the terminal device is reduced .

CN119071919APending Publication Date: 2024-12-03GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202411485991.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2021-01-07
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

The prior art fails to effectively configure the bandwidth for performing small data transmission processes, resulting in a large power consumption of terminal devices when performing data transmission in an inactive state.

Method used

Before performing a small data transmission process based on RACH, the terminal device determines the target bandwidth and performs data transmission on the bandwidth, including initial uplink BWP and initial downlink BWP or first uplink BWP and first downlink dedicated to small data transmission. BWP.

Benefits of technology

By determining the target bandwidth, the terminal device can efficiently complete small data transmission in an inactive state, reduce power consumption, and improve the data transmission capability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119071919A_ABST
    Figure CN119071919A_ABST
Patent Text Reader

Abstract

The invention discloses a data transmission method and device, communication equipment and a storage medium, and relates to the field of wireless communication. The method is applied to the terminal equipment, and comprises the following steps: determining a target bandwidth for a small data transmission process based on the RACH; and executing the small data transmission process based on the RACH with network equipment on the target bandwidth, wherein the small data transmission process is a data transmission process when the terminal device is in an inactive state. In the embodiment of the invention, the terminal equipment can realize a small data transmission process based on the RACH based on the determined target bandwidth.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of wireless communications, and in particular to a data transmission method, apparatus, communication equipment and storage medium. Background Art

[0002] The RRC_INACTIVE state (i.e., inactive state) is a new radio resource control (RRC) state introduced by the New Radio (NR) system from the perspective of energy saving.

[0003] Small Data Transmission (SDT) was introduced in R17. The small data transmission process corresponding to small data transmission is a non-active data transmission process. Through the small data transmission process, the terminal device does not need to enter the RRC_CONNECTED state (i.e., the connected state), and can complete data transmission in the non-active state, thereby reducing the power consumption and overhead of the terminal device.

[0004] The related technology has not yet proposed a solution on how to configure the bandwidth for executing the small data transmission process. Summary of the invention

[0005] The embodiments of the present application provide a data transmission method, apparatus, communication device and storage medium, and the terminal device can implement a small data transmission process based on a random access channel (RACH) based on a determined target bandwidth. The technical solution is as follows:

[0006] According to one aspect of the present application, a data transmission method is provided, which is applied to a terminal device, and the method includes:

[0007] Determining a target bandwidth for a RACH-based small data transmission process;

[0008] Performing the RACH-based small data transmission process with the network device on the target bandwidth;

[0009] The small data transmission process is a data transmission process when the terminal device is in an inactive state.

[0010] According to one aspect of the present application, a data transmission method is provided, which is applied to a network device, and the method includes:

[0011] A small data transmission process based on RACH is performed between the terminal device and the target bandwidth;

[0012] The small data transmission process is a data transmission process when the terminal device is in an inactive state.

[0013] According to one aspect of the present application, there is provided a data transmission device, which is applied to a terminal device, and the device includes: a bandwidth determination module and a transmission module;

[0014] The bandwidth determination module is used to determine the target bandwidth for the RACH-based small data transmission process;

[0015] The transmission module is used to perform the RACH-based small data transmission process between the network device and the target bandwidth;

[0016] The small data transmission process is a data transmission process when the terminal device is in an inactive state.

[0017] According to one aspect of the present application, there is provided a data transmission device, which is applied to a network device, and the device includes: a transmission module;

[0018] The transmission module is used to perform a RACH-based small data transmission process with the terminal device on the target bandwidth;

[0019] The small data transmission process is a data transmission process when the terminal device is in an inactive state.

[0020] According to one aspect of the present application, a terminal device is provided, the terminal device comprising: a processor and a transceiver connected to the processor; wherein,

[0021] The processor is configured to determine a target bandwidth for a RACH-based small data transmission process;

[0022] The transceiver is used to perform the RACH-based small data transmission process between the network device and the target bandwidth;

[0023] The small data transmission process is a data transmission process when the terminal device is in an inactive state.

[0024] According to one aspect of the present application, a network device is provided, the network device comprising: a processor and a transceiver connected to the processor; wherein:

[0025] The transceiver is used to perform a RACH-based small data transmission process with a terminal device on a target bandwidth;

[0026] The small data transmission process is a data transmission process when the terminal device is in an inactive state.

[0027] According to one aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores executable instructions, and the executable instructions are loaded and executed by a processor to implement the data transmission method as described in the above aspect.

[0028] According to one aspect of an embodiment of the present application, a chip is provided, which includes a programmable logic circuit and / or program instructions. When the chip runs on a computer device, it is used to implement the data transmission method described in the above aspect.

[0029] According to one aspect of the present application, a computer program product is provided. When the computer program product is executed on a processor of a computer device, the computer device executes the data transmission method described in the above aspect.

[0030] The technical solution provided by the embodiments of the present application includes at least the following beneficial effects:

[0031] Before the terminal device executes the RACH-based small data transmission process, the terminal device first determines the target bandwidth, and then implements the RACH-based small data transmission process on the target bandwidth, thereby providing an implementation method for determining the bandwidth for executing the small data transmission process. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0033] Figure 1 is a schematic diagram of part of the bandwidth provided by the related technology;

[0034] Figure 2 is a schematic diagram of a random access process provided by the related art;

[0035] Figure 3 is a block diagram of a communication system provided by an exemplary embodiment of the present application;

[0036] Figure 4 is a flow chart of a data transmission method provided by an exemplary embodiment of the present application;

[0037] Figure 5 is a flow chart of a data transmission method provided by an exemplary embodiment of the present application;

[0038] Figure 6 is a schematic diagram of an initial downlink BWP provided by an exemplary embodiment of the present application;

[0039] Figure 7 is a schematic diagram of a RACH-based small data transmission process provided by an exemplary embodiment of the present application;

[0040] Figure 8 is a schematic diagram of a RACH-based small data transmission process provided by an exemplary embodiment of the present application;

[0041] Fig. 9 is a schematic diagram of a RACH-based small data transmission process provided by an exemplary embodiment of the present application;

[0042] Fig.10 is a flow chart of a data transmission method provided by an exemplary embodiment of the present application;

[0043] Fig.11 is a schematic diagram of a RACH-based small data transmission process provided by an exemplary embodiment of the present application;

[0044] Fig.12 is a schematic diagram of a RACH-based small data transmission process provided by an exemplary embodiment of the present application;

[0045] Fig.13 is a schematic diagram of a RACH-based small data transmission process provided by an exemplary embodiment of the present application;

[0046] Fig.14 is a structural block diagram of a data transmission device provided by an exemplary embodiment of the present application;

[0047] Fig.15 is a structural block diagram of a data transmission device provided by an exemplary embodiment of the present application;

[0048] Fig.16 It is a structural diagram of a communication device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0049] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0050] First, the nouns involved in the embodiments of the present application are briefly introduced:

[0051] RRC Status:

[0052] In order to reduce air interface signaling and quickly restore wireless connections and data services, a new RRC state, the RRC_INACTIVE state, is defined in NR.

[0053] RRC_INACTIVE state (i.e. inactive state): mobility is based on cell selection reselection of the terminal device, there is a connection between the Core Network (CN) and the NR, the UE access context exists on a certain network device, paging is triggered by the Radio Access Network (RAN), the RAN-based paging area is managed by the RAN, and the network device side knows the location of the terminal device based on the RAN paging area level.

[0054] Bandwidth Part (BWP):

[0055] BWP is a concept introduced in NR. BWP defines an access bandwidth that is smaller than the cell system bandwidth and terminal capability. All transceiver operations of the terminal device can be performed within this smaller bandwidth, thereby achieving more flexible, more efficient, and lower power consumption terminal operations. For example, Figure 1 As shown, the terminal device can flexibly select BWPs of different bandwidths according to business requirements.

[0056] In the downlink direction, the terminal device is configured with up to 4 downlink BWPs. At any time, only one downlink BWP can be activated, and the terminal device receives the downlink channel on the activated downlink BWP. In the uplink direction, the terminal device is configured with up to 4 uplink BWPs. At any time, only one uplink BWP can be activated, and the terminal device receives the uplink channel on the activated uplink BWP; if the terminal device is configured with a supplementary uplink (SUL) carrier, 4 additional uplink BWPs can be configured. At any time, only one uplink BWP can be activated, and the terminal device receives the uplink channel on the activated uplink BWP.

[0057] For the downlink BWP, each downlink BWP contains at least one control resource set (Control Resource Set, CORESET) for receiving and detecting the physical downlink control channel (Physical Downlink Control Channel, PDCCH), that is, CORESET is the time and frequency range for the terminal device to search for PDCCH.

[0058] In a downlink BWP, CORESET can occupy continuous or non-continuous frequency domain resources. The network device can use a bitmap in RRC signaling to indicate the physical resource blocks (PRBs) occupied by CORESET in the downlink BWP. Each bit in the bitmap indicates an RB group containing 6 resource blocks (RBs).

[0059] In addition, the duration parameter in the CORESET configuration is used to describe the time domain length of the CORESET. Since the CORESET itself does not carry information about the time domain position, the CORESET describes a time domain area whose time domain position is not fixed and can float, which is determined by the duration parameter. Therefore, the network device needs to further specify the time domain area for the terminal device to receive the PDCCH by configuring the search space.

[0060] The uplink BWP and downlink BWP mentioned above are terminal-dedicated BWPs (i.e., UE-dedicated BWPs) configured using RRC dedicated signaling. In addition, the terminal device is also configured with an initial uplink BWP (i.e., initial UL BWP) and an initial downlink BWP (i.e., initial DL BWP). Before the terminal device enters the connected state, it works on the initial uplink BWP or the initial downlink BWP.

[0061] The initial uplink BWP is configured in the System Information Block 1 (SIB1), and the terminal device completes the transmission of the preamble, message 3 (ie, Msg3) or message A (ie, MsgA) in the initial random access process on the initial uplink BWP.

[0062] The initial downlink BWP includes CORESET#0, which is used to schedule SIB1, other system information (OtherSystem Information, OSI) or message 2 (i.e., Msg2), message 4 (i.e., Msg4) and other physical downlink control channel (Physical Downlink Shared Channel, PDSCH) information in the initial random access process. The method for the terminal device to determine CORESET#0 in the initial downlink BWP is as follows: when the terminal device completes the cell search, it obtains the synchronization signal block (Synchronization Signal Block, SSB) from the network device side, determines the frequency domain position of the SSB, and further determines the frequency offset value of CORESET#0 relative to the SSB through the physical broadcast channel (Physical Broadcast Channel, PBCH) in the SSB, and determines CORESET#0 based on the frequency domain position of the SSB and the frequency offset value of CORESET#0 relative to the SSB.

[0063] The standard supports two ways to determine the initial downlink BWP. The first is that if the initial downlink BWP is not configured by high-level signaling, the terminal device uses the frequency domain range of CORESET#0 as the bandwidth of the initial downlink BWP. The second is that if the initial downlink BWP is configured by high-level signaling (such as SIB1), the initial downlink BWP is determined according to the high-level signaling configuration. The significance of configuring the initial downlink BWP separately is that it can better support operations such as adding serving cells and cell switching, while supporting large bandwidth operations of terminal devices.

[0064] like Figure 2 As shown, for the case where the initial downlink BWP is configured separately, during the random access process, the terminal device receives a downlink message sent by the network device on CORESET#0, such as a random access response (Random Access Response, RAR), a contention resolution (Contention Resolution) message, a radio resource control establishment message (ie, RRCSetup) or a radio resource control release message (ie, RRCRelease) or a radio resource control reestablishment message (ie, RRCReestablishment). After receiving RRCSetup or RRCRelease or RRCReestablishment, the terminal device works on the initial downlink BWP.

[0065] Small Data Transmission (SDT):

[0066] Small data transmission is a data transmission mode configured for terminal devices in an inactive state. Through the small data transmission process, the terminal device can complete data transmission without entering the connection state, thereby reducing the power consumption and overhead of the terminal device.

[0067] Optionally, the small data transmission process includes: a small data transmission process based on a configured grant (Configured Grant, CG) and a small data transmission process based on a RACH.

[0068] The present application provides the following solution to the problem of how to configure the bandwidth for executing the small data transmission process.

[0069] Figure 3 A block diagram of a communication system provided by an exemplary embodiment of the present application is shown. The communication system may include: an access network 12 and a terminal device 14.

[0070] The access network 12 includes several network devices 120. The network device 120 may be a base station, which is a device deployed in the access network to provide wireless communication functions for the terminal. The base station may include various forms of macro base stations, micro base stations, relay stations, access points, and the like. In systems using different wireless access technologies, the names of devices with base station functions may be different. For example, in an LTE system, it is called eNodeB or eNB; in a 5G NR-U system, it is called gNodeB or gNB. With the evolution of communication technology, the description of "base station" may change. For the convenience of the embodiments of the present application, the above-mentioned devices that provide wireless communication functions for the terminal device 14 are collectively referred to as network devices.

[0071] The terminal device 14 may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem, as well as various forms of user equipment, mobile stations (MS), terminals, etc. For ease of description, the above-mentioned devices are collectively referred to as terminals. The network device 120 and the terminal device 14 communicate with each other through some air interface technology, such as a Uu interface. Optionally, the terminal device 14 supports the execution of a small data transmission process in an inactive state.

[0072] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-based access to Unlicensed spectrum, LTE-U) system, NR-U system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, Wireless Local Area Network (WLAN) system. Networks, WLAN), Wireless Fidelity (WiFi), next generation communication systems or other communication systems, etc.

[0073] Generally speaking, the number of connections supported by traditional communication systems is limited and easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle to vehicle (V2V) communication and vehicle to everything (V2X) system, etc. The embodiments of the present application can also be applied to these communication systems.

[0074] Figure 4FIG. 1 is a flowchart of a data transmission method provided by an exemplary embodiment of the present application. The method can be applied to Figure 3 In the communication system shown, the method includes:

[0075] Step 410: The terminal device determines a target bandwidth for a RACH-based small data transmission process.

[0076] Before executing the RACH-based small data transmission process, the terminal device determines a target bandwidth for the RACH-based small data transmission process. Optionally, the target bandwidth includes: a target bandwidth for uplink and a target bandwidth for downlink.

[0077] Optionally, the terminal device determines the target bandwidth for the RACH-based small data transmission process according to the configuration of the high-level signaling by receiving high-level signaling sent by the network device, such as SIB1.

[0078] Among them, the small data transmission process is the data transmission process when the terminal device is in an inactive state.

[0079] Small data transmission is a data transmission method configured for terminal devices in an inactive state, which does not require an RRC connection to be established between the terminal device and the network device. For terminal devices with small data volume and low transmission frequency, if the RRC connection with the network device is restored through the connection recovery process before data transmission, the terminal device needs to return to the inactive state after the data transmission is completed, and the power consumption of the terminal device is relatively large. By performing a small data transmission process in an inactive state, the terminal device can avoid the transition of the RRC state, thereby reducing the power consumption of the terminal device.

[0080] Optionally, the small data transmission process includes: a small data transmission process based on CG and a small data transmission process based on RACH. In the embodiment of the present application, the small data transmission process based on RACH is targeted. Among them, the small data transmission process based on RACH can be a small data transmission process based on 2-step RACH, or a small data transmission process based on 4-step RACH, and the embodiment of the present application does not limit this.

[0081] Step 420: On the target bandwidth, a small data transmission process based on RACH is performed between the terminal device and the network device.

[0082] After the terminal device determines the target bandwidth, the terminal device and the network device perform a small data transmission process based on RACH on the target bandwidth.

[0083] Optionally, the target bandwidth includes: a target bandwidth for uplink and a target bandwidth for downlink. The terminal device performs uplink transmission at the target bandwidth for uplink, and the network device performs uplink reception at the target bandwidth for uplink; the terminal device performs downlink reception at the target bandwidth for downlink, and the network device performs downlink transmission at the target bandwidth for downlink.

[0084] To sum up, the method provided in this embodiment is that before the terminal device executes the RACH-based small data transmission process, the terminal device first determines the target bandwidth, and then implements the RACH-based small data transmission process on the target bandwidth, thereby providing an implementation method for determining the bandwidth for executing the small data transmission process.

[0085] Based on Figure 4 In the optional embodiment, there are two different schemes for the target bandwidth.

[0086] 1) The target bandwidth includes: initial uplink BWP and initial downlink BWP.

[0087] Among them, the initial uplink BWP and the initial downlink BWP are the working bandwidths determined by the terminal device during the initial access process.

[0088] That is, the terminal device determines the initial uplink BWP and the initial downlink BWP during the initial access process, and uses the initial uplink BWP and the initial downlink BWP to perform a RACH-based small data transmission process between the terminal device and the network device.

[0089] 2) The target bandwidth includes: a first uplink BWP and a first downlink BWP.

[0090] Among them, the first uplink BWP and the first downlink BWP are configured for the terminal device and are BWPs dedicated to the small data transmission process based on RACH.

[0091] That is, for the RACH-based small data transmission process, the first uplink BWP and the first downlink BWP are introduced, and the RACH-based small data transmission process is performed between the terminal device and the network device using the newly introduced first uplink BWP and the first downlink BWP.

[0092] The following is an exemplary description of different solutions for the above two target bandwidths.

[0093] 1) The target bandwidth includes: initial uplink BWP and initial downlink BWP.

[0094] based on Figure 4 For an alternative embodiment, please refer to Figure 5 , which shows a flowchart of a data transmission method provided by an exemplary embodiment of the present application. The method can be applied to Figure 3 In the communication system shown, the method comprises the following steps:

[0095] In step 510, the terminal device determines the initial uplink BWP and the initial downlink BWP as the target bandwidth, and the initial downlink BWP includes CORESET#0.

[0096] The initial uplink BWP and the initial downlink BWP are the working bandwidths determined by the terminal device during the initial access process. CORESET#0 is a set of control resources used to carry the scheduling information of SIB1 or Remaining Minimum System Information (RMSI). Figure 6 As shown, the initial downlink BWP includes CORESET#0.

[0097] Optionally, the initial uplink BWP and the initial downlink BWP are determined based on SIB1 scheduled by CORESET#0. That is, after determining CORESET#0, the terminal device receives SIB1 scheduled by CORESET#0 and determines the initial uplink BWP and the initial downlink BWP through SIB1.

[0098] Optionally, the process of the terminal device determining CORESET#0 includes: when the terminal device completes the cell search, it obtains the SSB from the network device side, determines the frequency domain position of the SSB, and further determines the frequency offset value of CORESET#0 relative to the SSB through the PBCH in the SSB, and determines CORESET#0 based on the frequency domain position of the SSB and the frequency offset value of CORESET#0 relative to the SSB.

[0099] Step 520: On the target bandwidth, a small data transmission process based on RACH is performed between the terminal device and the network device.

[0100] Optionally, the RACH-based small data transmission process includes: a four-step RACH-based small data transmission process and a two-step RACH-based small data transmission process.

[0101] 1. On the target bandwidth, a small data transmission process based on the four-step RACH is performed between the terminal device and the network device.

[0102] Optionally, on the initial uplink BWP, the terminal device sends at least one of a preamble code, message 3, a retransmission of message 3, and an uplink transmission dynamically scheduled by the network device to the network device; correspondingly, on the initial uplink BWP, the network device receives at least one of a preamble code, message 3, a retransmission of message 3, and an uplink transmission dynamically scheduled by the network device sent by the terminal device.

[0103] Optionally, on CORESET#0 in the initial downlink BWP, the terminal device receives at least one of a random access response, a retransmission indication of message 3, and message 4. Correspondingly, on CORESET#0 in the initial downlink BWP, the network device sends at least one of a random access response, a retransmission indication of message 3, and message 4 to the terminal device.

[0104] It is understandable that after completing the transmission of message 4, the terminal device is still in an inactive state, and continuous uplink transmission or downlink transmission can be performed between the terminal device and the network device. In order to receive the uplink scheduling or downlink scheduling required for continuous uplink transmission or downlink transmission, the bandwidth can be switched from CORESET#0 to a larger bandwidth.

[0105] In a possible implementation, in response to message 4 including a contention conflict resolution message and message 4 not including a radio resource control release message, the terminal device receives resource scheduling on an initial downlink BWP, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling. Correspondingly, in response to message 4 including a contention conflict resolution message and message 4 not including a radio resource control release message, the network device sends resource scheduling on an initial downlink BWP, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling.

[0106] That is, when message 4 indicates that contention resolution has been completed and message 4 does not indicate termination of the small data transmission process, the terminal device is switched from CORESET#0 to the initial downlink BWP with a larger bandwidth to receive subsequent resource scheduling.

[0107] In another possible implementation, the initial downlink BWP also includes a first CORESET and / or a first search space, the first CORESET is a CORESET configured for the terminal device in the initial downlink BWP, and the first search space is a search space configured for the terminal device in the initial downlink BWP.

[0108] In response to message 4 including a contention conflict resolution message, and message 4 not including a radio resource control release message, the terminal device receives resource scheduling on the first CORESET and / or the first search space, and the resource scheduling includes at least one of uplink scheduling and downlink scheduling. Correspondingly, in response to message 4 including a contention conflict resolution message, and message 4 not including a radio resource control release message, the network device sends resource scheduling on the first CORESET and / or the first search space, and the resource scheduling includes at least one of uplink scheduling and downlink scheduling.

[0109] That is, the network device configures the first CORESET dedicated to the small data transmission process for the terminal device; or, the network device configures the first search space dedicated to the small data transmission process for the terminal device; or, the network device configures the first CORESET and the first search space dedicated to the small data transmission process for the terminal device. When message 4 indicates that contention resolution has been completed and message 4 does not indicate termination of the small data transmission process, the terminal device is switched from CORESET#0 to the first CORESET and / or the first search space with a larger bandwidth to receive subsequent resource scheduling.

[0110] Optionally, the first CORESET and / or the first search space are determined based on SIB1 scheduled by CORESET#0. That is, after determining CORESET#0, the terminal device receives SIB1 scheduled by CORESET#0, and in addition to determining the initial uplink BWP and the initial downlink BWP through SIB1, it also determines the first CORESET through SIB1; or, the first search space; or, the first CORESET and the first search space.

[0111] Optionally, uplink scheduling and downlink scheduling belong to the same RACH-based small data transmission process.

[0112] For example, Figure 7 As shown, the small data transmission process based on the four-step RACH between the terminal device and the network device includes the following steps:

[0113] S11, the terminal device sends a preamble code on the initial uplink BWP.

[0114] Accordingly, the network device receives the preamble on the initial uplink BWP.

[0115] S12, the network device sends a random access response on CORESET#0.

[0116] Correspondingly, the terminal device receives the random access response on CORESET#0.

[0117] S13, the terminal device sends message 3 on the initial uplink BWP.

[0118] Accordingly, the network device receives message 3 on the initial uplink BWP.

[0119] Optionally, message 3 includes an RRC message and uplink data.

[0120] S14, the network device sends message 4 on CORESET#0.

[0121] Correspondingly, the terminal device receives message 4 on CORESET#0.

[0122] Optionally, message 4 includes a contention conflict resolution message but does not include a radio resource control release message.

[0123] S15, the network device sends an uplink scheduling on the initial downlink BWP.

[0124] Correspondingly, the terminal device receives uplink scheduling on the initial downlink BWP.

[0125] In another implementation, the network device sends uplink scheduling on the first CORESET and / or the first search space. Correspondingly, the terminal device receives uplink scheduling on the first CORESET and / or the first search space.

[0126] S16, the network device sends a downlink schedule on the initial downlink BWP.

[0127] Correspondingly, the terminal device receives downlink scheduling on the initial downlink BWP.

[0128] In another implementation, the network device sends downlink scheduling on the first CORESET and / or the first search space. Correspondingly, the terminal device receives downlink scheduling on the first CORESET and / or the first search space.

[0129] 2. On the target bandwidth, a small data transmission process based on two-step RACH is performed between the terminal device and the network device.

[0130] Optionally, on the initial uplink BWP, the terminal device sends at least one of a preamble, a message A payload, a message 3, a retransmission of message 3, and an uplink transmission dynamically scheduled by the network device to the network device. Correspondingly, on the initial uplink BWP, the network device receives at least one of a preamble, a message A payload, a message 3, a retransmission of message 3, and an uplink transmission dynamically scheduled by the network device sent by the terminal device.

[0131] Optionally, on CORESET#0 in the initial downlink BWP, the terminal device receives at least one of a random access response, a retransmission indication of message 3, message 4, and message B sent by the network device. Correspondingly, on CORESET#0 in the initial downlink BWP, the network device sends at least one of a random access response, a retransmission indication of message 3, message 4, and message B to the terminal device.

[0132] It can be understood that in two-step RACH, if the network device only receives the preamble sent by the terminal device but does not receive the message A payload, the network device sends a random access response to the terminal device, and the terminal device sends message 3 to the network device after receiving the random access response. When the network device successfully receives message 3, it feeds back message 4 to the terminal device; if the network device successfully receives the preamble sent by the terminal device and the message A payload, the network device feeds back message B to the terminal device. After completing the transmission of message 4 or message B, the terminal device is still in an inactive state, and continuous uplink transmission or downlink transmission can be performed between the terminal device and the network device. In order to receive the uplink scheduling or downlink scheduling required for continuous uplink transmission or downlink transmission, the bandwidth can be switched from CORESET#0 to a larger bandwidth.

[0133] In a possible implementation, in response to message B including a contention conflict resolution message and message B not including a radio resource control release message, the terminal device receives resource scheduling on the initial downlink BWP, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling; or, in response to message 4 including a contention conflict resolution message and message 4 not including a radio resource control release message, the terminal device receives resource scheduling on the initial downlink BWP, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling. Accordingly, in response to message B including a contention conflict resolution message and message B not including a radio resource control release message, the network device sends resource scheduling on the initial downlink BWP, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling; or, in response to message 4 including a contention conflict resolution message and message 4 not including a radio resource control release message, the network device sends resource scheduling on the initial downlink BWP, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling.

[0134] That is, when message 4 or message B indicates that contention resolution has been completed and message 4 or message B does not indicate termination of the small data transmission process, the terminal device is switched from CORESET#0 to the initial downlink BWP with a larger bandwidth to receive subsequent resource scheduling.

[0135] In another possible implementation, the initial downlink BWP also includes a first CORESET and / or a first search space, the first CORESET is a CORESET configured for the terminal device in the initial downlink BWP, and the first search space is a search space configured for the terminal device in the initial downlink BWP.

[0136] In response to message B including a contention conflict resolution message, and message B not including a radio resource control release message, the terminal device receives resource scheduling on the first CORESET and / or the first search space, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling; or, in response to message 4 including a contention conflict resolution message, and message 4 not including a radio resource control release message, the terminal device receives resource scheduling on the first CORESET and / or the first search space, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling. Correspondingly, in response to message B including a contention conflict resolution message, and message B not including a radio resource control release message, the network device sends resource scheduling on the first CORESET and / or the first search space, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling; or, in response to message 4 including a contention conflict resolution message, and message 4 not including a radio resource control release message, the network device sends resource scheduling on the first CORESET and / or the first search space, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling.

[0137] That is, the network device configures the first CORESET dedicated to the small data transmission process for the terminal device; or, the network device configures the first search space dedicated to the small data transmission process for the terminal device; or, the network device configures the first CORESET and the first search space dedicated to the small data transmission process for the terminal device. When message 4 or message B indicates that contention resolution has been completed, and message 4 or message B does not indicate termination of the small data transmission process, the terminal device is switched from CORESET#0 to the first CORESET and / or the first search space with a larger bandwidth to receive subsequent resource scheduling.

[0138] Optionally, the first CORESET and / or the first search space are determined based on SIB1 scheduled by CORESET#0. That is, after determining CORESET#0, the terminal device receives SIB1 scheduled by CORESET#0, and in addition to determining the initial uplink BWP and the initial downlink BWP through SIB1, it also determines the first CORESET through SIB1; or, the first search space; or, the first CORESET and the first search space.

[0139] Optionally, uplink scheduling and downlink scheduling belong to the same RACH-based small data transmission process.

[0140] For example, Figure 8 As shown, the small data transmission process based on two-step RACH between the terminal device and the network device includes the following steps:

[0141] S21, the terminal device sends a preamble and a message A payload on the initial uplink BWP.

[0142] Accordingly, the network device receives the preamble and the message A payload on the initial uplink BWP.

[0143] Optionally, the message A payload includes an RRC message and uplink data.

[0144] S22, the network device sends message B on CORESET#0.

[0145] Correspondingly, the terminal device receives message B on CORESET#0.

[0146] Optionally, message B includes a contention conflict resolution message but does not include a radio resource control release message.

[0147] S23, the network device sends an uplink scheduling on the initial downlink BWP.

[0148] Correspondingly, the terminal device receives uplink scheduling on the initial downlink BWP.

[0149] In another implementation, the network device sends uplink scheduling on the first CORESET and / or the first search space. Correspondingly, the terminal device receives uplink scheduling on the first CORESET and / or the first search space.

[0150] S24, the network device sends a downlink schedule on the initial downlink BWP.

[0151] Correspondingly, the terminal device receives downlink scheduling on the initial downlink BWP.

[0152] In another implementation, the network device sends downlink scheduling on the first CORESET and / or the first search space. Correspondingly, the terminal device receives downlink scheduling on the first CORESET and / or the first search space.

[0153] For example, Fig. 9 As shown, the small data transmission process based on two-step RACH between the terminal device and the network device includes the following steps:

[0154] S31, the terminal device sends a preamble and a message A payload on the initial uplink BWP.

[0155] Accordingly, the network device only receives the preamble code on the initial uplink BWP and fails to successfully receive the message A payload.

[0156] S32, the network device sends a random access response on CORESET#0.

[0157] Correspondingly, the terminal device receives the random access response on CORESET#0.

[0158] S33, the terminal device sends message 3 on the initial uplink BWP.

[0159] Accordingly, the network device receives message 3 on the initial uplink BWP.

[0160] Optionally, message 3 includes an RRC message and uplink data.

[0161] S34, the network device sends message 4 on CORESET#0.

[0162] Correspondingly, the terminal device receives message 4 on CORESET#0.

[0163] Optionally, message 4 includes a contention conflict resolution message but does not include a radio resource control release message.

[0164] S35, the network device sends an uplink schedule on the initial downlink BWP.

[0165] Correspondingly, the terminal device receives uplink scheduling on the initial downlink BWP.

[0166] In another implementation, the network device sends uplink scheduling on the first CORESET and / or the first search space. Correspondingly, the terminal device receives uplink scheduling on the first CORESET and / or the first search space.

[0167] S36, the network device sends a downlink schedule on the initial downlink BWP.

[0168] Correspondingly, the terminal device receives downlink scheduling on the initial downlink BWP.

[0169] In another implementation, the network device sends downlink scheduling on the first CORESET and / or the first search space. Correspondingly, the terminal device receives downlink scheduling on the first CORESET and / or the first search space.

[0170] To sum up, the method provided in this embodiment, in the small data transmission process based on RACH, the terminal device can first perform a random access process on CORESET#0 in the initial uplink BWP and the initial downlink BWP, and then switch CORESET#0 to a larger initial downlink BWP, or switch CORESET#0 to a larger first CORESET and / or first search space, so as to facilitate subsequent uplink and downlink scheduling and uplink and downlink transmission, thereby enhancing the data transmission capability during the small data transmission process.

[0171] 2) The target bandwidth includes: a first uplink BWP and a first downlink BWP.

[0172] based on Figure 4 For an alternative embodiment, please refer to Fig.10 , which shows a flowchart of a data transmission method provided by an exemplary embodiment of the present application. The method can be applied to Figure 3 In the communication system shown, the method comprises the following steps:

[0173] Step 1010: The terminal device determines the first uplink BWP and the first downlink BWP as target bandwidths.

[0174] The first uplink BWP and the first downlink BWP are configured for the terminal device and are BWPs dedicated to the small data transmission process based on RACH. Optionally, the first downlink BWP includes CORESET#0.

[0175] Optionally, the first uplink BWP and the first downlink BWP are determined based on SIB1 scheduled by CORESET#0. That is, after determining CORESET#0, the terminal device receives SIB1 scheduled by CORESET#0 and determines the first uplink BWP and the first downlink BWP through SIB1.

[0176] Optionally, the process of the terminal device determining CORESET#0 includes: when the terminal device completes the cell search, it obtains the SSB from the network device side, determines the frequency domain position of the SSB, and further determines the frequency offset value of CORESET#0 relative to the SSB through the PBCH in the SSB, and determines CORESET#0 based on the frequency domain position of the SSB and the frequency offset value of CORESET#0 relative to the SSB.

[0177] Step 1020: A RACH-based small data transmission process is performed between the terminal device and the network device on the target bandwidth.

[0178] Optionally, the RACH-based small data transmission process includes: a four-step RACH-based small data transmission process and a two-step RACH-based small data transmission process.

[0179] 1. On the target bandwidth, a small data transmission process based on the four-step RACH is performed between the terminal device and the network device.

[0180] Optionally, on the first uplink BWP, the terminal device sends at least one of a preamble, message 3, a retransmission of message 3, and an uplink transmission dynamically scheduled by the network device to the network device. Correspondingly, on the first uplink BWP, the network device receives at least one of a preamble, message 3, a retransmission of message 3, and an uplink transmission dynamically scheduled by the network device sent by the terminal device.

[0181] Optionally, on the first downlink BWP, the terminal device receives at least one of a random access response, a retransmission indication of message 3, uplink scheduling, downlink scheduling, and message 4 sent by the network device. Correspondingly, on the first downlink BWP, the network device sends at least one of a random access response, a retransmission indication of message 3, uplink scheduling, downlink scheduling, and message 4 to the terminal device.

[0182] Optionally, uplink scheduling and downlink scheduling belong to the same RACH-based small data transmission process.

[0183] For example, Fig.11 As shown, the small data transmission process based on the four-step RACH between the terminal device and the network device includes the following steps:

[0184] S41, the terminal device sends a preamble code on the first uplink BWP.

[0185] Accordingly, the network device receives the preamble code on the first uplink BWP.

[0186] S42: The network device sends a random access response on the first downlink BWP.

[0187] Correspondingly, the terminal device receives a random access response on the first downlink BWP.

[0188] S43, the terminal device sends message 3 on the first uplink BWP.

[0189] Correspondingly, the network device receives message 3 on the first uplink BWP.

[0190] Optionally, message 3 includes an RRC message and uplink data.

[0191] S44, the network device sends message 4 on the first downlink BWP.

[0192] Correspondingly, the terminal device receives message 4 on the first downlink BWP.

[0193] S45, the network device sends an uplink scheduling on the first downlink BWP.

[0194] Correspondingly, the terminal device receives uplink scheduling on the first downlink BWP.

[0195] S46: The network device sends a downlink schedule on the first downlink BWP.

[0196] Correspondingly, the terminal device receives downlink scheduling on the first downlink BWP.

[0197] 2. On the target bandwidth, a small data transmission process based on two-step RACH is performed between the terminal device and the network device.

[0198] Optionally, on the first uplink BWP, the terminal device sends at least one of a preamble, a message A payload, a message 3, a retransmission of message 3, and an uplink transmission dynamically scheduled by the network device to the network device. Correspondingly, on the first uplink BWP, the network device receives at least one of a preamble, a message A payload, a message 3, a retransmission of message 3, and an uplink transmission dynamically scheduled by the network device sent by the terminal device.

[0199] Optionally, on the first downlink BWP, the terminal device receives at least one of a random access response, a retransmission indication of message 3, message 4, uplink scheduling, downlink scheduling, and message B sent by the network device. Correspondingly, on the first downlink BWP, the network device sends at least one of a random access response, a retransmission indication of message 3, message 4, uplink scheduling, downlink scheduling, and message B to the terminal device.

[0200] Optionally, uplink scheduling and downlink scheduling belong to the same RACH-based small data transmission process.

[0201] For example, Fig.12 As shown, the small data transmission process based on two-step RACH between the terminal device and the network device includes the following steps:

[0202] S51, the terminal device sends a preamble code and a message A payload on the first uplink BWP.

[0203] Accordingly, the network device receives the preamble and the message A payload on the first uplink BWP.

[0204] Optionally, the message A payload includes an RRC message and uplink data.

[0205] S52: The network device sends a message B on the first downlink BWP.

[0206] Correspondingly, the terminal device receives message B on the first downlink BWP.

[0207] S53: The network device sends an uplink scheduling on the first downlink BWP.

[0208] Correspondingly, the terminal device receives uplink scheduling on the first downlink BWP.

[0209] S54: The network device sends a downlink schedule on the first downlink BWP.

[0210] Correspondingly, the terminal device receives downlink scheduling on the first downlink BWP.

[0211] For example, Fig.13 As shown, the small data transmission process based on two-step RACH between the terminal device and the network device includes the following steps:

[0212] S61, the terminal device sends a preamble code and a message A payload on the first uplink BWP.

[0213] Accordingly, the network device only receives the preamble code on the first uplink BWP, and fails to successfully receive the message A payload.

[0214] S62: The network device sends a random access response on the first downlink BWP.

[0215] Correspondingly, the terminal device receives a random access response on the first downlink BWP.

[0216] S63, the terminal device sends message 3 on the first uplink BWP.

[0217] Correspondingly, the network device receives message 3 on the first uplink BWP.

[0218] Optionally, message 3 includes an RRC message and uplink data.

[0219] S64, the network device sends message 4 on the first downlink BWP.

[0220] Correspondingly, the terminal device receives message 4 on the first downlink BWP.

[0221] S65: The network device sends an uplink scheduling on the first downlink BWP.

[0222] Correspondingly, the terminal device receives uplink scheduling on the first downlink BWP.

[0223] S66: The network device sends a downlink schedule on the first downlink BWP.

[0224] Correspondingly, the terminal device receives downlink scheduling on the first downlink BWP.

[0225] To sum up, the method provided in this embodiment is to configure a dedicated first uplink BWP and a first downlink BWP for a small data transmission process based on RACH, so that the terminal device and the network device can implement a small data transmission process based on RACH on the first uplink BWP and the first downlink BWP.

[0226] It should be noted that the above method embodiments can be implemented separately or in combination, and this application does not limit this.

[0227] In the above-mentioned embodiments, the steps executed by the terminal device can be independently implemented as a data transmission method on the terminal device side, and the steps executed by the network device can be independently implemented as a data transmission method on the network device side.

[0228] Fig.14A structural block diagram of a data transmission device provided by an exemplary embodiment of the present application is shown. The device can be implemented as a terminal device, or implemented as a part of a terminal device. The device includes: a bandwidth determination module 1401 and a transmission module 1402;

[0229] The bandwidth determination module 1401 is used to determine the target bandwidth for the RACH-based small data transmission process;

[0230] The transmission module 1402 is used to perform the RACH-based small data transmission process between the network device and the target bandwidth;

[0231] The small data transmission process is a data transmission process when the terminal device is in an inactive state.

[0232] In an optional embodiment, the bandwidth determination module 1401 is used to determine an initial uplink BWP and an initial downlink BWP as the target bandwidth, and the initial downlink BWP includes CORESET#0.

[0233] In an optional embodiment, the RACH includes: a four-step RACH; the transmission module 1402 is used to send a preamble code, message 3, a retransmission of message 3, and at least one of uplink transmissions dynamically scheduled by the network device to the network device on the initial uplink BWP.

[0234] In an optional embodiment, the RACH includes: a four-step RACH; the transmission module 1402 is used to receive at least one of a random access response, a retransmission indication of message 3 and message 4 sent by the network device on the CORESET#0 in the initial downlink BWP.

[0235] In an optional embodiment, the transmission module 1402 is used to receive resource scheduling on the initial downlink BWP in response to the message 4 including a contention conflict resolution message and the message 4 not including a wireless resource control release message, the resource scheduling including: at least one of uplink scheduling and downlink scheduling.

[0236] In an optional embodiment, the initial downlink BWP further includes a first CORESET and / or a first search space, the first CORESET is a CORESET configured for the terminal device in the initial downlink BWP, and the first search space is a search space configured for the terminal device in the initial downlink BWP;

[0237] The transmission module 1402 is used to receive resource scheduling on the first CORESET and / or the first search space in response to the message 4 including a contention conflict resolution message and the message 4 not including a wireless resource control release message, wherein the resource scheduling includes at least one of uplink scheduling and downlink scheduling.

[0238] In an optional embodiment, the RACH includes: a two-step RACH; the transmission module 1402 is used to send a preamble code, a message A load, a message 3, a retransmission of message 3, and at least one of an uplink transmission dynamically scheduled by the network device to the network device on the initial uplink BWP.

[0239] In an optional embodiment, the RACH includes: a two-step RACH; the transmission module 1402 is used to receive at least one of a random access response, a retransmission indication of message 3, message 4 and message B sent by the network device on the CORESET#0 in the initial downlink BWP.

[0240] In an optional embodiment, the transmission module 1402 is used to receive resource scheduling on the initial downlink BWP in response to the message B including a contention conflict resolution message and the message B not including a wireless resource control release message, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling; or, the transmission module 1402 is used to receive resource scheduling on the initial downlink BWP in response to the message 4 including a contention conflict resolution message and the message 4 not including a wireless resource control release message, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling.

[0241] In an optional embodiment, the initial downlink BWP further includes a first CORESET and / or a first search space, the first CORESET is a CORESET configured for the terminal device in the initial downlink BWP, and the first search space is a search space configured for the terminal device in the initial downlink BWP;

[0242] The transmission module 1402 is used to receive resource scheduling on the first CORESET and / or the first search space in response to the message B including a contention conflict resolution message and the message B not including a wireless resource control release message, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling; or, the transmission module 1402 is used to receive resource scheduling on the first CORESET and / or the first search space in response to the message 4 including a contention conflict resolution message and the message 4 not including a wireless resource control release message, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling.

[0243] In an optional embodiment, the uplink scheduling and the downlink scheduling belong to the same RACH-based small data transmission process.

[0244] In an optional embodiment, the first CORESET and / or the first search space is determined based on SIB1 scheduled by the CORESET#0.

[0245] In an optional embodiment, the initial uplink BWP and the initial downlink BWP are determined based on SIB1 scheduled by the CORESET#0.

[0246] In an optional embodiment, the bandwidth determination module 1401 is used to determine the first uplink BWP and the first downlink BWP as the target bandwidth, and the first uplink BWP and the first downlink BWP are configured for the terminal device and are dedicated to the BWP of the RACH-based small data transmission process.

[0247] In an optional embodiment, the RACH includes: a four-step RACH; the transmission module 1402 is used to send at least one of a preamble code, message 3, retransmission of message 3 and uplink transmission dynamically scheduled by the network device to the network device on the first uplink BWP.

[0248] In an optional embodiment, the RACH includes: a four-step RACH; the transmission module 1402 is used to receive at least one of a random access response, a retransmission indication of message 3, uplink scheduling, downlink scheduling and message 4 sent by the network device on the first downlink BWP.

[0249] In an optional embodiment, the RACH includes: a two-step RACH; the transmission module 1402 is used to send at least one of a preamble code, a message A load, a message 3, a retransmission of message 3, and an uplink transmission dynamically scheduled by the network device to the network device on the first uplink BWP.

[0250] In an optional embodiment, the RACH includes: a two-step RACH; the transmission module 1402 is used to receive at least one of a random access response, a retransmission indication of message 3, message 4, uplink scheduling, downlink scheduling and message B sent by the network device on the first downlink BWP.

[0251] In an optional embodiment, the uplink scheduling and the downlink scheduling belong to the same RACH-based small data transmission process.

[0252] In an optional embodiment, the first uplink BWP and the first downlink BWP are determined based on SIB1 scheduled by CORESET#0.

[0253] Fig.15 A structural block diagram of a data transmission device provided by an exemplary embodiment of the present application is shown. The device can be implemented as a network device, or implemented as a part of a network device. The device includes: a transmission module 1501;

[0254] The transmission module 1501 is used to perform a RACH-based small data transmission process with a terminal device on a target bandwidth;

[0255] The small data transmission process is a data transmission process when the terminal device is in an inactive state.

[0256] In an optional embodiment, the target bandwidth includes: an initial uplink BWP and an initial downlink BWP, and the initial downlink BWP includes CORESET#0.

[0257] In an optional embodiment, the RACH includes: a four-step RACH; the transmission module 1501 is used to receive at least one of the preamble code, message 3, retransmission of message 3 and uplink transmission dynamically scheduled by the network device sent by the terminal device on the initial uplink BWP.

[0258] In an optional embodiment, the RACH includes: a four-step RACH; the transmission module 1501 is used to send a random access response, a retransmission indication of message 3, and at least one of message 4 to the terminal device on the CORESET#0 in the initial downlink BWP.

[0259] In an optional embodiment, the transmission module 1501 is used to send resource scheduling on the initial downlink BWP in response to the message 4 including a contention conflict resolution message and the message 4 not including a wireless resource control release message, wherein the resource scheduling includes: at least one of uplink scheduling and downlink scheduling.

[0260] In an optional embodiment, the initial downlink BWP further includes a first CORESET and / or a first search space, the first CORESET is a CORESET configured for the terminal device in the initial downlink BWP, and the first search space is a search space configured for the terminal device in the initial downlink BWP;

[0261] The transmission module 1501 is used to send resource scheduling on the first CORESET and / or the first search space in response to the message 4 including a contention conflict resolution message and the message 4 not including a wireless resource control release message, wherein the resource scheduling includes at least one of uplink scheduling and downlink scheduling.

[0262] In an optional embodiment, the RACH includes: a two-step RACH; the transmission module 1501 is used to receive at least one of the preamble code, message A load, message 3, retransmission of message 3 and uplink transmission dynamically scheduled by the network device sent by the terminal device on the initial uplink BWP.

[0263] In an optional embodiment, the RACH includes: a two-step RACH; the transmission module 1501 is used to send a random access response, a retransmission indication of message 3, message 4 and at least one of message B to the terminal device on the CORESET#0 in the initial downlink BWP.

[0264] In an optional embodiment, the transmission module 1501 is used to send resource scheduling on the initial downlink BWP in response to the message B including a contention conflict resolution message and the message B not including a wireless resource control release message, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling; or, the transmission module 1501 is used to send resource scheduling on the initial downlink BWP in response to the message 4 including a contention conflict resolution message and the message 4 not including a wireless resource control release message, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling.

[0265] In an optional embodiment, the initial downlink BWP further includes a first CORESET and / or a first search space, the first CORESET is a CORESET configured for the terminal device in the initial downlink BWP, and the first search space is a search space configured for the terminal device in the initial downlink BWP;

[0266] The transmission module 1501 is used to send resource scheduling on the first CORESET and / or the first search space in response to the message B including a contention conflict resolution message and the message B not including a wireless resource control release message, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling; or, the transmission module 1501 is used to send resource scheduling on the first CORESET and / or the first search space in response to the message 4 including a contention conflict resolution message and the message 4 not including a wireless resource control release message, and the resource scheduling includes: at least one of uplink scheduling and downlink scheduling.

[0267] In an optional embodiment, the uplink scheduling and the downlink scheduling belong to the same RACH-based small data transmission process.

[0268] In an optional embodiment, the first CORESET and / or the first search space is determined based on 1SIB1 scheduled by the CORESET#0.

[0269] In an optional embodiment, the initial uplink BWP and the initial downlink BWP are determined based on SIB1 scheduled by the CORESET#0.

[0270] In an optional embodiment, the target bandwidth includes: a first uplink BWP and a first downlink BWP, wherein the first uplink BWP and the first downlink BWP are configured for the terminal device and are BWPs dedicated to the RACH-based small data transmission process.

[0271] In an optional embodiment, the RACH includes: a four-step RACH; the transmission module 1501 is used to receive at least one of the preamble code, message 3, retransmission of message 3 and uplink transmission dynamically scheduled by the network device sent by the terminal device on the first uplink BWP.

[0272] In an optional embodiment, the RACH includes: a four-step RACH; the transmission module 1501 is used to send a random access response, a retransmission indication of message 3, uplink scheduling, downlink scheduling and at least one of message 4 to the terminal device on the first downlink BWP.

[0273] In an optional embodiment, the RACH includes: a two-step RACH; the transmission module 1501 is used to receive at least one of the preamble code, message A load, message 3, retransmission of message 3 and uplink transmission dynamically scheduled by the network device sent by the terminal device on the first uplink BWP.

[0274] In an optional embodiment, the RACH includes: a two-step RACH; the transmission module 1501 is used to send a random access response, a retransmission indication of message 3, message 4, uplink scheduling, downlink scheduling and at least one of message B to the terminal device on the first downlink BWP.

[0275] In an optional embodiment, the uplink scheduling and the downlink scheduling belong to the same RACH-based small data transmission process.

[0276] In an optional embodiment, the first uplink BWP and the first downlink BWP are determined based on SIB1 scheduled by CORESET#0.

[0277] Fig.16 A schematic diagram of the structure of a communication device (terminal device or network device) provided by an exemplary embodiment of the present application is shown. The communication device includes: a processor 101, a receiver 102, a transmitter 103, a memory 104 and a bus 105.

[0278] The processor 101 includes one or more processing cores. The processor 101 executes various functional applications and information processing by running software programs and modules.

[0279] The receiver 102 and the transmitter 103 may be implemented as a communication component, which may be a communication chip.

[0280] The memory 104 is connected to the processor 101 via a bus 105 .

[0281] The memory 104 may be used to store at least one instruction, and the processor 101 may be used to execute the at least one instruction to implement each step in the above method embodiment.

[0282] In addition, the memory 104 can be implemented by any type of volatile or non-volatile storage device or a 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 read-only memory (EPROM), a static random access memory (SRAM), a read-only memory (ROM), a magnetic memory, a flash memory, and a programmable read-only memory (PROM).

[0283] When the computer device is implemented as a terminal device, the processor and the transceiver in the computer device involved in the embodiment of the present application can execute the above Figures 4 to 13 In any of the methods shown, the steps performed by the terminal device are not repeated here.

[0284] In a possible implementation, when the computer device is implemented as a terminal device,

[0285] The processor is configured to determine a target bandwidth for a RACH-based small data transmission process;

[0286] The transceiver is used to perform the RACH-based small data transmission process between the network device and the target bandwidth;

[0287] The small data transmission process is a data transmission process when the terminal device is in an inactive state.

[0288] When the computer device is implemented as a network device, the processor and the transceiver in the computer device involved in the embodiment of the present application can execute the above Figures 4 to 13 In any of the methods shown, the steps performed by the network device are not repeated here.

[0289] In a possible implementation, when the computer device is implemented as a network device,

[0290] The transceiver is used to perform a small data transmission process based on a random access channel RACH with a terminal device on a target bandwidth;

[0291] The small data transmission process is a data transmission process when the terminal device is in an inactive state.

[0292] In an exemplary embodiment, a computer-readable storage medium is also provided, in which at least one instruction, at least one program, a code set or an instruction set is stored. The at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by a processor to implement the data transmission method performed by a communication device provided by the above-mentioned various method embodiments.

[0293] In an exemplary embodiment, a chip is also provided. The chip includes a programmable logic circuit and / or program instructions. When the chip runs on a computer device, it is used to implement the data transmission method described in the above aspects.

[0294] In an exemplary embodiment, a computer program product is further provided. When the computer program product is executed on a processor of a computer device, the computer device executes the data transmission method described in the above aspects.

[0295] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0296] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A data transmission method, characterized in that: Applied in a terminal device, the method comprises: Determining a target bandwidth for a small data transmission process based on a random access channel RACH; Performing the RACH-based small data transmission process with the network device on the target bandwidth; The small data transmission process is a data transmission process when the terminal device is in an inactive state.

2. The method according to claim 1, characterized in that The determining of a target bandwidth for a RACH-based small data transmission process comprises: An initial uplink bandwidth BWP and an initial downlink BWP are determined as the target bandwidth, and the initial downlink BWP includes a resource control set CORESET#0.

3. The method according to claim 2, characterized in that The RACH includes: a four-step RACH; the small data transmission process based on the RACH is performed between the network device on the target bandwidth, including: At least one of a random access response, a retransmission indication of message 3 and message 4 sent by the network device is received on the CORESET#0 in the initial downlink BWP.

4. The method according to claim 3, characterized in that The initial downlink BWP further includes a first CORESET and / or a first search space, wherein the first CORESET is a CORESET configured for the terminal device in the initial downlink BWP, and the first search space is a search space configured for the terminal device in the initial downlink BWP; The method further comprises: In response to the message 4 including a contention conflict resolution message and the message 4 not including a radio resource control release message, receiving resource scheduling on the first CORESET and / or the first search space, the resource scheduling including at least one of uplink scheduling and downlink scheduling.

5. The method according to claim 2, characterized in that: The RACH includes: a two-step RACH; the small data transmission process based on the RACH is performed between the network device on the target bandwidth, including: At least one of a random access response, a retransmission indication of message 3, message 4 and message B sent by the network device is received on the CORESET#0 in the initial downlink BWP.

6. The method according to claim 5, characterized in that The initial downlink BWP further includes a first CORESET and / or a first search space, wherein the first CORESET is a CORESET configured for the terminal device in the initial downlink BWP, and the first search space is a search space configured for the terminal device in the initial downlink BWP; The method further comprises: In response to the message B including a contention conflict resolution message, and the message B not including a radio resource control release message, receiving resource scheduling on the first CORESET and / or the first search space, the resource scheduling including: at least one of uplink scheduling and downlink scheduling; or, In response to the message 4 including a contention conflict resolution message and the message 4 not including a radio resource control release message, receiving resource scheduling on the first CORESET and / or the first search space, the resource scheduling including: at least one of uplink scheduling and downlink scheduling.

7. The method according to claim 4 or 6, characterized in that: The uplink scheduling and the downlink scheduling belong to the same RACH-based small data transmission process.

8. A data transmission device, characterized in that: Applied in a terminal device, the device comprises: a bandwidth determination module and a transmission module; The bandwidth determination module is used to determine the target bandwidth for a small data transmission process based on a random access channel RACH; The transmission module is used to perform the RACH-based small data transmission process between the network device and the target bandwidth; The small data transmission process is a data transmission process when the terminal device is in an inactive state.

9. The device according to claim 8, characterized in that The bandwidth determination module is used to determine an initial uplink bandwidth BWP and an initial downlink BWP as the target bandwidth, wherein the initial downlink BWP includes a resource control set CORESET#0.

10. The device according to claim 9, characterized in that The RACH includes: a four-step RACH; The transmission module is used to receive at least one of a random access response, a retransmission indication of message 3 and message 4 sent by the network device on the CORESET#0 in the initial downlink BWP.

11. The device according to claim 10, characterized in that The initial downlink BWP further includes a first CORESET and / or a first search space, wherein the first CORESET is a CORESET configured for the terminal device in the initial downlink BWP, and the first search space is a search space configured for the terminal device in the initial downlink BWP; The transmission module is used to receive resource scheduling on the first CORESET and / or the first search space in response to the message 4 including a contention conflict resolution message and the message 4 not including a wireless resource control release message, wherein the resource scheduling includes at least one of uplink scheduling and downlink scheduling.

12. The device according to claim 9, characterized in that The RACH includes: a two-step RACH; The transmission module is used to receive at least one of a random access response, a retransmission indication of message 3, message 4 and message B sent by the network device on the CORESET#0 in the initial downlink BWP.

13. The device according to claim 12, characterized in that The initial downlink BWP further includes a first CORESET and / or a first search space, wherein the first CORESET is a CORESET configured for the terminal device in the initial downlink BWP, and the first search space is a search space configured for the terminal device in the initial downlink BWP; The transmission module is configured to receive resource scheduling on the first CORESET and / or the first search space in response to the message B including a contention conflict resolution message and the message B not including a radio resource control release message, wherein the resource scheduling includes: at least one of uplink scheduling and downlink scheduling; or, The transmission module is used to receive resource scheduling on the first CORESET and / or the first search space in response to the message 4 including a contention conflict resolution message and the message 4 not including a wireless resource control release message, wherein the resource scheduling includes at least one of uplink scheduling and downlink scheduling.

14. The device according to claim 11 or 13, characterized in that The uplink scheduling and the downlink scheduling belong to the same RACH-based small data transmission process.

15. A data transmission device, characterized in that: Applied in a network device, the device comprises: a transmission module; The transmission module is used to perform a small data transmission process based on a random access channel RACH with the terminal device on the target bandwidth; The small data transmission process is a data transmission process when the terminal device is in an inactive state.

16. The device according to claim 15, characterized in that The target bandwidth includes: an initial uplink bandwidth BWP and an initial downlink BWP, and the initial downlink BWP includes a resource control set CORESET#0.

17. The device according to claim 16, characterized in that The RACH includes: a four-step RACH; The transmission module is used to send at least one of a random access response, a retransmission indication of message 3 and message 4 to the terminal device on the CORESET#0 in the initial downlink BWP.

18. The device according to claim 17, characterized in that The initial downlink BWP further includes a first CORESET and / or a first search space, wherein the first CORESET is a CORESET configured for the terminal device in the initial downlink BWP, and the first search space is a search space configured for the terminal device in the initial downlink BWP; The transmission module is used to send resource scheduling on the first CORESET and / or the first search space in response to the message 4 including a contention conflict resolution message and the message 4 not including a wireless resource control release message, wherein the resource scheduling includes at least one of uplink scheduling and downlink scheduling.

19. The device according to claim 16, characterized in that The RACH includes: a two-step RACH; The transmission module is used to send at least one of a random access response, a retransmission indication of message 3, message 4 and message B to the terminal device on the CORESET#0 in the initial downlink BWP.

20. The device according to claim 19, characterized in that The initial downlink BWP further includes a first CORESET and / or a first search space, wherein the first CORESET is a CORESET configured for the terminal device in the initial downlink BWP, and the first search space is a search space configured for the terminal device in the initial downlink BWP; The transmission module is configured to send resource scheduling on the first CORESET and / or the first search space in response to the message B including a contention conflict resolution message and the message B not including a radio resource control release message, wherein the resource scheduling includes: at least one of uplink scheduling and downlink scheduling; or, The transmission module is used to send resource scheduling on the first CORESET and / or the first search space in response to the message 4 including a contention conflict resolution message and the message 4 not including a wireless resource control release message, wherein the resource scheduling includes: at least one of uplink scheduling and downlink scheduling.

21. The device according to claim 18 or 20, characterized in that The uplink scheduling and the downlink scheduling belong to the same RACH-based small data transmission process.

22. A terminal device, characterized in that: The terminal device comprises a processor and a transceiver connected to the processor, and is configured to execute the method according to any one of claims 1 to 6.

Citation Information

Patent Citations

  • Base station device, terminal device, communication method, and integrated circuit

    JP2020014082A

  • Random access method and device

    WO2020186468A1