CN114982334B

CN114982334B - Data transmission method and device, and terminal equipment

Info

Publication number: CN114982334B
Application number: CN202080093609.1A
Authority: CN
Inventors: 石聪; 李海涛; 林雪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-03-17
Filing date: 2020-03-17
Publication date: 2025-01-24
Anticipated expiration: 2040-03-17
Also published as: WO2021184179A1; CN114982334A

Abstract

The embodiment of the application provides a data transmission method, a data transmission device and terminal equipment, wherein the method comprises the steps that the terminal equipment selects a first preamble from a first preamble group, the first preamble group has an association relationship with a first Physical Uplink Shared Channel (PUSCH) configuration, the first PUSCH configuration is used for first-class data transmission, the terminal equipment determines a first PUSCH resource corresponding to the first preamble based on the first PUSCH configuration, and the first-class data is transmitted on the first PUSCH resource.

Description

Data transmission method and device and terminal equipment

Technical Field

The embodiment of the application relates to the technical field of mobile communication, in particular to a data transmission method and device and terminal equipment.

Background

In a New Radio (NR) system, small data transmission is not supported in a Radio resource control (Radio Resource Control, RRC) inactive state. A 2-step random access procedure is introduced in NR, and a MSGA Physical Uplink shared channel (Physical Uplink SHARED CHANNEL, PUSCH) in the 2-step random access procedure can be configured to different sizes, so that it is clear how to transmit small data through the PUSCH.

Disclosure of Invention

The embodiment of the application provides a data transmission method and device and terminal equipment.

The data transmission method provided by the embodiment of the application comprises the following steps:

the method comprises the steps that terminal equipment selects a first preamble from a first preamble group, wherein the first preamble group has an association relation with a first PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration used for first-class data transmission;

and the terminal equipment determines a first PUSCH resource corresponding to the first preamble based on the first PUSCH configuration, and transmits the first type data on the first PUSCH resource.

The method comprises the steps that a terminal device selects a first RO resource from a first RO resource group, wherein the first RO resource group is used for first-class data transmission, the first RO resource group has an association relation with a first PUSCH configuration, and the first PUSCH configuration is used for the first-class data transmission;

and the terminal equipment determines a first PUSCH resource corresponding to the first RO resource based on the first PUSCH configuration, and transmits the first type data on the first PUSCH resource.

The data transmission device provided by the embodiment of the application comprises:

a selection unit, configured to select a first preamble from a first preamble group, where the first preamble group has an association relationship with a first PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration for first type data transmission;

A determining unit, configured to determine, based on the first PUSCH configuration, a first PUSCH resource corresponding to the first preamble;

and the transmission unit is used for transmitting the first type of data on the first PUSCH resource.

a selecting unit, configured to select a first RO resource from a first RO resource group, where the first RO resource group is an RO resource group for first-class data transmission, the first RO resource group has an association relationship with a first PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration for the first-class data transmission;

A determining unit, configured to determine, based on the first PUSCH configuration, a first PUSCH resource corresponding to the first RO resource;

The terminal equipment provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the data transmission method.

The chip provided by the embodiment of the application is used for realizing the data transmission method.

The chip comprises a processor for calling and running a computer program from a memory, so that a device provided with the chip executes the data transmission method.

The computer readable storage medium provided by the embodiment of the application is used for storing a computer program, and the computer program enables a computer to execute the data transmission method.

The computer program product provided by the embodiment of the application comprises computer program instructions, wherein the computer program instructions enable a computer to execute the data transmission method.

The computer program provided by the embodiment of the application, when running on a computer, causes the computer to execute the data transmission method.

By the technical scheme, specific PUSCH configuration and specific preamble groups or RO resource groups are configured for the first-class data transmission. By associating the specific PUSCH configuration with the specific preamble group or the RO resource group, the terminal device may transmit the first type of data using the PUSCH resource associated with the specific random access resource (such as the specific preamble or the specific RO resource) in the random access procedure. Since the specific random access resource is different from the random access resource adopted by the traditional terminal equipment, the influence on the traditional terminal equipment is avoided.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:

Fig. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

Fig. 2 is a flowchart of a data transmission method according to an embodiment of the present application;

Fig. 3 is a schematic diagram of association between a preamble group and PUSCH configuration provided in an embodiment of the present application;

fig. 4 is a schematic diagram of a preamble allocation according to an embodiment of the present application;

Fig. 5 is a second diagram of preamble allocation according to an embodiment of the present application;

Fig. 6 is a schematic diagram of a preamble allocation according to a third embodiment of the present application;

fig. 7 is a second schematic association diagram of a preamble group and PUSCH configuration provided in an embodiment of the present application;

fig. 8 is a second flowchart of a data transmission method according to an embodiment of the present application;

Fig. 9 is a schematic diagram of a data transmission device according to an embodiment of the present application;

fig. 10 is a schematic diagram II of a structure of a data transmission device according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 12 is a schematic block diagram of a chip of an embodiment of the application;

fig. 13 is a schematic block diagram of a communication system provided in an embodiment of the present application.

Detailed Description

The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The technical scheme of the embodiment of the application can be applied to various communication systems, such as a long term evolution (Long Term Evolution, LTE) system, an LTE frequency division duplex (Frequency Division Duplex, FDD) system, an LTE time division duplex (Time Division Duplex, TDD), a system, a 5G communication system or a future communication system and the like.

An exemplary communication system 100 to which embodiments of the present application may be applied is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device in communication with a terminal 120. Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area. Alternatively, the network device 110 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future communication system, etc.

The communication system 100 further includes at least one terminal 120 located within the coverage area of the network device 110. The terminal 120 is connected to the network device 110 through a wire line or a wireless interface. The terminal 110 connected to the network device 110 through a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". A terminal may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent or User Equipment, cellular telephone, cordless telephone, session initiation protocol (Session Initiation Protocol, SIP) phone, wireless local loop (Wireless Local Loop, WLL) station, personal digital assistant (Personal DIGITAL ASSISTANT, PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal in a 5G network or terminal in a future evolved PLMN, etc.

Alternatively, direct to Device (D2D) communication may be performed between the terminals 120.

Alternatively, the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.

Fig. 1 illustrates one network device and two terminals, alternatively, the communication system 100 may include multiple network devices and each network device may include other numbers of terminals within its coverage area, which is not limited by the embodiment of the present application.

Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited by the embodiment of the present application.

It should be understood that a device having a communication function in a network/system according to an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication system 100 may include the network device 110 and the terminal 120 with communication functions, where the network device 110 and the terminal 120 may be specific devices described above, which are not described herein again, and the communication system 100 may also include other devices, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiment of the present application.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean that a exists alone, while a and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following describes the technical solutions related to the embodiments of the present application.

● Small data transmission

The 3gpp r17 proposes that the small data transmission of the terminal device in the RRC inactive state needs to be supported, and the main purpose is to save power and signaling overhead, and specific project targets include:

small data transmission optimization based on random access procedure, wherein the random access procedure comprises a 4-step random access procedure and a 2-step random access procedure.

Small data transmission optimization based on a first type of pre-configured grant (tyepl configured grant), that is to say that the first type of pre-configured grant transmission needs to be supported in the RRC inactive state.

● RRC state

In the 5G network environment, for the purposes of reducing air interface signaling and quickly recovering wireless connection, and quickly recovering data traffic, a new RRC state, namely, an RRC INACTIVE (rrc_inactive) state, is defined. This state is different from the RRC IDLE (rrc_idle) state and the RRC ACTIVE (rrc_active) state. Wherein,

The rrc_idle state (abbreviated as RRC IDLE state) mobility is based on cell selection reselection, paging is initiated by the Core Network (CN), and paging areas are configured by the CN. The base station side has no context of the terminal equipment and no RRC connection.

The rrc_inactive state (abbreviated as RRC INACTIVE state) mobility is based on cell selection reselection, there is a connection between CN-NRs, terminal device context is present on a certain base station, paging is triggered by RAN, paging area based on RAN is managed by RAN, network side knows that the location of terminal device is based on paging area level of RAN.

The rrc_connected state (abbreviated as RRC CONNECTED state) is that there is an RRC connection and there is a terminal device context at the base station side and the terminal device side. The network side knows that the location of the terminal device is cell specific. Mobility is network-side controlled mobility. Unicast data may be transmitted between the terminal color board and the base station.

The three RRC states can be mutually switched, wherein some RRC parameters of the terminal equipment side in the RRC inactive state are configured through an RRC release message, and the main RRC parameters are as follows:

and the non-activated RNTI (I-RNTI) is used for identifying the non-activated context of the terminal equipment at the base station side and is unique in the base station.

The RAN notification area (RAN Notification Area, RNA) is an area for controlling the terminal device to perform cell selection reselection in the RRC inactive state, and is also a paging range area for the RAN initial paging.

The RAN paging cycle (RAN PAGING CYCLE) is used to calculate the paging occasion of the RAN initial page.

A next hop chain count (Next hop Chaining Counter, NCC) for determining the key used in the RRC connection recovery procedure.

When the terminal equipment moves in the RNA area, the network side is not informed, and the mobility behavior in the RRC idle state, namely the cell selection reselection principle is followed. When the terminal device moves out of the RAN configured paging area, the terminal device triggers the RRC connection procedure to resume (i.e., RRC resume procedure) and reacquires the RAN configured paging area. When the network side needs to transmit data to the terminal equipment, that is, when downlink data arrives, the base station storing the context of the terminal equipment triggers all cells in the RAN paging area to send paging messages to the terminal equipment, so that the terminal equipment in the RRC inactive state can recover RRC connection and receive the data. In addition, the terminal equipment in the RRC inactive state configures a RAN paging area in which the terminal equipment needs to perform periodic location update according to a network configuration period in order to ensure the reachability of the terminal equipment. The scenario where the terminal device is triggered to perform an RNA update is that RNAU timer expires or the terminal device moves to an area outside the RNA. Currently, the RRC inactive state defined by NR does not support the terminal device to transmit user plane data.

● Random access procedure

The random access procedure supports two random access types, a 2-step random access type (2-STEP RA TYPE) and a 4-step random access type (4-STEP RA TYPE). Both random access types support a Contention-based random access (content-Based Random Access, CBRA) procedure and a non-Contention-based random access (content-Free Random Access, CFRA) procedure.

The terminal device selects a random access type based on configuration of the network side, specifically 1) if the network side is not configured with CFRA resources, the terminal device determines whether to use a 2-step random access type or a 4-step random access type to execute a random access procedure based on a reference signal received Power (REFERENCE SIGNAL RECEIVED Power, RSRP) threshold. 2) If the network side configures CFRA resources of the 4-step random access type, the terminal equipment adopts the 4-step random access type to execute the random access flow. 3) If the network side configures CFRA resources of the 2-step random access type, the terminal equipment adopts the 2-step random access type to execute the random access flow.

The procedure of the 4-step random access type based on competition comprises the following steps:

MSG1, the terminal equipment sends the lead code to the base station.

MSG2, the base station sends random access response message to the terminal equipment.

MSG3, the terminal equipment sends the PUSCH to the base station.

MSG4, the base station sends the competition resolving information to the terminal equipment.

The contention-based 2-step random access type may increase latency while also reducing signaling overhead, comprising the steps of:

MSGA the terminal equipment sends the preamble and the PUSCH to the base station.

MSGB, the base station sends a contention resolution message to the terminal device.

The MAGA in the 2-step Random access type includes a preamble transmitted on a Physical Random access channel (Physical Random ACCESS CHANNEL, PRACH) and a payload (payload) transmitted on a PUSCH.

Since the NR does not support small data transmission in the RRC inactive state, a 2-step random access procedure is introduced in the NR, and PUSCH of MSGA in the 2-step random access procedure may be configured to be different sizes.

In the 2-step random access procedure, PUSCH configuration (PUSCH config) has an association relationship with the contention preamble group (CB preamble group), and the network can configure 2 PUSCH configs at most, wherein 1 PUSCH config has only 1 TB size (TB size). In the RRC inactive state or RRC idle state, PUSCH config supports a TB size (TB size) of 56 bits or 72 bits in consideration of coverage.

If the network side configures the contention preamble group A (CB preamble group A) and the contention preamble group B (CB preamble group B), the network side also configures a load threshold (payload threshold) for the terminal device to select the preamble group.

In order to support small data transmission in the RRC inactive state, the network side may configure PUSCH config for small data transmission, which has a relatively large TB size. And, the PUSCH config has an association relationship with one preamble group. However, this has an effect on the selection of the preamble group for legacy terminals, for example, for terminals that only need 72 bits to transmit data, the terminal will select the contention preamble group B with an association with PUSCH config for small data transmission according to the existing scheme. This will lead to a large amount of padding carried by the terminal device when transmitting data, reducing the efficiency of resource usage. Furthermore, since the network side is configured with PUSCH config for small data transmission, it is also clear how to prevent the legacy terminal device from selecting the PUSCH config. For this reason, the following technical solutions of the embodiments of the present application are provided.

Fig. 2 is a flow chart of a data transmission method according to an embodiment of the present application, as shown in fig. 2, the data transmission method includes the following steps:

Step 201, a terminal device selects a first preamble from a first preamble group, wherein the first preamble group has an association relationship with a first PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration for first-class data transmission.

In the embodiment of the application, the terminal equipment receives first configuration information sent by the network equipment, wherein the first configuration information is used for determining at least one of the following:

the first PUSCH configuration;

Index information of the first preamble group;

And the association relation between the first PUSCH configuration and the first preamble group.

Here, the network device may alternatively be a base station, such as a gNB.

In an embodiment of the present application, the first type of data may be small data (SMALL DATA). The first type of data may be, but not limited to, other types of data, such as data having a size within a specified range. Alternatively, the terminal device transmitting the first type of data may be referred to as a first type of terminal (e.g., a small data terminal), and the terminal device transmitting the second type of data may be referred to as a second type of terminal (e.g., a normal terminal). Here, the size range of the first type data and the size range of the second type data are different.

In the embodiment of the application, the network equipment configures the PUSCH configuration (PUSCH config for Type1 data) for the first type of data transmission. For example, the network device configures PUSCH configuration for small data transmission (PUSCH config for SMALL DATA). Here, the PUSCH configuration for the first type of data transmission is referred to as a first PUSCH configuration.

It should be noted that, the first PUSCH is configured to determine a plurality of PUSCH resources, and one PUSCH resource is one PUSCH resource unit (PUSCH Resource Unit, PRU). Each PUSCH resource of the plurality of PUSCH resources is a PUSCH resource for a first type of data transmission.

In the embodiment of the present application, the first PUSCH configuration has an association relationship with the first preamble group. Accordingly, the network device configures index information of the first preamble group and/or association relationship between the first PUSCH configuration and the first preamble group in addition to the first PUSCH configuration.

In the embodiment of the present application, the first preamble set may be a preamble set used for the first type of data transmission, or the first preamble set is a shared preamble set used for the first type of data transmission and the second type of data transmission. The following describes in detail the technical solution of the embodiment of the present application in connection with different implementation manners of the first preamble group.

● Mode one

The first preamble set is a preamble set for the first type of data transmission.

Here, all preambles in the first preamble group are configured for the first type of data transmission. When the terminal equipment in the RRC inactive state initiates the first type data transmission, the terminal equipment determines the first preamble group corresponding to the first type data, and selects a first preamble from the first preamble group.

In a specific implementation, the terminal device may select the first preamble group according to a size of the first type data. For example, assuming that there are 3 preamble groups, which are a first preamble group, a second preamble group, and a third preamble group, respectively, where the first preamble group corresponds to a data size Range of Range1, the second preamble group corresponds to a data size Range of Range2, and the third preamble group corresponds to a data size Range of Range3, the terminal device may determine to select the first preamble group according to the size of the first type data falling into Range 1. Since all preambles of the first preamble set are configured for said first type of data transmission, the first preamble selected by the terminal device from said first preamble set is the preamble for said first type of data transmission.

In the embodiment of the application, in determining which preambles belong to the preambles in the first preamble set, the contention preamble (Contention based preamble), the non-contention preamble (contention free preamble) and the preambles for the request system message (System Information, SI) need to be excluded, since these preambles are already allocated to other preamble sets.

As shown in fig. 3, the network side configures 3 preamble groups, which are a first preamble group, a contention preamble group a, and a contention preamble group B, where the first preamble group is associated with PUSCH config3 (i.e., the first PUSCH configuration), the contention preamble group a is associated with PUSCH config1, and the contention preamble group B is associated with PUSCH config2. Here, the preambles in the contention preamble group a and the contention preamble group B both belong to the contention preamble, and the preamble in the first preamble group is a preamble used for the first type of data transmission, and it should be noted that the preamble in the first preamble group actually also belongs to the contention type preamble, except that the data types targeted by the first preamble group and the contention preamble group a (or the contention preamble group B) are different. In an alternative, the first preamble set may also be referred to as the contention preamble set C. It should be noted that there is no intersection between different preamble groups.

In the embodiment of the application, the first preamble group comprises at least one first type of preamble associated with each SSB in a plurality of SSBs, or the first preamble group comprises at least one first type of preamble associated with a random access opportunity (RACH Occasion, RO), wherein the first type of preamble is the preamble used for the first type of data transmission. How to determine which preambles belong to the preambles of the first preamble group is described below in connection with different situations.

In case one, M SSBs are associated with one RO, M is an integer greater than 1 and less than or equal to N.

Here, the terminal device receives a first parameter and a second parameter sent by the network device, where the first parameter is used to determine N SSBs actually transmitted by the network device, N is a positive integer, and the second parameter is used to determine an association relationship between the N SSBs and the RO. In specific implementation, the network device sends the first parameter and the second parameter to the terminal device through a system broadcast message.

For the case that the second parameter is used to indicate that M SSBs are associated with one RO, the first preamble set includes at least one first type preamble associated with each SSB of the M SSBs, where the first type preamble is a preamble used for the first type data transmission.

Further optionally, each SSB is associated with at least one of the following in addition to the at least one first type preamble:

At least one contention preamble;

at least one non-contention preamble;

at least one preamble for requesting SI.

That is, in case that a plurality of SSBs are associated with one RO, the preamble used for data transmission of the first type may be a preamble excluding a contention preamble, a non-contention preamble, a preamble used for requesting SI, among a preamble set associated with each of the plurality of SSBs. The preamble type included in the preamble set associated with each SSB includes at least one of a first type preamble, a contention preamble, a non-contention preamble, and a preamble for requesting SI. Different types of preambles are used for different types of random access. For example, a first type preamble is used for random access for first type data transmission, a contention preamble is used for contention random access, a non-contention preamble is used for non-contention random access, and a preamble for requesting SI is used for requesting random access of SI.

In this embodiment, for the case where a plurality of SSBs associate one RO, one set of RO-associated preambles is allocated (associated) to the plurality of SSBs.

Referring to fig. 4, if 2 SSBs are associated with one RO (i.e., m=2), for ssb#1, the associated preamble set includes a contention preamble set 1, a non-contention preamble set 1, and a first type preamble set 1, wherein the contention preamble set 1 includes part of preambles in the contention preamble set a+b (i.e., the contention preamble set a and the contention preamble set B). Also for SSB#2, the associated preamble set includes a contention preamble set 2, a non-contention preamble set 2, and a first type preamble set 2, wherein the contention preamble set 2 includes part of the preambles in the contention preamble set A+B (i.e., the contention preamble set A and the contention preamble set B).

It should be noted that, the indexes of the preambles in one RO-associated preamble set are continuously distributed, and in the case that M SSBs are determined to be associated with one RO, the index range of each SSB-associated preamble set is determined, so that in order to distinguish which preambles in each SSB-associated preamble set belong to the first type of preamble, the network side terminal device is required to indicate index information of the first type of preamble in each SSB-associated first type of preamble set and/or the number of preambles contained in the first type of preamble set. In particular, the method comprises the steps of,

The terminal device receives first indication information sent by the network device, wherein the first indication information is used for indicating index information of a first type of lead codes in the at least one first type of lead codes and/or indicating the number of the at least one first type of lead codes.

Further, optionally, in the case that the first indication information does not indicate the index information of the first type of preambles in the at least one first type of preambles, the index information of the first type of preambles is predetermined index information, for example, the index information of the first type of preambles is the index information of the first preamble after the non-contention preamble set, or the index information of the first type of preambles is the index information of the first preamble after the contention preamble set.

Referring to fig. 5, fig. 5 is different from fig. 4 in that the first type preamble set 1 associated with ssb#1 and the first type preamble set 2 associated with ssb#2 in fig. 5 are centrally distributed. As with figure 4, for ssb#1, the associated preamble set includes a contention preamble set 1, a non-contention preamble set 1, and a first type preamble set 1, wherein the contention preamble set 1 includes part of the preambles in the contention preamble set a+b (i.e., the contention preamble set a and the contention preamble set B). Also for SSB#2, the associated preamble set includes a contention preamble set 2, a non-contention preamble set 2, and a first type preamble set 2, wherein the contention preamble set 2 includes part of the preambles in the contention preamble set A+B (i.e., the contention preamble set A and the contention preamble set B). Here, since the first type preamble set 1 associated with ssb#1 and the first type preamble set 2 associated with ssb#2 are intensively distributed, the network needs index information indicating the first type preamble in each first type preamble set associated with SSB.

In the second case, when one SSB associates M ROs, M is an integer equal to or greater than 1.

The first preamble set is a shared preamble set for the first type of data transmission and the second type of data transmission.

In the case that the second parameter is used to indicate that one SSB associates M ROs, for one RO of the M ROs, the first preamble group includes at least one first type preamble associated with the RO, where the first type preamble is a preamble used for the first type data transmission.

Further optionally, the RO is associated with at least one of the following in addition to the at least one first type preamble:

At least one contention preamble;

at least one non-contention preamble;

at least one preamble for requesting SI.

That is, in case that one SSB associates a plurality of ROs, the preamble used for data transmission of the first type may be a preamble excluding a contention preamble, a non-contention preamble, and a preamble used for SI request from one set of ROs-associated preambles. The preamble type included in the one RO-associated preamble set includes at least one of a first type preamble, a contention preamble, a non-contention preamble, and a preamble for requesting SI. Different types of preambles are used for different types of random access. For example, a first type preamble is used for random access for first type data transmission, a contention preamble is used for contention random access, a non-contention preamble is used for non-contention random access, and a preamble for requesting SI is used for requesting random access of SI.

It is understood that one RO-associated preamble set includes a contention preamble set, a non-contention preamble set, a first type preamble set, and a preamble set for SI request. Wherein the contention preamble set may be the contention preamble group a+b (i.e., the contention preamble group a and the contention preamble group B).

In this embodiment, for the case where one SSB associates a plurality of ROs, a plurality of RO-associated preamble sets are allocated (associated) to one SSB, where each RO-associated preamble set is repeated.

Referring to fig. 6, fig. 6 illustrates one RO-associated preamble set including a contention preamble set, a non-contention preamble set, a first type preamble set, and a preamble set for SI requests, wherein the contention preamble set includes a contention preamble group a+b (i.e., a contention preamble group a and a contention preamble group B).

It should be noted that, indexes of the preambles in one RO-associated preamble set are continuously distributed, and in order to distinguish which preambles in the RO-associated preamble set belong to the first type of preambles, the network side terminal device is required to indicate index information of the first type of preamble in the RO-associated first type of preamble set and/or the number of preambles contained in the first type of preamble set. In particular, the method comprises the steps of,

The terminal device receives second indication information sent by the network device, wherein the second indication information is used for indicating index information of a first type of lead codes in the at least one first type of lead codes and/or indicating the number of the at least one first type of lead codes.

And when the second indication information does not indicate the index information of the first type of the at least one first type of the preambles, the index information of the first type of the preambles is predetermined index information, for example, the index information of the first type of the preambles is the index information of the first preamble after the non-contention preamble set, or the index information of the first type of the preambles is the index information of the first preamble after the contention preamble set.

● Mode two

The first preamble set is a shared preamble set for the first type of data transmission and the second type of data transmission, wherein a size range of the first type of data and a size range of the second type of data are different.

In an alternative, the shared preamble set is a contention preamble set a. In another alternative, the shared preamble set is a contention preamble set B. Here, the contention preamble group a and the contention preamble group B may be existing contention preamble groups.

In this embodiment, the terminal device is configured with at most two preamble groups, i.e. a contention preamble group a and a contention preamble group B. Which preambles of the contention preamble group a and/or the contention preamble group B may be used for transmitting the first type data is indicated by the network side.

Specifically, the terminal device receives third indication information sent by the network device, wherein the third indication information is used for indicating at least one first type of preamble in the shared preamble group or indicating a preamble range in the shared preamble group, the preamble range is used for determining at least one first type of preamble, the first type of preamble is used for transmitting the first type of data, and the terminal device selects the first preamble from the at least one first type of preamble based on the third indication information.

Referring to fig. 7, the network side configures 2 preamble groups, which are respectively a contention preamble group a and a contention preamble group B, wherein the contention preamble group a is associated with PUSCH config1, the contention preamble group B is associated with PUSCH config2, and in addition, the contention preamble group a and/or the contention preamble group B may be associated with PUSCH config3 (i.e. the first PUSCH configuration).

In this embodiment, the shared preamble set includes at least one contention preamble in addition to the at least one first type of preamble, and the terminal device maps the at least one contention preamble in the shared preamble set to at least one PUSCH resource in a second PUSCH configuration, where the second PUSCH configuration is a PUSCH configuration for the second type of data transmission.

Referring to fig. 7, taking the case of associating PUSCH config1 and PUSCH config3 with the contention preamble group a as an example, the preamble in the contention preamble group a is divided into two parts, one part being associated with PUSCH config1 (i.e., at least one contention preamble is associated with PUSCH config 1) and the other part being associated with PUSCH config3 (i.e., at least one first type preamble is associated with PUSCH config 3). When the terminal device performs mapping from the preamble in the contention preamble group a to the PRU of PUSCH config1, if some of the preambles are the first type preambles allocated to the first type data transmission by the network, the terminal device needs to exclude the first type preambles. Likewise, the first type of preamble already allocated to the first type of data transmission needs to be excluded from mapping to PUSCH config2 for the preambles in the contention preamble group B.

Step 202, the terminal device determines a first PUSCH resource corresponding to the first preamble based on the first PUSCH configuration, and transmits the first type data on the first PUSCH resource.

In the embodiment of the application, the terminal equipment maps at least one first type of lead code in the first lead code group to at least one PUSCH resource in the first PUSCH configuration, wherein the first lead code in the at least one first type of lead code is mapped to the first PUSCH resource in the at least one PUSCH resource. In this way, the terminal device may determine that the PUSCH resource corresponding to the first preamble is the first PUSCH resource, and based on this, the terminal device transmits the first type data on the first PUSCH resource.

It should be noted that, in the technical solution of the embodiment of the present application, the network side is configured with one first PUSCH configuration and one first preamble set as an example, and not limited thereto, the network side may also be configured with a plurality of first PUSCH configurations and a plurality of first preamble sets, where different first PUSCH configurations in the plurality of first PUSCH configurations have different TB sizes. Correspondingly, if the network side configures a plurality of first PUSCH configurations, the association relationship between each first PUSCH configuration and the preamble may be determined by referring to the technical solution of the embodiment of the present application. For example, each first PUSCH configuration is associated with one first preamble group or with part of the preambles in a shared preamble group.

Fig. 8 is a second flow chart of a data transmission method according to an embodiment of the present application, as shown in fig. 8, where the data transmission method includes the following steps:

Step 801, a terminal device selects a first RO resource from a first RO resource group, where the first RO resource group is an RO resource group for first-class data transmission, the first RO resource group has an association relationship with a first PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration for the first-class data transmission.

In the embodiment of the present application, the terminal device receives second configuration information sent by the network device, where the second configuration information is used to determine at least one of the following:

the first PUSCH configuration;

Index information of the first RO resource group;

And the association relationship between the first PUSCH configuration and the first RO resource group.

Here, the network device may alternatively be a base station, such as a gNB.

In the embodiment of the present application, the first PUSCH configuration and the first RO resource group have an association relationship. Accordingly, the network device configures index information of the first RO resource group and/or association relationship between the first PUSCH configuration and the first RO resource group in addition to the first PUSCH configuration.

In the embodiment of the present application, the first PUSCH configuration has an association relationship with the first preamble group on the first RO resource group.

Further, optionally, the terminal device may support different sizes of first PUSCH configurations, e.g. the network may configure two TB sizes of first PUSCH configurations, e.g. PUSCH config1 and PUSCH config2, which respectively correspond to different preamble groups on the first RO resource group.

Step 802, the terminal device determines a first PUSCH resource corresponding to the first RO resource based on the first PUSCH configuration, and transmits the first type data on the first PUSCH resource.

In the embodiment of the application, when the terminal equipment initiates the first type data transmission, the first RO resource is selected from the first RO resources, the first PUSCH resource corresponding to the first RO resource is determined, and the first type data is transmitted on the first PUSCH resource.

It should be noted that, for a legacy terminal device (i.e., a terminal device transmitting the second type of data), when mapping the preamble to the PRU, the preamble on the RO resource already allocated to the first type of data transmission needs to be excluded.

It should be noted that, in the technical solution of the embodiment of the present application, the network side is configured with one first PUSCH configuration as an example, and not limited thereto, the network side may also be configured with a plurality of first PUSCH configurations, where different first PUSCH configurations in the plurality of first PUSCH configurations have different TB sizes. Correspondingly, if the network side configures a plurality of first PUSCH configurations, the association relationship between each first PUSCH configuration and the RO resource may be determined by referring to the technical solution of the embodiment of the present application. For example, each first PUSCH configuration is associated with a specific RO resource group.

Fig. 9 is a schematic structural diagram of a data transmission device according to an embodiment of the present application, which is applied to a terminal device, as shown in fig. 9, where the data transmission device includes:

a selecting unit 901, configured to select a first preamble from a first preamble set, where the first preamble set has an association relationship with a first PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration for first type data transmission;

A determining unit 902, configured to determine, based on the first PUSCH configuration, a first PUSCH resource corresponding to the first preamble;

a transmission unit 903, configured to transmit the first type of data on the first PUSCH resource.

In an alternative, the apparatus further comprises:

A receiving unit (not shown in the figure) configured to receive first configuration information sent by the network device, where the first configuration information is used to determine at least one of:

the first PUSCH configuration;

Index information of the first preamble group;

In an alternative, the first preamble set is a preamble set for the first type of data transmission.

In an alternative manner, the first preamble set includes at least one first type preamble associated with each SSB of the SSBs, or the first preamble set includes at least one first type preamble associated with an RO, wherein the first type preamble is a preamble used for the first type data transmission.

In an alternative, the apparatus further comprises:

a receiving unit, configured to receive a first parameter and a second parameter sent by a network device, where the first parameter is used to determine N SSBs actually transmitted by the network device, N is a positive integer, and the second parameter is used to determine an association relationship between the N SSBs and an RO,

The second parameter is used for indicating that M SSBs are associated with one RO, M is an integer greater than 1 and less than or equal to N, and the first preamble group comprises at least one first type preamble associated with each SSB in the M SSBs.

In an alternative manner, each SSB is associated with at least one of the following in addition to the at least one first type preamble:

At least one contention preamble;

at least one non-contention preamble;

at least one preamble for requesting SI.

In an optional manner, the receiving unit is further configured to receive first indication information sent by the network device, where the first indication information is used to indicate index information of a first type of preamble in the at least one first type of preamble and/or indicate a number of the at least one first type of preamble.

In an optional manner, in a case that the first indication information does not indicate index information of a first type preamble of the at least one first type preamble, the index information of the first type preamble is predetermined index information.

In an alternative, the apparatus further comprises:

And the second parameter is used for indicating that when one SSB associates M RO, M is an integer greater than or equal to 1, and for one RO in the M RO, the first preamble group contains at least one first type preamble associated with the RO.

In an alternative way, the RO is associated with at least one of the following in addition to the at least one first type preamble:

At least one contention preamble;

at least one non-contention preamble;

at least one preamble for requesting SI.

In an optional manner, the receiving unit is further configured to receive second indication information sent by the network device, where the second indication information is used to indicate index information of a first type of preamble in the at least one first type of preamble and/or indicate a number of the at least one first type of preamble.

In an optional manner, in a case that the second indication information does not indicate index information of a first type preamble of the at least one first type preamble, the index information of the first type preamble is predetermined index information.

In an alternative manner, the selecting unit 901 is configured to determine the first preamble set corresponding to the first type of data, and select a first preamble from the first preamble set.

In an alternative way, the first preamble set is a shared preamble set for the first type of data transmission and the second type of data transmission, wherein a size range of the first type of data and a size range of the second type of data are different.

In an alternative, the shared preamble set is the contention preamble set A, or

The shared preamble set is a contention preamble set B.

In an alternative, the apparatus further comprises:

A receiving unit, configured to receive third indication information sent by a network device, where the third indication information is used to indicate at least one first type of preamble in the shared preamble set or indicate a preamble range in the shared preamble set, where the preamble range is used to determine at least one first type of preamble;

The selecting unit is configured to select the first preamble from the at least one first type of preambles based on the third indication information.

In an alternative manner, the shared preamble set includes at least one contention preamble in addition to the at least one first type preamble;

The device further comprises a mapping unit, wherein the mapping unit is used for mapping the at least one contention preamble in the shared preamble group to at least one PUSCH resource in a second PUSCH configuration, and the second PUSCH configuration is a PUSCH configuration used for the second type of data transmission.

In an alternative manner, the device further comprises a mapping unit (not shown in the figure) configured to map at least one first type of preamble in the first preamble group to at least one PUSCH resource in the first PUSCH configuration, wherein the first preamble in the at least one first type of preamble is mapped to a first PUSCH resource in the at least one PUSCH resource.

In an alternative manner, the first type of data is small data.

It should be understood by those skilled in the art that the above description of the data transmission apparatus according to the embodiment of the present application may be understood with reference to the description of the data transmission method according to the embodiment of the present application.

Fig. 10 is a schematic diagram ii of the structural composition of a data transmission device according to an embodiment of the present application, which is applied to a terminal device, as shown in fig. 10, where the data transmission device includes:

a selecting unit 1001, configured to select a first RO resource from a first RO resource group, where the first RO resource group is an RO resource group for first-class data transmission, the first RO resource group has an association relationship with a first PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration for the first-class data transmission;

A determining unit 1002, configured to determine, based on the first PUSCH configuration, a first PUSCH resource corresponding to the first RO resource;

A transmission unit 1003, configured to transmit the first type of data on the first PUSCH resource.

In an alternative, the apparatus further comprises:

A receiving unit (not shown in the figure) is configured to receive second configuration information sent by the network device, where the second configuration information is used to determine at least one of the following:

the first PUSCH configuration;

Index information of the first RO resource group;

In an alternative manner, the first PUSCH configuration has an association relationship with the first preamble group on the first RO resource group.

In an alternative manner, the first type of data is small data.

Fig. 11 is a schematic block diagram of a communication device 1100 according to an embodiment of the present application. The communication device may be a terminal device or a network device, and the communication device 1100 shown in fig. 11 includes a processor 1110, where the processor 1110 may call and execute a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 11, the communication device 1100 may also include a memory 1120. Wherein the processor 1110 may call and run a computer program from the memory 1120 to implement the methods in embodiments of the present application.

Wherein the memory 1120 may be a separate device from the processor 1110 or may be integrated into the processor 1110.

Optionally, as shown in fig. 11, the communication device 1100 may further include a transceiver 1130, and the processor 1110 may control the transceiver 1130 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

The transceiver 1130 may include, among other things, a transmitter and a receiver. Transceiver 1130 may further include antennas, the number of which may be one or more.

Optionally, the communication device 1100 may be a network device in the embodiment of the present application, and the communication device 1100 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 1100 may be specifically a mobile terminal/terminal device according to an embodiment of the present application, and the communication device 1100 may implement a corresponding flow implemented by the mobile terminal/terminal device in each method according to an embodiment of the present application, which is not described herein for brevity.

Fig. 12 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 1200 shown in fig. 12 includes a processor 1210, and the processor 1210 may call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

Optionally, as shown in fig. 12, the chip 1200 may further include a memory 1220. Wherein the processor 1210 may call and run computer programs from the memory 1220 to implement the methods of embodiments of the present application.

The memory 1220 may be a separate device from the processor 1210, or may be integrated into the processor 1210.

Optionally, the chip 1200 may also include an input interface 1230. Wherein the processor 1210 may control the input interface 1230 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips.

Optionally, the chip 1200 may further include an output interface 1240. Wherein processor 1210 may control the output interface 1240 to communicate with other devices or chips, and in particular may output information or data to other devices or chips.

Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

Fig. 13 is a schematic block diagram of a communication system 1300 provided by an embodiment of the present application. As shown in fig. 13, the communication system 1300 includes a terminal device 1310 and a network device 1320.

The terminal device 1310 may be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1320 may be used to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The Processor may be a general purpose Processor, a digital signal Processor (DIGITAL SIGNAL Processor, DSP), an Application SPECIFIC INTEGRATED Circuit (ASIC), an off-the-shelf programmable gate array (Field Programmable GATE ARRAY, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate Synchronous dynamic random access memory (Double DATA RATE SDRAM, DDR SDRAM), enhanced Synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and Direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be appreciated that the above memory is exemplary and not limiting, and for example, the memory in the embodiments of the present application may be static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (double DATA RATE SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous connection dynamic random access memory (SYNCH LINK DRAM, SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which is not described herein for brevity.

The embodiment of the application also provides a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to a network device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the network device in each method in the embodiment of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. The storage medium includes a U disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of data transmission, the method comprising:

the method comprises the steps that terminal equipment selects a first preamble from a first preamble group, wherein the first preamble group has an association relationship with a first Physical Uplink Shared Channel (PUSCH) configuration, and the first PUSCH configuration is a PUSCH configuration used for first-class data transmission;

The terminal equipment determines a first PUSCH resource corresponding to the first preamble based on the first PUSCH configuration, and transmits the first type data on the first PUSCH resource;

Wherein the first preamble set is a preamble set for the first type of data transmission;

wherein the first preamble group comprises at least one first type preamble associated with each SSB of the plurality of synchronization signal blocks SSB, or

The first preamble group comprises at least one first type of preamble associated with a random access opportunity RO;

wherein the first type of preamble is a preamble for the first type of data transmission.

2. The method of claim 1, wherein the method further comprises:

the terminal equipment receives first configuration information sent by the network equipment, wherein the first configuration information is used for determining at least one of the following:

the first PUSCH configuration;

Index information of the first preamble group;

3. The method of claim 1, wherein the method further comprises:

The terminal equipment receives a first parameter and a second parameter sent by the network equipment, wherein the first parameter is used for determining N SSBs actually transmitted by the network equipment, N is a positive integer, the second parameter is used for determining the association relation between the N SSBs and the RO,

4. The method of claim 3, wherein each SSB is associated with at least one of the following in addition to the at least one first type preamble:

At least one contention preamble;

at least one non-contention preamble;

at least one preamble for requesting the system message SI.

5. The method according to claim 3 or 4, wherein the method further comprises:

6. The method of claim 5, wherein the first indication information does not indicate index information of a first type preamble of the at least one first type preamble, the index information of the first type preamble being predetermined index information.

7. The method of claim 1, wherein the method further comprises:

8. The method of claim 7, wherein the RO is associated with at least one of the following in addition to the at least one first type preamble:

At least one contention preamble;

at least one non-contention preamble;

at least one preamble for requesting SI.

9. The method according to claim 7 or 8, wherein the method further comprises:

10. The method of claim 9, wherein the second indication information does not indicate index information of a first type preamble of the at least one first type preamble, the index information of the first type preamble being predetermined index information.

11. The method of any of claims 1, 3, 4, 6 to 8, 10, wherein the terminal device selects a first preamble from a first preamble set, comprising:

The terminal equipment determines the first preamble group corresponding to the first type of data, and selects a first preamble from the first preamble group.

12. The method of claim 1 or 2, wherein the first preamble set is a shared preamble set for the first type of data transmission and the second type of data transmission, wherein a size range of the first type of data and a size range of the second type of data are different.

13. The method of claim 12, wherein,

The shared preamble group is the competition preamble group A, or

The shared preamble set is a contention preamble set B.

14. The method of claim 13, wherein the terminal device selecting a first preamble from a first preamble set comprises:

The terminal equipment receives third indication information sent by network equipment, wherein the third indication information is used for indicating at least one first type of lead code in the shared lead code group or indicating a lead code range in the shared lead code group, and the lead code range is used for determining at least one first type of lead code;

The terminal device selects the first preamble from the at least one first type of preamble based on the third indication information.

15. The method of claim 14, wherein the shared preamble set comprises at least one contention preamble in addition to the at least one first type preamble;

the method further comprises the steps of:

The terminal equipment maps the at least one competition lead code in the shared lead code group to at least one PUSCH resource in a second PUSCH configuration, wherein the second PUSCH configuration is the PUSCH configuration used for the second type data transmission.

16. The method of any of claims 1-4, 6-8, 10, 13-15, wherein the determining, by the terminal device, a first PUSCH resource corresponding to the first preamble based on the first PUSCH configuration comprises:

the terminal equipment maps at least one first type of preamble in the first preamble group to at least one PUSCH resource in the first PUSCH configuration, wherein the first preamble in the at least one first type of preamble is mapped to a first PUSCH resource in the at least one PUSCH resource.

17. The method of any of claims 1-4, 6-8, 10, 13-15, wherein the first type of data is small data.

18. A method of data transmission, the method comprising:

The terminal equipment determines a first PUSCH resource corresponding to the first RO resource based on the first PUSCH configuration, and transmits the first type data on the first PUSCH resource;

wherein, the first PUSCH configuration has an association relationship with a first preamble group on the first RO resource group;

19. The method of claim 18, wherein the method further comprises:

The terminal equipment receives second configuration information sent by the network equipment, wherein the second configuration information is used for determining at least one of the following:

the first PUSCH configuration;

Index information of the first RO resource group;

20. A data transmission apparatus, the apparatus comprising:

a transmission unit, configured to transmit the first type of data on the first PUSCH resource;

wherein,

The first preamble set includes at least one first type preamble associated with each SSB of the plurality of SSBs, or

The first preamble group comprises at least one first type preamble associated with one RO;

21. The apparatus of claim 20, wherein the apparatus further comprises:

the receiving unit is used for receiving first configuration information sent by the network equipment, and the first configuration information is used for determining at least one of the following:

the first PUSCH configuration;

Index information of the first preamble group;

22. The apparatus of claim 20, wherein the apparatus further comprises:

23. The apparatus of claim 22, wherein each SSB is associated with at least one of the following in addition to the at least one first type preamble:

At least one contention preamble;

at least one non-contention preamble;

at least one preamble for requesting SI.

24. The apparatus of claim 22 or 23, wherein the receiving unit is further configured to receive first indication information sent by the network device, where the first indication information is used to indicate index information of a first type preamble of the at least one first type preamble and/or indicate a number of the at least one first type preamble.

25. The apparatus of claim 24, wherein the first indication information does not indicate index information of a first type of preamble of the at least one first type of preamble, the index information of the first type of preamble being predetermined index information.

26. The apparatus of claim 20, wherein the apparatus further comprises:

27. The apparatus of claim 26, wherein the RO is associated with at least one of the following in addition to the at least one first type preamble:

At least one contention preamble;

at least one non-contention preamble;

at least one preamble for requesting SI.

28. The apparatus of claim 26 or 27, wherein the receiving unit is further configured to receive second indication information sent by the network device, where the second indication information is used to indicate index information of a first type preamble of the at least one first type preamble and/or indicate a number of the at least one first type preamble.

29. The apparatus of claim 28, wherein the second indication information indicates index information of a first type preamble of the at least one first type preamble, the index information of the first type preamble being predetermined index information.

30. The apparatus of any one of claims 20, 22, 23, 25 to 27, 29, wherein the selecting unit is configured to determine the first preamble group corresponding to the first type of data, and select a first preamble from the first preamble group.

31. The apparatus of claim 20 or 21, wherein the first preamble set is a shared preamble set for the first type of data transmission and the second type of data transmission, wherein a size range of the first type of data and a size range of the second type of data are different.

32. The apparatus of claim 31, wherein,

The shared preamble group is the competition preamble group A, or

The shared preamble set is a contention preamble set B.

33. The apparatus of claim 32, wherein the apparatus further comprises:

34. The apparatus of claim 33, wherein the shared preamble set comprises at least one contention preamble in addition to the at least one first type preamble;

35. The apparatus of any one of claims 20-23, 25-27, 29, 32-34, wherein the apparatus further comprises a mapping unit configured to map at least one first type of preamble in the first preamble set to at least one PUSCH resource in the first PUSCH configuration, wherein the first preamble in the at least one first type of preamble is mapped to a first PUSCH resource in the at least one PUSCH resource.

36. The apparatus of any of claims 20 to 23, 25 to 27, 29, 32 to 34, wherein the first type of data is small data.

37. A data transmission apparatus, the apparatus comprising:

38. The apparatus of claim 37, wherein the apparatus further comprises:

the receiving unit is used for receiving second configuration information sent by the network equipment, and the second configuration information is used for determining at least one of the following:

the first PUSCH configuration;

Index information of the first RO resource group;

39. A terminal device comprising a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory for performing the method according to any of claims 1 to 19.

40. A chip comprising a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 19.

41. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 19.