Data transmission method and system

By determining the mapping relationship of uplink data transmission resources in the terminal device, the resource determination problem when the uplink data transmission resource dimension is enhanced is solved, and the resource capacity is improved under OCC multiplexing.

CN121508754APending Publication Date: 2026-02-10SPREADTRUM SEMICON (NANJING) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411077571.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-07
Publication Date
2026-02-10

AI Technical Summary

Technical Problem

With the expansion of uplink data transmission resources, how terminal devices determine which uplink data transmission resources to use for uplink data transmission is a problem that needs to be solved.

Method used

The uplink data transmission resources are determined by mapping relationships, including the mapping relationships between Physical Random Access Channel (PRACH) resources and/or Physical Uplink Shared Channel (PUSCH) resources. Specifically, this includes the mapping between PRACH resources and Synchronization Signal-Physical Broadcast Channel Block (SSB), the mapping between PUSCH resources and SSB, and the mapping between PRACH resources and PUSCH resources.

Benefits of technology

With the introduction of OCC multiplexing, the transmission capacity of PUSCH and/or PRACH resources is increased, enabling effective determination of uplink data transmission resources in various situations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121508754A_ABST
    Figure CN121508754A_ABST
Patent Text Reader

Abstract

Provided in an embodiment of the present application are a data transmission method and system, relating to the technical field of communications, the method comprising: determining an uplink data transmission resource according to a mapping relationship, the uplink data transmission resource comprising a physical random access channel (PRACH) resource and / or a physical uplink shared channel (PUSCH) resource; sending uplink data based on the uplink data transmission resource; wherein the mapping relationship comprises at least one of the following: a mapping relationship between the PRACH resource and a synchronization signal-physical broadcast channel block (SSB); the mapping relation between the PUSCH resource and the SSB is determined; the mapping relation between the PRACH resource and the PUSCH resource is determined. According to the method and the device, the uplink data transmission resource for transmitting the uplink data can be determined under the condition that the transmission capacity of the PUSCH resource and / or the PRACH resource can be improved by introducing OCC multiplexing.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a data transmission method and system. Background Technology

[0002] As communication technologies continue to evolve, various communication scenarios are placing increasingly higher demands on the capacity of communication systems, especially on random access capacity and uplink data transmission capacity. Generally speaking, the most direct way to enhance system capacity is to expand the dimensions of uplink data transmission resource utilization.

[0003] With the expansion of uplink data transmission resources, how terminal devices determine which uplink data transmission resources to use for uplink data transmission is a problem that needs to be solved. Summary of the Invention

[0004] This application provides a data transmission method and system in several aspects, which can effectively determine uplink data transmission resources when the dimensions of uplink data transmission resources are expanded and enhanced.

[0005] In a first aspect, embodiments of this application provide a data transmission method, the method comprising: determining uplink data transmission resources according to a mapping relationship, the uplink data transmission resources including physical random access channel (PRACH) resources and / or physical uplink shared channel (PUSCH) resources; and transmitting uplink data based on the uplink data transmission resources;

[0006] The mapping relationship includes at least one of the following:

[0007] Mapping relationship between PRACH resources and Synchronization Signal-Physical Broadcast Channel Block (SSB);

[0008] Mapping relationship between PUSCH resources and SSB;

[0009] Mapping relationship between PRACH and PUSCH resources.

[0010] In some implementations, the uplink data is a first random access request message sent based on PRACH resources. The mapping relationship includes the mapping relationship between PRACH resources and SSBs, wherein: PRACH resources include random access channel timing (RO), random access preamble, and orthogonal code.

[0011] In some implementations, the mapping relationship between PRACH resources and SSBs is determined based on the mapping rate between SSBs and ROs, the SSB index order, and the PRACH resource mapping order. The mapping rate between SSBs and ROs represents the number of SSBs corresponding to one RO.

[0012] In some implementations, the uplink data is a second random access request message sent based on PRACH and PUSCH resources, and the mapping relationship includes the mapping relationship between PRACH resources and PUSCH resources, wherein:

[0013] PRACH resources include random access channel timing (RO), random access preamble, and orthogonal codes; and / or PUSCH resources include physical uplink shared channel timing (PO), demodulation reference signal (DMRS) resources, and orthogonal codes.

[0014] In some implementations, the mapping relationship between PRACH resources and PUSCH resources is determined based on the mapping rate between PRACH resources and PUSCH resources, the mapping order of PRACH resources, and the mapping order of PUSCH resources. The mapping rate between PRACH resources and PUSCH resources represents the number of PRACH resources corresponding to one PUSCH resource.

[0015] In some implementations, the mapping rate between PRACH resources and PUSCH resources is determined based on at least one of the following parameters:

[0016] The number of random access preambles, P;

[0017] The number of valid ROs (Representative Roots) R within the associated pattern period;

[0018] The number of DMRS resources S corresponding to the Physical Uplink Shared Channel Opportunity PO;

[0019] The number K of valid POs within the associated pattern period;

[0020] The length C of the orthogonal code included in the PRACH resource;

[0021] The PUSCH resource includes the length X of the orthogonal code.

[0022] In some implementations, the PRACH resource mapping order is as follows:

[0023] Within a single RO, sorted in ascending order by orthogonal key index;

[0024] Within a RO, sorted in ascending order by the index of the random access preamble;

[0025] In multiple frequency domain reused ROs, sort them in ascending order of the RO frequency domain resource index;

[0026] Multiple ROs that are time-domain multiplexed within a PRACH time slot are ordered in ascending order of the RO time-domain resource index;

[0027] Sort by PRACH slot number in ascending order.

[0028] In some implementations, the PRACH resource mapping order is as follows:

[0029] Within a RO, sorted in ascending order by the index of the random access preamble;

[0030] Within a single RO, sorted in ascending order by orthogonal key index;

[0031] In multiple frequency domain reused ROs, sort them in ascending order of the RO frequency domain resource index;

[0032] Multiple ROs that are time-domain multiplexed within a PRACH time slot are ordered in ascending order by the RO time-domain resource index.

[0033] Sort by PRACH slot number in ascending order.

[0034] In some implementations, the PRACH resource mapping order is as follows:

[0035] Within a RO, sorted in ascending order by the index of the random access preamble;

[0036] In multiple frequency domain reused ROs, sort them in ascending order by the RO frequency domain resource index;

[0037] Multiple ROs that are time-domain multiplexed within a PRACH time slot are ordered in ascending order by the RO time-domain resource index.

[0038] Sort by orthogonal key index in ascending order;

[0039] Sort by PRACH slot number in ascending order.

[0040] In some implementations, the PRACH resource mapping order is as follows:

[0041] Within a RO, sorted in ascending order by the index of the random access preamble;

[0042] In multiple frequency domain reused ROs, sort them in ascending order by the RO frequency domain resource index;

[0043] Multiple ROs that are time-domain multiplexed within a PRACH time slot are ordered in ascending order by the RO time-domain resource index.

[0044] Arranged in ascending order by PRACH slot number;

[0045] Sort by orthogonal key index in ascending order.

[0046] In some implementations, the mapping order of PUSCH resources is as follows:

[0047] In a PO, sorted in ascending order by the DMRS resource index, where the DMRS resource index is determined based on the DMRS port index, the DMRS sequence index, and the orthogonal code index;

[0048] At least one PO at the same time domain location is ordered from low to high frequency domain location;

[0049] At least one PO that is time-domain multiplexed within a time slot is sorted in ascending order by the PO time-domain resource index;

[0050] Sort by PUSCH slot number in ascending order.

[0051] In some implementations, a PO is ordered in ascending order by the DMRS resource index, including the following:

[0052] Sort in ascending order by DMRS port index, then by DMRS sequence index, and finally by orthogonal code index.

[0053] Sort in ascending order by DMRS sequence index, then by DMRS port index, and finally by orthogonal code index.

[0054] Sort in ascending order by orthogonal code index, then by DMRS sequence index, and finally by DMRS port index.

[0055] Sort in ascending order by orthogonal code index, then by DMRS port index, and finally by DMRS sequence index.

[0056] Sort in ascending order by DMRS port index, then by orthogonal code index, and finally by DMRS sequence index.

[0057] Sort in ascending order by DMRS sequence index, then by orthogonal code index, and finally by DMRS port index.

[0058] In some implementations, the mapping order of PUSCH resources is as follows:

[0059] Sort by orthogonal key index in ascending order;

[0060] At least one PO at the same time domain location is ordered from low to high frequency domain location;

[0061] Within a PO, sorted in ascending order by the DMRS resource index, where the DMRS resource index is determined based on the DMRS port index and the DMRS sequence index;

[0062] At least one PO at the same time domain location is ordered from low to high frequency domain location;

[0063] At least one PO that is time-domain multiplexed within a time slot is sorted in ascending order by the PO time-domain resource index;

[0064] Sort by PUSCH slot number in ascending order.

[0065] In some implementations, the mapping order of PUSCH resources is as follows:

[0066] At least one PO at the same time domain location is ordered from low to high frequency domain location;

[0067] Within a PO, sorted in ascending order by the DMRS resource index, where the DMRS resource index is determined based on the DMRS port index and the DMRS sequence index;

[0068] Sort by orthogonal key index in ascending order;

[0069] At least one PO at the same time domain location is ordered from low to high frequency domain location;

[0070] At least one PO that is time-domain multiplexed within a time slot is sorted in ascending order by the PO time-domain resource index;

[0071] Sort by PUSCH slot number in ascending order.

[0072] In some implementations, the mapping order of PUSCH resources is as follows:

[0073] At least one PO at the same time domain location is ordered from low to high frequency domain location;

[0074] Within a PO, sorted in ascending order by the DMRS resource index, where the DMRS resource index is determined based on the DMRS port index and the DMRS sequence index;

[0075] In the same time slot, POs are ordered in ascending order according to multiple time-domain multiplexing;

[0076] Sort by orthogonal key index in ascending order;

[0077] Sort by PUSCH slot number in ascending order.

[0078] In some implementations, the mapping order of PUSCH resources is as follows:

[0079] At least one PO at the same time domain location is ordered from low to high frequency domain location;

[0080] Within a PO, sorted in ascending order by the DMRS resource index, where the DMRS resource index is determined based on the DMRS port index and the DMRS sequence index;

[0081] At least one PO at the same time domain location is ordered from low to high frequency domain location;

[0082] At least one PO that is time-domain multiplexed within a time slot is sorted in ascending order by the PO time-domain resource index;

[0083] Sort by PUSCH slot number in ascending order;

[0084] Sort by orthogonal key index in ascending order.

[0085] In some implementations, uplink data is data sent by the terminal device in a disconnected state based on pre-configured PUSCH resources. The mapping relationship includes the mapping relationship between PUSCH resources and SSBs. The mapping relationship between PUSCH resources and SSBs is determined according to the mapping rate between SSBs and PUSCH resources, the SSB index order, and the mapping order of PUSCH resources. The mapping rate between SSBs and PUSCH resources represents the number of SSBs corresponding to one PUSCH resource.

[0086] In some implementations, the PUSCH resource mapping order is as follows:

[0087] Within a PO, sorted in ascending order by the DMRS resource index;

[0088] In the time domain, indexes are sorted in ascending order according to the PUSCH resource configuration cycle.

[0089] Sort by orthogonal key index in ascending order.

[0090] In some implementations, the PUSCH resource mapping order is as follows:

[0091] Within a PO, sorted in ascending order by the DMRS resource index;

[0092] Sort by orthogonal key index in ascending order;

[0093] In the time domain, the periodic index is configured in ascending order according to PUSCH.

[0094] In some implementations, within a PO, sorted in ascending order by the DMRS resource index, including the following:

[0095] Sort by DMRS port index in ascending order, then by DMRS sequence index in ascending order;

[0096] Sort in ascending order by DMRS sequence index and then by DMRS port index.

[0097] In some implementations, the PUSCH resource mapping order is as follows:

[0098] In the time domain, the periodic index is configured in ascending order according to the PUSCH configuration.

[0099] Within a PO, sorted in ascending order by the DMRS resource index, where the DMRS resource index is determined based on the DMRS port index, DMRS sequence index, and orthogonal code index.

[0100] In some implementations, the PUSCH resource mapping order is as follows:

[0101] Within a PO, sorted in ascending order by the DMRS resource index, where the DMRS resource index is determined based on the DMRS port index, DMRS sequence index, and orthogonal code index;

[0102] In the time domain, the periodic index is configured in ascending order according to PUSCH.

[0103] In some implementations, within a PO, sorted in ascending order by the DMRS resource index, including the following:

[0104] Sort in ascending order by DMRS port index, then by DMRS sequence index, and finally by orthogonal code index.

[0105] Sort in ascending order by DMRS sequence index, then by DMRS port index, and finally by orthogonal code index.

[0106] Sort in ascending order by orthogonal code index, then by DMRS sequence index, and finally by DMRS port index.

[0107] Sort in ascending order by orthogonal code index, then by DMRS port index, and finally by DMRS sequence index.

[0108] Sort in ascending order by DMRS port index, then by orthogonal code index, and finally by DMRS sequence index.

[0109] Sort in ascending order by DMRS sequence index, then by orthogonal code index, and finally by DMRS port index.

[0110] Secondly, embodiments of this application provide a data transmission method, which includes:

[0111] Receive uplink data transmitted based on uplink data transmission resources, which include: physical random access channel (PRACH) resources and / or physical uplink shared channel (PUSCH) resources;

[0112] Uplink data transmission resources are determined based on mapping relationships, which include at least one of the following:

[0113] Mapping relationship between PRACH resources and Synchronization Signal-Physical Broadcast Channel Block (SSB);

[0114] Mapping relationship between PUSCH resources and SSB;

[0115] Mapping relationship between PRACH and PUSCH resources.

[0116] Thirdly, embodiments of this application provide a data transmission system, including a terminal device and at least one network device;

[0117] The terminal device is used to: determine uplink data transmission resources based on the mapping relationship; and send uplink data based on the uplink data transmission resources.

[0118] Network devices are used to: receive uplink data;

[0119] The uplink data transmission resources include physical random access channel (PRACH) resources and / or physical uplink shared channel (PUSCH) resources.

[0120] The mapping relationship includes at least one of the following:

[0121] Mapping relationship between PRACH resources and Synchronization Signal-Physical Broadcast Channel Block (SSB);

[0122] Mapping relationship between PUSCH resources and SSB;

[0123] Mapping relationship between PRACH and PUSCH resources.

[0124] Fourthly, embodiments of this application provide a data transmission apparatus, including: a processor, a memory, and a communication interface;

[0125] The aforementioned memory is used to store programs or instructions.

[0126] The aforementioned communication interface is used to receive signals from other data transmission devices and transmit them to the processor, or to send signals from the processor to other data transmission devices;

[0127] The processor described above is used to execute the program or instructions described above so that the data transmission device implements the data transmission method provided by either the first aspect or the second aspect.

[0128] Fifthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the data transmission method provided in either the first or second aspect.

[0129] In a sixth aspect, embodiments of this application provide a computer program product, including a computer program that, when run, causes a computer to perform a data transmission method as provided in either the first aspect or the second aspect.

[0130] The data transmission method and system provided in this application determine uplink data transmission resources based on mapping relationships. These uplink data transmission resources include Physical Random Access Channel (PRACH) resources and / or Physical Uplink Shared Channel (PUSCH) resources. Uplink data is transmitted based on these uplink data transmission resources. The mapping relationships include at least one of the following: a mapping relationship between PRACH resources and Synchronization Signal-Physical Broadcast Channel Block (SSB); a mapping relationship between PUSCH resources and SSB; and a mapping relationship between PRACH resources and PUSCH resources. This application can determine uplink data transmission resources for transmitting uplink data when introducing OCC multiplexing can improve the transmission capacity of PUSCH resources and / or PRACH resources. Attached Figure Description

[0131] Figure 1 This is a flowchart illustrating a four-step random access procedure provided in an embodiment of this application.

[0132] Figure 2 This is a schematic diagram of the RO and SSB mapping relationship within a PRACH cycle provided in an embodiment of this application. Figure 1 ;

[0133] Figure 3 This is a schematic diagram of the RO and SSB mapping relationship within a PRACH cycle provided in an embodiment of this application. Figure 2 ;

[0134] Figure 4 This is a flowchart illustrating a two-step random access procedure provided in an embodiment of this application.

[0135] Figure 5 This is a schematic diagram of a PUSCH time slot provided in an embodiment of this application;

[0136] Figure 6 This is a schematic diagram showing the arrangement of POs in the time and frequency domains in a PUSCH slot according to an embodiment of this application.

[0137] Figure 7 This is a schematic diagram of the structure of a PO provided in an embodiment of this application;

[0138] Figure 8 This is a schematic diagram of a DMRS resource mapped to a PO provided in an embodiment of this application;

[0139] Figure 9 This is a schematic diagram of the architecture of a data transmission system provided in the embodiments of this application;

[0140] Figure 10 A flowchart illustrating the steps of a data transmission method provided in this application embodiment. Figure 1 ;

[0141] Figure 11 This is a schematic diagram showing the arrangement of ROs in the time and frequency domains in a PRACH slot according to an embodiment of this application;

[0142] Figure 12 This is a flowchart illustrating the steps of a data transmission method provided in an embodiment of this application. Figure 2 ;

[0143] Figure 13 This is a schematic diagram of the hardware structure of a data transmission device provided in an embodiment of this application. Detailed Implementation

[0144] In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0145] In the embodiments of this application, terms such as "first" and "second" are used to distinguish identical or similar items with essentially the same function and effect. For example, "first instruction information" and "second instruction information" are used only to distinguish different instruction information and do not limit their order. Those skilled in the art will understand that terms such as "first" and "second" do not limit the quantity or execution order, and that terms such as "first" and "second" do not necessarily imply that they are different.

[0146] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, a--c, bc, or abc, where a, b, and c can be single or multiple.

[0147] The following is a brief introduction to some of the terms and technologies involved in the embodiments of this application:

[0148] 1. PRACH (Physical Random Access): Physical random access channel, a physical channel used to carry random access request messages.

[0149] 2. PUSCH (Physical Uplink Shared Channel): A physical channel used to carry uplink data.

[0150] 3. SSB (Synchronization Signal-PBCH): The Synchronization Signal-Physical Broadcast Channel Block consists of three parts: Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), and Physical Broadcast Channel (PBCH).

[0151] 4. Terminal equipment:

[0152] The terminal devices in this application embodiment may include handheld devices, vehicle-mounted devices, etc., that have wireless communication capabilities. For example, some terminal devices include: mobile phones, tablets, PDAs, laptops, mobile internet devices (MIDs), wearable devices, VR devices, AR devices, wireless terminal devices in industrial control, wireless terminal devices in self-driving, wireless terminal devices in remote medical surgery, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, wireless terminal devices in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in future evolved public land mobile networks (PLMNs), etc., and the embodiments of this application are not limited to these.

[0153] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0154] The terminal equipment in this application embodiment can also be referred to as: user equipment (UE), mobile station (MS), mobile terminal equipment (MT), access terminal equipment, user unit, user station, mobile station, mobile station, remote station, remote terminal equipment, mobile device, user terminal equipment, terminal equipment, wireless communication equipment, user agent, or user device, etc.

[0155] In this embodiment of the application, the device for implementing the function of the terminal device can be the terminal device itself; or it can be a device that enables the terminal device to implement the function, such as a chip system, which can be installed in the terminal device.

[0156] 5. Network equipment

[0157] The network device in this application embodiment can refer to a public mobile communication network device, which is an interface device for terminal devices to access the Internet. It is also a form of radio station, which refers to a radio transceiver station that transmits information with terminal devices in a certain radio coverage area. It includes a base station (BS), which can also be called a base station device. It is a device deployed in a radio access network (RAN) to provide wireless communication functions. For example, in 2G networks, devices providing base station functionality include base transceiver stations (BTS); in 3G networks, devices providing base station functionality include NodeBs; in 4G networks, devices providing base station functionality include evolved NodeBs (eNBs); in wireless local area networks (WLANs), devices providing base station functionality are access points (APs); in 5G NR, devices providing base station functionality include gNBs and further evolved NodeBs (ng-eNBs). The gNB communicates with terminal devices using NR technology, while the ng-eNB communicates with terminal devices using evolved universal terrestrial radio access (E-UTRA) technology. Both gNBs and ng-eNBs can connect to the 5G core network. The network device 103 in this embodiment also includes devices providing base station functionality in future new data transmission systems.

[0158] In this embodiment of the application, the means for implementing the function of the network device can be the network device itself, or it can be a means that enables the network device to implement the function, such as a chip system, which can be installed in the network device.

[0159] Reference Figure 1 The diagram illustrates a four-step random access process, which includes the following steps:

[0160] S101. The terminal device reads the MIB (Master information block) and SIB (system information block).

[0161] Specifically, the terminal equipment (UE) first completes downlink synchronization by receiving the SSB, and then determines the PRACH resource configuration information by reading the SIB.

[0162] Specifically, the terminal device can obtain the time-frequency resource configuration parameters of the RO through the SIB, including the RO period, the number of ROs in the time domain within one PRACH period, the number of ROs multiplexed in the frequency domain, and the number of SSBs associated with each RO. For example, refer to... Figure 2 This illustrates a mapping relationship between RO and SSB in the frequency and time domains. Figure 2 In one PRACH cycle, the number of ROs in the time domain is 12 (RO1 to RO12), and the total number of SSBs is 16 (SSB1 to SSB12). There are two frequency domain ROs in the same time domain, and each RO corresponds to two SSBs. Therefore, only RO1 to RO8 have corresponding SSBs. (Refer to...) Figure 3 This illustrates another mapping relationship between RO and SSB in the frequency and time domains. Figure 3 In a PRACH cycle, there are 6 ROs in the time domain (PRACH cycle 1 includes RO1 to RO6, and PRACH cycle 2 includes RO7 to RO12), and the total number of SSBs is 4 (SSB1 to SSB4). There are two ROs in the frequency domain in the same time domain, and each RO corresponds to half of the SSBs. Therefore, only RO1 to RO8 have corresponding SSBs.

[0163] S102, The terminal device sends Msg1 (message 1).

[0164] Msg1 carries a preamble, which indicates the terminal device's intention to access the network device.

[0165] S103, The terminal device receives Msg2 (message 2).

[0166] If the network device successfully receives Msg1, it sends Msg2 scrambled with RA-RNT1 to the network device. Msg2 is a random access response message. Msg2 carries TA (Timing Advance), power correction, RA-RNT1 (Radio Access - Radio Network Temporary Identity), and resource indication Mgs3 (message 3) sent by the terminal device.

[0167] After sending Msg1, the terminal device can use RA-RNT1 to monitor Msg2 from the network device and descramble Msg2.

[0168] Furthermore, RA-RNTI is calculated using the time and frequency resources of RO (Random Access Channel occasion).

[0169] S104, The terminal device sends Msg3 (message 3).

[0170] Msg3 carries an RRC (Radio Resource Control) connection request and the identity information of the terminal device.

[0171] Specifically, the terminal device sends Msg3 to the forgotten device via the uplink scheduling instruction in Msg2.

[0172] S105, The terminal device receives Msg4 (message 4).

[0173] In this process, network devices can notify terminal devices of the completion of the initial access process via Msg4; otherwise, the terminal devices can determine that the initial access process has failed.

[0174] Furthermore, for initial access to NTN (Non-Terrestrial Network), high round-trip time (RTT) and propagation delay differences are the main factors to consider in uplink initial access. For example, the round-trip time of geostationary satellites is as high as 600ms, and the propagation delay difference of geostationary satellites is as high as 16ms.

[0175] Reference Figure 4 The diagram illustrates a two-step random access process, which includes the following steps:

[0176] S401, the terminal device sends MsgA (message A).

[0177] MsgA includes Msg1 and Msg3 in the four-step random access process. For details on Msg1 and Msg3, please refer to [link to relevant documentation]. Figure 1 The information about Msg1 and Msg3 will not be repeated here.

[0178] S402, the terminal device receives MsgB (message B).

[0179] MsgB includes Msg2 and Msg4 from the four-step random access procedure. For details on Msg2 and Msg4, please refer to [link to relevant documentation]. Figure 1 The information about Msg1 and Msg3 will not be repeated here.

[0180] It is understandable that when a network device successfully detects MsgA sent by a terminal device, it will carry the successful random access response corresponding to the terminal device through MsgB. The successful random access response will instruct the terminal device to use the uplink control channel (PUCCH) resources (including uplink control channel time and frequency domain resources) for sending the HARQ-ACK (Hybrid automatic repeat request acknowledgement) feedback corresponding to MsgB.

[0181] exist Figure 4 In MsgA, the RO resources for PRACH transmissions are configured by the network. Furthermore, the determination of the mapping relationship between SSB and RO is related to... Figure 1 The method for determining the mapping relationship between SSB and RO in the four-step random access process shown is consistent and can be referred to. Figure 2 and Figure 3 The message content carried by PUSCH in MsgA corresponds to... Figure 1The diagram shows Msg3 of the four-step random access procedure. For PUSCH resources in MsgA, the network device configures the PUSCH resources via higher-layer signaling. In the time domain, this includes: the PUSCH resource period, the time offset between a PRACH slot and its associated PUSCH resource start slot, the number of PUSCH slots associated with a PRACH slot, the number of PUSCH Occasions (POs) multiplexed in each PUSCH resource transmission slot, and the symbol positions occupied by each PO. In the frequency domain, this includes: the starting RB (Resource Block) index of the first PO in the frequency domain, the size of the PO in the frequency domain (i.e., the number of RBs it occupies), and the number of POs in the frequency domain. Furthermore, the same PO can be multiplexed by multiple users through DMRS (Demodulation Reference Signal) resources, which include DMRS sequences or DMRS ports. Different terminal devices can select the same PO (Program Point) but different DMRS ports or DMRS sequences for data transmission. The same PO can be associated with different DMRS resources, forming different Uplink Shared Channel Resource Units (PRUs). For PO configuration, please refer to [link / reference]. Figures 5 to 8 ,exist Figure 5 In this context, one PRACH slot is associated with p PUSCH slots. The time offset between a PRACH slot and PUSCH slot 1 is two slots. The frequency domain starting points of the p PUSCH slots are the same. Figure 6 In this context, it indicates that the number of time-domain multiplexed POs in each PUSCH slot is 2, and the number of frequency-domain multiplexed POs in each PUSCH slot is also 2. Therefore, each PUSCH slot includes 4 POs. Figure 7 In this context, each PO includes a PUSCH, GP (Guarding Spacing), and GB (Guarding Band). Each PO has multiple associated DMRS resources, for example, in... Figure 8 In the PO, DMRS resource indexes 0 to 3 are associated. DMRS resource index 0 corresponds to DMRS port 0 and DMRS sequence 0, DMRS resource index 1 corresponds to DMRS port 1 and DMRS sequence 0, DMRS resource index 2 corresponds to DMRS port 0 and DMRS sequence 1, and DMRS resource index 3 corresponds to DMRS port 1 and DMRS sequence 1.

[0182] Furthermore, a mapping relationship exists between preambles and PRUs. This mapping relationship is determined based on the mapping rate between preambles and PRUs, the preamble index, and the DMRS resource indexes contained in the PRU. The mapping rate between preambles and PRUs represents the number of preambles corresponding to one PRU. It is further determined using the following expression: L1 = ceil(P × R / S × K), where L1 represents the mapping rate between preambles and PRUs, R represents the number of all valid ROs within a single associated pattern period, P represents the number of preambles for each valid RO, K represents the number of valid POs within the associated pattern period, and S represents the number of DMRS resource indexes corresponding to each valid PO. Typically, one or more preambles will be mapped to one PRU, meaning the mapping rate between preambles and POs is greater than or equal to 1.

[0183] The above describes the mapping relationship between preamble and PRU in the prior art.

[0184] With the further evolution of communication technology, various communication scenarios are placing increasingly higher demands on the system capacity of the network side, especially for enhanced random access capacity. Generally speaking, the most direct way to enhance system capacity is to expand the dimensions of uplink data transmission resource utilization. For example, based on time-domain and frequency-domain multiplexing, code-domain multiplexing can be further applied. That is, code-domain multiplexing can enable multiple terminal devices to transmit data on the same time-frequency resources, with each terminal device allocated one or more OCCs during data transmission. There are currently three schemes for orthogonal code multiplexing: 1) OCC multiplexing in the frequency domain; 2) OCC multiplexing in the time domain; and 3) OCC multiplexing between time slots.

[0185] Among them, when using OCC extension to implement code division multiplexing of uplink data transmission resources, how the terminal device determines the uplink data transmission resources is a problem that needs to be solved.

[0186] To address the aforementioned technical problems, this application provides a data transmission method that determines uplink data transmission resources based on mapping relationships and transmits uplink data based on these resources. The mapping relationships include at least one of the following: a mapping relationship between PRACH resources and Synchronization Signal-Physical Broadcast Channel Block (SSB); a mapping relationship between PUSCH resources and SSBs; and a mapping relationship between PRACH resources and PUSCH resources. This application can determine uplink data transmission resources for transmitting uplink data when introducing OCC multiplexing can improve the transmission capacity of PUSCH resources and / or PRACH resources.

[0187] The technical solutions provided in this application will be described in detail below through specific embodiments. It should be noted that the following embodiments may exist independently or in combination with each other, and the same or similar content will not be described again in different embodiments.

[0188] Reference Figure 9 , Figure 9 This is a schematic diagram of the architecture of a data transmission system provided in an embodiment of this application. Figure 9 As shown, the data transmission system includes a terminal device 901 and a network device 902, and the terminal device 901 and the network device 902 communicate wirelessly via the network.

[0189] In this embodiment, the wireless communication between terminal device 901 and network device 902 can also be simply referred to as "communication," and the term "communication" can also be described as "data transmission," "information transmission," or "transmission." Those skilled in the art can use the technical solutions provided in this embodiment for wireless communication between network devices and terminal devices, such as wireless communication between access network devices and terminal devices, or wireless communication between core network devices and terminal devices, etc., and this embodiment does not impose any limitations.

[0190] Optionally, the sensing node described in the following embodiments of this application may refer to the terminal device 901 mentioned above, or it may refer to one or more chips or modules inside the terminal device 901 that are specifically used to sense environmental parameters or specific information.

[0191] Reference Figure 10 , Figure 10 This is a flowchart illustrating the steps of a data transmission method provided in an embodiment of this application. Figure 1 In some embodiments of this application, the entity executing the above-described data transmission method can be a terminal device or a device capable of supporting the terminal device in implementing related functions, such as a chip system, which can be installed in a network device. The above-described data transmission method includes:

[0192] S1001. Determine the uplink data transmission resources based on the mapping relationship.

[0193] Uplink data transmission resources include PRACH resources and / or PUSCH resources.

[0194] S1002, Send uplink data based on uplink data transmission resources.

[0195] The mapping relationship includes at least one of the following:

[0196] Mapping relationship between PRACH resources and Synchronization Signal-Physical Broadcast Channel Block (SSB);

[0197] Mapping relationship between PUSCH resources and SSB;

[0198] Mapping relationship between PRACH and PUSCH resources.

[0199] In this application embodiment, the mapping relationship is determined according to a preset or specified mapping rule in the protocol. This application enables the terminal device to determine uplink data transmission resources when it needs to send uplink data in various situations.

[0200] In one implementation, the uplink data is a first random access request message sent based on PRACH resources. The mapping relationship includes the mapping relationship between PRACH resources and SSBs. The PRACH resources include random access channel timing (RO), random access preamble, and orthogonal code. That is, a PRACH resource is uniquely determined by RO, preamble, and orthogonal code.

[0201] In this embodiment, when the PRACH resource includes orthogonal codes, this application can determine the uplink data transmission resources for transmitting uplink data based on the mapping relationship between the PRACH resource and the Synchronization Signal-Physical Broadcast Channel Block (SSB) or the mapping relationship between the PRACH resource and the PUSCH resource, thus improving the transmission capacity of the PRACH resource by introducing OCC multiplexing. Here, "PRACH resource including orthogonal codes" means that the terminal device needs to extend the PRACH resource using OCC when transmitting based on the PRACH resource.

[0202] The mapping relationship between PRACH resources and SSBs is determined based on the mapping rate between SSBs and ROs, the SSB index order, and the PRACH resource mapping order. The mapping rate between SSBs and ROs represents the number of SSBs corresponding to one RO.

[0203] In the embodiments of this application, it is possible to enhance the system capacity during a 4-step random access process or a 2-step random access process, and when the PRACH resource includes OCC, it is possible to determine the PRACH resource for sending uplink data.

[0204] Reference Figure 1 The mapping relationship between PRACH resources and SSBs can be applied to... Figure 1 The four-step random access process shown is as follows: Figure 4 In the two-step random access process, the first random access request message can be... Figure 1 Msg1 in the text may be Figure 4 MsgA in the middle.

[0205] Specifically, when the first random access request message needs to be sent, the terminal device determines the target SSB with better signal quality / strength from multiple SSBs based on SSB measurements. When initiating random access, the terminal device selects the PRACH resource corresponding to the target SSB according to the mapping relationship to send the first random access request message. The PRACH resource includes RO, Preamble, and Orthogonal Code. Since PRACH transmission uses OCC for code division multiplexing, the terminal device needs to apply an OCC to extend the random access request message when sending it. The terminal device sends random access request messages using the same RO and preamble by applying different OCCs. The network side can distinguish random access request messages sent by different UEs using the OCC code. When sending the first random access request message, the terminal device needs to select the OCC. Therefore, the mapping of SSBs and PRACH resources needs to consider the RO, preamble, and OCC included in the PRACH resource. Specifically, the mapping order of PRACH resources is adopted in the 4-step random access process and the 2-step random access process.

[0206] In some implementations, based on the mapping relationship between PRACH resources and PUSCH resources, the uplink data is a second random access request message sent based on PRACH resources and PUSCH resources, wherein: the PRACH resources include random access channel timing RO, random access preamble, and orthogonal code; and / or the PUSCH resources include physical uplink shared channel timing PO, demodulation reference signal DMRS resources, and orthogonal code.

[0207] In this embodiment, when both PRACH and PUSCH resources include orthogonal codes, this application can determine the uplink data transmission resources for transmitting uplink data based on the mapping relationship between PRACH and PUSCH resources. This is possible while introducing OCC multiplexing can improve the transmission capacity of PUSCH and PRACH resources. Here, "PUSCH resources including orthogonal codes" means that the terminal device needs to extend the PUSCH resources using OCC when transmitting based on PUSCH resources.

[0208] Specifically, the mapping relationship between PRACH resources and PUSCH resources is applied to Figure 4 The two-step random access procedure shown includes MsgA, which includes PRACH and PUSCH. After determining the PRACH resource, the terminal device determines the PUSCH resource that is mapped to the PRACH resource according to the mapping relationship between the PRACH resource and the PUSCH resource, and sends the second random access request message using the PRACH resource and the PUSCH resource.

[0209] Furthermore, the mapping relationship between PRACH resources and PUSCH resources is determined based on the mapping rate between PRACH resources and PUSCH resources, the mapping order of PRACH resources, and the mapping order of PUSCH resources. The mapping rate between PRACH resources and PUSCH resources represents the number of PRACH resources corresponding to one PUSCH resource.

[0210] The mapping rate can be understood as the number of PRACH resources corresponding to one PUSCH resource. For example, if one PUSCH resource corresponds to one PRACH resource, the mapping rate is 1; if one PUSCH resource corresponds to two PRACH resources, the mapping rate is 2.

[0211] Furthermore, the mapping rate is determined based on at least one of the following parameters:

[0212] The number of random access preambles, P;

[0213] The number of valid ROs (Representative Roots) R within the associated pattern period;

[0214] The number of DMRS resources S corresponding to the Physical Uplink Shared Channel Opportunity PO;

[0215] The number K of valid POs within the associated pattern period;

[0216] The length C of the orthogonal code included in the PRACH resource;

[0217] The PUSCH resource includes the length X of the orthogonal code.

[0218] In the embodiments of this application, P, R, S, K, C, and X are all configured by the network device for the terminal device.

[0219] In one embodiment, when the PUSCH resource includes orthogonal codes, the mapping rate satisfies the following expression:

[0220] L = ceil(T) preamble / T' pusch ) or L = ceil(T preamble / (X×T pusch ), where T preamble =P×R,

[0221] T' pusch =S×K×X,T pusch = S×K, where L represents the mapping rate. Here, " / " represents a ratio operation, and "×" represents a multiplication operation. It can be seen that after using OCC to expand the PUSCH resources, the number of PUSCH resources is S×K×X, which is an X-fold increase compared to S×K.

[0222] Here, `ceil` is a function that returns the smallest integer greater than or equal to a specified expression. For example, if T... preamble / T' pusch =1, then L=1, if T preamble / T' pusch =1.5, then L=1.

[0223] In another embodiment, the PRACH resource includes orthogonal codes, and the mapping rate satisfies the following expression: L =

[0224] ceil(T' preamble / T pusch ) or L = ceil((C × T preamble ) / T pusch ), where T' preamble =PeambleT pusch =Ssc,

[0225] T preamble =Peam, where L represents the mapping rate. It can be seen that after PRACH resources are extended using OCC, the number of PRACH resources is equal to the number of P sources, representing a C-fold increase compared to P.

[0226] In another embodiment, the PRACH resource includes orthogonal codes, the PUSCH resource includes orthogonal codes, and the mapping rate satisfies the following expression:

[0227] L = ceil(T) preamble / T” pusch ) or L = ceil((C × T preamble ) / (X×T pusch ), where T” preamble =P×R×

[0228] C,T” pusch =S×K×X,T pusch =S×K, where L represents the mapping rate.

[0229] In this embodiment of the application, the PRACH resource mapping order is one of the following methods:

[0230] The first type of PRACH resource mapping order is as follows:

[0231] Within a single RO, sorted in ascending order by orthogonal key index;

[0232] Within a RO, sorted in ascending order by the index of the random access preamble;

[0233] In multiple frequency domain reused ROs, sort them in ascending order of the RO frequency domain resource index;

[0234] Multiple ROs that are time-domain multiplexed within a PRACH time slot are ordered in ascending order of the RO time-domain resource index;

[0235] Sort by PRACH slot number in ascending order.

[0236] Reference Figure 11 Two PRACH time slots are configured, with corresponding PRACH time slot numbers 1 and 2. Each PRACH time slot reuses 2 ROs in the time domain and 2 ROs in the frequency domain. Within a time slot, the time domain resource indices of the corresponding ROs from front to back are 0 and 1, respectively. Within a time slot, the frequency domain resource indices of the corresponding ROs from low to high are 0 and 1, respectively. Figure 1 In this context, RO(m, n) represents the RO corresponding to time-domain resource index m and frequency-domain resource index n within a PRACH time slot.

[0237] For example, suppose the PRACH transport code domain contains two OCCs, with indices 0 and 1 respectively, and one RO corresponds to two preambles, with indices 0 and 1 respectively. A PRACH resource includes one OCC, one preamble, and one RO. Then, following the first PRACH resource mapping order (first step, within one RO, sorted in ascending order by orthogonal code index; second step, within one RO, sorted in ascending order by random access preamble index; third step, among multiple ROs multiplexed in the frequency domain, sorted in ascending order by RO frequency domain resource index; fourth step, among multiple ROs multiplexed in the time domain within one PRACH slot, sorted in ascending order by RO time domain resource index; fifth step, sorted in ascending order by PRACH slot number), the obtained PRACH resources are as shown in Table 1:

[0238] Table 1

[0239]

[0240]

[0241] The second type of PRACH resource mapping order is as follows:

[0242] Within a RO, sorted in ascending order by the index of the random access preamble;

[0243] Within a single RO, sorted in ascending order by orthogonal key index;

[0244] In multiple frequency domain reused ROs, sort them in ascending order of the RO frequency domain resource index;

[0245] Multiple ROs that are time-domain multiplexed within a PRACH time slot are ordered in ascending order by the RO time-domain resource index.

[0246] Sort by PRACH slot number in ascending order.

[0247] For example, assuming the PRACH transport code domain contains two OCCs with indices 0 and 1 respectively, and one RO corresponds to two preambles with indices 0 and 1 respectively. A PRACH resource includes one OCC, one preamble, and one RO. Following the second PRACH resource mapping order (first, within one RO, sorted in ascending order by the random access preamble index; second, within one RO, sorted in ascending order by the orthogonal code index; third, among multiple ROs multiplexed in the frequency domain, sorted in ascending order by the RO frequency domain resource index; fourth, among multiple ROs multiplexed in the time domain within one PRACH slot, sorted in ascending order by the RO time domain resource index; fifth, sorted in ascending order by the PRACH slot number), the obtained PRACH resources are as shown in Table 2:

[0248] Table 2

[0249]

[0250]

[0251] The third type of PRACH resource mapping order is as follows:

[0252] Within a RO, sorted in ascending order by the index of the random access preamble;

[0253] In multiple frequency domain reused ROs, sort them in ascending order by the RO frequency domain resource index;

[0254] Multiple ROs that are time-domain multiplexed within a PRACH time slot are ordered in ascending order by the RO time-domain resource index.

[0255] Sort by orthogonal key index in ascending order;

[0256] Sort by PRACH slot number in ascending order.

[0257] For example, suppose the PRACH transport code domain contains two OCCs, with indices 0 and 1 respectively, and one RO corresponds to two preambles, with indices 0 and 1 respectively. A PRACH resource includes one OCC, one preamble, and one RO. Then, following the third PRACH resource mapping order (first, within one RO, sorted in ascending order by the random access preamble index; second, among multiple ROs multiplexed in the frequency domain, sorted in ascending order by the RO frequency domain resource index; third, among multiple ROs multiplexed in the time domain within one PRACH slot, sorted in ascending order by the RO time domain resource index; fourth, sorted in ascending order by the orthogonal code index; fifth, sorted in ascending order by the PRACH slot number), the obtained PRACH resources are as shown in Table 3:

[0258] Table 3

[0259] PRACH Resources 0 Preamble 0, RO(0,0), OCC 0, PRACH slot 0 PRACH Resource 1 Preamble 1, RO(0,0), OCC 0, PRACH slot 0 PRACH Resource 2 Preamble 0, RO(0,1), OCC 0, PRACH slot 0 PRACH Resource 3 Preamble 1, RO(0,1), OCC 0, PRACH slot 0 PRACH Resource 4 Preamble 0, RO(1,0), OCC 0, PRACH slot 0 PRACH Resource 5 Preamble 1, RO(1,0), OCC 0, PRACH slot 0 PRACH Resource 6 Preamble 0, RO(1,1), OCC 0, PRACH slot 0 PRACH Resource 7 Preamble 1, RO(1,1), OCC 0, PRACH slot 0 PRACH Resource 8 Preamble 0, RO(0,0), OCC 1, PRACH slot 0 PRACH Resource 9 Preamble 1, RO(0,0), OCC 1, PRACH slot 0 PRACH Resources 10 Preamble 0, RO(0,1), OCC 1, PRACH slot 0 PRACH Resource 11 Preamble 1, RO(0,1), OCC 1, PRACH slot 0 PRACH Resources 12 Preamble 0, RO(1,0), OCC 1, PRACH slot 0 PRACH Resource 13 Preamble 1, RO(1,0), OCC 1, PRACH slot 0 PRACH Resource 14 Preamble 0, RO(1,1), OCC 1, PRACH slot 0 PRACH Resource 15 Preamble 1, RO(1,1), OCC 1, PRACH slot 0 PRACH Resource 16 Preamble 0, RO(0,0), OCC 0, PRACH slot 1 PRACH Resource 17 Preamble 1, RO(0,0), OCC 0, PRACH slot 1 PRACH Resource 18 Preamble 0, RO(0,1), OCC 0, PRACH slot 1 PRACH Resources 19 Preamble 1, RO(0,1), OCC 0, PRACH slot 1 PRACH Resources 20 Preamble 0, RO(1,0), OCC 0, PRACH slot 1 PRACH Resource 21 Preamble 1, RO(1,0), OCC 0, PRACH slot 1 PRACH Resource 22 Preamble 0, RO(1,1), OCC 0, PRACH slot 1 PRACH Resource 23 Preamble 1, RO(1,1), OCC 0, PRACH slot 1 PRACH Resource 24 Preamble 0, RO(0,0), OCC 1, PRACH slot 1 PRACH Resource 25 Preamble 1, RO(0,0), OCC 1, PRACH slot 1 PRACH Resource 26 Preamble 0, RO(0,1), OCC 1, PRACH slot 1 PRACH Resource 27 Preamble 1, RO(0,1), OCC 1, PRACH slot 1 PRACH Resource 28 Preamble 0, RO(1,0), OCC 1, PRACH slot 1 PRACH Resource 29 Preamble 1, RO(1,0), OCC 1, PRACH slot 1 PRACH Resources 30 Preamble 0, RO(1,1), OCC 1, PRACH slot 1 PRACH Resource 31 Preamble 1, RO(1,1), OCC 1, PRACH slot 1

[0260] The fourth PRACH resource mapping order is as follows:

[0261] Within a RO, sorted in ascending order by the index of the random access preamble;

[0262] In multiple frequency domain reused ROs, sort them in ascending order by the RO frequency domain resource index;

[0263] Multiple ROs that are time-domain multiplexed within a PRACH time slot are ordered in ascending order by the RO time-domain resource index.

[0264] Arranged in ascending order by PRACH slot number;

[0265] Sort by orthogonal key index in ascending order.

[0266] For example, suppose the PRACH transport code domain contains two OCCs, with indices 0 and 1 respectively, and one RO corresponds to two preambles, with indices 0 and 1 respectively. A PRACH resource includes one OCC, one preamble, and one RO. Then, following the fourth PRACH resource mapping order (first, within one RO, sorted in ascending order by the random access preamble index; second, among multiple ROs multiplexed in the frequency domain, sorted in ascending order by the RO frequency domain resource index; third, among multiple ROs multiplexed in the time domain within one PRACH slot, sorted in ascending order by the RO time domain resource index; fourth, sorted in ascending order by the PRACH slot number; fifth, sorted in ascending order by the orthogonal code index), the obtained PRACH resources are as shown in Table 4:

[0267] Table 4

[0268]

[0269]

[0270] Furthermore, for the four PRACH resource mapping orders in Tables 1 to 4, if the mapping rate between SSB and RO is 1, and if there are 8 SSBs with indices from 0 to 7, then SSB i and PRACH resource i have a mapping relationship, where i takes values ​​from 0 to 7.

[0271] For example, if a terminal device needs to send a first random access request message, it first detects the signal strength of SSB 0 to SSB 7. If the signal strength of SSB 2 is detected to be stronger, the first random access request message can be sent using PRACH resource 2. For PRACH resource 2 in Table 1, it includes: OCC 0, Preamble 1, RO(0,0), and PRACH slot 0; for PRACH resource 2 in Table 2, it includes: Preamble 0, OCC 1, RO(0,0), and PRACH slot 0; for PRACH resource 2 in Table 3, it includes: Preamble 0, RO(0,1), OCC 0, and PRACH slot 0; for PRACH resource 2 in Table 4, it includes: Preamble 0, RO(0,1), PRACH slot 0, and OCC 0.

[0272] In the embodiments of this application, multiple PRACH resource mapping orders are provided. Any PRACH resource mapping order can realize the mapping of SSB and PRACH resources, so that when the PRACH resource includes OCC, the system capacity can be enhanced in the 4-step random access process or the 2-step random access process, and when the PRACH resource includes OCC, the PRACH resource for sending uplink data can be determined.

[0273] In this embodiment of the application, the mapping order of PUSCH resources is one of the following methods:

[0274] The mapping order of the first type of PUSCH resource is as follows:

[0275] In a PO, sorted in ascending order by the DMRS resource index, where the DMRS resource index is determined based on the DMRS port index, the DMRS sequence index, and the orthogonal code index;

[0276] At least one PO at the same time domain location is ordered from low to high frequency domain location;

[0277] At least one PO that is time-domain multiplexed within a time slot is sorted in ascending order by the PO time-domain resource index;

[0278] Sort by PUSCH slot number in ascending order.

[0279] Furthermore, within a PO, ordered in ascending order by the DMRS resource index, the following item is included:

[0280] Sort in ascending order by DMRS port index, then by DMRS sequence index, and finally by orthogonal code index.

[0281] Sort in ascending order by DMRS sequence index, then by DMRS port index, and finally by orthogonal code index.

[0282] Sort in ascending order by orthogonal code index, then by DMRS sequence index, and finally by DMRS port index.

[0283] Sort in ascending order by orthogonal code index, then by DMRS port index, and finally by DMRS sequence index.

[0284] Sort in ascending order by DMRS port index, then by orthogonal code index, and finally by DMRS sequence index.

[0285] Sort in ascending order by DMRS sequence index, then by orthogonal code index, and finally by DMRS port index.

[0286] For example, if a DMRS resource includes: a DMRS port, a DMRS sequence, and an OCC, with DMRS port indices of 0 and 1, DMRS sequence indices of 0 and 1, and orthogonal code indices of 0 and 1, then the DMRS resource index is determined by sequentially sorting the DMRS sequence index in ascending order, the orthogonal code index in ascending order, and the DMRS port index in ascending order (first step, sorting by DMRS sequence index in ascending order; second step, sorting by orthogonal code index in ascending order; third step, sorting by DMRS port index in ascending order). The resulting DMRS resource index is shown in Table 5.

[0287] Table 5

[0288] DMRS Resources 0 DMRS port 0, DMRS sequence 0, OCC 0 DMRS Resource 1 DMRS Port 1, DMRS Sequence 0, OCC 0 DMRS Resource 2 DMRS port 0, DMRS sequence 1, OCC 0 DMRS Resource 3 DMRS Port 1, DMRS Sequence 1, OCC 0 DMRS Resource 4 DMRS port 0, DMRS sequence 0, OCC 1 DMRS Resource 5 DMRS Port 1, DMRS Sequence 0, OCC 1 DMRS Resource 6 DMRS Port 0, DMRS Sequence 1, OCC 1 DMRS Resource 7 DMRS Port 1, DMRS Sequence 1, OCC 1

[0289] Furthermore, if there are two PUSCH slot numbers, 0 and 1 respectively, two frequency domain resources and two time domain resources, with the two frequency domain resources represented by indices 0 and 1 from low to high, and the two time domain resources represented by indices 0 and 1 respectively, then there are four POs. Further, if a PUSCH resource includes one DMRS resource and one PO, then according to the first PUSCH resource mapping order (first step, within a PO, sorted in ascending order by DMRS resource index, where the DMRS resource index is determined based on the DMRS port index, DMRS sequence index, and orthogonal code index; second step, at least one PO at the same time domain position sorted in ascending order by frequency domain position from low to high; third step, at least one PO time-domain multiplexed within a slot sorted in ascending order by PO time domain resource index; fourth step, sorted in ascending order by PUSCH slot number), the PUSCH resources obtained are as shown in Table 6:

[0290] Table 6

[0291]

[0292]

[0293] Table 6 lists 64 PUSCH resources.

[0294] The mapping order of the second type of PUSCH resource is as follows:

[0295] Sort by orthogonal key index in ascending order;

[0296] Within a PO, sorted in ascending order by the DMRS resource index, where the DMRS resource index is determined based on the DMRS port index and the DMRS sequence index;

[0297] At least one PO at the same time domain location is ordered from low to high frequency domain location;

[0298] At least one PO that is time-domain multiplexed within a time slot is sorted in ascending order by the PO time-domain resource index;

[0299] Sort by PUSCH slot number in ascending order.

[0300] In the embodiments of this application, the mapping order of the second to fourth PUSCH resources, in a PO, the order of DMRS resource index in ascending order includes the following: in ascending order of DMRS port index, then in ascending order of DMRS sequence index; in ascending order of DMRS sequence index, then in ascending order of DMRS port index.

[0301] For example, if a DMRS resource includes a DMRS port and a DMRS sequence, and if the DMRS port index is 0 and 1, the DMRS sequence index is 0 and 1, and the orthogonal code index is 0 and 1, then the DMRS resource index determined in ascending order of DMRS sequence index and then in ascending order of DMRS port index is shown in Table 7.

[0302] Table 7

[0303] DMRS Resources 0 DMRS Port 0, DMRS Sequence 0 DMRS Resource 1 DMRS Port 1, DMRS Sequence 0 DMRS Resource 2 DMRS port 0, DMRS sequence 1 DMRS Resource 3 DMRS Port 1, DMRS Sequence 1

[0304] Furthermore, if there are two PUSCH slot numbers, 0 and 1 respectively, two frequency domain resources and two time domain resources, with the two frequency domain resources represented by indices 0 and 1 from low to high, and the two time domain resources represented by indices 0 and 1 respectively, then there are four POs. Further, if a PUSCH resource includes one DMRS resource and one PO, then according to the second PUSCH resource mapping order (first step, ascending order by orthogonal code index; second step, ascending order by DMRS resource index within a PO, where the DMRS resource index is determined based on the DMRS port index and DMRS sequence index; third step, at least one PO at the same time domain position, ascending order by frequency domain position from low to high; fourth step, at least one PO time-domain multiplexed within a slot, ascending order by PO time domain resource index; fifth step, ascending order by PUSCH slot number), the PUSCH resources obtained are as shown in Table 8:

[0305] Table 8

[0306]

[0307]

[0308] The mapping order of the third type of PUSCH resource is as follows:

[0309] Within a PO, sorted in ascending order by the DMRS resource index, where the DMRS resource index is determined based on the DMRS port index and the DMRS sequence index;

[0310] Sort by orthogonal key index in ascending order;

[0311] At least one PO at the same time domain location is ordered from low to high frequency domain location;

[0312] At least one PO that is time-domain multiplexed within a time slot is sorted in ascending order by the PO time-domain resource index;

[0313] Sort by PUSCH slot number in ascending order.

[0314] The example of the third type of PUSCH resource mapping order can be found above, and will not be repeated here.

[0315] The mapping order of the fourth type of PUSCH resource is as follows:

[0316] Within a PO, sorted in ascending order by the DMRS resource index, where the DMRS resource index is determined based on the DMRS port index and the DMRS sequence index;

[0317] At least one PO at the same time domain location is ordered from low to high frequency domain location;

[0318] At least one PO that is time-domain multiplexed within a time slot is sorted in ascending order by the PO time-domain resource index;

[0319] Sort by orthogonal key index in ascending order;

[0320] Sort by PUSCH slot number in ascending order.

[0321] The example of the fourth type of PUSCH resource mapping order can be found above, and will not be repeated here.

[0322] The mapping order of the fifth type of PUSCH resource is as follows:

[0323] Within a PO, sorted in ascending order by the DMRS resource index, where the DMRS resource index is determined based on the DMRS port index and the DMRS sequence index;

[0324] At least one PO at the same time domain location is ordered from low to high frequency domain location;

[0325] At least one PO that is time-domain multiplexed within a time slot is sorted in ascending order by the PO time-domain resource index;

[0326] Sort by PUSCH slot number in ascending order;

[0327] Sort by orthogonal key index in ascending order.

[0328] The example of the mapping order of the fifth type of PUSCH resource can be found above, and will not be repeated here.

[0329] Furthermore, if the mapping rate between PRACH resources and PUSCH resources is 1, and there are 32 PRACH resources and 64 PUSCH resources, then PRACH resource j and PUSCH resource j have a mapping relationship, where i ranges from 0 to 31. For example, based on Tables 1 and 6, PRACH resource 0 and PUSCH resource 0 have a mapping relationship.

[0330] In the embodiments of this application, multiple mapping orders for PUSCH resources are provided. Any mapping order for PUSCH resources can realize the mapping of PRACH resources and PUSCH resources. PRACH transmission and / or PUSCH transmission are extended using OCC, which can enhance the system capacity during the two-step random access process.

[0331] In one embodiment, the uplink data is data sent by the terminal device in a disconnected state based on pre-configured PUSCH resources. The mapping relationship includes the mapping relationship between PUSCH resources and SSBs. The mapping relationship between PUSCH resources and SSBs is determined according to the mapping rate between SSBs and PUSCH resources, the SSB index order, and the mapping order of PUSCH resources. The mapping rate between SSBs and PUSCH resources represents the number of SSBs corresponding to one PUSCH resource.

[0332] In the embodiments of this application, when the PUSCH resource includes orthogonal codes, this application can determine the uplink data transmission resource for transmitting uplink data based on the mapping relationship between the PUSCH resource and SSB, in order to improve the transmission capacity of the PUSCH resource by introducing OCC multiplexing.

[0333] Specifically, when the terminal device is in a disconnected state, it can utilize the pre-configured periodic PUSCH resources for data transmission. Specifically, the terminal device determines the target SSB with better signal quality based on SSB measurement results. When uplink data needs to be transmitted, it selects the PUSCH resource corresponding to the target SSB for uplink data transmission. In other words, a mapping relationship needs to be established between SSBs and PUSCH resources. When PUSCH resources include OCC multiplexing, the mapping relationship between SSBs and PUSCH resources needs to take OCC resources into account.

[0334] In this embodiment of the application, the PUSCH resource mapping order is one of the following:

[0335] The first type of PUSCH resource mapping order is as follows:

[0336] Within a PO, sorted in ascending order by the DMRS resource index;

[0337] In the time domain, indexes are sorted in ascending order according to the PUSCH resource configuration cycle.

[0338] Sort by orthogonal key index in ascending order.

[0339] Within a single PO, the DMRS resource index is sorted in ascending order as shown in Table 7, which will not be repeated here.

[0340] For example, considering two PUSCH configuration cycles with PUSCH resource configuration cycle indices of 0 and 1 respectively, and orthogonal code indices of 0 and 1 respectively, the PUSCH resources obtained according to the first PUSCH resource mapping order (step 1, the first PUSCH resource mapping order is as follows: step 2, within a PO, sorted in ascending order by DMRS resource index; step 3, in the time domain, sorted in ascending order by PUSCH resource configuration cycle index; step 4, sorted in ascending order by orthogonal code index) are as shown in Table 9:

[0341] Table 9

[0342]

[0343]

[0344] The second type of PUSCH resource mapping order is as follows:

[0345] Within a PO, sorted in ascending order by the DMRS resource index;

[0346] Sort by orthogonal key index in ascending order;

[0347] In the time domain, the periodic index is configured in ascending order according to PUSCH.

[0348] For example, if there are two PUSCH configuration cycles, with PUSCH resource configuration cycle indices of 0 and 1 respectively, and orthogonal code indices of 0 and 1 respectively, then according to this second PUSCH resource mapping order (first step, within a PO, sorted in ascending order by DMRS resource index; second step, sorted in ascending order by orthogonal code index; third step, sorted in ascending order by PUSCH configuration cycle index in the time domain), the PUSCH resources obtained can be as shown in Table 10:

[0349] Table 10

[0350] PUSCH Resources 0 DMRS resource 0, OCC 0, PUSCH resource configuration cycle 0 PUSCH Resource 1 DMRS resource 1, OCC 0, PUSCH resource configuration cycle 0 PUSCH Resource 2 DMRS resource 2, OCC 0, PUSCH resource configuration cycle 0 PUSCH Resource 3 DMRS resource 3, OCC 0, PUSCH resource configuration cycle 0 PUSCH Resource 4 DMRS resource 0, OCC 1, PUSCH resource configuration cycle 0 PUSCH Resource 5 DMRS resource 1, OCC 1, PUSCH resource configuration cycle 0 PUSCH Resource 6 DMRS resource 2, OCC 1, PUSCH resource configuration cycle 0 PUSCH Resource 7 DMRS resource 3, OCC 1, PUSCH resource configuration cycle 0 PUSCH Resource 8 DMRS resource 0, OCC 0, PUSCH resource configuration cycle 1 PUSCH Resource 9 DMRS resource 1, OCC 0, PUSCH resource configuration cycle 1 PUSCH Resources 10 DMRS resource 2, OCC 0, PUSCH resource configuration cycle 1 PUSCH Resources 11 DMRS resource 3, OCC 0, PUSCH resource configuration cycle 1 PUSCH Resources 12 DMRS resource 0, OCC 1, PUSCH resource configuration cycle 1 PUSCH Resources 13 DMRS resource 1, OCC 1, PUSCH resource configuration cycle 1 PUSCH Resource 14 DMRS resource 2, OCC 1, PUSCH resource configuration cycle 1 PUSCH Resources 15 DMRS resource 3, OCC 1, PUSCH resource configuration cycle 1

[0351] Among them, the method based on the first PUSCH resource mapping order and the second PUSCH resource mapping order within a PO, ordered by the DMRS resource index in ascending order, includes the following:

[0352] Sort by DMRS port index in ascending order, then by DMRS sequence index in ascending order;

[0353] Sort in ascending order by DMRS sequence index and then by DMRS port index.

[0354] Specific examples are shown in Table 7, and will not be repeated here.

[0355] The third type of PUSCH resource mapping order is as follows:

[0356] In the time domain, the periodic index is configured in ascending order according to the PUSCH configuration.

[0357] Within a PO, sorted in ascending order by the DMRS resource index, where the DMRS resource index is determined based on the DMRS port index, DMRS sequence index, and orthogonal code index.

[0358] Within a single PO, the DMRS resource index is sorted in ascending order as shown in Table 5, which will not be repeated here.

[0359] For example, if there are two PUSCH configuration cycles, with PUSCH resource configuration cycle indices of 0 and 1 respectively, then according to this third PUSCH resource mapping order (first, in the time domain, sorted in ascending order by PUSCH configuration cycle index; second, within a PO, sorted in ascending order by DMRS resource index), the PUSCH resources obtained can be as shown in Table 11:

[0360] Table 11

[0361] PUSCH Resources 0 PUSCH resource configuration cycle 0, DMRS resources 0 PUSCH Resource 1 PUSCH resource configuration cycle 1, DMRS resources 0 PUSCH Resource 2 PUSCH resource configuration cycle 0, DMRS resource 1 PUSCH Resource 3 PUSCH resource configuration cycle 1, DMRS resource 1 PUSCH Resource 4 PUSCH resource configuration cycle 0, DMRS resource 2 PUSCH Resource 5 PUSCH resource configuration cycle 1, DMRS resource 2 PUSCH Resource 6 PUSCH resource configuration cycle 0, DMRS resource 3 PUSCH Resource 7 PUSCH resource configuration cycle 1, DMRS resource 3 PUSCH Resource 8 PUSCH resource configuration cycle 0, DMRS resource 4 PUSCH Resource 9 PUSCH resource configuration cycle 1, DMRS resource 4 PUSCH Resources 10 PUSCH resource configuration cycle 0, DMRS resource 5 PUSCH Resources 11 PUSCH resource configuration cycle 1, DMRS resource 5 PUSCH Resources 12 PUSCH resource configuration cycle 0, DMRS resource 6 PUSCH Resources 13 PUSCH resource configuration cycle 1, DMRS resource 6 PUSCH Resource 14 PUSCH resource configuration cycle 0, DMRS resource 7 PUSCH Resources 15 PUSCH resource configuration cycle 1, DMRS resource 7

[0362] The fourth PUSCH resource mapping order is as follows:

[0363] Within a PO, sorted in ascending order by the DMRS resource index, where the DMRS resource index is determined based on the DMRS port index, DMRS sequence index, and orthogonal code index;

[0364] In the time domain, the periodic index is configured in ascending order according to PUSCH.

[0365] Within a single PO, the DMRS resource index is sorted in ascending order as shown in Table 5, which will not be repeated here.

[0366] For example, consider two PUSCH configuration cycles, with PUSCH resource configuration cycle indices of 0 and 1 respectively. Following this fourth PUSCH resource mapping order (first, within a PO, sorted in ascending order by DMRS resource index; second, in the time domain, sorted in ascending order by PUSCH configuration cycle index), the resulting PUSCH resources are as shown in Table 12:

[0367] Table 12

[0368] PUSCH Resources 0 DMRS resource 0, PUSCH resource configuration cycle 0 PUSCH Resource 1 DMRS resource 1, PUSCH resource configuration cycle 0 PUSCH Resource 2 DMRS resource 2, PUSCH resource configuration cycle 0 PUSCH Resource 3 DMRS resource 3, PUSCH resource configuration cycle 0 PUSCH Resource 4 DMRS resource 4, PUSCH resource configuration cycle 0 PUSCH Resource 5 DMRS resource 5, PUSCH resource configuration cycle 0 PUSCH Resource 6 DMRS resource 6, PUSCH resource configuration cycle 0 PUSCH Resource 7 DMRS resource 7, PUSCH resource configuration cycle 0 PUSCH Resource 8 DMRS resource 0, PUSCH resource configuration cycle 1 PUSCH Resource 9 DMRS resource 1, PUSCH resource configuration cycle 1 PUSCH Resources 10 DMRS resource 2, PUSCH resource configuration cycle 1 PUSCH Resources 11 DMRS resource 3, PUSCH resource configuration cycle 1 PUSCH Resources 12 DMRS resource 4, PUSCH resource configuration cycle 1 PUSCH Resources 13 DMRS resource 5, PUSCH resource configuration cycle 1 PUSCH Resource 14 DMRS resource 6, PUSCH resource configuration cycle 1 PUSCH Resources 15 DMRS resource 7, PUSCH resource configuration cycle 1

[0369] Furthermore, based on the third and fourth PUSCH resource mapping orders, within a PO, in ascending order of the DMRS resource index, the following item is included:

[0370] Sort in ascending order by DMRS port index, then by DMRS sequence index, and finally by orthogonal code index.

[0371] Sort in ascending order by DMRS sequence index, then by DMRS port index, and finally by orthogonal code index.

[0372] Sort in ascending order by orthogonal code index, then by DMRS sequence index, and finally by DMRS port index.

[0373] Sort in ascending order by orthogonal code index, then by DMRS port index, and finally by DMRS sequence index.

[0374] Sort in ascending order by DMRS port index, then by orthogonal code index, and finally by DMRS sequence index.

[0375] Sort in ascending order by DMRS sequence index, then by orthogonal code index, and finally by DMRS port index.

[0376] Within a single PO, the DMRS resource index is sorted in ascending order as shown in Table 5, which will not be repeated here.

[0377] Furthermore, if the mapping rate between SSB and PUSCH resource is 1, and there are 8 SSBs with indices from 0 to 7, then SSB i and PUSCH resource i have a mapping relationship, where i takes the values ​​from 0 to 7.

[0378] For example, if a terminal device needs to send uplink data while in a disconnected state, it first checks the signal strength of SSB 0 to SSB 7. If the signal strength of SSB 2 is detected to be stronger, the uplink data can be sent using PUSCH resource 2.

[0379] In the embodiments of this application, multiple PUSCH resource mapping orders are provided. Any PUSCH resource mapping order can be used to determine the mapping relationship between SSB and PUSCH resources, so that when the terminal device uploads uplink data to the network device, the system capacity is enhanced, and the PUSCH resources used to send uplink data can be determined.

[0380] In this embodiment of the application, the network device sends the above-mentioned mapping relationship, as well as PRACH resources and PUSCH resources, to the terminal device. The terminal device determines the uplink data transmission resources according to the above-mentioned mapping relationship, thereby realizing the transmission of uplink data based on the uplink data transmission resources.

[0381] Reference Figure 12 , Figure 12 This is a flowchart illustrating the steps of a data transmission method provided in an embodiment of this application. Figure 2 In some embodiments of this application, the entity executing the data transmission method can be a network device or a device capable of supporting the network device in implementing related functions, such as a chip system, which can be installed in the network device. The data transmission method includes:

[0382] S121. Receive uplink data sent based on uplink data transmission resources.

[0383] The uplink data transmission resources include: Physical Random Access Channel (PRACH) resources and / or Physical Uplink Shared Channel (PUSCH) resources.

[0384] Furthermore, the uplink data transmission resources are determined based on a mapping relationship, wherein the mapping relationship includes at least one of the following:

[0385] Mapping relationship between PRACH resources and Synchronization Signal-Physical Broadcast Channel Block (SSB);

[0386] Mapping relationship between PUSCH resources and SSB;

[0387] Mapping relationship between PRACH and PUSCH resources.

[0388] The specific implementation process of this embodiment refers to the embodiment on the terminal device side described above, and will not be repeated here.

[0389] The data transmission method of the embodiments of this application has been described above. The apparatus for performing the above data transmission method provided in the embodiments of this application is described below. Those skilled in the art will understand that the methods and apparatus can be combined with and referenced by each other, and the related apparatus provided in the embodiments of this application can perform the steps in the above data transmission method.

[0390] Reference Figure 13 , Figure 13This is a schematic diagram of the hardware structure of a data transmission device provided in an embodiment of this application. The embodiment of this application provides a data transmission device 130, which includes a processor 131, a memory 132, and a communication interface 133.

[0391] Memory 132 is used to store programs or instructions.

[0392] The communication interface 133 is used to receive signals from other data transmission devices and transmit them to the processor 131, or to send signals from the processor 131 to other data transmission devices.

[0393] The processor 131 is used to execute programs or instructions to enable the data transmission device to implement the data transmission method provided in the above embodiments.

[0394] This application also provides a chip, which includes a processor. The processor is used to call a computer program in memory to execute the technical solutions in the above embodiments. Its implementation principle and technical effects are similar to the related embodiments described above, and will not be repeated here.

[0395] This application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. When the computer program is executed by a processor, it implements the data transmission method described above. The data transmission method described in the above embodiments can be implemented wholly or partially by software, hardware, firmware, or any combination thereof. If implemented in software, the functionality can be stored as one or more instructions or code on or transmitted on the computer-readable medium. The computer-readable medium can include computer storage media and communication media, and can also include any medium that can transfer a computer program from one place to another. The storage medium can be any target medium accessible by a computer.

[0396] In one possible implementation, a computer-readable medium may include RAM, ROM, compact disc read-only memory (CD-ROM) or other optical disc storage, disk storage or other magnetic storage devices, or any other medium targeted to carry or to store the required program code in the form of instructions or data structures, and accessible by a computer. Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, disks and optical discs include optical discs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs reproduce data using laser optical principles. Combinations of the above should also be included within the scope of computer-readable media.

[0397] This application provides a computer program product, which includes a computer program that, when run, causes the computer to execute the aforementioned data transmission method.

[0398] The above specific embodiments further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of the present invention should be included within the scope of protection of the present invention.

Claims

1. A data transmission method, characterized in that, The method includes: The uplink data transmission resources are determined according to the mapping relationship. The uplink data transmission resources include physical random access channel (PRACH) resources and / or physical uplink shared channel (PUSCH) resources. Uplink data is sent based on the aforementioned uplink data transmission resources; The mapping relationship includes at least one of the following: Mapping relationship between PRACH resources and Synchronization Signal-Physical Broadcast Channel Block (SSB); Mapping relationship between PUSCH resources and SSB; Mapping relationship between PRACH and PUSCH resources.

2. The data transmission method according to claim 1, characterized in that, The uplink data is a first random access request message sent based on PRACH resources. The mapping relationship includes the mapping relationship between PRACH resources and SSB, wherein: the PRACH resources include random access channel timing (RO), random access preamble, and orthogonal code.

3. The data transmission method according to claim 2, characterized in that, The mapping relationship between PRACH resources and SSBs is determined based on the mapping rate between SSBs and ROs, the SSB index order, and the PRACH resource mapping order. The mapping rate between SSBs and ROs represents the number of SSBs corresponding to one RO.

4. The data transmission method according to claim 1, characterized in that, The uplink data is a second random access request message sent based on PRACH and PUSCH resources. The mapping relationship includes the mapping relationship between PRACH resources and PUSCH resources, wherein: The PRACH resources include random access channel timing (RO), random access preamble, and orthogonal codes; and / or the PUSCH resources include physical uplink shared channel timing (PO), demodulation reference signal (DMRS) resources, and orthogonal codes.

5. The data transmission method according to claim 4, characterized in that, The mapping relationship between the PRACH resources and the PUSCH resources is determined based on the mapping rate between the PRACH resources and the PUSCH resources, the mapping order of the PRACH resources, and the mapping order of the PUSCH resources. The mapping rate between the PRACH resources and the PUSCH resources represents the number of PRACH resources corresponding to one PUSCH resource.

6. The data transmission method according to claim 5, characterized in that, The mapping rate between the PRACH resource and the PUSCH resource is determined based on at least one of the following parameters: The number of random access preambles, P; The number of valid ROs (Representative Roots) R within the associated pattern period; The number of DMRS resources S corresponding to the Physical Uplink Shared Channel Opportunity PO; The number K of valid POs within the associated pattern period; The length C of the orthogonal code included in the PRACH resource; The PUSCH resource includes the length X of the orthogonal code.

7. The data transmission method according to any one of claims 3 to 6, characterized in that, The PRACH resource mapping order is as follows: Within a single RO, sorted in ascending order by orthogonal key index; Within a RO, sorted in ascending order by the index of the random access preamble; In multiple frequency domain reused ROs, sort them in ascending order by the RO frequency domain resource index; Multiple ROs that are time-domain multiplexed within a PRACH time slot are ordered in ascending order of the RO time-domain resource index; Sort by PRACH slot number in ascending order.

8. The data transmission method according to any one of claims 3 to 6, characterized in that, The PRACH resource mapping order is as follows: Within a RO, sorted in ascending order by the index of the random access preamble; Within a single RO, sorted in ascending order by orthogonal key index; In multiple frequency domain reused ROs, sort them in ascending order by the RO frequency domain resource index; Multiple ROs that are time-domain multiplexed within a PRACH time slot are ordered in ascending order by the RO time-domain resource index. Sort by PRACH slot number in ascending order.

9. The data transmission method according to any one of claims 3 to 6, characterized in that, The PRACH resource mapping order is as follows: Within a RO, sorted in ascending order by the index of the random access preamble; In multiple frequency domain reused ROs, sort them in ascending order by the RO frequency domain resource index; Multiple ROs that are time-domain multiplexed within a PRACH time slot are ordered in ascending order by the RO time-domain resource index. Sort by orthogonal key index in ascending order; Sort by PRACH slot number in ascending order.

10. The data transmission method according to any one of claims 3 to 6, characterized in that, The PRACH resource mapping order is as follows: Within a RO, sorted in ascending order by the index of the random access preamble; In multiple frequency domain reused ROs, sort them in ascending order by the RO frequency domain resource index; Multiple ROs that are time-domain multiplexed within a PRACH time slot are ordered in ascending order by the RO time-domain resource index. Arranged in ascending order by PRACH slot number; Sort by orthogonal key index in ascending order.

11. The data transmission method according to claim 5 or 6, characterized in that, The mapping order of the PUSCH resources is as follows: In a PO, sorted in ascending order by the DMRS resource index, wherein the DMRS resource index is determined based on the DMRS port index, the DMRS sequence index, and the orthogonal code index; At least one PO at the same time domain location is ordered from low to high frequency domain location; At least one PO that is time-domain multiplexed within a time slot is sorted in ascending order by the PO time-domain resource index; Sort by PUSCH slot number in ascending order.

12. The data transmission method according to claim 11, characterized in that, The order of sorting in ascending order of DMRS resource index within a PO includes the following: The sorting is performed sequentially in ascending order by the DMRS port index, then by the DMRS sequence index, and finally by the orthogonal code index. The order is sequentially sorted in ascending order by the DMRS sequence index, then by the DMRS port index, and finally by the orthogonal code index. The order is determined sequentially by the orthogonal code index in ascending order, the DMRS sequence index in ascending order, and the DMRS port index in ascending order. The order is sequentially determined by the orthogonal code index in ascending order, the DMRS port index in ascending order, and the DMRS sequence index in ascending order. The sorting is performed sequentially in ascending order by the DMRS port index, then by the orthogonal code index, and finally by the DMRS sequence index. The order is determined sequentially by the DMRS sequence index in ascending order, the orthogonal code index in ascending order, and the DMRS port index in ascending order.

13. The data transmission method according to claim 5 or 6, characterized in that, The mapping order of the PUSCH resources is as follows: Sort by orthogonal key index in ascending order; In a PO, sorted in ascending order by DMRS resource index, wherein the DMRS resource index is determined based on the DMRS port index and the DMRS sequence index; At least one PO at the same time domain location is ordered from low to high frequency domain location; At least one PO that is time-domain multiplexed within a time slot is sorted in ascending order by the PO time-domain resource index; Sort by PUSCH slot number in ascending order.

14. The data transmission method according to claim 5 or 6, characterized in that, The mapping order of the PUSCH resources is as follows: In a PO, sorted in ascending order by DMRS resource index, wherein the DMRS resource index is determined based on the DMRS port index and the DMRS sequence index; Sort by orthogonal key index in ascending order; At least one PO at the same time domain location is ordered from low to high frequency domain location; At least one PO that is time-domain multiplexed within a time slot is sorted in ascending order by the PO time-domain resource index; Sort by PUSCH slot number in ascending order.

15. The data transmission method according to claim 5 or 6, characterized in that, The mapping order of the PUSCH resources is as follows: In a PO, sorted in ascending order by DMRS resource index, wherein the DMRS resource index is determined based on the DMRS port index and the DMRS sequence index; At least one PO at the same time domain location is ordered from low to high frequency domain location; At least one PO that is time-domain multiplexed within a time slot is sorted in ascending order by the PO time-domain resource index; Sort in ascending order according to the orthogonal code index; Sort by PUSCH slot number in ascending order.

16. The data transmission method according to claim 5 or 6, characterized in that, The mapping order of the PUSCH resources is as follows: In a PO, sorted in ascending order by DMRS resource index, wherein the DMRS resource index is determined based on the DMRS port index and the DMRS sequence index; At least one PO at the same time domain location is ordered from low to high frequency domain location; At least one PO that is time-domain multiplexed within a time slot is sorted in ascending order by the PO time-domain resource index; Sort by PUSCH slot number in ascending order; Sort by orthogonal key index in ascending order.

17. The data transmission method according to claim 1, characterized in that, The uplink data is data sent by the terminal device in a disconnected state based on pre-configured PUSCH resources. The mapping relationship includes the mapping relationship between the PUSCH resources and the SSBs. The mapping relationship between the PUSCH resources and the SSBs is determined according to the mapping rate between the SSBs and the PUSCH resources, the SSB index order, and the mapping order of the PUSCH resources. The mapping rate between the SSBs and the PUSCH resources represents the number of SSBs corresponding to one PUSCH resource.

18. The data transmission method according to claim 17, characterized in that, The PUSCH resource mapping order is as follows: Within a PO, sorted in ascending order by the DMRS resource index; In the time domain, indexes are sorted in ascending order according to the PUSCH resource configuration cycle. Sort by orthogonal key index in ascending order.

19. The data transmission method according to claim 18, characterized in that, The PUSCH resource mapping order is as follows: Within a PO, sorted in ascending order by the DMRS resource index; Sort by orthogonal key index in ascending order; In the time domain, the periodic index is configured in ascending order according to PUSCH.

20. The data transmission method according to claim 18 or 19, characterized in that, The order of sorting within a PO in ascending order of the DMRS resource index includes the following: The sorting is performed sequentially in ascending order by the DMRS port index and then by the DMRS sequence index. The DMRS sequence index and the DMRS port index are ordered in ascending order.

21. The data transmission method according to claim 17, characterized in that, The PUSCH resource mapping order is as follows: In the time domain, the periodic index is configured in ascending order according to the PUSCH configuration. Within a PO, sorted in ascending order by the DMRS resource index, where the DMRS resource index is determined based on the DMRS port index, DMRS sequence index, and orthogonal code index.

22. The data transmission method according to claim 17, characterized in that, The PUSCH resource mapping order is as follows: Within a PO, sorted in ascending order by the DMRS resource index, where the DMRS resource index is determined based on the DMRS port index, DMRS sequence index, and orthogonal code index; In the time domain, the periodic index is configured in ascending order according to PUSCH.

23. The data transmission method according to claim 21 or 22, characterized in that, The order of sorting within a PO in ascending order of the DMRS resource index includes the following: The sorting is performed sequentially in ascending order by the DMRS port index, then by the DMRS sequence index, and finally by the orthogonal code index. The order is sequentially sorted in ascending order by the DMRS sequence index, then by the DMRS port index, and finally by the orthogonal code index. The order is determined sequentially by the orthogonal code index in ascending order, the DMRS sequence index in ascending order, and the DMRS port index in ascending order. The order is sequentially determined by the orthogonal code index in ascending order, the DMRS port index in ascending order, and the DMRS sequence index in ascending order. The sorting is performed sequentially in ascending order by the DMRS port index, then by the orthogonal code index, and finally by the DMRS sequence index. The order is determined sequentially by the DMRS sequence index in ascending order, the orthogonal code index in ascending order, and the DMRS port index in ascending order.

24. A data transmission method, characterized in that, include: Receive uplink data transmitted based on uplink data transmission resources, wherein the uplink data transmission resources include: physical random access channel (PRACH) resources and / or physical uplink shared channel (PUSCH) resources; The uplink data transmission resources are determined based on a mapping relationship, wherein the mapping relationship includes at least one of the following: Mapping relationship between PRACH resources and Synchronization Signal-Physical Broadcast Channel Block (SSB); Mapping relationship between PUSCH resources and SSB; Mapping relationship between PRACH and PUSCH resources.

25. A data transmission system, characterized in that, Includes terminal equipment and at least one network device; The terminal device is used to: determine uplink data transmission resources according to the mapping relationship; and send uplink data based on the uplink data transmission resources; The network device is used to: receive the uplink data; The uplink data transmission resources include physical random access channel (PRACH) resources and / or physical uplink shared channel (PUSCH) resources. The mapping relationship includes at least one of the following: Mapping relationship between PRACH resources and Synchronization Signal-Physical Broadcast Channel Block (SSB); Mapping relationship between PUSCH resources and SSB; Mapping relationship between PRACH and PUSCH resources.

26. A data transmission device, characterized in that, include: Includes processor, memory, and communication interface; The memory is used to store programs or instructions; The communication interface is used to receive signals from other data transmission devices and transmit them to the processor, or to send signals from the processor to other data transmission devices. The processor is used to execute the program or instructions to enable the data transmission device to implement the data transmission method as described in any one of claims 1 to 24.

27. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the data transmission method as described in any one of claims 1 to 24.

28. A computer program product, characterized in that, Includes a computer program that, when run, causes a computer to perform the data transmission method as described in any one of claims 1 to 24.