Wireless communication method, terminal device and network device

Abstract

The invention provides a wireless communication method, terminal equipment and network equipment. The wireless communication method comprises: a terminal device receiving configuration information sent by a network device, the configuration information being used for configuring a scheduling parameter of a first PUSCH transmission, the first PUSCH transmission being a PUSCH transmission based on an OCC, and the configuration information comprising an OCC related parameter.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method, terminal equipment and network equipment. Background Art

[0002] Orthogonal cover code (OCC) technology can generate a set of orthogonal code sequences to spread and encode the signal to be transmitted, thereby improving the system capacity, spectrum efficiency and anti-interference ability. Therefore, OCC multiplexing in physical uplink shared channel (PUSCH) transmission can effectively improve the uplink transmission capacity of the system. In this scenario, how to implement OCC multiplexing of PUSCH is a problem that needs to be solved. Summary of the invention

[0003] The present application provides a wireless communication method, terminal equipment and network equipment. The following introduces various aspects involved in the present application.

[0004] In a first aspect, a method for wireless communication is provided, comprising: a terminal device receives configuration information sent by a network device, the configuration information being used to configure 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.

[0005] In a second aspect, a method for wireless communication is provided, comprising: a network device sends configuration information to a terminal device, the configuration information being used to configure 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.

[0006] According to a third aspect, a terminal device is provided, comprising: a first receiving module for receiving configuration information sent by a network device, wherein the configuration information is used to configure 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.

[0007] In a fourth aspect, a network device is provided, comprising: a first sending module, used to send configuration information to a terminal device, wherein the configuration information is used to configure 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.

[0008] In a fifth aspect, a terminal device is provided, comprising 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 call the computer program in the memory so that the terminal device executes part or all of the steps in the method of the first aspect.

[0009] In a sixth aspect, a network device is provided, comprising 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 call the computer program in the memory so that the network device executes part or all of the steps in the method of the second aspect.

[0010] In a seventh aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned terminal device and / or network device. In another possible design, the system may also include other devices that interact with the terminal device or network device in the solution provided by the embodiment of the present application.

[0011] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program enables a computer to execute part or all of the steps in the methods of the above aspects.

[0012] In a ninth aspect, an embodiment of the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute some or all of the steps in the above-mentioned various aspects of the method. In some implementations, the computer program product can be a software installation package.

[0013] In the tenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0014] In the embodiment of the present application, the network device may indicate OCC-related parameters to the terminal device in the configuration information. In this way, when the terminal device performs the first PUSCH transmission, it may implement OCC multiplexing of the first PUSCH transmission according to the OCC-related parameters carried in the configuration information, thereby making the OCC-based PUSCH transmission more flexible. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 This is an example diagram of the system architecture of a wireless communication system to which the embodiments of the present application can be applied.

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

[0017] Figure 3 It is a schematic diagram of the retransmission process of the terminal device of OCC multiplexing.

[0018] Figure 4 It is a flowchart of configuration scheduling.

[0019] Figure 5 This is another flowchart for configuring scheduling.

[0020] Figure 6 It is a flowchart of a wireless communication method provided by an embodiment of the present application.

[0021] Figure 7 It is a schematic diagram of a possible resource occupancy mode of the first PUSCH transmission.

[0022] Figure 8 This is a diagram showing the relationship among CORESET, CCE, and REG.

[0023] Fig. 9 It is a flowchart of a wireless communication method provided by another embodiment of the present application.

[0024] Fig.10 It is a flowchart of a wireless communication method provided by another embodiment of the present application.

[0025] Fig.11 It is a flowchart of a wireless communication method provided by another embodiment of the present application.

[0026] Fig.12 It is a flowchart of a wireless communication method provided by another embodiment of the present application.

[0027] Fig.13 It is a schematic diagram of the structure of the terminal device provided in an embodiment of the present application.

[0028] Fig.14 It is a structural diagram of the network device provided in an embodiment of the present application.

[0029] Fig.15 It is a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0030] Communication system architecture

[0031] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, advanced long term evolution (LTE-A) system, new radio (NR) system, evolution system 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), wireless fidelity (WLAN-based access to unlicensed spectrum, NR-U) system, non terrestrial network (NTN) system, universal mobile telecommunication system (UMTS), wireless local area networks (WLAN), wireless Fidelity (WLAN-based access to unlicensed spectrum, NR-U) system, etc. fidelity, WiFi), fifth-generation communication (5G) systems or other communication systems, such as future communication systems, such as sixth-generation mobile communication systems, and satellite communication systems.

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

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

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

[0035] The embodiments of the present application can be applied to NTN systems and terrestrial networks (TN) systems. As an example and not a limitation, the NTN system includes an NR-based NTN system and an Internet of Things (IoT)-based NTN system. Exemplarily, in the scenario where narrowband Internet of Things (NB-IoT) and enhanced machine type communication (eMTC) are connected to NTN, the system composed of IoT terminal devices and NTN networks can be understood as an IoT-based NTN system.

[0036] The embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, wherein the terminal equipment 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 equipment, user agent or user device, etc.

[0037] In an embodiment of the present application, the terminal device may be a station (STATION, ST) in a WLAN, and may be 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 function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted 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.

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

[0039] The network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may also be referred to as an access network device or a wireless access network device, such as a base station. The network device in the embodiment of the present application may refer to a wireless access network (RAN) node (or device) that connects a terminal device to a wireless network. The base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The base station may also refer to a communication module, modem or chip used to be set in the aforementioned device or apparatus. The base station may also be a mobile switching center and a device to device D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communication device that performs the base station function, a network side device in a 6G network, and a device that performs the base station function in a future communication system. The base station may support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network equipment.

[0040] 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 based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0041] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device includes a CU and a DU. The gNB may also include an AAU.

[0042] The network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on aircraft, balloons and satellites in the air. The embodiments of the present application do not limit the scenarios in which the network equipment and terminal equipment are located.

[0043] As an example and not limitation, in an embodiment of the present application, the network device may have a mobile characteristic, for example, the network device may be a mobile device. In some embodiments of the present 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 the present application, the network device may also be a base station set up in a location such as land or water.

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

[0045] For example, Figure 1 The following is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application. Figure 1 As shown, 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 referred to as a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographical area and may communicate with terminal devices located in the coverage area. For example, the network device may be a satellite.

[0046] Figure 1A network device and two terminal devices are shown exemplarily. In some embodiments of the present application, the communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0047] It should be noted that Figure 1 The system to which the present application is applicable is only illustrated in the form of an example. Of course, the method shown in the embodiment of the present application can also be applied to other systems, such as a 6G system, a NR system, etc. The embodiment of the present application does not specifically limit this.

[0048] In some embodiments of the present application, Figure 1 The wireless communication system shown may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), but this is not limited in the embodiments of the present application.

[0049] For ease of understanding, some relevant technical knowledge involved in the embodiments of the present application is first introduced. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0050] NTN

[0051] Currently, the 3rd Generation Partnership Project (3GPP) is studying NTN technology. NTN system can be broadly understood as a general term for all networks involving flying objects, including satellite communication networks, high-altitude platform systems, air-to-ground networks, etc. Exemplarily, NTN system can include satellite communication networks, such as low-orbit satellite communication networks.

[0052] NTN can provide communication services to ground users by means of satellite communication. Compared with ground communication networks (for example, ground cellular network communication), satellite communication has many unique advantages.

[0053] First, satellite communications are not limited by the user's geographical location. For example, general ground communication networks cannot cover areas such as oceans, mountains, deserts, etc. where network equipment cannot be set up. Or, ground communication networks cannot cover certain areas that are not covered due to sparse population. For satellite communications, since a satellite can cover a larger ground area and the satellite can orbit the earth, in theory, every corner of the earth can be covered by the satellite communication network.

[0054] Secondly, satellite communications have great social value. Satellite communications can cover remote mountainous areas, poor and backward countries or regions at a relatively low cost, so that people in these areas can enjoy advanced voice communications and mobile Internet technologies. From this perspective, satellite communications are conducive to narrowing the digital divide with developed regions and promoting the development of these regions.

[0055] Again, satellite communication has a long distance, and the communication cost does not increase significantly with the increase of communication distance.

[0056] Finally, satellite communications are highly stable and not affected by natural disasters.

[0057] Communication satellites can be divided into LEO satellites, MEO satellites, GEO satellites, HEO satellites, etc. according to the different orbital altitudes. At present, the main research is on LEO satellites and GEO satellites.

[0058] With the development and popularization of NTN technology, more and more terminal devices can be connected to NTN. As a result, the amount of uplink data of NTN will continue to increase, and users' demand for the continuity and stability of NTN services will continue to increase, and the demand for NTN uplink capacity enhancement will also increase.

[0059] OCC

[0060] OCC technology is a spread spectrum and coding technology used in wireless communications. OCC technology can spread spectrum and encode the signal to be transmitted by generating a set of orthogonal code sequences, thereby improving the system's capacity, spectrum efficiency and anti-interference ability. In NTN, OCC technology has been applied in the physical uplink control channel (PUCCH). The practical results of OCC technology in PUCCH show that OCC technology can code-division multiplex the antenna ports of different terminal devices in the same code division multiplexing (CDM) group, thereby effectively enhancing the uplink capacity of the NTN system. In other words, the practice of OCC technology in PUCCH proves the feasibility of OCC multiplexing technology in enhancing the uplink capacity of the NTN system.

[0061] Radio network temporary identifier (RNTI)

[0062] Similar to the 4G LTE system, in the 5G NR system, the identifier assigned to the terminal device on the wireless side (base station side) is called RNTI. The role of RNTI in the blind detection process of the physical downlink control channel (PDCCH) is mainly reflected in the ability to distinguish different terminal devices and different message types. As an implementation method, network equipment (such as a base station) can scramble the cyclic redundancy check (CRC) part of the wireless channel information (such as control information and / or data) through RNTI. In this way, if the RNTI corresponding to the terminal device is different, even if the terminal device receives the wireless channel information, it cannot be decoded correctly, thereby distinguishing different terminal devices.

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

[0064] Hybrid automatic repeat request (HARQ)

[0065] HARQ is a technology that combines automatic repeat request (ARQ) and forward error correction (FEC). For ease of understanding, ARQ and FEC are briefly introduced first. FEC technology adds redundant information to the data block to be transmitted, so that the receiving end can correct some errors and reduce the number of retransmissions. For errors that FEC cannot correct, the receiving end needs to request the sending end to resend the data block according to the ARQ mechanism. For example, the sending end can add a CRC data segment to the data block to be transmitted so that the receiving end can detect the CRC data segment to determine whether the received data is erroneous. In some embodiments, if the receiving end determines that the data block is not erroneous, it can send an acknowledgment (ACK) to the sending end, and then the sending end continues to send new data. In some embodiments, if the receiving end determines that the data block is erroneous, it can send a negative acknowledgment (NACK) to the sending end, and then the sending end retransmits the same data. In some embodiments, if the sending end does not receive a reply from the receiving end within a specified time, the sending end considers that the transmission has failed, and in this case the sending end will automatically retransmit the same data.

[0066] As an example, the medium access control (MAC) layer can add a CRC data segment to the end of the data sent to the radio link control (RLC) layer so that the RLC layer can detect it to determine whether the received data is erroneous; if there is no error, the RLC layer can reply ACK to the MAC layer, and then the MAC layer can send new data; if there is an error, the RLC layer can reply NACK to the MAC layer, and then the MAC layer can retransmit the same data.

[0067] HARQ can combine FEC and ARQ, or in other words, HARQ is a hybrid retransmission request method. When the sender and the receiver perform data transmission based on HARQ, the receiver can store the previously received data at the receiver. In this way, the receiver can combine the retransmitted data with the previously received data and decode them. This process can also be called soft combining. Compared with ARQ, HARQ has a certain diversity gain, which can reduce the number of retransmissions and thus reduce the transmission delay. This is because the traditional ARQ technology simply and directly discards the erroneous data instead of storing it, and there is no soft combining process. Therefore, ARQ has no diversity gain, the number of retransmissions may be more, and the transmission delay is relatively long.

[0068] HARQ can use a stop-and-wait protocol to send data. That is, the sender will stop and wait for confirmation after sending each transport block (TB). In this scenario, a single-process HARQ will result in low transmission efficiency. Therefore, the communication system generally uses multiple stop-and-wait processes, that is, multiple HARQ processes for data transmission. In the scenario where multiple HARQ processes are used for data transmission, when a HARQ process is waiting for confirmation information, the sender can use another HARQ process to continue sending data. Figure 2 The process of using a stop-and-wait protocol to transmit data in multiple HARQ processes is introduced.

[0069] like Figure 2 As shown, it is assumed that there are five transmission blocks to be transmitted, namely transmission blocks 1, 2, 3, 4 and 5. Figure 2 Three transmission processes are shown. In the first transmission process, the transmitter transmits transmission blocks 1, 2, and 3, and these three transmission blocks are transmitted using HARQ processes 0, 1, and 2 respectively. A transmission error occurred in transmission block 1 during the first transmission process, so transmission block 1 started the HARQ retransmission mechanism during the second transmission process. Therefore, in the second transmission process, the transmitter transmits transmission blocks 1, 4, and 5, and these three transmission blocks are transmitted using HARQ processes 0, 1, and 2 respectively. A transmission error occurred again in transmission block 1 during the second transmission process, so the transmission block will start the HARQ retransmission mechanism again during the third transmission process. Therefore, in the third transmission process, the transmitter transmits transmission block 1, which is still transmitted using HARQ process 0. After the third transmission, transmission blocks 1, 2, 3, 4, and 5 are all transmitted successfully.

[0070] The HARQ process may include a synchronous HARQ process and an asynchronous HARQ process. For example, in a 5G NR system, the HARQ process may include a synchronous HARQ process and an asynchronous HARQ process. The following describes a method for determining the process number of an asynchronous HARQ process and the process number of a synchronous HARQ process.

[0071] The process number of the asynchronous HARQ process can be indicated by the HARQ process number (HPN) field in the corresponding DCI. As shown in Table 1, there is an HPN field in the DCI used to schedule PUSCH, and different values ​​of the HPN field correspond to different HARQ processes. In this way, the transmitter can use the stop-and-wait protocol to efficiently retransmit data according to the HPN indicated in the DCI. The number of bits occupied by the HPN field shown in Table 1 is 4, indicating that the DCI can indicate up to 16 HARQ processes, such as HARQ processes 0-15.

[0072] Table 1

[0073] Field (entry) Number of bits DCI format identifier 1 Frequency Domain Resource Allocation 4 Time Domain Resource Allocation × Frequency hopping indication 1 Modulation and coding schemes 5 New data indication 1 Redundant version 2 HPN 4 Scheduled PUSCH transmission power control command 2 Uplink / Supplementary Uplink Indication 0 or 1

[0074] In some embodiments, the asynchronous HARQ process may correspond to a dynamic scheduling approach.

[0075] The process number of the synchronous HARQ process can be calculated by the transmitting end according to a formula. In some embodiments, the calculation of the process number of the synchronous HARQ process is associated with information such as the first symbol of the PUSCH scheduling and the period of PUSCH transmission. For example, the transmitting end can calculate the process number of the synchronous HARQ process based on the current symbol, the high-level configuration and the corresponding formula. As an example, when starting to send PUSCH, the transmitting end (such as a terminal device) can calculate the HPN corresponding to the current PUSCH based on the formula in the 3GPP protocol TR38.3215.4.1. As an example, for uplink authorization scheduling that does not use harqProcID-Offset2 or cg-RetransmissionTimer configuration, the calculation formula for the synchronous HARQ process number corresponding to PUSCH is as follows:

[0076] HPN=[floor(CURRENT_symbol / periodicity)]modulonrofHARQ―Process

[0077] Among them, CURRENT_symbol represents the time domain start symbol of PUSCH, periodicity represents the period of PUSCH transmission, and nrofHARQ-Process represents the number of HARQ processes. For a detailed introduction to the above formula, please refer to the relevant protocol (such as 3GPP protocol), which will not be repeated here.

[0078] In some embodiments, the synchronous HARQ process may correspond to a semi-static scheduling method based on a configured grant (CG).

[0079] In some embodiments, the time domain symbols of all terminal devices performing OCC multiplexing in the same CDM group are the same. Therefore, when the HARQ process number is calculated according to the synchronous HARQ process, the HPN in the same CDM group is consistent.

[0080] 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 considered that each terminal device is equipped with a HPN. In this scenario, the retransmission of the terminal devices that perform OCC multiplexing in the same CDM group needs to be performed synchronously. However, if a terminal device receives an ACK, the terminal device does not need to perform retransmission synchronously. The specific process is as follows Figure 3 As shown. Figure 3 As shown, terminal devices 1 to 4 are terminal devices of OCC multiplexing in the same CDM group. In the first transmission process, terminal devices 1 and 4 transmit successfully, and there is no need to perform synchronous retransmissions later, while terminal devices 2 and 3 fail to transmit and need to perform synchronous retransmissions in the second transmission process. In the second transmission process, terminal device 2 transmits successfully, while terminal device 3 fails to transmit. Therefore, in the third transmission process, only terminal device 3 retransmits.

[0081] Configured Scheduling (CS)

[0082] In the 5G NR system, resource scheduling of terminal devices can be performed by configuring scheduling. In this mechanism, network devices (such as gNB) can schedule PDSCH / PUSCH transmissions without using DCI in each transmission. That is, the network device can configure all scheduling parameters for the terminal device in the radio resource control (RRC) signaling, and both the network device and the terminal device should transmit data on PDSCH and PUSCH according to the parameters specified in the RRC signaling. This method can help network devices reduce the load of physical layer and MAC layer scheduling.

[0083] However, one disadvantage of the above mechanism is that the network equipment cannot change the scheduling parameters of a single transmission, so when the channel conditions become very bad, there may be some problems with wireless link adaptation.

[0084] In some embodiments, there are two different types of configuration scheduling processes for uplink configuration authorization in the uplink, namely type 1 configuration scheduling and type 2 configuration scheduling. Figure 4 and Figure 5 The two types of configuration scheduling processes are introduced respectively.

[0085] Figure 4 The following is a flow chart of the configuration scheduling process for type 1. Figure 4 As shown, the process of configuring scheduling of type 1 may include step S410 and step S420.

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

[0087] In some embodiments, the network device may configure all parameters required for PUSCH scheduling to the terminal device through RRC configuration.

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

[0089] In some embodiments, once the terminal device processes the RRC configuration, the PUSCH is sent without any specific lower layer trigger (such as a DCI trigger).

[0090] Figure 5 The following is a flow chart of the configuration scheduling process for type 2. Figure 5 As shown, the process of configuring scheduling of type 2 may include steps S510 to S530.

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

[0092] In some embodiments, the network device may configure all parameters required for PUSCH scheduling to the terminal device through RRC configuration.

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

[0094] In some embodiments, when the network device wants to start granting (or scheduling) PUSCH, the network device may send a DCI to activate the above RRC configuration.

[0095] In some embodiments, the DCI is scrambled with a configured scheduling RNTI (CS-RNTI).

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

[0097] In some embodiments, once the terminal device processes the DCI, it can send PUSCH according to the above RRC configuration.

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

[0099] From the above description, it can be seen that performing OCC multiplexing in PUSCH transmission can effectively improve the uplink transmission capacity of the system (such as the NTN system). Then, in this scenario, how to implement OCC multiplexing of PUSCH is a problem that needs to be solved.

[0100] In view of the above problems, the present application provides a wireless communication method, terminal device and network device, which can implement OCC multiplexing of PUSCH based on OCC related parameters. The method embodiment of the present application is first introduced below.

[0101] Figure 6 It is a flowchart of a wireless communication method provided by an embodiment of the present application. Figure 6 The method shown is introduced from the perspective of interaction between a terminal device and a network device. The terminal device and the network device may be, for example, Figure 1 The terminal device 120 and the network device 110 are shown. In some embodiments, the embodiments of the present application may be applied to an NTN system, but the embodiments of the present application are not limited thereto. For example, the embodiments of the present application may be applied to a TN system.

[0102] Figure 6 The method shown may include step S610, which is described below.

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

[0104] In an embodiment of the present application, the configuration information may be used to configure (or indicate) scheduling parameters for the first PUSCH transmission. In other words, the configuration information may be used to schedule the first PUSCH transmission. In some embodiments, the configuration information may be used to configure CG parameters (or semi-static scheduling parameters). In some embodiments, the configuration information may be used to configure dynamic grant (DG) parameters.

[0105] In the embodiment of the present application, the first PUSCH transmission is an OCC-based PUSCH transmission. That is, when the terminal device performs the first PUSCH transmission, OCC multiplexing can be implemented through the OCC technology, so that the antenna port can be code-division multiplexed with other terminal devices on the same time-frequency resources, effectively enhancing the uplink capacity of the system.

[0106] In some embodiments, the first PUSCH transmission may be performed based on preconfigured uplink resources (such as CG resources). In some embodiments, the first PUSCH transmission may be performed based on dynamically scheduled uplink resources (such as DG resources).

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

[0108] The embodiments of the present application do not specifically limit the OCC-related parameters, as long as the parameters are related to implementing OCC multiplexing of the first PUSCH. Exemplarily, the OCC-related parameters may include one or more of the following: OCC scheme, OCC length, OCC codeword table, OCC codeword index.

[0109] 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. The embodiment of the present application does not limit the OCC scheme. Exemplarily, the OCC scheme can include one or more of the following: an OCC scheme across symbols, an OCC scheme across time slots, and an OCC scheme within a symbol.

[0110] In the cross-symbol OCC scheme, each symbol can be repeated M times, where M is the number of multiplexed terminal devices. In other words, an original symbol can be repeated M times in the time domain to become M symbols, and then each repeated symbol will be superimposed with an OCC codeword to achieve OCC multiplexing of the first PUSCH transmission. Taking 4 terminal devices for OCC multiplexing as an example, in the cross-symbol OCC scheme, each symbol can be repeated 4 times, and each repeated symbol will be superimposed with an OCC codeword.

[0111] In the cross-time slot OCC scheme, each time slot can be repeated M times, where M is the number of multiplexed terminal devices. In other words, the original time slot can be repeated M times in the time domain, becoming M time slots, and then each repeated time slot will be superimposed with an OCC codeword to achieve OCC multiplexing of the first PUSCH transmission. Taking 4 terminal devices for OCC multiplexing as an example, in the cross-time slot OCC scheme, each time slot can be repeated 4 times, and each repeated time slot will be superimposed with an OCC codeword.

[0112] The intra-symbol OCC scheme can use the oversampling characteristics of discrete Fourier transform (DFT) to comb-map the data of the terminal device to different subcarriers of a symbol. That is, 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, and then the data corresponding to the different values ​​in the OCC sequence (such as the Walsh sequence) can be comb-mapped to the subcarriers of the frequency domain resource unit through DFT. Taking OCC multiplexing of 4 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 the data corresponding to the different values ​​in the OCC sequence can be comb-mapped to the subcarriers of the resource block through DFT.

[0113] 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 the embodiments of the present application.

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

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

[0116] The embodiment of the present application does not limit the sequence for generating the OCC codeword. Exemplarily, the OCC codeword can be generated based on one or more of the following sequences: Walsh sequence, Gold sequence, Zadoff-Chu sequence, pseudo-random code, etc.

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

[0118] Table 2

[0119]

[0120]

[0121] 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 according to 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 the 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 based on the OCC codeword index and the OCC codeword table as [1 -1 1 -1 1 -1 1 -1].

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

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

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

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

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

[0127] In some embodiments, the first signaling may be used to schedule the terminal device to perform the first PUSCH transmission. For example, in a dynamic scheduling scenario, the first signaling may be used to schedule the terminal device to perform the first PUSCH transmission.

[0128] In some embodiments, the first signaling may be DCI signaling. The embodiment of the present application does not limit the format of the first signaling, and taking the first signaling as DCI signaling as an example, the first signaling may be DCI format 0_0.

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

[0130] The embodiments of the present application do not specifically limit the information carried by the first signaling. For example, the first signaling may carry an identifier of a CDM group (see the embodiments below). Alternatively, the first signaling may carry uplink authorization information (such as an activation indication or a deactivation indication). Alternatively, the first signaling may carry relevant parameters such as time domain resources, frequency domain resources, modulation and coding schemes, etc.

[0131] It can be seen that in some scenarios, the execution of the first PUSCH transmission may depend on the channel carrying the first signaling (such as PDCCH), so that the capacity of the channel carrying the first signaling may limit the OCC multiplexing of the first PUSCH transmission. For example, in the scenario where the first PUSCH transmission is executed based on the configuration scheduling of type 2, 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. For another example, in the 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 takes the case where the first signaling is DCI signaling and the OCC scheme is an OCC scheme across time slots as an example to illustrate this issue.

[0132] like Figure 7 As shown, it is assumed that the resource occupancy in the first PUSCH transmission process is 24 physical resource blocks (PRBs) and 4 time slots. In the scenario where the cross-time slot OCC solution is adopted, 4 terminal devices can be multiplexed at the same physical resource.

[0133] Assume that the resources occupied by the PDCCH transmission are consistent with the resources occupied by the first PUSCH transmission, that is, 24 PRBs and 4 time slots. When the network device activates and / or deactivates the configuration information for performing the first PUSCH transmission through the first signaling, or performs 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.

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

[0135] In some embodiments, the first signaling may be carried by CORESET in PDCCH. Figure 8 As shown, 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).

[0136] In some embodiments, the PDCCH may be composed of n consecutive CCEs, where n is the aggregation degree. The aggregation degree may be used to indicate the number of CCEs required by a terminal device. The corresponding relationship between the aggregation degree and CCE is given below in conjunction with Table 3.

[0137] Table 3

[0138] Degree of Polymerization Number of CCEs 1 1 2 2 4 4 8 8 16 16

[0139] As can be seen from Table 3, the value of the aggregation degree may include one of the following: 1, 2, 4, 8, 16. The higher the value of the aggregation degree, the more CCEs the terminal device needs. For example, when the aggregation degree is 1, each terminal device needs to be indicated by one CCE. For another example, when the aggregation degree is 2, each terminal device needs to be indicated by two CCEs. In some embodiments, the higher the aggregation degree, the more reliable the demodulation of the DCI will be.

[0140] In the scenario where 4 terminal devices perform OCC multiplexing transmission, taking the aggregation degree as 1 as an example, when the resources occupied by PDCCH transmission include 24 PRBs and 4 time slots, the number of terminal devices that PDCCH can serve is 24*4=96, so 96 CCEs are required for indication. Considering that each CORESET can include up to 12 CCEs, 96 CCEs require 8 CORESETs, which will occupy about 43% of PDCCH resources, resulting in limited PDCCH downlink capacity or insufficient PDCCH resources.

[0141] In response to the above problems, the embodiments of the present application propose that the first signaling can be used to activate and / or deactivate the configuration information of the terminal device group, or the first signaling can be used to schedule the terminal device group to perform the first PUSCH transmission. For example, in the scenario of type 2 configuration scheduling, the network device can use the first signaling to activate and / or deactivate the configuration information of the terminal device group. For another example, in the scenario of dynamic scheduling, the network device can use the first signaling to schedule the terminal device group to perform the first PUSCH transmission. This is described in detail below.

[0142] In some embodiments, the terminal device group may be a CDM group. That is, the embodiment of the present application may utilize the first signaling to implement activation and / or deactivation of configuration information of all terminal devices in the CDM group with the CDM group as the granularity, or the embodiment of the present application may utilize the first signaling to schedule all terminal devices in the CDM group to perform the first PUSCH transmission with the CDM group as the granularity.

[0143] In some embodiments, the first signaling can be used to indicate one or more of the following: activating configuration information for one or more CDM groups to perform a first PUSCH transmission, deactivating configuration information for one or more CDM groups to perform a first PUSCH transmission, and scheduling one or more CDM groups to perform a first PUSCH transmission.

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

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

[0146] As yet another example, the first signaling may be used to schedule one or more CDM groups to perform a first PUSCH transmission.

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

[0148] In some embodiments, in a dynamic scheduling scenario, the first signaling may be used to schedule one or more CDM groups to perform a first PUSCH transmission.

[0149] 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: an identifier of the CDM group to which the terminal device belongs, a first RNTI, and a mapping relationship between the CDM group and the PDCCH search space set.

[0150] 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 is necessary to activate and / or deactivate the configuration information based on the instruction of the network device, or whether it is necessary to perform the first PUSCH transmission based on the instruction of the network device, based on the identifier of the CDM group to which the terminal device belongs.

[0151] 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 identifier of the CDM group in the first signaling. Taking the number of data bits of the identifier of the CDM group in the first signaling as 4 as an example, the value range of the identifier of the CDM group to which the terminal device belongs can be 0-15. Taking the number of data bits of the identifier of the CDM group in the first signaling as 5 as an example, the value range of the identifier of the CDM group to which the terminal device belongs can be 0-31.

[0152] The first RNTI may be used to scramble and / or descramble the PDCCH that schedules the first PUSCH transmission. In some embodiments, the first RNTI may be an RNTI specifically used for scheduling the first PUSCH transmission. Therefore, in some embodiments, the first RNTI may also be understood or referred to as OCC-RNTI to be specifically used for scheduling the first PUSCH transmission.

[0153] In some embodiments, the first RNTI is configured according to the granularity of the CDM group. That is, the first RNTIs corresponding to the terminal devices in the same CDM group are the same.

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

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

[0156] In some embodiments, the mapping relationship between the CDM group and the PDCCH search space set is intended to ensure that different CDM groups with the same first RNTI can be configured with different PDCCH search space sets, so that different CDM groups can be identified by the PDCCH search space sets.

[0157] 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, so that different CDM groups can be identified by the PDCCH search space sets. For another example, the mapping relationship between the CDM group and the PDCCH search space set can be a one-to-one mapping relationship, so that the CDM group can be uniquely identified by the PDCCH search space set.

[0158] In some embodiments, the mapping relationship between the CDM group and the PDCCH search space set is indicated by a mapping relationship between an identifier of the CDM group and an identifier of the PDCCH search space set.

[0159] The embodiments of the present application do not limit how to activate and / or deactivate the configuration information of the CDM group based on the first signaling, or how to implement the scheduling of the CDM group based on the first signaling. The following takes the scenarios of type 2 configuration scheduling and dynamic scheduling as examples to provide several implementation methods.

[0160] Embodiment 1: First signaling implements activation and / or deactivation of configuration information of a CDM group

[0161] Embodiment 1 can be applied to the scenario of type 2 configuration scheduling. In the scenario of type 2 configuration scheduling, after the terminal device receives the configuration information sent by the network device, it will not immediately perform the first PUSCH transmission, but will start the uplink transmission after receiving the first signaling indicating the activation of the configuration information. That is to say, in Embodiment 1, the network device can activate the configuration information for the first PUSCH transmission based on the first signaling and / or activate all terminal devices in the CDM group. The first signaling can carry uplink authorization information (such as an activation indication or a deactivation indication), and may also include information such as time domain resources, frequency domain resources, modulation and coding schemes, etc.

[0162] Embodiment 1 can realize activation and / or deactivation of the configuration information of the CDM group, thereby alleviating the problem of limited downlink resources.

[0163] As an implementation method, Example 1 may explicitly indicate the CDM group that needs to be activated and / or deactivated. As another implementation method, Example 1 may implicitly indicate the CDM group that needs to be activated and / or deactivated. The embodiments of the present application do not limit the manner in which Example 1 implicitly indicates the CDM group that needs to be activated and / or deactivated. For example, the network device may implicitly indicate the CDM group that needs to be activated and / or deactivated through one or more of the following: the first RNTI, the PDCCH search space set.

[0164] The implementation methods of Example 1 are introduced below.

[0165] Implementation 1: The first signaling explicitly indicates the CDM group that needs to be activated and / or deactivated

[0166] In implementation mode 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 the 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.

[0167] In implementation method 1, the first RNTI corresponding to the terminal devices in the same CDM group is the same, and the first RNTIs corresponding to different CDM groups may be the same or different. In other words, the maximum number of CDM groups that a first RNTI can accommodate is related to the number of data bits for the identification of the CDM group in the first signaling. Taking the number of data bits for the identification of the CDM group in the first signaling as 4 as an example, this means that a first RNTI can be used for activation and / or deactivation of 16 CDM groups. Taking the number of data bits for the identification of the CDM group in the first signaling as 5 as an example, this means that a first RNTI can be used for activation and / or deactivation of 32 CDM groups.

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

[0169] In some embodiments, the first CDM group is a CDM group that needs to be activated. In some embodiments, the first CDM group may be any one or more CDM groups, which is not limited in the embodiments of the present application.

[0170] In some embodiments, the first signaling may include other information in addition to the identifier of the first CDM group. For example, the first signaling may include uplink authorization information, such as one or more of time domain resources, frequency domain resources, modulation and coding schemes, and the like.

[0171] 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 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 it is necessary to activate the configuration information for executing the first PUSCH transmission based on the comparison.

[0172] The identifier of the CDM group configured with the network device as the terminal device is idxCDM UE , the identifier of the first CDM group is idxCDM A For example, after the terminal device successfully descrambles the first signaling, it needs to carry the idxCDM A idxCDM pre-configured with network equipment UE For comparison. If idxCDM UE =idxCDM A , 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.

[0173] 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 sending activation indication signaling to each terminal device separately.

[0174] In some embodiments, after the terminal device activates the configuration information of the first PUSCH transmission based on the first signaling, the first PUSCH transmission can be performed based on the configuration information.

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

[0176] In some embodiments, the first CDM group is a CDM group that needs to be deactivated. In some embodiments, the first CDM group may be any one or more CDM groups among one or more CDM groups that have been activated, which is not limited in the embodiments of the present application.

[0177] 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 executing the first PUSCH transmission. Taking the first signaling encrypted 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 it is necessary to deactivate the configuration information for executing the first PUSCH transmission based on the comparison.

[0178] The identifier of the CDM group configured with the network device as the terminal device is idxCDM UE , the identifier of the first CDM group is idxCDM A For example, after the terminal device successfully descrambles the first signaling, it needs to carry the idxCDM A idxCDM pre-configured with network equipment UE For comparison. If idxCDM UE =idxCDM A , and the first signaling is used to indicate the deactivation of the configuration information of the first PUSCH transmission, then the terminal device deactivates the configuration information of the first PUSCH transmission.

[0179] Implementation 2: Implicitly indicating the CDM groups that need to be activated and / or deactivated based on the first RNTI

[0180] 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.

[0181] 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, the first RNTI corresponding to each CDM group is different). In this way, different first RNTIs can represent different CDM groups, so that the terminal device can determine the CDM group activated and / or deactivated by the first signaling indication based on the first RNTI.

[0182] In implementation method 2, the first RNTI corresponding to each terminal device in the same CDM group is the same.

[0183] Afterwards, the network device may send a first signaling to the terminal device to activate one or more CDM groups to perform configuration information for the first PUSCH transmission. In implementation 2, the format of the first signaling does not need to be changed compared to the current activation signaling and / or deactivation signaling, which can better achieve backward compatibility.

[0184] As an implementation method, if the terminal device successfully descrambles the first signaling, the terminal device activates the configuration information for performing 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, the terminal device activates the configuration information for the first PUSCH transmission. In this case, each terminal device participating in OCC multiplexing in the same CDM group will be collectively activated. Afterwards, the terminal device can perform the first PUSCH transmission based on the configuration information for the first PUSCH transmission.

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

[0186] As an implementation method, if the terminal device successfully descrambles the first signaling, the terminal device deactivates the configuration information for performing 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 deactivating the first PUSCH transmission, the terminal device deactivates the configuration information for the first PUSCH transmission. In this case, each terminal device participating in OCC multiplexing in the same CDM group will be collectively deactivated.

[0187] Implementation method 2 does not need to change the format of the current activation DCI, but directly allows different first RNTIs to represent different CDM groups, that is, different CDM groups correspond to different first RNTIs, thereby avoiding the process of the terminal device determining the identifier of the CDM group.

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

[0189] In implementation mode 3, when the network device sends configuration information to the terminal device, the configuration information may include OCC related parameters, CDM group identifiers, and a mapping relationship between CDM groups and PDCCH search space sets. Of course, in addition to the above information, the configuration information may also include other information, such as the first RNTI.

[0190] In implementation manner 3, different CDM groups may correspond to different PDCCH search space sets. In this way, different CDM groups will search and descramble the first signaling in different PDCCH search space sets.

[0191] In implementation mode 3, the identifier of the CDM group may be determined by the number of CDM groups and the PDCCH search space set. For example, terminal devices with different CDM group identifiers may be distributed in different CDM groups and correspond to different PDCCH search space sets.

[0192] In implementation mode 3, the first RNTIs corresponding to the terminal devices in the same CDM group are the same. The maximum number of CDM groups that can be accommodated by a first RNTI is the total number of CDM group identifiers (eg, 16).

[0193] Afterwards, the network device may send a first signaling to the terminal device to activate one or more CDM groups to perform configuration information for the first PUSCH transmission. In implementation mode 3, the format of the first signaling does not need to be changed compared to the current activation signaling and / or deactivation signaling, which can better achieve backward compatibility.

[0194] As an implementation method, if the terminal device successfully descrambles the first signaling in the PDCCH search space set corresponding to the terminal device, the terminal device activates the configuration information for executing the first PUSCH transmission. For example, if the terminal device searches for the first signaling encrypted with 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 activating the first PUSCH transmission, the terminal device activates the configuration information for the first PUSCH transmission. In this case, each terminal device participating in OCC multiplexing in the same CDM group will be collectively activated. Afterwards, the terminal device can perform the first PUSCH transmission based on the configuration information of the first PUSCH transmission.

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

[0196] As an implementation method, if the terminal device successfully descrambles the first signaling in the PDCCH search space set corresponding to the terminal device, the terminal device deactivates the configuration information for executing the first PUSCH transmission. For example, if the terminal device searches for the first signaling encrypted with 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, the terminal device deactivates the configuration information for the first PUSCH transmission. In this case, each terminal device participating in OCC multiplexing in the same CDM group will be collectively deactivated.

[0197] Implementation method 3 does not require any changes to the format of the current activation DCI, nor does it require the design of a different first RNTI for each CDM group. Instead, different CDM groups are distinguished by allocating different PDCCH search space sets to different CDM groups with the same first RNTI. Specifically, when the network device configures OCC-related parameters for the terminal device through configuration information, the mapping relationship between the CDM group and the PDCCH search space set can be configured. The mapping relationship can ensure that different CDM groups with the same first RNTI will be configured with different PDCCH search space sets.

[0198] Implementation 4: Implicitly indicating the need to activate and / or deactivate based on the PDCCH search space set and the first RNTI CDM Group

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

[0200] In implementation manner 4, different CDM groups may correspond to different PDCCH search space sets. In this way, different CDM groups will search and descramble the first signaling in different PDCCH search space sets.

[0201] Implementation method 4 can be understood as an extension of implementation method 3, and the difference between it and implementation method 3 is that the number of configured first RNTIs may be greater. That is to say, a first RNTI in implementation method 3 can correspond to a large group, and the large group can correspond to multiple first RNTIs in implementation method 4, that is, each large group can contain multiple small groups, and the CDM groups in each small group correspond to the PDCCH search space set. For example, assuming that the number of PDCCH search space sets supported by a first RNTI is M, then in implementation method 3, at most M CDM groups can be supported; but in implementation method 4, since the number of configured first RNTIs is multiple, such as configuring N (N is a positive integer greater than 1) first RNTIs, implementation method 4 can support at most M*N CDM groups.

[0202] The above-mentioned implementation methods 1 to 4 can all realize collective activation and / or deactivation of the CDM group, 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 separate activation and / or deactivation signaling.

[0203] The indication methods used in the above implementation modes 1 to 4 and the changes to the protocol can be found in Table 4.

[0204] Table 4

[0205]

[0206] Embodiment 2: First signaling implements scheduling of CDM group

[0207] Embodiment 2 can be applied to the scenario of dynamic scheduling. In the scenario of dynamic scheduling, each first PUSCH transmission of the terminal device needs to be scheduled by the network device through the first signaling. That is, in embodiment 2, the network device can schedule all terminal devices in the CDM group to perform the first PUSCH transmission based on the first signaling.

[0208] Embodiment 2 can implement the scheduling of PUSCH transmission of the CDM group, thereby alleviating the problem of limited downlink resources. In addition, the implementation method of embodiment 2 can be better compatible with the current PUSCH scheduling signaling (DCI) field format.

[0209] As an implementation method, Example 2 may explicitly indicate the CDM group that needs to be scheduled. As another implementation method, Example 2 may implicitly indicate the CDM group that needs to be scheduled. The embodiment of the present application does not limit the manner in which Example 2 implicitly indicates the CDM group that needs to be scheduled. For example, the network device may implicitly indicate the CDM group that needs to be scheduled through one or more of the following: the first RNTI, the PDCCH search space set, and the HPN.

[0210] The implementation methods of Example 2 are introduced below.

[0211] Implementation method 1: The first signaling explicitly indicates the CDM group to be scheduled

[0212] In implementation mode 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 the 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.

[0213] In implementation mode 1, the value range of the CDM group identifier may 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, the value range of the CDM group identifier may be 0-15, that is, one first RNTI may support up to 16 CDM groups.

[0214] In implementation method 1, the first RNTI corresponding to the terminal devices in the same CDM group is the same, and the first RNTIs corresponding to different CDM groups may be the same or different. In other words, the maximum number of CDM groups that a first RNTI can accommodate is related to the number of data bits of the CDM group identifier in the first signaling. Taking the number of data bits of the CDM group identifier in the first signaling as 4 as an example, this means that a first RNTI can be used for scheduling 16 CDM groups. Taking the number of data bits of the CDM group identifier in the first signaling as 5 as an example, this means that a first RNTI can be used for scheduling 32 CDM groups.

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

[0216] In some embodiments, the first CDM group is a CDM group that needs to be scheduled. In some embodiments, the first CDM group may be any one or more CDM groups, which is not limited in the embodiments of the present application.

[0217] 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 by the network device for the terminal 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 it is necessary to perform the first PUSCH transmission based on the first signaling according to the comparison.

[0218] The identifier of the CDM group configured with the network device as the terminal device is idxCDM UE , the identifier of the first CDM group is idxCDM A For example, after the terminal device successfully descrambles the first signaling, it needs to carry the idxCDM A idxCDM pre-configured with network equipment UE For comparison. If idxCDM UE =idxCDM A , the terminal device performs the first PUSCH transmission based on the first signaling.

[0219] 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 scheduling based on the first PUSCH transmission of the CDM group without the need for the network device to send scheduling indication signaling to each terminal device separately.

[0220] Implementation 2: Implicitly indicating the CDM group to be scheduled based on the first RNTI

[0221] 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.

[0222] 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, the first RNTI corresponding to each CDM group is different). In this way, different first RNTIs can represent different CDM groups, so that the terminal device can determine the CDM group scheduled by the first signaling according to the first RNTI.

[0223] In implementation method 2, the first RNTI corresponding to each terminal device in the same CDM group is the same.

[0224] Afterwards, the network device may send a first signaling to the terminal device to schedule one or more CDM groups to perform a first PUSCH transmission. In implementation mode 2, the format of the first signaling does not need to be changed compared to the current scheduling signaling, and backward compatibility can be better achieved.

[0225] As an implementation method, if the terminal device successfully descrambles the first signaling, the terminal device performs the first PUSCH transmission based on the first signaling. For example, if the terminal device successfully descrambles the first signaling, the terminal device performs the first PUSCH transmission based on the first signaling. In this case, each terminal device participating in OCC multiplexing in the same CDM group will collectively perform the first PUSCH transmission based on the first signaling.

[0226] Implementation method 2 does not need to change the format of the current scheduling DCI, but directly allows different first RNTIs to represent different CDM groups, that is, different CDM groups correspond to different first RNTIs, thereby avoiding the process of the terminal device determining the identifier of the CDM group. In addition, implementation method 2 can solve the problem that multiple CDM groups corresponding to the same first RNTI cannot be scheduled at the same time, because the first RNTI can be directly used to distinguish different CDM groups.

[0227] Implementation method 3: Implicitly indicating the CDM group to be scheduled based on the PDCCH search space set

[0228] In implementation mode 3, when the network device sends configuration information to the terminal device, the configuration information may include OCC related parameters, CDM group identifiers, and a mapping relationship between CDM groups and PDCCH search space sets. Of course, in addition to the above information, the configuration information may also include other information, such as the first RNTI.

[0229] In implementation manner 3, different CDM groups may correspond to different PDCCH search space sets. In this way, different CDM groups will search and descramble the first signaling in different PDCCH search space sets.

[0230] In implementation mode 3, the identifier of the CDM group may be determined by the number of CDM groups and the PDCCH search space set. For example, terminal devices with different CDM group identifiers may be distributed in different CDM groups and correspond to different PDCCH search space sets.

[0231] In implementation mode 3, the first RNTIs corresponding to the terminal devices in the same CDM group are the same. The maximum number of CDM groups that can be accommodated by a first RNTI is the total number of CDM group identifiers (eg, 16).

[0232] Afterwards, the network device may send a first signaling to the terminal device to schedule one or more CDM groups to perform a first PUSCH transmission. In implementation manner 3, the format of the first signaling does not need to be changed compared to the current scheduling signaling, and backward compatibility can be better achieved.

[0233] As an implementation method, 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. For example, if the terminal device searches for 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, the terminal device performs the first PUSCH transmission based on the first signaling. In this case, each terminal device participating in OCC multiplexing in the same CDM group will collectively perform the first PUSCH transmission based on the first signaling.

[0234] Implementation method 3 does not require any changes to the format of the current scheduling DCI, nor does it require the design of a different first RNTI for each CDM group. Instead, different CDM groups are distinguished by allocating different PDCCH search space sets to different CDM groups with the same first RNTI. Specifically, when the network device configures OCC-related parameters for the terminal device through configuration information, the mapping relationship between the CDM group and the PDCCH search space set can be configured. This mapping relationship can ensure that different CDM groups with the same first RNTI will be configured with different PDCCH search space sets. In addition, implementation method 3 can solve the problem that multiple CDM groups corresponding to the same first RNTI cannot be scheduled at the same time, because multiple CDM groups with the same first RNTI will be configured with different PDCCH search space sets, thereby achieving the distinction between different CDM groups.

[0235] Implementation 4: Implicitly indicating the CDM group to be scheduled based on the PDCCH search space set and the first RNTI

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

[0237] In implementation manner 4, different CDM groups may correspond to different PDCCH search space sets. In this way, different CDM groups will search and descramble the first signaling in different PDCCH search space sets.

[0238] Implementation method 4 can be understood as an extension of implementation method 3, and the difference between it and implementation method 3 is that the number of configured first RNTIs may be greater. That is to say, a first RNTI in implementation method 3 can correspond to a large group, and the large group can correspond to multiple first RNTIs in implementation method 4, that is, each large group can contain multiple small groups, and the CDM groups in each small group correspond to the PDCCH search space set. For example, assuming that the number of PDCCH search space sets supported by a first RNTI is M, then in implementation method 3, at most M CDM groups can be supported; but in implementation method 4, since the number of configured first RNTIs is multiple, such as configuring N (N is a positive integer greater than 1) first RNTIs, implementation method 4 can support at most M*N CDM groups.

[0239] Implementation 5: Implicitly indicating the CDM group to be scheduled based on HPN

[0240] In implementation mode 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 the 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.

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

[0242] In implementation mode 5, there is a mapping relationship between the identifier of the CDM group to which the terminal device belongs and the synchronous HPN of the terminal device. For example, the identifier of the CDM group to which the terminal device belongs may be the same as the synchronous HPN of the terminal device. In other words, when the network device configures the identifier of the CDM group to which the terminal device belongs to the terminal device, it may configure the identifier of the CDM group to which the terminal device belongs to the terminal device according to the mapping relationship between the identifier of the CDM group to which the terminal device belongs and the synchronous HPN of the terminal device.

[0243] Afterwards, 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 symbols of each terminal device are consistent, so the synchronous HPN of the terminal device (which can be understood as a virtual synchronous HPN) can be calculated based on the PUSCH time domain start symbol. Then, the terminal device can compare the calculated HPN with the identifier of the CDM group to which the terminal device belongs indicated in the configuration information. If the two satisfy a certain mapping relationship (for example, the two are the same), then each terminal device participating in OCC multiplexing in the same CDM group will collectively perform the first PUSCH transmission based on the first signaling.

[0244] In some embodiments, the first signaling sent by the network device to the terminal device is encrypted by the first RNTI.

[0245] In some embodiments, the first signaling includes information indicating the location of the PUSCH scheduling time domain resource. Since the transmission resources used by the terminal devices performing OCC multiplexing are consistent, the time domain start symbol of the PUSCH scheduled by each terminal device is also consistent, and the synchronous HPN of the terminal device can be calculated based on the time domain start symbol.

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

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

[0248] Implementation method 5 does not need to change the format of the current scheduling DCI, and distinguishes different CDM groups through HPN, thereby alleviating downlink resource limitations.

[0249] The above-mentioned implementation methods 1 to 5 can all realize collective scheduling of the CDM group, 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 the terminal devices scheduled individually.

[0250] The indication methods used in the above implementation modes 1 to 5 and the changes to the protocol can be found in Table 5.

[0251] Table 5

[0252]

[0253] For ease of understanding, the following Figures 9 to 12 The communication processes in different scheduling scenarios are introduced respectively.

[0254] Fig. 9 and Fig.10 The following is a schematic diagram of the communication process in the scenario of type 1 configuration scheduling. Fig. 9 and Fig.10As shown, the network device can send configuration information to different terminal devices in the CDM group respectively, and the configuration information carries OCC related parameters, and the configuration information is used to schedule the terminal device to perform the first PUSCH transmission. Afterwards, the terminal device performs the first PUSCH transmission based on the configuration information without any low-layer trigger (first signaling trigger).

[0255] In some embodiments, the network device may send configuration information to different terminal devices at different times, that is, the time when PUSCH starts scheduling can be allocated at will. Fig. 9 In the example of , the network device may send configuration information to terminal device 1 and terminal device 2 at different times. Fig.10 In the example, the time when the network device sends configuration information to terminal device 1, terminal device 2, terminal device 3 and terminal device 4 can be different. Taking the cross-time slot OCC scheme as an example, when the number of terminal devices multiplexed by OCC is 4, the time domain occupied resources of each PUSCH will include 4 data repetition time slots, and the 4 elements in the configured OCC codewords are used to spread the repeated data in the 4 time slots. Since the repeated data in each PUSCH has orthogonal completeness 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.

[0256] In some embodiments, the transmission resources configured by the network device to different terminal devices should be consistent, 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.

[0257] Fig.11 This is a schematic diagram of the communication process in the scenario of type 2 configuration scheduling. Fig.11 As shown, the network device can send configuration information to different terminal devices in the CDM group respectively, and the configuration information carries OCC-related parameters, and the configuration information is used to schedule the terminal device to perform the first PUSCH transmission. Afterwards, the network device can send a first signaling to the terminal devices in the CDM group at the granularity of the CDM group to activate the configuration parameters for the first PUSCH transmission. When the terminal device receives the first signaling, the terminal device can perform the first PUSCH transmission based on the configuration information.

[0258] 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 to the terminal device based on the granularity of the CDM group.

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

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

[0261] The above introduces four implementation methods for realizing CDM group activation and / or deactivation in the scenario of type 2 configuration scheduling. The following is an exemplary introduction to the communication processes corresponding to these four implementation methods.

[0262] Example 1: First signaling explicit indication

[0263] Assume that the network device uses semi-static scheduling to perform PUSCH scheduling on OCC multiplexed terminal devices, and configures the scheduling type to type 2, where the number of OCC multiplexed terminal devices is 4 (i.e., the number of terminal devices included in the CDM group is 4), namely terminal device 1 to terminal device 4.

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

[0265] Exemplarily, OCC-related parameters may include an OCC scheme across time slots, an OCC length of 4, the codeword table shown in Table 2, and the codeword index of the terminal device (such as the codeword index of terminal device 1 is 2, the codeword index of terminal device 2 is 3, the codeword index of terminal device 3 is 4, and the codeword index of terminal device 4 is 5).

[0266] Exemplarily, the number of data bits of the CDM group identifier in the first signaling is 4, and 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, both are dixCDM UE =6.

[0267] Exemplarily, since terminal devices 1 to 4 are in the same CDM group, the first RNTIs of terminal devices 1 to 4 are the same. In Example 1, the first RNTIs corresponding to different CDM groups may be the same or different.

[0268] Afterwards, the network device uses the first signaling to collectively activate the terminal devices 1 to 4 (ie, collective OCC activation). The activation method may refer to implementation method 1 of embodiment 1.

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

[0270] When the OCC multiplexing is finished, the network device may use the first signaling to collectively deactivate the terminal devices 1 to 4 (ie, collective OCC deactivation). The deactivation method may refer to implementation method 1 of embodiment 1.

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

[0272] Assume that the network device uses semi-static scheduling to perform PUSCH scheduling on OCC multiplexed terminal devices, and configures the scheduling type to type 2, where the number of OCC multiplexed terminal devices is 4 (i.e., the number of terminal devices included in the CDM group is 4), namely terminal device 1 to terminal device 4.

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

[0274] Exemplarily, OCC-related parameters may include an OCC scheme across time slots, an OCC length of 4, the codeword table shown in Table 2, and the codeword index of the terminal device (such as the codeword index of terminal device 1 is 2, the codeword index of terminal device 2 is 3, the codeword index of terminal device 3 is 4, and the codeword index of terminal device 4 is 5).

[0275] Exemplarily, since terminal devices 1 to 4 are in the same CDM group, the first RNTIs of terminal devices 1 to 4 are the same. In Example 2, different CDM groups correspond to different first RNTIs, or in other words, one CDM group corresponds to one first RNTI.

[0276] Afterwards, the network device uses the first signaling to collectively activate the terminal devices 1 to 4 (ie, collective OCC activation). The activation method may refer to implementation method 2 of embodiment 1.

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

[0278] When OCC multiplexing is completed, the network device may use the first signaling to collectively deactivate terminal devices 1 to 4 (ie, collective OCC deactivation). The deactivation method may refer to implementation method 2 of embodiment 1.

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

[0280] Assume that the network device uses semi-static scheduling to perform PUSCH scheduling on OCC multiplexed terminal devices, and configures the scheduling type to type 2, where the number of OCC multiplexed terminal devices is 4 (i.e., the number of terminal devices included in the CDM group is 4), namely terminal device 1 to terminal device 4.

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

[0282] Exemplarily, OCC-related parameters may include an OCC scheme across time slots, an OCC length of 4, the codeword table shown in Table 2, and the codeword index of the terminal device (such as the codeword index of terminal device 1 is 2, the codeword index of terminal device 2 is 3, the codeword index of terminal device 3 is 4, and the codeword index of terminal device 4 is 5).

[0283] Exemplarily, the terminal devices in the same CDM group have the same CDM group identifier. For example, the CDM group identifiers of terminal devices 1 to 4 are the same, such as 8.

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

[0285] Exemplarily, since terminal devices 1 to 4 are in the same CDM group, the first RNTIs of terminal devices 1 to 4 are the same. In Example 3, the first RNTIs corresponding to different CDM groups may be the same or different.

[0286] Afterwards, the network device uses the first signaling to collectively activate (ie, collective OCC activation) the terminal devices 1 to 4. The activation method may refer to implementation method 3 or implementation method 4 of embodiment 1.

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

[0288] When OCC multiplexing is completed, the network device may use the first signaling to collectively deactivate terminal devices 1 to 4 (ie, collective OCC deactivation). The deactivation method may refer to implementation method 3 or implementation method 4 of embodiment 1.

[0289] Fig.12Figure 1 is a schematic diagram of the communication process in a dynamic scheduling scenario. Fig.12 As shown, the network device can send configuration information to different terminal devices in the CDM group respectively, and the configuration information carries OCC related parameters, and the configuration information is used to schedule the terminal device to perform the first PUSCH transmission. Afterwards, the network device can send the first signaling to the terminal devices in the CDM group with the CDM group as the granularity to schedule the CDM group to collectively perform the first PUSCH transmission.

[0290] 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 to the terminal device based on the granularity of the CDM group.

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

[0292] The difference from type 2 configuration scheduling is that in the type 2 configuration scheduling process, 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 higher flexibility than type 2 configuration scheduling.

[0293] The above introduces five implementation methods for activating and / or deactivating a CDM group in a dynamic scheduling scenario. The following is an exemplary introduction to the communication processes corresponding to these five implementation methods.

[0294] Example 1: First signaling explicit indication

[0295] Assume that the network device uses dynamic scheduling to perform PUSCH scheduling on the OCC multiplexed terminal devices. In this case, there is no need for collective activation and deactivation of the OCC as in semi-static scheduling. Instead, it is necessary to schedule the first PUSCH transmission based on the first signaling, where the number of terminal devices multiplexed by OCC is 4 (i.e., the number of terminal devices included in the CDM group is 4), namely terminal device 1 to terminal device 4.

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

[0297] Exemplarily, OCC-related parameters may include an OCC scheme across time slots, an OCC length of 4, the codeword table shown in Table 2, and the codeword index of the terminal device (such as the codeword index of terminal device 1 is 2, the codeword index of terminal device 2 is 3, the codeword index of terminal device 3 is 4, and the codeword index of terminal device 4 is 5).

[0298] Exemplarily, the number of data bits of the CDM group identifier in the first signaling is 4, and 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, both are dixCDM UE =2.

[0299] Exemplarily, since terminal devices 1 to 4 are in the same CDM group, the first RNTIs of terminal devices 1 to 4 are the same. In Example 1, the first RNTIs corresponding to different CDM groups may be the same or different.

[0300] Afterwards, the network device uses the first signaling to collectively schedule the terminal devices 1 to 4 (ie, PUSCH group scheduling). The scheduling method can refer to implementation method 1 of embodiment 2.

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

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

[0303] Assume that the network device uses dynamic scheduling to perform PUSCH scheduling on the OCC multiplexed terminal devices. In this case, there is no need for collective activation and deactivation of the OCC as in semi-static scheduling. Instead, it is necessary to schedule the first PUSCH transmission based on the first signaling, where the number of terminal devices multiplexed by OCC is 4 (i.e., the number of terminal devices included in the CDM group is 4), namely terminal device 1 to terminal device 4.

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

[0305] Exemplarily, OCC-related parameters may include an OCC scheme across time slots, an OCC length of 4, the codeword table shown in Table 2, and the codeword index of the terminal device (such as the codeword index of terminal device 1 is 2, the codeword index of terminal device 2 is 3, the codeword index of terminal device 3 is 4, and the codeword index of terminal device 4 is 5).

[0306] Exemplarily, since terminal devices 1 to 4 are in the same CDM group, the first RNTIs of terminal devices 1 to 4 are the same. In Example 2, different CDM groups correspond to different first RNTIs, or in other words, one CDM group corresponds to one first RNTI.

[0307] Afterwards, the network device uses the first signaling to collectively schedule the terminal devices 1 to 4 (ie, PUSCH group scheduling). For the scheduling method, see implementation method 2 of embodiment 2.

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

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

[0310] Assume that the network device uses dynamic scheduling to perform PUSCH scheduling on the OCC multiplexed terminal devices. In this case, there is no need for collective activation and deactivation of the OCC as in semi-static scheduling. Instead, it is necessary to schedule the first PUSCH transmission based on the first signaling, where the number of terminal devices multiplexed by OCC is 4 (i.e., the number of terminal devices included in the CDM group is 4), namely terminal device 1 to terminal device 4.

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

[0312] Exemplarily, OCC-related parameters may include an OCC scheme across time slots, an OCC length of 4, the codeword table shown in Table 2, and the codeword index of the terminal device (such as the codeword index of terminal device 1 is 2, the codeword index of terminal device 2 is 3, the codeword index of terminal device 3 is 4, and the codeword index of terminal device 4 is 5).

[0313] Exemplarily, the identifier of the CDM group is determined by the number of CDM groups and the PDCCH search space set, and 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.

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

[0315] Exemplarily, since terminal devices 1 to 4 are in the same CDM group, the first RNTIs of terminal devices 1 to 4 are the same. In Example 3, the first RNTIs corresponding to different CDM groups may be the same or different.

[0316] Afterwards, the network device uses the first signaling to collectively schedule the terminal devices 1 to 4 (ie, PUSCH group scheduling). For the scheduling method, see implementation method 3 or implementation method 4 of embodiment 2.

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

[0318] Example 4: Based on HPN indication

[0319] Assume that the network device uses dynamic scheduling to perform PUSCH scheduling on the OCC multiplexed terminal devices. In this case, there is no need for collective activation and deactivation of the OCC as in semi-static scheduling. Instead, it is necessary to schedule the first PUSCH transmission based on the first signaling, where the number of terminal devices multiplexed by OCC is 4 (i.e., the number of terminal devices included in the CDM group is 4), namely terminal device 1 to terminal device 4.

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

[0321] Exemplarily, OCC-related parameters may include an OCC scheme across time slots, an OCC length of 4, the codeword table shown in Table 2, and the codeword index of the terminal device (such as the codeword index of terminal device 1 is 2, the codeword index of terminal device 2 is 3, the codeword index of terminal device 3 is 4, and the codeword index of terminal device 4 is 5).

[0322] Exemplarily, the number of data bits of the CDM group identifier in the first signaling is 4, and 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, both are dixCDM UE =2.

[0323] Exemplarily, since terminal devices 1 to 4 are in the same CDM group, the first RNTIs of terminal devices 1 to 4 are the same. In Example 5, the first RNTIs corresponding to different CDM groups may be the same or different.

[0324] Afterwards, the network device uses the first signaling to collectively schedule the terminal devices 1 to 4 (ie, PUSCH group scheduling). For the scheduling method, see implementation method 5 of embodiment 2.

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

[0326] Combination of the above Figures 1 to 12 , describes the method embodiment of the present application in detail, and the following is combined with Figures 13 to 15 , describes the device embodiment of the present application in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the parts not described in detail can refer to the previous method embodiment.

[0327] Fig.13 It is a schematic diagram of the structure of the terminal device provided in an embodiment of the present application. Fig.13 The terminal device 1300 shown may include a first receiving module 1310. The first receiving module 1310 may be used to receive configuration information sent by a network device, the configuration information being used to configure 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.

[0328] In some embodiments, the configuration information also includes one or more of the following information: an identifier of the CDM group to which the terminal device belongs; a first RNTI, the first RNTI being used to scramble and / or descramble the PDCCH that schedules the first PUSCH transmission; and a mapping relationship between the CDM group and the PDCCH search space set.

[0329] In some embodiments, the first RNTI is configured according to the granularity of a CDM group.

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

[0331] In some embodiments, the first signaling includes an identifier of a first CDM group, and the terminal device further includes a first execution module, which is used to: 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, execute the first PUSCH transmission based on the first signaling.

[0332] 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.

[0333] In some embodiments, the terminal device also includes a second execution module, which is used to: if the terminal device successfully descrambles the first signaling, activate or deactivate the configuration information for executing the first PUSCH transmission, or if the terminal device successfully descrambles the first signaling, 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.

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

[0335] In some embodiments, the terminal device also includes a third execution module, which is used to: 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 executes 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.

[0336] In some embodiments, the activation and / or deactivation of the configuration information of the first PUSCH transmission is determined based on the PDCCH search space set, or is jointly determined 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 is jointly determined based on the PDCCH search space set and the first RNTI.

[0337] In some embodiments, the terminal device also includes: a determination module, used to determine the HARQ process number corresponding to the first PUSCH transmission; and a fourth execution module, used 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.

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

[0339] In some embodiments, the OCC scheme includes one or more of the following: an OCC scheme across symbols, an OCC scheme across time slots, and an OCC scheme within a symbol.

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

[0341] In some embodiments, the first receiving module 1310 may be a transceiver 1530. The terminal device 1300 may further include a processor 1510 and a memory 1520. Fig.15 shown.

[0342] Fig.14 It is a structural diagram of the network device provided in an embodiment of the present application. Fig.14 The network device 1400 shown may include a first sending module 1410. The first sending module 1410 may be used to send configuration information to a terminal device, the configuration information being used to configure 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.

[0343] In some embodiments, the configuration information also includes one or more of the following information: an identifier of the CDM group to which the terminal device belongs; a first RNTI, the first RNTI being used to scramble and / or descramble the PDCCH that schedules the first PUSCH transmission; and a mapping relationship between the CDM group and the PDCCH search space set.

[0344] In some embodiments, the first RNTI is configured according to the granularity of a CDM group.

[0345] In some embodiments, the network device also includes: a second sending module 1320, used to send a first signaling to the terminal device, and the first signaling is used for one or more of the following: activating one or more CDM groups to execute the configuration information of the first PUSCH transmission; deactivating one or more CDM groups to execute the configuration information of the first PUSCH transmission; scheduling one or more CDM groups to execute the first PUSCH transmission.

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

[0347] 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.

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

[0349] In some embodiments, the activation and / or deactivation of the configuration information of the first PUSCH transmission is determined based on the PDCCH search space set, or is jointly determined 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 is jointly determined based on the PDCCH search space set and the first RNTI.

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

[0351] In some embodiments, the OCC scheme includes one or more of the following: an OCC scheme across symbols, an OCC scheme across time slots, and an OCC scheme within a symbol.

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

[0353] In some embodiments, the first sending module 1410 may be a transceiver 1530. The network device 1400 may further include a processor 1510 and a memory 1520. Fig.15 shown.

[0354] Fig.15 It is a schematic structural diagram of a communication device according to an embodiment of the present application. Fig.15 The dotted line in the figure indicates that the unit or module is optional. The device 1500 can be used to implement the method described in the above method embodiment. The device 1500 can be a chip, a terminal device or a network device.

[0355] The device 1500 may include one or more processors 1510. The processor 1510 may support the device 1500 to implement the method described in the method embodiment above. 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 also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0356] The apparatus 1500 may further include one or more memories 1520. The memory 1520 stores a program, which can be executed by the processor 1510, so that the processor 1510 executes the method described in the above method embodiment. The memory 1520 may be independent of the processor 1510 or integrated in the processor 1510.

[0357] The apparatus 1500 may further include a transceiver 1530. The processor 1510 may communicate with other devices or chips through the transceiver 1530. For example, the processor 1510 may transmit and receive data with other devices or chips through the transceiver 1530.

[0358] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal device or a network device provided in the present application, and the program enables a computer to execute the method performed by the terminal device or the network device in each embodiment of the present application.

[0359] The embodiment of the present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal device or network device provided in the embodiment of the present application, and the program enables the computer to execute the method performed by the terminal device or network device in each embodiment of the present application.

[0360] The embodiment of the present application also provides a computer program. The computer program can be applied to the terminal device or network device provided in the embodiment of the present application, and the computer program enables a computer to execute the method executed by the terminal device or network device in each embodiment of the present application.

[0361] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third" and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions.

[0362] In the embodiments of the present application, the "indication" mentioned can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0363] In the embodiment of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

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

[0365] In the embodiments of the present application, the term "include" may refer to direct inclusion or indirect inclusion. Optionally, the term "include" in the embodiments of the present application may be replaced with "indicates" or "is used to determine". For example, "A includes B" may be replaced with "A indicates B" or "A is used to determine B".

[0366] In the embodiments of the present application, "pre-definition" or "pre-configuration" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.

[0367] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0368] In the embodiments of the present application, the term "and / or" is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0369] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean 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 the present application.

[0370] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0372] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0373] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part 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, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0374] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A wireless communication method, characterized in that: include: The terminal device receives configuration information sent by the network device, where the configuration information is used to configure scheduling parameters of a first physical uplink shared channel PUSCH transmission, wherein the first PUSCH transmission is a PUSCH transmission based on an orthogonal cover code OCC, and the configuration information includes OCC-related parameters.

2. The method according to claim 1, characterized in that The configuration information also includes one or more of the following information: An identifier of the code division multiplexing CDM group to which the terminal device belongs; a first radio network temporary identifier RNTI, where the first RNTI is used to scramble and / or descramble a physical downlink control channel PDCCH that schedules the first PUSCH transmission; The mapping relationship between CDM groups and PDCCH search space sets.

3. The method according to claim 2, characterized in that The first RNTI is configured according to the granularity of the CDM group.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The terminal device receives a first signaling sent by the network device, where the first signaling is used for one or more of the following: Activate configuration information of 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; One or more CDM groups are scheduled to perform the first PUSCH transmission.

5. The method according to claim 4, characterized in that The first signaling includes an identifier of 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 configuration information for performing 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.

6. 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.

7. The method according to claim 6, characterized in that The method further comprises: If the terminal device successfully descrambles the first signaling, the terminal device activates or deactivates configuration information for performing 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.

8. The method according to claim 4, characterized in that The configuration information includes a mapping relationship between a CDM group and a PDCCH search space set, and different CDM groups correspond to different PDCCH search space sets.

9. The method according to claim 8, characterized in that The method further comprises: 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 performing 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.

10. The method according to claim 8 or 9, characterized in that: The activation and / or deactivation of the configuration information for the first PUSCH transmission is determined based on the PDCCH search space set, or is jointly determined 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 is determined jointly based on the PDCCH search space set and the first RNTI.

11. The method according to claim 4, characterized in that The method further comprises: 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 performs the first PUSCH transmission based on the first signaling.

12. The method according to any one of claims 1 to 11, characterized in that The OCC related parameters include one or more of the following: OCC scheme, OCC length, OCC codeword table, OCC codeword index.

13. The method according to claim 12, characterized in that The OCC scheme includes one or more of the following: an OCC scheme across symbols, an OCC scheme across time slots, and an OCC scheme within a symbol.

14. The method according to any one of claims 1 to 13, characterized in that The configuration information is carried in radio resource control RRC signaling.

15. A wireless communication method, characterized in that: include: The network device sends configuration information to the terminal device, where the configuration information is used to configure scheduling parameters of a first physical uplink shared channel PUSCH transmission, wherein the first PUSCH transmission is a PUSCH transmission based on an orthogonal cover code OCC, and the configuration information includes OCC-related parameters.

16. The method according to claim 15, characterized in that The configuration information also includes one or more of the following information: An identifier of the code division multiplexing CDM group to which the terminal device belongs; a first radio network temporary identifier RNTI, where the first RNTI is used to scramble and / or descramble a physical downlink control channel PDCCH that schedules the first PUSCH transmission; The mapping relationship between CDM groups and PDCCH search space sets.

17. The method according to claim 16, characterized in that The first RNTI is configured according to the granularity of the CDM group.

18. The method according to any one of claims 15 to 17, characterized in that: The method further comprises: The network device sends a first signaling to the terminal device, where the first signaling is used for one or more of the following: Activate configuration information of 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; One or more CDM groups are scheduled to perform the first PUSCH transmission.

19. The method according to claim 18, characterized in that The first signaling includes an identifier of a first CDM group.

20. 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.

21. The method according to claim 18, characterized in that The configuration information includes a mapping relationship between a CDM group and a PDCCH search space set, and different CDM groups correspond to different PDCCH search space sets.

22. The method according to claim 21, characterized in that: The activation and / or deactivation of the configuration information for the first PUSCH transmission is determined based on the PDCCH search space set, or is jointly determined 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 is determined jointly based on the PDCCH search space set and the first RNTI.

23. The method according to any one of claims 15 to 22, characterized in that The OCC related parameters include one or more of the following: OCC scheme, OCC length, OCC codeword table, OCC codeword index.

24. The method according to claim 23, characterized in that The OCC scheme includes one or more of the following: an OCC scheme across symbols, an OCC scheme across time slots, and an OCC scheme within a symbol.

25. The method according to any one of claims 15 to 24, characterized in that The configuration information is carried in radio resource control RRC signaling.

26. A terminal device, characterized in that: include: The first receiving module is used to receive configuration information sent by a network device, where the configuration information is used to configure scheduling parameters of a first physical uplink shared channel PUSCH transmission, wherein the first PUSCH transmission is a PUSCH transmission based on an orthogonal cover code OCC, and the configuration information includes OCC related parameters.

27. The terminal device according to claim 26, characterized in that: The configuration information also includes one or more of the following information: An identifier of the code division multiplexing CDM group to which the terminal device belongs; a first radio network temporary identifier RNTI, where the first RNTI is used to scramble and / or descramble a physical downlink control channel PDCCH that schedules the first PUSCH transmission; The mapping relationship between CDM groups and PDCCH search space sets.

28. The terminal device according to claim 27, characterized in that: The first RNTI is configured according to the granularity of the CDM group.

29. The terminal device according to any one of claims 26 to 28, characterized in that: The terminal device further includes: The second receiving module is configured to receive a first signaling sent by the network device, where the first signaling is used for one or more of the following: Activate configuration information of 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; One or more CDM groups are scheduled to perform the first PUSCH transmission.

30. The terminal device according to claim 29, characterized in that: The first signaling includes an identifier of a first CDM group, and the terminal device further includes a first execution module, which is used to: If the identifier of the first CDM group includes the identifier of the CDM group to which the terminal device belongs, activating or deactivating configuration information for performing 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.

31. The terminal device according to claim 29, 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.

32. The terminal device according to claim 31, characterized in that: The terminal device further includes a second execution module, configured to: If the terminal device successfully descrambles the first signaling, activate or deactivate configuration information for performing the first PUSCH transmission, or, If the terminal device successfully descrambles the first signaling, performing 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.

33. The terminal device according to claim 29, characterized in that: The configuration information includes a mapping relationship between a CDM group and a PDCCH search space set, and different CDM groups correspond to different PDCCH search space sets.

34. The terminal device according to claim 33, characterized in that: The terminal device further includes a third execution module, configured to: 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 performing 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.

35. The terminal device according to claim 33 or 34, characterized in that: The activation and / or deactivation of the configuration information for the first PUSCH transmission is determined based on the PDCCH search space set, or is jointly determined 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 is determined jointly based on the PDCCH search space set and the first RNTI.

36. The terminal device according to claim 29, characterized in that: The terminal device further includes: A determination module, configured to determine a HARQ process number corresponding to the first PUSCH transmission; A fourth execution module is used 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.

37. The terminal device according to any one of claims 26 to 36, characterized in that: The OCC related parameters include one or more of the following: OCC scheme, OCC length, OCC codeword table, OCC codeword index.

38. The terminal device according to claim 37, characterized in that: The OCC scheme includes one or more of the following: an OCC scheme across symbols, an OCC scheme across time slots, and an OCC scheme within a symbol.

39. The terminal device according to any one of claims 26 to 38, characterized in that: The configuration information is carried in radio resource control RRC signaling.

40. A network device, characterized in that: include: The first sending module is used to send configuration information to the terminal device, where the configuration information is used to configure scheduling parameters of the first physical uplink shared channel PUSCH transmission, wherein the first PUSCH transmission is a PUSCH transmission based on an orthogonal cover code OCC, and the configuration information includes OCC related parameters.

41. The network device according to claim 40, characterized in that The configuration information also includes one or more of the following information: An identifier of the code division multiplexing CDM group to which the terminal device belongs; a first radio network temporary identifier RNTI, where the first RNTI is used to scramble and / or descramble a physical downlink control channel PDCCH that schedules the first PUSCH transmission; The mapping relationship between CDM groups and PDCCH search space sets.

42. The network device according to claim 41, characterized in that The first RNTI is configured according to the granularity of the CDM group.

43. The network device according to any one of claims 40 to 42, characterized in that: The network device also includes: The second sending module is configured to send a first signaling to the terminal device, where the first signaling is used for one or more of the following: Activate configuration information of 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; One or more CDM groups are scheduled to perform the first PUSCH transmission.

44. The network device according to claim 43, characterized in that The first signaling includes an identifier of a first CDM group.

45. The network device according to claim 43, 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.

46. ​​The network device according to claim 43, characterized in that The configuration information includes a mapping relationship between a CDM group and a PDCCH search space set, and different CDM groups correspond to different PDCCH search space sets.

47. The network device according to claim 46, characterized in that: The activation and / or deactivation of the configuration information for the first PUSCH transmission is determined based on the PDCCH search space set, or is jointly determined 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 is determined jointly based on the PDCCH search space set and the first RNTI.

48. The network device according to any one of claims 40 to 47, characterized in that: The OCC related parameters include one or more of the following: OCC scheme, OCC length, OCC codeword table, OCC codeword index.

49. The network device according to claim 48, characterized in that The OCC scheme includes one or more of the following: an OCC scheme across symbols, an OCC scheme across time slots, and an OCC scheme within a symbol.

50. The network device according to any one of claims 40 to 49, characterized in that: The configuration information is carried in radio resource control RRC signaling.

51. A terminal device, characterized in that: It comprises a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the terminal device executes the method as described in any one of claims 1 to 14.

52. A network device, characterized in that: It comprises a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the network device executes the method as described in any one of claims 15-25.

53. A device, characterized in that It comprises a processor, which is used to call a program from a memory so that the device executes the method as described in any one of claims 1-14 or 15-25.

54. A chip, characterized in that: It comprises a processor, which is used to call a program from a memory, so that a device equipped with the chip executes the method as described in any one of claims 1-14 or 15-25.

55. A computer-readable storage medium, characterized in that: A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1-14 or 15-25.

56. A computer program product, characterized in that The method comprises a program which causes a computer to execute the method as claimed in any one of claims 1 to 14 or 15 to 25.

57. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1-14 or 15-25.

Images