Uplink transmission method and apparatus, and terminal

Abstract

The present application belongs to the technical field of communications. Disclosed are an uplink transmission method and apparatus, and a terminal. The uplink transmission method in the embodiments of the present application comprises: on the basis of a target orthogonal cover code (OCC) sequence, a terminal performing first uplink transmission within at least one target block, wherein the at least one target block is obtained by dividing a resource for the first uplink transmission according to a first length, and the first length is a resource length corresponding to one target block.

Description

Uplink transmission method, device and terminal

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202410578103.X, filed on May 10, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to an uplink transmission method, apparatus, and terminal. Background Technology

[0004] In non-terrestrial network (NTN) mobile communication systems, due to the large communication coverage area and the large number of terminals accessing the network simultaneously, and the fact that uplink transmission currently only supports single-layer transmission, the number of users that can reuse uplink transmission is limited, resulting in low system uplink capacity and poor uplink transmission performance. Summary of the Invention

[0005] This application provides an uplink transmission method, apparatus, and terminal that can increase the number of multiplexed users in uplink transmission, improve system uplink capacity, and solve the problem of poor uplink transmission performance.

[0006] Firstly, an uplink transmission method is provided, including:

[0007] The terminal performs a first uplink transmission based on the target orthogonal coverage code (OCC) sequence within at least one target block;

[0008] The at least one target block is obtained by dividing the resources of the first uplink transmission according to a first length, wherein the first length is the resource length corresponding to one target block.

[0009] Secondly, an uplink transmission device is provided, comprising:

[0010] The transmitting module is used to perform a first uplink transmission based on a target orthogonal coverage code (OCC) sequence within at least one target block;

[0011] The at least one target block is obtained by dividing the resources of the first uplink transmission according to a first length, wherein the first length is the resource length corresponding to one target block.

[0012] Thirdly, an uplink transmission device is provided, the device being configured to perform the steps of the method described in the first aspect.

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

[0014] Fifthly, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to perform a first uplink transmission based on a target orthogonal cover code (OCC) sequence within at least one target block;

[0015] The at least one target block is obtained by dividing the resources of the first uplink transmission according to a first length, wherein the first length is the resource length corresponding to one target block.

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

[0017] A seventh aspect provides a wireless communication system, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method described in the first aspect.

[0018] In a seventh aspect, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect.

[0019] Eighthly, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the method as described in the first aspect.

[0020] In this embodiment, the terminal performs a first uplink transmission based on a target orthogonal coverage code (OCC) sequence within at least one target block. The at least one target block is obtained by dividing the resources of the first uplink transmission according to a first length, where the first length is the resource length corresponding to one target block. Thus, OCC transmission of the first uplink transmission using an OCC sequence enables the reuse of transmission resources, increases the number of users reusing uplink transmission, and enhances the system's uplink capacity, thereby improving uplink transmission performance. Furthermore, by dividing the target block and allocating resources for OCC transmission, the transmission performance of OCC-based transmission can be improved. Attached Figure Description

[0021] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0022] Figure 2a is a schematic diagram of the relevant parameters of NPUSCH mapping in related technologies;

[0023] Figure 2b is a schematic diagram of a transmission method in a related technology;

[0024] Figure 2c is another transmission schematic diagram in the related technology;

[0025] Figure 2d is another transmission schematic diagram in the related technology;

[0026] Figure 2e is another transmission schematic diagram in the related technology;

[0027] Figure 2f is another transmission schematic diagram in the related technology;

[0028] Figure 2g is another transmission schematic diagram in the related technology;

[0029] Figure 2h is another schematic diagram of transmission in related technologies;

[0030] Figure 2i is another transmission schematic diagram in the related technology;

[0031] Figure 2j is another transmission schematic diagram in the related technology;

[0032] Figure 2k is another transmission schematic diagram in related technologies;

[0033] Figure 3 is a flowchart of an uplink transmission method provided in an embodiment of this application;

[0034] Figure 4 is a schematic diagram of the mapping relationship of the number of resource units of NPUSCH in related technologies;

[0035] Figure 5a is a schematic diagram of a transmission provided in an embodiment of this application;

[0036] Figure 5b is another transmission schematic diagram provided by an embodiment of this application;

[0037] Figure 6 is another transmission schematic diagram provided by an embodiment of this application;

[0038] Figure 7 is another transmission schematic diagram provided by an embodiment of this application;

[0039] Figure 8 is another transmission schematic diagram provided by an embodiment of this application;

[0040] Figure 9 is another transmission schematic diagram provided by an embodiment of this application;

[0041] Figure 10 is another transmission schematic diagram provided by an embodiment of this application;

[0042] Figure 11 is another transmission schematic diagram provided by an embodiment of this application;

[0043] Figure 12 is another transmission schematic diagram provided by an embodiment of this application;

[0044] Figure 13 is another transmission schematic diagram provided by an embodiment of this application;

[0045] Figure 14 is another transmission schematic diagram provided by an embodiment of this application;

[0046] Figure 15 is another transmission schematic diagram provided by an embodiment of this application;

[0047] Figure 16 is another transmission schematic diagram provided by an embodiment of this application;

[0048] Figure 17 is another transmission schematic diagram provided by an embodiment of this application;

[0049] Figure 18 is another transmission schematic diagram provided by an embodiment of this application;

[0050] Figure 19 is another transmission schematic diagram provided by an embodiment of this application;

[0051] Figure 20 is another transmission schematic diagram provided by an embodiment of this application;

[0052] Figure 21 is another transmission schematic diagram provided by an embodiment of this application;

[0053] Figure 22 is another transmission schematic diagram provided by an embodiment of this application;

[0054] Figure 23 is another transmission schematic diagram provided by an embodiment of this application;

[0055] Figure 24 is another transmission schematic diagram provided by an embodiment of this application;

[0056] Figure 25 is another transmission schematic diagram provided by an embodiment of this application;

[0057] Figure 26 is another transmission schematic diagram provided by an embodiment of this application;

[0058] Figure 27 is another transmission schematic diagram provided by an embodiment of this application;

[0059] Figure 28 is another transmission schematic diagram provided by an embodiment of this application;

[0060] Figure 29 is another transmission schematic diagram provided by an embodiment of this application;

[0061] Figure 30 is another transmission schematic diagram provided by an embodiment of this application;

[0062] Figure 31 is another transmission schematic diagram provided by an embodiment of this application;

[0063] Figure 32 is another transmission schematic diagram provided by an embodiment of this application;

[0064] Figure 33 is another transmission schematic diagram provided by an embodiment of this application;

[0065] Figure 34 is a schematic diagram of an uplink transmission device provided in an embodiment of this application;

[0066] Figure 35 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0067] Figure 36 is a schematic diagram of the structure of a terminal provided in an embodiment of this application. Detailed Implementation

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

[0069] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0070] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

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

[0072] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (WiFi) nodes, etc.The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0073] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. The core network functions include: BSF (Block Network Function), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), and Network Data Analytics Function (NWDAF). It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

[0074] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0075] For ease of understanding, the following explains some aspects of the embodiments of this application:

[0076] 1. R19 Internet of Things (IoT) Non-Terrestrial Network (NTN) Work Item Description (WID)

[0077] The specific scope of R19 NTN WID in terms of uplink capacity enhancement is as follows:

[0078] {

[0079] Support for uplink capacity enhancements;

[0080] This study investigates enhancement techniques for enabling multiple UE multiplexing in a single tone transmission with a subcarrier spacing of 3.75kHz or 15kHz in Narrowband Physical Uplink Shared Channel (NPUSCH) format 1 and Narrowband Physical Random Access Channel (NPRACH) [RAN1, RAN2] using orthogonal cover codes (OCC). The maximum number of multiplexed users supported is the minimum of the existing maximum allowed by uplink (UL) and downlink (DL) signaling and 4. If beneficial, this enhancement technique should be standardized.

[0081] Multi-tone support for 15kHz SCS should also be considered.

[0082] Note: The impact of actual hardware non-ideal factors should be taken into account.

[0083] }

[0084] As can be seen from the above description, the main research content of R19 NTN uplink capacity enhancement in the direction of IoT NTN focuses on using OCC for transmission of Narrowband Physical Uplink Shared Channel (NPUSCH) and Narrowband Physical Random Access Channel (NPRACH).

[0085] 2. NPUSCH

[0086] NB-IoT uses Single Carrier Frequency Division Multiple Access (SC-FDMA) in the uplink and supports both multi-tone and single-tone transmission.

[0087] Multi-tone transmission uses a 15kHz subcarrier spacing and a slot length of 0.5ms.

[0088] Single-tone transmission supports two subcarrier spacings: 15kHz and 3.75kHz. The 15kHz subcarrier is equivalent to the 15kHz subcarrier in LTE, with a slot length of 0.5ms, and provides consistent performance with LTE uplink. The 3.75kHz subcarrier has a symbol length four times that of the 15kHz subcarrier, with a slot length of 2ms. In this case, a system frame (10ms) contains 5 slots.

[0089] Single-tone transmission uses only one subcarrier in the frequency domain, while multi-tone transmission uses multiple subcarriers. Unlike LTE, NB-IoT does not define the concept of Resource Blocks (RBs) in the uplink. In the frequency domain, when the subcarrier spacing used in the uplink is 15kHz, it contains 12 consecutive subcarriers; when the subcarrier spacing used in the uplink is 3.75kHz, it contains 48 consecutive subcarriers.

[0090] A resource element (RE) is the smallest physical resource unit in NB-IoT. One RE can store one modulation symbol, which can be modulated using either Binary Phase Shift Keying (BPSK) (one RE stores 1 bit of data) or Quadrature Phase Shift Keying (QPSK) (one RE stores 2 bits of data).

[0091] NPUSCH supports two formats:

[0092] NPUSCH format 1: Used for transmitting Uplink Shared Channel (UL-SCH) data;

[0093] NPUSCH format 2: Used for transmitting uplink control information (UCI).

[0094] 3. Resource Unit (RU)

[0095] The basic unit for uplink scheduling and Hybrid Automatic Repeat reQuest (HARQ) message transmission is the Resource Unit (RU). The RU describes how NPUSCHs are mapped to REs. An RU in the time domain consists of... It consists of consecutive SC-FDMA symbols, and in the frequency domain it is composed of... It consists of consecutive subcarriers. and The definition is shown in Figure 2a.

[0096] The time-frequency resources occupied by an uplink RU are shown in the table below:

[0097] 4. Narrowband Demodulation Reference Signal (NDMRS)

[0098] The Narrowband Demodulation Reference Signal (NDMRS) is primarily used for uplink physical channel estimation to ensure correct decoding of the NPUSCH. The uplink-defined NDMRS is transmitted multiplexed with the data; therefore, NDMRS is only transmitted on RUs containing data transmission data. NB-IoT does not support multi-antenna transmission in the uplink; all uplink transmissions use a single antenna port.

[0099] For NPUSCH format 1, if a subcarrier spacing of 3.75 kHz is used, NDMRS is transmitted on the 5th SC-FDMA symbol (l=4) of each slot; if a subcarrier spacing of 15 kHz is used, NDMRS is transmitted on the 4th SC-FDMA symbol (l=3) of each slot. As shown in Figure 2b.

[0100] For NPUSCH format 2, if a subcarrier spacing of 3.75 kHz is used, NDMRS is transmitted on the first three SC-FDMA symbols (l = 0, 1, 2) of each slot; if a subcarrier spacing of 15 kHz is used, NDMRS is transmitted on the middle three SC-FDMA symbols (l = 2, 3, 4) of each slot, as shown in Figure 2c.

[0101] 5. Identify the Redundancy Version (RV)

[0102] NPUSCH in A series of consecutive NB-IoT uplink slot transmissions, one of which requires an uplink transport block (TB) to occupy There are N uplink slots. Rep indivual Divided into Each copy has an index of 1 copy. And each contains A consecutive NB-IoT uplink slot (if) Then L = 1; otherwise The index of the B consecutive NB-IoT uplink slots contained in the j-th segment is n. i And i = jB + b, b = 0, 1, ..., B-1. The redundant version used in the j-th copy is rv. idx (j) = 2 * mod(rv) DCI +j,2). It can be seen that the redundant version rv of NPUSCH format 1 transmission can only be 0 or 2.

[0103] 6. Physical layer mapping

[0104] When mapping NPUSCH to RE, the mapping is performed in the order of frequency domain first, then time domain. The modulated symbols are mapped to N... slots After each slot, these N will be... slots The slot continues to repeat. Then continue mapping the next N. slots One slot, then repeat. Next, until Until all slots are mapped (here) That is, N Rep ).

[0105] in,

[0106] It can be seen that when using a 3.75kHz subcarrier spacing, repetition is based on one slot; when using a 15kHz subcarrier spacing, repetition is based on one subframe (2 slots).

[0107] For example, the values ​​of each parameter are shown in the table below:

[0108] The transmission under different tones is shown in Figure 2d.

[0109] 7. Example of an OCC scheme based on NPUSCH

[0110] The following uses a 15kHz SCS. N rep =16,N RU Taking 1 as an example, we will illustrate some OCC schemes, and the OCC sequence used is represented by [w0, w1].

[0111] Figure 2e shows the result when OCC is not used.

[0112] An example of using Inter-RV OCC is shown in Figure 2f.

[0113] An example of using Inter-repetition OCC is shown in Figure 2g.

[0114] An example of using inter-slot OCC is shown in Figure 2h.

[0115] Another example of using Inter-slot OCC is shown in Figure 2i.

[0116] An example of using Inter-symbol OCC is shown in Figure 2j.

[0117] An example of using Intra-symbol OCC is shown in Figure 2k.

[0118] 8. OCC sequence

[0119] In the existing NR protocol, some OCC sequences have been standardized, such as:

[0120] The OCC sequences used in Physical Uplink Control Channel (PUCCH) format 1 transmissions are shown in the table below:

[0121] The table above shows the orthogonal sequences of PUCCH format 1.

[0122] The OCC sequence used in block-wise spreading transmission of PUCCH format 4 is shown in the table below:

[0123] The table above shows the current situation. At the same time, orthogonal sequences of PUCCH format 3 and PUCCH format 4 with interlaced mapping w n (m).

[0124] The table above shows the current situation. At the same time, orthogonal sequences of PUCCH format 3 and PUCCH format 4 with interlaced mapping w n (m).

[0125] The uplink transmission method, apparatus, and related equipment provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0126] Referring to Figure 3, which is a flowchart of an uplink transmission method provided in an embodiment of this application, the uplink transmission method includes the following steps:

[0127] Step 101: The terminal performs a first uplink transmission based on the target orthogonal overlay code (OCC) sequence within at least one target block;

[0128] The at least one target block is obtained by dividing the resources of the first uplink transmission according to a first length, wherein the first length is the resource length corresponding to one target block.

[0129] The first uplink transmission may include Physical Uplink Control Channel (PUCCH) transmission, Physical Uplink Shared Channel (PUSCH) transmission, Narrowband Physical Uplink Shared Channel (NPUSCH) transmission, or Narrowband Physical Random Access Channel (NPRACH), etc. This embodiment does not limit the specific transmission.

[0130] In addition, the terminal performing a first uplink transmission based on a target OCC sequence within at least one target block can be understood or replaced as the terminal performing OCC transmission based on a target OCC sequence within at least one target block.

[0131] In this context, "target block" is merely a designation, representing a set of resources in the time or frequency domain for the uplink transmission. It can also be described as a block, an OCC block, a multiplexed block, a resource set, or a multiplexed resource block, etc. A target block can be understood as a set of time or frequency domain resources used to multiply the target OCC sequence during OCC transmission.

[0132] In addition, the resource length of the first uplink transmission can be divided into one or more target blocks with a first length.

[0133] The first length can be directly indicated by the first indication information sent by the network-side device, or determined by transmission-related parameters or OCC transmission configuration parameters. The transmission-related parameters may include N. slots M identical The number of SCs or B values ​​in the scheduling, etc., N slots M represents the number of time slots determined based on the subcarrier spacing. identical Based on and N Rep The determined number of repetitions (i.e., the aforementioned) The superscript NPUSCH is omitted here. L is based on Determined coefficients (equal to M) identical ), N RU The number of RUs required to transmit one TB. The number of time slots occupied by a RU. N represents the number of SCs occupied by a RU. Rep N represents the number of repetitions.Rep Equivalent to N rep NPUSCH in A continuous NB-IoT uplink slot transmission, one TB needs to occupy One uplink slot. Put N Rep indivual Divided into Each copy has an index of 1 copy. And each portion contains B= A consecutive NB-IoT uplink slot (if) Then L = 1; otherwise Configuration parameters for OCC transfers can include the block granularity of the target block or the OCC length, etc.

[0134] In one implementation, the duration of the first uplink transmission is divided into one or more target blocks according to a first length; the first uplink transmission performs OCC transmission within one or more target blocks. A target block is merely a designation and may also be referred to as an OCC group or other names, used to represent the time-domain / frequency-domain resource set multiplied by a defined OCC sequence when performing OCC transmission.

[0135] In one embodiment, the first length can be indicated by a first signaling (at least one of System Information Block (SIB), Radio Resource Control (RRC), Downlink Control Information (DCI), and Medium Access Control (MAC) Control Element (CE)), including at least one of the following:

[0136] Multiple sub-carriers (SC); one or more RBs; multiple OFDM symbols; one or more time slots; one or more repetitions; one or more RUs; one or more milliseconds.

[0137] In one implementation, the first length can be determined by an implicit rule or protocol agreement of a first parameter indicated by a second signaling, including at least one of the following:

[0138] The first length equals the total number of transmission occasions (e.g., for TBoMS, it is N*K slots, where N is the number of slots occupied by one TB and K is the number of repetitions; for repetition type A or type B, it is the total number of repetitions), which can be understood as the entire transmission duration.

[0139] The first length is equal to N. slots (Existing parameters) number of time slots;

[0140] The first length is equal to M identical (Existing parameters) times;

[0141] The first length is equal to N. slots *M identical One time slot;

[0142] The first length is equal to the block granularity of the target block * OCC length;

[0143] The first length is equal to the number of SCs (sub-carriers) scheduled;

[0144] The first length equals one time slot (if) Then L = 1; otherwise ).

[0145] In one implementation, the block granularity of the target block is determined by at least one of OCC type and OCC length; or, the OCC type is determined by at least one of the target block granularity and OCC length; or, the OCC length is determined by the target block granularity and OCC type. The block granularity of the target block refers to the size of the time-domain or frequency-domain resource determined during OCC transmission and multiplied by the corresponding OCC code (an element in the sequence). The block granularity of the target block can also be described as block granularity, OCC block granularity, multiplexed block granularity, resource set granularity, or multiplexed resource block granularity, etc.

[0146] In one implementation, the OCC sequence used in the first uplink transmission is either agreed upon by the protocol, flexibly configured by the network, or determined based on the OCC length.

[0147] In one implementation, the RV used for the first uplink transmission can be determined based on the identifier of the target block (such as a sequence number).

[0148] Taking time-domain OCC transmission as an example, with the target block being an OCC block, the duration of the first uplink transmission is divided into one or more OCC blocks based on a first length;

[0149] The first uplink transmission performs OCC transmission within one or more OCC blocks; the first length is used to indicate the length of an OCC block. OCC block is only a name and may also be called OCC group or other names. It is mainly used to represent the set of time-domain or frequency-domain resources in which the target OCC sequence operates during OCC transmission.

[0150] It should be noted that the above-mentioned OCC transmission may be only in the time domain, or only in the frequency domain, or it may be both time-domain OCC and frequency-domain OCC. In this case, the processes of determining the first length, determining the OCC granularity, and determining the OCC type can all be determined independently in the time domain and frequency domain respectively.

[0151] In related technologies, under NTN scenarios, due to the large coverage area and potentially large number of simultaneous users, it is necessary to enhance the uplink channel capacity to improve system capacity and uplink user multiplexing capabilities. Furthermore, in NTN scenarios, the uplink shared channel only supports single-layer transmission; therefore, introducing an OCC (orthogonal cover codes) transmission scheme can be considered to enhance the uplink shared channel capacity.

[0152] The transmission symbols and RVs used in OCC transmission on the uplink shared channel need to be consistent, and mapping rules may even need to be modified to ensure this. This affects the allocation of time-frequency resources in the uplink shared channel itself. This application proposes a method for using OCC transmission on the physical uplink shared channel. By introducing an OCC block mechanism, the time-frequency resources for OCC application are allocated to coordinate with existing time-frequency resource allocation, thus enabling OCC transmission. For example, using slot-level OCC, different time slots using the same OCC sequence are mapped to the same transmission symbols; similarly, using symbol-level OCC, different OFDM symbols using the same OCC sequence are mapped to the same transmission symbols. For NPUSCH transmission in IoT NTN scenarios, existing protocols have some repetitive transmission interleaving operations, and the determination of RVs also involves some allocation of time-domain resources. This application coordinates the modification of mapping rules caused by OCC transmission with the allocation of existing time-frequency domain resources to ensure that the uplink shared channel can use OCC for transmission.

[0153] It should be noted that the upload transmission method in this application embodiment can be applied to IoT NTN scenarios, but is not limited to IoT NTN scenarios. This application embodiment is applicable not only to LTE NB-IoT or IoT NTN systems, but also to NR NTN systems. Furthermore, this application embodiment is not limited to NTN scenarios; it is equally applicable to TN scenarios.

[0154] In this embodiment, the terminal performs a first uplink transmission based on a target orthogonal coverage code (OCC) sequence within at least one target block. The at least one target block is obtained by dividing the resources of the first uplink transmission according to a first length, where the first length is the resource length corresponding to one target block. Thus, OCC transmission of the first uplink transmission using an OCC sequence enables the reuse of transmission resources, increases the number of users reusing uplink transmission, and enhances the system's uplink capacity, thereby improving uplink transmission performance. Furthermore, by dividing the target block and allocating resources for OCC transmission, the transmission performance of OCC-based transmission can be improved.

[0155] Optionally, the first length is at least one of the following indicated by the first indication information sent by the network-side device:

[0156] At least one subcarrier (SC); at least one resource element (RE); at least one resource block (RB); at least one orthogonal frequency division multiplexing (OFDM) symbol; at least one time slot; at least one repetition; at least one resource unit (RU); at least one millisecond.

[0157] The first indication information may be carried in the first signaling, and the first length may be explicitly indicated by the first signaling (at least one of System Message Block SIB, RRC, DCI, and MAC CE), including at least one of the following:

[0158] Multiple SCs (in IoT NTN scenarios); multiple REs (in NR NTN scenarios); one or more RBs; multiple OFDM symbols; one or more time slots; one or more repetitions; one or more RUs; one or more milliseconds.

[0159] In one implementation, when the first length is at least one repeated repetition (i.e., repetition-level OCC) indicated by the first indication information sent by the network-side device, the first length is <= M. identical Repeated time. (Through M) identical The value of is restricted, limiting the value of the first length, so that a target block is divided within M. identical Within each repetition, avoid making the resource span of a target block too large.

[0160] In one implementation, if the first length is at least one repeated repetition (i.e., repetition-level OCC) indicated by the first indication information sent by the network-side device, then... The mapping rules can then be modified to satisfy the OCC transmission of the first length indicated by the first indication information, thereby avoiding the problem caused by... The limitations result in a target block having too large a resource span; or, it can be modified. The value of is the same as in the case of multi-Tone, that is... To make single-tone It can be greater than 1.

[0161] In one implementation, when the first length is at least one Resource Unit (RU) (i.e., RU-level OCC) indicated by the first indication information sent by the network-side device, the existing rules for determining the RV can be modified, for example: the redundant version used for the j-th part is... (if Then L = 1; otherwise This allows two adjacent Resource Containers (RVs) to be the same, thus reducing the resource span of the target block when partitioning it.

[0162] In this embodiment, the terminal can determine the first length through the first indication information sent by the network-side device, and divide the resources of the first uplink transmission into at least one target block according to the first length, thereby enabling the division of resources for OCC application to realize OCC transmission and improving the transmission effect of OCC application.

[0163] Optionally, the first indication information carries at least one of the following:

[0164] System Information Block (SIB), Radio Resource Control (RRC), Downlink Control Information (DCI), and Medium Access Control (MAC) Control Element (CE).

[0165] The value of the first length can be indicated by SIB, RRC, DCI, or MAC CE. The DCI can be the DCI that schedules the first uplink transmission. The value of the first length can be indicated by the relevant field of the OCC configuration added in the DCI, or the existing DCI field can be reused to indicate the value of the first length.

[0166] Optionally, the first indication information is carried in SIB or RRC, and the first indication information includes a set of values ​​for the first length;

[0167] If the set of values ​​includes a single value, then the value in the set of values ​​is the first length; or

[0168] When the set of values ​​includes at least two values, the first length is the value in the set of values ​​indicated by DCI or MAC CE.

[0169] In one embodiment, the first length can be indicated by a first signaling (at least one of System Message Block (SIB), RRC, DCI, MAC CE), and the indication method includes at least one of the following:

[0170] (1) Configure the set of values ​​of the first length via SIB or RRC;

[0171] If only one value is configured in the set, then that value is determined to be the value of the first length;

[0172] If the set contains more than one value, then a specific value in the set is further indicated by DCI or MAC CE to determine the value of the first length.

[0173] (2) DCI or MAC CE indicates the value of the first length;

[0174] The aforementioned DCI can be the DCI that schedules the first uplink transmission. The value of the first length can be indicated by the relevant field of the newly added OCC configuration in the DCI, or the value of the first length can be indicated by reusing the existing DCI field.

[0175] Optionally, the first length is determined based on second indication information sent by the network-side device, the second indication information indicating at least one of the following:

[0176] OCC type, OCC length, number of multiplexed user equipment (UE) units, target OCC sequence, OCC index, number of repetitions, RU index indication, SC indication, and transmission duration.

[0177] The second indication information can be used to indicate a first parameter, which includes at least one of the following: OCC type, OCC length, number of multiplexed user equipment (UEs), target OCC sequence, OCC index, number of repetitions, RU index indication, SC indication, and transmission duration. Different first parameters can correspond to different first lengths, and the association between the first length and the first parameter can be configured by the network-side equipment or predefined by the protocol. The terminal can determine the first length through the first parameter and the association between the first length and the first parameter.

[0178] In one embodiment, the second indication information is carried in the second signaling, and the first parameter indicated by the second indication information includes at least one of the following:

[0179] OCC type, OCC length, number of multiplexed UEs, target OCC sequence, OCC index, number of repetitions, RU index indicator, SC indicator (I_SC, which can determine N_SC and SC position), and transmission duration.

[0180] In this embodiment, the terminal can determine the first length through the second indication information sent by the network-side device, and divide the resources of the first uplink transmission into at least one target block according to the first length, thereby enabling the division of resources for OCC application to realize OCC transmission and improving the transmission effect of OCC application.

[0181] Optionally, the first length is equal to the total number of transmission opportunities; or

[0182] The first length is equal to N slots One time slot; or

[0183] The first length is equal to M identical Repeat; or

[0184] The first length is equal to N slots ×M identical One time slot; or

[0185] The first length is equal to the product of the target block's granularity and the OCC length; or

[0186] The first length is equal to the number of scheduled SCs; or

[0187] The first length is equal to B time slots;

[0188] Where, N slots M represents the number of time slots determined based on the subcarrier spacing. identical Based on and N Rep A fixed number of repetitions, L is based on Determined coefficients, N RU The number of RUs required to transmit one TB. The number of time slots occupied by a RU. N represents the number of SCs occupied by a RU. Rep This represents the number of repetitions.

[0189] The value of L can be related to M. identical The values ​​of N are the same. slotsFor existing parameters, Δf is the subcarrier spacing. M identical For the existing parameters, M identical and Equivalent, N Rep B is an existing parameter. For L, if Then L = 1; otherwise

[0190] In one implementation, when the first length is determined based on the second indication information sent by the network-side device, the first length is equal to the total number of transmission opportunities; or

[0191] The first length is equal to N slots One time slot; or

[0192] The first length is equal to M identical Repeat; or

[0193] The first length is equal to N slots ×M identical One time slot; or

[0194] The first length is equal to the product of the target block's granularity and the OCC length; or

[0195] The first length is equal to the number of scheduled SCs; or

[0196] The first length is equal to B time slots.

[0197] In one implementation, the second indication information may be carried in the second signaling, and the first length may be determined by an implicit rule or protocol agreement based on the first parameter indicated by the second signaling, including at least one of the following:

[0198] The first length is equal to the total number of transmission occasions (e.g., for TBoMS, it is N*K slots, where N is the number of slots occupied by one TB and K is the number of repetitions; for repetition type A or type B, it is the total number of repetitions), which can be understood as the entire transmission duration.

[0199] The first length is equal to N. slots (Existing parameters) number of time slots;

[0200] The first length is equal to M identical (Existing parameters) times;

[0201] The first length is equal to N. slots *M identical One time slot;

[0202] The first length is equal to the block granularity of the target block * OCC length;

[0203] The first length is equal to the number of SCs (sub-carriers) scheduled;

[0204] The first length equals one time slot (if) Then L = 1; otherwise ).

[0205] In this embodiment, the terminal divides the resources of the first uplink transmission into at least one target block according to the first length, which can coordinate with the existing time and frequency resource allocation to realize OCC transmission and improve the transmission effect of OCC transmission.

[0206] Optionally, before the terminal performs a first uplink transmission based on a target OCC sequence within at least one target block, the method further includes:

[0207] The terminal determines the block granularity of the target block, which is the size of the resource in the target block multiplied by an element corresponding to the target OCC sequence.

[0208] In this embodiment, by determining the block granularity of the target block, the size of the resource corresponding to the element multiplied by the target OCC sequence during OCC transmission can be determined, thereby realizing resource mapping.

[0209] Optionally, the block granularity of the target block is determined based on at least one of OCC type and OCC length; or, the block granularity of the target block is indicated based on third indication information sent by the network-side device.

[0210] The third indication information can be carried in the first signaling, and the block granularity of the target block can be indicated by the first signaling. The first signaling simultaneously indicates the first length and the block granularity of the target block.

[0211] In addition, the OCC type or OCC length can be associated with the first uplink transmission, and the network-side device can configure the OCC type or OCC length for the terminal for the first uplink transmission.

[0212] Optionally, when the OCC type is an OCC associated with an OFDM symbol, the block granularity of the target block is 1 SC, 2 SCs, 3 SCs, 4 SCs, or 6 SCs;

[0213] or

[0214] When the OCC type is an OCC associated with multiple OFDM symbols, the block granularity of the target block is 1 OFDM symbol, or 1 symbol group, or the block granularity of the target block is the quotient of a first difference and the OCC length, where the first difference is the difference between the number of time-domain symbols in Time Domain Resource Assignment (TDRA) and the number of DMRS symbols.

[0215] or

[0216] When the OCC type is a slot-associated OCC, the block granularity of the target block is 1 slot or N. slots One time slot;

[0217] or

[0218] When the OCC type is an OCC associated with the number of repetitions, the block granularity of the target block is 1 repetition or N. slots Time slot;

[0219] or

[0220] When the OCC type is an OCC associated with a redundant version RV, the block granularity of the target block is N. slots ×M identical One time slot, or B time slots;

[0221] Where, N slots M represents the number of time slots determined based on the subcarrier spacing. identical Based on and N Rep A fixed number of repetitions, L is based on Determined coefficients, N RU The number of RUs required to transmit one TB. The number of time slots occupied by a RU. N represents the number of SCs occupied by a RU. Rep This represents the number of repetitions.

[0222] Specifically, the OCC type associated with one OFDM symbol can refer to intra-symbol OCC (i.e., OCC performed on frequency domain resources within one OFDM symbol). The OCC type associated with multiple OFDM symbols can refer to symbol-level OCC (including inter-symbol OCC, cross-symbol OCC, and inter-symbol group OCC). The OCC type associated with a time slot can refer to slot-level OCC (including inter-slot OCC, cross-slot OCC, and inter-slot group OCC). The OCC type associated with the number of repetitions can refer to a repetition-level OCC (including inter-repetition OCC, cross-repetition OCC, and inter-repetition group OCC). The OCC type associated with the redundant version (RV) can refer to an RV-level OCC (including inter-RV OCC, slot group OCC using the same RV, or repetition group OCC using the same RV, etc.).

[0223] In one embodiment, the block granularity of the target block is determined by at least one of OCC type and OCC length, including at least one of the following:

[0224] (1) When the OCC type is intra-symbol OCC (i.e., OCC is performed on frequency domain resources within an OFDM symbol), the block granularity of the target block can be 1SC, 2SCs, 3SCs, 4SCs, or 6SCs. For example, for a 6-Tone case, if the OCC length is 2, the block granularity of the target block is 3SCs; for a 12-Tone case, if the OCC length is 2, the block granularity of the target block is 6SCs; if the OCC length is 4, the block granularity of the target block is 3SCs; if the OCC length is 6, the block granularity of the target block is 2SCs; and so on.

[0225] (2) When the OCC type is symbol-level OCC (including inter-symbol OCC / across symbol OCC / inter-symbol group OCC), the block granularity of the target block is 1 OFDM symbol or 1 symbol group (containing multiple OFDM symbols); or the number of time-domain symbols allocated by TDRA minus the number of DMRS symbols and then divided by the OCC length to obtain a symbol group, corresponding to the block granularity of the target block, i.e. (TDRA allocated symbols - DMRS symbols) / OCC length (TDRA allocated symbols - DMRS symbols) / OCC length.

[0226] (3) When the OCC type is slot-level OCC (including inter-slot OCC / across-slot OCC / inter-slot group OCC), the block granularity of the target block is 1 slot or N. slots Each time slot.

[0227] (4) When the OCC type is repetition-level OCC (including inter-repetition OCC, cross-repetition OCC, and inter-repetition group OCC), the block granularity of the target block is 1 repetition or N. slots Time slot.

[0228] (5) When the OCC type is RV-level OCC (including inter-RV OCC, slot group OCC using the same RV, or repetition group OCC using the same RV, etc.), the block granularity of the target block is N. slots *M identical a time slot, or a time slot (if Then L = 1; otherwise ).

[0229] Optionally, when the block granularity of the target block is indicated based on third indication information sent by the network-side device, the method further includes:

[0230] The terminal determines the OCC type of the target block based on the block granularity of the target block, and the OCC type is associated with the block granularity of the target block.

[0231] The OCC type of the target block can be determined by the block granularity of the target block, and the mapping relationship between the block granularity of the target block and the OCC type can be agreed upon by the protocol.

[0232] For example, the set of block granularity of the target block is {6SCs, 1symbol, 1slot, N}. slots slots, If repetitions} (or a subset of this set) is used, then it means:

[0233] If the network-side device indicates that the block granularity of the target block is 6SCs, it means that the OCC type is intra-symbol / within asymbol OCC.

[0234] If the network-side device indicates that the block granularity of the target block is 1 symbol, it means that the OCC type is inter-symbol / across-symbol OCC.

[0235] If the network-side device indicates that the block granularity of the target block is 1 slot, it means that the OCC type is inter-slot / across-slot OCC.

[0236] If the network-side device indicates that the block granularity of the target block is N slots slots indicate that the OCC type is inter-repetition / across-repetition OCC;

[0237] If the network-side device indicates that the block granularity of the target block is Repetitions indicates that the OCC type is inter-RV / across-RV OCC.

[0238] In this embodiment, the terminal determines the OCC type of the target block based on the block granularity of the target block, thereby enabling it to determine the first length for dividing the target block or the OCC sequence for OCC transmission through the OCC type.

[0239] Optionally, if the block granularity of the target block is greater than or equal to one time slot, the DMRS within each time slot uses the same target OCC sequence as the data portion for OCC transmission.

[0240] In one implementation, if the block granularity of the target block is greater than or equal to one time slot (or the OCC type is slot-level OCC, repetition-level OCC, or RV-level OCC), then the DMRS in each time slot uses the same OCC code as the data portion.

[0241] Optionally, the target OCC sequence is based on a protocol agreement; or, the target OCC sequence is based on an indication from a network-side device; or, the target OCC sequence is determined based on the OCC length.

[0242] The OCC length can be associated with the first uplink transmission, and the network-side device can configure the OCC length for the first uplink transmission for the terminal.

[0243] The first uplink transmission performs OCC transmission within one or more target blocks, and the target OCC sequence used within the target block is determined by at least one of the following:

[0244] (1) The OCC sequence used by the protocol, such as a Walsh code-based OCC sequence from existing protocols: w i (m) = ej2πφ(m) / OCC_length, as shown in the table below:

[0245] DFT code based OCC sequence:

[0246] When the OCC length is equal to 2, use the OCC sequence shown in the table below: w n (m):

[0247] When the OCC length is equal to 4, use the OCC sequence shown in the table below: w n (m):

[0248] It could also be other target OCC sequences, such as PN sequences.

[0249] (2) The network can be flexibly configured to use the OCC sequence, such as supporting Walsh code based OCC sequence and DFT code based OCC sequence, and the network can instruct to use one of the two.

[0250] (3) Determine the OCC sequence to use based on the OCC length. For example, if the OCC length is less than or equal to 4, use the Walsh code based OCC sequence; and if the OCC length is greater than 4, use the DFT code based OCC sequence.

[0251] Optionally, before the terminal performs a first uplink transmission based on a target OCC sequence within at least one target block, the method further includes:

[0252] The terminal determines the target RV used for the first uplink transmission;

[0253] The target RV is determined based on the identifier of the target block, or the target RV is a preset RV.

[0254] Wherein, the first uplink transmission performs OCC transmission within one or more target blocks, and the method for determining the RV (i.e., target RV) used by different target blocks includes at least one of the following:

[0255] (1) Determine the RV to be used based on the identifier of the target block (such as the OCC block number);

[0256] For example, in NR systems, the OCC block number is used instead of the nth transmission timing or the nth actual repetition (n th transmission occasion or n th (actual repetition), meaning the RV sequence is configured as [0 2 3 1]. Assuming RV_id = 0, if the OCC block number modulo 4 equals 0, then RV0 is used; if the OCC block number modulo 4 equals 1, then RV2 is used; if the OCC block number modulo 4 equals 2, then RV3 is used; if the OCC block number modulo 4 equals 3, then RV1 is used; and so on. The redundant versions of PUSCH transmission are shown in the table below:

[0257] Among them, rv id The DCI indicating the PUSCH scheduling means that the rv is indicated by the DCI scheduling the PUSCH. id .

[0258] (2) RV0 is used in a fixed manner;

[0259] (3) Reuse existing mechanisms, such as the IoT system continuing to reuse the RV determination method in related technologies; for example, the NR system continuing to determine the RV used by indexing repetition / actual repetition / transmission occasion.

[0260] In this embodiment, the terminal determines the target RV used for the first uplink transmission, thereby enabling OCC transmission of the first uplink transmission based on the target RV.

[0261] Optionally, the resource duration of the first uplink transmission is determined based on the OCC length.

[0262] In one implementation, during the OCC transmission of the first uplink transmission, the final actual resource duration can be determined based on the resource length * OCC length determined by the configured or scheduled TDRA.

[0263] In one implementation, taking time-domain OCC transmission as an example, the first uplink transmission performs OCC transmission, and the time-domain resource duration of the first uplink transmission can be determined by the OCC length. For example, if 4 repetitions occupy 4 slots, using OCC transmission with an OCC length of 2 means that the first uplink transmission needs to occupy a duration of 4 slots * 2 = 8 slots.

[0264] It should be noted that, for slot-level OCC, when performing OCC transmission without modifying the existing RU partitioning, the number of available time slots within a TB mapped to a single RU may decrease exponentially with the OCC length. In one implementation, the time-domain resource duration of the first uplink transmission can be multiplied by the OCC length. For example, the time-domain resource duration can be increased by modifying the RU number mapping relationship, such as the actual number of RUs being the number of RUs indicated by the network side multiplied by the OCC length; or by configuring a multiplied number of repetitions.

[0265] In related technologies, when scheduling NPUSCH transmissions, I RU This will be indicated in the scheduling or configuration information, and the corresponding N can be obtained through the mapping relationship shown in Figure 4. RU In this embodiment of the application, the actual number of RUs (i.e., N) is determined. RU When using OCC for transmission, the actual number of RUs is the number of RUs indicated by the network side multiplied by the OCC length. In other words, when using OCC for transmission, N is no longer determined according to the mapping relationship shown in Figure 4. RU Instead, it is based on the number of RUs indicated by the network side (i.e., I... RUThe N is determined by the OCC length and the OCC length. RU Example: I RU =0, then N RU = 1 * OCC length, final N RU Equals 2, 4, ...; I RU =1, then N RU = 2 * OCC length, final N RU Equal to 4, 8, ... and so on. The network side (such as base stations) must ensure that the actual number of RUs does not exceed 10 during scheduling. Figure 4 shows the number of resource units (N) in an NPUSCH. RU (Number of resource units (N)) RU A schematic diagram of the mapping relationship for NPUSCH.

[0266] Optionally, when the first uplink transmission is a segmented transmission, the target block is less than or equal to the first transmission segment, which is any one of the multiple segments of the first uplink transmission; or, the first transmission segment includes one or more of the target blocks; or, the terminal expects to be configured with the same segmented configuration as the object performing the OCC transmission.

[0267] The statement that the terminal expects to be configured with the same segment configuration as the object performing OCC transmission can be understood or replaced as meaning that the terminal does not expect to be configured with a different segment configuration than the object performing OCC transmission.

[0268] It should be noted that NPUSCH transmission in IoT NTN scenarios involves segmented transmission. This means that continuous uplink transmission may be segmented into per-segment transmissions. Since uplink synchronization cannot be maintained for extended periods in NTN scenarios, some timing or frequency pre-compensation may be necessary to maintain uplink synchronization. The segment length can be {2, 4, 8, 16, 32, 64, 128, 256} ms, and there is a pre-compensation gap between segments to perform pre-compensation, with values ​​of {1 symbol, 1 slot, 2 slots}.

[0269] In one implementation, the target block is less than or equal to a segment, meaning the target block does not span segments.

[0270] In one implementation, a segment may include one or more target blocks.

[0271] In one implementation, users performing OCC transmissions do not expect to be configured with different segment configurations, such as segment length or pre-compensation gap.

[0272] Taking the target block as an OCC block as an example, the uplink transmission method of the embodiments of this application will be further explained through several example groups:

[0273] Example group 1:

[0274] In some embodiments, the network (i.e., the network-side device) configures or schedules a first uplink transmission, performs 4 repetitions of transmission, and performs OCC transmission. If the first length indicated by the network is 2 repetitions, the first uplink transmission is divided into an OCC block for every 2 repetitions, for a total of 2 OCC blocks, as shown in Figure 5a.

[0275] In some embodiments, the network configures or schedules a first uplink transmission with a transmission duration of 4 slots for OCC transmission. If the first length indicated by the network is 2 slots, the first uplink transmission is divided into an OCC block every 2 slots, for a total of 2 OCC blocks, as shown in Figure 5b.

[0276] In some embodiments, the network configures or schedules the first uplink transmission to occupy 1RB = 12SCs in the frequency domain for OCC transmission. If the first length indicated by the network is 6SCs, the first uplink transmission is divided into an OCC block every 6SCs, for a total of 2 OCC blocks, as shown in Figure 6.

[0277] In some embodiments, the network configures or schedules the first uplink transmission (NPUSCH single Tone, 15kHz SCS case), which occupies 1 subcarrier in the frequency domain and is scheduled as 1RU in the time domain (lasting 16 slots in the time domain), repeating twice, and performs OCC transmission. If the first length indicated by the network is 1 RU, then each RU of the first uplink transmission corresponds to one OCC block, for a total of 2 OCC blocks, as shown in Figure 7.

[0278] Example group two:

[0279] In some embodiments, when the network schedules the first uplink transmission as NPUSCH 12-Tone with 15kHz SCS, the repetition count is 1, N_RU = 1, and OCC transmission is performed. The OCC type is intra-symbol OCC / within symbol OCC (i.e., OCC is performed on frequency domain resources within one OFDM symbol), and the OCC block granularity is 6 SCs. If the network configures the first length set as {1,3,6,12} SCs via SIB messages, and further indicates '11' in the field corresponding to the DCI of the first uplink transmission, indicating the use of the 4th value in the first length set, i.e., the first length is 12 SCs, then the first uplink transmission can perform OCC transmission with OCC length = 2. The resource allocation method is shown in Figure 8.

[0280] In some embodiments, when the network schedules the first uplink transmission as NPUSCH 12-Tone with 15kHz SCS, the repetition count is 1, N_RU = 1, and OCC transmission is performed, where the OCC type is intra-symbol OCC / within symbol OCC (i.e., OCC is performed on frequency domain resources within one OFDM symbol), and the OCC length is 4. If the network configures the first length set as {12}SCs via RRC messages, then the first length is determined to be 12SCs, and the OCC block granularity for the first uplink transmission is 3SCs, performing OCC transmission with an OCC length of 4. The resource allocation method is shown in Figure 9.

[0281] In some embodiments, when the network schedules the first uplink transmission as NPUSCH single-Tone with 15kHz SCS, the repetition count is 2, N_RU = 1, and OCC transmission is performed, where the OCC type is symbol-level OCC and the OCC block granularity is 1 OFDM symbol.

[0282] If the network indicates that the first length is 4 time slots by scheduling the corresponding field in the DCI of the first uplink transmission, then the first uplink transmission will be carried out in OCC transmission with 4 time slots as one OCC block. The resource allocation methods corresponding to OCC length=2 and OCC length=4 are shown in Figure 10.

[0283] It can be seen that the supported OCC lengths are 2, 4, 6, 8, 12, etc.

[0284] If the network indicates that the first length is 1 RU by the corresponding field in the DCI of the first uplink transmission, then the first uplink transmission is carried out in OCC transmission with 1 RU (16 slots) as one OCC block. The resource allocation method corresponding to different OCC length=2 is shown in Figure 11.

[0285] In some embodiments, when the network schedules the first uplink transmission as NPUSCH single-Tone with 15kHz SCS, the repetition count is 2, N_RU = 1, and OCC transmission is performed. The OCC type is slot-level OCC (including inter-slot OCC / across slot OCC / inter-slot group OCC), and the OCC block granularity is one time slot. If the network indicates a first length of 8 time slots, the first uplink transmission performs OCC transmission with 8 time slots as one OCC block. The resource allocation method corresponding to OCC length = 2 is shown in Figure 12.

[0286] In some embodiments, when the network schedules the first uplink transmission as NPUSCH 6-Tone with 15kHz SCS, the repetition count is 4, N_RU = 1, and OCC transmission is performed. The OCC type is slot-level OCC (including inter-slot OCC / across slot OCC / inter-slot group OCC), and the OCC block granularity is one time slot. If the network indicates a first length of 8 time slots, then the first uplink transmission performs OCC transmission with 8 time slots as one OCC block.

[0287] Without modifying the existing mapping rules, the resource allocation method corresponding to OCC length=2 is shown in Figure 13.

[0288] Modify the existing mapping rules and adjust the mapping order. The resource allocation method corresponding to OCC length=2 is shown in Figure 14.

[0289] In some embodiments, when the network schedules the first uplink transmission as NPUSCH 3-Tone with 15kHz SCS, the repetition count is 8, N_RU = 1, and OCC transmission is performed. The OCC type is repetition-level OCC (including Inter-repetition OCC / across repetition OCC / inter-repetition group OCC), and the OCC block granularity is 1 repetition (i.e., corresponding to N).slots (time slot).

[0290] If the network configures the first length set as {4} through SIB messages, that is, determines the first length as 4 repetitions, then the first uplink transmission can perform OCC transmission with OCC length = 2, as shown in Figure 15.

[0291] It can be seen that in the case of revision-level OCC, due to M identical The value of the first length is also subject to certain restrictions, namely, the first length <= M. identical .

[0292] In some embodiments, when the network schedules the first uplink transmission as NPUSCH single-Tone with 15kHz SCS, the repetition count is 2, N_RU = 1, and OCC transmission is performed. The OCC type is repetition-level OCC (including inter-repetition OCC / across repetition OCC / inter-repetition group OCC), and the OCC block granularity is 1 time slot (i.e., corresponding to N). slots = 1 time slot).

[0293] If the network indicates a first length of 4 repetitions, then the first uplink transmission can perform an OCC transmission with an OCC length of 4, as shown in Figure 16.

[0294] It can be seen that, in this situation, due to Due to limitations, the mapping rules need to be modified to satisfy the OCC transmission with a first length of 4 repetitions;

[0295] Or, modify The value of is the same as in the case of multi-Tone, that is... To make it possible in single-tone cases It can be greater than 1.

[0296] In some embodiments, when the network schedules the first uplink transmission as NPUSCH 12-Tone with 15kHz SCS, the repetition count is 16, N_RU = 1, and OCC transmission is performed. The OCC type is RV-level OCC (including inter-RV OCC, slot group OCC using the same RV, or repetition group OCC using the same RV, etc.), and the OCC block granularity is the time-domain resource corresponding to one RV. Each time slot ( otherwise ),here

[0297] If the network indicates that the first length is the entire transmission duration, that is... If there are 1 time slot, the first uplink transmission can perform OCC transmission with OCC length = 2, as shown in Figure 17.

[0298] It can be seen that, under this condition, due to the limitations of the existing RV rules, at least 4 complete RVs corresponding to time-domain resource lengths are required to satisfy OCC transmission with OCC length = 2, which means that the number of repetitions cannot be less than 16.

[0299] Alternatively, the existing rules for determining RV can be modified, for example: the redundant version used for the j-th part is... (if Then L = 1; otherwise This makes two adjacent RVs the same RV. The above case, after modifying the RV rules, is shown in Figure 18.

[0300] In this way, as long as the number of repetitions is not less than 8, OCC transmission with OCC length = 2 can be performed.

[0301] Example group three:

[0302] In some embodiments, when the network schedules the first uplink transmission as PUSCH repetition type A with 15kHz SCS, the number of repetitions is 4, and OCC transmission is performed. The OCC type is inter-repetition OCC, the OCC block granularity is 1 repetition, and the first length is the entire transmission duration, i.e., 4 repetitions (=4 slots). Then the first uplink transmission can perform OCC transmission with OCC length=2 and OCC length=4, as shown in Figure 19.

[0303] In some embodiments, when the network schedules the first uplink transmission as NPUSCH 12-Tone with 15kHz SCS, the repetition count is 1, N_RU = 1, and OCC transmission is performed, where the OCC type is intra-symbol OCC / within symbol OCC (i.e., OCC is performed on frequency domain resources within one OFDM symbol), and the OCC block granularity is 6SCs. Since the network schedules a 12-ton NPUSCH transmission, the first length is 12SCs, and therefore the first uplink transmission can perform OCC transmission with an OCC length of 2, as shown in Figure 20.

[0304] In some embodiments, when the network schedules the first uplink transmission as NPUSCH 12-Tone with 15kHz SCS, the repetition count is 1, N_RU = 1, and OCC transmission is performed. The OCC type is intra-symbol OCC / within symbol OCC (i.e., OCC is performed on frequency domain resources within one OFDM symbol), the OCC block granularity is 3SCs, and the OCC length is 2. Therefore, the first length is determined to be 6SCs, and the first uplink transmission is divided into 2 OCC blocks for OCC transmission, as shown in Figure 21.

[0305] In some embodiments, when the network schedules the first uplink transmission as NPUSCH single-tone with 15kHz SCS, the repetition count is 2, N_RU = 1, and OCC transmission is performed, where the OCC type is symbol-level OCC and the OCC block granularity is 1 OFDM symbol. If the protocol specifies that the first length is equal to N... slots That is, 2 slots. The first uplink transmission uses 2 slots as one OCC block for OCC transmission. The resource allocation method corresponding to OCC length=4 is shown in Figure 22.

[0306] If the first length is determined implicitly to be equal to one time slot (if) Then L = 1; otherwise ), that is, 16 time slots. The first uplink transmission uses 16 time slots as one OCC block for OCC transmission. The resource allocation method corresponding to OCC length=2 is shown in Figure 23.

[0307] In some embodiments, when the network schedules the first uplink transmission as NPUSCH single-Tone with 15kHz SCS, the repetition count is 2, N_RU = 1, and OCC transmission is performed, where the OCC type is slot-level OCC (including inter-slot OCC / across slot OCC / inter-slot group OCC), and the OCC block granularity is one time slot. If the first length is implicitly determined to be equal to N... slots That is, 2 time slots. The first uplink transmission uses 2 slots as one OCC block and performs OCC transmission with OCC length = 2, as shown in Figure 24.

[0308] In this situation, because Due to limitations, the mapping rules need to be modified to enable OCC transmission.

[0309] If the first length is determined implicitly to be equal to one time slot (if) Then L = 1; otherwise ), that is, 16 time slots. The first uplink transmission uses 16 slots as one OCC block for OCC transmission, corresponding to the resource allocation method of OCC length=4 (it can be seen that the supported OCC lengths are 2, 4, 8, etc.) as shown in Figure 25.

[0310] In this situation, because Due to limitations, the mapping rules need to be modified to enable OCC transmission.

[0311] As can be seen, in the above case of slot-level OCC, without modifying the existing RU division, the transmission of OCC will cause the number of available time slots in a TB mapped to a RU to be reduced exponentially with the OCC length. Therefore, in some embodiments, the duration of the time domain resources of the first uplink transmission can also be multiplied by the OCC length. This can be accomplished by modifying the mapping relationship of the number of RUs, such as the actual number of RUs = the indicated number of RUs * the OCC length, as shown in Figure 26.

[0312] Alternatively, the repetition frequency can be increased to achieve this, as shown in Figure 27.

[0313] It can be seen that this approach requires modifying the rules for determining RV.

[0314] In some embodiments, when the network schedules the first uplink transmission as NPUSCH 3-Tone with 15kHz SCS, the repetition count is 8, N_RU = 1, and OCC transmission is performed. The OCC type is slot-level OCC (including Inter-repetition OCC / across repetition OCC / inter-repetition group OCC), and the OCC block granularity is one time slot. The first length is N as agreed upon by the protocol. slots If there are two time slots, then the first uplink transmission uses two time slots as one OCC block and performs OCC transmission with OCC length = 2, as shown in Figure 28.

[0315] In some embodiments, when the network schedules the first uplink transmission as NPUSCH 3-Tone with 15kHz SCS, the repetition count is 8, N_RU = 1, and OCC transmission is performed. The OCC type is repetition-level OCC (including Inter-repetition OCC / across repetition OCC / inter-repetition group OCC), and the OCC block granularity is 1 repetition (i.e., corresponding to N). slots (time slots). Since the first length is equal to M. identical N repetitions (i.e., N) slots *M identical (8 time slots), then the first uplink transmission can perform OCC transmission with OCC length = 2, as shown in Figure 29.

[0316] In some embodiments, when the network schedules the first uplink transmission as NPUSCH single-Tone with 15kHz SCS, the repetition count is 2, N_RU = 1, and OCC transmission is performed. The OCC type is repetition-level OCC (including inter-repetition OCC / across repetition OCC / inter-repetition group OCC), and the OCC block granularity is 1 repetition (i.e., corresponding to N). slots (time slots). If the protocol stipulates that the first length is equal to... There are 16 time slots, but in this case, due to Due to limitations, the mapping rules need to be modified to perform repetition-level OCC transmission, for example, transmission with OCC length=2, as shown in Figure 30;

[0317] Or, modify The value is the same as in the multi-Tone case, that is... Then the first length can be The number of repetitions needs to be greater than or equal to 4 to qualify. Here, assuming the repetition count is 4, the first uplink transmission can perform OCC transmission with OCC length = 2, as shown in Figure 31.

[0318] Or, modify The value of is equal to the OCC block granularity * OCC length, so the first length can be . The repetitions, for example, the first uplink transmission performs an OCC transmission with an OCC length of 2, as shown in Figure 31, except that the first length is 2 repetitions, corresponding to 2 slots.

[0319] In some embodiments, when the network schedules the first uplink transmission as NPUSCH 12-Tone with 15kHz SCS, the repetition count is 16, N_RU = 1, and OCC transmission is performed. The OCC type is RV-level OCC (including inter-RV OCC, slot group OCC using the same RV, or repetition group OCC using the same RV, etc.), and the OCC block granularity is the time-domain resource corresponding to one RV. Each time slot ( otherwise ),here The protocol stipulates that the first length is the entire transmission duration, i.e. With 32 time slots, the first uplink transmission can perform OCC transmission with OCC length = 2, as shown in Figure 32.

[0320] It can be seen that, under this circumstance, due to the limitations of the existing RV rules, at least 4 complete RVs corresponding to time-domain resource lengths are required to satisfy OCC transmission with OCC length = 2, which means that the number of repetitions cannot be less than 16.

[0321] Alternatively, the existing rules for determining RV can be modified, for example: the redundant version used for the j-th part is... (if Then L = 1; otherwise This makes two adjacent RVs the same RV. The above case, after modifying the RV rules, is shown in Figure 33.

[0322] In this way, as long as the number of repetitions is not less than 8, OCC transmission with OCC length = 2 can be performed.

[0323] This application proposes a method for using OCC transmission on a physical uplink shared channel. By introducing the mechanism of OCC blocks, the time and frequency resources for applying OCC are divided to coordinate with the existing time and frequency resource allocation, thereby realizing OCC transmission.

[0324] The uplink transmission method provided in this application can be executed by an uplink transmission device. This application uses an uplink transmission device executing the uplink transmission method as an example to illustrate the uplink transmission device provided in this application.

[0325] This application provides an uplink transmission device. As an example, the uplink transmission device may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0326] The uplink transmission device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0327] Specifically, referring to Figure 34, when the uplink transmission device is a terminal or a component within a terminal, the uplink transmission device 200 includes:

[0328] Transmission module 201 is used to perform a first uplink transmission based on a target orthogonal coverage code (OCC) sequence within at least one target block;

[0329] The at least one target block is obtained by dividing the resources of the first uplink transmission according to a first length, wherein the first length is the resource length corresponding to one target block.

[0330] Optionally, the first length is at least one of the following indicated by the first indication information sent by the network-side device:

[0331] At least one subcarrier SC; at least one resource element RE; at least one resource block RB; at least one orthogonal frequency division multiplexing (OFDM) symbol; at least one time slot; at least one repetition; at least one resource unit RU; at least one millisecond.

[0332] Optionally, the first indication information carries at least one of the following:

[0333] System Information Block (SIB), Radio Resource Control (RRC), Downlink Control Information (DCI), and Media Access Control (MAC) Control Unit (CE).

[0334] Optionally, the first indication information is carried in SIB or RRC, and the first indication information includes a set of values ​​for the first length;

[0335] If the set of values ​​includes a single value, then the value in the set of values ​​is the first length; or

[0336] When the set of values ​​includes at least two values, the first length is the value in the set of values ​​indicated by DCI or MAC CE.

[0337] Optionally, the first length is determined based on second indication information sent by the network-side device, the second indication information indicating at least one of the following:

[0338] OCC type, OCC length, number of multiplexed user equipment (UE) units, target OCC sequence, OCC index, number of repetitions, RU index indication, SC indication, and transmission duration.

[0339] Optionally, the first length is equal to the total number of transmission opportunities; or

[0340] The first length is equal to N slots One time slot; or

[0341] The first length is equal to Midentical Repeat; or

[0342] The first length is equal to N slots ×M identical One time slot; or

[0343] The first length is equal to the product of the target block's granularity and the OCC length; or

[0344] The first length is equal to the number of scheduled SCs; or

[0345] The first length is equal to B time slots;

[0346] Where, N slots M represents the number of time slots determined based on the subcarrier spacing. identical Based on and N Rep A fixed number of repetitions, L is based on Determined coefficients, N RU The number of RUs required to transmit one TB. The number of time slots occupied by a RU. N represents the number of SCs occupied by a RU. Rep This represents the number of repetitions.

[0347] Optionally, the device further includes:

[0348] Processing module 202 is used to determine the block granularity of the target block, wherein the block granularity of the target block is the size of the resource in the target block multiplied by an element corresponding to the target OCC sequence.

[0349] Optionally, the block granularity of the target block is determined based on at least one of OCC type and OCC length; or, the block granularity of the target block is indicated based on third indication information sent by the network-side device.

[0350] Optionally, when the OCC type is an OCC associated with an OFDM symbol, the block granularity of the target block is 1 SC, 2 SCs, 3 SCs, 4 SCs, or 6 SCs;

[0351] or

[0352] When the OCC type is an OCC associated with multiple OFDM symbols, the block granularity of the target block is 1 OFDM symbol, or 1 symbol group, or the block granularity of the target block is the quotient of a first difference and the OCC length, where the first difference is the difference between the number of time-domain symbols in the Time Domain Resource Allocation (TDRA) and the number of symbols in the DMRS.

[0353] or

[0354] When the OCC type is a slot-associated OCC, the block granularity of the target block is 1 slot or N. slots One time slot;

[0355] or

[0356] When the OCC type is an OCC associated with the number of repetitions, the block granularity of the target block is 1 repetition or N. slots Time slot;

[0357] or

[0358] When the OCC type is an OCC associated with a redundant version RV, the block granularity of the target block is N. slots ×M identical One time slot, or B time slots;

[0359] Where, N slots M represents the number of time slots determined based on the subcarrier spacing. identical Based on and N Rep A fixed number of repetitions, L is based on Determined coefficients, N RU The number of RUs required to transmit one TB. The number of time slots occupied by a RU. N represents the number of SCs occupied by a RU. Rep This represents the number of repetitions.

[0360] Optionally, when the block granularity of the target block is indicated based on third indication information sent by the network-side device, the processing module 202 is further configured to: determine the OCC type of the target block based on the block granularity of the target block, wherein the OCC type is associated with the block granularity of the target block.

[0361] Optionally, if the block granularity of the target block is greater than or equal to one time slot, the DMRS within each time slot uses the same target OCC sequence as the data portion for OCC transmission.

[0362] Optionally, the target OCC sequence is based on a protocol agreement; or, the target OCC sequence is based on an indication from a network-side device; or, the target OCC sequence is determined based on the OCC length.

[0363] Optionally, the processing module 202 is further configured to:

[0364] Determine the target RV used in the first uplink transmission;

[0365] The target RV is determined based on the identifier of the target block, or the target RV is a preset RV.

[0366] Optionally, the resource duration of the first uplink transmission is determined based on the OCC length.

[0367] Optionally, when the first uplink transmission is a segmented transmission, the target block is less than or equal to the first transmission segment, which is any one of the multiple segments of the first uplink transmission; or, the first transmission segment includes one or more of the target blocks; or, the terminal expects to be configured with the same segmented configuration as the object performing the OCC transmission.

[0368] The uplink transmission device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG3 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0369] As shown in Figure 35, this application embodiment also provides a communication device 300, including a processor 301 and a memory 302. The memory 302 stores a program or instructions that can run on the processor 301. For example, when the communication device 300 is a terminal, when the program or instructions are executed by the processor 301, they implement the various steps of the above-described uplink transmission method embodiment and achieve the same technical effect.

[0370] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG3. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal can be the uplink transmission device shown in FIG34. Specifically, FIG36 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0371] The terminal 400 includes, but is not limited to, at least some of the following components: radio frequency unit 401, network module 402, audio output unit 403, input unit 404, sensor 405, display unit 406, user input unit 407, interface unit 408, memory 409, and processor 410.

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

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

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

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

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

[0377] The radio frequency unit 401 is used for:

[0378] The first uplink transmission is performed within at least one target block based on the target orthogonal overlay code (OCC) sequence;

[0379] The at least one target block is obtained by dividing the resources of the first uplink transmission according to a first length, wherein the first length is the resource length corresponding to one target block.

[0380] Optionally, the first length is at least one of the following indicated by the first indication information sent by the network-side device:

[0381] At least one subcarrier SC; at least one resource element RE; at least one resource block RB; at least one orthogonal frequency division multiplexing (OFDM) symbol; at least one time slot; at least one repetition; at least one resource unit RU; at least one millisecond.

[0382] Optionally, the first indication information carries at least one of the following:

[0383] System Information Block (SIB), Radio Resource Control (RRC), Downlink Control Information (DCI), and Media Access Control (MAC) Control Unit (CE).

[0384] Optionally, the first indication information is carried in SIB or RRC, and the first indication information includes a set of values ​​for the first length;

[0385] If the set of values ​​includes a single value, then the value in the set of values ​​is the first length; or

[0386] When the set of values ​​includes at least two values, the first length is the value in the set of values ​​indicated by DCI or MAC CE.

[0387] Optionally, the first length is determined based on second indication information sent by the network-side device, the second indication information indicating at least one of the following:

[0388] OCC type, OCC length, number of multiplexed user equipment (UE) units, target OCC sequence, OCC index, number of repetitions, RU index indication, SC indication, and transmission duration.

[0389] Optionally, the first length is equal to the total number of transmission opportunities; or

[0390] The first length is equal to N slots One time slot; or

[0391] The first length is equal to M identical Repeat; or

[0392] The first length is equal to N slots ×M identical One time slot; or

[0393] The first length is equal to the product of the target block's granularity and the OCC length; or

[0394] The first length is equal to the number of scheduled SCs; or

[0395] The first length is equal to B time slots;

[0396] Where, N slots M represents the number of time slots determined based on the subcarrier spacing. identical Based on and N Rep A fixed number of repetitions, L is based on Determined coefficients, N RU The number of RUs required to transmit one TB. The number of time slots occupied by a RU. N represents the number of SCs occupied by a RU. Rep This represents the number of repetitions.

[0397] Optionally, the processor 410 is configured to: determine the block granularity of the target block, wherein the block granularity of the target block is the size of the resource in the target block multiplied by an element corresponding to one of the target OCC sequences.

[0398] Optionally, the block granularity of the target block is determined based on at least one of OCC type and OCC length; or, the block granularity of the target block is indicated based on third indication information sent by the network-side device.

[0399] Optionally, when the OCC type is an OCC associated with an OFDM symbol, the block granularity of the target block is 1 SC, 2 SCs, 3 SCs, 4 SCs, or 6 SCs;

[0400] or

[0401] When the OCC type is an OCC associated with multiple OFDM symbols, the block granularity of the target block is 1 OFDM symbol, or 1 symbol group, or the block granularity of the target block is the quotient of a first difference and the OCC length, where the first difference is the difference between the number of time-domain symbols in the Time Domain Resource Allocation (TDRA) and the number of symbols in the DMRS.

[0402] or

[0403] When the OCC type is a slot-associated OCC, the block granularity of the target block is 1 slot or N. slots One time slot;

[0404] or

[0405] When the OCC type is an OCC associated with the number of repetitions, the block granularity of the target block is 1 repetition or N. slots Time slot;

[0406] or

[0407] When the OCC type is an OCC associated with a redundant version RV, the block granularity of the target block is N. slots ×M identical One time slot, or B time slots;

[0408] Where, N slots M represents the number of time slots determined based on the subcarrier spacing. identical Based on and N Rep A fixed number of repetitions, L is based on Determined coefficients, N RU The number of RUs required to transmit one TB. The number of time slots occupied by a RU. N represents the number of SCs occupied by a RU. Rep This represents the number of repetitions.

[0409] Optionally, when the block granularity of the target block is indicated based on third indication information sent by the network-side device, the processor 410 is further configured to: determine the OCC type of the target block based on the block granularity of the target block, wherein the OCC type is associated with the block granularity of the target block.

[0410] Optionally, if the block granularity of the target block is greater than or equal to one time slot, the DMRS within each time slot uses the same target OCC sequence as the data portion for OCC transmission.

[0411] Optionally, the target OCC sequence is based on a protocol agreement; or, the target OCC sequence is based on an indication from a network-side device; or, the target OCC sequence is determined based on the OCC length.

[0412] Optionally, the processor 410 is further configured to:

[0413] Determine the target RV used in the first uplink transmission;

[0414] The target RV is determined based on the identifier of the target block, or the target RV is a preset RV.

[0415] Optionally, the resource duration of the first uplink transmission is determined based on the OCC length.

[0416] Optionally, when the first uplink transmission is a segmented transmission, the target block is less than or equal to the first transmission segment, which is any one of the multiple segments of the first uplink transmission; or, the first transmission segment includes one or more of the target blocks; or, the terminal expects to be configured with the same segmented configuration as the object performing the OCC transmission.

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

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

[0419] The processor mentioned above is the processor in the terminal or network-side device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

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

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

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

[0423] This application also provides a wireless communication system, including a terminal and a network-side device, wherein the terminal can be used to perform the steps of the uplink transmission method applied to the terminal as described above.

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

[0425] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

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

Claims

1. An uplink transmission method, comprising: The terminal performs a first uplink transmission based on the target orthogonal coverage code (OCC) sequence within at least one target block; The at least one target block is obtained by dividing the resources of the first uplink transmission according to a first length, wherein the first length is the resource length corresponding to one target block.

2. The method according to claim 1, wherein, The first length is indicated by at least one of the following in the first indication information sent by the network-side device: At least one subcarrier SC; at least one resource element RE; at least one resource block RB; at least one orthogonal frequency division multiplexing (OFDM) symbol; at least one time slot; at least one repetition; at least one resource unit RU; at least one millisecond.

3. The method according to claim 2, wherein, The first indication information carries at least one of the following: System Information Block (SIB), Radio Resource Control (RRC), Downlink Control Information (DCI), and Media Access Control (MAC) Control Unit (CE).

4. The method according to claim 2 or 3, wherein, The first indication information is carried in SIB or RRC, and the first indication information includes a set of values ​​for the first length; If the set of values ​​includes a single value, then the value in the set of values ​​is the first length. or When the set of values ​​includes at least two values, the first length is the value in the set of values ​​indicated by DCI or MAC CE.

5. The method according to claim 1, wherein, The first length is determined based on second indication information sent by the network-side device, the second indication information indicating at least one of the following: OCC type, OCC length, number of multiplexed user equipment (UE) units, target OCC sequence, OCC index, number of repetitions, RU index indication, SC indication, and transmission duration.

6. The method according to claim 1 or 5, wherein, The first length is equal to the total number of transmission opportunities; or The first length is equal to N slots One time slot; or The first length is equal to M identical Repeat; or The first length is equal to N slots ×M identical One time slot; or The first length is equal to the product of the target block's granularity and the OCC length; or The first length is equal to the number of scheduled SCs; or The first length is equal to B time slots; Where, N slots M represents the number of time slots determined based on the subcarrier spacing. identical Based on and N Rep A fixed number of repetitions, L is based on Determined coefficients, N RU The number of RUs required to transmit one TB. The number of time slots occupied by a RU. N represents the number of SCs occupied by a RU. Rep This represents the number of repetitions.

7. The method according to any one of claims 1-6, wherein, Before the terminal performs a first uplink transmission based on a target OCC sequence within at least one target block, the method further includes: The terminal determines the block granularity of the target block, which is the size of the resource in the target block multiplied by an element corresponding to the target OCC sequence.

8. The method according to claim 7, wherein, The block granularity of the target block is determined based on at least one of OCC type and OCC length; or, the block granularity of the target block is indicated based on third indication information sent by the network-side device.

9. The method according to claim 7 or 8, wherein, When the OCC type is an OCC associated with an OFDM symbol, the block granularity of the target block is 1 SC, 2 SC, 3 SC, 4 SC, or 6 SC; or When the OCC type is an OCC associated with multiple OFDM symbols, the block granularity of the target block is 1 OFDM symbol, or 1 symbol group, or the block granularity of the target block is the quotient of a first difference and the OCC length, where the first difference is the difference between the number of time-domain symbols in the Time Domain Resource Allocation (TDRA) and the number of symbols in the DMRS. or When the OCC type is a slot-associated OCC, the block granularity of the target block is 1 slot or N. slots One time slot; or When the OCC type is an OCC associated with the number of repetitions, the block granularity of the target block is 1 repetition or N. slots Time slot; or When the OCC type is an OCC associated with a redundant version RV, the block granularity of the target block is N. slots ×M identical One time slot, or B time slots; Where, N slots M represents the number of time slots determined based on the subcarrier spacing. identical Based on and N Rep A fixed number of repetitions, L is based on Determined coefficients, N RU The number of RUs required to transmit one TB. The number of time slots occupied by a RU. N represents the number of SCs occupied by a RU. Rep This represents the number of repetitions.

10. The method according to claim 8, wherein, When the block granularity of the target block is indicated based on third indication information sent by the network-side device, the method further includes: The terminal determines the OCC type of the target block based on the block granularity of the target block, and the OCC type is associated with the block granularity of the target block.

11. The method according to any one of claims 7-10, wherein, When the block granularity of the target block is greater than or equal to one time slot, the DMRS within each time slot uses the same target OCC sequence as the data portion for OCC transmission.

12. The method according to any one of claims 1-11, wherein, The target OCC sequence is based on a protocol agreement; or, the target OCC sequence is based on an indication from a network-side device; or, the target OCC sequence is determined based on the OCC length.

13. The method according to any one of claims 1-12, wherein, Before the terminal performs a first uplink transmission based on a target OCC sequence within at least one target block, the method further includes: The terminal determines the target RV used for the first uplink transmission; The target RV is determined based on the identifier of the target block, or the target RV is a preset RV.

14. The method according to any one of claims 1-13, wherein, The resource duration of the first uplink transmission is determined based on the OCC length.

15. The method according to any one of claims 1-14, wherein, In the case that the first uplink transmission is a segmented transmission, the target block is less than or equal to the first transmission segment, which is any one of the multiple segments of the first uplink transmission; or, the first transmission segment includes one or more of the target blocks; or, the terminal expects to be configured with the same segmented configuration as the object performing the OCC transmission.

16. An uplink transmission device, comprising: The transmitting module is used to perform a first uplink transmission based on a target orthogonal coverage code (OCC) sequence within at least one target block; The at least one target block is obtained by dividing the resources of the first uplink transmission according to a first length, wherein the first length is the resource length corresponding to one target block.

17. The apparatus according to claim 16, wherein, The device further includes: The processing module is used to determine the block granularity of the target block, wherein the block granularity of the target block is the size of the resource in the target block multiplied by an element corresponding to the target OCC sequence.

18. The apparatus according to claim 16 or 17, wherein, The block granularity of the target block is determined based on at least one of OCC type and OCC length; or, the block granularity of the target block is indicated based on third indication information sent by the network-side device.

19. The apparatus according to claim 18, wherein, When the block granularity of the target block is indicated based on the third indication information sent by the network-side device, the processing module is further configured to: determine the OCC type of the target block based on the block granularity of the target block, wherein the OCC type is associated with the block granularity of the target block.

20. The apparatus according to any one of claims 16-19, wherein, The processing module is also used for: Determine the target RV used in the first uplink transmission; The target RV is determined based on the identifier of the target block, or the target RV is a preset RV.

21. A terminal comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the uplink transmission method as claimed in any one of claims 1-15.

22. A readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the uplink transmission method as described in any one of claims 1-15.

Images