CN111511029A - Time domain resource position determining method and device - Google Patents
Time domain resource position determining method and device Download PDFInfo
- Publication number
- CN111511029A CN111511029A CN202010320416.7A CN202010320416A CN111511029A CN 111511029 A CN111511029 A CN 111511029A CN 202010320416 A CN202010320416 A CN 202010320416A CN 111511029 A CN111511029 A CN 111511029A
- Authority
- CN
- China
- Prior art keywords
- time domain
- domain resource
- pdsch
- dci
- processing
- 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.)
- Granted
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
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
- H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
- H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the application provides a method and a device for determining the position of a time domain resource, wherein the method comprises the following steps: receiving first Downlink Control Information (DCI), wherein the first DCI is used for scheduling a first Physical Downlink Shared Channel (PDSCH); and determining a second time domain resource position for processing the first PDSCH based on the first time domain resource position of the first PDSCH and a target time domain resource length, wherein the target time domain resource length is the time domain resource length required by DCI processing. By adopting the embodiment of the application, the situation that the terminal equipment cannot feed back the processing information of the PDSCH within the specified time can be avoided.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for determining a time domain resource location.
Background
In a 5G communication system, there are multiple Downlink Control Information (DCI) in the same time slot, and the scheduling of a Physical Downlink Shared Channel (PDSCH) by the DCI may be at any position of the time slot. However, DCI scheduling PDSCH follows the principle of processing PDSCH scheduled first, which is scheduled first, and thus a problem of DCI scheduling PDSCH in a disordered manner is likely to occur, which results in that the terminal device cannot feed back processing information of PDSCH within a predetermined time.
Disclosure of Invention
The embodiment of the application provides a method and a device for determining a time domain resource position, which are used for avoiding the situation that terminal equipment cannot feed back processing information of a PDSCH within a specified time.
In a first aspect, an embodiment of the present application provides a method for determining a time domain resource location, where the method is applied to a terminal device, and the method includes:
receiving first Downlink Control Information (DCI), wherein the first DCI is used for scheduling a first Physical Downlink Shared Channel (PDSCH);
determining a second time domain resource position for processing the first PDSCH based on the first time domain resource position of the first PDSCH and a target time domain resource length, wherein the target time domain resource length is a time domain resource length required by DCI processing, and the first time domain resource position comprises the second time domain resource position.
In a second aspect, an embodiment of the present application provides an apparatus, which is applied to a terminal device, and the apparatus includes:
a communication unit, configured to receive first downlink control information DCI, where the first DCI is used to schedule a first physical downlink shared channel PDSCH;
a processing unit, configured to determine a second time domain resource location for processing the first PDSCH based on a first time domain resource location of the first PDSCH and a target time domain resource length, where the target time domain resource length is a time domain resource length required for DCI processing, and the first time domain resource location includes the second time domain resource location.
In a third aspect, an embodiment of the present application provides a terminal device, including a processor, a memory, a communication interface, and one or more programs, where the one or more programs are stored in the memory and configured to be executed by the processor, and the program includes instructions for executing steps in the method according to the first aspect of the embodiment of the present application.
In a fourth aspect, the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program for electronic data exchange, where the computer program makes a computer perform some or all of the steps described in the method according to the first aspect of the present application.
In a fifth aspect, the present application provides a computer program product, where the computer program product includes a non-transitory computer-readable storage medium storing a computer program, where the computer program is operable to cause a computer to perform some or all of the steps described in the method according to the first aspect of the present application. The computer program product may be a software installation package.
It can be seen that, in the embodiment of the present application, the terminal device first receives the first DCI, and then determines a second time domain resource location for processing the first PDSCH based on the first time domain resource location of the first PDSCH and the target time domain resource length, and because the second time domain resource location for processing the first PDSCH is determined, the terminal device can not only feed back processing information of the first PDSCH within the appointed time, but also be beneficial to the terminal device being able to process PDSCHs scheduled by other DCIs in time and feed back processing information within the appointed time.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic architecture diagram of a communication system according to an embodiment of the present application;
fig. 2 is a schematic diagram of a time domain resource distribution provided in an embodiment of the present application;
fig. 3 is a flowchart illustrating a method for determining a time domain resource location according to an embodiment of the present application;
FIG. 4 is a diagram illustrating a time domain resource location determination according to an embodiment of the present application;
FIG. 5 is a schematic diagram of another time domain resource location determination provided in an embodiment of the present application;
FIG. 6 is a schematic diagram of another time domain resource location determination provided in an embodiment of the present application;
fig. 7 is a schematic structural diagram of a terminal device according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a data transmission device according to an embodiment of the present application.
Detailed Description
The terminology used in the description of the embodiments section of the present application is for the purpose of describing particular embodiments of the present application only and is not intended to be limiting of the present application. The terms "first," "second," "third," and "fourth," etc. in the description and claims of this application and in the accompanying drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions.
Referring to fig. 1, fig. 1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application, where the communication system includes a network device and a user equipment, and as shown in fig. 1, the network device may communicate with the user equipment, the communication system may be a global system for mobile Communication (CSM), a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a Worldwide Interoperability for Microwave Access (WiMAX) system, a long term evolution (L TE) system, a 5G communication system (e.g., New Radio (NR)), a communication system with a converged plurality of communication technologies (e.g., a communication system with L TE and NR technologies), or a network device and an NR device shown in fig. 1 are used for example and not limited to the present application.
The terminal device in the embodiment of the application is a device with a wireless communication function, and can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.). The terminal device may be a mobile phone (mobile phone), a tablet computer (pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote medical (remote medical), a wireless terminal in smart grid (smart grid), a wireless terminal in smart home (smart home), and the like. The terminal device may also be a handheld device with wireless communication capabilities, a vehicle mounted device, a wearable device, a computer device or other processing device connected to a wireless modem, etc.
For example, a device providing a base station function in a 2G network includes a Base Transceiver Station (BTS), a device providing a base station function in a 3G network includes a node B (NodeB), a device providing a base station function in a 4G network includes AN evolved node B (eNB), a device providing a base station function in a wireless local area network (W L AN) is AN Access Point (AP), a device gbb providing a base station function in a 5G New Radio (NR) and a node B (eNB) continuing to evolve, where the gbb and the terminal communicate with each other by using AN NR technique, and the eNB and the terminal communicate with each other by using AN E-utra (evolved universal Radio technology) in future, and the eNB and the terminal both include a base station (eNB) and a New Radio access node B (eNB) connected to the future communication system.
The scheduling procedure of PDSCH is described in detail below, taking the network device and the terminal device as examples.
When the network equipment sends a data packet to the terminal equipment, the data packet is coded and modulated by a physical layer and then sent to an antenna port for transmission. After the data packet reaches the terminal equipment, the data packet is demodulated and decoded through a physical layer of the terminal equipment, and a decoding result is fed back to the sending end. Generally, the network device determines whether data is decoded correctly according to hybrid automatic Repeat reQuest (HARQ) information fed back by the terminal device. If the terminal device can correctly receive the data packet, sending Acknowledgement (ACK) information to the network device, and if the terminal device cannot correctly receive the data packet, sending Negative Acknowledgement (NACK) information to the network device. And after receiving the NACK sent by the terminal equipment, the network equipment retransmits the data packet.
As shown in the time domain resource distribution of fig. 2 below, the terminal device schedules the first PDSCH through the first DCI and schedules the second PDSCH through the second DCI, for convenience of description, the first DCI and the second DCI are hereinafter referred to as DCI0 and DCI1, and the first PDSCH and the second PDSCH are referred to as P0 and P1. Downlink data P0 scheduled by DCI0 and downlink data P1 scheduled by DCI 1. In consideration of cost, the terminal device uses only one set of demodulation accelerator for PDSCH. Because the timing required by nr (new radio) is high, the terminal device starts the demodulation process for P0 soon after the DCI0 is decoded. However, when the terminal device demodulates the DCI1 after the same slot, the time domain resource distribution of the P1 scheduled by the DCI1 is located before the P0, the DCI is located before the time domain resource, and the scheduled PDSCH is located after the time domain resource, which is called out-of-order scheduling, and the forms and the numbers of the DCI and the PDSCH shown in fig. 2 are only used for example, and do not constitute a limitation to the embodiment of the present application.
The network device can know whether the terminal device successfully demodulates the PDSCH based on the HARQ mechanism, but in a disordered scheduling scenario, the terminal device cannot feed back the demodulation results of other PDSCHs within a predetermined time.
Referring to fig. 3, fig. 3 is a flowchart illustrating a method for determining a time domain resource location according to an embodiment of the present application, including the following steps:
step 301: receiving first Downlink Control Information (DCI), wherein the first DCI is used for scheduling a first Physical Downlink Shared Channel (PDSCH).
Step 302: and determining a second time domain resource position for processing the first PDSCH based on the first time domain resource position of the first PDSCH and a target time domain resource length, wherein the target time domain resource length is the time domain resource length required by DCI processing.
The time domain resource occupied by the first PDSCH may be Symbol, or may be other time slot resource.
The time domain resources occupied by the first PDSCH are multiple.
Wherein the first DCI and the first PDSCH are located in the same time slot.
The first time domain resource position comprises a starting time domain resource position and a terminating time domain resource position.
The first time domain resource location may or may not include the second time domain resource location.
The starting time domain resource position of the first DCI may be the same as or different from the starting time domain resource position of the first PDSCH.
The time domain resource length occupied by the first DCI and the time domain resource length occupied by the first PDSCH may be the same or different.
If the starting time domain resource position of the first DCI and the starting time domain resource position of the first PDSCH are available, the starting time domain resource position of the first PDSCH is located behind the starting time domain resource position of the first DCI.
Wherein, the time domain resource length occupied by the first DCI and the time domain resource length occupied by the first PDSCH may be different.
The target time domain resource length comprises a time domain resource degree required by hardware accelerator processing and a time domain resource length required by decoding software processing.
It can be seen that, in the embodiment of the present application, the terminal device first receives the first DCI, and then determines a second time domain resource location for processing the first PDSCH based on the first time domain resource location of the first PDSCH and the target time domain resource length, and because the second time domain resource location for processing the first PDSCH is determined, the terminal device can not only feed back processing information of the first PDSCH within the appointed time, but also be beneficial to the terminal device being able to process PDSCHs scheduled by other DCIs in time and feed back processing information within the appointed time.
In an implementation manner of the present application, a second DCI is received, where the second DCI is used to schedule a second PDSCH, and both the first DCI and the second DCI are located in a first time slot.
And the first DCI and the second DCI occupy different time domain resource positions.
The time domain resource position of the second DCI may be before the time domain resource position of the first DCI, or may be after the time domain resource position of the first DCI.
Wherein the second DCI and the second PDSCH are located in the same time slot.
The time domain resource position occupied by the second DCI may be the same as or different from the time domain resource position occupied by the second PDSCH.
The time domain resource length occupied by the second DCI and the time domain resource length occupied by the second PDSCH may be the same or different.
Wherein the time-domain starting domain resource position of the second DCI is located before the starting time-domain resource position of the second PDSCH.
It can be seen that, in the embodiment of the present application, multiple DCIs are transmitted in the same time slot, so that the utilization rate of the time slot can be improved.
In an implementation manner of the present application, the first PDSCH and the second PDSCH are both located in the first time slot, and the first PDSCH and the second PDSCH are used for transmitting different types of data.
The first PDSCH may be transmitted by system messages, Radio Resource Control (RRC) commands, or other types of data.
Wherein the second PDSCH transmission may be traffic data.
And the positions of the time domain resources occupied by the first PDSCH and the second PDSCH are different.
The length of the time domain resource for the first PDSCH may be greater than, equal to, or less than the length of the time domain resource occupied by the second PDSCH.
It can be seen that, in the embodiment of the present application, the utilization rate of the time slot can be improved by transmitting multiple PDSCHs in the same time slot.
In an implementation manner of the present application, the first time domain resource location includes a first starting time domain resource location of the first PDSCH, the first ending time domain resource location of the first DCI is located before the second starting time domain resource location of the second DCI, and the first starting time domain resource location is located after the second ending time domain resource location of the second PDSCH.
Wherein, the first terminating time domain resource position may be adjacent to the second starting time domain resource position, or may not be adjacent.
The first starting time domain resource position may be adjacent to the second terminating time domain resource position, or may not be adjacent to the second terminating time domain resource position.
The first time domain resource terminating position is located before the second time domain resource terminating position, and the first time domain resource terminating position is located after the second time domain resource terminating position, so that the problem of out-of-order scheduling exists.
In an implementation manner of the present application, the target time domain resource length is determined based on a first time domain resource length and a second time domain resource length, where the first time domain resource length is a time domain resource length required for performing hardware accelerated processing on the first DCI, and the second time domain resource length is a time domain resource length required for performing decoding software processing on the first DCI; determining a second time domain resource location for processing the first PDSCH based on the first time domain resource location of the first PDSCH and the target time domain resource length, comprising:
if a third time domain resource location is located behind a third terminating time domain resource location of the first PDSCH, determining that the second time domain resource location is the third terminating time domain resource location, the third time domain resource location is located behind the first starting time domain resource location, and the third time domain resource location and the first starting time domain resource location are separated by the target time domain resource length;
and if the third time domain resource position is located before the third termination time domain resource position, determining that the second time domain resource position is the third time domain resource position.
The first time domain resource length and the second time domain resource length may be equal, and may be 2 symbols.
The length of a third time domain resource required by the second DCI for performing the hardware acceleration processing may be equal to the length of the first time domain resource, and the length of a fourth time domain resource required by the second DCI for performing the decoding software processing may be equal to the length of the second time domain resource.
The hardware acceleration processing is used for modulating the scheduled PDSCH, and the software decoding processing is used for carrying out parameter configuration on the scheduled PDSCH.
For example, taking the feedback time of the terminal device corresponding to PDSCH processing capability 1(capability1) as an example, assuming that the subcarrier interval is 30khz (μ ═ 1), as shown in table 1, the time N1 for feeding back PDSCH processing information by the appointed terminal device is 13 symbols, the time for feeding back second PDSCH processing information is 10 symbols, the time domain resource length required for performing hardware acceleration processing on the first DCI and the second DCI is 2 symbols, the time domain resource length required for performing decoding software processing on the first DCI and the second DCI is 2 symbols, the time domain resource length occupied by the first PDSCH is 7 symbols, and the time domain resource length occupied by the second PDSCH is 2 symbols; as shown in fig. 4, assuming that time domain resource positions occupied by the first DCI are symbol0 and symbol1, time domain resource positions occupied by the second DCI are symbol4 and symbol5, time domain resource positions occupied by the first PDSCH are symbol7 to symbol13, time domain resource positions occupied by the second PDSCH are symbol5 and symbol6, since the starting time domain resource position of the first PDSCH is 7 and the target time domain resource length is 4symbol, the third time domain resource position of the first PDSCH is symbol11, since the third time domain resource position is located in front of the terminating time domain resource position symbol13 of the first PDSCH, the second time domain resource position is the third time domain resource position, the time domain resource position for processing the first PDSCH is symbol11, since the time domain resource length required for the second DCI to perform hardware acceleration processing and decoding software processing is 4symbol 10, the second PDSCH is processed in advance, and feedback processing is guaranteed, and then the first PDSCH is processed, so that the feedback of the processing information of the first PDSCH is ensured to be within 13 symbols.
TABLE 1
It can be seen that, in the embodiment of the present application, by determining the time domain resource location for processing the first PDSCH, not only is the timely processing of the first PDSCH ensured, but also the timeout of processing information for feeding back the second PDSCH is avoided.
In an implementation manner of the present application, after determining that the second time domain resource location is the third termination time domain resource location, the method further includes:
if the second time domain resource position and a fourth time domain resource position for processing the second PDSCH are the same time domain resource position, processing the second PDSCH, wherein the fourth time domain resource position is positioned behind the second termination time domain resource position and is separated from the second termination time domain resource position by the target time domain resource length;
processing the first PDSCH after the second PDSCH processing is completed.
And determining the processing sequence according to the data types transmitted by the first PDSCH and the second PDSCH.
For example, taking the feedback time of the terminal device corresponding to PDSCH processing capability 1(capability1) as an example, as shown in fig. 5, assuming that the time domain resource positions occupied by the first DCI are symbol0 and symbol1, the time domain resource positions occupied by the second DCI are symbol5 and symbol6, the time domain resource positions occupied by the first PDSCH are symbol7 to symbol13, and the time domain resource positions occupied by the second PDSCH are symbol5 and symbol6, since the starting time domain resource position of the first PDSCH is 7 and the target time domain resource length is 4symbol, the third time domain resource position of the first PDSCH is symbol11, and since the third time domain resource position is in front of the terminating time domain resource position symbol13 of the first PDSCH, the second time domain resource position is the third time domain resource position, the time domain resource position for processing the first PDSCH is symbol11, and since the second time domain resource position for hardware accelerated processing and decoding of the second DCI is 11, the second time domain resource position is symbol11, since the second PDSCH is used for transmitting service data and the first PDSCH transmits system messages, the second PDSCH is processed first, and time required for feeding back processing information of the first PDSCH and the second PDSCH is guaranteed.
It can be seen that, in the embodiment of the present application, the processing order is determined according to the type of the service, which is beneficial to the ordered processing of the data.
In an implementation manner of the present application, a third starting time domain resource location of the first DCI is adjacent to a fourth terminating time domain resource location of the second DCI, the third starting time domain resource location is after the fourth terminating time domain resource location, a fourth starting time domain resource location of the first PDSCH is adjacent to a fifth terminating time domain resource location of the second PDSCH, the fourth starting time domain resource location is after the fifth terminating time domain resource location, and starting time domain resource locations occupied by the second DCI and the second PDSCH are the same.
The time domain resource position of the first DCI is behind the time domain resource position of the second DCI, and the time domain resource position of the second PDSCH is behind the time domain resource position of the second PDSCH, so that out-of-order scheduling does not exist.
In an implementation manner of the present application, the determining, based on the first time domain resource location of the first PDSCH and the target time domain resource length, a second time domain resource location for processing the first PDSCH includes:
determining, based on the fourth starting time domain resource position and the target time domain resource length, that the second time domain resource position is a sixth terminating time domain resource position of the first PDSCH, the sixth terminating time domain resource position being located after the fourth starting time domain resource position, and the sixth terminating time domain resource being separated from the fourth starting time domain resource position by the target time domain resource length;
the target time domain resource length is determined based on a third time domain resource length, a fourth time domain resource length and a fifth time domain resource length, the third time domain resource length is a time domain resource length required for performing hardware acceleration processing on the second DCI, the fourth time domain resource length is a time domain resource length required for performing hardware acceleration processing on the first DCI, or a time domain resource length required for performing decoding software processing on the second DCI, and the fifth time domain resource length is a time domain resource length required for performing decoding software processing on the first DCI.
In one implementation of the present application, the DCI processing includes: performing hardware acceleration processing on the second DCI; after the hardware acceleration processing is carried out on the second DCI, carrying out decoding software processing on the second DCI, and carrying out hardware acceleration processing on the first DCI; and after the second DCI is subjected to decoding software processing and the first DCI is subjected to hardware acceleration processing, the first DCI is subjected to decoding software processing.
For example, taking the feedback time of the terminal device corresponding to PDSCH processing capability 1(capability1) as an example, as shown in fig. 6, assuming that the time domain resource positions occupied by the first DCI are symbol7 and symbol8, the time domain resource positions occupied by the second DCI are symbol5 and symbol6, the time domain resource positions occupied by the first PDSCH are symbol7 to symbol13, and the time domain resource positions occupied by the second PDSCH are symbol5 and symbol6, according to the above DCI processing manners, the time domain resource position for processing the first PDSCH is symbol13, and the time domain resource position for processing the second PDSCH is symbol11, thereby ensuring the time required for feeding back the processing information of the first PDSCH and the second PDSCH.
It can be seen that, in the embodiment of the present application, when the DCI is adjacent and the PDSCH is adjacent, DCI processing is adopted, so that time required for DCI processing is reduced, and it is beneficial for the terminal device to be able to quickly feed back PDSCH processing information.
Referring to fig. 7, fig. 7 is a terminal device according to an embodiment of the present application, including: one or more processors, one or more memories, one or more communication interfaces, and one or more programs;
the one or more programs are stored in the memory and configured to be executed by the one or more processors; the program includes instructions for performing the steps of:
receiving first Downlink Control Information (DCI), wherein the first DCI is used for scheduling a first Physical Downlink Shared Channel (PDSCH);
and determining a second time domain resource position for processing the first PDSCH based on the first time domain resource position of the first PDSCH and a target time domain resource length, wherein the target time domain resource length is the time domain resource length required by DCI processing.
In an implementation of the application, the program comprises instructions for further performing the steps of:
receiving second DCI, wherein the second DCI is used for scheduling a second PDSCH, and the first DCI and the second DCI are both located in a first time slot.
In an implementation manner of the present application, the first PDSCH and the second PDSCH are both located in the first time slot, and the first PDSCH and the second PDSCH are used for transmitting different types of data.
In an implementation manner of the present application, the first time domain resource location includes a first starting time domain resource location of the first PDSCH, the first ending time domain resource location of the first DCI is located before the second starting time domain resource location of the second DCI, and the first starting time domain resource location is located after the second ending time domain resource location of the second PDSCH.
In an implementation manner of the present application, the target time domain resource length is determined based on a first time domain resource length and a second time domain resource length, where the first time domain resource length is a time domain resource length required for performing hardware acceleration processing on the first DCI, and the second time domain resource length is a time domain resource length required for performing decoding software processing on the first DCI; in the aspect of determining a second time domain resource location for processing the first PDSCH based on the first time domain resource location of the first PDSCH and a target time domain resource length, the program includes instructions to perform further steps of:
if a third time domain resource location is located behind a third terminating time domain resource location of the first PDSCH, determining that the second time domain resource location is the third terminating time domain resource location, the third time domain resource location is located behind the first starting time domain resource location, and the third time domain resource location and the first starting time domain resource location are separated by the target time domain resource length;
and if the third time domain resource position is located before the third termination time domain resource position, determining that the second time domain resource position is the third time domain resource position.
In an implementation manner of this application, after determining that the second time domain resource location is the third terminating time domain resource location, the program includes instructions further configured to:
if the second time domain resource position and a fourth time domain resource position for processing the second PDSCH are the same time domain resource position, processing the second PDSCH, wherein the fourth time domain resource position is positioned behind the second termination time domain resource position and is separated from the second termination time domain resource position by the target time domain resource length;
processing the first PDSCH after the second PDSCH processing is completed.
In an implementation manner of the present application, a third starting time domain resource location of the first DCI is adjacent to a fourth terminating time domain resource location of the second DCI, the third starting time domain resource location is after the fourth terminating time domain resource location, a fourth starting time domain resource location of the first PDSCH is adjacent to a fifth terminating time domain resource location of the second PDSCH, the fourth starting time domain resource location is after the fifth terminating time domain resource location, and time domain resource locations occupied by the second DCI and the second PDSCH are the same.
In an implementation of the present application, in the determining a second time domain resource location for processing the first PDSCH based on the first time domain resource location of the first PDSCH and a target time domain resource length, the program includes instructions further configured to:
determining, based on the fourth starting time domain resource position and the target time domain resource length, that the second time domain resource position is a sixth terminating time domain resource position of the first PDSCH, the sixth terminating time domain resource position being located after the fourth starting time domain resource position, and the sixth terminating time domain resource being separated from the fourth starting time domain resource position by the target time domain resource length;
the target time domain resource length is determined based on a third time domain resource length, a fourth time domain resource length and a fifth time domain resource length, the third time domain resource length is a time domain resource length required for performing hardware acceleration processing on the second DCI, the fourth time domain resource length is a time domain resource length required for performing hardware acceleration processing on the first DCI, or a time domain resource length required for performing decoding software processing on the second DCI, and the fifth time domain resource length is a time domain resource length required for performing decoding software processing on the first DCI.
In one implementation of the present application, the DCI processing includes: performing hardware acceleration processing on the second DCI; after the hardware acceleration processing is carried out on the second DCI, carrying out decoding software processing on the second DCI, and carrying out hardware acceleration processing on the first DCI; and after the second DCI is subjected to decoding software processing and the first DCI is subjected to hardware acceleration processing, the first DCI is subjected to decoding software processing.
It should be noted that, for the specific implementation process of the present embodiment, reference may be made to the specific implementation process described in the above method embodiment, and a description thereof is omitted here.
Referring to fig. 8, fig. 8 is a time domain resource location determining apparatus provided in an embodiment of the present application, and the apparatus is applied to a terminal device, and the apparatus includes:
a communication unit 801, configured to receive target data in at least one radio bearer RB, where the target data in the at least one RB is data of a target service;
a processing unit 802, configured to determine, based on a first time domain resource location of the first PDSCH and a target time domain resource length, a second time domain resource location for processing the first PDSCH, where the target time domain resource length is a time domain resource length required for DCI processing.
In an implementation manner of the present application, the communication unit 801 is further configured to execute the following steps:
receiving second DCI, wherein the second DCI is used for scheduling a second PDSCH, and the first DCI and the second DCI are both located in a first time slot.
In an implementation manner of the present application, the first PDSCH and the second PDSCH are both located in the first time slot, and the first PDSCH and the second PDSCH are used for transmitting different types of data.
In an implementation manner of the present application, the first time domain resource location includes a first starting time domain resource location of the first PDSCH, the first ending time domain resource location of the first DCI is located before the second starting time domain resource location of the second DCI, and the first starting time domain resource location is located after the second ending time domain resource location of the second PDSCH.
In an implementation manner of the present application, the target time domain resource length is determined based on a first time domain resource length and a second time domain resource length, where the first time domain resource length is a time domain resource length required for performing hardware acceleration processing on the first DCI, and the second time domain resource length is a time domain resource length required for performing decoding software processing on the first DCI; in the aspect of determining a second time domain resource location for processing the first PDSCH based on the first time domain resource location of the first PDSCH and the target time domain resource length, the processing unit 802 is further configured to execute the following steps:
if a third time domain resource location is located behind a third terminating time domain resource location of the first PDSCH, determining that the second time domain resource location is the third terminating time domain resource location, the third time domain resource location is located behind the first starting time domain resource location, and the third time domain resource location and the first starting time domain resource location are separated by the target time domain resource length;
and if the third time domain resource position is located before the third termination time domain resource position, determining that the second time domain resource position is the third time domain resource position.
In an implementation manner of the present application, after determining that the second time domain resource location is the third terminating time domain resource location, the determining unit 802 is further configured to execute the following steps:
if the second time domain resource position and a fourth time domain resource position for processing the second PDSCH are the same time domain resource position, processing the second PDSCH, wherein the fourth time domain resource position is positioned behind the second termination time domain resource position and is separated from the second termination time domain resource position by the target time domain resource length;
processing the first PDSCH after the second PDSCH processing is completed.
In an implementation manner of the present application, a third starting time domain resource location of the first DCI is adjacent to a fourth terminating time domain resource location of the second DCI, the third starting time domain resource location is after the fourth terminating time domain resource location, a fourth starting time domain resource location of the first PDSCH is adjacent to a fifth terminating time domain resource location of the second PDSCH, the fourth starting time domain resource location is after the fifth terminating time domain resource location, and time domain resource locations occupied by the second DCI and the second PDSCH are the same.
In an implementation manner of this application, in the aspect of determining, based on the first time domain resource location of the first PDSCH and the target time domain resource length, a second time domain resource location for processing the first PDSCH, the determining unit 802 is further configured to execute instructions of:
determining, based on the fourth starting time domain resource position and the target time domain resource length, that the second time domain resource position is a sixth terminating time domain resource position of the first PDSCH, the sixth terminating time domain resource position being located after the fourth starting time domain resource position, and the sixth terminating time domain resource being separated from the fourth starting time domain resource position by the target time domain resource length;
the target time domain resource length is determined based on a third time domain resource length, a fourth time domain resource length and a fifth time domain resource length, the third time domain resource length is a time domain resource length required for performing hardware acceleration processing on the second DCI, the fourth time domain resource length is a time domain resource length required for performing hardware acceleration processing on the first DCI, or a time domain resource length required for performing decoding software processing on the second DCI, and the fifth time domain resource length is a time domain resource length required for performing decoding software processing on the first DCI.
In one implementation of the present application, the DCI processing includes: performing hardware acceleration processing on the second DCI; after the hardware acceleration processing is carried out on the second DCI, carrying out decoding software processing on the second DCI, and carrying out hardware acceleration processing on the first DCI; and after the second DCI is subjected to decoding software processing and the first DCI is subjected to hardware acceleration processing, the first DCI is subjected to decoding software processing.
It should be noted that, in the apparatus, the communication unit 801 may be implemented by a communication interface, and the processing unit 802 may be implemented by a processor.
Embodiments of the present application also provide a computer storage medium, where the computer storage medium stores a computer program for electronic data exchange, the computer program enabling a computer to execute part or all of the steps of any one of the methods as described in the above method embodiments, and the computer includes a user equipment.
Embodiments of the present application also provide a computer program product comprising a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any of the methods as described in the above method embodiments. The computer program product may be a software installation package, the computer comprising user equipment.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the above-described division of the units is only one type of division of logical functions, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be an electric or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit may be stored in a computer readable memory if it is implemented in the form of a software functional unit and sold or used as a stand-alone product. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a memory, and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the above-mentioned method of the embodiments of the present application. And the aforementioned memory comprises: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable memory, which may include: flash Memory disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.
The foregoing detailed description of the embodiments of the present application has been presented to illustrate the principles and implementations of the present application, and the above description of the embodiments is only provided to help understand the method and the core concept of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (12)
1. A time domain resource location determination method is applied to a terminal device, and comprises the following steps:
receiving first Downlink Control Information (DCI), wherein the first DCI is used for scheduling a first Physical Downlink Shared Channel (PDSCH);
and determining a second time domain resource position for processing the first PDSCH based on the first time domain resource position of the first PDSCH and a target time domain resource length, wherein the target time domain resource length is the time domain resource length required by DCI processing.
2. The method of claim 1, further comprising:
receiving second DCI, wherein the second DCI is used for scheduling a second PDSCH, and the first DCI and the second DCI are both located in a first time slot.
3. The method of claim 2, wherein the first PDSCH and the second PDSCH are both located in the first time slot, and wherein the first PDSCH and the second PDSCH are used to transmit different types of data.
4. The method of claim 2 or 3, wherein the first time domain resource location comprises a first starting time domain resource location of the first PDSCH, wherein a first terminating time domain resource location of the first DCI precedes a second starting time domain resource location of the second DCI, and wherein the first starting time domain resource location follows a second terminating time domain resource location of the second PDSCH.
5. The method of claim 4, wherein the target time domain resource length is determined based on a first time domain resource length required for hardware-accelerated processing of the first DCI and a second time domain resource length required for decoding software processing of the first DCI; determining a second time domain resource location for processing the first PDSCH based on the first time domain resource location of the first PDSCH and the target time domain resource length, comprising:
if a third time domain resource location is located behind a third terminating time domain resource location of the first PDSCH, determining that the second time domain resource location is the third terminating time domain resource location, the third time domain resource location is located behind the first starting time domain resource location, and the third time domain resource location and the first starting time domain resource location are separated by the target time domain resource length;
and if the third time domain resource position is located before the third termination time domain resource position, determining that the second time domain resource position is the third time domain resource position.
6. The method of claim 5, wherein after determining that the second time domain resource location is the third terminating time domain resource location, the method further comprises:
if the second time domain resource position and a fourth time domain resource position for processing the second PDSCH are the same time domain resource position, processing the second PDSCH, wherein the fourth time domain resource position is positioned behind the second termination time domain resource position and is separated from the second termination time domain resource position by the target time domain resource length;
processing the first PDSCH after the second PDSCH processing is completed.
7. The method of claim 2 or 3, wherein a third starting time domain resource location of the first DCI is adjacent to a fourth terminating time domain resource location of the second DCI, the third starting time domain resource location is subsequent to the fourth terminating time domain resource location, a fourth starting time domain resource location of the first PDSCH is adjacent to a fifth terminating time domain resource location of the second PDSCH, the fourth starting time domain resource location is subsequent to the fifth terminating time domain resource location, and time domain resource locations occupied by the second DCI and the second PDSCH are the same.
8. The method of claim 7, wherein the determining a second time domain resource location for processing the first PDSCH based on the first time domain resource location of the first PDSCH and a target time domain resource length comprises:
determining, based on the fourth starting time domain resource position and the target time domain resource length, that the second time domain resource position is a sixth terminating time domain resource position of the first PDSCH, the sixth terminating time domain resource position being located after the fourth starting time domain resource position, and the sixth terminating time domain resource being separated from the fourth starting time domain resource position by the target time domain resource length;
the target time domain resource length is determined based on a third time domain resource length, a fourth time domain resource length and a fifth time domain resource length, the third time domain resource length is a time domain resource length required for performing hardware acceleration processing on the second DCI, the fourth time domain resource length is a time domain resource length required for performing hardware acceleration processing on the first DCI, or a time domain resource length required for performing decoding software processing on the second DCI, and the fifth time domain resource length is a time domain resource length required for performing decoding software processing on the first DCI.
9. The method of claim 8, wherein the DCI processing comprises: performing hardware acceleration processing on the second DCI; after the hardware acceleration processing is carried out on the second DCI, carrying out decoding software processing on the second DCI, and carrying out hardware acceleration processing on the first DCI; and after the second DCI is subjected to decoding software processing and the first DCI is subjected to hardware acceleration processing, the first DCI is subjected to decoding software processing.
10. A time domain resource location determining apparatus, applied to a terminal device, the apparatus comprising:
a communication unit, configured to receive first downlink control information DCI, where the first DCI is used to schedule a first physical downlink shared channel PDSCH;
a processing unit, configured to determine a second time domain resource location for processing the first PDSCH based on a first time domain resource location of the first PDSCH and a target time domain resource length, where the target time domain resource length is a time domain resource length required for DCI processing, and the first time domain resource location includes the second time domain resource location.
11. A terminal device, characterized in that the terminal device comprises a memory, a communication interface, and one or more programs stored in the memory and configured to be executed by the processor, the programs comprising instructions for performing the steps in the method according to any one of claims 1-9.
12. A computer-readable storage medium, characterized in that a computer program for electronic data exchange is stored, wherein the computer program causes a computer to perform the method according to any one of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010320416.7A CN111511029B (en) | 2020-04-21 | 2020-04-21 | Time domain resource position determining method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010320416.7A CN111511029B (en) | 2020-04-21 | 2020-04-21 | Time domain resource position determining method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111511029A true CN111511029A (en) | 2020-08-07 |
| CN111511029B CN111511029B (en) | 2022-10-11 |
Family
ID=71874464
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010320416.7A Active CN111511029B (en) | 2020-04-21 | 2020-04-21 | Time domain resource position determining method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111511029B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022188074A1 (en) * | 2021-03-10 | 2022-09-15 | 北京小米移动软件有限公司 | Method and apparatus for configuring and determining downlink scheduling information, device, and medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109392136A (en) * | 2017-08-11 | 2019-02-26 | 电信科学技术研究院有限公司 | A kind of determination of time-domain resource, configuration method, terminal and network side equipment |
| WO2019061347A1 (en) * | 2017-09-29 | 2019-04-04 | Oppo广东移动通信有限公司 | Wireless communication method and device |
| CN109600846A (en) * | 2017-09-30 | 2019-04-09 | 华为技术有限公司 | A kind of determination method and device of time-domain information |
| CN110912663A (en) * | 2018-09-15 | 2020-03-24 | 华为技术有限公司 | Communication method and device |
| US20200120651A1 (en) * | 2017-09-30 | 2020-04-16 | Huawei Technologies Co., Ltd. | Information transmission method and apparatus |
| CN111030799A (en) * | 2017-09-14 | 2020-04-17 | Oppo广东移动通信有限公司 | Method, device, storage medium and system for determining time domain resources |
-
2020
- 2020-04-21 CN CN202010320416.7A patent/CN111511029B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109392136A (en) * | 2017-08-11 | 2019-02-26 | 电信科学技术研究院有限公司 | A kind of determination of time-domain resource, configuration method, terminal and network side equipment |
| CN111030799A (en) * | 2017-09-14 | 2020-04-17 | Oppo广东移动通信有限公司 | Method, device, storage medium and system for determining time domain resources |
| WO2019061347A1 (en) * | 2017-09-29 | 2019-04-04 | Oppo广东移动通信有限公司 | Wireless communication method and device |
| CN109600846A (en) * | 2017-09-30 | 2019-04-09 | 华为技术有限公司 | A kind of determination method and device of time-domain information |
| US20200120651A1 (en) * | 2017-09-30 | 2020-04-16 | Huawei Technologies Co., Ltd. | Information transmission method and apparatus |
| CN110912663A (en) * | 2018-09-15 | 2020-03-24 | 华为技术有限公司 | Communication method and device |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022188074A1 (en) * | 2021-03-10 | 2022-09-15 | 北京小米移动软件有限公司 | Method and apparatus for configuring and determining downlink scheduling information, device, and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111511029B (en) | 2022-10-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| TWI666946B (en) | User equipment supporting ultra-reliable low latency communication service, user equipment supporting enhanced mobile broadband service, and base station | |
| EP3435575B1 (en) | Method and device for transmitting data | |
| US11368201B2 (en) | Method for groupcast transmission and reception with feedback information, and apparatus therefor | |
| WO2021052254A1 (en) | Data transmission method, apparatus and system | |
| CN111818649B (en) | Data transmission device and method in direct communication | |
| CN105491621A (en) | Joint uplink data processing by plural base stations | |
| CN111699645B (en) | Communication method and device | |
| EP3598682B1 (en) | Method and apparatus for uplink data transmission | |
| EP3605899B1 (en) | Information processing method and device | |
| US11812455B2 (en) | Response information transmission method, communications device, and network device | |
| WO2018202193A1 (en) | Data transmission method, apparatus, and system | |
| CN109845364A (en) | Method, terminal device and the network equipment of transmitting uplink control information | |
| US20200178285A1 (en) | Acknowledgement information transmission method, terminal device, and network device | |
| CN110100494A (en) | A kind of method and apparatus of data transmission | |
| CN104471998A (en) | Method and network node for allocating resources of an uplink subframe | |
| CN108809495B (en) | Data transmission method and device | |
| WO2020194924A1 (en) | Terminal and transmission method | |
| CN109417443A (en) | Method, terminal device and the base station of transmitting feedback information | |
| EP3930375B1 (en) | Method and device for data transmission | |
| CN107615813A (en) | A kind of uplink data transmission method and device | |
| CN111511029B (en) | Time domain resource position determining method and device | |
| KR20210109620A (en) | Downlink data transmission method, reception method, apparatus and storage medium | |
| KR20220155322A (en) | Method and apparatus for performing sidelink transmission based on PUCCH processing time in NR V2X | |
| CN112787774B (en) | Processing method of hybrid automatic repeat request and communication device | |
| EP3790207B1 (en) | Information transmission method, communication device, and network device |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |