Prach retransmission method and apparatus, and device and readable storage medium

Abstract

The present application belongs to the technical field of communications, and in particular to a PRACH retransmission method and apparatus, and a device and a readable storage medium. The method comprises: a terminal determining a time offset; the terminal determining a target RO group on the basis of the time offset; and the terminal performing PRACH retransmission on the target RO group, wherein the time offset is counted by using temporally continuous valid ROs that are associated with the same SSB at the same frequency position, with preamble sets associated with the SSB being the same, or the time offset is counted by using temporally continuous valid ROs that are associated with the same SSB at the same frequency position, with preamble sets associated with the SSB on the valid ROs not being entirely the same, and when some preambles associated with one RO are not used for PRACH retransmission, all the preamble sets associated with the RO cannot be used for PRACH retransmission.

Description

PRACH repeated transmission method, device, equipment and readable storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese Patent Application No. 202311214381.9 filed in China on September 19, 2023, and claims priority to Chinese Patent Application No. 202311395595.0 filed in China on October 25, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a PRACH repeated transmission method, apparatus, device, and readable storage medium. Background Art

[0004] In the technology of repeated transmission of the Physical Random Access Channel (PRACH), the purpose of introducing a time offset between adjacent physical random access channel transmission opportunity sets (PRACH transmission Occasion groups or PRACH Occasion groups, referred to as RO groups) is to reduce the number of physical random access channel transmission opportunities (PRACH transmission Occasions or PRACH Occasions, ROs) detected by the network side, thereby alleviating the pressure on the receiver to detect PRACH.

[0005] However, the same synchronization signal / physical broadcast channel block (SS / PBCH block, SSB) may have different preamble sets associated with different ROs. According to the current time offset rules, some ROs are unavailable for a certain SSB and do not need to be detected, but are available for another SSB associated with this RO and need to be detected. This conflicts with the purpose of introducing the time offset. In addition, if the same SSB is associated with different preamble sets on different ROs, whether these ROs are calculated into the time offset is not currently specified. This will lead to different RO group determination results on the network side and the terminal side, resulting in inconsistent RO groups used by the transmitter and receiver, and thus the failure of repeated PRACH reception.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide a PRACH repeated transmission method, apparatus, device, and readable storage medium, which can solve the problem of PRACH repeated reception failure caused by unclear time offset rules introduced in related PRACH repeated transmission methods.

[0008] In a first aspect, a PRACH repeated transmission method is provided.

[0009] The terminal determines the time offset;

[0010] The terminal determines a target physical random access channel transmission opportunity set RO group according to the time offset;

[0011] The terminal performs repeated transmission of a physical random access channel PRACH on the target RO group;

[0012] The time offset is counted as valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position and the same Preamble set associated with the SSB;

[0013] Alternatively, the time offset is counted for valid ROs that are continuous in the time domain and associated with the same SSB at the same frequency position, and the Preamble sets associated with the SSB on the valid RO are not all the same, wherein when part of the Preamble associated with an RO is not used for PRACH repeated transmission, all Preamble sets associated with the RO cannot be used for PRACH repeated transmission.

[0014] In a second aspect, a PRACH repeated transmission method is provided.

[0015] The network-side device determines the time offset;

[0016] The network side device determines all available RO groups according to the time offset;

[0017] The network side device performs PRACH repeated reception on all available RO groups;

[0018] The time offset is counted as valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position and the same Preamble set associated with the SSB;

[0019] Alternatively, the time offset is counted as valid ROs that are continuous in the time domain and associated with the same SSB at the same frequency position, and the Preamble sets associated with the SSB on the valid RO are not all the same, wherein when part of the Preamble associated with an RO is not used for PRACH repeated transmission, all Preamble sets associated with the RO cannot be used for PRACH repeated transmission.

[0020] In a third aspect, a PRACH repeated transmission device is provided.

[0021] A first determination module is used for the terminal to determine the time offset;

[0022] A second determining module, configured for the terminal to determine a target RO group according to the time offset;

[0023] A transmission module, configured for the terminal to perform PRACH repeated transmission on the target RO group;

[0024] The time offset is counted as valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position and the same Preamble set associated with the SSB;

[0025] Alternatively, the time offset is counted as valid ROs that are continuous in the time domain and associated with the same SSB at the same frequency position, and the Preamble sets associated with the SSB on the valid RO are not all the same, wherein when part of the Preamble associated with an RO is not used for PRACH repeated transmission, all Preamble sets associated with the RO cannot be used for PRACH repeated transmission.

[0026] In a fourth aspect, a PRACH repeated transmission device is provided.

[0027] A third determination module is used for the network side device to determine the time offset;

[0028] A fourth determining module, configured for the network side device to determine all available RO groups according to the time offset;

[0029] A receiving module, configured for the network side device to repeatedly receive PRACH on all available RO groups;

[0030] The time offset is counted as valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position and the same Preamble set associated with the SSB;

[0031] Alternatively, the time offset is counted as valid ROs that are continuous in the time domain and associated with the same SSB at the same frequency position, and the Preamble sets associated with the SSB on the valid RO are not all the same, wherein when part of the Preamble associated with an RO is not used for PRACH repeated transmission, all Preamble sets associated with the RO cannot be used for PRACH repeated transmission.

[0032] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0033] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is used for the terminal to determine a time offset; the terminal determines a target physical random access channel transmission opportunity set RO group based on the time offset; the communication interface is used for the terminal to perform physical random access channel PRACH repeated transmission on the target RO group; wherein the time offset is counted by valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position and the same Preamble set associated with the SSB; or, the time offset is counted by valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position, and the Preamble sets associated with the SSB on the valid ROs are not all the same, wherein when part of the Preambles associated with an RO are not used for PRACH repeated transmission, all Preamble sets associated with the RO cannot be used for PRACH repeated transmission.

[0034] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0035] In an eighth aspect, a network side device is provided, comprising a processor and a communication interface, wherein the processor is used by the network side device to determine a time offset; the network side device determines all available RO groups based on the time offset; the communication interface is used by the network side device to perform PRACH repeated reception on all available RO groups; wherein the time offset is counted by valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position and the same Preamble set associated with the SSB; or, the time offset is counted by valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position, and the Preamble sets associated with the SSB on the valid ROs are not all the same, wherein when part of the Preamble associated with an RO is not used for PRACH repeated transmission, all Preamble sets associated with the RO cannot be used for PRACH repeated transmission.

[0036] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0037] In the tenth aspect, a wireless communication system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.

[0038] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0039] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0040] In an embodiment of the present application, a new rule for determining the time offset is set: the time offset is counted as valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position and the same Preamble set associated with the SSB; or, the time offset is counted as valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position, and the Preamble sets associated with the SSB on the valid RO are not all the same, wherein when part of the Preamble associated with an RO is not used for PRACH repeated transmission, then all Preamble sets associated with the RO cannot be used for PRACH repeated transmission. In the process of determining the time offset, the influence of the Preamble set associated with the SSB on the RO is also taken into consideration, so as to more accurately judge whether the RO associated with the SSB is available and needs to be detected, so that the terminal and the network side equipment have a consistent understanding of the RO group used for PRACH repeated transmission, thereby improving the PRACH repeated transmission performance. In addition, the embodiment of the present application improves the performance of PRACH repeated transmission and reduces the pressure of PRACH detection on the network side. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] FIG1a is a block diagram of a wireless communication system applicable to embodiments of the present application;

[0042] Figure 1b is a schematic diagram of the association relationship between SSB and RO;

[0043] Figure 1c is another schematic diagram of the association relationship between SSB and RO;

[0044] Figure 1d is a schematic diagram of a method for determining an RO group;

[0045] Figure 1e is a schematic diagram of another method for determining RO groups;

[0046] Figure 1f is a schematic diagram of a method for determining RO groups for different SSBs;

[0047] FIG2 is a flow chart of a PRACH repeated transmission method according to an embodiment of the present application;

[0048] FIG3 is a second flow chart of a PRACH repeated transmission method according to an embodiment of the present application;

[0049] FIG4a is a schematic diagram of one of the embodiments provided in the embodiments of the present application;

[0050] FIG4 b is one of the schematic diagrams of the embodiments provided in the present application;

[0051] FIG4c is a schematic diagram of one of the embodiments provided in the embodiments of the present application;

[0052] Figure 4d is one of the schematic diagrams of the embodiments provided in the present application;

[0053] FIG5 is a schematic diagram of a structure of a PRACH repeated transmission device according to an embodiment of the present application;

[0054] FIG6 is a second structural diagram of a PRACH repeated transmission apparatus according to an embodiment of the present application;

[0055] FIG7 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0056] FIG8 is a schematic diagram of the structure of a terminal provided in an embodiment of the present application;

[0057] FIG9 is a schematic diagram of a structure of a network side device according to an embodiment of the present application;

[0058] FIG10 is a second structural diagram of the network side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0059] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0060] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0061] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0062] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0063] FIG1a shows a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle user equipment (VUE), a ship-borne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AS) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0064] The core network device may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application server discovery function (EASDF), unified data management (UDM), unified data storage (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BNSF), network access function (UE ... Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiment of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0065] To better understand the technical solution of this application, the following contents are first introduced:

[0066] Random access process

[0067] The random access procedure includes a contention-based random access procedure and a non-contention-based random access procedure.

[0068] In the contention-based four-step random access (RACH) process, a user equipment (UE) first sends Msg1 (including a preamble) to the network on a time-frequency radio resource, namely, a RACH Occasion resource (RO resource). After detecting the preamble, the network sends Msg2 / Random Access Response (RAR) message, which includes the preamble number detected by the network and the uplink radio resources allocated to the UE for sending Msg3. After receiving Msg2, the UE confirms that at least one of the preamble numbers carried in Msg2 matches the number of the preamble it sent. Based on the resources indicated by the RAR, it sends Msg3 containing contention resolution information. After receiving Msg3, the network sends Msg4 containing contention resolution information. Upon receiving Msg4, the UE confirms that the contention resolution information matches the content sent in Msg3, completing the four-step random access process.

[0069] The network includes uplink (UL) grant information in the RAR to indicate the Msg3 Physical Uplink Shared Channel (PUSCH) scheduling information, and includes RAPID (RACH preamble ID), Temporary Cell-Radio Network Temporary Identity (TC-RNTI), Tracking Area (TA), etc. If the network does not receive the Msg3 PUSCH, it can schedule the retransmission of the Msg3 PUSCH in the TC-RNTI-scrambled Physical Downlink Control Channel (PDCCH).

[0070] For the contention random access process, different UEs randomly select Preamble for transmission. In this way, different UEs may select the same Preamble to send on the same time-frequency radio resources (RO resources). This situation can be understood as a UE Preamble conflict. In this case, different UEs will receive the same RAR. At this time, different UEs will transmit Msg3 PUSCH according to the scheduling information in the RAR UL grant. Since the relevant technology does not support repeated transmission of Msg3PUSCH, the network can only decode the PUSCH (including contention resolution information) sent by one UE on one Msg3 PUSCH scheduling resource. Therefore, the network will include the contention resolution information received in Msg3 in Msg4. If the contention resolution information in Msg4 received by the UE matches the contention resolution information sent by the UE in Msg3 PUSCH, the UE considers that the contention resolution is successful. If they do not match, the contention resolution is considered unsuccessful.

[0071] If the contention resolution is unsuccessful, the UE reselects resources, performs PRACH transmission, and makes the next random access attempt.

[0072] Random access resource selection

[0073] In NR, a cell can configure multiple frequency division multiplexing (FDM) PRACH transmission opportunities (PRACH transmission occasions, or PRACH Occasions) at a single PRACH transmission time domain location. For simplicity, these are referred to as ROs. The number of ROs that can be used for FDM at a given moment can be: {1, 2, 4, 8}, configured using the higher-layer parameter msg1-FDM. As shown in Figure 1b, at a given moment, there are eight RO resources distributed across different frequencies.

[0074] The random access preamble (Preamble) can only be transmitted on the time domain resources (i.e., RO resources) configured by the parameter PRACHConfigurationIndex. The random access preamble can only be transmitted on the frequency domain resources configured by the parameter msg1-FDM. The PRACH frequency domain resources n_RA∈{0,1,…,M-1}, where M is equal to the higher-layer parameter msg1-FDM. During initial access, the PRACH frequency domain resources n_RA are numbered in ascending order, starting from the lowest-frequency RO resource within the initial active uplink bandwidth part. Otherwise, the PRACH frequency domain resources n_RA are numbered in ascending order, starting from the lowest-frequency RO resource within the active uplink bandwidth part. As shown in Figure 1b, the RO resources are numbered from RO#0 to RO#7, in ascending order of frequency.

[0075] In NR, there is an association between the RO and the actual synchronization signal / physical broadcast channel block (SS / PBCH block, SSB) sent. One SSB may be associated with multiple ROs, or multiple SSBs may be associated with one RO (in this case, different SSBs correspond to different preamble codes), which is configured by the network through the parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB;

[0076] Typically, a base station can use different beams to transmit different SSBs. The number of SSBs is configured using the ssb-PositionsInBurst parameter. For FR2 (Frequency range 2), the maximum number of SSBs is 64. The corresponding UE sends the Preamble on the RO associated with the SSB. Based on the strength of the received downlink beam / SSB, the UE selects the RO / "RO and preamble combination" associated with the SSB with a good signal to send Msg1. In this way, the network can determine the SSB selected by the UE based on the RO / "RO and preamble combination" of the received Preamble. Msg2 is then sent on the downlink beam corresponding to the SSB to ensure the reception quality of the downlink signal.

[0077] Taking Figure 1b as an example, the number of FDM ROs at a given moment is eight, and the number of SSBs actually transmitted is four: SSB#0, SSB#1, SSB#2, and SSB#3. Each SSB is associated with two ROs. If the UE determines to send the PRACH / Msg1 / Preamble on the RO corresponding to SSB#0, the UE selects one RO between RO#0 and RO#1 for PRACH transmission.

[0078] Taking Figure 1c as an example, the number of FDM ROs at a given moment is 2, and the number of SSBs actually transmitted is 8, namely SSB#0, SSB#1, ..., SSB#7, with one RO associated with every two SSBs. When multiple SSBs share a RO, the preamble sets associated with these multiple SSBs are different, that is, the same preamble cannot belong to the preamble sets associated with different SSBs at the same time: Taking RO#0 in Figure 1c as an example, it has 60 preambles associated with SSBs, of which preambles with indices 0 to 29 are associated with SSB#0, and preambles with indices 30 to 59 are associated with SSB#1.

[0079] It should be noted that each square in Figures 1b and 1c represents an RO, not an SSB, and the labeled SSB indicates which SSB(s) the RO is associated with.

[0080] Before sending PRACH, the UE first performs resource selection. First, based on the received beam or reference signal received power (RSRP) of the SSB, it selects an SSB with RSRP higher than the threshold. If the RSRP of multiple SSBs is higher than the threshold, the terminal can select any SSB with RSRP higher than the threshold. If there is no SSB with RSRP higher than the threshold, the UE selects an SSB based on the implementation.

[0081] Based on the network (NW) configuration, the UE obtains the correspondence between the SSB and the RO. After selecting the SSB, the RO corresponding to the selected SSB is used as the RO for sending PRACH / Preamble. If the selected SSB is associated with multiple ROs, the terminal can select one of the ROs for PRACH / Preamble transmission.

[0082] For example: In the example shown in Figure 1b, assuming that the UE selects SSB#1, the UE can select one from RO#2 and RO#3 to send PRACH / Preamble; in the example shown in Figure 1c, if the UE selects SSB#1, the UE can select the available RO closest to the current time among the ROs (RO#0 or 4) associated with SSB#1 to send PRACH / Preamble.

[0083] In the selected RO, the UE selects a preamble from the preamble set associated with the selected SSB for PRACH transmission. As shown in Figure 1c, an RO is associated with two SSBs. In this case, the available preamble set associated with each SSB in the RO is divided into two subsets, one for each SSB. The UE selects a preamble sequence from the preamble subset corresponding to the selected SSB for PRACH transmission.

[0084] Random access resource selection for PRACH repetition

[0085] For PRACH repetition, the UE needs to repeatedly send the preamble on multiple ROs at different locations in the time domain associated with the same SSB. The PRACH repetition count can be {2, 4, 8}. After determining the PRACH repetition count, the UE needs to determine the RO group. The number of valid ROs in the RO group is equal to the PRACH repetition count.

[0086] Assuming the number of PRACH repetitions is N1, the overall RO group determination rule within time window X is as follows: First, determine the starting RO of the first RO group, then determine the remaining N-1 ROs in the first RO group. Then, determine the starting RO and remaining ROs of other RO groups in sequence. The remaining N1-1 ROs in each RO group are ROs associated with the same SSB, the same frequency position, and the same associated preamble set as the starting RO. After the first RO group is determined, the determination of the remaining RO groups is related to whether a time offset is configured. The purpose of introducing a time offset is to reduce the number of ROs detected on the network side, thereby alleviating pressure.

[0087] If no time offset is configured, for each SSB, the first valid RO within time window X is used as the starting RO of the first RO group, and the first RO group is determined based on the starting RO. Then, for the remaining ROs, excluding the determined RO group, the starting ROs of subsequent RO groups are determined within time window X in ascending order of frequency domain position followed by time domain position, and subsequent RO groups are further determined. For example, in Figure 1d, assuming the PRACH repetition count is 2, for SSB#0, the RO group shown in Figure 1d can be determined.

[0088] If a time offset is configured, for each SSB, the first valid RO found within time window X, in ascending order of frequency domain first and then time domain, is used as the starting RO of the first RO group. The first RO group is then determined based on the starting RO. The starting ROs and corresponding RO groups of subsequent RO groups are then determined, excluding the determined RO group, in ascending order of frequency domain first and then time domain. The starting RO of the nth RO group associated with the same SSB at the same frequency position is the RO that is time offset from the starting RO of the n-1th RO group. The time offset is defined as the number of valid ROs associated with the same SSB in the time domain. For example, in Figure 1e, assuming a PRACH repetition count of 2 and time offset = 3, the RO group shown in Figure 1e can be determined for SSB#0.

[0089] The purpose of introducing a time offset between adjacent RO groups is to reduce the number of ROs detected on the network side to reduce the pressure on the receiver to detect PRACH. The current time offset is defined as the number of valid ROs with the same frequency domain position associated with the same SSB in the time domain. However, the Preamble sets associated with the same SSB on different ROs may be different. According to the current time offset rules, some ROs are unavailable for a certain SSB and do not need to be detected, but are available for another SSB associated with this RO and need to be detected, which conflicts with the purpose of introducing the time offset. For example, as shown in Figure 1f below, assuming time offset = 3 and the number of PRACH repetitions is 2, then RO#1 is unavailable for SSB#0, but is available for SSB#2.

[0090] It is currently unclear whether ROs associated with the same SSB but with different preamble sets are considered in the RO offset. This can lead to different interpretations between the network and the terminal, resulting in inconsistent RO groups between the transmitter and receiver, and thus failure of repeated PRACH reception. Figure 1f assumes that the time offset includes all ROs associated with a specific SSB. However, it is also possible that the time offset does not include ROs associated with the same SSB but with different preamble sets.

[0091] The value of the time offset has not yet been determined and needs to be considered comprehensively based on various repetition times.

[0092] Therefore, when the preamble sets associated with SSB on different ROs are different, how to determine the time offset and how to determine the RO group need to be solved.

[0093] Furthermore, according to the current RO group determination method, when a time offset is configured, for the same SSB, after the first RO group is determined within time window X, the starting ROs of subsequent RO groups, excluding the previous RO group, are determined first in the frequency domain (from low frequency to high frequency) and then in the time domain, in combination with the time offset. (Understandably, the determination of the second RO group requires the removal of ROs associated with the first RO group, and the determination of the third RO group requires the removal of ROs associated with both the first and second RO groups; that is, the same RO cannot belong to two RO groups at the same time.) There are no specific rules for determining the starting RO of subsequent RO groups, determining when to use the frequency domain first and then the time domain, or when to use the time offset in combination.

[0094] The PRACH repeated transmission method provided in the embodiments of the present application is described in detail below with reference to some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0095] Referring to FIG. 2 , an embodiment of the present application provides a PRACH repetition transmission method, which may also be referred to as a PRACH transmission method with preamble repetition. The method is performed by a terminal and includes:

[0096] Step 201: The terminal determines the time offset;

[0097] Step 202: The terminal determines the target RO group based on the time offset;

[0098] Step 203: The terminal performs PRACH retransmission on the target RO group;

[0099] In this embodiment of the present application, the rules for determining the time offset include:

[0100] (1) The time offset is counted as a continuous valid RO in the time domain associated with the same SSB at the same frequency position and with the same preamble set associated with the SSB;

[0101] (2) The time offset is counted based on the valid ROs that are consecutive in the time domain and associated with the same SSB at the same frequency position. The preamble sets associated with the SSB on the valid ROs are not all the same. When some preambles associated with an RO are not used for PRACH repeated transmission, all preamble sets associated with the RO cannot be used for PRACH repeated transmission. That is, in the scenario shown in FIG1f above, RO#1 is unavailable for SSB#0 but available for SSB#2. Then, according to the rules for determining the time offset in the embodiment of the present application, when calculating the number of valid ROs, RO#1 is not counted in the number of valid ROs.

[0102] It should be noted that before the terminal determines the time offset, it is optionally necessary to meet the following conditions: the Preamble sets associated with the same SSB on different ROs are not all the same, where is a decimal greater than 1, or is a decimal less than 1 and Not an integer, where N is the number of SSBs associated with an RO. is the total number of SSBs.

[0103] In an embodiment of the present application, a new rule for determining the time offset is set: the time offset is counted as valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position and the same Preamble set associated with the SSB; or, the time offset is counted as valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position, and the Preamble sets associated with the SSB on the valid RO are not all the same, wherein when part of the Preamble associated with an RO is not used for PRACH repeated transmission, then all Preamble sets associated with the RO cannot be used for PRACH repeated transmission. In the process of determining the time offset, the influence of the Preamble set associated with the SSB on the RO is also taken into consideration, so as to more accurately judge whether the SSB associated with the RO is available and needs to be detected, so that the terminal and the network side equipment have a consistent understanding of the RO group used for PRACH repeated transmission, thereby improving the PRACH repeated transmission performance. In addition, the embodiment of the present application improves the performance of PRACH repeated transmission and reduces the pressure of PRACH detection on the network side.

[0104] In a possible implementation, the terminal determines the target RO group according to the time offset, including:

[0105] When the preset conditions are met, the terminal determines the target RO group based on the time offset;

[0106] The preconditions include one or more of the following:

[0107] (1) The time offset value is configured; for example, the network side may pre-configure the time offset value for the terminal.

[0108] (2) is an integer value;

[0109] (3) is an integer value;

[0110] (4) In all ROs associated with the same SSB at the same frequency domain position, the preamble sets associated with the SSB on the RO are all the same;

[0111] Where N is the number of SSBs associated with an RO, is the total number of SSBs.

[0112] In the embodiment of the present application, it is clarified under what circumstances the time offset is used to determine the target RO group. That is, when at least one of the above (1) to (4) is met, the terminal determines the target RO group according to the time offset.

[0113] It should be noted that when N ≥ 1, it means that N SSBs are associated with the same RO; when N < 1, it means that 1 SSB is associated with 1 / N ROs.

[0114] In a possible implementation, the terminal determines the target RO group according to the time offset, including:

[0115] (1) The terminal determines the starting RO of the first RO group associated with the target SSB within the first time range;

[0116] (2) The terminal determines multiple RO groups based on the starting RO and time offset of the first RO group;

[0117] (3) The terminal determines the target RO group from multiple RO groups;

[0118] The above-mentioned first time range can specifically be a preset time window X, and the target SSB is selected by the terminal, that is, it is selected by comparing the RSRP of the received beam (SSB) with the preset threshold as described above, or the target SSB is the SSB indicated by the network side device, that is, the network side indicates the target SSB to the terminal explicitly or implicitly.

[0119] The first time range may be composed of K SSB to RO association mode periods. Within the first time range, for all PRACH repetition times configured by the network, at least one RO group can be determined for all SSBs.

[0120] An SSB to RO association pattern period may include at least one SSB to RO association period.

[0121] In the embodiment of the present application, the terminal determines the RO group for repeated PRACH transmission in the preset time window X according to the target SSB. First, the starting RO of the first RO group is determined. Then, based on the starting RO and time offset of the first RO group, multiple RO groups are determined. Finally, the target RO group is determined from the multiple RO groups.

[0122] In a possible implementation, the terminal determines, within a first time range, a starting RO of a first RO group associated with a target SSB, including:

[0123] (1) The terminal divides the associated ROs into M categories according to the Preamble set on the RO associated with the target SSB, where the Preamble set associated with the SSB on each category of RO is the same;

[0124] (2) The terminal determines, in each type of RO, the first RO in the first time range as the starting RO of the first RO group in the order of increasing in the frequency domain first and then in the time domain, or determines, in each type of RO at each frequency position, the first RO in the first time range as the starting RO of the first RO group in the order of increasing in the time domain.

[0125] In a possible implementation, the terminal determines multiple RO groups according to the starting RO and time offset of the first RO group, including:

[0126] Within a first time range (e.g., a preset time window X), the terminal determines the starting RO of a subsequent RO group based on a frequency domain order followed by a time domain order, starting at each time corresponding to the starting RO of the first RO group + (time offset) * m ROs, where the value of m includes one or more integers not less than 0. It is understood that multiple starting times can be determined by adjusting different values ​​of m, but the setting of the value of m must ensure that the starting time does not exceed the first time range.

[0127] The terminal determines multiple RO groups based on the starting RO.

[0128] In a possible implementation, the terminal determines multiple RO groups according to the starting RO and time offset of the first RO group, including:

[0129] The terminal starts at each moment corresponding to the starting RO+(time offset)*m ROs of the first RO group within the first time range, and within a second time range (e.g., a preset time range X2), determines, among ROs outside the determined RO group, starting ROs of subsequent RO groups based on an order of first increasing in the frequency domain and then increasing in the time domain, where the value of m includes one or more integers not less than 0, and the second time range is the time length corresponding to the first RO group within the first time range, or the number of moments included in the first RO group, or the number of moments included in the first RO group - 1.

[0130] The terminal determines multiple RO groups based on the starting RO.

[0131] In a possible implementation, the terminal determines a target RO group from multiple RO groups, including one or more of the following:

[0132] (1) In the order of increasing in frequency domain first and then in time domain, the first available RO group closest to the current time in the first time range and associated with the target SSB is determined as the target RO group;

[0133] (2) Determine the available RO group with the lowest frequency position that is closest to the current time within the first time range and associated with the selected target SSB as the target RO group;

[0134] (3) Determine the available RO group that is closest to the current time within the first time range, is associated with the selected target SSB, and has the highest frequency position as the target RO group.

[0135] The ROs in the available RO group are after the current time.

[0136] It should be noted that, when selecting the available RO group closest to the current time, it is required that the ROs in the RO group are after the current time, that is, all ROs in the available RO group must be available relative to the current time.

[0137] In one possible implementation, the method further includes:

[0138] (1) If the preset conditions are not met, the terminal determines the starting RO of the first RO group associated with the target SSB within the first time range;

[0139] (2) Within the first time range, the terminal determines the starting RO of the RO group subsequently associated with the target SSB in the order of increasing frequency domain position first and then increasing time domain position.

[0140] The above describes the preset conditions for the terminal to determine the target RO group according to the time offset. In the embodiment of the present application, a method for determining the target RO group is provided for the case where the preset conditions are not met.

[0141] In a possible implementation, when no time offset is preconfigured, the terminal determines a time offset value, including:

[0142] The terminal determines the time offset value to be any of the following:

[0143] (1) A first number of repeated transmissions, which is the number of repeated transmissions configured for the terminal to perform PRACH repeated transmissions on the target RO group;

[0144] (2) A second number of repeated transmissions, where the second number of repeated transmissions is one of the configured multiple PRACH repeated transmissions.

[0145] In an embodiment of the present application, a method for determining the time offset value is provided for the case where the time offset value is not pre-configured. The number of PRACH retransmissions may be pre-configured to the terminal by the network side, and the configured number may be one or more. If it is one, the method for determining the time offset value described in (1) above may be adopted. If it is multiple, the method for determining the time offset value described in (2) above may be adopted. The target number of PRACH retransmissions may be configured by the network or specified by the protocol. For example, the target number of PRACH retransmissions may be the maximum number of PRACH repetitions.

[0146] In one possible implementation, the time offset satisfies:

[0147] The minimum value of the time offset is the configurable minimum number of PRACH retransmissions, and the maximum value of the time offset is greater than or equal to the configurable maximum number of PRACH retransmissions.

[0148] In the embodiments of the present application, the value range requirements of the time offset are clarified.

[0149] In one possible implementation, the time offset satisfies:

[0150] Different PRACH repetition transmission times correspond to the same time offset, or different PRACH repetition transmission times correspond to different time offsets.

[0151] In a possible implementation manner, the random access resource configuration for repeated PRACH transmission is used for a system message request, wherein the random access resource configuration for repeated PRACH transmission includes one of the following:

[0152] At least one of the system message request period si-RequestPeriod, random access association period index ra-AssociationPeriodIndex, and RO mask index ra-ssb-OccasionMaskIndex is not configured;

[0153] Configuring a system message request period and a random access associated period index, wherein the system message request period and the random access associated period index are in units of a first time range;

[0154] Configure the system message request period and random access association period index, wherein the system message request period and random access association period index are in units of SSB to RO association period.

[0155] It can be understood that not configuring at least one of the system message request period si-RequestPeriod, the random access association period index ra-AssociationPeriodIndex, and the RO mask index ra-ssb-OccasionMaskIndex can mean that at least one of the system message request period si-RequestPeriod, the random access association period index ra-AssociationPeriodIndex, and the RO mask index ra-ssb-OccasionMaskIndex is not configured or is not selected for configuration. Alternatively, at least one of the three parameters, si-RequestPeriod, ra-AssociationPeriodIndex, and ra-ssb-OccasionMaskIndex, is not included in the random access resource configuration for repeated PRACH transmission. For example, not configuring the system message request period si-RequestPeriod can be understood as not including the system message request period si-RequestPeriod parameter in the random access resource configuration for repeated PRACH transmission.

[0156] The system message request period is a period during which the terminal transmits or repeatedly transmits a PRACH to request system information. The terminal transmits a PRACH once or repeatedly transmits a PRACH (including multiple PRACH transmissions) within a system message request period. The random access association period index indicates a time range within the system message request period. The UE transmits or repeatedly transmits a PRACH within the time range indicated by the random access association period index within a system message request period.

[0157] In a possible implementation manner, the system message request period and the random access association period index are configured in units of SSB to RO association period, and at least one of the following is satisfied:

[0158] The time length of the determined target RO group is not greater than the system message request period;

[0159] All ROs in the determined target RO group are within one of the system message request cycles;

[0160] The time length of the time offset is not greater than the system message request period;

[0161] The time range indicated by the random access association period index is outside the time range of the determined target RO group.

[0162] In a possible implementation, the determined time length of the target RO group is a time length corresponding to the time length from the first RO corresponding time to the last RO corresponding time in the determined target RO group.

[0163] In a possible implementation manner, the time range of the determined target RO group is a time range corresponding to the first RO corresponding time to the last RO corresponding time in the determined target RO group.

[0164] It can be understood that the time range indicated by the random access association period index is not outside the time range of the determined target RO group, which may mean that the time range indicated by the random access association period index is included in the range of the determined target RO group.

[0165] Referring to FIG3 , an embodiment of the present application provides a PRACH repetition transmission method, which may also be referred to as a Preamble repetition PRACH transmission method. The method is performed by a network-side device and includes:

[0166] Step 301: The network side device determines the time offset;

[0167] Step 302: The network side device determines all available RO groups based on the time offset;

[0168] Step 303: The network-side device performs PRACH repeated reception on all available RO groups;

[0169] The time offset is counted by valid ROs that are consecutive in the time domain and are associated with the same SSB at the same frequency position and the same Preamble set associated with the SSB;

[0170] Alternatively, the time offset is counted based on the valid ROs that are consecutive in the time domain and are associated with the same SSB at the same frequency position. The Preamble sets associated with the SSB on the valid ROs are not all the same. When some Preambles associated with an RO are not used for PRACH repeated transmission, all Preamble sets associated with the RO cannot be used for PRACH repeated transmission.

[0171] It should be noted that, as the opposite side of the terminal, in order to ensure that PRACH can be correctly repeated, the rules and methods used by the network side in determining the time offset and determining the target RO group based on the time offset must be consistent with those of the terminal side. That is, it is ensured that the network side and the terminal have the same understanding, and the sending and receiving ends use the same RO group to ensure successful repeated PRACH reception.

[0172] It should also be noted that the network side needs to determine all RO groups corresponding to all SSBs. The network side does not need to determine the target RO group, or in other words, the target RO group determined by the network side is all available RO groups. After the network side determines all available RO groups, it will perform blind detection on all available RO groups.

[0173] In the embodiment of the present application, the description of the specific content of the network side solution can be understood by referring to the description of the terminal side solution, and will not be repeated here.

[0174] In a possible implementation, the network-side device determines all available RO groups based on the time offset, including:

[0175] When the preset conditions are met, the network-side device determines all available RO groups based on the time offset;

[0176] The preconditions include one or more of the following:

[0177] The time offset value is configured;

[0178] is an integer value;

[0179] is an integer value;

[0180] In all ROs associated with the same SSB at the same frequency domain position, the preamble sets associated with the SSB on the RO are all the same;

[0181] Where N is the number of SSBs associated with an RO, is the total number of SSBs.

[0182] In a possible implementation, the network-side device determines all available RO groups based on the time offset, including:

[0183] For all SSBs, the network-side device determines the starting RO of the first RO group associated with each SSB within the first time range;

[0184] The network-side device determines all available RO groups based on the starting RO and time offset of the first RO group;

[0185] In a possible implementation, for all SSBs, the network-side device determines, within a first time range, the starting RO of the first RO group associated with each SSB, including:

[0186] The network-side device divides the ROs associated with the same SSB into M categories based on the Preamble set on the RO associated with the SSB, where the Preamble set associated with the same SSB on each category of RO is the same;

[0187] The network-side device determines, in each type of RO, the first RO in the first time range as the starting RO of the first RO group in an order of increasing in the frequency domain first and then in the time domain, or determines, in each type of RO at each frequency position, the first RO in the first time range as the starting RO of the first RO group in an order of increasing in the time domain.

[0188] In a possible implementation, the network-side device determines all available RO groups based on the starting RO and time offset of the first RO group, including:

[0189] Within the first time range, the network-side device determines the starting RO of subsequent RO groups based on a frequency domain order followed by a time domain order, starting at each moment corresponding to the starting RO+(time offset)*m ROs of the first RO group, where the value of m includes one or more integers not less than 0.

[0190] The network-side device determines all available RO groups based on the starting RO.

[0191] In a possible implementation, the network-side device determines all available RO groups based on the starting RO and time offset of the first RO group, including:

[0192] The network-side device starts at each moment corresponding to the starting RO+(time offset)*m ROs of the first RO group within the first time range. Within the second time range, among the ROs outside the determined RO group, the network-side device determines the starting ROs of subsequent RO groups based on the order of first increasing in the frequency domain and then increasing in the time domain, where the value of m includes one or more integers not less than 0, and the second time range is the time length corresponding to the first RO group within the first time range, or the number of moments included in the first RO group, or the number of moments included in the first RO group - 1.

[0193] The network-side device determines all available RO groups based on the starting RO.

[0194] In one possible implementation, the method further includes:

[0195] If the preset condition is not met, the network side device determines the starting RO of the first RO group associated with each SSB for all SSBs within the first time range;

[0196] The network-side device determines, within the first time range, the starting RO of the subsequent RO group in the order of increasing frequency domain positions first and then increasing time domain positions.

[0197] In one possible implementation, when no time offset is preconfigured, the network-side device determines the time offset value, including:

[0198] The network-side device determines the time offset value to be any of the following:

[0199] a first number of repeated transmissions, where the first number of repeated transmissions is a number of repeated transmissions configured by the network side device for the terminal to perform PRACH repeated transmissions on the target RO group;

[0200] The second number of repeated transmissions is one of multiple PRACH repeated transmission times configured by the network side device.

[0201] In one possible implementation, the time offset satisfies:

[0202] The minimum value of the time offset is the configurable minimum number of PRACH retransmissions, and the maximum value of the time offset is greater than or equal to the configurable maximum number of PRACH retransmissions.

[0203] In one possible implementation, the time offset satisfies:

[0204] Different PRACH repetition transmission times correspond to the same time offset, or different PRACH repetition transmission times correspond to different time offsets.

[0205] In one possible implementation, the method further includes:

[0206] The network side device configures a random access resource configuration for PRACH repeated transmission requested by a system message, wherein the random access resource configuration for PRACH repeated transmission includes one of the following:

[0207] At least one of the system message request period si-RequestPeriod, random access association period index ra-AssociationPeriodIndex, and RO mask index ra-ssb-OccasionMaskIndex is not configured;

[0208] Configuring a system message request period and a random access associated period index, wherein the system message request period and the random access associated period index are in units of a first time range;

[0209] Configure the system message request period and random access association period index, wherein the system message request period and random access association period index are in units of SSB to RO association period.

[0210] In a possible implementation manner, the system message request period and the random access association period index are configured in units of SSB to RO association period, and at least one of the following is satisfied:

[0211] The time length of the determined target RO group is not greater than the system message request period;

[0212] All ROs in the determined target RO group are within one of the system message request cycles;

[0213] The time length of the time offset is not greater than the system message request period;

[0214] The time range indicated by the random access association period index is outside the time range of the determined target RO group.

[0215] The technical solution of this application is described below with reference to specific embodiments:

[0216] Example 1:

[0217] When the Preamble sets associated with the same SSB on different ROs are not all the same ( is a decimal greater than 1, or is a decimal less than 1 and is not an integer):

[0218] Embodiment 1-1: The time offset is counted by valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position and have the same preamble set associated with the SSB.

[0219] For example, N=2, The association relationship between SSB and RO / Preamble is shown in Figure 4a.

[0220] In the figure, every two SSBs are associated with the same RO. The two SSBs on the same RO occupy the same frequency domain resources, differing only in the preamble set. For example, for SSB#0, SSB#0 is associated with preamble set#0 on RO#0. {RO#6, RO#12, RO#18} are all associated with SSB#0 and have the same frequency domain location and associated preamble set as RO#0. {RO#4, RO#10, RO#16, RO#22} have the same frequency domain location as RO#0, but are associated with a different preamble set (associated with preamble set#1). Therefore, for SSB#0, when calculating the time offset using RO#0 as the starting RO, only RO#6, RO#12, and RO#18 are included. The next starting RO corresponding to time offset = 1 is RO#6, the next starting RO corresponding to time offset = 2 is RO#12, and the next starting RO corresponding to time offset = 3 is RO#18.

[0221] Embodiment 1-2: The time offset is counted by valid ROs consecutive in the time domain and associated with the same SSB at the same frequency position, wherein when a certain RO is unavailable for at least one SSB, the RO is considered unavailable.

[0222] For example, for SSB#0, with RO#0 as the starting RO, {RO#4, RO#6, RO#10, RO#12, RO#16, RO#18, RO#22} are all associated with SSB#0 and have the same frequency domain location as RO#0. The next starting ROs corresponding to time offsets 1 to 7 are shown in Figure 4b below.

[0223] Assuming the PRACH repetition count is 2, then {RO#0, RO#6} is the RO group associated with SSB#1, and {RO#2, RO#8} is the RO group associated with SSB#2. Assuming time offset = 3, RO#2 is unavailable for SSB#1 but available for SSB#2. In this case, RO#2 is considered unavailable for both SSB#1 and SSB#2. The UE does not send a preamble on RO#2, and the network does not detect on RO#2.

[0224] Example 1-3: For the same SSB, the associated ROs are divided into M categories based on the preamble set of their associated ROs, where the preamble set associated with the SSB is the same for each category of ROs. Within a time window X, the starting RO of the first RO group is determined for each category of ROs, or the starting RO of the first RO group is determined for each category of ROs on the same frequency.

[0225] For example, in Figure 4b, for SSB#0, its associated ROs {RO#0, RO#1, RO#3, RO#4, RO#6, RO#7, RO#9, RO#10, RO#12, RO#13, RO#15, RO#16, RO#18, RO#19, RO#21, RO#22} can be divided into two categories: the first category {RO#0, RO#3, RO#6, RO#9, RO#12, RO#15, RO#18, RO#21}, and the second category {RO#1, RO#4, RO#7, RO#10, RO#13, RO#16, RO#19, RO#22}. The first category ROs are associated with Preamble set #0, while the second category ROs are associated with Preamble set #1. Within time window X, the starting RO of the first RO group in the first category ROs is RO#0, and the starting RO of the first RO group in the second category ROs is RO#1. Alternatively, within the time window X, determine the starting RO of the first RO group in each type of RO at the same frequency position. In the figure, the starting RO of the first RO group in the first type of RO at the low-frequency position is RO#0, and the starting RO of the first RO group in the second type of RO is RO#4. At the high-frequency position, the starting RO of the first RO group in the first type of RO is RO#3, and the starting RO of the first RO group in the second type of RO is RO#1.

[0226] Example 2:

[0227] Example 2-1: If the time offset is not configured, the time offset may be set to be equal to the corresponding PRACH repetition number (RO group size) or equal to the configured maximum PRACH repetition number (maximum RO group size).

[0228] For example, if the PRACH repetition number set configured by the network is {2, 4, 8}, then when determining the RO group, the time offsets corresponding to PRACH repetition numbers 2, 4, and 8 are 2, 4, and 8, respectively. For another example, if the PRACH repetition number set configured by the network is {2, 4, 8}, then when determining the RO group, the time offsets corresponding to PRACH repetition numbers 2, 4, and 8 are all 8.

[0229] In Example 2-2, the minimum time offset is the configurable minimum PRACH repetition number, and the maximum time offset is greater than the configurable maximum PRACH repetition number. Devices with different PRACH repetition numbers can share the same time offset or use their own corresponding time offsets.

[0230] For example, the network can configure the number of PRACH repetitions to be {2, 4, 8}, the minimum time offset value is 2, and the maximum value is greater than 8.

[0231] Example 2-3: When the time offset value is configured, and is an integer value or If it is an integer value, the RO group is determined based on the time offset. Otherwise, the RO group is determined based on the rule without a time offset.

[0232] Integer value represents The number of ROs required for a SSB to complete a mapping cycle is an integer. An integer value represents an integer number of mapping cycles that can be completed on an RO. For example, when N<1, an SSB is associated with consecutive ROs, The number of ROs required to complete a mapping cycle for each SSB is an integer; when N>1, for example, N=4, The RO required for each SSB to complete a mapping cycle is 1.

[0233] Embodiment 2-4: Based on the RO group determination rule, the UE selects the first available RO group closest to the current time and associated with the selected SSB within the time window X to repeatedly transmit the PRACH.

[0234] For example, as shown in Figure 4c below, the UE triggers PRACH repetition transmission with a repetition count of 2 at time t1, and the UE selects SSB#0. Within the time window X, the RO group associated with SSB#0 closest to t1 is RO group#3 = {RO#6, RO#9}, so the UE selects RO group#3 for PRACH repetition transmission.

[0235] Example 2-5: For each SSB, starting from each moment corresponding to the starting RO+(time offset)*m ROs of the first RO group within the time window X, within the time range X2 / within M / (M-1) moments, among the ROs outside the determined RO group, the starting ROs of subsequent RO groups are determined sequentially based on the order of first increasing in the frequency domain and then increasing in the time domain, where m is an integer greater than or equal to 0, X2 is the time length / time span corresponding to the first RO group within the time range X, and M is the number of moments included in the first RO group within X.

[0236] For example, as shown in Figure 4d, assuming a PRACH repetition count of 2 and time offset = 3, for SSB#0, the starting RO of the first RO group within time window X is found, denoted by n1, in the order of time domain first and frequency domain second, and RO group#0 is determined. The time span corresponding to RO group#0 is 4 time moments. Therefore, starting from the time corresponding to n1 and the time of the RO corresponding to n1+(time offset)*1, within 4 / (4-1) time moments, the starting ROs and corresponding RO groups of subsequent RO groups are determined in ascending order of frequency domain first and then time domain.

[0237] Example 2-6: The above examples can be implemented in combination. For example, the time offset in Example 2-5 can be the time offset defined in Example 1-1 or the time offset defined in Example 1-2.

[0238] Example 3:

[0239] Example 3-1: The network-configured system message request period si-RequestPeriod and random access association period index ra-AssociationPeriodIndex are indicated in units of a first time range. For example, the first time range is time window X, where X includes K SSB-to-RO association mode periods. Then, the time unit indicated by the system message request period si-RequestPeriod and the random access association period index ra-AssociationPeriodIndex is X. For example, the system message request period si-RequestPeriod includes N2 time windows X, and the random access association period index ra-AssociationPeriodIndex indicates at least one time window X in the system message request period si-RequestPeriod.

[0240] Example 3-2: The network configures the system message request period si-RequestPeriod and the random access association period index ra-AssociationPeriodIndex to indicate the SSB to RO association period as a unit. For example, the system message request period si-RequestPeriod includes N3 SSB to RO association periods, and the random access association period index ra-AssociationPeriodIndex indicates at least one SSB to RO association period in the system message request period si-RequestPeriod. In this case, the configuration of the system message request period si-RequestPeriod and the random access association period index ra-AssociationPeriodIndex should ensure at least one of the following:

[0241] The time length of the determined RO group (i.e., the time length from the corresponding moment of the first RO to the corresponding moment of the last RO in the RO group) is not greater than the system message request period;

[0242] Ensure that all ROs in a certain RO group are within a system message request cycle;

[0243] Ensure that the configured time offset is no longer than the system message request period.

[0244] It is ensured that the time range indicated by the random access association period index cannot be outside the time range of the determined RO group (the time range corresponding to the first RO corresponding time to the last RO corresponding time in the RO group).

[0245] The PRACH repeated transmission method provided in the embodiment of the present application can be executed by a subject. In the embodiment of the present application, the PRACH repeated transmission method is executed by a PRACH repeated transmission device as an example to illustrate the PRACH repeated transmission device provided in the embodiment of the present application.

[0246] Referring to FIG5 , an embodiment of the present application provides a PRACH repeated transmission device, which can be applied to a terminal and includes:

[0247] A first determining module 501 is used for the terminal to determine a time offset;

[0248] A second determining module 502 is configured for the terminal to determine a target RO group according to the time offset;

[0249] A transmission module 503, configured for the terminal to perform PRACH repeated transmission on the target RO group;

[0250] The time offset is counted as valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position and the same Preamble set associated with the SSB;

[0251] Alternatively, the time offset is counted as valid ROs that are continuous in the time domain and associated with the same SSB at the same frequency position, and the Preamble sets associated with the SSB on the valid RO are not all the same, wherein when part of the Preamble associated with an RO is not used for PRACH repeated transmission, all Preamble sets associated with the RO cannot be used for PRACH repeated transmission.

[0252] Optionally, the second determining module is specifically configured to:

[0253] When a preset condition is met, the terminal determines a target RO group according to the time offset;

[0254] The preset conditions include one or more of the following:

[0255] The time offset value is configured;

[0256] is an integer value;

[0257] is an integer value;

[0258] In all ROs associated with the same SSB at the same frequency domain position, the preamble sets associated with the SSB on the RO are all the same;

[0259] Wherein, N is the number of SSBs associated with an RO, is the total number of SSBs.

[0260] Optionally, the second determining module is specifically configured to:

[0261] The terminal determines, within a first time range, a starting RO of a first RO group associated with a target SSB;

[0262] The terminal determines a plurality of RO groups according to the starting RO of the first RO group and the time offset;

[0263] The terminal determines the target RO group from the multiple RO groups;

[0264] Among them, the target SSB is the SSB selected by the terminal or indicated by the network side device.

[0265] Optionally, the second determining module is specifically configured to:

[0266] The terminal divides the associated ROs into M categories according to the Preamble set on the RO associated with the target SSB, wherein the Preamble set associated with the SSB on each category of RO is the same;

[0267] The terminal determines, in each type of RO, in an order of first increasing in the frequency domain and then increasing in the time domain, the first RO within the first time range as the starting RO of the first RO group; or the terminal determines, in each type of RO at each frequency position, in an order of increasing in the time domain, the first RO within the first time range as the starting RO of the first RO group.

[0268] Optionally, the second determining module is specifically configured to:

[0269] Within the first time range, the terminal determines the starting RO of a subsequent RO group based on a frequency domain order followed by a time domain order, starting at each moment corresponding to the starting RO+(time offset)*m ROs of the first RO group, where the value of m includes one or more integers not less than 0.

[0270] The terminal determines a plurality of RO groups based on the starting RO.

[0271] Optionally, the second determining module is specifically configured to:

[0272] The terminal, starting from each moment corresponding to starting RO+(time offset)*m ROs of the first RO group within the first time range, determines, within a second time range, among ROs outside the determined RO group, starting ROs of subsequent RO groups based on an order of first increasing in the frequency domain and then increasing in the time domain, where the value of m includes one or more integers not less than 0, and the second time range is the time length corresponding to the first RO group within the first time range, or the number of moments included in the first RO group, or the number of moments included in the first RO group minus 1.

[0273] The terminal determines a plurality of RO groups based on the starting RO.

[0274] Optionally, the second determining module is specifically configured to perform one or more of the following:

[0275] In the order of increasing in frequency domain first and then in time domain, the first available RO group closest to the current time within the first time range and associated with the target SSB is determined as the target RO group;

[0276] Determine the available RO group at the lowest frequency position closest to the current time within the first time range and associated with the selected target SSB as the target RO group;

[0277] Determine the available RO group at the highest frequency position closest to the current time within the first time range and associated with the selected target SSB as the target RO group;

[0278] The ROs in the available RO group are after the current time.

[0279] Optionally, the device further comprises:

[0280] a fifth determining module, configured to, if the preset condition is not met, determine, by the terminal, a starting RO of a first RO group associated with a target SSB within a first time range;

[0281] The sixth determining module is configured to determine, by the terminal within the first time range, the starting RO of the RO group subsequently associated with the target SSB in the order of increasing frequency domain position first and then increasing time domain position.

[0282] Optionally, when the time offset is not preconfigured, the first determining module is specifically configured to:

[0283] The terminal determines that the time offset value is any one of the following:

[0284] a first number of repeated transmissions, where the first number of repeated transmissions is a configured number of repeated transmissions corresponding to the PRACH repeated transmission performed by the terminal on the target RO group;

[0285] The second number of repeated transmissions is one of the multiple configured PRACH repeated transmission times.

[0286] Optionally, the time offset satisfies:

[0287] The minimum value of the time offset is the configurable minimum number of PRACH repeated transmissions, and the maximum value of the time offset is greater than or equal to the configurable maximum number of PRACH repeated transmissions.

[0288] Optionally, the time offset satisfies:

[0289] Different PRACH repetition transmission times correspond to the same time offset, or different PRACH repetition transmission times correspond to different time offsets.

[0290] Optionally, the random access resource configuration for repeated PRACH transmission is used for a system message request, wherein the random access resource configuration for repeated PRACH transmission includes one of the following:

[0291] At least one of the system message request period si-RequestPeriod, random access association period index ra-AssociationPeriodIndex, and RO mask index ra-ssb-OccasionMaskIndex is not configured;

[0292] Configuring a system message request period and a random access associated period index, wherein the system message request period and the random access associated period index are in units of a first time range;

[0293] Configure the system message request period and random access association period index, wherein the system message request period and random access association period index are in units of SSB to RO association period.

[0294] Optionally, the system message request period and random access association period index are configured in units of SSB to RO association period, and at least one of the following is satisfied:

[0295] The time length of the determined target RO group is not greater than the system message request period;

[0296] All ROs in the determined target RO group are within one of the system message request cycles;

[0297] The time length of the time offset is not greater than the system message request period;

[0298] The time range indicated by the random access association period index is outside the time range of the determined target RO group.

[0299] 6 , an embodiment of the present application provides a PRACH repeated transmission apparatus, which can be applied to a network-side device. The apparatus includes:

[0300] The third determining module 601 is used for the network side device to determine the time offset;

[0301] A fourth determining module 602 is configured for the network side device to determine all available RO groups according to the time offset;

[0302] A receiving module 603 is configured for the network side device to repeatedly receive PRACH on all available RO groups;

[0303] The time offset is counted as valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position and the same Preamble set associated with the SSB;

[0304] Alternatively, the time offset is counted as valid ROs that are continuous in the time domain and associated with the same SSB at the same frequency position, and the Preamble sets associated with the SSB on the valid RO are not all the same, wherein when part of the Preamble associated with an RO is not used for PRACH repeated transmission, all Preamble sets associated with the RO cannot be used for PRACH repeated transmission.

[0305] Optionally, the fourth determining module is specifically configured to:

[0306] When a preset condition is met, the network side device determines all available RO groups according to the time offset;

[0307] The preset conditions include one or more of the following:

[0308] The time offset value is configured;

[0309] is an integer value;

[0310] is an integer value;

[0311] In all ROs associated with the same SSB at the same frequency domain position, the preamble sets associated with the SSB on the RO are all the same;

[0312] Wherein, N is the number of SSBs associated with an RO, is the total number of SSBs.

[0313] Optionally, the fourth determining module is specifically configured to:

[0314] The network side device determines, for all SSBs within a first time range, a starting RO of a first RO group associated with each SSB;

[0315] The network-side device determines all available RO groups according to the starting RO of the first RO group and the time offset;

[0316] Among them, the target SSB is the SSB selected by the terminal or indicated by the network side device.

[0317] Optionally, the fourth determining module is specifically configured to:

[0318] The network-side device divides the ROs associated with the same SSB into M categories according to the Preamble set on the RO associated with the SSB, wherein the Preamble set associated with the SSB on each category of RO is the same;

[0319] The network-side device determines, in each type of RO, the first RO within the first time range as the starting RO of the first RO group in an order of increasing in the frequency domain first and then in the time domain, or determines, in each type of RO at each frequency position, the first RO within the first time range as the starting RO of the first RO group in an order of increasing in the time domain.

[0320] Optionally, the fourth determining module is specifically configured to:

[0321] Within the first time range, the network-side device determines, starting at each time instant corresponding to starting RO+(time offset)*m ROs of the first RO group, starting from a frequency domain order followed by a time domain order, where m is one or more integers not less than 0;

[0322] The network-side device determines all available RO groups based on the starting RO.

[0323] Optionally, the fourth determining module is specifically configured to:

[0324] The network-side device determines, starting from each moment corresponding to starting RO+(time offset)*m ROs of the first RO group within the first time range, starting from ROs other than the determined RO group within the second time range, the starting ROs of subsequent RO groups based on the order of first increasing in the frequency domain and then increasing in the time domain, where the value of m includes one or more integers not less than 0, and the second time range is the time length corresponding to the first RO group within the first time range, or the number of moments included in the first RO group, or the number of moments included in the first RO group - 1;

[0325] The network-side device determines all available RO groups based on the starting RO.

[0326] Optionally, the device further comprises:

[0327] a seventh determining module, configured to, when the preset condition is not satisfied, determine, by the network side device, for all SSBs within a first time range, a starting RO of a first RO group associated with each SSB;

[0328] An eighth determining module is configured to determine, by the network side device, within the first time range, a starting RO of a subsequent RO group in the order of increasing frequency domain positions first and then increasing time domain positions.

[0329] Optionally, when the time offset is not preconfigured, the third determining module is specifically configured to:

[0330] The network-side device determines that the time offset value is any one of the following:

[0331] a first number of repeated transmissions, where the first number of repeated transmissions is a number of repeated transmissions configured by the network side device for the terminal to perform PRACH repeated transmissions on the target RO group;

[0332] The second number of repeated transmissions is one of multiple PRACH repeated transmission times configured by the network side device.

[0333] Optionally, the time offset satisfies:

[0334] The minimum value of the time offset is the configurable minimum number of PRACH repeated transmissions, and the maximum value of the time offset is greater than or equal to the configurable maximum number of PRACH repeated transmissions.

[0335] Optionally, the time offset satisfies:

[0336] Different PRACH repetition transmission times correspond to the same time offset, or different PRACH repetition transmission times correspond to different time offsets.

[0337] Optionally, the device further comprises:

[0338] A configuration module, configured to configure a random access resource configuration for PRACH repeated transmission requested by a system message, wherein the random access resource configuration for PRACH repeated transmission includes one of the following:

[0339] At least one of the system message request period si-RequestPeriod, random access association period index ra-AssociationPeriodIndex, and RO mask index ra-ssb-OccasionMaskIndex is not configured;

[0340] Configuring a system message request period and a random access associated period index, wherein the system message request period and the random access associated period index are in units of a first time range;

[0341] Configure the system message request period and random access association period index, wherein the system message request period and random access association period index are in units of SSB to RO association period.

[0342] Optionally, the system message request period and random access association period index are configured in units of SSB to RO association period, and at least one of the following is satisfied:

[0343] The time length of the determined target RO group is not greater than the system message request period;

[0344] All ROs in the determined target RO group are within one of the system message request cycles;

[0345] The time length of the time offset is not greater than the system message request period;

[0346] The time range indicated by the random access association period index is outside the time range of the determined target RO group.

[0347] The PRACH retransmission apparatus in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component of the electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include, but is not limited to, the types of terminal 11 listed above. Other devices can include servers, network attached storage (NAS), etc., and are not specifically limited in the embodiments of the present application.

[0348] The PRACH repeated transmission device provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of Figures 2 to 4d and achieve the same technical effects. To avoid repetition, they will not be described here.

[0349] As shown in Figure 7, an embodiment of the present application further provides a communication device 700, including a processor 701 and a memory 702. The memory 702 stores a program or instruction that can be run on the processor 701. For example, when the communication device 700 is a terminal, the program or instruction, when executed by the processor 701, implements the various steps of the above-mentioned method embodiment and can achieve the same technical effect. When the communication device 700 is a network-side device, the program or instruction, when executed by the processor 701, implements the various steps of the above-mentioned method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0350] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps in the above-described terminal-side method embodiment. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and each implementation process and implementation method of the above-described method embodiment can be applied to this terminal embodiment and achieve the same technical effect. Specifically, Figure 8 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0351] The terminal 800 includes but is not limited to: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809 and at least some of the components of the processor 810.

[0352] Those skilled in the art will appreciate that the terminal 800 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 810 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG8 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0353] It should be understood that in an embodiment of the present application, the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042, and the GPU 8041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 806 may include a display panel 8061, and the display panel 8061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 807 includes a touch panel 8071 and at least one of other input devices 8072. The touch panel 8071 is also called a touch screen. The touch panel 8071 may include two parts: a touch detection device and a touch controller. Other input devices 8072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0354] In the embodiment of the present application, after receiving downlink data from a network-side device, the radio frequency unit 801 may transmit the data to the processor 810 for processing. Furthermore, the radio frequency unit 801 may send uplink data to the network-side device. Typically, the radio frequency unit 801 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0355] The memory 809 can be used to store software programs or instructions and various data. The memory 809 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 809 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 809 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0356] Processor 810 may include one or more processing units. Optionally, processor 810 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 810.

[0357] The processor 810 is configured to determine a time offset at the terminal.

[0358] Processor 810, configured for the terminal to determine a target RO group according to the time offset;

[0359] The radio frequency unit 801 is configured for the terminal to perform PRACH repeated transmission on the target RO group;

[0360] The time offset is counted as valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position and the same Preamble set associated with the SSB;

[0361] Alternatively, the time offset is counted as valid ROs that are continuous in the time domain and associated with the same SSB at the same frequency position, and the Preamble sets associated with the SSB on the valid RO are not all the same, wherein when part of the Preamble associated with an RO is not used for PRACH repeated transmission, all Preamble sets associated with the RO cannot be used for PRACH repeated transmission.

[0362] Optionally, the processor 810 is specifically configured to:

[0363] When a preset condition is met, the terminal determines a target RO group according to the time offset;

[0364] The preset conditions include one or more of the following:

[0365] The time offset value is configured;

[0366] is an integer value;

[0367] is an integer value;

[0368] In all ROs associated with the same SSB at the same frequency domain position, the preamble sets associated with the SSB on the RO are all the same;

[0369] Wherein, N is the number of SSBs associated with an RO, is the total number of SSBs.

[0370] Optionally, the processor 810 is specifically configured to:

[0371] The terminal determines, within a first time range, a starting RO of a first RO group associated with a target SSB;

[0372] The terminal determines a plurality of RO groups according to the starting RO of the first RO group and the time offset;

[0373] The terminal determines the target RO group from the multiple RO groups;

[0374] Among them, the target SSB is the SSB selected by the terminal or indicated by the network side device.

[0375] Optionally, the processor 810 is specifically configured to:

[0376] The terminal divides the associated ROs into M categories according to the Preamble set on the RO associated with the target SSB, wherein the Preamble set associated with the SSB on each category of RO is the same;

[0377] The terminal determines, in each type of RO, in an order of first increasing in the frequency domain and then increasing in the time domain, the first RO within the first time range as the starting RO of the first RO group; or the terminal determines, in each type of RO at each frequency position, in an order of increasing in the time domain, the first RO within the first time range as the starting RO of the first RO group.

[0378] Optionally, the processor 810 is specifically configured to:

[0379] Within the first time range, the terminal determines, starting at each time instant corresponding to the starting RO+(time offset)*m ROs of the first RO group, the starting RO of the subsequent RO group based on a frequency domain order followed by a time domain order, where the value of m includes one or more integers not less than 0;

[0380] The terminal determines a plurality of RO groups based on the starting RO.

[0381] Optionally, the processor 810 is specifically configured to:

[0382] The terminal determines, starting from each moment corresponding to starting RO+(time offset)*m ROs of the first RO group within the first time range, and within a second time range, among ROs outside the determined RO group, the starting ROs of subsequent RO groups based on the order of first increasing in the frequency domain and then increasing in the time domain, where the value of m includes one or more integers not less than 0, and the second time range is the time length corresponding to the first RO group within the first time range, or the number of moments included in the first RO group, or the number of moments included in the first RO group - 1;

[0383] The terminal determines a plurality of RO groups based on the starting RO.

[0384] Optionally, the processor 810 is specifically configured to perform one or more of the following:

[0385] In the order of increasing in frequency domain first and then in time domain, the first available RO group closest to the current time within the first time range and associated with the target SSB is determined as the target RO group;

[0386] Determine the available RO group that is closest to the current time within the first time range, is associated with the selected target SSB, and has the lowest frequency position as the target RO group;

[0387] Determine the available RO group that is closest to the current time within the first time range, is associated with the selected target SSB, and has the highest frequency position as the target RO group;

[0388] The ROs in the available RO group are after the current time.

[0389] Optionally, the processor 810 is configured to, if the preset condition is not met, determine, by the terminal, a starting RO of a first RO group associated with a target SSB within a first time range;

[0390] The processor 810 is configured to determine, by the terminal, within the first time range, a starting RO of an RO group subsequently associated with the target SSB in an order of increasing frequency domain positions first and then increasing time domain positions.

[0391] Optionally, when the time offset is not preconfigured, the processor 810 is specifically configured to:

[0392] The terminal determines that the time offset value is any one of the following:

[0393] a first number of repeated transmissions, where the first number of repeated transmissions is a configured number of repeated transmissions corresponding to the PRACH repeated transmission performed by the terminal on the target RO group;

[0394] The second number of repeated transmissions is one of the multiple configured PRACH repeated transmission times.

[0395] Optionally, the time offset satisfies:

[0396] The minimum value of the time offset is the configurable minimum number of PRACH repeated transmissions, and the maximum value of the time offset is greater than or equal to the configurable maximum number of PRACH repeated transmissions.

[0397] Optionally, the time offset satisfies:

[0398] Different PRACH repetition transmission times correspond to the same time offset, or different PRACH repetition transmission times correspond to different time offsets.

[0399] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be described here.

[0400] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the aforementioned network-side method embodiment. This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this network-side device embodiment and can achieve the same technical effects.

[0401] Specifically, embodiments of the present application further provide a network-side device, which is an access network device. As shown in Figure 9, the network-side device 900 includes an antenna 91, a radio frequency device 92, a baseband device 93, a processor 94, and a memory 95. Antenna 91 is connected to radio frequency device 92. In the uplink direction, radio frequency device 92 receives information via antenna 91 and sends the received information to baseband device 93 for processing. In the downlink direction, baseband device 93 processes the information to be transmitted and sends it to radio frequency device 92. Radio frequency device 92 processes the received information and then sends it through antenna 91.

[0402] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 93 , which includes a baseband processor.

[0403] The baseband device 93 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 9, one of the chips is, for example, a baseband processor, which is connected to the memory 95 through a bus interface to call the program in the memory 95 and execute the network device operations shown in the above method embodiment.

[0404] The network side device may further include a network interface 96, which is, for example, a Common Public Radio Interface (CPRI).

[0405] Specifically, the network side device 900 of the embodiment of the present application also includes: instructions or programs stored in the memory 95 and executable on the processor 94. The processor 94 calls the instructions or programs in the memory 95 to execute the methods of execution of each module shown in FIG6 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0406] Specifically, an embodiment of the present application further provides a network-side device, which is a core network device. As shown in Figure 10, the network-side device 1000 includes: a processor 1001, a network interface 1002, and a memory 1003. The network interface 1002 is, for example, a common public radio interface (CPRI).

[0407] Specifically, the network side device 1000 of the embodiment of the present application also includes: instructions or programs stored in the memory 1003 and executable on the processor 1001. The processor 1001 calls the instructions or programs in the memory 1003 to execute the method of execution of each module shown in Figure 6 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0408] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0409] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0410] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned method embodiment and achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

[0412] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0413] An embodiment of the present application also provides a wireless communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the terminal side method described above, and the network side device can be used to execute the steps of the network side method described above.

[0414] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0415] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0416] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A PRACH repeated transmission method, the method comprising: The terminal determines a time offset; The terminal determines a target physical random access channel transmission opportunity set RO group according to the time offset; The terminal performs repeated transmission of a physical random access channel PRACH on the target RO group; The time offset is counted by valid ROs that are continuous in the time domain and are associated with the same synchronization signal block SSB at the same frequency position and have the same preamble set associated with the SSB; Alternatively, the time offset is counted by valid ROs that are continuous in time domain and associated with the same SSB at the same frequency position, and the Preamble sets associated with the SSB on the valid ROs are not all the same, wherein when part of the Preambles associated with an RO are not used for PRACH repeated transmission, all Preamble sets associated with the RO are not used for PRACH repeated transmission.

2. The method according to claim 1, wherein: The terminal determines a target RO group according to the time offset, including: When a preset condition is met, the terminal determines a target RO group according to the time offset; The preset conditions include one or more of the following: The time offset value is configured; is an integer value; is an integer value; In all ROs associated with the same SSB at the same frequency domain position, the preamble sets associated with the SSB on the RO are all the same; Wherein, N is the number of SSBs associated with an RO, is the total number of SSBs.

3. The method according to claim 1 or 2, wherein: The terminal determines a target RO group according to the time offset, including: The terminal determines a starting RO of a first RO group associated with a target SSB within a first time range; The terminal determines a plurality of RO groups according to the starting RO of the first RO group and the time offset; the terminal determines the target RO group from the plurality of RO groups; Among them, the target SSB is the SSB selected by the terminal or indicated by the network side device.

4. The method according to claim 3, wherein: The terminal determines, within a first time range, a starting RO of a first RO group associated with a target SSB, including: The terminal divides the associated RO into M categories according to the Preamble set on the RO associated with the target SSB, wherein the Preamble set associated with the SSB on each category of RO is the same; The terminal determines, in each type of RO, the first RO within the first time range as the starting RO of the first RO group in an order of increasing in the frequency domain first and then in the time domain, or the terminal determines, in each type of RO at each frequency position, the first RO within the first time range as the starting RO of the first RO group in an order of increasing in the time domain.

5. The method according to claim 3 or 4, wherein: The terminal determines, according to the starting RO of the first RO group and the time offset, a plurality of RO groups, including: Within the first time range, the terminal determines the starting RO of the subsequent RO group based on the frequency domain order and then the time domain order, starting at each time corresponding to the starting RO+(time offset)*m ROs of the first RO group, where the value of m includes one or more integers not less than 0; The terminal determines a plurality of RO groups based on the starting RO.

6. The method according to any one of claims 3 to 5, wherein: The terminal determines, according to the starting RO of the first RO group and the time offset, a plurality of RO groups, including: The terminal starts at each moment corresponding to starting RO+(time offset)*m ROs of the first RO group within the first time range, and determines, in a second time range, among ROs outside the determined RO group, a starting RO of a subsequent RO group based on the order of increasing in frequency domain first and increasing in time domain later, where the value of m includes one or more integers not less than 0, and the second time range is the time length corresponding to the first RO group within the first time range, or the number of moments included in the first RO group, or the number of moments included in the first RO group - 1; The terminal determines a plurality of RO groups based on the starting RO.

7. The method according to claim 5 or 6, wherein: The terminal determines the target RO group from the multiple RO groups, including one or more of the following: In the order of increasing in frequency domain first and increasing in time domain second, determining the first available RO group in the first time range that is closest to the current time and associated with the target SSB as the target RO group; Determine the available RO group at the lowest frequency position closest to the current time within the first time range and associated with the selected target SSB as the target RO group; Determine the available RO group at the highest frequency position closest to the current time within the first time range and associated with the selected target SSB as the target RO group; The ROs in the available RO group are after the current time.

8. The method according to claim 2, further comprising: If the preset condition is not met, the terminal determines a starting RO of a first RO group associated with the target SSB within a first time range; The terminal determines, within the first time range, a starting RO of an RO group subsequently associated with the target SSB in the order of increasing frequency domain position first and then increasing time domain position.

9. The method according to claim 1, wherein: In the case where the time offset is not preconfigured, the terminal determines a value of the time offset, including: The terminal determines that the value of the time offset is any one of the following: a first number of repeated transmissions, where the first number of repeated transmissions is the number of repeated transmissions configured corresponding to the PRACH repeated transmission performed by the terminal on the target RO group; A second number of repeated transmissions, where the second number of repeated transmissions is one of the multiple configured PRACH repeated transmissions.

10. The method according to claim 1, wherein: The time offset satisfies: The minimum value of the time offset is the configurable minimum number of PRACH repeated transmissions, and the maximum value of the time offset is greater than or equal to the configurable maximum number of PRACH repeated transmissions.

11. The method according to claim 1, wherein: The time offset satisfies: Different PRACH repetition transmission times correspond to the same time offset, or different PRACH repetition transmission times correspond to different time offsets.

12. The method according to claim 1, wherein: The random access resource configuration for repeated PRACH transmission is used for a system message request, wherein the random access resource configuration for repeated PRACH transmission includes one of the following: At least one of the system message request period si-RequestPeriod, the random access association period index ra-AssociationPeriodIndex, and the RO mask index ra-ssb-OccasionMaskIndex is not configured; Configure a system message request period and a random access associated period index, wherein the system message request period and the random access associated period index are in units of a first time range; Configure a system message request period and a random access association period index, wherein the system message request period and the random access association period index are in units of SSB to RO association period.

13. The method according to claim 12, wherein: The system message request period and random access association period index are configured in units of SSB to RO association period, and at least one of the following is satisfied: The time length of the determined target RO group is not greater than the system message request period; All ROs in the determined target RO group are within a system message request cycle; The time length of the time offset is not greater than the system message request period; The time range indicated by the random access association period index is not outside the time range of the determined target RO group.

14. A PRACH repeated transmission method, the method comprising: The network-side device determines the time offset; The network side device determines all available RO groups according to the time offset; The network side device performs PRACH repeated reception on all available RO groups; The time offset is counted by valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position and the same Preamble set associated with the SSB; Alternatively, the time offset is counted by valid ROs that are continuous in time domain and associated with the same SSB at the same frequency position, and the Preamble sets associated with the SSB on the valid ROs are not all the same, wherein when part of the Preambles associated with an RO are not used for PRACH repeated transmission, all Preamble sets associated with the RO cannot be used for PRACH repeated transmission.

15. The method according to claim 14, wherein: The network side device determines all available RO groups according to the time offset, including: When a preset condition is met, the network side device determines all available RO groups according to the time offset; The preset conditions include one or more of the following: The time offset value is configured; is an integer value; is an integer value; In all ROs associated with the same SSB at the same frequency domain position, the preamble sets associated with the SSB on the RO are all the same; Wherein, N is the number of SSBs associated with an RO, is the number of all SSBs.

16. The method according to claim 14 or 15, wherein: The network side device determines all available RO groups according to the time offset, including: For all SSBs, the network side device determines the starting RO of the first RO group associated with each SSB within the first time range; The network side device determines all available RO groups according to the starting RO of the first RO group and the time offset.

17. The method according to claim 16, wherein: For all SSBs, the network side device determines the starting RO of the first RO group associated with each SSB within the first time range, including: The network side device divides the ROs associated with the same SSB into M categories according to the Preamble set on the RO associated with the SSB, wherein the Preamble set associated with the same SSB on each category of RO is the same; The network side device determines, in each type of RO, the first RO within the first time range as the starting RO of the first RO group in an order of increasing in the frequency domain first and then in the time domain, or the network side device determines, in each type of RO at each frequency position, the first RO within the first time range as the starting RO of the first RO group in an order of increasing in the time domain.

18. The method according to claim 16 or 17, wherein: The network side device determines all available RO groups according to the starting RO of the first RO group and the time offset, including: Within the first time range, the network side device determines the starting RO of the subsequent RO group based on the frequency domain order and then the time domain order, starting at each moment corresponding to the starting RO+(time offset)*m ROs of the first RO group, where the value of m includes one or more integers not less than 0; The network side device determines all available RO groups based on the starting RO.

19. The method according to any one of claims 16 to 18, wherein: The network side device determines all available RO groups according to the starting RO of the first RO group and the time offset, including: The network side device starts at each moment corresponding to starting RO+(time offset)*m ROs of the first RO group within the first time range, and determines, in a second time range, among ROs outside the determined RO group, a starting RO of a subsequent RO group based on the order of increasing in frequency domain first and increasing in time domain second, wherein the value of m includes one or more integers not less than 0, and the second time range is the time length corresponding to the first RO group within the first time range, or the number of moments included in the first RO group, or the number of moments included in the first RO group - 1; The network side device determines all available RO groups based on the starting RO.

20. The method according to claim 15, further comprising: When the preset condition is not met, the network side device determines, for all SSBs within the first time range, a starting RO of a first RO group associated with each SSB; The network side device determines, within the first time range, a starting RO of a subsequent RO group in the order of increasing frequency domain positions first and then increasing time domain positions.

21. The method according to claim 14, wherein: In the case where the time offset is not preconfigured, the network side device determines a value of the time offset, including: The network side device determines that the value of the time offset is any one of the following: A first number of repeated transmissions, where the first number of repeated transmissions is a number of repeated transmissions configured by the network side device for the terminal to perform PRACH repeated transmissions on the target RO group; The second number of repeated transmissions is one of a plurality of PRACH repeated transmissions configured by the network side device.

22. The method according to claim 14, wherein: The time offset satisfies: The minimum value of the time offset is the configurable minimum number of PRACH repeated transmissions, and the maximum value of the time offset is greater than or equal to the configurable maximum number of PRACH repeated transmissions.

23. The method according to claim 14, wherein: The time offset satisfies: Different PRACH repetition transmission times correspond to the same time offset, or different PRACH repetition transmission times correspond to different time offsets.

24. The method according to claim 14, further comprising: The network side device configures a random access resource configuration for PRACH repeated transmission requested by a system message, wherein the random access resource configuration for PRACH repeated transmission includes one of the following: At least one of the system message request period si-RequestPeriod, the random access association period index ra-AssociationPeriodIndex, and the RO mask index ra-ssb-OccasionMaskIndex is not configured; Configure a system message request period and a random access associated period index, wherein the system message request period and the random access associated period index are in units of a first time range; Configure a system message request period and a random access association period index, wherein the system message request period and the random access association period index are in units of SSB to RO association period.

25. The method according to claim 24, wherein: The system message request period and random access association period index are configured in units of SSB to RO association period, and at least one of the following is satisfied: The time length of the determined target RO group is not greater than the system message request period; All ROs in the determined target RO group are within a system message request cycle; The time length of the time offset is not greater than the system message request period; The time range indicated by the random access association period index is not outside the time range of the determined target RO group.

26. A PRACH repeated transmission device, the device comprising: A first determination module, used for the terminal to determine the time offset; A second determining module, configured for the terminal to determine a target RO group according to the time offset; A transmission module, used for the terminal to perform PRACH repeated transmission on the target RO group; The time offset is counted by valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position and the same Preamble set associated with the SSB; Alternatively, the time offset is counted by valid ROs that are continuous in time domain and associated with the same SSB at the same frequency position, and the Preamble sets associated with the SSB on the valid ROs are not all the same, wherein when part of the Preambles associated with an RO are not used for PRACH repeated transmission, all Preamble sets associated with the RO cannot be used for PRACH repeated transmission.

27. A PRACH repeated transmission device, the device comprising: A third determination module is used for the network side device to determine the time offset; A fourth determining module, configured for the network side device to determine all available RO groups according to the time offset; A receiving module, configured for the network side device to perform PRACH repeated reception on all available RO groups; The time offset is counted by valid ROs that are continuous in the time domain and are associated with the same SSB at the same frequency position and the same Preamble set associated with the SSB; Alternatively, the time offset is counted by valid ROs that are continuous in time domain and associated with the same SSB at the same frequency position, and the Preamble sets associated with the SSB on the valid ROs are not all the same, wherein when part of the Preambles associated with an RO are not used for PRACH repeated transmission, all Preamble sets associated with the RO cannot be used for PRACH repeated transmission.

28. A terminal, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the PRACH repeated transmission method according to any one of claims 1 to 13 are implemented.

29. A network side device, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the PRACH repeated transmission method as described in any one of claims 14 to 25 are implemented.

30. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the PRACH repeated transmission method according to any one of claims 1 to 13, or implements the steps of the PRACH repeated transmission method according to any one of claims 14 to 25.

Images