CN118019138A

CN118019138A - Communication method and device

Info

Publication number: CN118019138A
Application number: CN202211386451.4A
Authority: CN
Inventors: 杨苑青; 丁昱; 雷珍珠
Original assignee: Spreadtrum Semiconductor Nanjing Co Ltd
Current assignee: Spreadtrum Semiconductor Nanjing Co Ltd
Priority date: 2022-11-07
Filing date: 2022-11-07
Publication date: 2024-05-10

Abstract

A communication method and device relate to the technical field of communication. Specifically, the method comprises the following steps: resources for multiple PRACH transmissions are determined. The resources include shared ROs employed by M PRACH transmissions and dedicated ROs employed by N PRACH transmissions. M, N is a positive integer greater than or equal to 0, and the sum of M and N is equal to K, K being the number of repetitions of PRACH. The shared RO supports single PRACH transmission and multiple PRACH transmission. Dedicated ROs only support multiple PRACH transmissions. Then, the PRACH is transmitted based on at least one shared RO and/or a dedicated RO among the resources. The PRACH employing shared RO transmissions includes a dedicated preamble that supports only multiple PRACH transmissions. The technical scheme is beneficial to reducing the transmission delay of the multi-PRACH transmission, reducing the waste of resources and reducing the possibility of communication failure caused by insufficient preamble resources.

Description

Communication method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a communications method and apparatus.

Background

A multiple Physical Random Access Channel (PRACH) transmission is introduced in the new air interface (NR) to enhance uplink coverage. Specifically, in the case that the terminal device supports multiple PRACH transmissions, the terminal device may transmit the PRACH multiple times in one random access attempt. In other words, in case the terminal device supports multiple PRACH transmissions, the terminal device may transmit the random access request multiple times in one random access attempt. For terminal devices that do not support multiple PRACH transmissions, the terminal device supports a single PRACH transmission, in which case the terminal device can only transmit a PRACH once in one random access attempt. I.e. in case the terminal device only supports single PRACH transmission, the terminal device can only send one random access request in one random access attempt.

In the prior art, whether it is single PRACH transmission or multiple PRACH transmission, a terminal device transmits a random access request based on a random access occasion (RACH occision, RO). Therefore, the method has important practical value for research on how to send the random access request so that the network equipment can distinguish the multi-PRACH transmission from the single PRACH transmission and reduce the resource waste.

Disclosure of Invention

The application discloses a communication method and a communication device, which are beneficial to network equipment to distinguish multiple PRACH transmission from single PRACH transmission, reduce resource waste and improve communication performance.

In a first aspect, a communication method according to an embodiment of the present application specifically includes:

Resources for multiple PRACH transmissions are determined. Wherein the resource includes a shared RO employed by M PRACH transmissions and a dedicated RO employed by N PRACH transmissions. M, N is a positive integer greater than or equal to 0, and the sum of M and N is equal to K, K being the number of repetitions of PRACH. The shared RO supports single PRACH transmission and multiple PRACH transmission. The dedicated RO supports multiple PRACH transmissions and does not support single PRACH transmissions. Then, the PRACH is transmitted based on at least one shared RO and/or a dedicated RO among the resources. The PRACH adopting the shared RO transmission comprises a special preamble, wherein the special preamble supports multi-PRACH transmission and does not support single PRACH transmission.

In the embodiment of the application, the shared RO and the special RO can be adopted for the multi-PRACH transmission, and the special RO only supports the multi-PRACH transmission, so that when part of the PRACH transmission of the multi-PRACH transmission can be adopted for the shared RO, the part of the PRACH transmission transmits a special preamble only for the multi-PRACH transmission. When the shared RO is positioned before the special RO in the time domain, the transmission delay of the multi-PRACH transmission is reduced, and the waste of resources is reduced. In addition, a dedicated RO may be used for a part of the sub-PRACH transmission, in which case it may be unnecessary to distinguish preambles for single PRACH transmission and multiple PRACH transmission, thus contributing to reducing the possibility of communication failure caused by insufficient preamble resources due to limited resources of the preambles, thereby improving communication performance.

In one possible design, the shared ROs employed for M PRACH transmissions do not overlap in the time domain; and/or the number of the groups of groups,

The special RO adopted by N times of PRACH transmission is not overlapped in the time domain; and/or the number of the groups of groups,

The shared RO used for M PRACH transmissions and the dedicated RO used for N PRACH transmissions do not overlap in the time domain.

Thereby helping to reduce the likelihood of multi-PRACH transmission transmit power dispersion.

In one possible design, the first M PRACH transmissions of the multiple PRACH transmissions employ a shared RO. Thereby helping to reduce resource reservation for dedicated ROs.

In one possible design, the resources for the multiple PRACH transmissions are determined based on the number of PRACH transmissions of the shared RO and/or the dedicated RO employed for the multiple PRACH transmissions.

In one possible design, transmission indication information is received, where the transmission indication information is used to indicate a number of PRACH transmissions of a shared RO and/or a dedicated RO employed for the multiple PRACH transmissions. Thereby facilitating the acquisition of the terminal equipment and reducing the operation amount of the terminal equipment.

In one possible design, the number of PRACH transmissions of the shared RO and/or the dedicated RO employed for the multiple PRACH transmissions is determined based on the number of synchronization signal blocks SSBs having an RSRP greater than or equal to an RSRP threshold.

In one possible design of the device,And X is the number of synchronous signal blocks SSB with RSRP greater than or equal to an RSRP threshold, wherein i is used for representing the weight of PRACH transmission times adopting shared RO. Thereby helping to save signaling overhead.

In one possible design, one way to specifically determine the resources for multiple PRACH transmissions is:

Determining shared ROs adopted by M PRACH transmissions from the shared ROs associated with the X SSBs in the order of the RSRP of the SSB from high to low; and determining a dedicated RO employed for N PRACH transmissions from among the dedicated ROs associated with at least one SSB of the X SSBs. Thus, the multiple PRACH transmission preferentially uses the shared RO associated with the SSB with better signal quality to transmit the PRACH, and the probability of successful PRACH transmission is improved.

In one possible design, another way to specifically determine resources for multiple PRACH transmissions is:

determining the resources for multi-PRACH transmission from ROs associated with X SSBs that are located after a random access trigger occasion in a time sequence; wherein, the ROs associated with the X SSBs include dedicated ROs and/or shared ROs, where X is the number of SSBs with RSRP greater than or equal to an RSRP threshold. Thereby helping to reduce the latency of multiple PRACH transmissions.

In one possible design, the RSRP of the X SSBs is less than a first threshold and greater than a second threshold. Thereby helping to reduce the likelihood of collisions.

In one possible design, resources for multiple PRACH transmissions are determined from RSRP of X SSBs.

In one possible design, one way to specifically determine the resources for multiple PRACH transmissions from the RSRP of X SSBs is:

If the RSRP of the X SSBs is greater than or equal to a first threshold, determining resources for multi-PRACH transmission from the shared ROs associated with the X SSBs.

Wherein, X is the number of SSB with RSRP greater than or equal to the RSRP threshold.

By the technical scheme, the method and the device help to select the shared RO sending PRACH associated with the SSB with better signal quality, and help to reduce transmission delay.

In one possible design, yet another way to specifically determine resources for multiple PRACH transmissions is:

If the RSRP of the X SSBs is less than or equal to the second threshold, determining resources for multi-PRACH transmission from the dedicated ROs associated with the X SSBs;

Through the technical scheme, the possibility of occupying the shared RO when the signal quality is poor is reduced, and resource waste is caused.

For example, the first threshold and the second threshold may be used to characterize the range of RSRP of the SSB, or the first threshold and the second threshold may each be one RSRP threshold used to select or determine resources for multiple PRACH transmissions.

In one possible design, if an RAR is received within an RAR time window corresponding to an RO employed for the jth PRACH transmission, the PRACH transmission is stopped, j is less than K, and j is a positive integer. Since the RAR time window is associated with the RO, when the RAR is received within the RAR time window corresponding to the RO (shared RO or dedicated RO) actually used for PRACH transmission at a time, and a part of the PRACH is not transmitted, the part of the PRACH which is not transmitted can not be transmitted any more, which is helpful for reducing the waste of resources.

A second aspect is a communication method according to an embodiment of the present application, specifically including:

receiving PRACH based on at least one shared RO and/or dedicated RO among resources for multiple PRACH transmissions;

Wherein, the resource comprises shared RO adopted by M times of PRACH transmission and special RO adopted by N times of PRACH transmission; m, N is a positive integer greater than or equal to 0, and the sum of M and N is equal to K, K being the number of repetitions of PRACH; sharing ROs supports single PRACH transmission and multiple PRACH transmission; the dedicated RO supports multiple PRACH transmissions and does not support single PRACH transmissions.

In one possible design, the method further comprises:

And sending transmission indication information, wherein the transmission indication information is used for indicating the PRACH transmission times of the shared RO and/or the dedicated RO adopted by the multi-PRACH transmission.

In a third aspect, a communication device according to an embodiment of the present application is configured to perform corresponding functions in the method of any one of the first aspect and the possible designs of the first aspect. The communication device comprises, for example, a processing unit and a communication unit.

Wherein the processing unit is configured to determine resources for multiple PRACH transmissions. Wherein the resource includes a shared RO employed by M PRACH transmissions and a dedicated RO employed by N PRACH transmissions. M, N is a positive integer greater than or equal to 0, and the sum of M and N is equal to K, K being the number of repetitions of PRACH. The shared RO supports single PRACH transmission and multiple PRACH transmission. The dedicated RO supports multiple PRACH transmissions and does not support single PRACH transmissions.

A communication unit for transmitting PRACH based on at least one shared RO and/or dedicated RO of the resources. The PRACH adopting the shared RO transmission comprises a special preamble, wherein the special preamble supports multi-PRACH transmission and does not support single PRACH transmission.

In one possible design, the communication device may be a terminal device, a chip, or a module.

A fourth aspect is a communication device according to an embodiment of the present application, where the communication device is configured to perform corresponding functions in the method of any of the above fourth aspect and any of the possible designs of the fourth aspect. The communication device comprises, for example, a communication unit.

Wherein the communication unit is configured to receive a PRACH based on at least one shared RO and/or a dedicated RO among resources for multiple PRACH transmissions;

In a fifth aspect, another communications device according to an embodiment of the present application includes a processor and a memory, where the memory stores a computer program, and when the processor runs the computer program, the communications device is caused to perform the method of any one of the possible designs of the first aspect and the first aspect, or perform the method of any one of the possible designs of the second aspect and the second aspect.

In a sixth aspect, a computer readable storage medium is provided, the computer readable storage medium storing a computer program, the computer program implementing the method of any one of the above first aspect and the possible designs of the first aspect, or the method of any one of the above second aspect and the possible designs of the second aspect, when the computer program is run on a computer.

In a seventh aspect, there is provided a computer program product comprising a computer program which, when run on a computer, causes the computer to perform the method of any one of the above-described first aspect and any one of the possible designs of the first aspect, or the method of any one of the above-described second aspect and any one of the possible designs of the second aspect.

In an eighth aspect, a chip system is provided, the chip system comprising at least one processor and a memory for implementing the method of any one of the possible designs of the first aspect and the first aspect, or the method of any one of the possible designs of the second aspect and the second aspect. The chip system may be formed of a chip or may include a chip and other discrete devices.

In addition, the technical effects of any one of the possible designs in the second aspect to the eighth aspect may be referred to as technical effects of different designs in the first aspect, which are not described herein.

Drawings

Fig. 1A is a flow chart of a method for non-contention based random access procedure according to an embodiment of the present application;

Fig. 1B is a flow chart of a method of a four-step random access procedure according to an embodiment of the present application;

Fig. 1C is a flow chart of a method of a two-step random access procedure according to an embodiment of the present application;

Fig. 2 is a schematic diagram of a shared RO and a dedicated RO according to an embodiment of the present application;

Fig. 3 is a schematic diagram of a network architecture of a communication system according to an embodiment of the present application;

fig. 4A is a schematic diagram of a shared RO and a dedicated RO according to an embodiment of the present application;

Fig. 4B is a schematic diagram of another shared RO and a dedicated RO according to an embodiment of the present application;

fig. 4C is a schematic diagram of still another shared RO and a dedicated RO according to an embodiment of the present application;

Fig. 5A is a schematic diagram of a random access trigger timing and an RO according to an embodiment of the present application;

Fig. 5B is a schematic diagram of a random access trigger timing and an RO according to another embodiment of the present application;

FIG. 6A is a schematic diagram of RO overlapping in time domain according to an embodiment of the present application;

FIG. 6B is a schematic diagram of a non-overlapping RO in the time domain according to an embodiment of the present application;

fig. 7A is a schematic diagram of a correspondence relationship between RO and RAR time window according to an embodiment of the present application;

FIG. 7B is a diagram illustrating a relationship between RO and RAR time window according to another embodiment of the present application;

FIG. 7C is a diagram illustrating a relationship between RO and RAR time window according to another embodiment of the present application;

FIG. 8 is a flow chart of a communication method according to an embodiment of the application;

FIG. 9 is a schematic diagram of a mapping relationship between SSB and RO according to an embodiment of the present application;

Fig. 10A is a schematic structural diagram of a communication device according to an embodiment of the present application;

Fig. 10B is a schematic structural diagram of another communication device according to an embodiment of the present application.

Detailed Description

In the present application, "and/or" is merely an association relationship describing an association object, and indicates that three relationships may exist, for example, a and/or B may indicate: a exists alone, A and B exist together, and B exists alone. In this context, the character "/" indicates that the front and rear associated objects are an "or" relationship.

The following at least one (item) or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b or c may represent: a, b, c, a and b, a and c, b and c, or a, b and c, wherein each of a, b, c may itself be an element, or may be a collection comprising one or more elements.

The term "at least one" in the present application means one or more. "plurality" means two or more. The first, second, etc. descriptions in the embodiments of the present application are only used for illustrating and distinguishing the description objects, and no order is used, nor is the number of the devices in the embodiments of the present application limited, and no limitation on the embodiments of the present application should be construed. For example, the first threshold and the second threshold are merely for distinguishing between different thresholds, and are not intended to represent differences in the size, priority, importance, or the like of the two thresholds.

In the present disclosure, "exemplary," "in some embodiments," "in other embodiments," etc. are used to indicate an example, instance, or illustration. Any embodiment or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, the term use of an example is intended to present concepts in a concrete fashion.

"Of", "corresponding (corresponding, relevant)", "corresponding (corresponding)", and "associated" in the present application may be sometimes used in combination, and it should be noted that the meanings to be expressed are consistent when the distinction is not emphasized. Communication, transmission, etc. may sometimes be mixed in embodiments of the present application, it should be noted that the meaning expressed is consistent with the de-emphasis. For example, a transmission may include sending and/or receiving, either nouns or verbs.

In the application, "equal to" can be used in conjunction with "less than" or "greater than" but not in conjunction with "less than" and "greater than" at the same time. When the combination of the 'equal' and the 'less' is adopted, the method is applicable to the technical scheme adopted by the 'less'. When being used with 'equal to' and 'greater than', the method is applicable to the technical scheme adopted by 'greater than'.

First, some terms involved in the embodiments of the present application will be explained for easy understanding by those skilled in the art.

1. And a terminal device. The terminal device according to the embodiment of the present application is a device having a wireless communication function, and may be referred to as a terminal (terminal), a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), an access terminal device, a vehicle-mounted terminal device, an industrial control terminal device, a UE unit, a UE station, a mobile station, a remote terminal device, a mobile device, a UE terminal device, a wireless communication device, a UE agent, or a UE apparatus. The terminal device may be fixed or mobile. It should be noted that the terminal device may support at least one wireless communication technology, such as NR, 6G, or next generation wireless communication technology. For example, the terminal device may be a mobile phone, a tablet, a desktop, a notebook, a body, a car-mounted terminal, a Virtual Reality (VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned (SELF DRIVING), a wireless terminal in teleoperation (remote medical surgery), a wireless terminal in smart grid (SMART GRID), a wireless terminal in transportation security (transportation safety), a wireless terminal in smart city (SMART CITY), a wireless terminal in smart home (smart home), a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal DIGITAL ASSISTANT, PDA), a handheld device with wireless communication functionality, a computing device or other processing device connected to a wireless modem, a wearable device, a terminal device in a future mobile communication network, or a terminal in a future evolved public mobile network (public land mobile network, PLMN) or the like. In some embodiments of the present application, the terminal device may also be a device with a transceiver function, such as a chip system. The chip system may include a chip and may also include other discrete devices.

2. A network device. In the embodiment of the present application, the network device is a device that provides a wireless communication function for the terminal device, and may also be referred to as a radio access network (radio access network, RAN) device, or an access network element, etc. Wherein the network device may support at least one wireless communication technology, such as NR, 6G, or next generation wireless communication technology, etc. By way of example, network devices include, but are not limited to: next generation base stations (the next generation nodeB, gNB), evolved node bs (enbs), radio network controllers (radio network controller, RNCs), node Bs (NB), base station controllers (base station controller, BSC), base transceiver stations (base transceiver station, BTSs), home base stations (e.g., home evolved node B, or home node B, HNB), baseband units (BBU), transceiving points (TRANSMITTING AND RECEIVING points, TRPs), transmitting points (TRANSMITTING POINT, TP), mobile switching centers, and the like in a fifth generation mobile communication system (5 th-generation, 5G). The network device may also be a wireless controller, a centralized unit (centralized unit, CU), and/or a Distributed Unit (DU) in the cloud wireless access network (cloud radio access network, CRAN) scenario, or the network device may be a relay station, an access point, an in-vehicle device, a terminal device, a wearable device, and a network device in future mobile communications or a network device in a future evolved PLMN, etc. In some embodiments, the network device may also be an apparatus, such as a system-on-a-chip, having functionality for providing wireless communication for the terminal device. By way of example, the chip system may include a chip, and may also include other discrete devices.

In some embodiments, the network device may also communicate with an internet protocol (Internet Protocol, IP) network, such as the internet, a private IP network, or other data network, or the like.

3. Random access procedure. In the embodiment of the application, the terminal equipment can realize uplink synchronization with the network equipment through a random access process. Random access procedures from the perspective of medium access control (MEDIA ACCESS control, MAC) layer collision resolution can be classified into contention-based random access procedures and non-contention-based random access procedures. The contention-based random access procedure may be referred to as a collision-based random access procedure. The non-contention based random access procedure may also be referred to as a non-collision based random access procedure.

As shown in fig. 1A, a method flowchart of a non-contention based random access procedure specifically includes the following steps.

111. The terminal equipment sends a random access request, and the network equipment receives the random access request correspondingly. Specifically, the random access request includes a preamble allocated by the network device to the terminal device.

112. The network device receives the random access request and transmits a random access response (random access response, RAR). Correspondingly, the terminal equipment receives the RAR, thereby realizing uplink synchronization.

Specifically, after receiving the random access request, the network device estimates the transmission delay between the network device and the terminal device based on the preamble. Then, the network device calibrates the uplink timing based on the estimated transmission delay, and indicates to the terminal device through the random access response. For example, the network device may transmit the RAR on a payload (payload) of a physical downlink shared channel (physical downlink SHARED CHANNEL, PDSCH). Further, the RAR may be obtained by scrambling a random access radio network temporary identity (random access radio network temporary identifier, RA-RNTI). In some embodiments, the value of the RA-RNTI is determined by the location of the time-frequency resources carrying the preamble.

For the terminal device, after the terminal device sends the random access request, the terminal device may monitor a physical downlink control channel (physical downlink control channel, PDCCH) in a RAR time window (RAR window) according to the RA-RNTI to obtain downlink control information (downlink control information, DCI). Then, the terminal device parses the PDSCH payload using the RA-RNTI according to the DCI to receive the corresponding RAR scrambled by the RA-RNTI. If the RAR is received in the RAR window, the random access is considered to be successful, and uplink time synchronization is realized.

If the RAR is not received in the RAR window, the random access is considered to be failed, and the uplink time synchronization is not realized.

Furthermore, the contention-based random access procedure can be divided into a four-step random access procedure and a two-step random access procedure based on steps.

As shown in fig. 1B, a method flowchart of a four-step random access procedure specifically includes the following steps:

121. The terminal equipment sends a random access request, and the network equipment receives the random access request correspondingly. The random access request may also be referred to as message1 (Msg 1). The preamble is included in Msg 1.

122. The network device receives the random access request and sends the RAR. Correspondingly, the terminal device receives the RAR. The RAR may also be referred to as message2 (Msg 2).

For example, msg2 may contain an amount of time adjustment required for specifying uplink synchronization, uplink resources required for the terminal device to transmit message3 (message 3, msg 3), temporary cell radio network temporary identity (TC-RNTI), and the like.

For a specific description of steps 121 and 122, reference may be made to the related description in fig. 1A, and the detailed description will not be repeated here.

123. The terminal equipment receives the random access response and sends Msg3. Correspondingly, the network device receives Msg3.

For example, the terminal device sends Msg3 on a Physical Uplink Shared Channel (PUSCH) SHARE CHANNEL. For example, the Msg3 may contain a unique identifier of the terminal device. This flag may be used for conflict resolution for Msg 4. For example, for a terminal device in a connected state, the only flag of the terminal device is the cell-radio network temporary identity (cell-radio network temporary identifier, C-RNTI). For another example, for a terminal device in a non-connected state, the unique identifier of the terminal device is the unique terminal device identifier from the core network.

124. The network device receives Msg3 and sends message4 (message 4, msg 4). Corresponding to the above. The terminal device receives Msg4.

Specifically, the network device carries the flag for uniquely identifying the terminal device in Msg4 in the collision resolution mechanism to indicate the winning terminal device. And random access will be re-initiated for terminal devices that are not winning in the collision resolution. If the PDSCH received by the terminal device in the Msg4 is scrambled by the TC-RNTI specified by the Msg2, the TC-RNTI is converted into the C-RNTI after the random access is successful for the terminal device in the non-connected state.

It should be noted that, in the first two steps of Msg1 and Msg2 in the four steps of random access process, uplink time synchronization is mainly completed, and the main purpose of Msg3 and Msg4 is to assign a unique and legal identity to the terminal device for the subsequent data transmission.

As shown in fig. 1C, a method flowchart of a two-step random access procedure specifically includes the following steps:

131. The terminal device sends MsgA. Correspondingly, the network device receives MsgA. MsgA include Msg1 and Msg3.

132. The network device sends MsgB to the terminal device. Correspondingly, the terminal device receives MsgB. MsgB includes Msg2 and Msg4. Thereby realizing uplink synchronization.

It should be noted that, in the embodiment of the present application, since the terminal device sends the random access request in the PRACH, the terminal device sends the random access request may be referred to as: the terminal device transmits the PRACH. In addition, the preamble in the embodiment of the present application may be referred to as a preamble sequence, a preamble, etc., which is not limited.

3. Single PRACH transmission. The single PRACH transmission in the embodiment of the present application may also be referred to as SINGLE PRACH transmission. Specifically, the single PRACH transmission supports that the terminal device transmits a random access request or PRACH only once in one random access attempt (one RACH ATTEMPT). Wherein one random access attempt performs one random access procedure. In other words, in the case where the terminal device adopts a single PRACH transmission, a random access request or PRACH is transmitted in a random access procedure. For example, taking a four-step random access procedure as an example, the PRACH transmission may be understood as an Msg1 transmission again, that is, if the terminal device adopts a single PRACH transmission, msg1 is sent once in a single random access procedure.

4. Multiple PRACH transmissions. The multiple PRACH transmissions in the embodiments of the present application may also be referred to as mutiple PRACH transmissions. Specifically, the multi-PRACH transmission supports that the terminal device sends multiple random access requests or PRACH in one random access attempt. That is, in case that the terminal device adopts multi-PRACH transmission, multiple random access requests or PRACH may be transmitted in one random access procedure. For example, taking a four-step random access procedure as an example, the PRACH transmission may be understood as an Msg1 transmission again, that is, if the terminal device adopts a multi-PRACH transmission, multiple Msg1 transmissions are supported in one random access procedure.

For example, the terminal device adopts multiple PRACH transmission, and the number of PRACH repetitions is 4 as an example. The terminal device may support transmitting a random access request on 4 ROs, which are different in time domain, respectively in one random access attempt. For another example, in the case that the terminal device supports multiple chains (mutiple Tx chains), the terminal device may also simultaneously use 4 different antennas to respectively transmit random access requests on ROs different in the frequency domain.

The number of times of PRACH repetition may be referred to as the number of times of random access request repetition, PRACH repetition, the number of times of PRACH transmission, and the like. In the four-step random access procedure, the number of repetitions of the PRACH may also be referred to as Msg1 repetition, or the number of repetitions of Msg 1.

5. Random access trigger occasions. In the embodiment of the application, the random access triggering time can be understood as the time or time unit for triggering the terminal equipment to initiate random access.

Take NR as an example. For example, the random access trigger occasion may be a time slot or symbol that triggers the terminal device to initiate random access.

In some embodiments, the terminal device detects a power-on operation, triggering random access. In this case, the random access trigger occasion may refer to a time at which the terminal device detects the power-on operation. Or in other embodiments, the terminal device detects a network disconnection, triggering random access. In this case, the random access trigger occasion may refer to a symbol or a time at which the terminal device detects the network disconnection.

6. RO. In the embodiment of the application, RO refers to time-frequency resources used for PRACH transmission or time-frequency resources used for random access request transmission. That is, the terminal device transmits a random access request based on the RO, or the terminal device transmits a random access request on the RO. Specifically, by establishing the association relationship between the SSB and the RO, the terminal device can perform corresponding selection after receiving the SSB, and then send a random access request based on the RO associated with the selected SSB, so that after receiving the random access request, the network device can identify the SSB selected by the terminal device, and then send a random access response by adopting a beam corresponding to the SSB selected by the terminal device, thereby being beneficial to improving the possibility of uplink synchronization.

For example, the terminal device may make the selection of the SSB based on the RSRP of the SSB. For example, the terminal device selects an SSB having an RSRP greater than the RSRP threshold from the received SSBs. For example, the RSRP threshold may be indicated to the terminal device by the network device, may be predefined by a protocol, or may be determined by the terminal device by other means, which is not limited.

In the present application, one RO may be associated with or correspond to one SSB. Or multiple ROs are associated or correspond to one SSB. Still another or multiple SSBs are associated with or correspond to one RO. The method is suitable for the sending beam of the SSB in which direction the terminal equipment is located in can be judged by the network equipment from the RO in which the received preamble is located in a multi-direction beam scene.

In the case where a plurality of SSBs correspond to one RO, the network device can distinguish between different SSBs corresponding to the same RO by the preamble. For example, RO1 is taken as an example. SSB1 and SSB2 correspond to RO 1. In this case, SSB1, SSB2 may correspond to different preambles. For example, SSB1 corresponds to preamble 11 and preamble 12; SSB2 corresponds to preamble 21 and preamble 22. So that the terminal device can transmit the preamble 11 or the preamble 12 based on RO1 when selecting SSB 1. Or the terminal device may transmit the preamble 21 or the preamble 22 based on RO1 when selecting SSB 2.

In the embodiment of the application, the existing association rule or mapping rule of the SSB and the RO can be adopted to establish the corresponding relationship between the SSB and the RO, and the improved association rule or mapping rule of the SSB and the RO can also be adopted to establish the corresponding relationship between the SSB and the RO. The correspondence between SSB and RO may be referred to as association between SSB and RO, mapping between SSB and RO, and the like, which are not limited thereto.

However, whether it is a single PRACH transmission or a multiple PRACH transmission, it is for the terminal device to transmit a random access request based on the RO. In this way, it may not be possible for the network device to distinguish whether it is a single PRACH transmission or a multiple PRACH transmission after receiving the random access request, so that the network device may respond to the RAR for each preamble, which may easily cause the network device to send the RAR for multiple preamble responses to the terminal device in one random access attempt, resulting in resource waste. Therefore, how to distinguish whether a single PRACH transmission or a multiple PRACH transmission is a matter of investigation.

The first way is:

the ROs are divided into single ROs (sros) and multiple ROs (mros). Wherein sRO only supports single PRACH transmissions, not multiple PRACH transmissions. mRO support only multiple PRACH transmissions and not single PRACH transmissions. That is, in case that the terminal device adopts a single PRACH transmission, the random access request is transmitted based on sRO. In the case of multiple PRACH transmission, the terminal device sends a random access request based on mRO. So that the network device can distinguish whether it is a single PRACH transmission or a multiple PRACH transmission by the resources.

However, this approach may present a risk of lengthy delays. Take NR as an example. For example, as shown in fig. 2, sRO is located before mRO in the time domain, and in the case that the terminal device uses multiple PRACH transmission, the terminal device needs isochronous domain resources to reach mRO to send the random access request.

Note that, in the first mode, sRO is a conventional RO (legacy RO), mRO is a new RO, i.e., an additional RO or new RO. Or sRO and mRO are both legacy ROs.

Specifically, legacy ROs refer to ROs that map with SSBs on existing RO resources. Existing RO resources refer to resources configured based on existing (e.g., 3GPP protocol version R15, version R16, or version R17) PRACH configuration period and Association period (number of PRACH configuration period).

The second way is:

The preamble is divided into a legacy preamble and a dedicated preamble. Wherein, the legacy preamble only supports single PRACH transmission and does not support multiple PRACH transmission. The dedicated preamble only supports multiple PRACH transmissions and does not support single PRACH transmissions. In this case, multiple PRACH transmissions and single PRACH transmission resources are shared. I.e., for one RO, both multiple PRACH transmissions and single PRACH transmissions are supported. While helping network devices to distinguish whether a single PRACH transmission or a multiple PRACH transmission is performed by a preamble, the preamble is limited, especially for scenarios where multiple SSBs are associated with one RO, there may be insufficient preambles, increasing the risk of failure to communicate.

For example, one RO corresponds to 64 preambles in NR. Currently, preambles have been used to distinguish between a 4-step random access procedure and a 2-step random access procedure, to distinguish between repetition of Msg3, and to distinguish between a contention-based random access procedure and a non-contention-based random access procedure. Therefore, the number of preambles for distinguishing single PRACH transmission from multiple PRACH transmission may be less than 64, and thus, there may be a case where the preambles are insufficient for a scenario where a plurality of SSBs are associated with one RO.

In view of this, the embodiment of the present application provides a communication method, which uses time-frequency resources and preambles to jointly distinguish between multiple PRACH transmissions and single PRACH transmissions, so that a terminal device can use preambles only supporting multiple PRACH transmissions to perform part or all of the multiple PRACH transmissions based on ROs supporting single PRACH transmissions, which is helpful for improving resource utilization and reducing communication delay at the same time; the risk of incapacity of communication due to limited resources of the preamble can be reduced by adding ROs supporting only multiple PRACH transmissions.

In the embodiment of the present application, ROs that support multiple PRACH transmissions and do not support single PRACH transmissions may be referred to as dedicated ROs, DEDICATED RO, separate RO, additional ROs, and the like, which are not limited thereto. The ROs supporting single PRACH transmission and multiple PRACH transmission may be also referred to as shared ROs, and the like, which are not limited. For convenience of description, the following embodiments will take as an example that ROs supporting multiple PRACH transmissions and not supporting single PRACH transmissions are called dedicated ROs, and ROs supporting multiple PRACH transmissions and single PRACH transmissions are called shared ROs.

In addition, it should be noted that, in the embodiment of the present application, the dedicated RO and the shared RO are legacy ROs. Or in the embodiment of the present application, the dedicated RO may be understood as an additional RO, and the shared RO is a legacy RO.

For legacy RO, reference may be made to the description of the first mode, and the description is omitted here.

Fig. 3 is a network architecture diagram of a communication system according to an embodiment of the present application. The communication system as shown in the figure comprises a network device and a terminal device. The network equipment and the terminal equipment adopt a wireless communication mode. With respect to the network device and the terminal device, reference may be made to related descriptions in the term explanation, which are not repeated here.

It should be noted that fig. 3 is only a schematic illustration of a network architecture of a communication system, and does not limit the communication system to which the embodiment of the present application is applied. For example, the network architecture of the communication system to which the embodiment of the present application is applicable may include a plurality of network devices, and/or a plurality of terminal devices, which is not limited thereto.

Taking the network architecture shown in fig. 3 as an example, the communication method of the embodiment of the present application will be described in detail with reference to a specific scenario.

Scene 1: multiple PRACH transmissions. Take the number of repetitions of PRACH as K as an example. In addition, in the case that the number of repetition of the PRACH is K, the terminal device actually supports transmitting a maximum of K random access requests in one random access attempt. In other words, the terminal device actually supports a maximum of K transmissions of PRACH in one random access attempt.

Specifically, for multiple PRACH transmissions, M PRACH transmissions employ shared ROs and N PRACH transmissions employ dedicated ROs in one random access attempt. Wherein the sum of M and N is K, and M, N is a positive integer greater than or equal to 0. For example, when M is 0, in this random access attempt, dedicated RO is used for multiple PRACH transmissions. For another example, when N is 0, the shared RO is used for multiple PRACH transmissions in the random access attempt. For another example, when M has a value of 1,1 PRACH transmission uses a shared RO and the remaining K-1 PRACH transmissions use a dedicated RO.

It should be noted that, in the embodiment of the present application, one RO (may be a shared RO or a dedicated RO) is used for one PRACH transmission. In special cases, one RO may also be used for multiple PRACH transmissions. For example, one RO associates SSB1 and SSB2, then the terminal device may send PRACH twice with different chain based on the ROs associated with SSB1 and SSB2 after selecting SSB1 and SSB 2. Chain is understood here as a link or antenna.

Further, for multiple PRACH transmissions, in one random access attempt, the first M PRACH transmissions employ shared ROs and the last N PRACH transmissions employ dedicated ROs. Thereby helping to reduce transmission delay. For example, if M takes a value of 1, the first PRACH transmission uses a shared RO, and the 2 nd to K th PRACH transmissions use a dedicated RO.

In some embodiments, the PRACH employing shared RO transmissions includes a dedicated preamble. Wherein the dedicated preamble supports multiple PRACH transmissions and does not support single PRACH transmissions. That is, a dedicated preamble that supports only multiple PRACH transmissions with shared RO transmissions is employed. So that the network device recognizes whether the multi-PRACH transmission or the single PRACH transmission is performed after the shared RO receives the preamble.

In some embodiments of the application, ROs for multiple PRACH transmissions are non-overlapping in the time domain. Thereby helping to reduce the likelihood of multi-PRACH transmission transmit power dispersion. That is, the shared ROs employed for M PRACH transmissions do not overlap in the time domain, the dedicated ROs employed for N PRACH transmissions do not overlap in the time domain, and the shared ROs employed for M PRACH transmissions do not overlap in the time domain with the dedicated ROs employed for N PRACH transmissions.

For example, ROs for multi-PRACH transmission are shown in fig. 4A, including 2 shared ROs and 2 dedicated ROs. The 4 ROs (i.e., 2 shared ROs and 2 dedicated ROs) are non-overlapping in the time domain.

Or some or all ROs for multiple PRACH transmissions may also overlap in the time domain. For example, some or all ROs for multi-PRACH transmission do not overlap in the frequency domain. The scheme can be suitable for a scene that the terminal equipment adopts multiple chain transmission. For example, ROs for multi-PRACH transmission include shared RO1, shared RO2, dedicated RO1, and dedicated RO2, as shown in fig. 4B. Wherein, the shared RO1 and the dedicated RO1 are not overlapped in the frequency domain and are overlapped in the time domain, and the shared RO1, the shared RO2 and the dedicated RO2 are not overlapped in the time domain. For shared RO1 and dedicated RO1, the terminal device may transmit PRACH using different links. If the terminal device transmits PRACH once using link 1 and shared RO1, and transmits PRACH once using link 2 and dedicated RO 1. For example, ROs for multi-PRACH transmission are shown in fig. 4C, including 1 shared RO and 2 dedicated ROs. The 3 ROs (i.e., 1 shared RO and 2 dedicated ROs) are non-overlapping in the frequency domain and overlapping in the time domain.

Further, in some embodiments, the first M PRACH transmissions use shared ROs in order to improve efficiency of uplink synchronization and random access success.

For example, the terminal device may determine the resources of the multiple PRACH transmissions by:

mode 1: the network device sends transmission indication information to the terminal device. The transmission indication information is used for indicating the number of PRACH transmissions in which the multiple PRACH transmissions employ a shared RO and/or a dedicated RO. Thereby facilitating the acquisition of the terminal equipment and reducing the operation amount of the terminal equipment.

For example, the network device may indicate M and/or N by adding a parameter in the system message (system information, SI). For example, the PRACH transmission number indicating that the shared RO is used is M. The system message may be RACH-configCommon, and the network device may indicate to the terminal device that the number of PRACH transmissions using shared RO is M for multiple PARCH transmissions by adding a parameter m_prach_trans to RACH-configCommon. The parameter m_prach_trans may be referred to as multi_prach_trans or m_prach_trans, and the name of the parameter m_prach_trans is not limited.

In this case, the terminal device may determine resources for the multiple PRACH transmission based on the number of PRACH transmissions in which the multiple PRACH transmissions employ shared ROs and/or dedicated ROs.

For example, in the case where the number of repetitions of PRACH is 2 and the number of PRACH transmissions by the network device indicating that the terminal device adopts the shared RO is 1, the terminal device may select, from the shared ROs associated with at least one SSB, the shared RO that is located after the random access trigger timing and has the smallest time interval with the random access trigger timing as the shared RO adopted for the first PRACH transmission. And the terminal device may select the dedicated RO from among the dedicated ROs associated with the at least one SSB after the selected shared RO as the dedicated RO employed for the second PRACH transmission.

Specifically, the at least one SSB refers to an SSB, where RSRP in the SSBs received by the terminal device is greater than or equal to an RSRP threshold.

Of course, the above description is only an illustration of an implementation of determining resources for multiple PRACH transmissions for one terminal device, specifically in connection with multiple PRACH transmissions using shared ROs and/or dedicated ROs. The embodiment of the present application is not limited thereto. For example, in consideration of factors such as signal quality, delay or multiple chain, the terminal device may also determine resources for multiple PRACH transmission in conjunction with RSRP of SSB, location of RO in time domain, and so on, which will not be described in detail herein. For example, the terminal device determines the shared RO adopted by M PRACH transmissions from the shared ROs associated with the X SSBs according to the order of RSRP of the SSBs from high to low; and determining a dedicated RO employed by the N PRACH transmissions from among dedicated ROs associated with at least one SSB of the X SSBs. The RSRP of the X SSBs herein is greater than or equal to the RSRP threshold. See, in particular, the relevant description in mode 2.1, which is not described in detail here.

Mode 2: the terminal device determines resources for the multi-PRACH transmission by predefined rules.

The terminal equipment determines PRACH transmission times of sharing RO and/or special RO adopted by the multi-PRACH transmission according to the number of SSB; then, the terminal device determines resources for the multiple PRACH transmission according to the number of PRACH transmissions in which the multiple PRACH transmissions employ the shared RO and/or the dedicated RO.

The number of SSBs refers to the number of SSBs with better received signal quality/strength in SSBs received by the terminal device. For example, the number of SSBs is the number of SSBs, in which RSRP is greater than or equal to the RSRP threshold, in the SSBs received by the terminal device. With respect to the RSRP threshold, reference may be made to the relevant description in the noun interpretation, which is not repeated here. It should be understood that in the embodiment of the present application, the terminal device may also measure the received signal quality/strength by other parameters, such as signal quality (REFERENCE SIGNAL RECEIVING quality, RSRQ), which is not limited.

For example, the number of PRACH transmissions using a shared RO is M, where,X is the number of SSB. i is a weight used to characterize the number of PRACH transmissions with shared ROs. For example, the value of i may be/>1. 2, Etc. Specifically, i may be indicated by the network device to the terminal device, may be predefined by a protocol, or may be determined by the terminal device based on a policy or rule, which is not limited. In addition, the network device may also directly indicate/>, to the terminal deviceOr predefined/> by protocolOr the terminal device determines/>, based on a certain policy or rule

For example, the value of i is related to the number of shared ROs associated with one SSB in one Association period. For example, the terminal device selects 1 SSB as SSB1, and two shared ROs associated with SSB1 in one Association period, in which case i can be valuedOr may be 1. If the terminal device selects 1 SSB to be SSB2, there are 1 shared ROs associated with SSB2 in one Association period, in this case, the value of i may be 1 or a positive integer greater than 1.

Generally, when the value of X is constant, the smaller the value of i is, the larger the number of PRACH transmissions using the shared RO is. Under the condition that the value of X is fixed, when the value of i is larger than a certain value, the value of M is not changed. For example, when the value of X is 1 and the value of i is less than 1, the smaller the value of i is, the larger the value of M is; x is 1, and when i is greater than or equal to 1, M is 1 and is unchanged.

Of course, the foregoing is merely illustrative of the value of i, and the value of i may also relate to a parameter other than the number of shared ROs associated with one SSB in one Association period, or may relate to a plurality of parameters, or may be a fixed value, regardless of the parameter. The application is not limited in this regard.

Further, in some embodiments, the terminal device may determine the resources for the multiple PRACH transmissions based on the number of PRACH transmissions using the shared RO and/or the dedicated RO according to the multiple PRACH transmissions, based on:

The terminal device determines the shared RO used for M PRACH transmissions from among the shared ROs associated with the X SSBs in order of the RSRP of the SSB from high to low. And determining a dedicated RO employed for N PRACH transmissions from among the dedicated ROs associated with at least one SSB of the X SSBs. Thereby helping to increase the likelihood of random access success.

It should be understood that at least one SSB herein may refer to X SSBs, or may be SSBs other than the SSBs associated with the shared RO employed for M PRACH transmissions among the X SSBs. For example, the terminal device may determine the dedicated RO used for N PRACH transmissions from among the dedicated ROs associated with at least one SSB of the X SSBs in order of higher RSRP of the SSBs.

For example, the terminal device receives only 1 SSB satisfying the RSRP greater than or equal to the RSRP threshold value from the SSBs, and in this case, the value of X is 1, that is, the multiple PRACH transmission adopts the same beam. Thus, the terminal device selects a shared RO to be used for M PRACH transmissions from among shared ROs associated with SSBs having an RSRP greater than or equal to the RSRP threshold. The terminal device then selects a dedicated RO to be used for N PRACH transmissions from among the dedicated ROs associated with SSBs having an RSRP greater than or equal to the RSRP threshold.

Fig. 5A is a schematic diagram of a portion of an RO associated with an SSB according to an embodiment of the present application. The partial ROs associated with the SSB include shared RO1, private RO2, shared RO2, private RO3, private RO4, and the like.

Take PRACH repetition number of 4 and value of M of 1 as an example. In the case where the random access trigger timing of the terminal device is T1, the shared RO1 is the shared RO located after T1 and having the smallest time interval with T1, and therefore the terminal device selects the shared RO1 as the shared RO employed for the 1 st PRACH transmission. And the dedicated RO1, the dedicated RO2, and the dedicated RO3 are three dedicated ROs that are located after the shared RO1 and have a small time interval between the shared RO1 among the dedicated ROs associated with the SSB, the terminal device may select the dedicated RO1 as the dedicated RO used for the 2 nd PRACH transmission, the dedicated RO2 as the dedicated RO used for the 3 rd PRACH transmission, and the dedicated RO3 as the dedicated RO used for the 4 th PRACH transmission.

Take PRACH repetition number of 2 and M value of 1 as an example. In the case where the random access trigger timing of the terminal device is T2, the dedicated RO2 is a dedicated RO located after T2 and having the smallest time interval with T2. Thus, the terminal device selects the dedicated RO2 as the shared RO employed for the 1 st PRACH transmission. And the shared RO2 is located after the dedicated RO2 and is the shared RO having the smallest time interval with the dedicated RO2 among the shared ROs associated with the SSB, the terminal device selects the shared RO2 as the shared RO employed for the 2 nd PRACH transmission. Or in the case that the random access trigger timing of the terminal device is T2, the shared RO2 is the shared RO located after T2 and having the smallest time interval with T2, so the terminal device selects the shared RO2 as the shared RO employed for the 1 st PRACH transmission. And the dedicated RO3 is a dedicated RO located after the shared RO2 and having the smallest time interval between the shared RO2 among the dedicated ROs associated with the SSB, the terminal device may select the dedicated RO3 as the dedicated RO employed for the 2 nd PRACH transmission.

For example, there are a plurality of SSBs that satisfy the RSRP greater than or equal to the RSRP threshold among the SSBs, in which case the value of X is greater than 1, i.e. the multiple PRACH transmission may employ DIFFERENT BEAM. Thus, the terminal device may select the shared RO employed for M PRACH transmissions from among the shared ROs associated with the plurality of SSBs in order of RSRP of the SSBs from high to low. Then, the terminal device selects a dedicated RO used for N PRACH transmissions from among the dedicated ROs associated with at least one SSB of the plurality of SSBs.

Take SSB with RSRP greater than or equal to the RSRP threshold as SSB1 and SSB2, respectively, as an example. Wherein the RSRP of SSB1 is greater than the RSRP of SSB 2. FIG. 5B is a schematic diagram of a portion of an RO associated with SSB1 and SSB2 according to an embodiment of the present application. As shown, the partial ROs associated with SSB1 include shared RO11, private RO11, shared RO12, and private RO12, and the partial ROs associated with SSB2 include shared RO21, private RO21, shared RO22, and private RO22.

Take PRACH repetition number of 4 and M value of 2 as an example. In the case where the random access trigger timing of the terminal device is T0, the shared RO11 is the shared RO located after T0 and having the smallest time interval with T0, and therefore, the terminal device selects the shared RO11 as the shared RO used for the 1 st PRACH transmission, the shared RO21 as the shared RO used for the 2 nd PRACH transmission, the dedicated RO11 as the dedicated RO used for the 3 rd PRACH transmission, and the dedicated RO21 as the dedicated RO used for the 4 th PRACH transmission. Or when the random access trigger time of the terminal equipment is T0, the terminal equipment selects the shared RO11 as the shared RO adopted by the 1 st PRACH transmission, selects the special RO21 as the special RO adopted by the 2 nd PRACH transmission, selects the shared RO12 as the shared RO adopted by the 3 rd PRACH transmission, and selects the special RO22 as the special RO adopted by the 4 th PRACH transmission.

It should be noted that, the terminal device may also determine the resources for multiple PRACH transmission according to the number of PRACH transmissions using the shared RO and/or the dedicated RO in other manners, for example, in the manner of determining the resources for multiple PRACH transmission according to the number of PRACH transmissions using the shared RO and/or the dedicated RO in the manner of manner 1. The application is not limited in this regard.

Mode 2.2: the terminal device determines resources for multi-PRACH transmission from ROs that are located after the random access trigger occasion and associated with the X SSBs in a time sequence.

Wherein, the X SSBs refer to the number of SSBs with better receiving channel quality/strength among the SSBs received by the terminal device. Reference may be made specifically to the relevant description in mode 2.1, and no further description is given here. The ROs associated with the X SSBs refer to shared ROs associated with the X SSBs, and/or dedicated ROs associated with the X SSBs.

For example, the terminal device receives only 1 SSB satisfying the RSRP greater than or equal to the RSRP threshold value from the SSBs, and in this case, the value of X is 1, that is, the multiple PRACH transmission adopts the same beam. Thus, the terminal device determines resources for the multi-PRACH transmission from ROs associated with SSBs having RSRP greater than or equal to the RSRP threshold in time order.

Taking PRACH repetition number of 4 as an example, a specific manner of determining resources for multi-PRACH transmission will be described with reference to fig. 5A.

As shown in fig. 5A, in the case where the random access trigger timing of the terminal device is T1, the shared RO1 is located after T1 and the time interval with T1 is minimum. Thus, the terminal device selects shared RO1 as the RO employed for the 1 st PRACH transmission, dedicated RO1 as the RO employed for the 2 nd PRACH transmission, dedicated RO2 as the RO employed for the 3 rd PRACH transmission, and shared RO2 as the RO employed for the 4 th PRACH transmission in time order.

As shown in fig. 5A, in the case where the random access trigger timing of the terminal device is T2, the dedicated RO2 is the RO located after T2 and having the smallest time interval with T2. Thus, the terminal device selects the dedicated RO2 as the RO employed for the 1 st PRACH transmission, the shared RO2 as the RO employed for the 2 nd PRACH transmission, the dedicated RO3 as the RO employed for the 3 rd PRACH transmission, and the dedicated RO4 as the RO employed for the 4 th PRACH transmission in chronological order.

For example, there are a plurality of SSBs that satisfy the RSRP greater than or equal to the RSRP threshold among the SSBs, in which case the value of X is greater than 1, i.e. the multiple PRACH transmission may employ DIFFERENT BEAM. The terminal device determines resources for multi-PRACH transmission from ROs associated with a plurality of SSBs having an RSRP greater than or equal to an RSRP threshold in a time sequence.

Taking PRACH repetition number of 4 as an example, a specific manner of determining resources for multi-PRACH transmission will be described with reference to fig. 5B.

In the case where the random access trigger timing of the terminal device is T0, the shared RO11 is the RO located after T0 and having the smallest time interval with T0. Therefore, the terminal device selects the shared RO11 as the shared RO used for the 1 st PRACH transmission, selects the shared RO21 as the shared RO used for the 2 nd PRACH transmission, selects the dedicated RO11 as the dedicated RO used for the 3 rd PRACH transmission, and selects the dedicated RO21 as the dedicated RO used for the 4 th PRACH transmission.

The above-described fig. 5A and 5B are only for illustrative purposes, and do not limit the mapping relationship between the SSB-related dedicated RO and the shared RO. In addition, the foregoing merely illustrates selecting an RO for the terminal device, and the selection manner of the specific RO in the embodiment of the present application is not limited.

It should be further noted that, in the embodiment of the present application, in the case where the number of PRACH transmissions of the shared RO and/or the dedicated RO is determined for the reference multiple PRACH transmissions of the resource for multiple PRACH transmissions, the number of PRACH transmissions of the shared RO and/or the dedicated RO for multiple PRACH transmissions may be determined by the terminal device in addition to the network device in mode 1 or the terminal device in mode 2.1 according to a predefined rule, or may be determined by the terminal device in combination with a parameter indicated by the network device and a rule, which is not limited.

Mode 3: the terminal device determines resources for multi-PRACH transmission from ROs associated with the X SSBs according to RSRP of the X SSBs.

For example, the terminal device determines resources for multi-PRACH transmission from ROs associated with X SSBs according to a size relationship between RSRP of the SSBs and a threshold.

The description of X SSBs may be referred to in mode 2, and will not be described herein.

For example, the RSRP of the X SSBs is greater than or equal to a first threshold, and the terminal device determines resources for multi-PRACH transmission from the shared ROs associated with the X SSBs. That is, in case that RSRP of X SSBs is greater than the first threshold, the multiple PRACH transmissions all employ shared ROs. Thereby helping to select the shared RO sending PRACH associated with the SSB with better signal quality and reducing transmission delay.

As another example, the RSRP of the X SSBs is less than or equal to the second threshold, and the terminal device determines resources for the multi-PRACH transmission from the dedicated ROs associated with the X SSBs. That is, in case that RSRP of X SSBs is less than the second threshold, the multiple PRACH transmissions all employ dedicated ROs. Thereby being beneficial to reducing the possibility of occupying shared RO when the signal quality is poor, and causing resource waste.

As another example, the RSRP of the X SSBs is less than the first threshold and greater than the second threshold, and the terminal device determines resources for the multi-PRACH transmission from ROs associated with the X SSBs. Specifically, in this case, the manner in which the terminal device determines the resources for the multi-PRACH transmission from ROs associated with the X SSBs may be referred to as manner 2 or manner 1, and a detailed description thereof will not be repeated. That is, in the case where RSRP of X SSBs is smaller than the first threshold and larger than the second threshold, M PRACH transmissions among the multiple PRACH transmissions use shared ROs and N PRACH transmissions use dedicated ROs.

In particular, where the above examples are used in combination with one another, the first threshold is greater than the second threshold. For example, the first threshold and the second threshold are both greater than the RSRP threshold. Of course, the above examples may be used alone, and in this case, the magnitude relation between the first threshold value and the second threshold value is not limited.

Further, both the first threshold and the second threshold are less than a threshold for determining RSRP for either single PRACH transmission or multiple PRACH transmission.

By way of example, the first and second thresholds may be used to characterize the range of RSRP of the SSB. Or the first threshold and the second threshold are both RSRP thresholds for selecting or determining resources for multiple PRACH transmissions.

For example, the first threshold and the second threshold may be indicated to the terminal device by the network device, may be predefined by a protocol, or may be determined by the terminal device based on an algorithm, which is not limited.

Further, in some embodiments, the first threshold and the second threshold may be dynamically changed. For example, the first and second thresholds may dynamically vary with channel conditions.

For example, only 1 SSB with RSRP greater than or equal to the RSRP threshold value is received by the terminal device, and the value of X is 1. In this case, for example, if the RSRP of the SSB is greater than or equal to the first threshold, the terminal device determines resources for multi-PRACH transmission from the shared ROs associated with the SSB. As another example, if the RSRP of the SSB is less than or equal to the second threshold, the terminal device determines resources for multi-PRACH transmission from the special ROs associated with the SSB. As another example, if the RSRP of the SSB is less than the first threshold and greater than the second threshold, the terminal device determines resources for multi-PRACH transmission from the RO associated with the SSB.

Note that one SSB may correspond to one uplink transmission beam (UL Tx beam) or may correspond to a plurality of UL Tx beams, which is not limited.

For another example, if there are a plurality of SSBs with RSRP greater than or equal to the RSRP threshold among the SSBs received by the terminal device, the value of X is greater than 1. For example, if the RSRP of the X SSBs is greater than or equal to the first threshold, the terminal device determines resources for multi-PRACH transmission from the shared ROs associated with the X SSBs. As another example, if the RSRP of the X SSBs is less than or equal to the second threshold, the terminal device determines resources for multi-PRACH transmission from the dedicated ROs associated with the X SSBs. As another example, if the RSRP of the X SSBs is less than the first threshold and greater than the second threshold, the terminal device determines resources for multi-PRACH transmission from ROs associated with the X SSBs.

In other embodiments of the present application, in case that the value of X is greater than 1, if the RSRP of the part SSB is greater than or equal to the first threshold, the RSRP of the part SSB is less than or equal to the second threshold, and/or the RSRP of the part SSB is located between the first threshold and the second threshold, the terminal device may determine the resources for the multi-PRACH transmission in mode 1 or mode 2, or the terminal device may determine the resources for the multi-PRACH transmission from the shared ROs associated with the SSB having the RSRP greater than the second threshold and/or the dedicated ROs associated with the SSB having the RSRP less than or equal to the second threshold. Of course, in this case, the terminal device may also determine the resources for the multi-PRACH transmission in other manners, which is not limited.

It should be understood that modes 1, 2 and 3 are merely illustrative examples of determining resources for multiple PRACH transmissions by a terminal device and do not constitute a limitation on the manner in which the resources are determined for multiple PRACH transmissions.

In still other embodiments of the present application, one RO corresponds to one RAR window. Wherein, the RAR windows corresponding to different ROs may be the same. For example, as shown in fig. 6A, RO1 and RO2 overlap in the time domain and do not overlap in the frequency domain, and RO1 and RO2 may correspond to the same RAR window. As another example, as shown in fig. 6B, RO1 and RO2 do not overlap in the time domain, RO1 corresponds to one RAR window, RO2 corresponds to one RAR window, and RO1 and RO2 respectively correspond to different RAR windows.

The RO may be a shared RO or a dedicated RO.

For example, if the terminal device receives the RAR in the RAR window corresponding to the RO adopted in the jth PARCH transmission, the PRACH transmission is stopped. That is, the terminal device receives the RAR in the RAR window corresponding to a certain RO before the K number of incomplete PRACH transmissions, and does not transmit the PRACH any more.

Taking the repeated transmission times of PRACH as 2 as an example, the 1 st PRACH transmission adopts shared RO, the 2 nd PRACH transmission adopts special RO, the shared RO corresponds to RAR window1, and the special RO corresponds to RAR window2. If the terminal equipment receives the RAR in the RAR window1 and does not send the 2 nd PRACH, the 2 nd PRACH is not sent any more.

Taking the repeated transmission times of PRACH as 4 as an example, the 1 st PRACH transmission adopts shared RO1, the 2 nd PRACH transmission adopts shared RO2, the 3 rd PRACH transmission adopts special RO1, the shared RO1 corresponds to RAR window1, the shared RO2 corresponds to RAR window2, and the special RO1 corresponds to RAR window3. If the terminal device receives the RAR in the RAR window1 and has not yet transmitted the 2 nd, 3 rd and 4 th PRACH, the 2 nd, 3 rd and 4 th PRACH transmissions are not performed.

Or further, in the embodiment of the present application, in the case where the first M PRACH transmissions all use a shared RO and the second N PRACH transmissions all use a dedicated RO, the shared RO used in the first M PRACH transmissions may correspond to one RAR window, and the second N PRACH transmissions all use the dedicated RO to one RAR window.

Take the PRACH repeat transmission number of 4 as an example. As shown in fig. 7A, the 1 st PRACH transmission uses shared RO1, the 2 nd PRACH transmission uses dedicated RO1, the 3 rd PRACH transmission uses dedicated RO2, the 4 th PRACH transmission uses dedicated RO3, the shared RO1 corresponds to RAR window1, and the dedicated RO1, the dedicated RO2, and the dedicated RO3 all correspond to RAR window2. If the terminal device receives the RAR in the RAR window1 and does not send PRACH for the 2 nd, 3 rd and 4 th times, the PRACH transmission for the 2 nd, 3 rd and 4 th times is not executed any more.

Or as shown in fig. 7B, the 1 st PRACH transmission uses shared RO1, the 2 nd PRACH transmission uses dedicated RO1, the 3 rd PRACH transmission uses shared RO2, the 4 th PRACH transmission uses dedicated RO2, the shared RO1 corresponds to RAR window1, the dedicated RO1 corresponds to RAR window2, the shared RO2 corresponds to RAR window3, and the dedicated RO2 corresponds to RAR window4. If the terminal device receives the RAR in the RAR window1 and does not send PRACH for the 2 nd, 3 rd and 4 th times, the PRACH transmission for the 2 nd, 3 rd and 4 th times is not executed any more.

Or as shown in fig. 7C, the 1 st PRACH transmission uses RO1, the 2 nd PRACH transmission uses RO2, the 3 rd PRACH transmission uses RO3, the 4 th PRACH transmission uses RO4, and RO1, RO2, RO3, and RO4 correspond to one RAR window. If the terminal device receives the RAR in the RAR window and does not send PRACH for the 2 nd, 3 rd and 4 th times, PRACH transmission for the 2 nd, 3 rd and 4 th times is not executed any more. The RO1, the RO2, the RO3, and the RO4 may be dedicated ROs or shared ROs.

Note that, there may be no overlapping in the time domain, or there may be partial overlapping or total overlapping in the time domain, which is not limited to this.

The above embodiments may be used alone or in combination with each other to achieve different technical effects.

Based on the foregoing embodiments, a communication method according to an embodiment of the present application may be applied to a contention-based random access procedure, or may be applied to a non-contention-based random access procedure, as shown in fig. 8, and includes the following steps:

801. The terminal device determines resources for multiple PRACH transmissions. The resources include shared ROs employed by M PRACH transmissions and dedicated ROs employed by N PRACH transmissions. Wherein the sum of M and N is equal to K, and K is the repetition number of PRACH.

For example, the terminal device determines resources for the multiple PRACH transmission according to the number of PRACH transmissions in which the multiple PRACH transmissions employ shared ROs and/or dedicated ROs. Or the terminal device determines resources for multi-PRACH transmission from ROs associated with at least one SSB in time order. The at least one SSB may here be an SSB received by the terminal device that the SSB fulfils the RSRP threshold requirement, e.g. the RSRP of the SSB is greater than or equal to the RSRP threshold.

In particular, for a specific implementation manner of determining resources for multiple PRACH transmission by the terminal device, reference may be made to the above related description, which is not repeated here.

802. The terminal device transmits PRACH based on at least one shared RO and/or dedicated RO in the resource. Correspondingly, the network device receives the PRACH.

Wherein the PRACH employing shared RO transmission includes a dedicated preamble.

It should be noted that the PRACH is transmitted based on at least one shared RO and/or dedicated RO in the resource, and it is understood that the PRACH is transmitted on at least one shared RO and/or dedicated RO in the resource, or the PRACH is transmitted on at least one shared RO and/or dedicated RO in the resource.

That is, for multiple PRACH transmissions, the terminal device actually transmits a maximum of K PRACH. I.e. the terminal device may actually need not send K PRACH times, i.e. complete a random access procedure. For example, the number of repetitions of PRACH is 2, after the terminal device transmits PRACH 1 st time, the terminal device receives RAR, and if PRACH 2 nd time is not transmitted, it is not necessary to transmit PRACH 2 nd time.

Further, in other embodiments of the present application, the terminal device receives the RAR within the RAR time window corresponding to the RO actually used for transmitting the PRACH. For example, if an RAR is received in an RAR time window corresponding to an RO actually used for transmitting the PRACH, and there are remaining PRACH that are not transmitted, the PRACH transmission is stopped, that is, the PRACH is not transmitted any more.

Scene 2: single PRACH transmission. If the terminal device adopts single PRACH transmission, the terminal device sends the PRACH based on the shared RO, in which case the PRACH includes a preamble that only supports single PRACH transmission to distinguish multiple PRACH transmissions on the shared RO.

It should be understood that the present application may also be divided into three types of ROs supporting only single PRACH transmission, ROs supporting single PRACH transmission and multiple PRACH transmission, and ROs supporting only multiple PRACH transmission. In this case, the terminal device may transmit the random access request based on the RO supporting only the single PRACH transmission or the RO supporting both the single PRACH transmission and the multiple PRACH transmission when the single PRACH transmission is adopted, and the terminal device may transmit the random access request based on the RO supporting both the single PRACH transmission and the multiple PRACH transmission and/or the RO supporting only the multiple PRACH transmission when the multiple PRACH transmission is adopted. When the RO supporting the single PRACH transmission and the multiple PRACH transmission is used to send the random access request, the preamble included in the random access request needs to distinguish the single PRACH transmission and the multiple PRACH transmission. Further, when the ROs are classified into three types, the ROs supporting only single PRACH transmission and multiple PRACH transmission may be legacy ROs, and the ROs supporting only multiple PRACH transmission may be additional ROs. Or the RO which only supports single PRACH transmission is legacy RO, the RO which supports single PRACH transmission and multiple PRACH transmission, and the RO which only supports multiple PRACH transmission is additionally added RO. Or the RO only supporting single PRACH transmission, the RO supporting single PRACH transmission and multiple PRACH transmission and the RO only supporting multiple PRACH transmission are legacy RO.

In addition, the embodiment of the application also provides a mapping rule of the SSB and the RO. The shared RO and the dedicated RO share PRACH resources configured based on the existing PRACH configuration period and Association period (number of PRACH configuration period). For example, the shared RO and the dedicated RO are configured at intervals. For example, the example is that 8 SSBs are SSB1, SSB2, SSB3, SSB4, SSB5, SSB6, SSB7, SSB8, respectively. If msg 1-fdm=4, number of SSBs per RO (ssb-perRACH-Occasion) =1, the mapping relationship between ssb and RO can be shown in fig. 9. The shared ROs corresponding to 8 SSBs are mapped in Period (Period) 1, and similarly, the ROs corresponding to SSB1 in Period1 are all shared ROs, if the ROs corresponding to SSB1 in Period1 are shared ROs. The ROs corresponding to the 8 SSBs are mapped as dedicated ROs at Period 2. Similarly, the ROs corresponding to SSB2 to SSB8 in Period2 are all dedicated ROs, as the ROs corresponding to SSB1 in Period2 are dedicated ROs. The ROs corresponding to the 8 SSBs are mapped as shared ROs at Period 3. Similarly, the ROs corresponding to SSB2 to SSB8 in Period3 are all shared ROs, if the ROs corresponding to SSB1 in Period3 are shared ROs. The ROs corresponding to the 8 SSBs are mapped as dedicated ROs at Period 4. Similarly, the ROs corresponding to SSB2 to SSB8 in Period4 are all dedicated ROs, as in Period 4.

It should be noted that a Period refers to a Period Association Period, and a complete SSB mapping can be performed in this Period.

Or the mapping manner of the shared RO and the dedicated RO is separately configured. For example, the shared ROs are still mapped on PRACH resources configured based on existing (e.g., R15 protocol version) PRACH configuration period and Association period (number of PRACH configuration period). The dedicated RO is mapped on the newly configured PRACH resource, and specifically, the newly configured PRACH resource for mapping the dedicated RO may be configured by defining a time domain offset and/or a frequency domain offset, or may be a configuration mode independent of the existing PRACH resource for mapping the shared RO, which is not limited. In this case, the mapping of the shared RO and the SSB, and the mapping of the dedicated RO and the SSB may be independent of each other.

In some embodiments, regardless of the manner in which the SSBs are mapped to ROs, the terminal device selects the shared RO and/or the dedicated RO associated with the corresponding SSB from a round of complete SSB to RO mapping cycles. The terminal device then determines resources for the multi-PRACH transmission or the single PRACH transmission from the selected shared RO and/or dedicated RO associated with the SSB. Thereby helping to reduce transmission delay. The selection mode of the RO is not only suitable for the scene of multi-PRACH transmission, but also suitable for the scene of single PRACH transmission.

For example, for the mapping scheme shown in fig. 9, a complete cycle of SSB to RO mapping can be understood as one Association period.

It should be noted that the mapping manner shown in fig. 9 is only a schematic illustration, for example, the time intervals between different Period, the number of PRACH configuration Period included in one Period, etc. are not illustrated in fig. 8, and only the positional relationships of Period1, period2, period3, and Period4 in the time domain are shown in fig. 8.

Taking the example that the terminal equipment determines the resources for the multi-PRACH transmission according to the number of PRACH transmissions of the multi-PRACH transmission using the shared RO and/or the dedicated RO. The terminal device may first select the shared RO and the dedicated RO in a complete SSB-RO mapping period after the random access trigger timing and with the minimum time interval between the random access trigger timing, and if the number of shared ROs and/or dedicated ROs does not meet the requirement of the number of repeated transmission times of the PRACH, then select the shared RO and the dedicated RO in the next complete SSB-RO mapping period, and continue to select until the number of shared ROs and/or dedicated ROs does not meet the requirement of the number of repeated transmission times of the PRACH. For example, the number of repeated PRACH transmissions may be M for multiple PRACH transmissions using shared ROs and/or N for multiple PRACH transmissions using dedicated ROs.

Taking a terminal device to determine resources for multiple PRACH transmissions in time order as an example. The terminal device may determine, according to a time sequence, a shared RO and/or a dedicated RO used for multiple PRACH transmission in a mapping period of a complete SSB and an RO located after the random access trigger timing and having a minimum time interval from the random access trigger timing, and if it is determined that the shared RO and/or the dedicated RO used for multiple PRACH transmission cannot satisfy K PRACH transmissions, then continue to determine, according to the time sequence, the shared RO and/or the dedicated RO used for multiple PRACH transmission in a mapping period of a complete SSB and an RO in the next round until supporting transmission of K PRACH transmissions. K is the number of repetitions of PRACH.

In the embodiments of the present application described above, the communication method provided in the embodiments of the present application is described in terms of the network device and the terminal device as execution subjects. In order to achieve the above-mentioned communication method provided by the embodiment of the present application. In order to implement the functions in the communication method provided by the embodiment of the present application, the terminal device and the network device may include hardware structures and/or software modules, and implement the functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Some of the functions described above are performed in a hardware configuration, a software module, or a combination of hardware and software modules, depending on the specific application of the solution and design constraints.

As with the above concept, as shown in fig. 10A, an embodiment of the present application also provides a communication apparatus 1000, the apparatus 1010 including a communication unit 1012 and a processing unit 1011.

In an example, the apparatus 1010 is configured to implement a function of a terminal device in the above method. The apparatus 1010 may be a terminal device or an apparatus in a terminal device. The device can be a chip system, a module and the like. In the embodiment of the application, the chip system can be formed by a chip, and can also comprise the chip and other discrete devices.

For example, the processing unit 1011 is configured to determine resources for multiple PRACH transmissions; the communication unit 1012 is configured to transmit PRACH based on RO.

For another example, the communication unit 1012 is further configured to receive transmission indication information, where the transmission indication information is used to indicate the number of PRACH transmissions of the shared RO and/or the dedicated RO used for the multiple PRACH transmissions.

In yet another example, the apparatus 1010 is configured to implement a function of a network device in the above method. The apparatus 1010 may be a network device or may be an apparatus in a network device. The device can be a chip system, a module and the like. In the embodiment of the application, the chip system can be formed by a chip, and can also comprise the chip and other discrete devices.

For example, the communication unit 1012 is configured to receive PRACH.

As another example, the communication unit 1012 is further configured to transmit transmission instruction information.

For another example, the processing unit 1011 is also configured to determine transmission instruction information.

It should be understood that, regarding the specific execution of the processing unit 1011 and the communication unit 1012, reference may be made to the descriptions in the above method embodiments. The division of the modules in the embodiments of the present application is schematically only one logic function division, and there may be another division manner in actual implementation, and in addition, each functional module in each embodiment of the present application may be integrated in one processor, or may exist separately and physically, or two or more modules may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules.

As with the above concept, fig. 10B shows a communication device 1000 according to an embodiment of the present application.

The apparatus 1000 comprises at least one processor 1001 and at least one memory 1002 for storing computer programs and/or data. A memory 1002 is coupled to the processor 1001. The processor 1001 is configured to execute computer programs and/or data stored in the memory 1002 to implement the communication method shown in fig. 8. The coupling in the embodiments of the present application is a spaced coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms for information interaction between devices, units or modules. As another implementation, the memory 1002 may also be located outside the apparatus 1000. The processor 1001 may operate in conjunction with the memory 1002. The processor 1001 may execute a computer program stored in the memory 1002. At least one of the at least one memory may be included in the processor.

In some embodiments, apparatus 1000 may also include a communication interface 1003 for communicating with other devices over a transmission medium, such that modules used in apparatus 1000 may communicate with other devices. By way of example, communication interface 1003 may be a transceiver, circuit, bus, module, or other type of communication interface.

In an example, the apparatus 1000 may be a terminal device, or may be an apparatus in a terminal device, configured to implement a function of the terminal device in the above method.

Or in an example, the apparatus 1000 may be a network device, or may be an apparatus in a network device, configured to implement the functions of the network device in the foregoing method.

The connection medium between the communication interface 1003, the processor 1001, and the memory 1002 is not limited in the embodiment of the present application. For example, in FIG. 10B, the processor 1001 is coupled to both the memory 1002 and the communication interface 1003. Of course, in the embodiment of the present application, the memory 1002, the communication interface 1003, and the processor 1001 may be connected by a bus, where the bus may be classified into an address bus, a data bus, a control bus, and the like.

In the embodiment of the present application, the processor may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps and logic blocks disclosed in the embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution.

In the embodiment of the application, the memory may be a nonvolatile memory, such as a hard disk (HARD DISK DRIVE, H DD) or a solid state disk (s olid-S TA TE D RI VE, SSD), and the like, or may be a volatile memory (vola tile memory), such as a random-access memory (RAM). The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory in the embodiments of the present application may also be a circuit or any other device capable of implementing a storage function, for storing a computer program and/or data.

The method provided by the embodiment of the application can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program is loaded and executed on a computer, the flow or functions according to the embodiments of the present application are fully or partially produced. The computer may be a general purpose computer, a special purpose computer, a computer network, a network device, a user device, or other programmable apparatus. The computer program may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (digital video disc, abbreviated as DVD)), or a semiconductor medium (e.g., an SSD), etc.

It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims

1. A method of communication, the method comprising:

Determining resources for PRACH transmission of a plurality of physical random access channels, wherein the resources comprise shared random access time RO adopted by M PRACH transmission and special RO adopted by N PRACH transmission;

M, N is a positive integer greater than or equal to 0, and the sum of M and N is equal to K, wherein K is the repetition number of PRACH; the shared RO supports single PRACH transmission and multiple PRACH transmission; the special RO supports multiple PRACH transmission and does not support single PRACH transmission;

Transmitting PRACH based on at least one shared RO and/or dedicated RO of the resources; wherein the PRACH employing shared RO transmission includes a dedicated preamble that supports multiple PRACH transmissions, not single PRACH transmissions.

2. The method of claim 1, wherein the shared ROs employed by the M PRACH transmissions do not overlap in the time domain; and/or the number of the groups of groups,

The special RO adopted by the N times of PRACH transmission is not overlapped in the time domain; and/or the number of the groups of groups,

The shared RO adopted by the M PRACH transmissions and the dedicated RO adopted by the N PRACH transmissions do not overlap in time domain.

3. The method of claim 1 or 2, wherein the M PRACH transmissions are the first M PRACH transmissions of a multiple PRACH transmission.

4. The method of claim 1, wherein the determining resources for multi-PRACH transmission comprises:

and determining resources for the multi-PRACH transmission according to the PRACH transmission times of the shared RO and/or the dedicated RO adopted by the multi-PRACH transmission.

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

And receiving transmission indication information, wherein the transmission indication information is used for indicating the PRACH transmission times of the shared RO and/or the dedicated RO adopted by the multi-PRACH transmission.

6. The method according to claim 4, wherein the method further comprises:

And determining the PRACH transmission times of the shared RO and/or the dedicated RO adopted by the multi-PRACH transmission according to the number of the synchronous signal blocks SSB of which the reference signal received power RSRP is greater than or equal to the RSRP threshold.

7. The method according to claim 1 or 6, wherein,And X is the number of synchronous signal blocks SSB with RSRP greater than or equal to an RSRP threshold, and i is used for representing the weight of PRACH transmission times adopting shared RO.

8. The method of claim 1 or 4, wherein the determining resources for multi-PRACH transmission comprises:

Determining shared ROs adopted by the M PRACH transmissions from the shared ROs associated with the X SSBs in order of the RSRP of the SSB from high to low;

and determining a dedicated RO employed by the N PRACH transmissions from among dedicated ROs associated with at least one SSB of the X SSBs;

9. The method of claim 1, wherein the determining resources for multi-PRACH transmission comprises:

Determining the resources for multi-PRACH transmission from ROs associated with X SSBs that are located after a random access trigger occasion in a time sequence; wherein, the ROs associated with the X SSBs include dedicated ROs and/or shared ROs, where X is the number of SSBs with RSRP greater than or equal to an RSRP threshold.

10. The method of any of claims 4-9, wherein RSRP of the X SSBs is less than a first threshold and greater than a second threshold, wherein the first threshold is greater than the second threshold.

11. The method according to claim 1 or 2, wherein the determining resources for multi-PRACH transmission comprises:

if the RSRP of the X SSBs is greater than or equal to a first threshold, determining resources for multi-PRACH transmission from the shared ROs associated with the X SSBs; and/or the number of the groups of groups,

If the RSRP of the X SSBs is less than or equal to a second threshold, determining resources for multi-PRACH transmission from the dedicated ROs associated with the X SSBs;

12. The method according to claim 1, wherein the method further comprises:

And if the RAR is received in a random access response RAR time window corresponding to the RO adopted by the jth PRACH transmission, stopping the PRACH transmission, wherein j is smaller than K, and j is a positive integer.

13. A method of communication, the method comprising:

Receiving PRACH based on at least one shared RO and/or dedicated RO among resources for multi-physical random access channel PRACH transmission;

Wherein, the resources comprise shared random access opportunity RO adopted by M times of PRACH transmission and special RO adopted by N times of PRACH transmission; m, N is a positive integer greater than or equal to 0, and the sum of M and N is equal to K, wherein K is the repetition number of PRACH; the shared RO supports single PRACH transmission and multiple PRACH transmission; the dedicated RO supports multiple PRACH transmissions and does not support single PRACH transmissions.

14. The method of claim 13, wherein the shared ROs employed by the M PRACH transmissions do not overlap in time domain; and/or the number of the groups of groups,

15. The method of claim 13, wherein the method further comprises:

16. A communication device, comprising: a communication unit and a processing unit;

The processing unit, in combination with the communication unit, performs the method according to any of claims 1-12 or performs the method according to any of claims 13-15.

17. A communication device, comprising: a processor and a memory;

Wherein the memory stores a computer program which, when executed by the processor, causes the communication device to perform the method of any one of claims 1-12 or to perform the method of any one of claims 13-15.

18. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when run on a computer, implements the method according to any one of claims 1-12 or the method according to any one of claims 13-15.