WO2023131175A1 - 确定prach重复传输资源的方法、终端及网络侧设备 - Google Patents
确定prach重复传输资源的方法、终端及网络侧设备 Download PDFInfo
- Publication number
- WO2023131175A1 WO2023131175A1 PCT/CN2023/070396 CN2023070396W WO2023131175A1 WO 2023131175 A1 WO2023131175 A1 WO 2023131175A1 CN 2023070396 W CN2023070396 W CN 2023070396W WO 2023131175 A1 WO2023131175 A1 WO 2023131175A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- prach
- repeated transmission
- resource
- target
- transmission
- Prior art date
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 671
- 238000000034 method Methods 0.000 title claims abstract description 167
- 230000008569 process Effects 0.000 claims description 50
- 238000013507 mapping Methods 0.000 claims description 27
- 230000011664 signaling Effects 0.000 claims description 14
- 230000004044 response Effects 0.000 claims description 13
- 238000012545 processing Methods 0.000 claims description 8
- 230000003111 delayed effect Effects 0.000 claims 1
- 238000004891 communication Methods 0.000 abstract description 21
- 235000019527 sweetened beverage Nutrition 0.000 description 14
- 238000010586 diagram Methods 0.000 description 11
- 230000000694 effects Effects 0.000 description 11
- 230000006870 function Effects 0.000 description 11
- 238000001228 spectrum Methods 0.000 description 9
- 238000004590 computer program Methods 0.000 description 6
- 238000003672 processing method Methods 0.000 description 6
- 230000001360 synchronised effect Effects 0.000 description 5
- 101100274486 Mus musculus Cited2 gene Proteins 0.000 description 4
- 101150096622 Smr2 gene Proteins 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 230000000737 periodic effect Effects 0.000 description 4
- 238000013468 resource allocation Methods 0.000 description 4
- 238000012795 verification Methods 0.000 description 4
- 101100533725 Mus musculus Smr3a gene Proteins 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 230000001174 ascending effect Effects 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 230000008054 signal transmission Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 241000699670 Mus sp. Species 0.000 description 1
- 101150096310 SIB1 gene Proteins 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 238000005406 washing Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/08—Non-scheduled access, e.g. ALOHA
- H04W74/0833—Random access procedures, e.g. with 4-step access
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/1607—Details of the supervisory signal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0446—Resources in time domain, e.g. slots or frames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
- H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/08—Non-scheduled access, e.g. ALOHA
Definitions
- the present application belongs to the technical field of communication, and specifically relates to a method for determining PRACH repeated transmission resources, a terminal and a network side device.
- the random access procedure may be a contention-based random access procedure or a non-contention-based random access procedure.
- the random access process may be a four-step random access process (also called a Type-1 random access process) or a two-step random access process (also called a Type-2 random access process).
- Performing physical random access channel (Physical Random Access Channel, PRACH) repetition (repetition) transmission in the time domain can improve PRACH coverage.
- PRACH Physical Random Access Channel
- the resource allocation is relatively sparse and there may be a maximum PRACH configuration period of 160 ms. If this resource allocation scheme is used for PRACH repetition transmission, it may cause a long random access delay and may cause additional signal delays. order overhead.
- Embodiments of the present application provide a method for determining PRACH retransmission resources, a terminal and a network side device, which can solve the problem of long random access delay caused by existing resource allocation schemes.
- a method for determining PRACH repeated transmission resources which is applied to a terminal, and the method includes:
- the terminal acquires resource configuration information for the repeated transmission of the physical random access channel PRACH, where the resource configuration information indicates the configuration resources for the repeated transmission of the PRACH;
- the terminal determines whether the configured resource is used for PRACH repeated transmission.
- an apparatus for determining PRACH repeated transmission resources is provided, which is applied to a terminal, including:
- a first obtaining module configured to obtain resource configuration information for repeated transmission of a physical random access channel PRACH, where the resource configuration information indicates configuration resources for repeated transmission of the PRACH;
- the first determining module is configured to determine whether the configured resources are used for PRACH repeated transmission.
- a method for determining PRACH repeated transmission resources is provided, which is applied to a network side device, and the method includes:
- the network side device determines configuration resources for repeated transmission of the PRACH
- the network side device determines whether the configured resource is used to receive a PRACH for repeated transmission.
- an apparatus for determining PRACH repeated transmission resources is provided, which is applied to network side equipment, including:
- the fourth determination module is used to determine the configuration resources of PRACH repeated transmission
- a fifth determining module configured to determine whether the configured resource is used to receive a PRACH that is repeatedly transmitted.
- a terminal in a fifth aspect, includes a processor and a memory, the memory stores programs or instructions that can run on the processor, and when the programs or instructions are executed by the processor, the following The steps of the method in one aspect.
- a terminal including a processor and a communication interface, wherein the processor is configured to obtain resource configuration information for repeated transmission of a physical random access channel PRACH, and the resource configuration information indicates the repeated transmission of the PRACH The configured resource; determine whether the configured resource is used for PRACH repeated transmission.
- a network-side device in a seventh aspect, includes a processor and a memory, the memory stores programs or instructions that can run on the processor, and the programs or instructions are executed by the processor When realizing the steps of the method as described in the third aspect.
- a network side device including a processor and a communication interface, wherein the processor is configured to determine configuration resources for repeated transmission of the PRACH; and determine whether the configuration resources are used to receive the PRACH for repeated transmission.
- a system for determining PRACH repeated 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 repeated transmission resources as described in the first aspect, and the network The side device may be configured to perform the steps of the method for determining PRACH repeated transmission resources as described in the third aspect.
- a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method as described in the first aspect are implemented, or the The steps of the method described in the third aspect.
- a chip in an eleventh aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or an instruction to implement the method described in the first aspect. method, or implement the method as described in the third aspect.
- a computer program/program product is provided, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement the The steps of the method for determining PRACH repeated transmission resources, or the steps for realizing the method for determining PRACH repeated transmission resources as described in the third aspect
- the terminal acquires configuration resources for PRACH repeated transmission, and determines whether the configuration resources are actually used for PRACH repeated transmission, so that the terminal uses the configuration resources that can actually be used for PRACH repeated transmission to perform PRACH repeated transmission, which can Reduce random access delay.
- FIG. 1 is a block diagram of a wireless communication system to which an embodiment of the present application is applicable;
- FIG. 2 is a schematic diagram of an RO in which SSB is mapped to FDM according to an embodiment of the present application
- FIG. 3 is a schematic diagram of an RO where SSB is mapped to TDM/FDM according to an embodiment of the present application
- FIG. 4 is one of the schematic flowcharts of a method for determining PRACH repeated transmission resources according to an embodiment of the present application
- Fig. 5 is one of the RO processing methods of the embodiment of the present application.
- Figure 6 is the second RO processing method of the embodiment of the present application.
- Figure 7 is the third RO processing method of the embodiment of the present application.
- FIG. 8 is the fourth RO processing method of the embodiment of the present application.
- FIG. 9 is the fifth RO processing method of the embodiment of the present application.
- FIG. 10 is a second schematic flow diagram of a method for determining PRACH repeated transmission resources according to an embodiment of the present application.
- FIG. 11 is one of the schematic structural diagrams of an apparatus for determining PRACH repeated transmission resources according to an embodiment of the present application.
- FIG. 12 is a second structural schematic diagram of an apparatus for determining PRACH repeated transmission resources according to an embodiment of the present application.
- FIG. 13 is a schematic structural diagram of a communication device according to an embodiment of the present application.
- FIG. 14 is a schematic structural diagram of a terminal according to an embodiment of the present application.
- FIG. 15 is a schematic structural diagram of a network side device according to an embodiment of the present application.
- first, second and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific sequence or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or described herein and that "first" and “second” distinguish objects. It is usually one category, and the number of objects is not limited. For example, there may be one or more first objects.
- “and/or” in the description and claims means at least one of the connected objects, and the character “/” generally means that the related objects are an "or” relationship.
- LTE Long Term Evolution
- LTE-Advanced LTE-Advanced
- LTE-A Long Term Evolution-Advanced
- CDMA Code Division Multiple Access
- TDMA Time Division Multiple Access
- FDMA Frequency Division Multiple Access
- OFDMA Orthogonal Frequency Division Multiple Access
- SC-FDMA Single-carrier Frequency Division Multiple Access
- system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used for the above-mentioned system and radio technology, and can also be used for other systems and radio technologies.
- NR New Radio
- the following description describes the New Radio (NR) system for illustrative purposes, and uses NR terminology in most of the following descriptions, but these techniques can also be applied to applications other than NR system applications, such as the 6th generation (6 th Generation, 6G) communication system.
- 6G 6th Generation
- Fig. 1 shows a block diagram of a wireless communication system to which the embodiment of the present application is applicable.
- the wireless communication system includes a terminal 11 and a network side device 12 .
- the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a palmtop computer, a netbook, a super mobile personal computer (Ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), augmented reality (augmented reality, AR) / virtual reality (virtual reality, VR) equipment, robot, wearable device (Wearable Device) , Vehicle User Equipment (VUE), Pedestrian User Equipment (PUE), smart home (home equipment with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.), game consoles, personal computers (personal computer, PC), teller machine or self-service machine and other terminal side devices, wearable devices include: smart watches, smart
- the network side device 12 may include an access network device or a core network device, where the access network device may also be called a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function, or a wireless network. access network unit.
- the access network equipment may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point, or a WiFi node, etc., and the base station may be called a node B, an evolved node B (Evolved Node B, eNB), an access point, or a base station.
- BTS Base Transceiver Station
- BSS Basic Service Set
- ESS Extended Service Set
- Home Node B Home Evolved Node B
- TRP Transmitting Receiving Point
- TRP Transmitting Receiving Point
- the random access procedure may be a contention-based random access procedure or a non-contention-based random access procedure.
- the random access process may be a four-step random access process (also called a Type-1 random access process) or a two-step random access process (also called a Type-2 random access process).
- the UE first sends Msg1 to the network side device, including the preamble sequence (preamble); after the network detects the preamble, it will send Msg2/Random Access Response (Random Access Response, RAR) message, Contains the number of the preamble detected by the network side device, and the uplink wireless 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 is the same as the number of the preamble sent by itself If they are consistent, send Msg3 containing contention resolution information according to the resource indicated by RAR; after receiving Msg3, the network side device will send Msg4 containing contention resolution information; UE receives Msg4, confirms the resolution information and sends it in Msg3 , that is, complete 4-step random access.
- Msg2/Random Access Response Random Access Response
- the network side device contains uplink grant (UpLink grant, UL grant) information in the RAR to indicate Msg3 physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) scheduling information, and contains random access preamble identification (RACH preamble ID , RAPID), temporary cell radio network temporary identifier (Temporary Cell Radio Network Temporary Identifier, TC-RNTI), timing advance (Timing Advance, TA) and other information. If the network side device does not receive the Msg3 PUSCH, it can schedule the retransmission of the Msg3 PUSCH in the physical downlink control channel (Physical downlink control channel, PDCCH) scrambled by the TC-RNTI.
- UpLink grant, UL grant Msg3 physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) scheduling information
- RAPID random access preamble identification
- TC-RNTI Temporary Cell Radio Network Temporary Identifier
- Timing Advance Timing Advance
- the network side device can only solve the PUSCH sent by one UE (including contention resolution information) on one Msg3 PUSCH scheduling resource, so the network side device will include it in Msg4 and receive it in Msg3 received competition resolution information. If the contention resolution information received by the UE in Msg4 matches the contention resolution information sent by the UE in Msg3 PUSCH, the UE considers the contention resolution to be successful. If there is no match, the contention resolution is considered unsuccessful.
- the first step is that the UE sends MsgA to the network side. After receiving MsgA, the network side sends a MsgB message to the UE. If the UE does not receive MsgB within a certain period of time, the UE will add up the counter counting the number of times MsgA is sent and resend MsgA. If the counter for counting the number of times MsgA is sent reaches a certain threshold, the UE will switch from the 2-step random access process to the 4-step random access process. MsgA includes the MsgA preamble part and the MsgA PUSCH part.
- the preamble part is sent on the RO for 2-step RACH
- the PUSCH part is sent on the MsgA PUSCH resource associated with sending the MsgA preamble and the RO.
- the MsgA PUSCH resource is a group of PUSCH resources configured for each physical random access channel slot (PRACH slot), including time-frequency resources and demodulation reference signal (Demodulation Reference Signal, DMRS) resources.
- PRACH slot physical random access channel slot
- DMRS demodulation Reference Signal
- a cell can configure multiple Frequency Division Multiplex (FDM) physical random access channel transmission opportunities (PRACH transmission occasion), or PRACH Occasion, at a time domain position where PRACH is transmitted.
- FDM Frequency Division Multiplex
- PRACH transmission occasion physical random access channel transmission opportunities
- PRACH Occasion PRACH Occasion
- the number of ROs that can perform FDM can be: ⁇ 1, 2, 4, 8 ⁇ .
- FIG. 2 at a moment, there are 8 RO resources distributed on different frequencies.
- the random access preamble can only be transmitted on the time domain resource (ie RO resource) configured by the parameter PRACH configuration index (PRACHConfigurationIndex), and the random access preamble can only be transmitted on the frequency domain resource configured by the parameter prach-FDM.
- PRACH Frequency domain resource n RA ⁇ 0,1,...M-1 ⁇ , where M is equal to the higher layer parameter prach-FDM.
- the PRACH frequency domain resource n RA is numbered in ascending order from the RO resource with the lowest frequency in the initial active uplink bandwidth part; otherwise, the PRACH frequency domain resource n RA starts from the activated uplink bandwidth part (active uplink bandwidth part).
- the RO resources with the lowest frequency in bandwidth part) are numbered in ascending order. As shown in FIG. 2 , the RO resources are numbered as RO#0 to RO#7 in sequence from low to high in frequency.
- One SSB may be associated with multiple ROs, or multiple SSBs may be associated with one RO (in this case, different SSBs correspond to different Preamble codes).
- the base station can use different beams to send different SSBs, and the corresponding UE sends Preamble on the RO associated with the SSB.
- the UE selects the SSB associated with the good signal according to the strength of the received downlink beam/SSB.
- RO/"RO and preamble combination send Msg1.
- the network side device can determine the SSB selected by the UE according to the received Preamble RO/"RO and preamble combination".
- Msg2 is sent to ensure the reception quality of the downlink signal.
- the number of FDM ROs at a time is 8, and the number of SSBs actually transmitted is 4, namely SSB#0, SSB#1, SSB#2, and SSB#3, and each SSB is associated with 2 RO. 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 the PRACH.
- the number of FDM ROs at a time is 2, and the number of SSBs actually transmitted is 8, that is, SSB#0, SSB#1, ..., SSB#7, and every 2 SSBs are associated with 1 RO.
- the preamble sets associated with the multiple SSBs are different, that is, the same preamble cannot belong to the preamble sets associated with different SSBs at the same time.
- RO#0 in FIG. 3 there are 60 preambles associated with SSB, among which the preamble with index 0-29 is associated with SSB#0, and the preamble with index 30-59 is associated with SSB#1.
- each grid in FIG. 3 is used to represent ROs instead of SSBs, and the indicated SSBs refer to which/which SSBs the RO is associated with.
- the UE Before the UE sends PRACH, it first performs resource selection. First, according to the received beam (beam) or SSB Reference Signal Received Power (Reference Signal Received Power, RSRP), select the SSB whose RSRP is higher than the threshold; if there are multiple SSB RSRP Above this threshold, the UE can select any SSB with an RSRP above the threshold; if there is no SSB with an RSRP above the threshold, the UE selects an SSB based on implementation.
- beam beam
- RSRP Reference Signal Received Power
- the UE Based on the configuration of the network (Network, NW), the UE obtains the correspondence between the SSB and the RO; after selecting the SSB, the RO corresponding to the selected SSB is used as the RO for sending the PRACH/Preamble. If the selected SSB is associated with multiple ROs, the terminal can select one of the ROs for PRACH/Preamble transmission.
- NW Network, NW
- the UE selects a preamble from the preamble set associated with the selected SSB to send the PRACH.
- a preamble As shown in Figure 3, one RO is associated with two SSBs, then in the available Preamble set associated with the SSB in an RO, the preamble will be divided into two subsets, and each subset corresponds to an SSB. The UE will select a certain preamble sequence in the preamble subset corresponding to the selected SSB for PRACH transmission.
- the association between SSB and PRACH resources includes SSB to PRACH occasion mapping cycle (the mapping period from SSB to PRACH occasion), SSB to PRACH occasion mapping association period (the mapping association period from SSB to PRACH occasion), and SSB to PRACH occasion association pattern period (mapping pattern period from SSB to PRACH occasion).
- the purpose of these cycle times is mainly to be able to complete at least one random access attempt within a predefined period of time and to repeat the mapping between PRACH resources and SSBs in a certain pattern.
- PRACH repetition needs to ensure that such a pattern cannot be broken.
- the association pattern period consists of one or more association periods and is determined such that the pattern between PRACH occasions and SS/PBCH block indexes (SSB indexes) repeats at most every 160 milliseconds. PRACH occasions (if any) that are not associated with an SS/PBCH block index after an integer number of association periods are not used for PRACH transmission.
- SSB indexes SS/PBCH block indexes
- the MsgA PUSCH occasion does not overlap in time and frequency with any valid PRACH occasions related to the first type random access procedure or the second type random access procedure, then the MsgA PUSCH occasion is valid. This means that when PRACH and MsgA PUSCH resources overlap, PRACH is transmitted instead of MsgA PUSCH.
- UE For operation on a single carrier in an unpaired spectrum (for example, Time Division Duplex (TDD)), if the UE is configured by a higher layer to be in a certain slot (slot) Receive PDCCH, physical downlink shared channel (PDSCH), channel state information reference signal (Channel State Information Reference Signal, CSI-RS) or downlink positioning reference signal (DL Positioning Reference Signal, DL- PRS), if the UE does not detect the downlink control information (Downlink Control Information, DCI) format indicating that the UE sends PUSCH, PUCCH, PRACH or SRS in at least one symbol in this group of symbol sets, then the UE receives PDCCH, PDSCH, CSI-RS or DL-PRS, otherwise the UE does not receive PDCCH, PDSCH, CSI-RS or DL-PRS.
- DCI Downlink Control Information
- UE For operation on a single carrier in an unpaired spectrum, if the UE is configured by a higher layer to send a sounding reference signal (Sounding Reference Signal, SRS), physical uplink control channel (Physical Uplink Control Channel) in a group of symbols in a slot Channel, PUCCH), PUSCH or PRACH, and the UE detects the DCI format indicating that the UE receives CSI-RS or PDSCH from a subset of the group of symbols, then:
- SRS Sounding Reference Signal
- Physical Uplink Control Channel Physical Uplink Control Channel
- PUCCH Physical Uplink Control Channel
- the UE does not have the capability of "partialCancellation"
- the UE detects the DCI format control resource set (Control resource set, CORESET), the time interval between the last symbol of CORESET) does not exceed T proc,2 , then the UE does not expect to cancel the transmission of PUCCH or PUSCH or PRACH in this set; otherwise, the UE cancels the PRACH transmission, or decides according to the relevant agreement Cancel the transmission of PUCCH, PUSCH, or actual repetition of PUSCH.
- the UE has the capability of "partialCancellation" if there is a part of symbols in the set (a group of symbols for sending SRS, PUCCH, PUSCH or PRACH) and the UE detects the distance between the last symbol of CORESET in DCI format If the time interval does not exceed T proc,2 , the UE does not expect to cancel the transmission of PUCCH, PUSCH or PRACH on this part of symbols; for symbols outside this part of symbols, the UE cancels PRACH transmission, or decides to cancel PUCCH, PUSCH or PRACH according to relevant agreements The actual repeated transmission of PUSCH.
- both RACH Occasion (ie, RO) and PRACH Occasion refer to the time-frequency resources required for sending a PRACH sequence, that is, both RACH Occasion and PRACH Occasion can be represented by RO.
- the embodiment of the present application provides a method for determining PRACH repeated transmission resources, which is applied to a terminal, and the method includes:
- step 401 the terminal acquires resource configuration information for repeated transmission of a physical random access channel (PRACH), where the resource configuration information indicates configuration resources for repeated transmission of the PRACH.
- PRACH physical random access channel
- the definition of the PRACH repeated transmission is different from that of the PRACH retransmission.
- the PRACH repetition in the embodiment of the present application refers to the repeated transmission during each PRACH initial transmission or retransmission process, and the PRACH repetition only occurs in random access. before the RAR window ends.
- the resource configuration information for the repeated transmission of the PRACH may be configured by the network side device, that is, the network side device configures resources for the repeated transmission of the PRACH for the terminal.
- the configured resource refers to the resource configured by the network side device for the terminal for PRACH repetition transmission, not necessarily the transmission resource actually used by the terminal for PRACH repetition transmission.
- PRACH repetition resources refer to PRACH resources used to send PRACH repetition; PRACH resources that do not support PRACH repetition refer to PRACH resources used to send PRACH but do not perform repetition.
- the PRACH resources may be PRACH time-frequency resources and/or PRACH sequences.
- Step 402 the terminal determines whether the configured resources are used for repeated transmission of the PRACH.
- the terminal acquires configuration resources configured for it by the network side device according to the resource configuration information, and determines whether the configuration resources are actually used for PRACH repeated transmission.
- the terminal acquires configuration resources for PRACH repeated transmission, and determines whether the configuration resources are actually used for PRACH repeated transmission, so that the terminal uses the configuration resources that can actually be used for PRACH repeated transmission to perform PRACH repeated transmission, which can reduce Random access delay.
- the determining whether the configuration resource is used for PRACH repeated transmission includes at least one of the following:
- the terminal can determine whether the configuration resource can actually be used for PRACH repeated transmission.
- the method may further include:
- the validity of the configuration resource is related to the first gap requirement and/or time division multiplexing TDD uplink and downlink configuration
- the first gap requirement is a gap requirement between SSB transmission, a symbol set used for SSB transmission, and a symbol set used for PRACH transmission.
- the method for verifying the validity of the configured resource can be the same as the method for verifying the validity of the PRACH resource that does not perform repeated transmission in the prior art, that is Whether the configured 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.
- the validity verification rules of the configuration resources should be the same in the two cases of PRACH transmission, so the verification rules of PRACH non-repeated transmission can be used to verify Validity of configuration resources in this embodiment of the application.
- the PRACH occasion in the PRACH slot is valid in the following cases:
- the candidate SS/PBCH block index of the SS/PBCH block corresponds to the SS/PBCH block index provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon.
- the determining whether the configured resource is used for PRACH repeated transmission according to the validity of the configured resource includes at least one of the following:
- the configured resources include RO resources configured for PRACH repeated transmission.
- the first RO is an RO used only for repeated transmission of the PRACH, and the first RO may include one or more ROs.
- the determining whether the first RO is used for PRACH repeated transmission according to 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 for repeated transmission of the PRACH.
- the first target RO may refer to one or more ROs in the first RO.
- the RO For an RO that is only used for PRACH repeated transmission, if the RO is invalid, the RO will be discarded and cannot It is used for repeated transmission of PRACH. Wherein, when the first target RO is invalid and discarded, the first target RO may not be counted, or the first target RO may be counted. Instructions are given below.
- the method further includes: postponing the first target RO by a RO-level time domain position to obtain a second target RO, where the second target RO is used for repeated transmission of the PRACH.
- the configuration resources include a public RO and a first RO
- the public RO is used for the first PRACH repetition
- the first RO includes RO0, RO1, RO2, RO3 for the PRACH repetition
- RO0, RO1 , RO2, and RO3 respectively
- two PRACH repetitions can be performed respectively, among which, 1 RO0 and 1 RO1 are invalid due to overlapping with SSB transmission (that is, 1 RO0 and 1 RO1 on the right side in Figure 5 are the The first target RO)
- the invalid RO0 and RO1 will be postponed by one RO, so as to ensure that there are corresponding additional two ROs for sending PRACH repetitions, and ensure that the number of configured PRACH repetitions remains unchanged.
- the first target RO is included in the number of ROs repeatedly transmitted on the PRACH.
- the first target RO when the first target RO is invalid, the first target RO is discarded, but the first target RO is still counted.
- the first RO configured only for repeated PRACH transmission, as long as the common RO is valid (or the common RO is valid but not actually used for PRACH repeated transmission), the first RO will be mapped to the common RO, if the first If one or more of the ROs are invalid, the invalid first RO is discarded, but it will still be counted.
- the common RO is a commonly configured RO (also called a shared RO) used by the PRACH repeated transmission and the PRACH non-repeated transmission.
- the configuration resources include a public RO and a first RO
- the public RO is used for the first PRACH repetition
- the first RO includes RO0, RO1, RO2, RO3 for the PRACH repetition
- RO0, RO1 , RO2, and RO3 respectively
- two PRACH repetitions can be performed respectively, among which, 1 RO0 and 1 RO1 are invalid due to overlapping with SSB transmission (that is, 1 RO0 and 1 RO1 on the right side in Figure 6 are described
- the first target RO is discarded without extension, then the PRACH transmission in RO0 and RO1 can only be repeated twice (including the first repetition on the left), and the PRACH transmission in RO2 and RO3 is repeated because all RO Both are valid and can be repeated 3 times (including the first repetition on the left).
- the public RO is associated with the corresponding first RO.
- RO0 in the public RO on the left is associated with two RO0s in the first RO on the right
- RO1 in the public RO on the left is associated with two RO1s on the right
- other ROs By analogy, it will not be repeated here.
- the determining whether the first RO in the configured resource is used for PRACH repeated transmission according to the validity of the common RO in the configured resource includes at least one of the following:
- the first public RO may refer to one or more of the public ROs, and if the first public RO is invalid, the first RO associated with the first public RO is discarded , not used for PRACH repeated transmission.
- the configuration resources include a public RO and a first RO
- the public RO is used for the first PRACH repetition
- the first RO includes RO0, RO1, RO2, RO3 for the PRACH repetition
- RO0, RO1 , RO2, and RO3 respectively
- two PRACH repetitions can be performed respectively.
- two public ROs (RO2 and RO3 on the left) conflict with the PDSCH scheduled by the dynamic grant in the downlink
- the two public ROs The associated extra configured first ROs (2 RO2 and 2 RO3 on the right) are discarded without actual transmission, and no actual PRACH repetition transmission is performed.
- some public ROs in the configured resources may be valid, but due to conflicts with other resources or being configured as unavailable, the effective public ROs are not used for actual PRACH repeated transmission, then the public ROs associated with the The first RO is not used for actual PRACH retransmission.
- a specific embodiment is shown in FIG. 7 , which will not be repeated here.
- the configuration resources include public ROs and first ROs
- the public ROs are used for the first PRACH repetition
- the first ROs include RO0, RO1, RO2, and RO3 for PRACH repetitions
- RO0, RO1 , RO2, and RO3 respectively
- two PRACH repetitions can be performed respectively.
- two public ROs (RO2 and RO3 on the left) conflict with the PDSCH scheduled by the dynamic grant in the downlink
- the two public ROs The associated additionally configured first ROs (2 RO2 and 2 RO3 on the right) are still used for PRACH repeated transmission, ie not discarded.
- the first RO associated with the first public RO is still used for PRACH repeated transmission, as shown in FIG. 8, where I won't go into details.
- the configured resource is used for actual PRACH repeated transmission, for example, when PRACH repetition conflicts with other resources, some PRACH repetition can be discarded so as to ensure other high Priority signals can be sent or received on time; or, in order to ensure the actual number of PRACH repetitions, the PRACH occasion for repetition is postponed, skipping invalid or not actually sending PRACH ROs; or, even if the first repetition
- the resource is invalid or the PRACH is not actually sent, and the PRACH resources of subsequent repetitions can continue to send the remaining PRACH repetitions to reduce the delay of random access.
- the determining whether the configuration resource is used for PRACH repeated transmission according to the configuration information of the symbol where the configuration resource is located includes at least one of the following:
- the symbol of the third target RO in the first RO is configured as a flexible symbol in the common TDD uplink and downlink configuration information (tdd-UL-DL-configurationCommon), in the dedicated TDD uplink and downlink configuration information (tdd- UL-DL-ConfigurationDedicated) is configured as a downlink, then it is determined that the third target RO is not used for PRACH repeated transmission; wherein, the first RO is an RO in the configuration resource that is only used for PRACH repeated transmission.
- the third target RO is one or more of the first ROs that are only used for repeated transmission of the PRACH. If the additionally configured RO for sending PRACH repetition (for example, the third target RO in the first RO) is configured as a flexible symbol (flexible) in tdd-UL-DL-configurationCommon, in tdd-UL-DL - if DL is configured in ConfigurationDedicated, the third target RO is not used for repeated PRACH transmission.
- the symbol of the third target RO in the first RO is configured as a flexible symbol in the common TDD uplink and downlink configuration information, and is configured as a downlink in the DCI format, then it is determined that the third target RO is not used for PRACH Repeat transmission.
- the DCI format may be DCI format2-0, if the additionally configured RO for sending PRACH repetition (for example, the third target RO in the first RO) is located in the tdd-UL-DL- It is configured as flexible in configurationCommon, and is indicated as DL in DCI format2-0, and the RO is not used for PRACH repeated transmission.
- the first configuration information includes: at least one of common TDD uplink and downlink configuration information (tdd-UL-DL-configurationCommon), dedicated TDD uplink and downlink configuration information (tdd-UL-DL-ConfigurationDedicated) and DCI format item;
- the downlink signal is, for example: PDCCH, PDSCH, and the DCI format is, for example, DCI format2-0; that is, if the additionally configured RO for sending PRACH repetition (for example, 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 (that is, the symbol where RO is located), then the The third target RO is not used for PRACH repeated transmission.
- the additionally configured RO for sending PRACH repetition for example, the third target RO in the first RO
- the downlink signal is received on the above symbol (that is, the symbol where RO is located)
- the The third target RO is not used for PRACH repeated transmission.
- This embodiment determines whether the configuration information is actually used for PRACH repeated transmission based on the configuration information of the symbol where the configuration resource is located, and provides the use scheme of the transmission resource of the UE under different configurations, which can ensure the configuration resource and reduce the Delay for random access.
- the determining whether the configured resource is used for PRACH repeated transmission according to the conflict between the configured resource and other signal resources includes at least one of the following:
- the fourth target RO may be one or more ROs in the first RO that are only used for repeated PRACH transmission.
- the first uplink information may be MsgA of a random access procedure. That is: for an additionally configured RO for sending PRACH repetition (for example, the fourth target RO), if the RO overlaps at least part of the MsgA PUSCH transmission, the RO is not used for PRACH repetition.
- MsgA PUSCH since UEs that do not support PRACH repetition may not read and recognize additionally configured ROs for sending PRACH repetition, this means that MsgA PUSCH must be prioritized over individual ROs configured for PRACH repetition, that is, MsgA PUSCH has priority in the transmission of the fourth target RO.
- some PRACH repetitions are discarded to protect MsgA PUSCH, which may not cause PRACH reception failure, but can ensure timely transmission of MsgA PUSCH.
- the DCI format information indicates that the terminal performs PRACH repeated transmission in the fourth target RO, and the fourth target RO is the same as the time slot where the time slot is located. If at least one symbol in the symbol set overlaps, it is determined that the fourth target RO is not used for PRACH repeated transmission.
- the UE for the operation on a single carrier in the unpaired frequency spectrum, if the UE is configured by the high layer to receive downlink signals such as PDCCH, PDSCH, CSI-RS or DL PRS in a group of symbols in a time slot, the UE receives Downlink signals such as PDCCH, PDSCH, CSI-RS or DL PRS, even if the UE detects the DCI format, the DCI format instructs the UE to send PRACH repetition in an additionally configured RO (for example, the fourth target RO), and the additionally configured RO ( For example, the fourth target RO) overlaps with at least one symbol of the symbol set of the time slot, and the UE does not perform PRACH repeated transmission on the fourth target RO, but receives the downlink signal on the symbols of the time slot.
- RO for example, the fourth target RO
- the fourth target RO overlaps with at least one symbol of the symbol set of the time slot
- the priority of downlink signal reception is higher than that of PRACH repeated transmission
- related protocols can refer to corresponding modifications, for example:
- the UE For operation on a single carrier in an unpaired spectrum, if the UE is configured by the high layer to receive downlink signals such as PDCCH, PDSCH, CSI-RS or DL PRS in a group of symbols in a time slot, if the UE does not detect If the DCI format of PUSCH, PUCCH, PRACH non-repetition or SRS is sent in at least one symbol of the symbol set of the slot, the UE receives PDCCH, PDSCH, CSI-RS or DL-PRS; If the DCI format of the PRACH is specified, the UE does not receive downlink signals such as PDCCH, PDSCH, CSI-RS or DL-PRS in the symbol set of the slot.
- downlink signals such as PDCCH, PDSCH, CSI-RS or DL PRS
- a UE 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, a PUCCH, a PRACH 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).
- the fourth target RO is not used for PRACH repeated transmission.
- the UE for the operation on a single carrier in the unpaired frequency spectrum, if the UE is configured by the higher layer to send PRACH repetition , and the UE detects a DCI format indicating that the UE receives a downlink signal (such as CSI-RS or PDSCH) in the symbol subset from the group of symbols, then the UE does not perform PRACH retransmission in the fourth target RO, but in the fourth target RO. Receive downlink signals in a subset of the target symbols.
- the fourth target RO is not used for PRACH repeated transmission, but still counts corresponding PRACH repeated transmissions.
- the configured resources are used for PRACH repeated transmission, and when PRACH repetitions conflict with other resources, some PRACH repetitions can be discarded so as to ensure other high priority Level signals can be sent or received on time, reducing the delay of random access.
- the method further includes: determining the power allocation priority of the PRACH repeated transmission;
- the power allocation priority of the PRACH that performs repeated transmission is lower than the power allocation priority of the PRACH that does not perform repeated transmission on the primary cell (PCell).
- the repeatedly transmitted PRACH will be assigned power with a low priority relative to other uplink signals sent simultaneously during the carrier aggregation process, and related protocols can introduce corresponding modifications, for example:
- the total UE transmit power in a slot symbol is defined as the linear sum of the UE transmit power of PUSCH, PUCCH, PRACH and SRS in a slot symbol (The total UE transmit power in a symbol of a slot is defined as the sum of the linear values of UE transmit powers for PUSCH, PUCCH, PRACH, and SRS in the symbol of the slot).
- PRACH transmission without repetition on the Pcell PRACH transmission without repetition on the Pcell
- HARQ-ACK hybrid automatic repeat request acknowledgment
- SR scheduling request
- Link recovery request LRR
- PUCCH transmission with CSI or PUSCH transmission with CSI PUCCH transmission with CSI or PUSCH transmission with CSI (PUCCH transmission with CSI or PUSCH transmission with CSI);
- PUSCH transmission without HARQ-ACK information or CSI, for Type-2 random access procedure, PUSCH transmission on Pcell PUSCH transmission without HARQ-ACK information or CSI and, for Type-2 random access procedure, PUSCH transmission on the Pcell );
- SRS transmission with aperiodic SRS having higher priority than semi-persistent and/or periodic SRS, or PRACH transmission on a serving cell other than Pcell or PRACH repeated transmission (SRS transmission, with aperiodic SRS having higher priority than semi-persistent and/or periodic SRS, or PRACH transmission on a serving cell other than the Pcell or PRACH repetition transmissions).
- the power allocation priority of the PRACH that performs repeated transmission is the same as the power allocation priority of the PRACH that does not perform repeated transmission on the primary cell.
- the repeated PRACH will be allocated power with high priority relative to other uplink signals sent simultaneously during the carrier aggregation process.
- Relevant protocols can introduce corresponding modifications, such as:
- the total UE transmit power in a slot symbol is defined as the linear sum of the UE transmit power of PUSCH, PUCCH, PRACH and SRS in a slot symbol (The total UE transmit power in a symbol of a slot is defined as the sum of the linear values of UE transmit powers for PUSCH, PUCCH, PRACH, and SRS in the symbol of the slot).
- PRACH transmission on the Pcell or PRACH repetition transmission PRACH transmission on the Pcell or PRACH repetition transmission
- PUCCH transmission with HARQ-ACK information, and/or SR, and/or LRR, or PUSCH transmission with HARQ-ACK information PUCCH transmission with HARQ-ACK information, and/or SR, and/or LRR, or PUSCH transmission with HARQ-ACK information
- PUCCH transmission with CSI or PUSCH transmission with CSI PUCCH transmission with CSI or PUSCH transmission with CSI (PUCCH transmission with CSI or PUSCH transmission with CSI);
- PUSCH transmission without HARQ-ACK information or CSI, for Type-2 random access procedure, PUSCH transmission on Pcell PUSCH transmission without HARQ-ACK information or CSI and, for Type-2 random access procedure, PUSCH transmission on the Pcell );
- aperiodic SRS has higher priority than semi-persistent and/or periodic SRS, or PRACH transmission on serving cells other than Pcell (SRS transmission, with aperiodic SRS having higher priority than semi-persistent and/or periodic SRS, or PRACH transmission on a serving cell other than the Pcell).
- the power allocation priority of the repeated transmission of the PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on the primary cell;
- the power allocation priority of the repeated transmission of the PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on the non-primary cell;
- the power allocation priority of the PRACH that performs repeated transmission is the same as the power allocation priority of the PRACH that does not perform repeated transmission on the non-primary cell.
- the repeated transmission of the PRACH is completed within the first duration
- the first duration includes at least one of the following:
- a time value corresponding to the random access response window; the maximum value of the random access response window may be 10ms;
- the association mode period of the RO of repeated transmission from SSB to PRACH; the association mode period of the RO of repeated transmission from SSB to PRACH may be additionally configured for the repeated transmission of PRACH.
- M, N, L are positive integers.
- the specific values of M, N, and L may be defined by a protocol or configured by a system message.
- the RO-associated mode period of SSB to PRACH repeated transmission which may include one or more SSB-to-RO associated mode periods, so that the PRACH repeats the mode between RO and SSB at most at each predetermined time Repeated periodically (eg, every 640ms).
- the predetermined time period may be a positive integer multiple of the RO association mode period from the SSB to the (existing, single-transmission) PRACH.
- an RO configured with 4 repeated transmissions
- the first 3 repeated transmissions are within the associated mode cycle from SSB to RO
- the fourth repeated transmission occurs within the next associated mode cycle from SSB to RO, then the fourth repetitions will be discarded.
- the RO in FIG. 9 represents the RO configured for the repeated transmission of the PRACH, which may be a common RO or the first RO, which is not limited here.
- the remaining number of repeated PRACH transmissions may be all discarded, or part of the transmission may be completed before the end of the first duration.
- the terminal obtains the configuration resource for PRACH repeated transmission, and determines whether the configuration resource is actually used for PRACH repeated transmission, provides a solution when the configuration resource is invalid or conflicts with other signal resources, and can reduce random access delay. For example: when PRACH repetition conflicts with other resources, part of PRACH repetition can be discarded or the transmission power is not increased to ensure that other high-priority signals can be sent or received on time; or, in order to ensure the actual number of PRACH repetition, it is used for repetition
- the PRACH occasion needs to be postponed backwards, skipping invalid or not actually sending PRACH ROs; or, even if the resources of the first repetition are invalid or are not actually sent PRACH, the PRACH resources of subsequent repetitions can continue to send the remaining PRACH Repetition, reducing the delay of random access.
- the embodiment of the present application also provides a method for determining PRACH repeated transmission resources, which is applied to network side equipment, including:
- Step 101 the network side device determines the configuration resources for PRACH repeated transmission
- Step 102 the network side device determines whether the configured resource is used to receive a PRACH that is repeatedly transmitted.
- the definition of the PRACH repeated transmission is different from that of the PRACH retransmission.
- the PRACH repetition in the embodiment of the present application refers to the repeated transmission during each PRACH initial transmission or retransmission process, and the PRACH repetition only occurs in random access. before the end of the response window.
- the network side device configures resources for repeated transmission of the PRACH for the terminal.
- the configured resource refers to the resource configured by the network side device for the terminal for PRACH repetition transmission, not necessarily the transmission resource actually used by the terminal for PRACH repetition transmission.
- PRACH repetition resources refer to PRACH resources used to send PRACH repetition;
- PRACH resources that do not support PRACH repetition refer to PRACH resources used to send PRACH but do not perform repetition.
- PRACH resources may be PRACH time-frequency resources and/or PRACH sequences
- the terminal determines whether the configured resource is actually used for PRACH repeated transmission, and performs PRACH repeated transmission on the actually transmitted configured resource; then the network side device also needs to determine whether the configured resource is actually used for PRACH repeated transmission based on the rules corresponding to the terminal, And receive the PRACH for repeated transmission on the configured resource for actual transmission.
- the network side device configures resources for PRACH repeated transmission, and determines whether the configured resources are actually used for PRACH repeated transmission, so that the network side device can receive the PRACH for repeated transmission on the configured resources actually used for PRACH repeated transmission , which can reduce the random access delay.
- the method further includes: sending resource configuration information for repeated PRACH transmission to the terminal, where the resource configuration information indicates the configured resource.
- the network side device after the network side device configures the configuration resources for PRACH repeated 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 Repeated transmission, so as to determine the solution when the configuration resources are invalid or conflict with other signal resources, and reduce the random access delay.
- the determining whether the configured resource is used to receive a PRACH for repeated transmission includes at least one of the following:
- the terminal can determine whether the configuration resource can actually be used for PRACH repeated transmission.
- the method may further include:
- the validity of the configured resources is related to the first gap requirement and/or time division multiplexing TDD uplink and downlink configuration;
- the first gap requirement is SSB transmission, used for The gap requirement between the symbol set for SSB transmission and the symbol set for PRACH transmission.
- the method for verifying the validity of the configured resource may be the same as the method for verifying the validity of the PRACH resource that does not perform repeated transmission in the prior art, that is, configure Whether resources are available 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.
- the validity verification rules of the configuration resources should be the same in the two cases of PRACH transmission, so the verification rules of PRACH non-repeated transmission can be used to verify Validity of configuration resources in this embodiment of the application.
- the manner of determining the validity of the configured resource is not limited here.
- the determining whether the configured resource is used to receive a PRACH for repeated transmission according to the validity of the configured resource includes at least one of the following:
- the configured resources include RO resources configured for PRACH repeated transmission.
- the first RO is an RO used only for repeated transmission of the PRACH, and the first RO may include one or more ROs.
- it is determined whether the RO can actually be used for PRACH repeated transmission that is, whether the network side device needs to receive the repeated transmission of PRACH on the first RO.
- the determining whether the configuration resource is used to receive the PRACH for repeated transmission according to 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 repeated transmission of the PRACH.
- the first RO is an RO only used for repeated transmission of the PRACH.
- the first target RO may refer to one or more ROs in the first RO.
- the RO For an RO that is only used for PRACH repeated transmission, if the RO is invalid, the RO will be discarded and cannot It is used for repeated transmission of PRACH. Wherein, when the first target RO is invalid and discarded, the first target RO may not be counted, or the first target RO may be counted. Instructions are given below.
- the method further includes: determining a time-domain position of a second target RO, where the second target RO is obtained by delaying the first target RO by a time-domain position of an RO level, and the second target RO PRACH for receiving repeated transmissions.
- the first target RO when the first target RO is invalid, the first target RO is not counted, and the invalid first target RO can be postponed to obtain a new valid second target RO, thereby ensuring the effective number of PRACH repetitions.
- the first target RO when the first target RO is invalid, the first target RO is not counted, and the invalid first target RO can be postponed to obtain a new valid second target RO, thereby ensuring the effective number of PRACH repetitions.
- the first target RO is included in the number of ROs repeatedly transmitted on the PRACH.
- the first target RO when the first target RO is invalid, the first target RO is discarded, but the first target RO is still counted.
- the first RO will be mapped to the common RO, if the first If one or more of the ROs are invalid, the first invalid RO is discarded, but still counted, as shown in FIG. 6 for example, and will not be described here.
- the common RO is the common configuration used for the repeated transmission of the PRACH and the non-repeated transmission of the PRACH the RO.
- the determining whether the configuration resource is used to receive the PRACH for repeated transmission according to the validity of the common RO in the configuration resource includes at least one of the following:
- the first public RO may refer to one or more of the public ROs, and if the first public RO is invalid, the first RO associated with the first public RO is discarded , not used for repeated transmission of the PRACH, then the network side device does not need to receive the repeated transmission of the PRACH in the first RO associated with the first common RO.
- some public ROs in the configured resources may be valid, but due to conflicts with other resources or being configured as unavailable, the effective public ROs are not used for actual PRACH repeated transmission, then the public ROs associated with the The first RO is not used for actual repeated transmission of the PRACH, and the first RO associated with the first common RO is not used for receiving the PRACH for repeated transmission.
- the first RO associated with the first public RO is still used for PRACH repeated transmission, and the first RO associated with the first public RO is still used for Receive repeated transmissions of PRACH.
- the first common RO is valid but not actually used for PRACH repeated transmission
- the first RO associated with the first common RO is still used for PRACH repeated transmission
- the first public RO associated with the first public RO is still used to receive the PRACH for repeated transmission.
- the effectiveness of the first RO and/or common RO it is determined whether the configured resource is used for actual PRACH repeated transmission, for example, when PRACH repetition conflicts with other resources, some PRACH repetition can be discarded so as to ensure other high priority Level signals can be sent or received on time; or, in order to ensure the actual number of PRACH repetitions, the PRACH occasion for repetition is postponed, skipping invalid or not actually sending PRACH ROs; or, even if the resources for the first repetition If the PRACH is invalid or has not been actually sent, the PRACH resources of subsequent repetitions can continue to send the remaining PRACH repetitions to reduce the delay of random access.
- the following describes the specific implementation process of determining whether the configured resource is used to receive the PRACH for repeated transmission according to the configuration information of the symbol where the configured resource is located.
- the determining whether the configured resource is used to receive the PRACH for repeated transmission according to the configuration information of the symbol where the configured resource is located includes at least one of the following:
- the symbol of the third target RO in the first RO is configured as a flexible symbol in the public TDD uplink and downlink configuration information, and is configured as a downlink in the dedicated TDD uplink and downlink configuration information, then determine the second The triple target RO is not used to receive the PRACH for repeated transmissions.
- the first RO is an RO in the configuration resource that is only used for repeated transmission of the PRACH.
- the third target RO is one or more of the first ROs that are only used for repeated transmission of the PRACH. If the additionally configured RO for sending PRACH repetition (for example, the third target RO in the first RO) is configured as a flexible symbol (flexible) in tdd-UL-DL-configurationCommon, in tdd-UL-DL - if DL is configured in ConfigurationDedicated, the third target RO is not used for repeated transmission of the PRACH, and the network side device receives the repeated transmission of the PRACH on the third target RO.
- the additionally configured RO for sending PRACH repetition for example, the third target RO in the first RO
- the third target RO is configured as a flexible symbol (flexible) in tdd-UL-DL-configurationCommon, in tdd-UL-DL - - if DL is configured in ConfigurationDedicated
- the third target RO is not used for repeated transmission of the PRACH, and the network side device receives the repeated transmission of the PRACH on the third target RO.
- the symbol of the third target RO in the first RO is configured as a flexible symbol in the common TDD uplink and downlink configuration information, and is configured as a downlink in the DCI format, then it is determined that the third target RO is not used for reception Repeatedly transmitted PRACH.
- the DCI format may be DCI format2-0, if the additionally configured RO for sending PRACH repetition (for example, the third target RO in the first RO) is located in the tdd-UL-DL- configurationCommon is configured as flexible, and is indicated as DL in DCI format2-0, and the third target RO is not used for PRACH repeated transmission, then the third target RO is not used for receiving the PRACH for repeated transmission.
- the additionally configured RO for sending PRACH repetition for example, the third target RO in the first RO
- the third target RO is located in the tdd-UL-DL- configurationCommon is configured as flexible, and is indicated as DL in DCI format2-0, and the third target RO is not used for PRACH repeated transmission, then the third target RO is not used for receiving the PRACH for repeated transmission.
- the first configuration information includes: at least one of public TDD uplink and downlink configuration information, dedicated TDD uplink and downlink configuration information, and DCI format; wherein the first RO is the configuration resource RO used for PRACH retransmission only.
- the downlink signal is, for example: PDCCH, PDSCH, and the DCI format is, for example, DCI format2-0; that is, if the additionally configured RO for sending PRACH repetition (for example, 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 (that is, the symbol where RO is located), then the If the third target RO is not used for repeated transmission of the PRACH, then the third target RO is not used for receiving the PRACH for repeated transmission.
- the additionally configured RO for sending PRACH repetition for example, the third target RO in the first RO
- the downlink signal is received on the above symbol (that is, the symbol where RO is located)
- This embodiment determines whether the configuration information is actually used for PRACH repeated transmission based on the configuration information of the symbol where the configuration resource is located, and provides the use scheme of the transmission resource of the UE under different configurations, which can ensure the configuration resource and reduce the Delay for random access.
- determining whether the configured resource is used to receive a PRACH for repeated transmission according to the conflict between the configured resource and other signal resources includes:
- the fourth target RO in the first RO at least partially overlaps with the transmission resource of the first uplink information in the random access process, it is determined that the fourth target RO is not used to receive the PRACH for repeated transmission.
- the fourth target RO may be one or more ROs in the first RO that are only used for repeated PRACH transmission.
- the first uplink information may be MsgA of a random access procedure. That is: for an additionally configured RO for sending PRACH repetitions (such as the fourth target RO), if the RO overlaps at least partially with the MsgA PUSCH transmission, the RO is not used for PRACH repetition transmission, and the RO is not used for receiving repeated transmissions The Prach.
- MsgA PUSCH since UEs that do not support PRACH repetition may not read and recognize additionally configured ROs for sending PRACH repetition, this means that MsgA PUSCH must be prioritized over individual ROs configured for PRACH repetition, that is, MsgA PUSCH has priority in the transmission of the fourth target RO.
- some PRACH repetitions are discarded to protect MsgA PUSCH, which may not cause PRACH reception failure, but can ensure timely transmission of MsgA PUSCH.
- the DCI format information indicates that the terminal performs PRACH retransmission in the fourth target RO, and the fourth target RO and the time slot If at least one symbol in the set of symbols overlaps, the fourth target RO is not used for repeated transmission of the PRACH. If the high-level signaling notifies the network-side device of the indication information for the terminal, for example, notifying the network-side device that the terminal receives the downlink signal within the symbol, the network-side device can determine that the fourth target RO is not used for Receive repeated transmissions of PRACH.
- the fourth target RO Not used for PRACH retransmission. If the high-level signaling notifies the network side device of the instruction information for the terminal, for example, notifies the network side device that the terminal performs PRACH retransmission in the target symbol on the fourth target RO, then the network side device can determine in combination with the DCI format information, The fourth target RO is not used to receive the PRACH for repeated transmission.
- the configured resources are used for PRACH repeated transmission, and when PRACH repetitions conflict with other resources, some PRACH repetitions can be discarded so as to ensure other high priority Level signals can be sent or received on time, reducing the delay of random access.
- the network side device may also determine a power allocation priority for repeated PRACH transmission, where the power allocation priority includes at least one of the following:
- the power allocation priority of the PRACH that performs repeated transmission is lower than the power allocation priority of the PRACH that does not perform repeated transmission on the primary cell (PCell).
- the power allocation priority of the PRACH that performs repeated transmission is the same as the power allocation priority of the PRACH that does not perform repeated transmission on the primary cell.
- the power allocation priority of the repeated transmission of the PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on the primary cell;
- the power allocation priority of the repeated transmission of the PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on the non-primary cell;
- the power allocation priority of the PRACH that performs repeated transmission is the same as the power allocation priority of the PRACH that does not perform repeated transmission on the non-primary cell.
- the receiving of the PRACH repeated transmission is completed within a first duration
- the first duration includes at least one of the following:
- the association mode period of the RO of repeated transmission from SSB to PRACH; the association mode period of the RO of repeated transmission from SSB to PRACH may be additionally configured for the repeated transmission of PRACH.
- M, N, L are positive integers.
- the specific values of M, N, and L may be defined by a protocol or configured by a system message.
- the RO-associated mode period of SSB to PRACH repeated transmission which may include one or more SSB-to-RO associated mode periods, so that the PRACH repeats the mode between RO and SSB at most at each predetermined time Repeated periodically (eg, every 640ms).
- the predetermined time period may be a positive integer multiple of the RO association mode period from the SSB to the (existing, single-transmission) PRACH.
- the method further includes: sending resource configuration information for repeated PRACH transmission to the terminal, where the resource configuration information indicates the configured resource.
- the network side device after the network side device configures the configuration resources for PRACH repeated transmission, it can send the resource configuration information to the terminal,
- the network side device configures resources for PRACH repeated transmission, and determines whether the configured resources are actually used for PRACH repeated transmission, so that the network side device can receive the PRACH for repeated transmission on the configured resources actually used for PRACH repeated transmission , which can reduce the random access delay.
- the embodiment of the present application provides a solution when the configured resource is invalid or conflicts with other signal resources.
- the PRACH occasion for repetition needs to be postponed, skipping invalid or not actually sending PRACH ROs; or, even if the resources for the first repetition are invalid Or the PRACH is not actually sent, the PRACH resource of the subsequent repetition can continue to send the remaining PRACH repetition, reducing the delay of random access.
- the method for determining the PRACH retransmission resource provided in the embodiment of the present application may be executed by an apparatus for determining the PRACH retransmission resource.
- the method for determining the PRACH repeated transmission resource performed by the device for determining the PRACH repeated transmission resource is taken as an example to describe the device for determining the PRACH repeated transmission resource provided in the embodiment of the present application.
- the embodiment of the present application provides an apparatus 1100 for determining PRACH repeated transmission resources, which is applied to a terminal, including:
- the first obtaining module 1110 is configured to obtain resource configuration information for the repeated transmission of the physical random access channel PRACH, where the resource configuration information indicates the configuration resources for the repeated transmission of the PRACH;
- the first determining module 1120 is configured to determine whether the configured resource is used for PRACH repeated transmission.
- the first determination module includes at least one of the following:
- a first determining unit configured to determine whether the configured resource is used for PRACH repeated transmission according to the validity of the configured resource
- the second determining unit is configured to determine whether the configured resource is used for PRACH repeated transmission according to the configuration information of the symbol where the configured resource is located;
- the third determining unit is configured to determine whether the configured resource is used for PRACH repeated transmission according to the conflict between the configured resource and other signal resources.
- the device also includes:
- a second determining module configured to determine the validity of the configured resources
- the validity of the configured resource is related to the first gap requirement and/or time division multiplexing TDD uplink and downlink configuration
- the first gap requirement is a gap requirement between SSB transmission, a symbol set used for SSB transmission, and a symbol set used for PRACH transmission.
- the first determination unit includes at least one of:
- the first determination subunit is configured to determine whether the first RO is used for PRACH retransmission according to the validity of the first RO in the configuration resource;
- the second determining subunit is configured to determine whether the first RO in the configured resource is used for PRACH repeated transmission according to the validity of the common RO in the configured resource;
- the common RO is a commonly configured RO used by the PRACH repeated transmission and the PRACH non-repeated transmission; the first RO is an RO only used for the PRACH repeated transmission.
- the first determining subunit is specifically configured to:
- the first target RO in the first RO is invalid, it is determined that the first target RO is not used for repeated transmission of the PRACH.
- the device also includes:
- the first processing module is configured to delay the first target RO by an RO-level time domain position to obtain a second target RO, and the second target RO is used for repeated transmission of the PRACH.
- the first target RO is included in the number of ROs repeatedly transmitted on the PRACH.
- the second determining subunit is specifically configured to perform at least one of the following operations:
- first common RO in the common RO is invalid, then determine that the first RO associated with the first common RO is not used for PRACH repeated transmission;
- first common RO among the common ROs is valid but not used for PRACH repeated transmission, determine that the first RO associated with the first common RO is not used for PRACH repeated transmission;
- first common RO among the common ROs is valid but not used for repeated PRACH transmission, determine that the first RO associated with the first common RO is used for repeated PRACH transmission.
- the second determining unit is configured to perform at least one of the following operations:
- the symbol of the third target RO in the first RO is configured as a flexible symbol in the public TDD uplink and downlink configuration information, and is configured as a downlink in the dedicated TDD uplink and downlink configuration information, then determine the third target RO is not used for PRACH repeated transmission;
- the symbol of the third target RO in the first RO is configured as a flexible symbol in the common TDD uplink and downlink configuration information, and is configured as a downlink in the DCI format, it is determined that the third target RO is not used for PRACH repeated transmission ;
- the first configuration information includes: at least one of public TDD uplink and downlink configuration information, dedicated TDD uplink and downlink configuration information, and a DCI format;
- the first RO is an RO in the configuration resource that is only used for repeated transmission of the PRACH.
- the third determining unit is configured to perform at least one of the following operations:
- the fourth target RO in the first RO at least partially overlaps with the transmission resource of the first uplink information in the random access process, it is determined that the fourth target RO is not used for PRACH repeated transmission; the first RO is the The RO in the configuration resource is only used for PRACH repeated transmission;
- the DCI format information indicates that the terminal performs PRACH repeated transmission on the fourth target RO, and the fourth target RO is the same as the symbol set of the time slot At least one symbol overlaps, then it is determined that the fourth target RO is not used for PRACH repeated transmission;
- the high-level signaling indicates that the terminal performs repeated PRACH transmission in the target symbol on the fourth target RO
- the DCI format information indicates that the terminal receives the downlink signal in the symbol subset of the target symbol
- the device also includes:
- a third determining module configured to determine the power allocation priority of the PRACH repeated transmission
- the power allocation priority of the PRACH that performs repeated transmission is lower than the power allocation priority of the PRACH that does not perform repeated transmission on the primary cell;
- the power allocation priority of the PRACH that performs repeated transmission is the same as the power allocation priority of the PRACH that does not perform repeated transmission on the primary cell;
- the power allocation priority of the repeated transmission of the PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on the primary cell;
- the power allocation priority of the repeated transmission of the PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on the non-primary cell;
- the power allocation priority of the PRACH that performs repeated transmission is the same as the power allocation priority of the PRACH that does not perform repeated transmission on the non-primary cell.
- the repeated transmission of the PRACH is completed within the first duration
- the first duration includes at least one of the following:
- M, N, L are positive integers.
- the terminal obtains the configuration resource for PRACH repeated transmission, and determines whether the configuration resource is actually used for PRACH repeated transmission, provides a solution when the configuration resource is invalid or conflicts with other signal resources, and can reduce random access delay.
- the device for determining PRACH retransmission resources provided by the embodiment of the present application can realize each process realized by the method embodiments in Fig. 4-Fig. 9 and achieve the same technical effect. To avoid repetition, details are not repeated here.
- the embodiment of the present application provides an apparatus 1200 for determining PRACH repeated transmission resources, which is applied to network side equipment, including:
- the fourth determination module 1210 is used to determine the configuration resources of PRACH repeated transmission
- the fifth determining module 1220 is configured to determine whether the configured resource is used to receive a PRACH for repeated transmission.
- the fifth determination module includes:
- a fourth determining unit configured to determine whether the configured resource is used to receive a PRACH for repeated transmission according to the validity of the configured resource
- the fifth determination unit is configured to determine whether the configuration resource is used to receive the PRACH for repeated transmission according to the configuration information of the symbol where the configuration resource is located;
- the sixth determining unit is configured to determine whether the configured resource is used to receive the PRACH for repeated transmission according to the conflict between the configured resource and other signal resources.
- the device also includes:
- a sixth determining module configured to determine the validity of the configured resources
- the validity of the configured resource is related to the first gap requirement and/or time division multiplexing TDD uplink and downlink configuration
- the first gap requirement is a gap requirement among the synchronization signal block SSB transmission, the symbol set used for SSB transmission, and the symbol set used for PRACH transmission.
- the fourth determining unit includes at least one of the following:
- the third determining subunit is configured to determine whether the configured resource is used to receive a PRACH for repeated transmission according to the validity of the first RO in the configured resource;
- the fourth determining subunit is configured to determine whether the configuration resource is used to receive the PRACH for repeated transmission according to the validity of the common RO in the configuration resource;
- the common RO is a commonly configured RO used by the PRACH repeated transmission and the PRACH non-repeated transmission; the first RO is an RO only used for the PRACH repeated transmission.
- the third determining subunit is specifically configured to:
- the first target RO in the first RO is invalid, it is determined that the first target RO is not used for receiving PRACH repeated transmission.
- the device also includes:
- the seventh determination module is configured to determine the time domain position of the second target RO, the second target RO is obtained by delaying the first target RO by one RO level time domain position, and the second target RO is used to receive Repeatedly transmitted PRACH.
- the fourth determining subunit is configured to perform at least one of the following operations:
- the first common RO among the common ROs is valid but not used for repeated transmission of the PRACH, determine that the first RO associated with the first common RO is used to receive the PRACH for repeated transmission.
- the fifth determining unit is configured to perform at least one of the following operations:
- the symbol of the third target RO in the first RO is configured as a flexible symbol in the public TDD uplink and downlink configuration information, and is configured as a downlink in the dedicated TDD uplink and downlink configuration information, then determine the third target RO is not used to receive PRACH for repeated transmission;
- the symbol of the third target RO in the first RO is configured as a flexible symbol in the public TDD uplink and downlink configuration information, and is configured as a downlink in the DCI format, it is determined that the third target RO is not used to receive repeated transmission PRACH;
- the first configuration information includes: at least one of common TDD uplink and downlink configuration information, dedicated TDD uplink and downlink configuration information, and DCI formats;
- the first RO is an RO in the configuration resource that is only used for repeated transmission of the PRACH.
- the sixth determination unit is used for:
- the fourth target RO in the first RO at least partially overlaps with the transmission resource of the first uplink information in the random access process, it is determined that the fourth target RO is not used to receive the PRACH for repeated transmission.
- the receiving of the repeated PRACH transmission is completed within a first duration
- the first duration includes at least one of the following:
- M, N, L are positive integers.
- the device also includes:
- the first sending module is configured to send resource configuration information for PRACH repeated transmission to the terminal, where the resource configuration information indicates the configured resource.
- the network side device configures resources for PRACH repeated transmission, and determines whether the configured resources are actually used for PRACH repeated transmission, so that the network side device can receive the PRACH for repeated transmission on the configured resources actually used for PRACH repeated transmission , which can reduce the random access delay.
- the apparatus for determining PRACH retransmission resources provided by the embodiment of the present application can implement various processes implemented by the method embodiment in FIG. 10 and achieve the same technical effect. To avoid repetition, details are not repeated here.
- the apparatus for determining the PRACH retransmission resource in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or a component in the electronic device, such as an integrated circuit or a chip.
- the electronic device may be a terminal, or other devices other than the terminal.
- the terminal may include, but not limited to, the types of terminal 11 listed above, and other devices may be servers, Network Attached Storage (NAS), etc., which are not specifically limited in this embodiment of the present application.
- NAS Network Attached Storage
- this embodiment of the present application also provides a communication device 1300, including a processor 1301 and a memory 1302, and the memory 1302 stores programs or instructions that can run on the processor 1301, such as
- the communication device 1300 is a terminal
- the program or instruction is executed by the processor 1301
- each step of the above-mentioned method embodiment applied to the terminal can be implemented, and the same technical effect can be achieved.
- the communication device 1300 is a network-side device
- the steps of the above-mentioned method embodiments applied to the network-side device can be implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here repeat.
- the embodiment of the present application also provides a terminal, including a processor and a communication interface, and the processor is used to obtain resource configuration information for repeated transmission of a Physical Random Access Channel (PRACH), where the resource configuration information indicates configuration resources for repeated transmission of the PRACH; Determine whether the configured resources are used for PRACH retransmission.
- PRACH Physical Random Access Channel
- This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect.
- FIG. 14 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
- the terminal 1400 includes, but is not limited to: a radio frequency unit 1401, a network module 1402, an audio output unit 1403, an input unit 1404, a sensor 1405, a display unit 1406, a user input unit 1407, an interface unit 1408, a memory 1409, and a processor 1410. At least some parts.
- the terminal 1400 can also include a power supply (such as a battery) for supplying power to various components, and the power supply can be logically connected to the processor 1410 through the power management system, so as to manage charging, discharging, and power consumption through the power management system. Management and other functions.
- a power supply such as a battery
- the terminal structure shown in FIG. 14 does not constitute a limitation on the terminal.
- the terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange different components, which will not be repeated here.
- the input unit 1404 may include a graphics processing unit (Graphics Processing Unit, GPU) 14041 and a microphone 14042, and the graphics processor 14041 can be used by the image capture device (such as the image data of the still picture or video obtained by the camera) for processing.
- the display unit 1406 may include a display panel 14061, and the display panel 14061 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 at least one of a touch panel 14071 and other input devices 14072 . Touch panel 14071, also called touch screen.
- the touch panel 14071 may include two parts, 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 keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here.
- the radio frequency unit 1401 may transmit it to the processor 1410 for processing; in addition, the radio frequency unit 1401 may send the uplink data to the network side device.
- the radio frequency unit 1401 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
- the memory 1409 can be used to store software programs or instructions as well as various data.
- the memory 1409 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required by at least one function (such as a sound playing function, image playback function, etc.), etc.
- memory 1409 may include volatile memory or nonvolatile memory, or, memory 1409 may include both volatile and nonvolatile memory.
- Volatile memory can be random access memory (Random Access Memory, RAM), static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synch link DRAM , SLDRAM) and Direct Memory Bus Random Access Memory (Direct Rambus RAM, DRRAM).
- RAM Random Access Memory
- SRAM static random access memory
- DRAM dynamic random access memory
- DRAM synchronous dynamic random access memory
- SDRAM double data rate synchronous dynamic random access memory
- Double Data Rate SDRAM Double Data Rate SDRAM
- DDRSDRAM double data rate synchronous dynamic random access memory
- Enhanced SDRAM, ESDRAM enhanced synchronous dynamic random access memory
- Synch link DRAM , SLDRAM
- Direct Memory Bus Random Access Memory Direct Rambus
- the processor 1410 may include one or more processing units; optionally, the processor 1410 integrates an application processor and a modem processor, wherein the application processor mainly handles operations related to the operating system, user interface, and application programs, etc., Modem processors mainly process wireless communication signals, such as baseband processors. It can be understood that the foregoing modem processor may not be integrated into the processor 1410 .
- the processor 1410 is configured to acquire resource configuration information for PRACH repeated transmission, where the resource configuration information indicates the configured resources for the PRACH repeated transmission; and determine whether the configured resources are used for PRACH repeated transmission.
- the terminal acquires configuration resources for PRACH repeated transmission, and determines whether the configuration resources are actually used for PRACH repeated transmission, so that the terminal uses the configuration resources that can actually be used for PRACH repeated transmission to perform PRACH repeated transmission, which can reduce Random access delay.
- processor 1410 is further configured to perform at least one of the following operations:
- the configuration information of the symbol where the configuration resource is located determine whether the configuration resource is used for PRACH repeated transmission
- the processor 1410 is further configured to: determine the validity of the configuration resource
- the validity of the configured resource is related to the first gap requirement and/or time division multiplexing TDD uplink and downlink configuration
- the first gap requirement is a gap requirement among the synchronization signal block SSB transmission, the symbol set used for SSB transmission, and the symbol set used for PRACH transmission.
- processor 1410 is further configured to perform at least one of the following operations:
- the common RO is a commonly configured RO used by the PRACH repeated transmission and the PRACH non-repeated transmission; the first RO is an RO only used for the PRACH repeated transmission.
- 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 repeated transmission.
- the first target RO is included in the number of ROs repeatedly transmitted on the PRACH.
- processor 1410 is further configured to perform at least one of the following operations:
- first common RO in the common RO is invalid, then determine that the first RO associated with the first common RO is not used for PRACH repeated transmission;
- first common RO among the common ROs is valid but not used for PRACH repeated transmission, determine that the first RO associated with the first common RO is not used for PRACH repeated transmission;
- first common RO among the common ROs is valid but not used for repeated PRACH transmission, determine that the first RO associated with the first common RO is used for repeated PRACH transmission.
- processor 1410 is further configured to perform at least one of the following operations:
- the symbol of the third target RO in the first RO is configured as a flexible symbol in the public TDD uplink and downlink configuration information, and is configured as a downlink in the dedicated TDD uplink and downlink configuration information, then determine the third target RO is not used for PRACH repeated transmission;
- the symbol of the third target RO in the first RO is configured as a flexible symbol in the common TDD uplink and downlink configuration information, and is configured as a downlink in the DCI format, it is determined that the third target RO is not used for PRACH repeated transmission ;
- the first configuration information includes: at least one of public TDD uplink and downlink configuration information, dedicated TDD uplink and downlink configuration information, and a DCI format;
- the first RO is an RO in the configuration resource that is only used for repeated transmission of the PRACH.
- processor 1410 is further configured to perform at least one of the following operations:
- the fourth target RO in the first RO at least partially overlaps with the transmission resource of the first uplink information in the random access process, it is determined that the fourth target RO is not used for PRACH repeated transmission; the first RO is the The RO in the configuration resource is only used for PRACH repeated transmission;
- the DCI format information indicates that the terminal performs PRACH repeated transmission on the fourth target RO, and the fourth target RO is the same as the symbol set of the time slot At least one symbol overlaps, then it is determined that the fourth target RO is not used for PRACH repeated transmission;
- the high-level signaling indicates that the terminal performs repeated PRACH transmission in the target symbol on the fourth target RO
- the DCI format information indicates that the terminal receives the downlink signal in the symbol subset of the target symbol
- the processor 1410 is further configured to: determine the power allocation priority of the PRACH repeated transmission;
- the power allocation priority of the PRACH that performs repeated transmission is lower than the power allocation priority of the PRACH that does not perform repeated transmission on the primary cell;
- the power allocation priority of the PRACH that performs repeated transmission is the same as the power allocation priority of the PRACH that does not perform repeated transmission on the primary cell;
- the power allocation priority of the repeated transmission of the PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on the primary cell;
- the power allocation priority of the repeated transmission of the PRACH is the same as the power allocation priority of the PRACH that is not repeatedly transmitted on the non-primary cell;
- the power allocation priority of the PRACH that performs repeated transmission is the same as the power allocation priority of the PRACH that does not perform repeated transmission on the non-primary cell.
- the repeated transmission of the PRACH is completed within the first duration
- the first duration includes at least one of the following:
- M, N, L are positive integers.
- the terminal acquires configuration resources for PRACH repeated transmission, and determines whether the configuration resources are actually used for PRACH repeated transmission, so that the terminal uses the configuration resources that can actually be used for PRACH repeated transmission to perform PRACH repeated transmission, which can reduce Random access delay.
- the embodiment of the present application also provides a network side device, including a processor and a communication interface, and the processor is used to determine configuration resources for repeated transmission of the PRACH; and determine whether the configuration resources are used to receive the PRACH for repeated transmission.
- the network-side device embodiment corresponds to the above-mentioned network-side device method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this network-side device embodiment, and can achieve the same technical effect.
- the embodiment of the present application also provides a network side device.
- the network side device 1500 includes: an antenna 151 , a radio frequency device 152 , a baseband device 153 , a processor 154 and a memory 155 .
- the antenna 151 is connected to the radio frequency device 152 .
- the radio frequency device 152 receives information through the antenna 151, and sends the received information to the baseband device 153 for processing.
- the baseband device 153 processes the information to be sent and sends it to the radio frequency device 152
- the radio frequency device 152 processes the received information and sends it out through the antenna 151 .
- the method performed by the network side device in the above embodiments may be implemented in the baseband device 153, where the baseband device 153 includes a baseband processor.
- the baseband device 153 may include at least one baseband board, for example, a plurality of chips are arranged on the baseband board, as shown in FIG.
- the program executes the network device operations described in the above method embodiments.
- the network side device may also include a network interface 156, such as a common public radio interface (common public radio interface, CPRI).
- a network interface 156 such as a common public radio interface (common public radio interface, CPRI).
- the network-side device 1500 in the embodiment of the present invention further includes: instructions or programs stored in the memory 155 and operable on the processor 154, and the processor 154 calls the instructions or programs in the memory 155 to execute the various programs shown in FIG.
- the method of module execution achieves the same technical effect, so in order to avoid repetition, it is not repeated here.
- the embodiment of the present application also provides a readable storage medium, on which a program or an instruction is stored, and when the program or instruction is executed by a processor, each process of the above-mentioned method embodiment for determining PRACH repeated transmission resources is implemented, And can achieve the same technical effect, in order to avoid repetition, no more details here.
- the processor is the processor in the terminal described in the foregoing embodiments.
- the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk, and the like.
- the embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to realize the above-mentioned determination of PRACH repeated transmission resources
- the chip includes a processor and a communication interface
- the communication interface is coupled to the processor
- the processor is used to run programs or instructions to realize the above-mentioned determination of PRACH repeated transmission resources
- the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.
- the embodiment of the present application further provides a computer program/program product, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to realize the above-mentioned determination of PRACH repeated transmission resources
- a computer program/program product is stored in a storage medium
- the computer program/program product is executed by at least one processor to realize the above-mentioned determination of PRACH repeated transmission resources
- the embodiment of the present application also provides a system for determining PRACH repeated 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 repeated transmission resources applied to the terminal as described above, so
- the network-side device may be configured to execute the steps of the above-mentioned method for determining PRACH repeated transmission resources applied to the network-side device.
- the term “comprising”, “comprising” or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase “comprising a " does not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising that element.
- the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. Functions are performed, for example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
- the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation.
- the technical solution of the present application can be embodied in the form of a computer software product in essence or the part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, disk, CD) contains several instructions to enable a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in various embodiments of the present application.
- a terminal which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请公开了一种确定PRACH重复传输资源的方法、终端及网络侧设备,属于通信技术领域,本申请实施例确定PRACH重复传输资源的方法包括:终端获取针对物理随机接入信道PRACH重复传输的资源配置信息,所述资源配置信息指示所述PRACH重复传输的配置资源;所述终端确定所述配置资源是否用于PRACH重复传输。
Description
相关申请的交叉引用
本申请主张在2022年01月05日在中国提交的中国专利申请No.202210006549.6的优先权,其全部内容通过引用包含于此。
本申请属于通信技术领域,具体涉及一种确定PRACH重复传输资源的方法、终端及网络侧设备。
在现有技术中,随机接入过程可以是基于竞争的随机接入流程也可以是基于非竞争的随机接入的过程。随机接入过程可以是四步随机接入过程(又叫Type-1随机接入过程)或者两步随机接入过程(又叫Type-2随机接入过程)。
在时域做物理随机接入信道(Physical Random Access Channel,PRACH)重复(repetition)传输可以提升PRACH覆盖。现有的PRACH资源配置方案中,资源配置比较稀疏并且可能有最大160ms的PRACH配置周期,若利用该资源配置方案进行PRACH repetition传输,可能导致随机接入延时较长,并且可能导致额外的信令开销。
发明内容
本申请实施例提供一种确定PRACH重复传输资源的方法、终端及网络侧设备,能够解决现有的资源配置方案导致随机接入延时较长的问题。
第一方面,提供了一种确定PRACH重复传输资源的方法,应用于终端,该方法包括:
终端获取针对物理随机接入信道PRACH重复传输的资源配置信息,所述资源配置信息指示所述PRACH重复传输的配置资源;
所述终端确定所述配置资源是否用于PRACH重复传输。
第二方面,提供了一种确定PRACH重复传输资源的装置,应用于终端, 包括:
第一获取模块,用于获取针对物理随机接入信道PRACH重复传输的资源配置信息,所述资源配置信息指示所述PRACH重复传输的配置资源;
第一确定模块,用于确定所述配置资源是否用于PRACH重复传输。
第三方面,提供了一种确定PRACH重复传输资源的方法,应用于网络侧设备,该方法包括:
网络侧设备确定PRACH重复传输的配置资源;
所述网络侧设备确定所述配置资源是否用于接收重复传输的PRACH。
第四方面,提供了一种确定PRACH重复传输资源的装置,应用于网络侧设备,包括:
第四确定模块,用于确定PRACH重复传输的配置资源;
第五确定模块,用于确定所述配置资源是否用于接收重复传输的PRACH。
第五方面,提供了一种终端,该终端包括处理器和存储器,所述存储器存储可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面,提供了一种终端,包括处理器及通信接口,其中,所述处理器用于获取针对物理随机接入信道PRACH重复传输的资源配置信息,所述资源配置信息指示所述PRACH重复传输的配置资源;确定所述配置资源是否用于PRACH重复传输。
第七方面,提供了一种网络侧设备,该网络侧设备包括处理器和存储器,所述存储器存储可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如第三方面所述的方法的步骤。
第八方面,提供了一种网络侧设备,包括处理器及通信接口,其中,所述处理器用于确定PRACH重复传输的配置资源;确定所述配置资源是否用于接收重复传输的PRACH。
第九方面,提供了一种确定PRACH重复传输资源的***,包括:终端及网络侧设备,所述终端可用于执行如第一方面所述的确定PRACH重复传输资源的方法的步骤,所述网络侧设备可用于执行如第三方面所述的确定PRACH重复传输资源的方法的步骤。
第十方面,提供了一种可读存储介质,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤,或者实现如第三方面所述的方法的步骤。
第十一方面,提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现如第一方面所述的方法,或实现如第三方面所述的方法。
第十二方面,提供了一种计算机程序/程序产品,所述计算机程序/程序产品被存储在存储介质中,所述计算机程序/程序产品被至少一个处理器执行以实现如第一方面所述的确定PRACH重复传输资源的方法的步骤,或者实现如第三方面所述的确定PRACH重复传输资源的方法的步骤
在本申请实施例中,终端获取针对PRACH重复传输的配置资源,并确定所述配置资源是否实际用于PRACH重复传输,使终端利用能够实际用于PRACH重复传输的配置资源进行PRACH重复发送,能够降低随机接入延时。
图1是本申请实施例可应用的一种无线通信***的框图;
图2是本申请实施例的SSB映射到FDM的RO示意图;
图3是本申请实施例的SSB映射到TDM/FDM的RO示意图;
图4是本申请实施例的确定PRACH重复传输资源的方法的流程示意图之一;
图5是本申请实施例的RO处理方式之一;
图6是本申请实施例的RO处理方式之二;
图7是本申请实施例的RO处理方式之三;
图8是本申请实施例的RO处理方式之四;
图9是本申请实施例的RO处理方式之五;
图10是本申请实施例的确定PRACH重复传输资源的方法的流程示意图之二;
图11是本申请实施例的确定PRACH重复传输资源的装置的结构示意图之一;
图12是本申请实施例的确定PRACH重复传输资源的装置的结构示意图之二;
图13是本申请实施例的通信设备的结构示意图;
图14是本申请实施例的终端的结构示意图;
图15是本申请实施例的网络侧设备的结构示意图。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员所获得的所有其他实施例,都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象,而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换,以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施,且“第一”、“第二”所区别的对象通常为一类,并不限定对象的个数,例如第一对象可以是一个,也可以是多个。此外,说明书以及权利要求中“和/或”表示所连接对象的至少其中之一,字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是,本申请实施例所描述的技术不限于长期演进型(Long Term Evolution,LTE)/LTE的演进(LTE-Advanced,LTE-A)***,还可用于其他无线通信***,诸如码分多址(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)和其他***。本申请实施例中的术语“***”和“网络”常被可互换地使用,所描述的技术既可用于以上提及的***和无线电技术,也可用于其他***和无线电技术。以下描述出于示例目的描述了新空口(New Radio,NR)***,并且在以下大部分描述中使用NR术语,但是这些技术也可应用于NR***应用以外的应用,如第6代(6
th Generation,6G)通信***。
图1示出本申请实施例可应用的一种无线通信***的框图。无线通信***包括终端11和网络侧设备12。其中,终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant,PDA)、掌上电脑、上网本、超级移动个人计算机(Ultra-mobile personal computer,UMPC)、移动上网装置(Mobile Internet Device,MID)、增强现实(augmented reality,AR)/虚拟现实(virtual reality,VR)设备、机器人、可穿戴式设备(Wearable Device)、车载设备(Vehicle User Equipment,VUE)、行人终端(Pedestrian User Equipment,PUE)、智能家居(具有无线通信功能的家居设备,如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(personal computer,PC)、柜员机或者自助机等终端侧设备,可穿戴式设备包括:智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。需要说明的是,在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备或核心网设备,其中,接入网设备也可以称为无线接入网设备、无线接入网(Radio Access Network,RAN)、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network,WLAN)接入点或WiFi节点等,基站可被称为节点B、演进节点B(Evolved Node B,eNB)、接入点、基收发机站(Base Transceiver Station,BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set,BSS)、扩展服务集(Extended Service Set,ESS)、家用B节点、家用演进型B节点、发送接收点(Transmitting Receiving Point,TRP)或所述领域中其他某个合适的术语,只要达到相同的技术效果,所述基站不限于特定技术词汇,需要说明的是,在本申请实施例中仅以NR***中的基站为例进行介绍,并不限定基站的具体类型。
在进行本申请实施例的说明时,首先对下面描述中所用到的一些概念进行解释说明。
一、随机接入过程。
随机接入过程可以是基于竞争的随机接入流程也可以是基于非竞争的随 机接入的过程。随机接入过程可以是四步随机接入过程(又叫类型(Type)-1随机接入过程)或者两步随机接入过程(又叫Type-2随机接入过程)。
(1)4步随机接入过程(4-step RACH):
在竞争的4步随机接入过程中,UE首先向网络侧设备发送Msg1,包含前导序列(preamble);网络检测到preamble后,将发送Msg2/随机接入响应(Random Access Response,RAR)消息,包含网络侧设备所检测到的preamble的编号,以及分配给UE发送Msg3的上行无线资源;UE接收到Msg2后,确认Msg2中携带的preamble的编号中,至少有一个和自己所发送的preamble的编号一致,则根据RAR的指示的资源,发送包含竞争解决信息的Msg3;网络侧设备收到Msg3后,将发送包含竞争解决信息的Msg4;UE收到Msg4,确认进行解决信息和自己在Msg3中发送的一致,即完成4步随机接入。
网络侧设备在RAR中包含上行链路授权(UpLink grant,UL grant)信息用于指示Msg3物理上行共享信道(Physical Uplink Shared Channel,PUSCH)调度信息,并且包含随机接入前导码标识(RACH preamble ID,RAPID)、临时的小区无线网络临时标识(Temporary Cell Radio Network Temporary Identifier,TC-RNTI)、定时提前(Timing Advance,TA)等信息。如果网络侧设备没有接收到Msg3 PUSCH,可以在TC-RNTI加扰的物理下行控制信道(Physical downlink control channel,PDCCH)中调度Msg3 PUSCH的重传。
对于竞争的随机接入过程,不同的UE随机选取preamble进行传输,这样不同的UE可能在相同的时频无线资源上选取相同的preamble发送,这种情况可以理解为UE的preamble冲突。这种情况下,不同的UE会收到相同的RAR,则此时不同的UE会根据该RAR UL grant中的调度信息,进行Msg3 PUSCH的传输。在不支持Msg3 PUSCH的重复传输时,网络侧设备在一个Msg3 PUSCH调度资源上只能解出一个UE发送的PUSCH(包含竞争解决信息),所以,网络侧设备会在Msg4中包含在Msg3中收到的竞争解决信息。如果UE收到的Msg4中的竞争解决信息和UE在Msg3 PUSCH中发送的竞争解决信息匹配,则UE认为竞争解决成功。如果不匹配,则认为竞争解决不成功。
如果竞争解决不成功,则UE重新选择RACH发送资源,进行PRACH 发送,进行下一次随机接入尝试。
(2)两步随机接入过程(2-step RACH):
第一步是UE发送MsgA给网络侧。网络侧接收到MsgA后给UE发送MsgB消息给UE,如果UE在一定时间内都没有收到MsgB,UE会将统计MsgA发送次数的计数器累加一并重新发送MsgA。如果统计MsgA发送次数的计数器达到一定门限,UE会从2-step随机接入过程切换到4-step随机接入过程。MsgA包括MsgA preamble部分和MsgA PUSCH部分,preamble部分在用于2-step RACH的RO上发送,PUSCH部分在跟发送MsgA preamble以及RO想关联的MsgA PUSCH资源上发送。MsgA PUSCH资源是相对于每个物理随机接入信道时隙(PRACH slot)配置的一组PUSCH资源,包括时频资源和解调参考信号(Demodulation Reference Signal,DMRS)资源。
二、随机接入资源的选择及同步信号块(Synchronization Signal and PBCH block,SSB)到RO的映射(mapping)。
在NR中,小区可以在一个传输PRACH的时域位置上,配置多个频分复用(Frequency Division Multiplex,FDM)的物理随机接入信道传输机会(PRACH transmission occasion),又或者叫PRACH Occasion,这里为了简单简称为RO。在一个时刻,可以进行FDM的RO个数可以为:{1,2,4,8}。如图2所示,一个时刻,有8个RO资源分布在不同的频率上。
随机接入前导(Preamble)只能在参数PRACH配置索引(PRACHConfigurationIndex)配置的时域资源(即RO资源)上传输,随机接入前导只能在参数prach-FDM配置的频域资源上传输,PRACH频域资源n
RA∈{0,1,…M-1},其中M等于高层参数prach-FDM。在初始接入时,PRACH频域资源n
RA从初始激活上行部分带宽(initial active uplink bandwidth part)内频率最低RO资源开始升序编号,否则,PRACH频域资源n
RA从激活上行部分带宽(active uplink bandwidth part)内频率最低RO资源开始升序编号。如图2所示,RO资源按照频率从低到高,依次编号为RO#0~RO#7。
在NR中,RO和实际发送的SSB之间存在关联关系:
一个SSB可能关联多个RO,也可以多个SSB关联1个RO(这种情况下,不同SSB对应不同的Preamble码)。通常,基站可以采用不同的波束进 行不同的SSB的发送,对应的UE在与SSB关联的RO上发送Preamble,这样,UE根据接收到的下行波束/SSB的强度,选择信号好的SSB所关联的RO/“RO和preamble组合”,进行Msg1发送。这样,网络侧设备就可以根据接收到的Preamble的RO/“RO和preamble组合”,确定出UE所选择的SSB。并在SSB对应的下行波束上,发送Msg2,以确保下行信号的接收质量。
以图2为例,一个时刻上的FDM的RO数目为8个,实际传输的SSB数目为4个,即SSB#0、SSB#1、SSB#2、SSB#3,每个SSB关联2个RO。如果UE确定在SSB#0对应的RO上发送PRACH/Msg1/Preamble,那么UE在RO#0和RO#1中选择一个RO进行PRACH的发送。
以图3为例,一个时刻上的FDM的RO数目为2个,实际传输的SSB数目为8个,即SSB#0、SSB#1、……、SSB#7,每2个SSB关联1个RO。多个SSB共享一个RO时,该多个SSB关联的preamble集合是不同的,即同一个preamble也不能同时归属不同SSB关联的preamble集合。以图3中RO#0为例,其有60个与SSB关联的preamble,其中索引(index)为0~29的preamble与SSB#0关联,index为30~59的preamble与SSB#1关联。需要说明的是,图3中的每一个方格均用于表示RO,而不是SSB,其中标明的SSB是指该RO和哪个/哪些SSB是关联的。
UE发送PRACH前,首先进行资源选择,首先根据接收到的波束(beam)或SSB的参考信号接收功率(Reference Signal Received Power,RSRP),选择RSRP高于门限的SSB;如果有多个SSB的RSRP高于该门限,终端可以选择任一个RSRP高于门限的SSB;若没有RSRP高于门限的SSB,UE基于实现选择一个SSB。
基于网络(Network,NW)的配置,UE获得SSB和RO的对应关系;在选择了SSB之后,所选SSB对应的RO被作为发送PRACH/Preamble的RO。如果所选SSB关联多个RO,终端可以选择其中一个RO进行PRACH/Preamble发送。
例如:在图2所示的实施例中,假设UE选择了SSB#1,UE可以从RO#2和RO#3中选择一个进行PRACH/Preamble发送;在图3所示的实施例中,假如UE选择了SSB#1,则UE可以选择与SSB#1关联的RO(RO#0或RO#4) 中距离当前时间最近的可用的RO进行PRACH/Preamble发送。
在所选择的RO中,UE在所选SSB关联的preamble集合中选择一个preamble进行PRACH的发送。如图3中,一个RO关联2个SSB,那么一个RO中与SSB关联的可用的Preamble集合中,preamble会被分成两个子集,每个子集对应于一个SSB。UE将选取对应于所选SSB的那个preamble子集里的某个preamble序列用于PRACH的发送。
其中,SSB与PRACH资源之间的关联有SSB to PRACH occasion mapping cycle(SSB到PRACH occasion的映射周期)、SSB to PRACH occasion mapping association period(SSB至PRACH occasion的映射关联周期),以及SSB to PRACH occasion association pattern period(SSB至PRACH occasion的映射模式周期)。这些周期时间的目的主要是为了能够在预定义的一个时间段内至少完成一次随机接入尝试并且能以一定的模式重复PRACH资源跟SSB之间的映射。当PRACH重复时,PRACH重复需要确保这样的模式不能被打破。
三、在PRACH与其他信号或者时分复用(Time Division Duplex,TDD)配置的冲突时的处理方法。
1)如果在关联周期(association period)内的整数个SS/PBCH块索引到PRACH时机映射周期(mapping cycle)之后,有一组PRACH occasions或PRACH序列未映射到SS/PBCH块索引(SSB index),则没有SS/PBCH块索引映射到PRACH occasions或PRACH序列。这些PRACH资源将不能用于PRACH的发送。
2)关联模式周期包括一个或多个关联周期,并且被确定为使得PRACH occasions和SS/PBCH块索引(SSB indexes)之间的模式最多每160毫秒重复一次。在整数个关联周期之后与SS/PBCH块索引不关联的PRACH occasions(如果有的话)不用于PRACH传输。
3)如果MsgA PUSCH occasion在时间和频率上不与任何与第一类型随机接入过程或第二类型随机接入过程相关的有效PRACH occasions重叠,则MsgA PUSCH occasion有效。这就意味着当PRACH与MsgA PUSCH资源重叠时,传输PRACH而不是传输MsgA PUSCH。
4)对于在未配对频谱(例如,时分复用(Time Division Duplex,TDD)) 中的单个载波上的操作,如果UE由更高层(higher layer)配置为在某个时隙(slot)的一组符号中接收PDCCH、物理下行共享信道(Physical downlink shared channel,PDSCH)、信道状态信息参考信号(Channel State Information Reference Signal,CSI-RS)或下行链路定位参考信号(DL Positioning Reference Signal,DL-PRS),则如果UE在这组符号集合中的至少一个符号中未检测到指示UE发送PUSCH、PUCCH、PRACH或者SRS的下行控制信息(Downlink Control Information,DCI)格式,则UE接收PDCCH、PDSCH、CSI-RS或DL-PRS,否则UE不接收PDCCH、PDSCH、CSI-RS或DL-PRS。
5)对于在未配对频谱中的单个载波上的操作,如果UE由更高层配置为在时隙的一组符号中发送探测参考信号(Sounding Reference Signal,SRS)、物理上行控制信道(Physical Uplink Control Channel,PUCCH)、PUSCH或PRACH,并且UE检测到指示UE从该组符号的一个子集中接收CSI-RS或PDSCH的DCI格式,则:
如果UE不具备“部分取消(partialCancellation)”的能力,则如果该集合(发送SRS、PUCCH、PUSCH或PRACH的一组符号)中的第一个符号和UE检测到DCI格式的控制资源集(Control resource set,CORESET)的最后一个符号之间的时间间隔不超过T
proc,2,则UE不期望取消该集合中的PUCCH或PUSCH或PRACH的传输;否则,UE取消PRACH传输,或者根据相关协议决定取消PUCCH,PUSCH,或PUSCH的实际重复的发送。
如果UE具备“部分取消(partialCancellation)”的能力,则如果该集合(发送SRS、PUCCH、PUSCH或PRACH的一组符号)中有一部分符号和UE检测到DCI格式的CORESET的最后一个符号之间的时间间隔不超过T
proc,2,则UE不期望在这一部分符号上取消PUCCH或PUSCH或PRACH的传输;对于这一部分符号外的符号,UE取消PRACH传输,或者根据相关协议决定取消PUCCH、PUSCH或PUSCH的实际重复的发送。
需要说明的是,在本申请的实施例中,RACH Occasion(即RO)与PRACH Occasion都是指用于发送一个PRACH序列所需要的时频资源,即RACH Occasion和PRACH Occasion均可以用RO表示。
下面结合附图,通过一些实施例及其应用场景对本申请实施例提供的确 定PRACH重复传输资源的方法进行详细地说明。
如图4所示,本申请实施例提供一种确定PRACH重复传输资源的方法,应用于终端,所述方法包括:
步骤401、终端获取针对物理随机接入信道PRACH重复传输的资源配置信息,所述资源配置信息指示所述PRACH重复传输的配置资源。
该实施例中,所述PRACH重复传输与PRACH重传的定义不同,本申请实施例的PRACH重复是指在每次PRACH初传或者重传过程中做的重复传输,PRACH重复只发生在随机接入响应窗口(RAR window)结束之前。
所述针对PRACH重复传输的资源配置信息可以为网络侧设备配置,即网络侧设备为终端配置PRACH重复传输的资源。所述配置资源是指网络侧设备为终端配置的用于PRACH repetition传输的资源,并不一定是终端进行PRACH repetition传输实际使用的传输资源。PRACH repetition的资源指用于发送PRACH repetition的PRACH资源;不支持PRACH repetition的PRACH资源指用于发送PRACH但是没有做repetition的PRACH资源。PRACH资源可以是PRACH时频资源和/或PRACH序列。
步骤402、所述终端确定所述配置资源是否用于PRACH重复传输。
终端根据所述资源配置信息获取网络侧设备为其配置的配置资源,并确定所述配置资源是否实际用于PRACH重复传输。
本申请的实施例,终端获取针对PRACH重复传输的配置资源,并确定所述配置资源是否实际用于PRACH重复传输,使终端利用能够实际用于PRACH重复传输的配置资源进行PRACH重复发送,能够降低随机接入延时。
作为一个可选实施例,所述确定所述配置资源是否用于PRACH重复传输,包括以下至少一项:
(1)根据所述配置资源的有效性,确定所述配置资源是否用于PRACH重复传输;
(2)根据所述配置资源所在符号的配置信息,确定所述配置资源是否用于PRACH重复传输;
(3)根据所述配置资源与其他信号资源的冲突情况,确定所述配置资源是否用于PRACH重复传输。
该实施例中,终端可以根据配置资源的有效性、配置资源所在符号的配置信息、配置资源与其他信号资源的冲突情况中的一种或者多种方式的组合,确定配置资源是否能够实际用于PRACH重复传输。可选地,在根据所述配置资源的有效性确定所述配置资源是否能够实际用于PRACH重复传输时,所述方法还可以包括:
确定所述配置资源的有效性;其中,所述配置资源的有效性,与第一间隙要求和/或时分复用TDD上下行链路配置相关;
所述第一间隙要求为SSB传输、用于SSB传输的符号集、用于PRACH传输的符号集三者之间的间隙要求。
该实施例中,在基于配置资源的有效性确定是否实际用于PRACH重复传输时,配置资源验证有效性的方法可以与现有技术中不进行重复传输的PRACH资源的有效性验证方法相同,即配置资源是否有效取决于SSB传输、用于SSB传输的符号集和用于RPACH传输的符号集之间的间隙要求以及小区特定的TDD上行链路-下行链路配置。
可选地,对于可以同时发送PRACH重复传输和PRACH非重复传输的公共配置的资源,配置资源的有效性验证规则在两种PRACH传输情况下应相同,因此可以使用PRACH非重复传输的验证规则验证本申请实施例中的配置资源的有效性。
验证有效性的方法例如:对于成对频谱或额外的上行链路频谱,所有PRACH情况均有效;
对于未配对频谱:
如果未提供UE公共的TDD上下行链路配置(tdd-UL-DL-ConfigurationCommon),如果PRACH时隙中的PRACH occasion不在PRACH时隙中的SS/PBCH block之前,并且在最后一个SS/PBCH block接收符号之后至少N
gap个符号,则PRACH时隙中的PRACH occasion有效;其中,现有协议中提供了N
gap,并且如果提供了channelAccessMode=semistatic,则在UE不传输的下一信道占用时间开始之前,不与一组连续符号重叠。
如果向UE提供tdd-UL-DL-ConfigurationCommon,则PRACH slot中的PRACH occasion在以下情况下有效:
在UL符号范围内;或者,
不在PRACH时隙中的SS/PBCH block之前,且在最后一个下行线链路符号之后至少N
gap个符号,且在最后一个SS/PBCH block符号之后至少N
gap个符号。其中,现有协议中提供了N
gap,并且如果提供了channelAccessMode=semistatic,则在下一信道占用时间开始之前,不与一组连续符号重叠,其中不应存在任何传输;
SS/PBCH块的候选SS/PBCH块索引对应于SIB1或ServingCellConfigCommon中ssb-PositionsInBurst提供的SS/PBCH块索引。
需要说明的是,本申请实施例判断配置资源有效性的方法仅为示例性说明,也可以根据其他判断方式确定所述配置资源的有效性,在此不做限定。
下面通过具体实施例说明通过上述三种方式确定所述配置资源是否实际用于PRACH重复传输的具体实现过程。
作为一个可选实施例,所述根据所述配置资源的有效性,确定所述配置资源是否用于PRACH重复传输,包括以下至少一项:
1)根据所述配置资源中的第一RO的有效性,确定所述第一RO是否用于PRACH重复传输。
所述配置资源中包括针对PRACH重复传输配置的RO资源。所述第一RO为仅用于PRACH重复传输的RO,所述第一RO可以包括一个或者多个RO。该实施例根据额外配置的仅用于进行PRACH重复传输的RO的有效性,确定该RO是否能够实际用于PRACH重复传输。
可选地,所述根据所述配置资源中的第一RO的有效性,确定所述第一RO是否用于PRACH重复传输,包括:若所述第一RO中的第一目标RO无效,则确定所述第一目标RO不用于PRACH重复传输。
该实施例中,所述第一目标RO可以是指所述第一RO中的一个或者多个RO,对于仅用于进行PRACH重复传输的RO,若该RO无效,则该RO被丢弃,不能用于进行PRACH重复传输。其中,在第一目标RO无效被丢 弃时,可以不对该第一目标RO进行计数,也可以对该第一目标RO进行计数。下面分别说明。
可选地,所述方法还包括:将所述第一目标RO推迟一个RO级别的时域位置,获得第二目标RO,所述第二目标RO用于PRACH重复传输。
该情况下,在第一目标RO无效时,不对该第一目标RO进行计数,可以将无效的第一目标RO推迟,获得新的有效的第二目标RO,从而确保有效的PRACH repetition数量。例如图5所示,所述配置资源包括公共RO和第一RO,公共RO用于进行第一次PRACH repetition,第一RO包括用于PRACH repetition的RO0、RO1、RO2、RO3,且RO0、RO1、RO2、RO3各两个,可以分别进行两次PRACH repetition,其中,1个RO0和1个RO1由于与SSB传输重叠而无效(即图5中右侧的1个RO0和1个RO1为所述第一目标RO),则将无效的RO0和RO1向后顺延一个RO,从而确保有对应的额外两个RO用于PRACH repetition的发送,保证配置的PRACH repetition的数量不变。
可选地,所述第一目标RO计入所述PRACH重复传输的RO数量。
该实施例中,在第一目标RO无效时,丢弃该第一目标RO,但是仍对该第一目标RO进行计数。对于仅用于进行PRACH重复传输而单独配置的第一RO,只要公共RO有效(或者公共RO有效但未实际用于PRACH重复传输),所述第一RO都将映射到公共RO,如果第一RO中的一个或者多个无效,则无效的第一RO丢弃,但仍会计数。其中,所述公共RO为所述PRACH重复传输与PRACH非重复传输使用的公共配置的RO(也可以称为shared RO)。
例如图6所示,所述配置资源包括公共RO和第一RO,公共RO用于进行第一次PRACH repetition,第一RO包括用于PRACH repetition的RO0、RO1、RO2、RO3,且RO0、RO1、RO2、RO3各两个,可以分别进行两次PRACH repetition,其中,1个RO0和1个RO1由于与SSB传输重叠而无效(即图6中右侧的1个RO0和1个RO1为所述第一目标RO),在没有顺延的情况下被丢弃,则RO0和RO1中的PRACH传输只能重复两次(包括左边的第一次重复),而RO2和RO3中的PRACH重复传输因为所有RO都有效可以重复3次(包括左边的第一次重复)。
需要说明的是,在所述配置资源中包括公共RO以及第一RO时,公共RO与相应的第一RO关联。例如图5和图6所示,左侧的公共RO中的RO0与右侧的第一RO中的两个RO0关联,左侧的公共RO中的RO1与右侧的两个RO1关联,其他RO以此类推,在此不做赘述。
2)根据所述配置资源中的公共RO的有效性,确定所述配置资源中的第一RO是否用于PRACH重复传输;其中,所述公共RO为所述PRACH重复传输与PRACH非重复传输使用的公共配置的RO;所述第一RO为仅用于PRACH重复传输的RO。
该实施例通过确定公共RO的有效性,确定与该公共RO关联的第一RO的是否实际用于PRACH重复传输。
可选地,所述根据所述配置资源中的公共RO的有效性,确定所述配置资源中的第一RO是否用于PRACH重复传输,包括以下至少一项:
a:若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO不用于PRACH重复传输。
该实施例中,所述第一公共RO可以是指所述公共RO中的一个或者多个RO,若所述第一公共RO无效,则与所述第一公共RO关联的第一RO被丢弃,不用于PRACH重复传输。
例如图7所示,所述配置资源包括公共RO和第一RO,公共RO用于进行第一次PRACH repetition,第一RO包括用于PRACH repetition的RO0、RO1、RO2、RO3,且RO0、RO1、RO2、RO3各两个,可以分别进行两次PRACH repetition,其中,两个公共RO(左侧的RO2和RO3)与下行链路中由动态授权调度的PDSCH冲突,则与这两个公共RO相关联的额外配置的第一RO(右侧的2个RO2和2个RO3)没有实际传输而被丢弃,且不进行实际的PRACH repetition传输。
b:若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定与所述第一公共RO关联的第一RO不用于PRACH重复传输。
该实施例中,配置资源中的部分公共RO可能有效,但是由于与其他资源冲突或者被配置为不可用,导致该有效的公共RO未用于实际的PRACH重复传输,则与该公共RO关联的第一RO不用于实际的PRACH重复传输。 具体实施例如图7所示,在此不做赘述。
c:若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO用于PRACH重复传输。
该实施例中,若所述第一公共RO无效,则与所述第一公共RO关联的第一RO仍用于PRACH重复传输。例如图8所示,所述配置资源包括公共RO和第一RO,公共RO用于进行第一次PRACH repetition,第一RO包括用于PRACH repetition的RO0、RO1、RO2、RO3,且RO0、RO1、RO2、RO3各两个,可以分别进行两次PRACH repetition,其中,两个公共RO(左侧的RO2和RO3)与下行链路中由动态授权调度的PDSCH冲突,则与这两个公共RO相关联的额外配置的第一RO(右侧的2个RO2和2个RO3)仍然用于PRACH重复传输,即不丢弃。
d:若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定与所述第一公共RO关联的第一RO用于PRACH重复传输。
该实施例中,若所述第一公共RO有效但是未实际用于PRACH重复传输,则与所述第一公共RO关联的第一RO仍用于PRACH重复传输,例如图8所示,在此不做赘述。
该实施例根据第一RO和/或公共RO的有效性,确定配置资源是否用于实际的PRACH重复传输,例如针对PRACH repetition与其他资源相冲突时,某些PRACH repetition可以被丢弃从而确保其他高优先级的信号可以按时发送或者接收;或者,为了确保实际PRACH repetition的数量,用于repetition的PRACH occasion向后推迟,跳过无效的或者不实际发送PRACH的RO;或者,即便第一次repetition的资源无效或者没有被实际发送PRACH,后续repetition的PRACH资源还可以继续发送剩下的PRACH repetition,降低随机接入的延时。
下面说明根据所述配置资源所在符号的配置信息,确定所述配置资源是否用于PRACH重复传输的具体实现过程。
作为一个可选实施例,所述根据所述配置资源所在符号的配置信息,确定所述配置资源是否用于PRACH重复传输,包括以下至少一项:
A)若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置 信息(tdd-UL-DL-configurationCommon)中配置为灵活符号,在专用TDD上下行链路配置信息(tdd-UL-DL-ConfigurationDedicated)中配置为下行链路,则确定所述第三目标RO不用于PRACH重复传输;其中,所述第一RO为所述配置资源中的仅用于PRACH重复传输的RO。
该实施例中,所述第三目标RO为仅用于进行PRACH重复传输的第一RO中的一个或者多个。如果额外配置的用于发送PRACH repetition的RO(例如所述第一RO中的第三目标RO)所在符号在tdd-UL-DL-configurationCommon中配置为灵活符号(flexible),在tdd-UL-DL-ConfigurationDedicated中配置为DL,则所述第三目标RO不用于进行PRACH重复传输。
B)若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在DCI格式中配置为下行链路,则确定所述第三目标RO不用于PRACH重复传输。
该实施例中,所述DCI格式可以为DCI format2-0,如果额外配置的用于发送PRACH repetition的RO(例如所述第一RO中的第三目标RO)所在符号在tdd-UL-DL-configurationCommon中配置为flexible,在DCI format2-0中指示为DL,所述RO不用于PRACH重复传输。
C)若第一RO中的第三目标RO所在符号在第一配置信息中配置为灵活符号,且终端在所述符号上接收下行信号,则确定所述第三目标RO不用于PRACH重复传输。所述第一配置信息包括:公共TDD上下行链路配置信息(tdd-UL-DL-configurationCommon)、专用TDD上下行链路配置信息(tdd-UL-DL-ConfigurationDedicated)以及DCI格式中的至少一项;
该实施例中,所述下行信号例如:PDCCH、PDSCH,所述DCI格式例如DCI format2-0;即如果额外配置的用于发送PRACH repetition的RO(例如所述第一RO中的第三目标RO)所在符号在tdd-UL-DL-configurationCommon和/或tdd-UL-DL-ConfigurationDedicated和/或DCI format2-0中配置为flexible,但是下行信号在上述符号(即RO所在符号)上接收,则该第三目标RO不用于PRACH重复传输。
该实施例基于所述配置资源所在符号的配置信息,确定所述配置信息是 否实际用于PRACH重复传输,给出了UE在不同配置下的传输资源的使用方案,可以保证所述配置资源,降低随机接入的延时。
下面说明根据所述配置资源与其他信号资源的冲突情况,确定所述配置资源是否实际用于PRACH重复传输的实现过程。
作为一个可选实施例,所述根据所述配置资源与其他信号资源的冲突情况,确定所述配置资源是否用于PRACH重复传输,包括以下至少一项:
i)若第一RO中的第四目标RO与随机接入过程中的第一上行信息的传输资源至少部分重叠,则确定所述第四目标RO不用于PRACH重复传输;所述第一RO为所述配置资源中的仅用于PRACH重复传输的RO。
所述第四目标RO可以为仅用于进行PRACH重复传输的第一RO中的一个或者多个RO。所述第一上行信息可以为随机接入过程的MsgA。即:对于额外配置的用于发送PRACH重复的RO(例如所述第四目标RO),如果RO与MsgA PUSCH传输至少部分重叠,则该RO不用于PRACH重复发送。
该实施例中,由于不支持PRACH重复的UE可能不会读取和识别额外配置的用于发送PRACH重复的ROs,这意味着MsgA PUSCH必须优先于为PRACH重复配置的单独ROs,即MsgA PUSCH优先于所述第四目标RO的传输。另一方面,在第四目标RO和MsgA PUSCH的资源存在重叠时,丢弃部分PRACH重复,保护MsgA PUSCH,可能不会导致PRACH接收失败,但可以确保MsgA PUSCH的及时发送。
ii)若高层信令指示终端在时隙内的一组符号中接收下行信号,DCI格式信息指示终端在第四目标RO进行PRACH重复传输,且所述第四目标RO与所述时隙所在的符号集合中的至少一个符号重叠,则确定所述第四目标RO不用于PRACH重复传输。
该实施例中,对于在未配对频谱中的单个载波上的操作,如果UE由高层配置在时隙内的一组符号中接收PDCCH、PDSCH、CSI-RS或DL PRS等下行信号,则UE接收PDCCH、PDSCH、CSI-RS或者DL PRS等下行信号,即使UE检测到DCI格式,该DCI格式指示UE在一个额外配置的RO(例如第四目标RO)发送PRACH重复,并且该额外配置的RO(例如第四目标RO)与该时隙的符号集合的至少一个符号重叠,UE不在所述第四目标RO 上进行PRACH重复传输,而是在所述时隙的符号上接收下行信号。
该实施例中,下行信号接收的优先级高于PRACH重复传输,相关协议可以引用相应修改,例如:
对于在未配对频谱中的单个载波上的操作,如果UE由高层配置在时隙内的一组符号中接收PDCCH、PDSCH、CSI-RS或DL PRS等下行信号,如果UE未检测到指示UE在时隙的符号集合的至少一个符号中发送PUSCH、PUCCH、PRACH非重复或SRS的DCI格式,则UE接收PDCCH、PDSCH、CSI-RS或DL-PRS;否则,如果UE未检测到指示UE发送重复的PRACH的DCI格式,则UE不接收时隙的符号集合中的PDCCH、PDSCH、CSI-RS或DL-PRS等下行信号。(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,a PUCCH,a PRACH 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)。
iii)若高层信令指示终端在第四目标RO上的目标符号中进行PRACH重复传输,DCI格式信息指示终端在所述目标符号的符号子集中接收下行信号,则所述第四目标RO不用于PRACH重复传输。
该实施例中,对于在未配对频谱中的单个载波上的操作,如果UE由高层配置为在额外配置的RO(例如第四目标RO)上对应某个时隙的一组符号中发送PRACH重复,并且UE检测到DCI格式,该DCI格式指示UE从该组符号中接收符号子集中的下行信号(例如CSI-RS或PDSCH),则UE不在第四目标RO进行PRACH重复传输,而是在所述目标符号的子集中接收下行信号。可选地,所述第四目标RO不用于PRACH重复传输,但仍对相应的PRACH重复进行计数。
该实施例根据所述配置资源与其他信号资源的冲突情况,确定所述配置 资源是否用于PRACH重复传输,针对PRACH repetition与其他资源相冲突时,某些PRACH repetition可以被丢弃从而确保其他高优先级的信号可以按时发送或者接收,降低随机接入的延时。
作为一个可选实施例,所述方法还包括:确定所述PRACH重复传输的功率分配优先级;
所述功率分配优先级包括以下至少一项:
1)进行重复传输的PRACH的功率分配优先级低于在主小区(PCell)上不做重复传输的PRACH的功率分配优先级。
该实施例中,基于本实施列,重复传输的PRACH相对于在载波聚合过程中同时发送的其他上行信号,会被低优先级的分配功率,相关协议可以引入相应修改,例如:
时隙符号中的总UE发射功率被定义为时隙符号中PUSCH、PUCCH、PRACH和SRS的UE发射功率的线性值之和(The total UE transmit power in a symbol of a slot is defined as the sum of the linear values of UE transmit powers for PUSCH,PUCCH,PRACH,and SRS in the symbol of the slot)。
在Pcell上不进行PRACH重复传输(PRACH transmission without repetition on the Pcell);
具有更高优先级索引的PUCCH或PUSCH传输(PUCCH or PUSCH transmissions with higher priority index according to clause 9);
对于具有相同优先级索引的PUCCH或PUSCH传输(For PUCCH or PUSCH transmissions with same priority index);
带有混合自动重传请求应答(Hybrid automatic repeat request acknowledgement,HARQ-ACK)信息的PUCCH传输,和/或调度请求(Scheduling Request,SR),和/或链路恢复请求(Link recovery request,LRR),或带有HARQ-ACK信息的PUSCH传输(PUCCH transmission with HARQ-ACK information,and/or SR,and/or LRR,or PUSCH transmission with HARQ-ACK information);
带有CSI的PUCCH传输或带有CSI的PUSCH传输(PUCCH transmission with CSI or PUSCH transmission with CSI);
没有HARQ-ACK信息或CSI的PUSCH传输,对于Type-2随机接入过程,Pcell上的PUSCH传输(PUSCH transmission without HARQ-ACK information or CSI and,for Type-2 random access procedure,PUSCH transmission on the Pcell);
SRS传输,具有比半持续和/或周期SRS具有更高优先级的非周期SRS,或在除Pcell或PRACH重复传输之外的服务小区上的PRACH传输(SRS transmission,with aperiodic SRS having higher priority than semi-persistent and/or periodic SRS,or PRACH transmission on a serving cell other than the Pcell or PRACH repetition transmissions)。
2)进行重复传输的PRACH的功率分配优先级,与在主小区上不做重复传输的PRACH的功率分配优先级相同。
该实施例中,重复的PRACH相对于在载波聚合过程中同时发送的其他上行信号,会被高优先级的分配功率。相关协议可以引入相应修改,例如:
时隙符号中的总UE发射功率被定义为时隙符号中PUSCH、PUCCH、PRACH和SRS的UE发射功率的线性值之和(The total UE transmit power in a symbol of a slot is defined as the sum of the linear values of UE transmit powers for PUSCH,PUCCH,PRACH,and SRS in the symbol of the slot)。
Pcell上的PRACH传输或PRACH重复传输(PRACH transmission on the Pcell or PRACH repetition transmission);
具有更高优先级索引的PUCCH或PUSCH传输(PUCCH or PUSCH transmissions with higher priority index according to clause 9);
对于具有相同优先级索引的PUCCH或PUSCH传输(For PUCCH or PUSCH transmissions with same priority index);
带有HARQ-ACK信息的PUCCH传输,和/或SR,和/或LRR,或带有HARQ-ACK信息的PUSCH传输(PUCCH transmission with HARQ-ACK information,and/or SR,and/or LRR,or PUSCH transmission with HARQ-ACK information);
带有CSI的PUCCH传输或带有CSI的PUSCH传输(PUCCH transmission with CSI or PUSCH transmission with CSI);
没有HARQ-ACK信息或CSI的PUSCH传输,对于Type-2随机接入过程,Pcell上的PUSCH传输(PUSCH transmission without HARQ-ACK information or CSI and,for Type-2 random access procedure,PUSCH transmission on the Pcell);
SRS传输,非周期SRS具有比半持续和/或周期SRS更高的优先级,或者在除Pcell以外的服务小区上进行PRACH传输(SRS transmission,with aperiodic SRS having higher priority than semi-persistent and/or periodic SRS,or PRACH transmission on a serving cell other than the Pcell)。
3)若在主小区上进行所述PRACH重复传输,则重复传输的PRACH的功率分配优先级,与在主小区上不做重复传输的PRACH的功率分配优先级相同;
4)若在非主小区上进行所述PRACH重复传输,则重复传输的PRACH的功率分配优先级,与在非主小区上不做重复传输的PRACH的功率分配优先级相同;
5)进行重复传输的PRACH的功率分配优先级,与在非主小区上不做重复传输的PRACH的功率分配优先级相同。
该实施例通过定义所述PRACH重复传输的功率分配优先级,确保具有高优先级的信号可以按时发送或者接收,保证信号传输正常进行。
作为一个可选实施例,所述PRACH重复传输在第一持续时间内完成;
所述第一持续时间包括以下至少一项:
SSB至RO的映射周期的M倍时间;
SSB至RO的映射关联周期的N倍时间;
SSB至RO的关联模式周期的L倍时间;
随机接入响应窗口对应的时间值;所述随机接入响应窗口的最大值可以为10ms;
SSB至PRACH重复传输的RO的关联模式周期;所述SSB至PRACH重复传输的RO的关联模式周期可以是针对PRACH重复传输额外配置的。
其中,M、N、L为正整数。所述M、N、L的具体数值可以由协议定义或者由***消息配置。
该实施例中,额外的定义SSB到PRACH重复传输的RO关联模式周期,其可以包括一个或多个SSB到RO关联模式周期,使得PRACH重复RO和SSB之间的模式最多可以在每个预定时间周期(例如,每640ms)重复。可选地,所述预定时间周期可以是SSB到(现有的、单次发送的)PRACH的RO关联模式周期的正整数倍。
例如图9所示,配置了4次重复传输的RO,前3次重复传输在SSB到RO的关联模式周期内,但第4次重复出现在下一个SSB到RO的关联模式周期内,那么第4次重复将被丢弃。需要说明的是,图9中的RO表示为所述PRACH重复传输配置的RO,可以是公共RO也可以为第一RO,在此不做限定。
可选地,若配置的所述PRACH重复传输未在上述第一持续时间内完成,则剩余次数的PRACH重复传输可以全部丢弃,也可以在第一持续时间结束之前完成部分发送。
本申请实施例,终端获取针对PRACH重复传输的配置资源,并确定所述配置资源是否实际用于PRACH重复传输,提供了配置资源无效或者与其他信号资源冲突时的解决方案,能够降低随机接入延时。例如:针对PRACH repetition与其他资源相冲突时,部分PRACH repetition可以被丢弃或者不增加发送功率从而确保其他高优先级的信号可以按时发送或者接收;或者,为了确保实际PRACH repetition的数量,用于repetition的PRACH occasion需要向后推迟,跳过无效的或者不实际发送PRACH的RO;或者,即使第一次repetition的资源无效或者没有被实际发送PRACH,后续repetition的PRACH资源还可以继续发送剩下的PRACH repetition,降低随机接入的延时。
如图10所示,本申请实施例还提供一种确定PRACH重复传输资源的方法,应用于网络侧设备,包括:
步骤101、网络侧设备确定PRACH重复传输的配置资源;
步骤102、所述网络侧设备确定所述配置资源是否用于接收重复传输的PRACH。
该实施例中,所述PRACH重复传输与PRACH重传的定义不同,本申请实施例的PRACH重复是指在每次PRACH初传或者重传过程中做的重复传输, PRACH重复只发生在随机接入响应窗口结束之前。
网络侧设备为终端配置PRACH重复传输的资源。所述配置资源是指网络侧设备为终端配置的用于PRACH repetition传输的资源,并不一定是终端进行PRACH repetition传输实际使用的传输资源。PRACH repetition的资源指用于发送PRACH repetition的PRACH资源;不支持PRACH repetition的PRACH资源指用于发送PRACH但是没有做repetition的PRACH资源。PRACH资源可以是PRACH时频资源和/或PRACH序列
终端确定所述配置资源是否实际用于PRACH重复传输,并在实际传输的配置资源上进行PRACH重复传输;则网络侧设备也需要基于和终端相应的规则确定配置资源是否实际用于PRACH重复传输,并在实际传输的配置资源上接收重复传输的PRACH。
本申请的实施例,网络侧设备针对PRACH重复传输配置资源,并确定配置的资源是否实际用于PRACH重复传输,使网络侧设备可以在实际用于PRACH重复传输的配置资源上接收重复传输的PRACH,能够降低随机接入延时。
可选地,所述方法还包括:向终端发送针对PRACH重复传输的资源配置信息,所述资源配置信息指示所述配置资源。
该实施例中,网络侧设备配置了针对PRACH重复传输的配置资源后,可以通过资源配置信息将所述配置资源发送至所述终端,以使所述终端确定所述配置资源是否实际用于PRACH重复传输,从而确定配置资源无效或者与其他信号资源冲突时的解决方案,降低随机接入延时。
可选地,所述确定所述配置资源是否用于接收重复传输的PRACH,包括以下至少一项:
(1)根据所述配置资源的有效性,确定所述配置资源是否用于接收重复传输的PRACH;
(2)根据所述配置资源所在符号的配置信息,确定所述配置资源是否用于接收重复传输的PRACH;
(3)根据所述配置资源与其他信号资源的冲突情况,确定所述配置资源是否用于接收重复传输的PRACH。
该实施例中,终端可以根据配置资源的有效性、配置资源所在符号的配置信息、配置资源与其他信号资源的冲突情况中的一种或者多种方式的组合,确定配置资源是否能够实际用于PRACH重复传输。可选地,在根据所述配置资源的有效性确定所述配置资源是否用于接收重复传输的PRACH时,所述方法还可以包括:
确定所述配置资源的有效性;其中,所述配置资源的有效性,与第一间隙要求和/或时分复用TDD上下行链路配置相关;所述第一间隙要求为SSB传输、用于SSB传输的符号集、用于PRACH传输的符号集三者之间的间隙要求。
该实施例中,在基于配置资源的有效性确定是否接收重复传输的PRACH时,配置资源验证有效性的方法可以与现有技术中不进行重复传输的PRACH资源的有效性验证方法相同,即配置资源是否有效取决于SSB传输、用于SSB传输的符号集和用于RPACH传输的符号集之间的间隙要求以及小区特定的TDD上行链路-下行链路配置。
可选地,对于可以同时发送PRACH重复传输和PRACH非重复传输的公共配置的资源,配置资源的有效性验证规则在两种PRACH传输情况下应相同,因此可以使用PRACH非重复传输的验证规则验证本申请实施例中的配置资源的有效性。确定所述配置资源的有效性的方式在此不做限定。
下面通过具体实施例说明通过上述三种方式确定所述配置资源是否用于接收重复传输的PRACH的具体实现过程
作为一个可选实施例,所述根据所述配置资源的有效性,确定所述配置资源是否用于接收重复传输的PRACH,包括以下至少一项:
1)根据所述配置资源中的第一RO的有效性,确定所述配置资源是否用于接收重复传输的PRACH。
所述配置资源中包括针对PRACH重复传输配置的RO资源。所述第一RO为仅用于PRACH重复传输的RO,所述第一RO可以包括一个或者多个RO。该实施例根据额外配置的仅用于进行PRACH重复传输的RO的有效性,确定该RO是否能够实际用于PRACH重复传输,即网络侧设备是否需要在该第一RO上接收重复传输的PRACH。
可选地,所述根据所述配置资源中的第一RO的有效性,确定所述配置资源是否用于接收重复传输的PRACH,包括:若所述第一RO中的第一目标RO无效,则确定所述第一目标RO不用于接收PRACH重复传输。所述第一RO为仅用于PRACH重复传输的RO。
该实施例中,所述第一目标RO可以是指所述第一RO中的一个或者多个RO,对于仅用于进行PRACH重复传输的RO,若该RO无效,则该RO被丢弃,不能用于进行PRACH重复传输。其中,在第一目标RO无效被丢弃时,可以不对该第一目标RO进行计数,也可以对该第一目标RO进行计数。下面分别说明。
可选地,所述方法还包括:确定第二目标RO的时域位置,所述第二目标RO是将所述第一目标RO推迟一个RO级别的时域位置获得,所述第二目标RO用于接收重复传输的PRACH。
该情况下,在第一目标RO无效时,不对该第一目标RO进行计数,可以将无效的第一目标RO推迟,获得新的有效的第二目标RO,从而确保有效的PRACH repetition数量。例如图5所示,在此不做赘述。
可选地,所述第一目标RO计入所述PRACH重复传输的RO数量。该实施例中,在第一目标RO无效时,丢弃该第一目标RO,但是仍对该第一目标RO进行计数。对于仅用于进行PRACH重复传输而单独配置的第一RO,只要公共RO有效(或者公共RO有效但未实际用于PRACH重复传输),所述第一RO都将映射到公共RO,如果第一RO中的一个或者多个无效,则无效的第一RO丢弃,但仍会计数,例如图6所示,在此不做赘述。
2)根据所述配置资源中的公共RO的有效性,确定所述配置资源是否用于接收重复传输的PRACH;其中,所述公共RO为所述PRACH重复传输与PRACH非重复传输使用的公共配置的RO。
该实施例通过确定公共RO的有效性,确定与该公共RO关联的第一RO的是否用于接收重复传输的PRACH。
可选地,所述根据所述配置资源中的公共RO的有效性,确定所述配置资源是否用于接收重复传输的PRACH,包括以下至少一项:
a:若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO 关联的第一RO不用于接收重复传输的PRACH。
该实施例中,所述第一公共RO可以是指所述公共RO中的一个或者多个RO,若所述第一公共RO无效,则与所述第一公共RO关联的第一RO被丢弃,不用于PRACH重复传输,则网络侧设备不需要在所述第一公共RO关联的第一RO中接收重复传输的PRACH。
b:若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定所与所述第一公共RO关联的第一RO不用于接收重复传输的PRACH。
该实施例中,配置资源中的部分公共RO可能有效,但是由于与其他资源冲突或者被配置为不可用,导致该有效的公共RO未用于实际的PRACH重复传输,则与该公共RO关联的第一RO不用于实际的PRACH重复传输,则与所述第一公共RO关联的第一RO不用于接收重复传输的PRACH。
c:若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO用于接收重复传输的PRACH。
该实施例中,若所述第一公共RO无效,则与所述第一公共RO关联的第一RO仍用于PRACH重复传输,则与所述第一公共RO关联的第一RO仍用于接收重复传输的PRACH。
d:若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定与所述第一公共RO关联的第一RO用于接收重复传输的PRACH。
该实施例中,若所述第一公共RO有效但是未实际用于PRACH重复传输,则与所述第一公共RO关联的第一RO仍用于PRACH重复传输,则与所述第一公共RO关联的第一RO仍用于接收重复传输的PRACH。
该实施例根据第一RO和/公共RO的有效性,确定配置资源是否用于实际的PRACH重复传输,例如针对PRACH repetition与其他资源相冲突时,某些PRACH repetition可以被丢弃从而确保其他高优先级的信号可以按时发送或者接收;或者,为了确保实际PRACH repetition的数量,用于repetition的PRACH occasion向后推迟,跳过无效的或者不实际发送PRACH的RO;或者,即便第一次repetition的资源无效或者没有被实际发送PRACH,后续repetition的PRACH资源还可以继续发送剩下的PRACH repetition,降低随机接入的延时。
下面说明根据所述配置资源所在符号的配置信息,确定所述配置资源是否用于接收重复传输的PRACH的具体实现过程。
作为一个可选实施例,所述根据所述配置资源所在符号的配置信息,确定所述配置资源是否用于接收重复传输的PRACH,包括以下至少一项:
A)若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在专用TDD上下行链路配置信息中配置为下行链路,则确定所述第三目标RO不用于接收重复传输的PRACH。其中,所述第一RO为所述配置资源中的仅用于PRACH重复传输的RO。
该实施例中,所述第三目标RO为仅用于进行PRACH重复传输的第一RO中的一个或者多个。如果额外配置的用于发送PRACH repetition的RO(例如所述第一RO中的第三目标RO)所在符号在tdd-UL-DL-configurationCommon中配置为灵活符号(flexible),在tdd-UL-DL-ConfigurationDedicated中配置为DL,则所述第三目标RO不用于进行PRACH重复传输,则所述网络侧设备在所述第三目标RO上接收重复传输的PRACH。
B)若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在DCI格式中配置为下行链路,则确定所述第三目标RO不用于接收重复传输的PRACH。
该实施例中,所述DCI格式可以为DCI format2-0,如果额外配置的用于发送PRACH repetition的RO(例如所述第一RO中的第三目标RO)所在符号在tdd-UL-DL-configurationCommon中配置为flexible,在DCI format2-0中指示为DL,所述第三目标RO不用于PRACH重复传输,则所述第三目标RO不用于接收重复传输的PRACH。
C)若第一RO中的第三目标RO所在符号在第一配置信息中配置为灵活符号,且终端在所述符号上接收下行信号,则确定所述第三目标RO不用于接收重复传输的PRACH;所述第一配置信息包括:公共TDD上下行链路配置信息、专用TDD上下行链路配置信息以及DCI格式中的至少一项;其中,所述第一RO为所述配置资源中的仅用于PRACH重复传输的RO。
该实施例中,所述下行信号例如:PDCCH、PDSCH,所述DCI格式例 如DCI format2-0;即如果额外配置的用于发送PRACH repetition的RO(例如所述第一RO中的第三目标RO)所在符号在tdd-UL-DL-configurationCommon和/或tdd-UL-DL-ConfigurationDedicated和/或DCI format2-0中配置为flexible,但是下行信号在上述符号(即RO所在符号)上接收,则该第三目标RO不用于PRACH重复传输,则所述第三目标RO不用于接收重复传输的PRACH。
该实施例基于所述配置资源所在符号的配置信息,确定所述配置信息是否实际用于PRACH重复传输,给出了UE在不同配置下的传输资源的使用方案,可以保证所述配置资源,降低随机接入的延时。
下面说明根据所述配置资源与其他信号资源的冲突情况,确定所述配置资源是否实际用于PRACH重复传输的实现过程。
作为一个可选实施例,根据所述配置资源与其他信号资源的冲突情况,确定所述配置资源是否用于接收重复传输的PRACH,包括:
若第一RO中的第四目标RO与随机接入过程中的第一上行信息的传输资源至少部分重叠,则确定所述第四目标RO不用于接收重复传输的PRACH。
所述第四目标RO可以为仅用于进行PRACH重复传输的第一RO中的一个或者多个RO。所述第一上行信息可以为随机接入过程的MsgA。即:对于额外配置的用于发送PRACH重复的RO(例如所述第四目标RO),如果RO与MsgA PUSCH传输至少部分重叠,则该RO不用于PRACH重复发送,则该RO不用于接收重复传输的PRACH。
该实施例中,由于不支持PRACH重复的UE可能不会读取和识别额外配置的用于发送PRACH重复的ROs,这意味着MsgA PUSCH必须优先于为PRACH重复配置的单独ROs,即MsgA PUSCH优先于所述第四目标RO的传输。另一方面,在第四目标RO和MsgA PUSCH的资源存在重叠时,丢弃部分PRACH重复,保护MsgA PUSCH,可能不会导致PRACH接收失败,但可以确保MsgA PUSCH的及时发送。
可选地,若高层信令指示终端在时隙内的一组符号中接收下行信号,DCI格式信息指示终端在第四目标RO进行PRACH重复传输,且所述第四目标RO与所述时隙所在的符号集合中的至少一个符号重叠,则所述第四目标RO 不用于PRACH重复传输。若所述高层信令将对于终端的指示信息通知网络侧设备,例如通知网络侧设备终端在所述符号内接收下行信号,则网络侧设备结合DCI格式信息可以确定所述第四目标RO不用于接收重复传输的PRACH。
可选地,若高层信令指示终端在第四目标RO上的目标符号中进行PRACH重复传输,DCI格式信息指示终端在所述目标符号的符号子集中接收下行信号,则所述第四目标RO不用于PRACH重复传输。若所述高层信令将对于终端的指示信息通知网络侧设备,例如通知网络侧设备终端在第四目标RO上的目标符号中进行PRACH重复传输,则网络侧设备结合DCI格式信息可以确定,所述第四目标RO不用于接收重复传输的PRACH。
该实施例根据所述配置资源与其他信号资源的冲突情况,确定所述配置资源是否用于PRACH重复传输,针对PRACH repetition与其他资源相冲突时,某些PRACH repetition可以被丢弃从而确保其他高优先级的信号可以按时发送或者接收,降低随机接入的延时。
可选地,所述网络侧设备还可以确定PRACH重复传输的功率分配优先级,所述功率分配优先级包括以下至少一项:
1)进行重复传输的PRACH的功率分配优先级低于在主小区(PCell)上不做重复传输的PRACH的功率分配优先级。
2)进行重复传输的PRACH的功率分配优先级,与在主小区上不做重复传输的PRACH的功率分配优先级相同。
3)若在主小区上进行所述PRACH重复传输,则重复传输的PRACH的功率分配优先级,与在主小区上不做重复传输的PRACH的功率分配优先级相同;
4)若在非主小区上进行所述PRACH重复传输,则重复传输的PRACH的功率分配优先级,与在非主小区上不做重复传输的PRACH的功率分配优先级相同;
5)进行重复传输的PRACH的功率分配优先级,与在非主小区上不做重复传输的PRACH的功率分配优先级相同。
该实施例通过定义所述PRACH重复传输的功率分配优先级,确保具有 高优先级的信号可以按时发送或者接收,保证信号传输正常进行。
可选地,所述PRACH重复传输的接收在第一持续时间内完成;
所述第一持续时间包括以下至少一项:
SSB至RO的映射周期的M倍时间;
SSB至RO的映射关联周期的N倍时间;
SSB至RO的关联模式周期的L倍时间;
随机接入响应窗口对应的时间值;
SSB至PRACH重复传输的RO的关联模式周期;所述SSB至PRACH重复传输的RO的关联模式周期可以是针对PRACH重复传输额外配置的。
其中,M、N、L为正整数。所述M、N、L的具体数值可以由协议定义或者由***消息配置。
该实施例中,额外的定义SSB到PRACH重复传输的RO关联模式周期,其可以包括一个或多个SSB到RO关联模式周期,使得PRACH重复RO和SSB之间的模式最多可以在每个预定时间周期(例如,每640ms)重复。可选地,所述预定时间周期可以是SSB到(现有的、单次发送的)PRACH的RO关联模式周期的正整数倍。
可选地,所述方法还包括:向终端发送针对PRACH重复传输的资源配置信息,所述资源配置信息指示所述配置资源。
该实施例中,网络侧设备配置了针对PRACH重复传输的配置资源后,可以通过资源配置信息发送至所述终端,
本申请的实施例,网络侧设备针对PRACH重复传输配置资源,并确定配置的资源是否实际用于PRACH重复传输,使网络侧设备可以在实际用于PRACH重复传输的配置资源上接收重复传输的PRACH,能够降低随机接入延时。本申请实施例提供了配置资源无效或者与其他信号资源冲突时的解决方案,例如:针对PRACH repetition与其他资源相冲突时,部分PRACH repetition可以被丢弃或者不增加发送功率从而确保其他高优先级的信号可以按时发送或者接收;或者,为了确保实际PRACH repetition的数量,用于repetition的PRACH occasion需要向后推迟,跳过无效的或者不实际发送PRACH的RO;或者,即使第一次repetition的资源无效或者没有被实际发送 PRACH,后续repetition的PRACH资源还可以继续发送剩下的PRACH repetition,降低随机接入的延时。
本申请实施例提供的确定PRACH重复传输资源的方法,执行主体可以为确定PRACH重复传输资源的装置。本申请实施例中以确定PRACH重复传输资源的装置执行确定PRACH重复传输资源的方法为例,说明本申请实施例提供的确定PRACH重复传输资源的的装置。
如图11所示,本申请实施例提供一种确定PRACH重复传输资源的装置1100,应用于终端,包括:
第一获取模块1110,用于获取针对物理随机接入信道PRACH重复传输的资源配置信息,所述资源配置信息指示所述PRACH重复传输的配置资源;
第一确定模块1120,用于确定所述配置资源是否用于PRACH重复传输。
可选地,所述第一确定模块包括以下至少一项:
第一确定单元,用于根据所述配置资源的有效性,确定所述配置资源是否用于PRACH重复传输;
第二确定单元,用于根据所述配置资源所在符号的配置信息,确定所述配置资源是否用于PRACH重复传输;
第三确定单元,用于根据所述配置资源与其他信号资源的冲突情况,确定所述配置资源是否用于PRACH重复传输。
可选地,所述装置还包括:
第二确定模块,用于确定所述配置资源的有效性;
其中,所述配置资源的有效性,与第一间隙要求和/或时分复用TDD上下行链路配置相关;
所述第一间隙要求为SSB传输、用于SSB传输的符号集、用于PRACH传输的符号集三者之间的间隙要求。
可选地,所述第一确定单元包括至少一项:
第一确定子单元,用于根据所述配置资源中的第一RO的有效性,确定所述第一RO是否用于PRACH重复传输;
第二确定子单元,用于根据所述配置资源中的公共RO的有效性,确定所述配置资源中的第一RO是否用于PRACH重复传输;
其中,所述公共RO为所述PRACH重复传输与PRACH非重复传输使用的公共配置的RO;所述第一RO为仅用于PRACH重复传输的RO。
可选地,所述第一确定子单元具体用于:
若所述第一RO中的第一目标RO无效,则确定所述第一目标RO不用于PRACH重复传输。
可选地,所述装置还包括:
第一处理模块,用于将所述第一目标RO推迟一个RO级别的时域位置,获得第二目标RO,所述第二目标RO用于PRACH重复传输。
可选地,所述第一目标RO计入所述PRACH重复传输的RO数量。
可选地,所述第二确定子单元具体用于执行以下操作中的至少一项:
若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO不用于PRACH重复传输;
若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定与所述第一公共RO关联的第一RO不用于PRACH重复传输;
若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO用于PRACH重复传输;
若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定与所述第一公共RO关联的第一RO用于PRACH重复传输。
可选地,所述第二确定单元用于执行以下操作中的至少一项:
若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在专用TDD上下行链路配置信息中配置为下行链路,则确定所述第三目标RO不用于PRACH重复传输;
若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在DCI格式中配置为下行链路,则确定所述第三目标RO不用于PRACH重复传输;
若第一RO中的第三目标RO所在符号在第一配置信息中配置为灵活符号,且终端在所述符号上接收下行信号,则确定所述第三目标RO不用于PRACH重复传输;所述第一配置信息包括:公共TDD上下行链路配置信息、专用TDD上下行链路配置信息以及DCI格式中的至少一项;
其中,所述第一RO为所述配置资源中的仅用于PRACH重复传输的RO。
可选地,所述第三确定单元用于执行以下操作中的至少一项:
若第一RO中的第四目标RO与随机接入过程中的第一上行信息的传输资源至少部分重叠,则确定所述第四目标RO不用于PRACH重复传输;所述第一RO为所述配置资源中的仅用于PRACH重复传输的RO;
若高层信令指示终端在时隙内的一组符号中接收下行信号,DCI格式信息指示终端在第四目标RO进行PRACH重复传输,且所述第四目标RO与所述时隙所在的符号集合中的至少一个符号重叠,则确定所述第四目标RO不用于PRACH重复传输;
若高层信令指示终端在第四目标RO上的目标符号中进行PRACH重复传输,DCI格式信息指示终端在所述目标符号的符号子集中接收下行信号,则确定所述第四目标RO不用于PRACH重复传输。
可选地,所述装置还包括:
第三确定模块,用于确定所述PRACH重复传输的功率分配优先级;
所述功率分配优先级包括以下至少一项:
进行重复传输的PRACH的功率分配优先级低于在主小区上不做重复传输的PRACH的功率分配优先级;
进行重复传输的PRACH的功率分配优先级,与在主小区上不做重复传输的PRACH的功率分配优先级相同;
若在主小区上进行所述PRACH重复传输,则重复传输的PRACH的功率分配优先级,与在主小区上不做重复传输的PRACH的功率分配优先级相同;
若在非主小区上进行所述PRACH重复传输,则重复传输的PRACH的功率分配优先级,与在非主小区上不做重复传输的PRACH的功率分配优先级相同;
进行重复传输的PRACH的功率分配优先级,与在非主小区上不做重复传输的PRACH的功率分配优先级相同。
可选地,所述PRACH重复传输在第一持续时间内完成;
所述第一持续时间包括以下至少一项:
SSB至RO的映射周期的M倍时间;
SSB至RO的映射关联周期的N倍时间;
SSB至RO的关联模式周期的L倍时间;
随机接入响应窗口对应的时间值;
SSB至PRACH重复传输的RO的关联模式周期;
其中,M、N、L为正整数。
本申请实施例,终端获取针对PRACH重复传输的配置资源,并确定所述配置资源是否实际用于PRACH重复传输,提供了配置资源无效或者与其他信号资源冲突时的解决方案,能够降低随机接入延时。
需要说明的是,本申请实施例提供的确定PRACH重复传输资源的装置能够实现图4-图9的方法实施例实现的各个过程,并达到相同的技术效果,为避免重复,这里不再赘述。
如图12所示,本申请实施例提供一种确定PRACH重复传输资源的装置1200,应用于网络侧设备,包括:
第四确定模块1210,用于确定PRACH重复传输的配置资源;
第五确定模块1220,用于确定所述配置资源是否用于接收重复传输的PRACH。
可选地,所述第五确定模块包括:
第四确定单元,用于根据所述配置资源的有效性,确定所述配置资源是否用于接收重复传输的PRACH;
第五确定单元,用于根据所述配置资源所在符号的配置信息,确定所述配置资源是否用于接收重复传输的PRACH;
第六确定单元,用于根据所述配置资源与其他信号资源的冲突情况,确定所述配置资源是否用于接收重复传输的PRACH。
可选地,所述装置还包括:
第六确定模块,用于确定所述配置资源的有效性;
其中,所述配置资源的有效性,与第一间隙要求和/或时分复用TDD上下行链路配置相关;
所述第一间隙要求为同步信号块SSB传输、用于SSB传输的符号集、用于PRACH传输的符号集三者之间的间隙要求。
可选地,所述第四确定单元包括以下至少一项:
第三确定子单元,用于根据所述配置资源中的第一RO的有效性,确定所述配置资源是否用于接收重复传输的PRACH;
第四确定子单元,用于根据所述配置资源中的公共RO的有效性,确定所述配置资源是否用于接收重复传输的PRACH;
其中,所述公共RO为所述PRACH重复传输与PRACH非重复传输使用的公共配置的RO;所述第一RO为仅用于PRACH重复传输的RO。
可选地,所述第三确定子单元具体用于:
若所述第一RO中的第一目标RO无效,则确定所述第一目标RO不用于接收PRACH重复传输。
可选地,所述装置还包括:
第七确定模块,用于确定第二目标RO的时域位置,所述第二目标RO是将所述第一目标RO推迟一个RO级别的时域位置获得,所述第二目标RO用于接收重复传输的PRACH。
可选地,所述第四确定子单元用于执行以下操作中的至少一项:
若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO不用于接收重复传输的PRACH;
若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定所与所述第一公共RO关联的第一RO不用于接收重复传输的PRACH;
若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO用于接收重复传输的PRACH;
若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定与所述第一公共RO关联的第一RO用于接收重复传输的PRACH。
可选地,所述第五确定单元用于执行以下操作中的至少一项:
若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在专用TDD上下行链路配置信息中配置为下行链路,则确定所述第三目标RO不用于接收重复传输的PRACH;
若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在DCI格式中配置为下行链路,则确定所述第三目标RO 不用于接收重复传输的PRACH;
若第一RO中的第三目标RO所在符号在第一配置信息中配置为灵活符号,且终端在所述符号上接收下行信号,则确定所述第三目标RO不用于接收重复传输的PRACH;所述第一配置信息包括:公共TDD上下行链路配置信息、专用TDD上下行链路配置信息以及DCI格式中的至少一项;
其中,所述第一RO为所述配置资源中的仅用于PRACH重复传输的RO。
可选地,所述第六确定单元用于:
若第一RO中的第四目标RO与随机接入过程中的第一上行信息的传输资源至少部分重叠,则确定所述第四目标RO不用于接收重复传输的PRACH。
可选地,所述PRACH重复传输的接收在第一持续时间内完成;
所述第一持续时间包括以下至少一项:
SSB至RO的映射周期的M倍时间;
SSB至RO的映射关联周期的N倍时间;
SSB至RO的关联模式周期的L倍时间;
随机接入响应窗口对应的时间值;
SSB至PRACH重复传输的RO的关联模式周期;
其中,M、N、L为正整数。
可选地,所述装置还包括:
第一发送模块,用于向终端发送针对PRACH重复传输的资源配置信息,所述资源配置信息指示所述配置资源。
本申请的实施例,网络侧设备针对PRACH重复传输配置资源,并确定配置的资源是否实际用于PRACH重复传输,使网络侧设备可以在实际用于PRACH重复传输的配置资源上接收重复传输的PRACH,能够降低随机接入延时。
需要说明的是,本申请实施例提供的确定PRACH重复传输资源的装置能够实现图10的方法实施例实现的各个过程,并达到相同的技术效果,为避免重复,这里不再赘述。
本申请实施例中的确定PRACH重复传输资源的装置可以是电子设备,例如具有操作***的电子设备,也可以是电子设备中的部件,例如集成电路 或芯片。该电子设备可以是终端,也可以为除终端之外的其他设备。示例性的,终端可以包括但不限于上述所列举的终端11的类型,其他设备可以为服务器、网络附属存储器(Network Attached Storage,NAS)等,本申请实施例不作具体限定。
可选地,如图13所示,本申请实施例还提供一种通信设备1300,包括处理器1301和存储器1302,存储器1302上存储有可在所述处理器1301上运行的程序或指令,例如,该通信设备1300为终端时,该程序或指令被处理器1301执行时实现上述应用于终端的方法实施例的各个步骤,且能达到相同的技术效果。该通信设备1300为网络侧设备时,该程序或指令被处理器1301执行时实现上述应用于网络侧设备的方法实施例的各个步骤,且能达到相同的技术效果,为避免重复,这里不再赘述。
本申请实施例还提供一种终端,包括处理器和通信接口,处理器用于获取针对物理随机接入信道PRACH重复传输的资源配置信息,所述资源配置信息指示所述PRACH重复传输的配置资源;确定所述配置资源是否用于PRACH重复传输。该终端实施例与上述终端侧方法实施例对应,上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中,且能达到相同的技术效果。具体地,图14为实现本申请实施例的一种终端的硬件结构示意图。
该终端1400包括但不限于:射频单元1401、网络模块1402、音频输出单元1403、输入单元1404、传感器1405、显示单元1406、用户输入单元1407、接口单元1408、存储器1409以及处理器1410等中的至少部分部件。
本领域技术人员可以理解,终端1400还可以包括给各个部件供电的电源(比如电池),电源可以通过电源管理***与处理器1410逻辑相连,从而通过电源管理***实现管理充电、放电、以及功耗管理等功能。图14中示出的终端结构并不构成对终端的限定,终端可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置,在此不再赘述。
应理解的是,本申请实施例中,输入单元1404可以包括图形处理单元(Graphics Processing Unit,GPU)14041和麦克风14042,图形处理器14041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静 态图片或视频的图像数据进行处理。显示单元1406可包括显示面板14061,可以采用液晶显示器、有机发光二极管等形式来配置显示面板14061。用户输入单元1407包括触控面板14071以及其他输入设备14072中的至少一种。触控面板14071,也称为触摸屏。触控面板14071可包括触摸检测装置和触摸控制器两个部分。其他输入设备14072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆,在此不再赘述。
本申请实施例中,射频单元1401接收来自网络侧设备的下行数据后,可以传输给处理器1410进行处理;另外,射频单元1401可以向网络侧设备发送上行数据。通常,射频单元1401包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器1409可用于存储软件程序或指令以及各种数据。存储器1409可主要包括存储程序或指令的第一存储区和存储数据的第二存储区,其中,第一存储区可存储操作***、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外,存储器1409可以包括易失性存储器或非易失性存储器,或者,存储器1409可以包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(Read-Only Memory,ROM)、可编程只读存储器(Programmable ROM,PROM)、可擦除可编程只读存储器(Erasable PROM,EPROM)、电可擦除可编程只读存储器(Electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory,RAM),静态随机存取存储器(Static RAM,SRAM)、动态随机存取存储器(Dynamic RAM,DRAM)、同步动态随机存取存储器(Synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM,DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM,SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM,DRRAM)。本申请实施例中的存储器1409包括但不限于这些和任意其它适合类型的存储器。
处理器1410可包括一个或多个处理单元;可选地,处理器1410集成应用处理器和调制解调处理器,其中,应用处理器主要处理涉及操作***、用 户界面和应用程序等的操作,调制解调处理器主要处理无线通信信号,如基带处理器。可以理解的是,上述调制解调处理器也可以不集成到处理器1410中。
其中,处理器1410,用于获取针对物理随机接入信道PRACH重复传输的资源配置信息,所述资源配置信息指示所述PRACH重复传输的配置资源;确定所述配置资源是否用于PRACH重复传输。
本申请的实施例,终端获取针对PRACH重复传输的配置资源,并确定所述配置资源是否实际用于PRACH重复传输,使终端利用能够实际用于PRACH重复传输的配置资源进行PRACH重复发送,能够降低随机接入延时。
可选地,所述处理器1410还用于执行以下操作中的至少一项:
根据所述配置资源的有效性,确定所述配置资源是否用于PRACH重复传输;
根据所述配置资源所在符号的配置信息,确定所述配置资源是否用于PRACH重复传输;
根据所述配置资源与其他信号资源的冲突情况,确定所述配置资源是否用于PRACH重复传输。
可选地,所述处理器1410还用于:确定所述配置资源的有效性;
其中,所述配置资源的有效性,与第一间隙要求和/或时分复用TDD上下行链路配置相关;
所述第一间隙要求为同步信号块SSB传输、用于SSB传输的符号集、用于PRACH传输的符号集三者之间的间隙要求。
可选地,所述处理器1410还用于执行以下操作中的至少一项:
根据所述配置资源中的第一RO的有效性,确定所述第一RO是否用于PRACH重复传输;
根据所述配置资源中的公共RO的有效性,确定所述配置资源中的第一RO是否用于PRACH重复传输;
其中,所述公共RO为所述PRACH重复传输与PRACH非重复传输使用的公共配置的RO;所述第一RO为仅用于PRACH重复传输的RO。
可选地,所述处理器1410还用于:若所述第一RO中的第一目标RO无 效,则确定所述第一目标RO不用于PRACH重复传输。
可选地,所述处理器1410还用于:将所述第一目标RO推迟一个RO级别的时域位置,获得第二目标RO,所述第二目标RO用于PRACH重复传输。
可选地,所述第一目标RO计入所述PRACH重复传输的RO数量。
可选地,所述处理器1410还用于执行以下操作中的至少一项:
若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO不用于PRACH重复传输;
若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定与所述第一公共RO关联的第一RO不用于PRACH重复传输;
若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO用于PRACH重复传输;
若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定与所述第一公共RO关联的第一RO用于PRACH重复传输。
可选地,所述处理器1410还用于执行以下操作中的至少一项:
若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在专用TDD上下行链路配置信息中配置为下行链路,则确定所述第三目标RO不用于PRACH重复传输;
若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在DCI格式中配置为下行链路,则确定所述第三目标RO不用于PRACH重复传输;
若第一RO中的第三目标RO所在符号在第一配置信息中配置为灵活符号,且终端在所述符号上接收下行信号,则确定所述第三目标RO不用于PRACH重复传输;所述第一配置信息包括:公共TDD上下行链路配置信息、专用TDD上下行链路配置信息以及DCI格式中的至少一项;
其中,所述第一RO为所述配置资源中的仅用于PRACH重复传输的RO。
可选地,所述处理器1410还用于执行以下操作中的至少一项:
若第一RO中的第四目标RO与随机接入过程中的第一上行信息的传输资源至少部分重叠,则确定所述第四目标RO不用于PRACH重复传输;所述第一RO为所述配置资源中的仅用于PRACH重复传输的RO;
若高层信令指示终端在时隙内的一组符号中接收下行信号,DCI格式信息指示终端在第四目标RO进行PRACH重复传输,且所述第四目标RO与所述时隙所在的符号集合中的至少一个符号重叠,则确定所述第四目标RO不用于PRACH重复传输;
若高层信令指示终端在第四目标RO上的目标符号中进行PRACH重复传输,DCI格式信息指示终端在所述目标符号的符号子集中接收下行信号,则确定所述第四目标RO不用于PRACH重复传输。
可选地,所述处理器1410还用于:确定所述PRACH重复传输的功率分配优先级;
所述功率分配优先级包括以下至少一项:
进行重复传输的PRACH的功率分配优先级低于在主小区上不做重复传输的PRACH的功率分配优先级;
进行重复传输的PRACH的功率分配优先级,与在主小区上不做重复传输的PRACH的功率分配优先级相同;
若在主小区上进行所述PRACH重复传输,则重复传输的PRACH的功率分配优先级,与在主小区上不做重复传输的PRACH的功率分配优先级相同;
若在非主小区上进行所述PRACH重复传输,则重复传输的PRACH的功率分配优先级,与在非主小区上不做重复传输的PRACH的功率分配优先级相同;
进行重复传输的PRACH的功率分配优先级,与在非主小区上不做重复传输的PRACH的功率分配优先级相同。
可选地,所述PRACH重复传输在第一持续时间内完成;
所述第一持续时间包括以下至少一项:
SSB至RO的映射周期的M倍时间;
SSB至RO的映射关联周期的N倍时间;
SSB至RO的关联模式周期的L倍时间;
随机接入响应窗口对应的时间值;
SSB至PRACH重复传输的RO的关联模式周期;
其中,M、N、L为正整数。
本申请的实施例,终端获取针对PRACH重复传输的配置资源,并确定所述配置资源是否实际用于PRACH重复传输,使终端利用能够实际用于PRACH重复传输的配置资源进行PRACH重复发送,能够降低随机接入延时。
本申请实施例还提供一种网络侧设备,包括处理器和通信接口,处理器用于确定PRACH重复传输的配置资源;确定所述配置资源是否用于接收重复传输的PRACH。该网络侧设备实施例与上述网络侧设备方法实施例对应,上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中,且能达到相同的技术效果。
具体地,本申请实施例还提供了一种网络侧设备。如图15所示,该网络侧设备1500包括:天线151、射频装置152、基带装置153、处理器154和存储器155。天线151与射频装置152连接。在上行方向上,射频装置152通过天线151接收信息,将接收的信息发送给基带装置153进行处理。在下行方向上,基带装置153对要发送的信息进行处理,并发送给射频装置152,射频装置152对收到的信息进行处理后经过天线151发送出去。
以上实施例中网络侧设备执行的方法可以在基带装置153中实现,该基带装置153包括基带处理器。
基带装置153例如可以包括至少一个基带板,该基带板上设置有多个芯片,如图15所示,其中一个芯片例如为基带处理器,通过总线接口与存储器155连接,以调用存储器155中的程序,执行以上方法实施例中所述的网络设备操作。
该网络侧设备还可以包括网络接口156,该接口例如为通用公共无线接口(common public radio interface,CPRI)。
具体地,本发明实施例的网络侧设备1500还包括:存储在存储器155上并可在处理器154上运行的指令或程序,处理器154调用存储器155中的指令或程序执行图12所示各模块执行的方法,并达到相同的技术效果,为避免重复,故不在此赘述。
本申请实施例还提供一种可读存储介质,所述可读存储介质上存储有程序或指令,该程序或指令被处理器执行时实现上述确定PRACH重复传输资源的方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里 不再赘述。
其中,所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质,包括计算机可读存储介质,如计算机只读存储器ROM、随机存取存储器RAM、磁盘或者光盘等。
本申请实施例另提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现上述确定PRACH重复传输资源的方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
应理解,本申请实施例提到的芯片还可以称为***级芯片,***芯片,芯片***或片上***芯片等。
本申请实施例另提供了一种计算机程序/程序产品,所述计算机程序/程序产品被存储在存储介质中,所述计算机程序/程序产品被至少一个处理器执行以实现上述确定PRACH重复传输资源的方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
本申请实施例还提供了一种确定PRACH重复传输资源的***,包括:终端及网络侧设备,所述终端可用于执行如上所述的应用于终端的确定PRACH重复传输资源的方法的步骤,所述网络侧设备可用于执行如上所述的应用于网络侧设备的确定PRACH重复传输资源的方法的步骤。
需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外,需要指出的是,本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能,还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能,例如,可以按不同于所描述的次序来执行所描述的方法,并且还可以添加、省去、或组合各种步骤。另外,参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁盘、光盘)中,包括若干指令用以使得一台终端(可以是手机,计算机,服务器,空调器,或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述,但是本申请并不局限于上述的具体实施方式,上述的具体实施方式仅仅是示意性的,而不是限制性的,本领域的普通技术人员在本申请的启示下,在不脱离本申请宗旨和权利要求所保护的范围情况下,还可做出很多形式,均属于本申请的保护之内。
Claims (49)
- 一种确定PRACH重复传输资源的方法,包括:终端获取针对物理随机接入信道PRACH重复传输的资源配置信息,所述资源配置信息指示所述PRACH重复传输的配置资源;所述终端确定所述配置资源是否用于PRACH重复传输。
- 根据权利要求1所述的方法,其中,所述确定所述配置资源是否用于PRACH重复传输,包括以下至少一项:根据所述配置资源的有效性,确定所述配置资源是否用于PRACH重复传输;根据所述配置资源所在符号的配置信息,确定所述配置资源是否用于PRACH重复传输;根据所述配置资源与其他信号资源的冲突情况,确定所述配置资源是否用于PRACH重复传输。
- 根据权利要求2所述的方法,其中,所述方法还包括:确定所述配置资源的有效性;其中,所述配置资源的有效性,与第一间隙要求和/或时分复用TDD上下行链路配置相关;所述第一间隙要求为同步信号块SSB传输、用于SSB传输的符号集、用于PRACH传输的符号集三者之间的间隙要求。
- 根据权利要求2所述的方法,其中,所述根据所述配置资源的有效性,确定所述配置资源是否用于PRACH重复传输,包括以下至少一项:根据所述配置资源中的第一RO的有效性,确定所述第一RO是否用于PRACH重复传输;根据所述配置资源中的公共RO的有效性,确定所述配置资源中的第一RO是否用于PRACH重复传输;其中,所述公共RO为所述PRACH重复传输与PRACH非重复传输使用的公共配置的RO;所述第一RO为仅用于PRACH重复传输的RO。
- 根据权利要求4所述的方法,其中,所述根据所述配置资源中的第一 RO的有效性,确定所述第一RO是否用于PRACH重复传输,包括:若所述第一RO中的第一目标RO无效,则确定所述第一目标RO不用于PRACH重复传输。
- 根据权利要求5所述的方法,其中,所述方法还包括:将所述第一目标RO推迟一个RO级别的时域位置,获得第二目标RO,所述第二目标RO用于PRACH重复传输。
- 根据权利要求5所述的方法,其中,所述第一目标RO计入所述PRACH重复传输的RO数量。
- 根据权利要求4所述的方法,其中,所述根据所述配置资源中的公共RO的有效性,确定所述配置资源中的第一RO是否用于PRACH重复传输,包括以下至少一项:若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO不用于PRACH重复传输;若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定与所述第一公共RO关联的第一RO不用于PRACH重复传输;若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO用于PRACH重复传输;若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定与所述第一公共RO关联的第一RO用于PRACH重复传输。
- 根据权利要求2所述的方法,其中,所述根据所述配置资源所在符号的配置信息,确定所述配置资源是否用于PRACH重复传输,包括以下至少一项:若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在专用TDD上下行链路配置信息中配置为下行链路,则确定所述第三目标RO不用于PRACH重复传输;若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在DCI格式中配置为下行链路,则确定所述第三目标RO不用于PRACH重复传输;若第一RO中的第三目标RO所在符号在第一配置信息中配置为灵活符 号,且终端在所述符号上接收下行信号,则确定所述第三目标RO不用于PRACH重复传输;所述第一配置信息包括:公共TDD上下行链路配置信息、专用TDD上下行链路配置信息以及DCI格式中的至少一项;其中,所述第一RO为所述配置资源中的仅用于PRACH重复传输的RO。
- 根据权利要求2所述的方法,其中,所述根据所述配置资源与其他信号资源的冲突情况,确定所述配置资源是否用于PRACH重复传输,包括以下至少一项:若第一RO中的第四目标RO与随机接入过程中的第一上行信息的传输资源至少部分重叠,则确定所述第四目标RO不用于PRACH重复传输;所述第一RO为所述配置资源中的仅用于PRACH重复传输的RO;若高层信令指示终端在时隙内的一组符号中接收下行信号,DCI格式信息指示终端在第四目标RO进行PRACH重复传输,且所述第四目标RO与所述时隙所在的符号集合中的至少一个符号重叠,则确定所述第四目标RO不用于PRACH重复传输;若高层信令指示终端在第四目标RO上的目标符号中进行PRACH重复传输,DCI格式信息指示终端在所述目标符号的符号子集中接收下行信号,则确定所述第四目标RO不用于PRACH重复传输。
- 根据权利要求1所述的方法,其中,所述方法还包括:确定所述PRACH重复传输的功率分配优先级;所述功率分配优先级包括以下至少一项:进行重复传输的PRACH的功率分配优先级低于在主小区上不做重复传输的PRACH的功率分配优先级;进行重复传输的PRACH的功率分配优先级,与在主小区上不做重复传输的PRACH的功率分配优先级相同;若在主小区上进行所述PRACH重复传输,则重复传输的PRACH的功率分配优先级,与在主小区上不做重复传输的PRACH的功率分配优先级相同;若在非主小区上进行所述PRACH重复传输,则重复传输的PRACH的功率分配优先级,与在非主小区上不做重复传输的PRACH的功率分配优先级相同;进行重复传输的PRACH的功率分配优先级,与在非主小区上不做重复传输的PRACH的功率分配优先级相同。
- 根据权利要求1所述的方法,其中,所述PRACH重复传输在第一持续时间内完成;所述第一持续时间包括以下至少一项:SSB至RO的映射周期的M倍时间;SSB至RO的映射关联周期的N倍时间;SSB至RO的关联模式周期的L倍时间;随机接入响应窗口对应的时间值;SSB至PRACH重复传输的RO的关联模式周期;其中,M、N、L为正整数。
- 一种确定PRACH重复传输资源的方法,包括:网络侧设备确定PRACH重复传输的配置资源;所述网络侧设备确定所述配置资源是否用于接收重复传输的PRACH。
- 根据权利要求13所述的方法,其中,所述确定所述配置资源是否用于接收重复传输的PRACH,包括以下至少一项:根据所述配置资源的有效性,确定所述配置资源是否用于接收重复传输的PRACH;根据所述配置资源所在符号的配置信息,确定所述配置资源是否用于接收重复传输的PRACH;根据所述配置资源与其他信号资源的冲突情况,确定所述配置资源是否用于接收重复传输的PRACH。
- 根据权利要求14所述的方法,其中,所述方法还包括:确定所述配置资源的有效性;其中,所述配置资源的有效性,与第一间隙要求和/或时分复用TDD上下行链路配置相关;所述第一间隙要求为SSB传输、用于SSB传输的符号集、用于PRACH传输的符号集三者之间的间隙要求。
- 根据权利要求14所述的方法,其中,所述根据所述配置资源的有效 性,确定所述配置资源是否用于接收重复传输的PRACH,包括以下至少一项:根据所述配置资源中的第一RO的有效性,确定所述配置资源是否用于接收重复传输的PRACH;根据所述配置资源中的公共RO的有效性,确定所述配置资源是否用于接收重复传输的PRACH;其中,所述公共RO为所述PRACH重复传输与PRACH非重复传输使用的公共配置的RO;所述第一RO为仅用于PRACH重复传输的RO。
- 根据权利要求16所述的方法,其中,所述根据所述配置资源中的第一RO的有效性,确定所述配置资源是否用于接收重复传输的PRACH,包括:若所述第一RO中的第一目标RO无效,则确定所述第一目标RO不用于接收PRACH重复传输。
- 根据权利要求17所述的方法,其中,所述方法还包括:确定第二目标RO的时域位置,所述第二目标RO是将所述第一目标RO推迟一个RO级别的时域位置获得,所述第二目标RO用于接收重复传输的PRACH。
- 根据权利要求16所述的方法,其中,所述根据所述配置资源中的公共RO的有效性,确定所述配置资源是否用于接收重复传输的PRACH,包括以下至少一项:若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO不用于接收重复传输的PRACH;若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定与所述第一公共RO关联的第一RO不用于接收重复传输的PRACH;若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO用于接收重复传输的PRACH;若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定与所述第一公共RO关联的第一RO用于接收重复传输的PRACH。
- 根据权利要求14所述的方法,其中,所述根据所述配置资源所在符号的配置信息,确定所述配置资源是否用于接收重复传输的PRACH,包括以下至少一项:若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在专用TDD上下行链路配置信息中配置为下行链路,则确定所述第三目标RO不用于接收重复传输的PRACH;若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在DCI格式中配置为下行链路,则确定所述第三目标RO不用于接收重复传输的PRACH;若第一RO中的第三目标RO所在符号在第一配置信息中配置为灵活符号,且终端在所述符号上接收下行信号,则确定所述第三目标RO不用于接收重复传输的PRACH;所述第一配置信息包括:公共TDD上下行链路配置信息、专用TDD上下行链路配置信息以及DCI格式中的至少一项;其中,所述第一RO为所述配置资源中的仅用于PRACH重复传输的RO。
- 根据权利要求14所述的方法,其中,根据所述配置资源与其他信号资源的冲突情况,确定所述配置资源是否用于接收重复传输的PRACH,包括:若第一RO中的第四目标RO与随机接入过程中的第一上行信息的传输资源至少部分重叠,则确定所述第四目标RO不用于接收重复传输的PRACH。
- 根据权利要求13所述的方法,其中,所述PRACH重复传输的接收在第一持续时间内完成;所述第一持续时间包括以下至少一项:SSB至RO的映射周期的M倍时间;SSB至RO的映射关联周期的N倍时间;SSB至RO的关联模式周期的L倍时间;随机接入响应窗口对应的时间值;SSB至PRACH重复传输的RO的关联模式周期;其中,M、N、L为正整数。
- 根据权利要求13所述的方法,其中,所述方法还包括:向终端发送针对PRACH重复传输的资源配置信息,所述资源配置信息指示所述配置资源。
- 一种确定PRACH重复传输资源的装置,包括:第一获取模块,用于获取针对物理随机接入信道PRACH重复传输的资 源配置信息,所述资源配置信息指示所述PRACH重复传输的配置资源;第一确定模块,用于确定所述配置资源是否用于PRACH重复传输。
- 根据权利要求24所述的装置,其中,所述第一确定模块包括以下至少一项:第一确定单元,用于根据所述配置资源的有效性,确定所述配置资源是否用于PRACH重复传输;第二确定单元,用于根据所述配置资源所在符号的配置信息,确定所述配置资源是否用于PRACH重复传输;第三确定单元,用于根据所述配置资源与其他信号资源的冲突情况,确定所述配置资源是否用于PRACH重复传输。
- 根据权利要求25所述的装置,其中,所述装置还包括:第二确定模块,用于确定所述配置资源的有效性;其中,所述配置资源的有效性,与第一间隙要求和/或时分复用TDD上下行链路配置相关;所述第一间隙要求为SSB传输、用于SSB传输的符号集、用于PRACH传输的符号集三者之间的间隙要求。
- 根据权利要求25所述的装置,其中,所述第一确定单元包括至少一项:第一确定子单元,用于根据所述配置资源中的第一RO的有效性,确定所述第一RO是否用于PRACH重复传输;第二确定子单元,用于根据所述配置资源中的公共RO的有效性,确定所述配置资源中的第一RO是否用于PRACH重复传输;其中,所述公共RO为所述PRACH重复传输与PRACH非重复传输使用的公共配置的RO;所述第一RO为仅用于PRACH重复传输的RO。
- 根据权利要求27所述的装置,其中,所述第一确定子单元具体用于:若所述第一RO中的第一目标RO无效,则确定所述第一目标RO不用于PRACH重复传输。
- 根据权利要求28所述的装置,其中,所述装置还包括:第一处理模块,用于将所述第一目标RO推迟一个RO级别的时域位置, 获得第二目标RO,所述第二目标RO用于PRACH重复传输。
- 根据权利要求28所述的装置,其中,所述第一目标RO计入所述PRACH重复传输的RO数量。
- 根据权利要求27所述的装置,其中,所述第二确定子单元具体用于执行以下操作中的至少一项:若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO不用于PRACH重复传输;若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定与所述第一公共RO关联的第一RO不用于PRACH重复传输;若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO用于PRACH重复传输;若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定与所述第一公共RO关联的第一RO用于PRACH重复传输。
- 根据权利要求25所述的装置,其中,所述第二确定单元用于执行以下操作中的至少一项:若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在专用TDD上下行链路配置信息中配置为下行链路,则确定所述第三目标RO不用于PRACH重复传输;若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在DCI格式中配置为下行链路,则确定所述第三目标RO不用于PRACH重复传输;若第一RO中的第三目标RO所在符号在第一配置信息中配置为灵活符号,且终端在所述符号上接收下行信号,则确定所述第三目标RO不用于PRACH重复传输;所述第一配置信息包括:公共TDD上下行链路配置信息、专用TDD上下行链路配置信息以及DCI格式中的至少一项;其中,所述第一RO为所述配置资源中的仅用于PRACH重复传输的RO。
- 根据权利要求25所述的装置,其中,所述第三确定单元用于执行以下操作中的至少一项:若第一RO中的第四目标RO与随机接入过程中的第一上行信息的传输 资源至少部分重叠,则确定所述第四目标RO不用于PRACH重复传输;所述第一RO为所述配置资源中的仅用于PRACH重复传输的RO;若高层信令指示终端在时隙内的一组符号中接收下行信号,DCI格式信息指示终端在第四目标RO进行PRACH重复传输,且所述第四目标RO与所述时隙所在的符号集合中的至少一个符号重叠,则确定所述第四目标RO不用于PRACH重复传输;若高层信令指示终端在第四目标RO上的目标符号中进行PRACH重复传输,DCI格式信息指示终端在所述目标符号的符号子集中接收下行信号,则确定所述第四目标RO不用于PRACH重复传输。
- 根据权利要求24所述的装置,其中,所述装置还包括:第三确定模块,用于确定所述PRACH重复传输的功率分配优先级;所述功率分配优先级包括以下至少一项:进行重复传输的PRACH的功率分配优先级低于在主小区上不做重复传输的PRACH的功率分配优先级;进行重复传输的PRACH的功率分配优先级,与在主小区上不做重复传输的PRACH的功率分配优先级相同;若在主小区上进行所述PRACH重复传输,则重复传输的PRACH的功率分配优先级,与在主小区上不做重复传输的PRACH的功率分配优先级相同;若在非主小区上进行所述PRACH重复传输,则重复传输的PRACH的功率分配优先级,与在非主小区上不做重复传输的PRACH的功率分配优先级相同;进行重复传输的PRACH的功率分配优先级,与在非主小区上不做重复传输的PRACH的功率分配优先级相同。
- 根据权利要求24所述的装置,其中,所述PRACH重复传输在第一持续时间内完成;所述第一持续时间包括以下至少一项:SSB至RO的映射周期的M倍时间;SSB至RO的映射关联周期的N倍时间;SSB至RO的关联模式周期的L倍时间;随机接入响应窗口对应的时间值;SSB至PRACH重复传输的RO的关联模式周期;其中,M、N、L为正整数。
- 一种确定PRACH重复传输资源的装置,包括:第四确定模块,用于确定PRACH重复传输的配置资源;第五确定模块,用于确定所述配置资源是否用于接收重复传输的PRACH。
- 根据权利要求36所述的装置,其中,所述第五确定模块包括:第四确定单元,用于根据所述配置资源的有效性,确定所述配置资源是否用于接收重复传输的PRACH;第五确定单元,用于根据所述配置资源所在符号的配置信息,确定所述配置资源是否用于接收重复传输的PRACH;第六确定单元,用于根据所述配置资源与其他信号资源的冲突情况,确定所述配置资源是否用于接收重复传输的PRACH。
- 根据权利要求37所述的装置,其中,所述装置还包括:第六确定模块,用于确定所述配置资源的有效性;其中,所述配置资源的有效性,与第一间隙要求和/或时分复用TDD上下行链路配置相关;所述第一间隙要求为SSB传输、用于SSB传输的符号集、用于PRACH传输的符号集三者之间的间隙要求。
- 根据权利要求37所述的装置,其中,所述第四确定单元包括以下至少一项:第三确定子单元,用于根据所述配置资源中的第一RO的有效性,确定所述配置资源是否用于接收重复传输的PRACH;第四确定子单元,用于根据所述配置资源中的公共RO的有效性,确定所述配置资源是否用于接收重复传输的PRACH;其中,所述公共RO为所述PRACH重复传输与PRACH非重复传输使用的公共配置的RO;所述第一RO为仅用于PRACH重复传输的RO。
- 根据权利要求39所述的装置,其中,所述第三确定子单元具体用于:若所述第一RO中的第一目标RO无效,则确定所述第一目标RO不用于 接收PRACH重复传输。
- 根据权利要求40所述的装置,其中,所述装置还包括:第七确定模块,用于确定第二目标RO的时域位置,所述第二目标RO是将所述第一目标RO推迟一个RO级别的时域位置获得,所述第二目标RO用于接收重复传输的PRACH。
- 根据权利要求39所述的装置,其中,所述第四确定子单元用于执行以下操作中的至少一项:若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO不用于接收重复传输的PRACH;若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定所与所述第一公共RO关联的第一RO不用于接收重复传输的PRACH;若所述公共RO中的第一公共RO无效,则确定与所述第一公共RO关联的第一RO用于接收重复传输的PRACH;若所述公共RO中的第一公共RO有效但未用于PRACH重复传输,则确定与所述第一公共RO关联的第一RO用于接收重复传输的PRACH。
- 根据权利要求37所述的装置,其中,所述第五确定单元用于执行以下操作中的至少一项:若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在专用TDD上下行链路配置信息中配置为下行链路,则确定所述第三目标RO不用于接收重复传输的PRACH;若第一RO中的第三目标RO所在符号在公共TDD上下行链路配置信息中配置为灵活符号,在DCI格式中配置为下行链路,则确定所述第三目标RO不用于接收重复传输的PRACH;若第一RO中的第三目标RO所在符号在第一配置信息中配置为灵活符号,且终端在所述符号上接收下行信号,则确定所述第三目标RO不用于接收重复传输的PRACH;所述第一配置信息包括:公共TDD上下行链路配置信息、专用TDD上下行链路配置信息以及DCI格式中的至少一项;其中,所述第一RO为所述配置资源中的仅用于PRACH重复传输的RO。
- 根据权利要求37所述的装置,其中,所述第六确定单元用于:若第一RO中的第四目标RO与随机接入过程中的第一上行信息的传输资源至少部分重叠,则确定所述第四目标RO不用于接收重复传输的PRACH。
- 根据权利要求36所述的装置,其中,所述PRACH重复传输的接收在第一持续时间内完成;所述第一持续时间包括以下至少一项:SSB至RO的映射周期的M倍时间;SSB至RO的映射关联周期的N倍时间;SSB至RO的关联模式周期的L倍时间;随机接入响应窗口对应的时间值;SSB至PRACH重复传输的RO的关联模式周期;其中,M、N、L为正整数。
- 根据权利要求36所述的装置,其中,所述装置还包括:第一发送模块,用于向终端发送针对PRACH重复传输的资源配置信息,所述资源配置信息指示所述配置资源。
- 一种终端,包括处理器和存储器,所述存储器存储可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如权利要求1至12任一项所述的确定PRACH重复传输资源的方法的步骤。
- 一种网络侧设备,包括处理器和存储器,所述存储器存储可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如权利要求13至23任一项所述的确定PRACH重复传输资源的方法的步骤。
- 一种可读存储介质,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时实现如权利要求1-12任一项所述的确定PRACH重复传输资源的方法的步骤,或者实现如权利要求13至23任一项所述的确定PRACH重复传输资源的方法的步骤。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210006549.6 | 2022-01-05 | ||
CN202210006549.6A CN116456488A (zh) | 2022-01-05 | 2022-01-05 | 确定prach重复传输资源的方法、终端及网络侧设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023131175A1 true WO2023131175A1 (zh) | 2023-07-13 |
Family
ID=87073245
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2023/070396 WO2023131175A1 (zh) | 2022-01-05 | 2023-01-04 | 确定prach重复传输资源的方法、终端及网络侧设备 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN116456488A (zh) |
WO (1) | WO2023131175A1 (zh) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2020134809A1 (zh) * | 2018-12-24 | 2020-07-02 | 维沃移动通信有限公司 | 随机接入方法、网络侧设备和终端 |
US20210307078A1 (en) * | 2018-08-08 | 2021-09-30 | Samsung Electronics Co., Ltd. | Method and system for performing random access channel procedure for unlicensed operation |
WO2021221381A1 (ko) * | 2020-04-29 | 2021-11-04 | 주식회사 아이티엘 | 무선 통신 시스템에서 저감 캐퍼빌리티 단말을 위한 랜덤 액세스 방법 및 장치 |
US20210360660A1 (en) * | 2020-05-15 | 2021-11-18 | Samsung Electronics Co., Ltd. | Method and apparatus for coverage enhancement of msg3 |
-
2022
- 2022-01-05 CN CN202210006549.6A patent/CN116456488A/zh active Pending
-
2023
- 2023-01-04 WO PCT/CN2023/070396 patent/WO2023131175A1/zh unknown
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210307078A1 (en) * | 2018-08-08 | 2021-09-30 | Samsung Electronics Co., Ltd. | Method and system for performing random access channel procedure for unlicensed operation |
WO2020134809A1 (zh) * | 2018-12-24 | 2020-07-02 | 维沃移动通信有限公司 | 随机接入方法、网络侧设备和终端 |
WO2021221381A1 (ko) * | 2020-04-29 | 2021-11-04 | 주식회사 아이티엘 | 무선 통신 시스템에서 저감 캐퍼빌리티 단말을 위한 랜덤 액세스 방법 및 장치 |
US20210360660A1 (en) * | 2020-05-15 | 2021-11-18 | Samsung Electronics Co., Ltd. | Method and apparatus for coverage enhancement of msg3 |
Non-Patent Citations (1)
Title |
---|
HUAWEI ET AL.: "On PRACH resource indication and level determination during random access", 3GPP TSG RAN WG1 MEETING #83 R1-156446, no. TSGR1_83, 22 November 2015 (2015-11-22), XP051002908 * |
Also Published As
Publication number | Publication date |
---|---|
CN116456488A (zh) | 2023-07-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10999846B2 (en) | Resource allocation in random access procedure | |
US11937308B2 (en) | Two-step contention-based random access over radio resources in LAA | |
KR102429435B1 (ko) | 랜덤 액세스 프로세스에서 시간-주파수 리소스를 결정하고 구성하는 방법들 및 장치들 | |
CN105981453B (zh) | 用于在无网络覆盖下设备到设备通信中的初始同步和冲突避免的方法和*** | |
EP3337247A1 (en) | Random access response transmission method and device | |
WO2016127392A1 (en) | Methods and devices for random access | |
KR20170043539A (ko) | 면허 및 비면허 대역에 대한 통신 | |
US10869339B2 (en) | Method, device, computer-readable storage and carrier for random access | |
US20230156782A1 (en) | Random access method, configuration method, and related device | |
CN113973271A (zh) | 重复传输方法、装置及用户设备 | |
CN114080047B (zh) | 随机接入的信号传输方法、终端及网络侧设备 | |
WO2023116883A1 (zh) | Msg1重复传输的时频资源确定方法、装置及终端 | |
CN109600833A (zh) | 一种确定传输资源的方法及设备 | |
US20220046619A1 (en) | Base station, terminal, and wireless communication system | |
WO2023131175A1 (zh) | 确定prach重复传输资源的方法、终端及网络侧设备 | |
JP2023534661A (ja) | フィードバック情報伝送方法、装置、端末及びネットワーク側機器 | |
CN116208269A (zh) | 信息传输方法及设备 | |
WO2023131174A1 (zh) | Prach重复传输方法、终端及网络侧设备 | |
CN112584540A (zh) | 随机接入信号发送方法、执行该方法的设备和计算机可读介质 | |
WO2024152994A1 (zh) | 随机接入处理方法、装置、终端及网络侧设备 | |
WO2023116599A1 (zh) | Prach传输方法、装置、终端及网络侧设备 | |
WO2018139970A1 (en) | Control plane latency reduction in a wireless communications network | |
WO2023083290A1 (zh) | 随机接入方法、装置、终端及网络侧设备 | |
WO2023207785A1 (zh) | 终端操作方法、装置、终端及网络侧设备 | |
CN117858264A (zh) | 随机接入配置方法、装置、终端及网络侧设备 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 23737038 Country of ref document: EP Kind code of ref document: A1 |