Mapping method, terminal device, and network-side device

Abstract

This disclosure provides a mapping method, a terminal device, and a network-side device. The method includes: transmitting (201) a random access message based on a target mapping relationship between physical uplink shared channel PUSCH resources and synchronization signal block SSB-related resources, where the target mapping relationship is determined according to a preset mapping rule.

Description

Mapping methods, terminal devices and network-side devices

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 201910253397.8, filed in China on March 29, 2019, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to the field of communication technology, and in particular to a mapping method, terminal equipment, and network-side equipment. Background Technology

[0004] Fifth-generation (5G) mobile communication systems, also known as New Radio (NR) systems, need to adapt to diverse scenarios and service requirements. The main scenarios for NR systems include enhanced Mobile Broadband (eMBB) communication, massive Machine Type Communications (mMTC) communication, and Ultra-Reliable and Low Latency Communications (URLLC). These scenarios place demands on the system to achieve high reliability, low latency, high bandwidth, and wide coverage. For periodic services with fixed packet sizes, network equipment can employ semi-static scheduling to continuously allocate resources for the transmission of periodic services in order to reduce downlink control signaling overhead.

[0005] In uplink transmission mode, if a terminal needs to send uplink data, it must first obtain uplink timing synchronization through a random access procedure, that is, obtain uplink timing advance (TA) information from the network device. After obtaining uplink synchronization, the terminal can send uplink data through dynamic scheduling or semi-static scheduling. When the uplink data packet is small, in order to reduce resource and power consumption, the terminal can send uplink data in an asynchronous state.

[0006] During random access procedures, whether non-contention-based or contention-based, terminals are also in an asynchronous state when sending preambles. A cyclic prefix (CP) needs to be added to the preamble to offset the effects of transmission delay, and a guard interval exists between different terminals to reduce interference.

[0007] When a terminal transmits uplink data in an asynchronous state, such as when it transmits on the Physical Uplink Shared Channel (PUSCH) in an asynchronous state, during the non-contention-free random access process, i.e., in the 2-step Physical Random Access Channel (PRACH), the terminal sends a random access message carrying the PUSCH, also known as message A (msgA), when initiating random access. In this case, the msgA received by the network device corresponds to both the PRACH and PUSCH. The network device needs to perform blind detection on all possible PRACH and PUSCH transmission locations, resulting in high processing complexity.

[0008] Summary of the Invention

[0009] Some embodiments of this disclosure provide a mapping method, a terminal device, and a network-side device to address the problem of high processing complexity of network devices during random access in related technologies.

[0010] To solve the above-mentioned technical problems, this disclosure is implemented as follows:

[0011] In a first aspect, some embodiments of this disclosure provide a mapping method applied to a terminal device, the method comprising:

[0012] Based on the target mapping relationship between the Physical Uplink Shared Channel (PUSCH) resources and the Synchronization Signal Block (SSB) related resources, a random access message is sent.

[0013] The target mapping relationship is determined according to a preset mapping rule.

[0014] Secondly, some embodiments of this disclosure also provide a mapping method applied to a network-side device, the method comprising:

[0015] Based on the target mapping relationship between the Physical Uplink Shared Channel (PUSCH) resources and the Synchronization Signal Block (SSB) related resources, receive random access messages;

[0016] The target mapping relationship is determined according to a preset mapping rule.

[0017] Thirdly, some embodiments of this disclosure also provide a terminal device. The terminal device includes:

[0018] The sending module is used to send random access messages based on the target mapping relationship between the Physical Uplink Shared Channel (PUSCH) resources and the Synchronization Signal Block (SSB) related resources;

[0019] The target mapping relationship is determined according to a preset mapping rule.

[0020] Fourthly, some embodiments of this disclosure also provide a network-side device. This network-side device includes:

[0021] The receiving module is used to receive random access messages based on the target mapping relationship between the Physical Uplink Shared Channel (PUSCH) resources and the Synchronization Signal Block (SSB) related resources;

[0022] The target mapping relationship is determined according to a preset mapping rule.

[0023] Fifthly, some embodiments of this disclosure also provide a terminal device, including a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the mapping method provided in the first aspect above.

[0024] In a sixth aspect, some embodiments of this disclosure also provide a network-side device, including a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the mapping method provided in the second aspect above.

[0025] In a seventh aspect, some embodiments of this disclosure also provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the mapping method provided in the first aspect or the steps of the mapping method provided in the second aspect.

[0026] In some embodiments of this disclosure, random access messages are sent based on a target mapping relationship between Physical Uplink Shared Channel (PUSCH) resources and Synchronization Signal Block (SSB) related resources; wherein the target mapping relationship is determined according to a preset mapping rule. This avoids blind detection of transmission positions on all possible SSB-related resources and PUSCH resources, thereby reducing processing complexity. Attached Figure Description

[0027] To more clearly illustrate the technical solutions of some embodiments of this disclosure, the accompanying drawings used in the description of some embodiments of this disclosure will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0028] Figure 1 is a structural diagram of a network system to which some embodiments of this disclosure can be applied;

[0029] Figure 2 is a flowchart of a mapping method provided in some embodiments of this disclosure;

[0030] Figure 3a is one of the schematic diagrams showing the mapping relationship between PUSCH resource units and PRACH resource units provided in some embodiments of this disclosure;

[0031] Figure 3b is a second schematic diagram of the mapping relationship between PUSCH resource units and PRACH resource units provided in some embodiments of this disclosure;

[0032] Figure 4a is a third schematic diagram of the mapping relationship between PUSCH resource units and PRACH resource units provided in some embodiments of this disclosure;

[0033] Figure 4b is a schematic diagram of the mapping relationship between PUSCH resource units and PRACH resource units provided in some embodiments of this disclosure;

[0034] Figure 5a is one of the schematic diagrams showing the mapping relationship between PUSCH resource units and SSBs provided in some embodiments of this disclosure;

[0035] Figure 5b is a second schematic diagram of the mapping relationship between PUSCH resource units and SSBs provided in some embodiments of this disclosure;

[0036] Figure 6a is a third schematic diagram of the mapping relationship between PUSCH resource units and SSBs provided in some embodiments of this disclosure;

[0037] Figure 6b is a fourth schematic diagram of the mapping relationship between PUSCH resource units and SSBs provided in some embodiments of this disclosure;

[0038] Figure 7 is a flowchart of a mapping method provided in some embodiments of this disclosure;

[0039] Figure 8 is the fifth of several schematic diagrams illustrating the mapping relationship between PUSCH resource units and PRACH resource units provided in some embodiments of this disclosure;

[0040] Figure 9 is a sixth schematic diagram illustrating the mapping relationship between PUSCH resource units and PRACH resource units provided in some embodiments of this disclosure;

[0041] Figure 10 is the seventh of several schematic diagrams illustrating the mapping relationship between PUSCH resource units and PRACH resource units provided in some embodiments of this disclosure;

[0042] Figure 11 is a schematic diagram (eighth) of the mapping relationship between PUSCH resource units and PRACH resource units provided in some embodiments of this disclosure;

[0043] Figure 12 is a schematic diagram (9) illustrating the mapping relationship between PUSCH resource units and PRACH resource units provided in some embodiments of this disclosure;

[0044] Figure 13 is a schematic diagram of the mapping relationship between PUSCH resource units and PRACH resource units provided in some embodiments of this disclosure;

[0045] Figure 14 is an eleventh schematic diagram of the mapping relationship between PUSCH resource units and PRACH resource units provided in some embodiments of this disclosure;

[0046] Figure 15 is a schematic diagram, number 12, illustrating the mapping relationship between PUSCH resource units and PRACH resource units provided in some embodiments of this disclosure.

[0047] Figure 16 is a structural diagram of a terminal device provided in some embodiments of this disclosure;

[0048] Figure 17 is a structural diagram of a network-side device provided in some embodiments of this disclosure;

[0049] Figure 18 is a structural diagram of a terminal device provided in some embodiments of this disclosure;

[0050] Figure 19 is a structural diagram of a network-side device provided in some embodiments of this disclosure. Detailed Implementation

[0051] The technical solutions of some embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0052] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus. The terms "and / or" in the specification and claims indicate at least one of the connected objects.

[0053] Some embodiments of this disclosure provide a mapping method. Referring to Figure 1, Figure 1 is a structural diagram of a network system to which some embodiments of this disclosure can be applied. As shown in Figure 1, it includes a terminal device 11 and a network-side device 12. The terminal device 11 can be a user-side device such as a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), mobile internet device (MID), or wearable device. It should be noted that some embodiments of this disclosure do not limit the specific type of the terminal device 11. Network-side device 12 can be a base station, such as a macro station, a Long Term Evolution (LTE) base station (eNB), a 5G NR base station (NodeB, NB), or a next-generation base station (gNB). Network-side device 12 can also be a small cell, such as a Low Power Node (LPN), pico, or femto cell, or an Access Point (AP). A base station can also be a network node composed of a Central Unit (CU) and multiple Transmission Reception Points (TRPs) that it manages and controls. It should be noted that the specific type of network-side device 12 is not limited in some embodiments of this disclosure.

[0054] In some embodiments of this disclosure, the terminal device 11 can establish a target mapping relationship between Physical Uplink Shared Channel (PUSCH) resources and Synchronous Signal Block (SSB) related resources according to a preset mapping rule.

[0055] The aforementioned PUSCH resources may include Physical Uplink Shared Channel Occasion (PUO) and / or Physical Uplink Control Channel (PUCCH) resource elements of the PUO. The aforementioned SSB-related resources may include SSB and / or the Physical Random Access Channel (PRACH) resource elements corresponding to the SSB.

[0056] Furthermore, the terminal device 11 can send random access messages on random access resources based on the above target mapping relationship, wherein the random access resources may include PUSCH resources and SSB-related resources.

[0057] Network-side device 12 can also establish a target mapping relationship between PUSCH resources and SSB-related resources according to a preset mapping rule. Then, it can determine the transmission location of PUSCH resources and SSB-related resources based on the above target mapping relationship, thereby avoiding blind detection of the transmission locations of all possible SSB-related resources and PUSCH resources, thus reducing processing complexity and improving processing efficiency.

[0058] The mapping methods provided by some embodiments of this disclosure are described in detail below:

[0059] Some embodiments of this disclosure provide a mapping method applied to a terminal device. Referring to Figure 2, which is a flowchart of a mapping method provided by some embodiments of this disclosure, the method includes the following steps:

[0060] Step 201: Send a random access message based on the target mapping relationship between the Physical Uplink Shared Channel (PUSCH) resources and the Synchronization Signal Block (SSB) related resources;

[0061] The target mapping relationship is determined according to a preset mapping rule.

[0062] In some embodiments of this disclosure, the aforementioned PUSCH resources may include at least one of the PUO and the PUCCH resource unit of the PUO. The aforementioned PUCCH resource unit may include, but is not limited to, one or more of the following: PUSCH time-domain resources, PUSCH frequency-domain resources, Demodulation Reference Signal (DMRS) port, DMRS sequence, DMRS scrambling ID, and PUSCH scrambling ID.

[0063] The aforementioned SSB-related resources may include at least one of the SSB and its corresponding PRACH resource element. The aforementioned PRACH resource element may include, but is not limited to, at least one of the Physical Random Access Channel Occasion (RO) and preamble.

[0064] The aforementioned preset mapping rules may include one or more mapping rules. For example, the aforementioned preset mapping rules may include a first mapping rule, wherein the first mapping rule is used to determine the mapping relationship between PUSCH resources and PRACH resource units corresponding to SSBs; or the aforementioned preset mapping rules may include a second mapping rule, wherein the second mapping rule is used to determine the mapping relationship between PUSCH resources and SSBs; or the aforementioned preset mapping rules may include both the first mapping rule and the second mapping rule, in which case the mapping relationship between PUSCH resources and PRACH resource units corresponding to SSBs can be determined according to the first mapping rule, and the mapping relationship between PUSCH resources and SSBs can be determined according to the second mapping rule.

[0065] In some embodiments of this disclosure, after determining the target mapping relationship, the terminal device can send random access messages based on the target mapping relationship. The network side can determine the transmission positions on PUSCH resources and SSB-related resources based on the aforementioned target mapping relationship, or determine the transmission positions on SSB-related resources based on the transmission positions on PUSCH resources, or determine the transmission positions on PUSCH resources based on the transmission positions on SSB-related resources. This avoids blind detection of all possible transmission positions on SSB-related resources and PUSCH resources, thereby reducing processing complexity and improving processing efficiency.

[0066] Optionally, the preset mapping rule includes at least one of the following:

[0067] The first mapping rule is used to determine the mapping relationship between the PUSCH resource element and SSB of the Physical Uplink Shared Channel Transmission Opportunity (PUO).

[0068] The second mapping rule, wherein the first mapping rule is used to determine the mapping relationship between the PUSCH resource element of the PUO and the physical random access channel PRACH resource element corresponding to the SSB.

[0069] The following examples illustrate this:

[0070] Method 1: Configure only the first mapping rule mentioned above. In this way, the terminal side can determine the mapping relationship between PUSCH resources and PRACH resource units corresponding to SSB according to the first mapping rule mentioned above, and can send random access messages based on the mapping relationship.

[0071] Method 2: Configure only the second mapping rule mentioned above. In this way, the terminal side can determine the mapping relationship between PUSCH resources and SSB according to the second mapping rule mentioned above, and can send random access messages based on the mapping relationship.

[0072] Method 3: Configure both the first and second mapping rules mentioned above. This way, the terminal side can determine the mapping relationship between the PUSCH resource and the PRACH resource unit corresponding to the SSB according to the first mapping rule when there is an association between the PUSCH resource unit and the PRACH resource unit corresponding to the SSB; and determine the mapping relationship between the PUSCH resource and the SSB according to the second mapping rule when there is no association between the PUSCH resource unit and the PRACH resource unit corresponding to the SSB.

[0073] It should be noted that, when the first mapping rule and the second mapping rule are configured at the same time, the terminal side can also determine the mapping relationship between PUSCH resources and PRACH resource units corresponding to SSB according to the first mapping rule, and determine the mapping relationship between PUSCH resources and SSB according to the second mapping rule, and can send random access messages based on the two mapping relationships.

[0074] Optionally, the first mapping rule includes one of the following:

[0075] The PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB.

[0076] The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource units.

[0077] In practical applications, PUOs, PUSCH resource units, SSBs, and PRACH resource units can be numbered based on the number of PUOs, the number of PUSCH resource units in each PUO, the number of SSBs, and the number of PRACH resource units associated with each SSB.

[0078] In some embodiments of this disclosure, mapping between PUSCH resource units and PRACH resource units can be performed according to the numbering order of PUOs, the numbering order of PUSCH resource units, the numbering order of PRACH resource units, and the numbering order of SSBs.

[0079] For example, as shown in Figures 3a and 3b, for a PRACH resource unit of a PUO, each PUSCH resource unit of the PUO can be mapped to the corresponding PRACH resource unit of the SSB based on the numbering order of the PRACH resource units and the numbering order of the SSBs; or, for a PRACH resource unit corresponding to an SSB, the PRACH resource unit corresponding to the SSB can be mapped to the PUSCH resource unit of the PUO based on the numbering order of the PUSCH resource units and the numbering order of the PUOs.

[0080] For example, as shown in Figures 4a and 4b, for a PRACH resource unit of a PUO, each PUSCH resource unit of the PUO can be mapped sequentially to PRACH resource units corresponding to multiple SSBs based on the numbering order of the PRACH resource units and the numbering order of the SSBs. Optionally, the SSB is an SSB contained in an SSB group; or, for a PRACH resource unit corresponding to an SSB, the PUSCH resource unit corresponding to the SSB can be mapped sequentially to PUSCH resource units of multiple PUOs based on the numbering order of the PUSCH resource units and the numbering order of the PUOs.

[0081] It should be noted that PUSCH resource units and PRACH resource units can be mapped in an interleaved or non-interleaved manner. PUSCH resource units and SSBs can also be mapped in an interleaved or non-interleaved manner.

[0082] Optionally, the PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB, which may include:

[0083] The PUSCH resource units of the PUO are mapped to the PRACH resource units corresponding to I SSBs in the order of their PRACH resource unit numbers, and to N SSBs in the order of their SSB numbers; where I and N are both positive integers, and I is less than or equal to N.

[0084] In some embodiments of this disclosure, the I or N mentioned above may represent, but is not limited to, the following: the number of SSBs included in an SSB period; the number of SSBs associated with a PUO; the number of SSBs included in an SSB group; the number of SSBs in an associated period. The I mentioned above may be a positive integer less than or equal to N.

[0085] In practical applications, the N SSBs can be grouped. This allows the PUSCH resource units of a PUO to be mapped to the corresponding PRACH resource units of each group's SSBs according to their PRACH resource unit numbering order, and then further mapped to the N SSBs according to their SSB numbering order. In this mapping relationship, one or more PUO PUSCH resource units can be associated with the PRACH resource units corresponding to the SSBs of a group. Optionally, after all PUO PUSCH resource units are associated with the PRACH resource units corresponding to the SSBs of a group, they can then be associated with the PRACH resource units corresponding to the SSBs of other SSB groups.

[0086] The PUSCH resource units of the PUO are mapped to the PRACH resource units corresponding to I SSBs in the order of their PRACH resource unit numbers, and to N SSBs in the order of their SSB numbers. The PUSCH resource units can be mapped to the PRACH resource units corresponding to the I SSBs in an interleaved manner. Optionally, the mapping interval V of the SSBs is greater than or equal to 1; or the PUSCH resource units can be mapped to the PRACH resource units corresponding to the I SSBs in a non-interleaved manner, and the mapping interval V of the SSBs is 0.

[0087] For example, the configuration may contain the following information: one PUO is associated with N1 SSBs, where N1 ≤ N tx , where N tx This refers to the number of SSBs transmitted by the network side in each cycle. For a PUO, M1 PRACH resource units in the PRACH resource units corresponding to each associated SSB are associated with the PUCCH resource units of that PUO, where M1 is less than or equal to the total number of PRACH resource units corresponding to each SSB. Thus, a mapping relationship can be generated based on the above mapping rules and configuration information. In this embodiment, the number of PUSCH resource units of a PUO is K, which can be directly configured by the network or determined according to the configuration information.

[0088] For example, the following information is configured: 4 SSBs (SSB 0 to SSB 3) are associated with 1 PRACH Occasion (RO 0), and one SSB corresponds to 4 preambles. The number of SSBs associated with one PUO is 4. In this embodiment, the PUSCH resource unit is DMRS, the number of PUSCH resource units included in one PUO is 8, and the PRACH resource unit is the preamble. For one PUO, 2 preambles in the preambles corresponding to each SSB are associated with the DMRS of this PUO. Thus, based on the above configuration information, the PUSCH resource units of PUO 0 can be first mapped to the PRACH resource units corresponding to one SSB in the order of the numbers of the PRACH resource units, and then mapped to 4 SSBs in the order of the numbers of the SSBs, and the mapping relationship as shown in FIG. 3a can be obtained. Among them, the PUSCH resource units can be mapped to the PRACH resource units corresponding to the 4 SSBs in a non-interleaved manner, and the mapping interval V of the SSB is 0; for another example, based on the above configuration information, the PUSCH resource units of PUO 0 can be first mapped to the PRACH resource units corresponding to one SSB in the order of the numbers of the PRACH resource units, and then mapped to 4 SSBs in the order of the numbers of the SSBs, and the mapping relationship as shown in FIG. 3b can be obtained. Among them, the PUSCH resource units can be mapped to the PRACH resource units corresponding to the 4 SSBs in an interleaved manner, and the mapping interval V of the SSB = 1.

[0089] It should be noted that if N1*M1>K, then some of the PRACH resource units corresponding to one SSB are not associated with any PUSCH resource units. If N1*M1<K, then some of the PUSCH resource units in one PUO are not associated with any PRACH resource units and SSBs.

[0090] For example, the following information is configured: configure the number N1 of SSBs associated with each PUO, where N1≤N tx , optionally, N tx SSBs are correspondingly grouped, and the number of SSBs in each SSB group is N1. The number N2 of PUOs associated with each SSB. Thus, the mapping relationship can be generated based on the above configuration information and mapping rules. It should be noted that different PUOs are not limited to associating with different SSBs, which specifically depends on the number of PRACH resource units. In this embodiment, the number of PUSCH resource units of one PUO is K, and K can be directly configured by the network or determined according to the configuration information.

[0091] For example, the configuration includes the following information: 1 PUO is associated with 4 SSBs (SSB 0 to SSB 3), 1 SSB is associated with 2 PUOs (PUO 0 to PUO 1), that is, 2 PUOs are associated with 4 SSBs, and one SSB corresponds to 4 Preambles; the PUSCH resource unit is DMRS, the PRACH resource unit is a preamble, and the number of DMRSs for one PUSCH Occasion is 8.

[0092] Based on the above configuration information, the PUSCH resource units of the two PUOs, PUO 0 and PUO 1 can be mapped to the PRACH resource units corresponding to the four SSBs of one SSB group according to the PRACH resource unit numbering order, and then mapped to all SSBs according to the SSB numbering order.

[0093] Specifically, the PUSCH resource units of PUO 0 are first mapped to the PRACH resource units corresponding to one SSB according to the PRACH resource unit numbering order, and then mapped to four SSBs according to the SSB numbering order. Similarly, the PUSCH resource units of PUO 1 are first mapped to the PRACH resource units corresponding to one SSB according to the PRACH resource unit numbering order, and then mapped to four SSBs according to the SSB numbering order. The mapping relationship shown in Figure 4a can be obtained. In this case, the PUSCH resource units can be mapped to the PRACH resource units corresponding to the four SSBs in a non-interleaved manner, and the mapping interval V of the SSBs is 0.

[0094] For example, based on the above configuration information, the PUSCH resource units of 2 PUOs, PUO 0 and PUO 1 are mapped to the PRACH resource units corresponding to the 4 SSBs of 1 SSB group according to the PRACH resource unit numbering order, and then mapped to all SSBs according to the SSB numbering order.

[0095] Specifically, the PUSCH resource units of PUO 0 are first mapped to the PRACH resource units corresponding to one SSB according to their PRACH resource unit numbering order, and then mapped to four SSBs according to their SSB numbering order. Similarly, the PUSCH resource units of PUO 1 are first mapped to the PRACH resource units corresponding to one SSB according to their PRACH resource unit numbering order, and then mapped to four SSBs according to their SSB numbering order. This results in the mapping relationship shown in Figure 4b. In this mapping, the PUSCH resource units can be interleaved with the four SSBs and mapped to the PRACH resource units corresponding to those four SSBs. The mapping interval of the SSBs is V = 1.

[0096] Optionally, mapping the PRACH resource units corresponding to the SSB to the PUSCH resource units of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource units may include:

[0097] The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of J PUOs according to the numbering order of the PUSCH resource units, and to the PUSCH resource units of M PUOs according to the numbering order of the PUOs; where J and M are both positive integers, and J is less than or equal to M.

[0098] In some embodiments of this disclosure, J or M may represent, but is not limited to, the following: the number of PUOs included in a PUO cycle, or the number of PUOs in an associated cycle. J is a positive integer less than or equal to M.

[0099] In practical applications, the M PUOs can be grouped. The PRACH resource units corresponding to the SSBs can then be mapped to the PUSCH resource units of the PUOs in each group according to their PUSCH resource unit numbering order, and then further mapped to the M PUOs according to their PUSCH resource unit numbering order. In this mapping relationship, the PRACH resource units of one or more SSBs can be associated with the PUSCH resource units corresponding to the PUOs in a group. Optionally, after all the PRACH resource units corresponding to the SSBs have been associated with the PUSCH resource units corresponding to the PUOs in a group, they can then be associated with the PUSCH resource units corresponding to the PUOs in other PUO groups.

[0100] The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of J PUOs according to their PUSCH resource unit numbering order, and then mapped to M PUOs according to their PUO numbering order. The PRACH resource units corresponding to the SSB can be mapped to the PUSCH resource units of the J PUOs in an interleaved manner, optionally with a mapping interval L greater than 1; or the PRACH resource units corresponding to the SSB can be mapped to the PUSCH resource units of the J PUOs in a non-interleaved manner, optionally with a mapping interval L of 1. Optionally, the PRACH resource units corresponding to the SSB can be mapped to the PUSCH resource units of the J PUOs according to their PUSCH resource unit numbering order, then mapped to multiple frequency-multiplexed PUOs according to their frequency domain numbering order, and then mapped to multiple time-multiplexed PUOs according to their time domain numbering order.

[0101] Specifically, for the PRACH resource units corresponding to SSBs, mapping is performed first to PUSCH resource units, then to POOs according to their numbering order. That is, the PRACH resource units corresponding to SSBs are first mapped to the PUSCH resource units of a group of POOs according to their numbering order, and then mapped to M POOs according to their numbering order.

[0102] For example, the configuration may contain the following information: one PUO is associated with N1 SSBs, where N1 ≤ N tx , where N tx This refers to the number of SSBs transmitted by the network side in each cycle. For a PUO, M1 PRACH resource units in the PRACH resource units corresponding to each associated SSB are associated with the PUCCH resource units of that PUO, where M1 is less than or equal to the total number of PRACH resource units corresponding to each SSB. Thus, a mapping relationship can be generated based on the above mapping rules and configuration information. In this embodiment, the number of PUSCH resource units of a PUO is K, which can be directly configured by the network or determined according to the configuration information.

[0103] For another example, the following information is configured: 4 SSBs (SSB 0 to SSB 3) are associated with 1 PRACH Occasion (RO 0), and one SSB corresponds to 4 preambles. The number of SSBs associated with one PUO is 4. In this embodiment, the PUSCH resource unit is DMRS, the number of PUSCH resource units included in one PUO is 8, and the PRACH resource unit is the preamble. For one PUO, 2 preambles in the preambles corresponding to each SSB are associated with the DMRS of this PUSCH Occasion. Thus, based on the above configuration information, the PRACH resource units corresponding to the SSBs are first mapped to the PUSCH resource units of one PUO in the numbering order of the PUSCH resource units, and then mapped to M PUOs in the numbering order of the PUOs, and the mapping relationship shown in FIG. 3a can be obtained. Among them, the PRACH resource units corresponding to the SSBs can be mapped to the PUSCH resource units of this one PUO in a non-interleaved manner with the PUSCH resource units of one PUO. Optionally, the mapping interval L of the PUSCH resource units is 1; for another example, based on the above configuration information, the PRACH resource units corresponding to the SSBs are first mapped to the PUSCH resource units of one PUO in the numbering order of the PUSCH resource units, and then mapped to M PUOs in the numbering order of the PUOs, and the mapping relationship shown in FIG. 3b can be obtained. Among them, the PRACH resource units corresponding to the SSBs can be mapped to the PUSCH resource units of this one PUO in an interleaved manner with the PUSCH resource units of one PUO. Optionally, the mapping interval L of the PUSCH resource units is 4.

[0104] It should be noted that if N1*M1>K, then some of the PRACH resource units corresponding to one SSB are not associated with any PUSCH resource units. If N1*M1<K, then some of the PUSCH resource units in one PUO are not associated with any PRACH resource units and SSBs.

[0105] For example, the following information is configured: the number of SSBs N1 associated with each PUO is configured, and N1≤N tx , optionally, N tx [[ID=z10]]The N SSBs are correspondingly grouped, and the number of SSBs in each SSB group is N1. The number of PUOs N2 associated with each SSB. Thus, the mapping relationship can be generated based on the above configuration information and mapping rules. It should be noted that different PUOs are not limited to associating with different SSBs, which specifically depends on the number of PRACH resource units. In this embodiment, the number of PUSCH resource units of one PUO is K, and K can be directly configured by the network or determined according to the configuration information.

[0106] For example, the configuration includes the following information: 1 PUO is associated with 4 SSBs (SSB 0 to SSB 3), 1 SSB is associated with 2 PUOs (PUO 0 to PUO 1), that is, 2 PUOs are associated with 4 SSBs, and one SSB corresponds to 4 Preambles; the PUSCH resource unit is DMRS, the PRACH resource unit is a preamble, and the number of DMRSs for one PUSCH Occasion is 8.

[0107] Optionally, based on the above configuration information, the PRACH resource units corresponding to the four SSBs in one SSB group can be mapped to the PUSCH resource units of two PUOs according to the PUSCH resource unit numbering order, and then mapped to all PUOs according to the PUO numbering order.

[0108] For example, the PRACH resource unit corresponding to SSB 0 can be mapped to the PUSCH resource unit of one PUO according to the PUSCH resource unit numbering order, and then mapped to two PUOs according to the PUO numbering order. Similarly, the PRACH resource unit corresponding to SSB 1 can be mapped to the PUSCH resource unit of one PUO according to the PUSCH resource unit numbering order, and then mapped to two PUOs according to the PUO numbering order. For SSB 2 and SSB 3, the mapping relationship shown in Figure 4a can be obtained. Here, the PRACH resource unit corresponding to an SSB can be mapped to the PUSCH resource unit of a PUO in a non-interleaved manner. Optionally, the mapping interval L of the PUSCH resource units is 1.

[0109] Optionally, based on the above configuration information, the PRACH resource units corresponding to the four SSBs in one SSB group can be mapped to the PUSCH resource units of two PUOs according to the PUSCH resource unit numbering order, and then mapped to all PUOs according to the PUO numbering order.

[0110] For example, the PRACH resource unit corresponding to SSB 0 is first mapped to the PUSCH resource unit of one PUO according to the PUSCH resource unit numbering order, and then mapped to two PUOs according to the PUO numbering order. Similarly, the PRACH resource unit corresponding to SSB 1 is first mapped to the PUSCH resource unit of one PUO according to the PUSCH resource unit numbering order, and then mapped to two PUOs according to the PUO numbering order. For SSB 2 and SSB 3, the details are not elaborated here. The mapping relationship shown in Figure 4b can be obtained, where the PRACH resource unit corresponding to an SSB can be interleaved with the PUSCH resource unit of a PUO and mapped to the PUSCH resource unit of that PUO. Optionally, the mapping interval L of the PUSCH resource units is 4.

[0111] Optionally, the second mapping rule may include:

[0112] SSB maps to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO.

[0113] In some embodiments of this disclosure, the mapping between PUSCH resource units and SSBs can be performed according to the numbering order of PUOs, the numbering order of PUSCH resource units, and the numbering order of SSBs.

[0114] For example, based on the numbering order of PRACH resource units and SSBs, each SSB can be mapped to its corresponding PRACH resource unit in sequence, as shown in Figures 5a and 5b.

[0115] It should be noted that PUSCH resource units and SSBs can be mapped in an interleaved manner or in a non-interleaved manner.

[0116] Optionally, the SSB is mapped to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO, which may include:

[0117] SSB maps to the PUSCH resource units of a PUO according to the numbering order of the PUSCH resource units, and maps to P PUOs according to the numbering order of the PUOs; where P is a positive integer.

[0118] In some embodiments of this disclosure, P may represent, but is not limited to, the following: the number of PUOs included in a PUO cycle; the number of PUOs in an associated cycle.

[0119] For example, the configuration may contain the following information: one PUO is associated with N1 SSBs, where N1 ≤ N tx , where N txThis refers to the number of SSBs sent by the network side in each cycle. For a PUO, one SSB is associated with M2 PUSCH resource units. Therefore, a mapping relationship can be generated based on the above mapping rules and configuration information. In this embodiment, the number of PUSCH resource units in a PUO is K, where K can be directly configured by the network or determined according to the configuration information.

[0120] For example, the following information is configured: the number of SSBs associated with a PUO is 4, and for a PUO, the number of PUSCH resource units associated with each SSB is 2. In this embodiment, 4 SSBs (SSB 0 to SSB 3) are associated with PUO 0, the PUSCH resource unit is DMRS, and the number of PUSCH resource units contained in a PUO is 8.

[0121] Optionally, based on the above configuration information, the SSB can be first mapped to a PUSCH resource unit of a PUO according to the PUSCH resource unit numbering order, and then mapped to M PUOs according to the PUO numbering order, resulting in the mapping relationship shown in Figure 5a. Here, the SSB can be interleaved with the PUSCH resource units of a PUO and mapped to those PUOs in an interleaved manner. Optionally, the mapping interval L of the PUSCH resource units is 4.

[0122] Optionally, based on the above configuration information, the SSB can be first mapped to a PUSCH resource unit of a PUO according to the PUSCH resource unit numbering order, and then mapped to M PUOs according to the PUO numbering order, resulting in the mapping relationship shown in Figure 5b. Here, the SSB can be mapped to a PUO's PUSCH resource unit in a non-interleaved manner. Optionally, the mapping interval L of the PUSCH resource units is 1.

[0123] Optionally, configure the number of SSBs N1 associated with each PUO, where N1 ≤ N tx Optional, N tx The SSBs were grouped accordingly, and the number of SSBs in each SSB group was N1. In this embodiment, the number of SSBs in each SSB group was 4.

[0124] Optionally, a PUCCH resource unit can be associated with an SSB.

[0125] In some embodiments of this disclosure, each PUCCH resource unit may be associated with an SSB.

[0126] Furthermore, two adjacent PUSCH resource units can be associated with the same SSB. For example, PUSCH resource unit k is associated with SSB n, and PUSCH resource unit k+1 is associated with SSB n, as shown in Figure 6a. Two adjacent PUSCH resource units can also be associated with different SSBs. For example, PUSCH resource unit k is associated with SSB n, and PUSCH resource unit k+1 is associated with SSB n+1, as shown in Figure 6b.

[0127] Optionally, PUSCH resource units can be interleaved or non-interleaved with SSBs;

[0128] or

[0129] PUSCH resource units can be interleaved or non-interleaved with the corresponding PRACH resource units of SSB.

[0130] Optionally, before sending the random access message based on the target mapping relationship between the Physical Uplink Shared Channel (PUSCH) resources and the Synchronization Signal Block (SSB) related resources, the method may further include:

[0131] In the presence of first configuration information, a mapping relationship between the PUSCH resource unit of PUO and SSB is established according to the first mapping rule, wherein the first configuration information is used to indicate that there is an association between the PUSCH resource unit and the PRACH resource unit corresponding to the SSB;

[0132] Otherwise, according to the second mapping rule, establish the mapping relationship between the PUSCH resource unit of the PUO and the physical random access channel PRACH resource unit corresponding to the SSB.

[0133] In some embodiments of this disclosure, the first configuration information described above may explicitly or implicitly indicate that the PUSCH resource unit and the PRACH resource unit corresponding to the SSB are associated. For example, the first configuration information may carry an identification information for indicating that the PUSCH resource unit and the PRACH resource unit corresponding to the SSB are associated, or the first configuration information may carry a parameter through which the association between the PUSCH resource unit and the PRACH resource unit corresponding to the SSB can be indirectly obtained.

[0134] Specifically, in some embodiments of this disclosure, if there is an association between the PUSCH resource unit and the PRACH resource unit corresponding to the SSB, the mapping relationship between the PUSCH resource unit of the PUO and the PRACH resource unit corresponding to the SSB can be established solely according to the second mapping rule; otherwise, the mapping relationship between the PUSCH resource unit of the PUO and the PRACH resource unit corresponding to the SSB can be determined based on the second mapping rule.

[0135] It should be noted that the relevant content of the first mapping rule in this embodiment can be found in the aforementioned description of the first mapping rule, and the relevant content of the second mapping rule in this embodiment can be found in the aforementioned description of the second mapping rule, and will not be repeated here.

[0136] Optionally, the mapping parameters of the target mapping relationship are determined by configuration information, wherein the configuration information may include at least one of the following:

[0137] A PUO-associated SSB parameter, wherein the SSB parameter includes the number of SSBs or the set of SSBs;

[0138] The number of PUSCH resource units in a PUO;

[0139] A target SSB is associated with Q PRACH resource units and a PUO's PUSCH resource unit, where the target SSB is the SSB corresponding to the PUO and Q is a positive integer;

[0140] The mapping interval L of the PUSCH resource unit, where L is greater than or equal to 1;

[0141] The mapping interval V of SSB is greater than or equal to 0;

[0142] A PUO parameter associated with an SSB, wherein the PUO parameter includes at least one of the following: the time domain resource of the PUO, the frequency domain resource of the PUO, the number of PUOs, and the PUO number;

[0143] A PRACH resource unit parameter associated with a PUSCH resource unit in a PUO, wherein the PRACH resource unit parameter includes the number of PRACH resource units or the set of PRACH resource units;

[0144] The SSB grouping information includes at least one of the following: the SSB grouping method, the number of SSB groups, and the number of SSBs in each SSB group;

[0145] The number of PUSCH resource units associated with an SSB in a PUO.

[0146] In some embodiments of this disclosure, the above configuration information may be configured on the network side.

[0147] For the number of SSBs or SSB set associated with a PUO, if this parameter is not included in the configuration information, the number of SSBs associated with each PUO can be a default value, for example, N. tx , where N tx This refers to the number of SSBs sent by the network side in each cycle.

[0148] Optionally, when the PUSCH resource unit includes a DMRS port and a DMRS scrambling identifier, the number of PUSCH resource units of a PUO can be one of the following:

[0149] The number of DMRS ports in a PUO;

[0150] The product of the number of DMRS ports of a PUO and the number of DMRS scrambling identifiers of a PUO.

[0151] The mapping interval L of the aforementioned PUSCH resource units can refer to the interval between the PUSCH resource unit numbers associated with two consecutive PUSCH resource units when the PRACH resource unit corresponding to the SSB is associated with a PUSCH resource unit. Specifically, if the interval L is 1, the PUSCH resource unit and the PRACH resource unit corresponding to the SSB are non-interlace (or non-interleave) mapped; if the interval L > 1, the PUSCH resource unit and the PRACH resource unit corresponding to the SSB are interlace (or interleave) mapped.

[0152] Optionally, when L=1, the PUSCH resource unit is non-interleaved with the SSB, or the PUSCH resource unit is non-interleaved with the PRACH resource unit corresponding to the SSB.

[0153] When L>1, the PUSCH resource unit is interleaved with the SSB, or the PUSCH resource unit is interleaved with the PRACH resource unit corresponding to the SSB.

[0154] The mapping interval V of the SSB mentioned above can refer to the interval between the SSB numbers associated with two consecutive PUSCH resource units when a PUSCH resource unit of a PUO is associated with a PRACH resource unit corresponding to the SSB. Specifically, if the mapping interval V of the SSB is 0, then the mapping between the SSB and the PUSCH resource unit is a non-interleaved mapping; if the mapping interval V of the SSB is greater than 0, then the mapping between the SSB and the PUSCH resource unit is an interleaved mapping.

[0155] For the PRACH resource unit parameter associated with a PUSCH resource unit in a POO, if the configuration information does not include this parameter, then each PUSCH resource unit can be associated with 1 PRACH resource unit.

[0156] Regarding the above SSB grouping information, optionally, when SSB grouping is required, grouping can be performed according to at least one of the following:

[0157] The number of SSB packets is configured by the network side;

[0158] One RO corresponds to one SSB as a group;

[0159] All ROs at a given time point are grouped into one group;

[0160] All ROs within each time unit are grouped together as SSBs;

[0161] The number of configuration cycles contained in a single associated cycle.

[0162] Optionally, the PUSCH resource unit may include at least one of the following:

[0163] PUSCH's temporal resources;

[0164] PUSCH frequency domain resources;

[0165] DMRS port;

[0166] DMRS sequence;

[0167] DMRS scrambling identifier;

[0168] PUSCH scrambling identifier.

[0169] It should be noted that when a PUSCH resource unit includes the above-mentioned multiple parameters, different combinations of values ​​for these parameters represent different PUSCH resource units. For example, if a PUSCH resource unit includes a DMRS port and a DMRS scrambling identifier (i.e., scrambling ID), then DMRS port a1 and DMRS scrambling identifier b1 represent a PUSCH resource unit c1, and DMRS port a2 and DMRS scrambling identifier b1 represent a PUSCH resource unit c2.

[0170] Furthermore, when a PUSCH resource unit includes the aforementioned multiple parameters, the number of PUSCH resource units is determined by the number of each of the aforementioned multiple parameters. For example, the number of PUSCH resource units is the product of the number of each of the aforementioned multiple parameters.

[0171] For example, a PUSCH resource unit includes DMRS ports and DMRS scrambling identifiers. The number of DMRS ports is a1 and the number of DMRS scrambling identifiers is a2. Then the number of PUSCH resource units can be a1*a2.

[0172] Optionally, the network side can configure at least one of the following: the number of time-domain resources, the number of frequency-domain resources, the number of time-frequency-domain resources, the number of DMRS ports, the number of DMRS sequences, the number of DMRS Scrambling IDs, and the number of PUSCH Scrambling IDs.

[0173] Some embodiments of this disclosure provide a mapping method applied to a network-side device. Referring to Figure 7, which is a flowchart of a mapping method provided by some embodiments of this disclosure, the method includes the following steps:

[0174] Step 701: Receive random access messages based on the target mapping relationship between Physical Uplink Shared Channel (PUSCH) resources and Synchronization Signal Block (SSB) related resources;

[0175] The target mapping relationship is determined according to a preset mapping rule.

[0176] In some embodiments of this disclosure, the aforementioned PUSCH resources may include at least one of the PUO and the PUCCH resource unit of the PUO. The aforementioned PUCCH resource unit may include, but is not limited to, one or more of the following: PUSCH time-domain resources, PUSCH frequency-domain resources, DMRS port, DMRS sequence, DMRS scrambling ID, and PUSCH scrambling ID.

[0177] The aforementioned SSB-related resources may include at least one of the SSB and its corresponding PRACH resource unit. The aforementioned PRACH resource unit may include, but is not limited to, at least one of RO and preamble.

[0178] The aforementioned preset mapping rules may include one or more mapping rules. For example, the aforementioned preset mapping rules may include a first mapping rule, wherein the first mapping rule is used to determine the mapping relationship between PUSCH resources and PRACH resource units corresponding to SSBs; or the aforementioned preset mapping rules may include a second mapping rule, wherein the second mapping rule is used to determine the mapping relationship between PUSCH resources and SSBs; or the aforementioned preset mapping rules may include both the first mapping rule and the second mapping rule, in which case the mapping relationship between PUSCH resources and PRACH resource units corresponding to SSBs can be determined according to the first mapping rule, and the mapping relationship between PUSCH resources and SSBs can be determined according to the second mapping rule.

[0179] In some embodiments of this disclosure, the network side can determine the transmission position on the PUSCH resource and the SSB-related resource based on the above target mapping relationship when receiving random access messages, or determine the transmission position on the SSB-related resource based on the transmission position on the PUSCH resource, or determine the transmission position on the PUSCH resource based on the transmission position on the SSB-related resource, thereby avoiding blind detection of all possible transmission positions on the SSB-related resource and the PUSCH resource, thereby reducing processing complexity and improving processing efficiency.

[0180] Optionally, the preset mapping rule includes at least one of the following:

[0181] The first mapping rule is used to determine the mapping relationship between the PUSCH resource element and SSB of the Physical Uplink Shared Channel Transmission Opportunity (PUO).

[0182] The second mapping rule, wherein the first mapping rule is used to determine the mapping relationship between the PUSCH resource element of the PUO and the physical random access channel PRACH resource element corresponding to the SSB.

[0183] Optionally, the first mapping rule may include one of the following:

[0184] The PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB.

[0185] The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource units.

[0186] Optionally, the PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB, which may include:

[0187] The PUSCH resource units of the PUO are mapped to the PRACH resource units corresponding to I SSBs in the order of their PRACH resource unit numbers, and to N SSBs in the order of their SSB numbers; where I and N are both positive integers, and I is less than or equal to N.

[0188] Optionally, the PRACH resource unit corresponding to the SSB is mapped to the PUSCH resource unit of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource unit, which may include:

[0189] The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of J PUOs according to the numbering order of the PUSCH resource units, and to the PUSCH resource units of M PUOs according to the numbering order of the PUOs; where J and M are both positive integers, and J is less than or equal to M.

[0190] Optionally, the second mapping rule may include:

[0191] SSB maps to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO.

[0192] Optionally, the SSB is mapped to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO, which may include:

[0193] SSB maps to the PUSCH resource units of a PUO according to the numbering order of the PUSCH resource units, and maps to P PUOs according to the numbering order of the PUOs; where P is a positive integer.

[0194] The element is mapped to P PUOs according to their numbering order; where P is a positive integer.

[0195] Optionally, a PUCCH resource unit can be associated with an SSB.

[0196] Optionally, PUSCH resource units can be interleaved or non-interleaved with SSBs;

[0197] or

[0198] PUSCH resource units are interleaved or non-interleaved with the corresponding PRACH resource units of SSBs.

[0199] Optionally, the method may further include:

[0200] In the presence of first configuration information, a mapping relationship between the PUSCH resource unit of PUO and SSB is established according to the first mapping rule, wherein the first configuration information is used to indicate that there is an association between the PUSCH resource unit and the PRACH resource unit corresponding to the SSB;

[0201] Otherwise, according to the second mapping rule, establish the mapping relationship between the PUSCH resource unit of the PUO and the physical random access channel PRACH resource unit corresponding to the SSB.

[0202] Optionally, the mapping parameters of the target mapping relationship are determined by configuration information, wherein the configuration information includes at least one of the following:

[0203] A PUO-associated SSB parameter, wherein the SSB parameter includes the number of SSBs or the set of SSBs;

[0204] The number of PUSCH resource units in a PUO;

[0205] A target SSB is associated with Q PRACH resource units and a PUO's PUSCH resource unit, where the target SSB is the SSB corresponding to the PUO and Q is a positive integer;

[0206] The mapping interval L of the PUSCH resource unit, where L is greater than or equal to 1;

[0207] The mapping interval V of SSB is greater than or equal to 0;

[0208] A PUO parameter associated with an SSB, wherein the PUO parameter includes at least one of the following: the time domain resource of the PUO, the frequency domain resource of the PUO, the number of PUOs, and the PUO number;

[0209] A PRACH resource unit parameter associated with a PUSCH resource unit in a PUO, wherein the PRACH resource unit parameter includes the number of PRACH resource units or the set of PRACH resource units;

[0210] The SSB grouping information includes at least one of the following: the SSB grouping method, the number of SSB groups, and the number of SSBs in each SSB group;

[0211] The number of PUSCH resource units associated with an SSB in a PUO.

[0212] Optionally, when L=1, the PUSCH resource unit is non-interleaved with the SSB, or the PUSCH resource unit is non-interleaved with the PRACH resource unit corresponding to the SSB.

[0213] When L>1, the PUSCH resource unit is interleaved with the SSB, or the PUSCH resource unit is interleaved with the PRACH resource unit corresponding to the SSB.

[0214] Optionally, the PUSCH resource unit includes at least one of the following:

[0215] PUSCH's temporal resources;

[0216] PUSCH frequency domain resources;

[0217] DMRS port;

[0218] DMRS sequence;

[0219] DMRS scrambling identifier;

[0220] PUSCH scrambling identifier.

[0221] The following describes the mapping methods provided by some embodiments of this disclosure with reference to examples.

[0222] Assume the number of SSBs sent by the network side in each cycle is N. tx The SSB number is s{s=0,1,2,…,N tx The number of ROs associated with each SSB is N = ssb - perRACH - Occasion, with values ​​{1 / 8, 1 / 4, 1 / 2, 1, 2, 4, 8, 16}; the number of Preambles associated with each RO is P = CB - Preambles - per - SSB * max(1, SSB - per - rach - occasion). Therefore, the number of ROs after one round of mapping between SSB and PRACH is R' = N. tx *(1 / ssb-perRACH-Occasion), the number of ROs in an association period (where the association period is an integer multiple of the PRACH configuration period, and an SSB is associated with at least one RO) is R (where R is an integer multiple of R'), and the number of Preambles associated with each RO is P = CB - Preambles - per - SSB * max(1, SSB - per - rach - occasion).

[0223] For an associated periodic mapping, the ROs are numbered r (r = 0, 1, 2, ..., R-1), and the Preambles in each RO are numbered p (p = 0, 1, 2, ..., P), where P represents the number of Preambles in a RO. Therefore, (s, r, p) can represent the number of a PRACH resource unit associated with an SSB.

[0224] The PUOs used to send random access messages for 2-step RACH within a period are numbered u (u = 0, 1, 2, ..., U), and the PUSCH resource units in each PUO are numbered k (k = 0, 1, 2, ..., K). Here, K can identify the number of PUSCH resource units, so (u, k) can represent the number of a PUSCH resource unit.

[0225] Mapping Method 1:

[0226] The configuration includes the following information:

[0227] For each PUO, configure the number of SSBs associated with each PUO as N1, where N1 ≤ N tx That is, each POO is associated with N1 SSBs.

[0228] For PUO, configure the number of Preambles associated with each SSB to be M1 (the number of Preambles associated with each SSB is R, M1 <= R), that is, only M1 Preambles associated with each SSB are associated with the PUSCH resource unit of the PUO.

[0229] For a PUSCH resource unit (u,k) of a PUO, the Preamble (s,r,p) corresponding to the SSB can be associated in one of the following ways:

[0230] PUSCH resource units are associated with SSB preambles in the order of Preamble first, then SSB; that is, they are mapped to N1 SSB preambles according to their preamble numbering, with an SSB mapping interval V=0, and then mapped to N... tx Each SSB can be mapped as shown in Figure 3a;

[0231] The PUSCH resource unit is preambled first, then SSB, and associated with the SSB preamble; that is, it is mapped to the preamble corresponding to N1 SSBs according to the preamble numbering order, with the SSB mapping interval V=1, and then mapped to N according to the SSB numbering order. tx The SSBs can be mapped as shown in Figure 3b.

[0232] For a Preamble(s,r,p) corresponding to an SSB, it is associated with a PUSCH resource unit (u,k) in the order of PUSCH resource unit first, then PUO. That is, first, it is mapped to a PUSCH resource unit corresponding to a PUO according to the PUSCH resource unit numbering order, with an interval of L=1 for PUSCH resource mapping. Then, it is mapped to multiple PUOs according to the PUO numbering order, as shown in the mapping relationship in Figure 3a.

[0233] For a Preamble(s,r,p) corresponding to an SSB, it is associated with a PUSCH resource unit (u,k) in the order of PUSCH resource unit first, then PUO. That is, first, it is mapped to a PUSCH resource unit corresponding to a PUO according to the PUSCH resource unit numbering order, with an interval of L=4 for PUSCH resource mapping. Then, it is mapped to multiple PUOs according to the PUO numbering order, as shown in the mapping relationship in Figure 3b.

[0234] It should be noted that if N1*M1>K, some of the Preamble are not associated with any PUSCH resource units. If N1*M1<K, some of the PUSCH resource units are not associated with any Preamble and SSB.

[0235] Mapping method 2:

[0236] The following information is configured: for the PUO, the number of SSB associated with each PUO, N1, is configured, and N1≤N tx . Further, N tx SSBs are correspondingly grouped. The number of SSBs in each group is N1, and the number of Preamble corresponding to each SSB is R.

[0237] The number of PUO associated with one SSB is N2.

[0238] For all PUSCH resource units (u,k) of U PUOs, where U is the total number of PUOs in a configuration period or an association period, and the Preamble(s,r,p) corresponding to the SSB, they can be associated in one of the following ways:

[0239] The PUSCH resource units are associated with the Preamble of the SSB in the order of Preamble first and then SSB; that is, mapped to the Preamble corresponding to N1 SSBs in one SSB group according to the Preamble number order, the mapping interval V of the SSB is 0, and then mapped to N tx SSBs according to the SSB number order. After all the PUSCH resource units of the PUO are associated with the Preamble corresponding to the SSBs in a group, they are then associated with the Preamble corresponding to the SSBs in other SSB groups. The mapping relationship is shown in Figure 4a;

[0240] The PUSCH resource units are associated with the Preamble of the SSB in the order of Preamble first and then SSB; that is, mapped to the Preamble corresponding to N1 SSBs in one SSB group according to the Preamble number order, the mapping interval V of the SSB is 1, and then mapped to N tx SSBs according to the SSB number order. After all the PUSCH resource units of the PUO are associated with the Preamble corresponding to the SSBs in a group, they are then associated with the Preamble corresponding to the SSBs in other SSB groups. The mapping relationship is shown in Figure 4b.

[0241] For the Preamble(s,r,p) corresponding to one SSB group, it is associated with the PUSCH resource units (u,k) in the order of PUSCH resource units first and then PUO, that is: first, map to the PUSCH resource units corresponding to Y PUOs according to the PUSCH resource unit number order, with the PUSCH resource mapping interval being L, and then map to U PUOs according to the PUO number order. After all the Preamble corresponding to the SSB in one group are associated with the PUSCH resource units of the PUO, then associate the Preamble corresponding to the SSB in other SSB groups with the PUSCH resource units. The mapping relationships are shown in Figure 4a (L = 1) and Figure 4b (L = 4).

[0242] It should be noted that if N tx *R > U*K, then the Preamble of some SSBs is not associated with any PUSCH resource unit; if N tx *R < U*K, then some PUSCH resource units are not associated with any Preamble of SSBs.

[0243] Example 1:

[0244] For example, 4 SSBs (SSB 0 to SSB 3) are associated with 1 PRACH Occasion (for example, RO 0), and one SSB corresponds to 4 Preamble (i.e., preambles). The number of SSBs associated with one PUO is 2. The PUSCH resource units are DMRS, and the number is 8.

[0245] Embodiment 1: The DMRS of the PUO is associated with the Preamble in the order of Preamble first and then SSB, and multiple consecutive DMRS are associated with different SSBs.

[0246] For example, the DMRS of the PUO first maps to the Preamble corresponding to 2 SSBs according to the Preamble number order, and then maps according to the SSB number order, and the SSB mapping interval V = 1.

[0247] Another example, the Preamble of the SSB is associated with the DMRS of the PUO in the order of PUSCH resource units first and then PUO, and multiple consecutive DMRS are associated with different SSBs.

[0248] Specifically, the Preamble corresponding to the SSB first maps to the DMRS of 1 PUO according to the PUSCH resource unit number order, and then maps according to the PUO number order; the PUSCH number interval L = 2; the SSBs of one RO are used as one SSB group, and 4 SSBs are associated with 1 RO, as shown in Figure 8:

[0249] The DMRS(0,0) of PUO 0 is associated with the Preamble(0,0,0) of SSB 0;

[0250] The DMRS(0,1) of PUO 0 is associated with the Preamble(1,0,4) corresponding to SSB 1;

[0251] The DMRS(0,2) of PUO 0 is associated with the Preamble(0,0,1) corresponding to SSB 0;

[0252] The DMRS(0,3) of PUO 0 is associated with the Preamble(1,0,5) of SSB 1;

[0253] …

[0254] Implementation Method 2: The DMRS of PUO are associated with the Preamble in the order of Preamble first, then SSB, and multiple consecutive DMRS are associated with the same SSB.

[0255] For example, PUO's DMRS first maps the Preamble to the Preamble corresponding to the two SSBs according to the Preamble numbering order, and then maps according to the SSB numbering order, with the SSB mapping interval V = 0.

[0256] For example, the SSB Preamble associates the DMRS of the PUO in the order of first PUSCH resource units, then PUO, and multiple consecutive DMRS are associated with the same SSB.

[0257] Specifically, the preamble corresponding to an SSB is first mapped to the DMRS of one PUO according to the numbering order of the PUSCH resource units, and then mapped according to the numbering order of the PUOs; the PUSCH numbering interval L = 1; the SSB of one RO is a grouped SSB, and 4 SSBs are associated with 1 RO, as shown in Figure 9:

[0258] The DMRS(0,0) of PUO 0 is associated with the Preamble(0,0,0) of SSB 0;

[0259] The DMRS(0,1) of PUO 0 is associated with the Preamble(0,0,1) corresponding to SSB 0;

[0260] The DMRS(0,2) of PUO 0 is associated with the Preamble(0,0,2) corresponding to SSB 0;

[0261] The DMRS(0,3) of PUO 0 is associated with the Preamble(0,0,3) of SSB 0;

[0262] …

[0263] Example 2:

[0264] For example, one SSB is associated with two PRACH Occasions, and one SSB corresponds to four Preambles.

[0265] A PUO is associated with 2 SSBs and 8 PUSCH resource units (DMRS).

[0266] Implementation method 1: The DMRS of PUO are associated with the Preamble in the order of Preamble first, then SSB, and multiple consecutive DMRS are associated with different SSBs, which is called interleaving mapping.

[0267] For example, PUO's DMRS first maps the Preamble to the Preamble corresponding to the two SSBs according to the Preamble numbering order, and then maps according to the SSB numbering order, with the SSB mapping interval V = 1.

[0268] For example, the SSB Preamble associates the DMRS of the PUO in the order of first PUSCH resource units, then PUO, and multiple consecutive DMRS are associated with different SSBs.

[0269] Specifically, the SSB corresponding to the Preamble is first mapped to the DMRS of one PUO according to the numbering order of the PUSCH resource unit, and then mapped according to the numbering order of the PUO; the PUSCH numbering interval L = 2;

[0270] Two SSBs form an SSB group, and one SSB is associated with two ROs, as shown in Figure 10:

[0271] The DMRS(0,0) of PUO 0 is associated with the Preamble(0,0,0) of SSB 0;

[0272] The DMRS(0,1) of PUO 0 is associated with the Preamble(1,2,0) corresponding to SSB 1;

[0273] The DMRS(0,2) of PUO 0 is associated with the Preamble(0,0,1) corresponding to SSB 0;

[0274] The DMRS(0,3) of PUO 0 is associated with the Preamble(1,2,1) of SSB 1;

[0275] …

[0276] Implementation Method 2: The DMRS of PUO are first mapped according to the Preamble number order, and then mapped according to the SSB number order to associate the Preamble. Multiple consecutive DMRS are associated with the same SSB, which is a non-interleaved mapping.

[0277] For example, PUO's DMRS first maps the Preamble to the Preamble corresponding to the two SSBs according to the Preamble numbering order, and then maps according to the SSB numbering order, with the SSB mapping interval V = 0.

[0278] For example, the SSB Preamble associates the DMRS of the PUO in the order of first PUSCH resource units, then PUO, and multiple consecutive DMRS are associated with the same SSB.

[0279] Specifically, the SSB corresponding to the Preamble is first mapped to the DMRS of one PUO according to the numbering order of the PUSCH resource unit, and then mapped according to the numbering order of the PUO; the PUSCH numbering interval L = 1;

[0280] Two SSBs form an SSB group, and one SSB is associated with two ROs, as shown in Figure 11:

[0281] The DMRS(0,0) of PUO 0 is associated with the Preamble(0,0,0) of SSB 0;

[0282] The DMRS(0,1) of PUO 0 is associated with the Preamble(0,0,1) corresponding to SSB 0;

[0283] The DMRS(0,2) of PUO 0 is associated with the Preamble(0,1,0) corresponding to SSB 0;

[0284] The DMRS(0,3) of PUO 0 is associated with the Preamble(0,1,1) of SSB 0;

[0285] …

[0286] Example 3:

[0287] For example, four SSBs (SSB 0 to SSB 3) are associated with one PRACH Occasion (RO 0), and one SSB corresponds to four Preambles. A PUO is associated with four SSBs, and its PUSCH resource units are DMRS, numbering eight. For a PUO, two Preambles from the Preamble corresponding to each SSB are associated with the PUO's DMRS.

[0288] Implementation method 1: The DMRS of PUO are associated with the Preamble in the order of Preamble first, then SSB, and multiple consecutive DMRS are associated with different SSBs, which is called interleaving mapping.

[0289] For example, PUO's DMRS first maps the Preamble to the Preamble corresponding to the 4 SSBs according to the Preamble numbering order, and then maps according to the SSB numbering order, with the SSB mapping interval V=1.

[0290] For example, the SSB Preamble associates the DMRS of the PUO in the order of first PUSCH resource units, then PUO, and multiple consecutive DMRS are associated with different SSBs.

[0291] Specifically, the SSB corresponding to the Preamble is first mapped to the DMRS of one PUO according to the numbering order of the PUSCH resource unit, and then mapped according to the numbering order of the PUO; the PUSCH numbering interval L = 4;

[0292] Four SSBs are grouped into one SSB group, and four SSBs are associated with one RO, as shown in Figure 12:

[0293] The DMRS(0,0) of PUO 0 is associated with the Preamble(0,0,0) of SSB 0;

[0294] The DMRS(0,1) of PUO 0 is associated with the Preamble(1,0,4) corresponding to SSB 1;

[0295] The DMRS(0,2) of PUO 0 is associated with the Preamble(2,0,8) corresponding to SSB 2;

[0296] The DMRS(0,3) of PUO 0 is associated with the Preamble(3,0,12) corresponding to SSB 3;

[0297] …

[0298] Implementation Method 2: PUO's DMRS is based on mapping the Preamble first according to the Preamble number order and then according to the SSB number order, and the DMRS and SSB are mapped in a non-interleaved manner.

[0299] For example, PUO's DMRS first maps the Preamble to the Preamble corresponding to the 4 SSBs according to the Preamble numbering order, and then maps according to the SSB numbering order, with the SSB mapping interval V = 0.

[0300] For example, the SSB Preamble associates the DMRS of the PUO in the order of first PUSCH resource units, then PUO, and multiple consecutive DMRS are associated with the same SSB.

[0301] Specifically, the SSB corresponding to the Preamble is first mapped to the DMRS of one PUO according to the numbering order of the PUSCH resource units, and then mapped according to the numbering order of the PUOs; the PUSCH numbering interval L = 1; 4 SSBs are grouped into one SSB group, and 1 SSB is associated with 2 ROs, as shown in Figure 13:

[0302] The DMRS(0,0) of PUO 0 is associated with the Preamble(0,0,0) of SSB 0;

[0303] The DMRS(0,1) of PUO 0 is associated with the Preamble(0,0,1) corresponding to SSB 0;

[0304] The DMRS(0,2) of PUO 0 is associated with the Preamble(1,0,4) of SSB 1;

[0305] The DMRS(0,3) of PUO 0 is associated with the Preamble(1,0,5) of SSB 1;

[0306] …

[0307] Example 4:

[0308] For example, four SSBs (SSB 0 to SSB 3) are associated with four PRACH Occasions (RO 0 to RO 3), and one SSB corresponds to four Preambles. A PUO is associated with four SSBs, and its PUSCH resource units are DMRS, numbering eight. For a PUO, two Preambles from the Preamble corresponding to each SSB are associated with the PUO's DMRS.

[0309] Implementation method 1: The DMRS of PUO are associated with the Preamble in the order of Preamble first, then SSB, and multiple consecutive DMRS are associated with different SSBs, which is called interleaving mapping.

[0310] For example, PUO's DMRS first maps the Preamble to the Preamble corresponding to the 4 SSBs according to the Preamble numbering order, and then maps according to the SSB numbering order, with the SSB mapping interval V=1.

[0311] For example, the SSB Preamble associates the DMRS of the PUO in the order of first PUSCH resource units, then PUO, and multiple consecutive DMRS are associated with different SSBs.

[0312] Specifically, the preamble corresponding to an SSB is first mapped to the DMRS of one PUO according to the numbering order of the PUSCH resource units, and then mapped according to the numbering order of the PUOs; the PUSCH numbering interval L = 4; four SSBs form an SSB group, and one SSB is associated with one RO, as shown in Figure 3b:

[0313] The DMRS(0,0) of PUO 0 is associated with the Preamble(0,0,0) of SSB 0;

[0314] The DMRS(0,1) of PUO 0 is associated with the Preamble(1,1,0) corresponding to SSB 1;

[0315] The DMRS(0,2) of PUO 0 is associated with the Preamble(2,2,0) corresponding to SSB 2;

[0316] The DMRS(0,3) of PUO 0 is associated with the Preamble(3,3,0) corresponding to SSB 3;

[0317] …

[0318] Implementation Method 2: The DMRS of PUO is first mapped according to the Preamble number order, and then mapped according to the SSB number order to associate the Preamble. The PUSCH resource unit and SSB are mapped in a non-interleaved manner.

[0319] For example, PUO's DMRS first maps the Preamble to the Preamble corresponding to the 4 SSBs according to the Preamble numbering order, and then maps according to the SSB numbering order, with the SSB mapping interval V = 0.

[0320] For example, the SSB Preamble associates the DMRS of the PUO in the order of first PUSCH resource units, then PUO, and multiple consecutive DMRS are associated with the same SSB.

[0321] Specifically, the SSB corresponding to the Preamble is first mapped to the DMRS of one PUO according to the numbering order of the PUSCH resource unit, and then mapped according to the numbering order of the PUO; the PUSCH numbering interval L = 1;

[0322] Four SSBs are grouped together; one SSB is associated with one RO. This can be illustrated in Figure 3a:

[0323] The DMRS(0,0) of PUO 0 is associated with the Preamble(0,0,0) of SSB 0;

[0324] The DMRS(0,1) of PUO 0 is associated with the Preamble(0,0,1) of SSB 1;

[0325] The DMRS(0,2) of PUO 0 is associated with the Preamble(1,1,0) of SSB 0;

[0326] The DMRS(0,3) of PUO 0 is associated with the Preamble(1,1,1) of SSB 1;

[0327] …

[0328] Example 5:

[0329] For example, two SSBs (SSB 0 to SSB 3) are associated with two PRACH Occasions (RO 0 to RO 1), and one SSB corresponds to four Preambles. The number of SSBs N associated with a PUO is 2, and the number of PUSCH resource units is DMRS, with a quantity K of 10.

[0330] In this implementation, the DMRS of PUO are associated with the Preamble in the order of Preamble first, then SSB, and multiple consecutive DMRS are associated with different SSBs, which is called interleaving mapping.

[0331] For example, PUO's DMRS first maps the Preamble to the Preamble corresponding to the two SSBs according to the Preamble numbering order, and then maps according to the SSB numbering order, with the SSB mapping interval V = 1.

[0332] For example, the SSB Preamble associates the DMRS of the PUO in the order of first PUSCH resource units, then PUO, and multiple consecutive DMRS are associated with different SSBs.

[0333] Specifically, the SSB corresponding to the Preamble is first mapped to the DMRS of one PUO according to the numbering order of the PUSCH resource unit, and then mapped according to the numbering order of the PUO; the PUSCH numbering interval L = 2;

[0334] Two SSBs are grouped together; the number of PUSCH resource units is greater than the preamble corresponding to a group of SSBs, therefore some PUSCH resource units are not associated with the preamble. This can be illustrated in Figure 14.

[0335] The DMRS(0,0) of PUO 0 is associated with the Preamble(0,0,0) corresponding to SSB 0;

[0336] The DMRS(0,1) of PUO 0 is associated with the Preamble(1,1,0) corresponding to SSB 1;

[0337] The DMRS(0,2) of PUO 0 is associated with the Preamble(0,0,1) corresponding to SSB 0;

[0338] The DMRS(0,3) of PUO 0 is associated with the Preamble(1,1,1) corresponding to SSB 1;

[0339] …

[0340] It should be noted that since N*M<K (i.e., 2*4<10), the DMRS 8 to DMRS 9 in the PUO are not associated with any Preamble.

[0341] Example 6:

[0342] For example, among 4 SSBs (SSB 0 to SSB 3), one SSB corresponds to 4 Preamble. The number of SSBs associated with one PUO is 4, and the PUSCH resource units are DMRS, with a quantity of 8.

[0343] Embodiment 1: The DMRS of the PUO associates with the Preamble in the order of first Preamble and then SSB, and multiple consecutive DMRS are associated with different SSBs, that is, interleaved mapping.

[0344] For example, the DMRS of the PUO first maps to the Preamble corresponding to 4 SSBs grouped by 1 SSB in the order of the Preamble number, and then maps in the order of the SSB number. The mapping interval V of the SSB is 1.

[0345] Another example is that the Preamble of the SSB associates with the DMRS of the PUO in the order of first PUSCH resource unit and then PUO, and multiple consecutive DMRS are associated with different SSBs.

[0346] Specifically, the Preamble corresponding to the SSB first maps to the DMRS of 2 PUOs in the order of the PUSCH resource unit number, and then maps in the order of the PUO number; the PUSCH number interval L = 4;

[0347] 4 SSBs are grouped as a set. It can be as shown in Figure 4b:

[0348] The Preamble(0,0,0) corresponding to SSB 0 is associated with DMRS(0,0) of PUO 0;

[0349] The Preamble(0,0,1) corresponding to SSB 0 is associated with DMRS(0,4) of PUO 0;

[0350] The Preamble(0,0,2) corresponding to SSB 0 is associated with DMRS(1,0) of PUO 1;

[0351] The Preamble(0,0,3) corresponding to SSB 0 is associated with DMRS(1,4) of PUO 1;

[0352] …

[0353] Implementation Method 2: The DMRS of PUO are associated with the Preamble in the order of Preamble first, then SSB, and multiple consecutive DMRS are associated with the same SSB, which is a non-interleaved mapping.

[0354] For example, PUO's DMRS first maps the Preamble to the Preamble corresponding to the 4 SSBs in a group of 1 SSB according to the Preamble numbering order, and then maps according to the SSB numbering order, with the SSB mapping interval V = 0.

[0355] For example, the SSB Preamble associates the DMRS of the PUO in the order of first PUSCH resource units, then PUO, and multiple consecutive DMRS are associated with the same SSB.

[0356] Specifically, the SSB corresponding to the Preamble is first mapped to the DMRS of the two PUOs according to the numbering order of the PUSCH resource units, and then mapped according to the numbering order of the PUOs; the PUSCH numbering interval L = 1;

[0357] Four SSBs are grouped together. This can be illustrated as shown in Figure 4a:

[0358] The Preamble(0,0,0) corresponding to SSB 0 is associated with DMRS(0,0) of PUO 0;

[0359] The Preamble(0,0,1) corresponding to SSB 0 is associated with DMRS(0,1) of PUO 0;

[0360] The Preamble(0,0,2) corresponding to SSB 0 is associated with DMRS(1,0) of PUO 1;

[0361] The Preamble(0,0,3) corresponding to SSB 0 is associated with DMRS(1,1) of PUO 1;

[0362] …

[0363] Example 7:

[0364] For example, one SSB is associated with four PRACH Occasions, and one SSB corresponds to R = 16 Preambles. The number of SSBs associated with one PUO is N = 1 / 2, that is, two PUOs are associated with one SSB.

[0365] PUO's DMRS associates the Preamble in the order of Preamble first, then SSB, and multiple consecutive DMRSs are associated with the same SSB, which is a non-interleaved mapping.

[0366] For example, PUO's DMRS first maps the Preamble to the Preamble corresponding to 1 SSB according to the Preamble numbering order, and then maps according to the SSB numbering order, with the SSB mapping interval V = 0.

[0367] For example, the SSB Preamble associates the DMRS of the PUO in the order of first PUSCH resource units, then PUO, and multiple consecutive DMRS are associated with the same SSB.

[0368] Specifically, the SSB corresponding to the Preamble is first mapped to the DMRS of the two PUOs according to the numbering order of the PUSCH resource units, and then mapped according to the numbering order of the PUOs; the PUSCH numbering interval L = 1;

[0369] One SSB is grouped together; one SSB is associated with four ROs. This can be illustrated in Figure 15.

[0370] The DMRS(0,0) of PUO 0 is associated with the Preamble(0,0,0) of SSB 0;

[0371] The DMRS(0,1) of PUO 0 is associated with the Preamble(0,0,1) of SSB 1;

[0372] The DMRS(0,2) of PUO 0 is associated with the Preamble(0,0,2) corresponding to SSB 0;

[0373] The DMRS(0,3) of PUO 0 is associated with the Preamble(1,2,3) of SSB 1;

[0374] …

[0375] Referring to Figure 16, Figure 16 is a structural diagram of a terminal device provided in some embodiments of this disclosure. As shown in Figure 16, the terminal device 1600 includes:

[0376] The sending module 1601 is used to send random access messages according to the target mapping relationship between the Physical Uplink Shared Channel (PUSCH) resources and the Synchronization Signal Block (SSB) related resources;

[0377] The target mapping relationship is determined according to a preset mapping rule.

[0378] Optionally, the preset mapping rule includes at least one of the following:

[0379] The first mapping rule is used to determine the mapping relationship between the PUSCH resource element and SSB of the Physical Uplink Shared Channel Transmission Opportunity (PUO).

[0380] The second mapping rule, wherein the first mapping rule is used to determine the mapping relationship between the PUSCH resource element of the PUO and the physical random access channel PRACH resource element corresponding to the SSB.

[0381] Optionally, the first mapping rule includes one of the following:

[0382] The PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB.

[0383] The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource units.

[0384] Optionally, the PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB, including:

[0385] The PUSCH resource units of the PUO are mapped to the PRACH resource units corresponding to I SSBs in the order of their PRACH resource unit numbers, and to N SSBs in the order of their SSB numbers; where I and N are both positive integers, and I is less than or equal to N.

[0386] Optionally, the PRACH resource unit corresponding to the SSB is mapped to the PUSCH resource unit of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource unit, including:

[0387] The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of J PUOs according to the numbering order of the PUSCH resource units, and to the PUSCH resource units of M PUOs according to the numbering order of the PUOs; where J and M are both positive integers, and J is less than or equal to M.

[0388] Optionally, the second mapping rule includes:

[0389] SSB maps to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO.

[0390] Optionally, the SSB is mapped to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO, including:

[0391] SSB maps to the PUSCH resource units of a PUO according to the numbering order of the PUSCH resource units, and maps to P PUOs according to the numbering order of the PUOs; where P is a positive integer.

[0392] Optionally, a PUCCH resource unit can be associated with an SSB.

[0393] Optionally, PUSCH resource units can be interleaved or non-interleaved with SSBs;

[0394] or

[0395] PUSCH resource units are interleaved or non-interleaved with the corresponding PRACH resource units of SSBs.

[0396] Optionally, the terminal device further includes an establishment module, which is specifically used for:

[0397] Before sending a random access message based on the target mapping relationship between the Physical Uplink Shared Channel (PUSCH) resources and the Synchronization Signal Block (SSB) related resources, if the first configuration information exists, a mapping relationship between the PUSCH resource units of the PUO and the SSB is established according to the first mapping rule. The first configuration information is used to indicate that the PUSCH resource units and the corresponding PRACH resource units of the SSB are associated.

[0398] Otherwise, according to the second mapping rule, establish the mapping relationship between the PUSCH resource unit of the PUO and the physical random access channel PRACH resource unit corresponding to the SSB.

[0399] Optionally, the mapping parameters of the target mapping relationship are determined by configuration information, wherein the configuration information includes at least one of the following:

[0400] A PUO-associated SSB parameter, wherein the SSB parameter includes the number of SSBs or the set of SSBs;

[0401] The number of PUSCH resource units in a PUO;

[0402] A target SSB is associated with Q PRACH resource units and a PUO's PUSCH resource unit, where the target SSB is the SSB corresponding to the PUO and Q is a positive integer;

[0403] The mapping interval L of the PUSCH resource unit, where L is greater than or equal to 1;

[0404] The mapping interval V of SSB is greater than or equal to 0;

[0405] A PUO parameter associated with an SSB, wherein the PUO parameter includes at least one of the following: the time domain resource of the PUO, the frequency domain resource of the PUO, the number of PUOs, and the PUO number;

[0406] A PRACH resource unit parameter associated with a PUSCH resource unit in a PUO, wherein the PRACH resource unit parameter includes the number of PRACH resource units or the set of PRACH resource units;

[0407] The SSB grouping information includes at least one of the following: the SSB grouping method, the number of SSB groups, and the number of SSBs in each SSB group;

[0408] The number of PUSCH resource units associated with an SSB in a PUO.

[0409] Optionally, when L=1, the PUSCH resource unit is non-interleaved with the SSB, or the PUSCH resource unit is non-interleaved with the PRACH resource unit corresponding to the SSB.

[0410] When L>1, the PUSCH resource unit is interleaved with the SSB, or the PUSCH resource unit is interleaved with the PRACH resource unit corresponding to the SSB.

[0411] Optionally, the PUSCH resource unit includes at least one of the following:

[0412] PUSCH's temporal resources;

[0413] PUSCH frequency domain resources;

[0414] DMRS port;

[0415] DMRS sequence;

[0416] DMRS scrambling identifier;

[0417] PUSCH scrambling identifier.

[0418] The terminal device 1600 provided in some embodiments of this disclosure can implement the various processes implemented by the terminal device in the above method embodiments. To avoid repetition, it will not be described again here.

[0419] The terminal device 1600 of some embodiments of this disclosure includes a transmitting module 1601, which is used to transmit random access messages according to the target mapping relationship between Physical Uplink Shared Channel (PUSCH) resources and Synchronization Signal Block (SSB) related resources; wherein the target mapping relationship is determined according to a preset mapping rule. This avoids blind detection of transmission positions on all possible SSB related resources and PUSCH resources, thereby reducing processing complexity.

[0420] Referring to Figure 17, Figure 17 is a structural diagram of a network-side device provided in some embodiments of this disclosure. As shown in Figure 17, the network-side device 1700 includes:

[0421] The receiving module 1701 is used to receive random access messages according to the target mapping relationship between the Physical Uplink Shared Channel (PUSCH) resources and the Synchronization Signal Block (SSB) related resources;

[0422] The target mapping relationship is determined according to a preset mapping rule.

[0423] Optionally, the preset mapping rule includes at least one of the following:

[0424] The first mapping rule is used to determine the mapping relationship between the PUSCH resource element and SSB of the Physical Uplink Shared Channel Transmission Opportunity (PUO).

[0425] The second mapping rule, wherein the first mapping rule is used to determine the mapping relationship between the PUSCH resource element of the PUO and the physical random access channel PRACH resource element corresponding to the SSB.

[0426] Optionally, the first mapping rule includes one of the following:

[0427] The PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB.

[0428] The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource units.

[0429] Optionally, the PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB, including:

[0430] The PUSCH resource units of the PUO are mapped to the PRACH resource units corresponding to I SSBs in the order of their PRACH resource unit numbers, and to N SSBs in the order of their SSB numbers; where I and N are both positive integers, and I is less than or equal to N.

[0431] Optionally, the PRACH resource unit corresponding to the SSB is mapped to the PUSCH resource unit of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource unit, including:

[0432] The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of J PUOs according to the numbering order of the PUSCH resource units, and to the PUSCH resource units of M PUOs according to the numbering order of the PUOs; where J and M are both positive integers, and J is less than or equal to M.

[0433] Optionally, the second mapping rule includes:

[0434] SSB maps to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO.

[0435] Optionally, the SSB is mapped to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO, including:

[0436] SSB maps to the PUSCH resource units of a PUO according to the numbering order of the PUSCH resource units, and maps to P PUOs according to the numbering order of the PUOs; where P is a positive integer.

[0437] The network-side device 1700 provided in some embodiments of this disclosure can implement the various processes implemented by the network-side device in the above method embodiments. To avoid repetition, it will not be described again here.

[0438] The network-side device 1700 of some embodiments of this disclosure includes a receiving module 1701, which is used to receive random access messages according to the target mapping relationship between Physical Uplink Shared Channel (PUSCH) resources and Synchronization Signal Block (SSB) related resources; wherein the target mapping relationship is determined according to a preset mapping rule. This avoids blind detection of transmission positions on all possible SSB related resources and PUSCH resources, thereby reducing processing complexity.

[0439] Figure 18 is a structural diagram of another terminal device provided in some embodiments of this disclosure. Referring to Figure 18, the terminal device 1800 includes, but is not limited to, components such as: a radio frequency unit 1801, a network module 1802, an audio output unit 1803, an input unit 1804, a sensor 1805, a display unit 1806, a user input unit 1807, an interface unit 1808, a memory 1809, a processor 1810, and a power supply 1811. Those skilled in the art will understand that the terminal device structure shown in Figure 18 does not constitute a limitation on the terminal device. The terminal device may include more or fewer components than shown, or combine certain components, or have different component arrangements. In some embodiments of this disclosure, the terminal device includes, but is not limited to, mobile phones, tablet computers, laptop computers, PDAs, vehicle terminals, wearable devices, and pedometers.

[0440] The processor 1810 is configured to send random access messages based on the target mapping relationship between the Physical Uplink Shared Channel (PUSCH) resources and the Synchronization Signal Block (SSB) related resources; wherein the target mapping relationship is determined according to a preset mapping rule.

[0441] The preset mapping rule includes at least one of the following:

[0442] The first mapping rule is used to determine the mapping relationship between the PUSCH resource element and SSB of the Physical Uplink Shared Channel Transmission Opportunity (PUO).

[0443] The second mapping rule, wherein the first mapping rule is used to determine the mapping relationship between the PUSCH resource element of the PUO and the physical random access channel PRACH resource element corresponding to the SSB.

[0444] Optionally, the first mapping rule includes one of the following:

[0445] The PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB.

[0446] The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource units.

[0447] Optionally, the PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB, including:

[0448] The PUSCH resource units of the PUO are mapped to the PRACH resource units corresponding to I SSBs in the order of their PRACH resource unit numbers, and to N SSBs in the order of their SSB numbers; where I and N are both positive integers, and I is less than or equal to N.

[0449] Optionally, the PRACH resource unit corresponding to the SSB is mapped to the PUSCH resource unit of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource unit, including:

[0450] The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of J PUOs according to the numbering order of the PUSCH resource units, and to the PUSCH resource units of M PUOs according to the numbering order of the PUOs; where J and M are both positive integers, and J is less than or equal to M.

[0451] Optionally, the second mapping rule includes:

[0452] SSB maps to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO.

[0453] Optionally, the SSB is mapped to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO, including:

[0454] SSB maps to the PUSCH resource units of a PUO according to the numbering order of the PUSCH resource units, and maps to P PUOs according to the numbering order of the PUOs; where P is a positive integer.

[0455] Optionally, a PUCCH resource unit can be associated with an SSB.

[0456] Optionally, PUSCH resource units can be interleaved or non-interleaved with SSBs;

[0457] or

[0458] PUSCH resource units are interleaved or non-interleaved with the corresponding PRACH resource units of SSBs.

[0459] Optionally, before sending the random access message based on the target mapping relationship between the Physical Uplink Shared Channel (PUSCH) resources and the Synchronization Signal Block (SSB) related resources, the method further includes:

[0460] In the presence of first configuration information, a mapping relationship between the PUSCH resource unit of PUO and SSB is established according to the first mapping rule, wherein the first configuration information is used to indicate that there is an association between the PUSCH resource unit and the PRACH resource unit corresponding to the SSB;

[0461] Otherwise, according to the second mapping rule, establish the mapping relationship between the PUSCH resource unit of the PUO and the physical random access channel PRACH resource unit corresponding to the SSB.

[0462] Optionally, the mapping parameters of the target mapping relationship are determined by configuration information, wherein the configuration information includes at least one of the following:

[0463] A PUO-associated SSB parameter, wherein the SSB parameter includes the number of SSBs or the set of SSBs;

[0464] The number of PUSCH resource units in a PUO;

[0465] A target SSB is associated with Q PRACH resource units and a PUO's PUSCH resource unit, where the target SSB is the SSB corresponding to the PUO and Q is a positive integer;

[0466] The mapping interval L of the PUSCH resource unit, where L is greater than or equal to 1;

[0467] The mapping interval V of SSB is greater than or equal to 0;

[0468] A PUO parameter associated with an SSB, wherein the PUO parameter includes at least one of the following: the time domain resource of the PUO, the frequency domain resource of the PUO, the number of PUOs, and the PUO number;

[0469] A PRACH resource unit parameter associated with a PUSCH resource unit in a PUO, wherein the PRACH resource unit parameter includes the number of PRACH resource units or the set of PRACH resource units;

[0470] The SSB grouping information includes at least one of the following: the SSB grouping method, the number of SSB groups, and the number of SSBs in each SSB group;

[0471] The number of PUSCH resource units associated with an SSB in a PUO.

[0472] Optionally, when L=1, the PUSCH resource unit is non-interleaved with the SSB, or the PUSCH resource unit is non-interleaved with the PRACH resource unit corresponding to the SSB.

[0473] When L>1, the PUSCH resource unit is interleaved with the SSB, or the PUSCH resource unit is interleaved with the PRACH resource unit corresponding to the SSB.

[0474] Optionally, the PUSCH resource unit includes at least one of the following:

[0475] PUSCH's temporal resources;

[0476] PUSCH frequency domain resources;

[0477] DMRS port;

[0478] DMRS sequence;

[0479] DMRS scrambling identifier;

[0480] PUSCH scrambling identifier.

[0481] It should be understood that in some embodiments of this disclosure, the radio frequency unit 1801 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink data from the base station and processes it with the processor 1810; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 1801 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc. Furthermore, the radio frequency unit 1801 can also communicate with networks and other devices through a wireless communication system.

[0482] The terminal device provides users with wireless broadband internet access through the network module 1802, such as helping users send and receive emails, browse web pages, and access streaming media.

[0483] The audio output unit 1803 can convert audio data received by the radio frequency unit 1801 or the network module 1802 or stored in the memory 1809 into audio signals and output them as sound. Furthermore, the audio output unit 1803 can also provide audio output related to specific functions performed by the terminal device 1800 (e.g., call signal reception sound, message reception sound, etc.). The audio output unit 1803 includes a speaker, a buzzer, and a receiver, etc.

[0484] Input unit 1804 is used to receive audio or video signals. Input unit 1804 may include a graphics processing unit (GPU) 18041 and a microphone 18042. GPU 18041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on display unit 1806. The image frames processed by GPU 18041 can be stored in memory 1809 (or other storage medium) or transmitted via radio frequency unit 1801 or network module 1802. Microphone 18042 can receive sound and process such sound into audio data. The processed audio data can be converted into a format that can be transmitted to a mobile communication base station via radio frequency unit 1801 in telephone call mode.

[0485] The terminal device 1800 also includes at least one sensor 1805, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display panel 18061 according to the ambient light level, and the proximity sensor can turn off the display panel 18061 and / or backlight when the terminal device 1800 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity and can be used to identify the terminal device's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. The sensor 1805 may also include a fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared sensor, etc., which will not be described in detail here.

[0486] The display unit 1806 is used to display information input by the user or information provided to the user. The display unit 1806 may include a display panel 18061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0487] User input unit 1807 can be used to receive input numerical or character information, and to generate key signal inputs related to user settings and function control of the terminal device. Specifically, user input unit 1807 includes a touch panel 18071 and other input devices 18072. Touch panel 18071, also known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 18071). Touch panel 18071 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to processor 1810, which receives and executes commands from processor 1810. In addition, touch panel 18071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 18071, the user input unit 1807 may also include other input devices 18072. Specifically, other input devices 18072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0488] Furthermore, the touch panel 18071 can cover the display panel 18061. When the touch panel 18071 detects a touch operation on or near it, it transmits the information to the processor 1810 to determine the type of touch event. Subsequently, the processor 1810 provides corresponding visual output on the display panel 18061 according to the type of touch event. Although in Figure 18, the touch panel 18071 and the display panel 18061 are shown as two separate components to implement the input and output functions of the terminal device, in some embodiments, the touch panel 18071 and the display panel 18061 can be integrated to implement the input and output functions of the terminal device. Specific details are not limited here.

[0489] Interface unit 1808 serves as an interface for connecting external devices to terminal device 1800. For example, external devices may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, and so on. Interface unit 1808 can be used to receive input from external devices (e.g., data, power, etc.) and transmit the received input to one or more elements within terminal device 1800, or it can be used to transmit data between terminal device 1800 and external devices.

[0490] The memory 1809 can be used to store software programs and various data. The memory 1809 may primarily include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). Furthermore, the memory 1809 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0491] Processor 1810 is the control center of the terminal device. It connects various parts of the terminal device via various interfaces and lines. By running or executing software programs and / or modules stored in memory 1809, and by calling data stored in memory 1809, it performs various functions and processes data of the terminal device, thereby providing overall monitoring of the terminal device. Processor 1810 may include one or more processing units; optionally, processor 1810 may integrate an application processor and a modem processor. The application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into processor 1810.

[0492] The terminal device 1800 may also include a power supply 1811 (such as a battery) to power various components. Optionally, the power supply 1811 may be logically connected to the processor 1810 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0493] In addition, the terminal device 1800 includes some functional modules not shown, which will not be described in detail here.

[0494] Optionally, some embodiments of this disclosure also provide a terminal device, including a processor 1810, a memory 1809, and a computer program stored in the memory 1809 and executable on the processor 1810. When the computer program is executed by the processor 1810, it implements the various processes of the above-described mapping method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0495] Referring to Figure 19, which is a structural diagram of a network-side device provided in some embodiments of this disclosure. As shown in Figure 19, the network-side device 1900 includes: a processor 1901, a memory 1902, a bus interface 1903, and a transceiver 1904, wherein the processor 1901, the memory 1902, and the transceiver 1904 are all connected to the bus interface 1903.

[0496] In some embodiments of this disclosure, the network-side device 1900 further includes a computer program stored on a memory 1902 and executable on a processor 1901.

[0497] In some embodiments of this disclosure, the transceiver 1904 is configured to: receive random access messages based on the target mapping relationship between Physical Uplink Shared Channel (PUSCH) resources and Synchronization Signal Block (SSB) related resources;

[0498] The target mapping relationship is determined according to a preset mapping rule.

[0499] Optionally, the preset mapping rule includes at least one of the following:

[0500] The first mapping rule is used to determine the mapping relationship between the PUSCH resource element and SSB of the Physical Uplink Shared Channel Transmission Opportunity (PUO).

[0501] The second mapping rule, wherein the first mapping rule is used to determine the mapping relationship between the PUSCH resource element of the PUO and the physical random access channel PRACH resource element corresponding to the SSB.

[0502] Optionally, the first mapping rule includes one of the following:

[0503] The PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB.

[0504] The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource units.

[0505] Optionally, the PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB, including:

[0506] The PUSCH resource units of the PUO are mapped to the PRACH resource units corresponding to I SSBs in the order of their PRACH resource unit numbers, and to N SSBs in the order of their SSB numbers; where I and N are both positive integers, and I is less than or equal to N.

[0507] Optionally, the PRACH resource unit corresponding to the SSB is mapped to the PUSCH resource unit of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource unit, including:

[0508] The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of J PUOs according to the numbering order of the PUSCH resource units, and to the PUSCH resource units of M PUOs according to the numbering order of the PUOs; where J and M are both positive integers, and J is less than or equal to M.

[0509] Optionally, the second mapping rule includes:

[0510] SSB maps to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO.

[0511] Optionally, the SSB is mapped to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO, including:

[0512] SSB maps to the PUSCH resource units of a PUO according to the numbering order of the PUSCH resource units, and maps to P PUOs according to the numbering order of the PUOs; where P is a positive integer.

[0513] Some embodiments of this disclosure also provide a computer-readable storage medium storing a computer program. When executed by a processor, this computer program implements the various processes of the above-described mapping method embodiments and achieves the same technical effects. To avoid repetition, further details are omitted here. The computer-readable storage medium may include, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0514] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0515] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this disclosure.

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

[0517] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0518] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0519] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0520] In addition, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0521] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this disclosure, or the part that contributes to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0522] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program controlling related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0523] It is understood that the embodiments described in some embodiments of this disclosure can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, modules, units, and subunits can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in this disclosure, or combinations thereof.

[0524] For software implementation, the techniques described in some embodiments of this disclosure can be implemented by modules (e.g., procedures, functions, etc.) that perform the functions described in some embodiments of this disclosure. The software code can be stored in memory and executed by a processor. The memory can be implemented in the processor or external to the processor.

[0525] The embodiments of this disclosure have been described above with reference to the accompanying drawings. However, this disclosure is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this disclosure without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this disclosure.

Claims

1. A mapping method applied to a terminal device, comprising: Based on the target mapping relationship between the Physical Uplink Shared Channel (PUSCH) resources and the Synchronization Signal Block (SSB) related resources, a random access message is sent. The target mapping relationship is determined according to a preset mapping rule.

2. The method according to claim 1, wherein, The preset mapping rule includes at least one of the following: The first mapping rule is used to determine the mapping relationship between the PUSCH resource element and SSB of the Physical Uplink Shared Channel Transmission Opportunity (PUO). The second mapping rule, wherein the first mapping rule is used to determine the mapping relationship between the PUSCH resource element of the PUO and the physical random access channel PRACH resource element corresponding to the SSB.

3. The method according to claim 2, wherein, The first mapping rule includes the following: The PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB. The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource units.

4. The method according to claim 3, wherein, The PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB, including: The PUSCH resource units of the PUO are mapped to the PRACH resource units corresponding to I SSBs in the order of their PRACH resource unit numbers, and to N SSBs in the order of their SSB numbers; where I and N are both positive integers, and I is less than or equal to N.

5. The method according to claim 3, wherein, The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource units, including: The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of J PUOs according to the numbering order of the PUSCH resource units, and to the PUSCH resource units of M PUOs according to the numbering order of the PUOs; where J and M are both positive integers, and J is less than or equal to M.

6. The method according to claim 2, wherein, The second mapping rule includes: SSB maps to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO.

7. The method according to claim 6, wherein, The SSB is mapped to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO, including: SSB maps to the PUSCH resource units of a PUO according to the numbering order of the PUSCH resource units, and maps to P PUOs according to the numbering order of the PUOs; where P is a positive integer.

8. The method according to claim 2, wherein, A PUCCH resource unit is associated with an SSB.

9. The method according to claim 2, wherein: PUSCH resource units are interleaved or non-interleaved with SSBs; or PUSCH resource units are interleaved or non-interleaved with the corresponding PRACH resource units of SSBs.

10. The method according to claim 1, wherein, Before sending the random access message based on the target mapping relationship between the Physical Uplink Shared Channel (PUSCH) resources and the Synchronization Signal Block (SSB) related resources, the method further includes: In the presence of first configuration information, a mapping relationship between the PUSCH resource unit of PUO and SSB is established according to the first mapping rule, wherein the first configuration information is used to indicate that there is an association between the PUSCH resource unit and the PRACH resource unit corresponding to the SSB; Otherwise, according to the second mapping rule, establish the mapping relationship between the PUSCH resource unit of the PUO and the physical random access channel PRACH resource unit corresponding to the SSB.

11. The method according to claim 1, wherein, The mapping parameters of the target mapping relationship are determined by configuration information, wherein the configuration information includes at least one of the following: A PUO-associated SSB parameter, wherein the SSB parameter includes the number of SSBs or the set of SSBs; The number of PUSCH resource units in a PUO; A target SSB is associated with Q PRACH resource units and a PUO's PUSCH resource unit, where the target SSB is the SSB corresponding to the PUO and Q is a positive integer; The mapping interval L of the PUSCH resource unit, where L is greater than or equal to 1; The mapping interval V of SSB is greater than or equal to 0; A PUO parameter associated with an SSB, wherein the PUO parameter includes at least one of the following: the time domain resource of the PUO, the frequency domain resource of the PUO, the number of PUOs, and the PUO number; A PRACH resource unit parameter associated with a PUSCH resource unit in a PUO, wherein the PRACH resource unit parameter includes the number of PRACH resource units or the set of PRACH resource units; The SSB grouping information includes at least one of the following: the SSB grouping method, the number of SSB groups, and the number of SSBs in each SSB group; The number of PUSCH resource units associated with an SSB in a PUO.

12. The method according to claim 11, wherein: When L=1, the PUSCH resource unit is non-interleaved with the SSB, or the PUSCH resource unit is non-interleaved with the PRACH resource unit corresponding to the SSB. When L>1, the PUSCH resource unit is interleaved with the SSB, or the PUSCH resource unit is interleaved with the PRACH resource unit corresponding to the SSB.

13. The method according to claim 1, wherein, The PUSCH resource unit includes at least one of the following: PUSCH's temporal resources; PUSCH frequency domain resources; Demodulation reference signal DMRS port; DMRS sequence; DMRS scrambling identifier; PUSCH scrambling identifier.

14. A mapping method applied to a network-side device, comprising: Based on the target mapping relationship between the Physical Uplink Shared Channel (PUSCH) resources and the Synchronization Signal Block (SSB) related resources, receive random access messages; The target mapping relationship is determined according to a preset mapping rule.

15. The method according to claim 14, wherein, The preset mapping rule includes at least one of the following: The first mapping rule is used to determine the mapping relationship between the PUSCH resource element and SSB of the Physical Uplink Shared Channel Transmission Opportunity (PUO). The second mapping rule, wherein the first mapping rule is used to determine the mapping relationship between the PUSCH resource element of the PUO and the physical random access channel PRACH resource element corresponding to the SSB.

16. The method according to claim 15, wherein, The first mapping rule includes the following: The PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB. The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource units.

17. The method according to claim 16, wherein, The PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB, including: The PUSCH resource units of the PUO are mapped to the PRACH resource units corresponding to I SSBs in the order of their PRACH resource unit numbers, and to N SSBs in the order of their SSB numbers; where I and N are both positive integers, and I is less than or equal to N.

18. The method according to claim 16, wherein, The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource units, including: The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of J PUOs according to the numbering order of the PUSCH resource units, and to the PUSCH resource units of M PUOs according to the numbering order of the PUOs; where J and M are both positive integers, and J is less than or equal to M.

19. The method according to claim 15, wherein, The second mapping rule includes: SSB maps to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO.

20. The method according to claim 19, wherein, The SSB is mapped to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO, including: SSB maps to the PUSCH resource units of a PUO according to the numbering order of the PUSCH resource units, and maps to P PUOs according to the numbering order of the PUOs; where P is a positive integer.

21. A terminal device, comprising: The sending module is used to send random access messages based on the target mapping relationship between the Physical Uplink Shared Channel (PUSCH) resources and the Synchronization Signal Block (SSB) related resources; The target mapping relationship is determined according to a preset mapping rule.

22. The terminal device according to claim 21, wherein, The preset mapping rule includes at least one of the following: The first mapping rule is used to determine the mapping relationship between the PUSCH resource element and SSB of the Physical Uplink Shared Channel Transmission Opportunity (PUO). The second mapping rule, wherein the first mapping rule is used to determine the mapping relationship between the PUSCH resource element of the PUO and the physical random access channel PRACH resource element corresponding to the SSB.

23. The terminal device according to claim 22, wherein, The first mapping rule includes the following: The PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB. The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource units.

24. The terminal device according to claim 23, wherein, The PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB, including: The PUSCH resource units of the PUO are mapped to the PRACH resource units corresponding to I SSBs in the order of their PRACH resource unit numbers, and to N SSBs in the order of their SSB numbers; where I and N are both positive integers, and I is less than or equal to N.

25. The terminal device according to claim 23, wherein, The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource units, including: The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of J PUOs according to the numbering order of the PUSCH resource units, and to the PUSCH resource units of M PUOs according to the numbering order of the PUOs; where J and M are both positive integers, and J is less than or equal to M.

26. The terminal device according to claim 22, wherein, The second mapping rule includes: SSB maps to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO.

27. The terminal device according to claim 26, wherein, The SSB is mapped to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO, including: SSB maps to the PUSCH resource units of a PUO according to the numbering order of the PUSCH resource units, and maps to P PUOs according to the numbering order of the PUOs; where P is a positive integer.

28. A network-side device, comprising: The receiving module is used to receive random access messages based on the target mapping relationship between the Physical Uplink Shared Channel (PUSCH) resources and the Synchronization Signal Block (SSB) related resources; The target mapping relationship is determined according to a preset mapping rule.

29. The network-side device according to claim 28, wherein, The preset mapping rule includes at least one of the following: The first mapping rule is used to determine the mapping relationship between the PUSCH resource element and SSB of the Physical Uplink Shared Channel Transmission Opportunity (PUO). The second mapping rule, wherein the first mapping rule is used to determine the mapping relationship between the PUSCH resource element of the PUO and the physical random access channel PRACH resource element corresponding to the SSB.

30. The network-side device according to claim 29, wherein, The first mapping rule includes the following: The PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB. The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource units.

31. The network-side device according to claim 30, wherein, The PUSCH resource units of the PUO are mapped to the corresponding PRACH resource units of the SSB according to the numbering order of the PRACH resource units and the numbering order of the SSB, including: The PUSCH resource units of the PUO are mapped to the PRACH resource units corresponding to I SSBs in the order of their PRACH resource unit numbers, and to N SSBs in the order of their SSB numbers; where I and N are both positive integers, and I is less than or equal to N.

32. The network-side device according to claim 30, wherein, The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of the PUO according to the numbering order of the PUO and the numbering order of the PUSCH resource units, including: The PRACH resource units corresponding to the SSB are mapped to the PUSCH resource units of J PUOs according to the numbering order of the PUSCH resource units, and to the PUSCH resource units of M PUOs according to the numbering order of the PUOs; where J and M are both positive integers, and J is less than or equal to M.

33. The network-side device according to claim 29, wherein, The second mapping rule includes: SSB maps to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO.

34. The network-side device according to claim 33, wherein, The SSB is mapped to the PUSCH resource units of the PUO according to the numbering order of the PUSCH resource units and the numbering order of the PUO, including: SSB maps to the PUSCH resource units of a PUO according to the numbering order of the PUSCH resource units, and maps to P PUOs according to the numbering order of the PUOs; where P is a positive integer.

35. A terminal device comprising a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the mapping method as described in any one of claims 1 to 13.

36. A network-side device, comprising a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the mapping method as described in any one of claims 14 to 20.

37. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the mapping method as claimed in any one of claims 1 to 13, or implements the steps of the mapping method as claimed in any one of claims 14 to 20.