Data transmission method and device, and terminal equipment

Abstract

An embodiment of the present application provides a data transmission method and apparatus, and a terminal device, the method comprising: the terminal device selects a first preamble code from a first preamble code group, the first preamble code group is associated with a first physical uplink shared channel PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration for a first type of data transmission; the terminal device determines a first PUSCH resource corresponding to the first preamble code based on the first PUSCH configuration, and transmits the first type of data on the first PUSCH resource.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a data transmission method and apparatus, and a terminal device. Background Art

[0002] In the New Radio (NR) system, small data transmission is not supported when the Radio Resource Control (RRC) is not activated. NR introduces a two-step random access process, in which the Physical Uplink Shared Channel (PUSCH) of the MSGA in the two-step random access process can be configured to different sizes. How to transmit small data through the PUSCH needs to be clarified. Summary of the invention

[0003] The embodiments of the present application provide a data transmission method and apparatus, and a terminal device.

[0004] The data transmission method provided in the embodiment of the present application includes:

[0005] The terminal device selects a first preamble from a first preamble group, the first preamble group is associated with a first PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration for first-category data transmission;

[0006] The terminal device determines a first PUSCH resource corresponding to the first preamble code based on the first PUSCH configuration, and transmits the first type of data on the first PUSCH resource.

[0007] The data transmission method provided in the embodiment of the present application includes:

[0008] The terminal device selects a first RO resource from a first RO resource group, where the first RO resource group is an RO resource group used for first-type data transmission, the first RO resource group is associated with a first PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration used for the first-type data transmission;

[0009] 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 of data on the first PUSCH resource.

[0010] The data transmission device provided in the embodiment of the present application includes:

[0011] A selection unit, configured to select a first preamble from a first preamble group, wherein the first preamble group is associated with a first PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration for first-type data transmission;

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

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

[0014] The data transmission device provided in the embodiment of the present application includes:

[0015] A selection unit, configured to select a first RO resource from a first RO resource group, wherein the first RO resource group is an RO resource group used for first-type data transmission, the first RO resource group is associated with a first PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration used for the first-type data transmission;

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

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

[0018] The terminal device provided in the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above-mentioned data transmission method.

[0019] The chip provided in the embodiment of the present application is used to implement the above-mentioned data transmission method.

[0020] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned data transmission method.

[0021] The computer-readable storage medium provided in the embodiment of the present application is used to store a computer program, which enables a computer to execute the above-mentioned data transmission method.

[0022] The computer program product provided in the embodiment of the present application includes computer program instructions, which enable a computer to execute the above-mentioned data transmission method.

[0023] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned data transmission method.

[0024] Through the above technical solution, a specific PUSCH configuration and a specific preamble group or RO resource group are configured for the first type of data transmission. By associating the specific PUSCH configuration with the specific preamble group or RO resource group, the terminal device can use the PUSCH resource associated with the specific random access resource (such as a specific preamble or a specific RO resource) to transmit the first type of data during the random access process. Since the specific random access resource is different from the random access resource used by the traditional terminal device, the impact on the traditional terminal device is avoided. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0026] Figure 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

[0027] Figure 2 Schematic diagram of the data transmission method provided in the embodiment of the present application Figure 1 ;

[0028] Figure 3 This is a schematic diagram of the association between the preamble group and the PUSCH configuration provided in the embodiment of the present application Figure 1 ;

[0029] Figure 4 This is a schematic diagram of the preamble allocation provided in the embodiment of the present application. Figure 1 ;

[0030] Figure 5 This is a schematic diagram of the preamble allocation provided in the embodiment of the present application. Figure 2 ;

[0031] Figure 6 This is a schematic diagram of the preamble allocation provided in the embodiment of the present application. Figure 3 ;

[0032] Figure 7 This is a schematic diagram of the association between the preamble group and the PUSCH configuration provided in the embodiment of the present application Figure 2 ;

[0033] Figure 8 Schematic diagram of the data transmission method provided in the embodiment of the present application Figure 2 ;

[0034] Fig. 9 Schematic diagram of the structure of the data transmission device provided in the embodiment of the present application Figure 1 ;

[0035] Fig.10 Schematic diagram of the structure of the data transmission device provided in the embodiment of the present application Figure 2 ;

[0036] Fig.11 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0037] Fig.12 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0038] Fig.13 It is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0040] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, 5G communication system or future communication system, etc.

[0041] For example, the communication system 100 used in the embodiment of the present application is as follows: Figure 1 As shown. The communication system 100 may include a network device 110, which may be a device that communicates with a terminal 120. The network device 110 may provide communication coverage for a specific geographical area, and may communicate with terminals located within the coverage area. Optionally, the network device 110 may be an evolved base station (eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle-mounted 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.

[0042] The communication system 100 also includes at least one terminal 120 located within the coverage of the network device 110. The terminal 120 is connected to the network device 110 via a wired line or a wireless interface. The terminal 110 connected to the network device 110 via a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". The terminal may refer to an access terminal, a user equipment (UE), a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user device, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G network or a terminal in a future evolved PLMN, etc.

[0043] Optionally, the terminals 120 may perform device-to-device (D2D) communication.

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

[0045] Figure 1 One network device and two terminals are shown exemplarily. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminals within its coverage area, which is not limited in the embodiments of the present application.

[0046] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

[0047] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1 Taking the communication system 100 shown as an example, the communication system 100 may include a network device 110 and a terminal 120 with communication functions. The network device 110 and the terminal 120 may be the specific devices described above and will not be repeated here. The communication system 100 may also include other devices, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

[0048] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0049] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions related to the embodiments of the present application are described below.

[0050] Small data transmission

[0051] 3GPP R17 proposes the need to support small data transmission of terminal devices in the RRC inactive state. The main purpose is to save power and signaling overhead. The specific project goals include:

[0052] Small data transmission optimization based on random access procedure, where the random access procedure includes 4-step random access procedure and 2-step random access procedure.

[0053] Small data transmission optimization based on type 1 pre-configured grant, that is, it is necessary to support type 1 pre-configured grant transmission in RRC inactive state.

[0054] RRC status

[0055] In order to reduce air interface signaling and quickly restore wireless connections and data services in the 5G network environment, a new RRC state is defined, namely the RRC inactive (RRC_INACTIVE) state. This state is different from the RRC idle (RRC_IDLE) state and the RRC active (RRC_ACTIVE) state.

[0056] RRC_IDLE state (abbreviated as RRC idle state): Mobility is based on cell selection and reselection, paging is initiated by the core network (CN), and the paging area is configured by the CN. There is no context of the terminal device on the base station side, and there is no RRC connection.

[0057] RRC_INACTIVE state (RRC inactive state for short): Mobility is based on cell selection and reselection, there is a connection between CN and NR, the terminal device context exists on a certain base station, paging is triggered by RAN, and the RAN-based paging area is managed by RAN. The network side knows the location of the terminal device based on the RAN paging area level.

[0058] RRC_CONNECTED state (RRC connection state for short): There is an RRC connection, and there is a terminal device context on the base station side and the terminal device side. The network side knows the location of the terminal device at the specific cell level. Mobility is mobility controlled by the network side. Unicast data can be transmitted between the terminal board and the base station.

[0059] The above three RRC states can be converted to each other. Among them, some RRC parameters on the terminal device side in the RRC inactive state are configured through the RRC release message. The main RRC parameters are as follows:

[0060] The inactive RNTI (I-RNTI) is used to identify the inactive context of the terminal device on the base station side and is unique within the base station.

[0061] RAN Notification Area (RNA) is an area used to control the cell selection and reselection of the terminal device in the RRC inactive state, and is also the paging range area of ​​the RAN initial paging.

[0062] RAN Paging cycle: used to calculate the paging opportunity of RAN initial paging.

[0063] Next hop chaining counter (NCC) is used to determine the key used during RRC connection recovery.

[0064] When the terminal device moves within the RNA area, it does not need to notify the network side and follows the mobility behavior in the RRC idle state, that is, the cell selection and reselection principle. When the terminal device moves out of the paging area configured by the RAN, the terminal device triggers the RRC connection recovery process (that is, RRC resume procedure) and reacquires the paging area configured by the RAN. When the network side needs to transmit data to the terminal device, that is, when downlink data arrives, the base station that saves the terminal device context will trigger all cells in the RAN paging area to send a paging message to the terminal device, so that the terminal device in the RRC inactive state can restore the RRC connection and receive data. In addition, the terminal device in the RRC inactive state is configured with a RAN paging area. In this area, in order to ensure the reachability of the terminal device, the terminal device needs to perform periodic location updates according to the period configured by the network. The scenarios that trigger the terminal device to perform RNA updates include the expiration of the RNAU timer or the movement of the terminal device to an area outside the RNA. At present, the RRC inactive state defined by NR does not support the transmission of user plane data by terminal devices.

[0065] ●Random access process

[0066] The random access procedure supports two random access types, 2-step RA type and 4-step RA type. Both random access types support contention-based random access (CBRA) and contention-free random access (CFRA) procedures.

[0067] The terminal device selects the random access type based on the configuration on the network side. Specifically, 1) If the network side does not configure CFRA resources, the terminal device determines whether to use the 2-step random access type or the 4-step random access type to perform the random access process based on the Reference Signal Received Power (RSRP) threshold. 2) If the network side configures CFRA resources of the 4-step random access type, the terminal device uses the 4-step random access type to perform the random access process. 3) If the network side configures CFRA resources of the 2-step random access type, the terminal device uses the 2-step random access type to perform the random access process.

[0068] The contention-based 4-step random access type procedure includes the following steps:

[0069] MSG1: The terminal device sends a preamble code to the base station.

[0070] MSG2: The base station sends a random access response message to the terminal device.

[0071] MSG3: The terminal device sends PUSCH to the base station.

[0072] MSG4: The base station sends a contention resolution message to the terminal device.

[0073] The contention-based 2-step random access type can improve latency while reducing signaling overhead, including the following steps:

[0074] MSGA: The terminal device sends a preamble and PUSCH to the base station.

[0075] MSGB: The base station sends a contention resolution message to the terminal device.

[0076] It should be noted that the MAGA in the 2-step random access type includes a preamble transmitted on a physical random access channel (PRACH) and a payload transmitted on a PUSCH.

[0077] Since NR does not support small data transmission in the RRC inactive state, a two-step random access process is introduced in NR. The PUSCH of the MSGA in the two-step random access process can be configured to different sizes.

[0078] In the 2-step random access process, the PUSCH configuration (PUSCH config) is associated with the contention preamble group (CB preamblegroup). The network can configure up to 2 PUSCH configs, of which 1 PUSCH config has only 1 TB size (TB size). In RRC inactive state or RRC idle state, considering the coverage range, the TB size (TB size) supported by the PUSCH config is 56 bits or 72 bits.

[0079] If the network side configures CB preamble group A and CB preamble group B, the network side will also configure a payload threshold for the terminal device to select the preamble group.

[0080] In order to support small data transmission under the RRC non-activated state, the network side will configure the PUSCH config for small data transmission, and the PUSCH config has a relatively large TB size. And the PUSCH config is associated with a preamble group. However, this will affect the selection of preamble groups by traditional terminal devices. For example, for terminal devices that only need 72 bits to transmit data, the terminal device will select contention preamble group B according to the existing mechanism, and the contention preamble group B is associated with the PUSCH config for small data transmission. This will cause the terminal device to carry a large amount of padding when transmitting data, reducing resource utilization efficiency. In addition, since the network side is configured with the PUSCH config for small data transmission, it is also necessary to clarify how to prevent traditional terminal devices from selecting the PUSCH config. To this end, the following technical solution of the embodiment of the present application is proposed.

[0081] Figure 2 Schematic diagram of the data transmission method provided in the embodiment of the present application Figure 1 ,like Figure 2 As shown, the data transmission method includes the following steps:

[0082] Step 201: A terminal device selects a first preamble code from a first preamble code group, wherein the first preamble code group is associated with a first PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration for a first type of data transmission.

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

[0084] the first PUSCH configuration;

[0085] Index information of the first preamble group;

[0086] The association relationship between the first PUSCH configuration and the first preamble code group.

[0087] Here, optionally, the network device may be a base station, such as a gNB.

[0088] In the embodiment of the present application, the first type of data may be small data. Not limited thereto, the first type of data may also be other types of data, such as data with a size within a specified range. Optionally, a terminal device that transmits the first type of data may be referred to as a first type of terminal (such as a small data terminal), and a terminal device that transmits the second type of data may be referred to as a second type of terminal (such as a normal terminal). Here, the size range of the first type of data is different from the size range of the second type of data.

[0089] In the embodiment of the present application, the network device configures a PUSCH configuration for Type 1 data transmission (PUSCH config for Type 1 data). For example, the network device configures a PUSCH configuration for small data transmission (PUSCH config for small data). Here, the PUSCH configuration for Type 1 data transmission is referred to as the first PUSCH configuration.

[0090] It should be noted that the first PUSCH configuration is used to determine a plurality of PUSCH resources, and one PUSCH resource is a PUSCH resource unit (PRU). Each of the plurality of PUSCH resources is a PUSCH resource for first-category data transmission.

[0091] In the embodiment of the present application, the first PUSCH configuration is associated with the first preamble group. Accordingly, in addition to configuring the first PUSCH configuration, the network device also configures index information of the first preamble group and / or the association between the first PUSCH configuration and the first preamble group.

[0092] In the embodiment of the present application, the first preamble group may be a preamble group for the first type of data transmission, or the first preamble group is a shared preamble group for the first type of data transmission and the second type of data transmission. The technical solution of the embodiment of the present application is described in detail below in combination with different implementations of the first preamble group.

[0093] ●Method 1

[0094] The first preamble group is a preamble group used for the first type of data transmission.

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

[0096] In specific implementation, the terminal device can select the first preamble code group according to the size of the first category of data. For example: assuming that there are 3 preamble code groups, namely the first preamble code group, the second preamble code group, and the third preamble code group, wherein the data size range corresponding to the first preamble code group is Range1, the data size range corresponding to the second preamble code group is Range2, and the data size range corresponding to the third preamble code group is Range3, then the terminal device can determine to select the first preamble code group according to the size of the first category of data falling into Range1. Since all preamble codes in the first preamble code group are configured for the first category of data transmission, the first preamble code selected by the terminal device from the first preamble code group is the preamble code used for the first category of data transmission.

[0097] In an embodiment of the present application, when determining which preamble codes belong to the first preamble code group, it is necessary to exclude contention based preamble codes, non-contention free preamble codes and preamble codes used to request system information (System Information, SI) because these preamble codes have been allocated to other preamble code groups.

[0098] like Figure 3As shown, the network side configures three preamble groups, namely the first preamble group, contention preamble group A, and contention preamble group B, wherein the first preamble group is associated with PUSCH config3 (i.e., the first PUSCH configuration), contention preamble group A is associated with PUSCH config1, and contention preamble group B is associated with PUSCH config2. Here, the preambles in contention preamble group A and contention preamble group B are both contention preambles, and the preambles in the first preamble group are preambles for the first type of data transmission. It should be noted that the preambles in the first preamble group are actually also contention-type preambles, but the first preamble group and contention preamble group A (or contention preamble group B) target different data types. In an optional manner, the first preamble group may also be referred to as contention preamble group C. It should be noted that there is no intersection between different preamble groups.

[0099] In an embodiment of the present application, the first preamble group includes at least one first-type preamble associated with each SSB in a plurality of SSBs; or, the first preamble group includes at least one first-type preamble associated with a random access opportunity (RACH Occasion, RO); wherein the first-type preamble is a preamble used for the first-type data transmission. The following describes how to determine which preambles belong to the first preamble group in combination with different situations.

[0100] Case 1: M SSBs are associated with one RO, where M is an integer greater than 1 and less than or equal to N.

[0101] Here, the terminal device receives a first parameter and a second parameter sent by a network device, the first parameter is used to determine the N SSBs actually transmitted by the network device, N is a positive integer, and the second parameter is used to determine the 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 via a system broadcast message.

[0102] In the case where the second parameter is used to indicate that M SSBs are associated with one RO, the first preamble code group includes at least one first-type preamble code associated with each SSB in the M SSBs, and the first-type preamble code is a preamble code used for the first-type data transmission.

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

[0104] at least one contention preamble;

[0105] at least one non-contention preamble;

[0106] At least one preamble for requesting SI.

[0107] That is to say, in the case where multiple SSBs are associated with one RO, the preamble used for the first type of data transmission can be a preamble code that excludes contention preambles, non-contention preambles, and preambles for requesting SI from the preamble code set associated with each SSB in the multiple SSBs. It should be noted that the preamble code types included in the preamble code set associated with each SSB include the first type of preamble code and at least one of the following: contention preamble code, non-contention preamble code, and preamble code for requesting SI. Different types of preamble codes are used for different types of random access. For example: the first type of preamble code is used for random access of the first type of data transmission, the contention preamble code is used for contention random access, the non-contention preamble code is used for non-contention random access, and the preamble code for requesting SI is used for random access for requesting SI.

[0108] In this embodiment, in the case where multiple SSBs are associated with one RO, a preamble code set associated with one RO will be allocated (associated) to multiple SSBs.

[0109] Reference Figure 4 , if two SSBs are associated with one RO (i.e., M=2), then for SSB#1, the associated preamble sets include: contention preamble set 1, non-contention preamble set 1, and first-category preamble set 1, wherein contention preamble set 1 includes some preambles in contention preamble group A+B (i.e., contention preamble group A and contention preamble group B). Similarly, for SSB#2, the associated preamble sets include: contention preamble set 2, non-contention preamble set 2, and first-category preamble set 2, wherein contention preamble set 2 includes some preambles in contention preamble group A+B (i.e., contention preamble group A and contention preamble group B).

[0110] It should be noted that the indexes of the preambles in a preamble set associated with an RO are continuously distributed. When M SSBs are determined to be associated with an RO, the index range of the preamble set associated with each SSB is determined. In order to distinguish which preambles in the preamble set associated with each SSB belong to the first category of preambles, the network side needs to indicate to the terminal device the index information of the first first category preamble in the first category of preamble set associated with each SSB and / or the number of preambles included in the first category of preamble set. Specifically,

[0111] The terminal device receives first indication information sent by the network device, where the first indication information is used to indicate index information of the first first-type preamble code in the at least one first-type preamble code and / or indicate the number of the at least one first-type preamble code.

[0112] Further, optionally, when the first indication information does not indicate the index information of the first first-class preamble code in the at least one first-class preamble code, the index information of the first first-class preamble code is predetermined index information, for example, the index information of the first first-class preamble code is the index information of the first preamble code after a non-competitive preamble code set, or the index information of the first first-class preamble code is the index information of the first preamble code after a competitive preamble code set.

[0113] Reference Figure 5 , Figure 5 and Figure 4 The difference is that Figure 5 The first type of preamble set 1 associated with SSB#1 and the first type of preamble set 2 associated with SSB#2 are concentrated. Figure 4 The same is that for SSB#1, the associated preamble set includes: contention preamble set 1, non-contention preamble set 1 and first-class preamble set 1, wherein contention preamble set 1 includes some preambles in contention preamble group A+B (i.e., contention preamble group A and contention preamble group B). Similarly, for SSB#2, the associated preamble set includes: contention preamble set 2, non-contention preamble set 2 and first-class preamble set 2, wherein contention preamble set 2 includes some preambles in contention preamble group A+B (i.e., contention preamble group A and contention preamble group B). Here, since the first-class preamble set 1 associated with SSB#1 and the first-class preamble set 2 associated with SSB#2 are concentratedly distributed, the network needs to indicate the index information of the first first-class preamble in the first-class preamble set associated with each SSB.

[0114] Case 2: When one SSB is associated with M ROs, M is an integer greater than or equal to 1.

[0115] The first preamble group is a shared preamble group used for the first type of data transmission and the second type of data transmission.

[0116] Here, the terminal device receives a first parameter and a second parameter sent by a network device, the first parameter is used to determine the N SSBs actually transmitted by the network device, N is a positive integer, and the second parameter is used to determine the 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 via a system broadcast message.

[0117] In the case where the second parameter is used to indicate that one SSB is associated with M ROs, for one RO among the M ROs, the first preamble group includes at least one first-type preamble associated with the RO, and the first-type preamble is a preamble used for the first-type data transmission.

[0118] Further, optionally, in addition to being associated with the at least one first-type preamble, the RO is also associated with at least one of the following:

[0119] at least one contention preamble;

[0120] at least one non-contention preamble;

[0121] At least one preamble for requesting SI.

[0122] That is to say, when a SSB is associated with multiple ROs, the preamble used for the first type of data transmission can be a preamble code set associated with an RO, excluding the contention preamble code, the non-contention preamble code, and the preamble code for requesting SI. It should be noted that the preamble code types included in the preamble code set associated with an RO include the first type of preamble code and at least one of the following: contention preamble code, non-contention preamble code, and preamble code for requesting SI. Different types of preamble codes are used for different types of random access. For example: the first type of preamble code is used for random access of the first type of data transmission, the contention preamble code is used for contention random access, the non-contention preamble code is used for non-contention random access, and the preamble code for requesting SI is used for random access for requesting SI.

[0123] It can be understood that a RO-associated preamble set includes: a contention preamble set, a non-contention preamble set, a first-class preamble set, and a preamble set for SI request. Among them, the contention preamble set can be contention preamble group A+B (i.e., contention preamble group A and contention preamble group B).

[0124] In this embodiment, in the case where one SSB is associated with multiple ROs, the preamble code sets associated with multiple ROs are allocated (associated) to one SSB, where the preamble code sets associated with each RO are repeated.

[0125] Reference Figure 6 , Figure 6 An RO-associated preamble set is illustrated, including: a contention preamble set, a non-contention preamble set, a first-class preamble set and a preamble set for SI request, wherein the contention preamble set includes contention preamble group A+B (ie, contention preamble group A and contention preamble group B).

[0126] It should be noted that the indexes of the preambles in a RO-associated preamble set are continuously distributed. In order to distinguish which preambles in the RO-associated preamble set belong to the first category of preambles, the network side needs to indicate to the terminal device the index information of the first first category of preambles in the RO-associated first category of preamble set and / or the number of preambles included in the first category of preamble set. Specifically,

[0127] The terminal device receives second indication information sent by the network device, where the second indication information is used to indicate the index information of the first first-type preamble code in the at least one first-type preamble code and / or indicate the number of the at least one first-type preamble code.

[0128] When the second indication information does not indicate the index information of the first first-class preamble code in the at least one first-class preamble code, the index information of the first first-class preamble code is predetermined index information, for example, the index information of the first first-class preamble code is the index information of the first preamble code after the non-competitive preamble code set, or the index information of the first first-class preamble code is the index information of the first preamble code after the competitive preamble code set.

[0129] ●Method 2

[0130] The first preamble code group is a shared preamble code group used for the first type of data transmission and the second type of data transmission, wherein the size range of the first type of data is different from the size range of the second type of data.

[0131] In an optional manner, the shared preamble group is contention preamble group A. In another optional manner, the shared preamble group is contention preamble group B. Here, contention preamble group A and contention preamble group B may be existing contention preamble groups.

[0132] In this embodiment, the terminal device is configured with at most two preamble groups, namely contention preamble group A and contention preamble group B. The network side indicates which preambles in contention preamble group A and / or contention preamble group B can be used to transmit the first type of data.

[0133] Specifically, the terminal device receives third indication information sent by the network device, and the third indication information is used to indicate at least one first-class preamble code in the shared preamble code group or to indicate a preamble code range in the shared preamble code group, and the preamble code range is used to determine at least one first-class preamble code; wherein the first-class preamble code is a preamble code used for the transmission of the first-class data; the terminal device selects the first preamble code from the at least one first-class preamble code based on the third indication information.

[0134] Reference Figure 7 The network side configures two preamble groups, namely contention preamble group A and contention preamble group B. Contention preamble group A is associated with PUSCH config1, and contention preamble group B is associated with PUSCH config2. In addition, contention preamble group A and / or contention preamble group B can also be associated with PUSCH config3 (i.e., the first PUSCH configuration).

[0135] In this embodiment, in addition to the at least one first-type preamble code, the shared preamble code group also includes at least one contention preamble code; the terminal device maps the at least one contention preamble code in the shared preamble code group to at least one PUSCH resource in the second PUSCH configuration; wherein the second PUSCH configuration is a PUSCH configuration for the second-type data transmission.

[0136] Reference Figure 7 Taking the contention preamble group A associated with PUSCH config1 and PUSCH config3 as an example, the preambles in contention preamble group A are divided into two parts, one part is associated with PUSCH config1 (that is, at least one contention preamble is associated with PUSCH config1), and the other part is associated with PUSCH config3 (that is, at least one first-class preamble is associated with PUSCH config3). When the terminal device maps the preambles in contention preamble group A to the PRU of PUSCH config1, if some of the preambles are first-class preambles assigned by the network to the first-class data transmission, the terminal device needs to exclude these first-class preambles. Similarly, for the preambles in contention preamble group B, it is also necessary to exclude those first-class preambles that have been assigned to the first-class data transmission before mapping to PUSCH config2.

[0137] Step 202: The terminal device determines a first PUSCH resource corresponding to the first preamble code based on the first PUSCH configuration, and transmits the first type of data on the first PUSCH resource.

[0138] In an embodiment of the present application, the terminal device maps at least one first-category 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-category preamble is mapped to the first PUSCH resource in the at least one PUSCH resource. In this way, the terminal device can 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-category data on the first PUSCH resource.

[0139] It should be noted that the technical solution of the embodiment of the present application takes the configuration of a first PUSCH configuration and a first preamble code group on the network side as an example, but is not limited to this. The network side can also configure multiple first PUSCH configurations and multiple first preamble code groups, wherein different first PUSCH configurations in the multiple first PUSCH configurations have different TB sizes. Accordingly, if the network side configures multiple first PUSCH configurations, then the association relationship between each first PUSCH configuration and the preamble code can be determined with reference to the technical solution of the embodiment of the present application. For example: each first PUSCH configuration is associated with a first preamble code group or is associated with part of the preamble codes in the shared preamble group.

[0140] Figure 8 Schematic diagram of the data transmission method provided in the embodiment of the present application Figure 2 ,like Figure 8 As shown, the data transmission method includes the following steps:

[0141] Step 801: The terminal device selects a first RO resource from a first RO resource group, where the first RO resource group is an RO resource group used for first type data transmission, and the first RO resource group is associated with a first PUSCH configuration, which is a PUSCH configuration used for the first type data transmission.

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

[0143] the first PUSCH configuration;

[0144] Index information of the first RO resource group;

[0145] The association relationship between the first PUSCH configuration and the first RO resource group.

[0146] Here, optionally, the network device may be a base station, such as a gNB.

[0147] In the embodiment of the present application, the first type of data may be small data. Not limited thereto, the first type of data may also be other types of data, such as data with a size within a specified range. Optionally, a terminal device that transmits the first type of data may be referred to as a first type of terminal (such as a small data terminal), and a terminal device that transmits the second type of data may be referred to as a second type of terminal (such as a normal terminal). Here, the size range of the first type of data is different from the size range of the second type of data.

[0148] In the embodiment of the present application, the network device configures a PUSCH configuration for Type 1 data transmission (PUSCH config for Type 1 data). For example, the network device configures a PUSCH configuration for small data transmission (PUSCH config for small data). Here, the PUSCH configuration for Type 1 data transmission is referred to as the first PUSCH configuration.

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

[0150] In the embodiment of the present application, the first PUSCH configuration is associated with the first preamble code group on the first RO resource group.

[0151] Further, optionally, the terminal device may support first PUSCH configurations of different sizes. For example, the network may configure first PUSCH configurations of two TB sizes, such as PUSCH config1 and PUSCH config2. The two first PUSCH configurations correspond to different preamble code groups on the first RO resource group.

[0152] 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 of data on the first PUSCH resource.

[0153] In an embodiment of the present application, when initiating first-type data transmission, the terminal device selects the first RO resource from the first RO resources, determines a first PUSCH resource corresponding to the first RO resource, and transmits the first-type data on the first PUSCH resource.

[0154] It should be noted that for a traditional terminal device (ie, a terminal device transmitting the second type of data), when mapping the preamble code to the PRU, the preamble code on the RO resource that has been allocated to the first type of data transmission needs to be excluded.

[0155] It should be noted that the technical solution of the embodiment of the present application takes the configuration of a first PUSCH configuration on the network side as an example, but is not limited to this. The network side can also configure multiple first PUSCH configurations, wherein different first PUSCH configurations in the multiple first PUSCH configurations have different TB sizes. Accordingly, if the network side configures multiple first PUSCH configurations, then the association relationship between each first PUSCH configuration and the RO resource can 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.

[0156] Fig. 9 Schematic diagram of the structure of the data transmission device provided in the embodiment of the present application Figure 1 , applied to terminal devices, such as Fig. 9 As shown, the data transmission device includes:

[0157] A selecting unit 901 is configured to select a first preamble from a first preamble group, where the first preamble group is associated with a first PUSCH configuration, where the first PUSCH configuration is a PUSCH configuration for first-type data transmission;

[0158] A determining unit 902 is configured to determine a first PUSCH resource corresponding to the first preamble code based on the first PUSCH configuration;

[0159] The transmission unit 903 is configured to transmit the first type of data on the first PUSCH resource.

[0160] In an optional manner, the device further includes:

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

[0162] the first PUSCH configuration;

[0163] Index information of the first preamble group;

[0164] The association relationship between the first PUSCH configuration and the first preamble code group.

[0165] In an optional manner, the first preamble code group is a preamble code group used for the first type of data transmission.

[0166] In an optional embodiment, the first preamble code group includes at least one first-class preamble code associated with each SSB in multiple SSBs; or, the first preamble code group includes at least one first-class preamble code associated with an RO; wherein the first-class preamble code is a preamble code used for the first-class data transmission.

[0167] In an optional manner, the device further includes:

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

[0169] The second parameter is used to indicate that M SSBs are associated with one RO, where M is an integer greater than 1 and less than or equal to N, and the first preamble code group includes at least one first-type preamble code associated with each SSB in the M SSBs.

[0170] In an optional manner, each SSB is associated with at least one of the following in addition to being associated with the at least one first-type preamble:

[0171] at least one contention preamble;

[0172] at least one non-contention preamble;

[0173] At least one preamble for requesting SI.

[0174] In an optional manner, the receiving unit is also used to receive first indication information sent by the network device, and the first indication information is used to indicate the index information of the first first-class preamble code in the at least one first-class preamble code and / or indicate the number of the at least one first-class preamble code.

[0175] In an optional manner, when the first indication information does not indicate the index information of the first first-type preamble code in the at least one first-type preamble code, the index information of the first first-type preamble code is predetermined index information.

[0176] In an optional manner, the device further includes:

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

[0178] The second parameter is used to indicate that, when one SSB is associated with M ROs, M is an integer greater than or equal to 1, and for one RO among the M ROs, the first preamble code group includes at least one first-type preamble code associated with the RO.

[0179] In an optional manner, the RO is associated with at least one of the following in addition to the at least one first-type preamble:

[0180] at least one contention preamble;

[0181] at least one non-contention preamble;

[0182] At least one preamble for requesting SI.

[0183] In an optional embodiment, the receiving unit is also used to receive second indication information sent by the network device, and the second indication information is used to indicate the index information of the first first-class preamble code in the at least one first-class preamble code and / or indicate the number of the at least one first-class preamble code.

[0184] In an optional manner, when the second indication information does not indicate the index information of the first first-type preamble code in the at least one first-type preamble code, the index information of the first first-type preamble code is predetermined index information.

[0185] In an optional manner, the selection unit 901 is used to determine the first preamble code group corresponding to the first category of data, and select a first preamble code from the first preamble code group.

[0186] In an optional manner, the first preamble code group is a shared preamble code group used for the first type of data transmission and the second type of data transmission, wherein the size range of the first type of data is different from the size range of the second type of data.

[0187] In an optional manner, the shared preamble group is contention preamble group A; or,

[0188] The shared preamble code group is contention preamble code group B.

[0189] In an optional manner, the device further includes:

[0190] a receiving unit, configured to receive third indication information sent by a network device, wherein the third indication information is used to indicate at least one first-category preamble in the shared preamble group or to indicate a preamble range in the shared preamble group, the preamble range being used to determine at least one first-category preamble; wherein the first-category preamble is a preamble used for transmission of the first-category data;

[0191] The selection unit is configured to select the first preamble code from the at least one first-type preamble code based on the third indication information.

[0192] In an optional manner, the shared preamble group includes at least one contention preamble in addition to the at least one first-category preamble;

[0193] The device also includes: a mapping unit, configured to map the at least one contention preamble in the shared preamble group to at least one PUSCH resource in a second PUSCH configuration; wherein the second PUSCH configuration is a PUSCH configuration for the second type of data transmission.

[0194] In an optional embodiment, the device also includes: a mapping unit (not shown in the figure), used to map at least one first-type preamble code in the first preamble code group to at least one PUSCH resource in the first PUSCH configuration; wherein the first preamble code in the at least one first-type preamble code is mapped to the first PUSCH resource in the at least one PUSCH resource.

[0195] In an optional manner, the first category of data is small data.

[0196] Those skilled in the art should understand that the relevant description of the above-mentioned data transmission device in the embodiment of the present application can be understood by referring to the relevant description of the data transmission method in the embodiment of the present application.

[0197] Fig.10 Schematic diagram of the structure of the data transmission device provided in the embodiment of the present application Figure 2 , applied to terminal devices, such as Fig.10 As shown, the data transmission device includes:

[0198] A selection unit 1001 is configured to select a first RO resource from a first RO resource group, where the first RO resource group is an RO resource group used for first-type data transmission, the first RO resource group is associated with a first PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration used for the first-type data transmission;

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

[0200] The transmission unit 1003 is used to transmit the first type of data on the first PUSCH resource.

[0201] In an optional manner, the device further includes:

[0202] The receiving unit (not shown in the figure) is used 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:

[0203] the first PUSCH configuration;

[0204] Index information of the first RO resource group;

[0205] The association relationship between the first PUSCH configuration and the first RO resource group.

[0206] In an optional manner, the first PUSCH configuration is associated with the first preamble code group on the first RO resource group.

[0207] In an optional manner, the first category of data is small data.

[0208] Those skilled in the art should understand that the relevant description of the above-mentioned data transmission device in the embodiment of the present application can be understood by referring to the relevant description of the data transmission method in the embodiment of the present application.

[0209] Fig.11 1 is a schematic structural diagram of a communication device 1100 provided in an embodiment of the present application. The communication device may be a terminal device or a network device. Fig.11 The communication device 1100 shown includes a processor 1110, and the processor 1110 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0210] Alternatively, if Fig.11 As shown, the communication device 1100 may further include a memory 1120. The processor 1110 may call and run a computer program from the memory 1120 to implement the method in the embodiment of the present application.

[0211] The memory 1120 may be a separate device independent of the processor 1110 , or may be integrated into the processor 1110 .

[0212] Alternatively, if Fig.11 As shown, the communication device 1100 may further include a transceiver 1130, and the processor 1110 may control the transceiver 1130 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0213] The transceiver 1130 may include a transmitter and a receiver. The transceiver 1130 may further include an antenna, and the number of the antennas may be one or more.

[0214] Optionally, the communication device 1100 may specifically be a network device of an embodiment of the present application, and the communication device 1100 may implement corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0215] Optionally, the communication device 1100 may specifically be a mobile terminal / terminal device of an embodiment of the present application, and the communication device 1100 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, which will not be described again for the sake of brevity.

[0216] Fig.12 It is a schematic structural diagram of the chip of an embodiment of the present application. Fig.12 The chip 1200 shown includes a processor 1210, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0217] Alternatively, if Fig.12 As shown, the chip 1200 may further include a memory 1220. The processor 1210 may call and run a computer program from the memory 1220 to implement the method in the embodiment of the present application.

[0218] The memory 1220 may be a separate device independent of the processor 1210 , or may be integrated into the processor 1210 .

[0219] Optionally, the chip 1200 may further include an input interface 1230. The processor 1210 may control the input interface 1230 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0220] Optionally, the chip 1200 may further include an output interface 1240. The processor 1210 may control the output interface 1240 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0221] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0222] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0223] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

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

[0225] Among them, the terminal device 1310 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1320 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0226] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0227] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0228] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, 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 (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0229] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0230] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0231] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0232] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0233] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0234] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0235] The embodiment of the present application also provides a computer program.

[0236] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.

[0237] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0238] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0239] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0240] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0241] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple 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.

[0242] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0243] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0244] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A data transmission method, the method comprising: The terminal device selects a first preamble from a first preamble group, the first preamble group is associated with a first physical uplink shared channel PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration for first-type data transmission; The terminal device determines, based on the first PUSCH configuration, a first PUSCH resource corresponding to the first preamble code, and transmits the first type of data on the first PUSCH resource; The first preamble group is a preamble group used for transmitting the first type of data; The first preamble group includes at least one first-type preamble associated with each SSB in a plurality of synchronization signal blocks SSB; or The first preamble group includes at least one first type preamble associated with a random access opportunity RO; The first type of preamble code is a preamble code used for the first type of data transmission.

2. The method according to claim 1, wherein: The method further comprises: The terminal device receives first configuration information sent by the network device, where the first configuration information is used to determine at least one of the following: the first PUSCH configuration; Index information of the first preamble group; The association relationship between the first PUSCH configuration and the first preamble code group.

3. The method according to claim 1, wherein: The method further comprises: The terminal device receives a first parameter and a second parameter sent by a network device, wherein the first parameter is used to determine N SSBs actually transmitted by the network device, where N is a positive integer, and the second parameter is used to determine an association relationship between the N SSBs and the RO; wherein: The second parameter is used to indicate that M SSBs are associated with one RO, where M is an integer greater than 1 and less than or equal to N, and the first preamble code group includes at least one first-type preamble code associated with each SSB in the M SSBs.

4. The method according to claim 3, wherein: In addition to being associated with the at least one first-type preamble, each SSB is also associated with at least one of the following: at least one contention preamble; at least one non-contention preamble; At least one preamble code for requesting a system message SI.

5. The method according to claim 3 or 4, wherein: The method further comprises: The terminal device receives first indication information sent by the network device, where the first indication information is used to indicate index information of the first first-type preamble code in the at least one first-type preamble code and / or indicate the number of the at least one first-type preamble code.

6. The method according to claim 5, wherein: When the first indication information does not indicate the index information of the first first-type preamble code in the at least one first-type preamble code, the index information of the first first-type preamble code is predetermined index information.

7. The method according to claim 1, wherein: The method further comprises: The terminal device receives a first parameter and a second parameter sent by a network device, wherein the first parameter is used to determine N SSBs actually transmitted by the network device, where N is a positive integer, and the second parameter is used to determine an association relationship between the N SSBs and the RO; wherein: The second parameter is used to indicate that, when one SSB is associated with M ROs, M is an integer greater than or equal to 1, and for one RO among the M ROs, the first preamble code group includes at least one first-type preamble code associated with the RO.

8. The method according to claim 7, wherein: In addition to being associated with the at least one first-type preamble, the RO is also associated with at least one of the following: 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: The terminal device receives second indication information sent by the network device, where the second indication information is used to indicate the index information of the first first-type preamble code in the at least one first-type preamble code and / or indicate the number of the at least one first-type preamble code.

10. The method according to claim 9, wherein: When the second indication information does not indicate the index information of the first first-type preamble code in the at least one first-type preamble code, the index information of the first first-type preamble code is predetermined index information.

11. The method according to any one of claims 1, 3, 4, 6 to 8, 10, wherein: The terminal device selects a first preamble code from a first preamble code group, including: The terminal device determines the first preamble code group corresponding to the first type of data, and selects a first preamble code from the first preamble code group.

12. The method according to claim 1 or 2, wherein: The first preamble code group is a shared preamble code group used for the first type of data transmission and the second type of data transmission, wherein the size range of the first type of data is different from the size range of the second type of data.

13. The method according to claim 12, wherein: The shared preamble group is a contention preamble group A; or, The shared preamble code group is contention preamble code group B.

14. The method according to claim 13, wherein: The terminal device selects a first preamble code from a first preamble code group, including: The terminal device receives third indication information sent by the network device, where the third indication information is used to indicate at least one first-category preamble in the shared preamble group or to indicate a preamble range in the shared preamble group, where the preamble range is used to determine at least one first-category preamble; wherein the first-category preamble is a preamble used for transmitting the first-category data; The terminal device selects the first preamble code from the at least one first-type preamble code based on the third indication information.

15. The method according to claim 14, wherein: The shared preamble group includes at least one contention preamble in addition to the at least one first-category preamble; The method further comprises: The terminal device maps the at least one contention preamble in the shared preamble group to at least one PUSCH resource in a second PUSCH configuration; wherein the second PUSCH configuration is a PUSCH configuration for the second type of data transmission.

16. The method according to any one of claims 1 to 4, 6 to 8, 10, 13 to 15, wherein The terminal device determines, based on the first PUSCH configuration, a first PUSCH resource corresponding to the first preamble code, including: The terminal device maps at least one first-type preamble in the first preamble group to at least one PUSCH resource in the first PUSCH configuration; wherein a first preamble in the at least one first-type preamble is mapped to a first PUSCH resource in the at least one PUSCH resource.

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

18. A data transmission method, the method comprising: The terminal device selects a first RO resource from a first RO resource group, where the first RO resource group is an RO resource group used for first-type data transmission, the first RO resource group is associated with a first PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration used for the first-type data transmission; The terminal device determines, based on the first PUSCH configuration, a first PUSCH resource corresponding to the first RO resource, and transmits the first type of data on the first PUSCH resource; The first PUSCH configuration is associated with the first preamble group on the first RO resource group; The first preamble group includes at least one first-type preamble associated with each SSB in a plurality of synchronization signal blocks SSB; or The first preamble group includes at least one first type preamble associated with a random access opportunity RO; The first type of preamble code is a preamble code used for the first type of data transmission.

19. The method according to claim 18, wherein: The method further comprises: 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; The association relationship between the first PUSCH configuration and the first RO resource group.

20. A data transmission device, comprising: A selection unit, configured to select a first preamble from a first preamble group, wherein the first preamble group is associated 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; a transmission unit, configured to transmit the first type of data on the first PUSCH resource; The first preamble group is a preamble group used for transmitting the first type of data; in, The first preamble group includes at least one first-type preamble associated with each SSB in a plurality of SSBs; or, The first preamble group includes at least one first-type preamble associated with an RO; The first type of preamble code is a preamble code used for the first type of data transmission.

21. The device according to claim 20, wherein: The device also includes: A receiving unit, configured to receive first configuration information sent by a network device, wherein the first configuration information is used to determine at least one of the following: the first PUSCH configuration; Index information of the first preamble group; The association relationship between the first PUSCH configuration and the first preamble code group.

22. The device according to claim 20, wherein: The device also includes: A receiving unit, configured to receive a first parameter and a second parameter sent by a network device, wherein the first parameter is used to determine N SSBs actually transmitted by the network device, where N is a positive integer, and the second parameter is used to determine an association relationship between the N SSBs and the RO; wherein, The second parameter is used to indicate that M SSBs are associated with one RO, where M is an integer greater than 1 and less than or equal to N, and the first preamble code group includes at least one first-type preamble code associated with each SSB in the M SSBs.

23. The device according to claim 22, wherein: In addition to being associated with the at least one first-type preamble, each SSB is also associated with at least one of the following: at least one contention preamble; at least one non-contention preamble; At least one preamble for requesting SI.

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

25. The device according to claim 24, wherein: When the first indication information does not indicate the index information of the first first-type preamble code in the at least one first-type preamble code, the index information of the first first-type preamble code is predetermined index information.

26. The device according to claim 20, wherein: The device also includes: A receiving unit, configured to receive a first parameter and a second parameter sent by a network device, wherein the first parameter is used to determine N SSBs actually transmitted by the network device, where N is a positive integer, and the second parameter is used to determine an association relationship between the N SSBs and the RO; wherein, The second parameter is used to indicate that, when one SSB is associated with M ROs, M is an integer greater than or equal to 1, and for one RO among the M ROs, the first preamble code group includes at least one first-type preamble code associated with the RO.

27. The device according to claim 26, wherein: In addition to being associated with the at least one first-type preamble, the RO is also associated with at least one of the following: at least one contention preamble; at least one non-contention preamble; At least one preamble for requesting SI.

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

29. The device according to claim 28, wherein When the second indication information does not indicate the index information of the first first-type preamble code in the at least one first-type preamble code, the index information of the first first-type preamble code is predetermined index information.

30. The device according to any one of claims 20, 22, 23, 25 to 27, 29, wherein: The selection unit is configured to determine the first preamble code group corresponding to the first category of data, and select a first preamble code from the first preamble code group.

31. The device according to claim 20 or 21, wherein: The first preamble code group is a shared preamble code group used for the first type of data transmission and the second type of data transmission, wherein the size range of the first type of data is different from the size range of the second type of data.

32. The device according to claim 31, wherein The shared preamble group is a contention preamble group A; or, The shared preamble code group is contention preamble code group B.

33. The device according to claim 32, wherein: The device also includes: a receiving unit, configured to receive third indication information sent by a network device, wherein the third indication information is used to indicate at least one first-category preamble in the shared preamble group or to indicate a preamble range in the shared preamble group, the preamble range being used to determine at least one first-category preamble; wherein the first-category preamble is a preamble used for transmission of the first-category data; The selection unit is configured to select the first preamble code from the at least one first-type preamble code based on the third indication information.

34. The device according to claim 33, wherein: The shared preamble group includes at least one contention preamble in addition to the at least one first-category preamble; The device also includes: a mapping unit, configured to map the at least one contention preamble in the shared preamble group to at least one PUSCH resource in a second PUSCH configuration; wherein the second PUSCH configuration is a PUSCH configuration for the second type of data transmission.

35. The device according to any one of claims 20 to 23, 25 to 27, 29, 32 to 34, wherein: The device also includes: a mapping unit, configured to map at least one first-type preamble in the first preamble group to at least one PUSCH resource in the first PUSCH configuration; wherein a first preamble in the at least one first-type preamble is mapped to a first PUSCH resource in the at least one PUSCH resource.

36. The device according to any one 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 device, the device comprising: A selection unit, configured to select a first RO resource from a first RO resource group, wherein the first RO resource group is an RO resource group used for first-type data transmission, the first RO resource group is associated with a first PUSCH configuration, and the first PUSCH configuration is a PUSCH configuration used for the first-type data transmission; a determining unit, configured to determine, based on the first PUSCH configuration, a first PUSCH resource corresponding to the first RO resource; a transmission unit, configured to transmit the first type of data on the first PUSCH resource; The first PUSCH configuration is associated with the first preamble group on the first RO resource group; The first preamble group includes at least one first-type preamble associated with each SSB in a plurality of synchronization signal blocks SSB; or The first preamble group includes at least one first type preamble associated with a random access opportunity RO; The first type of preamble code is a preamble code used for the first type of data transmission.

38. The device according to claim 37, wherein The device also includes: A receiving unit, configured to receive second configuration information sent by a network device, wherein 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; The association relationship between the first PUSCH configuration and the first RO resource group.

39. A terminal device, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 1 to 19.

40. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 19.

41. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 19.

Images