System and method for determining sequence length

Abstract

Systems and methods for determining a sequence length are provided. A wireless communication device can determine a sequence length of a sequence. The wireless communication device can apply the sequence to an uplink transmission in accordance with the sequence length.

Description

Technical Field

[0001] This disclosure relates generally to wireless communications, including but not limited to systems and methods for determining sequence lengths. Background Technology

[0002] The standards organization Third Generation Partnership Project (3GPP) is currently specifying a new radio interface called 5G New Radio (5G NR) and the next-generation packet core network (NG-CN or NGC). 5G NR will have three main components: the 5G Access Network (5G-AN), the 5G Core Network (5GC), and the User Equipment (UE). To facilitate the implementation of different data services and requirements, the elements of 5GC (also known as network functions) have been simplified, some based on software and others on hardware, so that they can be adapted as needed. Satellite communication is one of the typical scenarios for non-terrestrial networks in 3GPP standardization. Summary of the Invention

[0003] The exemplary embodiments disclosed herein relate to solving problems associated with one or more difficulties presented in the prior art, and provide additional features that will become apparent when taken in conjunction with the accompanying drawings and the following detailed description. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example and are not limiting, and that various modifications can be made to the disclosed embodiments by those skilled in the art who have read this disclosure, while remaining within the scope of this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium. A wireless communication device (e.g., a user equipment (UE)) can determine the sequence length of a sequence. The wireless communication device can apply the sequence to an uplink transmission based on the sequence length. In some embodiments, the uplink transmission may include at least one of the following: multiple repetitions of a Physical Uplink Shared Channel (PUSCH) transmission scheduled by downlink control information (DCI) signaling; multiple repetitions of a PUSCH transmission scheduled by at least one of a Random Access Response (RAR) message or a Fallback RAR message (e.g., RAR (msg2) schedules msg3 in a 4-step RACH, and Fallback RAR (msgB) schedules msg3 in a 2-step RACH); multiple repetitions of a PUSCH transmission during a random access procedure (e.g., MsgA PUSCH); or multiple repetitions of a configured licensed PUSCH transmission.

[0005] In some embodiments, the application sequence may include applying at least one sequence to one or more units in an uplink transmission. One or more units in an uplink transmission may include at least one of the following: one or more repeat groups, one or more repeats, one or more time slots, one or more symbols, one or more resource elements (REs), or one or more resource blocks (RBs). In some embodiments, the sequence may include at least one of the following: an orthogonal overlay code (OCC) sequence, a non-orthogonal multiple access (NOMA) sequence, or a sequence based on a discrete Fourier transform (DFT), Walsh sequence, Zadov-Chu (ZC) sequence, or a Hadamard matrix or code. In some embodiments, the sequence length may refer to at least one of the following: the nominal sequence length; or the actual sequence length. In some embodiments, there is no distinction between the actual sequence length and the nominal sequence length.

[0006] In some embodiments, the actual sequence length may include at least one of the following: the actual length of an orthogonal cover code (OCC) sequence, a non-orthogonal multiple access (NOMA) sequence, or a sequence based on a discrete Fourier transform (DFT), Walsh sequence, Zadov-Chu (ZC) sequence, or a Hadamard matrix or code; an actual time-domain window (TDW) for applying the sequence or for multiplexing uplink transmissions from multiple wireless communication devices (e.g., UE multiplexing); a sequence length calculated by the wireless communication device for the sequence; or a sequence length to be applied to uplink transmissions. In some embodiments, the wireless communication device may determine the actual sequence length of the sequence based on at least one of the following: the actual TDW for demodulation reference signal (DMRS) bundling, the nominal sequence length of the sequence, one or more events, reconfiguration, or a capability report of the wireless communication device.

[0007] In some embodiments, a wireless communication device may transmit a capability report of the wireless communication device to a wireless communication node. The wireless communication device may receive signaling for determining the nominal sequence length based on the capability report. The wireless communication device may determine the actual sequence length of the sequence. The capability report may include at least one of the following: an indication of the maximum duration, which may be at least one of the following: the maximum duration in which the wireless communication device supports application sequences, demodulation reference signal (DMRS) bundling, or multiplexing uplink transmissions from multiple wireless communication devices; a value at the granularity or level of time slots, symbols, repetitions, or milliseconds (ms); applicable only to non-terrestrial networks (NTN); applicable to NTN or terrestrial networks (TN); or a maximum duration taking into account at least one of the following: phase pre-compensation capability, timing of timing advance (TA) pre-compensation update, or timing of antenna switching; an indication regarding whether TA pre-compensation updates are allowed within the actual sequence length. The wireless communication device may report the indication. TA pre-compensation updates may not be considered when determining the actual sequence length. This indication may be combined with one or more defined capabilities of the maximum duration. An indication regarding whether phase continuity and / or power consistency can be maintained during TA pre-compensation updates.

[0008] In some embodiments, the wireless communication device may determine the nominal sequence length of the sequence as: the same as the number of repetitions; the same as the number of repetition groups; the same as the number of repetitions within the number of repetitions; based on the sequence index; or based on a predefined or broadcast sequence pool or sequence set. One or more events may include at least one of the following: a configured downlink time slot, a reception timing, or a monitoring timing; the occurrence of a gap exceeding a threshold between two consecutive Physical Uplink Shared Channel (PUSCH) transmissions; the occurrence of a gap with at least one scheduled uplink transmission and not exceeding the threshold; the dropping or cancellation of a defined PUSCH transmission; the dropping or cancellation of a defined Physical Uplink Control Channel (PUCCH) transmission; the situation where two PUSCH transmissions with different Sounding Reference Signal (SRS) resource sets are associated and used for PUSCH repetition type A or B; the occurrence of uplink timing adjustment; the occurrence of frequency hopping; the occurrence of phase discontinuity; the occurrence of power inconsistency; the occurrence of TA pre-compensation update; or the occurrence of antenna switching.

[0009] In some embodiments, the repetition configuration may include an indication of at least one of the following: the number of repetitions for uplink transmissions; a repetition group number; the number of repetitions within a repetition group; a number of consecutive repetitions; or a number of repetitions with a time-domain gap less than the defined number of symbols or time slots. In some embodiments, the wireless communication device may determine the actual sequence length of the sequence as: based on at least one of the following: the maximum duration indicated via a capability report, or the subcarrier spacing (SCS) configuration for uplink transmissions; timing information updated according to TA pre-compensation; starting at the first symbol of the first PUSCH transmission in a time slot for PUSCH transmissions within the nominal sequence length; ending at the last symbol of the last PUSCH transmission in a time slot for PUSCH transmissions within the nominal sequence length; ending at the last symbol of the last PUSCH transmission before one or more events; starting at the first symbol of the first PUSCH transmission after one or more events; the same as the nominal sequence length; one or more times the nominal sequence length; the maximum value of the nominal sequence length and the number of repetitions indicated via the repetition configuration; the same as the actual TDW for DMRS bundling; the minimum value of the actual TDW for DMRS bundling; or a portion of the nominal sequence length. In some embodiments, the nominal sequence length may include multiple actual sequence lengths. Each actual sequence may have the same length.

[0010] In some embodiments, a wireless communication node (e.g., a base station (BS)) can receive uplink transmissions from a wireless communication device. A sequence may have been applied to the uplink transmission based on a sequence length determined by the wireless communication device (e.g., a UE). Attached Figure Description

[0011] Various exemplary embodiments of this solution are described in detail below with reference to the figures or accompanying drawings. The drawings are provided for illustrative purposes only and depict only exemplary embodiments of the solution to facilitate the reader's understanding. Therefore, the drawings should not be considered as limitations on the breadth, scope, or applicability of the solution. It should be noted that these drawings are not necessarily drawn to scale for clarity and ease of illustration.

[0012] Figure 1 An example cellular communication network according to an embodiment of the present disclosure is shown, in which the techniques disclosed herein may be implemented;

[0013] Figure 2 Block diagrams of example base station and user equipment apparatuses according to some embodiments of the present disclosure are shown;

[0014] Figure 3 Example implementations of non-terrestrial network (NTN) communication according to some embodiments of this disclosure are shown;

[0015] Figure 4 Example methods for user equipment (UE) demultiplexing according to some embodiments of this disclosure are shown;

[0016] Figure 5 Example sequence lengths according to some embodiments of this disclosure are shown;

[0017] Figure 6 Example methods for determining sequence length according to some embodiments of this disclosure are shown; and

[0018] Figure 7 A flowchart of an example method for determining sequence length according to an embodiment of the present disclosure is shown. Detailed Implementation

[0019] 1. Mobile communication technology and environment

[0020] Figure 1 An example wireless communication network and / or system 100 according to an embodiment of this disclosure is illustrated, in which the techniques disclosed herein may be implemented. In the following discussion, wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as "network 100". Such an example network 100 includes a base station 102 (hereinafter referred to as "BS 102"; also referred to as a wireless communication node) and user equipment 104 (hereinafter referred to as "UE 104"; also referred to as a wireless communication device), which may communicate with each other via a communication link 110 (e.g., a wireless communication channel); and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1 In this context, BS 102 and UE 104 are included within the corresponding geographical boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating within its allocated bandwidth to provide adequate radio coverage to its intended users.

[0021] For example, BS 102 can operate at the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118 / 124 can be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, BS 102 and UE 104 are described herein as non-limiting examples of "communication nodes," which generally practice the methods disclosed herein. According to various embodiments of this solution, such communication nodes may be able to perform wireless and / or wired communication.

[0022] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) according to some embodiments of this solution is shown. System 200 may include components and elements configured to support known or conventional operating characteristics that do not need to be described in detail herein. In one illustrative embodiment, system 200 can be used in wireless communication environments (such as...) Figure 1 In a wireless communication environment 100, data symbols are conveyed (e.g., transmitted and received), as described above.

[0023] System 200 typically includes a base station 202 (hereinafter referred to as "BS 202") and a user equipment 204 (hereinafter referred to as "UE 204"). BS 202 includes a BS (Base Station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with each other via a data communication bus 220 when necessary. UE 204 includes a UE (User Equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with each other via a data communication bus 240 when necessary. BS 202 communicates with UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for data transmission as described herein.

[0024] As understood by those skilled in the art, in addition to Figure 2In addition to the modules shown, system 200 may include any number of modules. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps are generally described in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend on the specific application and design constraints imposed on the system as a whole. Those skilled in the art, skilled in the art, can implement such functionality in a suitable manner for each specific application; however, such implementation decisions should not be construed as limiting the scope of this disclosure.

[0025] According to some embodiments, UE transceiver 230, which may be referred to herein as "uplink" transceiver 230, includes a radio frequency (RF) transmitter and an RF receiver, each including circuitry coupled to antenna 232. A duplex switch (not shown) can alternately couple the uplink transmitter or receiver to the uplink antenna in a time-division duplex manner. Similarly, according to some embodiments, BS transceiver 210, which may be referred to herein as "downlink" transceiver 210, includes a radio frequency (RF) transmitter and an RF receiver, each including circuitry coupled to antenna 212. A downlink duplex switch can alternately couple the downlink transmitter or receiver to downlink antenna 212 in a time-division duplex manner. The operation of the two transceiver modules 210 and 230 can be time-coordinated, such that while the downlink transmitter is coupled to downlink antenna 212, the uplink receiver circuitry is coupled to uplink antenna 232 for receiving transmissions on radio transmission link 250. Conversely, the operation of the two transceiver modules 210 and 230 can be time-coordinated, such that while the uplink transmitter is coupled to the uplink antenna 232, the downlink receiver is coupled to the downlink antenna 212 for receiving transmissions on the wireless transmission link 250. In some embodiments, there is tight time synchronization with a minimum guard time between variations in the duplex direction.

[0026] UE transceiver 230 and base transceiver 210 are configured to communicate via wireless data communication link 250 and cooperate with RF antenna arrangements 212 / 232 appropriately configured to support specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 230 and base transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that this disclosure is not necessarily limited to specific standards and associated protocols in application. More precisely, UE transceiver 230 and base transceiver 210 may be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

[0027] According to various embodiments, BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femtocell, or a picocell. According to some embodiments, UE 204 may be embodied in various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 may be implemented or carried out using a general-purpose processor, content-addressable memory, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, and are designed to perform the functions described herein. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, or the like. The processor may also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors coupled with a digital signal processor core, or any other such configuration.

[0028] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be directly embodied in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any actual combination thereof. Memory modules 216 and 234 can 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, memory modules 216 and 234 can be coupled to processor modules 210 and 230 respectively, such that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234 respectively. Memory modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some embodiments, 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 processor modules 210 and 230 respectively. Memory modules 216 and 234 may each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0029] Network communication module 218 generally refers to the hardware, software, firmware, processing logic, and / or other components of base station 202 that enable bidirectional communication between BS transceiver 210 and other network components and communication nodes configured to communicate with base station 202. For example, network communication module 218 may be configured to support Internet or WiMAX traffic. In a typical deployment, without limitations, network communication module 218 provides an 802.3 Ethernet interface, allowing base station transceiver 210 to communicate with a conventional Ethernet-based computer network. In this way, network communication module 218 may include a physical interface for a connection to a computer network (e.g., a mobile switching center (MSC)). The terms “configured for…”, “configured as…”, and their variations, as used herein with respect to a specified operation or function, refer to devices, components, circuits, structures, machines, signals, etc., that are physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0030] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") is a conceptual and logical layout that defines the openness of network communication used by systems (e.g., wireless communication devices, wireless communication nodes) to interconnection and communication with other systems. The model is decomposed into seven sub-components or layers, each representing a conceptual set of services provided to the layers above and below it. The OSI model also defines logical networks and effectively describes the transmission of computer packets using different layer protocols. The OSI model may also be referred to as the seven-layer OSI model or the seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the Medium Access Control (MAC) layer. In some embodiments, the third layer may be the Radio Link Control (RLC) layer. In some embodiments, the fourth layer may be the Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer may be the Radio Resource Control (RRC) layer. In some embodiments, the sixth layer may be the Non-Access Stratum (NAS) layer or the Internet Protocol (IP) layer, and the seventh layer is another layer.

[0031] Various exemplary embodiments of this solution are described below with reference to the accompanying drawings to enable those skilled in the art to make and use the solution. It will be apparent to those skilled in the art that various changes or modifications can be made to the examples described herein without departing from the scope of this solution after reading this disclosure. Therefore, this solution is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of this solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in a sample order, and unless otherwise expressly stated, this solution is not limited to the specific order or hierarchy presented.

[0032] 2. Systems and methods for determining sequence length

[0033] Uplink (UL) coverage enhancements, such as duplication, can be supported in both new radio (NR) terrestrial networks (TN) and non-terrestrial networks (NTN). However, the use of duplication can significantly reduce system capacity and individual user throughput. Duplication can also increase user equipment (UE) transmission time. Therefore, higher utilization of UL resources in the time domain can be implemented.

[0034] In practical NR NTN deployments, it is increasingly evident that systems can be severely resource-constrained, especially in UL (Upper Limit) systems, when a limited amount of spectrum is expected to be available for NR NTN service deployment. To address the UL capacity issue, sequences (e.g., orthogonal coverage code (OCC) sequences) can be applied to data transmissions with repetitions, allowing data from multiple UEs to be extracted from a multiplexed signal by utilizing different sequences. However, sequence utilization requires that channel information be nearly identical between repetitions. The actual sequence length can be determined by several other factors (e.g., power, timing advance (TA)) and the nominal sequence length. In this disclosure, a method for determining the sequence length is implemented.

[0035] Figure 3 Example implementations of non-terrestrial networks (NTNs) according to some embodiments of this disclosure are shown. An example structure of a transparent NTN is shown in... Figure 3 As shown in the diagram. The link between the UE and the satellite can be a serving link. The link between the BS and the satellite can be a feeder link and can be shared by all UEs within the same cell.

[0036] Physical Uplink Shared Channel (PUSCH) Configuration

[0037] Below is a structure RRC parameter PUSCH-TimeDomainResourceAllocation information element. It can be seen that the duration of the PUSCH transmission can be configured using the list of Telecommunications and Digital Government Regulatory Agencies (TDRA) with parameters startSymbolAndLength, startSymbolAndLength-r16, or length-r16, and the repetition number can be configured with parameters numberOfRepetitions or numberOfRepetitionsExt-r17.

[0038] PUSCH-TimeDomainResourceAllocation information element

[0039]

[0040]

[0041] The IE (Information Element) PUSCH-TimeDomainResourceAllocation can be used to configure the time-domain relationship between the Physical Downlink Control Channel (PDCCH) and the PUSCH. The PUSCH-TimeDomainResourceAllocationList can include one or more such PUSCH-TimeDomainResourceAllocations. The network can indicate in the UL authorization which configured time-domain allocations the UE can apply to that UL authorization. The UE can determine the bit width of the DCI field based on the number of entries in the PUSCH-TimeDomainResourceAllocationList. A value of 0 in the DCI field can refer to the first element in the list, a value of 1 in the DCI field can refer to the second element in the list, and so on.

[0042] The following example uses the TDRA field in DCI format 0_1 ​​to illustrate the process of scheduling PUSCH transmissions via DCI.

[0043] -Time-domain resource allocation – 0, 1, 2, 3, 4, 5, or 6 bits.

[0044] - If the higher-level parameter `pusch-TimeDomainAllocationListDCI-0-1` is not configured, and the higher-level parameter `pusch-TimeDomainAllocationListForMultiPUSCH` is not configured, but the higher-level parameter `pusch-TimeDomainAllocationList` is configured, then 0, 1, 2, 3, or 4 bits can be defined. The bit width of this field is determined in bits, where I is the number of entries in the higher-level parameter `pusch-TimeDomainAllocationList`.

[0045] - If the higher-level parameter pusch-TimeDomainAllocationListDCI-0-1 or pusch-TimeDomainAllocationListForMultiPUSCH is configured, then define 0, 1, 2, 3, 4, 5, or 6 bits. The bit width of this field can be determined in bits, where I is the number of entries in the higher-level parameter pusch-TimeDomainAllocationListDCI-0-1 or pusch-TimeDomainAllocationListForMultiPUSCH.

[0046] - Otherwise, the width of the field can be determined to be bits, where I is the number of entries in the default table.

[0047] When repetition is configured for PUSCH transmission, the data and associated DMRS can be identical in each repetition if the redundant versions are the same. However, when multiple UEs are multiplexed in the same frequency and time domain resources, the data portion can be multiplexed in a non-orthogonal manner, which can increase decoding complexity to eliminate interference from other UEs.

[0048] Joint Channel Estimation / Demodulation Reference Signal (DMRS) Bundling

[0049] Joint channel estimation (JCE) can be considered for NR coverage enhancement. For JCE, reference signals (RS) from different time instances can be used together to estimate the channel, providing better channel estimation and potentially better decoding performance. Since the RSs to be jointly estimated may be coherent, the DMRS bundling time-domain window (TDW) can be specified, during which DMRS can be bundled for estimation. For example, a UE can report its ability to maintain power consistency and phase continuity to support the maximum duration of DM-RS bundling. The network can configure the nominal TDW length. The UE can determine the actual TDW based on the nominal TDW configuration and events that cause power consistency and phase continuity to be lost across multiple transmissions within the nominal TDW. The UE can maintain power consistency and phase continuity within the actual TDW.

[0050] The following events can be specified for actual TDW determination.

[0051] - Downlink slots or downlink reception or downlink monitoring for unpaired spectrum based on tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0052] - The gap between any two consecutive PUSCH transmissions, or the gap between any two consecutive PUCCH transmissions, is more than 13 symbols for a normal cyclic prefix or more than 11 symbols for an extended cyclic prefix.

[0053] - The gap between any two consecutive PUSCH transmissions or between any two consecutive PUCCH transmissions shall not exceed 13 symbols, but other uplink transmissions are scheduled between two consecutive PUSCH transmissions or between two consecutive PUCCH transmissions.

[0054] - For PUSCH repeat type A, or PUSCH repeat type B, or PUSCH transfers processed by TB on multiple time slots, the PUSCH transfer is discarded or canceled.

[0055] - For PUCCH repeating PUCCH transmissions, the PUCCH transmission is discarded or canceled.

[0056] - For any two consecutive PUSCH transfers of PUSCH repetition type A or PUSCH repetition type B, and when two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, where the higher-level parameter usage in SRS-ResourceSet is set to "codebook" or "non-codebook", different SRS resource set associations are used for the two PUSCH transfers of PUSCH repetition type A or PUSCH repetition type B.

[0057] - For any two consecutive PUCCH transmissions that repeat PUCCH, and when the repeating PUCCH resources used by the UE for PUCCH transmission include first and second spatial relationships or first and second sets of power control parameters, different spatial relationships or different power control parameters are used for the two PUCCH transmissions that repeat PUCCH.

[0058] - Uplink timing adjustments in response to timing advance commands.

[0059] - Frequency hopping.

[0060] - For a half-duplex UE with reduced capability, the dropping or cancellation of PUSCH or PUCCH transmissions, or the overlap between gaps between two consecutive PUSCH or PUCCH transmissions and any symbols received or monitored by downlink.

[0061] In addition, the following phase difference limits can be defined for DMRS bundling.

[0062]

[0063] Table 1. Maximum permissible phase difference for DMRS bundling

[0064] To introduce orthogonality among UEs, a method can be provided such that each UE uses a sequence to be multiplied with the data portion of a transmission received / transmitted by the UE (e.g., a PUSCH transmission transmitted by the UE), so that UEs can be distinguished by the sequence and the data portion can be extracted from the multiplexed signal. A method for determining the sequence length is described in this disclosure.

[0065] Figure 4Example user equipment (UE) demultiplexing according to some embodiments of this disclosure is illustrated. To better understand the principle, consider the sequence [+1 +1; +1 -1] as an example. UE1 can select the sequence [+1 +1], and UE2 can select the sequence [+1 -1]. Each UE can have two repetitions with the same content. UE1 and UE2 can transmit X1 and X2 respectively in the same time and frequency domain resources; therefore, the superimposed signal can be represented as Y1 and Y2 at the positions of the first and second repetitions. Figure 4 As shown, X1 and X2 can be calculated based on Y1 and Y2 and their corresponding channel state information. It can be noted that demultiplexing is only effective when the channel information is identical or nearly identical between repetitions. The determination of the sequence length can take into account factors related to the channel, power, TA, phase difference between time slots, etc. In some embodiments, the PUSCH transmission in this disclosure includes at least one of the following PUSCH transmissions: PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2, PUSCH repetition type A with configured authorization, or PUSCH repetition type B, and TB processing over multiple time slots.

[0066] Example 1: The actual sequence length (or the actual TDW used for sequence applications) can be determined based on at least one of the following: the actual TDW used for DMRS bundling, the nominal sequence length, events, repetition configuration, or capability reports.

[0067] In some embodiments, the actual sequence length may refer to at least one of the following: actual sequence length, actual OCC length (e.g., the actual length of the OCC sequence used as a sequence), actual time-domain window (TDW) for sequence application (or UE multiplexing), determined / calculated sequence length, or sequence length applied to uplink transmission. In some embodiments, the nominal sequence length may refer to at least one of the following: nominal sequence length, nominal OCC length, nominal TDW for application (or UE multiplexing), configured sequence length, or sequence length determined by repetition number. In some embodiments, the maximum number of UEs multiplexed may be associated with the actual sequence length of the UE. In some embodiments, the maximum number of UEs multiplexed may be associated with the minimum actual sequence length of multiple UEs.

[0068] The sequence in this implementation example may refer to (or include / comprise) at least one of the following: an orthogonal covering code (OCC) sequence or a non-orthogonal multiple access (NOMA) sequence. The OCC sequence may be based at least on a discrete Fourier transform (DFT) sequence, a Walsh sequence, a Zadov-Chu (ZC) sequence, or a Hadamard matrix or code.

[0069] For example, OCC sequences with different sequence lengths can be shown below.

[0070]

[0071] Table 2. Examples of OCC sequences with lengths of 2, 4, and 8

[0072] How to determine the nominal sequence length

[0073] The wireless communication device can determine the nominal sequence length of a sequence based on signaling from the wireless communication node, which in turn determines the nominal sequence length based on the capability report of the wireless communication device.

[0074] Option 1: Explicit signaling from the BS includes at least one of the following: RRC messages, MAC CE messages, DCI messages, or system information (e.g., SIB). In some embodiments, the nominal sequence length configured by the BS can be determined by a capability report. Capabilities for DMRS bundling can be specified (e.g., indicated / configured via the parameter maxDurationDMRS-Bundling-r17), indicating whether the UE supports the maximum duration during which the UE can maintain power consistency and phase continuity to support DM-RS bundling for PUSCH / PUCCH transmissions. Similarly, for UE multiplexing or sequence applications, the UE can also report capabilities for (or including) at least one of the following, taking into account all factors or events that could lead to phase discontinuities or power inconsistencies:

[0075] 1. Maximum duration.

[0076] In some implementations, the maximum duration can be at least one of the following: slot level, symbol level, repetition level, or millisecond level. In some implementations, the maximum duration can represent / indicate the duration for which the UE is able to support at least one of sequence application, UE multiplexing, or DMRS bundling during this period. In some implementations, the maximum duration can be used only for NTN. In some implementations, the maximum duration can be used for TN or NTN. In some implementations, the maximum duration can take into account the capability of phase pre-compensation, the timing / period of TA pre-compensation updates, and / or the timing / period of antenna switching.

[0077] 2. Whether TA pre-compensation updates are allowed within the actual sequence length.

[0078] In some implementations, the UE can report that TA pre-compensation updates are allowed within the actual sequence length, without considering TA pre-compensation updates in the actual sequence length determination. In some implementations, the UE can report that TA pre-compensation updates are not allowed within the actual sequence length. This capability can be combined with at least one of the following: the capability for the maximum duration of DMRS bundling for TN or NTN; a new capability that allows the UE to support at least one of sequence application, UE multiplexing, or DMRS bundling during this period without considering the maximum duration of TA pre-compensation updates and / or antenna handover; or a new capability that allows the UE to support at least one of sequence application, UE multiplexing, or DMRS bundling during this period without considering the maximum duration of events determined by the UE that cause power consistency and phase continuity to be compromised.

[0079] 3. Can phase continuity and / or power consistency be maintained during TA pre-compensation updates?

[0080] More specifically, when a TA pre-compensation update occurs, can the phase difference limitation of at least one of sequence application, UE multiplexing, or DMRS bundling be maintained? In some embodiments, this capability 3 may be similar to capability 2, but expressed more broadly. Sub-bullet notations of capability 2 may also be used here.

[0081] Option 2: Implicit determination

[0082] In some embodiments, the nominal sequence length may be the same as the number of repeats. In some embodiments, the nominal sequence length may be the same as the number of repeat groups. In some embodiments, repeats with the same redundant version may be considered to belong to the same repeat group. The number of repeat groups (e.g., the number of repeat groups) may be the same as the number of unique redundant versions. In some embodiments, the number of repeat groups is a predefined value, such as 2 or 4.

[0083] In some embodiments, the nominal sequence length may be the same as the number of repeats within a repeat group. In some embodiments, repeats with the same redundant version may be considered to belong to the same repeat group. The number of repeat groups may be the same as the number of unique redundant versions. In some embodiments, the number of repeat groups may be a predefined value, such as 2 or 4.

[0084] In some embodiments, the nominal sequence length may be determined by the sequence index (e.g., the index number assigned to the sequence). In some embodiments, the sequence pool or set may be predefined or broadcast, and the sequence index may be configured by the BS or determined by other parameters, and the nominal sequence length may be the same as the length of the sequence indicated by the sequence index.

[0085] In some embodiments, the nominal sequence length may be determined by a predefined or broadcast sequence pool (or sequence set). In some embodiments, the sequence pool or set may be predefined or broadcast. Sequences in the sequence pool or sequence set may have the same length. The nominal sequence length may be the same as the length of sequences in the predefined or broadcast sequence pool (or sequence set).

[0086] What is the event (e.g., a triggering event or condition used to determine the actual sequence length)?

[0087] Since the determination of actual sequence length is similar to the determination of actual TDW in DMRS bundles, the events can also consider / include existing events defined for DMRS bundles, such as the following events used for actual TDW determination, which can be used for actual sequence length determination.

[0088] - During downlink time slots or downlink reception or downlink monitoring for unpaired spectrum based on tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0089] - When the gap between any two consecutive PUSCH transmissions or the gap between any two consecutive PUCCH transmissions exceeds the duration, where the duration can be a predefined value (e.g., 13 symbols for NCP or 11 symbols for ECP) ​​or configured by the BS.

[0090] - When the gap between any two consecutive PUSCH transmissions or the gap between any two consecutive PUCCH transmissions does not exceed the duration, but one or more other uplink transmissions are scheduled between two consecutive PUSCH transmissions or two consecutive PUCCH transmissions.

[0091] - For PUSCH repeat type A, or PUSCH repeat type B, or PUSCH transmissions processed by TB on multiple time slots, the dropping or cancellation of PUSCH transmissions occurs.

[0092] - For PUCCH repeating PUCCH transmissions, the dropping or cancellation of PUCCH transmissions occurs.

[0093] - For any two consecutive PUSCH transfers of PUSCH repetition type A or PUSCH repetition type B, and when two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, where the higher-level parameter usage in SRS-ResourceSet is set to "codebook" or "non-codebook", different SRS resource set associations are used for the two PUSCH transfers of PUSCH repetition type A or PUSCH repetition type B.

[0094] - For any two consecutive PUCCH transmissions that repeat PUCCH, and when the repeating PUCCH resources used by the UE for PUCCH transmission include first and second spatial relationships or first and second sets of power control parameters, different spatial relationships or different power control parameters are used for the two PUCCH transmissions that repeat PUCCH.

[0095] - During or during an uplink timing adjustment in response to a timing advance command.

[0096] - During frequency hopping, or when frequency hopping occurs.

[0097] - For a half-duplex UE with reduced capability, the occurrence of dropping or canceling a PUSCH or PUCCH transmission, or the overlap between a gap between two consecutive PUSCH transmissions or two consecutive PUCCH transmissions and any symbol received or monitored by the downlink.

[0098] In addition, additional events can be defined for the actual sequence length (e.g., actual sequence length). Additional events can be the occurrence of phase discontinuity, for example, when the phase difference is greater than the maximum permissible phase difference. Additional events can be the occurrence of power inconsistency, for example, when the power difference is greater than the maximum permissible power difference. Additional events can be the occurrence of TA pre-compensation updates, for example, when a TA pre-compensation update occurs. Additional events can be the occurrence of antenna switching, for example, when an antenna switching occurs.

[0099] How to determine the actual sequence length

[0100] 1. In some embodiments, the UE can determine the actual sequence length based on the capability report. In some embodiments, the nominal sequence length may not be configured, or there may be no nominal sequence length, and the actual sequence length can be determined by configuring the maximum duration and / or the subcarrier spacing (SCS) of uplink transmission in the capability report.

[0101] For example, a UE can report a maximum duration of 4 ms, which could mean that within 4 ms, the UE is able to maintain power consistency and phase continuity to support sequence applications. Then, in a PUSCH transmission with 16 repetitions (e.g., in 16 time slots), the actual sequence length could be 4 when the SCS is 15 kHz, 8 when the SCS is 30 kHz, and so on. In NR, for a 15 kHz SCS, one time slot could be 1 ms, and for a 30 kHz SCS, one time slot could be 0.5 ms.

[0102] For example, a UE can report the maximum duration of 4 time slots, which could mean that the UE is able to maintain power consistency and phase continuity within 4 time slots to support sequence applications. In a PUSCH transmission with 16 repetitions (e.g., in 16 time slots), the actual sequence length can be 4.

[0103] In some embodiments, the UE can determine the actual sequence length based on the timing of the TA pre-compensation update. For example, a TA pre-compensation update can be considered an event that causes power consistency and phase continuity to be lost across multiple transmissions within the nominal TDW. For example, the actual sequence length can be equal to or less than the TA pre-compensation update period. The TA pre-compensation update period can be configured by the BS in at least one of the following: RRC message, DCI signaling, or MAC CE signaling. For example, the nominal sequence length can be equal to or less than the TA pre-compensation update period. The TA pre-compensation update period can be configured by the BS in at least one of the following: RRC message, DCI signaling, or MAC CE signaling. Therefore, the TA pre-compensation update may not need to be considered in determining the actual sequence length.

[0104] 2. In some embodiments, the UE can determine the actual sequence length based on the nominal sequence length and / or an event. For PUSCH transmissions with repeated PUSCH, the nominal sequence length may include one or more actual sequence lengths. The UE may determine the actual sequence length as follows: the start of a first actual sequence length may be the first symbol of the first PUSCH transmission in the time slot used for PUSCH transmission within the nominal sequence length; if the actual sequence length reaches the end of the last PUSCH transmission within the nominal sequence length, the end of the actual sequence length may be the last symbol of the last PUSCH transmission in the time slot used for PUSCH transmission within the nominal sequence length; if an event occurs within the nominal sequence length, the end of the actual sequence length may be the last symbol of the PUSCH transmission before the event; or the start of a new actual sequence length may be the first symbol of a PUSCH transmission after the event within the nominal sequence length.

[0105] For PUCCH transmissions with PUCCH repetition, the nominal sequence length may include one or more actual sequence lengths. The UE may determine the actual sequence length as follows: the start of a first actual sequence length may be the first symbol of the first PUCCH transmission in the time slot determined for the PUCCH transmission within the nominal sequence length; if the actual sequence length reaches the end of the last PUCCH transmission within the nominal sequence length, the end of the actual sequence length may be the last symbol of the last PUCCH transmission in the time slot determined for the PUCCH transmission within the nominal sequence length; if an event occurs within the nominal sequence length, the end of the actual sequence length may be the last symbol of the PUCCH transmission preceding the event; the start of a new actual sequence length may be the first symbol of a PUCCH transmission following the event within the nominal sequence length. In some embodiments, the actual sequence length may be the same as the nominal sequence length. In some embodiments, the actual sequence length may be one or more times the nominal sequence length.

[0106] Assuming the nominal sequence length is 8, the sequence can be S = [s1, s2, ..., s8]. Due to events, the actual sequence length can be 8 or shortened to 2 or 4. Figure 5 This is an example illustrating the effect of actual sequence length. Figure 5 Example sequence lengths are shown according to some embodiments of this disclosure.

[0107] 3. In some embodiments, the UE may determine the actual sequence length based on the nominal sequence length and / or repetition configuration. The repetition configuration may include at least one of the following: the number of repetitions; the number of repetition groups; the number of repetitions within a repetition group; the number of consecutive repetitions; or the number of repetitions with a time-domain gap of less than N symbols or time slots, where N is an integer value.

[0108] In some implementations, the actual sequence length can be the maximum of the nominal sequence length and the number of repetitions. In some implementations, the actual sequence can include N nominal sequences connected in sequence. N can be equal to the number of repetitions / nominal sequence length. For example, when the nominal sequence length can be 4, the sequence can be [s1,s2,s3,s4], and when the number of repetitions can be 8, the actual sequence can be [s1,s2,s3,s4,s1,s2,s3,s4] with a length of 8.

[0109] In some implementations, the actual sequence length can be the minimum of the nominal sequence length and the number of repetitions. In some implementations, the number of repetitions N is less than the nominal sequence length, the actual sequence length is also N, and the actual sequence includes the first N sequence elements of the nominal sequence. For example, when the nominal sequence length can be 4, the sequence can be [s1,s2,s3,s4], and when the number of repetitions can be 2, the actual sequence can be adjusted to [s1,s2] of length 2. For example, when the nominal sequence length can be 8, the nominal sequence can be [s1,s2,s3,s4,s5,s6,s7,s8], and when the number of repetitions can be 5, the actual sequence can be [s1,s2,s3,s4,s5] of length 5.

[0110] 4. In some embodiments, the UE can determine the actual sequence length based on the actual TDW used for DMRS bundling. For DMRS bundling, the determination of the actual TDW can be specified. For sequence application or UE multiplexing, the actual sequence length can be determined based on the actual TDW used for DMRS bundling. In some embodiments, the actual sequence length can be equal to the minimum actual TDW used for DMRS bundling. In some embodiments, the actual sequence length within a nominal sequence can be the same.

[0111] For example, such as Figure 6 As shown, the UE can be configured with 8 repetitions. The UE can determine the nominal TDW used for DMRS bundling as 8 time slots. The UE can determine 3 actual TDWs used for DMRS bundling, each with 2, 4, and 2 time slots respectively. The minimum number of these actual TDWs can be 2. The actual sequence length can be 2.

[0112] It should be understood that one or more features from the above / below examples of implementations are not limited to specific examples of implementations, but can be combined in any way (e.g., in any priority and / or order, simultaneously or otherwise).

[0113] Figure 7 A flowchart of a method 700 for determining sequence length is shown. Method 700 can be used in conjunction with this document. Figure 1-6 The method may be implemented using any one or more of the detailed components and devices. In general, in some embodiments, method 700 may be performed by the UE. Depending on the embodiment, additional, fewer, or different operations may be performed in method 700. At least one aspect of the operations relates to a system, method, apparatus, or computer-readable medium.

[0114] A wireless communication device (e.g., a user equipment (UE)) can determine the sequence length of a sequence. The wireless communication device can apply the sequence to an uplink transmission based on the sequence length. In some embodiments, the uplink transmission may include at least one of the following: multiple repetitions of a Physical Uplink Shared Channel (PUSCH) transmission scheduled by downlink control information (DCI) signaling; multiple repetitions of a PUSCH transmission scheduled by at least one of a Random Access Response (RAR) message or a fallback RAR message (e.g., RAR (msg2) schedules msg3 in a 4-step RACH, and fallback RAR (msgB) schedules msg3 in a 2-step RACH); multiple repetitions of a PUSCH transmission during a random access procedure (e.g., MsgA PUSCH transmission); or multiple repetitions of a configured licensed PUSCH transmission.

[0115] In some embodiments, the application sequence may include applying at least one sequence to one or more units in an uplink transmission. One or more units in an uplink transmission may include at least one of the following: one or more repeat groups, one or more repeats, one or more time slots, one or more symbols, one or more resource elements (REs), or one or more resource blocks (RBs). In some embodiments, the sequence may include at least one of the following: an orthogonal overlay code (OCC) sequence, a non-orthogonal multiple access (NOMA) sequence, or a sequence based on a discrete Fourier transform (DFT), Walsh sequence, Zadov-Chu (ZC) sequence, or a Hadamard matrix or code. In some embodiments, the sequence length may refer to at least one of the following: the nominal sequence length; or the actual sequence length. In some embodiments, there is no distinction between the actual sequence length and the nominal sequence length.

[0116] In some embodiments, the actual sequence length may include at least one of the following: the actual length of an orthogonal cover code (OCC) sequence, a non-orthogonal multiple access (NOMA) sequence, or a sequence based on a discrete Fourier transform (DFT), Walsh sequence, Zadov-Chu (ZC) sequence, or a Hadamard matrix or code; an actual time-domain window (TDW) for applying the sequence or for multiplexing uplink transmissions from multiple wireless communication devices (e.g., UE multiplexing); a sequence length calculated by the wireless communication device for the sequence; or a sequence length to be applied to uplink transmissions. In some embodiments, the wireless communication device may determine the actual sequence length of the sequence based on at least one of the following: the actual TDW for demodulation reference signal (DMRS) bundling, the nominal sequence length of the sequence, one or more events, reconfiguration, or a capability report of the wireless communication device.

[0117] In some embodiments, a wireless communication device may transmit a capability report of the wireless communication device to a wireless communication node. The wireless communication device may receive signaling for determining the nominal sequence length based on the capability report. The wireless communication device may determine the actual sequence length of the sequence. The capability report may include at least one of the following: an indication of the maximum duration, which may be at least one of the following: the maximum duration in which the wireless communication device supports application sequences, demodulation reference signal (DMRS) bundling, or multiplexing uplink transmissions from multiple wireless communication devices; a value at the granularity or level of time slots, symbols, repetitions, or milliseconds (ms); applicable only to non-terrestrial networks (NTN); applicable to NTN or terrestrial networks (TN); or a maximum duration taking into account at least one of the following: phase pre-compensation capability, timing of timing advance (TA) pre-compensation update, or timing of antenna switching; an indication regarding whether TA pre-compensation updates are allowed within the actual sequence length. The wireless communication device may report the indication. TA pre-compensation updates may not be considered when determining the actual sequence length. This indication may be combined with one or more defined capabilities of the maximum duration. An indication regarding whether phase continuity and / or power consistency can be maintained during TA pre-compensation updates.

[0118] In some embodiments, the wireless communication device may determine the nominal sequence length of the sequence as: the same as the number of repetitions; the same as the number of repetition groups; the same as the number of repetitions within the number of repetitions; based on the sequence index; or based on a predefined or broadcast sequence pool or sequence set. One or more events may include at least one of the following: a configured downlink time slot, a reception timing, or a monitoring timing; the occurrence of a gap exceeding a threshold between two consecutive Physical Uplink Shared Channel (PUSCH) transmissions; the occurrence of a gap with at least one scheduled uplink transmission and not exceeding the threshold; the dropping or cancellation of a defined PUSCH transmission; the dropping or cancellation of a defined Physical Uplink Control Channel (PUCCH) transmission; the situation where two PUSCH transmissions with different Sounding Reference Signal (SRS) resource sets are associated and used for PUSCH repetition type A or B; the occurrence of uplink timing adjustment; the occurrence of frequency hopping; the occurrence of phase discontinuity; the occurrence of power inconsistency; the occurrence of TA pre-compensation update; or the occurrence of antenna switching.

[0119] In some embodiments, the repetition configuration may include an indication of at least one of the following: the number of repetitions for uplink transmissions; the number of repetition groups; the number of repetitions within a repetition group; the number of consecutive repetitions; or the number of repetitions with a time-domain gap less than the defined number of symbols or time slots. In some embodiments, the wireless communication device may determine the actual sequence length of the sequence as: based on at least one of the following: the maximum duration indicated via a capability report, or the subcarrier spacing (SCS) configuration for uplink transmissions; timing information updated according to TA pre-compensation; starting at the first symbol of the first PUSCH transmission in a time slot for PUSCH transmissions within the nominal sequence length; ending at the last symbol of the last PUSCH transmission in a time slot for PUSCH transmissions within the nominal sequence length; ending at the last symbol of the last PUSCH transmission before one or more events; starting at the first symbol of the first PUSCH transmission after one or more events; the same as the nominal sequence length; one or more times the nominal sequence length; the maximum value of the nominal sequence length and the number of repetitions indicated via the repetition configuration; the same as the actual TDW for DMRS bundling; the minimum value of the actual TDW for DMRS bundling; or a portion of the nominal sequence length. In some embodiments, the nominal sequence length may include multiple actual sequence lengths. Each actual sequence may have the same length.

[0120] In some embodiments, a wireless communication node (e.g., a base station (BS)) can receive uplink transmissions from a wireless communication device. The sequence may have been applied to the uplink transmission based on the actual sequence length determined by the wireless communication device (e.g., a UE).

[0121] While various embodiments of the present solution have been described above, it should be understood that they are presented by way of example only and not by way of limitation. Similarly, various figures may depict exemplary architectures or configurations provided to enable those skilled in the art to understand exemplary features and functionality of the present solution. However, those skilled in the art will understand that the present solution is not limited to the exemplary architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as will be understood by those skilled in the art, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the illustrative embodiments described above.

[0122] It should also be understood that any reference to elements in this document using names such as “first,” “second,” etc., generally does not limit the number or order of those elements. Rather, these names may be used herein as a convenient means of distinguishing two or more elements or instances of elements. Therefore, a reference to the first and second elements does not imply that only two elements may be used, or that the first element must somehow precede the second element.

[0123] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, and symbols referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0124] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code containing instructions (which may be referred to herein as "software" or "software module"), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above in general terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation decisions will not depart from the scope of this disclosure.

[0125] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented within or executed 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 devices or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communicating with various components within a network or 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, such as a combination of a DSP and a microprocessor, multiple microprocessors, a combination of one or more microprocessors with a DSP core, or any other suitable configuration for performing the functions described herein.

[0126] If implemented as software, the functionality can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. A computer-readable medium includes both computer storage media and communication media, including any medium capable of enabling the transfer of a computer program or code from one place to another. A storage medium can be any available medium accessible to a computer. By way of example and not limitation, such a computer-readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and is accessible to a computer.

[0127] In this document, as used herein, the term "module" refers to software, firmware, hardware, and any combination of these elements used to perform the associated functions described herein. Furthermore, for the purposes of discussion, various modules are described as discrete modules; however, it will be apparent to those skilled in the art that two or more modules can be combined to form a single module that performs the associated functions according to embodiments of this solution.

[0128] Additionally, memory or other storage devices and communication components may be employed in embodiments of this solution. It should be understood that, for clarity, embodiments of this solution have been described above with reference to different functional units and processors. However, it will be apparent that any suitable functional distribution among different functional units, processing logic elements, or domains may be used without diminishing the effectiveness of this solution. For example, a function illustrated as being performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means of providing the described functionality and do not indicate a strict logical or physical structure or organization.

[0129] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can 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 accorded the widest scope consistent with the novel features and principles disclosed herein, as described in the claims.

Claims

1. A method comprising: The sequence length is determined by the wireless communication device; as well as The wireless communication device applies the sequence to the uplink transmission according to the sequence length.

2. The method according to claim 1, wherein, The uplink transmission includes at least one of the following: Multiple repetitions of Physical Uplink Shared Channel (PUSCH) transmissions scheduled by Downlink Control Information (DCI) signaling; Multiple repetitions of PUSCH transmissions scheduled by at least one of a Random Access Response (RAR) message or a Fallback RAR message; Multiple repetitions of PUSCH transmissions during random access; or Multiple repetitions of the configured authorized PUSCH transfer.

3. The method according to claim 1, wherein, Applying the sequence includes applying at least one sequence to one or more units in the uplink transmission, and The one or more units in the uplink transmission include at least one of the following: One or more repeating groups, Repeat once or multiple times, One or more time slots, One or more symbols, One or more resource elements (REs), or One or more resource blocks (RBs).

4. The method according to claim 1, wherein, The sequence includes at least one of the following: an orthogonal covering code (OCC) sequence, a non-orthogonal multiple access (NOMA) sequence, or a sequence based on a discrete Fourier transform (DFT) sequence, a Walsh sequence, a Zadov-Chu (ZC) sequence, or a Hadamard matrix or code.

5. The method according to claim 1, wherein, The sequence length refers to at least one of the following: Nominal sequence length; or Actual sequence length.

6. The method according to claim 5, wherein, The actual sequence length includes at least one of the following: The actual length of a sequence of orthogonal covering codes (OCC), nonorthogonal multiple access (NOMA), or sequences based on discrete Fourier transform (DFT), Walsh, Zadov-Chu (ZC), or Hadamard matrices or codes; The actual time-domain window (TDW) is used to apply the sequence or to multiplex uplink transmissions from multiple wireless communication devices. The sequence length calculated by the wireless communication device for the sequence; or The sequence length to be applied to uplink transmission.

7. The method according to claim 5, comprising: The actual sequence length of the sequence is determined by the wireless communication device based on at least one of the following: The actual TDW used for demodulation reference signal (DMRS) bundling, The nominal sequence length of the sequence. One or more events, Repeated configuration, or The capability report of the wireless communication device.

8. The method of claim 5, comprising at least one of the following: The wireless communication device transmits a capability report of the wireless communication device to the wireless communication node; The wireless communication device receives signaling for determining the nominal sequence length based on the capability report; or The actual sequence length of the sequence is determined by the wireless communication device.

9. The method according to claim 8, wherein, The capability report includes at least one of the following: An indication of the maximum duration, wherein the maximum duration is at least one of the following: The maximum duration during which the wireless communication device supports the application of the sequence, demodulation reference signal (DMRS) bundling, or multiplexing of uplink transmissions from multiple wireless communication devices; Values ​​for time slots, symbols, repetitions, or milliseconds (ms); Only applicable to non-terrestrial networks (NTN); Applicable to NTN or terrestrial networks (TN); or The maximum duration of at least one of the following was considered: phase precompensation capability, timing of timing advance (TA) precompensation update, or timing of antenna switching; Indications regarding whether TA pre-compensation updates are permitted within the actual sequence length, wherein at least one of the following is true: The wireless communication device reports the instruction; TA pre-compensation update is not considered when determining the actual sequence length; or The indication is combined with one or more defined capabilities for a maximum duration; or Instructions regarding whether phase continuity and / or power consistency can be maintained during TA pre-compensation updates.

10. The method of claim 7, comprising: The nominal sequence length of the sequence is determined by the wireless communication device as follows: Same as the number of repetitions; Same as the number of repeat groups; The same number of repetitions as within the repeating number; Based on sequence indexing; or Based on predefined or broadcast sequence pools or sequence sets.

11. The method according to claim 7, wherein, The one or more events include at least one of the following: Configured downlink time slots, reception timing, or monitoring timing; The occurrence of a gap exceeding a threshold between two consecutive Physical Uplink Shared Channel (PUSCH) transmissions; The occurrence of a gap with at least one scheduled uplink transmission and not exceeding a threshold; The defined discarding or cancellation of PUSCH transmissions; The dropping or cancellation of the defined Physical Uplink Control Channel (PUCCH) transmission; Different probe reference signal (SRS) resource sets are associated for two PUSCH transmissions of PUSCH repetition type A or B; The occurrence of uplink timing adjustments; Frequency hopping occurs; The occurrence of phase discontinuity; Inconsistent power output occurs; The occurrence of TA pre-compensation update; or Antenna switching occurs.

12. The method according to claim 7, wherein, The repeated configuration includes an indication of at least one of the following: The number of repetitions used for the uplink transmission; Number of repeating groups; The number of repetitions within a repeating group; Number of consecutive repetitions; or The number of repetitions of time-domain gaps that are less than the defined number of symbols or time slots.

13. The method of claim 7, comprising: The actual sequence length of the sequence is determined by the wireless communication device as follows: Based on at least one of the following: the maximum duration indicated by the capability report, or the subcarrier spacing (SCS) configuration of the uplink transmission; Based on the timing information updated according to TA pre-compensation; It begins at the first symbol of the first PUSCH transmission in the time slot used for PUSCH transmission within the nominal sequence length; The transmission ends at the last symbol of the last PUSCH transmission within the time slot used for PUSCH transmission within the nominal sequence length. It ends at the last symbol of the last PUSCH transmission preceding the one or more events mentioned above; It begins at the first symbol of the first PUSCH transmission following the one or more events; Same as the nominal sequence length; One or more times the nominal sequence length; The maximum value of the nominal sequence length and the number of repetitions indicated by the repetition configuration; Same as the actual TDW used for DMRS bundling; Minimum actual TDW used for DMRS bundling; or A portion of the nominal sequence length.

14. A method comprising: The wireless communication node receives uplink transmissions from the wireless communication device. The sequence, based on a sequence length determined by the wireless communication device, has been applied to the uplink transmission.

15. A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1-14.

16. An apparatus comprising: At least one processor is configured to perform the method according to any one of claims 1-14.

Images