[go: up one dir, main page]

WO2019129012A1 - 控制信息的传输方法 - Google Patents

控制信息的传输方法 Download PDF

Info

Publication number
WO2019129012A1
WO2019129012A1 PCT/CN2018/123629 CN2018123629W WO2019129012A1 WO 2019129012 A1 WO2019129012 A1 WO 2019129012A1 CN 2018123629 W CN2018123629 W CN 2018123629W WO 2019129012 A1 WO2019129012 A1 WO 2019129012A1
Authority
WO
WIPO (PCT)
Prior art keywords
uplink
time
rur
control information
terminal device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/123629
Other languages
English (en)
French (fr)
Inventor
杜白
张鹏
李化加
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP18897577.5A priority Critical patent/EP3720217B1/en
Publication of WO2019129012A1 publication Critical patent/WO2019129012A1/zh
Priority to US16/915,757 priority patent/US11251930B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0096—Indication of changes in allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT the frequencies being arranged in component carriers
    • 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/0037—Inter-user or inter-terminal allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority
    • 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/0078—Timing of allocation
    • H04L5/0087—Timing of allocation when data requirements change
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • 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/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • 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/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient

Definitions

  • Embodiments of the present invention relate to the field of wireless communications, and in particular, to a method for transmitting control information.
  • the 5G mobile communication system supports an enhanced mobile broadband (eMBB) service, an ultra reliable and low latency communications (URLLC) service, and a mass machine type communications (mMTC) service.
  • eMBB services include: ultra high definition video, augmented reality (AR), virtual reality (VR), etc.
  • the main features of these services are large amount of transmitted data and high transmission rate.
  • Typical URLLC services include wireless control in industrial manufacturing or production processes, motion control for driverless cars and drones, and tactile interaction applications such as remote repair and remote surgery.
  • the main features of these services are ultra-high reliability. Low latency, low data transfer and burstiness.
  • Typical mMTC services include: smart grid distribution automation, smart city, etc. The main features are huge number of networked devices, small amount of transmitted data, and insensitive data transmission delay. These mMTC terminals need to meet low cost and very long standby. The demand for time.
  • the URLLC service requires extremely high latency. For example, if the reliability is not considered, the transmission delay is required to be within 0.5 milliseconds (millisecond, ms). Under the premise of 99.999% reliability, the transmission delay is required to be 1 ms. Within. Different services have different requirements for mobile communication systems. How to better support the data transmission requirements of multiple different services at the same time is one of the technical problems that need to be solved in current 5G mobile communication systems.
  • the smallest scheduling time unit is a transmission time interval (TTI) with a time length of 1 ms.
  • TTI transmission time interval
  • the data transmission of the wireless air interface can use a shorter scheduling time unit.
  • slot based scheduling and non-slot based scheduling may be supported, wherein one time slot may include 12 or 14 time domain symbols, where time The domain symbol may be an orthogonal frequency division multiplexing (OFDM) symbol, or may be a discrete Fourier transform spread OFDM (DFTS-OFDM) symbol.
  • OFDM orthogonal frequency division multiplexing
  • DFTS-OFDM discrete Fourier transform spread OFDM
  • a long scheduling time unit is usually used for data transmission to improve transmission efficiency, for example, one time slot with 15 kHz subcarrier spacing, corresponding to 12 or 14 time slots.
  • the domain symbol corresponds to a length of 1 ms.
  • the URLLC service data usually uses a shorter scheduling time unit to meet the requirements of ultra-short delay, for example, two time domain symbols with 15 kHz subcarrier spacing, or seven time domain symbols with 60 kHz subcarrier spacing.
  • the generation of data packets of the URLLC service is bursty and random, and may not generate data packets for a long period of time, or may generate multiple data packets in a short time.
  • the characteristics of the data packets of the URLLC service affect the way in which the transmission resources are allocated in the communication system.
  • Transmission resources herein include, but are not limited to, time domain symbols, frequency domain resources, time-frequency resources, codeword resources, and beam resources.
  • the allocation of transmission resources is done by the network device. If the network device allocates transmission resources for the URLLC service by using reserved resources, the transmission resources reserved when no URLLC service data needs to be transmitted are wasted.
  • the short delay feature of the URLLC service requires that the data packet is transmitted in a very short time, so the network device needs to reserve a sufficient bandwidth for the URLLC service, thereby causing a serious decrease in the utilization of the transmission resource.
  • the resource size reserved for the uplink URLLC service may be appropriately reduced, and the URL-based service that can tolerate a certain transmission delay adopts an authorization-based transmission mode, that is, a scheduling-based transmission mode.
  • the eMBB service adopts slot-based scheduling, when there is a URLLC service that needs to allocate transmission resources, the URLLC service may be allocated without resources due to the eMBB service being transmitted. At this time, part or all of the allocated time-frequency resources for transmitting the eMBB service data may be used to transmit the URLLC service data in a preemptive manner.
  • the network device needs to send an uplink preemption indication to the terminal device in order to prevent the eMBB terminal device from transmitting on the preempted time-frequency resource in time to avoid interference of the eMBB service data to the URLLC service data.
  • the terminal device in order to detect the uplink preemption indication in time, the terminal device needs to perform blind detection on the uplink preemption indication in time, thereby increasing the number of blind detections of the terminal device.
  • the maximum number of blind detections of the downlink control information by the terminal device is fixed. When the terminal device consumes excessive blind detection times on the uplink preemption indication, the number of blind detections of the downlink control information by the terminal device is affected. Thereby affecting the performance of the terminal device.
  • the present application provides a method for transmitting control information, which can reduce the blind detection overhead of the chip of the terminal device or the terminal device for the uplink preemption indication.
  • a control information transmission method includes: receiving first control information from a network device, where the first control information is used to indicate that the uplink data is sent on the first time-frequency resource; and determining, according to the first time-frequency resource and the reference uplink resource (RUR)
  • the uplink preemption indication (PI) is monitored, the uplink PI is used to indicate the third time-frequency resource in the RUR, and the third time-frequency resource is the time-frequency resource that stops sending the uplink data.
  • the chip of the terminal device or the terminal device Since the preemption only occurs in the RUR, when the RUR does not overlap with the first time-frequency resource used for uplink data transmission, the chip of the terminal device or the terminal device does not need to monitor the uplink PI. By determining whether the first time-frequency resource overlaps with the RUR, it is determined whether the uplink PI is to be monitored, thereby effectively avoiding blind detection of the uplink PI by the chip of the terminal device or the terminal device that does not need to receive the uplink PI, and reducing the terminal device. Or the blind detection overhead of the chip of the terminal device to the uplink PI.
  • determining, by the first time-frequency resource and the RUR, the monitoring of the uplink PI including: when the first time-frequency resource overlaps with the RUR, determining to monitor the uplink PI; And/or, when the first time-frequency resource does not overlap with the RUR, it is determined that the uplink PI is not monitored.
  • the control information transmission method further includes: receiving second control information from the network device, where the second control information is used to indicate that the uplink PI is monitored or whether the uplink PI is performed. Monitoring, the second control information can be carried by signaling.
  • the frequency domain of the RUR is a part or all of the frequency range of the first bandwidth part (BWP), and the first BWP is a BWP for transmitting uplink data.
  • BWP bandwidth part
  • control information transmission method further includes: receiving third control information from the network device, where the third control information is used to indicate a time domain range, a time domain location, and a frequency domain of the RUR. At least one of a range, a frequency domain location, and a time-frequency location.
  • the network device can flexibly configure the time domain location information of the RUR.
  • control information transmission method further includes: receiving fourth control information from the network device, where the fourth control information is used to indicate an opportunity to monitor the uplink PI.
  • the network device can flexibly configure the monitoring timing of the uplink PI, thereby effectively controlling the blind detection overhead of the chip of the terminal device or the terminal device to the uplink PI.
  • the time range of the RUR is the nth time domain symbol to the mth time domain symbol after the timing of monitoring the uplink PI, where n and m are positive integers. And n is less than or equal to m, where the time domain symbol is a time domain symbol for uplink data transmission.
  • the timing of monitoring the uplink PI is located in an nth time domain symbol before the RUR start symbol, where n is a positive integer.
  • the uplink PI is an uplink PI of the neighboring cell.
  • the neighboring cell here refers to the neighboring cell of the terminal device, that is, the terminal device can receive the downlink signal of the neighboring cell and/or the uplink signal sent by the terminal device can be received by the network device that manages the neighboring cell.
  • the terminal device determines whether to stop transmitting data on the time-frequency resource indicated by the uplink PI of the neighboring cell according to whether the first time-frequency resource overlaps with the RUR of the neighboring cell by receiving the uplink PI of the neighboring cell.
  • the interference of the uplink data sent by the terminal device to the uplink URL LC service data sent by the terminal device in the neighboring cell can be reduced.
  • a control information transmission method is provided, and an execution body of the method may be a network or a chip or component for a network device.
  • the method is a method corresponding to the first aspect or any possible implementation of the first aspect, and thus the advantageous effects of the first aspect or any possible implementation of the first aspect can also be achieved.
  • the method includes: generating second control information, where the second control information is used to indicate that the uplink PI is monitored, the uplink time PI is used to indicate the third time-frequency resource in the RUR, and the third time-frequency resource is used to stop sending the uplink data. a resource; transmitting the second control information.
  • the frequency domain of the RUR is a part or all of the frequency range of the first BWP, and the first BWP is a BWP for transmitting the uplink data.
  • the method further includes: sending third control information, where the third control information is used to indicate a time domain range, a time domain location, a frequency domain range, a frequency domain location, and a time of the RUR. At least one of the frequency positions.
  • the method further includes: sending fourth control information, where the fourth control information is used to indicate an opportunity to monitor the uplink PI.
  • the time range of the RUR is the nth time domain symbol to the mth time domain symbol after the timing of monitoring the uplink PI, where n and m are positive integers. And n is less than or equal to m, and the time domain symbol is a time domain symbol for uplink data transmission.
  • the timing of monitoring the uplink PI is located in an nth time domain symbol before the RUR start symbol, where n is a positive integer.
  • a communication device for performing the unit, module or circuit of the method of the first aspect or any of the possible implementations of the first aspect.
  • a communication device for performing a unit, module or circuit of the method of any of the above-described second or second aspects of the second aspect.
  • a communication device including a processor, and optionally, a memory.
  • the memory may be used to store computer programs or instructions, and may also be used to store intermediate data processed by the processor; the processor may be used to execute computer programs or instructions for memory storage, or may be used to perform storage or firmware in the processor.
  • the processor and the memory communicate with each other through an internal connection path.
  • a computer readable storage medium for storing a computer program or instructions that, when executed on a computer, cause the computer to perform any of the first aspect or any of the possible implementations of the first aspect The method of the method, or the method of any of the possible implementations of the second aspect or the second aspect described above.
  • a computer program product which, when run on a computer, causes the computer to perform the method of any of the first aspect or the first aspect of the first aspect, or to perform the second or second aspect A method in any possible implementation of the aspect.
  • FIG. 1 is a schematic structural diagram of a mobile communication system to which an embodiment of the present application is applied;
  • FIG. 2 is a schematic flowchart of preempting time-frequency resources used for transmitting eMBB service data by uplink URLLC service data;
  • FIG. 3 is a schematic diagram of a method for transmitting control information according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a relationship between a first time-frequency resource and a reference uplink resource
  • FIG. 5 is a schematic diagram of another method for transmitting control information according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a time-frequency location of a reference uplink resource according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a positional relationship between an uplink PI monitoring opportunity and a reference uplink resource according to an embodiment of the present application
  • FIG. 8 is a schematic diagram of a positional relationship between another uplink PI monitoring opportunity and a reference uplink resource according to an embodiment of the present application
  • FIG. 9 is a schematic diagram of a method for resource allocation of a reference uplink resource according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic diagram of an inter-cell cooperation scenario provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of another method for transmitting control information according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of still another method for transmitting control information according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of another communication apparatus according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic structural diagram of still another communication apparatus according to an embodiment of the present application.
  • FIG. 1 is a schematic structural diagram of a mobile communication system to which an embodiment of the present application is applied.
  • the mobile communication system includes a core network device 110, a radio access network device 120, and at least one terminal device (such as the terminal device 130 and the terminal device 140 in FIG. 1).
  • the terminal device is connected to the radio access network device by means of a wireless connection, and the radio access network device is connected to the core network device by wireless or wired.
  • the core network device and the wireless access network device may be independent physical devices, or may integrate the functions of the core network device with the logical functions of the wireless access network device on the same physical device, or may be a physical device.
  • the functions of some core network devices and the functions of some wireless access network devices are integrated.
  • the terminal device can be fixed or mobile.
  • FIG. 1 is only a schematic diagram, and the communication system may further include other network devices, such as a wireless relay device and a wireless backhaul device, which are not shown in FIG. 1.
  • the embodiment of the present application does not limit the number of core network devices, radio access network devices, and terminal devices included in the mobile communication system.
  • the radio access network device is an access device that the terminal device accesses to the mobile communication system by using a wireless device, and may be a base station NodeB, an evolved base station eNodeB, a 5G mobile communication system, or a new radio (NR) communication system.
  • a radio access network device is referred to as a network device.
  • a network device refers to a radio access network device.
  • 5G and NR may be equivalent.
  • the terminal device may also be referred to as a terminal terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), and the like.
  • the terminal device can be a mobile phone, a tablet, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, and an industrial control (industrial control).
  • Wireless terminal wireless terminal in self driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless in transport safety A terminal, a wireless terminal in a smart city, a wireless terminal in a smart home, and the like.
  • Radio access network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or on-board; they can also be deployed on the water; they can also be deployed on aircraft, balloons and satellites in the air.
  • the application scenarios of the radio access network device and the terminal device are not limited.
  • the radio access network device and the terminal device and the terminal device and the terminal device and the terminal device can communicate through a licensed spectrum, or can communicate through an unlicensed spectrum, or can simultaneously pass the licensed spectrum and Authorize the spectrum for communication.
  • Communication between the radio access network device and the terminal device and between the terminal device and the terminal device may be performed through a spectrum of 6 gigahertz (GHz) or less, or may be communicated through a spectrum of 6 GHz or higher, or may be used below 6 GHz.
  • the spectrum communicates with the spectrum above 6 GHz.
  • the embodiment of the present application does not limit the spectrum resources used between the radio access network device and the terminal device.
  • the network device Due to the burstiness of the data of the URLLC service, in order to improve the system resource utilization, the network device usually does not reserve resources for downlink data transmission of the URLLC service.
  • the URLLC service data arrives at the network device, if there is no idle time-frequency resource at this time, the network device cannot wait for the scheduled transmission of the eMBB service data to complete the URLLC service data in order to meet the ultra-short delay requirement of the URLLC service.
  • Schedule The network device can allocate resources for URLLC service data in a preemption manner.
  • the preemption means that the network device selects part or all of the time-frequency resources on the time-frequency resources that have been allocated for transmitting the eMBB service data, and uses the time-frequency resources for transmitting the URLLC service data, and the time-frequency of the network device used for transmitting the URLLC service data.
  • the data of the eMBB service is not sent on the resource.
  • the network device may send a preemption indication (PI) to the terminal device to notify the eMBB terminal device of the preempted resource location.
  • PI preemption indication
  • RDR reference downlink resource
  • the eMBB terminal device with the transmission resource being preempted can clear the data on the preempted resource from the cache, and avoid the part of the data participating in the decoding and HARQ merging, thereby improving the transmission performance of the eMBB service data.
  • the uplink URLLC service data can be transmitted in two ways.
  • the first one is a grant-free (GF) transmission mode. That is, the system pre-defines some GF resources.
  • the terminal device uses the GF resource to transmit the URLLC service data to the network device;
  • the second is the grant based (GB) transmission mode, that is, when the terminal device has the URLLC service data to be transmitted to the network device, the terminal device sends the network device to the network device.
  • a scheduling request (SR) is sent, and then the network device allocates an uplink transmission resource to the terminal device, and the terminal device transmits the URLLC service data to the network device by using the uplink transmission resource allocated by the network device.
  • SR scheduling request
  • the GF transmission mode of the URLLC service data can reduce the transmission delay. However, since the GF resource needs to be reserved, the transmission efficiency is lower than that of the GB transmission mode. For some specific URLLC service data, if it can tolerate a certain transmission delay, you can consider the GB transmission mode to improve transmission efficiency.
  • the network device may allocate a part to the eMBB terminal device.
  • the transmission resource is allocated to the URLLC terminal device for transmitting the URLLC service data to reduce the waiting delay of the URLLC service data.
  • the URLLC terminal device refers to a terminal device that has URLLC service data to be transmitted to the network device
  • the eMBB terminal device refers to a terminal device that has eMBB service data to be transmitted to the network device.
  • the URLLC terminal device and the eMBB terminal device may be the same terminal device or different terminal devices.
  • the terminal device may be referred to as a URLLC terminal device or an eMBB terminal device.
  • the network device after receiving the SR1 sent by the eMBB terminal device at time t1, the network device allocates uplink time-frequency resource A to the eMBB terminal device by using downlink control information (DCI) at time t1+n1.
  • the DCI sent to the eMBB terminal device is recorded as DCI1.
  • the eMBB terminal device After receiving the DCI1 sent by the network device, the eMBB terminal device sends the eMBB service data to the network device at the time t1+n1+n2.
  • the minimum scheduling time unit of the eMBB service data is one time slot.
  • the network device When the network device receives the SR2 sent by the URLLC terminal device at time t2, and finds that there is no available transmission resource, the network device sends an uplink PI to the eMBB terminal device at time t2+m0, which is used to indicate that the uplink time-frequency resource B is the URLLC terminal device. Preemption, used to transmit URLLC service data.
  • the uplink time-frequency resource B may be part or all of the uplink time-frequency resource A, and the uplink time-frequency resource B may also overlap with the uplink time-frequency resource A. In the present application, the overlap includes complete coincidence and partial overlap.
  • the eMBB terminal device After receiving the uplink PI, the eMBB terminal device stops transmitting data on the time-frequency resource C where the time-frequency resource B and the time-frequency resource A overlap, so as to avoid the eMBB service data and the URLLC service on the same time-frequency resource C. Data, causing serious interference with each other.
  • the network device sends DCI2 to the URLLC terminal device at time t2+m1, and allocates time-frequency resource D for transmitting URLLC service data.
  • the uplink time-frequency resource D may be part or all of the uplink time-frequency resource B, and the time-frequency resource D may also overlap with the time-frequency resource B.
  • the URLLC terminal device After receiving the DCI2 sent by the network device, the URLLC terminal device sends the URLLC service data to the network device at time t2+m1+m2.
  • t1, t2, n1, n2, m0, m1, m2 are all positive real numbers, t1 is smaller than t2, and the relationship between m0 and m1 is not limited, that is, m0 may be equal to m1, may be smaller than m1, or may be greater than m1.
  • t1+n1+n2 is less than or equal to t2+m1+m2, and the relationship between t1+n1 and t2, t1+n1 and t2+m0 is not limited.
  • the uplink PI may be sent to a terminal device that is preempted by a certain resource, or may be sent to a certain group of terminal devices, or may be sent to all terminal devices in the cell.
  • the uplink PI can be used as a Downlink Control Information (DCI) in a specific format, or as a field in a DCI of a certain format.
  • DCI is carried in a Physical Downlink Control Channel (PDCCH) and sent by the network device to the terminal device.
  • PDCH Physical Downlink Control Channel
  • the terminal device In order to confirm whether the network device sends a certain format of DCI to the network device, the terminal device needs to perform blind detection (BD) on the DCI on the time-frequency resource that may appear on the PDCCH at the time corresponding to the monitoring timing of the DCI. .
  • the success of the DCI blind check is usually judged by the success of the cyclic redundancy check (CRC).
  • CRC cyclic redundancy check
  • the CRC check fails, it indicates that the DCI is sent to the terminal device; when the CRC check fails, the network device may not send the DCI, or the DCI sent by the network device may not be sent to the terminal device. It is also possible that the received signal quality of the PDCCH is too poor to be correctly decoded.
  • the monitor and the detect are not strictly distinguished and can be replaced with each other.
  • the eMBB terminal device determines the data transmission behavior according to the uplink PI. For example, the uplink data on the time-frequency resource indicated by the uplink PI may be stopped, or the uplink data on the time-frequency resource indicated by the uplink PI may be suspended or delayed.
  • the transmitting parameter may also change the transmission parameter of the uplink data on the time-frequency resource indicated by the uplink PI, where the transmission parameter may include at least one of a transmission power of the data, a modulation and coding scheme, and a data mapping. Therefore, the uplink PI needs to be sent to the eMBB terminal device whose resources are preempted in time. Correspondingly, the eMBB terminal device also needs to perform blind detection on the DCI carrying the uplink PI in time.
  • the detection timing of the DCI carrying the uplink PI may be defined as that each time domain symbol is detected once, that is, the DCI carrying the uplink PI may appear in any time domain symbol.
  • the eMBB terminal device needs to blindly check the DCI carrying the uplink PI in each time domain symbol, which consumes a large amount of blind detection resources, so that the eMBB terminal device does not have enough resources to go.
  • Blind detection of DCI in other formats another problem is that the eMBB terminal device may increase the power consumption of the eMBB terminal device due to the increase in the number of blind detections.
  • the control information transmission method provided by the embodiment of the present application relates to the second communication device transmitting control information to the first communication device for reducing the number of blind detections of the control information by the first communication device.
  • the first communication device may be a terminal device, or may be a chip or component that can be used for the terminal, and the second communication device may be a network device or a chip or component that can be used for the network device.
  • the control information transmission method may be applicable to a scenario in which the second service data preempts the transmission resource that has been allocated to the first service data in the uplink data transmission.
  • the first service data and the second service data may be two different service data from the same terminal device or from two different terminal devices, such as two different types of service data, or the same type but quality of service (
  • the quality of service (QoS) requires different service data, which is not limited by the embodiment of the present application.
  • the first service data is the eMBB service data
  • the second service data is the URLLC service data
  • the first communication device is the terminal device
  • the second communication device is the network device.
  • the first service data may also be mMTC service data.
  • the specific types of the first service data and the second service data are not limited in this application.
  • the specific names of the first communication device and the second communication device are not limited in this application. It can be understood that the first service data can be carried by the first data channel, and the second service data can be carried by the second data channel, and the first time-frequency resource resource used for transmitting the first service data can be understood as the first data.
  • the first time-frequency resource of the channel, the second time-frequency time-frequency resource allocated to the second service data can be understood as the second time-frequency resource allocated to the second data channel, and the first service data is used for the second service data time-frequency resource.
  • the preemption can be understood as the preemption of the time-frequency resource of the second data channel by the first data channel.
  • a reference uplink resource may be defined.
  • the uplink PI is used to indicate third time-frequency resource information within the RUR.
  • the third time-frequency resource may be time-frequency resource information for stopping the transmission of the uplink data, time information for stopping the transmission of the uplink data, or time-frequency resource information for changing the transmission parameter.
  • the time information may be location information of a time domain symbol that stops transmitting uplink data, or may be a start time domain symbol location information that stops sending uplink data, where the transmission parameters may include: data transmission power, modulation and coding scheme, and data mapping. At least one of them.
  • the RUR can also be understood as an uplink time-frequency resource in which resource preemption may occur.
  • the corresponding third time-frequency resource is an uplink time-frequency resource in which resource preemption has occurred.
  • the third time-frequency resource may be continuous or discrete in the time domain, and may be continuous or discrete in the frequency domain.
  • the indication granularity of the uplink PI may be inconsistent with the time-frequency resource that is actually preempted, which may cause the time-frequency resource indicated by the uplink PI to have only part of the time-frequency. Resources are preempted.
  • the indication granularity of the uplink PI is 6 resource blocks (RBs), but only the time-frequency resources of only 2 RBs are preempted.
  • stopping the transmission of the uplink data may also be understood as the resource for transmitting the uplink data is reconfigured. For example, after the third time-frequency resource is reconfigured, it is no longer used for transmitting the uplink data.
  • the uplink PI may be used to indicate the time-frequency resource that is affected in the RUR in the uplink data transmission of the terminal device, and notify the terminal device to stop sending the uplink data in time on the third time-frequency resource indicated by the uplink PI, or notify the terminal device to The transmission parameter is adjusted on the third time-frequency resource indicated by the uplink PI.
  • the time-frequency resources that are affected in the uplink data transmission include the time-frequency resources that are preempted by other service data, and may also include reserved resources, or may be any other scenario that the terminal device stops transmitting uplink data or adjusts the transmission.
  • the time-frequency resource of the parameter In the embodiment of the present application, the foregoing line PI is used to indicate the time-frequency resource that is preempted in the RUR as an example, but the application does not limit this.
  • the present application provides a control information transmission method for reducing blind detection of an uplink PI by a terminal device.
  • the network device sends the first control information to the terminal device.
  • the terminal device receives the first control information from the network device.
  • the first control information is used to indicate that the terminal device sends uplink data on the first time-frequency resource.
  • the terminal device may determine, according to the first time-frequency resource and the RUR, whether to monitor the uplink PI or determine that the uplink PI is not monitored.
  • the first time-frequency resource may be allocated to the network device for transmitting time-frequency resources of the eMBB service data.
  • the condition 1 here refers to whether the first time-frequency resource overlaps with the RUR.
  • the terminal device determines that the uplink PI is not monitored. Because the uplink preemption only occurs in the RUR, when the condition is not met, the terminal device does not need to monitor the uplink PI.
  • the terminal device does not need to monitor the uplink PI.
  • the uplink feedback can be used as a special uplink data transmission, which is equivalent to the uplink data transmission.
  • the uplink feedback here includes a hybrid automatic repeat request (HARQ) acknowledgement (ACK) and a negative acknowledgement (NACK), and may also include channel state information (CSI). Feedback.
  • HARQ hybrid automatic repeat request
  • NACK negative acknowledgement
  • CSI channel state information
  • the present application further provides another control information transmission method for reducing blind detection of the uplink PI by the terminal device.
  • the network device sends second control information to the terminal device.
  • the terminal device receives the second control information from the network device.
  • the second control information is used to indicate that the terminal device monitors the uplink PI or indicates whether the terminal device monitors the uplink PI, and the second control information can be carried by using the signaling.
  • the signaling may be radio resource control (RRC) signaling, physical layer signaling, or medium access control signaling.
  • RRC radio resource control
  • the signaling may be sent to a specific terminal device; or may be group signaling, that is, sent to a group of terminal devices; or may be broadcast signaling, that is, sent to all terminal devices in the cell.
  • the physical layer signaling may be a DCI, for example, may be a DCI sent to the eMBB terminal device for scheduling uplink data transmission, that is, when the eMBB terminal device is scheduled to perform uplink data transmission, indicating whether the eMBB terminal device needs to uplink. PI is monitored.
  • the terminal device determines, according to the second control information, that the uplink PI is monitored or that the uplink PI is not monitored.
  • the second control information may have a value, for example, the value is a first value, indicating that the terminal device monitors the uplink PI, and the second control information may also take two values, for example, the value is the first value.
  • the terminal device is configured to monitor the uplink PI, and the value is a second value used to indicate that the terminal device does not monitor the uplink PI.
  • the first value may be 1, and the second value may be 0; or, the first value is 0, and the second value is 1.
  • the condition 2 herein refers to whether the terminal device receives the second control information or whether the value of the second control information received by the terminal device is the first value. It can be understood that the condition 2 can be used separately, that is, as long as the condition 2 is satisfied, the terminal device monitors the uplink PI at the time corresponding to the monitoring timing of the uplink PI; when the condition 2 is not met, the terminal device does not receive the second. When the value of the control information or the received second control information is not the first value, the terminal device does not monitor the uplink PI. Condition 2 can also be used in combination with other conditions in the embodiments of the present application.
  • the terminal device monitors the uplink PI at the time corresponding to the monitoring timing of the uplink PI; When one or one of the conditions 2 is not satisfied, the terminal device does not monitor the uplink PI.
  • the second control information and the first control information may be carried in the same DCI, that is, the second control information is carried in the DCI that schedules the uplink data.
  • the embodiment of the present application monitors the uplink PI by signaling the semi-static or dynamic notification terminal device, and can specifically notify which terminal devices need to monitor the uplink PI, thereby effectively avoiding terminal devices that do not need to receive the uplink PI. Blind detection of the uplink PI.
  • the present application does not limit the time-frequency position of the RUR, and the RUR may be continuous at the time-frequency position, as shown in (A) and (C) of FIG. 6; the RUR may also be discrete at the time-frequency position.
  • the RUR may be part of the frequency band in the frequency domain, as shown in (A), (C), and (D) in FIG. 6; the RUR may also be across the entire frequency band in the frequency domain, as shown in FIG. 6 ( B); RUR can be continuous in the frequency domain, as shown in Figure 6; RUR can also be discrete in the frequency domain, not shown in Figure 6.
  • RUR can be continuous or discrete in the time domain.
  • the frequency band here can be a subband or an upstream BWP.
  • the frequency range of the RUR in the embodiment of the present application may be the entire frequency range of the first bandwidth part (BWP), where the first BWP is a BWP for transmitting uplink data.
  • a plurality of terminal devices that activate the same BWP may form a group of terminal devices.
  • the network device sends the same group common uplink PI.
  • the group of public uplink PIs can be scrambled using a group of public radio network temporary identifiers (RNTIs).
  • the terminal device can monitor only the uplink PI corresponding to the first BWP.
  • the uplink PI may not be distinguished by the RNTI, but different terminal devices are configured with different search spaces, and each search space corresponds to one uplink PI and RUR.
  • the terminal device determines the packet according to the configured search space, or determines the search space according to the grouping. Which group the terminal device belongs to can be indicated by signaling.
  • the frequency domain range of the RUR in the embodiment of the present application may also be a partial frequency domain range of the first BWP.
  • the relationship between the uplink PI and the RUR is described below.
  • the uplink PI and the RUR may have a one-to-one relationship, a one-to-many relationship, or a many-to-one relationship.
  • the relationship between the uplink PI and the RUR can also be understood as the relationship between the monitoring timing of the uplink PI and the RUR or the relationship between the search space and the RUR, and therefore, relates to the relationship between the uplink PI and the RUR.
  • the uplink PI, the time domain location of the uplink PI, and the monitoring timing or search space of the uplink PI may be interchanged.
  • the RUR corresponding to the monitoring timing of an uplink PI may be referred to as a RUR, and the time-frequency position of the RUR may be continuous or discrete, as shown in FIG. 6.
  • the RUR is split into multiple RURs by multiple uplink PI monitoring opportunities in one time unit.
  • a time unit here can be one or more time slots.
  • an uplink PI is in one-to-one correspondence with a RUR, and each uplink PI is sent in a previous symbol of its corresponding RUR.
  • the monitoring timing of the uplink PI is located on a discontinuous symbol. Taking one time slot as an example, as shown in FIG. 7, it is assumed that the monitoring timing of the uplink PI is located in symbol 0, symbol 3, symbol 6, symbol 9, and symbol 12 in one slot.
  • the first RUR is located in symbol 1 and symbol 2; the second RUR is located in symbol 4 and symbol 5; the third RUR is located in symbol 7 and symbol 8; the fourth RUR Located at symbol 10 and symbol 11; the fifth RUR is at symbol 13.
  • the monitoring timing of the uplink PI is located at symbol 0, symbol 3, symbol 6 and symbol 9; correspondingly, the first RUR is located at symbol 1 and symbol 2; the second RUR is located at symbol 4 and symbol 5 The third RUR is located at symbol 7 and symbol 8; the fourth RUR is located at symbol 10, symbol 11, symbol 12, and symbol 13.
  • the monitoring timing of the uplink PI is located in symbol 3, symbol 6, symbol 9 and symbol 12 in one slot; correspondingly, the first RUR is located in symbol 4 and symbol 5; the second RUR is located in the symbol 7 and symbol 8; the third RUR is located at symbol 10 and symbol 11; the fourth RUR is at symbol 13.
  • the monitoring timing of the uplink PI is located in symbol 3, symbol 6 and symbol 9 in one slot; correspondingly, the first RUR is located in symbol 4 and symbol 5; the second RUR is located in symbol 7 and symbol 8; The third RUR is located at symbol 10, symbol 11, symbol 12, and symbol 13.
  • the symbols in one time slot may be numbered from 1 or may be numbered from 0, which is not limited in this application.
  • symbols refer to time domain symbols, and may be OFDM symbols or DFTS-OFDM symbols.
  • symbols refer to time domain symbols, and may be OFDM symbols or DFTS-OFDM symbols.
  • the terminal device only needs to monitor the uplink PI on the time domain symbol corresponding to the uplink PI monitoring occasion in the time domain, so that the blind detection overhead of the terminal device to the uplink PI can be effectively reduced.
  • the time range of the RUR corresponding to an uplink PI is very narrow, only one or two time domain symbols are used, and the number of bits required by the corresponding uplink PI to indicate that the resource is preempted may be relatively small, which is beneficial to improving the uplink. PI reliability and transmission efficiency.
  • a further possible design is that, as shown in Figure 8, different RURs overlap on time-frequency resources.
  • the monitoring timing of the uplink PI is the same as that of FIG. 7, but the time domain position of the RUR is a symbol after the monitoring timing of the corresponding uplink PI to the end of the time slot.
  • the present application also provides a method of determining the time-frequency location of the RUR.
  • the time-frequency location of the RUR can be predefined by the protocol. For example, the time-domain symbol in which the protocol pre-defined RUR is located, and the frequency range of the RUR is BWP.
  • This method of predefining the time-frequency location of the RUR can reduce signaling overhead.
  • the time-frequency location of the RUR may also be to notify the terminal device by signaling after the network device determines.
  • the signaling can notify the time-frequency location of the specific RUR, or it can be a predefined configuration.
  • the signaling notification only carries the index or number of the RUR configuration. Dynamic or semi-static configuration of the time-frequency location of the RUR can make the scheduling of network devices more flexible and resource utilization higher.
  • the time-frequency location of the RUR includes the time domain location and the frequency domain location.
  • the time domain range can also be used to represent its time domain location; for the frequency domain continuous RUR, the frequency domain range can be represented by the frequency domain range.
  • the time-frequency location of the RUR is also determined by the following method: the time domain location protocol of the RUR is predefined, and the frequency domain location of the RUR is signaled to the terminal device by the network device; or the frequency domain location protocol of the RUR is predefined, and the time of the RUR The location of the domain is signaled to the terminal device by the network device; or the frequency domain location protocol of the RUR is predefined, and the time domain location of the RUR is determined by the monitoring timing of the RUR uplink PI.
  • the time domain of the RUR ranges from the nth time domain symbol to the mth time domain symbol after the timing of monitoring the uplink PI, where n and m are positive integers, and n is less than or equal to m, where the time domain is The symbol is a time domain symbol for uplink data transmission; or, the time domain range of the RUR is between a first timing for monitoring the uplink PI and a second timing for monitoring the uplink PI, wherein the first timing and the The second timing is adjacent, and the time domain start position of the first timing is earlier than the time domain start position of the second timing.
  • the time domain location of the RUR predefined by the protocol may be, for example, a time slot or a time domain location of the RUR described above.
  • the frequency domain location of the protocol predefined RUR can be a subband or a BWP.
  • the network device may send the third control information to the terminal device by using a signaling, and correspondingly, the terminal device receives the third control information from the network device.
  • the third control information is used to indicate at least one of a time domain range, a time domain location, a frequency domain range, a frequency domain location, and a time-frequency location of the RUR.
  • the application also provides a method of determining the timing of uplink PI monitoring.
  • the monitoring timing of the uplink PI may be a protocol definition, or may be notified to the terminal device by the network device after the determination.
  • the monitoring timing of the specific uplink PI may be notified by signaling, or may be defined by several configurations, and then the index or number of the configuration of the uplink PI monitoring opportunity is notified by signaling. As shown in Table 1, Table 2, Table 3, and Table 4, three upstream PI monitoring timing configurations are defined.
  • the multiple configurations of the monitoring occasions herein may be protocol pre-defined, or may be sent to the terminal device through RRC signaling after the network device determines. By defining the configuration of multiple monitoring opportunities, different monitoring devices are assigned different monitoring opportunities.
  • the monitoring timing is discrete in one time slot, thus effectively reducing the blindness of the terminal device to the uplink PI.
  • the terminal devices of various monitoring occasions in the cell have, correspondingly, there are RURs in each time domain symbol.
  • URLLC service data needs to be transmitted, the time-frequency resources can be preempted in time. The transmission of URLLC business data.
  • the network device may send the fourth control information to the terminal device by using the signaling, and correspondingly, the terminal device receives the fourth control information from the network device, where the fourth control information is used to indicate the terminal device pair.
  • the timing of uplink PI monitoring may indicate a specific monitoring opportunity location, for example, indicating, by using a bit bitmap, which time domain symbols need to monitor the uplink PI in one time slot.
  • the fourth control information may also indicate an index or number of the configuration of the monitoring opportunity.
  • the terminal device may determine the monitoring timing of the uplink PI according to the fourth control information.
  • the monitoring timing of the uplink PI can also be determined by the time domain location of the RUR. For example, the timing at which the terminal device monitors the uplink PI is located in the nth time domain symbol before the RUR start symbol, where n is a positive integer; or the timing at which the terminal device monitors the uplink PI is located at the first RUR and the second Between the RURs, wherein the first RUR and the second RUR are adjacent, and the time domain starting position of the second RUR is earlier than the time domain starting position of the first RUR.
  • the monitoring timing of the uplink PI can also be a time domain range, which is determined by the corresponding RUR. For example, based on the start time point T1 of the RUR. [T1-p, T1-q] is the monitoring timing of the corresponding uplink PI, where p and q are positive numbers, and p is greater than or equal to q, and p is less than T1.
  • the above example is based on the RUR start time point, or it can be based on the end time point.
  • the uplink PI may also be transmitted in the RUR.
  • the above q may also be less than zero.
  • the UE since the UE has a processing time after receiving the PI, it is assumed to be ⁇ . Assuming that the end time point of RUR is T2, then after T2- ⁇ , it is meaningless to receive PI again, so T1-q ⁇ T2- ⁇ can also be limited.
  • the terminal device monitors the uplink PI in one time slot less than or equal to 7 times.
  • the application also provides an indication design of the uplink PI, that is, how the uplink PI indicates the third time-frequency resource in the RUR.
  • the first field used to indicate the third time-frequency resource in the RUR in the uplink PI may adopt a fixed number of bits.
  • the uplink PI includes a length of 2 bits or 4 bits.
  • the field is used to indicate the third time-frequency resource within the RUR.
  • the value of the bit length of the first field needs to be compromised between the indication granularity and the overhead of the uplink PI. The longer the bit length of the first field is, the finer the granularity is, but the larger the overhead of the uplink PI is.
  • the uplink PI may include multiple first fields for indicating third time-frequency resources of respective RURs in multiple carriers, and each carrier corresponds to a first field.
  • the corresponding RUR includes four fourth time-frequency resources, and each bit in the first field corresponds to a fourth time-frequency resource in the RUR.
  • the RUR is divided into four fourth time-frequency resources from the time domain; as shown in (B) of FIG. 9, the RUR is divided into two time units in the time domain, The frequency domain is divided into two frequency domain units, and is divided into four fourth time-frequency resources; as shown in (C) of FIG. 9, the RUR is divided into four fourth time-frequency resources from the frequency domain.
  • the RUR adopts a specific segmentation method, which can be pre-defined by the protocol, or can be notified to the terminal device by signaling after the network device determines.
  • the segmentation method as shown in (A) of FIG. 9 can be adopted, so that the finest indication granularity can be provided in the time domain; when the time domain symbol of the RUR is two In this case, the segmentation method shown in (B) of FIG. 9 may be used, and the third time-frequency resource is indicated in the time domain and the frequency domain; when the time domain symbol of the RUR is one, it may be as shown in FIG. 9.
  • the corresponding RUR includes two fourth time-frequency resources, and each bit in the first field corresponds to a fourth time-frequency resource in the RUR.
  • the RUR is divided into two fourth time-frequency resources from the time domain; as shown in (E) of FIG. 9, the RUR is divided into two fourth time-frequencys from the frequency domain. Resources.
  • the RUR adopts a specific segmentation method, which can be pre-defined by the protocol, or can be notified to the terminal device by signaling after the network device determines. For example, when the time domain symbol of the RUR is four or two, the segmentation method as shown in (D) of FIG. 9 can be adopted; when the time domain symbol of the RUR is one, it can be adopted as shown in FIG. 9 ( E) The segmentation method shown.
  • the present application also provides another indication design of the uplink PI, where the uplink PI indicates the start time of the third time-frequency resource.
  • the terminal device stops transmitting uplink data at the start time indicated by the uplink PI. That is, the uplink PI notifies the time point that the terminal device does not send the uplink data after this time point until the next time it is scheduled to continue to send the uplink data.
  • some time-frequency resources are not allowed to be preempted by uplink data transmission. For example, some special reserved resources, downlink transmission resources in a time division duplex (TDD) system, or some uplink reference signals. Time-frequency resources used, etc. These time-frequency resources that are not allowed to be preempted may be dynamically time-varying or semi-statically configured, so that the RUR may overlap with these time-frequency resources that are not allowed to be preempted. There are two ways to handle it:
  • RUR may include time-frequency resources that are not allowed to be preempted, that is, RUR and time-frequency resources that are not allowed to be preempted may overlap. Assuming that the time-frequency resource that is not allowed to be preempted is the resource A, the RUR in S320 and S1120 in the embodiment of the present application needs to obtain the updated RUR after the resource A is removed, and then perform related condition determination according to the updated RUR.
  • the RUR range is adjusted according to the definition or configuration of the time-frequency resource that is not allowed to be preempted, and the RUR does not overlap with the time-frequency resource that is not allowed to be preempted.
  • the application also provides a control information transmission method in an inter-cell cooperation scenario.
  • a first terminal device in the coverage of the cell A the first terminal device provides the wireless connection service by the cell A; the second terminal device in the coverage of the cell B, and the second terminal device is the cell.
  • B provides a wireless connection service; cell A is adjacent to cell B and the coverage areas of the two cells partially overlap.
  • Cell A and Cell B may be managed by the same network device or by two different network devices. When cell A and cell B are managed by the same network device, the information interaction between cell A and cell B interacts through a message interface or internal circuit inside the network device.
  • cell A and cell B are respectively managed by two different network devices, it is assumed that cell A is managed by the first network device, and cell B is managed by the second network device, and information interaction between cell A and cell B passes through the first A message interface interaction between the network device and the second network device.
  • FIG. 9 Only two scenarios of cell cooperation are shown in FIG. 9, the present application does not limit the number of cells participating in cooperation.
  • the embodiment of the present application is also applicable to a scenario in which the cell A and the cell B are managed by the same network device.
  • the second terminal device When the second terminal device sends the URLLC service data, it also receives the interference of the uplink data sent by the first terminal device located at the coverage edge of the cell A and close to the cell B. Therefore, when the second terminal device preempts the time-frequency resource to perform the URLLC service data transmission, the first terminal device in the cell A also needs to know the time-frequency location at which the second terminal device performs preemption, and the time-frequency resource that is preempted by the second terminal device. The uplink data transmission is stopped at the location, thereby avoiding interference to the URLLC service data of the second terminal device, and improving the reliability of the URLLC service data transmission of the second terminal device.
  • the first terminal device needs to monitor the uplink PI of the cell B sent by the second network device, which we call the second uplink PI.
  • the first terminal device first needs to determine the monitoring timing of the second uplink PI.
  • the monitoring timing of the uplink PI may be predefined by a protocol, or may be notified to the terminal device by signaling after the network device determines, or may be determined according to the RUR. Further, the RUR may also be a protocol pre-defined, or may be notified to the terminal device by signaling after the network device determines.
  • the first terminal device may determine the monitoring timing of the second uplink PI of the cell B transmitted by the second network device according to the definition of the protocol.
  • the first terminal device When the monitoring timing of the uplink PI is that the network device notifies the terminal device by signaling, the first terminal device has two methods to obtain the monitoring timing of the second uplink PI of the cell B: one is to directly receive the relevant signaling of the cell B; The other is that the second network device sends the information about the monitoring occasion of the second uplink PI of the cell B to the first network device, and the first network device sends the information about the monitoring timing of the second uplink PI of the cell B to the first network device. The order is sent to the first terminal device.
  • the first terminal device may determine the second RUR corresponding to the second uplink PI of the cell B according to the definition of the protocol, and then determine the second according to the second RUR. The timing of monitoring the uplink PI.
  • the first terminal device has two methods to determine the monitoring timing of the second uplink PI of the cell B: Directly receiving the relevant signaling of the cell B, acquiring information about the second RUR corresponding to the second uplink PI, and then determining the monitoring timing of the second uplink PI according to the second RUR; and the other is the second network device
  • the information about the second RUR corresponding to the second uplink PI is sent to the first network device, and the first network device sends the information about the second RUR of the cell B to the first terminal device by using the signaling. Then, according to the related information of the second RUR, the monitoring timing of the second uplink PI is determined.
  • the present application provides a method for transmitting control information.
  • the first network device sends the first control information to the first terminal device.
  • the first terminal device receives the first control information from the first network device.
  • the first control information is used to indicate that the first terminal device sends uplink data on the first time-frequency resource.
  • the first terminal device determines, according to the first time-frequency resource and the second RUR, the second uplink PI to be monitored or determines that the second uplink PI is not monitored.
  • the second uplink PI indicates the fifth time-frequency resource information in the second RUR, and the second uplink PI is the uplink PI of the neighboring cell of the first terminal device.
  • the neighboring cell of the first terminal device can be understood as that the first terminal device can receive the downlink signal of the neighboring cell and/or the uplink signal sent by the first terminal device can be received by the network device that manages the neighboring cell. In the scenario shown in FIG. 10, the neighboring cell of the first terminal device refers to cell B.
  • the fifth time-frequency resource may be time-frequency resource information for stopping the transmission of the uplink data, time information for stopping the transmission of the uplink data, or time-frequency resource information for changing the transmission parameter.
  • the first time-frequency resource may be allocated to the first network device for transmitting the time-frequency resource of the eMBB service data.
  • the condition 3 herein refers to whether the first time-frequency resource overlaps with the second RUR.
  • the first terminal device determines that the second uplink PI is not monitored.
  • the first terminal device may also determine whether to monitor the second uplink PI by determining whether the condition 4 is met.
  • Condition 4 here refers to whether the first terminal device can detect the downlink synchronization signal or other reference signals of the neighboring cell. When the first terminal device detects a downlink synchronization signal or other reference signal of the neighboring cell, the condition 4 is considered to be satisfied. It can be understood that the above condition three and condition four can be used singly or in combination. That is, when the condition 3 is satisfied, the first terminal device determines to monitor the second uplink PI; or when the condition 4 is satisfied, the first terminal device determines to monitor the second uplink PI; When the condition 4 is satisfied, the first terminal device determines to monitor the second uplink PI.
  • the present application provides a method for transmitting control information.
  • the first network device sends fifth control information to the first terminal device.
  • the first terminal device receives the fifth control information from the first network device.
  • the fifth control information is used to indicate that the first terminal device monitors the second uplink PI or whether the first terminal device monitors the second uplink PI, and the fifth control information can be carried by signaling.
  • the first terminal device determines, according to the fifth control information, that the second uplink PI is monitored or that the second uplink PI is not monitored.
  • condition 5 refers to whether the first terminal device receives the fifth control information or whether the value of the fifth control information received by the first terminal device is the first value. It can be understood that the condition 5 can be used separately, that is, as long as the condition 5 is satisfied, the first terminal device monitors the second uplink PI at the time corresponding to the monitoring timing of the second uplink PI; when the condition 5 is not satisfied, the first terminal The device determines that the second uplink PI is not monitored.
  • Condition 5 can also be used in combination with Condition 3 and/or Condition 4.
  • the first terminal device determines to monitor the second uplink PI at the time corresponding to the monitoring occasion of the second uplink PI; when one of the condition 3 and the condition 5 is not satisfied, the first A terminal device determines that the second uplink PI is not monitored.
  • the first terminal device determines that the second uplink PI is monitored at a time corresponding to the monitoring occasion of the second uplink PI; when one of the condition 4 and the condition 5 is not satisfied, The first terminal device determines not to monitor the second uplink PI.
  • the first terminal device determines to monitor the second uplink PI at the time corresponding to the monitoring timing of the second uplink PI; when the condition 3, the condition 4, and the condition 5 When any one is not satisfied, the first terminal device determines not to monitor the second uplink PI.
  • the capabilities of different terminal devices may be different. For example, some terminal devices can receive uplink PIs; some terminal devices do not support receiving uplink PIs; some terminal devices can receive uplink PIs in a cell but do not support receiving uplink PIs in neighboring cells; It can receive the uplink PI in the cell and the uplink PI in the neighboring cell.
  • the terminal device may report the capability information of the uplink PI to the network device, where the capability information may include at least one of the following: the uplink PI is not supported, the uplink PI is supported, and the uplink PI in the receiving cell is supported but the receiving is not supported.
  • the uplink PI of the neighboring cell supports the uplink PI in the receiving cell and the uplink PI supporting the neighboring cell, and supports the number of neighboring cells in the uplink PI of the neighboring cell.
  • the number of neighboring cells supporting the uplink PI of the neighboring cell means that the uplink PI of several neighboring cells can be monitored.
  • the control information transmission method provided by the embodiment of the present application is introduced from the perspective of the network device and the terminal device.
  • the network device and the terminal device include corresponding hardware structures and/or software modules for performing respective functions.
  • the embodiments of the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and method steps of the various examples described in the embodiments provided herein. Whether a function is executed by hardware or computer software to drive hardware may depend on the application scenario and design constraints of the technical solution. The technical personnel can use different methods to implement the described functions for different application scenarios, which is not limited in this application.
  • FIG. 13 , FIG. 14 and FIG. 15 are schematic diagrams showing the structures of three possible communication devices according to an embodiment of the present application.
  • the communication device can be used to implement the functions of the terminal device in the foregoing method embodiment, and thus the beneficial effects of the foregoing method embodiments can also be achieved.
  • the communication device may be the terminal device 130 or the terminal device 140 as shown in FIG. 1, or may be a chip applied to the terminal device.
  • the communication device 1300 includes a transceiving unit 1310 and a processing unit 1320.
  • the transceiver unit 1310 is configured to receive first control information, where the first control information is used to indicate that the uplink data is sent on the first time-frequency resource.
  • the processing unit 1320 is configured to determine, according to the first time-frequency resource and the RUR, the uplink PI, where the uplink PI indicates the third time-frequency resource in the RUR, and the third time-frequency resource is the time-frequency resource that stops sending the uplink data.
  • the transceiver unit 1310 is further configured to receive second control information, where the second control information is used to indicate that the uplink PI is monitored.
  • the transceiver unit 1310 is further configured to receive third control information, where the third control information is used to indicate at least one of a time domain range, a time domain location, a frequency domain range, a frequency domain location, and a time-frequency location of the RUR.
  • the transceiver unit 1310 is further configured to receive fourth control information, where the fourth control information is used to indicate an opportunity to monitor the uplink PI.
  • the uplink PI may be an uplink PI of the current cell or an uplink PI of a neighboring cell.
  • the local cell here refers to a cell that provides a wireless connection service for the terminal device, and the neighboring cell refers to a neighboring cell of the terminal device.
  • transceiver unit 1310 and the processing unit 1320 can be directly obtained by referring to the related description of the terminal device in the foregoing method embodiment, and details are not described herein.
  • the communication device 1400 includes a processor 1410, and optionally, a memory 1420.
  • the memory 1420 can be used to store computer programs or instructions, and can also be used to store intermediate data processed by the processor; the processor 1410 can be used to execute computer programs or instructions stored in the memory 1420, and can also be used to perform storage or firmware.
  • the computer program or instructions in processor 1410 when executed by computer 1410, are used to perform the functions of the terminal device as described in the method embodiments.
  • the processor 1410 and the memory 1420 communicate with one another via internal connection paths, such as control and/or data signals can be transmitted over the bus.
  • the embodiment of the present application does not limit the number of the processor 1410 and the memory 1420 included in the communication device 1400.
  • the communication device 1500 includes a processing circuit 1510 for performing the function of the processing unit 1310 in the present embodiment, and a transceiver circuit 1520 for performing the transceiver unit 1320 of the present embodiment.
  • the processing circuit and the transceiver circuit communicate with each other through internal circuits.
  • the terminal device chip When the communication device is a chip of a terminal device, the terminal device chip implements the function of the terminal device in the foregoing method embodiment.
  • the terminal device chip receives information from other modules in the terminal device, such as a radio frequency module or an antenna, and the information is sent by the network device to the terminal device.
  • the communication device shown in FIG. 13 , FIG. 14 and FIG. 15 can also be used to implement the functions of the network device in the foregoing method embodiment, and thus the beneficial effects of the foregoing method embodiments can also be achieved.
  • the communication device may also be the radio access network device 120 as shown in FIG. 1, or may be a chip applied to the radio access network device.
  • the communication device 1300 includes a transceiving unit 1310 and a processing unit 1320.
  • the processing unit 1320 is configured to generate second control information, where the second control information is used to indicate that the uplink PI is monitored, the uplink PI is the third time-frequency resource in the RUR, and the third time-frequency resource is the time-frequency resource that stops sending the uplink data. ;
  • the transceiver unit 1310 is configured to send second control information.
  • the transceiver unit 1310 is further configured to send third control information, where the third control information is used to indicate at least one of a time domain range, a time domain location, a frequency domain range, a frequency domain location, and a time-frequency location of the RUR.
  • the transceiver unit 1310 is further configured to send fourth control information, where the fourth control information is used to indicate an opportunity to monitor the uplink PI.
  • the uplink PI may be an uplink PI of the current cell or an uplink PI of a neighboring cell.
  • transceiver unit 1310 and the processing unit 1320 can be directly obtained by referring to the related description of the network device in the foregoing method embodiment, and details are not described herein.
  • the communication device 1400 includes a processor 1410, and optionally, a memory 1420.
  • the memory 1420 can be used to store computer programs or instructions, and can also be used to store intermediate data processed by the processor; the processor 1410 can be used to execute computer programs or instructions stored in the memory 1420, and can also be used to perform storage or firmware.
  • the computer program or instructions in processor 1410 when executed by computer 1410, are used to perform the functions of the network device as described in the method embodiments.
  • the processor 1410 and the memory 1420 communicate with one another via internal connection paths, such as control and/or data signals can be transmitted over the bus.
  • the embodiment of the present application does not limit the number of the processor 1410 and the memory 1420 included in the communication device 1400.
  • the communication device 1500 includes a processing circuit 1510 for performing the function of the processing unit 1310 in the present embodiment, and a transceiver circuit 1520 for performing the transceiver unit 1320 of the present embodiment.
  • the processing circuit and the transceiver circuit communicate with each other through internal circuits.
  • the network device chip When the communication device is a chip of a network device, the network device chip implements the function of the network device in the foregoing method embodiment.
  • the network device chip sends information to other modules in the network device, such as a radio frequency module or an antenna, and the information is sent to the terminal device.
  • processors in the embodiment of the present application may be a central processing unit (CPU), and may be other general-purpose processors, digital signal processors (DSPs), and application specific integrated circuits. (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof.
  • a general purpose processor can be a microprocessor or any conventional processor.
  • the method steps in the embodiments of the present application may be implemented by means of hardware, or may be implemented by a processor executing software instructions.
  • the software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (Programmable ROM). , PROM), Erasable PROM (EPROM), Electrically Erasable Programmable Read Only Memory (EEPROM), Register, Hard Disk, Mobile Hard Disk, CD-ROM, or well known in the art Any other form of storage medium.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a network device or terminal device.
  • the processor and the storage medium can also exist as discrete components in the transmitting device or the receiving device.
  • the computer program product includes one or more computer programs or instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer program or instructions may be stored in or transmitted by a computer readable storage medium.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server that integrates one or more available media.
  • the usable medium may be a magnetic medium such as a floppy disk, a hard disk, a magnetic tape, or an optical medium such as a DVD, or a semiconductor medium such as a solid state disk (SSD).
  • plural refers to two or more.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character “/” in this article generally indicates that the contextual object is an “or” relationship; in the formula, the character “/” indicates that the contextual object is a "divide” relationship.

Landscapes

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

Abstract

本申请提供了一种控制信息传输方法，涉及无线通信领域。该方法包括：终端设备根据用于传输上行数据的时频资源与参考上行资源RUR之间是否重叠确定是否对上行抢占指示PI进行监测，从而能够有效地避免了那些无需接收上行PI的终端设备对上行PI的盲检，降低了终端设备对上行PI的盲检开销。

Description

控制信息的传输方法
本申请要求于2017年12月29日提交中国国家知识产权局、申请号为201711490121.9、发明名称为“控制信息的传输方法”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明实施例涉及无线通信领域，尤其涉及控制信息的传输方法。
背景技术
5G移动通信系统支持增强型移动宽带(enhanced mobile broadband，eMBB)业务、高可靠低时延通信(ultra reliable and low latency communications，URLLC)业务以及海量机器类通信(massive machine type communications，mMTC)业务。典型的eMBB业务有：超高清视频、增强现实(augmented reality，AR)、虚拟现实(virtual reality，VR)等，这些业务的主要特点是传输数据量大、传输速率很高。典型的URLLC业务有：工业制造或生产流程中的无线控制、无人驾驶汽车和无人驾驶飞机的运动控制以及远程修理、远程手术等触觉交互类应用，这些业务的主要特点是超高可靠性、低延时，传输数据量较少以及具有突发性。典型的mMTC业务有：智能电网配电自动化、智慧城市等，主要特点是联网设备数量巨大、传输数据量较小、数据对传输时延不敏感，这些mMTC终端需要满足低成本和非常长的待机时间的需求。
URLLC业务对时延要求极高，例如：不考虑可靠性的情况下，传输时延要求在0.5毫秒(millisecond，ms)以内；在达到99.999％的可靠性的前提下，传输时延要求在1ms以内。不同业务对移动通信系统的需求不同，如何更好地同时支持多种不同业务的数据传输需求，是当前5G移动通信系统所需要解决的技术问题之一。
在长期演进(long term evolution，LTE)系统中，最小的调度时间单元是时间长度为1ms的传输时间间隔(transmission time interval，TTI)。为了满足URLLC业务的传输时延需求，无线空口的数据传输可以使用更短的调度时间单元。在5G移动通信系统中，可以支持基于时隙的(slot based)调度和基于非时隙的(non-slot based)调度,其中，一个时隙可以包括12或14个时域符号，这里的时域符号可以是正交频分复用(orthogonal frequency division multiplexing，OFDM)符号，也可以是离散傅里叶变换扩展正交频分复用(discrete fourier transform spread OFDM，DFTS-OFDM)符号。当最小的调度时间单元为一个时隙或多个时隙的时候，我们称这种调度为slot based调度。当最小的调度时间单元为非整数个时隙的时候，我们称这种调度为non-slot based调度，例如最小的调度时间单元为两个时域符号。
由于eMBB业务的数据量比较大，而且传输速率比较高，因此通常采用较长的调度时间单元进行数据传输以提高传输效率，例如，采用15kHz子载波间隔的一个时隙，对应12或14个时域符号，对应的时间长度为1ms。URLLC业务数据通常采用较短的调度时间单元，以满足超短时延的需求，例如，采用15kHz子载波间隔的2个时域符号，或者采用60kHz子载波间隔的7个时域符号。
URLLC业务的数据包的产生具有突发性和随机性，可能在很长一段时间内都不会产生数据包，也可能在很短时间内产生多个数据包。URLLC业务的数据包的特性会影 响通信系统中的传输资源的分配方式。这里的传输资源包括但不限于：时域符号、频域资源、时频资源、码字资源以及波束资源等。通常传输资源的分配由网络设备来完成。如果网络设备采用预留资源的方式为URLLC业务分配传输资源，则在无URLLC业务数据需要传输的时候预留的传输资源是浪费的。而且URLLC业务的短时延特性要求数据包在极短的时间内传输完成，所以网络设备需要预留足够大的带宽给URLLC业务，从而导致传输资源的利用率严重下降。
为了提高上行传输资源的利用率，可以适当减少为上行URLLC业务预留的资源大小，而对于那些可以容忍一定传输时延的URLLC业务采用基于授权的传输方式，即采用基于调度的传输方式。但是，由于eMBB业务采用基于时隙的调度，当有URLLC业务需要分配传输资源的时候，可能由于eMBB业务正在传输而导致URLLC业务无资源可以分配。此时，可以采用抢占的方式，将已经分配的、用于传输eMBB业务数据的时频资源的部分或全部用于传输URLLC业务数据。为了及时让eMBB终端设备在被抢占的时频资源上停止发送，避免eMBB业务数据对URLLC业务数据的干扰，网络设备需要给终端设备发送上行抢占指示。对应的，为了及时检测到上行抢占指示，终端设备需要及时对上行抢占指示进行盲检，从而增加了终端设备的盲检次数。而终端设备对下行控制信息的最大盲检次数是一定的，当终端设备在上行抢占指示上消耗了过多的盲检次数的时候，就会影响终端设备对其它下行控制信息的盲检次数，从而影响终端设备的性能。
发明内容
本申请提供了一种控制信息的传输方法，可以降低终端设备或终端设备的芯片对上行抢占指示的盲检开销。
第一方面，提供了一种控制信息传输方法，该方法的执行主体可以是终端设备也可以是用于终端设备的芯片或部件。该方法包括：接收来自网络设备的第一控制信息，第一控制信息用于指示在第一时频资源上发送上行数据；根据第一时频资源和参考上行资源(reference uplink resource，RUR)确定对上行抢占指示(preemption indication，PI)进行监测，上行PI用于在RUR内指示第三时频资源，第三时频资源为停止发送上行数据的时频资源。由于抢占只可能发生在RUR内，所以当RUR与用于上行数据传输的第一时频资源无重叠时，该终端设备或终端设备的芯片无需对上行PI进行监测。通过判断第一时频资源是否与RUR重叠来确定是否要对上行PI进行监测，从而有效地避免了那些无需接收上行PI的终端设备或终端设备的芯片对上行PI的盲检，降低了终端设备或终端设备的芯片对上行PI的盲检开销。
在第一方面的一种可能的实现方式中，根据第一时频资源和RUR确定对上行PI进行监测,包括：当第一时频资源与RUR有交叠时，确定对上行PI进行监测；和/或，当第一时频资源与RUR没有交叠时，确定对上行PI不进行监测。
在第一方面的一种可能的实现方式中，该控制信息传输方法还包括：接收来自网络设备的第二控制信息，第二控制信息用于指示对上行PI进行监测或指示是否对上行PI进行监测，第二控制信息可以通过信令承载。通过信令半静态或动态通知终端设备对上行PI进行监测，可以有针对性地通知哪些终端设备需要对上行PI进行监测，从而有效地避免了那些无需接收上行PI的终端设备对上行PI的盲检。
在第一方面的一种可能的实现方式中，RUR的频域范围为第一带宽部分(bandwidth part，BWP)的部分或全部频域范围，第一BWP为用于传输上行数据的BWP。
在第一方面的一种可能的实现方式中，该控制信息传输方法还包括：接收来自网络设备的第三控制信息，第三控制信息用于指示RUR的时域范围、时域位置、频域范围、频域位置和时频位置中的至少一个。通过这种实现方式，网络设备可以灵活配置RUR的时域位置信息。
在第一方面的一种可能的实现方式中，该控制信息传输方法还包括：接收来自网络设备的第四控制信息，第四控制信息用于指示对上行PI进行监测的时机。通过这种实现方式，网络设备可以灵活配置上行PI的监测时机，从而有效地控制终端设备或终端设备的芯片对上行PI的盲检开销。
在第一方面的一种可能的实现方式中，RUR的时域范围为对上行PI进行监测的时机之后的第n个时域符号到第m个时域符号，其中，n和m为正整数，且n小于等于m，这里的时域符号为用于上行数据传输的时域符号。
在第一方面的一种可能的实现方式中，对上行PI进行监测的时机位于RUR起始符号之前的第n个时域符号，其中，n为正整数。
在第一方面的一种可能的实现方式中，上行PI为邻区的上行PI。这里的邻区是指终端设备的邻区，即该终端设备能够接收到该邻区下行信号和/或该终端设备发送的上行信号能够被管理该邻区的网络设备接收到。终端设备通过接收邻区的上行PI，根据第一时频资源是否与邻区的RUR重叠来判断是否要在邻区的上行PI所指示的时频资源上停止发送数据。通过这种实现方式，能够降低终端设备发送的上行数据对邻区的终端设备发送的上行URLLC业务数据的干扰。
第二方面，提供了一种控制信息传输方法，该方法的执行主体可以是网络也可以是用于网络设备的芯片或部件。该方法是与第一方面或第一方面的任意可能的实现方式相对应的方法，因此也能实现第一方面或第一方面任意可能的实现方式中的有益效果。该方法包括：生成第二控制信息，第二控制信息用于指示对上行PI进行监测，上行PI用于在RUR内指示第三时频资源，第三时频资源为停止发送上行数据的时频资源；发送所述第二控制信息。
在第二方面的一种可能的实现方式中，RUR的频域范围为第一BWP的部分或全部频域范围，第一BWP为用于传输所述上行数据的BWP。
在第二方面的一种可能的实现方式中，该方法还包括：发送第三控制信息，第三控制信息用于指示RUR的时域范围、时域位置、频域范围、频域位置和时频位置中的至少一个。
在第二方面的一种可能的实现方式中，该方法还包括：发送第四控制信息，第四控制信息用于指示对上行PI进行监测的时机。
在第二方面的一种可能的实现方式中，RUR的时域范围为对上行PI进行监测的时机之后的第n个时域符号到第m个时域符号，其中，n和m为正整数，且n小于等于m，时域符号为用于上行数据传输的时域符号。
在第二方面的一种可能的实现方式中，对上行PI进行监测的时机位于RUR起始符号之前的第n个时域符号，其中，n为正整数。
第三方面，提供了一种通信装置，用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的单元、模块或电路。
第四方面，提供了一种通信装置，用于执行上述第二方面或第二方面的任意可能的实现方式中的方法的单元、模块或电路。
第五方面，提供了一种通信装置，包括处理器，可选的，还可以包括存储器。其中，存储器可以用于存储计算机程序或指令，也可以用于存储处理器处理的中间数据；处理器可以用于执行存储器存储的计算机程序或指令，也可以用于执行存储或固化在处理器中的计算机程序或指令，当处理器执行计算机程序或指令时，用于执行如上述第一方面或第一方面的任意可能的实现方式中的方法，或者用于执行如上述第二方面或第二方面的任意可能的实现方式中的方法。处理器和存储器之间通过内部连接通路互相通信。
第六方面，提供了一种计算机可读存储介质，用于存储计算机程序或指令，当该计算机程序或指令在计算机上运行时，使得计算机执行上述第一方面或第一方面的任意可能的实现方式中的方法，或者执行上述第二方面或第二方面的任意可能的实现方式中的方法。
第七方面，提供了一种计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面或第一方面的任意可能的实现方式中的方法，或者执行上述第二方面或第二方面的任意可能的实现方式中的方法。
附图说明
图1为本申请的实施例应用的移动通信系统的架构示意图；
图2为上行URLLC业务数据抢占用于传输eMBB业务数据的时频资源的流程示意图；
图3为本申请实施例提供的一种控制信息传输方法示意图；
图4为第一时频资源与参考上行资源之间的关系示意图；
图5为本申请实施例提供的另一种控制信息传输方法示意图；
图6为本申请实施例提供的参考上行资源的时频位置的示意图；
图7为本申请实施例提供的一种上行PI监测时机与参考上行资源之间的位置关系示意图；
图8为本申请实施例提供的另一种上行PI监测时机与参考上行资源之间的位置关系示意图；
图9为本申请实施例提供的参考上行资源的资源划分方法示意图；
图10本申请实施例提供的一种小区间协作场景示意图；
图11为本申请实施例提供的另一种控制信息传输方法示意图；
图12为本申请实施例提供的又一种控制信息传输方法示意图；
图13为本申请实施例提供的一种通信装置的结构示意图；
图14为本申请实施例提供的另一种通信装置的结构示意图；
图15为本申请实施例提供的又一种通信装置的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述。
图1是本申请的实施例应用的移动通信系统的架构示意图。如图1所示，该移动通信系统包括核心网设备110、无线接入网设备120和至少一个终端设备(如图1中的终端设备130和终端设备140)。终端设备通过无线的方式与无线接入网设备相连，无线接入网设备通过无线或有线方式与核心网设备连接。核心网设备与无线接入网设备可以是独立的不同的物理设备，也可以是将核心网设备的功能与无线接入网设备的逻辑功能集成在同一个物理设备上，还可以是一个物理设备上集成了部分核心网设备的功能和部分的无线接入网设备的功能。终端设备可以是固定位置的，也可以是可移动的。图1只是示意图，该通信系统中还可以包括其它网络设备，如还可以包括无线中继设备和无线回传设备，在图1中未画出。本申请的实施例对该移动通信系统中包括的核心网设备、无线接入网设备和终端设备的数量不做限定。
无线接入网设备是终端设备通过无线方式接入到该移动通信系统中的接入设备，可以是基站NodeB、演进型基站eNodeB、5G移动通信系统或新一代无线(new radio，NR)通信系统中的基站、未来移动通信系统中的基站、WiFi系统中的接入节点等，本申请的实施例对无线接入网设备所采用的具体技术和具体设备形态不做限定。在本申请中，无线接入网设备简称网络设备，如果无特殊说明，在本申请中，网络设备均指无线接入网设备。在本申请中，术语5G和NR可以等同。
终端设备也可以称为终端Terminal、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等。终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality，VR)终端设备、增强现实(Augmented Reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。
无线接入网设备和终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和人造卫星上。本申请的实施例对无线接入网设备和终端设备的应用场景不做限定。
无线接入网设备和终端设备之间以及终端设备和终端设备之间可以通过授权频谱(licensed spectrum)进行通信，也可以通过免授权频谱(unlicensed spectrum)进行通信，也可以同时通过授权频谱和免授权频谱进行通信。无线接入网设备和终端设备之间以及终端设备和终端设备之间可以通过6吉兆赫(gigahertz，GHz)以下的频谱进行通信，也可以通过6GHz以上的频谱进行通信，还可以同时使用6GHz以下的频谱和6GHz以上的频谱进行通信。本申请的实施例对无线接入网设备和终端设备之间所使用的频谱资源不做限定。
【实施例一：单小区场景】
由于URLLC业务的数据的突发性，为了提高系统资源利用率，网络设备通常不会为URLLC业务的下行数据传输预留资源。当URLLC业务数据到达网络设备时，如果此时没有空闲的时频资源，网络设备为了满足URLLC业务的超短时延需求，无法等待将本次调度的eMBB业务数据传输完成之后再对URLLC业务数据进行调度。网络设备可以采用抢 占(preemption)的方式，为URLLC业务数据分配资源。这里的抢占是指网络设备在已经分配的、用于传输eMBB业务数据的时频资源上选择部分或全部的时频资源用于传输URLLC业务数据，网络设备在用于传输URLLC业务数据的时频资源上不发送eMBB业务的数据。
当下行的URLLC业务数据抢占了下行eMBB业务数据的传输资源时，eMBB业务数据的传输质量会受到严重影响。为了降低抢占对eMBB业务数据的传输质量的影响，网络设备可以向终端设备发送一个抢占指示(preemption indication，PI)，用于通知eMBB终端设备被抢占的资源位置。为了简化抢占指示的设计，定义了参考下行资源(reference downlink resource，RDR)，下行抢占指示所指示的是RDR中的部分或全部时频资源被抢占。传输资源被抢占的eMBB终端设备，可以将被抢占的资源上的数据从缓存中清除，避免这部分数据参与译码和HARQ合并，从而提升eMBB业务数据的传输性能。
上行URLLC业务数据可以有两种传输方式，第一种是免授权(grant free，GF)的传输方式，即系统预先定义了一些GF资源，当终端设备有URLLC业务数据需要传输给网络设备时，终端设备使用GF资源将URLLC业务数据传输给网络设备；第二种是基于授权(grant based，GB)的传输方式，即当终端设备有URLLC业务数据需要传输给网络设备时，终端设备向网络设备发送调度请求(scheduling request，SR)，然后由网络设备给终端设备分配上行传输资源，终端设备使用网络设备分配的上行传输资源将URLLC业务数据传输给网络设备。URLLC业务数据采用GF传输方式能降低传输时延，但是由于需要预留GF资源，所以传输效率相对于GB传输方式要低。对于某些特定的URLLC业务数据，如果其可以容忍一定的传输时延，则可以考虑采用GB传输方式，以提升传输效率。
当网络设备收到URLLC终端设备发送的SR时，如果当前没有空闲的传输资源分配给URLLC终端设备，例如，传输资源都分配给eMBB终端设备了，则网络设备可以将一部分已经分配给eMBB终端设备的传输资源分配给URLLC终端设备用于传输URLLC业务数据，以降低URLLC业务数据的等待时延。在本申请中，URLLC终端设备是指有URLLC业务数据需要传输给网络设备的终端设备，eMBB终端设备是指有eMBB业务数据需要传输给网络设备的终端设备。URLLC终端设备和eMBB终端设备可以是同一个终端设备，也可以是不同的终端设备。当某个终端设备既有URLLC业务数据需要传输给网络设备，又有eMBB业务数据需要传输给网络设备，则这个终端设备既可以称为URLLC终端设备，也可以称为eMBB终端设备。
如图2所示，网络设备在t1时刻收到eMBB终端设备发送的SR1之后，在t1+n1时刻通过下行控制信息(downlink control information，DCI)给eMBB终端设备分配上行时频资源A。将发送给eMBB终端设备的DCI记为DCI1。eMBB终端设备收到网络设备发送的DCI1之后，在t1+n1+n2时刻向网络设备发送eMBB业务数据，通常eMBB业务数据的最小调度时间单元为一个时隙。当网络设备在t2时刻收到URLLC终端设备发送的SR2，发现没有可用的传输资源时，网络设备在t2+m0时刻向eMBB终端设备发送上行PI，用于指示上行时频资源B被URLLC终端设备抢占、用于传输URLLC业务数据。上行时频资源B可以为上行时频资源A的一部分或全部，上行时频资源B也可以与上行时频资源 A有交叠。在本申请中，交叠包括完全重合和部分重合。eMBB终端设备收到上行PI之后，将停止在时频资源B与时频资源A重叠的时频资源C上发送数据，以避免在相同的时频资源C上即有eMBB业务数据又有URLLC业务数据，相互之间产生严重干扰。网络设备在t2+m1时刻向URLLC终端设备发送DCI2，分配时频资源D用于传输URLLC业务数据。上行时频资源D可以为上行时频资源B中的一部分或者全部，时频资源D也可以与时频资源B有交叠。URLLC终端设备收到网络设备发送的DCI2之后，在t2+m1+m2时刻向网络设备发送URLLC业务数据。上述t1，t2，n1，n2，m0，m1，m2均为正实数，t1小于t2，m0与m1之间的大小关系不做限定，即m0可以等于m1、也可以小于m1、也可以大于m1，t1+n1+n2小于等于t2+m1+m2，t1+n1与t2、t1+n1与t2+m0之间的大小关系不做限定。
上行PI可以是发送给某一个资源被抢占的终端设备，也可以是发送给某一组终端设备，也可以是发送给小区内所有的终端设备。上行PI可以作为一种特定格式的下行控制信息(Downlink Control Information，DCI)，也可以作为某种格式的DCI中的一个字段。DCI承载在物理下行控制信道(Physical Downlink Control Channel，PDCCH)中，由网络设备发送给终端设备。
终端设备为了确认网络设备是否给自己发送了某种格式的DCI，终端设备需要在该DCI的监测时机对应的时刻在PDCCH可能出现的时频资源上对该DCI进行盲检(blind detection，BD)。DCI盲检是否成功通常是通过循环冗余校验(cyclic redundancy check，CRC)是否成功来判断。当CRC校验成功时，则说明该DCI是发送给该终端设备的；当CRC校验失败时，则可能是网络设备没有发送DCI，也可能是网络设备发送的DCI不是发送给该终端设备的，也可能是PDCCH的接收信号质量太差导致无法正确译码。在本申请中，监测(monitor)和检测(detect)并不做严格区分，可以相互替换。
eMBB终端设备根据上行PI来确定数据传输行为，例如，可以停止上行PI所指示的时频资源上的上行数据的发送，也可以暂停或延后上行PI所指示的时频资源上的上行数据的发送，还可以改变上行PI所指示的时频资源上的上行数据的传输参数，这里的传输参数可以包括数据的发送功率、调制编码方案和数据映射中的至少一个。因此上行PI需要及时发送给资源被抢占的eMBB终端设备。对应的，eMBB终端设备也需要及时对承载上行PI的DCI进行盲检。为了让上行PI更及时地将抢占信息通知到eMBB终端设备，可以将承载上行PI的DCI的检测时机定义为每个时域符号检测一次，即承载上行PI的DCI可以出现在任意一个时域符号。但这样会带来两个问题：一个是，eMBB终端设备需要在每个时域符号对承载上行PI的DCI进行盲检，这样会消耗大量的盲检资源，使得eMBB终端设备没有足够的资源去盲检其它格式的DCI；另一个问题是，eMBB终端设备由于盲检次数的增加会导致eMBB终端设备的功耗增加。
本申请实施例提供的控制信息传输方法涉及第二通信装置向第一通信装置发送控制信息，用于降低第一通信装置对控制信息的盲检次数。第一通信装置可以为终端设备，也可以为可用于终端的芯片或部件，第二通信装置可以为网络设备，也可以为可用于网络设备的芯片或部件。该控制信息传输方法可以适用于上行数据传输中第二业务数据抢占已经分配给第一业务数据的传输资源的场景。第一业务数据和第二业务数据可以是来 自同一终端设备或来自两个不同终端设备的两种不同的业务数据，比如可以是两种不同类型的业务数据，也可以是类型相同但是业务质量(quality of service，QoS)需求不同的业务数据，本申请实施例对此不做限定。
为便于理解和说明，在本申请的各个实施例中以第一业务数据为eMBB业务数据，第二业务数据为URLLC业务数据，第一通信装置为终端设备，第二通信装置为网络设备为例进行说明。第一业务数据也可以为mMTC业务数据，本申请对第一业务数据和第二业务数据的具体类型不做限定，本申请对第一通信装置和第二通信装置的具体名称也不做限定。可以理解的是，第一业务数据可以通过第一数据信道承载，第二业务数据可以通过第二数据信道承载，那么用于传输第一业务数据的第一时频资源资源可以理解为第一数据信道的第一时频资源，分配给第二业务数据的第二时频时频资源可以理解为分配给第二数据信道的第二时频资源，第一业务数据对第二业务数据时频资源的抢占，可以理解为第一数据信道对第二数据信道的时频资源的抢占。
与RDR相对应，为了简化上行PI的设计，可以定义参考上行资源(reference uplink resource，RUR)。上行PI用于在RUR内指示第三时频资源信息。第三时频资源可以是停止发送上行数据的时频资源信息，也可以是停止发送上行数据的时间信息，还可以是改变传输参数的时频资源信息。其中，时间信息可以是停止发送上行数据的时域符号的位置信息，也可以是停止发送上行数据的起始时域符号位置信息，传输参数可以包括：数据的发送功率、调制编码方案和数据映射中的至少一项。RUR也可以理解为可能发生资源抢占的上行时频资源，对应的第三时频资源为已经发生资源抢占的上行时频资源。第三时频资源在时域上可以是连续的也可以是离散的，在频域上可以是连续的也可以是离散的。当上行PI用于指示RUR内被抢占的时频资源时，由于上行PI的指示粒度与实际发生抢占的时频资源之间可能不一致，从而可能导致上行PI所指示的时频资源只有部分时频资源被抢占。例如，上行PI的指示粒度为6个资源块(resource block，RB)，但实际只有2个RB的时频资源被抢占。在本申请中，停止发送上行数据也可以理解为用于发送该上行数据的资源被重新配置了，例如，第三时频资源被重新配置后，不再用于发送该上行数据。
上行PI可以用于指示终端设备的上行数据传输中在RUR内被影响的时频资源，通知终端设备在上行PI所指示的第三时频资源上能及时停止发送上行数据，或者通知终端设备在上行PI所指示的第三时频资源上调整传输参数。这里的上行数据传输中被影响的时频资源包括上面所述的被其它业务数据抢占的时频资源，也可以包括预留资源，也可以是其它任何场景希望终端设备停止发送上行数据或调整传输参数的时频资源。在本申请的实施例中，以上行PI用于指示RUR内被抢占的时频资源为例，但本申请对此并不做限定。
如图3所示，本申请提供了一种控制信息传输方法，用于降低终端设备对上行PI的盲检。
S310，网络设备向终端设备发送第一控制信息。对应的，终端设备接收来自网络设备的第一控制信息。其中，第一控制信息用于指示该终端设备在第一时频资源上发送上行数据。
S320，该终端设备可以根据第一时频资源和RUR确定对上行PI进行监测或确定对 上行PI不进行监测。
具体的，第一时频资源可以为网络设备分配给终端设备用于传输eMBB业务数据的时频资源。如图4中的(A)图所示，当第一时频资源与RUR有交叠时，我们称满足条件一，终端设备确定对上行PI进行监测。可以理解的是，这里的条件一是指第一时频资源与RUR是否有交叠。如图4中的(B)图所示，当第一时频资源与RUR没有交叠时，即不满足条件一，终端设备确定对上行PI不进行监测。因为上行抢占只会发生在RUR内，所以当条件一不满足时，终端设备无需对上行PI进行监测。通过判断第一时频资源是否与RUR重叠来确定是否要对上行PI进行监测，从而有效地避免了那些无需接收上行PI的终端设备对上行PI的盲检。
可以理解的是，如果终端设备没有被调度，或者说，该终端设备没有上行数据传输时，该终端设备无需对上行PI进行监测。当允许对上行反馈进行抢占时，上行反馈可以作为一种特殊的上行数据传输，与上行数据传输等同处理。这里的上行反馈包括混合自动重传请求(hybrid automatic repeat request,HARQ)的肯定应答(acknowledgement，ACK)和否定应答(negative acknowledgement，NACK)，也可以包括信道状态信息(channel state information,CSI)的反馈。
如图5所示，本申请还提供了另一种控制信息传输方法，用于降低终端设备对上行PI的盲检。
S510，网络设备向终端设备发送第二控制信息。对应的，终端设备接收来自网络设备的第二控制信息。其中，该第二控制信息用于指示终端设备对上行PI进行监测或指示终端设备是否对上行PI进行监测，第二控制信息可以通过信令承载。
在本申请中，信令可以是无线资源控制(radio resource control，RRC)信令，也可以是物理层信令，还可以是媒体接入控制(medium access control)信令。信令可以是发给某个特定终端设备的；也可以是组信令，即发给一组终端设备的；还可以是广播信令，即发给小区内所有终端设备的。这里物理层信令可以是DCI，例如可以是发给eMBB终端设备的、用于调度上行数据传输的DCI，即在调度eMBB终端设备进行上行数据传输的同时，指示该eMBB终端设备是否要对上行PI进行监测。
S520，终端设备根据第二控制信息确定对上行PI进行监测或确定不对上行PI进行监测。
具体的，第二控制信息可以有一个取值，例如，取值为第一数值，指示终端设备对上行PI进行监测；第二控制信息也可以两个取值，例如，取值为第一数值用于指示终端设备对上行PI进行监测，取值为第二数值用于指示终端设备不对上行PI进行监测。这里的第一数值可以为1，第二数值可以为0；或者，第一数值为0，第二数值为1。当终端设备收到第二控制信息或收到的第二控制信息的取值为第一数值时，我们称满足条件二。这里的条件二是指终端设备是否收到第二控制信息或终端设备收到的第二控制信息的取值是否为第一数值。可以理解的是，条件二可以单独使用，即只要满足条件二，终端设备就在上行PI的监测时机对应的时刻对上行PI进行监测；当不满足条件二时，即终端设备没有收到第二控制信息或收到的第二控制信息的取值不是第一数值时，终端设备不对上行PI进行监测。条件二也可以与本申请实施例中的其它条件结合起来使用，例如，当满足条件二且还满足条件一时，终端设备才会在上行PI的监测时机对应的时 刻对上行PI进行监测；当条件一或条件二中有一个不满足时，终端设备不对上行PI进行监测。
可选的，第二控制信息与第一控制信息可以承载在相同的DCI中，即第二控制信息承载在调度上行数据的DCI中。
本申请的实施例通过信令半静态或动态通知终端设备对上行PI进行监测，可以有针对性地通知哪些终端设备需要对上行PI进行监测，从而有效地避免了那些无需接收上行PI的终端设备对上行PI的盲检。
本申请对RUR的时频位置不做限定，RUR在时频位置上可以是连续的，如图6中的(A)和(C)所示；RUR在时频位置上也可以是离散的，如图6中的(B)和(D)所示。例如，RUR在频域上可以是频带的一部分，如图6中的(A)、(C)和(D)所示；RUR在频域上也可以是跨整个频带，如图6中的(B)所示；RUR在频域上可以是连续的，如图6所示；RUR在频域上也可以是离散的，图6中未示出。RUR在时域上可以是连续的，也可以是离散的。这里的频带可以是子带或者上行的BWP。
具体的，本申请的实施例中的RUR的频域范围可以为第一带宽部分(bandwidth part，BWP)的全部频域范围，这里的第一BWP为用于传输上行数据的BWP。激活同一个BWP的多个终端设备可以组成一组终端设备，针对该组终端设备，网络设备发送同一个组公共(group common)上行PI。该组公共上行PI可以使用一个组公共的无线网络临时标识(radio network temporary identifier，RNTI)进行加扰。终端设备可以只对与第一BWP相对应的上行PI进行监测。上行PI也可以不通过RNTI进行区分，而是给不同组的终端设备配置不同的搜索空间，每个搜索空间对应一个上行PI和RUR。此时终端设备根据配置的搜索空间来确定分组，或者说是根据分组来确定搜索空间。终端设备属于哪一个组可以通过信令来进行指示。
本申请的实施例中的RUR的频域范围也可以为第一BWP的部分频域范围。
下面对上行PI与RUR之间的关系进行描述。上行PI与RUR之间可以是一对一的关系，也可以是一对多的关系，还可以是多对一的关系。在本申请中，上行PI与RUR之间的关系也可以理解为是上行PI的监测时机与RUR之间的关系或者搜索空间与RUR之间的关系，因此，涉及到上行PI与RUR之间的关系的时候，上行PI、上行PI的时域位置以及上行PI的监测时机或者搜索空间可以互换。与某个上行PI的监测时机对应的RUR可以称之为一个RUR，该RUR的时频位置可以是连续的也可以是离散的，如图6所示。
一种可能的设计是，RUR在一个时间单元内被多个上行PI的监测时机分割成多个RUR。这里的一个时间单元可以为一个或多个时隙。可选的，一个上行PI与一个RUR一一对应，每个上行PI在其对应的RUR的前一个符号发送。上行PI的监测时机位于不连续的符号上。以一个时隙为例，如图7所示，假设上行PI的监测时机位于一个时隙中的符号0、符号3、符号6、符号9、符号12。则对应的在该时隙内有五个RUR，第一个RUR位于符号1和符号2；第二个RUR位于符号4和符号5；第三个RUR位于符号7和符号8；第四个RUR位于符号10和符号11；第五个RUR位于符号13。
另一种可能的实现是，上行PI的监测时机位于符号0、符号3、符号6和符号9；对应的，第一个RUR位于符号1和符号2；第二个RUR位于符号4和符号5；第三个RUR位于符号7和符号8；第四个RUR位于符号10、符号11、符号12和符号13。
还一种可能的实现是，上行PI的监测时机位于一个时隙中符号3、符号6、符号9和符号12；对应的，第一个RUR位于符号4和符号5；第二个RUR位于符号7和符号8；第三个RUR位于符号10和符号11；第四个RUR位于符号13。
还一种可能的实现是，上行PI的监测时机位于一个时隙中符号3、符号6和符号9；对应的，第一个RUR位于符号4和符号5；第二个RUR位于符号7和符号8；第三个RUR位于符号10、符号11、符号12和符号13。
在本申请中，在一个时隙内的符号可以从1开始编号，也可以从0开始编号，本申请对此不做限定。
需要说明的是，在本申请中，如果没有特殊说明，符号均指时域符号，可以是OFDM符号，也可以是DFTS-OFDM符号。通过上述设计，终端设备只需要在时域离散的与上行PI监测时机对应的时域符号上对上行PI进行监测，因此可以有效地降低终端设备对上行PI的盲检开销。同时，由于与某一个上行PI对应的RUR的时域范围很窄，只有一两个时域符号，对应的上行PI所需要的用于指示被抢占资源的比特数可以比较少，有利于提高上行PI的可靠性以及传输效率。
还一种可能的设计是，如图8所示，不同的RUR在时频资源上存在交叠。例如，上行PI的监测时机与图7相同，但RUR的时域位置为对应的上行PI的监测时机之后的一个符号到该时隙结束。
本申请还提供了确定RUR的时频位置的方法。RUR的时频位置可以是协议预定义的，例如，协议预定义RUR所在的时域符号，RUR的频域范围为BWP。这种协议预定义RUR的时频位置的方法可以减少信令开销。RUR的时频位置也可以是在网络设备确定之后通过信令通知终端设备。信令可以通知具体的RUR的时频位置，也可以是预定义几种配置，信令通知中只携带RUR配置的索引或编号。通过信令动态或半静态配置RUR的时频位置，可以让网络设备的调度更灵活，资源利用率更高。RUR的时频位置包括时域位置和频域位置。对于时域连续的RUR还可以通过时域范围来表示其时域位置；对于频域连续的RUR可以通过频域范围来表示其频域位置。
RUR的时频位置还有如下确定方法：RUR的时域位置协议预定义，RUR的频域位置由网络设备通过信令通知给终端设备；或者，RUR的频域位置协议预定义，RUR的时域位置由网络设备通过信令通知给终端设备；或者，RUR的频域位置协议预定义，RUR的时域位置由该RUR上行PI的监测时机确定。例如，RUR的时域范围为对上行PI进行监测的时机之后的第n个时域符号到第m个时域符号，其中，n和m为正整数，且n小于等于m，这里的时域符号为用于上行数据传输的时域符号；或者，RUR的时域范围位于对上行PI进行监测的第一时机和对上行PI进行监测的第二时机之间，其中，第一时机与所述第二时机相邻，且第一时机的时域起始位置早于第二时机的时域起始位置。
协议预定义的RUR的时域位置例如可以为一个时隙，或者为上述的RUR的时域位置。协议预定义的RUR的频域位置可以为一个子带或一个BWP。
为了确定RUR的时频位置，网络设备可以通过信令向终端设备发送第三控制信息，对应的，终端设备接收来自网络设备的第三控制信息。其中，第三控制信息用于指示RUR的时域范围、时域位置、频域范围、频域位置和时频位置中的至少一个。
本申请还提供了确定上行PI监测时机的方法。上行PI的监测时机可以是协议预定 义，也可以是网络设备确定之后通过信令通知终端设备。可以通过信令通知具体的上行PI的监测时机，也可以是定义几种配置，再通过信令通知上行PI监测时机的配置的索引或编号。如表1、表2、表3和表4所示，定义了三种上行PI监测时机的配置。这里的监测时机的多种配置可以是协议预定义，也可以是网络设备确定后通过RRC信令发送给终端设备。通过定义多种监测时机的配置，给不同的终端设备分配不同的监测时机，对于单个终端设备而言，监测时机在一个时隙内是离散的，因此能够有效地降低终端设备对上行PI的盲检次数；另一方面，由于小区内各种监测时机的终端设备都有，对应的，在各个时域符号上都有RUR，当有URLLC业务数据需要传输时，能够及时抢占到时频资源用于URLLC业务数据的传输。
表1
配置索引 上行PI的监测时机(符号在时隙内的编号)
0 0,3,6,9,12
1 1,4,7,10,13
2 2,5,8,11
表2
配置索引 上行PI的监测时机(符号在时隙内的编号)
0 0,3,6,9
1 1,4,7,10
2 2,5,8,11
表3
配置索引 上行PI的监测时机(符号在时隙内的编号)
0 3,6,9,12
1 4,7,10,13
2 5,8,11
表4
配置索引 上行PI的监测时机(符号在时隙内的编号)
0 3,6,9
1 4,7,10
2 5,8,11
为了确定上行PI的监测时机，网络设备可以通过信令向终端设备发送第四控制信息，对应的，终端设备接收来自网络设备的第四控制信息，其中，第四控制信息用于指示终端设备对上行PI进行监测的时机。具体的，第四控制信息可以指示具体的监测时机的位置，例如，通过比特位图的方式指示在一个时隙中哪几个时域符号上需要对上行PI进行监测。第四控制信息还可以指示监测时机的配置的索引或编号。终端设备可以根据该第四控制信息确定上行PI的监测时机。
上行PI的监测时机还可以通过RUR的时域位置来确定。例如，终端设备对上行PI进行监测的时机位于RUR起始符号之前的第n个时域符号，其中，n为正整数；或者，终端设备对上行PI进行监测的时机位于第一RUR和第二RUR之间，其中，第一RUR和第二RUR相邻，且第二RUR的时域起始位置早于第一RUR的时域起始位置。
上行PI的监测时机也可以是一个时域范围，由对应的RUR决定。例如，以RUR的开始时间点T1为基准。[T1-p,T1-q]为对应的上行PI的监测时机，其中，p和q为正数，且p大于等于q，p小于T1。上面例子是以RUR的开始时间点为基准的例子，也可以是以结束时间点为基准。
此外，上行PI也可以在RUR内发送，此时，上述的q也可以小于0。在另一个例子中，由于UE收到PI后有一个处理时间，假设为Δ。假设RUR的结束时间点为T2，那么在T2-Δ后，再接收PI就没有意义了，因此也可以限制T1-q≤T2-Δ。
为了有效降低终端设备对上行PI的盲检次数，终端设备在一个时隙内对上行PI进行监测的次数小于等于7次。
本申请还提供一种上行PI的指示设计，即上行PI如何指示RUR内的第三时频资源。为了减少终端设备对上行PI的盲检次数，上行PI中用于指示RUR内的第三时频资源的第一字段可以采用固定比特数，例如，上行PI包括一个长度为2比特或4比特的字段用于指示RUR内的第三时频资源。第一字段的比特长度的取值需要在指示粒度和上行PI的开销之间进行折中。第一字段的比特长度越长，指示粒度越细，但是上行PI的开销越大；相反，第一字段的比特长度越短，上行PI的开销越小，但是指示粒度越粗，从而会导致上行eMBB业务数据的无效重传。可以理解的是，对于多载波场景，上行PI可以包括多个第一字段分别用于指示多个载波内各自的RUR的第三时频资源，每个载波对应一个第一字段。
当第一字段长度为4比特时，对应的RUR包括四个第四时频资源，第一字段中的每一个比特对应RUR中的一个第四时频资源。如图9中的(A)所示，RUR从时域上分割成四个第四时频资源；如图9中的(B)所示，RUR在时域上分割为两个时间单元，在频域上分割为两个频域单元，一共分割成了四个第四时频资源；如图9中的(C)所示，RUR从频域上分割成四个第四时频资源。RUR具体采用哪一种分割方法，可以协议预定义，也可以网络设备确定后通过信令通知终端设备。例如，当RUR的时域符号为四个时，可以采用如图9中的(A)所示的分割方法，以便能在时域上提供最细的指示粒度；当RUR的时域符号为两个时，可以采用如图9中的(B)所示的分割方法，同时在时域和频域对第三时频资源进行指示；当RUR的时域符号为一个时，可以采用如图9中的(C)所示的分割方法。
当第一字段长度为2比特时，对应的RUR包括两个第四时频资源，第一字段中的每一个比特对应RUR中的一个第四时频资源。如图9中的(D)所示，RUR从时域上分割成两个第四时频资源；如图9中的(E)所示，RUR从频域上分割成两个第四时频资源。RUR具体采用哪一种分割方法，可以协议预定义，也可以网络设备确定后通过信令通知终端设备。例如，当RUR的时域符号为四个或两个时，可以采用如图9中的(D)所示的分割方法；当RUR的时域符号为一个时，可以采用如图9中的(E)所示的分割方法。
本申请还提供另一种上行PI的指示设计，上行PI指示第三时频资源的起始时间。 终端设备在上行PI所指示的起始时间停止发送上行数据。即上行PI通知一个时间点，终端设备在这个时间点之后不再发送上行数据，直到下一次被调度才继续开始发送上行数据。
在某些场景下，有一些时频资源不允许被上行数据传输抢占，例如，一些特殊的预留资源，时分双工(time division duplex，TDD)系统中的下行传输资源，或者一些上行参考信号所使用的时频资源等。这些不允许被抢占的时频资源可能是动态时变的，也可能是半静态配置的，从而导致RUR可能和这些不允许被抢占的时频资源有交叠。对应的有两种处理方式：
(1)RUR的定义保持不变，RUR可以包括部分不允许抢占的时频资源，也就是RUR和不允许被抢占的时频资源可以交叠。假设不允许被抢占的时频资源为资源A，那么在本申请实施例的S320和S1120中的RUR需要剔除资源A之后得到更新后的RUR，再根据更新后的RUR进行相关的条件判断。
(2)根据不允许被抢占的时频资源的定义或配置，调整RUR的范围，RUR与不允许被抢占的时频资源不重叠。
【实施例二：多小区场景】
本申请还提供一种小区间协作场景下的控制信息传输方法。如图10所示，在小区A的覆盖范围有一个第一终端设备，第一终端设备由小区A提供无线连接服务；小区B的覆盖范围内有一个第二终端设备，第二终端设备由小区B提供无线连接服务；小区A与小区B相邻且两个小区的覆盖区有部分重叠。小区A和小区B可能由同一个网络设备管理，也可能由两个不同的网络设备管理。当小区A和小区B由同一个网络设备管理时，小区A和小区B之间的信息交互通过网络设备内部的消息接口或内部电路交互。当小区A和小区B分别由两个不同的网络设备管理时，假设小区A由第一网络设备管理，小区B由第二网络设备管理，则小区A和小区B之间的信息交互通过第一网络设备和第二网络设备之间的消息接口交互。虽然图9中只示出了两个小区协作的场景，但本申请对参与协作的小区的数量不做限定。
下面以小区A和小区B分别由两个不同的网络设备管理为例进行说明，但本申请的实施例也适用于小区A和小区B由同一个网络设备管理的场景。
当第二终端设备发送URLLC业务数据时，也会受到位于小区A的覆盖边缘且靠近小区B的第一终端设备发送的上行数据的干扰。因此，当第二终端设备抢占时频资源进行URLLC业务数据传输时，小区A内的第一终端设备也需要知道第二终端设备进行抢占的时频位置，在第二终端设备抢占的时频资源位置上停止上行数据发送，从而避免对第二终端设备的URLLC业务数据产生干扰，提高第二终端设备的URLLC业务数据传输的可靠性。也就是说，第一终端设备需要监测由第二网络设备发送的小区B的上行PI，我们称该PI为第二上行PI。第一终端设备为了监测第二网络设备发送的第二上行PI，首先需要确定第二上行PI的监测时机。
根据前述实施例一的相关描述，上行PI的监测时机可以协议预定义，也可以网络设备确定后通过信令通知终端设备，还可以是根据RUR确定。进一步的，RUR也可以是协议预定义，也可以是网络设备确定后通过信令通知终端设备。
当上行PI的监测时机是协议预定时，那么第一终端设备可以根据协议的定义确定 第二网络设备发送的小区B的第二上行PI的监测时机。
当上行PI的监测时机是网络设备通过信令通知终端设备时，第一终端设备有两种方法可以获得小区B的第二上行PI的监测时机：一种是直接接收小区B的相关信令；另一种是第二网络设备将小区B的第二上行PI的监测时机的相关信息发送给第一网络设备，第一网络设备再将小区B的第二上行PI的监测时机的相关信息通过信令发送给第一终端设备。
当上行PI的监测时机是根据RUR确定且RUR是协议预定义时，那么第一终端设备可以根据协议的定义确定小区B的第二上行PI对应的第二RUR，然后根据第二RUR确定第二上行PI的监测时机。
当上行PI的监测时机是根据RUR确定、且RUR是网络设备确定后通过信令通知终端设备时，第一终端设备有两种方法可以确定小区B的第二上行PI的监测时机：一种是直接接收小区B的相关信令获取与第二上行PI相对应的第二RUR的相关信息，然后根据第二RUR确定第二上行PI的监测时机；另一种是第二网络设备将小区B的与第二上行PI相对应的第二RUR的相关信息发送给第一网络设备，第一网络设备再将小区B的第二RUR的相关信息通过信令发送给第一终端设备，第一终端设备再根据第二RUR的相关信息确定出第二上行PI的监测时机。
有关第二上行PI与第二RUR的更详细的描述可以参考实施例一中上行PI与RUR的相关描述。
如图11所示，本申请提供了一种控制信息的传输方法。
S1110，第一网络设备向第一终端设备发送第一控制信息。对应的，第一终端设备接收来自第一网络设备的第一控制信息。其中，第一控制信息用于指示该第一终端设备在第一时频资源上发送上行数据。
S1120，第一终端设备根据第一时频资源和第二RUR确定对第二上行PI进行监测或确定对第二上行PI不进行监测。其中，第二上行PI在第二RUR内指示第五时频资源信息，第二上行PI为第一终端设备的邻区的上行PI。第一终端设备的邻区可以理解为第一终端设备能够接收到该邻区下行信号和/或第一终端设备发送的上行信号能够被管理该邻区的网络设备接收到。在图10所示的场景中，第一终端设备的邻区是指小区B。第五时频资源可以是停止发送上行数据的时频资源信息，也可以是停止发送上行数据的时间信息，还可以是改变传输参数的时频资源信息。当第一终端设备确定需要对第二上行PI进行监测时，需要进一步地确定第二上行PI的监测时机。
具体的，第一时频资源可以为第一网络设备分配给第一终端设备用于传输eMBB业务数据的时频资源。当第一时频资源与第二RUR有交叠时，我们称满足条件三，第一终端设备确定对第二上行PI进行监测。可以理解的是，这里的条件三是指第一时频资源与第二RUR是否有交叠。当第一时频资源与第二RUR没有交叠时，即不满足条件三，第一终端设备确定不对第二上行PI进行监测。通过判断第一时频资源是否与第二RUR重叠来确定是否要对第二上行PI进行监测，从而有效地避免了那些无需接收第二上行PI的终端设备对第二上行PI的盲检。
可选的，第一终端设备也可以通过判断条件四是否满足，来确定是否要对第二上行PI进行监测。这里的条件四是指第一终端设备能否检测到邻区的下行同步信号或者其它 参考信号。当第一终端设备检测到邻区的下行同步信号或者其它参考信号时，认为条件四满足。可以理解的是，上述条件三和条件四可以单独使用，也可以组合使用。即可以是当条件三满足时，第一终端设备确定对第二上行PI进行监测；也可以是当条件四满足时，第一终端设备确定对第二上行PI进行监测；还可以是当条件三和条件四都满足时，第一终端设备确定对第二上行PI进行监测。
如图12所示，本申请提供了一种控制信息的传输方法。
S1210，第一网络设备向第一终端设备发送第五控制信息。对应的，第一终端设备接收来自第一网络设备的第五控制信息。其中，该第五控制信息用于指示第一终端设备对第二上行PI进行监测或指示第一终端设备是否对第二上行PI进行监测，第五控制信息可以通过信令承载。
S1220，第一终端设备根据第五控制信息确定对第二上行PI进行监测或确定不对第二上行PI进行监测。
具体的，有关第五控制信息更详细的设计可以参考S520中对第二控制信息的相关描述。当第一终端设备收到第五控制信息或收到的第五控制信息的取值为第一数值时，我们称满足条件五。这里的条件五是指第一终端设备是否收到第五控制信息或第一终端设备收到的第五控制信息的取值是否为第一数值。可以理解的是，条件五可以单独使用，即只要满足条件五，第一终端设备就在第二上行PI的监测时机对应的时刻对第二上行PI进行监测；条件五不满足时，第一终端设备确定不对第二上行PI进行监测。条件五也可以与条件三和/或条件四结合起来使用。例如，当满足条件三且满足条件五时，第一终端设备确定在第二上行PI的监测时机对应的时刻对第二上行PI进行监测；当条件三和条件五中有一个不满足时，第一终端设备确定不对第二上行PI进行监测。又例如，当满足条件四且满足条件五时，第一终端设备确定在第二上行PI的监测时机对应的时刻对第二上行PI进行监测；当条件四和条件五中有一个不满足时，第一终端设备确定不对第二上行PI进行监测。又例如，当条件三、条件四和条件五均满足时，第一终端设备确定在第二上行PI的监测时机对应的时刻对第二上行PI进行监测；当条件三、条件四和条件五中有任意一个不满足时，第一终端设备确定不对第二上行PI进行监测。
不同的终端设备的能力可以不同，例如，有些终端设备可以接收上行PI；有些终端设备不支持接收上行PI；有些终端设备可以接收小区内的上行PI但不支持接收邻区的上行PI；有些终端可以接收小区内的上行PI以及邻区的上行PI。终端设备可以将接收上行PI的能力信息上报给网络设备，具体的该能力信息可以包括以下中的至少一个：不支持接收上行PI，支持接收上行PI，支持接收小区内的上行PI但不支持接收邻小区的上行PI，支持接收小区内的上行PI以及支持接收邻小区的上行PI，支持接收邻小区的上行PI的邻小区个数。这里的支持接收邻小区的上行PI的邻小区个数是指能支持对几个邻小区的上行PI进行监测。网络设备调度URLLC终端设备的时候，避免抢占不支持接收上行PI
上述本申请提供的实施例中，从网络设备和终端设备的角度对本申请实施例提供的控制信息传输方法进行了介绍。可以理解的是，为了实现上述功能，网络设备和终端设备包含了执行各个功能相应的硬件结构和/或软件模块。结合本申请提供的实施例所描述的各示例的单元及方法步骤，本申请的实施例能够以硬件或硬件和计算机软件的结合 形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，可以取决于技术方案的应用场景和设计约束条件。专业技术人员可以针对不同的应用场景使用不同的方法来实现所描述的功能，本申请对此不作限定。
【实施例三】
图13、图14和图15为本申请的实施例提供的三种可能的通信装置的结构示意图。该通信装置可以用于实现上述方法实施例中终端设备的功能，因此也能实现上述方法实施例所具备的有益效果。在本申请的实施例中，该通信装置可以是如图1所示的终端设备130或终端设备140，也可以是应用于终端设备的芯片。
如图13所示，通信装置1300包括收发单元1310和处理单元1320。
收发单元1310用于接收第一控制信息，该第一控制信息用于指示在第一时频资源上发送上行数据。
处理单元1320用于根据第一时频资源和RUR确定对上行PI进行监测，上行PI在RUR内指示第三时频资源，第三时频资源为停止发送上行数据的时频资源。
收发单元1310还可以用于接收第二控制信息，第二控制信息用于指示对上行PI进行监测。
收发单元1310还可以用于接收第三控制信息，第三控制信息用于指示RUR的时域范围、时域位置、频域范围、频域位置和时频位置中的至少一个。
收发单元1310还可以用于接收第四控制信息，第四控制信息用于指示对上行PI进行监测的时机。
上述上行PI可以是本小区的上行PI，也可以是邻区的上行PI。这里的本小区是指为该终端设备提供无线连接服务的小区，邻区是指该终端设备的邻区。
有关上述收发单元1310和处理单元1320更详细的描述可以直接参考上述方法实施例中终端设备的相关描述直接得到，这里不加赘述。
如图14所示，通信装置1400包括处理器1410，可选的，还可以包括存储器1420。其中，存储器1420可以用于存储计算机程序或指令，也可以用于存储处理器处理的中间数据；处理器1410可以用于执行存储器1420存储的计算机程序或指令，也可以用于执行存储或固化在处理器1410中的计算机程序或指令，当处理器1410执行计算机程序或指令时，用于完成如方法实施例中所述的终端设备的功能。处理器1410和存储器1420之间通过内部连接通路互相通信，如可以通过总线传输控制和/或数据信号。本申请的实施例对通信装置1400中包括的处理器1410和存储器1420的个数不做限定。
如图15所示，通信装置1500包括处理电路1510和收发电路1520，其中，处理电路1510用于执行本实施例中处理单元1310的功能，收发电路1520用于执行本实施例中收发单元1320的功能。处理电路和收发电路之间通过内部电路互相通信。
当上述通信装置为终端设备的芯片时，该终端设备芯片实现上述方法实施例中终端设备的功能。该终端设备芯片从终端设备中的其它模块(如射频模块或天线)接收信息，该信息是网络设备发送给终端设备的。
【实施例四】
如图13、图14和图15所示的通信装置还可以用于实现上述方法实施例中网络设备的功能，因此也能实现上述方法实施例所具备的有益效果。在本申请的实施例中，该 通信装置还可以是如图1所示的无线接入网设备120，也可以是应用于该无线接入网设备的芯片。
如图13所示，通信装置1300包括收发单元1310和处理单元1320。
处理单元1320用于生成第二控制信息，第二控制信息用于指示对上行PI进行监测，上行PI在RUR内指示第三时频资源，第三时频资源为停止发送上行数据的时频资源；
收发单元1310用于发送第二控制信息。
收发单元1310还可以用于发送第三控制信息，第三控制信息用于指示RUR的时域范围、时域位置、频域范围、频域位置和时频位置中的至少一个。
收发单元1310还可以用于发送第四控制信息，第四控制信息用于指示对上行PI进行监测的时机。
上述上行PI可以是本小区的上行PI，也可以是邻区的上行PI。
有关上述收发单元1310和处理单元1320更详细的描述可以直接参考上述方法实施例中网络设备的相关描述直接得到，这里不加赘述。
如图14所示，通信装置1400包括处理器1410，可选的，还可以包括存储器1420。其中，存储器1420可以用于存储计算机程序或指令，也可以用于存储处理器处理的中间数据；处理器1410可以用于执行存储器1420存储的计算机程序或指令，也可以用于执行存储或固化在处理器1410中的计算机程序或指令，当处理器1410执行计算机程序或指令时，用于完成如方法实施例中所述的网络设备的功能。处理器1410和存储器1420之间通过内部连接通路互相通信，如可以通过总线传输控制和/或数据信号。本申请的实施例对通信装置1400中包括的处理器1410和存储器1420的个数不做限定。
如图15所示，通信装置1500包括处理电路1510和收发电路1520，其中，处理电路1510用于执行本实施例中处理单元1310的功能，收发电路1520用于执行本实施例中收发单元1320的功能。处理电路和收发电路之间通过内部电路互相通信。
当上述通信装置为网络设备的芯片时，该网络设备芯片实现上述方法实施例中网络设备的功能。该网络设备芯片向网络设备中的其它模块(如射频模块或天线)发送信息，该信息是发送给终端设备的。
在本申请的各个实施例中，如果没有特殊说明，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法步骤可以通过硬件的方式来实现，也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable  PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于网络设备或终端设备中。当然，处理器和存储介质也可以作为分立组件存在于发送设备或接收设备中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，DVD；还可以是半导体介质，例如，固态硬盘(solid state disk，SSD)。
本文中的术语“多个”是指两个或两个以上。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系；在公式中，字符“/”，表示前后关联对象是一种“相除”的关系。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。
可以理解的是，在本申请的实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请的实施例的实施过程构成任何限定。

Claims (19)

  1. 一种控制信息传输方法，包括：
    接收来自网络设备的第一控制信息，所述第一控制信息用于指示在第一时频资源上发送上行数据；
    根据所述第一时频资源和参考上行资源RUR确定对上行抢占指示PI进行监测，所述上行PI用于在所述RUR内指示第三时频资源，所述第三时频资源为停止发送上行数据的时频资源。
  2. 根据权利要求1所述的方法，其特征在于，所述根据所述第一时频资源和参考上行资源RUR确定对上行抢占指示PI进行监测,包括：
    当所述第一时频资源与RUR有交叠时，确定对所述上行PI进行监测。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    接收来自网络设备的第二控制信息，所述第二控制信息用于指示对所述上行PI进行监测或用于指示是否对所述上行PI进行监测。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述RUR的频域范围为第一带宽部分BWP的部分或全部频域范围，所述第一BWP为用于传输所述上行数据的BWP。
  5. 根据权利要求1至3任一项所述的方法，其特征在于，所述方法还包括：
    接收来自网络设备的第三控制信息，所述第三控制信息用于指示所述RUR的时域范围、时域位置、频域范围、频域位置和时频位置中的至少一个。
  6. 根据权利要求1至3任一项所述的方法，其特征在于，所述方法还包括：
    接收来自网络设备的第四控制信息，所述第四控制信息用于指示对所述上行PI进行监测的时机。
  7. 根据权利要求6所述的方法，其特征在于，所述RUR的时域范围为所述对上行PI进行监测的时机之后的第n个时域符号到第m个时域符号，其中，n和m为正整数，且n小于等于m，所述时域符号为用于上行数据传输的时域符号。
  8. 根据权利要求1至5任一项所述的方法，其特征在于，所述对上行PI进行监测的时机位于所述RUR起始符号之前的第n个时域符号，其中，n为正整数。
  9. 根据权利要求1至8任一项所述的方法，其特征在于，所述上行PI为邻区的上行PI。
  10. 一种控制信息传输方法，包括：
    生成第二控制信息，所述第二控制信息用于指示对上行抢占指示PI进行监测，所述上行PI用于在参考上行资源RUR内指示第三时频资源，所述第三时频资源为停止发送上行数据的时频资源；
    发送所述第二控制信息。
  11. 根据权利要求10所述的方法，其特征在于，所述RUR的频域范围为第一带宽部分BWP的部分或全部频域范围，所述第一BWP为用于传输所述上行数据的BWP。
  12. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    发送第三控制信息，所述第三控制信息用于指示所述RUR的时域范围、时域位置、频域范围、频域位置和时频位置中的至少一个。
  13. 根据权利要求10任一项所述的方法，其特征在于，所述方法还包括：
    发送第四控制信息，所述第四控制信息用于指示对所述上行PI进行监测的时机。
  14. 根据权利要求13所述的方法，其特征在于，所述RUR的时域范围为所述对上行PI进行监测的时机之后的第n个时域符号到第m个时域符号，其中，n和m为正整数，且n小于等于m，所述时域符号为用于上行数据传输的时域符号。
  15. 根据权利要求10至12中任一项所述的方法，其特征在于，所述对上行PI进行监测的时机位于所述RUR起始符号之前的第n个时域符号，其中，n为正整数。
  16. 根据权利要求10至15任一项所述的方法，其特征在于，所述上行PI为邻区的上行PI。
  17. 一种通信装置，用于实现如权利要求1至9或10至16中任一项所述的方法。
  18. 一种计算机可读存储介质，其特征在于，用于存储计算机程序或指令，当所述计算机程序或指令被运行时，实现如权利要求1至9或10至16中任一项所述的方法。
  19. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机程序或指令，当所述计算机程序或指令被运行时，实现如权利要求1至9或10至16中任一项所述的方法。
PCT/CN2018/123629 2017-12-29 2018-12-25 控制信息的传输方法 Ceased WO2019129012A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18897577.5A EP3720217B1 (en) 2017-12-29 2018-12-25 Control information transmission method
US16/915,757 US11251930B2 (en) 2017-12-29 2020-06-29 Control information transmission method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711490121.9 2017-12-29
CN201711490121.9A CN109996341B (zh) 2017-12-29 2017-12-29 控制信息的传输方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/915,757 Continuation US11251930B2 (en) 2017-12-29 2020-06-29 Control information transmission method

Publications (1)

Publication Number Publication Date
WO2019129012A1 true WO2019129012A1 (zh) 2019-07-04

Family

ID=67066672

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/123629 Ceased WO2019129012A1 (zh) 2017-12-29 2018-12-25 控制信息的传输方法

Country Status (4)

Country Link
US (1) US11251930B2 (zh)
EP (1) EP3720217B1 (zh)
CN (1) CN109996341B (zh)
WO (1) WO2019129012A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110582122A (zh) * 2019-08-06 2019-12-17 中兴通讯股份有限公司 一种资源指示方法、装置、服务节点和存储介质
WO2021159443A1 (en) * 2020-02-14 2021-08-19 Qualcomm Incorporated Pdcch with preemption indication
WO2021198029A1 (en) * 2020-04-01 2021-10-07 Sony Group Corporation Communications device, infrastructure equipment and methods

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019153348A1 (zh) * 2018-02-12 2019-08-15 北京小米移动软件有限公司 传输信息的方法、基站及用户设备
EP3768011B1 (en) * 2018-03-30 2023-08-23 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Uplink control information transmission method and device
WO2020034166A1 (zh) * 2018-08-16 2020-02-20 Oppo广东移动通信有限公司 一种信号传输方法及装置、终端、网络设备
JP7201794B2 (ja) * 2018-08-31 2023-01-10 オッポ広東移動通信有限公司 伝送停止を指示する方法、端末装置、ネットワーク装置、及び記憶媒体
US11606799B2 (en) 2018-09-26 2023-03-14 Qualcomm Incorporated Preemption indication and permission indication management for mobile broadband and low latency communication multiplexing
US11317354B2 (en) * 2018-11-12 2022-04-26 Qualcomm Incorporated Uplink preemption indication
GB2580049B (en) * 2018-12-20 2021-01-13 Tcl Communication Ltd Uplink multiplexing in cellular wireless communication networks
WO2020168235A1 (en) * 2019-02-14 2020-08-20 Hua Zhou Uplink transmission with uplink grant processing prioritization
JP7290712B2 (ja) * 2019-03-14 2023-06-13 株式会社Ｎｔｔドコモ 端末、無線通信方法、基地局及びシステム
CN112020142A (zh) * 2019-05-30 2020-12-01 中国电信股份有限公司 数据复用传输方法、基站、终端以及存储介质
CN112188620B (zh) * 2019-07-01 2022-04-05 华为技术有限公司 一种通信方法及装置
US11350453B2 (en) * 2019-07-18 2022-05-31 Samsung Electronics Co., Ltd. System and method for performing transmission cancellation indication monitoring
WO2021056330A1 (zh) * 2019-09-26 2021-04-01 华为技术有限公司 数据处理的方法和装置
WO2021072779A1 (zh) * 2019-10-18 2021-04-22 华为技术有限公司 传输处理方法、装置、设备以及存储介质
JP2023501201A (ja) * 2019-11-07 2023-01-18 富士通株式会社 サイドリンクリソースのリザーブ方法及び装置
WO2022151445A1 (zh) * 2021-01-15 2022-07-21 华为技术有限公司 一种上行传输的方法和装置
CN115334662B (zh) * 2021-05-11 2025-10-10 展讯通信（上海）有限公司 数据传输方法、装置及设备
CN114007274B (zh) * 2021-09-17 2023-11-14 厦门大学 基于urllc业务时延容忍度的资源复用方法及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106455081A (zh) * 2016-10-31 2017-02-22 宇龙计算机通信科技(深圳)有限公司 资源配置方法及资源配置装置
CN106455103A (zh) * 2016-11-30 2017-02-22 宇龙计算机通信科技(深圳)有限公司 资源配置方法和资源配置装置
CN107079450A (zh) * 2014-10-16 2017-08-18 高通股份有限公司 用于增强型分量载波的传输抢占控制

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101512585B1 (ko) * 2011-02-12 2015-04-15 후지쯔 가부시끼가이샤 협력 다중 포인트 송신/수신의 업링크 채널 자원을 할당하기 위한 방법 및 디바이스
CN107027181B (zh) * 2016-02-02 2020-02-04 电信科学技术研究院 一种上行控制信息的传输方法及装置
WO2017213374A1 (en) * 2016-06-07 2017-12-14 Samsung Electronics Co., Ltd. Method and device for providing different services in mobile communication system
KR102123233B1 (ko) * 2016-09-01 2020-06-17 주식회사 케이티 차세대 무선 액세스 망에서 데이터를 송수신하는 방법 및 그 장치
KR102814157B1 (ko) * 2017-01-04 2025-05-28 토요타 찌도샤 카부시끼카이샤 통신 방법, 단말기기 및 네트워크 기기
US11122576B2 (en) * 2017-02-02 2021-09-14 Lg Electronics Inc. Method and apparatus for indicating preempted resource information
WO2018175420A1 (en) * 2017-03-20 2018-09-27 Convida Wireless, Llc Scheduling and control in new radio using preemption indication
US10856307B2 (en) * 2017-03-21 2020-12-01 Kt Corporation Method for transmitting and receiving downlink pre-emption indication information using bitmap in new radio networks and apparatus thereof
EP3635887B1 (en) * 2017-05-03 2021-10-20 Convida Wireless, LLC Infrastructure equipment, mobile terminal, computer software and methods
EP3402288B1 (en) * 2017-05-12 2021-02-24 ASUSTek Computer Inc. Method and apparatus for improving scheduling in a wireless communication system
CN109152009B (zh) * 2017-06-15 2020-12-08 华为技术有限公司 通信方法、终端设备和网络设备
PL3641197T3 (pl) * 2017-06-16 2024-04-15 Wilus Institute Of Standards And Technology Inc. Sposób, urządzenie i system do wysyłania lub odbierania kanału sterującego i kanału danych w systemie komunikacji bezprzewodowej
CN109462892B (zh) * 2017-06-30 2019-11-19 华为技术有限公司 控制信息传输方法和设备
KR102365147B1 (ko) * 2017-08-10 2022-02-18 애플 인크. 뉴 라디오에 대한 선점 지시들
CN111345101B (zh) * 2017-08-29 2023-10-31 日本电气株式会社 用于传输和接收抢占指示的方法和装置
US10873934B2 (en) * 2017-09-28 2020-12-22 Ofinno, Llc Pre-emption indication in a wireless device
WO2019066318A1 (ko) * 2017-09-29 2019-04-04 한국전자통신연구원 통신 시스템에서 프리엠션의 지시 방법
CN109803410B (zh) * 2017-11-17 2024-06-07 中兴通讯股份有限公司 资源指示方法及装置
US10779328B2 (en) * 2017-11-27 2020-09-15 Qualcomm Incorporated Reference signal and preempted resources collision handling
CN109842946B (zh) * 2017-11-29 2023-01-13 华为技术有限公司 抢占资源进行数据传输的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107079450A (zh) * 2014-10-16 2017-08-18 高通股份有限公司 用于增强型分量载波的传输抢占控制
CN106455081A (zh) * 2016-10-31 2017-02-22 宇龙计算机通信科技(深圳)有限公司 资源配置方法及资源配置装置
CN106455103A (zh) * 2016-11-30 2017-02-22 宇龙计算机通信科技(深圳)有限公司 资源配置方法和资源配置装置

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
CATR: "DISCUSSION on THE DESIGN of DL PREEMPTION INDICATION", 3GPP TSG RAN WG1 MEETING #90, R1-1714228, 25 August 2017 (2017-08-25), XP051317016 *
CATR: "DISCUSSION on THE DESIGN of DL PREEMPTION INDICATION", 3GPP TSG RAN WG1 MEETING NR#3, R1-1716652, 21 September 2017 (2017-09-21), XP051330172 *
See also references of EP3720217A4
SPREADTRUM COMMUNICATIONS: "CONSIDERARION on MONITORING PREEMPRION INDICA- TION in BANDWIDTH PARTS", 3GPP TSG RAN WG1 MEETING ADHOC #3, R1-1715517, 21 September 2017 (2017-09-21), XP051329060 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110582122A (zh) * 2019-08-06 2019-12-17 中兴通讯股份有限公司 一种资源指示方法、装置、服务节点和存储介质
WO2021159443A1 (en) * 2020-02-14 2021-08-19 Qualcomm Incorporated Pdcch with preemption indication
US12212506B2 (en) 2020-02-14 2025-01-28 Qualcomm Incorporated PDCCH with preemption indication
WO2021198029A1 (en) * 2020-04-01 2021-10-07 Sony Group Corporation Communications device, infrastructure equipment and methods

Also Published As

Publication number Publication date
EP3720217A1 (en) 2020-10-07
EP3720217B1 (en) 2024-03-06
US11251930B2 (en) 2022-02-15
CN109996341A (zh) 2019-07-09
US20200328866A1 (en) 2020-10-15
CN109996341B (zh) 2023-03-24
EP3720217A4 (en) 2021-01-06

Similar Documents

Publication Publication Date Title
CN109996341B (zh) 控制信息的传输方法
US11196516B2 (en) Methods for autonomous uplink transmissions and retransmissions
CN109462892B (zh) 控制信息传输方法和设备
JP7516558B2 (ja) 切り替え方法及び装置
US20200120701A1 (en) Wireless Communication Method and Device
WO2023025301A1 (zh) 一种通信方法及通信装置
EP4044720B1 (en) Measurement method, apparatus and system
WO2019137245A1 (zh) 上行控制信息传输方法及装置
WO2018166048A1 (zh) 一种传输方向的配置方法、设备及系统
US11191123B2 (en) Method and device for performing uplink transmission
WO2018133669A1 (zh) 一种资源调度方法以及无线接入网设备和终端设备
CN109923919B (zh) 在第五代（5g）新无线电中支持超宽带宽的装置和方法
CN113518441B (zh) 物理下行控制信道的监听方法和装置
US20230199740A1 (en) Communication method and apparatus
CN116326112B (zh) 用于放宽的ue处理时间的方法
WO2020200044A1 (zh) 一种通信方法及设备
CN111385863A (zh) 一种功率控制方法和装置
WO2019029463A1 (zh) 一种接收控制信息、发送控制信息的方法及设备
WO2021000725A1 (zh) 一种通信方法及装置
CN108811112B (zh) 数据传输方法、设备和系统
US20190124705A1 (en) Identifier management method, apparatus, and system
WO2019157897A1 (zh) 一种上行数据的发送方法、接收方法和装置
WO2021204207A1 (zh) 下行数据发送和接收方法及装置
WO2021036763A1 (zh) 监测周期的调整方法及装置
WO2019192515A1 (zh) 一种反馈信息的传输方法和装置

Legal Events

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

Ref document number: 18897577

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018897577

Country of ref document: EP

Effective date: 20200701