[go: up one dir, main page]

WO2022017354A1 - Pdcch的校验方法、发送方法、终端及网络侧设备 - Google Patents

Pdcch的校验方法、发送方法、终端及网络侧设备 Download PDF

Info

Publication number
WO2022017354A1
WO2022017354A1 PCT/CN2021/107269 CN2021107269W WO2022017354A1 WO 2022017354 A1 WO2022017354 A1 WO 2022017354A1 CN 2021107269 W CN2021107269 W CN 2021107269W WO 2022017354 A1 WO2022017354 A1 WO 2022017354A1
Authority
WO
WIPO (PCT)
Prior art keywords
dci
field
pusch
semi
pdcch
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2021/107269
Other languages
English (en)
French (fr)
Inventor
李�根
李娜
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2022017354A1 publication Critical patent/WO2022017354A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H04L5/0057—Physical resource allocation for CQI
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames

Definitions

  • the present application belongs to the technical field of wireless communication, and specifically relates to a method for checking a physical downlink control channel (Physical Downlink Control Channel, PDCCH), a method for sending it, a terminal and a network side device.
  • PDCCH Physical Downlink Control Channel
  • New Radio Unlicensed Spectrum introduces scheduling of multiple physical uplink shared channels (Multi Physical Uplink Shared Channel, Multi-PUSCH) to DCI format 0_1 in Rel-16, but semi-static transmission in related technologies
  • DCI Downlink Control Information
  • Single-PUSCH Single-PUSCH
  • the activation or deactivation of the DCI for semi-static transmission is a problem that needs to be solved.
  • the purpose of the embodiments of the present application is to provide a PDCCH checking method, a sending method, a terminal, and a network side device, so as to solve the problem of how to activate or deactivate semi-static transmission using DCI scheduling Multi-PUSCH.
  • a method for checking PDCCH which is applied to a terminal, and the method includes:
  • the An indication field corresponds to multiple physical uplink shared channels PUSCH, and the first indication field includes at least one of an NDI field and an RVI field.
  • a device for checking PDCCH including:
  • a first receiving module configured to receive the first DCI
  • a first check module configured to determine that the first DCI is used as a semi-static transmission if the target bit position of the first indication field of the first DCI indicates '0' or not all '1' or a preset value.
  • the first indication field corresponds to multiple physical uplink shared channels PUSCH, and the first indication field includes at least one of an NDI field and an RVI field.
  • the first check module is configured to indicate that the DFI flag field of the first DCI is '0' if the PDCCH transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI Or the DFI flag field does not exist, and the target bit position of the first indication field of the first DCI indicates '0' or not all '1' or a preset value, it is determined that the first DCI is used as the activation of semi-static transmission or deactivate.
  • the target bit position is one of the following:
  • the bit position corresponding to the valid PUSCH in the NDI field of the first DCI is the highest or lowest M'*a bits in the NDI field, where M' is the bit position of the valid PUSCH scheduled by the first DCI.
  • the number, a is the size of each PUSCH NDI in the NDI field.
  • the bit position corresponding to the valid PUSCH in the RVI domain of the first DCI is the highest or lowest M'*b bits in the RVI domain, where M' is the bit position of the valid PUSCH scheduled by the first DCI.
  • the number, b is the size of each PUSCH RVI in the RVI field.
  • the target bit position indication is not all '1', including that one of the target bit positions is '0', and the rest are '1'.
  • the verification device of the PDCCH also includes:
  • a first determining module configured to determine that the start and length indication value SLIV used by the activated semi-static transmission is a predefined SLIV in the effective SLIV in the TDRA domain of the time domain resource allocation of the first DCI.
  • the PDCCH verification apparatus further includes:
  • the second determining module is configured to determine that the SLIV used by the activated semi-static transmission is the SLIV corresponding to the PUSCH in the first N bit positions or the last N bit positions in the TDRA field of the first DCI.
  • the PDCCH verification apparatus further includes:
  • a third determining module configured to determine that the SLIV used by the activated semi-static transmission is the SLIV corresponding to the target valid PUSCH in the TDRA field of the first DCI, and the target valid PUSCH is the SLIV in the first indication field
  • the bit positions corresponding to the valid PUSCH indicate the valid PUSCH corresponding to the position of '0'.
  • the PDCCH verification device further includes:
  • a second verification module configured to determine that the first DCI is used for deactivation of semi-static transmission if the first DCI also satisfies at least one of the following conditions:
  • the HARQ process quantity field of the first DCI indicates all '0';
  • the modulation and coding scheme MCS field of the first DCI indicates all '0';
  • the frequency domain resource allocation of the first DCI indicates that the FDRA domain is invalid resource allocation.
  • the PDCCH verification device further includes:
  • a second receiving module configured to receive the second DCI
  • the third check module is used for if the PDCCH transmitting the second DCI is scrambled by CS-RNTI or SP-CSI-RNTI, the DFI flag field of the second DCI is indicated as '0' or the DFI flag field does not exist , and the valid PUSCH position indications in the NDI field of the second DCI are all '1', it is determined that the second DCI is used as the scheduled retransmission of semi-static transmission.
  • the semi-static transmission is SPS PDSCH transmission or the second type of configuration grant PUSCH transmission or semi-static CSI transmission.
  • a third aspect provides a method for sending a PDCCH, which is applied to a network side device, including:
  • the target bit position of the first indication field of the first DCI indicates '0' or not all '1' or a preset value
  • An indication field includes at least one of an NDI field and an RVI field.
  • a device for transmitting PDCCH including:
  • a first sending module configured to transmit the first DCI used for activation or deactivation of semi-static transmission, wherein the target bit position of the first indication field of the first DCI indicates '0' or not all '1' or By default, the first indication field includes at least one of an NDI field and an RVI field.
  • the PDCCH for transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI, and the DFI flag field of the first DCI indicates '0' or the DFI flag field does not exist.
  • the target bit position is one of the following:
  • the bit position corresponding to the valid PUSCH in the NDI field of the first DCI is the highest or lowest M'*a bits in the NDI field, where M' is the bit position of the valid PUSCH scheduled by the first DCI.
  • the number, a is the size of each PUSCH NDI in the NDI field.
  • the bit position corresponding to the valid PUSCH in the RVI domain of the first DCI is the highest or lowest M'*b bits in the RVI domain, where M' is the bit position of the valid PUSCH scheduled by the first DCI.
  • the number, b is the size of each PUSCH RVI in the RVI field.
  • the target bit position indication is not all '1', including that one of the target bit positions is '0', and the rest are '1'.
  • the first DCI also satisfies at least one of the following conditions:
  • the HARQ process quantity field of the first DCI indicates all '0';
  • the modulation and coding scheme MCS field of the first DCI indicates all '0';
  • the frequency domain resource allocation of the first DCI indicates that the FDRA domain is invalid resource allocation.
  • the apparatus for transmitting the PDCCH further includes:
  • the second sending module is configured to transmit the second DCI used for the scheduled retransmission of semi-static transmission, the PDCCH for transmitting the second DCI is scrambled by CS-RNTI or SP-CSI-RNTI, and the DFI of the second DCI is scrambled by CS-RNTI or SP-CSI-RNTI.
  • the flag field indicates '0' or the DFI flag field does not exist, and the valid PUSCH positions in the NDI field of the second DCI indicate all '1'.
  • the semi-static transmission is SPS PDSCH transmission or the second type of configuration grant PUSCH transmission or semi-static CSI transmission.
  • a terminal in a fifth aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, when the program or instruction is executed by the processor.
  • a network side device in a sixth aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the The processor implements the steps of the method as described in the third aspect when executed.
  • a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect, or the The steps of the method described in the third aspect.
  • a chip in an eighth aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a network-side device program or instruction, and implements the method described in the first aspect. the method described above, or implement the method described in the third aspect.
  • a program product is provided, the program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to implement the method as described in the first aspect, or implement the method as described in the first aspect.
  • the verification and configuration method of the DCI scheduling Multi-PUSCH used for activation or deactivation of semi-static transmission is specified, so that the terminal can accurately determine the timing of activation or deactivation of semi-static transmission.
  • FIG. 1 is a block diagram of a wireless communication system to which an embodiment of the present application can be applied;
  • FIG. 2 is a schematic flowchart of a method for checking a PDCCH according to an embodiment of the present application
  • FIG. 3 is a schematic flowchart of a method for sending a PDCCH according to an embodiment of the present application
  • FIG. 4 is a schematic structural diagram of an apparatus for checking a PDCCH according to an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of an apparatus for sending a PDCCH according to an embodiment of the present application
  • FIG. 6 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a terminal according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a network side device according to an embodiment of the present application.
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the associated objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution-Advanced
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
  • NR New Radio
  • the following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the description below, although these techniques are also applicable to applications other than NR system applications, such as 6th generation ( 6 th Generation, 6G) communication system.
  • 6th generation 6 th Generation, 6G
  • FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied.
  • the wireless communication system includes a terminal 11 and a network-side device 12 .
  • the terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital computer Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (VUE), pedestrian terminal (PUE) and other terminal-side devices, wearable devices include: bracelets, headphones, glasses, etc.
  • PDA Personal Digital Assistant
  • the network side device 12 may be a base station or a core network, wherein the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN Access Point, WiFi Node, Send Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms.
  • the base station in the NR system is taken as an example, but the specific type of the base station is not limited.
  • the activation or deactivation of semi-static transmission in the related art is designed using DCI, only considering the activation or deactivation of semi-static transmission using DCI scheduling a single PUSCH, how to use DCI scheduling Multi-PUSCH to activate semi-static transmission Or deactivation is the problem that needs to be solved.
  • an embodiment of the present application provides a method for checking a physical downlink control channel (Physical Downlink Control Channel, PDCCH), which is applied to a terminal, including:
  • Step 21 Receive the first DCI
  • the first DCI is DCI format 0_1 that supports scheduling of Multi-PUSCH.
  • Step 22 If the target bit position of the first indication field of the first DCI indicates '0' or not all '1' or a preset value, determine that the first DCI is used for activation or deactivation of semi-static transmission,
  • the first indication field corresponds to multiple PUSCHs, and the first indication field includes at least one of a new data indicator (New data indicator, NDI) and a redundancy version indication (RVI) field.
  • New data indicator NDI
  • RVI redundancy version indication
  • the NDI field is an NDI of an enabled (Transport Block, TB) in the DCI, which is used to indicate the time-domain position of the scheduled PUSCH transmission.
  • non-all '1' means that the target bit position is not all '1', for example, one position in the target bit position is '0', and the rest are '1'.
  • the preset value refers to a value different from all '0' and not all '1', such as '10' and the like.
  • the preset value may be agreed by the protocol.
  • the target bit position of the first indication field of the first DCI indicates '0' or not all '1' or a preset value, it is determined that the first DCI is used as a semi-static Activation or deactivation of transmissions includes:
  • the PDCCH transmitting the first DCI is scrambled by the Configured Scheduling Radio Network Temporary Identity (CS-RNTI) or the Semi-Persistently Scheduled Channel State Information Radio Network Temporary Identity (SP-CSI-RNTI)
  • CS-RNTI Configured Scheduling Radio Network Temporary Identity
  • SP-CSI-RNTI Semi-Persistently Scheduled Channel State Information Radio Network Temporary Identity
  • DFI Deep Flow Inspection
  • the first DCI in the PDCCH is used as a semi-persistent scheduling (Semi-Persistent Scheduling, SPS) physical downlink shared channel (Physical Downlink Shared Channel, PDSCH) or configuration grant (Configured grant) PUSCH retransmission, or, used as SPS PDSCH or Type 2 Configured grant (Type 2 Configured grant) PUSCH activation or semi-static CSI transmission, or , for deactivation of SPS PDSCH or Type 2 Configured grant PUSCH or semi-static CSI transmission, or for DFI transmission.
  • SPS semi-persistent scheduling
  • PDSCH Physical Downlink Shared Channel
  • configuration grant Configured grant
  • PUSCH retransmission or, used as SPS PDSCH or Type 2 Configured grant (Type 2 Configured grant) PUSCH activation or semi-static CSI transmission, or , for deactivation of SPS PDSCH or Type 2 Configured grant PUSCH or semi-static CSI transmission, or for DFI transmission.
  • the DFI flag field of the first DCI indicates '0' or the DFI flag field does not exist, it can be considered that the first DCI is not used for DFI transmission.
  • the target bit position of the first indication field indicates '0' or not all '1' or a preset value, it may be considered that the first DCI is used for activation or deactivation of semi-static transmission.
  • the semi-static transmission is SPS PDSCH transmission or Type 2 Configured grant PUSCH transmission or semi-static CSI transmission.
  • the verification and configuration method of the DCI scheduling Multi-PUSCH used for the activation or deactivation of semi-static transmission is specified, so that the terminal can accurately determine the timing of activation or deactivation of semi-static transmission.
  • the following example describes the target bit position of the first indication field of the first DCI in the above embodiment.
  • the target bit positions of the first indication field are all bit positions of the first indication field. That is to say, if the PDCCH transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI, the DFI flag field of the first DCI indicates '0' or the DFI flag field does not exist, and the first All bit positions of the indication field indicate '0' or not all '1' or a preset value, and it is determined that the first DCI is used for activation or deactivation of semi-static transmission. All bit positions indicating '0' can also be described as indicating all '0'.
  • the following further includes:
  • the start and length indicator values (Start and Length Indicator Value, SLIV) used for determining the activated semi-static transmission are predefined in the valid SLIV in the time domain resource allocation (TDRA) field of the first DCI SLIV.
  • the terminal can determine the size of each field in the first DCI according to the Multi-PUSCH TDRA table, and it is assumed that the maximum number of PUSCHs that can be scheduled by the Multi-PUSCH TDRA table is M , then the size of the NDI field in the first DCI is M*a bits, a is the size of each PUSCH NDI in the NDI field, the size of the RVI field in the first DCI is M*b bits, and b is all The size of each PUSCH RVI in the above RVI field.
  • the terminal can determine the Multi-PUSCH TDRA table according to Table 3.
  • the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is not configured in pusch-ConfigCommon, the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is not configured in pusch-Config, and the PUSCH of DCI format0_1 is not configured in pusch-Config Domain resource allocation table (pusch-TimeDomainAllocationList-ForDCIformat0_1), Multi PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList-ForMultiPUSCH) is not configured in pusch-Config, then determine Default A table as Multi-PUSCH TDRA table.
  • PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is configured in pusch-ConfigCommon, PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is not configured in pusch-Config, and PUSCH of DCI format0_1 is not configured in pusch-Config Domain resource allocation table (pusch-TimeDomainAllocationList-ForDCIformat0_1), Multi PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList-ForMultiPUSCH) is not configured in pusch-Config, then determine the PUSCH time domain resource allocation table configured in pusch-ConfigCommon (pusch- TimeDomainAllocationList) as the Multi-PUSCH TDRA table.
  • PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is configured or not configured in pusch-ConfigCommon, PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is configured in pusch-Config, and DCI format0_1 is not configured in pusch-Config.
  • the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList-ForDCIformat0_1), the Multi PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList-ForMultiPUSCH) is not configured in pusch-Config, then determine the PUSCH time domain resource allocation table configured in pusch-Config (pusch-TimeDomainAllocationList) as the Multi-PUSCH TDRA table.
  • the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is configured or not configured in pusch-ConfigCommon, the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is configured or not configured in pusch-Config, and the configuration in pusch-Config If the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList-ForDCIformat0_1) of DCI format0_1 and the Multi PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList-ForMultiPUSCH) does not exist in pusch-Config, then determine the DCI format0_1 configured in pusch-Config.
  • the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList-ForDCIformat0_1) is used as the Multi-PUSCH TDRA table.
  • the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is configured or not configured in pusch-ConfigCommon, the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is configured or not configured in pusch-Config, and the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is not configured in pusch-Config.
  • the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList-ForDCIformat0_1) of DCI format0_1 exists, and the Multi PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList-ForMultiPUSCH) is configured in pusch-Config, then determine the Multi PUSCH configured in pusch-Config.
  • the domain resource allocation table (pusch-TimeDomainAllocationList-ForMultiPUSCH) is used as the Multi-PUSCH TDRA table.
  • each PUSCH corresponds to one SLIV, for example, the SLIVs corresponding to the M' PUSCHs can be respectively are SLIV 0 , SLIV 1 , ..., SLIV M'-1 .
  • the valid SLIV refers to the SLIV corresponding to the actually scheduled valid PUSCH, for example, SLIV 0 .
  • the target bit position of the first indication field is a bit position corresponding to a valid PUSCH of the first indication field. That is to say, if the PDCCH transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI, the DFI flag field of the first DCI indicates '0' or the DFI flag field does not exist, and the first The bit position corresponding to the valid PUSCH in the indication field indicates '0' or not all '1' or a preset value, and it is determined that the first DCI is used for activation or deactivation of semi-static transmission.
  • the bit position indication '0' corresponding to the valid PUSCH can also be described as the position indication of the valid PUSCH is all '0'.
  • the bit position corresponding to the valid PUSCH in the NDI field of the first DCI is determined by the number of valid PUSCHs scheduled by the first DCI and each PUSCH NDI in the NDI field size is determined.
  • the bit position corresponding to the valid PUSCH in the NDI field of the first DCI is the highest or lowest M'*a bits in the NDI field, where M' is the first The number of valid PUSCHs scheduled by DCI, a is the size of each PUSCH NDI in the NDI field. That is to say, the bit position corresponding to the valid PUSCH in the NDI field of the first DCI indicates '0' or not all '1' or a preset value, which means that the highest or lowest M'*a bits in the NDI field indicate '0' ' or not all '1' or a default value.
  • the bit position corresponding to the valid PUSCH in the RVI field of the first DCI is determined by the number of valid PUSCHs scheduled by the first DCI and the RVI of each PUSCH in the RVI field size is determined.
  • the bit position corresponding to the valid PUSCH in the RVI field of the first DCI is the highest or lowest M'*b bits in the RVI field, and M' is the first The number of valid PUSCHs scheduled by DCI, and b is the size of each PUSCH RVI in the RVI domain. That is to say, the bit position corresponding to the valid PUSCH in the RVI domain of the first DCI indicates '0' or not all '1' or a preset value, which means that the highest or lowest M'*b bits in the RVI domain indicate '0' ' or not all '1' or a default value.
  • the method further includes: determining the activated The SLIV used by the semi-static transmission is a predefined SLIV in the effective SLIV in the TDRA domain for the time domain resource allocation of the first DCI.
  • the following further includes: determine that the SLIV used by the activated semi-static transmission is the SLIV corresponding to the target valid PUSCH in the TDRA field of the first DCI, and the target valid PUSCH is the bit corresponding to the valid PUSCH in the first indication field A valid PUSCH corresponding to a position indicating '0' in the position.
  • the target bit position of the first indication field is the first N bit positions or the last N bit positions of the first indication field. That is to say, if the PDCCH transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI, the DFI flag field of the first DCI indicates '0' or the DFI flag field does not exist, and the first The first N bit positions or the last N bit positions of the indication field indicate '0' or not all '1' or a preset value, and it is determined that the first DCI is used for activation or deactivation of semi-static transmission.
  • a positive integer indicating '0' in the first N bit positions or the last N bit positions 1 may also be described as the first N bit positions or the last N bit positions indicating all '0'.
  • the first N bit positions or the last N bit positions are, for example, the first position or the last position.
  • the first DCI is used for activation or deactivation of semi-static transmission Afterwards, it also includes: determining that the SLIV used by the activated semi-static transmission is the SLIV corresponding to the PUSCH in the first N bit positions or the last N bit positions in the TDRA field of the first DCI (for example, SLIV0 or SLIV M' -1 ).
  • the method further includes: if the first DCI also satisfies at least one of the following conditions, determining the first DCI A DCI is used for deactivation of semi-static transmissions:
  • the HARQ process quantity field of the first DCI indicates all '0';
  • the modulation and coding scheme (Modulation and coding scheme, MCS) field of the first DCI indicates all '0';
  • the frequency domain resource allocation (Frequency domain resource allocation, FDRA) domain of the first DCI indicates that the resource allocation is invalid.
  • the FDRA domain is used to indicate the frequency domain resources of the scheduled PUSCH.
  • the first DCI is used as the activation of semi-static transmission.
  • the verification method of the PDCCH further includes:
  • the DFI flag field of the second DCI indicates '0' or the DFI flag field does not exist, and the second DCI
  • the valid PUSCH position indications in the NDI field are all '1', and it is determined that the second DCI is used as a scheduled retransmission of semi-static transmission.
  • Embodiment 1 of the present invention is a diagrammatic representation of Embodiment 1 of the present invention.
  • the CS-RNTI scrambled DCI format 0_1 refers to the Multi-PUSCH TDRA table. Assuming that the configured Multi-PUSCH TDRA table can schedule up to 4 PUSCHs, when the TDRA field of the DCI indicates that more than 1 PUSCH is scheduled, the NDI field in the DCI is 4 bits, and the RVI field is also 4 bits.
  • the UE considers the PDCCH as the DCI for activating semi-static transmission:
  • the first bit in NDI and RVI of DCI is '0', that is, NDI and RVI are '0xxx';
  • the number of valid PUSCHs indicated by the TDRA field in the DCI (assuming 2), NDI and RVI are '01xx' or '10xx'.
  • SLIV 0 is used; for '10xx', SLIV1 is used.
  • the above x is 0 or 1, or a predefined value.
  • Embodiment 2 of the present invention is a diagrammatic representation of Embodiment 2 of the present invention.
  • the Multi-PUSCH TDRA table When configuring the Multi-PUSCH TDRA table, refer to the Multi-PUSCH TDRA table for the DCI format 0_1 scrambled by SP-CSI-RNTI. Assuming that the configured Multi-PUSCH TDRA table can schedule up to 4 PUSCHs, when the TDRA field of the DCI indicates that more than 1 PUSCH is scheduled, the NDI field in the DCI is 4 bits, and the RVI field is also 4 bits.
  • the UE considers the PDCCH as the DCI for activating semi-static transmission:
  • the RVI of DCI is '0000';
  • the first bit in the RVI of the DCI is '0', that is, the RVI is '0xxx';
  • SLIV 0 is used; for '10xx', SLIV1 is used.
  • the above x is 0 or 1, or a predefined value.
  • an embodiment of the present application further provides a method for sending a PDCCH, which is applied to a network side device, including:
  • Step 31 transmitting the first DCI used for activation or deactivation of semi-static transmission, wherein the target bit position of the first indication field of the first DCI indicates '0' or not all '1' or a preset value,
  • the first indication field includes at least one of an NDI field and an RVI field.
  • the verification and configuration method of the DCI scheduling Multi-PUSCH used for activation or deactivation of semi-static transmission is specified, so that the terminal can accurately determine the timing of activation or deactivation of semi-static transmission.
  • the first DCI further satisfies the following conditions: the PDCCH transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI, and the DFI flag field of the first DCI Indicated as '0' or the DFI flag field does not exist.
  • the target bit position is one of the following:
  • the bit position corresponding to the valid PUSCH in the NDI field of the first DCI is determined by the number of valid PUSCHs scheduled by the first DCI and each PUSCH NDI in the NDI field size is determined.
  • the bit position corresponding to the valid PUSCH in the NDI field of the first DCI is the highest or lowest M'*a bits in the NDI field, where M' is the first The number of valid PUSCHs scheduled by DCI, a is the size of each PUSCH NDI in the NDI field.
  • the bit position corresponding to the valid PUSCH in the RVI field of the first DCI is determined by the number of valid PUSCHs scheduled by the first DCI and the RVI of each PUSCH in the RVI field size is determined.
  • the bit position corresponding to the valid PUSCH in the RVI field of the first DCI is the highest or lowest M'*b bits in the RVI field, and M' is the first The number of valid PUSCHs scheduled by DCI, and b is the size of each PUSCH RVI in the RVI domain.
  • the target bit position indication is not all '1', including that one position in the target bit position is '0', and the rest are '1'.
  • the first DCI optionally, if the first DCI is used for deactivation of semi-static transmission, the first DCI also satisfies at least one of the following conditions:
  • the HARQ process quantity field of the first DCI indicates all '0';
  • the modulation and coding scheme MCS field of the first DCI indicates all '0';
  • the frequency domain resource allocation of the first DCI indicates that the FDRA domain is invalid resource allocation.
  • the method for sending the PDCCH further includes:
  • a second DCI used as a scheduled retransmission of semi-static transmission is transmitted, the PDCCH in which the second DCI is transmitted is scrambled by CS-RNTI or SP-CSI-RNTI, and the DFI flag field of the second DCI indicates '0' Or the DFI flag field does not exist, and the valid PUSCH positions in the NDI field of the second DCI indicate all '1'.
  • the semi-static transmission is SPS PDSCH transmission or the second type of configuration grant PUSCH transmission or semi-static CSI transmission.
  • the execution subject may be a PDCCH verification apparatus, or a control module in the PDCCH verification apparatus for executing the PDCCH verification method.
  • the method for verifying the PDCCH performed by the PDCCH verification device is taken as an example to describe the PDCCH verification device provided in the embodiments of the present application.
  • an embodiment of the present application further provides a PDCCH verification apparatus 40, including:
  • a first receiving module 41 configured to receive the first DCI
  • a first check module 42 configured to determine that the first DCI is used for semi-static transmission if the target bit position of the first indication field of the first DCI indicates '0' or not all '1' or a preset value
  • the first indication field corresponds to multiple PUSCHs, and the first indication field includes at least one of an NDI field and an RVI field.
  • the first check module 42 is configured to indicate that the DFI flag field of the first DCI is '0 if the PDCCH transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI ' or the DFI flag field does not exist, and the target bit position of the first indication field of the first DCI indicates '0' or not all '1' or a preset value, it is determined that the first DCI is used for semi-static transmission. activate or deactivate.
  • the target bit position is one of the following:
  • the bit position corresponding to the valid PUSCH in the NDI field of the first DCI is the highest or lowest M'*a bits in the NDI field, where M' is the bit position of the valid PUSCH scheduled by the first DCI.
  • the number, a is the size of each PUSCH NDI in the NDI field.
  • the bit position corresponding to the valid PUSCH in the RVI domain of the first DCI is the highest or lowest M'*b bits in the RVI domain, where M' is the bit position of the valid PUSCH scheduled by the first DCI.
  • the number, b is the size of each PUSCH RVI in the RVI field.
  • the target bit position indication is not all '1', including that one of the target bit positions is '0', and the rest are '1'.
  • the verification device of the PDCCH also includes:
  • a first determining module configured to determine that the start and length indication value SLIV used by the activated semi-static transmission is a predefined SLIV in the effective SLIV in the TDRA domain of the time domain resource allocation of the first DCI.
  • the PDCCH verification apparatus further includes:
  • the second determining module is configured to determine that the SLIV used by the activated semi-static transmission is the SLIV corresponding to the PUSCH in the first N bit positions or the last N bit positions in the TDRA field of the first DCI.
  • the PDCCH verification apparatus further includes:
  • a third determining module configured to determine that the SLIV used by the activated semi-static transmission is the SLIV corresponding to the target valid PUSCH in the TDRA field of the first DCI, and the target valid PUSCH is the SLIV in the first indication field
  • the bit positions corresponding to the valid PUSCH indicate the valid PUSCH corresponding to the position of '0'.
  • the PDCCH verification device further includes:
  • a second verification module configured to determine that the first DCI is used for deactivation of semi-static transmission if the first DCI also satisfies at least one of the following conditions:
  • the HARQ process quantity field of the first DCI indicates all '0';
  • the modulation and coding scheme MCS field of the first DCI indicates all '0';
  • the frequency domain resource allocation of the first DCI indicates that the FDRA domain is invalid resource allocation.
  • the PDCCH verification device further includes:
  • a second receiving module configured to receive the second DCI
  • the third check module is used for if the PDCCH transmitting the second DCI is scrambled by CS-RNTI or SP-CSI-RNTI, the DFI flag field of the second DCI is indicated as '0' or the DFI flag field does not exist , and the valid PUSCH position indications in the NDI field of the second DCI are all '1', it is determined that the second DCI is used as the scheduled retransmission of semi-static transmission.
  • the semi-static transmission is SPS PDSCH transmission or the second type of configuration grant PUSCH transmission or semi-static CSI transmission.
  • the verification and configuration method of the DCI scheduling Multi-PUSCH used for activation or deactivation of semi-static transmission is specified, so that the terminal can accurately determine the timing of activation or deactivation of semi-static transmission.
  • the device for verifying the PDCCH in this embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal.
  • the device may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal may include, but is not limited to, the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (personal computer, PC), a television ( television, TV), teller machine, or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • the device for checking the PDCCH in the embodiment of the present application may be a device having an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • the apparatus for checking the PDCCH provided in the embodiment of the present application can implement each process implemented by the method embodiment in FIG. 2 , and achieve the same technical effect. To avoid repetition, details are not repeated here.
  • the execution subject may be a PDCCH sending apparatus, or a control module in the PDCCH sending apparatus for executing the PDCCH sending method.
  • the PDCCH transmitting apparatus provided in the embodiments of the present application is described by taking the PDCCH transmitting apparatus executing the PDCCH transmitting method as an example.
  • an embodiment of the present application further provides an apparatus 50 for sending a PDCCH, including:
  • the first sending module 51 is configured to transmit the first DCI used for activation or deactivation of semi-static transmission, wherein the target bit position of the first indication field of the first DCI indicates '0' or not all '1' Or a preset value, the first indication field includes at least one of an NDI field and an RVI field.
  • the first DCI also satisfies the following conditions: the PDCCH for transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI, and the DFI flag field of the first DCI indicates '0' or The DFI flag field does not exist.
  • the target bit position is one of the following:
  • the bit position corresponding to the valid PUSCH in the NDI field of the first DCI is determined by the number of valid PUSCHs scheduled by the first DCI and the size of each PUSCH NDI in the NDI field.
  • the bit position corresponding to the valid PUSCH in the NDI field of the first DCI is the highest or lowest M'*a bits in the NDI field, where M' is the bit position of the valid PUSCH scheduled by the first DCI.
  • the number, a is the size of each PUSCH NDI in the NDI field.
  • the bit position corresponding to the valid PUSCH in the RVI field of the first DCI is determined by the number of valid PUSCHs scheduled by the first DCI and the size of each PUSCH RVI in the RVI field.
  • the bit position corresponding to the valid PUSCH in the RVI domain of the first DCI is the highest or lowest M'*b bits in the RVI domain, where M' is the bit position of the valid PUSCH scheduled by the first DCI.
  • the number, b is the size of each PUSCH RVI in the RVI field.
  • the first N bit positions or the last N bit positions are the first N bit positions or the last N bit positions, and N is a positive integer greater than or equal to 1.
  • the indication of the target bit position is not all '1', including that one position in the target bit position is '0', and the rest are '1'.
  • the first DCI also satisfies at least one of the following conditions:
  • the HARQ process quantity field of the first DCI indicates all '0';
  • the modulation and coding scheme MCS field of the first DCI indicates all '0';
  • the frequency domain resource allocation of the first DCI indicates that the FDRA domain is invalid resource allocation.
  • the apparatus for transmitting the PDCCH further includes:
  • the second sending module is configured to transmit the second DCI used for the scheduled retransmission of semi-static transmission, the PDCCH for transmitting the second DCI is scrambled by CS-RNTI or SP-CSI-RNTI, and the DFI of the second DCI is scrambled by CS-RNTI or SP-CSI-RNTI.
  • the flag field indicates '0' or the DFI flag field does not exist, and the valid PUSCH positions in the NDI field of the second DCI indicate all '1'.
  • the semi-static transmission is SPS PDSCH transmission or the second type of configuration grant PUSCH transmission or semi-static CSI transmission.
  • the verification and configuration method of the DCI scheduling Multi-PUSCH used for activation or deactivation of semi-static transmission is specified, so that the terminal can accurately determine the timing of activation or deactivation of semi-static transmission.
  • the apparatus for sending the PDCCH provided in the embodiment of the present application can implement each process implemented by the method embodiment in FIG. 3 , and achieve the same technical effect. To avoid repetition, details are not described here.
  • an embodiment of the present application further provides a communication device 60, including a processor 61, a memory 62, a program or an instruction stored in the memory 62 and executable on the processor 61, for example, the communication
  • a communication device 60 including a processor 61, a memory 62, a program or an instruction stored in the memory 62 and executable on the processor 61, for example, the communication
  • the device 60 is a terminal
  • the program or instruction is executed by the processor 61
  • each process of the above-mentioned embodiments of the PDCCH verification method can be implemented, and the same technical effect can be achieved.
  • the communication device 60 is a network side device, when the program or instruction is executed by the processor 61, each process of the above-mentioned PDCCH sending method embodiment can be achieved, and the same technical effect can be achieved. To avoid repetition, details are not described here.
  • FIG. 7 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 70 includes but is not limited to: a radio frequency unit 71, a network module 72, an audio output unit 73, an input unit 74, a sensor 75, a display unit 76, a user input unit 77, an interface unit 78, a memory 79, and a processor 710 and other components .
  • the terminal 70 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 710 through a power management system, so as to manage charging, discharging, and power consumption through the power management system management and other functions.
  • a power source such as a battery
  • the terminal structure shown in FIG. 7 does not constitute a limitation on the terminal, and the terminal may include more or less components than shown, or combine some components, or arrange different components, which will not be repeated here.
  • the input unit 74 may include a graphics processor (Graphics Processing Unit, GPU) 741 and a microphone 742. Such as camera) to obtain still pictures or video image data for processing.
  • the display unit 76 may include a display panel 761, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 77 includes a touch panel 771 and other input devices 772 .
  • the touch panel 771 is also called a touch screen.
  • the touch panel 771 may include two parts, a touch detection device and a touch controller.
  • Other input devices 772 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which are not described herein again.
  • the radio frequency unit 71 processes it to the processor 710; in addition, it sends the uplink data to the network side device.
  • the radio frequency unit 71 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • Memory 79 may be used to store software programs or instructions as well as various data.
  • the memory 79 may mainly include a storage program or instruction area and a storage data area, wherein the storage program or instruction area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.) and the like.
  • the memory 79 may include a high-speed random access memory, and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM) , PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • ROM Read-Only Memory
  • PROM programmable read-only memory
  • PROM erasable programmable read-only memory
  • Erasable PROM Erasable PROM
  • EPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory for example at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the processor 710 may include one or more processing units; optionally, the processor 710 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, application programs or instructions, etc., Modem processors mainly deal with wireless communications, such as baseband processors. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 710.
  • the radio frequency unit 71 is used for receiving the first DCI
  • the processor 710 is configured to, if the target bit position of the first indication field of the first DCI indicates '0' or not all '1' or a preset value, determine whether the first DCI is used as the activation of semi-static transmission or For deactivation, the first indication field corresponds to multiple PUSCHs, and the first indication field includes at least one of an NDI field and an RVI field.
  • the verification and configuration method of the DCI scheduling Multi-PUSCH used for activation or deactivation of semi-static transmission is specified, so that the terminal can accurately determine the timing of activation or deactivation of semi-static transmission.
  • the processor 710 is further configured to indicate that the DFI flag field of the first DCI is '0' or DFI if the PDCCH transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI The flag field does not exist, and the target bit position of the first indication field of the first DCI indicates '0' or not all '1' or a preset value, it is determined that the first DCI is used for activation or deactivation of semi-static transmission activation.
  • the target bit position is one of the following:
  • the bit position corresponding to the valid PUSCH in the NDI field of the first DCI is determined by the number of valid PUSCHs scheduled by the first DCI and the size of each PUSCH NDI in the NDI field.
  • the bit position corresponding to the valid PUSCH in the NDI field of the first DCI is the highest or lowest M'*a bits in the NDI field, where M' is the bit position of the valid PUSCH scheduled by the first DCI.
  • the number, a is the size of each PUSCH NDI in the NDI field.
  • the bit position corresponding to the valid PUSCH in the RVI field of the first DCI is determined by the number of valid PUSCHs scheduled by the first DCI and the size of each PUSCH RVI in the RVI field.
  • the bit position corresponding to the valid PUSCH in the RVI domain of the first DCI is the highest or lowest M'*b bits in the RVI domain, where M' is the bit position of the valid PUSCH scheduled by the first DCI.
  • the number, b is the size of each PUSCH RVI in the RVI field.
  • the indication of the target bit position is not all '1', including that one position in the target bit position is '0', and the rest are '1'.
  • the processor 710 is further configured to determine that the start and length indication value SLIV used by the activated semi-static transmission is a predefined value in the effective SLIV in the TDRA domain of the time domain resource allocation of the first DCI SLIV.
  • the processor 710 is further configured to determine that the SLIV used by the activated semi-static transmission is: The SLIV corresponding to the PUSCH in the first N bit positions or the last N bit positions in the TDRA field of the first DCI.
  • the processor 710 is further configured to determine that the SLIV used by the activated semi-static transmission is the first SLIV.
  • the processor 710 is further configured to determine that the first DCI is used for deactivation of semi-static transmission if the first DCI also satisfies at least one of the following conditions:
  • the HARQ process quantity field of the first DCI indicates all '0';
  • the modulation and coding scheme MCS field of the first DCI indicates all '0';
  • the frequency domain resource allocation of the first DCI indicates that the FDRA domain is invalid resource allocation.
  • the radio frequency unit 71 is further configured to receive the second DCI
  • the processor 710 is further configured to indicate that if the PDCCH transmitting the second DCI is scrambled by CS-RNTI or SP-CSI-RNTI, the DFI flag field of the second DCI indicates '0' or the DFI flag field is not. exists, and the valid PUSCH positions in the NDI field of the second DCI indicate all '1', it is determined that the second DCI is used as a scheduled retransmission of semi-static transmission.
  • the semi-static transmission is SPS PDSCH transmission or the second type of configuration authorized PUSCH transmission or semi-static CSI transmission.
  • the network device 80 includes: an antenna 81 , a radio frequency device 82 , and a baseband device 83 .
  • the antenna 81 is connected to the radio frequency device 82 .
  • the radio frequency device 82 receives information through the antenna 81, and sends the received information to the baseband device 83 for processing.
  • the baseband device 83 processes the information to be sent and sends it to the radio frequency device 82
  • the radio frequency device 82 processes the received information and sends it out through the antenna 81 .
  • the above-mentioned frequency band processing apparatus may be located in the baseband apparatus 83 , and the method performed by the network side device in the above embodiments may be implemented in the baseband apparatus 83 .
  • the baseband apparatus 83 includes a processor 84 and a memory 85 .
  • the baseband device 83 may include, for example, at least one baseband board on which a plurality of chips are arranged. As shown in FIG. 8 , one of the chips is, for example, the processor 84 and is connected to the memory 85 to call the program in the memory 85 to execute The network devices shown in the above method embodiments operate.
  • the baseband device 83 may further include a network interface 86 for exchanging information with the radio frequency device 82, and the interface is, for example, a common public radio interface (CPRI for short).
  • CPRI common public radio interface
  • the network-side device in the embodiment of the present invention further includes: instructions or programs stored in the memory 85 and executable on the processor 84, and the processor 84 invokes the instructions or programs in the memory 85 to execute each module shown in FIG. 3
  • Embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, each process of the foregoing PDCCH verification method embodiment is implemented, and can To achieve the same technical effect, in order to avoid repetition, details are not repeated here.
  • Embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, each process of the above-mentioned PDCCH sending method embodiment is implemented, and can achieve The same technical effect, in order to avoid repetition, will not be repeated here.
  • the processor is the processor in the terminal described in the foregoing embodiment.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a network-side device program or instruction to implement the calibration of the PDCCH described above.
  • the chip includes a processor and a communication interface
  • the communication interface is coupled to the processor
  • the processor is used to run a network-side device program or instruction to implement the calibration of the PDCCH described above.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a network-side device program or instruction to implement the above-mentioned sending of the PDCCH
  • the chip includes a processor and a communication interface
  • the communication interface is coupled to the processor
  • the processor is used to run a network-side device program or instruction to implement the above-mentioned sending of the PDCCH
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • An embodiment of the present application further provides a program product, the program product is stored in a non-volatile storage medium, the program product is executed by at least one processor to implement each process of the foregoing PDCCH verification method embodiment, and The same technical effect can be achieved, and in order to avoid repetition, details are not repeated here.
  • An embodiment of the present application further provides a program product, where the program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to implement each process of the foregoing PDCCH sending method embodiments, and The same technical effect can be achieved, and in order to avoid repetition, details are not repeated here.
  • modules, units, sub-modules, sub-units, etc. can be implemented in one or more Application Specific Integrated Circuits (ASIC), Digital Signal Processing (DSP), digital signal processing equipment ( DSP Device, DSPD), Programmable Logic Device (Programmable Logic Device, PLD), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), general-purpose processor, controller, microcontroller, microprocessor, for in other electronic units or combinations thereof that perform the functions described herein.
  • ASIC Application Specific Integrated Circuits
  • DSP Digital Signal Processing
  • DSP Device digital signal processing equipment
  • PLD Programmable Logic Device
  • Field-Programmable Gate Array Field-Programmable Gate Array
  • FPGA Field-Programmable Gate Array

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种PDCCH的校验方法、发送方法、终端及网络侧设备，属于无线通信技术领域。应用于终端的PDCCH的校验方法包括：接收第一DCI；若所述第一DCI的第一指示域的目标比特位置指示'0'或者非全'1'或者预设值，确定所述第一DCI用作半静态传输的激活或去激活，所述第一指示域对应多个PUSCH，所述第一指示域包括NDI域和RVI域中的至少一项。

Description

PDCCH的校验方法、发送方法、终端及网络侧设备
相关申请的交叉引用
本申请主张在2020年7月21日在中国提交的中国专利申请号No.202010708044.5的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于无线通信技术领域，具体涉及一种物理下行控制信道(Physical Downlink Control Channel，PDCCH)的校验方法、发送方法、终端及网络侧设备。
背景技术
新无线未许可频谱(New Radio Unlicensed spectrum，NRU)在Rel-16对DCI format 0_1引入了多个物理上行共享信道(Multi Physical Uplink Shared Channel，Multi-PUSCH)的调度，但是相关技术中半静态传输的激活或去激活使用下行控制信息(Downlink Control Information，DCI)进行设计时，仅考虑了使用调度单个PUSCH(Single-PUSCH)的DCI进行半静态传输的激活或去激活，如何使用调度Multi-PUSCH的DCI进行半静态传输的激活或去激活是需要解决的问题。
发明内容
本申请实施例的目的是提供一种PDCCH的校验方法、发送方法、终端及网络侧设备，以解决如何使用调度Multi-PUSCH的DCI进行半静态传输的激活或去激活的问题。
为了解决上述技术问题，本申请是这样实现的：
第一方面，提供了一种PDCCH的校验方法，应用于终端，该方法包括：
接收第一下行控制信息DCI；
若所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活，所述第一指示 域对应多个物理上行共享信道PUSCH，所述第一指示域包括NDI域和RVI域中的至少一项。
第二方面，提供了一种PDCCH的校验装置，包括：
第一接收模块，用于接收第一DCI；
第一校验模块，用于若所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活，所述第一指示域对应多个物理上行共享信道PUSCH，所述第一指示域包括NDI域和RVI域中的至少一项。
可选的，所述第一校验模块，用于若传输所述第一DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第一DCI的DFI标志域指示为‘0’或者DFI标志域不存在，且所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活。
可选的，所述目标比特位置为以下之一：
所有比特位置；
有效PUSCH对应的比特位置；
前N个比特位置或者最后N个比特位置，N为大于或等于1的正整数。
可选的，所述第一DCI的NDI域中的有效PUSCH对应的比特位置为所述NDI域中的最高或最低M’*a个比特，M’为所述第一DCI调度的有效PUSCH的个数，a为所述NDI域中的每个PUSCH NDI的大小。
可选的，所述第一DCI的RVI域中的有效PUSCH对应的比特位置为所述RVI域中的最高或最低M’*b个比特，M’为所述第一DCI调度的有效PUSCH的个数，b为所述RVI域中的每个PUSCH RVI的大小。
可选的，所述目标比特位置指示非全‘1’包括所述目标比特位置中的一个位置为‘0’，其余为‘1’。
可选的，若所述第一指示域的所有比特位置均指示‘0’或者非全‘1’或者预设值，或者，所述第一指示域的有效PUSCH对应的比特位置均指示‘0’，所述PDCCH的验证装置还包括：
第一确定模块，用于确定激活的所述半静态传输所使用的起始和长度指示值SLIV为所述第一DCI的时域资源分配TDRA域中的有效SLIV中的预 定义的SLIV。
可选的，若所述第一指示域的前N个比特位置或者最后N个比特位置指示‘0’，所述PDCCH的验证装置还包括：
第二确定模块，用于确定激活的所述半静态传输所使用的SLIV为所述第一DCI的TDRA域中的所述前N个比特位置或者最后N个比特位置的PUSCH对应的SLIV。
可选的，若所述第一指示域的有效PUSCH对应的比特位置指示非全‘1’，所述PDCCH的验证装置还包括：
第三确定模块，用于确定激活的所述半静态传输所使用的SLIV为所述第一DCI的TDRA域中的目标有效PUSCH对应的SLIV，所述目标有效PUSCH为所述第一指示域中的有效PUSCH对应的比特位置中指示‘0’的位置对应的有效PUSCH。
可选的，所述PDCCH的验证装置还包括：
第二校验模块，用于若所述第一DCI还满足以下条件中的至少一项，确定所述第一DCI用作半静态传输的去激活：
所述第一DCI的HARQ进程数量域指示全‘0’；
所述第一DCI的调制和编码方案MCS域指示全‘0’；
所述第一DCI的频域资源分配FDRA域指示为无效资源分配。
可选的，所述PDCCH的验证装置还包括：
第二接收模块，用于接收第二DCI；
第三校验模块，用于若传输所述第二DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第二DCI的DFI标志域指示为‘0’或者DFI标志域不存在，且所述第二DCI的NDI域中的有效PUSCH位置指示全‘1’，确定所述第二DCI用作半静态传输的调度重传。
可选的，所述半静态传输为SPS PDSCH传输或第二类型的配置授权PUSCH传输或半静态的CSI传输。
第三方面，提供了一种PDCCH的发送方法，应用于网络侧设备，包括：
传输用作半静态传输的激活或去激活的第一DCI，其中，所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，所述第一指示 域包括NDI域和RVI域中的至少一项。
第四方面，提供了一种PDCCH的传输装置，包括：
第一发送模块，用于传输用作半静态传输的激活或去激活的第一DCI，其中，所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，所述第一指示域包括NDI域和RVI域中的至少一项。
可选的，传输所述第一DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第一DCI的DFI标志域指示为‘0’或者DFI标志域不存在。
可选的，所述目标比特位置为以下之一：
所有比特位置；
有效PUSCH对应的比特位置；
前N个比特位置或者最后N个比特位置，N为大于或等于1的正整数。
可选的，所述第一DCI的NDI域中的有效PUSCH对应的比特位置为所述NDI域中的最高或最低M’*a个比特，M’为所述第一DCI调度的有效PUSCH的个数，a为所述NDI域中的每个PUSCH NDI的大小。
可选的，所述第一DCI的RVI域中的有效PUSCH对应的比特位置为所述RVI域中的最高或最低M’*b个比特，M’为所述第一DCI调度的有效PUSCH的个数，b为所述RVI域中的每个PUSCH RVI的大小。
可选的，所述目标比特位置指示非全‘1’包括所述目标比特位置中的一个位置为‘0’，其余为‘1’。
可选的，若所述第一DCI用作半静态传输的去激活，所述第一DCI还满足以下条件中的至少一项：
所述第一DCI的HARQ进程数量域指示全‘0’；
所述第一DCI的调制和编码方案MCS域指示全‘0’；
所述第一DCI的频域资源分配FDRA域指示为无效资源分配。
可选的，所述PDCCH的传输装置还包括：
第二发送模块，用于传输用作半静态传输的调度重传的第二DCI，传输所述第二DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第二DCI的DFI标志域指示为‘0’或者DFI标志域不存在，且所述第二DCI的NDI域中的有效PUSCH位置指示全‘1’。
可选的，所述半静态传输为SPS PDSCH传输或第二类型的配置授权PUSCH传输或半静态的CSI传输。
第五方面，提供了一种终端，该终端包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面，提供了一种网络侧设备，该网络侧设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第三方面所述的方法的步骤。
第七方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤。
第八方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络侧设备程序或指令，实现如第一方面所述的方法，或实现如第三方面所述的方法。
第九方面，提供了一种程序产品，所述程序产品存储在非易失的存储介质中，所述程序产品被至少一个处理器执行以实现如第一方面所述的方法，或实现如第三方面所述的方法。
在本申请实施例中，明确了用作半静态传输的激活或去激活的调度Multi-PUSCH的DCI的验证和配置方法，以使得终端能够准确确定进行半静态传输的激活或去激活的时机。
附图说明
图1是本申请实施例可应用的一种无线通信系统的框图；
图2是本申请实施例的PDCCH的校验方法的流程示意图；
图3是本申请实施例的PDCCH的发送方法的流程示意图；
图4是本申请实施例的PDCCH的校验装置的结构示意图；
图5是本申请实施例的PDCCH的发送装置的结构示意图；
图6是本申请实施例的通信设备的结构示意图；
图7是本申请实施例的终端的结构示意图；
图8是本申请实施例的网络侧设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。然而，以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，尽管这些技术也可应用于NR系统应用以外的应用，如第6代(6 th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11也可以称作终端设备或者用户终端(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal  Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(VUE)、行人终端(PUE)等终端侧设备，可穿戴式设备包括：手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
对于DCI调度单个PUSCH(Single-PUSCH)的场景，按照表1和表2来校验DCI是否用作激活或去激活半静态传输。
表1激活半静态传输的DCI的配置
Figure PCTCN2021107269-appb-000001
表2去激活半静态传输的配置
Figure PCTCN2021107269-appb-000002
相关技术中半静态传输的激活或去激活使用DCI进行设计时，仅考虑了使用调度单个PUSCH的DCI进行半静态传输的激活或去激活，如何使用调度Multi-PUSCH的DCI进行半静态传输的激活或去激活是需要解决的问题。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供的PDCCH的校验方法、发送方法、终端及网络侧设备进行详细地说明。
请参考图2，本申请实施例提供一种物理下行控制信道(Physical Downlink Control Channel，PDCCH)的校验方法，应用于终端，包括：
步骤21：接收第一DCI；
所述第一DCI为支持调度Multi-PUSCH的DCI format 0_1。
步骤22：若所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活，所述第一指示域对应多个PUSCH，所述第一指示域包括新数据指示(New data indicator，NDI)和冗余版本指示(RVI)域中的至少一项。
本申请实施例中，所述NDI域为DCI中使能(enabled)传输块(Transport  Block，TB)的NDI，用于指示调度的PUSCH传输的时域位置。
本申请实施例中，非全‘1’是指所述目标比特位置不全指示‘1’，例如，所述目标比特位置中的一个位置为‘0’，其余为‘1’。
本申请实施例中，预设值是指不同于全‘0’、非全‘1’的值，例如‘10’等。所述预设值可以由协议约定。
本申请实施例中，可选的，若所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活包括：
若传输所述第一DCI的PDCCH由配置调度无线网络临时标识(Configured Scheduling Radio Network Temporary Identity，CS-RNTI)或半静态调度信道状态信息无线网络临时标识(SP-CSI-RNTI)加扰，所述第一DCI的深度流检测(Deep Flow Inspection，DFI)标志域指示为‘0’或者DFI标志域不存在，且所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活。
本申请实施例中，当检测到PDCCH由CS-RNTI或SP-CSI-RNTI加扰时，可以认为该PDCCH中的第一DCI用作半持续调度(Semi-Persistent Scheduling，SPS)物理下行共享信道(Physical Downlink Shared Channel，PDSCH)或配置授权(Configured grant)PUSCH的重传，或者，用作SPS PDSCH或第二类型的配置授权(Type 2 Configured grant)PUSCH的激活或半静态的CSI传输，或者，用作SPS PDSCH或Type 2 Configured grant PUSCH或半静态的CSI传输的去激活，或者，用作DFI的传输。
进一步的，当检测到所述第一DCI的DFI标志域指示为‘0’或者DFI标志域不存在，可以认为该第一DCI不用作DFI传输。当检测到所述第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，可以认为该第一DCI用作半静态传输的激活或去激活。
可选的，所述半静态传输为SPS PDSCH传输或Type 2 Configured grant PUSCH传输或半静态的CSI传输。
本申请实施例中，明确了用作半静态传输的激活或去激活的调度Multi-PUSCH的DCI的验证和配置方法，以使得终端能够准确确定进行半静 态传输的激活或去激活的时机。
下面举例对上述实施例中的第一DCI的第一指示域的目标比特位置进行说明。
在本申请的一些实施例中，可选的，第一指示域的目标比特位置为第一指示域的所有比特位置。也就是说，若传输所述第一DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第一DCI的DFI标志域指示为‘0’或者DFI标志域不存在，且第一指示域的所有比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活。所有比特位置指示‘0’也可以描述为指示全‘0’。
本申请实施例中，若第一指示域的所有比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活之后还包括：确定激活的所述半静态传输所使用的起始和长度指示值(Start and Length Indicator Value，SLIV)为所述第一DCI的时域资源分配(TDRA)域中的有效SLIV中的预定义的SLIV。
本申请实施例中，如果配置了Multi-PUSCH TDRA表，终端可以根据Multi-PUSCH TDRA表来确定第一DCI中各个域的大小，假设Multi-PUSCH TDRA表可调度的PUSCH的最大个数为M，则第一DCI中NDI域的大小为M*a个比特，a为所述NDI域中的每个PUSCH NDI的大小，第一DCI中RVI域的大小为M*b个比特，b为所述RVI域中的每个PUSCH RVI的大小。
终端可以根据表3确定Multi-PUSCH TDRA表。
表3
Figure PCTCN2021107269-appb-000003
从表3可以看出：
1)若pusch-ConfigCommon中未配置PUSCH时域资源分配表(pusch-TimeDomainAllocationList)、pusch-Config中未配置PUSCH时域资源分配表(pusch-TimeDomainAllocationList)、pusch-Config中未配置DCI format0_1的PUSCH时域资源分配表(pusch-TimeDomainAllocationList-ForDCIformat0_1)、pusch-Config中未配置Multi PUSCH时域资源分配表(pusch-TimeDomainAllocationList–ForMultiPUSCH)，则确定Default A表作 为Multi-PUSCH TDRA表。
2)若pusch-ConfigCommon中配置了PUSCH时域资源分配表(pusch-TimeDomainAllocationList)、pusch-Config中未配置PUSCH时域资源分配表(pusch-TimeDomainAllocationList)、pusch-Config中未配置DCI format0_1的PUSCH时域资源分配表(pusch-TimeDomainAllocationList-ForDCIformat0_1)、pusch-Config中未配置Multi PUSCH时域资源分配表(pusch-TimeDomainAllocationList–ForMultiPUSCH)，则确定pusch-ConfigCommon中配置的PUSCH时域资源分配表(pusch-TimeDomainAllocationList)作为Multi-PUSCH TDRA表。
3)若pusch-ConfigCommon中配置了或未配置PUSCH时域资源分配表(pusch-TimeDomainAllocationList)、pusch-Config中配置了PUSCH时域资源分配表(pusch-TimeDomainAllocationList)、pusch-Config中未配置DCI format0_1的PUSCH时域资源分配表(pusch-TimeDomainAllocationList-ForDCIformat0_1)、pusch-Config中未配置Multi PUSCH时域资源分配表(pusch-TimeDomainAllocationList–ForMultiPUSCH)，则确定pusch-Config中配置的PUSCH时域资源分配表(pusch-TimeDomainAllocationList)作为Multi-PUSCH TDRA表。
4)若pusch-ConfigCommon中配置了或未配置PUSCH时域资源分配表(pusch-TimeDomainAllocationList)、pusch-Config中配置了或未配置PUSCH时域资源分配表(pusch-TimeDomainAllocationList)、pusch-Config中配置了DCI format0_1的PUSCH时域资源分配表(pusch-TimeDomainAllocationList-ForDCIformat0_1)、pusch-Config中不存在Multi PUSCH时域资源分配表(pusch-TimeDomainAllocationList–ForMultiPUSCH)，则确定pusch-Config中配置的DCI format0_1的PUSCH时域资源分配表(pusch-TimeDomainAllocationList-ForDCIformat0_1)作为Multi-PUSCH TDRA表。
5)若pusch-ConfigCommon中配置了或未配置PUSCH时域资源分配表(pusch-TimeDomainAllocationList)、pusch-Config中配置了或未配置PUSCH时域资源分配表(pusch-TimeDomainAllocationList)、pusch-Config中不存在 DCI format0_1的PUSCH时域资源分配表(pusch-TimeDomainAllocationList-ForDCIformat0_1)、pusch-Config中配置了Multi PUSCH时域资源分配表(pusch-TimeDomainAllocationList–ForMultiPUSCH)，则确定pusch-Config中配置的Multi PUSCH时域资源分配表(pusch-TimeDomainAllocationList–ForMultiPUSCH)作为Multi-PUSCH TDRA表。
假设第一DCI中TDRA域中实际调度的有效PUSCH的个数为M’(1＝<M’<＝M))，每个PUSCH对应一个SLIV，例如则该M’个PUSCH对应的SLIV可以分别为SLIV 0,SLIV 1,…,SLIV M’-1。有效SLIV则是指实际调度的有效PUSCH对应的SLIV，例如为SLIV 0。
在本申请的一些实施例中，可选的，第一指示域的目标比特位置为第一指示域的有效PUSCH对应的比特位置。也就是说，若传输所述第一DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第一DCI的DFI标志域指示为‘0’或者DFI标志域不存在，且第一指示域的有效PUSCH对应的比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活。有效PUSCH对应的比特位置指示‘0’也可以描述为有效PUSCH的位置指示全‘0’。
本申请实施例中，可选的，所述第一DCI的NDI域中的有效PUSCH对应的比特位置由所述第一DCI调度的有效PUSCH的个数和所述NDI域中的每个PUSCH NDI的大小确定。
本申请实施例中，可选的，所述第一DCI的NDI域中的有效PUSCH对应的比特位置为所述NDI域中的最高或最低M’*a个比特，M’为所述第一DCI调度的有效PUSCH的个数，a为所述NDI域中的每个PUSCH NDI的大小。也就是说，第一DCI的NDI域的有效PUSCH对应的比特位置指示‘0’或者非全‘1’或者预设值，是指NDI域中的最高或最低M’*a个比特指示‘0’或者非全‘1’或者预设值。
本申请实施例中，可选的，所述第一DCI的RVI域中的有效PUSCH对应的比特位置由所述第一DCI调度的有效PUSCH的个数和所述RVI域中的每个PUSCH RVI的大小确定。
本申请实施例中，可选的，所述第一DCI的RVI域中的有效PUSCH对 应的比特位置为所述RVI域中的最高或最低M’*b个比特，M’为所述第一DCI调度的有效PUSCH的个数，b为所述RVI域中的每个PUSCH RVI的大小。也就是说，第一DCI的RVI域的有效PUSCH对应的比特位置指示‘0’或者非全‘1’或者预设值，是指RVI域中的最高或最低M’*b个比特指示‘0’或者非全‘1’或者预设值。
本申请实施例中，可选的，若第一指示域的有效PUSCH对应的比特位置指示‘0’，确定所述第一DCI用作半静态传输的激活或去激活之后还包括：确定激活的所述半静态传输所使用的SLIV为所述第一DCI的时域资源分配TDRA域中的有效SLIV中的预定义的SLIV。
本申请实施例中，可选的，若所述第一指示域的有效PUSCH对应的比特位置指示非全‘1’，确定所述第一DCI用作半静态传输的激活或去激活之后还包括：确定激活的所述半静态传输所使用的SLIV为所述第一DCI的TDRA域中的目标有效PUSCH对应的SLIV，所述目标有效PUSCH为所述第一指示域中的有效PUSCH对应的比特位置中指示‘0’的位置对应的有效PUSCH。
在本申请的一些实施例中，可选的，第一指示域的目标比特位置为第一指示域的前N个比特位置或者最后N个比特位置。也就是说，若传输所述第一DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第一DCI的DFI标志域指示为‘0’或者DFI标志域不存在，且第一指示域的前N个比特位置或者最后N个比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活。前N个比特位置或者最后N个比特位置1的正整数指示‘0’也可以描述为前N个比特位置或者最后N个比特位置指示全‘0’。
本申请实施例中，可选的，前N个比特位置或者最后N个比特位置例如为第一个位置或者最后一个位置。
本申请实施例中，可选的，若所述第一指示域的前N个比特位置或者最后N个比特位置指示‘0’，确定所述第一DCI用作半静态传输的激活或去激活之后还包括：确定激活的所述半静态传输所使用的SLIV为所述第一DCI的TDRA域中的前N个比特位置或者最后N个比特位置的PUSCH对应的SLIV(例如SLIV0或SLIV M’-1)。
本申请实施例中，可选的，确定所述第一DCI用作半静态传输的激活或去激活之后还包括：若所述第一DCI还满足以下条件中的至少一项，确定所述第一DCI用作半静态传输的去激活：
所述第一DCI的HARQ进程数量域指示全‘0’；
所述第一DCI的调制和编码方案(Modulation and coding scheme，MCS)域指示全‘0’；
所述第一DCI的频域资源分配(Frequency domain resource allocation，FDRA)域指示为无效资源分配。所述FDRA域用于指示调度的PUSCH的频域资源。
也就是说，若不满足上述条件，所述第一DCI则用作半静态传输的激活。
本申请实施例中，可选的，所述PDCCH的验证方法还包括：
接收第二DCI；
若传输所述第二DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第二DCI的DFI标志域指示为‘0’或者DFI标志域不存在，且所述第二DCI的NDI域中的有效PUSCH位置指示全‘1’，确定所述第二DCI用作半静态传输的调度重传。
下面结合具体实施例，本申请的上述PDCCH的验证方法进行说明。
本发明实施例一：
当配置了Multi-PUSCH TDRA表时，CS-RNTI加扰的DCI format 0_1参考该Multi-PUSCH TDRA表。假设配置的Multi-PUSCH TDRA表最大可调度4个PUSCH，当DCI的TDRA域指示调度大于1个PUSCH时，则DCI中的NDI域为4比特，RVI域也为4比特。
此时若满足以下条件之一，UE认为该PDCCH为激活半静态传输的DCI：
1、DCI的NDI和RVI为‘0000’；
2、DCI中TDRA域指示的有效PUSCH个数(假设为2)，NDI和RVI为‘00xx’；
3、DCI的NDI和RVI中的第1个比特为‘0’，即NDI和RVI为‘0xxx’；
4、DCI中TDRA域指示的有效PUSCH个数(假设为2)，NDI和RVI为‘01xx’或‘10xx’。
其中，对于‘01xx’，SLIV 0被使用；对于‘10xx’，SLIV1被使用。
上述x为0或1，或者预定义值。
本发明实施方式二：
当配置Multi-PUSCH TDRA表时，SP-CSI-RNTI加扰的DCI format 0_1参考Multi-PUSCH TDRA表。假设该配置的Multi-PUSCH TDRA表最大可调度4个PUSCH，当DCI的TDRA域指示调度大于1个PUSCH时，则DCI中的NDI域为4比特，RVI域也为4比特。
此时若满足以下条件之一，UE认为该PDCCH为激活半静态传输的DCI：
1、DCI的RVI为‘0000’；
2、DCI中TDRA域指示的有效PUSCH个数(假设为2)，RVI为‘00xx’；
3、DCI的RVI中的第1个比特为‘0’，即RVI为‘0xxx’；
4、DCI中TDRA域指示的有效PUSCH个数(假设为2)，RVI为‘01xx’或‘10xx’。
其中，对于‘01xx’，SLIV 0被使用；对于‘10xx’，SLIV1被使用。
上述x为0或1，或者预定义值。
请参考图3，本申请实施例还提供一种PDCCH的发送方法，应用于网络侧设备，包括：
步骤31：传输用作半静态传输的激活或去激活的第一DCI，其中，所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，所述第一指示域包括NDI域和RVI域中的至少一项。
本申请实施例中，明确了用作半静态传输的激活或去激活的调度Multi-PUSCH的DCI的验证和配置方法，以使得终端能够准确确定进行半静态传输的激活或去激活的时机。
本申请实施例中，可选的，所述第一DCI还满足以下条件：传输所述第一DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第一DCI的DFI标志域指示为‘0’或者DFI标志域不存在。
本申请实施例中，可选的，所述目标比特位置为以下之一：
所有比特位置；
有效PUSCH对应的比特位置；
前N个比特位置或者最后N个比特位置，N为大于或等于1的正整数。
本申请实施例中，可选的，所述第一DCI的NDI域中的有效PUSCH对应的比特位置由所述第一DCI调度的有效PUSCH的个数和所述NDI域中的每个PUSCH NDI的大小确定。
本申请实施例中，可选的，所述第一DCI的NDI域中的有效PUSCH对应的比特位置为所述NDI域中的最高或最低M’*a个比特，M’为所述第一DCI调度的有效PUSCH的个数，a为所述NDI域中的每个PUSCH NDI的大小。
本申请实施例中，可选的，所述第一DCI的RVI域中的有效PUSCH对应的比特位置由所述第一DCI调度的有效PUSCH的个数和所述RVI域中的每个PUSCH RVI的大小确定。
本申请实施例中，可选的，所述第一DCI的RVI域中的有效PUSCH对应的比特位置为所述RVI域中的最高或最低M’*b个比特，M’为所述第一DCI调度的有效PUSCH的个数，b为所述RVI域中的每个PUSCH RVI的大小。
本申请实施例中，可选的，所述目标比特位置指示非全‘1’包括所述目标比特位置中的一个位置为‘0’，其余为‘1’。
本申请实施例中，可选的，若所述第一DCI用作半静态传输的去激活，所述第一DCI还满足以下条件中的至少一项：
所述第一DCI的HARQ进程数量域指示全‘0’；
所述第一DCI的调制和编码方案MCS域指示全‘0’；
所述第一DCI的频域资源分配FDRA域指示为无效资源分配。
本申请实施例中，可选的，该PDCCH的发送方法还包括：
传输用作半静态传输的调度重传的第二DCI，传输所述第二DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第二DCI的DFI标志域指示为‘0’或者DFI标志域不存在，且所述第二DCI的NDI域中的有效PUSCH位置指示全‘1’。
本申请实施例中，可选的，所述半静态传输为SPS PDSCH传输或第二类型的配置授权PUSCH传输或半静态的CSI传输。
需要说明的是，本申请实施例提供的PDCCH的校验方法，执行主体可以为PDCCH的校验装置，或者，该PDCCH的校验装置中的用于执行PDCCH 的校验方法的控制模块。本申请实施例中以PDCCH的校验装置执行PDCCH的校验方法为例，说明本申请实施例提供的PDCCH的校验装置。
请参考图4，本申请实施例还提供一种PDCCH的校验装置40，包括：
第一接收模块41，用于接收第一DCI；
第一校验模块42，用于若所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活，所述第一指示域对应多个PUSCH，所述第一指示域包括NDI域和RVI域中的至少一项。
可选的，所述第一校验模块42，用于若传输所述第一DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第一DCI的DFI标志域指示为‘0’或者DFI标志域不存在，且所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活。
可选的，所述目标比特位置为以下之一：
所有比特位置；
有效PUSCH对应的比特位置；
前N个比特位置或者最后N个比特位置，N为大于或等于1的正整数。
可选的，所述第一DCI的NDI域中的有效PUSCH对应的比特位置为所述NDI域中的最高或最低M’*a个比特，M’为所述第一DCI调度的有效PUSCH的个数，a为所述NDI域中的每个PUSCH NDI的大小。
可选的，所述第一DCI的RVI域中的有效PUSCH对应的比特位置为所述RVI域中的最高或最低M’*b个比特，M’为所述第一DCI调度的有效PUSCH的个数，b为所述RVI域中的每个PUSCH RVI的大小。
可选的，所述目标比特位置指示非全‘1’包括所述目标比特位置中的一个位置为‘0’，其余为‘1’。
可选的，若所述第一指示域的所有比特位置均指示‘0’或者非全‘1’或者预设值，或者，所述第一指示域的有效PUSCH对应的比特位置均指示‘0’，所述PDCCH的验证装置还包括：
第一确定模块，用于确定激活的所述半静态传输所使用的起始和长度指示值SLIV为所述第一DCI的时域资源分配TDRA域中的有效SLIV中的预 定义的SLIV。
可选的，若所述第一指示域的前N个比特位置或者最后N个比特位置指示‘0’，所述PDCCH的验证装置还包括：
第二确定模块，用于确定激活的所述半静态传输所使用的SLIV为所述第一DCI的TDRA域中的所述前N个比特位置或者最后N个比特位置的PUSCH对应的SLIV。
可选的，若所述第一指示域的有效PUSCH对应的比特位置指示非全‘1’，所述PDCCH的验证装置还包括：
第三确定模块，用于确定激活的所述半静态传输所使用的SLIV为所述第一DCI的TDRA域中的目标有效PUSCH对应的SLIV，所述目标有效PUSCH为所述第一指示域中的有效PUSCH对应的比特位置中指示‘0’的位置对应的有效PUSCH。
可选的，所述PDCCH的验证装置还包括：
第二校验模块，用于若所述第一DCI还满足以下条件中的至少一项，确定所述第一DCI用作半静态传输的去激活：
所述第一DCI的HARQ进程数量域指示全‘0’；
所述第一DCI的调制和编码方案MCS域指示全‘0’；
所述第一DCI的频域资源分配FDRA域指示为无效资源分配。
可选的，所述PDCCH的验证装置还包括：
第二接收模块，用于接收第二DCI；
第三校验模块，用于若传输所述第二DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第二DCI的DFI标志域指示为‘0’或者DFI标志域不存在，且所述第二DCI的NDI域中的有效PUSCH位置指示全‘1’，确定所述第二DCI用作半静态传输的调度重传。
可选的，所述半静态传输为SPS PDSCH传输或第二类型的配置授权PUSCH传输或半静态的CSI传输。
本申请实施例中，明确了用作半静态传输的激活或去激活的调度Multi-PUSCH的DCI的验证和配置方法，以使得终端能够准确确定进行半静态传输的激活或去激活的时机。
本申请实施例中的PDCCH的校验装置可以是装置，也可以是终端中的部件、集成电路、或芯片。该装置可以是移动终端，也可以为非移动终端。示例性的，移动终端可以包括但不限于上述所列举的终端11的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例中的PDCCH的校验装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的PDCCH的校验装置能够实现图2的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，本申请实施例提供的PDCCH的发送方法，执行主体可以为PDCCH的发送装置，或者，该PDCCH的发送装置中的用于执行PDCCH的发送方法的控制模块。本申请实施例中以PDCCH的发送装置执行PDCCH的发送方法为例，说明本申请实施例提供的PDCCH的发送装置。
请参考图5，本申请实施例还提供一种PDCCH的发送装置50，包括：
第一发送模块51，用于传输用作半静态传输的激活或去激活的第一DCI，其中，所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，所述第一指示域包括NDI域和RVI域中的至少一项。
可选的，所述第一DCI还满足以下条件：传输所述第一DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第一DCI的DFI标志域指示为‘0’或者DFI标志域不存在。
可选的，所述目标比特位置为以下之一：
所有比特位置；
有效PUSCH对应的比特位置；
前N个比特位置或者最后N个比特位置，N为大于或等于1的正整数。
可选的，所述第一DCI的NDI域中的有效PUSCH对应的比特位置由所述第一DCI调度的有效PUSCH的个数和所述NDI域中的每个PUSCH NDI的大小确定。
可选的，所述第一DCI的NDI域中的有效PUSCH对应的比特位置为所述NDI域中的最高或最低M’*a个比特，M’为所述第一DCI调度的有效PUSCH的个数，a为所述NDI域中的每个PUSCH NDI的大小。
可选的，所述第一DCI的RVI域中的有效PUSCH对应的比特位置由所述第一DCI调度的有效PUSCH的个数和所述RVI域中的每个PUSCH RVI的大小确定。
可选的，所述第一DCI的RVI域中的有效PUSCH对应的比特位置为所述RVI域中的最高或最低M’*b个比特，M’为所述第一DCI调度的有效PUSCH的个数，b为所述RVI域中的每个PUSCH RVI的大小。
可选的，所述前N个比特位置或者最后N个比特位置为前N个比特位置或者最后N个比特位置，N为大于或等于1的正整数。
可选的，所述目标比特位置指示非全‘1’包括所述目标比特位置中的一个位置为‘0’，其余为‘1’。
可选的，若所述第一DCI用作半静态传输的去激活，所述第一DCI还满足以下条件中的至少一项：
所述第一DCI的HARQ进程数量域指示全‘0’；
所述第一DCI的调制和编码方案MCS域指示全‘0’；
所述第一DCI的频域资源分配FDRA域指示为无效资源分配。
可选的，所述PDCCH的传输装置还包括：
第二发送模块，用于传输用作半静态传输的调度重传的第二DCI，传输所述第二DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第二DCI的DFI标志域指示为‘0’或者DFI标志域不存在，且所述第二DCI的NDI域中的有效PUSCH位置指示全‘1’。
可选的，所述半静态传输为SPS PDSCH传输或第二类型的配置授权PUSCH传输或半静态的CSI传输。
本申请实施例中，明确了用作半静态传输的激活或去激活的调度Multi-PUSCH的DCI的验证和配置方法，以使得终端能够准确确定进行半静态传输的激活或去激活的时机。
本申请实施例提供的PDCCH的发送装置能够实现图3的方法实施例实 现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
如图6所示，本申请实施例还提供一种通信设备60，包括处理器61，存储器62，存储在存储器62上并可在所述处理器61上运行的程序或指令，例如，该通信设备60为终端时，该程序或指令被处理器61执行时实现上述PDCCH的校验方法实施例的各个过程，且能达到相同的技术效果。该通信设备60为网络侧设备时，该程序或指令被处理器61执行时实现上述PDCCH的发送方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
图7为实现本申请实施例的一种终端的硬件结构示意图。该终端70包括但不限于：射频单元71、网络模块72、音频输出单元73、输入单元74、传感器75、显示单元76、用户输入单元77、接口单元78、存储器79、以及处理器710等部件。
本领域技术人员可以理解，终端70还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器710逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图7中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元74可以包括图形处理器(Graphics Processing Unit，GPU)741和麦克风742，图形处理器741对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元76可包括显示面板761，可以采用液晶显示器、有机发光二极管等形式来配置显示面板761。用户输入单元77包括触控面板771以及其他输入设备772。触控面板771，也称为触摸屏。触控面板771可包括触摸检测装置和触摸控制器两个部分。其他输入设备772可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元71将来自网络侧设备的下行数据接收后，给处理器710处理；另外，将上行的数据发送给网络侧设备。通常，射频单元71包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、 双工器等。
存储器79可用于存储软件程序或指令以及各种数据。存储器79可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器79可以包括高速随机存取存储器，还可以包括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器710可包括一个或多个处理单元；可选的，处理器710可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器710中。
其中，射频单元71，用于接收第一DCI；
处理器710，用于若所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活，所述第一指示域对应多个PUSCH，所述第一指示域包括NDI域和RVI域中的至少一项。
本申请实施例中，明确了用作半静态传输的激活或去激活的调度Multi-PUSCH的DCI的验证和配置方法，以使得终端能够准确确定进行半静态传输的激活或去激活的时机。
可选的，所述处理器710还用于若传输所述第一DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第一DCI的DFI标志域指示为‘0’或者DFI标志域不存在，且所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活。
可选的，所述目标比特位置为以下之一：
所有比特位置；
指示有效物理上行共享信道PUSCH的位置；
前N个比特位置或者最后N个比特位置，N为大于或等于1的正整数。
可选的，所述第一DCI的NDI域中的有效PUSCH对应的比特位置由所述第一DCI调度的有效PUSCH的个数和所述NDI域中的每个PUSCH NDI的大小确定。
可选的，所述第一DCI的NDI域中的有效PUSCH对应的比特位置为所述NDI域中的最高或最低M’*a个比特，M’为所述第一DCI调度的有效PUSCH的个数，a为所述NDI域中的每个PUSCH NDI的大小。
可选的，所述第一DCI的RVI域中的有效PUSCH对应的比特位置由所述第一DCI调度的有效PUSCH的个数和所述RVI域中的每个PUSCH RVI的大小确定。
可选的，所述第一DCI的RVI域中的有效PUSCH对应的比特位置为所述RVI域中的最高或最低M’*b个比特，M’为所述第一DCI调度的有效PUSCH的个数，b为所述RVI域中的每个PUSCH RVI的大小。
可选的，所述目标比特位置指示非全‘1’包括所述目标比特位置中的一个位置为‘0’，其余为‘1’。
可选的，若所述第一指示域的所有比特位置均指示‘0’或者非全‘1’或者预设值，或者，所述第一指示域的有效PUSCH对应的比特位置均指示‘0’，所述处理器710，还用于确定激活的所述半静态传输所使用的起始和长度指示值SLIV为所述第一DCI的时域资源分配TDRA域中的有效SLIV中的预定义的SLIV。
可选的，若所述第一指示域的前N个比特位置或者最后N个比特位置指示‘0’，所述处理器710，还用于确定激活的所述半静态传输所使用的SLIV为所述第一DCI的TDRA域中的前N个比特位置或者最后N个比特位置的PUSCH对应的SLIV。
可选的，若所述第一指示域的有效PUSCH对应的比特位置指示非全‘1’，所述处理器710，还用于确定激活的所述半静态传输所使用的SLIV为所述第一DCI的TDRA域中的目标有效PUSCH对应的SLIV，所述目标有效PUSCH为所述第一指示域中的有效PUSCH对应的比特位置中指示‘0’的位置对应的有效PUSCH。
可选的，所述处理器710，还用于若所述第一DCI还满足以下条件中的至少一项，确定所述第一DCI用作半静态传输的去激活：
所述第一DCI的HARQ进程数量域指示全‘0’；
所述第一DCI的调制和编码方案MCS域指示全‘0’；
所述第一DCI的频域资源分配FDRA域指示为无效资源分配。
可选的，所述射频单元71，还用于接收第二DCI；
所述处理器710，还用于若传输所述第二DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第二DCI的DFI标志域指示为‘0’或者DFI标志域不存在，且所述第二DCI的NDI域中的有效PUSCH位置指示全‘1’，确定所述第二DCI用作半静态传输的调度重传。
可选的，所述半静态传输为SPS PDSCH传输或第二类型的配置授权PUSCH传输或半静态的CSI传输。
具体地，本申请实施例还提供了一种网络侧设备。如图8所示，该网络设备80包括：天线81、射频装置82、基带装置83。天线81与射频装置82连接。在上行方向上，射频装置82通过天线81接收信息，将接收的信息发送给基带装置83进行处理。在下行方向上，基带装置83对要发送的信息进行处理，并发送给射频装置82，射频装置82对收到的信息进行处理后经过天线81发送出去。
上述频带处理装置可以位于基带装置83中，以上实施例中网络侧设备执行的方法可以在基带装置83中实现，该基带装置83包括处理器84和存储器85。
基带装置83例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图8所示，其中一个芯片例如为处理器84，与存储器85连接，以调用存储器85中的程序，执行以上方法实施例中所示的网络设备操作。
该基带装置83还可以包括网络接口86，用于与射频装置82交互信息，该接口例如为通用公共无线接口(common public radio interface，简称CPRI)。
具体地，本发明实施例的网络侧设备还包括：存储在存储器85上并可在处理器84上运行的指令或程序，处理器84调用存储器85中的指令或程序执行图3所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不 在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述PDCCH的校验方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述PDCCH的发送方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络侧设备程序或指令，实现上述PDCCH的校验方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络侧设备程序或指令，实现上述PDCCH的发送方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种程序产品，所述程序产品存储在非易失的存储介质中，所述程序产品被至少一个处理器执行以实现上述PDCCH的验证方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例另提供了一种程序产品，所述程序产品存储在非易失的存储介质中，所述程序产品被至少一个处理器执行以实现上述PDCCH的发送方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
可以理解的是，本公开描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，模块、单元、子模块、子单元等可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processing，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本申请所述功能的其它电子单元或其组合中。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (28)

  1. 一种物理下行控制信道PDCCH的校验方法，应用于终端，包括：
    接收第一下行控制信息DCI；
    若所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活，所述第一指示域对应多个物理上行共享信道PUSCH，所述第一指示域包括新数据指示NDI域和冗余版本指示RVI域中的至少一项。
  2. 根据权利要求1所述的方法，其中，若所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活包括：
    若传输所述第一DCI的PDCCH由配置调度无线网络临时标识CS-RNTI或半静态调度信道状态信息无线网络临时标识SP-CSI-RNTI加扰，所述第一DCI的深度流检测DFI标志域指示为‘0’或者DFI标志域不存在，且所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活。
  3. 根据权利要求1或2所述的方法，其中，所述目标比特位置为以下之一：
    所有比特位置；
    有效PUSCH对应的比特位置；
    前N个比特位置或者最后N个比特位置，N为大于或等于1的正整数。
  4. 根据权利要求3所述的方法，其中，所述第一DCI的NDI域中的有效PUSCH对应的比特位置为所述NDI域中的最高或最低M’*a个比特，M’为所述第一DCI调度的有效PUSCH的个数，a为所述NDI域中的每个PUSCH NDI的大小。
  5. 根据权利要求3所述的方法，其中，所述第一DCI的RVI域中的有效PUSCH对应的比特位置为所述RVI域中的最高或最低M’*b个比特，M’为所述第一DCI调度的有效PUSCH的个数，b为所述RVI域中的每个PUSCH RVI的大小。
  6. 根据权利要求1或2所述的方法，其中，所述目标比特位置指示非全‘1’包括所述目标比特位置中的一个位置为‘0’，其余为‘1’。
  7. 根据权利要求3所述的方法，其中，若所述第一指示域的所有比特位置均指示‘0’或者非全‘1’或者预设值，或者，所述第一指示域的有效PUSCH对应的比特位置均指示‘0’，确定所述第一DCI用作半静态传输的激活或去激活之后，所述方法还包括：
    确定激活的所述半静态传输所使用的起始和长度指示值SLIV为所述第一DCI的时域资源分配TDRA域中的有效SLIV中的预定义的SLIV。
  8. 根据权利要求3所述的方法，其中，若所述第一指示域的前N个比特位置或者最后N个比特位置指示‘0’，确定所述第一DCI用作半静态传输的激活或去激活之后，所述方法还包括：
    确定激活的所述半静态传输所使用的SLIV为所述第一DCI的TDRA域中的所述前N个比特位置或者最后N个比特位置的PUSCH对应的SLIV。
  9. 根据权利要求3所述的方法，其中，若所述第一指示域的有效PUSCH对应的比特位置指示非全‘1’，确定所述第一DCI用作半静态传输的激活或去激活之后，所述方法还包括：
    确定激活的所述半静态传输所使用的SLIV为所述第一DCI的TDRA域中的目标有效PUSCH对应的SLIV，所述目标有效PUSCH为所述第一指示域中的有效PUSCH对应的比特位置中指示‘0’的位置对应的有效PUSCH。
  10. 根据权利要求1或2所述的方法，其中，确定所述第一DCI用作半静态传输的激活或去激活之后，所述方法还包括：
    若所述第一DCI还满足以下条件中的至少一项，确定所述第一DCI用作半静态传输的去激活：
    所述第一DCI的HARQ进程数量域指示全‘0’；
    所述第一DCI的调制和编码方案MCS域指示全‘0’；
    所述第一DCI的频域资源分配FDRA域指示为无效资源分配。
  11. 根据权利要求1所述的方法，还包括：
    接收第二DCI；
    若传输所述第二DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述 第二DCI的DFI标志域指示为‘0’或者DFI标志域不存在，且所述第二DCI的NDI域中的有效PUSCH位置指示全‘1’，确定所述第二DCI用作半静态传输的调度重传。
  12. 根据权利要求1或11所述的方法，其中，所述半静态传输为半静态调度物理下行共享信道SPS PDSCH传输或第二类型的配置授权PUSCH传输或半静态的CSI传输。
  13. 一种PDCCH的校验装置，包括：
    第一接收模块，用于接收第一DCI；
    第一校验模块，用于若所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，确定所述第一DCI用作半静态传输的激活或去激活，所述第一指示域对应多个PUSCH，所述第一指示域包括NDI域和RVI域中的至少一项。
  14. 一种PDCCH的发送方法，应用于网络侧设备，包括：
    传输用作半静态传输的激活或去激活的第一DCI，其中，所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，所述第一指示域包括NDI域和RVI域中的至少一项。
  15. 根据权利要求14所述的PDCCH的发送方法，其中，传输所述第一DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第一DCI的DFI标志域指示为‘0’或者DFI标志域不存在。
  16. 根据权利要求14或15所述的PDCCH的发送方法，其中，所述目标比特位置为以下之一：
    所有比特位置；
    有效PUSCH对应的比特位置；
    前N个比特位置或者最后N个比特位置，N为大于或等于1的正整数。
  17. 根据权利要求16所述的方法，其中，所述第一DCI的NDI域中的有效PUSCH对应的比特位置为所述NDI域中的最高或最低M’*a个比特，M’为所述第一DCI调度的有效PUSCH的个数，a为所述NDI域中的每个PUSCH NDI的大小。
  18. 根据权利要求16所述的方法，其中，所述第一DCI的RVI域中的有 效PUSCH对应的比特位置为所述RVI域中的最高或最低M’*b个比特，M’为所述第一DCI调度的有效PUSCH的个数，b为所述RVI域中的每个PUSCH RVI的大小。
  19. 根据权利要求14或15所述的方法，其中，所述目标比特位置指示非全‘1’包括所述目标比特位置中的一个位置为‘0’，其余为‘1’。
  20. 根据权利要求14或15所述的方法，其中，若所述第一DCI用作半静态传输的去激活，所述第一DCI还满足以下条件中的至少一项：
    所述第一DCI的HARQ进程数量域指示全‘0’；
    所述第一DCI的调制和编码方案MCS域指示全‘0’；
    所述第一DCI的频域资源分配FDRA域指示为无效资源分配。
  21. 根据权利要求14所述的方法，还包括：
    传输用作半静态传输的调度重传的第二DCI，传输所述第二DCI的PDCCH由CS-RNTI或SP-CSI-RNTI加扰，所述第二DCI的DFI标志域指示为‘0’或者DFI标志域不存在，且所述第二DCI的NDI域中的有效PUSCH位置指示全‘1’。
  22. 根据权利要求14或21所述的方法，其中，所述半静态传输为SPS PDSCH传输或第二类型的配置授权PUSCH传输或半静态的CSI传输。
  23. 一种PDCCH的传输装置，包括：
    第一发送模块，用于传输用作半静态传输的激活或去激活的第一DCI，其中，所述第一DCI的第一指示域的目标比特位置指示‘0’或者非全‘1’或者预设值，所述第一指示域包括NDI域和RVI域中的至少一项。
  24. 一种终端，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至12任一项所述的PDCCH的校验方法的步骤。
  25. 一种网络侧设备，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求14至22任一项所述的PDCCH的发送方法的步骤。
  26. 一种可读存储介质，其中，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1-12任一项所述的PDCCH 的校验方法，或者实现如权利要求14至22任一项所述的PDCCH的发送方法的步骤。
  27. 一种芯片，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如权利要求1-12任一项所述的PDCCH的校验方法，或者实现如权利要求14至22任一项所述的PDCCH的发送方法。
  28. 一种程序产品，其中，所述程序产品存储在非易失的存储介质中，所述程序产品被至少一个处理器执行以实现如权利要求1-12任一项所述的PDCCH的校验方法，或者实现如权利要求14至22任一项所述的PDCCH的发送方法。
PCT/CN2021/107269 2020-07-21 2021-07-20 Pdcch的校验方法、发送方法、终端及网络侧设备 Ceased WO2022017354A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010708044.5 2020-07-21
CN202010708044.5A CN113965999B (zh) 2020-07-21 2020-07-21 Pdcch的校验方法、发送方法、终端及网络侧设备

Publications (1)

Publication Number Publication Date
WO2022017354A1 true WO2022017354A1 (zh) 2022-01-27

Family

ID=79460084

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/107269 Ceased WO2022017354A1 (zh) 2020-07-21 2021-07-20 Pdcch的校验方法、发送方法、终端及网络侧设备

Country Status (2)

Country Link
CN (1) CN113965999B (zh)
WO (1) WO2022017354A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116391430A (zh) * 2023-02-16 2023-07-04 北京小米移动软件有限公司 一种传输配置信息的方法、装置以及可读存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7765648B2 (ja) * 2022-02-10 2025-11-06 １Ｆｉｎｉｔｙ株式会社 データ送信方法、データ受信方法及び装置
WO2024207426A1 (en) * 2023-04-07 2024-10-10 Qualcomm Incorporated Activation indication for multiple physical uplink shared channel configured grant
CN121056937A (zh) * 2024-05-31 2025-12-02 华为技术有限公司 一种码块校验方法及相关装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019028890A1 (zh) * 2017-08-11 2019-02-14 Oppo广东移动通信有限公司 半静态调度的处理方法、通信设备及存储介质
WO2019138360A1 (en) * 2018-01-12 2019-07-18 Telefonaktiebolaget Lm Ericsson (Publ) Activation and deactivation of semi-persistent csi reporting
WO2020032695A1 (en) * 2018-08-09 2020-02-13 Samsung Electronics Co., Ltd. Method and apparatus for scheduling multiple transmission in a wireless communication system
CN110944398A (zh) * 2019-11-07 2020-03-31 北京展讯高科通信技术有限公司 资源处理方法及相关设备
CN110971355A (zh) * 2018-09-28 2020-04-07 华为技术有限公司 上行免动态授权传输的配置方法及通信装置
EP3820224A1 (en) * 2019-11-07 2021-05-12 Comcast Cable Communications LLC Wireless communications for scheduling transmissions

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020033785A1 (en) * 2018-08-10 2020-02-13 Intel Corporation Physical uplink shared channel enhancements for new radio ultra-reliable low-latency communication
CN110536460A (zh) * 2018-09-28 2019-12-03 中兴通讯股份有限公司 Sps激活或去激活方法、装置、通信设备及存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019028890A1 (zh) * 2017-08-11 2019-02-14 Oppo广东移动通信有限公司 半静态调度的处理方法、通信设备及存储介质
WO2019138360A1 (en) * 2018-01-12 2019-07-18 Telefonaktiebolaget Lm Ericsson (Publ) Activation and deactivation of semi-persistent csi reporting
WO2020032695A1 (en) * 2018-08-09 2020-02-13 Samsung Electronics Co., Ltd. Method and apparatus for scheduling multiple transmission in a wireless communication system
CN110971355A (zh) * 2018-09-28 2020-04-07 华为技术有限公司 上行免动态授权传输的配置方法及通信装置
CN110944398A (zh) * 2019-11-07 2020-03-31 北京展讯高科通信技术有限公司 资源处理方法及相关设备
EP3820224A1 (en) * 2019-11-07 2021-05-12 Comcast Cable Communications LLC Wireless communications for scheduling transmissions

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
NTT DOCOMO, INC: "Maintenance for DL/UL data scheduling and HARQ procedure", 3GPP TSG RAN WG1 MEETING #94BIS; R1-1811375, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 29 September 2018 (2018-09-29), Chengdu, China,, pages 1 - 15, XP051518779 *
VIVO: "Remaining issues on enhancements to configured grant", 3GPP TSG RAN WG1 MEETING #102E; R1-2005336, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 8 August 2020 (2020-08-08), -Meeting; 20200817 - 20200828, XP051917362 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116391430A (zh) * 2023-02-16 2023-07-04 北京小米移动软件有限公司 一种传输配置信息的方法、装置以及可读存储介质

Also Published As

Publication number Publication date
CN113965999B (zh) 2025-07-15
CN113965999A (zh) 2022-01-21

Similar Documents

Publication Publication Date Title
CN114765863B (zh) 传输处理方法及相关设备
WO2022017354A1 (zh) Pdcch的校验方法、发送方法、终端及网络侧设备
CN114585099B (zh) Pusch的调度传输方法、终端和网络侧设备
CN115333694A (zh) Csi测量资源的处理方法及装置、终端及可读存储介质
CN114071747B (zh) 信息确定方法、信息发送方法及终端
WO2022206997A1 (zh) 功率控制参数指示方法、终端及网络侧设备
CN114071767B (zh) Sps pdsch的类型指示方法、装置、终端及网络侧设备
WO2022148389A1 (zh) 编码调制符号数的确定方法、装置及通信设备
CN113939036B (zh) 信道监听、传输方法、终端及网络侧设备
WO2022063072A1 (zh) 上行信道传输方法、装置及终端
CN116367312A (zh) 传输确定方法、装置、终端、网络侧设备和存储介质
WO2022017409A1 (zh) 上行传输方法、装置及相关设备
WO2022228341A1 (zh) 上行信道的传输参数方法、终端及网络侧设备
WO2022028464A1 (zh) 资源调度方法、装置及设备
CN115442004B (zh) 上行数据传输方法、装置、终端及介质
WO2022002250A1 (zh) Pdcch监听方法、发送方法及相关设备
CN114374955A (zh) 传输方法、优先级定义方法、装置及通信设备
CN113839728B (zh) Dci检测方法、发送方法及相关设备
WO2022002259A1 (zh) 旁链路传输方法、传输装置和终端
WO2018082546A1 (zh) 下行控制信道的检测方法、发送方法、网络侧设备及终端
CN114650120B (zh) 信息确定方法、装置及通信设备
EP4178141A1 (en) Sidelink transmission method and transmission apparatus, and communication device
WO2022007951A1 (zh) 资源传输方法、装置及通信设备
WO2022033424A1 (zh) 资源传输方法、装置及通信设备
WO2022143494A1 (zh) 物理下行共享信道资源配置方法、装置、设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21845507

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21845507

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 21845507

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC ( EPO FORM 1205A DATED 01/08/2023 )

122 Ep: pct application non-entry in european phase

Ref document number: 21845507

Country of ref document: EP

Kind code of ref document: A1