Method, terminal and network side device for determining prach repetition transmission resources

Abstract

The application discloses a method for determining PRACH repeated transmission resources, a terminal and a network side device, and belongs to the technical field of communication. The method for determining PRACH repeated transmission resources comprises the following steps: a terminal acquires resource configuration information for physical random access channel (PRACH) repeated transmission, wherein the resource configuration information indicates configured resources of the PRACH repeated transmission; and the terminal determines whether the configured resources are used for PRACH repeated transmission.

Description

Technical Field

[0001] This application belongs to the field of communication technology, and specifically relates to a method for determining PRACH repeated transmission resources, a terminal, and a network-side device. Background Technology

[0002] In existing technologies, random access procedures can be either contention-based or non-contention-based. A random access procedure can be a four-step random access procedure (also known as a Type-1 random access procedure) or a two-step random access procedure (also known as a Type-2 random access procedure).

[0003] Performing repetition transmissions on the Physical Random Access Channel (PRACH) in the time domain can improve PRACH coverage. Existing PRACH resource configuration schemes are relatively sparse and may have a maximum PRACH configuration period of 160ms. Using this resource configuration scheme for PRACH repetition transmissions could lead to longer random access delays and additional signaling overhead. Summary of the Invention

[0004] This application provides a method, terminal, and network-side device for determining PRACH retransmission resources, which can solve the problem of long random access delays caused by existing resource configuration schemes.

[0005] Firstly, a method for determining PRACH retransmission resources is provided, applied to a terminal, the method comprising:

[0006] The terminal obtains resource configuration information for repeated transmission of the Physical Random Access Channel (PRACH), the resource configuration information indicating the configuration resources for the repeated transmission of the PRACH;

[0007] The terminal determines whether the configuration resources are used for PRACH retransmission.

[0008] Secondly, an apparatus for determining PRACH retransmission resources is provided, applied to a terminal, comprising:

[0009] The first acquisition module is used to acquire resource configuration information for repeated transmission of the Physical Random Access Channel (PRACH), wherein the resource configuration information indicates the configuration resources for the repeated transmission of the PRACH.

[0010] The first determining module is used to determine whether the configuration resources are used for PRACH repeated transmission.

[0011] Thirdly, a method for determining PRACH retransmission resources is provided, applied to network-side devices, the method comprising:

[0012] Network-side devices determine the configuration resources for PRACH retransmission;

[0013] The network-side device determines whether the configuration resources are used to receive recurring PRACH transmissions.

[0014] Fourthly, an apparatus for determining PRACH retransmission resources is provided, applied to network-side equipment, comprising:

[0015] The fourth determination module is used to determine the configuration resources for repeated PRACH transmissions;

[0016] The fifth determining module is used to determine whether the configuration resource is used to receive repeatedly transmitted PRACH.

[0017] Fifthly, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0018] In a sixth aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to acquire resource configuration information for repeated transmission of the Physical Random Access Channel (PRACH), the resource configuration information indicating the configuration resources for the repeated transmission of PRACH; and determine whether the configuration resources are used for repeated transmission of PRACH.

[0019] In a seventh aspect, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the third aspect.

[0020] Eighthly, a network-side device is provided, including a processor and a communication interface, wherein the processor is configured to determine configuration resources for repeated PRACH transmissions; and to determine whether the configuration resources are used to receive repeatedly transmitted PRACH.

[0021] A ninth aspect provides a system for determining PRACH repeatable transmission resources, comprising: a terminal and a network-side device, wherein the terminal is configured to perform the steps of the method for determining PRACH repeatable transmission resources as described in the first aspect, and the network-side device is configured to perform the steps of the method for determining PRACH repeatable transmission resources as described in the third aspect.

[0022] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the third aspect.

[0023] Eleventhly, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being 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 third aspect.

[0024] In a twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and executed by at least one processor to implement the steps of the method for determining PRACH repeat transfer resources as described in the first aspect, or to implement the steps of the method for determining PRACH repeat transfer resources as described in the third aspect.

[0025] In this embodiment of the application, the terminal obtains configuration resources for PRACH retransmission and determines whether the configuration resources are actually used for PRACH retransmission, so that the terminal can use the configuration resources that can be actually used for PRACH retransmission to perform PRACH retransmission, thereby reducing random access latency. Attached Figure Description

[0026] Figure 1 This is a block diagram of a wireless communication system applicable to embodiments of this application;

[0027] Figure 2 This is a schematic diagram of the SSB mapping to the RO of the FDM in an embodiment of this application;

[0028] Figure 3 This is a schematic diagram of the RO mapping of SSB to TDM / FDM in an embodiment of this application;

[0029] Figure 4 This is one of the flowcharts illustrating the method for determining PRACH retransmission resources according to an embodiment of this application;

[0030] Figure 5 This is one of the RO processing methods in the embodiments of this application;

[0031] Figure 6 This is the second RO processing method in the embodiments of this application;

[0032] Figure 7 This is the third RO processing method in the embodiments of this application;

[0033] Figure 8 This is the fourth RO processing method in the embodiments of this application;

[0034] Figure 9 This is the fifth RO processing method in the embodiments of this application;

[0035] Figure 10 This is a second flowchart illustrating the method for determining PRACH retransmission resources according to an embodiment of this application;

[0036] Figure 11 This is one of the structural schematic diagrams of an apparatus for determining PRACH retransmission resources according to an embodiment of this application;

[0037] Figure 12 This is a second schematic diagram of the apparatus for determining PRACH retransmission resources according to an embodiment of this application;

[0038] Figure 13 This is a schematic diagram of the structure of a communication device according to an embodiment of this application;

[0039] Figure 14 This is a schematic diagram of the terminal structure according to an embodiment of this application;

[0040] Figure 15 This is a schematic diagram of the network-side device according to an embodiment of this application. Detailed Implementation

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

[0042] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0043] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, 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), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and NR terminology is used in most of the following description; however, these technologies can also be applied to applications beyond NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0044] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. Terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment. Network-side equipment 12 may include access network equipment or core network equipment. Access network equipment may also be referred to as radio access network equipment, radio access network (RAN), radio access network function, or radio access network unit. Access network equipment may include base stations, WLAN access points, or WiFi nodes, etc. Base stations may be referred to as Node B, evolved Node B (eNB), access point, base transceiver station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home B node, home evolved B node, Transmitting Receiving Point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0045] In describing the embodiments of this application, some concepts used in the following description will first be explained.

[0046] I. Random Access Procedure.

[0047] The random access procedure can be either a contention-based or non-contention-based random access procedure. It can be a four-step random access procedure (also known as a Type-1 random access procedure) or a two-step random access procedure (also known as a Type-2 random access procedure).

[0048] (1) 4-step random access procedure (RACH):

[0049] In the contention-based 4-step random access process, the UE first sends Msg1 to the network device, containing a preamble sequence. After detecting the preamble, the network sends Msg2 / Random Access Response (RAR) message, containing the number of the preamble detected by the network device and the uplink radio resources allocated to the UE to send Msg3. After receiving Msg2, the UE confirms that at least one of the preamble numbers carried in Msg2 matches the number of its own preamble. Then, according to the resources indicated by the RAR, it sends Msg3 containing contention resolution information. After receiving Msg3, the network device sends Msg4 containing contention resolution information. Upon receiving Msg4, the UE confirms that the resolution information is consistent with what it sent in Msg3, thus completing the 4-step random access process.

[0050] The network-side device includes uplink grant (UL grant) information in the RAR to indicate Msg3 Physical Uplink Shared Channel (PUSCH) scheduling information, and also includes RAPID (RACHpreamble ID), Temporary Cell Radio Network Temporary Identifier (TC-RNTI), Timing Advance (TA), and other information. If the network-side device does not receive the Msg3 PUSCH, it can schedule a retransmission of the Msg3 PUSCH in the Physical Downlink Control Channel (PDCCH) scrambled with TC-RNTI.

[0051] In a contention-based random access procedure, different UEs randomly select a preamble for transmission. This means different UEs might select the same preamble to transmit on the same time-frequency radio resources, a situation known as UE preamble conflict. In this case, different UEs will receive the same RAR (Registered Access Request). Therefore, different UEs will transmit the Msg3 PUSCH according to the scheduling information in the RAR ULgrant. When repeated transmission of the Msg3 PUSCH is not supported, the network-side device can only decode one UE's PUSCH (containing contention resolution information) on a single Msg3 PUSCH scheduling resource. Therefore, the network-side device will include the contention resolution information received in Msg3 in Msg4. If the contention resolution information received by the UE in Msg4 matches the contention resolution information sent by the UE in the Msg3 PUSCH, the UE considers the contention resolution successful. If they do not match, the contention resolution is considered unsuccessful.

[0052] If contention resolution fails, the UE will reselect RACH transmission resources, perform PRACH transmission, and attempt another random access attempt.

[0053] (2) Two-step random access procedure (2-step RACH):

[0054] The first step is for the UE to send MsgA to the network. After receiving MsgA, the network sends MsgB to the UE. If the UE does not receive MsgB within a certain time, it increments a counter counting the number of MsgA transmissions and retransmits MsgA. If the counter counts the number of MsgA transmissions and reaches a certain threshold, the UE switches from a 2-step random access procedure to a 4-step random access procedure. MsgA includes a MsgA preamble and a MsgA PUSCH. The preamble is transmitted on the RO used for 2-step RACH, and the PUSCH is transmitted on the MsgAPUSCH resources associated with the MsgA preamble and RO. The MsgA PUSCH resources are a set of PUSCH resources configured relative to each physical random access channel slot (PRACH slot), including time-frequency resources and demodulation reference signal (DMRS) resources.

[0055] II. Selection of Random Access Resources and Mapping of Synchronization Signal and PBCH Block (SSB) to RO.

[0056] In NR, a cell can configure multiple Frequency Division Multiplex (FDM) Physical Random Access Channel transmission opportunities (ROs) at a single time-domain location for PRACH transmission. At any given time, the number of ROs that can perform FDM transmissions can be {1, 2, 4, 8}. For example... Figure 2 As shown, at any given moment, there are 8 RO resources distributed at different frequencies.

[0057] The random access preamble can only be transmitted on the time-domain resources (i.e., RO resources) configured by the PRACH configuration index parameter, and can only be transmitted on the frequency-domain resources configured by the prach-FDM parameter. The PRACH frequency-domain resource n RA ∈{0, 1, ..., M-1}, where M equals the higher-layer parameter prach-FDM. At initial access, the PRACH frequency domain resources n RA Starting with the lowest frequency RO resource within the initial active uplink bandwidth part, number them in ascending order; otherwise, use the PRACH frequency domain resource n. RA Number the resources in ascending order, starting with the lowest frequency RO resource within the active uplink bandwidth part. For example... Figure 2 As shown, RO resources are numbered sequentially from low to high frequency as RO#0 to RO#7.

[0058] In NR, there is a correlation between RO and the actual SSB transmitted:

[0059] A single SSB may be associated with multiple ROs, or multiple SSBs may be associated with a single RO (in which case, different SSBs correspond to different preamble codes). Typically, the base station can use different beams to transmit different SSBs. The corresponding UE transmits a 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 the strongest signal and transmits Msg1. Thus, the network-side equipment can determine the SSB selected by the UE based on the received preamble's RO / "RO and preamble combination" and transmit Msg2 on the corresponding downlink beam to ensure the quality of downlink signal reception.

[0060] by Figure 2For example, at any given time, there are 8 ROs in an FDM, and 4 SSBs are actually transmitted, namely SSB#0, SSB#1, SSB#2, and SSB#3. Each SSB is associated with 2 ROs. If the UE determines to send PRACH / Msg1 / Preamble on the RO corresponding to SSB#0, then the UE selects one RO from RO#0 and RO#1 to send PRACH.

[0061] by Figure 3 For example, at a given moment, the number of Original Front Ends (ROs) in an FDM is 2, and the actual number of Sub-Sessions (SSBs) transmitted is 8, namely SSB#0, SSB#1, ..., SSB#7. Each pair of SSBs is associated with one RO. When multiple SSBs share a single RO, the preamble sets associated with these multiple SSBs are different; that is, the same preamble cannot simultaneously belong to the preamble sets associated with different SSBs. Figure 3 Taking RO#0 as an example, it has 60 preambles associated with SSB. Among them, preambles with indices 0-29 are associated with SSB#0, and preambles with indices 30-59 are associated with SSB#1. It should be noted that... Figure 3 Each square in the diagram represents an RO, not an SSB, where the indicated SSB refers to which / which SSBs the RO is associated with.

[0062] Before sending PRACH, the UE first performs resource selection. First, based on the RSRP (Reference Signal Received Power) of the received beam or SSB, the UE selects an SSB with an RSRP higher than a threshold. If multiple SSBs have RSRPs higher than the threshold, the terminal can select any SSB with an RSRP higher than the threshold. If no SSB has an RSRP higher than the threshold, the UE selects an SSB based on implementation.

[0063] Based on network (NW) configuration, the UE obtains the mapping between SSBs and ROs. After selecting an SSB, the RO corresponding to the selected SSB is used as the RO for transmitting PRACH / Preamble. If the selected SSB is associated with multiple ROs, the terminal can choose one of the ROs to transmit PRACH / Preamble.

[0064] For example: in Figure 2 In the illustrated embodiment, assuming the UE selects SSB#1, the UE can choose between RO#2 and RO#3 for PRACH / Preamble transmission; Figure 3In the illustrated embodiment, if the UE selects SSB#1, the UE can select the nearest available RO (RO#0 or RO#4) associated with SSB#1 to perform PRACH / Preamble transmission.

[0065] In the selected RO, the UE selects a preamble from the preamble set associated with the selected SSB for PRACH transmission. For example... Figure 3 In this scenario, if an Original Region (RO) is associated with two Service Subsystems (SSBs), then the available preamble set associated with each SSB within an RO will be divided into two subsets, each corresponding to one SSB. The UE will select a preamble sequence from the subset corresponding to the chosen SSB for PRACH transmission.

[0066] The associations between SSBs and PRACH resources include the SSB-to-PRACH occasion mapping cycle, the SSB-to-PRACH occasion mapping association period, and the SSB-to-PRACH occasion association pattern period. The purpose of these periods is primarily to ensure that at least one random access attempt is completed within a predefined time period and that the mapping between PRACH resources and SSBs is repeated in a certain pattern. When PRACH is repeated, it is necessary to ensure that this pattern is not broken.

[0067] III. Handling methods when PRACH conflicts with other signals or Time Division Duplex (TDD) configurations.

[0068] 1) If, after an integer number of SS / PBCH block index to PRACH mapping cycles within an association period, a set of PRACH occasions or PRACH sequences is not mapped to an SS / PBCH block index (SSB index), then no SS / PBCH block index is mapped to a PRACH occasion or PRACH sequence. These PRACH resources will not be available for PRACH transmission.

[0069] 2) The associated pattern period consists of one or more associated periods and is determined such that the pattern between PRACH occasions and SS / PBCH block indexes repeats at most once every 160 milliseconds. PRACH occasions (if any) not associated with SS / PBCH block indexes after an integer number of associated periods are not used for PRACH transmission.

[0070] 3) A MsgA PUSCH occasion is valid if it does not overlap in time and frequency with any valid PRACH occasions associated with Type I or Type II random access procedures. This means that when PRACH and MsgA PUSCH resources overlap, PRACH is transmitted instead of MsgA PUSCH.

[0071] 4) For operation on a single carrier in unpaired spectrum (TDD), if the UE is configured by a higher layer to receive PDCCH, Physical downlink shared channel (PDSCH), Channel State Information Reference Signal (CSI-RS), or Downlink Positioning Reference Signal (DL-PRS) in a set of symbols in a slot, then if the UE does not detect a DCI format instructing the UE to send PUSCH, PUCCH, PRACH, or SRS in at least one symbol in this set of symbols, then the UE receives PDCCH, PDSCH, CSI-RS, or DL-PRS; otherwise, the UE does not receive PDCCH, PDSCH, CSI-RS, or DL-PRS.

[0072] 5) For operation on a single carrier in an unpaired spectrum, if the UE is configured by a higher layer to transmit a Sounding Reference Signal (SRS), Physical Uplink Control Channel (PUCCH), PUSCH, or PRACH in a set of symbols in a time slot, and the UE detects a DCI format instructing the UE to receive CSI-RS or PDSCH from a subset of that set of symbols, then:

[0073] If the UE does not have the capability of "partial cancellation", then if the time interval between the first symbol in the set (a set of symbols transmitting SRS, PUCCH, PUSCH, or PRACH) and the last symbol of the DCI format CORESET detected by the UE does not exceed T proc,2 If the UE does not expect to cancel the transmission of PUCCH, PUSCH, or PRACH in that set, then the UE cancels the PRACH transmission, or decides to cancel the actual duplicate transmission of PUCCH, PUSCH, or PUSCH according to the relevant protocol.

[0074] If the UE has the capability of "partial cancellation", then if the time interval between a portion of the symbols in the set (a set of symbols transmitting SRS, PUCCH, PUSCH, or PRACH) and the last symbol of the DCI format CORESET detected by the UE does not exceed T proc,2 If the UE does not expect to cancel the transmission of PUCCH, PUSCH, or PRACH on this part of the symbols, the UE cancels the PRACH transmission or decides to cancel the actual duplicate transmission of PUCCH, PUSCH, or PUSCH according to the relevant protocol.

[0075] It should be noted that, in the embodiments of this application, RACH Occasion (i.e., RO) and PRACH Occasion both refer to the time-frequency resources required to send a PRACH sequence, that is, both RACH Occasion and PRACH Occasion can be represented by RO.

[0076] The method for determining PRACH repeated transmission resources provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0077] like Figure 4 As shown in the figure, this application provides a method for determining PRACH retransmission resources, applied to a terminal, the method comprising:

[0078] Step 401: The terminal obtains resource configuration information for repeated transmission of the Physical Random Access Channel (PRACH), wherein the resource configuration information indicates the configuration resources for repeated PRACH transmission.

[0079] In this embodiment, the definition of PRACH repeated transmission is different from that of PRACH retransmission. In this embodiment of the application, PRACH repeated transmission refers to repeated transmission during each PRACH initial transmission or retransmission process. PRACH repeated transmission only occurs before the end of the Random Access Response Window (RAR window).

[0080] The resource configuration information for PRACH repetition transmission can be configured by the network-side device, meaning the network-side device configures resources for PRACH repetition transmission for the terminal. These configured resources refer to the resources configured by the network-side device for PRACH repetition transmission, and are not necessarily the actual transmission resources used by the terminal for PRACH repetition transmission. PRACH repetition resources refer to the PRACH resources used to send PRACH repetitions; PRACH resources that do not support PRACH repetitions refer to the PRACH resources used to send PRACH but not for repetition. PRACH resources can be PRACH time-frequency resources and / or PRACH sequences.

[0081] Step 402: The terminal determines whether the configuration resources are used for PRACH retransmission.

[0082] The terminal obtains the configuration resources configured for it by the network-side device based on the resource configuration information, and determines whether the configuration resources are actually used for PRACH repetitive transmission.

[0083] In an embodiment of this application, the terminal obtains configuration resources for PRACH retransmission and determines whether the configuration resources are actually used for PRACH retransmission, so that the terminal can use the configuration resources that can be actually used for PRACH retransmission to perform PRACH retransmission, thereby reducing random access latency.

[0084] As an optional embodiment, determining whether the configuration resource is used for PRACH retransmission includes at least one of the following:

[0085] (1) Determine whether the configuration resource is used for PRACH retransmission based on the validity of the configuration resource;

[0086] (2) Determine whether the configuration resource is used for PRACH retransmission based on the configuration information of the symbol where the configuration resource is located;

[0087] (3) Determine whether the configuration resource is used for PRACH repeated transmission based on the conflict between the configuration resource and other signal resources.

[0088] In this embodiment, the terminal can determine whether a configuration resource can actually be used for PRACH repetition transmission based on one or a combination of the following: the validity of the configuration resource, the configuration information of the symbol containing the configuration resource, and the conflict between the configuration resource and other signal resources. Optionally, when determining whether a configuration resource can actually be used for PRACH repetition transmission based on the validity of the configuration resource, the method may further include:

[0089] Determine the validity of the configuration resources; wherein the validity of the configuration resources is related to the first gap requirement and / or the time division multiplexing (TDD) uplink and downlink configuration;

[0090] The first gap requirement is the gap requirement between SSB transmission, the symbol set used for SSB transmission, and the symbol set used for PRACH transmission.

[0091] In this embodiment, when determining whether a configuration resource is actually used for repeated PRACH transmission based on its validity, the method for verifying the validity of the configuration resource can be the same as the method for verifying the validity of PRACH resources that are not used for repeated transmission in the prior art. That is, whether the configuration resource is valid depends on the gap requirements between SSB transmission, the symbol set used for SSB transmission and the symbol set used for RPACH transmission, and the cell-specific TDD uplink-downlink configuration.

[0092] Optionally, for resources that can send both PRACH repeat transmissions and PRACH non-repeating transmissions simultaneously, the validity verification rules for the configuration resources should be the same in both PRACH transmission cases. Therefore, the validity of the configuration resources in the embodiments of this application can be verified using the verification rules for PRACH non-repeating transmissions.

[0093] For example, the validity of the test can be verified by checking whether the test is valid for paired spectrum or additional uplink spectrum.

[0094] For unpaired spectrum:

[0095] If a common TDD uplink / downlink configuration (tdd-UL-DL-ConfigurationCommon) for the UE is not provided, and if the PRACH occasion in the PRACH slot does not precede the SS / PBCH block in the PRACH slot, and is at least N symbols after the last SS / PBCH block received... gap If there are 1 symbol, then the PRACH occasion in the PRACH slot is valid; among which, the existing protocol provides N gapFurthermore, if channelAccessMode=semistatic is provided, it will not overlap with a set of consecutive symbols before the start of the next channel occupancy time when the UE does not transmit.

[0096] If tdd-UL-DL-ConfigurationCommon is provided to the UE, then PRACH slot PRACH Hoccasion is valid in the following cases:

[0097] Within the UL symbol range; or,

[0098] Not preceding the SS / PBCH block in the PRACH slot, and at least N after the last downlink link symbol. gap There are at least N symbols, and at least N symbols after the last SS / PBCH block symbol. gap There are N symbols. Among them, the existing protocol provides N. gap Furthermore, if channelAccessMode=semistatic is provided, it will not overlap with a set of consecutive symbols before the start of the next channel occupancy time, during which no transmissions should exist;

[0099] The candidate SS / PBCH block indexes correspond to the SS / PBCH block indexes provided by SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon.

[0100] It should be noted that the method for determining the validity of configuration resources in this application embodiment is only an illustrative example. The validity of the configuration resources can also be determined according to other determination methods, which are not limited here.

[0101] The following specific examples illustrate the detailed implementation process of determining whether the configuration resources are actually used for PRACH retransmission using the three methods described above.

[0102] As an optional embodiment, determining whether the configuration resource is used for PRACH retransmission based on the validity of the configuration resource includes at least one of the following:

[0103] 1) Determine whether the first RO is used for PRACH retransmission based on the validity of the first RO in the configuration resources.

[0104] The configuration resources include RO resources configured for PRACH repeat transmission. The first RO is an RO used only for PRACH repeat transmission, and the first RO may include one or more ROs. This embodiment determines whether an RO can actually be used for PRACH repeat transmission based on the validity of the additionally configured RO used only for PRACH repeat transmission.

[0105] Optionally, determining whether the first RO is used for PRACH retransmission based on the validity of the first RO in the configuration resources includes: if the first target RO in the first RO is invalid, then determining that the first target RO is not used for PRACH retransmission.

[0106] In this embodiment, the first target RO can refer to one or more ROs. For ROs used only for PRACH retransmission, if the RO is invalid, it is discarded and cannot be used for PRACH retransmission. When a first target RO is invalidated and discarded, it may or may not be counted. These will be explained below.

[0107] Optionally, the method further includes: delaying the first target RO by one RO level in the time domain to obtain a second target RO, the second target RO being used for PRACH retransmission.

[0108] In this scenario, when the first target RO is invalid, it is not counted. The invalid first target RO can be postponed, and a new valid second target RO can be obtained, thus ensuring the number of valid PRACH repetitions. For example... Figure 5 As shown, the configuration resources include a common RO and a first RO. The common RO is used for the first PRACH repetition. The first RO includes RO0, RO1, RO2, and RO3 for PRACH repetition, with two of each of RO0, RO1, RO2, and RO3, allowing for two PRACH repetitions each. One RO0 and one RO1 are invalid due to overlap with SSB transmissions (i.e.,...). Figure 5 If the 1 RO0 and 1 RO1 on the right side are the first target ROs, then the invalid RO0 and RO1 will be shifted to the next RO, thereby ensuring that there are two additional ROs for the transmission of PRACH repetitions and ensuring that the number of configured PRACH repetitions remains unchanged.

[0109] Optionally, the first target RO is included in the number of ROs repeatedly transmitted by the PRACH.

[0110] In this embodiment, when a first target RO is invalid, it is discarded, but it is still counted. For a first RO configured solely for PRACH repeat transmission, as long as a common RO is valid (or a common RO is valid but not actually used for PRACH repeat transmission), the first RO will be mapped to the common RO. If one or more of the first ROs are invalid, the invalid first RO is discarded, but it will still be counted. The common RO is a RO with a common configuration used for both PRACH repeat transmission and PRACH non-repeating transmission (also referred to as a shared RO).

[0111] For example Figure 6 As shown, the configuration resources include a common RO and a first RO. The common RO is used for the first PRACH repetition. The first RO includes RO0, RO1, RO2, and RO3 for PRACH repetition, with two of each of RO0, RO1, RO2, and RO3, allowing for two PRACH repetitions each. One RO0 and one RO1 are invalid due to overlap with SSB transmissions (i.e.,...). Figure 6 If the first target RO is one RO0 and one RO1 on the right side of the middle, and is discarded without being followed up, then the PRACH transmission in RO0 and RO1 can only be repeated twice (including the first repetition on the left), while the PRACH repetition transmission in RO2 and RO3 can be repeated three times (including the first repetition on the left) because all ROs are valid.

[0112] It should be noted that when the configuration resources include both a common RO and a first RO, the common RO is associated with the corresponding first RO. For example... Figure 5 and Figure 6 As shown, RO0 in the common RO on the left is associated with the two RO0s in the first RO on the right, and RO1 in the common RO on the left is associated with the two RO1s on the right. Other ROs follow the same pattern, which will not be elaborated here.

[0113] 2) Based on the validity of the common ROs in the configuration resources, determine whether the first RO in the configuration resources is used for PRACH repeat transmission; wherein, the common RO is the RO in the common configuration used by the PRACH repeat transmission and the PRACH non-repeating transmission; the first RO is the RO used only for PRACH repeat transmission.

[0114] This embodiment determines whether the first RO associated with the public RO is actually used for PRACH retransmission by determining the validity of the public RO.

[0115] Optionally, determining whether a first RO in the configuration resource is used for PRACH retransmission based on the validity of the public RO in the configuration resource includes at least one of the following:

[0116] a: If the first common RO in the common RO is invalid, then it is determined that the first RO associated with the first common RO is not used for PRACH retransmission.

[0117] In this embodiment, the first common RO can refer to one or more ROs among the common ROs. If the first common RO is invalid, the first RO associated with the first common RO is discarded and not used for PRACH retransmission.

[0118] For example Figure 7 As shown, the configuration resources include common ROs and first ROs. The common ROs are used for the first PRACH repetition. The first ROs include RO0, RO1, RO2, and RO3 for PRACH repetition, and there are two of each of RO0, RO1, RO2, and RO3, which can each perform two PRACH repetitions. If two common ROs (RO2 and RO3 on the left) conflict with the PDSCH scheduled by dynamic grant in the downlink, the additional first ROs associated with these two common ROs (the two RO2s and two RO3s on the right) are discarded without actual transmission and no actual PRACH repetition transmission is performed.

[0119] b: If the first common RO in the common RO is valid but not used for PRACH retransmission, then it is determined that the first RO associated with the first common RO is not used for PRACH retransmission.

[0120] In this embodiment, some common remote routes (ROs) in the configuration resources may be valid, but due to conflicts with other resources or being configured as unavailable, these valid common ROs are not used for actual PRACH retransmissions. Therefore, the first RO associated with this common RO is not used for actual PRACH retransmissions. Specific implementation examples include... Figure 7 As shown, it will not be elaborated upon here.

[0121] c: If the first common RO in the common RO is invalid, then the first RO associated with the first common RO is determined to be used for PRACH retransmission.

[0122] In this embodiment, if the first common RO is invalid, the first RO associated with the first common RO is still used for PRACH retransmission. For example Figure 8As shown, the configuration resources include common ROs and first ROs. The common ROs are used for the first PRACH repetition. The first ROs include RO0, RO1, RO2, and RO3 for PRACH repetition, and there are two of each of RO0, RO1, RO2, and RO3, which can each be used for two PRACH repetitions. If two common ROs (RO2 and RO3 on the left) conflict with the PDSCH scheduled by dynamic grant in the downlink, the additional first ROs associated with these two common ROs (the two RO2s and two RO3s on the right) are still used for PRACH retransmission, i.e., they are not discarded.

[0123] d: If the first common RO in the common RO is valid but not used for PRACH retransmission, then the first RO associated with the first common RO is determined to be used for PRACH retransmission.

[0124] In this embodiment, if the first public RO is valid but not actually used for PRACH retransmission, the first RO associated with the first public RO is still used for PRACH retransmission, for example... Figure 8 As shown, it will not be elaborated upon here.

[0125] This embodiment determines whether the configured resources are used for actual PRACH repetition transmission based on the validity of the first RO and / or common RO. For example, when a PRACH repetition conflicts with other resources, some PRACH repetitions can be discarded to ensure that other high-priority signals can be sent or received on time; or, in order to ensure the number of actual PRACH repetitions, the PRACH occasions used for repetitions are postponed, skipping invalid ROs or ROs that do not actually send PRACHs; or, even if the resources for the first repetition are invalid or PRACHs are not actually sent, the PRACH resources for subsequent repetitions can still continue to send the remaining PRACH repetitions, reducing the latency of random access.

[0126] The following describes the specific implementation process of determining whether the configuration resource is used for PRACH retransmission based on the configuration information of the symbol where the configuration resource is located.

[0127] As an optional embodiment, determining whether the configuration resource is used for PRACH retransmission based on the configuration information of the symbol where the configuration resource is located includes at least one of the following:

[0128] A) If the symbol containing the third target RO in the first RO is configured as a flexible symbol in the common TDD uplink / downlink configuration information (tdd-UL-DL-configurationCommon) and as a downlink in the dedicated TDD uplink / downlink configuration information (tdd-UL-DL-ConfigurationDedicated), then it is determined that the third target RO is not used for PRACH repetition transmission; wherein, the first RO is the RO in the configuration resource that is only used for PRACH repetition transmission.

[0129] In this embodiment, the third target RO is one or more of the first ROs used only for PRACH repetition. If the symbol of an additional RO used for sending PRACH repetition (e.g., the third target RO among the first ROs) is configured as a flexible symbol in tdd-UL-DL-configurationCommon and as DL in tdd-UL-DL-ConfigurationDedicated, then the third target RO is not used for PRACH repetition.

[0130] B) If the symbol containing the third target RO in the first RO is configured as a flexible symbol in the public TDD uplink and downlink configuration information and as a downlink in the DCI format, then it is determined that the third target RO is not used for PRACH retransmission.

[0131] In this embodiment, the DCI format can be DCI format2-0. If the symbol of the additional RO used to send PRACH repetition (e.g., the third target RO in the first RO) is configured as flexible in tdd-UL-DL-configurationCommon and indicated as DL in DCI format2-0, the RO is not used for PRACH repetition transmission.

[0132] C) If the symbol containing the third target RO in the first RO is configured as a flexible symbol in the first configuration information, and the terminal receives downlink signals on the symbol, then it is determined that the third target RO is not used for PRACH retransmission. The first configuration information includes at least one of the following: common TDD uplink / downlink configuration information (tdd-UL-DL-configurationCommon), dedicated TDD uplink / downlink configuration information (tdd-UL-DL-ConfigurationDedicated), and DCI format;

[0133] In this embodiment, the downlink signals are, for example, PDCCH and PDSCH, and the DCI format is, for example, DCI format2-0. That is, if the symbol containing the additionally configured RO for transmitting PRACH repetition (e.g., the third target RO in the first RO) is configured as flexible in tdd-UL-DL-configurationCommon and / or tdd-UL-DL-ConfigurationDedicated and / or DCI format2-0, but the downlink signal is received on the above symbol (i.e., the symbol containing the RO), then the third target RO is not used for PRACH repetition transmission.

[0134] This embodiment determines whether the configuration information is actually used for PRACH repetitive transmission based on the configuration information of the symbol where the configuration resource is located, and provides a scheme for the use of transmission resources by the UE under different configurations, which can guarantee the configuration resources and reduce the latency of random access.

[0135] The following describes the process of determining whether the configuration resource is actually used for PRACH repetitive transmission based on the conflict between the configuration resource and other signal resources.

[0136] As an optional embodiment, determining whether the configuration resource is used for repeated PRACH transmission based on conflicts between the configuration resource and other signal resources includes at least one of the following:

[0137] i) If the fourth target RO in the first RO at least partially overlaps with the transmission resources of the first uplink information in the random access process, then the fourth target RO is determined not to be used for PRACH repetition transmission; the first RO is the RO in the configuration resources that is only used for PRACH repetition transmission.

[0138] The fourth target RO can be one or more of the first ROs used solely for PRACH repetition transmission. The first uplink information can be the MsgA of the random access procedure. That is, for an additional RO configured for sending PRACH repetition (e.g., the fourth target RO), if the RO at least partially overlaps with the MsgA PUSCH transmission, then the RO is not used for PRACH repetition transmission.

[0139] In this embodiment, since a UE that does not support PRACH duplication may not read and recognize the additional ROs configured for sending PRACH duplication, this means that MsgA PUSCH must take priority over the individual ROs configured for PRACH duplication, i.e., MsgAPUSCH takes priority over the transmission of the fourth target RO. On the other hand, when there is overlap between the resources of the fourth target RO and MsgA PUSCH, discarding part of the PRACH duplication to protect MsgA PUSCH may not cause PRACH reception failure, but can ensure the timely transmission of MsgA PUSCH.

[0140] ii) If the higher-layer signaling instructs the terminal to receive downlink signals in a set of symbols within the time slot, the DCI format information instructs the terminal to perform PRACH retransmission in the fourth target RO, and the fourth target RO overlaps with at least one symbol in the symbol set where the time slot is located, then it is determined that the fourth target RO is not used for PRACH retransmission.

[0141] In this embodiment, for operation on a single carrier in an unpaired spectrum, if the UE receives downlink signals such as PDCCH, PDSCH, CSI-RS, or DL ​​PRS in a set of symbols within a time slot configured by a higher layer, the UE receives downlink signals such as PDCCH, PDSCH, CSI-RS, or DL ​​PRS even if the UE detects a DCI format that instructs the UE to transmit PRACH repetition in an additional configured RO (e.g., a fourth target RO), and the additional configured RO (e.g., the fourth target RO) overlaps with at least one symbol of the symbol set of the time slot, the UE does not perform PRACH repetition transmission on the fourth target RO, but instead receives downlink signals on the symbols of the time slot.

[0142] In this embodiment, downlink signal reception has a higher priority than PRACH retransmission, and the relevant protocols can be modified accordingly, for example:

[0143] For operation on a single carrier in an unpaired spectrum, if the UE is configured by a higher layer to receive downlink signals such as PDCCH, PDSCH, CSI-RS, or DL-PRS in a set of symbols within a time slot, and if the UE does not detect a DCI format instructing the UE to transmit non-repeating PUSCH, PUCCH, PRACH, or SRS in at least one symbol of the symbol set of the time slot, then the UE receives PDCCH, PDSCH, CSI-RS, or DL-PRS; otherwise, if the UE does not detect a DCI format instructing the UE to transmit repeated PRACH, then the UE does not receive downlink signals such as PDCCH, PDSCH, CSI-RS, or DL-PRS in the symbol set of the time slot. (For operation on a single carrier in unpaired spectrum, if a UE is configured by higher layers to receive a PDCCH, or a PDSCH, or a CSI-RS, or a DL PRS in a set of symbols of a slot, the UE receives the PDCCH, the PDSCH, the CSI-RS, or the DL PRS if the UE does not detect a DCI format that indicates to the UE to transmit a PUSCH, aPUCCH, aPRACH without repetition, or a SRS in at least one symbol of the set of symbols of the slot; otherwise and if the UE does not detect a DCI format that indicates to the UE to transmit a PRACH with repetition, the UE does not receive the PDCCH, or the PDSCH, or the CSI-RS, or the DL PRS in the set of symbols of the slot).

[0144] iii) If higher-layer signaling instructs the terminal to perform PRACH retransmission on a target symbol on the fourth target RO, and DCI format information instructs the terminal to receive downlink signals in a subset of symbols of the target symbol, then the fourth target RO is not used for PRACH retransmission.

[0145] In this embodiment, for operation on a single carrier in an unpaired spectrum, if the UE is configured by a higher layer to transmit PRACH repetitions in a set of symbols corresponding to a certain time slot on an additionally configured RO (e.g., a fourth target RO), and the UE detects a DCI format indicating that the UE will receive downlink signals (e.g., CSI-RS or PDSCH) from a subset of symbols in that set of symbols, then the UE will not perform PRACH repetition transmission on the fourth target RO, but will instead receive downlink signals from the subset of the target symbols. Optionally, the fourth target RO may not be used for PRACH repetition transmission, but the corresponding PRACH repetitions may still be counted.

[0146] This embodiment determines whether the configuration resource is used for PRACH repetition based on the conflict between the configuration resource and other signal resources. When a PRACH repetition conflicts with other resources, some PRACH repetitions can be discarded to ensure that other high-priority signals can be sent or received on time, thereby reducing the latency of random access.

[0147] As an optional embodiment, the method further includes: determining the power allocation priority for the repeated PRACH transmissions;

[0148] The power allocation priority includes at least one of the following:

[0149] 1) The power allocation priority of PRACH that is repeatedly transmitted is lower than that of PRACH that is not repeatedly transmitted on the primary cell (PCell).

[0150] In this embodiment, based on this implementation, the repeatedly transmitted PRACH signals will be allocated power with lower priority compared to other uplink signals transmitted simultaneously during carrier aggregation. The relevant protocol can be modified accordingly, for example:

[0151] The total UE transmit power in a time slot symbol is defined as the sum of the linear values ​​of the UE transmit powers for PUSCH, PUCCH, PRACH, and SRS in the time slot symbol.

[0152] PRACH transmission without repetition on the Pcell;

[0153] PUCCH or PUSCH transmissions with a higher priority index (according to clause 9);

[0154] For PUCCH or PUSCH transmissions with the same priority index;

[0155] PUCCH transmission with HARQ-ACK information, and / or SR, and / or LRR, or PUSCH transmission with HARQ-ACK information.

[0156] PUCCH transmission with CSI or PUSCH transmission with CSI;

[0157] PUSCH transmission without HARQ-ACK information or CSI, for Type-2 random access procedure, PUSCH transmission on the Pcell.

[0158] SRS transmission, with aperiodic SRS having higher priority than semi-persistent and / or periodic SRS, or PRACH transmission on aserving cell other than the Pcell or PRACH repetition transmissions.

[0159] 2) The power allocation priority for PRACHs that are repeatedly transmitted is the same as the power allocation priority for PRACHs that are not repeatedly transmitted on the primary cell.

[0160] In this embodiment, repeated PRACH signals are allocated power with higher priority than other uplink signals transmitted simultaneously during carrier aggregation. Related protocols can be modified accordingly, for example:

[0161] The total UE transmit power in a time slot symbol is defined as the sum of the linear values ​​of the UE transmit powers for PUSCH, PUCCH, PRACH, and SRS in the time slot symbol.

[0162] PRACH transmission on the Pcell or PRACH repetition transmission;

[0163] PUCCH or PUSCH transmissions with a higher priority index (according to clause 9);

[0164] For PUCCH or PUSCH transmissions with the same priority index;

[0165] PUCCH transmission with HARQ-ACK information, and / or SR, and / or LRR, or PUSCH transmission with HARQ-ACK information.

[0166] PUCCH transmission with CSI or PUSCH transmission with CSI;

[0167] PUSCH transmission without HARQ-ACK information or CSI, for Type-2 random access procedure, PUSCH transmission on the Pcell.

[0168] SRS transmission, with aperiodic SRS having higher priority than semi-persistent and / or periodic SRS, or PRACH transmission on aserving cell other than the Pcell.

[0169] 3) If the PRACH is repeatedly transmitted on the primary cell, the power allocation priority of the repeatedly transmitted PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on the primary cell.

[0170] 4) If the PRACH is repeatedly transmitted on a non-primary cell, the power allocation priority of the repeatedly transmitted PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on a non-primary cell.

[0171] 5) The power allocation priority for PRACHs that are repeatedly transmitted is the same as the power allocation priority for PRACHs that are not repeatedly transmitted on non-primary cells.

[0172] This embodiment ensures that high-priority signals can be sent or received on time by defining the power allocation priority of the PRACH repeated transmission, thus guaranteeing normal signal transmission.

[0173] As an optional embodiment, the PRACH retransmission is completed within the first duration;

[0174] The first duration includes at least one of the following:

[0175] The mapping period from SSB to RO is M times the time.

[0176] The mapping association period from SSB to RO is N times the time;

[0177] The correlation pattern period from SSB to RO is L times the time.

[0178] The time value corresponding to the random access response window; the maximum value of the random access response window can be 10ms;

[0179] The associated mode period of the RO for repeated SSB to PRACH transmissions; the associated mode period of the RO for repeated SSB to PRACH transmissions may be additionally configured for repeated PRACH transmissions.

[0180] Where M, N, and L are positive integers. The specific values ​​of M, N, and L can be defined by the protocol or configured by system messages.

[0181] In this embodiment, an additional RO association pattern period for repeated SSB-PRACH transmissions is defined, which may include one or more SSB-RO association pattern periods, such that the pattern of repeated RO and SSB transmissions in PRACH can be repeated at most every predetermined time period (e.g., every 640ms). Optionally, the predetermined time period may be a positive integer multiple of the RO association pattern period of SSB to (existing, single-transmission) PRACH.

[0182] For example Figure 9As shown, a RO configured with 4 repeated transmissions has its first 3 repeated transmissions occurring within the SSB-to-RO association mode cycle. However, if the 4th repeated transmission occurs within the next SSB-to-RO association mode cycle, then the 4th repeated transmission will be discarded. It should be noted that... Figure 9 The RO in the PRACH repeat transmission configuration refers to the RO of the PRACH repeat transmission configuration. It can be a common RO or the first RO, and there is no limitation here.

[0183] Optionally, if the configured PRACH repeat transmission is not completed within the first duration, the remaining PRACH repeat transmissions can be discarded entirely, or partially transmitted before the end of the first duration.

[0184] In this embodiment, the terminal obtains configuration resources for PRACH repetition and determines whether the configuration resources are actually used for PRACH repetition. It provides solutions for situations where configuration resources are invalid or conflict with other signal resources, thereby reducing random access latency. For example, when a PRACH repetition conflicts with other resources, some PRACH repetitions can be discarded or their transmission power not increased to ensure that other high-priority signals can be sent or received on time; or, to ensure the actual number of PRACH repetitions, the PRACH Hoccasion used for repetitions needs to be postponed, skipping invalid or non-transmitted PRACH repetitions; or, even if the resources for the first repetition are invalid or the PRACH is not actually transmitted, the PRACH resources for subsequent repetitions can still be used to transmit the remaining PRACH repetitions, reducing random access latency.

[0185] like Figure 10 As shown in the embodiments of this application, a method for determining PRACH retransmission resources is also provided, applied to a network-side device, including:

[0186] Step 101: The network-side device determines the configuration resources for PRACH retransmission;

[0187] Step 102: The network-side device determines whether the configuration resources are used to receive repetitive PRACH transmissions.

[0188] In this embodiment, the definition of PRACH repeated transmission is different from that of PRACH retransmission. In this embodiment, PRACH repeated transmission refers to repeated transmission during each PRACH initial transmission or retransmission process. PRACH repeated transmission only occurs before the end of the random access response window.

[0189] The network-side device configures resources for PRACH repetition transmission for the terminal. These configured resources refer to the resources configured by the network-side device for PRACH repetition transmission, and are not necessarily the actual transmission resources used by the terminal for PRACH repetition transmission. PRACH repetition resources refer to the PRACH resources used for sending PRACH repetitions; PRACH resources that do not support PRACH repetitions refer to the PRACH resources used for sending PRACH but not for repetition. PRACH resources can be PRACH time-frequency resources and / or PRACH sequences.

[0190] The terminal determines whether the configuration resource is actually used for PRACH retransmission and performs PRACH retransmission on the configuration resource that is actually being transmitted; then the network-side device also needs to determine whether the configuration resource is actually used for PRACH retransmission based on the corresponding rules of the terminal, and receive the retransmitted PRACH on the configuration resource that is actually being transmitted.

[0191] In embodiments of this application, the network-side device configures resources for PRACH retransmission and determines whether the configured resources are actually used for PRACH retransmission, so that the network-side device can receive retransmitted PRACH on the configured resources actually used for PRACH retransmission, thereby reducing random access latency.

[0192] Optionally, the method further includes: sending resource configuration information for repeated PRACH transmissions to the terminal, the resource configuration information indicating the configured resources.

[0193] In this embodiment, after the network-side device configures the configuration resources for PRACH repetitive transmission, it can send the configuration resources to the terminal through resource configuration information, so that the terminal can determine whether the configuration resources are actually used for PRACH repetitive transmission, thereby determining the solution when the configuration resources are invalid or conflict with other signal resources, and reducing random access latency.

[0194] Optionally, determining whether the configuration resource is used to receive repetitive PRACH transmissions includes at least one of the following:

[0195] (1) Determine whether the configuration resource is used to receive repeatedly transmitted PRACH based on the validity of the configuration resource;

[0196] (2) Determine whether the configuration resource is used to receive repetitive PRACH based on the configuration information of the symbol where the configuration resource is located;

[0197] (3) Determine whether the configuration resource is used to receive repeated PRACH transmissions based on the conflict between the configuration resource and other signal resources.

[0198] In this embodiment, the terminal can determine whether a configuration resource can actually be used for PRACH retransmission based on one or a combination of the following: the validity of the configuration resource, the configuration information of the symbol containing the configuration resource, and the conflict between the configuration resource and other signal resources. Optionally, when determining whether the configuration resource is used to receive retransmitted PRACH based on the validity of the configuration resource, the method may further include:

[0199] Determine the validity of the configuration resources; wherein the validity of the configuration resources is related to the first gap requirement and / or the time division multiplexing (TDD) uplink and downlink configuration; the first gap requirement is the gap requirement among SSB transmission, the symbol set used for SSB transmission, and the symbol set used for PRACH transmission.

[0200] In this embodiment, when determining whether to receive duplicate PRACH transmissions based on the validity of configuration resources, the method for verifying the validity of configuration resources can be the same as the method for verifying the validity of PRACH resources that are not duplicated in the prior art. That is, whether the configuration resources are valid depends on the SSB transmission, the gap requirement between the symbol set used for SSB transmission and the symbol set used for RPACH transmission, and the cell-specific TDD uplink-downlink configuration.

[0201] Optionally, for resources that can simultaneously send both repeated and non-repeated PRACH transmissions of a common configuration, the validity verification rules for the configuration resource should be the same in both PRACH transmission scenarios. Therefore, the validity of the configuration resource in this embodiment can be verified using the verification rules for non-repeated PRACH transmissions. The method for determining the validity of the configuration resource is not limited here.

[0202] The following specific embodiments illustrate the detailed implementation process of determining whether the configuration resources are used to receive repetitive PRACH transmissions using the three methods described above.

[0203] As an optional embodiment, determining whether the configuration resource is used to receive repetitive PRACH transmissions based on the validity of the configuration resource includes at least one of the following:

[0204] 1) Determine whether the configuration resource is used to receive repetitive PRACH transmissions based on the validity of the first RO in the configuration resource.

[0205] The configuration resources include RO resources configured for PRACH retransmission. The first RO is an RO used only for PRACH retransmission, and the first RO may include one or more ROs. This embodiment determines whether an additional RO configured only for PRACH retransmission can actually be used for PRACH retransmission based on the validity of the RO, that is, whether the network-side device needs to receive retransmitted PRACH on the first RO.

[0206] Optionally, determining whether the configuration resource is used to receive repeated PRACH transmissions based on the validity of the first RO in the configuration resource includes: if the first target RO in the first RO is invalid, then determining that the first target RO is not used to receive repeated PRACH transmissions. The first RO is an RO used only for repeated PRACH transmissions.

[0207] In this embodiment, the first target RO can refer to one or more ROs. For ROs used only for PRACH retransmission, if the RO is invalid, it is discarded and cannot be used for PRACH retransmission. When a first target RO is invalidated and discarded, it may or may not be counted. These will be explained below.

[0208] Optionally, the method further includes: determining the time-domain position of a second target RO, wherein the second target RO is obtained by delaying the first target RO by one RO level in the time-domain position, and the second target RO is used to receive repeatedly transmitted PRACH.

[0209] In this scenario, when the first target RO is invalid, it is not counted. The invalid first target RO can be postponed, and a new valid second target RO can be obtained, thus ensuring the number of valid PRACH repetitions. For example... Figure 5 As shown, it will not be elaborated upon here.

[0210] Optionally, the first target RO is included in the number of ROs used in the PRACH retransmission. In this embodiment, when the first target RO is invalid, it is discarded, but it is still counted. For a first RO configured solely for PRACH retransmission, as long as the common RO is valid (or the common RO is valid but not actually used for PRACH retransmission), the first RO will be mapped to the common RO. If one or more of the first ROs are invalid, the invalid first ROs are discarded, but they are still counted. Figure 6 As shown, it will not be elaborated upon here.

[0211] 2) Determine whether the configuration resource is used to receive repetitive PRACH transmissions based on the validity of the common RO in the configuration resource; wherein, the common RO is the RO of the common configuration used for both repetitive PRACH transmissions and non-repetitive PRACH transmissions.

[0212] This embodiment determines whether a first RO associated with a public RO is used to receive repetitive transmissions by determining the validity of the public RO.

[0213] Optionally, determining whether the configuration resource is used to receive recurring PRACH transmissions based on the validity of the public RO in the configuration resource includes at least one of the following:

[0214] a: If the first common RO in the common RO is invalid, then it is determined that the first RO associated with the first common RO is not used to receive repetitive PRACH transmissions.

[0215] In this embodiment, the first common RO can refer to one or more ROs among the common ROs. If the first common RO is invalid, the first RO associated with the first common RO is discarded and not used for PRACH retransmission. Therefore, the network-side device does not need to receive retransmitted PRACH in the first RO associated with the first common RO.

[0216] b: If the first common RO in the common RO is valid but not used for PRACH retransmission, then it is determined that the first RO associated with the first common RO is not used to receive retransmission PRACH.

[0217] In this embodiment, some public ROs in the configuration resources may be valid, but due to conflicts with other resources or being configured as unavailable, the valid public RO is not used for actual PRACH retransmission. Therefore, the first RO associated with the public RO is not used for actual PRACH retransmission, and the first RO associated with the first public RO is not used to receive retransmitted PRACH.

[0218] c: If the first common RO in the common RO is invalid, then the first RO associated with the first common RO is determined to be used to receive repeated PRACH transmissions.

[0219] In this embodiment, if the first public RO is invalid, the first RO associated with the first public RO is still used for PRACH retransmission, and the first RO associated with the first public RO is still used to receive retransmitted PRACH.

[0220] d: If the first public RO in the public RO is valid but not used for PRACH retransmission, then the first RO associated with the first public RO is determined to be used to receive retransmission PRACH.

[0221] In this embodiment, if the first public RO is valid but not actually used for PRACH retransmission, the first RO associated with the first public RO is still used for PRACH retransmission, and the first RO associated with the first public RO is still used to receive retransmitted PRACH.

[0222] This embodiment determines whether the configured resources are used for actual PRACH repetition transmission based on the validity of the first RO and / or common RO. For example, when a PRACH repetition conflicts with other resources, some PRACH repetitions can be discarded to ensure that other high-priority signals can be sent or received on time; or, in order to ensure the number of actual PRACH repetitions, the PRACH occasions used for repetitions are postponed, skipping invalid ROs or ROs that do not actually send PRACHs; or, even if the resources for the first repetition are invalid or PRACHs are not actually sent, the PRACH resources for subsequent repetitions can still continue to send the remaining PRACH repetitions, reducing the latency of random access.

[0223] The following describes the specific implementation process of determining whether the configuration resource is used to receive repeatedly transmitted PRACH based on the configuration information of the symbol where the configuration resource is located.

[0224] As an optional embodiment, determining whether the configuration resource is used to receive repeatedly transmitted PRACH based on the configuration information of the symbol where the configuration resource is located includes at least one of the following:

[0225] A) If the symbol containing the third target RO in the first RO is configured as a flexible symbol in the public TDD uplink / downlink configuration information and as a downlink in the dedicated TDD uplink / downlink configuration information, then it is determined that the third target RO is not used to receive repetitive PRACH transmissions. Here, the first RO is the RO in the configuration resource that is only used for repetitive PRACH transmissions.

[0226] In this embodiment, the third target RO is one or more of the first ROs used only for PRACH repetition. If the symbol of the additional RO used for sending PRACH repetition (e.g., the third target RO among the first ROs) is configured as a flexible symbol in tdd-UL-DL-configurationCommon and as DL in tdd-UL-DL-ConfigurationDedicated, then the third target RO is not used for PRACH repetition, and the network-side device receives the repetitive PRACH on the third target RO.

[0227] B) If the symbol containing the third target RO in the first RO is configured as a flexible symbol in the public TDD uplink and downlink configuration information and as a downlink in the DCI format, then it is determined that the third target RO is not used to receive repetitive PRACH transmissions.

[0228] In this embodiment, the DCI format can be DCI format2-0. If the symbol of the additionally configured RO used to send PRACH repetition (e.g., the third target RO in the first RO) is configured as flexible in tdd-UL-DL-configurationCommon and indicated as DL in DCI format2-0, and the third target RO is not used for PRACH repetition, then the third target RO is not used to receive repetitive PRACH transmissions.

[0229] C) If the symbol containing the third target RO in the first RO is configured as a flexible symbol in the first configuration information, and the terminal receives downlink signals on the symbol, then it is determined that the third target RO is not used to receive repetitive PRACH transmissions; the first configuration information includes at least one of: public TDD uplink / downlink configuration information, dedicated TDD uplink / downlink configuration information, and DCI format; wherein, the first RO is an RO in the configuration resources that is only used for repetitive PRACH transmissions.

[0230] In this embodiment, the downlink signals are, for example, PDCCH and PDSCH, and the DCI format is, for example, DCI format2-0. That is, if the symbol containing the additionally configured RO for transmitting PRACH repetition (e.g., the third target RO in the first RO) is configured as flexible in tdd-UL-DL-configurationCommon and / or tdd-UL-DL-ConfigurationDedicated and / or DCI format2-0, but the downlink signal is received on the above symbol (i.e., the symbol containing the RO), then the third target RO is not used for PRACH repetition transmission, and the third target RO is not used to receive repetitive PRACH transmissions.

[0231] This embodiment determines whether the configuration information is actually used for PRACH repetitive transmission based on the configuration information of the symbol where the configuration resource is located, and provides a scheme for the use of transmission resources by the UE under different configurations, which can guarantee the configuration resources and reduce the latency of random access.

[0232] The following describes the process of determining whether the configuration resource is actually used for PRACH repetitive transmission based on the conflict between the configuration resource and other signal resources.

[0233] As an optional embodiment, determining whether the configuration resource is used to receive repeatedly transmitted PRACH based on conflicts between the configuration resource and other signal resources includes:

[0234] If the fourth target RO in the first RO at least partially overlaps with the transmission resources of the first uplink information in the random access process, then it is determined that the fourth target RO is not used to receive retransmitted PRACH.

[0235] The fourth target RO can be one or more ROs used solely for PRACH retransmission. The first uplink information can be the MsgA of the random access procedure. That is, for an additional RO configured for sending PRACH retransmissions (e.g., the fourth target RO), if the RO at least partially overlaps with the MsgA PUSCH transmission, then the RO is not used for PRACH retransmission, and therefore the RO is not used for receiving retransmitted PRACH.

[0236] In this embodiment, since a UE that does not support PRACH duplication may not read and recognize the additional ROs configured for sending PRACH duplication, this means that MsgA PUSCH must take priority over the individual ROs configured for PRACH duplication, i.e., MsgAPUSCH takes priority over the transmission of the fourth target RO. On the other hand, when there is overlap between the resources of the fourth target RO and MsgA PUSCH, discarding part of the PRACH duplication to protect MsgA PUSCH may not cause PRACH reception failure, but can ensure the timely transmission of MsgA PUSCH.

[0237] Optionally, if higher-layer signaling instructs the terminal to receive downlink signals in a set of symbols within a time slot, and DCI format information instructs the terminal to perform PRACH retransmission in a fourth target RO, and the fourth target RO overlaps with at least one symbol in the symbol set containing the time slot, then the fourth target RO is not used for PRACH retransmission. If the higher-layer signaling notifies the network-side device of the instruction information for the terminal, for example, notifying the network-side device that the terminal receives downlink signals within the symbol, then the network-side device, in conjunction with the DCI format information, can determine that the fourth target RO is not used to receive retransmitted PRACH.

[0238] Optionally, if higher-layer signaling instructs the terminal to perform PRACH retransmission on a target symbol on the fourth target RO, and DCI format information instructs the terminal to receive downlink signals in a subset of symbols of the target symbol, then the fourth target RO is not used for PRACH retransmission. If the higher-layer signaling notifies the network-side device of the instruction information for the terminal, for example, notifying the network-side device that the terminal performs PRACH retransmission on a target symbol on the fourth target RO, then the network-side device, in conjunction with the DCI format information, can determine that the fourth target RO is not used to receive retransmitted PRACH.

[0239] This embodiment determines whether the configuration resource is used for PRACH repetition based on the conflict between the configuration resource and other signal resources. When a PRACH repetition conflicts with other resources, some PRACH repetitions can be discarded to ensure that other high-priority signals can be sent or received on time, thereby reducing the latency of random access.

[0240] Optionally, the network-side device may also determine the power allocation priority for PRACH repetitive transmissions, the power allocation priority including at least one of the following:

[0241] 1) The power allocation priority of PRACH that is repeatedly transmitted is lower than that of PRACH that is not repeatedly transmitted on the primary cell (PCell).

[0242] 2) The power allocation priority for PRACHs that are repeatedly transmitted is the same as the power allocation priority for PRACHs that are not repeatedly transmitted on the primary cell.

[0243] 3) If the PRACH is repeatedly transmitted on the primary cell, the power allocation priority of the repeatedly transmitted PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on the primary cell.

[0244] 4) If the PRACH is repeatedly transmitted on a non-primary cell, the power allocation priority of the repeatedly transmitted PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on a non-primary cell.

[0245] 5) The power allocation priority for PRACHs that are repeatedly transmitted is the same as the power allocation priority for PRACHs that are not repeatedly transmitted on non-primary cells.

[0246] This embodiment ensures that high-priority signals can be sent or received on time by defining the power allocation priority of the PRACH repeated transmission, thus guaranteeing normal signal transmission.

[0247] Optionally, the reception of the PRACH retransmission is completed within the first duration;

[0248] The first duration includes at least one of the following:

[0249] The mapping period from SSB to RO is M times the time.

[0250] The mapping association period from SSB to RO is N times the time;

[0251] The correlation pattern period from SSB to RO is L times the time.

[0252] The time value corresponding to the random access response window;

[0253] The associated mode period of the RO for repeated SSB to PRACH transmissions; the associated mode period of the RO for repeated SSB to PRACH transmissions may be additionally configured for repeated PRACH transmissions.

[0254] Where M, N, and L are positive integers. The specific values ​​of M, N, and L can be defined by the protocol or configured by system messages.

[0255] In this embodiment, an additional RO association pattern period for repeated SSB-PRACH transmissions is defined, which may include one or more SSB-RO association pattern periods, such that the pattern of repeated RO and SSB transmissions in PRACH can be repeated at most every predetermined time period (e.g., every 640ms). Optionally, the predetermined time period may be a positive integer multiple of the RO association pattern period of SSB to (existing, single-transmission) PRACH.

[0256] Optionally, the method further includes: sending resource configuration information for repeated PRACH transmissions to the terminal, the resource configuration information indicating the configured resources.

[0257] In this embodiment, after the network-side device configures the configuration resources for PRACH repetitive transmission, it can send the resource configuration information to the terminal.

[0258] In embodiments of this application, the network-side device configures resources for PRACH repetition and determines whether the configured resources are actually used for PRACH repetition. This allows the network-side device to receive repetitive PRACH transmissions on the configured resources actually used for PRACH repetition, reducing random access latency. Embodiments of this application provide solutions for situations where configured resources are invalid or conflict with other signal resources. For example, when a PRACH repetition conflicts with other resources, some PRACH repetitions can be discarded or their transmission power not increased to ensure that other high-priority signals can be sent or received on time; or, to ensure the actual number of PRACH repetitions, the PRACH Hoccasion used for repetitions needs to be postponed, skipping invalid or non-transmitted PRACH ROs; or, even if the resources for the first repetition are invalid or the PRACH is not actually transmitted, the PRACH resources for subsequent repetitions can still be used to transmit the remaining PRACH repetitions, reducing random access latency.

[0259] The method for determining PRACH repeatable transmission resources provided in this application can be executed by an apparatus for determining PRACH repeatable transmission resources. This application uses an example of an apparatus for determining PRACH repeatable transmission resources executing the method for determining PRACH repeatable transmission resources to illustrate the apparatus for determining PRACH repeatable transmission resources provided in this application.

[0260] like Figure 11 As shown, this application provides an apparatus 1100 for determining PRACH repeated transmission resources, applied to a terminal, including:

[0261] The first acquisition module 1110 is used to acquire resource configuration information for repeated transmission of the Physical Random Access Channel (PRACH), wherein the resource configuration information indicates the configuration resources for the repeated transmission of the PRACH.

[0262] The first determining module 1120 is used to determine whether the configuration resources are used for PRACH repeated transmission.

[0263] Optionally, the first determining module includes at least one of the following:

[0264] The first determining unit is configured to determine whether the configuration resource is used for PRACH retransmission based on the validity of the configuration resource.

[0265] The second determining unit is used to determine whether the configuration resource is used for PRACH repeated transmission based on the configuration information of the symbol where the configuration resource is located;

[0266] The third determining unit is used to determine whether the configuration resource is used for PRACH repeated transmission based on the conflict between the configuration resource and other signal resources.

[0267] Optionally, the device further includes:

[0268] The second determining module is used to determine the validity of the configuration resources;

[0269] The validity of the configured resources is related to the first gap requirement and / or the time-division multiplexing (TDD) uplink and downlink configuration.

[0270] The first gap requirement is the gap requirement between SSB transmission, the symbol set used for SSB transmission, and the symbol set used for PRACH transmission.

[0271] Optionally, the first determining unit includes at least one of the following:

[0272] The first determining subunit is used to determine whether the first RO is used for PRACH repeated transmission based on the validity of the first RO in the configuration resources.

[0273] The second determining subunit is used to determine whether the first RO in the configuration resource is used for PRACH repeated transmission based on the validity of the common RO in the configuration resource;

[0274] Wherein, the common RO is the RO of the common configuration used by the PRACH repeat transmission and the PRACH non-repeat transmission; the first RO is the RO used only for PRACH repeat transmission.

[0275] Optionally, the first determining subunit is specifically used for:

[0276] If the first target RO in the first RO is invalid, then it is determined that the first target RO is not used for PRACH retransmission.

[0277] Optionally, the device further includes:

[0278] The first processing module is used to postpone the first target RO by one RO level in the time domain to obtain a second target RO, and the second target RO is used for PRACH repeated transmission.

[0279] Optionally, the first target RO is included in the number of ROs repeatedly transmitted by the PRACH.

[0280] Optionally, the second determining subunit is specifically used to perform at least one of the following operations:

[0281] If the first common RO in the common RO is invalid, then it is determined that the first RO associated with the first common RO is not used for PRACH retransmission;

[0282] If the first common RO in the common RO is valid but not used for PRACH retransmission, then it is determined that the first RO associated with the first common RO is not used for PRACH retransmission.

[0283] If the first common RO in the common RO is invalid, then the first RO associated with the first common RO is determined to be used for PRACH retransmission;

[0284] If the first common RO in the common ROs is valid but not used for PRACH retransmission, then the first RO associated with the first common RO is determined to be used for PRACH retransmission.

[0285] Optionally, the second determining unit is used to perform at least one of the following operations:

[0286] If the symbol containing the third target RO in the first RO is configured as a flexible symbol in the public TDD uplink and downlink configuration information and as a downlink in the dedicated TDD uplink and downlink configuration information, then it is determined that the third target RO is not used for PRACH retransmission.

[0287] If the symbol containing the third target RO in the first RO is configured as a flexible symbol in the public TDD uplink and downlink configuration information and as a downlink in the DCI format, then it is determined that the third target RO is not used for PRACH retransmission.

[0288] If the symbol containing the third target RO in the first RO is configured as a flexible symbol in the first configuration information, and the terminal receives downlink signals on the symbol, then it is determined that the third target RO is not used for PRACH repetitive transmission; the first configuration information includes at least one of the following: public TDD uplink and downlink configuration information, dedicated TDD uplink and downlink configuration information, and DCI format;

[0289] Wherein, the first RO is the RO in the configuration resources that is only used for PRACH repeated transmission.

[0290] Optionally, the third determining unit is used to perform at least one of the following operations:

[0291] If the fourth target RO in the first RO at least partially overlaps with the transmission resources of the first uplink information in the random access process, then it is determined that the fourth target RO is not used for PRACH repetition transmission; the first RO is the RO in the configuration resources that is only used for PRACH repetition transmission.

[0292] If higher-layer signaling instructs the terminal to receive downlink signals in a set of symbols within a time slot, and DCI format information instructs the terminal to perform PRACH retransmission in the fourth target RO, and the fourth target RO overlaps with at least one symbol in the symbol set where the time slot is located, then it is determined that the fourth target RO is not used for PRACH retransmission.

[0293] If higher-layer signaling instructs the terminal to perform PRACH retransmission on a target symbol on the fourth target RO, and DCI format information instructs the terminal to receive downlink signals in a subset of symbols of the target symbol, then it is determined that the fourth target RO is not used for PRACH retransmission.

[0294] Optionally, the device further includes:

[0295] The third determining module is used to determine the power allocation priority of the PRACH repeated transmission;

[0296] The power allocation priority includes at least one of the following:

[0297] The power allocation priority of PRACH that is repeatedly transmitted is lower than the power allocation priority of PRACH that is not repeatedly transmitted on the primary cell.

[0298] The power allocation priority for PRACHs that are repeatedly transmitted is the same as the power allocation priority for PRACHs that are not repeatedly transmitted on the primary cell.

[0299] If the PRACH is repeatedly transmitted on the primary cell, the power allocation priority of the repeatedly transmitted PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on the primary cell.

[0300] If the PRACH is repeatedly transmitted on a non-primary cell, the power allocation priority of the repeatedly transmitted PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on a non-primary cell.

[0301] The power allocation priority for PRACHs that are repeatedly transmitted is the same as the power allocation priority for PRACHs that are not repeatedly transmitted on non-primary cells.

[0302] Optionally, the PRACH retransmission is completed within the first duration;

[0303] The first duration includes at least one of the following:

[0304] The mapping period from SSB to RO is M times the time.

[0305] The mapping association period from SSB to RO is N times the time;

[0306] The correlation pattern period from SSB to RO is L times the time.

[0307] The time value corresponding to the random access response window;

[0308] The associated mode cycle of RO repeated transmission from SSB to PRACH;

[0309] Where M, N, and L are positive integers.

[0310] In this embodiment, the terminal obtains configuration resources for PRACH repetitive transmission and determines whether the configuration resources are actually used for PRACH repetitive transmission. This provides a solution when the configuration resources are invalid or conflict with other signal resources, thereby reducing random access latency.

[0311] It should be noted that the apparatus for determining PRACH repeated transmission resources provided in this application embodiment can achieve... Figures 4-9 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0312] like Figure 12 As shown, this application provides an apparatus 1200 for determining PRACH repeated transmission resources, applied to a network-side device, including:

[0313] The fourth determining module 1210 is used to determine the configuration resources for PRACH retransmission;

[0314] The fifth determining module 1220 is used to determine whether the configuration resource is used to receive repeatedly transmitted PRACH.

[0315] Optionally, the fifth determining module includes:

[0316] The fourth determining unit is used to determine whether the configuration resource is used to receive repeatedly transmitted PRACH based on the validity of the configuration resource;

[0317] The fifth determining unit is used to determine whether the configuration resource is used to receive repeatedly transmitted PRACH based on the configuration information of the symbol where the configuration resource is located;

[0318] The sixth determining unit is used to determine whether the configuration resource is used to receive repeatedly transmitted PRACH based on the conflict between the configuration resource and other signal resources.

[0319] Optionally, the device further includes:

[0320] The sixth determining module is used to determine the validity of the configuration resources;

[0321] The validity of the configured resources is related to the first gap requirement and / or the time-division multiplexing (TDD) uplink and downlink configuration.

[0322] The first gap requirement is the gap requirement between the Synchronization Signal Block (SSB) transmission, the symbol set used for SSB transmission, and the symbol set used for PRACH transmission.

[0323] Optionally, the fourth determining unit includes at least one of the following:

[0324] The third determining subunit is used to determine whether the configuration resource is used to receive repetitive PRACH transmissions based on the validity of the first RO in the configuration resource.

[0325] The fourth determining subunit is used to determine whether the configuration resource is used to receive repetitive PRACH transmissions based on the validity of the common RO in the configuration resource.

[0326] Wherein, the common RO is the RO of the common configuration used by the PRACH repeat transmission and the PRACH non-repeat transmission; the first RO is the RO used only for PRACH repeat transmission.

[0327] Optionally, the third determining subunit is specifically used for:

[0328] If the first target RO in the first RO is invalid, then it is determined that the first target RO is not used to receive PRACH retransmissions.

[0329] Optionally, the device further includes:

[0330] The seventh determining module is used to determine the time domain position of the second target RO, which is obtained by delaying the first target RO by one RO level in the time domain. The second target RO is used to receive the retransmitted PRACH.

[0331] Optionally, the fourth determining subunit is used to perform at least one of the following operations:

[0332] If the first common RO in the common RO is invalid, then it is determined that the first RO associated with the first common RO is not used to receive retransmitted PRACH;

[0333] If the first public RO in the public RO is valid but not used for PRACH retransmission, then it is determined that the first RO associated with the first public RO is not used to receive retransmission PRACH.

[0334] If the first common RO in the common RO is invalid, then the first RO associated with the first common RO is determined to be used to receive retransmitted PRACH.

[0335] If the first public RO in the public RO is valid but not used for PRACH retransmission, then the first RO associated with the first public RO is determined to be used to receive retransmission PRACH.

[0336] Optionally, the fifth determining unit is used to perform at least one of the following operations:

[0337] If the symbol containing the third target RO in the first RO is configured as a flexible symbol in the public TDD uplink and downlink configuration information and as a downlink in the dedicated TDD uplink and downlink configuration information, then it is determined that the third target RO is not used to receive retransmitted PRACH.

[0338] If the symbol containing the third target RO in the first RO is configured as a flexible symbol in the public TDD uplink and downlink configuration information and as a downlink in the DCI format, then it is determined that the third target RO is not used to receive repetitive PRACH transmissions.

[0339] If the symbol containing the third target RO in the first RO is configured as a flexible symbol in the first configuration information, and the terminal receives downlink signals on the symbol, then it is determined that the third target RO is not used to receive repetitive PRACH transmissions; the first configuration information includes at least one of the following: public TDD uplink / downlink configuration information, dedicated TDD uplink / downlink configuration information, and DCI format;

[0340] Wherein, the first RO is the RO in the configuration resources that is only used for PRACH repeated transmission.

[0341] Optionally, the sixth determining unit is used to:

[0342] If the fourth target RO in the first RO at least partially overlaps with the transmission resources of the first uplink information in the random access process, then it is determined that the fourth target RO is not used to receive retransmitted PRACH.

[0343] Optionally, the reception of the PRACH retransmission is completed within the first duration;

[0344] The first duration includes at least one of the following:

[0345] The mapping period from SSB to RO is M times the time.

[0346] The mapping association period from SSB to RO is N times the time;

[0347] The correlation pattern period from SSB to RO is L times the time.

[0348] The time value corresponding to the random access response window;

[0349] The associated mode cycle of RO repeated transmission from SSB to PRACH;

[0350] Where M, N, and L are positive integers.

[0351] Optionally, the device further includes:

[0352] The first sending module is used to send resource configuration information for repeated PRACH transmissions to the terminal, wherein the resource configuration information indicates the configured resources.

[0353] In embodiments of this application, the network-side device configures resources for PRACH retransmission and determines whether the configured resources are actually used for PRACH retransmission, so that the network-side device can receive retransmitted PRACH on the configured resources actually used for PRACH retransmission, thereby reducing random access latency.

[0354] It should be noted that the apparatus for determining PRACH repeated transmission resources provided in this application embodiment can achieve... Figure 10 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0355] The apparatus for determining PRACH repeated transmission resources in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or other devices besides a terminal. For example, the terminal can include, but is not limited to, the type of terminal 11 listed above; other devices can be servers, network attached storage (NAS), etc., and this application embodiment does not specifically limit the scope.

[0356] Optional, such as Figure 13 As shown in the illustration, this application also provides a communication device 1300, including a processor 1301 and a memory 1302. The memory 1302 stores a program or instructions that can run on the processor 1301. For example, when the communication device 1300 is a terminal, the program or instructions executed by the processor 1301 implement the various steps of the method embodiments applied to the terminal described above, and achieve the same technical effect. When the communication device 1300 is a network-side device, the program or instructions executed by the processor 1301 implement the various steps of the method embodiments applied to the network-side device described above, and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0357] This application embodiment also provides a terminal, including a processor and a communication interface. The processor is used to acquire resource configuration information for repeated transmission of the Physical Random Access Channel (PRACH), the resource configuration information indicating the configuration resources for the repeated PRACH transmission; and to determine whether the configuration resources are used for repeated PRACH transmission. This terminal embodiment corresponds to the above-described terminal-side method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. Specifically, Figure 14 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0358] The terminal 1400 includes, but is not limited to, at least some of the following components: radio frequency unit 1401, network module 1402, audio output unit 1403, input unit 1404, sensor 1405, display unit 1406, user input unit 1407, interface unit 1408, memory 1409, and processor 1410.

[0359] Those skilled in the art will understand that the terminal 1400 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 1410 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 14The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0360] It should be understood that, in this embodiment, the input unit 1404 may include a graphics processing unit (GPU) 14041 and a microphone 14042. The GPU 14041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1406 may include a display panel 14061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1407 includes a touch panel 14071 and at least one of other input devices 14072. The touch panel 14071 is also called a touch screen. The touch panel 14071 may include a touch detection device and a touch controller. Other input devices 14072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0361] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1401 can transmit it to the processor 1410 for processing; in addition, the radio frequency unit 1401 can send uplink data to the network-side device. Typically, the radio frequency unit 1401 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0362] The memory 1409 can be used to store software programs or instructions and various data. The memory 1409 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback function, image playback function, etc.). Furthermore, the memory 1409 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can 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 memory bus RAM (DRRAM). The memory 1409 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0363] Processor 1410 may include one or more processing units; optionally, processor 1410 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1410.

[0364] The processor 1410 is configured to acquire resource configuration information for repeated transmission of the Physical Random Access Channel (PRACH), wherein the resource configuration information indicates the configuration resources for repeated PRACH transmission; and determine whether the configuration resources are used for repeated PRACH transmission.

[0365] In an embodiment of this application, the terminal obtains configuration resources for PRACH retransmission and determines whether the configuration resources are actually used for PRACH retransmission, so that the terminal can use the configuration resources that can be actually used for PRACH retransmission to perform PRACH retransmission, thereby reducing random access latency.

[0366] Optionally, the processor 1410 is further configured to perform at least one of the following operations:

[0367] Based on the validity of the configuration resources, determine whether the configuration resources are used for PRACH retransmission;

[0368] Based on the configuration information of the symbol where the configuration resource is located, determine whether the configuration resource is used for PRACH retransmission;

[0369] Based on the conflict between the configuration resource and other signal resources, determine whether the configuration resource is used for PRACH retransmission.

[0370] Optionally, the processor 1410 is further configured to: determine the validity of the configuration resources;

[0371] The validity of the configured resources is related to the first gap requirement and / or the time-division multiplexing (TDD) uplink and downlink configuration.

[0372] The first gap requirement is the gap requirement between the Synchronization Signal Block (SSB) transmission, the symbol set used for SSB transmission, and the symbol set used for PRACH transmission.

[0373] Optionally, the processor 1410 is further configured to perform at least one of the following operations:

[0374] Based on the validity of the first RO in the configuration resources, determine whether the first RO is used for PRACH retransmission;

[0375] Based on the validity of the common ROs in the configuration resources, determine whether the first RO in the configuration resources is used for PRACH retransmission;

[0376] Wherein, the common RO is the RO of the common configuration used by the PRACH repeat transmission and the PRACH non-repeat transmission; the first RO is the RO used only for PRACH repeat transmission.

[0377] Optionally, the processor 1410 is further configured to: if the first target RO in the first RO is invalid, determine that the first target RO is not used for PRACH retransmission.

[0378] Optionally, the processor 1410 is further configured to: delay the first target RO by one RO level in the time domain to obtain a second target RO, the second target RO being used for PRACH retransmission.

[0379] Optionally, the first target RO is included in the number of ROs repeatedly transmitted by the PRACH.

[0380] Optionally, the processor 1410 is further configured to perform at least one of the following operations:

[0381] If the first common RO in the common RO is invalid, then it is determined that the first RO associated with the first common RO is not used for PRACH retransmission;

[0382] If the first common RO in the common RO is valid but not used for PRACH retransmission, then it is determined that the first RO associated with the first common RO is not used for PRACH retransmission.

[0383] If the first common RO in the common RO is invalid, then the first RO associated with the first common RO is determined to be used for PRACH retransmission;

[0384] If the first common RO in the common ROs is valid but not used for PRACH retransmission, then the first RO associated with the first common RO is determined to be used for PRACH retransmission.

[0385] Optionally, the processor 1410 is further configured to perform at least one of the following operations:

[0386] If the symbol containing the third target RO in the first RO is configured as a flexible symbol in the public TDD uplink and downlink configuration information and as a downlink in the dedicated TDD uplink and downlink configuration information, then it is determined that the third target RO is not used for PRACH retransmission.

[0387] If the symbol containing the third target RO in the first RO is configured as a flexible symbol in the public TDD uplink and downlink configuration information and as a downlink in the DCI format, then it is determined that the third target RO is not used for PRACH retransmission.

[0388] If the symbol containing the third target RO in the first RO is configured as a flexible symbol in the first configuration information, and the terminal receives downlink signals on the symbol, then it is determined that the third target RO is not used for PRACH repetitive transmission; the first configuration information includes at least one of the following: public TDD uplink and downlink configuration information, dedicated TDD uplink and downlink configuration information, and DCI format;

[0389] Wherein, the first RO is the RO in the configuration resources that is only used for PRACH repeated transmission.

[0390] Optionally, the processor 1410 is further configured to perform at least one of the following operations:

[0391] If the fourth target RO in the first RO at least partially overlaps with the transmission resources of the first uplink information in the random access process, then it is determined that the fourth target RO is not used for PRACH repetition transmission; the first RO is the RO in the configuration resources that is only used for PRACH repetition transmission.

[0392] If higher-layer signaling instructs the terminal to receive downlink signals in a set of symbols within a time slot, and DCI format information instructs the terminal to perform PRACH retransmission in the fourth target RO, and the fourth target RO overlaps with at least one symbol in the symbol set where the time slot is located, then it is determined that the fourth target RO is not used for PRACH retransmission.

[0393] If higher-layer signaling instructs the terminal to perform PRACH retransmission on a target symbol on the fourth target RO, and DCI format information instructs the terminal to receive downlink signals in a subset of symbols of the target symbol, then it is determined that the fourth target RO is not used for PRACH retransmission.

[0394] Optionally, the processor 1410 is further configured to: determine the power allocation priority of the PRACH repetitive transmission;

[0395] The power allocation priority includes at least one of the following:

[0396] The power allocation priority of PRACH that is repeatedly transmitted is lower than the power allocation priority of PRACH that is not repeatedly transmitted on the primary cell.

[0397] The power allocation priority for PRACHs that are repeatedly transmitted is the same as the power allocation priority for PRACHs that are not repeatedly transmitted on the primary cell.

[0398] If the PRACH is repeatedly transmitted on the primary cell, the power allocation priority of the repeatedly transmitted PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on the primary cell.

[0399] If the PRACH is repeatedly transmitted on a non-primary cell, the power allocation priority of the repeatedly transmitted PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on a non-primary cell.

[0400] The power allocation priority for PRACHs that are repeatedly transmitted is the same as the power allocation priority for PRACHs that are not repeatedly transmitted on non-primary cells.

[0401] Optionally, the PRACH retransmission is completed within the first duration;

[0402] The first duration includes at least one of the following:

[0403] The mapping period from SSB to RO is M times the time.

[0404] The mapping association period from SSB to RO is N times the time;

[0405] The correlation pattern period from SSB to RO is L times the time.

[0406] The time value corresponding to the random access response window;

[0407] The associated mode cycle of RO repeated transmission from SSB to PRACH;

[0408] Where M, N, and L are positive integers.

[0409] In an embodiment of this application, the terminal obtains configuration resources for PRACH retransmission and determines whether the configuration resources are actually used for PRACH retransmission, so that the terminal can use the configuration resources that can be actually used for PRACH retransmission to perform PRACH retransmission, thereby reducing random access latency.

[0410] This application also provides a network-side device, including a processor and a communication interface. The processor is used to determine configuration resources for repeated PRACH transmissions and to determine whether the configuration resources are used to receive repeatedly transmitted PRACH. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0411] Specifically, embodiments of this application also provide a network-side device. For example... Figure 15 As shown, the network-side device 1500 includes: an antenna 151, a radio frequency (RF) device 152, a baseband device 153, a processor 154, and a memory 155. The antenna 151 is connected to the RF device 152. In the uplink direction, the RF device 152 receives information through the antenna 151 and transmits the received information to the baseband device 153 for processing. In the downlink direction, the baseband device 153 processes the information to be transmitted and sends it to the RF device 152. The RF device 152 processes the received information and transmits it through the antenna 151.

[0412] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 153, which includes a baseband processor.

[0413] Baseband device 153 may include, for example, at least one baseband board on which multiple chips are disposed, such as Figure 15 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 155 via a bus interface to call the program in the memory 155 and execute the network device operation described in the above method embodiment.

[0414] The network-side device may also include a network interface 156, such as a common public radio interface (CPRI).

[0415] Specifically, the network-side device 1500 of this embodiment further includes: instructions or programs stored in memory 155 and executable on processor 154, wherein processor 154 calls the instructions or programs in memory 155 to execute. Figure 12 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0416] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described method embodiment for determining PRACH repeated transmission resources and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0417] The processor is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0418] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described method embodiment for determining PRACH repeated transmission resources, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0419] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0420] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described method embodiment for determining PRACH repeated transmission resources, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0421] This application also provides a system for determining PRACH repeatable transmission resources, including: a terminal and a network-side device. The terminal can be used to perform the steps of the method for determining PRACH repeatable transmission resources applied to the terminal as described above, and the network-side device can be used to perform the steps of the method for determining PRACH repeatable transmission resources applied to the network-side device as described above.

[0422] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

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

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

Claims

1. A method for determining PRACH repetition transmission resource, characterized in that, include: The terminal obtains resource configuration information for repeated transmission of the Physical Random Access Channel (PRACH), the resource configuration information indicating the configuration resources for the repeated transmission of the PRACH; The terminal determines whether the configuration resources are used for PRACH retransmission; Determining whether the configuration resource is used for PRACH retransmission includes at least one of the following: Based on the validity of the configuration resource, determine whether the configuration resource is used for PRACH repeat transmission; the determination of whether the configuration resource is used for PRACH repeat transmission based on the validity of the configuration resource includes at least one of the following: determining whether the first RO in the configuration resource is used for PRACH repeat transmission based on the validity of the first RO; determining whether the first RO in the configuration resource is used for PRACH repeat transmission based on the validity of the common RO in the configuration resource; wherein, the common RO is a RO in common configuration used by both PRACH repeat transmission and PRACH non-repeating transmission; the first RO is a RO used only for PRACH repeat transmission; Based on the configuration information of the symbol where the configuration resource is located, it is determined whether the configuration resource is used for PRACH repetition transmission. This determination includes at least one of the following: if the symbol containing the third target RO in the first RO is configured as a flexible symbol in the public TDD uplink / downlink configuration information and as a downlink in the dedicated TDD uplink / downlink configuration information, then the third target RO is determined not to be used for PRACH repetition transmission; if the symbol containing the third target RO in the first RO is configured as a flexible symbol in the public TDD uplink / downlink configuration information and as a downlink in the DCI format, then the third target RO is determined not to be used for PRACH repetition transmission; if the symbol containing the third target RO in the first RO is configured as a flexible symbol in the first configuration information, and the terminal receives a downlink signal on the symbol, then the third target RO is determined not to be used for PRACH repetition transmission; the first configuration information includes at least one of: public TDD uplink / downlink configuration information, dedicated TDD uplink / downlink configuration information, and DCI format; wherein, the first RO is the RO in the configuration resource that is only used for PRACH repetition transmission.

2. The method according to claim 1, characterized in that, The step of determining whether the configuration resource is used for PRACH retransmission further includes: Based on the conflict between the configuration resource and other signal resources, determine whether the configuration resource is used for PRACH retransmission.

3. The method according to claim 1, characterized in that, The method further includes: Determine the validity of the configured resources; The validity of the configured resources is related to the first gap requirement and / or the time-division multiplexing (TDD) uplink and downlink configuration. The first gap requirement is the gap requirement between the Synchronization Signal Block (SSB) transmission, the symbol set used for SSB transmission, and the symbol set used for PRACH transmission.

4. The method according to claim 1, characterized in that, The step of determining whether the first RO is used for PRACH retransmission based on the validity of the first RO in the configuration resources includes: If the first target RO in the first RO is invalid, then it is determined that the first target RO is not used for PRACH retransmission.

5. The method according to claim 4, characterized in that, The method further includes: The first target RO is delayed by one RO level in the time domain to obtain the second target RO, which is used for PRACH retransmission.

6. The method according to claim 4, characterized in that, The first target RO is included in the number of ROs repeatedly transmitted by the PRACH.

7. The method according to claim 1, characterized in that, Determining whether a first RO in the configuration resource is used for PRACH retransmission based on the validity of the public RO in the configuration resource includes at least one of the following: If the first common RO in the common RO is invalid, then it is determined that the first RO associated with the first common RO is not used for PRACH retransmission; If the first common RO in the common RO is valid but not used for PRACH retransmission, then it is determined that the first RO associated with the first common RO is not used for PRACH retransmission. If the first common RO in the common RO is invalid, then the first RO associated with the first common RO is determined to be used for PRACH retransmission; If the first common RO in the common ROs is valid but not used for PRACH retransmission, then the first RO associated with the first common RO is determined to be used for PRACH retransmission.

8. The method according to claim 2, characterized in that, The step of determining whether the configuration resource is used for PRACH retransmission based on the conflict between the configuration resource and other signal resources includes at least one of the following: If the fourth target RO in the first RO at least partially overlaps with the transmission resources of the first uplink information in the random access process, then it is determined that the fourth target RO is not used for PRACH repetition transmission; the first RO is the RO in the configuration resources that is only used for PRACH repetition transmission. If higher-layer signaling instructs the terminal to receive downlink signals in a set of symbols within a time slot, and DCI format information instructs the terminal to perform PRACH retransmission in the fourth target RO, and the fourth target RO overlaps with at least one symbol in the symbol set where the time slot is located, then it is determined that the fourth target RO is not used for PRACH retransmission. If higher-layer signaling instructs the terminal to perform PRACH retransmission on a target symbol on the fourth target RO, and DCI format information instructs the terminal to receive downlink signals in a subset of symbols of the target symbol, then it is determined that the fourth target RO is not used for PRACH retransmission.

9. The method according to claim 1, characterized in that, The method further includes: Determine the power allocation priority for the repeated PRACH transmissions; The power allocation priority includes at least one of the following: The power allocation priority of PRACH that is repeatedly transmitted is lower than the power allocation priority of PRACH that is not repeatedly transmitted on the primary cell. The power allocation priority for PRACHs that are repeatedly transmitted is the same as the power allocation priority for PRACHs that are not repeatedly transmitted on the primary cell. If the PRACH is repeatedly transmitted on the primary cell, the power allocation priority of the repeatedly transmitted PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on the primary cell. If the PRACH is repeatedly transmitted on a non-primary cell, the power allocation priority of the repeatedly transmitted PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on a non-primary cell. The power allocation priority for PRACHs that are repeatedly transmitted is the same as the power allocation priority for PRACHs that are not repeatedly transmitted on non-primary cells.

10. The method according to claim 1, characterized in that, The PRACH repeat transmission is completed within the first duration; The first duration includes at least one of the following: The mapping period from SSB to RO is M times the time. The mapping association period from SSB to RO is N times the time; The correlation pattern period from SSB to RO is L times the time. The time value corresponding to the random access response window; The associated mode cycle of RO repeated transmission from SSB to PRACH; Where M, N, and L are positive integers.

11. A method for determining PRACH retransmission resources, characterized in that, include: Network-side devices determine the configuration resources for PRACH retransmission; The network-side device determines whether the configured resources are used to receive repetitive PRACH transmissions; Determining whether the configuration resource is used to receive repetitive PRACH transmissions includes at least one of the following: Based on the validity of the configuration resource, determine whether the configuration resource is used to receive repeated PRACH transmissions; the determination of whether the configuration resource is used to receive repeated PRACH transmissions based on the validity of the configuration resource includes at least one of the following: determining whether the configuration resource is used to receive repeated PRACH transmissions based on the validity of a first RO in the configuration resource; determining whether the configuration resource is used to receive repeated PRACH transmissions based on the validity of a common RO in the configuration resource; wherein, the common RO is a RO in common configuration used for both repeated PRACH transmissions and non-repeated PRACH transmissions; the first RO is a RO used only for repeated PRACH transmissions; Based on the configuration information of the symbol where the configuration resource is located, determine whether the configuration resource is used to receive repetitive PRACH transmissions; the determination of whether the configuration resource is used to receive repetitive PRACH transmissions based on the configuration information of the symbol where the configuration resource is located includes at least one of the following: if the symbol where the third target RO in the first RO is located is configured as a flexible symbol in the public TDD uplink / downlink configuration information and as a downlink in the dedicated TDD uplink / downlink configuration information, then determine that the third target RO is not used to receive repetitive PRACH transmissions; if the symbol where the third target RO in the first RO is located is configured as a flexible symbol in the public TDD uplink / downlink configuration information and as a downlink in the dedicated TDD uplink / downlink configuration information, then determine that the third target RO is not used to receive repetitive PRACH transmissions; If the symbol of the third target RO in the first RO is configured as a flexible symbol in the configuration information and as a downlink in the DCI format, then it is determined that the third target RO is not used to receive repeated PRACH transmissions; if the symbol of the third target RO in the first RO is configured as a flexible symbol in the first configuration information, and the terminal receives downlink signals on the symbol, then it is determined that the third target RO is not used to receive repeated PRACH transmissions; the first configuration information includes at least one of: public TDD uplink / downlink configuration information, dedicated TDD uplink / downlink configuration information, and DCI format; wherein, the first RO is an RO in the configuration resources that is only used for repeated PRACH transmissions.

12. The method according to claim 11, characterized in that, The step of determining whether the configuration resource is used to receive repeatedly transmitted PRACH further includes: Based on the conflict between the configuration resource and other signal resources, determine whether the configuration resource is used to receive repetitive PRACH transmissions.

13. The method according to claim 11, characterized in that, The method further includes: Determine the validity of the configured resources; The validity of the configured resources is related to the first gap requirement and / or the time-division multiplexing (TDD) uplink and downlink configuration. The first gap requirement is the gap requirement between SSB transmission, the symbol set used for SSB transmission, and the symbol set used for PRACH transmission.

14. The method according to claim 11, characterized in that, The step of determining whether the configuration resource is used to receive repetitive PRACH transmissions based on the validity of the first RO in the configuration resource includes: If the first target RO in the first RO is invalid, then it is determined that the first target RO is not used to receive PRACH retransmissions.

15. The method according to claim 14, characterized in that, The method further includes: The time-domain position of the second target RO is determined. The second target RO is obtained by delaying the first target RO by one RO level in the time-domain position. The second target RO is used to receive the retransmitted PRACH.

16. The method according to claim 11, characterized in that, Determining whether the configuration resource is used to receive recurring PRACH transmissions based on the validity of the public RO in the configuration resource includes at least one of the following: If the first common RO in the common RO is invalid, then it is determined that the first RO associated with the first common RO is not used to receive retransmitted PRACH; If the first common RO in the common RO is valid but not used for PRACH retransmission, then it is determined that the first RO associated with the first common RO is not used to receive retransmitted PRACH. If the first common RO in the common RO is invalid, then the first RO associated with the first common RO is determined to be used to receive retransmitted PRACH. If the first public RO in the public RO is valid but not used for PRACH retransmission, then the first RO associated with the first public RO is determined to be used to receive retransmission PRACH.

17. The method according to claim 12, characterized in that, Based on the conflict between the configuration resource and other signal resources, determining whether the configuration resource is used to receive repetitive PRACH transmissions includes: If the fourth target RO in the first RO at least partially overlaps with the transmission resources of the first uplink information in the random access process, then it is determined that the fourth target RO is not used to receive retransmitted PRACH.

18. The method according to claim 11, characterized in that, The reception of the PRACH repeated transmission is completed within the first duration; The first duration includes at least one of the following: The mapping period from SSB to RO is M times the time. The mapping association period from SSB to RO is N times the time. The time of the correlation pattern from SSB to RO is L times the time. The time value corresponding to the random access response window; The associated mode cycle of RO repeated transmission from SSB to PRACH; Where M, N, and L are positive integers.

19. The method according to claim 11, characterized in that, The method further includes: Send resource configuration information for repeated PRACH transmissions to the terminal, wherein the resource configuration information indicates the configured resources.

20. An apparatus for determining PRACH retransmission resources, characterized in that, include: The first acquisition module is used to acquire resource configuration information for repeated transmission of the Physical Random Access Channel (PRACH), wherein the resource configuration information indicates the configuration resources for the repeated transmission of the PRACH. The first determining module is used to determine whether the configuration resources are used for PRACH repeated transmission; The first determining module includes at least one of the following: A first determining unit is configured to determine whether the configuration resource is used for PRACH retransmission based on the validity of the configuration resource; the first determining unit includes at least one: a first determining subunit, configured to determine whether the first RO is used for PRACH retransmission based on the validity of the first RO in the configuration resource; The second determining subunit is used to determine whether a first RO in the configuration resources is used for PRACH repeat transmission based on the validity of the common RO in the configuration resources; wherein, the common RO is a common configuration RO used by the PRACH repeat transmission and the PRACH non-repeating transmission; and the first RO is a RO used only for PRACH repeat transmission. The second determining unit is configured to determine whether the configuration resource is used for PRACH repetition transmission based on the configuration information of the symbol where the configuration resource is located. The second determining unit is configured to perform at least one of the following operations: if the symbol where the third target RO in the first RO is located is configured as a flexible symbol in the public TDD uplink / downlink configuration information and as a downlink in the dedicated TDD uplink / downlink configuration information, then the third target RO is determined not to be used for PRACH repetition transmission; if the symbol where the third target RO in the first RO is located is configured as a flexible symbol in the public TDD uplink / downlink configuration information and as a downlink in the DCI format, then the third target RO is determined not to be used for PRACH repetition transmission; if the symbol where the third target RO in the first RO is located is configured as a flexible symbol in the first configuration information, and the terminal receives a downlink signal on the symbol, then the third target RO is determined not to be used for PRACH repetition transmission; the first configuration information includes at least one of: public TDD uplink / downlink configuration information, dedicated TDD uplink / downlink configuration information, and DCI format; wherein, the first RO is the RO in the configuration resource that is only used for PRACH repetition transmission.

21. The apparatus according to claim 20, characterized in that, The first determining module further includes: The third determining unit is used to determine whether the configuration resource is used for PRACH repeated transmission based on the conflict between the configuration resource and other signal resources.

22. The apparatus according to claim 20, characterized in that, The device further includes: The second determining module is used to determine the validity of the configuration resources; The validity of the configured resources is related to the first gap requirement and / or the time-division multiplexing (TDD) uplink and downlink configuration. The first gap requirement is the gap requirement between SSB transmission, the symbol set used for SSB transmission, and the symbol set used for PRACH transmission.

23. The apparatus according to claim 20, characterized in that, The first determining subunit is specifically used for: If the first target RO in the first RO is invalid, then it is determined that the first target RO is not used for PRACH retransmission.

24. The apparatus according to claim 23, characterized in that, The device further includes: The first processing module is used to postpone the first target RO by one RO level in the time domain to obtain a second target RO, and the second target RO is used for PRACH repeated transmission.

25. The apparatus according to claim 23, characterized in that, The first target RO is included in the number of ROs repeatedly transmitted by the PRACH.

26. The apparatus according to claim 20, characterized in that, The second determining subunit is specifically used to perform at least one of the following operations: If the first common RO in the common RO is invalid, then it is determined that the first RO associated with the first common RO is not used for PRACH retransmission; If the first common RO in the common RO is valid but not used for PRACH retransmission, then it is determined that the first RO associated with the first common RO is not used for PRACH retransmission. If the first common RO in the common RO is invalid, then the first RO associated with the first common RO is determined to be used for PRACH retransmission; If the first common RO in the common ROs is valid but not used for PRACH retransmission, then the first RO associated with the first common RO is determined to be used for PRACH retransmission.

27. The apparatus according to claim 21, characterized in that, The third determining unit is used to perform at least one of the following operations: If the fourth target RO in the first RO at least partially overlaps with the transmission resources of the first uplink information in the random access process, then it is determined that the fourth target RO is not used for PRACH repetition transmission; the first RO is the RO in the configuration resources that is only used for PRACH repetition transmission. If higher-layer signaling instructs the terminal to receive downlink signals in a set of symbols within a time slot, and DCI format information instructs the terminal to perform PRACH retransmission in the fourth target RO, and the fourth target RO overlaps with at least one symbol in the symbol set where the time slot is located, then it is determined that the fourth target RO is not used for PRACH retransmission. If higher-layer signaling instructs the terminal to perform PRACH retransmission on a target symbol on the fourth target RO, and DCI format information instructs the terminal to receive downlink signals in a subset of symbols of the target symbol, then it is determined that the fourth target RO is not used for PRACH retransmission.

28. The apparatus according to claim 20, characterized in that, The device further includes: The third determining module is used to determine the power allocation priority of the PRACH repeated transmission; The power allocation priority includes at least one of the following: The power allocation priority of PRACH that is repeatedly transmitted is lower than the power allocation priority of PRACH that is not repeatedly transmitted on the primary cell. The power allocation priority for PRACHs that are repeatedly transmitted is the same as the power allocation priority for PRACHs that are not repeatedly transmitted on the primary cell. If the PRACH is repeatedly transmitted on the primary cell, the power allocation priority of the repeatedly transmitted PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on the primary cell. If the PRACH is repeatedly transmitted on a non-primary cell, the power allocation priority of the repeatedly transmitted PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on a non-primary cell. The power allocation priority for PRACHs that are repeatedly transmitted is the same as the power allocation priority for PRACHs that are not repeatedly transmitted on non-primary cells.

29. The apparatus according to claim 20, characterized in that, The PRACH repeat transmission is completed within the first duration; The first duration includes at least one of the following: The mapping period from SSB to RO is M times the time. The mapping association period from SSB to RO is N times the time; The correlation pattern period from SSB to RO is L times the time. The time value corresponding to the random access response window; The associated mode cycle of RO repeated transmission from SSB to PRACH; Where M, N, and L are positive integers.

30. An apparatus for determining PRACH repetitive transmission resources, characterized in that, include: The fourth determination module is used to determine the configuration resources for repeated PRACH transmissions; The fifth determining module is used to determine whether the configured resources are used to receive repeatedly transmitted PRACH. The fifth determining module includes at least one of the following: A fourth determining unit is configured to determine whether the configuration resource is used to receive repetitive PRACH transmissions based on the validity of the configuration resource. The fourth determining unit includes at least one of the following: a third determining subunit is configured to determine whether the configuration resource is used to receive repetitive PRACH transmissions based on the validity of a first RO in the configuration resource; a fourth determining subunit is configured to determine whether the configuration resource is used to receive repetitive PRACH transmissions based on the validity of a common RO in the configuration resource; wherein the common RO is a RO in common configuration used for both repetitive and non-repetitive PRACH transmissions; and the first RO is a RO used only for repetitive PRACH transmissions. The fifth determining unit is configured to determine whether the configuration resource is used to receive repetitive PRACH transmissions based on the configuration information of the symbol where the configuration resource is located. The fifth determining unit is configured to perform at least one of the following operations: if the symbol where the third target RO in the first RO is located is configured as a flexible symbol in the public TDD uplink / downlink configuration information and as a downlink in the dedicated TDD uplink / downlink configuration information, then the third target RO is determined not to be used to receive repetitive PRACH transmissions; if the symbol where the third target RO in the first RO is located is configured as a flexible symbol in the public TDD uplink / downlink configuration information and as a downlink in the DCI format, then the third target RO is determined not to be used to receive repetitive PRACH transmissions; if the symbol where the third target RO in the first RO is located is configured as a flexible symbol in the first configuration information, and the terminal receives a downlink signal on the symbol, then the third target RO is determined not to be used to receive repetitive PRACH transmissions; the first configuration information includes at least one of: public TDD uplink / downlink configuration information, dedicated TDD uplink / downlink configuration information, and DCI format; wherein, the first RO is an RO in the configuration resource that is only used for repetitive PRACH transmissions.

31. The apparatus according to claim 30, characterized in that, The fifth determining module further includes: The sixth determining unit is used to determine whether the configuration resource is used to receive repeatedly transmitted PRACH based on the conflict between the configuration resource and other signal resources.

32. The apparatus according to claim 30, characterized in that, The device further includes: The sixth determining module is used to determine the validity of the configuration resources; The validity of the configured resources is related to the first gap requirement and / or the time-division multiplexing (TDD) uplink and downlink configuration. The first gap requirement is the gap requirement between SSB transmission, the symbol set used for SSB transmission, and the symbol set used for PRACH transmission.

33. The apparatus according to claim 30, characterized in that, The third determining subunit is specifically used for: If the first target RO in the first RO is invalid, then it is determined that the first target RO is not used to receive PRACH retransmissions.

34. The apparatus according to claim 33, characterized in that, The device further includes: The seventh determining module is used to determine the time domain position of the second target RO, which is obtained by delaying the first target RO by one RO level in the time domain. The second target RO is used to receive the retransmitted PRACH.

35. The apparatus according to claim 30, characterized in that, The fourth determining subunit is used to perform at least one of the following operations: If the first common RO in the common RO is invalid, then it is determined that the first RO associated with the first common RO is not used to receive retransmitted PRACH; If the first public RO in the public RO is valid but not used for PRACH retransmission, then it is determined that the first RO associated with the first public RO is not used to receive retransmission PRACH. If the first common RO in the common RO is invalid, then the first RO associated with the first common RO is determined to be used to receive retransmitted PRACH. If the first public RO in the public RO is valid but not used for PRACH retransmission, then the first RO associated with the first public RO is determined to be used to receive retransmission PRACH.

36. The apparatus according to claim 31, characterized in that, The sixth determining unit is used for: If the fourth target RO in the first RO at least partially overlaps with the transmission resources of the first uplink information in the random access process, then it is determined that the fourth target RO is not used to receive retransmitted PRACH.

37. The apparatus according to claim 30, characterized in that, The reception of the PRACH repeated transmission is completed within the first duration; The first duration includes at least one of the following: The mapping period from SSB to RO is M times the time. The mapping association period from SSB to RO is N times the time. The time of the correlation pattern from SSB to RO is L times the time. The time value corresponding to the random access response window; The associated mode cycle of RO repeated transmission from SSB to PRACH; Where M, N, and L are positive integers.

38. The apparatus according to claim 30, characterized in that, The device further includes: The first sending module is used to send resource configuration information for repeated PRACH transmissions to the terminal, wherein the resource configuration information indicates the configured resources.

39. A terminal, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method for determining PRACH repeat transfer resources as described in any one of claims 1 to 10.

40. A network-side device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method for determining PRACH repeat transfer resources as described in any one of claims 11 to 19.

41. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the method for determining PRACH repeatable transmission resources as described in any one of claims 1-10, or the steps of the method for determining PRACH repeatable transmission resources as described in any one of claims 11-19.

Images