Systems, methods, and non-transitory processor-readable media for indicating duplicate information for retransmission
By configuring appropriate time and frequency domain resources in the cellular communication network and optimizing PRACH repeated transmission, the problems of coverage evaluation and low efficiency under the new 5G air interface standard are solved, and the coverage and access performance of the cellular communication network are improved.
Patent Information
- Application Number
- CN202280094061.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-08-02
- Publication Date
- 2024-11-15
AI Technical Summary
When the existing cellular communication networks implement the new 5G air interface (NR) standard, they fail to fully evaluate the comparison between the coverage and traditional wireless access technology, resulting in low PRACH repeated transmission efficiency, affecting service quality and capital operation expenditure.
By configuring time domain resources and frequency domain resources for PRACH repetition between the user equipment and the base station, using multiple time domain window combinations and frequency domain resource configurations, the repeated transmission process of PRACH is optimized and coverage and reception performance is improved.
It effectively improves the coverage and efficiency of PRACH, recognizes the best transmission beam, improves the performance of the access process, and reduces operating costs.
Smart Images

Figure CN118975357A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to wireless communications and, more particularly, to systems, methods, and non-transitory processor-readable media that indicate repetitive information for transmission. Background Art
[0002] Currently, the first phase of standardization of the fifth generation mobile communication technology (5G) has been completed. A series of features are specified in the first three new radio (NR) versions (i.e., Rel-15, Rel-16 and Rel-17). Coverage is a key factor in the implementation of cellular communication networks due to its direct impact on service quality as well as capital expenditure (CAPEX) and operational expenditure (OPEX). Although coverage is important for the success of NR implementation, to date, no comprehensive coverage assessment has been conducted considering all NR specification details and compared with traditional radio access technology (RAT). Summary of the invention
[0003] In some deployments, systems, methods, apparatuses, and non-transitory computer-readable media are used by a user equipment (UE) to determine time domain resources and frequency domain resources for transmitting at least one physical random access channel (PRACH) repetition. The UE uses the time domain resources and frequency domain resources to transmit at least one PRACH repetition to a base station.
[0004] In some deployments, systems, methods, apparatuses, and non-transitory computer-readable media are used by a base station to configure time domain resources and frequency domain resources for transmitting at least one PRACH repetition for a UE. The base station uses the time domain resources and frequency domain resources to receive at least one PRACH repetition from the UE.
[0005] The above and other aspects and embodiments thereof are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0006] Various example deployments of the present solution are described in detail below with reference to the following pictures or drawings. These drawings are provided for illustrative purposes only and only depict example deployments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered as limiting the breadth, scope or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.
[0007] Figure 1 is a diagram illustrating an example cellular communication network according to some deployments.
[0008] Figure 2 Block diagrams of example base stations and example user equipment are shown in accordance with some deployments.
[0009] Figure 3 An example scheme implemented to support initial access is shown.
[0010] Figure 4 It is a table of PRACH configuration indices mapped to random access configurations according to some deployments.
[0011] Figure 5 An example of the structure of Radio Resource Control (RRC) signaling according to some deployments is shown.
[0012] Figure 6 is a table showing the relationship between the number of repetitions and the time-domain window index according to some deployments.
[0013] Figure 7 Resources used for transmission of uplink data (eg, PRACH-related data) according to some deployments are shown.
[0014] Figure 8 Resources used for transmission of uplink data (eg, PRACH-related data) according to some deployments are shown.
[0015] Fig. 9 Resources used for transmission of uplink data (eg, PRACH-related data) according to some deployments are shown.
[0016] Fig.10 Resources used for transmission of uplink data (eg, PRACH-related data) according to some deployments are shown.
[0017] Fig.11 Resources used for transmission of uplink data (eg, PRACH-related data) according to some deployments are shown.
[0018] Fig.12Resources used for transmission of uplink data (eg, PRACH-related data) according to some deployments are shown.
[0019] Fig.13 Resources used for transmission of uplink data (eg, PRACH-related data) according to some deployments are shown.
[0020] Fig.14 Resources used for transmission of uplink data (eg, PRACH-related data) according to some deployments are shown.
[0021] Fig.15 , Fig.16 and Fig.17 A table is shown associating RO resources with SSBs using RO window combinations according to some deployments.
[0022] Fig.18 Resources used for transmission of uplink data (eg, PRACH-related data) according to some deployments are shown.
[0023] Fig.19 Resources used for transmission of uplink data (eg, PRACH-related data) according to some deployments are shown.
[0024] Fig. 20 Resources used for transmission of uplink data (eg, PRACH-related data) according to some deployments are shown.
[0025] Fig.21 Resources used for transmission of uplink data (eg, PRACH-related data) according to some deployments are shown.
[0026] Fig. 22 Resources used for transmission of uplink data (eg, PRACH-related data) according to some deployments are shown.
[0027] Fig.23 Resources used for transmission of uplink data (eg, PRACH-related data) according to some deployments are shown.
[0028] Fig.24 is a flow chart illustrating an example method for transmitting at least one PRACH repetition in accordance with some deployments. DETAILED DESCRIPTION
[0029] Various example deployments of the present solution are described below with reference to the accompanying drawings to enable those of ordinary skill in the art to make and use the present solution. As will be apparent to those of ordinary skill in the art, after reading this disclosure, various changes or modifications may be made to the examples described herein without departing from the scope of the present solution. Therefore, the present solution is not limited to the example deployments and applications described and illustrated herein. In addition, the specific order or hierarchy of steps in the methods disclosed herein are merely example methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes may be redeployed while remaining within the scope of the present solution. Therefore, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or actions in an example order, and unless otherwise expressly stated, the present solution is not limited to the specific order or hierarchy presented.
[0030] Among the physical channels used during the initial access process and the handover process, the physical random access channel (PRACH) for requesting uplink allocation to send uplink data to the base station is a potential coverage bottleneck. The deployment disclosed herein relates to improving the coverage of the PRACH, and more specifically, to repeated transmissions of the PRACH. PRACH resources for different numbers of repetitions may be indicated according to various deployments.
[0031] Figure 1 An example wireless communication system 100 is shown that can be deployed in accordance with the present disclosure. In the following discussion, the wireless communication system 100 can be any wireless network, such as a cellular network or a narrowband network. The system 100 includes a base station (BS) 102 and a UE 104 that can communicate with each other via a communication link 110 (e.g., a wireless communication channel), and a cluster of cells (e.g., at least 126, 130, 132, 134, 136, 138, and 140) covering a geographic area 101. Figure 1 , base station 102 and UE 104 are shown as being located within respective geographic boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating on its allocated bandwidth to provide adequate wireless coverage to its intended users.
[0032] For example, the base station 102 can operate on the allocated channel transmission bandwidth to provide sufficient coverage to the UE 104. The base station 102 and the UE 104 can communicate via a downlink radio frame 118 and an uplink radio frame 124, respectively. Each radio frame 118 / 124 can also be divided into subframes (or time slots) 120 / 127, and the subframes 120 / 127 can include data symbols 122 / 128. In the present disclosure, the base station 102 and the UE 104 are described herein as communication nodes that can generally practice the non-limiting examples of the methods disclosed herein. According to various deployments of the present solution, such communication nodes may be capable of wireless and / or wired communication.
[0033] Figure 2 A block diagram of an example wireless communication system 200 for sending and receiving wireless communication signals according to some deployments is shown. The system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In some deployments, the system 200 may be used in a wireless communication environment (such as, for example, the wireless communication environment described above). Figure 1 1 and 10. In some embodiments, the wireless communication system 100 may be used to communicate (eg, send and receive) data symbols in the wireless communication system 100.
[0034] The system 200 generally includes a base station 202 and a UE 204. The base station 202 includes a base station transceiver module 210 (hereinafter also referred to as: base station transceiver 210, transceiver 210), a base station antenna 212 (hereinafter also referred to as: antenna 212 or downlink antenna 212), a base station processor module 214 (hereinafter also referred to as: processor module 214), a base station memory module 216 (hereinafter also referred to as: memory module 216), and a network communication module 218, each module coupled to and interconnected with each other via a data communication bus 220 as needed. The UE 204 includes a UE transceiver module 230 (hereinafter also referred to as UE transceiver 230, transceiver 230), a UE antenna 232 (hereinafter also referred to as: antenna 232 or uplink antenna 232), a UE memory module 234 (hereinafter also referred to as: memory module 234), and a UE processor module 236 (hereinafter also referred to as: processor module 236), each module coupled to and interconnected with each other via a data communication bus 240 as needed. The base station 202 communicates with the UE 204 via a communication channel 250 , which may be any wireless channel or other medium suitable for data transmission as described herein.
[0035] System 200 may also include Figure 2Any number of modules other than the modules shown in . The various illustrative blocks, modules, circuits, and processing logic described in conjunction with the deployment disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. In order to clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described according to their functions. Whether this functionality is implemented as hardware, firmware, or software may depend on the specific application and the design constraints imposed on the entire system. Personnel familiar with the concepts described herein can implement this functionality in an appropriate manner for each specific application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.
[0036] According to some deployments, the UE transceiver 230 may be referred to herein as an uplink transceiver 230 including a Radio Frequency (RF) transmitter and an RF receiver, each of which includes a circuit coupled to an antenna 232. A duplex switch (not shown) may alternately couple the uplink transmitter or receiver to the uplink antenna in a time duplex manner. Similarly, according to some deployments, the base station transceiver 210 may be referred to herein as a downlink transceiver 210 including an RF transmitter and an RF receiver, each of which includes a circuit coupled to an antenna 212. The downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time division duplex manner. The operation of the two transceiver modules 210 and 230 may be coordinated in time so that the uplink receiver circuit is coupled to the uplink antenna 232 so as to receive transmissions over the wireless transmission link 250 while the downlink transmitter is coupled to the downlink antenna 212. In some deployments, there is tight time synchronization with a minimum guard time between changes in both duplex directions.
[0037] The UE transceiver 230 and the base station transceiver 210 are configured to communicate via a wireless data communication link 250 and cooperate with an appropriately configured RF antenna deployment 212 / 232 that can support a specific wireless communication protocol and modulation scheme. In some illustrative deployments, the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards, such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to application to specific standards and related protocols. Instead, the UE transceiver 230 and the base station transceiver 210 can be configured to support alternative or additional wireless data communication protocols (including future standards or variations thereof).
[0038] According to various deployments, the base station 202 can be, for example, a gNB, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a micro station. In some deployments, the UE 204 can be implemented in various types of user equipment, such as a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, a wearable computing device, etc. The processor modules 214 and 236 can be implemented or implemented using a general-purpose processor, a content addressable memory, a digital signal processor, an application-specific integrated circuit, a field programmable gate array, any suitable programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof designed to perform the functions described herein. In this way, the processor can be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor can also be implemented as a combination of computing devices, for example, a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a digital signal processor core, or any other such configuration combination.
[0039] Further, the steps of the methods or algorithms described in conjunction with the arrangements disclosed herein may be implemented directly in hardware, in firmware, in software modules executed by the processor modules 214 and 236, respectively, or in any practical combination thereof. The memory modules 216 and 234 may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, the memory modules 216 and 234 may be coupled to 210 and 230, respectively, so that the processor modules 210 and 230 can read information from and write information to the memory modules 216 and 234, respectively. The memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some arrangements, the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by the processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.
[0040] The network communication module 218 generally represents the hardware, software, firmware, processing logic and / or other components of the base station 202, which implement bidirectional communication between the base station transceiver 210 and other network components and communication nodes configured to communicate with the base station 202. For example, the network communication module 218 can be configured to support Internet or WiMAX (World Interoperability for Microwave Access) services. In a typical deployment, but without limitation, the network communication module 218 provides an 802.3 Ethernet interface so that the base station transceiver 210 can communicate with a traditional Ethernet-based computer network. In this way, the network communication module 218 can include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms "configured to", "configured to" and various variations thereof used herein with respect to a specified operation or function refer to a device, component, circuit, structure, machine, signal, etc., which is physically constructed, programmed, formatted and / or deployed to perform a specified operation or function.
[0041] In some examples, Figure 3 An example scheme 300 is shown for supporting initial access (eg, PRACH procedure) in a frequency range FR1 (eg, a frequency band below 6 GHz) and a frequency range FR2 (eg, a frequency band above 6 GHz). Figure 3 In the scheme 300, base station communication 301 (e.g., beamforming) of a base station (e.g., base station 102, 202) can be shown on the top bar, and UE communication 302 (e.g., beamforming) of a UE (e.g., UE 104, 204) can be shown on the bottom bar. For example, the transmission of PRACH can be transmitted via Msg1 310. The scheme 300 also includes different PRACH formats, PRACH resource configurations, the relationship between synchronization signal / physical broadcast channel (PBCH) blocks (Synchronization Signal / Physical Broadcasting Channel Block, SSB) and PRACH opportunities, PRACH retransmission mechanisms, and PRACH power control mechanisms.
[0042] Figure 3 The shaded beams in are the beams used to transmit or receive data. Figure 3As shown, the UE transmits a preamble at a PRACH Occasion (RO) according to the configuration of the PRACH transmission and the selected SSB. When transmitting the preamble in the RO, if the transmission-reception correspondence on the UE side can be guaranteed, a fixed mapping between the UE's receiving (receiving, Rx) beam and the UE's transmitting (transmitting, Tx) beam can be used. A unique Tx beam can be determined based on its reception of the SSB. Specifically, the UE may try to use different Rx beams 303 to receive the SSB from the base station (for example, at 305), and determine the best Rx beam 304. In some deployments, the best Rx beam 304 (for example, the best downlink Rx beam) is the beam with the highest RSRP (Reference Signal Receiving Power). According to the best Rx beam 304, the best Tx beam 306 (for example, the best uplink Tx beam) is determined based on the beam correspondence. The RO used to transmit the PRACH will be determined according to the relationship between the SSB and the PRACH opportunity. Based on this relationship, the base station can determine the SSB selected by the UE. The same beam 315 may be used to transmit subsequent downlink transmissions, including Msg2 320 (which may also be referred to as a Random Access Response (RAR)) and Msg4 340. According to a conventional RACH procedure, the RAR (e.g., Msg2 320) is transmitted after the PRACH transmission (e.g., Msg1 310) ends. The RAR window starts at the first symbol of the earliest Control Resource Set (CORESET) for which the UE is configured to receive a Physical Downlink Control Channel (PDCCH) of a Type 1-PDCCH Common Search Space (CSS) set, i.e., the RAR window starts at least a predefined number of time units (e.g., symbols) after the last symbol of the PRACH opportunity corresponding to the PRACH transmission.
[0043] On the other hand, if the Tx-Rx correspondence on the UE side cannot be guaranteed, the UE needs to try different Tx beams 307 to transmit PRACH (e.g., Msg1 310). This is likely to happen when the UE is using the millimeter (mm) band. According to the current initial access process, after the previous RACH transmission fails, the UE can only determine the appropriate transmission beam by trying RACH retransmissions using various Tx beams 307, which is inefficient.
[0044] Therefore, allowing multiple PRACH transmissions before the RAR window starts or ends can effectively improve coverage and efficiency. More specifically, multiple PRACH transmissions with the same beam (also referred to as PRACH repetitions) can be combined and received at the base station, which is useful for improving reception performance. PRACH repetitions using different beams can be used to identify the best UE Tx beam, and further use the best UE Tx beam for subsequent uplink transmissions (e.g., Msg3 330). This improves the performance of the access process. Some deployments disclosed herein involve distinguishing RACH resources for RACH transmissions with different numbers of repetitions.
[0045] In some deployments, the base station configures the time domain resources for RACH transmission for the UE, for example, via RRC signaling or PDCCH (such as a parameter PRACH configuration index (or prach-ConfigurationIndex). The PRACH configuration index is an index mapped to a row in the random access configuration table, Figure 4 400. In some examples, the entire table of random access configurations may have 256 rows, where the value of the PRACH configuration index is in the range of 0 to 255, indicating 256 different random access configurations. The random access configuration includes, for example, the preamble format, n i mod x=y, subframe number, starting symbol, number of PRACH slots in the subframe, and The UE transmits RACH transmissions using the time domain resources defined by the random access configuration. Table 400 indicates the preamble format to be used for each PRACH configuration index. In some examples, for each PRACH configuration index, for n i mod x=y, x and y are provided. In some examples, n i represents the system frame number (SFN) where the RACH transmission (e.g., preamble) resource is located, x represents the period, and y represents the offset. i is a set of SFNs that satisfy period x and offset y. In addition, for each PRACH configuration index, the time domain resource used to transmit the preamble is determined by parameters (such as SFN, subframe number, starting symbol, number of PRACH slots in a subframe, and In some examples, is the number of time domain PRACH opportunities within a PRACH slot. In some examples, is the PRACH duration.
[0046] In some examples, the base station configures frequency domain resources for RACH transmission for the UE via RRC signaling. Figure 5 An example of the structure of RRC signaling 500 is shown in . The RRC signaling parameter msg1-FrequencyStart (msg1-frequency start) provides the frequency starting resource block (Resource Block, RB) within the carrier, which is defined by an integer from 0 to a maximum number. In addition, the RRC signaling parameter msg1-FDM also provides the number of RACH transmission resources for frequency domain multiplexing (FDMed). In some deployments, the base station configures time-frequency resources, which include time domain resources and frequency domain resources. Time-frequency resources are shown in some figures of this document, where the vertical dimension corresponds to frequency and the horizontal dimension corresponds to time.
[0047] In some deployments, different time domain windows for PRACH transmissions with different numbers of repetitions are defined. The UE may determine different time domain windows for the repetitions of the PRACH transmissions.
[0048] In some deployments, time domain windows for different PRACH transmissions with different numbers of repetitions do not overlap each other in the time domain. In some deployments, different time domain windows are consecutive to each other according to an order or sequence in the time domain. In some examples, the order is predefined. In some deployments, the time domain windows are sorted in ascending order of the number of repetitions, and the time domain windows with fewer numbers of repetitions are sequentially located before the time domain windows with more numbers of repetitions.
[0049] Thus, in some examples, the multiple time domain windows are arranged in order, or the multiple time domain windows are cyclic. The order in which the multiple time domain windows are arranged includes an ascending order of the number of repetitions of each PRACH transmission in the multiple PRACH transmissions. In some examples, the multiple time domain windows are continuous with each other.
[0050] For example, a number M (eg, 4) of different repetition numbers N (including N=1, 2, 4, 8) are supported in one cell. The time domain windows used for PRACH transmission with different repetition numbers N are cyclically arranged. Figure 6600 is a table showing the relationship between the number of repetitions and the time domain window index according to some deployments. The time domain window index identifies the corresponding time domain window corresponding to different numbers of repetitions. In some examples, the time domain window index can be deployed in an order corresponding to the number of repetitions (e.g., N=1, 2, 4, 8). For example, time domain window index 1 corresponds to N=1, time domain window index 2 corresponds to N=2, time domain window index 3 corresponds to N=4, time domain window index 4 corresponds to N=8, time domain window index 5 corresponds to N=1, and so on. Parameter A is a non-negative integer, for example, A=0, 1, 2, 3, 4, ..., etc. M (e.g., 4) is the number of different numbers of repetitions. The first time domain window has a time domain window index of 1 and is used for PRACH transmission with a repetition number of N=1, which means that the PRACH transmission is non-repetitive. The second time domain window has a time domain window index of 6 and is used for PRACH transmission with a repetition number of N=2. The third time domain window has a time domain window index of 11 and is used for PRACH transmission with a repetition number of N=4. The fourth time domain window has a time domain window index of 16 and is used for PRACH transmission with a repetition number N = 8. The first, second, third and fourth time domain windows are directly connected to each other in this order. Due to the cyclic nature, the fifth time domain window is used for PRACH transmission with N = 1, and so on.
[0051] The time domain window used for PRACH transmission may be referred to as an RO window, an RO bundle, or an RO group. In some deployments, an RO window group or a time domain window group may be defined as a time domain resource containing two or more RO windows. In some examples, an RO window group contains one RO window for each repetition number. Figure 7 As shown, it shows that according to the resources 700 that some deployed UEs can use to transmit uplink data (eg, PRACH related data), there are two RO window groups 710 and 720. The horizontal dimension corresponds to time, and the vertical dimension corresponds to frequency. Figure 7Each block in is a resource in resource 700, which corresponds to a frame, a subframe, a time slot, a RACH opportunity or a millisecond along the horizontal dimension. Each RO window includes one or more (e.g., two) time domain resources for preamble transmission. The first RO window group 710 includes RO windows 701, 702, 703 and 704. The second RO window group 720 includes RO windows 705, 706, 707 and 708. In some deployments, the base station can configure the group period (e.g., group period 715) of the RO window group for the UE. The RO window group occurs periodically (e.g., per each group period 715). Then, adjacent RO window groups can be non-continuous (e.g., there is a gap of at least one time domain resource between two adjacent RO window groups), and the group period can be continuous. In other words, in some examples, a plurality of time domain windows include at least one time domain window group, the at least one time domain window group occurs periodically, and adjacent time domain window groups are non-continuous. In other examples, the plurality of time-domain windows include at least two sets of time-domain window groups, the time-domain window groups in the same set appear periodically, and different sets of time-domain window groups are configured with different periods.
[0052] Figure 8 Resources 800 that a UE may use to transmit uplink data (eg, PRACH-related data) according to some deployments are shown. The horizontal dimension corresponds to time, and the vertical dimension corresponds to frequency. Figure 8 Each block in is one of the resources 800, which corresponds to a frame, a subframe, a time slot, a RACH opportunity, or a millisecond along the horizontal dimension. Each RO window includes one or more (e.g., two) time domain resources. Figure 8 As shown, RO windows 801 to RO windows 816 are associated with different repetition quantities in the described cyclic manner. For example, different RO windows are continuously connected without gaps therebetween. As shown, the end point of an RO window is the starting point of the next RO window. In some deployments, different RO windows may also be discontinuous.
[0053] In some deployments, the lengths of the RO windows corresponding to different numbers of repetitions are the same. In other deployments, the lengths of the RO windows corresponding to different numbers of repetitions are different. That is, in some examples, the UE determines the length for each time domain window in the multiple time domain windows. The lengths of two or more time domain windows in the multiple time domain windows are the same or different. For example, the base station can (via RRC signaling) configure a reference length (L) of the RO window for the UE from a value set (e.g., 5ms, 10ms, 20ms, 40ms, 80ms, 160ms, etc.). R). In addition, the base station can configure at least one scaling factor (α) for the UE from a value set (e.g., 1 / 4, 1 / 2, 1, 2, 4, etc.) via RRC signaling. This parameter is used to flexibly control the length ratio of RO windows with different numbers of repetitions. The UE determines the length of each time domain window in the multiple time domain windows by receiving one or more reference lengths and at least one scaling factor from the base station, and determines the length of each time domain window in the multiple time domain windows based on the reference length, at least one scaling factor, and one or more of the different numbers of repetitions.
[0054] For example, the actual length of the RO window (L A ) The UE can use the repetition number (N), the scaling factor (α) and the reference length of the RO window (L R ) is determined. In some examples, the following expression can be used:
[0055]
[0056] In some examples where there is no scaling factor or α=1, the actual length of the RO window (L A ) is equal to or equal to L R .
[0057] In some examples where the scaling factor α is greater than 1, the larger the number of repetitions, the longer the actual length of the corresponding RO window. A =L R ; For N = 2, L A =2L R ; For N = 4, L A =4L R ; For N = 8, L A =8L R This mechanism helps to maintain the same RACH resource capacity with different repetition numbers.
[0058] In some examples where the scaling factor α is less than 1, the larger the number of repetitions, the shorter the actual length of the RO window. A =L R ; For N=2, L A =L R / 2; for N=4, L A =L R / 4; for N=8, L A =L R / 8. This mechanism improves the efficiency of RACH resource utilization.
[0059] In some examples, two repetition numbers are supported in one cell, N=1 and N=2. The reference length of the RO window is L R = 20 ms or 2 radio frames. The scaling factor is determined to be α = 2. Then, the actual length of the RO window is determined using expression (1). For N = 1, L A =L R =20ms; for N=2, L A =2L R =40ms. Fig. 9 Resources 900 that a UE may use to transmit uplink data (eg, PRACH-related data) according to some deployments are shown. The horizontal dimension corresponds to time, and the vertical dimension corresponds to frequency. Fig. 9 Each block in is a resource in resources 900, which corresponds to a frame, a subframe, a time slot, a RACH opportunity, or a millisecond (ms), etc. along the horizontal dimension. Fig. 9 In the example shown, each time domain resource has a length of 10 ms. Each RO window 910 includes 2 time domain resources. Each RO window 920 includes 4 time domain resources. Fig. 9 As shown, RO window 910 and RO window 920 are associated with different repetition numbers in the cyclic manner. According to expression (1) as described above, RO windows 910 and 920 are determined using scaling factors. For RO window 910, N=1, the length of RO window 910 is determined to be 20ms or 2 time domain resources (e.g., L A =L R =20ms). For RO window 920, N=2, the length of RO window 920 is determined to be 40ms or 4 time domain resources (eg, L A =2L R =40ms).
[0060] In some deployments, different RO windows may be non-continuous. In some deployments, some RO windows are continuous, and some other RO windows are non-continuous. For example, RO windows 910 and 920 are continuous, but RO window 920 and next RO window 910 are non-continuous.
[0061] In some deployments, the same RACH configuration including at least one of the following is used for different RO windows of PRACH transmission with the same number of repetitions: prach-ConfigurationIndex, msg1-FDM, msg1-FrequencyStart, ra-ResponseWindow (e.g., the time domain window for monitoring PDCCH for random access responses), totalNumberOfRA-Preambles (e.g., the total number of preambles used for contention-based and contention-free random access), and ssb-perRACH-OccasionAndCB-PreamblesPerSSB (e.g., the number of SSBs for each RACH occasion and the number of contention-based preambles for each SSB, etc.).
[0062] In some deployments, different RACH configurations including two or more of the following are used for different RO windows with different numbers of repetitions of PRACH transmissions: prach-ConfigurationIndex, msg1-FDM, msg1-FrequencyStart, ra-ResponseWindow, totalNumberOfRA-Preambles, and ssb-perRACH-OccasionAndCB-PreamblesPerSSB, etc.
[0063] In some examples, each time domain window in the plurality of time domain windows corresponds to one PRACH transmission in the plurality of PRACH transmissions. Each PRACH transmission in the plurality of PRACH transmissions has a different number of repetitions. Therefore, time domain windows for PRACH transmissions with different numbers of repetitions can be effectively defined and implemented. The network can effectively distinguish RACH transmissions with different numbers of repetitions to avoid confusion and improve PRACH reception performance.
[0064] In some deployments, different time domain windows for PRACH transmissions with different numbers of repetitions are defined. The UE may determine different time domain windows for repetitions of PRACH transmissions based on an offset relative to a reference PRACH transmission resource or a reference time domain resource.
[0065] In some deployments, the PRACH configuration (e.g., Figure 4The PRACH configuration index (prach-ConfigurationIndex) shown can be shared by PRACH transmissions with different repetition numbers. The PRACH transmission resource with repetition number = 1 (or non-repetitive PRACH transmission) can be determined according to the second row of Table 400. The PRACH transmission resource with repetition number = 1 is a reference time domain resource. The resources of PRACH transmissions with other repetition numbers can be determined by adding an offset relative to the reference time domain resource determined using the table. In some examples, the UE determines multiple time domain windows by determining a reference time domain window (e.g., corresponding to non-repetition) and determining at least one time domain window (e.g., corresponding to at least one repetition or two transmissions) based on the reference time domain window and the offset.
[0066] Fig.10 Resources 1000 that a UE may use to transmit uplink data (eg, PRACH-related data) according to some deployments are shown. The horizontal dimension corresponds to time, and the vertical dimension corresponds to frequency. Fig.10 Each block in is one of the resources 1000 that corresponds to a frame along the horizontal dimension. Fig.10 In the example shown, a PRACH configuration (e.g., with prach-ConfigurationIndex=0) is configured for PRACH transmissions with different numbers of repetitions. The offset can be determined based on an offset step size at a radio frame level represented as O (e.g., O=1 frame) configured by the base station for the UE. The offset of the RO window for PRACH transmissions with a repetition number greater than 1 can be determined based on the offset step size O. For example, expression (2) can be used to determine the offset based on the index i of the RO window:
[0067] Offset=O*(i-1)(2),
[0068] Wherein, i represents the index of the RO window, i.e., the i-th RO window. Therefore, in some examples, the reference time domain window corresponds to a non-repeated PRACH or the number of repetitions is equal to 1. Each time domain window of the at least one time domain window corresponds to at least one PRACH repetition. The offset is determined based on the step size and the number of repetitions of the at least one repetition.
[0069] Different numbers of repetitions can share the same RACH configuration, and the offset is used to allocate time domain resources for PRACH transmissions of different numbers of repetitions over time. Different numbers of repetitions have different time domain resources or different RO windows. Therefore, the offset step size combined with the number of repetitions can be used to define the offset of the RO window corresponding to a given number of repetitions.
[0070] According to the PRACH configuration, at least one radio frame satisfies the following:
[0071] SFN mod 16 = 1 (3),
[0072] Including SFN=1, 17, 33, ..., etc., the at least one radio frame is determined as a radio frame for PRACH transmission with a repetition number=1 (e.g., no repetition). In the example shown in expression (3), 16 refers to the number of frames in one cycle. Such at least one radio frame can be considered as a first RO window. The second RO window (e.g., i=2) can be determined as a radio frame that satisfies the following conditions:
[0073] SFN mod 16 = 1+O*(i-1) = 2 (4),
[0074] These include SFN=2, 18, 34, ..., etc. The third RO window (eg, i=3) may be determined as a radio frame that satisfies the following conditions:
[0075] SFN mod 16 = 1+O*(i-1) = 3 (5),
[0076] These include SFN=3, 19, 35, ..., etc. The fourth RO window (eg, i=4) may be determined as a radio frame that satisfies the following conditions:
[0077] SFN mod 16 = 1+O*(i-1) = 4 (6),
[0078] These include SFN=4, 20, 36, ... etc. The RO windows are mapped to PRACH transmissions with different repetition numbers according to a sequence (such as ascending order). For example, the second RO window is used for PRACH transmission with repetition number=2, the third RO window is used for PRACH transmission with repetition number=4, and the fourth RO window is used for PRACH transmission with repetition number=8.
[0079] exist Fig.10 , the RO window 1010 with SFN 1 is the first RO window and spans one frame in length. In the case of a step size of 1 frame, the RO window 1020 with SFN 2 is the second RO window and spans one frame in length, with a repetition number N=2. The RO window 1030 with SFN 3 is the third RO window, spans one frame in length and has a repetition number N=4. The RO window 1040 with SFN 4 is the fourth RO window, spans one frame in length and has a repetition number N=8.
[0080] In some deployments, the lengths of the RO windows for PRACH transmissions with different numbers of repetitions may be different. In some examples, the offset relative to the first RO window is determined based on the length of the RO window. Thus, different RO windows do not overlap with each other. For example, the i-th RO window may be determined based on the starting SFN of the first RO window and the total length of the first (i-1) RO windows. th The starting SFN of the RO window. For example, in, is the i th The starting SFN of the RO window, and L n It is nth th The length of the RO window. Alternatively, the (i-1)th th The starting SFN of the RO window and the (i-1)th th The length of the RO window determines the i-th th The starting SFN of the RO window. For example, in, is the i th The starting SFN of the RO window, is the (i-1)th th The starting SFN of the RO window, and L i-1 is the (i-1)th th The length of the RO window.
[0081] In some deployments, the base station configures different PRACH configurations for PRACH transmissions with different numbers of repetitions for the UE. For example, PRACH configuration index #0 is configured for PRACH transmission with number of repetitions = 1. PRACH configuration index #4 is configured for PRACH transmission with number of repetitions = 2. In some examples, the UE detects a collision or conflict between RO windows for different PRACH transmissions with different numbers of repetitions (for example, two RO windows for different PRACH transmissions with different numbers of repetitions overlap in time). This may be the result of PRACH resources for different PRACH transmissions with different numbers of repetitions being independently configured. That is, the UE may determine the same resource based on different configurations of PRACH transmissions with different numbers of repetitions. In some examples, the UE uses an offset to modify the time domain resources (for example, for a PRACH transmission with a larger number of repetitions). In some examples, the UE determines that at least two of the multiple time domain windows overlap in time, and modifies one or more of the at least two time domain windows in the multiple time domain windows based on at least one offset.
[0082] In some examples, the UE determines that at least two PRACH resources within each time domain window overlap in both the time domain and the frequency domain, and the UE modifies one or more of the at least two PRACH resources based on at least one offset. The at least one offset can be a time domain offset or a frequency domain offset.
[0083] Fig.11 Resources 1100 that a UE may use to transmit uplink data (eg, PRACH-related data) according to some deployments are shown. The horizontal dimension corresponds to time, and the vertical dimension corresponds to frequency. Fig.11 Each block in is one of the resources 1100 that corresponds to a frame along the horizontal dimension. Fig.11 In the example shown, the UE may detect that a collision occurs in a radio frame that satisfies the following equation:
[0084] SFN mod 16=1(7).
[0085] This frame 1110 can be used by the UE as an RO window for PRACH transmission with a repetition number N=1 (no repetition). The radio frame 1120 for PRACH transmission with a repetition number N=2 can be determined by the UE by adding an offset (e.g., 1 frame). Then, the radio frame satisfies the following equation:
[0086] SFN mod 16 = 2 (8),
[0087] This radio frame may be used for PRACH transmission with repetition number = 2. With respect to radio frames that do not conflict (e.g., overlap) with PRACH transmissions with different repetition numbers, the original configuration received by the UE from the base station may be followed. For example, radio frame 1130 SFN = 9 is determined according to the configuration of PRACH transmission with repetition number = 2 (e.g., SFN mod 8 = 1), and since this radio frame does not conflict with other PRACH transmissions, the offset is not used to modify the radio frame.
[0088] In some deployments, different PRACH configuration tables may be defined for PRACH transmissions with different numbers of repetitions. The PRACH transmission resources (e.g., RO window) may be determined according to the corresponding tables. In some deployments, if there is a conflict between PRACH transmissions with different numbers of repetitions, the UE may apply an offset to at least one of the PRACH transmissions to modify the PRACH transmission resources.
[0089] In some deployments, a subframe level offset may be defined instead of or in addition to a frame level offset and used to modify the PRACH transmission resources of at least one of the PRACH transmissions. Fig.121200 and subframes (or time slots) 1205 that a UE may use to transmit uplink data (e.g., PRACH-related data) according to some deployments are shown. The horizontal dimension corresponds to time (e.g., frame and subframe), and the vertical dimension corresponds to frequency. For example, frame 1201 includes subframes (or time slots) 1210 to 1250. Fig.12 In the example shown, according to the configuration received by the UE from the base station, subframe (or time slot) 1250 (e.g., subframe (or time slot) index 4 and 9) is a subframe (or time slot) for PRACH transmission with a repetition number N = 1. For PRACH transmissions with other repetition numbers, the UE can use a subframe-level offset to determine the transmission resource, for example, subframe (or time slot) 1240 (e.g., subframe (or time slot) index 3 and 8) is used for PRACH transmission with a repetition number N = 2. Subframe (or time slot) 1230 (e.g., subframe (or time slot) index 2 and 7) is used for PRACH transmission with a repetition number N = 4. Subframe 1220 (e.g., subframe (or time slot) index 1 and 6) is used for PRACH transmission with a repetition number N = 8.
[0090] In some deployments, the same RACH configuration including at least one of the following is used for different RO windows of PRACH transmissions with the same number of repetitions: prach-ConfigurationIndex, msg1-FDM, msg1-FrequencyStart, ra-ResponseWindow, totalNumberOfRA-Preambles, and ssb-perRACH-OccasionAndCB-PreamblesPerSSB, etc.
[0091] In some deployments, different RACH configurations including two or more of the following are used for different RO windows with different numbers of repetitions of PRACH transmissions: prach-ConfigurationIndex, msg1-FDM, msg1-FrequencyStart, ra-ResponseWindow, totalNumberOfRA-Preambles, and ssb-perRACH-OccasionAndCB-PreamblesPerSSB, etc.
[0092] In some examples, each time domain window in the plurality of time domain windows corresponds to a PRACH transmission in the plurality of PRACH transmissions. Each PRACH transmission in the plurality of PRACH transmissions has a different number of repetitions. Therefore, time domain windows for PRACH transmissions with different numbers of repetitions can be effectively defined and implemented. The network can effectively distinguish RACH transmissions with different numbers of repetitions to avoid confusion and improve PRACH reception performance.
[0093] In some deployments, an association between ROs and SSBs within or across different RO windows may be defined. In some examples where one or more ROs are within a RO window according to the PRACH configuration, the ROs are sorted and then mapped to one or more SSBs. The UE transmits the PRACH in the RO mapped to the selected SSB. During this process, the RO sorting rule on which the ROs are sorted is considered in conjunction with the properties of the RO window. As discussed in further detail herein, sorting may be performed in multiple RO windows within a time period, in each RO window, or in multiple RO windows to ensure a certain number of repeated PRACH transmissions. In other words, in some examples, the UE sorts multiple time domain resources in a time domain window and maps the multiple time domain resources to at least one SSB based on the sorting.
[0094] In some deployments, the UE performs cyclic association or cyclic mapping in multiple RO windows within a specific time period (e.g., 160ms). In other words, in each example, the UE maps multiple time domain resources in two or more time domain windows of the multiple time domain windows within a time period to at least one SSB. Multiple RO windows are configured for PRACH transmissions with the same number of repetitions. Fig.13 Frame 1300 and subframe (or time slot) 1305 that a UE according to some deployments can use to transmit uplink data (e.g., PRACH related data) are shown. The horizontal dimension corresponds to time (e.g., frame and subframe), and the vertical dimension corresponds to frequency. For example, frame 1301 includes subframe (or time slot) 1306, and frame 1303 includes subframe (or time slot) 1307.
[0095] like Fig.13As shown, a time period 1304 is defined as a plurality of frames (e.g., 16 frames (SFN 0, SFN 1, SFN 2, ..., SFN 15, respectively) or 160 milliseconds). Within the time period 1304, there are two RO windows (e.g., frame 1301 with SFN 0 and frame 1303 with SFN 8) configured for PRACH transmission with a repetition number = 1. Other RO windows not shown may exist in the time period 1304. In each RO window, there are two time domain resources (e.g., 2 ROs) for transmitting PRACH. For example, in the RO window 1301, there are two ROs 1310 (in subframe 4) and 1320 (in subframe 9). In the RO window 1303, there are two ROs 1330 (in subframe 4) and 1340 (in subframe 9). Therefore, there are a total of 4 ROs within the time period 1304.
[0096] Three SSBs (e.g., SSB#0, SSB#1, and SSB#3) are transmitted in the cell. In this example, one SSB is associated with one RO in a one-to-one mapping. Other mapping methods (such as many-to-one or one-to-many mapping) can be implemented similarly. The first RO 1310 (earliest in time) as subframe #4 in SFN 0 (e.g., frame 1301) within time period 1304 is mapped to SSB#0. The second RO 1320 (second earliest in time) as subframe #9 in SFN 0 (e.g., frame 1301) within time period 1304 is mapped to SSB#1. The third RO 1330 (third earliest in time) as subframe #4 in SFN 8 (e.g., frame 1303) within time period 1304 is mapped to SSB#3. Because all available SSBs have been mapped once, in some examples, the (temporally last) remaining RO 1340, which is subframe #9 in SFN 8 (e.g., frame 1303) in period 1304, cannot complete a full round of SSB-RO association. Therefore, RO 1340 is not associated with any SSB.
[0097] In some deployments, the UE performs cyclic association or cyclic mapping in each RO window. In other words, in some examples, the UE maps multiple time domain resources in each time domain window of multiple time domain windows to at least one SSB. Fig.14 Frame 1400 and subframe (or time slot) 1405 that a UE according to some deployments can use to transmit uplink data (e.g., PRACH related data) are shown. The horizontal dimension corresponds to time (e.g., frame and subframe), and the vertical dimension corresponds to frequency. For example, as shown, each of frames 1401, 1402, 1403, and 1404 includes 10 subframes (or time slots).
[0098] like Fig.14As shown, each RO window 1410, 1412 and 1414 includes two frames. For example, RO window 1410 includes RO frame 1401 (SFN=0) and RO frame 1402 (SFN=1). RO window 1412 includes RO frame 1403 (SFN=8) and RO frame 1404 (SFN=9). There are 4 time domain resources (e.g., 4 ROs) for transmitting PRACH in each RO window. For example, in RO window 1410, there are 4 ROs 1420, 1430, 1440 and 1450. RO 1420 and RO 1430 are in frame 1401, and RO 1440 and RO 1450 are in frame 1402.
[0099] Three SSBs are transmitted in the cell, for example, SSB#0, SSB#1, and SSB#3. In this example, one SSB is associated with one RO in a one-to-one mapping. Other mapping methods, such as many-to-one mapping or one-to-many mapping, can be implemented similarly. The first RO 1420 (earliest in time) as subframe #4 in SFN 0 (e.g., frame 1401) within the RO window 1410 is mapped to SSB#0. The second RO 1430 (second earliest in time) as subframe #9 in SFN 0 (frame 1401) within the RO window 1410 is mapped to SSB#1. The third RO 1440 (third earliest in time) as subframe #4 in SFN 8 (e.g., frame 1402) within the RO window 1410 is mapped to SSB#3. Because all available SSBs have been mapped, in some examples, the remaining RO 1450 (last in time) in RO window 1410, which is subframe #9 in SFN 8 (e.g., frame 1402), cannot complete a full round of SSB-RO association. Therefore, RO 1450 is not associated with any SSB. The same association pattern can be repeated for other RO windows 1412 and RO windows 1414 with the same number of repetitions for PRACH transmissions.
[0100] In some deployments, the UE performs cyclic association or cyclic mapping in multiple RO windows to ensure a certain number of repetitions of PRACH transmission. In some examples, the UE determines two or more time domain windows in the multiple time domain windows based on the number of at least one repetition, and maps multiple time domain resources in the two or more time domain windows in the multiple time domain windows to at least one SSB. Multiple RO windows are configured for PRACH transmission with the same number of repetitions. Again, refer to Fig.14, each RO window 1410, 1412 and 1414 includes two consecutive frames. For example, RO window 1410 includes RO frame 1401 (SFN=0) and RO frame 1402 (SFN=1). RO window 1412 includes RO frame 1403 (SFN=8) and RO frame 1404 (SFN=9). There are 4 time domain resources (e.g., 4 ROs) for transmitting PRACH in each RO window. For example, in RO window 1410, there are 4 ROs 1420, 1430, 1440 and 1450. RO 1420 and RO 1430 are in frame 1401, and RO 1440 and RO 1450 are in frame 1402. RO window 1412 may include 4 ROs in the same time domain position.
[0101] Three SSBs are transmitted in the cell, for example, SSB#0, SSB#1, and SSB#3. In this example, one SSB is associated with one RO in a one-to-one mapping. Other mapping methods, such as many-to-one mapping or one-to-many mapping, can be implemented similarly. In order to ensure PRACH transmission with a repetition number N=2, at least 6 ROs are required, so that 2 ROs become associated with each SSB. Therefore, the UE combines RO window 1410 and RO window 1412 into an RO window combination. The RO window combination includes a total of 8 ROs, which allows 6 ROs to be repeatedly mapped to or associated with an SSB, and 2 ROs are not mapped.
[0102] An example of using RO window combination to associate RO with SSB is as follows Fig.15 , Fig.16 and Fig.17 As shown. Fig.15 In the table shown, SSB#0 is mapped to RO in subframe 4 (1420) of SFN=0 (frame 1401) and RO in subframe 9 (1450) of SFN=1 (frame 1402). SSB#1 is mapped to RO in subframe 9 (1430) of SFN=0 (frame 1401) and RO in subframe 4 of SFN=8 (frame 1403). SSB#3 is mapped to RO in subframe 4 (1440) of SFN=1 (frame 1402) and RO in subframe 9 of SFN=8 (frame 1403).
[0103] exist Fig.16In the table shown, SSB#0 is mapped to RO in subframe 4 (1420) of SFN=0 (frame 1401) and RO in subframe 9 (1430) of SFN=0 (frame 1401). SSB#1 is mapped to RO in subframe 4 (1440) of SFN=1 (frame 1402) and RO in subframe 9 of SFN=1 (frame 1402). SSB#3 is mapped to RO in subframe 4 of SFN=8 (frame 1403) and RO in subframe 9 of SFN=8 (frame 1403).
[0104] exist Fig.17 In the table shown, SSB#0 is mapped to RO in subframe 4 (1420) of SFN=0 (frame 1401) and RO in subframe 4 of SFN=8 (frame 1403). SSB#1 is mapped to RO in subframe 9 (1430) of SFN=0 (frame 1401) and RO in subframe 9 of SFN=8 (frame 1403). SSB#3 is mapped to RO in subframe 4 (1440) of SFN=1 (frame 1402) and RO in subframe 4 of SFN=9 (frame 1404).
[0105] Figures 15 to 17 The remaining ROs within the RO window combination in are reserved and are not associated with any SSB. Therefore, the time domain windows for PRACH transmissions with different repetition numbers can be effectively defined and implemented. The network can effectively distinguish RACH transmissions with different repetition numbers to avoid confusion and improve PRACH reception performance.
[0106] Fig.18 A radio frame 1800 and subframes (or time slots) 1806 and subframes (or time slots) 1807 are shown, which can be used by a UE to transmit uplink data (e.g., PRACH related data) according to some deployments. The horizontal dimension corresponds to time (e.g., radio frame and subframe), and the vertical dimension corresponds to frequency. For example, radio frame 1801 includes subframe (or time slot) 1806, and frame 1802 includes subframe (or time slot) 1807. In some deployments, the time domain resources (e.g., RO) of PRACH repetitions occupy consecutive radio frames, and the first M time domain resources (e.g., RO 1820) are obtained through signaling configuration. When M is less than the number of repetitions N, the latter (NM) time domain resources (such as additional ROs of RO 1830) occupy radio frames adjacent to the radio frames of the first M time domain resources. Fig.18In the embodiment, for PRACH transmission with repetition number N=2, RO1820 in subframe 1812 of the first radio frame 1801 is obtained through signaling configuration, and the additional RO 1830 is determined according to the above rule, that is, located in the second radio frame 1802 and in subframe 1814. RO 1820 and RO 1830 occupy the same time domain position in each radio frame, for example, occupy the same subframe (for example, subframe 1812 and subframe 1814 have the same subframe index) and the same symbol (for example, RO1820 and RO 1830 have the same starting symbol index and the same number of symbols).
[0107] Fig.19 A radio frame 1900 and a subframe (or time slot) 1906 are shown that can be used by a UE to transmit uplink data (e.g., PRACH related data) according to some deployments. The horizontal dimension corresponds to time (e.g., radio frame and subframe), and the vertical dimension corresponds to frequency. For example, a radio frame 1901 includes a subframe (or time slot) 1906. In some deployments, the time domain resources (e.g., RO) repeated by the PRACH occupy consecutive subframes (or time slots), and the first M time domain resources (e.g., RO 1920) are obtained through signaling configuration. When M is less than the number of repetitions N, the latter (NM) time domain resources (such as additional ROs of RO 1930) occupy subframes (or time slots) adjacent to the subframes (or time slots) of the first M time domain resources. In Fig.19 In the embodiment, for PRACH transmission with repetition number N=2, RO 1920 in the fifth subframe 1912 (or time slot) of the first radio frame 1901 is obtained through signaling configuration, and additional RO 1930 is determined according to the above rules, for example, located in the sixth subframe 1913 (or time slot) of the first radio frame 1901. RO 1920 and RO 1930 occupy the same time domain position in each subframe (or time slot), that is, occupy the same symbol (for example, RO 1820 and RO 1830 have the same starting symbol index and the same number of symbols).
[0108] Some deployments involve defining different frequency domain resources for PRACH transmissions with different numbers of repetitions. The base station can configure the frequency resources for PRACH transmission for the UE via RRC signaling (e.g., msg1-FDM and msg1-FrequencyStart). In some examples, msg1-FDM indicates the number of FDMed PRACH transmission resources, and msg1-FrequencyStart indicates the frequency starting point (e.g., frequency starting RB index) of the first PRACH transmission resource (e.g., the lowest resource). In some examples, 4 PRACH repetition numbers are supported within the cell (e.g., N=1, 2, 4, 8).
[0109] In some deployments, the base station configures a frequency resource set for PRACH transmission for each number of PRACH repetitions for the UE. Multiple frequency resource sets (equal to the number of repetitions, e.g., 4) for PRACH transmission are configured. In some deployments, the UE receives a frequency resource set for each number of at least one repetition from the base station.
[0110] In some deployments, the base station configures a reference frequency resource set for PRACH transmission for a PRACH transmission with one number of repetitions (e.g., N=1) for the UE. In addition, the base station configures one or more frequency offsets for the UE for determining frequency resources for PRACH transmission with at least one other number of repetitions (e.g., N=2, 4, and 8). In some examples, the UE receives a reference frequency domain resource set for at least one number of repetitions from the base station, receives one or more offsets corresponding to at least one other number of at least one repetition from the base station, and determines a frequency domain resource set for at least one number of at least one repetition for each number of at least one other number of at least one repetitions based on the reference frequency domain resource set and the one or more offsets.
[0111] In some deployments, the configuration of "msg1-FDM" is shared by all PRACH transmissions with different numbers of repetitions. In some examples, the UE receives a number of frequency-domain multiplexed resources from the base station, and the number of frequency-domain multiplexed resources is the same for any number of at least one repetition. For example, msg1-FDM=2 means that there are 2 frequency-domain resources for each of the PRACH transmissions with repetition numbers = 1, 2, 4, and 8. Therefore, there are a total of 8 FDMed PRACH transmission resources. The configuration of "msg1-FrequencyStart" is valid for PRACH transmissions with repetition number = 1. The frequency starting point of PRACH transmissions with other numbers of repetitions can be implicitly determined by the UE. For example, the end RB of the frequency resource for PRACH transmission with repetition number N=1 is X, and RB(X+B) is the frequency start of PRACH transmission with repetition number N=2. B is a positive integer, for example B=1. Similarly, assuming that RB(Y) is the end RB of the frequency resource of the PRACH transmission with a repetition number N=2, RB(Y+1) is the frequency start of the PRACH transmission with a repetition number N=4, and so on. Therefore, different frequency resources can be obtained. Therefore, in some examples, the UE receives a frequency starting point of a first frequency domain resource among multiple frequency domain resources corresponding to at least one repetition of the first number from the base station, and determines a frequency starting point of a second frequency domain resource among multiple frequency domain resources corresponding to at least one repetition of the second number.
[0112] In some deployments, a time domain resource for a PRACH transmission with a larger number of repetitions may last for more frames than a time domain resource for a PRACH transmission with a smaller number of repetitions. In some examples, the time domain resources include a first time domain resource corresponding to a first number of repetitions and a second time domain resource corresponding to a second number of repetitions. The first time domain resource and the second time domain resource have the same starting point. The first number is greater than the second number. The first time domain resource lasts for a longer period of time than the second time domain resource.
[0113] Fig. 20 Frame 2000 and subframe (or time slot) 2006 and subframe (or time slot) 2007 that can be used to transmit uplink data (e.g., PRACH related data) according to some deployments of UE are shown. The horizontal dimension corresponds to time (e.g., frame and subframe), and the vertical dimension corresponds to frequency. For example, frame 2001 includes subframe (or time slot) 2006, and frame 2002 includes subframe (or time slot) 2007. For PRACH transmission with different numbers of repetitions, RO 2010, 2020, 2030 and 2040 as shown in the figure can be used for transmission. According to the PRACH configuration, a radio frame (e.g., frame 2001) that satisfies SFN mod 8=0 is determined as a radio frame for PRACH transmission. There are two ROs in the time domain of a radio frame. As shown in the figure, in frame 2001, the RO is located in the time domain of subframes (or time slots) 2012 and 2014. PRACH transmission with more than 2 repetitions cannot be implemented only in frame 2001. For PRACH transmission with repetition number N=4, the radio frame for PRACH transmission can be extended from frame 2001 (SFN0) to frame 2001 and frame 2002 (SFN1). For PRACH transmission with repetition number N=8, the radio frame for PRACH transmission can be extended from frame 2001 (SFN0) to frame 2001, frame 2002, frame 2003 and frame 2004 (SFN0 to SFN3). As shown in the figure, the UE transmits PRACH transmission with repetition numbers N=1, 2, 4 and 8 in RO 2040, RO 2030, RO 2020 and RO 2010 in subframes (or time slots) 2012 and 2014, respectively. The UE transmits PRACH transmissions with repetition numbers N=4 and 8 in RO 2010 and 2020 in subframes (or time slots) 2016 and 2018. The UE transmits PRACH transmissions with repetition number N=8 in RO 2010 in subframes (or time slots) of frame 2003 and frame 2004.
[0114] Therefore, time domain windows for PRACH transmissions with different numbers of repetitions can be effectively defined and implemented. The network can effectively distinguish RACH transmissions with different numbers of repetitions to avoid confusion and improve PRACH reception performance.
[0115] In some deployments, the frequency domain resources used for PRACH transmission within a PRACH repetition bundle may be different. The frequency domain resources may also be referred to as PRACH transmission with frequency hopping. For example, for a PRACH transmission with a repetition number N=4, there are four PRACH transmissions within a PRACH repetition bundle.
[0116] In some deployments, the frequency domain resources include at least one configured frequency domain resource and at least one additional frequency domain resource mapped to the at least one configured frequency domain resource. The at least one configured frequency domain resource and the at least one additional frequency domain resource do not overlap in the frequency domain. Fig.21 A subframe (or time slot) 2100 is shown that a UE may use to transmit uplink data (e.g., PRACH related data) according to some deployments. The subframe (or time slot) includes a subframe (or time slot) 2102 and a subframe (or time slot) 2104. The horizontal dimension corresponds to time (e.g., frame, subframe, or time slot), and the vertical dimension corresponds to frequency. ROs 2112, 2114, 2116, and 2118 are in subframe (or time slot) 2102, and ROs 2122, 2124, 2126, and 2128 are in subframe (or time slot) 2104. Fig.21In the example shown, each of the ROs 2112, 2114, 2116, and 2118 configured via signaling is mapped to additional ROs 2122, 2124, 2126, and 2128, respectively. For example, RO 2112 is mapped to 2122, RO 2114 is mapped to 2124, RO 2116 is mapped to 2126, and RO 2118 is mapped to 2128. The additional ROs 2122, 2124, 2126, and 2128 are located on one side of the configured RO from a frequency domain perspective. For example, as shown in the figure, the additional ROs 2122, 2124, 2126, and 2128 are all located on the higher frequency side of the configured ROs 2112, 2114, 2116, and 2118. In some deployments, the additional ROs are all located on the lower frequency side of the configured ROs. Signaling may be used to indicate which side of the bandwidth of the configured RO is currently used by the additional ROs 2122, 2124, 2126, and 2128, i.e., to indicate whether the additional ROs 2122, 2124, 2126, and 2128 are lower or higher in frequency than the configured ROs 2112, 2114, 2116, and 2118. The configured ROs 2112, 2114, 2116, and 2118 and the additional ROs 2122, 2124, 2126, and 2128 are combined to provide transmission resources for PRACH repetition with frequency hopping. Each RO in each configured RO and one RO corresponding thereto in the additional ROs 2122, 2124, 2126, and 2128 may be referred to as an RO combination. For different RO combinations, the frequency domain offsets (e.g., 2132, 2134) between the configured ROs 2112, 2114, 2116, and 2118 and the corresponding additional ROs 2122, 2124, 2126, and 2128 may be the same, i.e., Fig.21 , offset 2132 (between RO 2118 and RO 2128) is equal to offset 2134 (between RO 2116 and RO 2126). In some examples, the offset is indicated via signaling (e.g., RRC signaling, MAC layer signaling, or physical layer signaling, etc.). In some examples, an additional frequency domain starting RB of the first additional RO may be configured (e.g., Fig.21 In some examples, the starting RB of the first additional RO can be determined according to the configuration of the configured RO, for example, the starting RB of the first additional RO is the last RB of the last configured RO plus a margin (e.g., 1), or the last RB of the last additional RO is the first RB of the first configured RO minus a margin (e.g., 1). The additional ROs are connected to each other in the frequency domain.
[0117] Fig. 22A subframe (or time slot) 2200 is shown that a UE may use to transmit uplink data (e.g., PRACH related data) according to some deployments. The subframe (or time slot) includes a subframe (or time slot) 2202 and a subframe (or time slot) 2204. The horizontal dimension corresponds to time (e.g., frame, subframe, or time slot), and the vertical dimension corresponds to frequency. ROs 2212, 2214, 2216, and 2218 are in subframe (or time slot) 2202, and ROs 2222, 2224, 2226, and 2228 are in subframe (or time slot) 2204. Fig. 22 As shown, each of the ROs 2212, 2214, 2216, and 2218 configured via signaling is mapped to one of the additional ROs 2222, 2224, 2226, and 2228. For example, RO 2212 is mapped to 2222, RO 2214 is mapped to 2224, RO 2216 is mapped to 2226, and RO 2218 is mapped to 2228. The additional ROs 2222, 2224, 2226, and 2228 are located on both sides of the configured ROs 2212, 2214, 2216, and 2218 in the frequency domain. Fig. 22In the embodiment, there are additional ROs (e.g., RO 2222 and RO 2224) located at the higher frequency side of the configured ROs 2212, 2214, 2216, and 2218, and two other additional ROs (e.g., RO 2226 and RO 2228) located at the lower frequency side of the configured ROs 2212, 2214, 2216, and 2218. The configured ROs 2212, 2214, 2216, and 2218 and the additional ROs 2222, 2224, 2226, and 2228 are combined to provide transmission resources for PRACH repetition with frequency hopping. Each of the configured ROs 2212, 2214, 2216, and 2218 and one RO corresponding thereto of the additional ROs 2212, 2214, 2216, and 2218 may be referred to as an RO combination. For different RO combinations, the absolute values of the frequency offsets (e.g., offsets 2232 and offsets 2234) between the configured ROs 2212, 2214, 2216, and 2218 and the corresponding additional ROs 2212, 2214, 2216, and 2218 may be the same. That is, the absolute value of offset 2234 (between RO 2218 and RO 2224) is equal to offset 2232 (between RO 2212 and RO 2226). In some examples, the offset is indicated via signaling (e.g., RRC signaling, MAC layer signaling, or physical layer signaling, etc.). The offset may be configured for all RO combinations or for each RO combination separately. In some examples, additional signaling may be used in some examples to indicate the frequency start RB on each side of the additional ROs 2212, 2214, 2216, and 2218. In some examples, the configured ROs 2212, 2214, 2216, and 2218 and the additional ROs 2212, 2214, 2216, and 2218 are connected to each other in the frequency domain. That is, the starting RB of the first additional RO (e.g., 2224) of a higher frequency is the last RB of the last configured RO (e.g., 2212) plus a margin (e.g., 1), and the last RB of the last additional RO (e.g., 2226) of a lower frequency is the first RB of the first configured RO (e.g., 2218) minus a margin (e.g., 1).
[0118] Fig.23 A subframe (or time slot) 2300 is shown that a UE may use to transmit uplink data (e.g., PRACH related data) according to some deployments. The subframe (or time slot) includes a subframe (or time slot) 2302 and a subframe (or time slot) 2304. The horizontal dimension corresponds to time (e.g., frame, subframe, or time slot), and the vertical dimension corresponds to frequency. ROs 2312, 2314, 2316, and 2318 are in subframe (or time slot) 2302, and ROs 2322, 2324 are in subframe (or time slot) 2304. Fig.23 In another example shown, two or more ROs of the ROs 2312, 2314, 2316, and 2318 configured via signaling may be mapped with an additional RO (e.g., 2322 or 2324). The additional RO 2322 and the additional RO 2324 may be located on one side or both sides of the configured ROs 2312, 2314, 2316, and 2318 in the frequency domain. Fig.23 In the example, two configured ROs are mapped to an additional RO. For example, RO 2318 and RO 2316 are mapped to RO 2324, and RO 2314 and RO 2312 are mapped to RO 2322. The mapping relationship between the configured RO and the additional RO can be configured via RRC signaling. For example, the mapping factor can be configured to 2, which means that two configured ROs are mapped to one additional RO. The configured ROs mapped to the same additional RO can be adjacent (e.g., adjacent configured ROs in the frequency domain are mapped to the same additional RO) or non-adjacent (e.g., at least two non-adjacent configured ROs in the frequency domain are mapped to the same additional RO). In some examples, additional signaling can be used in some examples to indicate the frequency starting RB of the additional RO on each side of the configured RO in the frequency domain. In other examples, the configured RO and the additional RO are connected to each other in the frequency domain (e.g., continuous, with no gaps therebetween). That is, the starting RB of the first attached RO of higher frequency is the last RB of the last configured RO plus a margin (e.g., 1), and the last RB of the last attached RO of lower frequency is the first RB of the first configured RO minus a margin (e.g., 1).
[0119] In some deployments, the time domain window may be determined based on the SSB index, or the SSB sequence in all actually transmitted SSBs. Regarding the SSB sequence in all actually transmitted SSBs, if three SSBs (e.g., #0, #2, #4) are actually transmitted, the sequence of SSB#0 in all actually transmitted SSBs is 1, the sequence of SSB#2 in all actually transmitted SSBs is 2, and the sequence of SSB#4 in all actually transmitted SSBs is 3. In other words, the sequence refers to the sequence position or sequence number in time where the transmitted SSB is located.
[0120] In some examples, the RO window may be determined in the manner described herein, except that the SSB index or the SSB sequence in all actually transmitted SSBs is used instead of the repetition number. Each RO window is then associated with the same SSB, and PRACH repetitions with different beams may be transmitted within the RO window. Thus, in some examples, the time domain window is determined based on the SSB index or the SSB sequence.
[0121] Fig.24 24 is a flow chart illustrating an example method 2400 for transmitting at least one PRACH repetition according to some deployments. Figures 1 to 24 , method 2400 can be performed by UE 104 / 204 and base station 102 / 202.
[0122] At 2420, the UE determines time domain resources and frequency domain resources for transmitting at least one PRACH repetition. In some examples, determining the time domain resources and frequency domain resources includes: receiving a configuration, indication, or other information defining the time domain resources and frequency domain resources from the network. In this regard, at 2410, the base station may configure the time domain resources and frequency domain resources for transmitting at least one PRACH repetition. In other examples, the UE may use other methods to determine the time domain resources and frequency domain resources.
[0123] At 2430, the UE transmits at least one PRACH repetition to the base station using time domain resources and frequency domain resources. At 2440, the base station receives at least one PRACH repetition from the UE using time domain resources and frequency domain resources.
[0124] In some examples, the UE determines a time domain window (e.g., an RO window). The time domain resource is within the time domain window. In some examples, each time domain window in a plurality of time domain windows corresponds to a PRACH transmission in a plurality of PRACH transmissions. Each PRACH transmission in a plurality of PRACH transmissions has a different number of repetitions.
[0125] In some examples, multiple time domain windows are arranged in order, or multiple time domain windows are cyclic. The order in which multiple time domain windows are arranged includes an ascending order of the number of repetitions of each PRACH transmission in multiple PRACH transmissions. In some examples, multiple time domain windows are continuously connected to each other. In some examples, multiple time domain windows include at least one time domain window group, the at least one time domain window group appears periodically, and adjacent time domain window groups are non-continuous. In some examples, multiple time domain windows include at least two time domain window group sets, a centralized time domain window group appears periodically, and different time domain window group sets are configured with different periods. In some examples, the UE determines the length of each time domain window in multiple time domain windows. The lengths of two or more time domain windows in multiple time domain windows are the same or different. The UE determines the length of each time domain window in multiple time domain windows in the following manner: the UE receives a reference length and at least one proportional factor from a base station, and the UE determines the length of each time domain window in multiple time domain windows based on one or more of the reference length, at least one proportional factor, and different numbers of repetitions.
[0126] In some examples, the UE determines multiple time domain windows by determining a reference time domain window (e.g., corresponding to non-repetition), and determining at least one time domain window (e.g., corresponding to at least one repetition or two transmissions) based on the reference time domain window and the offset. In some examples, the reference time domain window corresponds to a non-repetitive PRACH. Each time domain window in the at least one time domain window corresponds to at least one PRACH repetition. The offset is determined based on the step size and the number of repetitions of the at least one repetition. In some examples, the UE determines that two time domain windows in the multiple time domain windows overlap in time, and modifies one of the two time domain windows in the multiple time domain windows based on the offset.
[0127] In some examples, the UE sorts multiple time domain resources in the time domain window and maps the multiple time domain resources to at least one SSB based on the sorting. In some examples, the UE maps multiple time domain resources in two or more time domain windows of the multiple time domain windows within the time period to at least one SSB. In some examples, the UE maps multiple time domain resources in each time domain window of the multiple time domain windows to at least one SSB. In some examples, the UE determines two or more time domain windows of the multiple time domain windows based on the number of at least one repetition, and maps multiple time domain resources in two or more time domain windows of the multiple time domain windows to at least one SSB.
[0128] In some deployments, the UE receives a frequency domain resource set for each number of at least one repetition from a base station. In some examples, the UE receives a reference frequency domain resource set for one number of at least one repetition from the base station, receives one or more offsets corresponding to at least one other number of at least one repetition from the base station, and determines a frequency domain resource set for each number of at least one repetition of at least one other number of at least one repetition based on the reference frequency domain resource set and the one or more offsets. In some examples, the UE receives the number of frequency domain multiplexed resources from the base station, and the number of frequency domain multiplexed resources is the same for any number of at least one repetition. In some examples, the UE receives a frequency starting point of a first frequency domain resource among a plurality of frequency domain resources corresponding to at least one repetition of a first number from the base station, and determines a frequency starting point of a second frequency domain resource among a plurality of frequency domain resources corresponding to at least one repetition of a second number.
[0129] In some examples, the time domain resource includes a first time domain resource corresponding to the first number of repetitions and a second time domain resource corresponding to the second number of repetitions. The first time domain resource and the second time domain resource have the same starting point. The first number is greater than the second number. The first time domain resource lasts for a longer period of time than the second time domain resource.
[0130] In some examples, the time domain window is determined based on an SSB index or an SSB sequence.
[0131] Although various deployments of the present disclosure have been described above, it should be understood that these embodiments are presented only as examples and not as limitations. Similarly, various diagrams may depict example architectures or configurations, which are provided to enable those of ordinary skill in the art to understand the example features and functions of the present solution. However, those of ordinary skill in the art will understand that the solution is not limited to the example architectures or configurations shown, but may be implemented using various alternative architectures and configurations. In addition, as those of ordinary skill in the art will understand, one or more features of one deployment may be combined with one or more features of another deployment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative deployments.
[0132] It should also be understood that any reference to elements using names such as "first", "second", etc. in this article does not generally limit the number or order of these elements. Instead, these names can be used as a convenient means of distinguishing between two or more elements or instances of elements in this article. Therefore, the reference to the first and second elements does not mean that only two elements can be used or that the first element must precede the second element in some way.
[0133] In addition, those skilled in the art will appreciate that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, and symbols such as may be referenced in the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.
[0134] Those of ordinary skill in the art will further understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of the two), firmware, various forms of programs or design codes in conjunction with instructions (which, for convenience, may be referred to herein as "software" or "software modules"), or any combination of these technologies. In order to clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functions. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the overall system. The technician may implement the described functionality in various ways for each specific application, but such implementation decisions will not result in a departure from the scope of the present disclosure.
[0135] Further, it will be understood by those of ordinary skill in the art that the various illustrative logic blocks, modules, devices, components and circuits described herein may be implemented in or performed by an integrated circuit (IC), which may include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device or any combination thereof. The logic blocks, modules and circuits may also include antennas and / or transceivers to communicate with various components within a network or within a device. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller or state machine. The processor may also be implemented as a combination of computing devices, for example, a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or a combination of any other suitable configurations that perform the functions described herein.
[0136] If these functions are implemented in software, they can be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, and communication media include any medium that can enable a computer program or code to be transferred from one location to another. The storage medium can be any available medium that a computer can access. As an example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or can be used to store the required program code in the form of instructions or data structures and any other medium that can be accessed by a computer.
[0137] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. In addition, for the purpose of discussion, various modules are described as separate modules; however, as is clear to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs associated functions according to the deployment of the present solution.
[0138] In addition, memory or other storage devices and communication components can be used in the deployment of this solution. It should be understood that, for the purpose of clarity, the above description describes the deployment of this solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functions between different functional units, processing logic elements or domains can be used without detracting from this solution. For example, functions shown as being performed by separate processing logic elements or controllers can be performed by the same processing logic element or controller. Therefore, references to specific functional units are only references to suitable means for providing the described functions, rather than indicating a strict logical or physical structure or organization.
[0139] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be given the widest scope consistent with the new features and principles disclosed herein as described in the following claims.
Claims
1. A wireless communication method, include: The wireless communication device determines a time domain resource and a frequency domain resource for transmitting at least one repetition of a physical access channel PRACH; as well as The wireless communication device transmits the at least one PRACH repetition to a base station using the time domain resources and the frequency domain resources.
2. The method according to claim 1, further comprising: include: The wireless communication device determines a time domain window, wherein the time domain resources are within the time domain window.
3. The method according to claim 1, in, Each time domain window of the plurality of time domain windows corresponds to one PRACH transmission of the plurality of PRACH transmissions, and each PRACH transmission of the plurality of PRACH transmissions has a different number of repetitions.
4. The method according to claim 3, in, One of the following situations occurs: The multiple time domain windows are arranged in sequence; or The multiple time domain windows are cyclic.
5. The method according to claim 4, in, The order in which the plurality of time domain windows are arranged comprises an ascending order of a number of repetitions of each of the plurality of PRACH transmissions.
6. The method according to claim 3, in, The multiple time domain windows are continuous with each other.
7. The method according to claim 3, in, The multiple time domain windows include at least one time domain window group, the at least one time domain window group appears periodically, and adjacent time domain window groups are non-continuous.
8. The method according to claim 3, in, The multiple time domain windows include at least two time domain window group sets, the time domain window groups in one set appear periodically, and different time domain window group sets are configured with different periods.
9. The method according to claim 3, further comprising: include: The length of each time domain window among the multiple time domain windows is determined, wherein the lengths of two or more time domain windows among the multiple time domain windows are the same or different.
10. The method according to claim 9, further comprising: include: The length of each time domain window in the plurality of time domain windows is determined by: The wireless communication device receives a reference length and at least one scaling factor from the base station; as well as The wireless communication device determines a length of each of the plurality of time domain windows based on one or more of the reference length, the at least one scaling factor, and the different numbers of repetitions.
11. The method according to claim 3, further comprising: include: The multiple time domain windows are determined by: determining a reference time domain window; and At least one time domain window is determined based on the reference time domain window and the offset.
12. The method according to claim 11, in, The reference time domain window corresponds to the non-repeated PRACH; and Each time domain window of the at least one time domain window corresponds to the at least one PRACH repetition.
13. The method according to claim 11, in, The offset is determined based on a step size and a number of repetitions of the at least one repetition.
14. The method according to claim 3, further comprising: include: The wireless communication device determines that two time domain windows among the plurality of time domain windows overlap in time; as well as One of the two time-domain windows of the plurality of time-domain windows is modified based on the offset.
15. The method according to claim 2, further comprising: include: The wireless communication device sorts a plurality of time domain resources in the time domain window; as well as The wireless communication device maps the plurality of time domain resources to at least one synchronization signal / physical broadcast channel (PBCH) block (SSB) based on the ranking.
16. The method according to claim 3, further comprising: include: The wireless communication device maps a plurality of time domain resources in two or more of the plurality of time domain windows within a time period to at least one synchronization signal / physical broadcast channel (PBCH) block (SSB).
17. The method according to claim 3, further comprising: include: The wireless communication device maps a plurality of time domain resources in each of the plurality of time domain windows to at least one synchronization signal / physical broadcast channel (PBCH) block (SSB).
18. The method according to claim 3, further comprising: include: determining two or more time domain windows among the plurality of time domain windows based on the number of the at least one repetition; as well as The wireless communication device maps a plurality of time domain resources in the two or more time domain windows of the plurality of time domain windows to at least one synchronization signal / physical broadcast channel (PBCH) block (SSB).
19. The method according to claim 1, further comprising: include: The wireless communication device receives, from the base station, a frequency domain resource set for each number of the at least one repetition.
20. The method according to claim 1, further comprising: include: The wireless communication device receives, from the base station, a reference frequency domain resource set for a number of the at least one repetition; The wireless communication device receives from the base station one or more offsets corresponding to at least one other number of the at least one repetition; as well as The wireless communication device determines a frequency-domain resource set for each of the at least one other number of the at least one repetition based on the reference frequency-domain resource set and the one or more offsets.
21. The method according to claim 1, further comprising: include: The wireless communication device receives the number of frequency-domain multiplexed resources from the base station, and the number of frequency-domain multiplexed resources is the same for any number of the at least one repetition.
22. The method according to claim 1, further comprising: include: The wireless communication device receives, from the base station, a frequency starting point of a first frequency domain resource among a plurality of frequency domain resources corresponding to the at least one repetition of a first number; as well as The wireless communication device determines a frequency starting point of a second frequency domain resource among a plurality of frequency domain resources corresponding to the at least one repetition of a second number.
23. The method according to claim 1, in, The time domain resources include first time domain resources corresponding to the first number of repetitions and second time domain resources corresponding to the second number of repetitions; The first time domain resource and the second time domain resource have the same starting point; and The first amount is greater than the second amount; and The first time domain resource lasts for a longer period of time than the second time domain resource.
24. The method according to claim 2, in, The time domain window is determined according to a synchronization signal / physical broadcast channel (PBCH) block (SSB) index or an SSB sequence.
25. The method according to claim 1, in, The frequency domain resources include at least one configured frequency domain resource and at least one additional frequency domain resource mapped to the at least one configured frequency domain resource, and the at least one configured frequency domain resource and the at least one additional frequency domain resource do not overlap in the frequency domain.
26. A wireless communication device comprising at least one processor and a memory, in, The at least one processor is configured to read code from the memory and implement the method according to claim 1.
27. A computer program product, comprising a computer-readable program medium on which codes are stored, which, when executed by at least one processor, cause the at least one processor to implement the method according to claim 1.
28. A wireless communication method, include: The base station configures, for the wireless communication device, time domain resources and frequency domain resources for transmitting at least one repetition of a physical random access channel (PRACH); as well as The base station receives the at least one PRACH repetition from the wireless communication device using the time domain resources and the frequency domain resources.
29. A wireless communication device comprising at least one processor and a memory, in, The at least one processor is configured to read code from the memory and implement the method according to claim 28.
30. A computer program product comprising a computer readable program medium having codes stored thereon, which when executed by at least one processor cause the at least one processor to implement the method according to claim 28.
