Wireless communication method, terminal device, and network device

Abstract

Provided are a wireless communication method, a terminal device, and a network device. The wireless communication method comprises: a terminal device receiving configuration information sent by a network device, wherein the configuration information is used for configuring a scheduling parameter of a first PUSCH transmission, the first PUSCH transmission being an OCC-based PUSCH transmission, and the configuration information comprises an OCC-related parameter.

Description

Wireless communication methods, terminal devices, and network devices Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a wireless communication method, terminal device, and network device. Background Technology

[0002] Orthogonal cover code (OCC) technology can improve system capacity, spectral efficiency, and anti-interference capability by generating a set of orthogonal code sequences to spread and encode the signal to be transmitted. Therefore, OCC multiplexing in physical uplink shared channel (PUSCH) transmission can effectively improve the uplink transmission capacity of the system. How to implement PUSCH OCC multiplexing in this scenario is a problem that needs to be solved.

[0003] Summary of the Invention

[0004] This application provides a wireless communication method, terminal device, and network device. The various aspects covered by this application are described below.

[0005] In a first aspect, a wireless communication method is provided, comprising: a terminal device receiving configuration information sent by a network device, the configuration information being used to configure scheduling parameters for a first PUSCH transmission, wherein the first PUSCH transmission is an OCC-based PUSCH transmission, and the configuration information includes OCC-related parameters.

[0006] Secondly, a wireless communication method is provided, comprising: a network device sending configuration information to a terminal device, the configuration information being used to configure scheduling parameters for a first PUSCH transmission, wherein the first PUSCH transmission is an OCC-based PUSCH transmission, and the configuration information includes OCC-related parameters.

[0007] Thirdly, a terminal device is provided, comprising: a first receiving module, configured to receive configuration information sent by a network device, the configuration information being used to configure scheduling parameters for a first PUSCH transmission, wherein the first PUSCH transmission is an OCC-based PUSCH transmission, and the configuration information includes OCC-related parameters.

[0008] Fourthly, a network device is provided, comprising: a first sending module, configured to send configuration information to a terminal device, the configuration information being used to configure scheduling parameters for a first PUSCH transmission, wherein the first PUSCH transmission is an OCC-based PUSCH transmission, and the configuration information includes OCC-related parameters.

[0009] Fifthly, a terminal device is provided, including a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the terminal device to perform some or all of the steps in the method of the first aspect.

[0010] In a sixth aspect, a network device is provided, including a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the network device to perform some or all of the steps in the method of the second aspect.

[0011] Seventhly, embodiments of this application provide a communication system including the aforementioned terminal device and / or network device. In another possible design, the system may further include other devices that interact with the terminal device or network device as described in the embodiments of this application.

[0012] Eighthly, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a computer to perform some or all of the steps in the methods described above.

[0013] Ninthly, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0014] In a tenth aspect, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.

[0015] In this embodiment, the network device can indicate OCC-related parameters to the terminal device in the configuration information. In this way, the terminal device can perform OCC multiplexing of the first PUSCH transmission based on the OCC-related parameters carried in the configuration information when performing the first PUSCH transmission, thereby making OCC-based PUSCH transmission more flexible. Attached Figure Description

[0016] Figure 1 is a system architecture example diagram of a wireless communication system applicable to embodiments of this application.

[0017] Figure 2 is a schematic diagram of the data transmission process based on multiple HARQ processes.

[0018] Figure 3 is a schematic diagram of the retransmission process of the terminal equipment using OCC multiplexing.

[0019] Figure 4 is a schematic diagram of the configuration scheduling process.

[0020] Figure 5 is a schematic diagram of another configuration scheduling process.

[0021] Figure 6 is a flowchart illustrating a wireless communication method provided in an embodiment of this application.

[0022] Figure 7 is a schematic diagram of one possible resource allocation method for the first PUSCH transmission.

[0023] Figure 8 is a schematic diagram of the relationship between CORESET, CCE, and REG.

[0024] Figure 9 is a flowchart illustrating a wireless communication method provided in another embodiment of this application.

[0025] Figure 10 is a flowchart illustrating a wireless communication method according to another embodiment of this application.

[0026] Figure 11 is a flowchart illustrating a wireless communication method according to another embodiment of this application.

[0027] Figure 12 is a flowchart illustrating a wireless communication method provided in another embodiment of this application.

[0028] Figure 13 is a schematic diagram of the structure of the terminal device provided in the embodiment of this application.

[0029] Figure 14 is a schematic diagram of the structure of the network device provided in an embodiment of this application.

[0030] Figure 15 is a schematic structural diagram of the communication device provided in an embodiment of this application. Detailed Implementation

[0031] Communication system architecture

[0032] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System for 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, evolution of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Non-Terrestrial Network (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), and Wireless Fidelity (WF). Fidelity (WiFi), 5th-generation (5G) communication systems or other communication systems, such as future communication systems, such as 6th-generation mobile communication systems, or satellite communication systems.

[0033] Traditional communication systems typically 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 communication but also, 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. The embodiments of this application can also be applied to these communication systems.

[0034] The communication system in this application embodiment can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, and standalone (SA) network deployment scenarios.

[0035] The communication system in this application embodiment can be applied to unlicensed spectrum, which can also be considered as shared spectrum; or, the communication system in this application embodiment can also be applied to licensed spectrum, which can also be considered as dedicated spectrum.

[0036] The embodiments of this application can be applied to NTN systems as well as terrestrial networks (TN) systems. By way of example and not limitation, NTN systems include NR-based NTN systems and Internet of Things (IoT)-based NTN systems. For example, in scenarios where narrowband Internet of Things (NB-IoT) and enhanced machine-type communication (eMTC) access NTN, the system composed of IoT terminal devices and the NTN network can be understood as an IoT-based NTN system.

[0037] This application describes various embodiments in conjunction with network devices and terminal devices. The terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment, etc.

[0038] In the embodiments of this application, the terminal device may be a station (ST) in a WLAN, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, 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 next-generation communication system such as an NR network, or a terminal device in a future evolved public land mobile network (PLMN) network, etc.

[0039] In the embodiments of this application, the terminal device can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as handheld devices with wireless connectivity, in-vehicle devices, etc. The terminal device in the embodiments of this application can be a mobile phone, tablet computer, laptop computer, PDA, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a scheduling entity, providing sidelink signals between terminal devices in V2X or D2D, etc. For example, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices can communicate without relaying communication signals through base stations.

[0040] The network device in this application embodiment can be a device for communicating with a terminal device. This network device can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master MeNB, auxiliary SeNB, multi-mode radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, or a device that performs base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device performing base station functions in future communication systems. Base stations can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0041] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0042] In some deployments, the network device in this application embodiment may refer to a CU or a DU, or the network device may include both a CU and a DU. The gNB may also include an AAU.

[0043] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0044] By way of example and not limitation, in the embodiments of this application, the network device may have mobility characteristics; for example, the network device may be a mobile device. In some embodiments of this application, the network device may be a satellite or a balloon station. For example, the satellite may be a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. In some embodiments of this application, the network device may also be a base station located on land, water, or other similar locations.

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

[0046] For example, Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. As shown in Figure 1, the communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120 (or a communication terminal, terminal). The network device 110 may provide communication coverage for a specific geographical area and may communicate with terminal devices located within that coverage area. For example, the network device may be a satellite.

[0047] Figure 1 illustrates an exemplary network device and two terminal devices. In some embodiments of this 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. This application does not limit this aspect.

[0048] It should be noted that Figure 1 is only an example illustrating the system to which this application applies. Of course, the method shown in the embodiments of this application can also be applied to other systems, such as 6G systems, NR systems, etc., and the embodiments of this application do not specifically limit this.

[0049] In some embodiments of this application, the wireless communication system shown in FIG1 may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), but this application does not limit this.

[0050] To facilitate understanding, some related technical knowledge involved in the embodiments of this application is first introduced. The following related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0051] NTN

[0052] The 3rd Generation Partnership Project (3GPP) is currently researching NTN technology. NTN systems can be broadly understood as a general term for all networks involving flying objects, including satellite communication networks, high-altitude platform systems, and air-to-ground networks. For example, an NTN system can include satellite communication networks, such as low-Earth orbit satellite communication networks.

[0053] NTN can provide communication services to terrestrial users via satellite. Compared to terrestrial communication networks (e.g., terrestrial cellular communication), satellite communication has many unique advantages.

[0054] First, satellite communication is not limited by the user's geographical location. For example, conventional terrestrial communication networks cannot cover areas such as oceans, mountains, and deserts where network equipment cannot be deployed. Alternatively, terrestrial communication networks cannot cover certain areas that are sparsely populated and therefore not covered. However, with satellite communication, since a single satellite can cover a large area of ​​the Earth, and satellites orbit the Earth, theoretically, every corner of the Earth can be covered by satellite communication networks.

[0055] Secondly, satellite communication has significant social value. It can reach remote mountainous areas and impoverished, underdeveloped countries or regions at a relatively low cost, enabling people in these areas to enjoy advanced voice communication and mobile internet technologies. From this perspective, satellite communication helps bridge the digital divide with developed regions and promotes development in those areas.

[0056] Secondly, satellite communication has a long range, and the communication cost does not increase significantly with the increase in communication distance.

[0057] Finally, satellite communication is highly stable and unaffected by natural disasters.

[0058] Communication satellites can be classified according to their orbital altitude, such as LEO satellites, MEO satellites, GEO satellites, and HEO satellites. Currently, research primarily focuses on LEO and GEO satellites.

[0059] With the development and popularization of NTN technology, more and more terminal devices can connect to NTN. As a result, the uplink data volume of NTN will continue to increase, users' demand for the continuity and stability of NTN services will continue to increase, and the demand for enhancing the uplink capacity of NTN will also increase day by day.

[0060] OCC

[0061] OCC (Optical Code Coding) is a spreading and coding technique used in wireless communication. OCC generates a set of orthogonal code sequences to spread and code the signal to be transmitted, thereby improving system capacity, spectral efficiency, and interference immunity. In NTN (Network Narrowing Node) systems, OCC has already been applied in the Physical Uplink Control Channel (PUCCH). Practical results of OCC in PUCCH demonstrate that OCC can perform code division multiplexing on the antenna ports of different terminal devices within the same code division multiplexing (CDM) group, effectively enhancing the uplink capacity of the NTN system. In other words, the practical application of OCC in PUCCH proves the feasibility of OCC multiplexing technology in enhancing the uplink capacity of NTN systems.

[0062] Radio network temporary identifier (RNTI)

[0063] Similar to 4G LTE systems, in 5G NR systems, the identifier assigned to terminal devices by the radio side (base station side) is called the RNTI. The role of the RNTI in the blind detection process of the physical downlink control channel (PDCCH) is mainly reflected in its ability to distinguish between different terminal devices and different message types. As one implementation method, network devices (such as base stations) can use the RNTI to scramble the cyclic redundancy check (CRC) portion of radio channel information (such as control information and / or data). In this way, if the RNTI corresponding to a terminal device is different, even if the terminal device receives the radio channel information, it cannot decode it correctly, thus distinguishing between different terminal devices.

[0064] In 5G NR, terminal devices can use specific RNTIs within a specific control resource set (CORESET) to search for downlink control information (DCI). In some implementations, this specific CORESET can be understood as the search space of the RNTI. That is, the terminal device can use a specific RNTI to blindly detect the PDCCH area carrying the DCI. For example, the terminal device can use a specific RNTI to blindly detect the common search space (CSS), or it can use a specific RNTI to blindly detect the UE-specific search space (USS), etc.

[0065] Hybrid Automatic Repeat Request (HARQ)

[0066] HARQ is a technique that combines Automatic Repeat Request (ARQ) and Forward Error Correction (FEC). For ease of understanding, ARQ and FEC are briefly introduced first. FEC adds redundant information to the data block to be transmitted, enabling the receiver to correct some errors and thus reduce the number of retransmissions. For errors that FEC cannot correct, the receiver needs to request the sender to retransmit the data block according to the ARQ mechanism. For example, the sender can add a CRC segment to the data block to be transmitted, so that the receiver can check the CRC segment to determine whether the received data is erroneous. In some embodiments, if the receiver determines that the data block is not erroneous, it can send an acknowledgment (ACK) to the sender, and then the sender continues to send new data. In some embodiments, if the receiver determines that the data block is erroneous, it can send a non-acknowledgment (NACK) to the sender, and then the sender retransmits the same data. In some embodiments, if the sender does not receive a reply from the receiver within a specified time, the sender considers the transmission to have failed, and in this case, the sender will automatically retransmit the same data.

[0067] As an example, the Media Access Control (MAC) layer can append a CRC segment to the end of the data sent to the Radio Link Control (RLC) layer so that the RLC layer can check it to determine if the received data is erroneous. If there is no error, the RLC layer can reply with an ACK to the MAC layer, after which the MAC layer can send new data. If there is an error, the RLC layer can reply with a NACK to the MAC layer, after which the MAC layer can retransmit the same data.

[0068] HARQ combines FEC and ARQ, or in other words, it's a hybrid retransmission request method. When the sender and receiver transmit data based on HARQ, the receiver can store previously received data. This allows the receiver to combine the retransmitted data with the previously received data before decoding; this process is also known as soft combining. Compared to ARQ, HARQ offers diversity gain, reducing the number of retransmissions and thus lowering transmission latency. This is because traditional ARQ simply discards erroneous data rather than storing it, and it lacks a soft combining process. Therefore, ARQ has no diversity gain, potentially requiring more retransmissions and resulting in relatively longer transmission latency.

[0069] HARQ can use a stop-and-wait protocol to send data. That is, the sender pauses and waits for acknowledgment after sending each transport block (TB). In this scenario, a single-process HARQ results in low transmission efficiency. Therefore, communication systems typically use multiple stop-and-wait processes, i.e., multiple HARQ processes, for data transmission. In scenarios using multiple HARQ processes for data transmission, while one HARQ process is waiting for acknowledgment, the sender can use another HARQ process to continue sending data. The process of multiple HARQ processes using the stop-and-wait protocol is described below with reference to Figure 2.

[0070] As shown in Figure 2, assume there are five transport blocks to be transmitted: transport blocks 1, 2, 3, 4, and 5. Figure 2 illustrates three transmission processes. In the first transmission, the sender transmits transport blocks 1, 2, and 3, using HARQ processes 0, 1, and 2 respectively. Transport block 1 encounters a transmission error in the first transmission, so it initiates the HARQ retransmission mechanism in the second transmission. Therefore, in the second transmission, the sender transmits transport blocks 1, 4, and 5, using HARQ processes 0, 1, and 2 respectively. Transport block 1 again encounters a transmission error in the second transmission, so it initiates the HARQ retransmission mechanism again in the third transmission. Therefore, in the third transmission, the sender transmits transport block 1, still using HARQ process 0. After the third transmission, transport blocks 1, 2, 3, 4, and 5 are all successfully transmitted.

[0071] HARQ processes can include synchronous HARQ processes and asynchronous HARQ processes. For example, in a 5G NR system, HARQ processes can include both synchronous and asynchronous HARQ processes. The process IDs of asynchronous HARQ processes and synchronous HARQ processes are described below.

[0072] The process number of an asynchronous HARQ process can be indicated by the HARQ process number (HPN) field in the corresponding DCI. As shown in Table 1, the DCI used for scheduling PUSCH has an HPN field, and different values ​​of the HPN field correspond to different HARQ processes. In this way, the sender can efficiently retransmit data using the stop-and-wait protocol based on the HPN indicated in the DCI. The HPN field shown in Table 1 occupies 4 bits, indicating that the DCI can indicate a maximum of 16 HARQ processes, such as HARQ processes 0-15.

[0073] Table 1

[0074] In some embodiments, asynchronous HARQ processes can correspond to dynamic scheduling.

[0075] The process number of the synchronous HARQ process can be calculated by the sender using a formula. In some embodiments, the calculation of the synchronous HARQ process process number is associated with information such as the first symbol of the PUSCH scheduling and the PUSCH transmission period. For example, the sender can calculate the process number of the synchronous HARQ process based on the current symbol, the higher-layer configuration, and the corresponding formula. As an example, when PUSCH transmission begins, the sender (such as a terminal device) can calculate the HPN corresponding to the current PUSCH based on the formula in 3GPP protocol TR38.321 5.4.1. As an example, for uplink grant scheduling without harqProcID-Offset2 or cg-RetransmissionTimer configuration, the formula for calculating the synchronous HARQ process number corresponding to the PUSCH is as follows: HPN = [floor(CURRENT_symbol / periodicity)]modulo nrofHARQ―Process

[0076] Where CURRENT_symbol represents the time-domain start symbol of PUSCH, periodicity represents the PUSCH transmission period, and nrofHARQ_Process represents the number of HARQ processes. For a detailed explanation of the above formulas, please refer to the relevant protocols (such as the 3GPP protocol), which will not be elaborated upon here.

[0077] In some embodiments, the synchronous HARQ process can correspond to a semi-static scheduling approach based on configured grants (CG).

[0078] In some embodiments, all terminal devices that perform OCC multiplexing in the same CDM group have the same time domain symbol. Therefore, when calculating the HARQ process number according to the synchronous HARQ process, the HPN in the same CDM group is consistent.

[0079] In some embodiments, a control channel element (CCE) in the PDCCH can be used to indicate a terminal device. In this case, it can be assumed that each terminal device is equipped with an HPN. In this scenario, retransmissions of terminal devices multiplexed by OCC within the same CDM group need to be performed synchronously. However, if a terminal device receives an ACK, it does not need to perform synchronous retransmission, as shown in Figure 3. As shown in Figure 3, terminal devices 1 to 4 are OCC-multiplexed terminal devices in the same CDM group. In the first transmission, terminal devices 1 and 4 transmit successfully and do not need to perform synchronous retransmissions. However, terminal devices 2 and 3 fail to transmit and need to perform synchronous retransmissions in the second transmission. In the second transmission, terminal device 2 transmits successfully, while terminal device 3 fails. Therefore, in the third transmission, only terminal device 3 performs a retransmission.

[0080] Configured scheduling (CS)

[0081] In 5G NR systems, resource scheduling for terminal devices can be performed through configuration scheduling. In this mechanism, network devices (such as gNBs) can schedule PDSCH / PUSCH transmissions without using DCI in every transmission. That is, network devices can configure all scheduling parameters for terminal devices in radio resource control (RRC) signaling, and both the network device and the terminal device should transmit data on the PDSCH and PUSCH according to the parameters specified in the RRC signaling. This approach helps network devices reduce the scheduling load at the physical layer and MAC layer.

[0082] However, one drawback of the above mechanism is that network devices cannot change the scheduling parameters of a single transmission. Therefore, wireless link adaptation may encounter some problems when channel conditions become very bad.

[0083] In some embodiments, uplink configuration authorization involves two different types of configuration scheduling processes in the uplink: Type 1 configuration scheduling and Type 2 configuration scheduling. The processes for these two types of configuration scheduling are described below with reference to Figures 4 and 5.

[0084] Figure 4 is a schematic diagram of the configuration scheduling process for Type 1. As shown in Figure 4, the configuration scheduling process for Type 1 may include steps S410 and S420.

[0085] In step S410, the network device sends an RRC configuration to configure the parameters required for PUSCH scheduling.

[0086] In some embodiments, network devices can configure all the parameters required for PUSCH scheduling to end devices via RRC configuration.

[0087] In step S420, the terminal device performs PUSCH transmission based on the RRC configuration sent by the network device.

[0088] In some embodiments, once the terminal device has processed the RRC configuration, it will send a PUSCH without any specific low-level trigger (such as a DCI trigger).

[0089] Figure 5 is a schematic diagram of the configuration scheduling process for Type 2. As shown in Figure 5, the configuration scheduling process for Type 2 may include steps S510 to S530.

[0090] In step S510, the network device sends an RRC configuration to configure the parameters required for PUSCH scheduling.

[0091] In some embodiments, network devices can configure all the parameters required for PUSCH scheduling to end devices via RRC configuration.

[0092] In step S520, the network device sends a DCI to activate the RRC configuration of step S510.

[0093] In some embodiments, when a network device wants to begin authorizing (or scheduling) a PUSCH, the network device may send a DCI to activate the aforementioned RRC configuration.

[0094] In some embodiments, the DCI is scrambled using configured scheduling RNTI (CS-RNTI).

[0095] In step S530, the terminal device performs PUSCH transmission based on the RRC configuration sent by the network device.

[0096] In some embodiments, once the terminal device has processed the DCI, it can send the PUSCH according to the RRC configuration described above.

[0097] It should be noted that the difference between configuration scheduling of type 1 and type 2 lies in whether or not there is authorization to send PUSCH according to RRC configuration (i.e., step S520). It should also be noted that for both type 1 and type 2 configuration scheduling, the terminal device must monitor the PDCCH to prevent network devices from sending other types of DCI.

[0098] As described above, OCC multiplexing in PUSCH transmission can effectively improve the uplink transmission capacity of a system (such as an NTN system). Therefore, how to implement OCC multiplexing of PUSCH in this scenario is a problem that needs to be solved.

[0099] To address the aforementioned problems, this application provides a wireless communication method, terminal device, and network device capable of realizing PUSCH OCC multiplexing based on OCC-related parameters. The method embodiments of this application will be described below.

[0100] Figure 6 is a schematic flowchart of a wireless communication method provided in an embodiment of this application. The method shown in Figure 6 is described from the perspective of interaction between a terminal device and a network device, which can be, for example, the terminal device 120 and the network device 110 shown in Figure 1. In some embodiments, the embodiments of this application can be applied to an NTN system, but the embodiments of this application are not limited thereto. For example, the embodiments of this application can be applied to a TN system.

[0101] The method shown in Figure 6 may include step S610, which will be described below.

[0102] In step S610, the terminal device receives configuration information sent by the network device.

[0103] In this embodiment, the configuration information can be used to configure (or indicate) the scheduling parameters for the first PUSCH transmission. Alternatively, the configuration information can be used to schedule the first PUSCH transmission. In some embodiments, the configuration information can be used to configure CG parameters (or semi-static scheduling parameters). In some embodiments, the configuration information can be used to configure dynamic grant (DG) parameters.

[0104] In this embodiment, the first PUSCH transmission is an OCC-based PUSCH transmission. That is, when the terminal device performs the first PUSCH transmission, it can achieve OCC multiplexing through OCC technology, so that it can perform code division multiplexing of antenna ports on the same time and frequency resources as other terminal devices, effectively enhancing the uplink capacity of the system.

[0105] In some embodiments, the first PUSCH transfer may be performed based on pre-configured uplink resources (such as CG resources). In some embodiments, the first PUSCH transfer may be performed based on dynamically scheduled uplink resources (such as DG resources).

[0106] In some embodiments, the configuration information may include (or carry) OCC-related parameters. In this way, the terminal device can perform OCC multiplexing of the first PUSCH transmission based on the OCC-related parameters carried in the configuration information when performing the first PUSCH transmission, thereby helping to ensure more flexible OCC-based PUSCH transmission.

[0107] This application does not specifically limit the OCC-related parameters, as long as the parameters are related to the OCC multiplexing of the first PUSCH. For example, the OCC-related parameters may include one or more of the following: OCC scheme, OCC length, OCC codeword table, and OCC codeword index.

[0108] The OCC scheme can be used to indicate the implementation method of OCC multiplexing, that is, the OCC scheme can be used to indicate how to implement OCC multiplexing of the first PUSCH transmission. This application does not limit the OCC scheme; for example, the OCC scheme may include one or more of the following: a cross-symbol OCC scheme, a cross-timeslot OCC scheme, and an intra-symbol OCC scheme.

[0109] In a cross-symbol OCC scheme, each symbol can be repeated M times, where M is the number of multiplexing terminal devices. That is, one original symbol can be repeated M times in the time domain, becoming M symbols. Then, each repeated symbol is superimposed with its OCC codeword to achieve OCC multiplexing for the first PUSCH transmission. Taking OCC multiplexing with 4 terminal devices as an example, in a cross-symbol OCC scheme, each symbol can be repeated 4 times, and each repeated symbol is superimposed with its OCC codeword.

[0110] In a cross-timeslot OCC scheme, each time slot can be repeated M times, where M is the number of multiplexed terminal devices. That is, an original time slot can be repeated M times in the time domain, becoming M time slots. Then, each repeated time slot is superimposed with OCC codewords to achieve OCC multiplexing of the first PUSCH transmission. Taking OCC multiplexing with 4 terminal devices as an example, in a cross-timeslot OCC scheme, each time slot can be repeated 4 times, and each repeated time slot is superimposed with OCC codewords.

[0111] Intra-symbol OCC schemes can utilize the oversampling property of the Discrete Fourier Transform (DFT) to comb-map the data from terminal devices onto different subcarriers of a symbol. In other words, a frequency domain resource unit (such as a resource block) can be repeated M times in the frequency domain before the DFT operation, where M is the number of multiplexed terminal devices. Then, after the DFT, the data corresponding to different values ​​in the OCC sequence (such as a Walsh sequence) can be comb-mapped onto the subcarriers of that frequency domain resource unit. Taking OCC multiplexing with four terminal devices as an example, in the intra-symbol OCC scheme, a resource block can be repeated M times in the frequency domain before the DFT operation, and then, after the DFT, the data corresponding to different values ​​in the OCC sequence can be comb-mapped onto the subcarriers of that resource block.

[0112] In some embodiments, the OCC scheme may use equal-length sequence groups, or the OCC scheme may use unequal-length sequence groups, which is not limited in this application.

[0113] The OCC length can be used to indicate the length of an OCC codeword (or OCC sequence), that is, the OCC length can be used to indicate the number of OCC codewords applied on a specific physical resource. For example, the OCC length can include one or more of the following: 2, 4, 8. However, this application embodiment is not limited to this; the OCC length can also be any other arbitrary value, for example, the OCC length can also be 16, 32, etc.

[0114] The OCC codeword table can be used to indicate the mapping relationship between the OCC codeword index and the OCC codewords, so that the terminal device can determine the codeword corresponding to the first PUSCH transmission based on the OCC codeword table. For example, the terminal device can determine the codeword corresponding to the first PUSCH transmission based on the OCC codeword index and the OCC codeword table.

[0115] This application does not limit the sequence used to generate OCC codewords. For example, OCC codewords can be generated based on one or more of the following sequences: Walsh sequence, Gold sequence, Zadoff-Chu sequence, pseudo-random code, etc.

[0116] The following example uses the method of generating OCC codewords based on Walsh sequences, and provides an example of an OCC codeword table in conjunction with Table 2.

[0117] Table 2

[0118] The OCC codeword index can be used by the terminal device to determine the codeword corresponding to the first PUSCH transmission. For example, the terminal device can query the OCC codeword index table based on the OCC codeword index to determine the codeword corresponding to the first PUSCH transmission. Taking the OCC codeword table shown in Table 2 as an example, the range of the OCC codeword index corresponding to this OCC codeword table is 0-13. Assuming that the OCC codeword index indicated in the configuration information is 7, the terminal device can determine the codeword corresponding to the first PUSCH transmission as [1 -1 1 -1 1 -1 1 -1] based on the OCC codeword index and the OCC codeword table.

[0119] In some embodiments, the above configuration information may be carried in RRC signaling. In other words, the above configuration information may be RRC configuration.

[0120] In some embodiments, the network device can send multiple sets of configuration information to the terminal device. These multiple sets of configuration information are used to configure multiple sets of scheduling parameters for the first PUSCH transmission. For example, the network device can configure multiple sets of CG parameters for the terminal device. In this scenario, each set of configuration information can include OCC-related parameters.

[0121] In some embodiments, the above configuration information can be applied to configuration scheduling (or semi-static scheduling) scenarios. For example, the above configuration information can be applied to type 1 configuration scheduling and / or type 2 configuration scheduling scenarios. In some embodiments, the above configuration information can be applied to dynamic scheduling scenarios.

[0122] In some embodiments, when the above configuration information is applied to a type 2 configuration scheduling or dynamic scheduling scenario, the method shown in FIG6 may further include step S620. In step S620, the terminal device receives a first signaling sent by the network device.

[0123] In some embodiments, the first signaling can be used to activate and / or activate the configuration information for executing the first PUSCH transmission; that is, the first signaling can be used to activate and / or activate the configuration information in step S610. In other words, the first signaling can be used to authorize the terminal device to execute the first PUSCH transmission based on the configuration information in step S610. For example, in a configuration scheduling scenario of type 2, the first signaling can be used to activate and / or activate the configuration information for executing the first PUSCH transmission.

[0124] In some embodiments, the first signaling can be used to schedule the terminal device to perform a first PUSCH transmission. For example, in a dynamically scheduled scenario, the first signaling can be used to schedule the terminal device to perform a first PUSCH transmission.

[0125] In some embodiments, the first signaling can be DCI signaling. This application does not limit the format of the first signaling; taking DCI signaling as an example, the first signaling can be DCI format 0_0.

[0126] In some embodiments, the first signaling may be carried on the PDCCH.

[0127] This application does not specifically limit the information carried in the first signaling. For example, the first signaling may carry the identifier of the CDM group (see the embodiments below). Alternatively, the first signaling may carry uplink authorization information (such as activation or deactivation indication). Or, the first signaling may carry parameters related to time-domain resources, frequency-domain resources, modulation and coding schemes, etc.

[0128] As can be seen, in some scenarios, the execution of the first PUSCH transmission may depend on the channel carrying the first signaling (such as PDCCH), which may limit the OCC multiplexing of the first PUSCH transmission due to the limited capacity of the channel carrying the first signaling. For example, in a scenario where the first PUSCH transmission is executed based on type 2 configuration scheduling, the network device needs to send the first signaling to the terminal device to activate and / or deactivate the configuration information for executing the first PUSCH transmission. Therefore, the capacity of the channel carrying the first signaling may limit the OCC multiplexing of the first PUSCH transmission. As another example, in a scenario where the first PUSCH transmission is executed based on dynamic scheduling, the network device needs to send the first signaling to the terminal device to schedule the execution of the first PUSCH transmission. Therefore, the capacity of the channel carrying the first signaling may limit the OCC multiplexing of the first PUSCH transmission. The following example, using DCI signaling as the first signaling and a cross-timeslot OCC scheme, illustrates this problem.

[0129] As shown in Figure 7, it is assumed that the resource usage during the first PUSCH transmission process is 24 physical resource blocks (PRBs) and 4 time slots. In the scenario using the cross-time slot OCC scheme, 4 terminal devices can be reused at the same physical resource location.

[0130] Assume that the resources occupied by the PDCCH transmission are the same as those occupied by the first PUSCH transmission, namely 24 PRBs and 4 time slots. When the network device activates and / or deactivates the configuration information for executing the first PUSCH transmission through the first signaling, or executes the first PUSCH transmission through the first signaling scheduling (dynamic scheduling), the network device can send the first signaling to the terminal device through the PDCCH.

[0131] In some embodiments, the first signaling may include information such as uplink and downlink resource allocation, HARQ information, and power control.

[0132] In some embodiments, the first signaling can be carried by CORESET in PDCCH. As shown in Figure 8, the time domain width of CORESET can be 3 orthogonal frequency division multiplexing (OFDM) symbols. The basic unit of CORESET is CCE, and each CCE includes 6 resource element groups (REGs).

[0133] In some embodiments, the PDCCH can consist of n consecutive CCEs, where n is the degree of aggregation. The degree of aggregation can be used to indicate the number of CCEs required by a terminal device. The correspondence between the degree of aggregation and CCEs is given below with reference to Table 3.

[0134] Table 3

[0135] As shown in Table 3, the aggregation degree can take one of the following values: 1, 2, 4, 8, or 16. A higher aggregation degree requires more CCEs for each terminal device. For example, with an aggregation degree of 1, each terminal device needs one CCE for indication. Similarly, with an aggregation degree of 2, each terminal device needs two CCEs for indication. In some embodiments, a higher aggregation degree results in more reliable DCI demodulation.

[0136] In a scenario where four terminal devices perform OCC multiplexing transmission, taking an aggregation degree of 1 as an example, when the PDCCH transmission occupies 24 PRBs and 4 time slots, the number of terminal devices that the PDCCH can serve is 24 * 4 = 96. Therefore, 96 CCEs are needed for indication. Considering that each CORESET can include a maximum of 12 CCEs, 96 CCEs require 8 CORESETs, which consumes approximately 43% of the PDCCH resources. This can lead to limited downlink capacity of the PDCCH or even a shortage of PDCCH resources.

[0137] To address the aforementioned issues, embodiments of this application propose using first signaling to activate and / or deactivate the configuration information of a terminal device group, or to schedule the terminal device group to perform first PUSCH transmission. For example, in a type 2 configuration scheduling scenario, the network device can use first signaling to activate and / or deactivate the configuration information of the terminal device group. As another example, in a dynamic scheduling scenario, the network device can use first signaling to schedule the terminal device group to perform first PUSCH transmission. This will be described in detail below.

[0138] In some embodiments, the aforementioned terminal device group can be a CDM group. That is, embodiments of this application can utilize the first signaling to activate and / or deactivate the configuration information of all terminal devices within a CDM group at the CDM group level; or, embodiments of this application can utilize the first signaling to schedule all terminal devices within a CDM group to perform the first PUSCH transmission at the CDM group level.

[0139] In some embodiments, the first signaling may be used to instruct one or more of the following: activate configuration information for one or more CDM groups to perform the first PUSCH transmission, deactivate configuration information for one or more CDM groups to perform the first PUSCH transmission, or schedule one or more CDM groups to perform the first PUSCH transmission.

[0140] As an example, the first signaling can be used to activate configuration information for one or more CDM groups to perform the first PUSCH transmission.

[0141] As another example, the first signaling can be used to deactivate the configuration information for one or more CDM groups to perform the first PUSCH transmission.

[0142] As yet another example, the first signaling can be used to schedule one or more CDM groups to perform the first PUSCH transfer.

[0143] In some embodiments, in a configuration scheduling scenario of type 2, the first signaling can be used to activate and / or deactivate configuration information for one or more CDM groups to perform the first PUSCH transmission.

[0144] In some embodiments, in a dynamically scheduled scenario, the first signaling can be used to schedule one or more CDM groups to perform a first PUSCH transmission.

[0145] In some embodiments, when the first signaling is used to activate and / or deactivate the configuration information of the terminal device group, or when the first signaling is used to schedule the terminal device group to perform the first PUSCH transmission, the configuration information sent by the network device to the terminal device (i.e., the configuration information in step S610) may also include one or more of the following information: the identifier of the CDM group to which the terminal device belongs, the first RNTI, and the mapping relationship between the CDM group and the PDCCH search space set.

[0146] The identifier of the CDM group to which the terminal device belongs can be used to identify the CDM group to which the terminal device belongs. In this way, when the network device activates and / or deactivates the configuration information of the CDM group, or when the network device schedules the CDM group to perform the first PUSCH transmission, the terminal device can determine whether it needs to activate and / or deactivate the configuration information based on the network device's instruction, or whether it needs to perform the first PUSCH transmission based on the network device's instruction, based on the identifier of the CDM group to which the terminal device belongs.

[0147] In some embodiments, the value range of the identifier of the CDM group to which the terminal device belongs is related to the number of data bits of the CDM group identifier in the first signaling. Taking a data bit length of 4 bits for the CDM group identifier in the first signaling as an example, the value range of the identifier of the CDM group to which the terminal device belongs can be 0-15. Taking a data bit length of 5 bits for the CDM group identifier in the first signaling as an example, the value range of the identifier of the CDM group to which the terminal device belongs can be 0-31.

[0148] The first RNTI can be used to scramble and / or descramble the PDCCH for scheduling the first PUSCH transmission. In some embodiments, the first RNTI can be an RNTI specifically for scheduling the first PUSCH transmission; therefore, in some embodiments, the first RNTI can also be understood or referred to as the OCC-RNTI, specifically for scheduling the first PUSCH transmission.

[0149] In some embodiments, the first RNTI is configured at the granularity of CDM groups. That is, terminal devices within the same CDM group have the same first RNTI.

[0150] In some embodiments, the first RNTI corresponding to different CDM groups may be different. In some embodiments, the first RNTI corresponding to different CDM groups may be the same.

[0151] In some embodiments, the maximum number of CDM groups that a first RNTI can accommodate is related to the number of data bits for the CDM group identifier in the first signaling; in other words, the maximum number of CDM groups that a first RNTI can accommodate is determined by the number of data bits for the CDM group identifier in the first signaling. For example, if the number of data bits for the CDM group identifier in the first signaling is 4, this means that a first RNTI can be used for the activation and / or deactivation of 16 CDM groups. For example, if the number of data bits for the CDM group identifier in the first signaling is 5, this means that a first RNTI can be used for the activation and / or deactivation of 32 CDM groups.

[0152] In some embodiments, the mapping relationship between CDM groups and PDCCH search space sets is designed to ensure that different CDM groups with the same first RNTI can be configured with different PDCCH search space sets so as to identify different CDM groups through the PDCCH search space sets.

[0153] In some embodiments, different CDM groups may correspond to different PDCCH search space sets. For example, different CDM groups with the same first RNTI may correspond to different PDCCH search space sets to identify different CDM groups through the PDCCH search space set. Alternatively, the mapping relationship between CDM groups and PDCCH search space sets may be a one-to-one mapping relationship to uniquely identify CDM groups through the PDCCH search space set.

[0154] In some embodiments, the mapping relationship between CDM groups and PDCCH search space sets is indicated by the mapping relationship between the identifiers of CDM groups and the identifiers of PDCCH search space sets.

[0155] This application does not limit how to activate and / or deactivate the configuration information of the CDM group based on the first signaling, or how to schedule the CDM group based on the first signaling. The following examples, using type 2 configuration scheduling and dynamic scheduling scenarios, provide several implementation methods.

[0156] Example 1: The first signaling implements the activation and / or deactivation of the configuration information of the CDM group.

[0157] Example 1 can be applied to a configuration scheduling scenario of type 2. In the configuration scheduling scenario of type 2, after receiving the configuration information sent by the network device, the terminal device does not immediately execute the first PUSCH transmission. Instead, it only starts uplink transmission after receiving the first signaling instruction to activate the configuration information. That is, in Example 1, the network device can activate and / or activate the configuration information for all terminal devices in the CDM group to execute the first PUSCH transmission based on the first signaling. The first signaling may carry uplink authorization information (such as activation or deactivation instructions) and may also include information such as time domain resources, frequency domain resources, modulation and coding schemes.

[0158] Example 1 enables the activation and / or deactivation of CDM group configuration information, thereby alleviating the problem of limited downlink resources.

[0159] As one implementation, Embodiment 1 may explicitly indicate the CDM groups that need to be activated and / or deactivated. As another implementation, Embodiment 1 may implicitly indicate the CDM groups that need to be activated and / or deactivated. This application does not limit the manner in which Embodiment 1 implicitly indicates the CDM groups that need to be activated and / or deactivated. For example, the network device may implicitly indicate the CDM groups that need to be activated and / or deactivated through one or more of the following: a first RNTI, PDCCH search space set.

[0160] The implementation of Example 1 will be described below.

[0161] Implementation Method 1: The first signaling explicitly indicates which CDM groups need to be activated and / or deactivated.

[0162] In implementation method 1, when the network device sends configuration information to the terminal device, the configuration information may include OCC-related parameters and the identifier of the CDM group to which the terminal device belongs. Of course, in addition to OCC-related parameters and the identifier of the CDM group to which the terminal device belongs, the configuration information may also include other information, such as the first RNTI.

[0163] In implementation method 1, terminal devices within the same CDM group share the same first RNTI, while first RNTIs for different CDM groups can be the same or different. In other words, the maximum number of CDM groups that a single first RNTI can accommodate is related to the number of data bits for the CDM group identifier in the first signaling. For example, if the number of data bits for the CDM group identifier in the first signaling is 4, this means that one first RNTI can be used for the activation and / or deactivation of 16 CDM groups. For example, if the number of data bits for the CDM group identifier in the first signaling is 5, this means that one first RNTI can be used for the activation and / or deactivation of 32 CDM groups.

[0164] Subsequently, the network device can send a first signaling message to the terminal device to activate configuration information for one or more CDM groups to perform the first PUSCH transmission. In implementation 1, the first signaling message may include (or carry) the identifier of the first CDM group.

[0165] In some embodiments, the first CDM group is the CDM group that needs to be activated. In some embodiments, the first CDM group can be any one or more CDM groups, and this application embodiment is not limited in this respect.

[0166] In some embodiments, the first signaling may include other information besides the identifier of the first CDM group. For example, the first signaling may include uplink grant information, such as one or more of information including time domain resources, frequency domain resources, modulation and coding schemes, etc.

[0167] In some embodiments, if the identifier of the first CDM group includes the identifier of the CDM group to which the terminal device belongs, the terminal device activates the configuration information for executing the first PUSCH transmission. Taking the first signaling being scrambled via the first RNTI as an example, if the terminal device successfully descrambles the received first signaling using the first RNTI configured for it, the terminal device needs to compare the identifier of the first CDM group carried in the first signaling with the identifier of the CDM group configured for the terminal device by the network device to determine whether the identifier of the first CDM group includes the identifier of the CDM group to which the terminal device belongs, so as to determine whether the configuration information for executing the first PUSCH transmission needs to be activated based on the comparison results.

[0168] The identifier for a CDM group configured with network devices as terminal devices is idxCDM. UE The identifier for the first CDM group is idxCDM. A For example, after the terminal device successfully descrambles the first signaling message, it needs to extract the idxCDM carried in the first signaling message. A With the network device pre-configured idxCDM UE Perform a comparison. If idxCDM UE =idxCDM A And if the first signaling is used to indicate the configuration information for activating the first PUSCH transmission, then the terminal device activates the configuration information for the first PUSCH transmission.

[0169] Since the terminal devices in the same CDM group are configured with the same first RNTI, and the CDM group identifiers of the terminal devices participating in OCC multiplexing in the same CDM group are the same, the terminal devices participating in OCC multiplexing in the same CDM group will realize the activation of the first PUSCH transmission based on the CDM group, without the network device needing to send activation indication signaling separately for each terminal device.

[0170] In some embodiments, after the terminal device activates the configuration information for the first PUSCH transmission based on the first signaling, it can perform the first PUSCH transmission based on the configuration information.

[0171] In some embodiments, after OCC multiplexing ends, the network device may send a first signaling message to the terminal device to deactivate the configuration information for one or more CDM groups to perform the first PUSCH transmission. In implementation 1, the first signaling message may include (or carry) the identifier of the first CDM group.

[0172] In some embodiments, the first CDM group is a CDM group that needs to be deactivated. In some embodiments, the first CDM group can be any one or more CDM groups that are already activated, and this application embodiment is not limited in this respect.

[0173] In some embodiments, if the identifier of the first CDM group includes the identifier of the CDM group to which the terminal device belongs, the terminal device deactivates the configuration information for performing the first PUSCH transmission. Taking the first signaling scrambled via the first RNTI as an example, if the terminal device successfully descrambles the received first signaling using the first RNTI configured for it, the terminal device needs to compare the identifier of the first CDM group carried in the first signaling with the identifier of the CDM group configured for the terminal device by the network device to determine whether the identifier of the first CDM group includes the identifier of the CDM group to which the terminal device belongs, so as to determine whether the configuration information for performing the first PUSCH transmission needs to be deactivated based on the comparison result.

[0174] The identifier for a CDM group configured with network devices as terminal devices is idxCDM. UE The identifier for the first CDM group is idxCDM. A For example, after the terminal device successfully descrambles the first signaling message, it needs to extract the idxCDM carried in the first signaling message. A With the network device pre-configured idxCDM UE Perform a comparison. If idxCDM UE =idxCDM A If the first signaling is used to instruct the deactivation of the configuration information for the first PUSCH transmission, then the terminal device will deactivate the configuration information for the first PUSCH transmission.

[0175] Implementation Method 2: Based on the implicit indication of the first RNTI of the CDM group that needs to be activated and / or deactivated

[0176] In implementation method 2, when the network device sends configuration information to the terminal device, the configuration information may include OCC-related parameters and the first RNTI.

[0177] In implementation method 2, there is a one-to-one correspondence between the first RNTI and the CDM group, that is, one CDM group corresponds to one first RNTI (or, each CDM group corresponds to a different first RNTI). In this way, different first RNTIs can represent different CDM groups, so that the terminal device can determine the CDM group that the first signaling instruction is activated and / or deactivated based on the first RNTI.

[0178] In implementation method 2, the first RNTI is the same for each terminal device within the same CDM group.

[0179] Subsequently, the network device can send a first signaling message to the terminal device to activate the configuration information for one or more CDM groups to perform the first PUSCH transmission. In implementation method 2, the format of the first signaling message does not need to be changed compared to the current activation and / or deactivation signaling messages, thus achieving better backward compatibility.

[0180] As one implementation, if the terminal device successfully descrambles the first signaling, it activates the configuration information for executing the first PUSCH transmission. For example, if the terminal device successfully descrambles the first signaling, and the first signaling is used to indicate the configuration information for activating the first PUSCH transmission, then the terminal device activates the configuration information for the first PUSCH transmission. In this case, all terminal devices participating in OCC multiplexing within the same CDM group will be collectively activated. Afterward, the terminal device can execute the first PUSCH transmission based on the configuration information for the first PUSCH transmission.

[0181] In some embodiments, after OCC multiplexing ends, the network device may send a first signaling to the terminal device to deactivate the configuration information for one or more CDM groups to perform the first PUSCH transmission.

[0182] As one implementation, if the terminal device successfully descrambles the first signaling, it deactivates the configuration information for executing the first PUSCH transmission. For example, if the terminal device successfully descrambles the first signaling, and the first signaling is used to indicate the deactivation of the configuration information for the first PUSCH transmission, then the terminal device deactivates the configuration information for the first PUSCH transmission. In this case, all terminal devices participating in OCC multiplexing within the same CDM group will collectively deactivate.

[0183] Implementation method 2 does not require modification of the current active DCI format. Instead, it directly assigns different first RNTIs to different CDM groups, meaning that different CDM groups correspond to different first RNTIs, thereby avoiding the process of terminal devices determining the CDM group identifier.

[0184] Implementation Method 3: Implicitly indicating the CDM groups that need to be activated and / or deactivated based on the PDCCH search space set.

[0185] In implementation method 3, when the network device sends configuration information to the terminal device, the configuration information may include OCC-related parameters, the identifier of the CDM group, and the mapping relationship between the CDM group and the PDCCH search space set. Of course, in addition to the above information, the configuration information may also include other information, such as the first RNTI.

[0186] In implementation method 3, the PDCCH search space sets corresponding to different CDM groups can be different. In this way, different CDM groups will perform the search and descrambling of the first signaling in different PDCCH search space sets.

[0187] In implementation method 3, the identifier of a CDM group can be determined by the number of CDM groups and the PDCCH search space set. For example, terminal devices with different CDM group identifiers will be distributed in different CDM groups and will also correspond to different PDCCH search space sets.

[0188] In implementation method 3, the terminal devices within the same CDM group have the same first RNTI. The maximum number of CDM groups that a first RNTI can accommodate is the total number of CDM group identifiers (e.g., 16).

[0189] Subsequently, the network device can send a first signaling message to the terminal device to activate the configuration information for one or more CDM groups to perform the first PUSCH transmission. In implementation method 3, the format of the first signaling message does not need to be changed compared to the current activation and / or deactivation signaling messages, thus achieving better backward compatibility.

[0190] As one implementation, if the terminal device successfully descrambles the first signaling in its corresponding PDCCH search space set, the terminal device activates the configuration information for executing the first PUSCH transmission. For example, if the terminal device receives and successfully descrambles the first signaling scrambled by the first RNTI in the PDCCH search space set pre-configured for it by the network device, and the first signaling is used to indicate the configuration information for activating the first PUSCH transmission, then the terminal device activates the configuration information for the first PUSCH transmission. In this case, all terminal devices participating in OCC multiplexing within the same CDM group will be collectively activated. Afterwards, the terminal device can execute the first PUSCH transmission based on the configuration information for the first PUSCH transmission.

[0191] In some embodiments, after OCC multiplexing ends, the network device may send a first signaling to the terminal device to deactivate the configuration information for one or more CDM groups to perform the first PUSCH transmission.

[0192] As one implementation, if the terminal device successfully descrambles the first signaling in its corresponding PDCCH search space set, then the terminal device deactivates the configuration information for executing the first PUSCH transmission. For example, if the terminal device receives the first signaling scrambled by the first RNTI in the PDCCH search space set pre-configured for it by the network device and successfully descrambles the first signaling, and the first signaling is used to indicate the configuration information for deactivating the first PUSCH transmission, then the terminal device deactivates the configuration information for the first PUSCH transmission. In this case, all terminal devices participating in OCC multiplexing in the same CDM group will collectively deactivate.

[0193] Implementation method 3 requires neither modifying the current active DCI format nor designing different first RNTIs for each CDM group. Instead, it distinguishes different CDM groups by assigning different PDCCH search space sets to different CDM groups with the same first RNTI. Specifically, when configuring OCC-related parameters for terminal devices using configuration information, network devices can configure the mapping relationship between CDM groups and PDCCH search space sets. This mapping relationship ensures that different CDM groups with the same first RNTI will be configured with different PDCCH search space sets.

[0194] Implementation Method 4: Based on the PDCCH search space set and the first RNTI implicitly indicating the CDM groups that need to be activated and / or deactivated

[0195] In implementation method 4, when the network device sends configuration information to the terminal device, the configuration information may include OCC related parameters, the identifier of the CDM group, the mapping relationship between the CDM group and the PDCCH search space set, and the first RNTI.

[0196] In implementation method 4, different CDM groups can have different PDCCH search space sets. In this way, different CDM groups will perform the search and descrambling of the first signaling in different PDCCH search space sets.

[0197] Implementation method 4 can be understood as an extension of implementation method 3. The difference lies in the potential for a larger number of configured first RNTIs. In other words, one first RNTI in implementation method 3 can correspond to a large group, and this large group in implementation method 4 can correspond to multiple first RNTIs. Each large group can contain multiple smaller groups, and each group's CDM sets correspond to a PDCCH search space set. For example, assuming a first RNTI can support M PDCCH search space sets, implementation method 3 can support at most M CDM sets. However, in implementation method 4, since there are multiple configured first RNTIs, such as N (where N is a positive integer greater than 1), implementation method 4 can support at most M*N CDM sets.

[0198] The above implementation methods 1 to 4 can all achieve collective activation and / or deactivation of CDM groups, which can effectively alleviate the problem of insufficient downlink resources. For example, when the number of terminal devices multiplexed by OCC in the CDM group is 4, the downlink resources required for the first signaling will be reduced to 1 / 4 of the downlink resources required for individual activation and / or deactivation signaling.

[0199] The indication methods used in implementation methods 1 to 4 above, as well as the changes to the protocol, can be found in Table 4.

[0200] Table 4

[0201] Example 2: First signaling implementation of CDM group scheduling

[0202] Example 2 can be applied to dynamic scheduling scenarios. In dynamic scheduling scenarios, each first PUSCH transmission by a terminal device requires scheduling by the network device via first signaling. That is, in Example 2, the network device can schedule all terminal devices within the CDM group to perform first PUSCH transmissions based on the first signaling.

[0203] Example 2 enables the scheduling of PUSCH transmissions within CDM groups, thereby alleviating the problem of limited downlink resources. Furthermore, the implementation of Example 2 is more compatible with the current signaling (DCI) field format for PUSCH scheduling.

[0204] As one implementation, Embodiment 2 can explicitly indicate the CDM groups that need to be scheduled. As another implementation, Embodiment 2 can implicitly indicate the CDM groups that need to be scheduled. This application does not limit the method by which Embodiment 2 implicitly indicates the CDM groups that need to be scheduled. For example, the network device can implicitly indicate the CDM groups that need to be scheduled through one or more of the following: a first RNTI, a PDCCH search space set, and an HPN.

[0205] The implementation of Example 2 will be described below.

[0206] Implementation Method 1: The first signaling explicitly indicates the CDM group that needs to be scheduled.

[0207] In implementation method 1, when the network device sends configuration information to the terminal device, the configuration information may include OCC-related parameters and the identifier of the CDM group to which the terminal device belongs. Of course, in addition to OCC-related parameters and the identifier of the CDM group to which the terminal device belongs, the configuration information may also include other information, such as the first RNTI.

[0208] In implementation method 1, the value range of the CDM group identifier can be related to the number of data bits of the CDM group identifier in the first signaling. For example, if the number of data bits of the CDM group identifier in the first signaling is 4, then the value range of the CDM group identifier can be 0-15, that is, a first RNTI can support a maximum of 16 CDM groups.

[0209] In implementation method 1, terminal devices within the same CDM group share the same first RNTI, while first RNTIs for different CDM groups can be the same or different. In other words, the maximum number of CDM groups that a single first RNTI can accommodate depends on the number of data bits used to identify the CDM group in the first signaling. For example, if the number of data bits used to identify the CDM group in the first signaling is 4, this means that one first RNTI can be used for scheduling 16 CDM groups. If the number of data bits used to identify the CDM group in the first signaling is 5, this means that one first RNTI can be used for scheduling 32 CDM groups.

[0210] Subsequently, the network device can send a first signaling message to the terminal device to schedule one or more CDM groups to perform a first PUSCH transmission. In implementation 1, the first signaling message may include (or carry) the identifier of the first CDM group.

[0211] In some embodiments, the first CDM group is the CDM group that needs to be scheduled. In some embodiments, the first CDM group can be any one or more CDM groups, and this application embodiment is not limited in this respect.

[0212] In some embodiments, if the identifier of the first CDM group includes the identifier of the CDM group to which the terminal device belongs, the terminal device performs a first PUSCH transmission based on the first signaling. Taking the first signaling scrambled by the first RNTI as an example, if the terminal device successfully descrambles the received first signaling using the first RNTI configured for it, the terminal device needs to compare the identifier of the first CDM group carried in the first signaling with the identifier of the CDM group configured for the terminal device by the network device to determine whether the identifier of the first CDM group includes the identifier of the CDM group to which the terminal device belongs, so as to determine whether the first PUSCH transmission needs to be performed based on the first signaling according to the comparison results.

[0213] The identifier for a CDM group configured with network devices as terminal devices is idxCDM. UE The identifier for the first CDM group is idxCDM. A For example, after the terminal device successfully descrambles the first signaling message, it needs to extract the idxCDM carried in the first signaling message. A With the network device pre-configured idxCDM UE Perform a comparison. If idxCDM UE =idxCDM A Then the terminal device performs the first PUSCH transmission based on the first signaling.

[0214] Since the terminal devices in the same CDM group are configured with the same first RNTI, and the CDM group identifiers of the terminal devices participating in OCC multiplexing in the same CDM group are the same, the terminal devices participating in OCC multiplexing in the same CDM group will implement the scheduling of the first PUSCH transmission based on the CDM group, without the network device needing to send scheduling indication signaling separately for each terminal device.

[0215] Implementation Method 2: Based on the implicit indication of the first RNTI of the CDM group that needs to be scheduled

[0216] In implementation method 2, when the network device sends configuration information to the terminal device, the configuration information may include OCC-related parameters and the first RNTI.

[0217] In implementation method 2, there is a one-to-one correspondence between the first RNTI and the CDM group, that is, one CDM group corresponds to one first RNTI (or, each CDM group corresponds to a different first RNTI). In this way, different first RNTIs can represent different CDM groups, so that the terminal device can determine the CDM group for the first signaling scheduling based on the first RNTI.

[0218] In implementation method 2, the first RNTI is the same for each terminal device within the same CDM group.

[0219] Subsequently, the network device can send a first signaling message to the terminal device to schedule one or more CDM groups to perform the first PUSCH transmission. In implementation method 2, the format of the first signaling message does not need to be changed compared to the current scheduling signaling message, which can better achieve backward compatibility.

[0220] As one implementation, if the terminal device successfully descrambles the first signaling, it performs the first PUSCH transmission based on the first signaling. For example, if the terminal device successfully descrambles the first signaling, it performs the first PUSCH transmission based on the first signaling. In this case, all terminal devices participating in OCC multiplexing within the same CDM group will collectively perform the first PUSCH transmission based on the first signaling.

[0221] Implementation method 2 does not require modification to the current scheduling DCI format. Instead, it directly assigns different first RNTIs to different CDM groups, meaning that different CDM groups correspond to different first RNTIs. This avoids the need for terminal devices to determine the CDM group identifier. Furthermore, implementation method 2 solves the problem of multiple CDM groups corresponding to the same first RNTI being unable to be scheduled simultaneously, because the first RNTI can be directly used to distinguish different CDM groups.

[0222] Implementation Method 3: Implicitly indicating the CDM groups that need to be scheduled based on the PDCCH search space set

[0223] In implementation method 3, when the network device sends configuration information to the terminal device, the configuration information may include OCC-related parameters, the identifier of the CDM group, and the mapping relationship between the CDM group and the PDCCH search space set. Of course, in addition to the above information, the configuration information may also include other information, such as the first RNTI.

[0224] In implementation method 3, the PDCCH search space sets corresponding to different CDM groups can be different. In this way, different CDM groups will perform the search and descrambling of the first signaling in different PDCCH search space sets.

[0225] In implementation method 3, the identifier of a CDM group can be determined by the number of CDM groups and the PDCCH search space set. For example, terminal devices with different CDM group identifiers will be distributed in different CDM groups and will also correspond to different PDCCH search space sets.

[0226] In implementation method 3, the terminal devices within the same CDM group have the same first RNTI. The maximum number of CDM groups that a first RNTI can accommodate is the total number of CDM group identifiers (e.g., 16).

[0227] Subsequently, the network device can send a first signaling message to the terminal device to schedule one or more CDM groups to perform the first PUSCH transmission. In implementation method 3, the format of the first signaling message does not need to be changed compared to the current scheduling signaling message, which can better achieve backward compatibility.

[0228] As one implementation, if the terminal device successfully descrambles the first signaling in its corresponding PDCCH search space set, then the terminal device performs the first PUSCH transmission based on the first signaling. For example, if the terminal device receives the first signaling scrambled by the first RNTI in the PDCCH search space set pre-configured for it by the network device and successfully descrambles the first signaling, then the terminal device performs the first PUSCH transmission based on the first signaling. In this case, all terminal devices participating in OCC multiplexing in the same CDM group will collectively perform the first PUSCH transmission based on the first signaling.

[0229] Implementation method 3 requires neither modifying the current scheduling DCI format nor designing different first RNTIs for each CDM group. Instead, it distinguishes different CDM groups by assigning different PDCCH search space sets to different CDM groups with the same first RNTI. Specifically, when configuring OCC-related parameters for terminal devices using configuration information, network devices can configure the mapping relationship between CDM groups and PDCCH search space sets. This mapping relationship ensures that different CDM groups with the same first RNTI will be configured with different PDCCH search space sets. Furthermore, implementation method 3 can solve the problem of multiple CDM groups with the same first RNTI being unable to be scheduled simultaneously, because multiple CDM groups with the same first RNTI will be configured with different PDCCH search space sets, thus achieving the distinction between different CDM groups.

[0230] Implementation Method 4: Search the space set based on PDCCH and implicitly indicate the CDM group that needs to be scheduled using the first RNTI.

[0231] In implementation method 4, when the network device sends configuration information to the terminal device, the configuration information may include OCC related parameters, the identifier of the CDM group, the mapping relationship between the CDM group and the PDCCH search space set, and the first RNTI.

[0232] In implementation method 4, different CDM groups can have different PDCCH search space sets. In this way, different CDM groups will perform the search and descrambling of the first signaling in different PDCCH search space sets.

[0233] Implementation method 4 can be understood as an extension of implementation method 3. The difference lies in the potential for a larger number of configured first RNTIs. In other words, one first RNTI in implementation method 3 can correspond to a large group, and this large group in implementation method 4 can correspond to multiple first RNTIs. Each large group can contain multiple smaller groups, and each group's CDM sets correspond to a PDCCH search space set. For example, assuming a first RNTI can support M PDCCH search space sets, implementation method 3 can support at most M CDM sets. However, in implementation method 4, since there are multiple configured first RNTIs, such as N (where N is a positive integer greater than 1), implementation method 4 can support at most M*N CDM sets.

[0234] Implementation Method 5: Based on HPN implicit indication of the CDM group that needs to be scheduled

[0235] In implementation method 5, when the network device sends configuration information to the terminal device, the configuration information may include OCC-related parameters and the identifier of the CDM group to which the terminal device belongs. Of course, in addition to OCC-related parameters and the identifier of the CDM group to which the terminal device belongs, the configuration information may also include other information, such as the first RNTI.

[0236] In implementation method 5, the first RNTI corresponding to the terminal devices within the same CDM group is the same.

[0237] In implementation method 5, there is a mapping relationship between the identifier of the CDM group to which the terminal device belongs and the synchronization HPN of the terminal device. For example, the identifier of the CDM group to which the terminal device belongs can be the same as the synchronization HPN of the terminal device. In other words, when configuring the identifier of the CDM group to which the terminal device belongs, the network device can configure the identifier of the CDM group to which the terminal device belongs based on the mapping relationship between the identifier of the CDM group to which the terminal device belongs and the synchronization HPN of the terminal device.

[0238] Subsequently, the network device can send a first signaling to the terminal device to schedule one or more CDM groups to perform the first PUSCH transmission. In this case, the PUSCH time-domain start symbol of each terminal device is consistent, so the synchronization HPN of the terminal device can be calculated based on the PUSCH time-domain start symbol (which can be understood as a virtual synchronization HPN). Then, the terminal device can compare the calculated HPN with the identifier of the CDM group to which the terminal device belongs, as indicated in the configuration information. If the two satisfy a certain mapping relationship (for example, they are the same), then all terminal devices participating in OCC multiplexing in the same CDM group will collectively perform the first PUSCH transmission based on the first signaling.

[0239] In some embodiments, the first signaling sent by the network device to the terminal device is scrambled by a first RNTI.

[0240] In some embodiments, the first signaling includes indication information of the PUSCH scheduling time-domain resource location. Since the terminal devices using OCC multiplexing locks use the same transmission resources, the time-domain start symbols of the PUSCHs scheduled by each terminal device are also the same, and the synchronization HPN of the terminal devices can be calculated based on the time-domain start symbol.

[0241] As one possible implementation, for uplink grant scheduling that does not use harqProcID-Offset2 or cg-RetransmissionTimer configuration, the HPN determined based on the synchronous HARQ process number calculation formula corresponding to the PUSCH is: HPN = [floor(CURRENT_symbol / periodicity)]modulo nrofHARQ―Process. Assuming the time-domain start symbol of the PUSCH indicated by the first signaling is 33, and both parameters harqProcID-Offset2 and cg-RetransmissionTimer take their default values ​​(16 and 14 respectively), then the HPN corresponding to the PUSCH = [floor(33 / 14)]modulo 16 = 2.

[0242] Afterwards, the terminal device can compare the HPN with the identifier of the CDM group to which the terminal device belongs, as configured by the network device. For example, if both are 2, then all terminal devices in the CDM group corresponding to the terminal device will perform the first PUSCH transmission based on the first signaling.

[0243] Implementation method 5 does not require any changes to the current scheduling DCI format. It uses HPN to distinguish different CDM groups, thus alleviating downlink resource constraints.

[0244] All of the above implementation methods 1 to 5 can achieve collective scheduling of CDM groups, which can effectively alleviate the problem of insufficient downlink resources. For example, when the number of terminal devices multiplexed by OCC in the CDM group is 4, the downlink resources required for the first signaling will be reduced to 1 / 4 of the downlink resources of individually scheduled terminal devices.

[0245] The indication methods used in implementation methods 1 to 5 and the modifications made to the protocol can be found in Table 5.

[0246] Table 5

[0247] To facilitate understanding, the communication process under different scheduling scenarios will be introduced below with reference to Figures 9 to 12.

[0248] Figures 9 and 10 illustrate the communication flow in a Type 1 configuration scheduling scenario. As shown in Figures 9 and 10, the network device can send configuration information to different terminal devices within the CDM group. This configuration information carries OCC-related parameters and is used to schedule the terminal devices to perform the first PUSCH transmission. Subsequently, the terminal devices perform the first PUSCH transmission based on this configuration information without any lower-level triggering (first signaling trigger).

[0249] In some embodiments, the network device can send configuration information to different terminal devices at different times, meaning the PUSCH start scheduling time can be arbitrarily allocated. For example, in the example of Figure 9, the network device can send configuration information to terminal device 1 and terminal device 2 at different times. As another example, in the example of Figure 10, the network device can send configuration information to terminal device 1, terminal device 2, terminal device 3, and terminal device 4 at different times. Taking a cross-slot OCC scheme as an example, when the number of terminal devices multiplexed by OCC is 4, the time domain resources occupied by each PUSCH will include 4 data repetition slots, and the repetitive data in these 4 slots will be spread using the 4 elements of the configured OCC codeword. Since the repetitive data within each PUSCH has orthogonality completeness with respect to the OCC codeword, even if the network device sends configuration information to each terminal device at different times, the OCC orthogonality between different terminal devices can still be maintained.

[0250] In some embodiments, the network device should configure consistent transmission resources for different terminal devices, that is, different terminal devices need to use the same resources to perform the first PUSCH transmission to achieve OCC multiplexing, thereby improving the uplink capacity of the system.

[0251] Figure 11 illustrates the communication flow in a Type 2 configuration scheduling scenario. As shown in Figure 11, the network device can send configuration information to different terminal devices within the CDM group. This configuration information carries OCC-related parameters and is used to schedule the terminal devices to execute the first PUSCH transmission. Subsequently, the network device can send a first signaling message to the terminal devices within the CDM group at the CDM group level to activate the configuration parameters for the first PUSCH transmission. Upon receiving the first signaling message, the terminal device can execute the first PUSCH transmission based on the configuration information.

[0252] In some embodiments, the network device may also configure the first RNTI and / or the identifier of the CDM group to which the terminal device belongs, at the CDM group level.

[0253] In some embodiments, the network device may also configure the mapping relationship between the CDM group and the PDCCH search space set for the terminal device.

[0254] In some embodiments, the configuration information sent by the network device may also include scheduling information for the first PUSCH transmission, such as the scheduling period.

[0255] The above section introduced four implementation methods for CDM group activation and / or deactivation in the scenario of configuration scheduling of type 2. The following section provides an exemplary description of the communication process corresponding to each of these four implementation methods.

[0256] Example 1: First signaling explicit indication

[0257] Suppose that the network device uses a semi-static scheduling method to perform PUSCH scheduling on the OCC multiplexed terminal devices, and the scheduling type is configured as type 2, where the number of OCC multiplexed terminal devices is 4 (that is, the number of terminal devices in the CDM group is 4), namely terminal device 1 to terminal device 4.

[0258] The network device can send configuration information to terminal devices 1 to 4. The configuration information may include OCC-related parameters, the identifier of the CDM group to which the terminal device belongs, and the first RNTI.

[0259] For example, the OCC-related parameters may include a cross-timeslot OCC scheme, an OCC length of 4, a codeword table as shown in Table 2, and a codeword index of the terminal device (e.g., codeword index 2 for terminal device 1, codeword index 3 for terminal device 2, codeword index 4 for terminal device 3, and codeword index 5 for terminal device 4).

[0260] For example, if the data bits of the CDM group identifier in the first signaling are 4, then the value range of the CDM group identifier is 0-15. In Example 1, since terminal devices 1 to 4 are in the same CDM group, the CDM group identifiers of terminal devices 1 to 4 are the same, for example, all are dixCDM. UE =6.

[0261] For example, since terminal devices 1 to 4 are in the same CDM group, the first RNTI of terminal devices 1 to 4 is the same. In Example 1, the first RNTIs corresponding to different CDM groups may be the same or different.

[0262] Subsequently, the network device uses the first signaling to collectively activate terminal devices 1 to 4 (i.e., collective OCC activation). The activation method can be found in Implementation Method 1 of Example 1.

[0263] Subsequently, terminal devices 1 to 4 can perform the first PUSCH transmission based on the configuration information. For example, terminal devices 1 to 4 can perform the first PUSCH transmission on the same time-frequency resources.

[0264] After OCC multiplexing ends, the network device can use the first signaling to collectively deactivate terminal devices 1 to 4 (i.e., collective OCC deactivation). The deactivation method can be found in Implementation Method 1 of Example 1.

[0265] Example 2: Based on the first RNTI indication

[0266] Suppose that the network device uses a semi-static scheduling method to perform PUSCH scheduling on the OCC multiplexed terminal devices, and the scheduling type is configured as type 2, where the number of OCC multiplexed terminal devices is 4 (that is, the number of terminal devices in the CDM group is 4), namely terminal device 1 to terminal device 4.

[0267] The network device can send configuration information to terminal devices 1 to 4, which may include OCC-related parameters and the first RNTI.

[0268] For example, the OCC-related parameters may include a cross-timeslot OCC scheme, an OCC length of 4, a codeword table as shown in Table 2, and a codeword index of the terminal device (e.g., codeword index 2 for terminal device 1, codeword index 3 for terminal device 2, codeword index 4 for terminal device 3, and codeword index 5 for terminal device 4).

[0269] For example, since terminal devices 1 to 4 are in the same CDM group, the first RNTI of terminal devices 1 to 4 is the same. In Example 2, the first RNTIs corresponding to different CDM groups are different, or in other words, one CDM group corresponds to one type of first RNTI.

[0270] Subsequently, the network device uses the first signaling to collectively activate terminal devices 1 to 4 (i.e., collective OCC activation). The activation method can be found in implementation method 2 of embodiment 1.

[0271] Subsequently, terminal devices 1 to 4 can perform the first PUSCH transmission based on the configuration information. For example, terminal devices 1 to 4 can perform the first PUSCH transmission on the same time-frequency resources.

[0272] After OCC multiplexing ends, the network device can use the first signaling to collectively deactivate terminal devices 1 to 4 (i.e., collective OCC deactivation). The deactivation method can be found in implementation method 2 of embodiment 1.

[0273] Example 3: Search space set based on PDCCH or search space set based on PDCCH and first RNTI indication

[0274] Suppose that the network device uses a semi-static scheduling method to perform PUSCH scheduling on the OCC multiplexed terminal devices, and the scheduling type is configured as type 2, where the number of OCC multiplexed terminal devices is 4 (that is, the number of terminal devices in the CDM group is 4), namely terminal device 1 to terminal device 4.

[0275] The network device can send configuration information to terminal devices 1 to 4. The configuration information may include OCC-related parameters, the identifier of the CDM group to which the terminal device belongs, the first RNTI, and the mapping relationship between the CDM group and the PDCCH search space set.

[0276] For example, the OCC-related parameters may include a cross-timeslot OCC scheme, an OCC length of 4, a codeword table as shown in Table 2, and a codeword index of the terminal device (e.g., codeword index 2 for terminal device 1, codeword index 3 for terminal device 2, codeword index 4 for terminal device 3, and codeword index 5 for terminal device 4).

[0277] For example, terminal devices in the same CDM group have the same CDM group identifier. For instance, terminal devices 1 to 4 have the same CDM group identifier, such as 8.

[0278] For example, different CDM groups correspond to different PDCCH search space sets, thereby avoiding conflicts in activation and / or deactivation of different CDM groups.

[0279] For example, since terminal devices 1 to 4 are in the same CDM group, their first RNTIs are the same. In Example 3, the first RNTIs corresponding to different CDM groups may be the same or different.

[0280] Subsequently, the network device uses the first signaling to collectively activate terminal devices 1 to 4 (i.e., collective OCC activation). The activation method can be found in implementation method 3 or implementation method 4 of embodiment 1.

[0281] Subsequently, terminal devices 1 to 4 can perform the first PUSCH transmission based on the configuration information. For example, terminal devices 1 to 4 can perform the first PUSCH transmission on the same time-frequency resources.

[0282] After OCC multiplexing ends, the network device can use the first signaling to collectively deactivate terminal devices 1 to 4 (i.e., collective OCC deactivation). The deactivation method can be found in implementation method 3 or implementation method 4 of embodiment 1.

[0283] Figure 12 illustrates the communication process in a dynamic scheduling scenario. As shown in Figure 12, the network device can send configuration information to different terminal devices within the CDM group. This configuration information carries OCC-related parameters and is used to schedule the terminal devices to perform the first PUSCH transmission. Subsequently, the network device can send the first signaling to the terminal devices within the CDM group at the CDM group level to schedule the CDM group to collectively perform the first PUSCH transmission.

[0284] In some embodiments, the network device may also configure the first RNTI and / or the identifier of the CDM group to which the terminal device belongs, at the CDM group level.

[0285] In some embodiments, the network device may also configure the mapping relationship between the CDM group and the PDCCH search space set for the terminal device.

[0286] The difference between dynamic scheduling and configuration scheduling of type 2 is that in configuration scheduling of type 2, the configuration information can include the scheduling information of the first PUSCH transmission (such as the scheduling period), while dynamic scheduling does not need to configure this information in the configuration information. This information is indicated by the first signaling of dynamic scheduling. Therefore, dynamic scheduling has greater flexibility than configuration scheduling of type 2.

[0287] The above section introduced five implementation methods for activating and / or deactivating CDM groups in dynamic scheduling scenarios. The following section provides an exemplary description of the communication processes corresponding to these five implementation methods.

[0288] Example 1: First signaling explicit indication

[0289] Assuming the network device uses dynamic scheduling to schedule PUSCH for OCC-multiplexed terminal devices, in this case, there is no need for collective activation and deactivation of OCC as in semi-static scheduling. Instead, scheduling of the first PUSCH transmission is required based on the first signaling. The number of OCC-multiplexed terminal devices is 4 (i.e., the number of terminal devices in the CDM group is 4), namely terminal device 1 to terminal device 4.

[0290] The network device can send configuration information to terminal devices 1 to 4. The configuration information may include OCC-related parameters, the identifier of the CDM group to which the terminal device belongs, and the first RNTI.

[0291] For example, the OCC-related parameters may include a cross-timeslot OCC scheme, an OCC length of 4, a codeword table as shown in Table 2, and a codeword index of the terminal device (e.g., codeword index 2 for terminal device 1, codeword index 3 for terminal device 2, codeword index 4 for terminal device 3, and codeword index 5 for terminal device 4).

[0292] For example, if the data bits of the CDM group identifier in the first signaling are 4, then the value range of the CDM group identifier is 0-15. In Example 1, since terminal devices 1 to 4 are in the same CDM group, the CDM group identifiers of terminal devices 1 to 4 are the same, for example, all are dixCDM. UE =2.

[0293] For example, since terminal devices 1 to 4 are in the same CDM group, the first RNTI of terminal devices 1 to 4 is the same. In Example 1, the first RNTIs corresponding to different CDM groups may be the same or different.

[0294] Subsequently, the network device uses the first signaling to perform collective scheduling (i.e., PUSCH group scheduling) on ​​terminal devices 1 to 4. The scheduling method can be found in implementation method 1 of embodiment 2.

[0295] Subsequently, terminal devices 1 to 4 can perform the first PUSCH transmission based on the configuration information. For example, terminal devices 1 to 4 can perform the first PUSCH transmission on the same time-frequency resources.

[0296] Example 2: Based on the first RNTI indication

[0297] Assuming the network device uses dynamic scheduling to schedule PUSCH for OCC-multiplexed terminal devices, in this case, there is no need for collective activation and deactivation of OCC as in semi-static scheduling. Instead, scheduling of the first PUSCH transmission is required based on the first signaling. The number of OCC-multiplexed terminal devices is 4 (i.e., the number of terminal devices in the CDM group is 4), namely terminal device 1 to terminal device 4.

[0298] The network device can send configuration information to terminal devices 1 to 4, which may include OCC-related parameters and the first RNTI.

[0299] For example, the OCC-related parameters may include a cross-timeslot OCC scheme, an OCC length of 4, a codeword table as shown in Table 2, and a codeword index of the terminal device (e.g., codeword index 2 for terminal device 1, codeword index 3 for terminal device 2, codeword index 4 for terminal device 3, and codeword index 5 for terminal device 4).

[0300] For example, since terminal devices 1 to 4 are in the same CDM group, the first RNTI of terminal devices 1 to 4 is the same. In Example 2, the first RNTIs corresponding to different CDM groups are different, or in other words, one CDM group corresponds to one type of first RNTI.

[0301] Subsequently, the network device uses the first signaling to perform collective scheduling (i.e., PUSCH group scheduling) on ​​terminal devices 1 to 4. The scheduling method is described in Implementation Method 2 of Example 2.

[0302] Subsequently, terminal devices 1 to 4 can perform the first PUSCH transmission based on the configuration information. For example, terminal devices 1 to 4 can perform the first PUSCH transmission on the same time-frequency resources.

[0303] Example 3: Search space set based on PDCCH or search space set based on PDCCH and first RNTI indication

[0304] Assuming the network device uses dynamic scheduling to schedule PUSCH for OCC-multiplexed terminal devices, in this case, there is no need for collective activation and deactivation of OCC as in semi-static scheduling. Instead, scheduling of the first PUSCH transmission is required based on the first signaling. The number of OCC-multiplexed terminal devices is 4 (i.e., the number of terminal devices in the CDM group is 4), namely terminal device 1 to terminal device 4.

[0305] The network device can send configuration information to terminal devices 1 to 4. The configuration information may include OCC-related parameters, the identifier of the CDM group to which the terminal device belongs, the first RNTI, and the mapping relationship between the CDM group and the PDCCH search space set.

[0306] For example, the OCC-related parameters may include a cross-timeslot OCC scheme, an OCC length of 4, a codeword table as shown in Table 2, and a codeword index of the terminal device (e.g., codeword index 2 for terminal device 1, codeword index 3 for terminal device 2, codeword index 4 for terminal device 3, and codeword index 5 for terminal device 4).

[0307] For example, the identifier of a CDM group is determined by the number of CDM groups and the PDCCH search space set. Terminal devices in different CDM groups have different CDM group identifiers and correspond to different PDCCH search space sets. Terminal devices in the same CDM group have the same CDM group identifier and correspond to the same PDCCH search space set.

[0308] For example, the mapping between CDM groups and PDCCH search space sets can ensure that different CDM groups with the same first RNTI will be configured with different PDCCH search space sets.

[0309] For example, since terminal devices 1 to 4 are in the same CDM group, their first RNTIs are the same. In Example 3, the first RNTIs corresponding to different CDM groups may be the same or different.

[0310] Subsequently, the network device uses the first signaling to perform collective scheduling (i.e., PUSCH group scheduling) on ​​terminal devices 1 to 4. The scheduling method is described in implementation method 3 or implementation method 4 of embodiment 2.

[0311] Subsequently, terminal devices 1 to 4 can perform the first PUSCH transmission based on the configuration information. For example, terminal devices 1 to 4 can perform the first PUSCH transmission on the same time-frequency resources.

[0312] Example 4: Based on HPN indication

[0313] Assuming the network device uses dynamic scheduling to schedule PUSCH for OCC-multiplexed terminal devices, in this case, there is no need for collective activation and deactivation of OCC as in semi-static scheduling. Instead, scheduling of the first PUSCH transmission is required based on the first signaling. The number of OCC-multiplexed terminal devices is 4 (i.e., the number of terminal devices in the CDM group is 4), namely terminal device 1 to terminal device 4.

[0314] The network device can send configuration information to terminal devices 1 to 4. The configuration information may include OCC-related parameters, the identifier of the CDM group to which the terminal device belongs, and the first RNTI.

[0315] For example, the OCC-related parameters may include a cross-timeslot OCC scheme, an OCC length of 4, a codeword table as shown in Table 2, and a codeword index of the terminal device (e.g., codeword index 2 for terminal device 1, codeword index 3 for terminal device 2, codeword index 4 for terminal device 3, and codeword index 5 for terminal device 4).

[0316] For example, if the data bits of the CDM group identifier in the first signaling are 4, then the value range of the CDM group identifier is 0-15. In Example 5, since terminal devices 1 to 4 are in the same CDM group, the CDM group identifiers of terminal devices 1 to 4 are the same, for example, all are dixCDM. UE =2.

[0317] For example, since terminal devices 1 to 4 are in the same CDM group, their first RNTIs are the same. In Example 5, the first RNTIs corresponding to different CDM groups may be the same or different.

[0318] Subsequently, the network device uses the first signaling to perform collective scheduling (i.e., PUSCH group scheduling) on ​​terminal devices 1 to 4. The scheduling method is described in implementation method 5 of embodiment 2.

[0319] Subsequently, terminal devices 1 to 4 can perform the first PUSCH transmission based on the configuration information. For example, terminal devices 1 to 4 can perform the first PUSCH transmission on the same time-frequency resources.

[0320] The method embodiments of this application have been described in detail above with reference to Figures 1 to 12. The apparatus embodiments of this application will be described in detail below with reference to Figures 13 to 15. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0321] Figure 13 is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. The terminal device 1300 shown in Figure 13 may include a first receiving module 1310. The first receiving module 1310 can be used to receive configuration information sent by a network device. The configuration information is used to configure the scheduling parameters of a first PUSCH transmission, wherein the first PUSCH transmission is an OCC-based PUSCH transmission, and the configuration information includes OCC-related parameters.

[0322] In some embodiments, the configuration information further includes one or more of the following: the identifier of the CDM group to which the terminal device belongs; a first RNTI, which is used to scramble and / or descramble the PDCCH transmitted by the first PUSCH; and the mapping relationship between the CDM group and the PDCCH search space set.

[0323] In some embodiments, the first RNTI is configured at the granularity of the CDM group.

[0324] In some embodiments, the terminal device further includes: a second receiving module 1320, configured to receive a first signaling sent by the network device, the first signaling being used for one or more of the following: activating configuration information for one or more CDM groups to perform the first PUSCH transmission; deactivating configuration information for one or more CDM groups to perform the first PUSCH transmission; scheduling one or more CDM groups to perform the first PUSCH transmission.

[0325] In some embodiments, the first signaling includes an identifier of a first CDM group, and the terminal device further includes a first execution module, configured to: activate or deactivate configuration information for executing the first PUSCH transmission if the identifier of the first CDM group includes an identifier of the CDM group to which the terminal device belongs, or execute the first PUSCH transmission based on the first signaling if the identifier of the first CDM group includes an identifier of the CDM group to which the terminal device belongs.

[0326] In some embodiments, the configuration information includes the first RNTI, and there is a one-to-one correspondence between the first RNTI and the one or more CDM groups.

[0327] In some embodiments, the terminal device further includes a second execution module, configured to: activate or deactivate configuration information for executing the first PUSCH transmission if the terminal device successfully descrambles the first signaling, or execute the first PUSCH transmission based on the first signaling if the terminal device successfully descrambles the first signaling; wherein the first signaling is descrambled by the terminal device using a first RNTI carried in the configuration information.

[0328] In some embodiments, the configuration information includes a mapping relationship between CDM groups and PDCCH search space sets, and different CDM groups correspond to different PDCCH search space sets.

[0329] In some embodiments, the terminal device further includes a third execution module, configured to: activate or deactivate configuration information for executing the first PUSCH transmission if the terminal device successfully descrambles the first signaling in the PDCCH search space set corresponding to the terminal device; or, if the terminal device successfully descrambles the first signaling in the PDCCH search space set corresponding to the terminal device, execute the first PUSCH transmission based on the first signaling; wherein the first signaling is descrambled by the terminal device using the first RNTI carried in the configuration information.

[0330] In some embodiments, the activation and / or deactivation of the configuration information for the first PUSCH transmission is determined based on the PDCCH search space set, or based on the PDCCH search space set and the first RNTI; and / or, the execution of the first PUSCH transmission is determined based on the PDCCH search space set, or based on the PDCCH search space set and the first RNTI.

[0331] In some embodiments, the terminal device further includes: a determining module, configured to determine the HARQ process number corresponding to the first PUSCH transmission; and a fourth execution module, configured to execute the first PUSCH transmission based on the first signaling if the terminal device determines that the HARQ process number corresponding to the first PUSCH transmission is the same as the identifier of the CDM group to which the terminal device belongs.

[0332] In some embodiments, the OCC-related parameters include one or more of the following: OCC scheme, OCC length, OCC codeword table, and OCC codeword index.

[0333] In some embodiments, the OCC scheme includes one or more of the following: a cross-symbol OCC scheme, a cross-timeslot OCC scheme, and an intra-symbol OCC scheme.

[0334] In some embodiments, the configuration information is carried in RRC signaling.

[0335] In some embodiments, the first receiving module 1310 may be a transceiver 1530. The terminal device 1300 may also include a processor 1510 and a memory 1520, as shown in FIG15.

[0336] Figure 14 is a schematic diagram of the network device provided in an embodiment of this application. The network device 1400 shown in Figure 14 may include a first sending module 1410. The first sending module 1410 can be used to send configuration information to a terminal device. The configuration information is used to configure the scheduling parameters of a first PUSCH transmission, wherein the first PUSCH transmission is an OCC-based PUSCH transmission, and the configuration information includes OCC-related parameters.

[0337] In some embodiments, the configuration information further includes one or more of the following: the identifier of the CDM group to which the terminal device belongs; a first RNTI, which is used to scramble and / or descramble the PDCCH transmitted by the first PUSCH; and the mapping relationship between the CDM group and the PDCCH search space set.

[0338] In some embodiments, the first RNTI is configured at the granularity of the CDM group.

[0339] In some embodiments, the network device further includes: a second sending module 1320, configured to send a first signaling to the terminal device, the first signaling being used for one or more of the following: activating configuration information for one or more CDM groups to perform the first PUSCH transmission; deactivating configuration information for one or more CDM groups to perform the first PUSCH transmission; scheduling one or more CDM groups to perform the first PUSCH transmission.

[0340] In some embodiments, the first signaling includes an identifier of a first CDM group.

[0341] In some embodiments, the configuration information includes the first RNTI, and there is a one-to-one correspondence between the first RNTI and the one or more CDM groups.

[0342] In some embodiments, the configuration information includes a mapping relationship between CDM groups and PDCCH search space sets, and different CDM groups correspond to different PDCCH search space sets.

[0343] In some embodiments, the activation and / or deactivation of the configuration information for the first PUSCH transmission is determined based on the PDCCH search space set, or based on the PDCCH search space set and the first RNTI; and / or, the execution of the first PUSCH transmission is determined based on the PDCCH search space set, or based on the PDCCH search space set and the first RNTI.

[0344] In some embodiments, the OCC-related parameters include one or more of the following: OCC scheme, OCC length, OCC codeword table, and OCC codeword index.

[0345] In some embodiments, the OCC scheme includes one or more of the following: a cross-symbol OCC scheme, a cross-timeslot OCC scheme, and an intra-symbol OCC scheme.

[0346] In some embodiments, the configuration information is carried in RRC signaling.

[0347] In some embodiments, the first transmitting module 1410 may be a transceiver 1530. The network device 1400 may also include a processor 1510 and a memory 1520, as shown in FIG15.

[0348] Figure 15 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 15 indicate that the unit or module is optional. This device 1500 can be used to implement the methods described in the above method embodiments. Device 1500 can be a chip, a terminal device, or a network device.

[0349] Apparatus 1500 may include one or more processors 1510. The processor 1510 may support apparatus 1500 in implementing the methods described in the preceding method embodiments. The processor 1510 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0350] The apparatus 1500 may further include one or more memories 1520. The memories 1520 store a program that can be executed by the processor 1510, causing the processor 1510 to perform the methods described in the preceding method embodiments. The memories 1520 may be independent of the processor 1510 or integrated into the processor 1510.

[0351] The device 1500 may also include a transceiver 1530. The processor 1510 can communicate with other devices or chips via the transceiver 1530. For example, the processor 1510 can send and receive data with other devices or chips via the transceiver 1530.

[0352] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal device or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.

[0353] This application also provides a computer program product. The computer program product includes a program. This computer program product can be applied to a terminal device or network device provided in the embodiments of this application, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.

[0354] This application also provides a computer program. This computer program can be applied to the terminal device or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal device or network device in various embodiments of this application.

[0355] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0356] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0357] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0358] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0359] In the embodiments of this application, the term "comprising" can refer to direct inclusion or indirect inclusion. Optionally, "comprising" in the embodiments of this application can be replaced with "instructing" or "used to determine". For example, "A includes B" can be replaced with "A instructs B" or "A is used to determine B".

[0360] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0361] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0362] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0363] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0364] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0365] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0366] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0367] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0368] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

A method for wireless communication, characterized in that, include: The terminal device receives configuration information sent by the network device. The configuration information is used to configure the scheduling parameters for the first physical uplink shared channel (PUSCH) transmission. The first PUSCH transmission is a PUSCH transmission based on orthogonal coverage code (OCC), and the configuration information includes OCC-related parameters. The method according to claim 1, characterized in that, The configuration information also includes one or more of the following: The identifier of the Code Division Multiplexing (CDM) group to which the terminal device belongs; First Radio Network Temporary Identifier (RNTI), the first RNTI is used to scramble and / or descramble the Physical Downlink Control Channel (PDCCH) for the transmission of the first PUSCH; Mapping relationship between CDM group and PDCCH search space set. The method according to claim 2, characterized in that, The first RNTI is configured according to the granularity of the CDM group. The method according to any one of claims 1-3 is characterized in that, The method further includes: The terminal device receives a first signaling sent by the network device, the first signaling being used for one or more of the following: Activate one or more CDM groups to execute the configuration information for the first PUSCH transmission; Deactivate the configuration information for one or more CDM groups to execute the first PUSCH transmission; Schedule one or more CDM groups to perform the first PUSCH transmission. The method according to claim 4, characterized in that, The first signaling includes an identifier for a first CDM group, and the method further includes: If the identifier of the first CDM group includes the identifier of the CDM group to which the terminal device belongs, the terminal device activates or deactivates the configuration information for executing the first PUSCH transmission, or... If the identifier of the first CDM group includes the identifier of the CDM group to which the terminal device belongs, the terminal device performs the first PUSCH transmission based on the first signaling. The method according to claim 4, characterized in that, The configuration information includes the first RNTI, and there is a one-to-one correspondence between the first RNTI and the one or more CDM groups. The method according to claim 6, characterized in that, The method further includes: If the terminal device successfully descrambles the first signaling, the terminal device activates or deactivates the configuration information for executing the first PUSCH transmission, or... If the terminal device successfully descrambles the first signaling, the terminal device performs the first PUSCH transmission based on the first signaling. The first signaling is descrambled by the terminal device using the first RNTI carried in the configuration information. The method according to claim 4, characterized in that, The configuration information includes the mapping relationship between CDM groups and PDCCH search space sets, and different CDM groups correspond to different PDCCH search space sets. The method according to claim 8, characterized in that, The method further includes: If the terminal device successfully descrambles the first signaling in the PDCCH search space set corresponding to the terminal device, the terminal device activates or deactivates the configuration information for executing the first PUSCH transmission, or... If the terminal device successfully descrambles the first signaling in the PDCCH search space set corresponding to the terminal device, the terminal device performs the first PUSCH transmission based on the first signaling. The first signaling is descrambled by the terminal device using the first RNTI carried in the configuration information. The method according to claim 8 or 9, characterized in that: The activation and / or deactivation of the configuration information transmitted in the first PUSCH is determined based on the PDCCH search space set, or based on the PDCCH search space set and the first RNTI; and / or, The execution of the first PUSCH transmission is determined based on the PDCCH search space set, or based on the PDCCH search space set and the first RNTI. The method according to claim 4, characterized in that, The method further includes: The terminal device determines the HARQ process number corresponding to the first PUSCH transmission. If the terminal device determines that the HARQ process number corresponding to the first PUSCH transmission is the same as the identifier of the CDM group to which the terminal device belongs, the terminal device executes the first PUSCH transmission based on the first signaling. The method according to any one of claims 1-11, characterized in that, The OCC-related parameters include one or more of the following: OCC scheme, OCC length, OCC codeword table, and OCC codeword index. The method according to claim 12, characterized in that, The OCC scheme includes one or more of the following: cross-symbol OCC scheme, cross-time slot OCC scheme, and intra-symbol OCC scheme. The method according to any one of claims 1-13 is characterized in that, The configuration information is carried in Radio Resource Control (RRC) signaling. A method for wireless communication, characterized in that, include: The network device sends configuration information to the terminal device. The configuration information is used to configure the scheduling parameters of the first physical uplink shared channel (PUSCH) transmission. The first PUSCH transmission is a PUSCH transmission based on orthogonal coverage code (OCC), and the configuration information includes OCC-related parameters. The method according to claim 15, characterized in that, The configuration information also includes one or more of the following: The identifier of the Code Division Multiplexing (CDM) group to which the terminal device belongs; First Radio Network Temporary Identifier (RNTI), the first RNTI is used to scramble and / or descramble the Physical Downlink Control Channel (PDCCH) for the transmission of the first PUSCH; Mapping relationship between CDM group and PDCCH search space set. The method according to claim 16, characterized in that, The first RNTI is configured according to the granularity of the CDM group. The method according to any one of claims 15-17 is characterized in that, The method further includes: The network device sends a first signaling message to the terminal device, the first signaling message being used for one or more of the following: Activate one or more CDM groups to execute the configuration information for the first PUSCH transmission; Deactivate the configuration information for one or more CDM groups to execute the first PUSCH transmission; Schedule one or more CDM groups to perform the first PUSCH transmission. The method according to claim 18, characterized in that, The first signaling includes the identifier of the first CDM group. The method according to claim 18, characterized in that, The configuration information includes the first RNTI, and there is a one-to-one correspondence between the first RNTI and the one or more CDM groups. The method according to claim 18, characterized in that, The configuration information includes the mapping relationship between CDM groups and PDCCH search space sets, and different CDM groups correspond to different PDCCH search space sets. The method according to claim 21, characterized in that: The activation and / or deactivation of the configuration information transmitted in the first PUSCH is determined based on the PDCCH search space set, or based on the PDCCH search space set and the first RNTI; and / or, The execution of the first PUSCH transmission is determined based on the PDCCH search space set, or based on the PDCCH search space set and the first RNTI. The method according to any one of claims 15-22 is characterized in that, The OCC-related parameters include one or more of the following: OCC scheme, OCC length, OCC codeword table, and OCC codeword index. The method according to claim 23, characterized in that, The OCC scheme includes one or more of the following: cross-symbol OCC scheme, cross-time slot OCC scheme, and intra-symbol OCC scheme. The method according to any one of claims 15-24 is characterized in that, The configuration information is carried in Radio Resource Control (RRC) signaling. A terminal device, characterized in that, include: The first receiving module is used to receive configuration information sent by the network device. The configuration information is used to configure the scheduling parameters of the first physical uplink shared channel (PUSCH) transmission. The first PUSCH transmission is a PUSCH transmission based on orthogonal coverage code (OCC), and the configuration information includes OCC-related parameters. The terminal device according to claim 26 is characterized in that, The configuration information also includes one or more of the following: The identifier of the Code Division Multiplexing (CDM) group to which the terminal device belongs; First Radio Network Temporary Identifier (RNTI), the first RNTI is used to scramble and / or descramble the Physical Downlink Control Channel (PDCCH) for the transmission of the first PUSCH; Mapping relationship between CDM group and PDCCH search space set. The terminal device according to claim 27 is characterized in that, The first RNTI is configured according to the granularity of the CDM group. The terminal device according to any one of claims 26-28 is characterized in that, The terminal device also includes: The second receiving module is configured to receive a first signaling sent by the network device, wherein the first signaling is used for one or more of the following: Activate one or more CDM groups to execute the configuration information for the first PUSCH transmission; Deactivate the configuration information for one or more CDM groups to execute the first PUSCH transmission; Schedule one or more CDM groups to perform the first PUSCH transmission. The terminal device according to claim 29 is characterized in that, The first signaling includes an identifier for a first CDM group, and the terminal device further includes a first execution module for: If the identifier of the first CDM group includes the identifier of the CDM group to which the terminal device belongs, activate or deactivate the configuration information for executing the first PUSCH transmission, or... If the identifier of the first CDM group includes the identifier of the CDM group to which the terminal device belongs, the first PUSCH transmission is performed based on the first signaling. The terminal device according to claim 29 is characterized in that, The configuration information includes the first RNTI, and there is a one-to-one correspondence between the first RNTI and the one or more CDM groups. The terminal device according to claim 31 is characterized in that, The terminal device further includes a second execution module, used for: If the terminal device successfully descrambles the first signaling, it activates or deactivates the configuration information for executing the first PUSCH transmission, or... If the terminal device successfully descrambles the first signaling, it performs the first PUSCH transmission based on the first signaling. The first signaling is descrambled by the terminal device using the first RNTI carried in the configuration information. The terminal device according to claim 29 is characterized in that, The configuration information includes the mapping relationship between CDM groups and PDCCH search space sets, and different CDM groups correspond to different PDCCH search space sets. The terminal device according to claim 33 is characterized in that, The terminal device further includes a third execution module, used for: If the terminal device successfully descrambles the first signaling in the PDCCH search space set corresponding to the terminal device, the terminal device activates or deactivates the configuration information for executing the first PUSCH transmission, or... If the terminal device successfully descrambles the first signaling in the PDCCH search space set corresponding to the terminal device, the terminal device performs the first PUSCH transmission based on the first signaling. The first signaling is descrambled by the terminal device using the first RNTI carried in the configuration information. The terminal device according to claim 33 or 34 is characterized in that: The activation and / or deactivation of the configuration information transmitted in the first PUSCH is determined based on the PDCCH search space set, or based on the PDCCH search space set and the first RNTI; and / or, The execution of the first PUSCH transmission is determined based on the PDCCH search space set, or based on the PDCCH search space set and the first RNTI. The terminal device according to claim 29 is characterized in that, The terminal device also includes: The determination module is used to determine the HARQ process number corresponding to the first PUSCH transmission; The fourth execution module is configured to execute the first PUSCH transmission based on the first signaling if the terminal device determines that the HARQ process number corresponding to the first PUSCH transmission is the same as the identifier of the CDM group to which the terminal device belongs. The terminal device according to any one of claims 26-36 is characterized in that, The OCC-related parameters include one or more of the following: OCC scheme, OCC length, OCC codeword table, and OCC codeword index. The terminal device according to claim 37 is characterized in that, The OCC scheme includes one or more of the following: cross-symbol OCC scheme, cross-time slot OCC scheme, and intra-symbol OCC scheme. The terminal device according to any one of claims 26-38 is characterized in that, The configuration information is carried in Radio Resource Control (RRC) signaling. A network device, characterized in that, include: The first sending module is used to send configuration information to the terminal device. The configuration information is used to configure the scheduling parameters of the first physical uplink shared channel (PUSCH) transmission. The first PUSCH transmission is a PUSCH transmission based on orthogonal coverage code (OCC), and the configuration information includes OCC-related parameters. The network device according to claim 40 is characterized in that, The configuration information also includes one or more of the following: The identifier of the Code Division Multiplexing (CDM) group to which the terminal device belongs; First Radio Network Temporary Identifier (RNTI), the first RNTI is used to scramble and / or descramble the Physical Downlink Control Channel (PDCCH) for the transmission of the first PUSCH; Mapping relationship between CDM group and PDCCH search space set. The network device according to claim 41, characterized in that, The first RNTI is configured according to the granularity of the CDM group. The network device according to any one of claims 40-42 is characterized in that, The network device also includes: The second sending module is configured to send a first signaling message to the terminal device, wherein the first signaling message is used for one or more of the following: Activate one or more CDM groups to execute the configuration information for the first PUSCH transmission; Deactivate the configuration information for one or more CDM groups to execute the first PUSCH transmission; Schedule one or more CDM groups to perform the first PUSCH transmission. The network device according to claim 43 is characterized in that, The first signaling includes the identifier of the first CDM group. The network device according to claim 43 is characterized in that, The configuration information includes the first RNTI, and there is a one-to-one correspondence between the first RNTI and the one or more CDM groups. The network device according to claim 43 is characterized in that, The configuration information includes the mapping relationship between CDM groups and PDCCH search space sets, and different CDM groups correspond to different PDCCH search space sets. The network device according to claim 46 is characterized in that: The activation and / or deactivation of the configuration information transmitted in the first PUSCH is determined based on the PDCCH search space set, or based on the PDCCH search space set and the first RNTI; and / or, The execution of the first PUSCH transmission is determined based on the PDCCH search space set, or based on the PDCCH search space set and the first RNTI. The network device according to any one of claims 40-47 is characterized in that, The OCC-related parameters include one or more of the following: OCC scheme, OCC length, OCC codeword table, and OCC codeword index. The network device according to claim 48 is characterized in that, The OCC scheme includes one or more of the following: cross-symbol OCC scheme, cross-time slot OCC scheme, and intra-symbol OCC scheme. The network device according to any one of claims 40-49 is characterized in that, The configuration information is carried in Radio Resource Control (RRC) signaling. A terminal device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or send signals so that the terminal device performs the method as described in any one of claims 1-14. A network device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the network device performs the method as described in any one of claims 15-25. An apparatus characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1-14 or 15-25. A chip characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-14 or 15-25. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-14 or 15-25. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-14 or 15-25. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-14 or 15-25.

Images