Uplink transmission method, apparatus, device, and storage medium

Abstract

The application discloses an uplink transmission method, device and equipment and a storage medium, and relates to the technical field of communication. The method comprises the following steps: a terminal device adjusts PUSCH transmission in a first OCC group, the terminal device determines one or more OCC groups according to resources occupied by the PUSCH transmission and / or OCC length, and transmits the PUSCH to which the OCC is applied in the one or more OCC groups, and the first OCC group is at least one OCC group in the one or more OCC groups (410). Embodiments of the application provide a PUSCH transmission adjustment scheme based on an OCC group, that is, the terminal device adjusts the PUSCH transmission in the OCC group meeting the condition, so that the specific behavior of the terminal device is clear when the PUSCH to which the OCC is applied collides with other channels, signal interference caused by the collision is avoided, and the communication reliability is improved.

Description

Uplink transmission method, device, equipment and storage medium Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to an uplink transmission method, apparatus, device, and storage medium. Background Art

[0002] In related communication systems, OCC (Orthogonal Cover Code) is used between OFDM (Orthogonal Frequency Division Multiplexing) symbols or time slots occupied by PUSCH (Physical Uplink Shared Channel) transmission to improve system capacity.

[0003] Therefore, when the PUSCH using OCC collides with other channels, how to handle this is an urgent problem that needs to be solved.

[0004] Summary of the Invention

[0005] The embodiments of the present application provide an uplink transmission method, apparatus, device, and storage medium. The technical solutions provided by the embodiments of the present application are as follows:

[0006] According to one aspect of an embodiment of the present application, an uplink transmission method is provided, the method including:

[0007] The terminal device adjusts the PUSCH transmission in the first OCC group. The terminal device determines one or more OCC groups based on the resources occupied by the PUSCH transmission and / or the OCC length, and sends the PUSCH applying the OCC within the one or more OCC groups. The first OCC group is at least one OCC group among the one or more OCC groups.

[0008] According to one aspect of an embodiment of the present application, an uplink transmission device is provided, the device comprising:

[0009] A processing module is used to adjust the PUSCH transmission in the first OCC group. The terminal device determines one or more OCC groups based on the resources occupied by the PUSCH transmission and / or the OCC length, and sends the PUSCH applying the OCC within the one or more OCC groups. The first OCC group is at least one OCC group among the one or more OCC groups.

[0010] According to one aspect of an embodiment of the present application, a terminal device is provided, comprising a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program to implement the above method.

[0011] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to be executed by a processor to implement the above method.

[0012] According to one aspect of an embodiment of the present application, a chip is provided, which includes a programmable logic circuit and / or program instructions, and when the chip is running, is used to implement the above method.

[0013] According to one aspect of an embodiment of the present application, a computer program product is provided, which includes computer instructions stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement the above method.

[0014] The technical solutions provided by the embodiments of the present application may have the following beneficial effects:

[0015] An embodiment of the present application provides a PUSCH transmission adjustment scheme based on the OCC group, that is, the terminal device adjusts the PUSCH transmission in the OCC group that meets the conditions, thereby clarifying the specific behavior of the terminal device when the PUSCH using the OCC collides with other channels, avoiding signal interference caused by the collision, and improving communication reliability. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0017] FIG2 is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application;

[0018] FIG3 is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application;

[0019] FIG4 is a flowchart of an uplink transmission method provided by an embodiment of the present application;

[0020] FIG5 is a schematic diagram of using OCCs between symbols occupied by PUSCH transmission according to an embodiment of the present application;

[0021] FIG6 is a schematic diagram of using OCC between time slots occupied by PUSCH transmission according to an embodiment of the present application;

[0022] FIG7 is a schematic diagram of a collision between a PUSCH and a single PUCCH transmission in an OCC group provided by one embodiment of the present application;

[0023] FIG8 is a schematic diagram of a collision between a PUSCH and a single PUCCH transmission in an OCC group provided by another embodiment of the present application;

[0024] FIG9 is a schematic diagram of a collision between a PUSCH and a single PUCCH transmission in an OCC group provided by another embodiment of the present application;

[0025] FIG10 is a schematic diagram showing that a PUSCH in an OCC group does not meet the conditions for multiplexing UCI according to an embodiment of the present application;

[0026] FIG11 is a schematic diagram showing that a PUSCH in an OCC group satisfies the conditions for multiplexing UCI according to an embodiment of the present application;

[0027] FIG12 is a schematic diagram of determining whether the first symbol for PUSCH transmission in an OCC group meets the conditions for multiplexing UCI on the PUSCH according to one embodiment of the present application;

[0028] FIG13 is a schematic diagram of collision between type A PUSCH repeated transmission and PUCCH repeated transmission provided by one embodiment of the present application;

[0029] FIG14 is a schematic diagram of collision between type B PUSCH repeated transmission and PUCCH repeated transmission provided by one embodiment of the present application;

[0030] FIG15 is a schematic diagram of applying OCC to a PUCCH in an OCC group provided by one embodiment of the present application;

[0031] FIG16 is a schematic diagram of a collision of PUCCHs on different time slots in an OCC group provided by one embodiment of the present application;

[0032] FIG17 is a schematic diagram of a collision between a type A PUSCH repetitive transmission and a downlink symbol that is not based on an available time slot count, provided by one embodiment of the present application;

[0033] FIG18 is a schematic diagram of a collision between type A PUSCH repetitive transmission and downlink symbols based on available time slot count according to an embodiment of the present application;

[0034] FIG19 is a schematic diagram of a collision between type A PUSCH repetitive transmission and downlink symbols based on available time slot count provided by another embodiment of the present application;

[0035] FIG20 is a schematic diagram of a collision between type A PUSCH repetitive transmission and transmit / receive switching time based on available time slot count according to an embodiment of the present application;

[0036] FIG21 is a block diagram of an uplink transmission device provided by one embodiment of the present application;

[0037] Figure 22 is a structural diagram of a terminal device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0038] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0039] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. A person skilled in the art will appreciate that, with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0040] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system, B5G (Beyound5G) system, sixth-generation communication (6G) system or other communication systems, etc.

[0041] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0042] The communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0043] The communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as an unshared spectrum.

[0044] The embodiments of the present application can be applied to both non-terrestrial networks (NTN) and terrestrial networks (TN). NTNs generally use satellite communications to provide communication services to terrestrial users. Currently, NTN systems include NR-NTN and IoT-NTN systems, and may include other NTN systems in the future.

[0045] For example, Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application. As shown in Figure 1, communication system 100 may include network device 110, which may be a device that communicates with terminal device 120. Network device 110 may provide communication coverage for a specific geographic area and may communicate with terminal devices located within the coverage area.

[0046] Figure 1 exemplarily shows a network device 110 and two terminal devices 120. In some embodiments of the present application, the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0047] For example, FIG2 is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application. Referring to FIG2 , the communication system may include a terminal device 201 and a satellite 202, and wireless communication may be performed between the terminal device 201 and the satellite 202. The network formed between the terminal device 201 and the satellite 202 may also be referred to as an NTN. In the architecture of the communication system shown in FIG2 , the satellite 202 may have the function of a base station, and the terminal device 201 and the satellite 202 may communicate directly with each other. In this system architecture, the satellite 202 may be referred to as a network device. In some embodiments of the present application, a plurality of satellites 202 may be included in the communication system, and each network satellite 202 may include a different number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0048] For example, FIG3 is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application. Referring to FIG3 , the communication system includes a terminal device 301, a satellite 302, and a base station 303. Wireless communication can be performed between the terminal device 301 and the satellite 302, and communication can be performed between the satellite 302 and the base station 303. The network formed between the terminal device 301, the satellite 302, and the base station 303 can also be referred to as an NTN. In the architecture of the communication system shown in FIG3 , the satellite 302 may not have the function of a base station, and the communication between the terminal device 301 and the base station 303 needs to be transferred through the satellite 302. In this system architecture, the base station 303 can be referred to as a network device. In some embodiments of the present application, the communication system may include multiple base stations 303, each base station 303 can communicate with one or more satellites 302, and each satellite 302 can include other numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0049] In future evolved communication systems such as B5G (Beyond 5G) or 6G, distributed multiple-input multiple-output (Distributed MIMO, also known as distributed antenna system) scenarios and / or massive multiple-input multiple-output (Massive MIMO, also known as massive antenna matrix system) scenarios may also be included. In some cases, Distributed MIMO and / or Massive MIMO can also support cell-free or terminal-centric (UE-centric) network deployment scenarios. It should be understood that the above scenarios are also applicable to TN and / or NTN.

[0050] The terminal devices mentioned in the embodiments of the present application may refer to UE (User Equipment), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, user agent or user device. Optionally, the terminal device 10 may also be a cellular phone, a cordless phone, a SIP (Session Initiation Protocol) phone, a WLL (Wireless Local Loop) station, a PDA (Personal Digital Assistant), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5GS (5th Generation System) or a terminal device in a future evolved PLMN (Public Land Mobile Network), etc., and the embodiments of the present application are not limited to this. For convenience of description, the above-mentioned devices are collectively referred to as terminal devices. In the embodiments of the present application, "terminal device" and "UE" are often used interchangeably, but those skilled in the art will understand that the two can express the same meaning.

[0051] The network equipment mentioned in the embodiments of the present application may be an access network device, which may be located on the ground or on a satellite. An access network device is a device deployed in an access network to provide wireless communication functions for terminal devices. Access network devices may include various forms of macro base stations, micro base stations, relay stations, access points, and the like. In systems using different wireless access technologies, the names of devices with access network device functions may be different. For example, in a 5G NR system, they are called gNodeB or gNB. With the evolution of communication technology, the name "access network device" may change. For the convenience of description, in the embodiments of the present application, the above-mentioned devices that provide wireless communication functions for terminal devices are collectively referred to as access network devices. Optionally, a communication relationship can be established between a terminal device and a core network device through the access network device.

[0052] The "5G NR system" in the embodiments of the present application may also be referred to as a 5G system or an NR system, but those skilled in the art will understand its meaning. The technical solutions described in the embodiments of the present application may be applicable to LTE systems, 5G NR systems, subsequent evolution systems of 5G NR systems (e.g., B5G systems, 6G systems), and other communication systems such as NB-IoT (Narrow Band Internet of Things) systems, and this application does not limit this.

[0053] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources (for example, frequency domain resources, or spectrum resources) on the carrier used by the cell. The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0054] Before introducing the technical solution of this application, the collision handling mechanism of PUSCH (Physical Uplink Shared Channel) and PUCCH (Physical Uplink Control Channel) in the NR system is introduced.

[0055] 1. Collision between single-slot PUCCH transmission and PUSCH transmission

[0056] If a terminal device wants to send collided PUCCH and PUSCH in a timeslot, and at least one of the collided PUCCH and PUSCH is scheduled by DCI (Downlink Control Information), the terminal device expects the earliest PUCCH or the first symbol S0 of the collided PUCCH and PUSCH in the timeslot to meet the following time conditions, so as to multiplex UCI (Uplink Control Information) on PUSCH:

[0057] ●S0 is not earlier than the last symbol of any PDSCH (Physical Downlink Shared Channel) The symbol where the HARQ-ACK (Hybrid Automatic Repeat request-Acknowledgement) information of the PDSCH is sent on the collided PUCCH, Determined according to the PDSCH processing capability of the terminal equipment;

[0058] ●S0 is not earlier than the last symbol of the PDCCH (Physical Downlink Control Channel) associated with the HARQ-ACK information The symbol where the associated HARQ-ACK information is sent on the collided PUCCH, Determined according to PDCCH processing time;

[0059] ● S0 is not earlier than the last symbol of any PDCCH scheduling the colliding PUSCH and the colliding PUCCH carrying HARQ-ACK information. or The symbol where and Determined by the PUSCH processing capability of the terminal device.

[0060] If the terminal device wants to send colliding PUCCH and PUSCH in one time slot, and one of the colliding PUCCHs carries HARQ-ACK information in response to SPS (Semi-Persistent Scheduling) PDSCH, and the colliding PUSCH is not DCI scheduled, the terminal device expects the first symbol S0 of the earliest PUCCH or PUSCH to meet the above first time condition.

[0061] The terminal device does not expect the PUCCH or PUSCH scheduled by the DCI to collide with other PUCCH or PUSCH that does not meet the above time requirements.

[0062] The terminal device does not send a PUSCH that collides with a PUCCH in a time slot.

[0063] 2. PUSCH repeated transmission collides with PUCCH repeated transmission:

[0064] If the terminal device is in the first number The terminal device sends PUCCH on a number of time slots and sends PUSCH using Type A repeated transmission or multi-slot processing TB (Transport Block) on a second number of time slots. If the PUCCH transmission collides with the PUSCH transmission on one or more time slots and the conditions for multiplexing UCI on PUSCH are met in the colliding time slot, the terminal device sends PUCCH in the colliding time slot and does not send PUSCH.

[0065] If the terminal device is in the first number The terminal device sends PUCCH on time slots and sends PUSCH using Type B repeated transmission on a second number of time slots. If the PUCCH transmission collides with the actual PUSCH repeated transmission on one or more time slots, and the actual PUSCH repeated transmission that collides meets the conditions for multiplexing UCI on PUSCH, the terminal device sends PUCCH and does not send the actual PUSCH repeated transmission that collides.

[0066] In the aforementioned NR system, when PUSCH collides with other channels, PUSCH transmission is adjusted based on the time slot. NTN systems use OCC between OFDM symbols or time slots occupied by PUSCH transmission to improve system capacity. However, adjusting PUSCH colliding with other channels based on the time slot will destroy the orthogonality within the OCC group. Therefore, when PUSCH using OCC collides with other channels, how to adjust PUSCH transmission is an urgent problem that needs to be solved.

[0067] Please refer to Figure 4, which shows a flow chart of an uplink transmission method provided by an embodiment of the present application. The method can be applied to the network architecture shown in Figure 1. The method may include the following steps:

[0068] In step 410, the terminal device adjusts the PUSCH transmission in the first OCC group. The terminal device determines one or more OCC groups based on the resources occupied by the PUSCH transmission and / or the OCC length, and sends the PUSCH applying the OCC within the one or more OCC groups. The first OCC group is at least one OCC group among the one or more OCC groups.

[0069] Terminal devices use OCC between symbols or time slots occupied by PUSCH transmissions to improve system capacity. Symbols and time slots are the units of division of the time domain in communication systems, and symbols are OFDM symbols.

[0070] For the use of OCC between symbols occupied by PUSCH transmission, each PUSCH is an OCC group, and the symbols occupied by PUSCH transmission in the OCC group are divided into two groups according to the OCC length N. SF Group them, each group is an OCC block (or called OCC orthogonal block), and multiply them by the corresponding orthogonal sequence w n (m),m=0,1…N SF -1. n is the orthogonal sequence index (i.e., OCC index). Different users use different OCC indices, thereby performing code division multiplexing within the OCC group.

[0071] Taking Figure 5 as an example, PUSCH transmission occupies symbols 0-13. If the OCC length is N SF=2, the symbols occupied by PUSCH transmission are divided into 2 groups, i.e. 2 OCC blocks, and multiplied by the corresponding orthogonal sequence w n (m), for example, user 1 uses OCC index n=0, such as w0(m)=[1 1], and user 2 uses OCC index n=1, such as w1(m)=[1-1], thereby achieving code division multiplexing of user 1 and user 2 within the OCC group.

[0072] In addition, the use of OCC between symbols occupied by PUSCH transmission can be between symbols belonging to the same time slot occupied by PUSCH transmission, or between symbols belonging to different time slots occupied by PUSCH transmission. This application does not limit this.

[0073] For the use of OCC in the time slots occupied by PUSCH transmission, the time slots occupied by PUSCH transmission are divided into the time slots occupied by PUSCH transmission according to the OCC length N. SF Divide OCC groups, each OCC group contains N SF OCC blocks (or called OCC orthogonal blocks), and multiplied by the corresponding orthogonal sequence w n (m),m=0,1…N SF Different users use different OCC indexes n, thereby performing code division multiplexing within the OCC group.

[0074] Taking Figure 6 as an example, PUSCH transmission occupies multiple time slots, and the OCC length is N SF =2, every two time slots occupied by PUSCH transmission are regarded as an OCC group, and each time slot in the OCC group is an OCC block, and multiplied by the corresponding orthogonal sequence w n (m), for example, user 1 uses OCC index n=0, such as w0(m)=[1 1], and user 2 uses OCC index n=1, such as w1(m)=[1-1], thereby achieving code division multiplexing of user 1 and user 2 within the OCC group.

[0075] In some embodiments, the terminal device determines one or more OCC groups based on the resources occupied by the PUSCH transmission and the OCC length, and sends the PUSCH to which the OCC is applied within the above one or more OCC groups. For example, for the use of OCC between symbols occupied by PUSCH transmission, the terminal device may determine one or more OCC groups based on the symbols occupied by the PUSCH transmission and the OCC length, and send the PUSCH to which the OCC is applied within the above one or more OCC groups. For another example, for the use of OCC between time slots occupied by PUSCH transmission, the terminal device may determine one or more OCC groups based on the time slots occupied by the PUSCH transmission and the OCC length, and send the PUSCH to which the OCC is applied within the above one or more OCC groups.

[0076] In some embodiments, the terminal device may also determine one or more OCC groups based solely on the resources occupied by the PUSCH transmission, and transmit the PUSCH to which the OCC is applied within the one or more OCC groups. For example, for using OCC between time slots occupied by PUSCH transmission, the terminal device may determine one or more OCC groups based on the time slots occupied by the PUSCH transmission, such as one time slot as an OCC group, and transmit the PUSCH to which the OCC is applied within the one or more OCC groups.

[0077] In some embodiments, the OCC group includes multiple OCC blocks, and different OCC blocks in the OCC group correspond to different time domain and / or frequency domain resources. The terminal device applies OCC between the OCC blocks in the OCC group.

[0078] In some embodiments, the first OCC group is at least one OCC group among the one or more OCC groups that satisfies a first condition, wherein the first condition may be a pre-set condition.

[0079] In some embodiments, the first condition is that the PUSCH sent by the terminal device collides with the PUCCH. That is, the PUSCH sent by the terminal device collides with the PUCCH in the first OCC group.

[0080] In some embodiments, if the PUSCH sent by the terminal device collides with the PUCCH in the first OCC group, the terminal device cancels sending the PUSCH in the first OCC group.

[0081] In some embodiments, if the PUSCH sent by the terminal device collides with the PUCCH in the first OCC group, the terminal device cancels sending the PUCCH in the first OCC group.

[0082] In some embodiments, if the PUSCH sent by the terminal device collides with the PUCCH in the first OCC group, the terminal device sends the PUCCH that collides with the PUSCH in the first OCC group after the PUSCH.

[0083] Case 1: PUSCH transmission collides with single-slot PUCCH transmission

[0084] In some embodiments, the PUCCH is a single PUCCH transmission, such as a single-slot PUCCH transmission.

[0085] In some embodiments, if the PUSCH sent by the terminal device collides with the single-slot PUCCH in the first OCC group, the terminal device cancels sending the PUSCH in the first OCC group.

[0086] Taking Figure 7 as an example, the PUSCH transmitted by the terminal device occupies symbols 0-13 in the time slot, and OCC is applied between the symbols occupied by the PUSCH transmission. Then, symbols 0-13 of time slot 0 belong to OCC group 0, and symbols 0-13 of time slot 1 belong to OCC group 1. If the PUCCH transmission occupies symbols 0-1 of time slot 0 and collides with the PUSCH in OCC group 0, the terminal device cancels the transmission of the PUSCH in OCC group 0.

[0087] Taking Figure 8 as an example, the terminal device sends PUSCH in time slots 0-3, and applies N in the time slots occupied by PUSCH transmission. SF =2, then time slots 0-1 are OCC group 0, and time slots 2-3 are OCC group 1. If the PUCCH sent by the terminal device in time slot 0 collides with the PUSCH in OCC group 0, the terminal device cancels sending the PUSCH in OCC group 0.

[0088] In some embodiments, if the PUSCH sent by the terminal device collides with the single-slot PUCCH in the first OCC group, the terminal device cancels sending the PUCCH in the first OCC group, or sends the PUCCH that collides with the PUSCH in the first OCC group after the PUSCH.

[0089] Taking Figure 9 as an example, if the PUCCH sent by the terminal device in time slot 0 collides with the PUSCH in OCC group 0, the terminal device sends the PUCCH that collides with the PUSCH in OCC group 0 after transmitting the PUSCH of OCC group 0 and OCC group 1.

[0090] In some embodiments, if the PUSCH sent by the terminal device collides with the single-slot PUCCH in the first OCC group, and the terminal device does not have the ability to multiplex UCI on PUSCH, or does not meet the conditions for multiplexing UCI on PUSCH, the terminal device cancels sending PUSCH in the first OCC group.

[0091] Multiplexing UCI on PUSCH means transmitting UCI on PUSCH. Whether the terminal device has the ability to multiplex UCI on PUSCH depends on the capabilities of the terminal device itself or the configuration of the network device, and this application does not limit this. In addition, even if the terminal device has the ability to multiplex UCI on PUSCH, it is necessary to determine whether the terminal device meets the conditions for multiplexing UCI on PUSCH. If the terminal device meets the conditions for multiplexing UCI on PUSCH, UCI can be multiplexed on PUSCH; conversely, if the terminal device does not meet the conditions for multiplexing UCI on PUSCH, UCI cannot be multiplexed on PUSCH. For an introduction to determining whether the terminal device meets the conditions for multiplexing UCI on PUSCH, please refer to the following embodiments.

[0092] Taking Figure 10 as an example, the PUCCH transmitted by the terminal device in time slot 0 collides with the PUSCH in OCC group 0. The PUCCH carries the HARQ-ACK information corresponding to the PDSCH. If the time interval between the last symbol of the PDSCH and the first symbol of the PUSCH in OCC group 0 does not meet the conditions for multiplexing UCI on the PUSCH, the terminal device cancels the transmission of the PUSCH in OCC group 0.

[0093] In some embodiments, if the PUSCH sent by the terminal device collides with the single-slot PUCCH in the first OCC group, and the terminal device does not have the ability to multiplex UCI on the PUSCH, or does not meet the conditions for multiplexing UCI on the PUSCH, the terminal device cancels sending the PUCCH in the first OCC group, or sends the PUCCH that collides with the PUSCH in the first OCC group after the PUSCH.

[0094] In some embodiments, if the PUSCH sent by the terminal device collides with the single-slot PUCCH in the first OCC group, the terminal device sends the PUSCH multiplexed with UCI in the first OCC group.

[0095] In some embodiments, if the PUSCH sent by the terminal device collides with the single-slot PUCCH in the first OCC group, and the terminal device has the ability to multiplex UCI on the PUSCH and meets the conditions for multiplexing UCI on the PUSCH, then the terminal device sends the PUSCH with multiplexed UCI in the first OCC group.

[0096] Taking Figure 11 as an example, the PUCCH transmitted by the terminal device in timeslot 0 collides with the PUSCH in OCC group 0, and the PUCCH carries the HARQ-ACK information corresponding to the PDSCH. If the interval between the last symbol of the PDSCH and the first symbol of the PUSCH in OCC group 0 meets the conditions for multiplexing UCI on the PUSCH, the terminal device transmits the PUSCH with the UCI multiplexed in OCC group 0.

[0097] In some embodiments, the terminal device determines whether the condition for multiplexing UCI on PUSCH is met in the following manner: the terminal device determines whether the condition for multiplexing UCI on PUSCH is met based on the first symbol used for PUSCH transmission in the first OCC group.

[0098] Exemplarily, if the PUSCH sent by the terminal device collides with the single-slot PUCCH in the first OCC group, the PUCCH carries the HARQ-ACK information corresponding to the PDSCH, and the terminal device obtains the time interval between the last symbol of the PDSCH and the first symbol used for PUSCH transmission in the first OCC group, and determines whether the conditions for multiplexing UCI on the PUSCH are met based on the time interval. If the time interval is greater than or equal to a certain threshold, it is determined that the conditions for multiplexing UCI on the PUSCH are met; if the time interval is less than a certain threshold, it is determined that the conditions for multiplexing UCI on the PUSCH are not met. The above thresholds may be agreed upon by the protocol, configured by the network device, pre-configured, or depend on the implementation of the terminal device, and this application does not limit this.

[0099] Taking Figure 12 as an example, a PUCCH transmitted by a terminal device carrying HARQ-ACK information corresponding to the PDSCH collides with a PUSCH transmission in OCC group 0. Although the PUCCH is transmitted in time slot 1, it is still necessary to determine whether OCC group 0 meets the conditions for multiplexing UCI on the PUSCH based on the first symbol used for PUSCH transmission in OCC group 0, that is, the first symbol used for PUSCH transmission in time slot 0. This method can prevent interference between PUSCHs in different time slots within the OCC group.

[0100] Case 2: PUSCH transmission collides with repeated PUCCH transmissions

[0101] In some embodiments, the PUSCH is a PUSCH using type A repetition transmission, or a PUSCH using multi-slot processing TB, or a PUSCH using type B repetition transmission; and the PUCCH is a PUCCH repetition transmission.

[0102] PUSCH retransmission includes two modes: Type A and Type B. This application does not describe these two modes in detail, as they are well known to those skilled in the art.

[0103] In some embodiments, if a PUSCH using type A repeated transmission or a PUSCH using multi-slot processing TB sent by a terminal device collides with a PUCCH repeated transmission in the first OCC group, the terminal device cancels sending the PUSCH in the first OCC group.

[0104] Taking FIG. 13 as an example, if the PUCCH repetition transmission sent by the terminal device collides with the PUSCH transmission in OCC group 0, the terminal device cancels sending the PUSCH repetition transmission in OCC group 0.

[0105] In some embodiments, if the PUSCH using type A repeated transmission or the PUSCH with multi-slot processing TB sent by the terminal device collides with the PUCCH repeated transmission in the first OCC group, the terminal device cancels sending the colliding PUCCH in the first OCC group, or sends the PUCCH that collides with the PUSCH in the first OCC group after the PUSCH.

[0106] In some embodiments, if a PUSCH transmitted by a terminal device using type B repetition transmission collides with a PUCCH repetition transmission in the first OCC group, the terminal device cancels sending the PUSCH in the first OCC group.

[0107] Taking Figure 14 as an example, for PUSCH using Type B repetitions, the terminal device applies OCC between repetitions. If a PUCCH repetition sent by the terminal device collides with a PUSCH transmission in OCC group 0, the terminal device cancels the PUSCH repetition in OCC group 0.

[0108] In some embodiments, if the PUSCH sent by the terminal device using type B repetition transmission collides with the PUCCH repetition transmission in the first OCC group, the terminal device cancels sending the colliding PUCCH in the first OCC group, or sends the PUCCH that collides with the PUSCH in the first OCC group after the PUSCH.

[0109] For the above-mentioned cases 1 and 2, when the PUSCH sent by the terminal device collides with the PUCCH in the first OCC group, the terminal device cancels the sending of the colliding PUSCH or PUCCH in the first OCC group, or sends the colliding PUCCH after the PUSCH, or sends the PUSCH with multiplexed UCI, thereby avoiding the collision between the PUSCH and the PUCCH in the first OCC group. Among them, the terminal device cancels the sending of the colliding PUSCH in the first OCC group to ensure the normal transmission of information on the PUCCH. The terminal device cancels the sending of the colliding PUCCH in the first OCC group to avoid interference of the PUCCH with other multiplexed users. When the PUSCH sent by the terminal device collides with the PUCCH in the first OCC group, the specific method used by the terminal device to adjust the PUSCH transmission in the first OCC group can be agreed upon by the protocol or configured by the network device, and this application does not limit this.

[0110] Next, the PUCCH transmission method within the OCC group is introduced and explained.

[0111] In some embodiments, if the terminal device cancels sending PUSCH in the first OCC group, the terminal device sends PUCCH using OCC in the first OCC group. The OCC sequence used by the terminal device to send PUCCH in the first OCC group may reuse the OCC sequence used to send PUSCH in the first OCC group, or a new set of OCC sequences may be determined, which is not limited in this application.

[0112] Taking Figure 15 as an example, after the terminal device cancels sending PUSCH in OCC group 0, it reuses the orthogonal sequence applied by OCC group 0 to send PUCCH, thereby maintaining the orthogonality between different users in OCC group 0.

[0113] In some embodiments, if the terminal device cancels sending PUSCH in the first OCC group, the terminal device does not expect PUCCHs on different OCC blocks in the first OCC group to collide.

[0114] Taking Figure 16 as an example, PUCCH1 and PUCCH2 sent by the terminal device collide with the PUSCH on time slot 0 and time slot 1 in OCC group 0 respectively. Although the terminal device cancels the transmission of PUSCH in OCC group 0 to avoid collision with PUCCH, when the network device combines and receives the time slots in OCC group 0, PUCCH1 and PUCCH2 will collide. Therefore, it is necessary to stipulate that the terminal device does not expect the PUCCH on time slot 0 and time slot 1 in OCC group 0 to collide.

[0115] In some embodiments, the terminal device sends a PUSCH multiplexed with UCI in the first OCC group, including: the terminal device sends a PUSCH multiplexed with the same UCI on different OCC blocks in the first OCC group.

[0116] Taking Figure 11 as an example, the PUSCH sent by the terminal device on time slot 0 and time slot 1 in OCC group 0 should multiplex the same UCI to ensure that the PUSCHs on these two time slots can be combined and received.

[0117] Through the above method, when the PUSCH sent by the terminal device collides with the PUCCH in the first OCC group, the terminal device sends the PUCCH applying OCC in the first OCC group, and / or does not expect the PUCCH on different OCC blocks in the first OCC group to collide, thereby avoiding the collision of PUCCH in the first OCC group.

[0118] In some embodiments, the first condition is that the PUSCH sent by the terminal device collides with the first symbol. In other words, the PUSCH sent by the terminal device collides with the first symbol in the first OCC group.

[0119] In some embodiments, if the PUSCH sent by the terminal device collides with the first symbol in the first OCC group, the terminal device cancels sending the PUSCH in the first OCC group.

[0120] In some embodiments, for type A PUSCH repetition transmission not based on available time slot count, if the PUSCH sent by the terminal device collides with the first symbol in the first OCC group, the terminal device cancels sending the PUSCH in the first OCC group.

[0121] Taking Figure 17 as an example, the PUSCH retransmission is not based on the available time slot count, and the PUSCH on time slot 0 collides with the downlink symbol, then the terminal device cancels the PUSCH retransmission in OCC group 0.

[0122] In some embodiments, if the PUSCH sent by the terminal device collides with the first symbol in the first OCC group, the terminal device cancels sending the PUSCH in the first OCC group, and / or determines the OCC group based on available time slots.

[0123] In some embodiments, for type A PUSCH repetition transmission based on available time slot count, or PUSCH with multi-time slot processing TB, if the PUSCH sent by the terminal device collides with the first symbol in the first OCC group, the terminal device cancels sending the PUSCH in the first OCC group, and / or determines the OCC group based on the available time slots. The first symbol is a downlink symbol determined based on uplink and downlink configuration information or SSB (Synchronization Signal / PBCH Block) time domain position information.

[0124] Taking Figure 18 as an example, PUSCH retransmission is based on the available time slot count, and if the PUSCH in OCC group 0 collides with the downlink symbol, the terminal device cancels sending the PUSCH in OCC group 0.

[0125] Taking Figure 19 as an example, PUSCH retransmission is based on the available time slot count, and if the PUSCH on time slot 0 collides with the downlink symbol, the terminal device cancels the transmission of the PUSCH on time slot 0 and determines the OCC group based on the uplink available time slots, that is, OCC group 0 contains time slots 1-2, and OCC group 1 contains time slots 3-4.

[0126] In some embodiments, the first symbol is a symbol for the DCI to instruct the terminal device to perform downlink reception, or a downlink symbol indicated by DCI 2_0. DCI 2_0 (DCI Format 2_0) is used to notify the time slot format, COT (Channel Occupancy Time) duration, available RB (Resource Block) set, and search space group switching.

[0127] In some embodiments, if the PUSCH sent by the terminal device collides with the symbol indicated by the DCI for downlink reception by the terminal device, or the downlink symbol indicated by DCI 2_0, in the first OCC group, the terminal device cancels sending the PUSCH in the first OCC group.

[0128] In some embodiments, the terminal device is a half-duplex device, and the first symbol is a symbol where the transmit-receive conversion process is performed.

[0129] In some embodiments, if the terminal device is a half-duplex device, the PUSCH sent by the terminal device collides with the symbol where the transceiver conversion processing is located in the first OCC group, then the terminal device cancels sending the PUSCH in the first OCC group, and / or determines the OCC group based on the available time slot.

[0130] Taking Figure 20 as an example, after the half-duplex terminal device receives the SSB in time slot 0, it performs transceiver conversion in time slot 1, causing the symbol where the transceiver conversion processing is performed to conflict with the PUSCH. The terminal device then cancels the PUSCH on the transmission time slot 1 and determines the OCC group based on the uplink available time slots, that is, OCC group 0 includes time slots 2-3.

[0131] Through the above method, when the PUSCH sent by the terminal device collides with the first symbol in the first OCC group, the terminal device cancels sending PUSCH in the first OCC group and determines the OCC group based on the available time slot, thereby ensuring that the terminal device sends PUSCH at a reasonable uplink symbol position.

[0132] In some embodiments, the first condition is that the PUSCH transmission is cancelled by DCI. If the PUSCH transmission sent by the terminal device in the first OCC group is cancelled by DCI, the terminal device cancels sending the PUSCH in the first OCC group.

[0133] Taking Figure 6 as an example, if the PUSCH on timeslot 0 is canceled by DCI 2_4, the terminal device cancels the transmission of the PUSCH on OCC group 0 (i.e., timeslot 0 and timeslot 1). DCI 2_4 (DCI Format 2_4) is used to notify the terminal device of the cancellation of the PRB (Physical Resource Block) and OFDM symbol of the corresponding UL transmission.

[0134] An embodiment of the present application provides a PUSCH transmission adjustment scheme based on the OCC group, that is, the terminal device adjusts the PUSCH transmission in the OCC group that meets the conditions, thereby clarifying the specific behavior of the terminal device when the PUSCH using the OCC collides with other channels, avoiding signal interference caused by the collision, and improving communication reliability.

[0135] In addition, the technical solution provided in the embodiments of the present application can be applied in the NTN system, and can also be extended to any communication system that uses the OCC solution.

[0136] The following are device embodiments of the present application, which can be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0137] Please refer to Figure 21, which shows a block diagram of an uplink transmission device provided by one embodiment of the present application. This device has the function of implementing the above-mentioned uplink transmission method. The function can be implemented by hardware or by hardware executing corresponding software. This device can be the terminal device described above, or it can be provided in a terminal device. As shown in Figure 21, the device 2100 may include: a processing module 2110.

[0138] The processing module 2110 is used to adjust the PUSCH transmission in the first OCC group. The terminal device determines one or more OCC groups based on the resources occupied by the PUSCH transmission and / or the OCC length, and sends the PUSCH applying the OCC within the one or more OCC groups. The first OCC group is at least one OCC group among the one or more OCC groups.

[0139] In some embodiments, the PUSCH collides with the PUCCH in the first OCC group.

[0140] In some embodiments, the processing module 2110 is used to: cancel sending the PUSCH in the first OCC group; or cancel sending the PUCCH in the first OCC group; or send the PUCCH that collides with the PUSCH in the first OCC group after the PUSCH.

[0141] In some embodiments, the terminal device does not have the ability to multiplex UCI on the PUSCH, or does not meet the conditions for multiplexing UCI on the PUSCH.

[0142] In some embodiments, when the terminal device cancels sending the PUSCH in the first OCC group, the terminal device sends the PUCCH to which the OCC is applied in the first OCC group.

[0143] In some embodiments, the terminal device does not expect PUCCHs on different OCC blocks in the first OCC group to collide.

[0144] In some embodiments, the processing module 2110 is configured to send a PUSCH multiplexed with UCI in the first OCC group.

[0145] In some embodiments, the terminal device has the ability to multiplex UCI on the PUSCH and meets the conditions for multiplexing UCI on the PUSCH.

[0146] In some embodiments, the processing module 2110 is configured to send a PUSCH multiplexed with the same UCI on different OCC blocks in the first OCC group.

[0147] In some embodiments, the processing module 2110 is further configured to determine, based on a first symbol in the first OCC group used for the PUSCH transmission, whether a condition for multiplexing UCI on the PUSCH is met.

[0148] In some embodiments, the OCC group includes multiple OCC blocks, and different OCC blocks in the OCC group correspond to different time domain and / or frequency domain resources, and the terminal device applies OCC between the OCC blocks in the OCC group.

[0149] In some embodiments, the PUCCH is a single PUCCH transmission.

[0150] In some embodiments, the PUSCH is a PUSCH using type A repeated transmission, or a PUSCH using multi-slot processing TB, or a PUSCH using type B repeated transmission; and the PUCCH is a PUCCH repeated transmission.

[0151] In some embodiments, the PUSCH collides with a first symbol in the first OCC group.

[0152] In some embodiments, the processing module 2110 is configured to cancel sending the PUSCH in the first OCC group.

[0153] In some embodiments, the PUSCH is a type A PUSCH repetition transmission that is not based on the available time slot count; or, the first symbol is a symbol indicated by downlink control information DCI indicating that the terminal device is performing downlink reception, or a downlink symbol indicated by DCI 2_0.

[0154] In some embodiments, the processing module 2110 is configured to cancel sending the PUSCH in the first OCC group, and / or determine an OCC group based on available time slots.

[0155] In some embodiments, the PUSCH is a type A PUSCH repeated transmission based on the available time slot count, or a PUSCH with multi-slot processing TB, and the first symbol is a downlink symbol determined based on the uplink and downlink configuration information or SSB time domain position information; or, the terminal device is a half-duplex device, and the first symbol is the symbol where the transmit and receive conversion processing is located.

[0156] In some embodiments, the processing module 2110 is configured to cancel sending the PUSCH in the first OCC group if the PUSCH transmission is cancelled by DCI.

[0157] It should be noted that, when the device provided in the above embodiment realizes its function, it only uses the division of the above-mentioned functional modules as an example. In actual application, the above-mentioned functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0158] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here. For details not described in detail in the embodiment of the device, reference can be made to the above method embodiment.

[0159] Please refer to Figure 22, which shows a schematic diagram of the structure of a terminal device provided by one embodiment of the present application. The terminal device 2200 may include: a processor 2201, a transceiver 2202, and a memory 2203. The processor 2201 is used to implement the various processing functions of the terminal device 2200, such as implementing the functions of the aforementioned processing modules, generating information to be transmitted, processing received information, and controlling transmission and / or reception. The transceiver 2202 is used to implement the transmission and / or reception functions.

[0160] The processor 2201 includes one or more processing cores. The processor 2201 executes various functional applications and information processing by running software programs and modules.

[0161] The transceiver 2202 may include a receiver and a transmitter. For example, the receiver and the transmitter may be implemented as the same wireless communication component, which may include a wireless communication chip and a radio frequency antenna.

[0162] The memory 2203 may be connected to the processor 2201 and the transceiver 2202 .

[0163] The memory 2203 may be used to store a computer program executed by the processor, and the processor 2201 is used to execute the computer program to implement each step in the above method embodiment.

[0164] In some embodiments, the processor 2201 is used to adjust the PUSCH transmission in the first OCC group, and the terminal device determines one or more OCC groups based on the resources occupied by the PUSCH transmission and / or the OCC length, and sends the PUSCH applying the OCC within the one or more OCC groups, and the first OCC group is at least one OCC group among the one or more OCC groups.

[0165] For details not described in detail in this embodiment, please refer to the above embodiments and will not be described in detail here.

[0166] In addition, the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, static access memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0167] The embodiment of the present application also provides a computer-readable storage medium, wherein the storage medium stores a computer program, and the computer program is used to be executed by a processor to implement the above-mentioned uplink transmission method. In some embodiments, the computer-readable storage medium may include: ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives) or an optical disk, etc. Among them, the random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0168] An embodiment of the present application further provides a chip, which includes a programmable logic circuit and / or program instructions, and when the chip is running, is used to implement the above-mentioned uplink transmission method.

[0169] An embodiment of the present application also provides a computer program product, which includes computer instructions stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement the above-mentioned uplink transmission method.

[0170] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0171] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0172] In some embodiments of the present application, "predefined" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, predefined may refer to information defined in a protocol.

[0173] In some embodiments of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, it may include the BLE protocol, the Wi-Fi protocol and related protocols used in future communication systems, and the present application does not limit this.

[0174] In this document, "plurality" refers to two or more. "And / or" describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. The character " / " generally indicates an "or" relationship between the associated objects.

[0175] The term “greater than or equal to” mentioned herein may mean greater than or equal to, or greater than, and the term “less than or equal to” may mean less than or equal to, or less than.

[0176] In addition, the step numbers described in this document only illustrate a possible execution order between the steps. In some other embodiments, the above steps may not be executed in the order of the numbers, such as two steps with different numbers are executed at the same time, or two steps with different numbers are executed in the opposite order of the diagram. The embodiments of the present application are not limited to this.

[0177] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0178] The above description is merely an exemplary embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. An uplink transmission method, characterized in that: The method comprises: The terminal device adjusts the physical uplink shared channel PUSCH transmission in the first orthogonal cover code OCC group. The terminal device determines one or more OCC groups based on the resources occupied by the PUSCH transmission and / or the OCC length, and sends the PUSCH applying the OCC within the one or more OCC groups. The first OCC group is at least one OCC group among the one or more OCC groups.

2. The method according to claim 1, characterized in that The PUSCH collides with a physical uplink control channel PUCCH in the first OCC group.

3. The method according to claim 2, characterized in that The terminal device adjusts PUSCH transmission in the first OCC group, including: The terminal device cancels sending the PUSCH in the first OCC group; or, The terminal device cancels sending the PUCCH in the first OCC group; or, The terminal device sends the PUCCH that collides with the PUSCH in the first OCC group after the PUSCH.

4. The method according to claim 3, characterized in that The terminal device does not have the ability to multiplex uplink control information UCI on the PUSCH, or does not meet the conditions for multiplexing UCI on the PUSCH.

5. The method according to claim 3 or 4, characterized in that In a case where the terminal device cancels sending the PUSCH in the first OCC group, the terminal device sends the PUCCH to which the OCC is applied in the first OCC group.

6. The method according to any one of claims 3 to 5, characterized in that The terminal device does not expect PUCCHs on different OCC blocks in the first OCC group to collide.

7. The method according to claim 2, characterized in that The terminal device adjusts PUSCH transmission in the first OCC group, including: The terminal device sends a PUSCH multiplexed with UCI in the first OCC group.

8. The method according to claim 7, characterized in that The terminal device has the ability to multiplex UCI on the PUSCH and meets the conditions for multiplexing UCI on the PUSCH.

9. The method according to claim 7 or 8, characterized in that The terminal device sending a PUSCH multiplexed with UCI in the first OCC group includes: The terminal device sends a PUSCH multiplexed with the same UCI on different OCC blocks in the first OCC group.

10. The method according to claim 4 or 8, characterized in that The method further comprises: The terminal device determines whether a condition for multiplexing UCI on the PUSCH is met based on the first symbol used for the PUSCH transmission in the first OCC group.

11. The method according to claim 6 or 9, characterized in that The OCC group includes multiple OCC blocks, and different OCC blocks in the OCC group correspond to different time domain and / or frequency domain resources. The terminal device applies OCC between the OCC blocks in the OCC group.

12. The method according to any one of claims 2 to 11, characterized in that The PUCCH is a single PUCCH transmission.

13. The method according to any one of claims 2 to 11, characterized in that The PUSCH is a PUSCH using type A repeated transmission, or a PUSCH using multi-slot transport block TB processing, or a PUSCH using type B repeated transmission; and the PUCCH is a PUCCH repeated transmission.

14. The method according to claim 1, wherein The PUSCH collides with a first symbol in the first OCC group.

15. The method according to claim 14, characterized in that The terminal device adjusts PUSCH transmission in the first OCC group, including: The terminal device cancels sending the PUSCH in the first OCC group.

16. The method according to claim 15, characterized in that The PUSCH is a type A PUSCH repetitive transmission not based on available time slot count; or, The first symbol is a symbol indicated by downlink control information DCI for the terminal device to perform downlink reception, or a downlink symbol indicated by DCI 2_0.

17. The method according to claim 14, characterized in that The terminal device adjusts PUSCH transmission in the first OCC group, including: The terminal device cancels sending the PUSCH in the first OCC group and / or determines an OCC group based on available time slots.

18. The method according to claim 17, characterized in that The PUSCH is a type A PUSCH repeated transmission based on an available time slot count, or a PUSCH of a multi-time slot processing TB; and the first symbol is a downlink symbol determined based on uplink and downlink configuration information or synchronization signal block SSB time domain position information; or, The terminal device is a half-duplex device, and the first symbol is a symbol where the transmitting and receiving conversion processing is performed.

19. The method according to claim 1, wherein The terminal device adjusts PUSCH transmission in the first OCC group, including: If the PUSCH transmission is canceled by DCI, the terminal device cancels sending the PUSCH in the first OCC group.

20. An uplink transmission device, characterized in that: The device comprises: A processing module is used to adjust the physical uplink shared channel PUSCH transmission in the first orthogonal cover code OCC group. The terminal device determines one or more OCC groups based on the resources occupied by the PUSCH transmission and / or the OCC length, and sends the PUSCH applying the OCC within the one or more OCC groups. The first OCC group is at least one OCC group among the one or more OCC groups.

21. The device according to claim 20, characterized in that The PUSCH collides with a physical uplink control channel PUCCH in the first OCC group.

22. The device according to claim 21, characterized in that The processing module is used to: canceling transmission of the PUSCH in the first OCC group; or, canceling transmission of the PUCCH in the first OCC group; or, The PUCCH colliding with the PUSCH in the first OCC group is transmitted after the PUSCH.

23. The device according to claim 22, characterized in that The terminal device does not have the ability to multiplex uplink control information UCI on the PUSCH, or does not meet the conditions for multiplexing UCI on the PUSCH.

24. The device according to claim 22 or 23, characterized in that In a case where the terminal device cancels sending the PUSCH in the first OCC group, the terminal device sends the PUCCH to which the OCC is applied in the first OCC group.

25. The device according to any one of claims 22 to 24, characterized in that The terminal device does not expect PUCCHs on different OCC blocks in the first OCC group to collide.

26. The device according to claim 21, characterized in that The processing module is configured to send a PUSCH multiplexed with UCI in the first OCC group.

27. The device according to claim 26, characterized in that The terminal device has the ability to multiplex UCI on the PUSCH and meets the conditions for multiplexing UCI on the PUSCH.

28. The device according to claim 26 or 27, characterized in that The processing module is configured to send PUSCHs multiplexed with the same UCI on different OCC blocks in the first OCC group.

29. The device according to claim 23 or 27, characterized in that The processing module is further configured to determine, based on a first symbol in the first OCC group used for the PUSCH transmission, whether a condition for multiplexing UCI on the PUSCH is met.

30. The device according to claim 25 or 28, characterized in that The OCC group includes multiple OCC blocks, and different OCC blocks in the OCC group correspond to different time domain and / or frequency domain resources. The terminal device applies OCC between the OCC blocks in the OCC group.

31. The device according to any one of claims 21 to 30, characterized in that The PUCCH is a single PUCCH transmission.

32. The device according to any one of claims 21 to 30, characterized in that The PUSCH is a PUSCH using type A repeated transmission, or a PUSCH using multi-slot transport block TB processing, or a PUSCH using type B repeated transmission; and the PUCCH is a PUCCH repeated transmission.

33. The device according to claim 20, characterized in that The PUSCH collides with a first symbol in the first OCC group.

34. The device according to claim 33, characterized in that The processing module is configured to cancel sending the PUSCH in the first OCC group.

35. The device according to claim 34, characterized in that The PUSCH is a type A PUSCH repetitive transmission not based on available time slot count; or, The first symbol is a symbol indicated by downlink control information DCI for the terminal device to perform downlink reception, or a downlink symbol indicated by DCI 2_0.

36. The device according to claim 33, characterized in that The processing module is configured to cancel sending the PUSCH in the first OCC group and / or determine an OCC group based on available time slots.

37. The device according to claim 36, characterized in that The PUSCH is a type A PUSCH repeated transmission based on an available time slot count, or a PUSCH of a multi-time slot processing TB; and the first symbol is a downlink symbol determined based on uplink and downlink configuration information or synchronization signal block SSB time domain position information; or, The terminal device is a half-duplex device, and the first symbol is a symbol where the transmitting and receiving conversion processing is performed.

38. The device according to claim 20, characterized in that The processing module is configured to cancel sending the PUSCH in the first OCC group if the PUSCH transmission is canceled by the DCI.

39. A terminal device, characterized in that: The terminal device includes a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program to implement the method according to any one of claims 1 to 19.

40. A computer-readable storage medium, characterized in that The storage medium stores a computer program, which is configured to be executed by a processor to implement the method according to any one of claims 1 to 19.

41. A chip, characterized in that: The chip includes a programmable logic circuit and / or program instructions, and when the chip is running, is used to implement the method according to any one of claims 1 to 19.

42. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement the method according to any one of claims 1 to 19.

Images