[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

CN110035542B - Method and device for activating or releasing semi-persistent scheduling or scheduling-free data transmission and user equipment - Google Patents

Method and device for activating or releasing semi-persistent scheduling or scheduling-free data transmission and user equipment Download PDF

Info

Publication number
CN110035542B
CN110035542B CN201810026977.9A CN201810026977A CN110035542B CN 110035542 B CN110035542 B CN 110035542B CN 201810026977 A CN201810026977 A CN 201810026977A CN 110035542 B CN110035542 B CN 110035542B
Authority
CN
China
Prior art keywords
scheduling
dci format
release
pusch
dci
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.)
Active
Application number
CN201810026977.9A
Other languages
Chinese (zh)
Other versions
CN110035542A (en
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.)
Beijing Ziguang Zhanrui Communication Technology Co Ltd
Original Assignee
Beijing Ziguang Zhanrui Communication Technology 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 Beijing Ziguang Zhanrui Communication Technology Co Ltd filed Critical Beijing Ziguang Zhanrui Communication Technology Co Ltd
Priority to CN201810026977.9A priority Critical patent/CN110035542B/en
Publication of CN110035542A publication Critical patent/CN110035542A/en
Application granted granted Critical
Publication of CN110035542B publication Critical patent/CN110035542B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0061—Error detection codes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • 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 signaling, i.e. of overhead other than pilot signals
    • 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

Landscapes

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

Abstract

The invention provides a method and a device for activating or releasing semi-persistent scheduling or scheduling-free data transmission and user equipment. The method comprises the following steps: receiving DCI issued by a base station; when the DCI is a first DCI format for scheduling the PDSCH, determining whether to activate downlink semi-persistent scheduling according to the first DCI format for scheduling the PDSCH; when the DCI is a second DCI format for scheduling the PDSCH, determining whether to release downlink semi-persistent scheduling according to the second DCI format for scheduling the PDSCH; when the DCI is a first DCI format of a scheduling PUSCH, determining whether to activate an uplink scheduling-free type 2 according to the first DCI format of the scheduling PUSCH; and when the DCI is a second DCI format of a scheduling PUSCH, determining whether to release the uplink scheduling-free type 2 according to the second DCI format of the scheduling PUSCH. The invention can determine whether to activate or release the downlink semi-persistent scheduling or activate or release the uplink non-scheduling type 2 according to the received DCI.

Description

Method and device for activating or releasing semi-persistent scheduling or scheduling-free data transmission and user equipment
Technical Field
The present invention relates to the field of wireless communications technologies, and in particular, to a method and an apparatus for activating or releasing semi-persistent scheduling or scheduling-free data transmission, and a user equipment.
Background
Semi-persistent scheduling in LTE (Long Term Evolution) refers to semi-statically configuring radio resources and periodically allocating the resources to a specific UE (User Equipment). A PDCCH (Physical Downlink Control Channel) scrambled with SPS (Semi-Persistent Scheduling) C-RNTI (Cell Radio Network Temporary Identifier) specifies a Radio resource (referred to as SPS resource herein) used by the UE, and the UE uses the SPS resource to transmit or receive data every one period. The eNodeB (base station) does not need to re-issue the PDCCH in this subframe (referred to herein as an SPS subframe) to specify the allocated resources, reducing the corresponding PDCCH overhead. After the UE is configured with SPS, the UE cannot be used, and the PDCCH scrambled by the SPS C-RNTI must be used for activation. The eNodeB activates/releases the SPS of the UE through the PDCCH scrambled by the SPS C-RNTI. The UE will verify whether the received PDCCH is used for SPS activation or release only if the following conditions are met:
CRC (Cyclic Redundancy Check) Check bits of the PDCCH are scrambled by using the SPS C-RNTI;
the NDI (New Data indicator) field is set to 0. For the DCI (Downlink Control Information) format 2/2a/2B/2C, the NDI field is for the TB (Transport Block) that is enabled.
As shown in table 1, a special field for PDCCH validation is activated for semi-persistent scheduling; as shown in table 2, the special field of PDCCH validation is released for semi-persistent scheduling.
TABLE 1
Figure BDA0001545235020000021
TABLE 2
Figure BDA0001545235020000022
If all fields in the corresponding DCI format are set as shown in Table 1or Table 2, the verification is successful, otherwise, the verification fails. If the verification is successful, the UE treats the received DCI as a valid SPS activation/release; if the verification fails, the UE may consider the received DCI to use a non-matching CRC.
The NR (New Radio, New air interface) includes downlink semi-persistent scheduling and uplink non-scheduling type 2(type 2grant free PUSCH), which may be used as they are also required to be activated by DCI, or may require the DCI to release resources for downlink semi-persistent scheduling or non-scheduling type 2 uplink transmission. SPS C-RNTI is adopted for downlink semi-persistent scheduling configured by high-level signaling, and CS-RNTI is adopted for uplink transmission configured with scheduling-free type 2. The DCI format for scheduling a PDSCH (Physical Downlink Shared Channel) includes DCI1_0 and DCI1_1, and the DCI format for scheduling a PUSCH (Physical Uplink Shared Channel) includes DCI0_0 and DCI0_ 1.
Currently, the UE cannot determine whether to activate or release downlink semi-persistent scheduling or activate or release uplink non-scheduling type 2 according to the received DCI.
Disclosure of Invention
The activation or release semi-persistent scheduling or scheduling-free data transmission method, the activation or release semi-persistent scheduling or scheduling-free data transmission device and the user equipment can determine whether to activate or release downlink semi-persistent scheduling or activate or release uplink scheduling-free type 2 according to the received DCI.
In a first aspect, the present invention provides an activation or release method for semi-persistent scheduling or scheduling-free data transmission, including:
receiving DCI issued by a base station;
when the DCI is a first DCI format for scheduling the PDSCH, determining whether to activate downlink semi-persistent scheduling according to the first DCI format for scheduling the PDSCH;
when the DCI is a second DCI format for scheduling the PDSCH, determining whether to release downlink semi-persistent scheduling according to the second DCI format for scheduling the PDSCH;
when the DCI is a first DCI format of a scheduling PUSCH, determining whether to activate an uplink scheduling-free type 2 according to the first DCI format of the scheduling PUSCH;
and when the DCI is a second DCI format of the scheduling PUSCH, determining whether to release the uplink scheduling-free type 2 according to the second DCI format of the scheduling PUSCH.
Optionally, the determining whether to activate downlink semi-persistent scheduling according to the first DCI format of the scheduled PDSCH includes: determining whether to activate downlink semi-persistent scheduling according to the number of HARQ processes in the first DCI format of the scheduling PDSCH and a redundancy version field;
the determining whether to release downlink semi-persistent scheduling according to the second DCI format for scheduling the PDSCH includes: determining whether to release downlink semi-persistent scheduling according to the number of HARQ processes in the second DCI format of the scheduling PDSCH and a redundancy version field;
the determining whether to activate an uplink scheduling-free type 2 according to the first DCI format for scheduling the PUSCH includes: determining whether to activate an uplink scheduling-free type 2 according to the number of HARQ processes in the first DCI format of the scheduling PUSCH and a redundancy version field;
the determining whether to release the uplink scheduling-free type 2 according to the second DCI format of the scheduled PUSCH includes: and determining whether to release the uplink scheduling-free type 2 according to the number of HARQ processes in the second DCI format of the scheduling PUSCH and the redundancy version field.
Optionally, the determining whether to activate downlink semi-persistent scheduling according to the first DCI format of the scheduled PDSCH includes: determining whether to activate downlink semi-persistent scheduling according to the number of HARQ processes in the first DCI format for scheduling the PDSCH and a TPC command for scheduling the PUCCH;
the determining whether to release downlink semi-persistent scheduling according to the second DCI format of the scheduled PDSCH includes: determining whether to release downlink semi-persistent scheduling according to the number of HARQ processes in the second DCI format for scheduling the PDSCH and a TPC command for scheduling the PUCCH;
the determining whether to activate uplink non-scheduling type 2 according to the first DCI format of the scheduled PUSCH includes: determining whether to activate an uplink scheduling-free type 2 according to the number of HARQ processes in the first DCI format for scheduling the PUSCH and a TPC command for scheduling the PUSCH;
the determining whether to release the uplink scheduling-free type 2 according to the second DCI format of the scheduled PUSCH includes: and determining whether to release the uplink scheduling-free type 2 according to the number of HARQ processes in the second DCI format for scheduling the PUSCH and the TPC command for scheduling the PUSCH.
Optionally, the determining whether to activate downlink semi-persistent scheduling according to the first DCI format for scheduling the PDSCH includes: determining whether to activate downlink semi-persistent scheduling according to the number of HARQ processes in the first DCI format of the scheduled PDSCH and a downlink allocation index field;
the determining whether to release downlink semi-persistent scheduling according to the second DCI format of the scheduled PDSCH includes: determining whether to release downlink semi-persistent scheduling according to the number of HARQ processes in the second DCI format of the scheduled PDSCH and a downlink allocation index field;
the determining whether to activate an uplink scheduling-free type 2 according to the first DCI format for scheduling the PUSCH includes: determining whether to activate an uplink scheduling-free type 2 according to the number of HARQ processes in the first DCI format for scheduling the PUSCH and a downlink allocation index field;
the determining whether to release the uplink scheduling-free type 2 according to the second DCI format of the scheduled PUSCH includes: and determining whether to release the uplink scheduling-free type 2 according to the number of HARQ processes in the second DCI format for scheduling the PUSCH and the downlink allocation index field.
Optionally, the determining whether to activate downlink semi-persistent scheduling according to the first DCI format of the scheduled PDSCH includes: determining whether to activate downlink semi-persistent scheduling according to a downlink allocation index field and a redundancy version field in a first DCI format of the scheduled PDSCH;
the determining whether to release downlink semi-persistent scheduling according to the second DCI format of the scheduled PDSCH includes: determining whether to release downlink semi-persistent scheduling according to a downlink allocation index field and a redundancy version field in a second DCI format of the scheduled PDSCH;
the determining whether to activate uplink non-scheduling type 2 according to the first DCI format of the scheduled PUSCH includes: determining whether to activate an uplink scheduling-free type 2 according to a downlink allocation index field and a redundancy version field in a first DCI format of the scheduling PUSCH;
the determining whether to release the uplink scheduling-free type 2 according to the second DCI format of the scheduled PUSCH includes: and determining whether to release the uplink scheduling-free type 2 according to a downlink allocation index field and a redundancy version field in a second DCI format of the scheduling PUSCH.
Optionally, the determining whether to activate downlink semi-persistent scheduling according to the first DCI format of the scheduled PDSCH includes: determining whether to activate downlink semi-persistent scheduling according to a downlink allocation index field in a first DCI format of the scheduled PDSCH and a TPC command of the scheduled PUCCH;
the determining whether to release downlink semi-persistent scheduling according to the second DCI format for scheduling the PDSCH includes: determining whether to release downlink semi-persistent scheduling according to a downlink allocation index field in a second DCI format of the scheduling PDSCH and a TPC command of the scheduling PUCCH;
the determining whether to activate uplink non-scheduling type 2 according to the first DCI format of the scheduled PUSCH includes: determining whether to activate an uplink scheduling-free type 2 according to a downlink allocation index field in a first DCI format of the scheduling PUSCH and a TPC command of the scheduling PUSCH;
the determining whether to release the uplink scheduling-free type 2 according to the second DCI format for scheduling the PUSCH includes: and determining whether to release the uplink scheduling-free type 2 according to the downlink allocation index field in the second DCI format of the scheduling PUSCH and the TPC command of the scheduling PUSCH.
Optionally, the determining whether to activate downlink semi-persistent scheduling according to the first DCI format of the scheduled PDSCH includes: determining whether to activate downlink semi-persistent scheduling according to a redundancy version field in a first DCI format of the scheduling PDSCH and a TPC command of the scheduling PUCCH;
the determining whether to release downlink semi-persistent scheduling according to the second DCI format of the scheduled PDSCH includes: determining whether to release downlink semi-persistent scheduling according to a redundancy version field in a second DCI format of the scheduling PDSCH and a TPC command of the scheduling PUCCH;
the determining whether to activate uplink non-scheduling type 2 according to the first DCI format of the scheduled PUSCH includes: determining whether to activate an uplink scheduling-free type 2 according to a redundancy version field in the first DCI format of the scheduling PUSCH and a TPC command of the scheduling PUSCH;
the determining whether to release the uplink scheduling-free type 2 according to the second DCI format of the scheduled PUSCH includes: and determining whether to release the uplink scheduling-free type 2 according to the redundancy version field in the second DCI format of the scheduling PUSCH and the TPC command of the scheduling PUSCH.
Optionally, the method further comprises:
judging whether CRC check bits of the PDCCH are scrambled by using SPS C-RNTI or CS-RNTI;
when the CRC check bit of the PDCCH is scrambled by using the SPS C-RNTI, determining whether to activate or release downlink semi-persistent scheduling;
and when the CRC check bit of the PDCCH is scrambled by using the CS-RNTI, determining whether to activate or release the uplink exemption scheduling type 2.
In a second aspect, the present invention provides an apparatus for activating or releasing semi-persistent scheduling or scheduling-free data transmission, comprising:
a receiving unit, configured to receive DCI issued by a base station;
a first determining unit, configured to determine whether to activate downlink semi-persistent scheduling according to a first DCI format of a scheduled PDSCH when the DCI is the first DCI format of the scheduled PDSCH;
a second determining unit, configured to determine whether to release downlink semi-persistent scheduling according to a second DCI format of a scheduled PDSCH when the DCI is the second DCI format of the scheduled PDSCH;
a third determining unit, configured to determine, when the DCI is the first DCI format of the scheduled PUSCH, whether to activate uplink non-scheduling type 2 according to the first DCI format of the scheduled PUSCH;
and a fourth determining unit, configured to determine whether to release the uplink scheduling-free type 2 according to the second DCI format of the scheduled PUSCH when the DCI is the second DCI format of the scheduled PUSCH.
Optionally, the first determining unit is configured to determine whether to activate downlink semi-persistent scheduling according to the number of HARQ processes in the first DCI format for scheduling the PDSCH and a redundancy version field;
the second determining unit is configured to determine whether to release downlink semi-persistent scheduling according to the number of HARQ processes in the second DCI format of the scheduled PDSCH and the redundancy version field;
the third determining unit is configured to determine whether to activate an uplink scheduling-free type 2 according to the number of HARQ processes in the first DCI format for scheduling the PUSCH and a redundancy version field;
the fourth determining unit is configured to determine whether to release the uplink scheduling-free type 2 according to the number of HARQ processes in the second DCI format for scheduling the PUSCH and the redundancy version field.
Optionally, the first determining unit is configured to determine whether to activate downlink semi-persistent scheduling according to the number of HARQ processes in the first DCI format for scheduling the PDSCH and a TPC command for scheduling the PUCCH;
the second determining unit is configured to determine whether to release downlink semi-persistent scheduling according to the number of HARQ processes in the second DCI format for scheduling the PDSCH and the TPC command for scheduling the PUCCH;
the third determining unit is configured to determine whether to activate uplink scheduling-free type 2 according to the number of HARQ processes in the first DCI format for scheduling the PUSCH and the TPC command for scheduling the PUSCH;
and the fourth determining unit is configured to determine whether to release the uplink scheduling-free type 2 according to the number of HARQ processes in the second DCI format for scheduling the PUSCH and the TPC command for scheduling the PUSCH.
Optionally, the first determining unit is configured to determine whether to activate downlink semi-persistent scheduling according to the number of HARQ processes in the first DCI format for scheduling the PDSCH and a downlink allocation index field;
the second determining unit is configured to determine whether to release downlink semi-persistent scheduling according to the number of HARQ processes in the second DCI format for scheduling the PDSCH and the downlink allocation index field;
the third determining unit is configured to determine whether to activate uplink non-scheduling type 2 according to the number of HARQ processes in the first DCI format for scheduling PUSCH and the downlink allocation index field;
and the fourth determining unit is configured to determine whether to release the uplink scheduling-free type 2 according to the number of HARQ processes in the second DCI format for scheduling the PUSCH and the downlink allocation index field.
Optionally, the first determining unit is configured to determine whether to activate downlink semi-persistent scheduling according to a downlink allocation index field and a redundancy version field in a first DCI format for scheduling the PDSCH;
the second determining unit is configured to determine whether to release downlink semi-persistent scheduling according to a downlink allocation index field and a redundancy version field in a second DCI format of the scheduled PDSCH;
the third determining unit is configured to determine whether to activate an uplink scheduling-free type 2 according to a downlink allocation index field and a redundancy version field in the first DCI format of the scheduled PUSCH;
and the fourth determining unit is configured to determine whether to release the uplink scheduling-free type 2 according to the downlink allocation index field and the redundancy version field in the second DCI format for scheduling the PUSCH.
Optionally, the first determining unit is configured to determine whether to activate downlink semi-persistent scheduling according to a downlink allocation index field in a first DCI format of the scheduled PDSCH and a TPC command of a scheduled PUCCH;
the second determining unit is configured to determine whether to release downlink semi-persistent scheduling according to a downlink allocation index field in a second DCI format of the scheduled PDSCH and a TPC command of the scheduled PUCCH;
the third determining unit is configured to determine whether to activate an uplink scheduling-free type 2 according to a downlink assignment index field in the first DCI format for scheduling the PUSCH and a TPC command for scheduling the PUSCH;
and the fourth determining unit is configured to determine whether to release the uplink scheduling-free type 2 according to the downlink allocation index field in the second DCI format for scheduling the PUSCH and the TPC command for scheduling the PUSCH.
Optionally, the first determining unit is configured to determine whether to activate downlink semi-persistent scheduling according to a redundancy version field in a first DCI format of the scheduled PDSCH and a TPC command of a scheduled PUCCH;
the second determining unit is configured to determine whether to release downlink semi-persistent scheduling according to a redundancy version field in a second DCI format of the scheduled PDSCH and a TPC command of the scheduled PUCCH;
the third determining unit is configured to determine whether to activate an uplink scheduling-free type 2 according to a redundancy version field in the first DCI format of the scheduling PUSCH and the TPC command of the scheduling PUSCH;
and the fourth determining unit is configured to determine whether to release the uplink scheduling-free type 2 according to the redundancy version field in the second DCI format for scheduling the PUSCH and the TPC command for scheduling the PUSCH.
Optionally, the apparatus further comprises:
the judging unit is used for judging whether CRC check bits of the PDCCH are scrambled by using SPS C-RNTI or scrambled by using CS-RNTI;
the first determining unit is configured to determine whether to activate downlink semi-persistent scheduling when a CRC check bit of the PDCCH is scrambled using SPS C-RNTI;
the second determining unit is configured to determine whether to release downlink semi-persistent scheduling when the CRC check bits of the PDCCH are scrambled using SPS C-RNTI;
the third determining unit is configured to determine whether to activate uplink scheduling-free type 2 when the CRC check bits of the PDCCH are scrambled using the CS-RNTI;
the fourth determining unit is configured to determine whether to release the uplink scheduling-exempt type 2 when the CRC check bits of the PDCCH are scrambled using the CS-RNTI.
In a third aspect, the present invention provides a user equipment, where the user equipment includes the above-mentioned activated or released semi-persistent scheduling or scheduling-free data transmission apparatus.
According to the method, the device and the user equipment for transmitting the activation or release semi-persistent scheduling or scheduling-free data, whether downlink semi-persistent scheduling is activated or released is determined according to the received first DCI format or the received second DCI format of the scheduling PDSCH, and whether uplink scheduling-free type 2 is activated or released is determined according to the received first DCI format or the received second DCI format of the scheduling PUSCH, so that whether downlink semi-persistent scheduling is to be activated or released or the uplink scheduling-free type 2 is to be activated or released can be determined according to the received DCI format.
Drawings
FIG. 1 is a flowchart illustrating a method for activating or deactivating semi-persistent scheduling or scheduling-free data transmission according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of an apparatus for activating or releasing semi-persistent scheduling or scheduling-free data transmission according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
First, DCI format DCI1_0 and DCI1_1 for scheduling PDSCH and DCI format DCI0_0 and DCI0_1 for scheduling PUSCH are introduced.
(1) DCI1_0 contains the following information:
DCI format identification (Identifier for DCI formats) - [1] bits
Frequency domain resource allocation
Figure BDA0001545235020000111
Figure BDA0001545235020000112
Time domain resource allocation (Time domain resource allocation) -X bits
VRB-to-PRB mapping (VRB-to-PRB mapping) -1 bit
Modulation and coding scheme (5 bits)
New data indicator (New data indicator) -1 bit
Redundancy version (Redundancy version) - [2] bits
Number of HARQ processes (HARQ process number) - [4] bits
Downlink assignment index (Downlink assignment index) -2 bits
TPC command (TPC command for scheduled PUCCH) - [2] bits for scheduling PUCCH
PUCCH resource indicator (PUCCH resource indicator) - [2] bits
PDSCH-to-HARQ _ feedback timing indicator (PDSCH-to-HARQ _ feedback timing indicator) - [3] bits
(2) DCI1_1 contains the following information:
carrier indicator-0 or 3bits.
DCI format identification (Identifier for DCI formats) - [1] bits
Partial Bandwidth indicator (Bandwidth part indicator) -0, 1or 2bits
Frequency domain resource allocation (Frequency domain resource assignment) -if only resource allocation type 0 is configured
Figure BDA0001545235020000121
If only resource allocation type 1 is configured
Figure BDA0001545235020000122
If two resource allocations are configured
Figure BDA0001545235020000123
Time domain resource allocation (Time domain resource allocation) -1, 2,3, or 4bits
VRB-to-PRB mapping (VRB-to-PRB mapping) -0 or 1bit
PRB bundling size indicator (PRB bundling size indicator) -0 or 1bit
Rate matching indicator (Rate matching indicator) -0, 1, or 2bits
ZP CSI-RS trigger (ZP CSI-RS trigger) -X bits
Transmission block 1:
modulation and coding scheme (5 bits)
New data indicator (New data indicator) -1 bit
Redundancy version (Redundancy version) - [2] bits
And a transmission block 2:
modulation and coding scheme (5 bits)
New data indicator (New data indicator) -1 bit
Redundancy version (Redundancy version) - [2] bits
HARQ process number (HARQ process number) -4 bits
Downlink assignment index (Downlink assignment index) -0 or 4bits
TPC command (TPC command for scheduled PUCCH) - [2] bits for scheduling PUCCH
PUCCH resource indicator (PUCCH resource indicator) - [2] bits
PDSCH-to-HARQ feedback timing indicator (PDSCH-to-HARQ feedback timing indicator) -3 bits
Antenna port (Antenna ports) -4, 5, or 6bits
Transmission configuration indication (Transmission configuration indication) -0 bit or 3bits
SRS request (SRS request) -2 bits
CBG Transmission information (CBG Transmission information) -0, 2,4,6, or 8bits
CBG flushing out information-0 or 1bit.
DMRS sequence initialization (DMRS sequence initialization) -0 or 1bit
(3) DCI0_0 contains the following information:
DCI format identification (Identifier for DCI formats) - [1] bits
Frequency domain resource allocation
Figure BDA0001545235020000131
Figure BDA0001545235020000132
Time domain resource allocation (Time domain resource allocation) -X bits
Frequency domain hopping flag (Frequency hopping flag) -1 bit.
Modulation and coding scheme (5 bits)
New data indicator (New data indicator) -1 bit
Redundancy version (Redundancy version) - [2] bits
Number of HARQ processes (HARQ process number) - [4] bits
Downlink assignment index (Downlink assignment index) -2 bits
TPC command for scheduled PUSCH (TPC command for scheduled PUSCH) - [2] bits
UL/SUL indicator (UL/SUL indicator) -0 bit if the UE is not SUL-configured, otherwise 1bit
(4) DCI0_1 contains the following information:
carrier indicator-0 or 3bits.
DCI format identification (Identifier for DCI formats) - [1] bits
Partial Bandwidth indicator (Bandwidth part indicator) -0, 1or 2bits
Frequency domain resource allocation (Frequency domain resource assignment) -if only resource allocation type 0 is configured
Figure BDA0001545235020000141
Only resource allocation type 1 is configured
Figure BDA0001545235020000142
If two resource allocations are configured
Figure BDA0001545235020000143
Time domain resource allocation (Time domain resource allocation) -1, 2,3, or 4bits
VRB-to-PRB mapping (VRB-to-PRB mapping) -0 or 1bit
Frequency domain hopping flag (Frequency hopping flag) -0 or 1bit
Modulation and coding scheme (5 bits)
New data indicator (New data indicator) -1 bit
Redundancy version (Redundancy version) - [2] bits
Number of HARQ processes (HARQ process number) -4 bits
The first downlink assignment index (1st downlink assignment index) -1 or 2bits
The first downlink assignment index (2nd downlink assignment index) -0 or 2bits
TPC command (TPC command for scheduled PUSCH) - [2] bits for scheduling PUSCH
SRS resource indication
Figure BDA0001545235020000144
Precoding information and number of layers (layers) -0, 2,3,4,5,6bits
Antenna port (Antenna ports) -2, 3,4,5,6bits
SRS request (SRS request) -2 bits
CSI request (CSI request) -0, 1,2,3,4,5, or 6bits
CBG Transmission information (CBG Transmission information) -0, 2,4,6, or 8bits
PTRS-DMRS association-0 or 2bits
beta _ offset indicator-0 or 2bits
DMRS sequence initialization (DMRS sequence initialization) -0 or 1bit
UL/SUL indicator (UL/SUL indicator) -0 bit if the UE is not SUL-configured, otherwise 1bit.
An embodiment of the present invention provides a method for activating or releasing semi-persistent scheduling or scheduling-free data transmission, as shown in fig. 1, where the method includes:
and S11, receiving the DCI issued by the base station.
S12, when the DCI is the first DCI format of the scheduled PDSCH, determining whether to activate downlink semi-persistent scheduling according to the first DCI format of the scheduled PDSCH.
The first DCI format of the scheduled PDSCH is the DCI1_ 0.
S13, when the DCI is the second DCI format of the scheduled PDSCH, determining whether to release the downlink semi-persistent scheduling according to the second DCI format of the scheduled PDSCH.
Wherein a second DCI format, DCI1_1, of the scheduled PDSCH.
S14, when the DCI is the first DCI format of the scheduling PUSCH, determining whether to activate the uplink scheduling-free type 2 according to the first DCI format of the scheduling PUSCH.
Here, the DCI0_0, which is the first DCI format for the scheduled PUSCH.
S15, when the DCI is the second DCI format of the scheduling PUSCH, determining whether to release the uplink scheduling-free type 2 according to the second DCI format of the scheduling PUSCH.
Wherein, the second DCI format of the scheduled PUSCH is DCI0_ 1.
According to the method for transmitting the activation or release semi-persistent scheduling or scheduling-free data, whether downlink semi-persistent scheduling is activated or released is determined according to the first DCI format or the second DCI format of the received scheduling PDSCH, and whether uplink scheduling-free type 2 is activated or released is determined according to the first DCI format or the second DCI format of the received scheduling PUSCH, so that whether downlink semi-persistent scheduling is to be activated or released or whether uplink scheduling-free type 2 is to be activated or released can be determined according to the received DCI format.
The method for activating or releasing semi-persistent scheduling or scheduling-free data transmission according to the present invention is described in detail with reference to specific embodiments.
Example 1
The base station adopts DCI format 1_0/DCI format 1_1 to activate or release downlink semi-persistent scheduling, adopts DCI format 0_0/DCI format 0_1 to activate or release uplink scheduling-free type 2, and uses different values of HARQ process number and redundancy version field in the corresponding format to represent activation or release.
The UE determines whether to activate or release downlink semi-persistent scheduling or whether to activate or release uplink non-scheduling type 2 according to the number of HARQ processes and the redundancy version field in the corresponding format of the received DCI.
When the CRC check bits of the PDCCH are scrambled using the SPS C-RNTI, the UE may verify whether the received PDCCH is used for activation or release of downlink SPS. When the CRC check bit of the PDCCH is scrambled by using the CS-RNTI, the UE can verify whether the received PDCCH is used for activating or releasing the uplink exemption scheduling type 2.
As shown in table 3, setting the number of HARQ processes of DCI format 1_0 to '0000' and setting the redundancy version to '00' indicates activating downlink semi-persistent scheduling;
the number of HARQ processes of DCI format 1_1 is '0000' and the redundancy version of the enabled transport block is '00', which indicates that downlink semi-persistent scheduling is activated;
the number of HARQ processes in DCI format 0_0 is '0000' and the redundancy version is '00', indicating that uplink scheduling-free type 2 is activated;
the number of HARQ processes of DCI format 0_1 is '0000' and the redundancy version is '00', which indicates that uplink non-scheduling type 2 is activated.
TABLE 3
Figure BDA0001545235020000171
As shown in table 4, the number of HARQ processes in DCI format 1_0 is '1111' and the redundancy version is '11', which indicates releasing downlink semi-persistent scheduling;
the number of HARQ processes of DCI format 1_1 is '1111' and the redundancy version of an enabled transport block is '11', indicating that downlink semi-persistent scheduling is released;
the number of the HARQ processes of DCI format 0_0 is '1111' and the redundancy version is '11', which indicates that the uplink scheduling-free type 2 is released;
the number of HARQ processes in DCI format 0_1 is set to '1111' and the redundancy version is set to '11', which indicates that the uplink non-scheduling type 2 is released.
TABLE 4
Figure BDA0001545235020000172
Example 2
And activating or releasing downlink semi-persistent scheduling by using DCI format 1_0/DCI format 1_1, activating or releasing uplink scheduling-free type 2 by using DCI format 0_0/DCI format 0_1, and representing activation or release by using the number of HARQ processes in the corresponding format and different values of TPC commands for scheduling PUSCH/TPC commands for scheduling PUCCH.
The UE determines whether to activate or release downlink semi-persistent scheduling or whether to activate or release uplink non-scheduling type 2 according to the number of HARQ processes in the corresponding format of the received DCI and the TPC command of the scheduling PUSCH/the TPC command of the scheduling PUCCH.
When the CRC check bits of the PDCCH are scrambled using the SPS C-RNTI, the UE may verify whether the received PDCCH is used for activation or release of downlink SPS. When the CRC check bits of the PDCCH are scrambled using the CS-RNTI, the UE will verify whether the received PDCCH is used for activation or release of uplink exempt scheduling type 2.
As shown in table 5, setting the number of HARQ processes of DCI format 1_0 to '0000' and setting the TPC command for scheduling PUCCH to '00' indicates to activate downlink semi-persistent scheduling;
the number of HARQ processes of DCI format 1_1 is '0000' and the TPC command for scheduling PUCCH is '00' to indicate that downlink semi-persistent scheduling is activated;
the number of HARQ processes of DCI format 0_0 is '0000' and the TPC command for scheduling PUSCH is '00', which indicates that uplink scheduling-free type 2 is activated;
the number of HARQ processes in DCI format 0_1 is '0000' and the TPC command for scheduling PUSCH is '00', which indicates that uplink non-scheduling type 2 is activated.
TABLE 5
Figure BDA0001545235020000181
Figure BDA0001545235020000191
As shown in table 6, the number of HARQ processes in DCI format 1_0 is set to '1111' and the TPC command for scheduling PUCCH is set to '11', which indicates release of downlink semi-persistent scheduling;
the number of HARQ processes in DCI format 1_1 is '1111' and the TPC command for scheduling PUCCH is '11' to indicate that the downlink semi-persistent scheduling is released;
the number of HARQ processes of DCI format 0_0 is '1111' and the TPC command for scheduling PUSCH is '11' to indicate that the uplink scheduling-free type 2 is released;
the number of HARQ processes in DCI format 0_1 is '1111' and the TPC command for scheduling PUSCH is '11', which indicates releasing uplink null scheduling type 2.
TABLE 6
Figure BDA0001545235020000192
Example 3
And activating or releasing downlink semi-persistent scheduling by using DCI format 1_0/DCI format 1_1, activating or releasing uplink scheduling-free type 2 by using DCI format 0_0/DCI format 0_1, and representing activation or release by using different values of HARQ process number and downlink allocation index field in corresponding formats.
The UE determines whether to activate or release downlink semi-persistent scheduling or whether to activate or release uplink non-scheduling type 2 according to the number of HARQ processes in the corresponding format of the received DCI and the downlink assignment index field.
When the CRC check bits of the PDCCH are scrambled using the SPS C-RNTI, the UE may verify whether the received PDCCH is used for activation or release of the downlink SPS. When the CRC check bit of the PDCCH is scrambled by using the CS-RNTI, the UE can verify whether the received PDCCH is used for activating or releasing the uplink exemption scheduling type 2.
As shown in table 7, the number of HARQ processes in DCI format 1_0 is '0000' and the downlink assignment index is '00', which indicates that downlink semi-persistent scheduling is activated;
the number of HARQ processes of DCI format 1_1 is '0000' and the downlink allocation index is '00' to indicate that downlink semi-persistent scheduling is activated;
the number of HARQ processes of DCI format 0_0 is '0000' and the downlink assignment index is '00', indicating that uplink non-scheduling type 2 is activated;
the number of HARQ processes of DCI format 0_1 is '0000' and the downlink assignment index is '00', which indicates that the uplink non-scheduling type 2 is activated.
TABLE 7
Figure BDA0001545235020000201
As shown in table 8, the number of HARQ processes in DCI format 1_0 is '1111' and the downlink assignment index is '11', which indicates releasing downlink semi-persistent scheduling;
the number of HARQ processes of DCI format 1_1 is '1111' and the downlink allocation index is '11' to release downlink semi-persistent scheduling;
the number of HARQ processes of DCI format 0_0 is '1111' and the downlink assignment index is '11', indicating that the uplink scheduling-free type 2 is released;
the number of HARQ processes of DCI format 0_1 is '1111' and the downlink allocation index is '11', which indicates that the uplink non-scheduling type 2 is released.
TABLE 8
Figure BDA0001545235020000211
Example 4
The method comprises the steps of activating or releasing downlink semi-persistent scheduling by using DCI format 1_0/DCI format 1_1, activating or releasing uplink scheduling-free type 2 by using DCI format 0_0/DCI format 0_1, and representing activation or release by using different values of downlink allocation index fields and different values of redundancy version fields in corresponding formats.
The UE determines whether to activate or release downlink semi-persistent scheduling or whether to activate or release uplink non-scheduling type 2 according to the downlink allocation index field and the redundancy version field in the corresponding format of the received DCI.
As shown in table 9, setting the downlink allocation index of DCI format 1_0 to '00' and setting the redundancy version to '00' indicates activating downlink semi-persistent scheduling;
the downlink allocation index of the DCI format 1_1 is set to '00' and the redundancy version of the enabled transport block is set to '00' to indicate that downlink semi-persistent scheduling is activated;
the downlink allocation index of the DCI format 0_0 is set to '00' and the redundancy version set to '00' indicates that the uplink scheduling-free type 2 is activated;
the downlink allocation index of DCI format 0_1 is set to '00' and the redundancy version is set to '00' to indicate that the uplink exempt scheduling type 2 is activated.
TABLE 9
Figure BDA0001545235020000221
As shown in table 10, setting the downlink allocation index of DCI format 1_0 to '11' and setting the redundancy version to '11' indicates releasing downlink semi-persistent scheduling;
the downlink allocation index of the DCI format 1_1 is set to '11' and the redundancy version of the enabled transport block is set to '11', indicating that downlink semi-persistent scheduling is released;
the downlink allocation index of the DCI format 0_0 is set to '11' and the redundancy version is set to '11', which indicates that the uplink scheduling-free type 2 is released;
the downlink allocation index of DCI format 0_1 is set to '11' and the redundancy version is set to '11', indicating that the uplink exemption scheduling type 2 is released.
Watch 10
Figure BDA0001545235020000222
Example 5
And activating or releasing downlink semi-persistent scheduling by using DCI format 1_0/DCI format 1_1, activating or releasing uplink scheduling-free type 2 by using DCI format 0_0/DCI format 0_1, and representing activation or release by using different values of downlink allocation index fields in corresponding formats and different values of TPC commands for scheduling PUSCHs/TPC commands for scheduling PUCCHs.
The UE determines whether to activate or release downlink semi-persistent scheduling or whether to activate or release uplink non-scheduling type 2 according to the downlink allocation index field in the corresponding format of the received DCI and the TPC command of the scheduling PUSCH/the TPC command of the scheduling PUCCH.
As shown in table 11, setting the downlink allocation index of DCI format 1_0 to '00' and setting the TPC command for scheduling PUCCH to '00' indicates activating downlink semi-persistent scheduling;
the downlink allocation index of the DCI format 1_1 is set to '00' and the TPC command for scheduling PUCCH is set to '00' to indicate that downlink semi-persistent scheduling is activated;
the downlink allocation index of the DCI format 0_0 is set to '00' and the TPC command for scheduling PUSCH is set to '00' to indicate that the uplink scheduling-free type 2 is activated;
the downlink allocation index of DCI format 0_1 is set to '00' and the TPC command for scheduling PUSCH is set to '00' to indicate that uplink exempt scheduling type 2 is activated.
TABLE 11
Figure BDA0001545235020000231
As shown in table 12, setting the downlink allocation index of DCI format 1_0 to '11' and setting the TPC command for scheduling PUCCH to '11' indicates releasing downlink semi-persistent scheduling;
the downlink allocation index of the DCI format 1_1 is set to '11' and the TPC command for scheduling the PUCCH is set to '11' to indicate that downlink semi-persistent scheduling is released;
the downlink allocation index of DCI format 0_0 is set to '11' and the TPC command for scheduling PUSCH is set to '11' to indicate that uplink scheduling-free type 2 is released;
the downlink allocation index of DCI format 0_1 is set to '11' and the TPC command for scheduling PUSCH is set to '11', which indicates that the uplink non-scheduling type 2 is released.
TABLE 12
Figure BDA0001545235020000241
Example 6
The downlink semi-persistent scheduling is activated or released by using DCI format 1_0/DCI format 1_1, the uplink scheduling-free type 2 is activated or released by using DCI format 0_0/DCI format 0_1, and the activation or release is represented by different values of redundancy version fields in the corresponding formats and different values of TPC commands of PUSCH scheduling and PUCCH scheduling.
The UE determines whether to activate or release downlink semi-persistent scheduling or whether to activate or release uplink non-scheduling type 2 according to the redundancy version field in the corresponding format of the received DCI and the TPC command of the scheduling PUSCH/the TPC command of the scheduling PUCCH.
As shown in table 13, setting the redundancy version of DCI format 1_0 to '00' and setting the TPC command for scheduling PUCCH to '00' indicates to activate downlink semi-persistent scheduling;
setting the redundancy version of the enabled transport block of the DCI format 1_1 to '00' and setting the TPC command of the scheduling PUCCH to '00' indicates activating downlink semi-persistent scheduling;
setting the redundancy version of the DCI format 0_0 to be '00' and setting the TPC command of scheduling PUSCH to be '00' represents activating the uplink scheduling-free type 2;
setting the redundancy version of DCI format 0_1 to '00' and setting the TPC command for scheduling PUSCH to '00' indicates activating uplink exempt scheduling type 2.
Watch 13
Figure BDA0001545235020000251
As shown in table 14, setting the redundancy version of DCI format 1_0 to '11' and setting the TPC command for scheduling PUCCH to '11' indicates releasing downlink semi-persistent scheduling;
setting the redundancy version of the enabled transport block of the DCI format 1_1 to '11' and setting the TPC command of the scheduling PUCCH to '11' indicates releasing downlink semi-persistent scheduling;
setting the redundancy version of the DCI format 0_0 to be '11' and setting the TPC command of scheduling PUSCH to be '11' to represent that the uplink scheduling-free type 2 is released;
the redundancy version of DCI format 0_1 is set to '11' and the TPC command for scheduling PUSCH is set to '11', which indicates that the uplink exemption scheduling type 2 is released.
TABLE 14
Figure BDA0001545235020000252
Figure BDA0001545235020000261
An embodiment of the present invention further provides an apparatus for activating or releasing semi-persistent scheduling or scheduling-free data transmission, as shown in fig. 2, the apparatus includes:
a receiving unit 11, configured to receive DCI sent by a base station;
a first determining unit 12, configured to determine whether to activate downlink semi-persistent scheduling according to a first DCI format of a scheduled PDSCH when the DCI is the first DCI format of the scheduled PDSCH;
a second determining unit 13, configured to determine whether to release the downlink semi-persistent scheduling according to a second DCI format for scheduling the PDSCH when the DCI is the second DCI format for scheduling the PDSCH;
a third determining unit 14, configured to determine, when the DCI is the first DCI format of the scheduled PUSCH, whether to activate uplink non-scheduling type 2 according to the first DCI format of the scheduled PUSCH;
a fourth determining unit 15, configured to determine whether to release the uplink scheduling-free type 2 according to the second DCI format of the scheduled PUSCH when the DCI is the second DCI format of the scheduled PUSCH.
The activation or release semi-persistent scheduling or scheduling-free data transmission device provided by the embodiment of the invention determines whether to activate or release downlink semi-persistent scheduling according to the first DCI format or the second DCI format of the received scheduled PDSCH, and determines whether to activate or release uplink scheduling-free type 2 according to the first DCI format or the second DCI format of the received scheduled PUSCH, so that whether to activate or release downlink semi-persistent scheduling or activate or release uplink scheduling-free type 2 can be determined according to the received DCI format.
Optionally, the first determining unit 12 is configured to determine whether to activate downlink semi-persistent scheduling according to the number of HARQ processes in the first DCI format of the scheduled PDSCH and a redundancy version field;
the second determining unit 13 is configured to determine whether to release downlink semi-persistent scheduling according to the number of HARQ processes in the second DCI format of the scheduled PDSCH and the redundancy version field;
the third determining unit 14 is configured to determine whether to activate uplink scheduling-free type 2 according to the number of HARQ processes in the first DCI format of the scheduled PUSCH and the redundancy version field;
the fourth determining unit 15 is configured to determine whether to release the uplink scheduling-free type 2 according to the number of HARQ processes in the second DCI format for scheduling the PUSCH and the redundancy version field.
Optionally, the first determining unit 12 is configured to determine whether to activate downlink semi-persistent scheduling according to the number of HARQ processes in the first DCI format for scheduling the PDSCH and a TPC command for scheduling the PUCCH;
the second determining unit 13 is configured to determine whether to release downlink semi-persistent scheduling according to the number of HARQ processes in the second DCI format for scheduling the PDSCH and the TPC command for scheduling the PUCCH;
the third determining unit 14 is configured to determine whether to activate the uplink scheduling-free type 2 according to the number of HARQ processes in the first DCI format for scheduling the PUSCH and the TPC command for scheduling the PUSCH;
the fourth determining unit 15 is configured to determine whether to release the uplink scheduling-free type 2 according to the number of HARQ processes in the second DCI format for scheduling the PUSCH and the TPC command for scheduling the PUSCH.
Optionally, the first determining unit 12 is configured to determine whether to activate downlink semi-persistent scheduling according to the number of HARQ processes in the first DCI format for scheduling the PDSCH and a downlink allocation index field;
the second determining unit 13 is configured to determine whether to release downlink semi-persistent scheduling according to the number of HARQ processes in the second DCI format for scheduling the PDSCH and the downlink allocation index field;
the third determining unit 14 is configured to determine whether to activate the uplink non-scheduling type 2 according to the number of HARQ processes in the first DCI format for scheduling the PUSCH and the downlink allocation index field;
the fourth determining unit 15 is configured to determine whether to release the uplink scheduling-free type 2 according to the number of HARQ processes in the second DCI format for scheduling the PUSCH and the downlink allocation index field.
Optionally, the first determining unit 12 is configured to determine whether to activate downlink semi-persistent scheduling according to a downlink allocation index field and a redundancy version field in a first DCI format of the scheduled PDSCH;
the second determining unit 13 is configured to determine whether to release downlink semi-persistent scheduling according to a downlink allocation index field and a redundancy version field in a second DCI format of the scheduled PDSCH;
the third determining unit 14 is configured to determine whether to activate an uplink scheduling-free type 2 according to a downlink allocation index field and a redundancy version field in the first DCI format for scheduling the PUSCH;
the fourth determining unit 15 is configured to determine whether to release the uplink scheduling-free type 2 according to the downlink allocation index field and the redundancy version field in the second DCI format of the scheduled PUSCH.
Optionally, the first determining unit 12 is configured to determine whether to activate downlink semi-persistent scheduling according to a downlink allocation index field in a first DCI format of the scheduled PDSCH and a TPC command of a scheduled PUCCH;
the second determining unit 13 is configured to determine whether to release downlink semi-persistent scheduling according to a downlink allocation index field in a second DCI format of the scheduled PDSCH and a TPC command of a scheduled PUCCH;
the third determining unit 14 is configured to determine whether to activate uplink scheduling-free type 2 according to the downlink allocation index field in the first DCI format for scheduling the PUSCH and the TPC command for scheduling the PUSCH;
the fourth determining unit 15 is configured to determine whether to release the uplink scheduling-free type 2 according to the downlink allocation index field in the second DCI format for scheduling the PUSCH and the TPC command for scheduling the PUSCH.
Optionally, the first determining unit 12 is configured to determine whether to activate downlink semi-persistent scheduling according to a redundancy version field in the first DCI format for scheduling the PDSCH and a TPC command for scheduling the PUCCH;
the second determining unit 13 is configured to determine whether to release downlink semi-persistent scheduling according to a redundancy version field in the second DCI format of the scheduled PDSCH and a TPC command of the scheduled PUCCH;
the third determining unit 14 is configured to determine whether to activate uplink scheduling-free type 2 according to a redundancy version field in the first DCI format of the scheduled PUSCH and a TPC command of the scheduled PUSCH;
the fourth determining unit 15 is configured to determine whether to release the uplink scheduling-free type 2 according to the redundancy version field in the second DCI format for scheduling the PUSCH and the TPC command for scheduling the PUSCH.
Optionally, the apparatus further comprises:
the judging unit is used for judging whether CRC check bits of the PDCCH are scrambled by using SPS C-RNTI or scrambled by using CS-RNTI;
the first determining unit 12 is configured to determine whether to activate downlink semi-persistent scheduling when the CRC check bits of the PDCCH are scrambled using SPS C-RNTI;
the second determining unit 13 is configured to determine whether to release downlink semi-persistent scheduling when the CRC check bits of the PDCCH are scrambled using SPS C-RNTI;
the third determining unit 14 is configured to determine whether to activate an uplink scheduling-free type 2 when the CRC check bits of the PDCCH are scrambled using CS-RNTI;
the fourth determining unit 15 is configured to determine whether to release the uplink scheduling-exempt type 2 when the CRC check bits of the PDCCH are scrambled using the CS-RNTI.
The apparatus of this embodiment may be configured to implement the technical solutions of the above method embodiments, and the implementation principles and technical effects are similar, which are not described herein again.
The embodiment of the invention also provides the user equipment which comprises the device for activating or releasing the semi-persistent scheduling or scheduling-free data transmission.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above may be implemented by a computer program, which may be stored in a computer readable storage medium and executed by a computer to implement the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are also within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (5)

1. A method of activating or releasing semi-persistent scheduling or scheduling-free data transmission, the method comprising:
receiving downlink control information DCI issued by a base station;
when the DCI is a first DCI format for scheduling the PDSCH, determining whether to activate downlink semi-persistent scheduling according to the first DCI format for scheduling the PDSCH;
when the DCI is a second DCI format for scheduling the PDSCH, determining whether to release downlink semi-persistent scheduling according to the second DCI format for scheduling the PDSCH;
when the DCI is a first DCI format of a scheduling PUSCH, determining whether to activate an uplink scheduling-free type 2 according to the first DCI format of the scheduling PUSCH;
when the DCI is a second DCI format of a scheduling PUSCH, determining whether to release the uplink scheduling-free type 2 according to the second DCI format of the scheduling PUSCH;
the determining whether to activate downlink semi-persistent scheduling according to the first DCI format of the scheduled PDSCH comprises: determining whether to activate downlink semi-persistent scheduling according to the number of HARQ processes in the first DCI format of the scheduling PDSCH and a redundancy version field;
the determining whether to release downlink semi-persistent scheduling according to the second DCI format for scheduling the PDSCH includes: determining whether to release downlink semi-persistent scheduling according to the number of HARQ processes in the second DCI format of the scheduling PDSCH and a redundancy version field;
the determining whether to activate uplink non-scheduling type 2 according to the first DCI format of the scheduled PUSCH includes: determining whether to activate an uplink scheduling-free type 2 according to the number of HARQ processes in the first DCI format of the scheduling PUSCH and a redundancy version field;
the determining whether to release the uplink scheduling-free type 2 according to the second DCI format of the scheduled PUSCH includes: and determining whether to release the uplink scheduling-free type 2 according to the number of HARQ processes in the second DCI format of the scheduling PUSCH and the redundancy version field.
2. The method of claim 1, further comprising:
judging whether CRC check bits of the PDCCH are scrambled by using SPS C-RNTI or CS-RNTI;
when the CRC check bit of the PDCCH is scrambled by using the SPS C-RNTI, determining whether to activate or release downlink semi-persistent scheduling;
and when the CRC check bit of the PDCCH is scrambled by using the CS-RNTI, determining whether to activate or release the uplink non-scheduling type 2.
3. An apparatus for activating or deactivating semi-persistent scheduling or scheduling-free data transmission, comprising:
a receiving unit, configured to receive DCI issued by a base station;
a first determining unit, configured to determine whether to activate downlink semi-persistent scheduling according to a first DCI format for scheduling a PDSCH when the DCI is the first DCI format for scheduling the PDSCH;
a second determining unit, configured to determine whether to release downlink semi-persistent scheduling according to a second DCI format of a scheduled PDSCH when the DCI is the second DCI format of the scheduled PDSCH;
a third determining unit, configured to determine, when the DCI is the first DCI format of the scheduled PUSCH, whether to activate uplink non-scheduling type 2 according to the first DCI format of the scheduled PUSCH;
a fourth determining unit, configured to determine whether to release the uplink scheduling-free type 2 according to a second DCI format of a scheduling PUSCH when the DCI is the second DCI format of the scheduling PUSCH;
the first determining unit is further configured to determine whether to activate downlink semi-persistent scheduling according to the number of HARQ processes and a redundancy version field in the first DCI format for scheduling the PDSCH;
the second determining unit is further configured to determine whether to release downlink semi-persistent scheduling according to the number of HARQ processes and a redundancy version field in the second DCI format for scheduling the PDSCH;
the third determining unit is further configured to determine whether to activate uplink scheduling-free type 2 according to the number of HARQ processes in the first DCI format of the scheduled PUSCH and the redundancy version field;
the fourth determining unit is further configured to determine whether to release the uplink scheduling-free type 2 according to the number of HARQ processes in the second DCI format for scheduling the PUSCH and the redundancy version field.
4. The apparatus of claim 3, further comprising:
the judging unit is used for judging whether CRC check bits of the PDCCH are scrambled by using SPS C-RNTI or scrambled by using CS-RNTI;
the first determining unit is configured to determine whether to activate downlink semi-persistent scheduling when a CRC check bit of the PDCCH is scrambled using SPS C-RNTI;
the second determining unit is configured to determine whether to release downlink semi-persistent scheduling when the CRC check bits of the PDCCH are scrambled using SPS C-RNTI;
the third determining unit is configured to determine whether to activate uplink scheduling-free type 2 when the CRC check bits of the PDCCH are scrambled using the CS-RNTI;
the fourth determining unit is configured to determine whether to release the uplink scheduling-exempt type 2 when the CRC check bits of the PDCCH are scrambled using the CS-RNTI.
5. A user equipment, characterized in that the user equipment comprises the activated or released semi-persistent scheduling or scheduling-free data transmission apparatus according to any of claims 3 to 4.
CN201810026977.9A 2018-01-11 2018-01-11 Method and device for activating or releasing semi-persistent scheduling or scheduling-free data transmission and user equipment Active CN110035542B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810026977.9A CN110035542B (en) 2018-01-11 2018-01-11 Method and device for activating or releasing semi-persistent scheduling or scheduling-free data transmission and user equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810026977.9A CN110035542B (en) 2018-01-11 2018-01-11 Method and device for activating or releasing semi-persistent scheduling or scheduling-free data transmission and user equipment

Publications (2)

Publication Number Publication Date
CN110035542A CN110035542A (en) 2019-07-19
CN110035542B true CN110035542B (en) 2022-09-20

Family

ID=67234679

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810026977.9A Active CN110035542B (en) 2018-01-11 2018-01-11 Method and device for activating or releasing semi-persistent scheduling or scheduling-free data transmission and user equipment

Country Status (1)

Country Link
CN (1) CN110035542B (en)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112583534A (en) * 2019-09-29 2021-03-30 大唐移动通信设备有限公司 Method for sending and receiving signaling, network equipment and terminal
CN110944398B (en) * 2019-11-07 2022-08-26 北京紫光展锐通信技术有限公司 Resource processing method and related equipment
WO2021088062A1 (en) * 2019-11-08 2021-05-14 华为技术有限公司 Communication method and apparatus
CN111193578B (en) * 2020-01-07 2022-03-22 北京紫光展锐通信技术有限公司 Method and system for triggering HARQ-ACK feedback information and method and system for sending HARQ-ACK feedback information
JP7429718B2 (en) * 2020-02-07 2024-02-08 オッポ広東移動通信有限公司 Information reception method, transmission method, device and equipment
CN113329494B (en) * 2020-02-28 2022-06-03 大唐移动通信设备有限公司 Verification method, sending method and equipment for releasing signaling
US20230300835A1 (en) * 2020-04-09 2023-09-21 Telefonaktiebolaget Lm Ericsson (Publ) Systems and methods for tci state activation and codepoint to tci state mapping
CN113677011A (en) * 2020-05-15 2021-11-19 华为技术有限公司 Communication method and related equipment
CN115804202B (en) * 2020-07-27 2024-07-09 Oppo广东移动通信有限公司 Wireless communication method, terminal device and network device

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2166804A1 (en) * 2008-09-17 2010-03-24 Panasonic Corporation Deactivation of semi-persistent resource allocations in a mobile communication network
JP2012512613A (en) * 2008-12-17 2012-05-31 モトローラ モビリティ インコーポレイテッド Semi-permanent resource release by wireless communication device
CN102300331B (en) * 2011-08-19 2013-11-27 电信科学技术研究院 Data transmission method and equipment

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
R1-090024 "PDCCH Validation for Semi-Persistent Scheduling Release";Research In Motion等;《3GPP tsg_ran\WG1_RL1》;20090106;第9.2节、表9.2.1-1、表9.2.2-1 *
R1-090197 "DCI formats and bit fields for SPS deactivation";LG Electronics;《3GPP tsg_ran\WG1_RL1》;20090107;表2 *
R1-1706052 "Semi-Persistent Scheduling for NR";Ericsson;《3GPP tsg_ran\WG1_RL1》;20170325;全文 *
R1-1711686 "[DRAFT LS] to RAN2 on UL SPS / grant free";NTT DOCOMO;《3GPP tsg_ran\WG1_RL1》;20170710;第1节 *

Also Published As

Publication number Publication date
CN110035542A (en) 2019-07-19

Similar Documents

Publication Publication Date Title
CN110035542B (en) Method and device for activating or releasing semi-persistent scheduling or scheduling-free data transmission and user equipment
CN110557233B (en) Codebook feedback method, codebook feedback device, codebook feedback equipment and codebook feedback storage medium
CN109417457B (en) Triggering of reference signals and control signaling
JP5862678B2 (en) Resource allocation method, channel state information transmission method, base station, and user equipment
CN102158971B (en) Method and equipment for realizing semi-persistent scheduling service or similar semi-persistent scheduling service
CN111989885B (en) Method and apparatus for uplink transmission in a communication system
US10805947B2 (en) Method for uplink packet scheduling and device thereof
CN102349346B (en) Resourse Distribute in wireless communication system
US11683788B2 (en) System and method for data channel transmission and reception
CN109687950B (en) Transmission method and device on unlicensed frequency band
EP2615876B1 (en) Transmission method, base station and user equipment for channel quality information
CN106658742A (en) Method, device and system for data scheduling and transmission
CN105610549A (en) Transmission method and transmission system for downlink control information
CN103167615A (en) Information processing method and device
CN111836366B (en) Uplink transmission method and communication device
KR20150090800A (en) A method and an apparatus for operating of a transmission device and a reception device over resource allocation of Device to Device communication in the wireless communication system
JP6982622B2 (en) Resource signaling for PUCCH
EP3545720B1 (en) Method and device for transmitting downlink control information
CN111615861B (en) Multi-bit scheduling request
CN108605323A (en) For realizing the method and apparatus of the control and reference signal of physical uplink shared channel communication
CN106304350B (en) The PUCCH channel dynamic allocation method and device of SPS business
CN104579591A (en) Feedback resource distribution method and system for TDD (Time Division Duplexing) downlink multi-subframe scheduling
CN118764141A (en) Method and apparatus for transmitting or receiving feedback information in communication system
CN108632885B (en) Method for sending buffer status report, terminal equipment and network equipment
US20180323911A1 (en) Device and Method of Handling a Code Block Group Retransmission

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
CB02 Change of applicant information

Address after: 100191, Haidian District, Zhichun Road, Beijing No. 7 to the real building, block B, 18

Applicant after: Beijing Ziguang zhanrui Communication Technology Co.,Ltd.

Address before: 100191, Haidian District, Zhichun Road, Beijing No. 7 to the real building, block B, 18

Applicant before: BEIJING SPREADTRUM HI-TECH COMMUNICATIONS TECHNOLOGY Co.,Ltd.

CB02 Change of applicant information
GR01 Patent grant
GR01 Patent grant