WO2020011253A1

WO2020011253A1 - Communication method and communication device

Info

Publication number: WO2020011253A1
Application number: PCT/CN2019/095819
Authority: WO
Inventors: 张莉莉; 温容慧; 刘哲; 吕永霞
Original assignee: 华为技术有限公司
Priority date: 2018-07-13
Filing date: 2019-07-12
Publication date: 2020-01-16
Also published as: CN110719155A; CN110719155B

Abstract

Provided in the present application are a communication method and a terminal device, the method comprising: when a terminal device sends URLLC data over a first resource and cancels the sending of eMBB data, the terminal device determines that the duration or number of times of cancelling the sending of the eMBB data reaches a first threshold or the duration or number of times of sending the URLLC data reaches a first threshold, the first resource being a time domain resource wherein a URLLC data resource overlaps an eMBB data resource; and the terminal device sends the URLLC data and the eMBB data over the first resource. Implementing the present application facilitates improvement of the communication quality of the eMBB service.

Description

Communication method and communication equipment

This application claims priority from a Chinese patent application filed on July 13, 2018 with the Chinese Patent Office, application number 201810767399.4, and application name "A Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. .

Technical field

The present application relates to the field of communication technologies, and in particular, to a communication method and a communication device.

Background technique

Mobile communication technology has profoundly changed people's lives, but people's pursuit of higher performance mobile communication technology has never stopped. In order to cope with the explosive growth of mobile data traffic in the future, the connection of massive mobile communication devices, and the emergence of various new services and application scenarios, the fifth generation (5G) mobile communication system came into being. The International Telecommunication Union (ITU) defines three major application scenarios for 5G and future mobile communication systems: enhanced mobile broadband (eMBB), ultra-reliable, and low-latency communication. communications (URLLC) and mass machine type communications (mMTC).

The main characteristics of the eMBB service are the large amount of data transmitted and the high transmission rate. The main features of the URLLC service are ultra-reliability, low latency, small amount of data transmitted, and burstiness. The main characteristics of the mMTC business are the huge number of networked devices, the small amount of data transmitted, and the insensitivity of data to transmission delays. These mMTC terminals need to meet the requirements of low cost and very long standby time. 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 a technical problem that needs to be solved in current 5G mobile communication systems. For example, how to support both the URLLC service and the eMBB service is one of the hot topics in the current 5G mobile communication system.

In the existing practical application, if the time-frequency resource of the eMBB data sent to the access network device overlaps with the time-frequency resource of the URLLC data sent to the access network device, the eMBB data will bring the URLLC data reception. interference. In order to avoid eMBB data from interfering with the reception of URLLC data, usually eMBB terminals do not send eMBB data at time-frequency resources that overlap with URLLC data. However, in practice, it is found that such an anti-interference method can only send URLLC data on time-frequency resources that overlap with URLLC data, and cannot send eMBB data in a timely manner, which seriously affects the communication quality of eMBB services.

Summary of the invention

The embodiments of the present application provide a communication method and a communication device, which are beneficial to improving the communication quality of the eMBB service.

In a first aspect, an embodiment of the present application provides a communication method. The method includes: when a terminal device sends high-reliability low-latency communication URLLC data on a first resource and cancels sending enhanced mobile broadband eMBB data, the method includes: The terminal device determines that the duration or number of times to cancel sending eMBB data reaches a first threshold, or the duration or number of times to send URLLC data reaches a first threshold, where the first resource is a time-frequency resource in which the URLLC data resource overlaps with the eMBB data resource; The terminal device sends URLLC data and eMBB data on the first resource.

It can be seen that, by implementing the method described in the first aspect, in addition to the manner in which the terminal device sends URLLC data in a time-frequency resource where the URLLC data resource overlaps with the eMBB data resource and cancels the eMBB data, the terminal device can The URLLC data and the eMBB data are transmitted in a time-frequency resource where the URLLC data resource and the eMBB data resource overlap. Therefore, implementing the method described in the first aspect is beneficial to improving the communication quality of the eMBB service.

Optionally, when the terminal device sends URLLC data and eMBB data on the first resource, the terminal device determines that the number or duration of sending eMBB data on the first resource reaches a second threshold, or sends The duration or number of URLLC data reaches the second threshold; the terminal device sends URLLC data on the first resource, and cancels sending eMBB data.

By implementing this implementation mode, after the terminal device sends URLLC data on the first resource and cancels sending eMBB data multiple times, the terminal device may send URLLC data and eMBB data on the first resource multiple times. After the terminal device sends URLLC data and eMBB data on the first resource multiple times, the terminal device may send URLLC data on the first resource multiple times and cancel sending of eMBB data. Or, after the terminal device sends URLLC data on the first resource and cancels sending the eMBB data to a first threshold, the time when sending the URLLC data and eMBB data on the first resource can reach a second threshold . After the terminal device sends URLLC data and eMBB data on the first resource to the second threshold, sending URLLC data on the first resource and canceling sending eMBB data can reach the second threshold The length of time. Therefore, the terminal device can flexibly switch between the two transmission states.

Optionally, the terminal device may further receive a first target received power value sent by an access network device, where the first target received power value is used by the terminal device to determine when to send eMBB data when the second resource sends eMBB data. Transmit power, the second resource is a time-frequency resource in which the URLLC data resource and the eMBB data resource do not overlap.

By implementing this embodiment, the first target received power value can be flexibly configured.

Optionally, the terminal device may further receive a second target received power value sent by the access network device, and the second target received power value is used by the terminal device to determine sending when the first resource sends URLLC data and eMBB data. The transmission power of eMBB data.

By implementing this embodiment, the second target received power value can be flexibly configured.

Optionally, the first target power value is greater than the second target power value. By implementing this implementation mode, it is beneficial to avoid interference of eMBB data with URLLC data.

Optionally, the terminal device may further receive a third threshold value sent by the access network device, and when URLLC data and eMBB data are sent on the first resource, the modulation and coding policy MCS of the eMBB data sent by the terminal device Is less than or equal to the third threshold. By implementing this implementation mode, it is beneficial to avoid interference of eMBB data with URLLC data.

Optionally, the terminal device may further receive a third target received power value sent by the access network device, and the third target received power value is used by the terminal device to send URLLC data on the first resource and cancel sending of eMBB data , Determine the transmit power for sending URLLC data. By implementing this embodiment, the third target received power value can be flexibly configured.

Optionally, the terminal device may further receive a fourth target received power value sent by the access network device, where the fourth target received power value is used when the terminal device sends URLLC data and eMBB data on the first resource, and determines Transmit power for sending URLLC data. By implementing this embodiment, the fourth target received power value can be flexibly configured.

Optionally, the fourth target power value is greater than the third target power value. By implementing this implementation mode, it is beneficial to avoid interference of eMBB data with URLLC data.

Optionally, the terminal device may also receive a fourth threshold value sent by the access network device, where when the first resource sends URLLC data and eMBB data, the MCS of the URLLC data sent by the terminal device is less than or equal to The fourth threshold is described. By implementing this implementation mode, it is beneficial to avoid interference of eMBB data with URLLC data.

Optionally, the terminal device may further receive configuration information sent by an access network device, where the configuration information is used to configure a state of sending URLLC data on the first resource, and cancel a state of sending eMBB data, and configure the Status of the first resource sending URLLC data and eMBB data.

By implementing this embodiment, the state of the terminal device can be flexibly configured.

Optionally, the terminal device may further receive the first threshold value sent by an access network device. By implementing the embodiment, the first threshold can be flexibly configured.

Optionally, the terminal device may further receive the second threshold value sent by an access network device. By implementing the embodiment, the second threshold can be flexibly configured.

In a second aspect, an embodiment of the present application provides a communication method. The method includes: the terminal device determines that the duration or number of times to cancel sending enhanced mobile broadband eMBB data reaches a first threshold; and the terminal device sends on a first resource. eMBB data, wherein the first resource is a time-frequency resource in which high-reliability low-latency communication URLLC data resource and eMBB data resource overlap.

It can be seen that, by implementing the method described in the second aspect, in addition to canceling the sending of eMBB data by using time-frequency resources where URLLC data resources overlap with eMBB data resources, the terminal device can also use URLLC data. A method for sending eMBB data when time-frequency resources whose resources overlap with eMBB data resources. Therefore, implementing the method described in the second aspect is beneficial to improving the communication quality of the eMBB service.

Optionally, the terminal device determines that the number or duration of sending eMBB data on the first resource reaches a second threshold; and the terminal device cancels sending eMBB data on the first resource. By implementing this embodiment, the terminal device can flexibly switch between two transmission states.

Optionally, the terminal device may further receive a first target received power value sent by an access network device, where the first target received power value is used by the terminal device to determine when to send eMBB data when the second resource sends eMBB data. Transmit power, the second resource is a time-frequency resource in which the URLLC data resource and the eMBB data resource do not overlap. By implementing this embodiment, the first target received power value can be flexibly configured.

Optionally, the terminal device receives a second target received power value sent by the access network device, and the second target received power value is used by the terminal device to determine when to send eMBB data when the first resource sends eMBB data. Transmit power. By implementing this embodiment, the second target received power value can be flexibly configured.

Optionally, the terminal device may also receive a third threshold value sent by the access network device, wherein when the eMBB data is sent on the first resource, the modulation and coding strategy MCS of the eMBB data sent by the terminal device is less than Or equal to the third threshold. By implementing this implementation mode, it is beneficial to avoid interference of eMBB data with URLLC data.

Optionally, the terminal device may also receive configuration information sent by an access network device, where the configuration information is used to configure a state in which eMBB data is canceled on the first resource and configured on the first resource. Status of sending eMBB data. By implementing this embodiment, the state of the terminal device can be flexibly configured.

Optionally, the terminal device may further receive the first threshold value sent by an access network device. By implementing this embodiment, the first threshold can be flexibly configured.

Optionally, the terminal device may further receive the second threshold value sent by an access network device. By implementing this embodiment, the second threshold can be flexibly configured.

In a third aspect, an embodiment of the present application provides a communication method. The method includes: when a terminal device sends URLLC data on a first resource according to a third target received power value, determining that the duration or number of times that URLLC data is sent reaches the first Threshold. The terminal device sends URLLC data on a first resource according to a fourth target received power value; wherein the first resource is a time-frequency resource in which high-reliability low-latency communication URLLC data resource and eMBB data resource overlap.

It can be seen that by implementing the method described in the third aspect, the terminal device can send URLLC data on the first resource according to different target receive power values, and the terminal device can receive power on the first resource according to the fourth target When sending URLLC data, you can reduce the interference of eMBB data on URLLC data. Therefore, when the terminal device sends URLLC data on the first resource according to the fourth target received power value, the first terminal device may send eMBB data on the first resource. Therefore, implementing the method described in the third aspect is beneficial to improving the communication quality of the eMBB service.

Optionally, when the terminal device sends URLLC data on the first resource according to a fourth target received power value, the terminal device determines that the number or duration of sending URLLC data on the first resource reaches a second threshold ; The terminal device sends URLLC data on the first resource according to the third target received power value. By implementing this embodiment, the terminal device can flexibly switch between two transmission states.

Optionally, the terminal device may also receive a third target received power value sent by the access network device. By implementing this embodiment, the third target received power value can be flexibly configured.

Optionally, the terminal device may further receive a fourth target received power value sent by the access network device. By implementing this embodiment, the fourth target received power value can be flexibly configured.

Optionally, the terminal device receives a fourth threshold value sent by an access network device, and when the terminal device sends URLLC data on the first resource according to the fourth target received power value, the terminal device sends the URLLC data The modulation and coding strategy MCS is less than or equal to the fourth threshold. By implementing this implementation mode, it is beneficial to avoid interference of eMBB data with URLLC data.

Optionally, the terminal device may also receive configuration information sent by an access network device, where the configuration information is used to configure a state in which the first resource sends URLLC data according to the third target received power value, And a state configured in the first resource to send URLLC data according to the fourth target received power value. By implementing this embodiment, the state of the terminal device can be flexibly configured.

According to a fourth aspect, a communication device is provided, and the terminal device may execute the foregoing first aspect, second aspect, third aspect, possible implementation manner of the first aspect, possible implementation manner of the second aspect, or possible implementation of the third aspect. Method in implementation. This function can be realized by hardware, and can also be implemented by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the functions described above. The unit may be software and / or hardware. Based on the same inventive concept, the principle and beneficial effects of the terminal device for solving problems can be referred to the above first aspect, second aspect, third aspect, possible implementation manners of the first aspect, possible implementation manners of the second aspect, or third aspect. The possible implementations and beneficial effects will not be repeated here.

According to a fifth aspect, a communication device is provided. The terminal device includes a processor, a memory, and a communication interface; the processor, the communication interface, and the memory are connected; wherein the communication interface may be a transceiver. The communication interface is used to implement communication with other network elements (such as terminal equipment). Among them, one or more programs are stored in a memory, and the processor calls the programs stored in the memory to implement the first aspect, the second aspect, the third aspect, a possible implementation manner of the first aspect, and the second aspect. For a possible implementation manner or a solution in a possible implementation manner of the third aspect, the implementation manner of the terminal device for solving the problem and the beneficial effects may refer to the first aspect, the second aspect, the third aspect, the possible implementation manner of the first aspect, The possible implementation manners in the second aspect or the possible implementation manners in the third aspect and the beneficial effects are not repeated here.

According to a sixth aspect, a computer program product is provided that, when run on a computer, causes the computer to execute the first aspect, the second aspect, the third aspect, a possible implementation manner of the first aspect, and a possible implementation of the second aspect. Method or the third aspect of the possible implementation method.

In a seventh aspect, a chip product for a terminal device is provided, which implements the first aspect, the second aspect, the third aspect, a possible implementation manner of the first aspect, a possible implementation manner of the second aspect, or a possible implementation of the third aspect. Way in the way.

According to an eighth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions that, when run on a computer, cause the computer to execute the first, second, and third aspects described above. , A possible implementation manner of the first aspect, a possible implementation manner of the second aspect, or a method in a possible implementation manner of the third aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

1 and 2 are schematic diagrams of a communication system provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of overlapping time-frequency resources of URLLC data and eMBB data; FIG.

4 is a schematic flowchart of a communication method according to an embodiment of the present application;

5 and 6 are schematic diagrams of sending data on a first resource according to an embodiment of the present application;

7 is a schematic flowchart of another communication method according to an embodiment of the present application;

8 and 9 are schematic diagrams of sending data on a first resource according to an embodiment of the present application;

10 is a schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 11 is a schematic structural diagram of another communication device according to an embodiment of the present application.

detailed description

The specific embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

In order to better understand the embodiments of the present application, a communication system applicable to the embodiments of the present application is described below.

FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application. As shown in FIG. 1, the communication system includes an access network device and a terminal device. The terminal device may send URLLC data and eMBB data to the access network device. That is, in the communication system shown in FIG. 1, the same terminal device can send URLLC data and eMBB data to the access network device. Of course, the communication system may also include multiple terminal devices that can send URLLC data and eMBB data. Figure 1 illustrates one terminal device as an example.

FIG. 2 is a schematic diagram of another communication system according to an embodiment of the present application. As shown in FIG. 2, the communication system includes an access network device, a first terminal device, and a second terminal device. The first terminal device may send eMBB data to the access network device, and the second terminal device may send URLLC data to the access network device. That is, in the communication system shown in FIG. 2, URLLC data and eMBB data are sent by different terminal devices to the access network device.

The access network device may provide communication coverage for a specific geographic area, and may communicate with terminal devices located in the coverage area. The access network device may support communication protocols of different standards, or may support different communication protocols. Communication mode. For example, the access network device may be an evolutionary base station (eNodeB, eNB, or eNodeB) in an LTE system, or a radio network controller in a cloud radio access network (CRAN), or may be The access network equipment in the 5G network, such as gNB, may be a small station, a micro station, or a transmission reception point (TRP), a relay station, an access point, or a public land mobile network (public land evolved in the future). land network (PLMN), etc.

The terminal device may refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile terminal, user terminal, terminal, wireless communication device , User agent, or user device. The access terminal can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital processing (PDA), and wireless communication. Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, end devices in the Internet of Things, virtual reality devices, end devices in future 5G networks, or future public land mobile networks (public land mobile network, PLMN).

The access network device and the terminal device can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on the water; it can also be deployed on air planes, balloons, and artificial satellites. The embodiments of this application do not limit the application scenarios of the access network device and the terminal device.

In the communication system shown in FIG. 1 and FIG. 2, time-frequency resources of URLLC data and eMBB data have overlap. For example, as shown in FIG. 3, time slots 1 to 7 are allocated resources for transmitting eMBB data, and black portions in time slots 1 to 7 are allocated resources for transmitting URLLC data. It can be seen that the black parts in time slots 1 to 7 are time-frequency resources where URLLC data and eMBB data overlap.

In FIG. 1, if the time-frequency resource of the eMBB data sent to the access network device overlaps with the time-frequency resource of the URLLC data sent to the access network device, the reception of the eMBB data will interfere with the reception of the URLLC data. Similarly, the first terminal device in FIG. 2 sends eMBB data to the access network device when the URLLC data and the eMBB data overlap, and the second terminal device in FIG. 2 sends the time-frequency resource when the URLLC data and the eMBB data overlap. Sending URLLC data to the access network device, the eMBB data sent by the second terminal device will interfere with the reception of the URLLC data. In order to avoid interference from the reception of eMBB data to the reception of URLLC data, the terminal device in FIG. 1 usually does not send eMBB data in time-frequency resources where URLLC data and eMBB data overlap. As shown in FIG. 2, the second terminal device in URLLC Time and frequency resources where data and eMBB data overlap do not send eMBB data. It has been found in practice that such an anti-interference method can only send URLLC data on overlapping time-frequency resources, and cannot send eMBB data in a timely manner, which seriously affects the communication quality of eMBB services.

To this end, this application provides a communication method and a terminal device to improve the communication quality of the eMBB service.

The following further describes the communication method and the terminal device provided in this application.

Based on the communication system described in FIG. 1, please refer to FIG. 4, which is a communication method provided by an embodiment of the present application. As shown in FIG. 4, the communication method includes the following 401 and 402 sections, where:

401. When the terminal device sends URLLC data on the first resource and cancels sending eMBB data, the terminal device determines that the duration or number of times to cancel sending eMBB data reaches a first threshold, or the terminal device determines the duration or time to send URLLC data or The number of times reaches a first threshold.

It should be particularly noted that, in all embodiments of the present application, the duration or number of times reaching the first threshold may be that the duration or number of times is equal to or greater than the first threshold, and details are not described herein again.

402. The terminal device sends URLLC data and eMBB data on the first resource.

The first resource is an overlapping resource between a time-frequency resource for transmitting eMBB data and a time-frequency resource for transmitting URLLC data. For example, the first resource may be a time-frequency resource corresponding to a black area in timeslot 1, timeslot 3, timeslot 5, and timeslot 7 in FIG. 3.

Exemplarily, the canceling sending of eMBB data may be: canceling sending of eMBB data by punching on resources transmitting URLLC, or some of the time-frequency resources allocated to eMBB data overlap with resources of URLLC, No eMBB data is transmitted over the entire time-frequency resource to which the eMBB data is allocated.

For example, in FIG. 3, the time-frequency resource allocated by the access network device to the eMBB data at one time is the resource of one time slot. The canceling sending of the eMBB data may be punching and canceling the sending of the eMBB data on a resource that transmits URLLC such as timeslot 1, timeslot 3, timeslot 5, and timeslot 7. Alternatively, the cancellation of sending the eMBB data may be that no eMBB data is sent on the entire resource of the transmission URLLC such as time slot 1, time slot 3, time slot 5, and time slot 7.

The full text uses time slots as examples, but this is only to illustrate the examples given in the technical solution of the present application. The present invention includes, but is not limited to, time slots such as mini time slots, symbols, mini symbols, subframes, mini subframes, or frames. Any expression, as long as it is a mini-slot, a symbol, a mini-symbol, a sub-frame, a mini-sub-frame, a frame, or a new time term generated by the evolution of the standard, and any time unit belongs to the protection of this application. The scope of this is not repeated here.

Optionally, the first threshold may be sent by the access network device to the terminal device, or may be prescribed by a standard, or may be preset. There is no specific limitation on this application, as long as it is the first The threshold-related solutions all belong to the scope protected by this application. This allows flexible configuration of the first threshold.

For example, as shown in FIG. 5, the time-frequency resource corresponding to the black area in FIG. 5 is a time-frequency resource in which the URLLC data resource and the eMBB data resource overlap, that is, the first resource. The terminal device may count the number of times that the eMBB data is cancelled to be sent on the first resource through the counter 1. When the terminal device determines that the number of times recorded by the counter 1 reaches the first threshold, the counter 1 is cleared to zero, and URLLC data and eMBB data are sent on the first resource. When the terminal device sends URLLC data on the first resource and cancels sending eMBB data, restarts the counter 1 and counts the number of times that the eMBB data is canceled. For example, the first threshold is 3 times, the terminal device sends URLLC data on the first resource in timeslot 1, timeslot 3, and timeslot 5, and cancels sending eMBB data, respectively, and the counter 1 records The number of times the terminal device cancels sending eMBB data is three times. When the terminal device sends URLLC data on the first resource in slot 7 and cancels sending eMBB data, it determines that the terminal device recorded in the counter 1 cancels sending. The number of times of eMBB data reaches the first threshold (3 times). The terminal device may first clear the number of times of the counter 1 and then send URLLC data and eMBB data in the first resource of the time slot 7. Alternatively, the terminal device may first send URLLC data and eMBB data in the first resource of time slot 7, and then reset the number of times of the counter 1 to zero. Alternatively, when the terminal device sends URLLC data and eMBB data to the first resource in time slot 7, the terminal device clears the number of times of the counter 1 to zero. Further, the terminal device sends URLLC data on the first resource again, and restarts the counter 1 when canceling sending eMBB data, and counts the number of times that eMBB data is canceled.

For another example, in addition to the above counter 1 being used to count the number of times that eMBB data is canceled, the counter 1 may also be used to count the number of times that URLLC data is sent. When the terminal device determines that the number of times recorded by the counter 1 reaches a first threshold, the counter 1 is cleared to zero, and URLLC data and eMBB data are sent on the first resource. When sending URLLC data on the first resource and canceling sending eMBB data, the counter 1 is restarted to count the number of times URLLC data is sent. For example, the first threshold is three times. As shown in FIG. 5, the terminal device sends URLLC data on the first resource in timeslot 1, timeslot 3, and timeslot 5, and cancels sending eMBB data. The terminal device sends URLLC data on the first resource in time slot 7 and cancels sending eMBB data respectively. The terminal device records URLLC data transmission times 3 times in the counter 1 and the terminal device is in the time slot When sending URLLC data on the first resource of 7 and canceling sending eMBB data, it is determined that the number of times that the terminal device recorded by the counter 1 sends URLLC data reaches a first threshold (3 times). The terminal device may first clear the number of times of the timer 1 and then send URLLC data and eMBB data at the first resource in the time slot 7. Alternatively, the terminal device may first send URLLC data and eMBB data on the first resource in time slot 7, and then reset the number of times of the timer 1 to zero. Alternatively, the terminal device may clear the number of times of the timer 1 when the URLLC data and the eMBB data are sent by the first resource in the time slot 7. Further, the terminal device sends URLLC data on the first resource again, and restarts the counter 1 when canceling sending eMBB data, and counts the number of times that URLLC data is canceled.

For another example, the terminal device may perform statistics on the duration of canceling sending of eMBB data on the first resource by using timer 1. When the terminal device determines that the duration recorded by the timer 1 reaches the first threshold, the timer 1 is cleared to zero, and URLLC data and eMBB data are sent on the first resource. When URLLC data is sent on the first resource and eMBB data is canceled, the timer 1 is restarted to count the duration of canceling eMBB data. For example, the first threshold is 0.3 ms (milliseconds), and the duration of the first resource is 0.1 ms. As shown in FIG. 5, the terminal device sends URLLC data on the first resource in time slot 1, time slot 3, and time slot 5 and cancels sending eMBB data respectively, and the terminal device recorded in the counter 1 cancels sending The duration of eMBB data is 0.3ms. When the terminal device sends URLLC data on the first resource in time slot 7 and cancels sending eMBB data, it is determined that the duration that the terminal device recorded in the timer 1 cancels sending eMBB data reaches the first threshold (0.3 ms). The terminal device may first reset the duration of the timer 1 to zero, and then send URLLC data and eMBB data at the first resource in the time slot 7. Alternatively, the terminal device may first send URLLC data and eMBB data on the first resource in time slot 7, and then clear the duration of the timer 1. Alternatively, the terminal device may clear the duration of the timer 1 when the URLLC data and the eMBB data are sent by the first resource in the time slot 7. Further, the terminal device sends URLLC data on the first resource again, and restarts the timer 1 when canceling sending of eMBB data, and counts the duration of canceling sending of eMBB data.

For another example, the timer 1 may not be used to count the duration of sending eMBB data, and the timer 1 may be used to count the duration of sending URLLC data. When the terminal device determines that the duration recorded by the timer 1 reaches a first threshold, the timer 1 is cleared to zero, and URLLC data and eMBB data are sent on the first resource. When sending URLLC data on the first resource and canceling sending eMBB data, the timer 1 is restarted to count the duration of sending URLLC data. For example, the first threshold is 0.3 ms (milliseconds), and the duration of the first resource is 0.1 ms. As shown in FIG. 5, the terminal device sends URLLC data on the first resource in time slot 1, time slot 3, and time slot 5 and cancels sending eMBB data respectively, and the terminal device recorded by the counter 1 sends URLLC data The duration of the data is 0.3ms. When the terminal device sends URLLC data on the first resource in time slot 7 and cancels sending eMBB data, it is determined that the duration that the terminal device sends URLLC data recorded by the timer 1 reaches the first threshold ( 0.3ms). The terminal device may first reset the duration of the timer 1 to zero, and then send URLLC data and eMBB data at the first resource in the time slot 7. Alternatively, the terminal device may first send URLLC data and eMBB data on the first resource in time slot 7, and then clear the duration of the timer 1. Alternatively, the terminal device may clear the duration of the timer 1 when the URLLC data and the eMBB data are sent by the first resource in the time slot 7. Further, the terminal device sends URLLC data on the first resource again, and restarts the timer 1 when canceling sending of eMBB data, and counts the duration of sending the URLLC data.

It can be seen that, by implementing the method described in FIG. 4, in addition to the manner in which the terminal device sends URLLC data in a time-frequency resource where the URLLC data resource overlaps with the eMBB data resource and cancels sending the eMBB data, the terminal device can also use A method for sending URLLC data and eMBB data in a time-frequency resource where the URLLC data resource overlaps with the eMBB data resource. Therefore, implementing the method described in FIG. 4 is beneficial to improving the communication quality of the eMBB service.

As an optional implementation manner, when the terminal device sends URLLC data and eMBB data on the first resource, the terminal device determines that the number or duration of sending eMBB data on the first resource reaches a second The threshold value, or the duration or number of times that URLLC data is sent reaches a second threshold; the terminal device sends URLLC data on the first resource, and cancels sending eMBB data.

By implementing this embodiment, after a terminal device sends URLLC data on a first resource and cancels sending eMBB data multiple times, it can send URLLC data and eMBB data on the first resource multiple times. The terminal device can The number of times the URLLC data is sent multiple times on the resource or the number of times the eMBB data is sent on the first resource reaches the second threshold. The terminal device sends the URLLC data on the first resource and cancels sending the eMBB data. Alternatively, when the duration that the terminal device sends URLLC data or the eMBB data duration on the first resource reaches a second threshold, the terminal device sends URLLC data on the first resource and cancels sending the eMBB data. Therefore, the terminal device can flexibly switch between the two transmission states.

Exemplarily, after the terminal device sends URLLC data on the first resource and cancels sending eMBB data multiple times, the terminal device sends URLLC data and eMBB data on the first resource once. Alternatively, after the terminal device sends URLLC data on the first resource and cancels sending the eMBB data to a first threshold, the terminal device sends URLLC data and eMBB data on the first resource once. This embodiment of the present application No restrictions.

For example, the terminal device may count the number of times that the eMBB data is canceled on the first resource through the counter 1. When the terminal device determines that the number of times recorded by the counter 1 reaches the first threshold, the counter 1 is cleared to zero, and URLLC data and eMBB data are sent on the first resource. When URLLC data is sent on the first resource and eMBB data is canceled, the counter 1 is restarted to count the number of times that eMBB data is canceled. The terminal device may also count the number of times that the eMBB data is transmitted on the first resource through the counter 2. When the terminal device determines that the number of times recorded by the counter 2 reaches the second threshold, the counter 2 is cleared, URLLC data is transmitted on the first resource, and eMBB data is canceled. When URLLC data and eMBB data are sent on the first resource, the counter 2 is restarted to count the number of times that eMBB data is sent on the first resource.

As shown in FIG. 6, the first threshold value is 3 times, and the second threshold value is 2 times. According to the principle described above, the terminal device sends URLLC data at the first resource in time slot 1, time slot 3, and time slot 5 and cancels sending eMBB data respectively. The terminal device recorded by the counter 1 cancels sending eMBB. The number of times of data is 3 times. When the terminal device sends URLLC data on the first resource in time slot 7 and cancels sending eMBB data, it is determined that the number of times that the terminal device recorded in the counter 1 cancels sending eMBB data reaches a first threshold (3 times). The terminal device clears the number of times of the counter 1 and sends URLLC data and eMBB data on the first resource in time slot 7, and starts the counter 2 to perform the number of times of sending eMBB data on the first resource. count. The terminal device sends URLLC data and eMBB data at the first resource in time slot 9, and the terminal device recorded by the counter 2 sends the eMBB data twice. When the terminal device sends URLLC data and eMBB data on the first resource in time slot 11, the terminal device determines that the number of times that the terminal device recorded in counter 2 sends eMBB data on the first resource reaches a second threshold (2 Times). The terminal device may first clear the number of times of the counter 2 and then send URLLC data at the first resource of the time slot 11 and cancel sending of eMBB data, and start the counter 1 to perform counting. Alternatively, the terminal device may first send URLLC data at the first resource of slot 11 and cancel sending of eMBB data, and start the counter 1 to count, and then clear the number of times of the counter 2 to zero. Alternatively, when the terminal device sends URLLC data in the first resource of time slot 11 and cancels sending eMBB data, the terminal device clears the number of times of the counter 2 to zero.

For another example, the terminal device may also count the number of times that the URLLC data is sent through the counter 1. When the terminal device determines that the number of times recorded by the counter 1 reaches the first threshold, the counter 1 is cleared, and URLLC data and eMBB data are sent on the first resource. When sending URLLC data on the first resource and canceling sending eMBB data, the counter 1 is restarted to count the number of times URLLC data is sent. The terminal device may also count the number of times that the URLLC data is sent on the first resource through the counter 2. When the terminal device determines that the number of times recorded by the counter 2 reaches a second threshold value, the counter 2 is cleared to zero The first resource sends URLLC data and cancels sending eMBB data. When sending URLLC data and sending eMBB data on the first resource, the counter 2 is restarted to count the number of times that URLLC data is sent.

As shown in FIG. 6, the first threshold value is 3 times, and the second threshold value is 2 times. According to the principle described above, the terminal device sends URLLC data at the first resource in timeslot 1, timeslot 3, and timeslot 5, and cancels sending eMBB data respectively. The number of times the terminal device sends URLLC data recorded by the counter 1 is 3. Times. When the terminal device sends URLLC data on the first resource in time slot 7 and cancels sending eMBB data, it is determined that the number of times that the terminal device records URLLC data recorded by the counter 1 reaches the first threshold (3 times) . The terminal device clears the number of times of the counter 1 and sends URLLC data and eMBB data on the first resource in time slot 7, and starts the counter 2 to send URLLC data on the first resource. The number of times is counted. The terminal device sends URLLC data and eMBB data at the first resource in time slot 9, and the terminal device records the number of times that the terminal device sends URLLC data recorded by the counter 2. When the terminal device sends URLLC data and eMBB data on the first resource in time slot 11, the terminal device determines that the number of times that the terminal device sends URLLC data on the first resource recorded by the counter 2 reaches the second threshold ( 2 times). The terminal device may first clear the number of times of the counter 2 and then send URLLC data at the first resource in the time slot 11 and cancel sending of eMBB data, and start the counter 1 to count. Alternatively, the terminal device may first send URLLC data on the first resource in slot 11 and cancel sending eMBB data, and start the counter 1 to count, and then clear the number of times of the counter 2 to zero. Alternatively, when the terminal device sends URLLC data to the first resource in time slot 11 and cancels sending eMBB data, the terminal device clears the number of times of the counter 2 to zero.

For another example, the terminal device can time the duration of canceling the sending of eMBB data on the first resource by using timer 1. When the terminal device determines that the duration recorded by the timer 1 reaches the first threshold, the timer 1 is cleared to zero, and URLLC data and eMBB data are sent on the first resource. When URLLC data is sent on the first resource and eMBB data is canceled, the timer 1 is restarted to count the duration of canceling eMBB data. The terminal device may also time the duration of sending the eMBB data on the first resource by using timer 2. When the terminal device determines that the duration recorded by the timer 2 reaches the second threshold, the timer 2 is cleared, URLLC data is sent on the first resource, and eMBB data is canceled. When sending URLLC data and eMBB data on the first resource, restarting the timer 2 to count the duration of sending eMBB data on the first resource.

As shown in FIG. 6, the first threshold is 0.3 ms, the second threshold is 0.2 ms, and the duration of the first resource is 0.1 ms. According to the previously described principle, the terminal device sends URLLC data at the first resource in time slot 1, time slot 3, and time slot 5, and cancels sending eMBB data respectively. The terminal device recorded by the timer 1 The time to cancel sending eMBB data is 0.3ms. When the terminal device sends URLLC data on the first resource in time slot 7 and cancels sending eMBB data, it is determined that the duration that the terminal device recorded in the timer 1 cancels sending eMBB data reaches a first threshold (0.3 ms). The terminal device clears the duration of the timer 1 and sends URLLC data and eMBB data on the first resource in time slot 7, and starts the timer 2 to send eMBB on the first resource The duration of the data is counted. The terminal device sends URLLC data and eMBB data at the first resource in time slot 9, and the time duration for the terminal device to send eMBB data recorded by the timer 2 is 0.2 ms. When the terminal device sends URLLC data and eMBB data on the first resource in time slot 11, the terminal device determines that the duration that the terminal device recorded by the timer 2 sends eMBB data on the first resource reaches the The second threshold (0.2ms). The terminal device may first clear the duration of the timer 2 and then send URLLC data at the first resource of the time slot 11 and cancel sending of eMBB data, and start the timer 1 to count. Alternatively, the terminal device may first send URLLC data on the first resource in slot 11 and cancel sending of eMBB data, and start the timer 1 to count, and then reset the duration of the timer 2 to zero. Alternatively, when the terminal device sends URLLC data to the first resource in time slot 11 and cancels sending eMBB data, the terminal device clears the duration of the timer 2 to zero.

For another example, the terminal device can time the duration of sending URLLC data by using timer 1. When the terminal device determines that the time length recorded by the timer 1 reaches the first threshold, the timer 1 is cleared to zero, and URLLC data and eMBB data are sent on the first resource. When sending URLLC data on the first resource and canceling sending eMBB data, the timer 1 is restarted to count the duration of sending URLLC data. The terminal device may also time the duration of sending the URLLC data through the timer 2. When the terminal device determines that the duration recorded by the timer 2 reaches the second threshold, the timer 2 is cleared, URLLC data is sent on the first resource, and eMBB data is canceled. When sending URLLC data and sending eMBB data on the first resource, restart the timer 2 to count the duration of sending URLLC data.

As shown in FIG. 6, the first threshold is 0.3 ms, the second threshold is 0.2 ms, and the duration of the first resource is 0.1 ms. According to the previously described principle, the terminal device sends URLLC data at the first resource in timeslot 1, timeslot 3, and timeslot 5, and cancels sending eMBB data respectively. The terminal device recorded by timer 1 sends URLLC. The duration of the data is 0.3ms. When the terminal device sends URLLC data on the first resource in time slot 7 and cancels sending eMBB data, it is determined that the duration of sending the URLLC data by the terminal device recorded by the timer 1 reaches the first threshold (0.3ms ). The terminal device clears the duration of the timer 1 and sends URLLC data and eMBB data on the first resource in time slot 7, and starts the timer 2 to send URLLC on the first resource The duration of the data is counted. The terminal device sends URLLC data and eMBB data at the first resource in time slot 9, and the terminal device records URLLC data sent by the timer 2 for a duration of 0.2 ms. When the terminal device sends URLLC data and eMBB data on the first resource in time slot 11, the terminal device determines that the duration that the terminal device recorded by the timer 2 sends URLLC data on the first resource reaches the first time. Two thresholds (0.2ms). The terminal device may first clear the duration of the timer 2 and then send URLLC data at the first resource of the time slot 11 and cancel sending of eMBB data, and start the timer 1 to count. Alternatively, the terminal device may first send URLLC data on the first resource in slot 11 and cancel sending of eMBB data, and start the timer 1 to count, and then reset the duration of the timer 2 to zero. Alternatively, when the terminal device sends URLLC data to the first resource in time slot 11 and cancels sending eMBB data, the terminal device clears the duration of the timer 2 to zero.

Optionally, the first threshold may be greater than the second threshold, ensuring that more URLLC data is sent on the first resource, and canceling sending eMBB data to ensure that URLLC data is not disturbed. Optionally, the second threshold may be sent by an access network device, that is, the terminal device may receive the second threshold sent by the access network device. This allows flexible configuration of the second threshold.

As an optional implementation manner, the terminal device receives the first target received power value sent by an access network device, and the first target received power value is used when the terminal device sends eMBB data on a second resource, Determine the transmit power for sending eMBB data, and the second resource is a time-frequency resource in which the URLLC data resource and the eMBB data resource do not overlap. For example, the second resource may be a time-frequency resource other than the black part in FIG. 3 to FIG. 6. The first target received power value is a target received power value set by the access network device to the terminal device to send eMBB data on the second resource.

As an optional implementation manner, the terminal device receives a second target received power value sent by the access network device, and the second target received power value is used when the terminal device sends URLLC data and eMBB data in the first resource. To determine the transmit power for sending eMBB data. The second target received power value is a target received power value set by the access network device to the terminal device to send eMBB data on the first resource.

As an optional implementation manner, the first target power value is greater than the second target power value. When the URLLC data and the eMBB data are sent at the same time by the first resource, the eMBB data will cause interference with the URLLC data. By reducing the reception power of the access network device to the eMBB data when the URLLC data and the eMBB data are sent by the first resource, it is beneficial to avoid interference of the eMBB data with the URLLC data.

As an optional implementation manner, the terminal device receives a third threshold value sent by an access network device. When the URLLC data and the eMBB data are sent on the first resource, the modulation and coding strategy MCS of the eMBB data sent by the terminal device is less than or equal to the third threshold. The third threshold may be a smaller value. When sending URLLC data and eMBB data on the first resource, reducing the MCS of the eMBB data is beneficial to avoid interference of the eMBB data with the URLLC data.

As an optional implementation manner, the terminal device receives a third target received power value sent by the access network device, and the third target received power value is used by the terminal device to send URLLC data on the first resource, and cancels When sending eMBB data, determine the transmit power for sending URLLC data. The third target received power value is a target received power value set by the access network device to the terminal device and sending URLLC data on the first resource.

By implementing this embodiment, the third target received power value can be flexibly configured.

As an optional implementation manner, the terminal device receives a fourth target received power value sent by the access network device, and the fourth target received power value is used by the terminal device to send URLLC data and For eMBB data, determine the transmit power for sending URLLC data. The fourth target received power value is a target received power value set by the access network device to the terminal device and sending URLLC data on the first resource.

By implementing this embodiment, the fourth target received power value can be flexibly configured.

As an optional implementation manner, the fourth target power value is greater than the third target power value. By increasing the receiving power of the access network device to the URLLC data when the URLLC data and the eMBB data are sent by the first resource, it is beneficial to avoid interference of the eMBB data with the URLLC data.

As an optional implementation manner, the terminal device receives a fourth threshold sent by an access network device. When the URLLC data and the eMBB data are sent by the first resource, the MCS of the URLLC data sent by the terminal device is less than or equal to the fourth threshold. Optionally, the third threshold is equal to the fourth threshold. Alternatively, the third threshold is not equal to the fourth threshold, for example, the fourth threshold is larger than the third threshold, or the fourth threshold is smaller than the third threshold. When the fourth threshold value is greater than the third threshold value, URLLC data information can be transmitted faster and the delay can be made smaller. When the fourth threshold is smaller than the third threshold, URLLC data information transmission can be made more reliable. The fourth threshold may be a smaller value. When sending URLLC data and eMBB data on the first resource, reducing the MCS of the URLLC data is beneficial to avoid interference of eMBB data with URLLC data.

As an optional implementation manner, the terminal device receives configuration information sent by an access network device, where the configuration information is used to configure a state in which URLLC data is sent on a first resource and cancel sending of eMBB data, and configuration Status of sending URLLC data and eMBB data on the first resource.

That is, two states can be configured on the terminal device. State 1 is a state where URLLC data is sent on the first resource and eMBB data is canceled. State 2 is a state where URLLC data and eMBB data are transmitted on the first resource. When the terminal device is in the state 1, if the terminal device determines that the duration or number of times to cancel sending eMBB data reaches the first threshold, or the duration or number of times to send URLLC data reaches the first threshold, the terminal The device enters state 2 and sends URLLC data and eMBB data on the first resource. When the terminal device is in the state 2, the terminal device determines that the number or duration of sending eMBB data on the first resource reaches the second threshold, or the duration or number of sending URLLC data reaches the second threshold A second threshold, the terminal device enters the state 1, sends URLLC data on the first resource, and cancels sending eMBB data.

By implementing this embodiment, the access network device can flexibly configure the state of the terminal device.

As an optional implementation manner, the access network device may send the time-frequency resources of the URLLC data and the eMBB data to the terminal device to the access network device of the neighboring cell, so that the access network device of the neighboring cell can perform interference coordination. . For example, neighboring cells negotiate time and frequency resources for simultaneous transmission of URLLC data and eMBB data, thereby aligning the moments of interference between the two sides, and avoiding unnecessary interference on resources with only one type of data transmission. Among them, only one type of data transmission resource is a resource for URLLC data transmission only, or only a resource for eMBB data transmission.

Based on the communication system described in FIG. 2, please refer to FIG. 7, which is another communication method provided by an embodiment of the present application. The communication method shown in FIG. 7 is different from the communication method shown in FIG. 4 in that URLLC data and eMBB data in FIG. 4 are sent by the same terminal device, and URLLC data and eMBB data in FIG. 7 are sent by different terminal devices, such as URLLC The data is sent by the second terminal device, and the eMBB data is sent by the first terminal device. Of course, the URLLC data may also be sent by the first terminal device, and the eMBB data is sent by the second terminal device. The present invention does not specifically limit this. As shown in FIG. 7, the communication method includes:

701. The first terminal device determines that the duration or number of times to cancel sending eMBB data reaches a first threshold.

702. The first terminal device sends eMBB data on a first resource.

703. When the second terminal device sends URLLC data on the first resource according to the third target received power value, the second terminal device determines that the duration or number of times that the URLLC data is sent reaches the first threshold.

704. The second terminal device sends URLLC data on the first resource according to a fourth target received power value.

In the embodiment of the present application, after the first terminal device determines that the duration or number of times to cancel sending eMBB data reaches the first threshold, the first terminal device sends the eMBB data on the first resource, and the second After the duration or number of times that the terminal device sends URLLC data reaches the first threshold, the second terminal device sends URLLC data on the first resource according to a fourth target received power value.

The above-mentioned 701, 702, and 703, 704 are not restricted by the order of the temporal relationship. That is, 703 and 704 can be executed first, and then 701 and 702 can be executed. Alternatively, 701 and 702 can be executed first, and then 703 and 704 can be executed.

In the embodiment of the present application, when the first terminal device cancels sending eMBB data on the first resource, the second terminal device sends URLLC data on the first resource according to the third target received power value. . When the first terminal device sends eMBB data on the first resource, the second terminal device sends URLLC data on the first resource according to the fourth target received power value.

For example, as shown in FIG. 3, when the first terminal device cancels sending eMBB data on the first resource in time slot 1, time slot 3, and time slot 5, the second terminal device performs time slot 1, URLLC data is sent on the first resources in timeslots 3 and 5 according to the third target received power value. When the first terminal device sends eMBB data on the first resource in time slot 7, the second terminal device sends URLLC on the first resource in time slot 7 according to the fourth target received power value data.

The third target received power value and the fourth target received power value are target received power values set by the access network device to the second terminal device for sending URLLC data. The third target received power value and the fourth target received power value are used to determine a transmit power at which the second terminal device sends URLLC data on the first resource. Optionally, the fourth target received power is greater than the third target received power. By increasing the receiving power of the access network device to the URLLC data when the first resource sends the URLLC data and the eMBB data, it is beneficial to avoid interference of the eMBB data with the URLLC data.

For example, the first terminal device may count the number of times that the eMBB data is canceled to be sent on the first resource through the counter 1. When the first terminal device determines that the number of times recorded by the counter 1 reaches the first threshold, the counter 1 is cleared to zero, and eMBB data is sent on the first resource. When the sending of the eMBB data is cancelled on the first resource, the counter 1 is restarted to count the number of times that the sending of the eMBB data is cancelled. The second terminal device may count, through the counter 2, the number of times URLLC data is sent on the first resource. When the second terminal device determines that the number of times recorded by the counter 2 reaches the first threshold, the counter 2 is cleared, and URLLC data is sent on the first resource according to the fourth target received power value. When URLLC data is sent on the first resource according to the third target received power value, the counter 2 is restarted to count the number of times that URLLC data is sent on the first resource.

For example, as shown in FIG. 8, the first threshold value is 3 times. The first terminal device cancels sending eMBB data on the first resource in timeslot 1, time slot 3, and time slot 5, respectively, and the number of times that the first terminal device cancels sending eMBB data recorded by the counter 1 is 3 times. The second resource of the second terminal device in slot 1, slot 3, and slot 5 sends URLLC data according to the third target received power value, and the second terminal device recorded by the counter 2 URLLC data is sent three times. The first terminal device determines that the number of times recorded by the counter 1 reaches the first threshold (three times), and then the first terminal device may first clear the number of times of the timer 1 to zero, and then time slot 7 Sending eMBB data on the first resource. Alternatively, the first terminal device may first send eMBB data on the first resource in time slot 7, and then clear the number of times of the timer 1. Alternatively, when the first terminal device sends eMBB data on the first resource in time slot 7, the number of times of the timer 1 is cleared to zero. If the second terminal device determines that the number of times recorded by the counter 2 reaches the first threshold (three times), the second terminal device may first clear the number of times of the timer 2 to zero and then time slot 7 Sending URLLC data on the first resource according to the fourth target received power value. Alternatively, the second terminal device may first send URLLC data according to the fourth target received power value at the first resource in time slot 7, and then clear the number of times of the timer 1. Alternatively, the first terminal device may clear the number of times of the timer 1 when the first resource of the time slot 7 sends URLLC data according to the fourth target received power value.

For another example, the first terminal device may perform statistics on the duration of canceling the sending of eMBB data on the first resource by using timer 1. When the first terminal device determines that the duration recorded by the timer 1 reaches the first threshold, the timer 1 is cleared to zero, and eMBB data is sent on the first resource. When the sending of eMBB data is canceled on the first resource, the first terminal device restarts the timer 1 to count the duration of canceling sending of eMBB data. The second terminal device may perform statistics on the duration of sending URLLC data on the first resource by using the timer 2. When the second terminal device determines that the duration recorded by the timer 2 reaches the first threshold, clear the timer 2 and send the first resource according to the fourth target received power value to send URLLC data. When URLLC data is sent on the first resource according to the third target received power value, the second terminal device restarts the timer 2 to count the duration of canceling sending URLLC data.

For example, the first threshold is 0.3 ms (milliseconds), and the duration of the first resource is 0.1 ms. For example, as shown in FIG. 8, the first terminal device cancels sending eMBB data on the first resources in timeslot 1, timeslot 3, and timeslot 5, respectively, and the first terminal device recorded by timer 1 The time to cancel sending eMBB data is 0.3ms. Sending, by the second terminal device, URLLC data on the first resource of time slot 1, time slot 3, and time slot 5 according to the third target received power value, and the second terminal device recorded by the timer 2 The duration of sending URLLC data is 0.3ms. The first terminal device determines that the duration recorded by the timer 1 reaches a first threshold (0.3ms), and then the first terminal device may first clear the duration of the timer 1 to zero, and Sending eMBB data on the first resource. Alternatively, the first terminal device may first send eMBB data on the first resource in time slot 7, and then clear the duration of the timer 1. Alternatively, when the first terminal device sends eMBB data on the first resource in time slot 7, the duration of the timer 1 is cleared to zero. If the second terminal device determines that the duration recorded by the timer 2 reaches the first threshold (0.3ms), the second terminal device may first clear the duration of the timer 2 to zero, and then The URLLC data is sent on the first resource of 7 according to the fourth target received power value. Alternatively, the second terminal device may first send URLLC data according to the fourth target received power value at the first resource in time slot 7, and then reset the duration of the timer 2 to zero. Alternatively, the first terminal device may clear the duration of the timer 2 when the first resource of time slot 7 sends URLLC data according to the fourth target received power value.

It can be seen that by implementing the method described in FIG. 7, the first terminal device does not always cancel sending eMBB data at time-frequency resources where the URLLC data resource overlaps with the eMBB data resource. Time-frequency resources with overlapping data resources can also send eMBB data. Therefore, implementing the method described in FIG. 7 is beneficial to improving the communication quality of the eMBB service.

As an optional implementation manner, the first terminal device determines that the number or duration of sending eMBB data on the first resource reaches a second threshold; the first terminal device cancels sending on the first resource eMBB data. When the second terminal device sends URLLC data on the first resource according to the fourth target received power value, the second terminal device determines that the number or duration of sending URLLC data on the first resource reaches the The second threshold; the second terminal device sends URLLC data on the first resource according to the third target received power value.

In this implementation manner, after the first terminal device cancels sending eMBB data on the first resource one or more times, the first terminal device may send eMBB data on the first resource multiple times. After the second terminal device sends URLLC data on the first resource according to the third target received power value one or more times, the second terminal device sends URLLC on the first resource according to the fourth target received power value. data. After the time when the first terminal device cancels sending eMBB data on the first resource reaches the first threshold, the time when the eMBB data is sent on the first resource may reach the second threshold. After sending, by the second terminal device, URLLC data one or more times according to the third target received power value on the first resource, sending URLLC data according to the fourth target received power value on the first resource The duration may reach the second threshold. Certainly, after the first terminal device cancels sending the eMBB data on the first resource one or more times, the first terminal device may send the eMBB data on the first resource once. And after the second terminal device sends URLLC data one or more times according to the third target received power value on the first resource, it sends one time according to the fourth target received power value on the first resource. URLLC data. Alternatively, after the duration that the first terminal device cancels sending the eMBB data on the first resource reaches the first threshold, the first terminal device sends the eMBB data on the first resource once. After the second terminal device sends URLLC data according to the third target receiving power value on the first resource, the duration of sending URLLC data reaches the first threshold, and then performs one time on the first resource according to the fourth target. The received power value sends URLLC data.

For example, the first terminal device may count the number of times that the eMBB data is canceled to be sent on the first resource through the counter 1. When the first terminal device determines that the number of times recorded by the counter 1 reaches the first threshold, the counter 1 is cleared to zero, and eMBB data is sent on the first resource. When the sending of the eMBB data is cancelled on the first resource, the counter 1 is restarted to count the number of times that the sending of the eMBB data is cancelled. The first terminal device may also count the number of times that the eMBB data is transmitted on the first resource through the counter 2. When the first terminal device determines that the number of times recorded by the counter 2 reaches the second threshold, the counter 2 is cleared to zero, and the eMBB data is canceled from being transmitted on the first resource. When sending eMBB data on the first resource, restarting the counter 2 counts the number of times eMBB data is sent on the first resource.

The second terminal device may count, through the counter 3, the number of times that the URLLC data is sent on the first resource. When the second terminal device determines that the number of times recorded by the counter 3 reaches the first threshold, clear the counter 3 and send URLLC data according to the fourth target received power value at the first resource . When URLLC data is sent on the first resource according to the third target received power value, the counter 3 is restarted to count the number of times that URLLC data is sent. The second terminal device may also count the number of times that the URLLC data is sent on the first resource through the counter 4. When the second terminal device determines that the number of times recorded by the counter 4 reaches the second threshold, clear the counter 4 and send URLLC data on the first resource according to the third target received power value . When URLLC data is sent on the first resource according to the fourth target received power value, the counter 4 is restarted to count the number of times that URLLC data is sent on the first resource.

For example, as shown in FIG. 9, the first threshold value is 3 times, and the second threshold value is 2 times. According to the previously described principle, the first resource of the second terminal device in timeslot 1, timeslot 3, and timeslot 5 respectively sends URLLC data according to the received power value of the third target. The first resource sends URLLC data three times. The first terminal device cancels sending eMBB data on the first resource in timeslot 1, timeslot 3, and timeslot 5, respectively, and the number of times that the counter 1 cancels sending eMBB data on the first resource is 3 Times.

After the first terminal device determines that the number of times recorded by the counter 1 reaches the first threshold (three times), it clears the number of times of the counter 1 and sends eMBB data at the first resource in the time slot 7 And start the counter 2 to count the number of times eMBB data is sent on the first resource. The first terminal device sends eMBB data on the first resource in time slot 9, and the number of times recorded by the counter 2 is two. The first terminal device determines that the number of times recorded by the counter 2 reaches a second threshold (2 times), and the first terminal device may first clear the number of times of the counter 2 to zero, and then in the first time slot 11 A resource cancels sending eMBB data and starts the counter 1 to count. Alternatively, the first terminal device may cancel sending the eMBB data on the first resource in the time slot 11 and start the counter 1 to count, and then clear the number of times of the timer 2 to zero. Alternatively, when the first terminal device cancels sending the eMBB data by the first resource in time slot 11, the number of times of the timer 2 is cleared to zero.

After the second terminal device determines that the number of times recorded by the counter 3 reaches the first threshold (three times), the number of times of the counter 3 is cleared, and the first resource in the time slot 7 is determined according to the first resource. The fourth target receives the power value to send URLLC data, and starts the counter 4 to count the number of times URLLC data is sent on the first resource. The second terminal device sends URLLC data according to the fourth target received power value in the first resource in time slot 9, and the number of times recorded by the counter 4 is two. The second terminal device determines that the number of times recorded by the counter 4 reaches the second threshold (2 times), and the second terminal device may first clear the number of times of the counter 4 to zero, and The first resource sends URLLC data according to the third target received power value, and starts the counter 3 to count. Alternatively, the first terminal device may first send URLLC data according to the third target received power value at the first resource in time slot 11, and start the counter 3 to count, and then count the The number of times is cleared. Alternatively, the first terminal device may clear the number of times of the timer 4 when the first resource of the time slot 11 sends URLLC data according to the third target received power value.

For another example, the first terminal device may time the duration of canceling sending of eMBB data on the first resource by using timer 1. When the first terminal device determines that the duration recorded by the timer 1 reaches the first threshold, the timer 1 is cleared to zero, and eMBB data is sent on the first resource. When the sending of eMBB data is canceled on the first resource, the timer 1 is restarted to count the duration of canceling sending of eMBB data. The first terminal device may also use a timer 2 to time the duration of sending the eMBB data on the first resource. When the first terminal device determines that the duration recorded by the timer 2 reaches the second threshold, Clear the timer 2 and cancel sending eMBB data on the first resource. When sending eMBB data on the first resource, restarting the timer 2 to count the duration of sending eMBB data on the first resource.

The second terminal device may time the duration of sending the URLLC data in the first resource through the timer 3. When the second terminal device determines that the duration recorded by the timer 3 reaches the first threshold, clear the timer 3 and send the first resource according to the fourth target received power value to send URLLC data. When URLLC data is sent on the first resource according to the third target received power value, the timer 3 is restarted to count the duration of sending URLLC data. The second terminal device may also time the duration of sending the URLLC data in the first resource through the timer 4. When the second terminal device determines that the duration recorded by the timer 4 reaches the second threshold, clear the timer 4 and send the first resource according to the third target received power value to send URLLC data. When URLLC data is sent on the first resource according to the fourth target received power value, the timer 4 is restarted to count the duration of sending URLLC data on the first resource. That is, the timer 3 counts the duration of sending URLLC data at the first resource according to the third target receiving power value, and the timer 4 counts the time at which the first resource receives the URLLC data according to the fourth target. Duration of URLLC data sent by the power value.

For example, as shown in FIG. 9, the first threshold value is 0.3 ms, the second threshold value is 0.2 ms, and the duration of the first resource is 0.1 ms. According to the previously described principle, the first resource of the second terminal device in timeslot 1, timeslot 3, and timeslot 5 respectively sends URLLC data according to the received power value of the third target, and the timer 3 records The duration of sending URLLC data in the first resource is 0.3 ms. The first terminal device cancels sending eMBB data at the first resource in timeslot 1, time slot 3, and time slot 5, respectively, and the duration recorded by timer 1 to cancel sending eMBB data at the first resource is 0.3ms.

After the first terminal device determines that the duration recorded by the timer 1 reaches a first threshold (0.3 ms), it clears the duration of the timer 1 to zero, and sends eMBB data at the first resource in the time slot 7 And start the timer 2 to time the duration of sending eMBB data on the first resource. The first terminal device sends eMBB data at the first resource in time slot 9, and the duration recorded by the timer 2 is 0.2 ms. The first terminal device determines that the duration recorded by the timer 2 reaches a second threshold value (0.2 ms), and the first terminal device may first clear the duration of the timer 2 to zero, and then reset the duration of the timer 2 at time slot 11. The first resource cancels sending the eMBB data, and starts the timer 1 to perform timing. Alternatively, the first terminal device may cancel sending the eMBB data at the first resource of the time slot 11 and start the timer 1 to perform timing, and then clear the duration of the timer 2 to zero. Alternatively, when the first terminal device cancels sending the eMBB data by the first resource in time slot 11, the duration of the timer 2 is cleared to zero.

After the second terminal device determines that the duration recorded by the timer 3 reaches a first threshold (0.3 ms), clearing the duration of the timer 3 to zero, and according to the first resource in the time slot 7 according to the first resource The fourth target receives the power value to send URLLC data, and starts the timer 4 to time the duration of sending the URLLC data on the first resource. The second terminal device sends URLLC data according to the fourth target received power value in the first resource in time slot 9, and the duration recorded by the timer 4 is 0.2 ms. The second terminal device determines that the duration recorded by the timer 4 reaches the second threshold (0.3ms), and the second terminal device may first clear the duration of the timer 4 to zero and then time slot 11 The first resource sends URLLC data according to the third target received power value, and starts the timer 3 for timing. Alternatively, the first terminal device may first send URLLC data according to the third target received power value at the first resource in time slot 11, and start the timer 3 to time, and then set the timer 4 The duration is cleared. Alternatively, the first terminal device may clear the duration of the timer 4 when the first resource of the time slot 11 sends URLLC data according to the third target received power value.

Optionally, the first threshold may be sent by an access network device, that is, the second terminal device and the first terminal device may receive the first threshold sent by the access network device. This allows flexible configuration of the first threshold.

Optionally, the second threshold may be sent by an access network device, that is, the second terminal device and the first terminal device may receive a second threshold sent by the access network device. This allows flexible configuration of the second threshold.

As an optional implementation manner, the first terminal device may further receive a first target received power value sent by an access network device, and the first target received power value is used by the first terminal device to send on a second resource. When the eMBB data is transmitted, the transmission power for sending the eMBB data is determined, and the second resource is a time-frequency resource in which the URLLC data resource and the eMBB data resource do not overlap. The first target received power value is a target received power value set by the access network device to the first terminal device to send eMBB data on the second resource.

As an optional implementation manner, the first terminal device receives a second target received power value sent by an access network device, and the second target received power value is used by the first terminal device to send eMBB data on a first resource. At that time, determine the transmit power for sending eMBB data. The second target received power value is a target received power value set by the access network device to the first terminal device to send eMBB data on the first resource.

As an optional implementation manner, the first target power value is greater than the second target power value. By implementing this implementation mode, it is beneficial to avoid interference of eMBB data with URLLC data.

As an optional implementation manner, the first terminal device receives a third threshold value sent by an access network device, and when eMBB data is sent on a first resource, modulation of the eMBB data sent by the first terminal device The MCS is smaller than or equal to the third threshold. By implementing this implementation mode, it is beneficial to avoid interference of eMBB data with URLLC data.

As an optional implementation manner, the second terminal device may receive the third target received power value sent by an access network device.

As an optional implementation manner, the second terminal device may receive the fourth target received power value sent by an access network device.

As an optional implementation manner, the fourth target power value is greater than the third target power value. By implementing this implementation mode, it is beneficial to avoid interference of eMBB data with URLLC data.

As an optional implementation manner, the second terminal device receives a fourth threshold value sent by an access network device, and when sending URLLC data on the first resource according to the fourth target received power value, all the The MCS of the URLLC data sent by the second terminal device is less than or equal to the fourth threshold. Optionally, the third threshold is equal to the fourth threshold. Alternatively, the third threshold is not equal to the fourth threshold, for example, the fourth threshold is larger than the third threshold, or the fourth threshold is smaller than the third threshold. When the fourth threshold value is greater than the third threshold value, URLLC data information can be transmitted faster and the delay can be made smaller. When the fourth threshold is smaller than the third threshold, URLLC data information transmission can be made more reliable. The fourth threshold may be a smaller value. When URLLC data is sent on the first resource according to the fourth target received power value, reducing the MCS of the URLLC data is beneficial to avoid interference of eMBB data with URLLC data.

As an optional implementation manner, the first terminal device receives configuration information sent by an access network device, where the configuration information is used to configure a state in which eMBB data is canceled on the first resource and configured on the first resource. Status of the resource sending eMBB data.

By implementing this embodiment, the access network device can flexibly configure the state of the first terminal device.

As an optional implementation manner, the second terminal device receives configuration information sent by an access network device, where the configuration information is used to configure the first resource to send according to the third target received power value. A state of the URLLC data, and a state configured in the first resource to send the URLLC data according to the fourth target received power value.

By implementing this embodiment, the access network device can flexibly configure the state of the second terminal device.

As an optional implementation manner, the access network device may send the time-frequency resource of the second terminal device to send URLLC data according to the fourth target received power value to the access network device of the neighboring cell, thereby accessing the neighboring cell. Network equipment for interference coordination. For example, neighboring cells negotiate time and frequency resources for simultaneous transmission of URLLC data and eMBB data, thereby aligning the moments of interference between the two sides, and avoiding unnecessary interference on resources with only one type of data transmission. Among them, only one type of data transmission resource is a resource for URLLC data transmission only, or only a resource for eMBB data transmission.

It is stated throughout the text that any one of the thresholds (such as any of the first threshold, the second threshold, the third threshold, and the fourth threshold) is greater than or equal to the corresponding threshold.

Although the embodiments of the present application may use the terms first, second, third, etc. to describe various kinds of information, the information should not be limited to these terms. These terms are used to distinguish the same type of information from each other. For example, without departing from the scope of the present invention, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information.

In the embodiment of the present invention, the device may be divided into functional modules according to the foregoing method example. For example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one module. The above integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of the modules in the embodiment of the present invention is schematic, and is only a logical function division. In actual implementation, there may be another division manner.

Please refer to FIG. 10, which is a communication device provided by an implementation of the present invention. The communication device may be used to perform a behavioral function of the terminal device in FIG. 4. The structure of the communication device is briefly described below. For specific functions and features, please refer to the method embodiments, and details are not described herein again. The communication device includes: a communication module 1001 and a processing module 1002. among them:

The processing module 1002 is configured to send URLLC data on a first resource and cancel sending eMBB data, and determine that the duration or number of times to cancel sending eMBB data reaches a first threshold, or the duration or number of times to send URLLC data reaches the A threshold, wherein the first resource is a time-frequency resource in which the URLLC data resource and the eMBB data resource overlap; the communication module 1001 is configured to: after the processing module 1002 determines that the first threshold is reached, URLLC data and eMBB data are sent on the resource.

Optionally, the processing module 1002 is further configured to determine that when the communication module 1001 sends URLLC data and eMBB data on the first resource, the number or duration of sending eMBB data on the first resource reaches The second threshold, or the duration or number of times that URLLC data is sent reaches the second threshold; the communication module 1001 is further configured to send the URLLC data on the first resource after the processing module 1002 determines that the second threshold is reached And cancel sending eMBB data.

Optionally, the communication module 1001 is further configured to receive a first target received power value sent by an access network device, where the first target received power value is used to determine to send eMBB data when the second resource sends eMBB data. And the second resource is a time-frequency resource whose URLLC data resource and eMBB data resource do not overlap.

Optionally, the communication module 1001 is further configured to receive a second target received power value sent by the access network device, where the second target received power value is used by the communication module 1001 to send URLLC data and For eMBB data, determine the transmit power for sending eMBB data.

Optionally, the first target power value is greater than the second target power value.

Optionally, the communication module 1001 is further configured to receive a third threshold value sent by an access network device, where when sending URLLC data and eMBB data on the first resource, the eMBB data sent by the communication module 1001 The modulation and coding strategy MCS is less than or equal to the third threshold.

Optionally, the communication module 1001 is further configured to receive a third target received power value sent by an access network device, where the third target received power value is used to send URLLC data on the first resource, and cancel When sending eMBB data, determine the transmit power for sending URLLC data.

Optionally, the communication module 1001 is further configured to receive a fourth target received power value sent by an access network device, where the fourth target received power value is used to send URLLC data and eMBB data on the first resource. , Determine the transmit power for sending URLLC data.

Optionally, the fourth target power value is greater than the third target power value.

Optionally, the communication module 1001 is further configured to receive a fourth threshold sent by an access network device, where when the first resource sends URLLC data and eMBB data, the MCS of the URLLC data sent by the communication device is less than or equal to The fourth threshold.

Optionally, the communication module 1001 is further configured to receive configuration information sent by an access network device, where the configuration information is used to configure sending of URLLC data on the first resource and canceling a status of sending eMBB data, And a state configured to send URLLC data and eMBB data on the first resource.

Optionally, the communication module 1001 is further configured to receive the first threshold value sent by an access network device.

Optionally, the communication module 1001 is further configured to receive the second threshold value sent by an access network device.

Please refer to FIG. 10, which is a communication device provided by an implementation of the present invention. The communication device may be configured to perform a behavior function of the first terminal device in the method described in FIG. 7. The communication device includes: a communication module 1001 and a processing module 1002. among them:

The processing module 1002 is configured to determine that the duration or number of times to cancel sending eMBB data reaches a first threshold; the communication module 1001 is configured to send on a first resource after the processing module 1002 reaches the first threshold The eMBB data, wherein the first resource is a time-frequency resource in which the URLLC data resource and the eMBB data resource overlap.

Optionally, the processing module 1002 is further configured to determine that the number or duration of sending eMBB data on the first resource reaches a second threshold; the processing module 1002 is further configured to reach the first threshold when the processing module 1002 reaches the first threshold. After two thresholds, cancel sending eMBB data on the first resource.

Optionally, the communication module 1001 is further configured to receive a second target received power value sent by the access network device, where the second target received power value is used to determine transmission of sending eMBB data when the first resource sends eMBB data power.

Optionally, the communication module 1001 is further configured to receive a third threshold value sent by an access network device. When the eMBB data is sent on the first resource, the modulation and coding strategy MCS of the sent eMBB data is less than or Equal to the third threshold.

Optionally, the communication module 1001 is further configured to receive configuration information sent by an access network device, where the configuration information is used to configure a state in which the first resource cancels sending eMBB data, and is configured in the Status of the first resource sending eMBB data.

Please refer to FIG. 10, which is a communication device provided by an implementation of the present invention. The communication device may be used to perform a behavior function of the second communication device in the method described in FIG. 7. The communication device includes: a communication module 1001 and a processing module 1002. among them:

The processing module 1002 is configured to determine that, when the URLLC data is sent on the first resource according to the third target received power value, the duration or number of times that the URLLC data is sent reaches a first threshold. The communication module 1001 is configured to send URLLC data on the first resource according to a fourth target received power value after the processing module 1002 reaches the first threshold, where the first resource is URLLC data Time-frequency resources whose resources overlap with eMBB data resources.

Optionally, the processing module 1002 is further configured to, when sending URLLC data on the first resource according to the fourth target received power value, determine that the number or duration of sending URLLC data on the first resource reaches A second threshold; the communication module 1001 is further configured to send URLLC data on the first resource according to the third target received power value after the processing module 1002 reaches the second threshold.

Optionally, the communication module 1001 is further configured to receive the third target received power value sent by an access network device.

Optionally, the communication module 1001 is further configured to receive the fourth target received power value sent by an access network device.

Optionally, the communication module 1001 is further configured to receive a fourth threshold value sent by an access network device, wherein when the URLLC data is sent on the first resource according to the fourth target received power value, the communication The modulation and coding strategy MCS of the URLLC data sent by the module 1001 is less than or equal to the fourth threshold.

Optionally, the communication module 1001 is further configured to receive configuration information sent by an access network device, where the configuration information is configured to configure the first resource to send URLLC data according to the third target received power value. And a state configured in the first resource to send URLLC data according to the fourth target received power value.

Please refer to FIG. 11, which is a schematic structural diagram of a communication device disclosed in an embodiment of the present application. The communication device may perform the behavior function of the terminal device shown in FIG. 4 or the first terminal device or the second terminal device shown in FIG. 7 in the foregoing method embodiment. As shown in FIG. 11, the communication device 1100 includes a processor 1101, a memory 1102, and a communication interface 1103. The processor 1101 and the memory 1102 are connected to the communication interface 1103.

The processor 1101 may be a central processing unit (CPU), a general-purpose processor, a coprocessor, a digital signal processor (DSP), and an application-specific integrated circuit (ASIC). Field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The processor 1101 may also be a combination that implements computing functions, such as a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on.

The communication interface 1103 is used to implement communication with other network elements (such as an access network device).

The processor 1101 calls the program code stored in the memory 1102 to execute the steps performed by the terminal device, the first terminal device, or the second terminal device in the foregoing method embodiment.

In the above embodiments, the description of each embodiment has its own emphasis. For a part that is not described in detail in one embodiment, reference may be made to related descriptions in other embodiments.

Finally, it should be noted that the above embodiments are only used to describe the technical solution of the present application, rather than limiting it. Although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: The technical solutions described in the foregoing embodiments can still be modified, or some or all of the technical features can be equivalently replaced; and these modifications or replacements do not deviate the essence of the corresponding technical solutions from the technical solutions of the embodiments of this application range.

Claims

A communication method, characterized in that the method includes:

When the terminal device sends high-reliability low-latency communication URLLC data on the first resource and cancels sending enhanced mobile broadband eMBB data, the terminal device determines that the duration or number of times to cancel sending eMBB data reaches a first threshold, or sends URLLC data The duration or number of times reaches the first threshold, wherein the first resource is a time-frequency resource in which the URLLC data resource and the eMBB data resource overlap;

The terminal device sends URLLC data and eMBB data on the first resource.
The method according to claim 1, wherein when the terminal device sends URLLC data and eMBB data on the first resource, the method further comprises:

Determining, by the terminal device, that the number or duration of sending eMBB data on the first resource reaches a second threshold, or that the duration or number of sending URLLC data reaches the second threshold;

The terminal device sends URLLC data on the first resource, and cancels sending eMBB data.
The method according to claim 1 or 2, further comprising:

Receiving, by the terminal device, a first target received power value sent by an access network device, where the first target received power value is used by the terminal device to determine transmit power for sending eMBB data when the second resource sends eMBB data, and The second resource is a time-frequency resource in which the URLLC data resource and the eMBB data resource do not overlap.
The method according to any one of claims 1 to 3, wherein the method further comprises:

Receiving, by the terminal device, a second target received power value sent by the access network device, where the second target received power value is used by the terminal device to determine to send eMBB data when the first resource sends URLLC data and eMBB data Transmit power.
The method according to any one of claims 1 to 4, further comprising:

The terminal device receives a third threshold sent by the access network device, and when URLLC data and eMBB data are sent on the first resource, the modulation and coding strategy MCS of the eMBB data sent by the terminal device is less than or Is equal to the third threshold.
The method according to any one of claims 1 to 5, further comprising:

Receiving, by the terminal device, a third target received power value sent by the access network device, where the third target received power value is used by the terminal device to send URLLC data on the first resource and cancel sending eMBB data , Determine the transmit power for sending URLLC data.
The method according to any one of claims 1 to 6, wherein the method further comprises:

Receiving, by the terminal device, a fourth target received power value sent by the access network device, where the fourth target received power value is used when the terminal device sends URLLC data and eMBB data on the first resource, and determines Transmit power for sending URLLC data.
The method according to any one of claims 1 to 7, wherein the method further comprises:

The terminal device receives a fourth threshold sent by the access network device, and when the URLLC data and the eMBB data are sent by the first resource, the MCS of the URLLC data sent by the terminal device is less than or equal to the fourth threshold.
The method according to any one of claims 1 to 8, wherein the method further comprises:

Receiving, by the terminal device, configuration information sent by the access network device, where the configuration information is used to configure sending of URLLC data on a first resource and cancel sending of eMBB data, and configuring sending on the first resource Status of URLLC data and eMBB data.
A communication method, characterized in that the method includes:

The terminal device determines that the duration or number of times to cancel sending enhanced mobile broadband eMBB data reaches a first threshold;

The terminal device sends eMBB data on a first resource, where the first resource is a time-frequency resource in which high-reliability low-latency communication URLLC data resource and eMBB data resource overlap.
The method according to claim 10, further comprising:

Determining, by the terminal device, that the number or duration of sending eMBB data on the first resource reaches a second threshold;

The terminal device cancels sending eMBB data on the first resource.
The method according to claim 10 or 11, further comprising:

Receiving, by the terminal device, a first target received power value sent by an access network device, where the first target received power value is used by the terminal device to determine transmit power for sending eMBB data when the second resource sends eMBB data, and The second resource is a time-frequency resource in which the URLLC data resource and the eMBB data resource do not overlap.
The method according to any one of claims 10 to 12, wherein the method further comprises:

Receiving, by the terminal device, a second target received power value sent by the access network device, where the second target received power value is used by the terminal device to determine transmit power for sending eMBB data when the first resource sends eMBB data .
The method according to any one of claims 10 to 13, wherein the method further comprises:

Receiving, by the terminal device, a third threshold value sent by the access network device, wherein when the eMBB data is sent on the first resource, the modulation and coding strategy MCS of the eMBB data sent by the terminal device is less than or equal to the third Threshold.
The method according to any one of claims 10 to 14, wherein the method further comprises:

The terminal device receives configuration information sent by the access network device, where the configuration information is used to configure a state in which eMBB data is canceled and sent in the first resource.
The method according to any one of claims 1 to 15, wherein the method further comprises:

Receiving, by the terminal device, the first threshold value sent by the access network device.
The method according to claim 2 or 11, further comprising:

Receiving, by the terminal device, the second threshold value sent by the access network device.
A communication device, characterized in that the communication device includes:

A processing module, configured to send high-reliability low-latency communication URLLC data on the first resource and cancel sending enhanced mobile broadband eMBB data, determine whether the duration or number of times to cancel sending eMBB data reaches the first threshold, or The duration or number of times reaches the first threshold, wherein the first resource is a time-frequency resource in which the URLLC data resource and the eMBB data resource overlap;

The communication module is configured to send URLLC data and eMBB data on the first resource after the processing module determines that the first threshold is reached.
The communication device according to claim 18, wherein:

The processing module is further configured to determine, when the communication module sends URLLC data and eMBB data on the first resource, that the number or duration of sending eMBB data on the first resource reaches a second threshold, or The duration or number of times of sending URLLC data reaches the second threshold;

The communication module is further configured to send URLLC data on the first resource and cancel sending eMBB data after the processing module determines that a second threshold is reached.
The communication device according to claim 18 or 19, wherein

The communication module is further configured to receive a first target received power value sent by an access network device, where the first target received power value is used by the communication module to determine when to send eMBB data when the second resource sends eMBB data. Transmit power, the second resource is a time-frequency resource in which the URLLC data resource and the eMBB data resource do not overlap.
The communication device according to any one of claims 18 to 20, wherein

The communication module is further configured to receive a second target received power value sent by the access network device, where the second target received power value is used when the communication module sends URLLC data and eMBB data at a first resource, Determine the transmit power for sending eMBB data.
The communication device according to any one of claims 18 to 21, wherein

The communication module is further configured to receive a third threshold value sent by the access network device, where, when URLLC data and eMBB data are sent on the first resource, the modulation and coding of the eMBB data sent by the communication module The policy MCS is less than or equal to the third threshold.
The communication device according to any one of claims 18 to 22, wherein

The communication module is further configured to receive a third target received power value sent by the access network device, where the third target received power value is used by the communication module to send URLLC data on the first resource, and When canceling sending eMBB data, determine the transmit power for sending URLLC data.
The communication device according to any one of claims 18 to 23, wherein

The communication module is further configured to receive a fourth target received power value sent by the access network device, where the fourth target received power value is used by the communication module to send URLLC data and eMBB on the first resource. When transmitting data, determine the transmit power for sending URLLC data.
The communication device according to any one of claims 18 to 24, wherein

The communication module is further configured to receive a fourth threshold sent by the access network device, wherein when the URLLC data and the eMBB data are sent by the first resource, the MCS of the URLLC data sent by the communication module is less than or equal to the first Four thresholds.
The communication device according to any one of claims 18 to 25, wherein

The communication module is further configured to receive configuration information sent by the access network device, where the configuration information is used to configure a state in which URLLC data is sent at a first resource, and cancel sending of eMBB data, and is configured in the The first resource sends the status of URLLC data and eMBB data.
A communication device, characterized in that the communication device includes:

A processing module, configured to determine that the duration or number of times to cancel sending enhanced mobile broadband eMBB data reaches a first threshold;

A communication module, configured to send eMBB data on a first resource after the processing module determines that the first threshold is reached, where the first resource is a high-reliability low-latency communication URLLC data resource that overlaps with an eMBB data resource Time-frequency resources.
The communication device according to claim 27, wherein

The processing module is further configured to determine that the number or duration of sending eMBB data on the first resource reaches a second threshold;

The processing module is further configured to cancel sending eMBB data on the first resource after the processing module determines that the second threshold is reached.
The communication device according to claim 27 or 28, wherein

The communication module is further configured to receive a first target received power value sent by an access network device, where the first target received power value is used by the communication module to determine when to send eMBB data when the second resource sends eMBB data. Transmit power, the second resource is a time-frequency resource in which the URLLC data resource and the eMBB data resource do not overlap.
The communication device according to any one of claims 27 to 29, wherein

The communication module is further configured to receive a second target received power value sent by the access network device, where the second target received power value is used by the communication module to determine to send eMBB when the first resource sends eMBB data. The transmit power of the data.
The communication device according to any one of claims 27 to 30, wherein

The communication module is further configured to receive a third threshold value sent by the access network device. When the eMBB data is sent on the first resource, the modulation and coding strategy MCS of the eMBB data sent by the communication module is less than or equal to The third threshold.
The communication device according to any one of claims 27 to 31, wherein

The communication module is further configured to receive configuration information sent by the access network device, where the configuration information is used to configure a state in which eMBB data is canceled on the first resource, and to send eMBB on the first resource. The status of the data.
The communication device according to any one of claims 27 to 32, wherein

The communication module is further configured to receive the first threshold value sent by the access network device.
The communication device according to claim 19 or 28, wherein

The communication module is further configured to receive the second threshold value sent by the access network device.
A computer program product, characterized in that when it is run on a computer, the computer is caused to execute the method according to any one of claims 1 to 17.
A chip product, wherein the chip product is used to implement the method according to any one of claims 1 to 17 above.
A computer-readable storage medium is characterized in that instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, the computer is caused to execute the method according to any one of claims 1 to 17 above.