CN112261730B

CN112261730B - Communication method and communication device

Info

Publication number: CN112261730B
Application number: CN201910946340.6A
Authority: CN
Inventors: 王俊伟; 托斯顿·斯科尔; 胡丹; 张兴炜
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-07-22
Filing date: 2019-10-30
Publication date: 2022-05-31
Anticipated expiration: 2039-10-30
Also published as: CN112261730A

Abstract

A communication method and a communication apparatus determine whether to execute a BWP handoff command according to whether a time domain resource corresponding to a transition period for performing BWP handoff overlaps with a time domain resource for transmitting or receiving data. When the time domain resource corresponding to the transition period for performing BWP handover partially overlaps or completely overlaps the time domain resource used for transmitting or receiving data, the BWP handover command is abandoned, and the data is preferentially transmitted or received, which provides a solution for reducing the delay of URLLC service.

Description

Communication method and communication device

Technical Field

The present application relates to the field of communications, and more particularly, to a method of communication and a communication apparatus.

Background

Currently, a bandwidth part (BWP) refers to a set of consecutive Physical Resource Blocks (PRBs) configured by a network device for a terminal device in an uplink carrier or a downlink carrier. The network device may configure a plurality of BWPs for the terminal device, but only one BWP can be activated in a certain time unit, and the corresponding data can be received and transmitted only on the corresponding BWP.

Switching of the end device from one BWP to another BWP is a way to activate BWP, and during BWP switching, the existing third Generation Partnership Project (3 GPP) release 15(release 15, R15) protocol specifies that the end device cannot receive data sent by the network device, nor send any signal or data to the network device.

In this case, for a service with a relatively high latency requirement, for example, a high-reliability and low-latency communication (URLLC) service, since the terminal device is not allowed to perform any transmission during BWP handover, the low latency requirement of the URLLC service cannot be met.

Disclosure of Invention

The application provides a communication method which can meet the requirement of URLLC service on low time delay.

In a first aspect, a communication method is provided, where an execution subject of the method may be a terminal device, and may also be a module, such as a chip, in the terminal device. The method is described below with the terminal device as the execution subject. The terminal device receives first scheduling information at an nth time unit, the first scheduling information instructing the terminal device to switch an active BWP from a first BWP to a second BWP, n being a positive integer. The terminal equipment receives second scheduling information, wherein the second scheduling information indicates the terminal equipment to send first data or receive the first data on first time domain resources; and the terminal device determines whether to switch the activated BWP from the first BWP to a second BWP according to whether the first time domain resource and the second time domain resource are overlapped, wherein the second time domain resource is a time domain resource between the nth time unit and an n + k time unit, the n + k time unit is a time unit for completing BWP switching by the terminal device, and k is a positive integer.

Based on the above technical solution, when the first time domain resource and the second time domain resource are partially overlapped or completely overlapped, the data related to the URLLC service is preferentially sent or received on the first time domain resource, so as to reduce the influence of the BWP handover command being preferentially executed on the delay of the URLLC service when the first time domain resource and the second time domain resource are overlapped, thereby meeting the requirement of the URLLC service for low delay.

It should be noted that, when the second scheduling information indicates that the terminal device sends the first data on the first time domain resource, at this time, when it is determined whether the first time domain resource overlaps with the second time domain resource, it also needs to determine by combining a Time Advanced (TA), and it can be determined that the first time domain resource does not overlap with the second time domain resource only when an interval between the first time domain resource and the second time domain resource is not less than the TA, or is not less than a sum of the TA and a radio frequency switching time length. TA is a time advance when the terminal device sends data #1, and may be indicated to the terminal device by the network device, and the radio frequency switching time length is a time length required when the terminal device switches the radio frequency, and the time length may be determined based on a protocol. The description herein is also applicable to the communication method of the second aspect, and is not repeated in the following for brevity.

In one possible implementation, the determining whether to switch the activated BWP from the first BWP to the second BWP according to whether the first time-domain resource overlaps with a second time-domain resource includes: when the first time domain resource partially overlaps or completely overlaps with the second time domain resource, the terminal device does not switch the activated BWP from the first BWP to the second BWP, and transmits the first data on the first time domain resource or receives the first data; or, when the first time domain resource and the second time domain resource do not overlap, the terminal device switches the activated BWP from the first BWP to the second BWP, and transmits the first data on the first time domain resource or receives the first data.

In one implementation, the first scheduling information and the second scheduling information are received on a first carrier, the first carrier including the first BWP and the second BWP.

In one implementation, the second scheduling information indicates that the terminal device transmits the first data or receives the first data on the first time domain resource on a second carrier.

In a multi-carrier scenario, for a first carrier and a second carrier belonging to the same frequency band, when a second time domain resource on the first carrier overlaps with a first time domain resource on the second carrier, at this time, although the first carrier and the second carrier are different carriers, since the first carrier and the second carrier belong to the same frequency band, executing a BWP handover command on the second time domain resource on the first carrier may cause interruption of receiving or transmission of first data on the first time domain resource on the second carrier. Based on the above technical solution, when the second time domain resource on the first carrier partially overlaps or completely overlaps with the first time domain resource on the second carrier, the handover command of performing BWP on the second time domain resource on the first carrier is abandoned, and instead, the data related to the URLLC service is sent or received on the first time domain resource on the second carrier, that is, when the second time domain resource on the first carrier partially overlaps or completely overlaps with the first time domain resource on the second carrier, the data related to the URLLC service is sent or received preferentially on the first time domain resource on the second carrier, so that the influence of preferentially executing the BWP handover command on the delay of the URLLC service when the second time domain resource on the first carrier overlaps with the first time domain resource on the second carrier is reduced, and the requirement of the URLLC service on low delay is further satisfied.

In one implementation, the first scheduling information is received on a first carrier, the first carrier includes the first BWP and the second BWP, the second scheduling information is received on a second carrier, and the second scheduling information instructs the terminal device to transmit the first data or receive the first data on the first time domain resource on the second carrier.

In one implementation, the first scheduling information further instructs the terminal device to send second data on a third time domain resource, where the third time domain resource is not overlapped with the first time domain resource and the second time domain resource, and when the first time domain resource is partially overlapped or completely overlapped with the second time domain resource, the method further includes: and the terminal equipment does not transmit the second data on the third time domain resource.

In one implementation, the first scheduling information further instructs the terminal device to receive second data on a third time domain resource, where the third time domain resource is not overlapped with the first time domain resource and the second time domain resource, and when the first time domain resource is partially overlapped or completely overlapped with the second time domain resource, the method further includes: the terminal device does not receive the second data on the third time domain resource.

In a second aspect, a communication method is provided, where an execution subject of the method may be a network device, and may also be a module, such as a chip, in the network device. The method is described below with the network device as the execution subject. The network device sends first scheduling information at an nth time unit, the first scheduling information instructing the terminal device to switch the active BWP from the first BWP to the second BWP, n being a positive integer. And the network equipment sends second scheduling information, wherein the second scheduling information indicates the terminal equipment to send the first data or receive the first data on the first time domain resource. The network device determines whether to switch the activated BWP from the first BWP to a second BWP according to whether the first time domain resource overlaps with a second time domain resource, where the second time domain resource is a time domain resource between the nth time unit and an n + k time unit, the n + k time unit is a time unit for the terminal device to complete BWP switching, and k is a positive integer.

The second aspect is a method of a network device side corresponding to the first aspect, so that the beneficial effects of the first aspect can also be achieved, which is not described herein again.

In one possible implementation, the determining whether to switch the activated BWP from the first BWP to the second BWP according to whether the first time-domain resource overlaps with a second time-domain resource includes: when the first time domain resource partially overlaps or completely overlaps with the second time domain resource, the network device does not switch the activated BWP from the first BWP to the second BWP, and receives the first data or transmits the first data on the first time domain resource; or, when the first time-domain resource and the second time-domain resource do not overlap, the network device switches the activated BWP from the first BWP to the second BWP, and receives the first data or transmits the first data on the first time-domain resource.

In one possible implementation, the first scheduling information and the second scheduling information are transmitted on a first carrier, where the first carrier includes the first BWP and the second BWP.

In a possible implementation manner, the second scheduling information instructs the terminal device to transmit the first data or receive the first data on the first time domain resource on a second carrier.

In one possible implementation, the first scheduling information is transmitted on a first carrier, the first carrier includes the first BWP and the second BWP, the second scheduling information is transmitted on a second carrier, and the second scheduling information instructs the terminal device to transmit the first data or receive the first data on the first time domain resource on the second carrier.

In a third aspect, a communication method is provided, where an execution subject of the method may be a terminal device, and may also be a module, such as a chip, in the terminal device. The method is described below with the terminal device as the execution subject. The terminal device receives third scheduling information from the network device on a fourth time-domain resource, the third scheduling information instructing the terminal device to switch the active BWP from the first BWP to the second BWP, the third scheduling information further instructing the terminal device to receive third data on a fifth time-domain resource. The terminal device switches the active BWP from the first BWP to the second BWP. And the terminal equipment receives fourth scheduling information from the network equipment on a sixth time domain resource, wherein the fourth scheduling information indicates the terminal equipment to receive fourth data on a seventh time domain resource. And the terminal equipment receives the fourth data from the network equipment on the seventh time domain resource. And the terminal equipment receives the third data from the network equipment on the fifth time domain resource.

In a possible implementation manner of the third aspect, the terminal device switches the active BWP from the first BWP to the second BWP before the sixth time-domain resource.

In a fourth aspect, a communication method is provided, where an execution subject of the method may be a network device, or may be a module, such as a chip, in the network device. The method is described below with the network device as the execution subject. The network device sends third scheduling information to the terminal device on a fourth time domain resource, the third scheduling information instructing the terminal device to switch the active BWP from the first BWP to the second BWP, the third scheduling information further instructing the terminal device to receive third data on a fifth time domain resource. The network device switches the active BWP from the first BWP to the second BWP. And the network equipment sends fourth scheduling information to the terminal equipment on a sixth time domain resource, wherein the fourth scheduling information indicates the terminal equipment to receive fourth data on a seventh time domain resource. And the network equipment sends the fourth data to the terminal equipment on the seventh time domain resource. And the network equipment sends the third data to the terminal equipment on the fifth time domain resource.

In one possible implementation of the fourth aspect, the network device switches the active BWP from the first BWP to the second BWP before the sixth time-domain resource.

In a possible implementation manner of the third aspect or the fourth aspect, the third scheduling information is transmitted on the first BWP; the fourth scheduling information is transmitted on the second BWP. That is, the third scheduling information is transmitted by the network device to the terminal device on the first BWP, and the fourth scheduling information is transmitted by the network device to the terminal device on the second BWP.

In a possible implementation manner of the third aspect or the fourth aspect, the third data and the fourth data are transmitted on the second BWP.

In a possible implementation manner of the third or fourth aspect, the first BWP and the second BWP belong to the same carrier.

In a fifth aspect, a communication method is provided, where an execution subject of the method may be a terminal device, or a module, such as a chip, in the terminal device. The method is described below with the terminal device as the execution subject. The terminal device receives third scheduling information from the network device on a fourth time-domain resource, the third scheduling information instructing the terminal device to switch the activated BWP from the first BWP to the second BWP, and the third scheduling information further instructing the terminal device to transmit third data on a fifth time-domain resource. The terminal device switches the active BWP from the first BWP to the second BWP before a sixth time-domain resource. And the terminal equipment receives sixth scheduling information from the network equipment on a sixth time domain resource, wherein the sixth scheduling information indicates the terminal equipment to cancel the third data sent on the fifth time frequency resource.

In a sixth aspect, a communication method is provided, where an execution subject of the method may be a network device, or a module, such as a chip, in the network device. The method is described below with the network device as the execution subject. The network device sends third scheduling information to the first terminal device on a fourth time-domain resource, the third scheduling information instructs the first terminal device to switch the activated BWP from the first BWP to the second BWP, and the third scheduling information further instructs the first terminal device to send third data on a fifth time-frequency resource. The network device switches the active BWP of the first terminal device from the first BWP to the second BWP before the sixth time-domain resource. And the network equipment sends sixth scheduling information to the first terminal equipment on the sixth time domain resource, wherein the sixth scheduling information indicates that the first terminal equipment cancels the sending of the third data on the fifth time frequency resource.

In a possible implementation manner of the sixth aspect, the network device sends fifth scheduling information to the second terminal device on an eighth time-domain resource, where the fifth scheduling information indicates that the second terminal device sends fifth data on a ninth time-frequency resource, and the ninth time-frequency resource is partially overlapped or completely overlapped with the fifth time-frequency resource.

In a possible implementation manner of the sixth aspect, the network device receives the fifth data from the second terminal device on the ninth time-frequency resource.

In a possible implementation manner of the fifth aspect or the sixth aspect, the sixth scheduling information includes a cancellation indication field indicating that the transmission of the third data is cancelled.

In a possible implementation manner of the fifth aspect or the sixth aspect, the sixth scheduling information includes information of a tenth time-frequency resource, which indicates that data transmission in the tenth time-frequency resource is cancelled, and the tenth time-frequency resource partially overlaps or completely overlaps with the fifth time-frequency resource.

In a possible implementation manner of the fifth or sixth aspect, the third scheduling information includes an index of the second BWP.

In a possible implementation manner of the fifth or sixth aspect, the third scheduling information is transmitted on the first BWP; the sixth scheduling information is transmitted on the second BWP.

In a possible implementation manner of the fifth or sixth aspect, the first BWP and the second BWP belong to the same carrier.

In a possible implementation manner of the fifth aspect or the sixth aspect, a starting time of the sixth time domain resource is later than a starting time of the fourth time domain resource and earlier than a starting time of a fifth time domain resource, and the fifth time domain resource is a time domain resource corresponding to the fifth time domain resource.

In a seventh aspect, a communication apparatus is provided, where the communication apparatus may be a terminal device in the foregoing method, or a chip applied in the terminal device. The communication device includes: a processor, coupled to the memory, and configured to execute the instructions in the memory to implement the method performed by the terminal device in the first aspect and any one of the possible implementations of the first aspect, or to implement the method performed by the terminal device in the third aspect and any one of the possible implementations of the third aspect, or to implement the method performed by the terminal device in the fifth aspect and any one of the possible implementations of the fifth aspect. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.

When the communication device is a terminal device, the communication interface may be a transceiver, or an input/output interface.

When the communication device is a chip applied to a terminal device, the communication interface may be an input/output interface.

Alternatively, the transceiver may be a transmit-receive circuit. Alternatively, the input/output interface may be an input/output circuit.

In an eighth aspect, a communication apparatus is provided, where the communication apparatus may be a network device in the method, or a chip applied to a network device. The communication device includes: a processor, coupled to the memory, may be configured to execute the instructions in the memory to implement the method performed by the network device in the second aspect and any one of the possible implementations thereof. Optionally, the communication apparatus further includes a memory, and implements the method performed by the network device in the fourth aspect and any one of its possible implementations, or implements the method performed by the network device in the sixth aspect and any one of its possible implementations. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.

When the communication device is a network device, the communication interface may be a transceiver, or an input/output interface.

When the communication device is a chip applied in a network device, the communication interface may be an input/output interface.

A ninth aspect provides a program for performing, when executed by a communication apparatus, any of the methods of the first aspect and its possible implementations, or for performing any of the methods of the second aspect and its possible implementations, or for performing any of the methods of the third aspect and its possible implementations, or for performing any of the methods of the fourth aspect and its possible implementations, or for performing any of the methods of the fifth aspect and its possible implementations, or for performing any of the methods of the sixth aspect and its possible implementations.

In a sixth aspect, a program product is provided, the program product comprising: program code for causing a communication apparatus to perform any of the methods of the first aspect and its possible embodiments described above, or for performing any of the methods of the second aspect and its possible embodiments, or for performing any of the methods of the third aspect and its possible embodiments, or for performing any of the methods of the fourth aspect and its possible embodiments, or for performing any of the methods of the fifth aspect and its possible embodiments, or for performing any of the methods of the sixth aspect and its possible embodiments, when said program code is run by the communication apparatus.

In a seventh aspect, there is provided a computer readable storage medium storing a program which, when executed, causes a communication apparatus to perform any one of the methods of the first aspect and its possible implementations, or to perform any one of the methods of the second aspect and its possible implementations, or to perform any one of the methods of the third aspect and its possible implementations, or to perform any one of the methods of the fourth aspect and its possible implementations, or to perform any one of the methods of the fifth aspect and its possible implementations, or to perform any one of the methods of the sixth aspect and its possible implementations.

Drawings

Fig. 1 is an architecture diagram of a mobile communication system suitable for use in embodiments of the present application;

FIG. 2 is a BWP handoff diagram;

FIG. 3 is a schematic interaction diagram of a method of communication provided herein;

fig. 4 is a schematic diagram of BWP handover and data transmission in a single carrier scenario;

fig. 5 is another schematic diagram of BWP handover and data transmission in a single carrier scenario;

fig. 6 is a schematic diagram of BWP handover and data transmission in a multi-carrier scenario;

fig. 7 is another diagram illustrating BWP handover and data transmission in a multi-carrier scenario;

fig. 8 is a further diagram of BWP handover and data transmission in a multi-carrier scenario;

fig. 9 is a further schematic diagram of BWP handover and data transmission in a multi-carrier scenario;

fig. 10 is still another schematic diagram of BWP handover and data transmission in a single carrier scenario;

FIG. 11 is a schematic diagram of a communication method provided herein;

FIG. 12 is a schematic diagram of scheduling timing relationships provided herein;

FIG. 13 is a schematic diagram of a communication method provided herein;

FIG. 14 is a schematic diagram of scheduling timing relationships provided herein;

FIG. 15 is a schematic block diagram of a communications device provided herein;

fig. 16 is a schematic block diagram of another communication device provided herein.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, a Time Division Duplex (TDD) system, a New Radio (NR) in a 5th Generation (5G) mobile communication system, a future mobile communication system, and the like.

Fig. 1 is a schematic architecture diagram of a mobile communication system suitable for use in the embodiments of the present application. As shown in fig. 1, the mobile communication system includes a core network device 110, a radio access network device 120, and at least one terminal device (e.g., a terminal device 130 and a terminal device 140 in fig. 1). The terminal equipment is connected with the wireless access network equipment in a wireless mode, and the wireless access network equipment is connected with the core network equipment in a wireless or wired mode. The core network device and the radio access network device may be separate physical devices, or the function of the core network device and the logical function of the radio access network device may be integrated on the same physical device, or a physical device may be integrated with a part of the function of the core network device and a part of the function of the radio access network device. The terminal equipment may be fixed or mobile. Fig. 1 is a schematic diagram, and other network devices, such as a wireless relay device and a wireless backhaul device, may also be included in the communication system, which are not shown in fig. 1. The embodiments of the present application do not limit the number of core network devices, radio access network devices, and terminal devices included in the mobile communication system.

The Radio Access Network device in this embodiment is an Access device in which a terminal device is accessed to the mobile communication system in a wireless manner, and may be a base station NodeB, an evolved node b (eNodeB), a Transmission Reception Point (TRP), a next generation base station (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an Access node in a WiFi system, or may be a Radio controller in a Cloud Radio Access Network (CRAN) scenario, or may be a relay station, a vehicle-mounted device, a wearable device, a Network device in a PLMN Network in the future evolution, or the like. The embodiments of the present application do not limit the specific technologies and the specific device forms adopted by the radio access network device. In this application, a radio access network device is referred to as a network device for short, and if no special description is provided, network devices are referred to as radio access network devices in this application.

The Terminal device in the embodiment of the present application may also be referred to as a Terminal, a Terminal device (UE), a Mobile Station (MS), a Mobile Terminal (MT), and the like. The terminal device may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned driving (self driving), a wireless terminal in remote surgery (remote medical supply), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in home (smart home), and the like. The embodiment of the present application does not limit the specific technology and the specific device form adopted by the terminal device.

The network equipment and the terminal equipment can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; can also be deployed on the water surface; it may also be deployed on airborne airplanes, balloons and satellite vehicles. The embodiment of the application does not limit the application scenarios of the network device and the terminal device.

The network device and the terminal device may communicate with each other through a licensed spectrum (licensed spectrum), may communicate with each other through an unlicensed spectrum (unlicensed spectrum), or may communicate with each other through both the licensed spectrum and the unlicensed spectrum. The network device and the terminal device may communicate with each other through a frequency spectrum of 6 gigahertz (GHz) or less, through a frequency spectrum of 6GHz or more, or through both a frequency spectrum of 6GHz or less and a frequency spectrum of 6GHz or more. The embodiments of the present application do not limit the spectrum resources used between the network device and the terminal device.

It is to be understood that, in the embodiments of the present application, a Physical Downlink Shared Channel (PDSCH), a Physical Downlink Control Channel (PDCCH), and a Physical Uplink Shared Channel (PUSCH) are only used as examples of a downlink data channel, a downlink control channel, and an uplink data channel, and in different systems and different scenarios, data channels and control channels may have different names, which is not limited in the embodiments of the present application.

First, a time domain resource used for communication in the embodiment of the present application is briefly described.

In the embodiment of the present application, a time domain resource used by a network device and a terminal device for communication may be divided into a plurality of time units in a time domain. The plurality of time units may be consecutive, or some adjacent time units may have a certain time interval therebetween, and the embodiment of the present application is not particularly limited. The time unit may be a time unit that includes information for uplink data transmission and/or downlink data transmission. In the embodiments of the present application, the length of one time unit is not limited, for example, 1 time unit may be one or more subframes; or, it may be one or more slots (slots); alternatively, it may be one or more symbols. In the embodiments of the present application, a symbol is also referred to as a time domain symbol, and may be an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a single carrier-frequency division multiplexing (SC-FDM) symbol. The symbols in the embodiments of the present application all refer to time domain symbols, if not otherwise specified. In the embodiment of the present application, for a plurality of time units, the time units have a time sequence relationship in a time domain, and the time lengths corresponding to any two time units may be the same or different.

Hereinafter, for the sake of easy understanding, a bandwidth part (BWP) referred to in the embodiments of the present application will be described.

BWP refers to a set of consecutive Physical Resource Blocks (PRBs) configured by a network device for a terminal device in an uplink carrier or a downlink carrier. The network device may configure multiple BWPs for the terminal device, but only one BWP can be activated in a certain time unit, and the corresponding data can be received and transmitted only on the corresponding BWP. As shown in fig. 2, in the time unit corresponding to t0 to t1, the terminal device operates on BWP #1, in the time unit corresponding to t2 to t3, the terminal device operates on BWP #2, that is, in the time unit corresponding to t1 to t2, the terminal device switches from BWP #1 to BWP #2, and in the time unit corresponding to t4 to t5, the terminal device operates on BWP #3, that is, in the time unit corresponding to t3 to t4, the terminal device switches from BWP #2 to BWP # 3. During BWP handover, existing protocols provide for the end device to be unable to receive information sent by the network device during this period, and to send any information to the network device.

In this case, for the traffic with higher latency requirement, for example, URLLC traffic, the low latency requirement of URLLC traffic cannot be met because the terminal device is not allowed to make any transmission during BWP handover.

In view of this, the embodiments of the present application provide a communication method, so as to meet the requirement of the URLLC service on low latency.

Hereinafter, the communication method according to the embodiment of the present application will be described in detail with reference to fig. 3 to 10.

Fig. 3 is a schematic interaction diagram of a method 200 of communication provided by an embodiment of the application. Each step of the method 200 is described in detail below.

In the embodiment of the present application, the method 200 is described by taking a terminal device and a network device as an example of an execution subject for executing the method 200. By way of example and not limitation, the execution subject of the execution method 200 may also be a chip corresponding to the terminal device and a chip corresponding to the network device.

In S210, the network device transmits scheduling information #1 (i.e., an example of first scheduling information) to the terminal device at the nth time unit, where the scheduling information #1 instructs the terminal device to switch the active BWP from BWP #1 (i.e., an example of the first BWP) to BWP #2 (i.e., an example of the second BWP) before the (n + k) th time unit, where n and k are both positive integers. Accordingly, the terminal device receives the scheduling information #1 from the network device on the nth time unit.

In other words, the network device transmits scheduling information #1 to the terminal device, the scheduling information #1 instructing the terminal device to execute the BWP switch command. For example, a BWP #2 index may be included in the scheduling information #1 to instruct the terminal device to switch the active BWP from BWP #1 (i.e., the currently active BWP) to BWP # 2.

Alternatively, the scheduling information #1 may not indicate the time when the BWP handover is completed. The value of k is determined by the time required for BWP handover, and the time required for BWP handover is reported to the network device by the terminal device according to its own capability, so that the terminal device and the network device can know the time for BWP handover completion; alternatively, the time required for BWP handover may be predefined by the protocol. In this embodiment, the network device sends scheduling information #1 to the terminal device indicating that the active BWP is to be switched from BWP #1 to BWP #2 on the nth time unit. For example, BWP #2 index is included in the scheduling information #1 to instruct the terminal device to switch the active BWP from BWP #1 (i.e., the currently active BWP) to BWP # 2.

In S220, the network device transmits scheduling information #2 (i.e., an example of second scheduling information) to the terminal device, the scheduling information #2 instructing the terminal device to transmit data #1 (i.e., an example of first data) or receive data #1 on time domain resource #1 (i.e., an example of first time domain resource). Accordingly, the terminal device receives the scheduling information #2 from the network device.

In S230, the terminal device determines whether to switch the activated BWP from BWP #1 to BWP #2 according to whether the time-domain resource #1 overlaps with a time-domain resource #2 (i.e., an instance of a second time-domain resource), where the time-domain resource #2 is a time-domain resource between the nth time unit and the (n + k) th time unit. It should be noted that the time domain resource between the nth time unit and the (n + k) th time unit may be a time domain resource between the nth time unit and the (n + k) th time unit, including the nth time unit and the (n + k) th time unit, that is, a time domain resource from the nth time unit to the (n + k) th time unit; or the time domain resources between the nth time unit and the (n + k) th time unit excluding the nth time unit and the (n + k) th time unit, that is, the time domain resources from the (n +1) th time unit to the (n + k-1) th time unit; it is also possible that the time domain resource between the nth time unit and the (n + k) th time unit only includes one of the nth time unit and the (n + k) th time unit, i.e. the time domain resource from the nth time unit to the (n + k-1) th time unit, or the time domain resource from the (n +1) th time unit to the (n + k) th time unit.

In order to keep consistent with the behavior of the terminal device, the network device may also determine whether to switch the active BWP from BWP #1 to BWP #2 as described in S230, accordingly. At this time, the method 200 may further include S240.

In S240, the network device determines whether to switch the activated BWP from BWP #1 to BWP #2 according to whether the time-domain resource #1 overlaps with the time-domain resource #2, where the time-domain resource #2 is a time-domain resource between the nth time unit and the (n + k) th time unit.

The terminal device, upon receiving the scheduling information #1 and the scheduling information #2, may determine whether to execute the BWP switch command according to whether the time domain resource #1 and the time domain resource #2 overlap.

When the time-domain resource #1 partially overlaps or completely overlaps with the time-domain resource #2, the terminal device does not switch the active BWP from BWP #1 to BWP # 2. In other words, the terminal device maintains the active BWP unchanged at BWP # 1. Further, when the terminal device does not execute the BWP switch command, the terminal device may also execute the scheduling information #2, transmitting the data #1 or receiving the data #1 on the time-domain resource #1 on the BWP # 1.

When the time-domain resource #1 does not overlap with the time-domain resource #2, the terminal device switches the active BWP from BWP #1 to BWP # 2. In other words, the terminal device switches the active BWP to BWP # 2. Furthermore, the terminal device may also execute the scheduling information #2 after completing BWP switching, and transmit data #1 or receive data #1 on the time-domain resource #1 on BWP # 2.

It should be noted that, when the scheduling information #2 indicates that the terminal device transmits data #1 on the time domain resource #1, and determines whether the time domain resource #1 and the time domain resource #2 overlap, it needs to determine in combination with a Timing Advance (TA), and only when an interval between the time domain resource #1 and the time domain resource #2 is not less than the TA, or not less than a sum of the TA and a radio frequency switching time length, it can be determined that the time domain resource #1 and the time domain resource #2 do not overlap. TA is a time advance when the terminal device sends data #1, and may be indicated to the terminal device by the network device, and the radio frequency switching time length is a time length required when the terminal device switches the radio frequency, and the time length may be determined based on a protocol.

It should be noted that the scheduling information #2 may be control information (e.g., Downlink Control Information (DCI)) carried on the PDCCH, or may be higher layer signaling, for example, the higher layer signaling is used to allocate a configuration grant (configured grant) for uplink scheduling, that is, to notify the terminal device to transmit the data #1 using the time domain resource #1 configured in advance by the higher layer signaling, or the higher layer signaling is used to configure semi-persistent scheduling (SPS) for downlink scheduling, that is, to notify the terminal device to receive the data #1 using the time domain resource (e.g., time domain resource #1) within a certain period configured in advance by the higher layer signaling.

It should be further noted that, if the terminal device determines to execute the BWP handover command, when performing the BWP handover, the time length required for BWP handover may include d time units, where d is a positive integer less than or equal to k +1, the start time of BWP handover is located on the time-domain resource #2, and the value of d and the start time of BWP handover may be indicated to the terminal device by the network device, or may be determined by negotiation between the terminal device and the network device, or determined based on a protocol.

Therefore, based on the above technical solution, when the time domain resource #1 and the time domain resource #2 are partially overlapped or completely overlapped, the data related to the URLLC service is preferentially received or transmitted on the time domain resource #1, so that the influence of the BWP handover command being preferentially executed on the delay of the URLLC service when the time domain resource #1 and the time domain resource #2 are overlapped is reduced, and the requirement of the URLLC service on low delay is further satisfied.

The method 200 for communication provided by the embodiment of the present application is described in detail in the following scenarios.

Scene #1 Single Carrier scene

As shown in fig. 4, the terminal device receives scheduling information #1 on the nth time unit (e.g., symbol #0 of slot # n), for example, scheduling information #1 indicates that the terminal device completes BWP switching before the nth + k time unit (e.g., slot # (n +1)), and an index of BWP #2 may be included in scheduling information # 1. Further, the terminal device receives scheduling information #2 on symbol #1 of slot # n, the scheduling information #2 being used for scheduling URLLC traffic, e.g., the scheduling information #2 instructs the terminal device to transmit data (e.g., data #1) related to the URLLC traffic on slot # (n +1) (e.g., time domain resource # 1).

Assuming that the start time of BWP handover is symbol #3 of slot # n, the terminal device determines, in combination with the value of d, that the completion time of BWP handover is the last symbol on slot # (n +1), and it can be seen that, at this time, resource overlapping occurs between the terminal device sending data #1 and BWP handover, the terminal device may not execute the BWP handover command, that is, the terminal device maintains the activated BWP unchanged at BWP #1, and sends data related to URLLC traffic on slot # (n +1) on BWP # 1.

As shown in fig. 5, the terminal device receives scheduling information #1 on symbol #0 of slot # n, for example, scheduling information #1 indicates that the terminal device completes BWP switching before slot # (n +1), and an index of BWP #2 may be included in scheduling information # 1. Furthermore, the terminal device receives scheduling information #2 on symbol #1 of slot # n, the scheduling information #2 being used for scheduling URLLC traffic, e.g., the scheduling information #2 instructs the terminal device to transmit data related to URLLC traffic on slot # (n + 3).

Assuming that the start time of BWP handover is symbol #3 of slot # n, the terminal device determines, in combination with the value of d, that the completion time of BWP handover is the last symbol on slot # (n +1), and it can be seen that at this time, resource overlapping does not occur between the terminal device sending data #1 and BWP handover, the terminal device may execute a BWP handover command, that is, the terminal device switches active BWP from BWP #1 to BWP #2, and sends data related to URLLC service on slot # (n +3) on BWP # 2.

Scenario #2 multicarrier scenario (a scenario including two carriers (e.g., carrier #1 and carrier #2) is illustrated as an example).

As shown in fig. 6, it is assumed that two carriers (e.g., carrier #1 and carrier #2) are configured, and that carrier #1 and carrier #2 belong to the same frequency band, where carrier #1 operates on BWP #1 and carrier #2 operates on BWP # 3. The terminal device receives scheduling information #1 on the nth time unit (e.g., symbol #0 of slot # n) on carrier #1, for example, scheduling information #1 indicates that the terminal device completes BWP handover before the nth + k time unit (e.g., slot # (n +1)) on carrier #1, and an index of BWP #2 may be included in scheduling information # 1. Furthermore, the terminal device receives scheduling information #2 on symbol #1 of slot # n on carrier #1, the scheduling information #2 being used for scheduling URLLC traffic, e.g., scheduling information #2 instructs the terminal device to transmit data related to URLLC traffic on time domain resource #1 (e.g., slot # (n +1)) on carrier # 2.

Assuming that the start time of BWP handover is symbol #3 of slot # n, the terminal device determines, in combination with the value of d, that the completion time of BWP handover is the last symbol on slot # (n +1), and it can be seen that, at this time, resource overlapping occurs between the terminal device transmitting data #1 on carrier #2 and performing BWP handover on carrier #1, the terminal device may not execute a BWP handover command on carrier #1, that is, the terminal device maintains the activated BWP on carrier #1 unchanged at BWP #1, and transmits data related to URLLC traffic on slot # (n +1) on BWP #3 on carrier # 2.

It should be noted that, the carrier #1 and the carrier #2 appearing hereinafter are the same as the description about the carrier #1 and the carrier #2 in fig. 6, and for brevity, the description thereof is omitted.

As shown in fig. 7, the terminal device receives scheduling information #1 on the nth time unit (e.g., symbol #0 of slot # n) on carrier #1, for example, scheduling information #1 indicates that the terminal device completes BWP handover before the nth + k time unit (e.g., slot # (n +1)) on carrier #1, and an index of BWP #2 may be included in scheduling information # 1. Furthermore, the terminal device receives scheduling information #2 on symbol #1 of slot # n on carrier #1, scheduling information #2 being used for scheduling URLLC traffic, e.g., scheduling information #2 instructs the terminal device to transmit data related to URLLC traffic on time domain resource #1 (e.g., slot # (n +3)) on carrier # 2.

Assuming that the start time of BWP handover is symbol #3 of slot # n, the terminal device determines, in combination with the value of d, that the completion time of BWP handover is the last symbol on slot # (n +1), and it can be seen that, at this time, resource overlapping does not occur between the terminal device transmitting data #1 on carrier #2 and performing BWP handover on carrier #1, the terminal device may execute a BWP handover command on carrier #1, that is, the terminal device switches active BWP on carrier #1 from BWP #1 to BWP #2, and transmits data related to URLLC traffic on slot # (n +3) on BWP #3 on carrier # 2.

Fig. 6 and 7 describe the case where the scheduling information #1 and the scheduling information #2 are transmitted on the same carrier (for example, carrier #1), and the case where the scheduling information #1 and the scheduling information #2 are transmitted on different carriers will be described below with reference to fig. 8 and 9.

As shown in fig. 8, the terminal device receives scheduling information #1 on the nth time unit (e.g., symbol #0 of slot # n) on carrier #1, for example, the scheduling information #1 indicates that the terminal device completes BWP switching before the (n + k) th time unit (e.g., slot # (n +1)) on carrier #1, and the index of BWP #2 is included in the scheduling information # 1. Furthermore, the terminal device receives scheduling information #2 on symbol #1 of slot # n on carrier #2, scheduling information #2 being used for scheduling URLLC traffic, e.g., scheduling information #2 instructs the terminal device to transmit data related to URLLC traffic on time domain resource #1 (e.g., slot # (n +1)) on carrier # 2.

As shown in fig. 9, the terminal device receives scheduling information #1 on the nth time unit (e.g., symbol #0 of slot # n) on carrier #1, for example, scheduling information #1 indicates that the terminal device completes BWP handover before the nth + k time unit (e.g., slot # (n +1)) on carrier #1, and an index of BWP #2 may be included in scheduling information # 1. Further, the terminal device receives scheduling information #2 on symbol #1 of slot # n on carrier #2, the scheduling information #2 being used for scheduling the URLLC traffic, e.g., the scheduling information #2 instructs the terminal device to transmit data related to the URLLC traffic on time domain resource #1 (e.g., slot # (n +3)) on carrier # 2.

Assuming that the start time of BWP handover is symbol #3 of slot # n, the terminal device determines, in combination with the value of d, that the completion time of BWP handover is the last symbol on slot # (n +1), and it can be seen that, at this time, resource overlapping does not occur between the terminal device transmitting data #1 on carrier #2 and performing BWP handover on carrier #1, the terminal device may execute a BWP handover command on carrier #1, that is, the terminal device switches active BWP from BWP #1 to BWP #2 on carrier #1, and transmits data related to URLLC traffic on slot # (n +3) on BWP #3 on carrier # 2.

In the method 200, the scheduling information #1 may further instruct the terminal device to transmit data #2 (i.e., an instance of the second data) or receive data #2 on the time-domain resource #3 (i.e., an instance of the third time-domain resource), i.e., the scheduling information #1 instructs the terminal device to switch the active BWP from BWP #1 to BWP #2, and instructs the terminal device to transmit data #2 or receive data #2 on the time-domain resource #3, in other words, the scheduling information #1 instructs the terminal device to transmit data #2 or receive data #2 on the time-domain resource #3 on BWP # 2.

When the terminal device does not switch BWP from BWP #1 to BWP #2, i.e. the active BWP remains unchanged on BWP #1, the terminal device may not transmit data #2 or receive data #2 on time-domain resource #3 on BWP #1, i.e. the terminal device abandons transmitting data #2 or receiving data # 2.

For example, in a multi-carrier scenario, scheduling information #1 is received by the terminal device on symbol #0 of slot # n on carrier #1, and scheduling information #1 instructs the terminal device to switch active BWP from BWP #1 to BWP #2 on carrier #1 as well as to receive data (e.g., data #2) related to enhanced mobile broadband (eMBB) traffic on slot # (n +5) (e.g., time domain resource #3) on carrier #1, in other words, scheduling information #1 instructs the terminal device to receive data related to eMBB traffic on slot # (n +5) on BWP #2 of carrier # 1.

If the terminal device does not switch the active BWP from BWP #1 to BWP #2 on carrier #1, the terminal device may not receive data related to the eMBB traffic on slot # (n +5) on BWP #1 of carrier #1, i.e., the terminal device drops receiving data related to the eMBB traffic on slot # (n +5) on BWP #1 of carrier # 1.

In a multi-carrier scenario, for the carrier #1 and the carrier #2 belonging to the same frequency band, when the time domain resource #2 on the carrier #1 overlaps with the time domain resource #1 on the carrier #2, at this time, although the carrier #1 and the carrier #2 are different carriers, since the carrier #1 and the carrier #2 belong to the same frequency band, executing the BWP handover command on the time domain resource #2 on the carrier #1 may cause the interruption of the reception or the interruption of the transmission of the data #1 on the time domain resource #1 on the carrier # 2. Based on the above technical solution, when the time domain resource #2 on the carrier #1 is partially overlapped or completely overlapped with the time domain resource #1 on the carrier #2, the time domain resource #2 on the carrier #1 is abandoned to execute the BWP handover command, and instead, the data related to the URLLC service is transmitted or received on the time domain resource #1 on the carrier #2, that is, when the time domain resource #2 on the carrier #1 is partially overlapped or completely overlapped with the time domain resource #1 on the carrier #2, the data related to the URLLC service is preferentially transmitted or received on the time domain resource #1 on the carrier #2, so that the influence of preferentially executing the BWP handover command on the delay of the URLLC service when the time domain resource #2 on the carrier #1 is overlapped with the time domain resource #1 on the carrier #2 is reduced, and the requirement of the URLLC service for low delay is further satisfied.

In the embodiment of the present application, in order to meet the requirement of the URLLC service on low latency, another communication method is provided in the embodiment of the present application, and the method is described below.

In order to avoid the above-mentioned partial overlap or complete overlap of the time domain resource #1 and the time domain resource #2, the network device may schedule the URLLC service after the BWP handover is completed, and accordingly, the terminal device may initiate reception of scheduling information of the URLLC service after the BWP handover is completed, thereby reducing the influence of the BWP handover on the URLLC service.

In addition, the network device and the terminal device may agree in advance that only the URLLC service is scheduled after the BWP handover is completed, so that the terminal device only detects the control channel of the URLLC service after the BWP handover is completed, and there is no need to detect the control channel of other services (e.g., eMBB service), thereby further saving power consumption of the terminal device.

For example, as shown in fig. 10, the terminal device receives scheduling information #1 on the nth time unit (e.g., symbol #0 of slot # n), e.g., scheduling information #1 indicates that the terminal device receives data related to the eMBB service on slot # (n +5), and scheduling information #1 also indicates that the terminal device completes BWP handover before the n + k time unit (e.g., slot # (n +1)), and an index of BWP #2 may be included in the scheduling information # 1.

The terminal device completes BWP handover before the last symbol of slot # (n +1), and does not receive scheduling information #2 for scheduling URLLC traffic before BWP handover is completed. According to the convention with the network device, the terminal device will start receiving the scheduling information #2 only after the BWP handover is completed, for example, the terminal device receives the scheduling information #2 on the last symbol of slot # (n +2), and the scheduling information #2 indicates the terminal device to receive data related to the URLLC service at slot # (n + 3). Since the network device may transmit the scheduling information #2 only after the BWP handover is completed, the BWP handover does not affect the URLLC traffic.

In addition, in order to reduce the impact of BWP handover on URLLC service, i.e. to meet the requirement of URLLC service for low latency, another communication method is provided in the embodiments of the present application, and the method is described below.

Method #1

For a terminal device in a serving cell supporting URLLC, it may ignore all BWP handover commands from the network device, for example, when the network device configures the serving cell supporting URLLC, the value of processing type2Enabled in the protocol may be TRUE, which indicates that the serving cell supports URLLC service.

Specifically, for a terminal device in a serving cell supporting URLLC, it may ignore field information of the BWP handover command carried in DCI; alternatively, the terminal device may ignore timer-based BWP handover commands or not enable a timer for BWP handover.

The timer for switching BWP refers to that the terminal device switches to the default BWP if the terminal device does not receive the scheduling information from the network device within a certain time period (the time period may be configured by the network device).

The timer-based BWP switch command is that the terminal device does not switch to the default BWP if the terminal device does not receive the scheduling information from the network device within a certain time period after the timer is started.

For example, when the network device sends the cell parameter configuration information or the BWP parameter configuration information to the terminal device, the parameter configuration information may include an indication of BWP handover enable or disable. When a cell or BWP supports data transmission for high priority services, BWP is disabled. When BWP switch disable (disabled), the BWP switch indication is ignored, e.g., the BWP switch indication based on the scheduling signaling is ignored, and the timer for BWP switch is not started, regardless of whether the BWP switch is a network device or a terminal device.

Method #2

The terminal equipment only executes the BWP switching command indicated by the DCI for scheduling the URLLC service, and ignores the BWP switching command indicated by the DCI for scheduling the eMBB service. The terminal device may identify DCI for scheduling URLLC service by the following method:

a, identifying DCI for scheduling URLLC traffic by Radio Network Temporary Identity (RNTI), for example, by modulation and coding scheme-RNTI (MCS-RNTI).

b, identifying the DCI used for scheduling the URLLC traffic according to a control resource set (CORESET) carrying the DCI used for scheduling the URLLC traffic or a search space set.

c, indicating DCI for scheduling URLLC traffic and DCI for scheduling eMBB traffic by using several bits (bits) in DCI. The bit here may be a reserved bit or a newly added bit, which is not particularly limited in this embodiment of the present application.

In the embodiment of the present application, in order to meet the requirement of high-priority traffic data, control signaling, or signals, another communication method is provided in the embodiment of the present application, so that the terminal device and the network device can transmit the high-priority traffic data, control signaling, or signals in time after completing BWP handover. The high-priority service data in the present application may be the service data of URLLC, or other high-priority service data. The control signaling with high priority may be a pre-Preemption Indication (PI) sent by the network device to the terminal device, indicating that some time-frequency resources are used by the service data or signaling with high priority, but data is not sent to the terminal device on the time-frequency resources. The control signaling with high priority may also be an uplink cancel indication (UL CI) sent by the network device to the terminal device, and is used to indicate that data, signaling, or signals are not sent on some time-frequency resources, or to indicate to cancel sending of data, signaling, or signals. The control signaling with high priority may also be uplink scheduling signaling or downlink scheduling signaling for scheduling the high-priority service data, or hybrid automatic repeat request-acknowledgement (HARQ-ACK) information corresponding to the high-priority service data. The high-priority control signaling may also be a Scheduling Request (SR) of high-priority service data, and is used for the terminal device to request scheduling information from the network device; or, it may be a Buffer Status Report (BSR) sent by the terminal device to the network device. The high priority signal may be a reference signal.

The communication method shown in fig. 11 will be described in detail below. It is understood that the execution subject of the method may be a terminal device and a network device, and may also be a module, such as a chip, in the terminal device and the network device.

S310, the network device sends third scheduling information to the terminal device on the fourth time domain resource, where the third scheduling information instructs the terminal device to switch the active BWP from the first BWP to the second BWP. And the corresponding terminal equipment receives the third scheduling information from the network equipment on the fourth time domain resource. Optionally, the third scheduling information includes indication information, e.g., an index, of the second BWP.

The third scheduling information further indicates scheduling of the third data, for example, indicating the terminal device to receive the third data on the fifth time domain resource, or indicating the terminal device to transmit the third data on the fifth time domain resource. Wherein the start time of the fifth time domain resource may be later than the end time of the fourth time domain resource. Optionally, the terminal device sends the third data through the PUSCH, or receives the third data through the PDSCH.

It is understood that the first BWP and the second BWP are two different BWPs within the same carrier (or cell).

S320, the network device and the terminal device switch the active BWP from the first BWP to the second BWP.

In one implementation, the terminal device and the network device may determine a completion time of the BWP handover according to the BWP handover capability of the terminal device. On the premise of determining that the BWP switching is completed, the network device may schedule the terminal device in time, thereby ensuring that high-priority service data, signaling, or signals are transmitted in time. For example, after the network device determines that the terminal device has completed the BWP handover according to the BWP handover capability of the terminal device, the network device transmits the fourth scheduling information to the terminal device on the sixth time domain resource.

S330, the network device sends the fourth scheduling information to the terminal device on the sixth time domain resource. Correspondingly, the terminal device receives the fourth scheduling information from the network device on the sixth time domain resource.

The fourth scheduling information indicates that fourth data is scheduled, for example, the terminal device is instructed to receive the fourth data on the seventh time domain resource, or the terminal device is instructed to transmit the fourth data on the seventh time domain resource. The starting time of the sixth time domain resource is later than the starting time of the fourth time domain resource, and the starting time of the seventh time domain resource is earlier than the starting time of the fifth time domain resource. This scenario, we also refer to an out of order (out of order) transmission scenario. The active BWP of the terminal device has been switched to the second BWP before the starting time of the sixth time-domain resource. Optionally, the terminal device sends the fourth data through the PUSCH, or receives the fourth data through the PDSCH.

S340, the terminal device receives the fourth data on the seventh time domain resource, and correspondingly, the network device sends the fourth data on the seventh time domain resource. Or, the terminal device sends the fourth data on the seventh time domain resource, and correspondingly, the network device receives the fourth data on the seventh time domain resource.

It will be appreciated that the fourth data here may be sent on the new active BWP, i.e. on the second BWP.

S350, the terminal device receives the third data on the fifth time domain resource, and correspondingly, the network device sends the third data on the fifth time domain resource. Or, the terminal device sends the third data on the fifth time domain resource, and correspondingly, the network device receives the third data on the fifth time domain resource.

It will be appreciated that the third data is here sent on the new active BWP, i.e. on the second BWP. Optionally, the priority of the fourth data is higher than the priority of the third data.

It is understood that the terminal device can perform S350 only if the terminal device supports the above-described out-of-order transmission scenario. If the terminal device has no limitation on the scenario of data transmission, the terminal device may perform S350. If the terminal device has a limitation on the scenario of data transmission, the terminal device may determine whether to perform S350 according to the capability of the terminal device and/or the scheduling timing relationship. And if the data transmission is judged to be a disordered transmission scene according to the scheduling time sequence relation and the terminal does not support the disordered transmission scene, the terminal equipment gives up receiving the third data or sending the third data. If the data transmission is judged to be a sequential transmission scenario according to the scheduling timing relationship, S350 is executed.

The scheduling process in fig. 11 is described below by taking an example where the fourth time domain resource is a symbol #0 on slot # n, the fifth time domain resource is slot # (n +5), the sixth time domain resource is a symbol #0 on slot # (n +3), and the seventh time domain resource is slot # (n + 4). The specific scheduling timing relationship is shown in fig. 12.

The network device sends the third scheduling information on the symbol #0 of slot # n to instruct the terminal device to send the third data on slot # (n +5), and instruct the terminal device to switch the active BWP to the second BWP. The network device may determine that the terminal device has completed the BWP handover before the symbol #0 of slot # (n +3) according to the BWP handover capability of the terminal device. The network device receives the scheduling request of the fourth data of the terminal device before slot # (n +3), and the priority of the fourth data is higher than that of the third data, so that the network device sends the fourth scheduling information on the symbol #0 of slot # (n +3) to instruct the terminal device to send the fourth data on the slot # (n +4) through the PUSCH. The terminal device receives the third scheduling information on symbol #0 of slot # n and executes the BWP switch command. After completing BWP switching, the terminal device monitors the downlink control signaling, and after monitoring the fourth scheduling information at slot #0 (n +3), sends the fourth data to the network device through the PUSCH on slot # (n + 4).

It is to be understood that the above-mentioned fourth scheduling information and fourth data may both be transmitted on the second BWP; it is also possible that one of the fourth scheduling information and the fourth data is transmitted on the second BWP and the other is transmitted on the active BWP of the other carrier. If the terminal device supports activation of a plurality of BWPs on one carrier, it may be that one of the fourth scheduling information and the fourth data is transmitted on the second BWP and the other is transmitted on another BWP other than the first BWP and the second BWP on the carrier.

The method shown in fig. 13 will be described in detail below. It is understood that the execution subject of the method may be a terminal device and a network device, and may also be a module, such as a chip, in the terminal device and the network device.

S410, the network device sends third scheduling information to the first terminal device on the fourth time domain resource, where the third scheduling information instructs the first terminal device to switch the active BWP from the first BWP to the second BWP. The corresponding first terminal device receives the third scheduling information from the network device on the fourth time domain resource. Optionally, the third scheduling information includes indication information, e.g., an index, of the second BWP.

The third scheduling information further instructs the first terminal device to transmit third data on the fifth time-frequency resource. And the time domain resource corresponding to the fifth time frequency resource is the fifth time domain resource. And the starting time of the fifth time domain resource is later than the ending time of the fourth time domain resource. Optionally, the first terminal device sends the third data through a PUSCH.

S420, the network device and the first terminal device switch the active BWP to a second BWP.

In one implementation, the first terminal device and the network device may determine a completion time of the BWP handover according to the BWP handover capability of the first terminal device. On the premise of determining that the BWP switching is completed, the network device may schedule the first terminal device in time, so as to ensure that the high-priority service data, signaling, or signal is transmitted in time. For example, after the network device determines that the terminal device has completed the BWP handover according to the BWP handover capability of the terminal device, the network device sends an uplink cancellation indication to the first terminal device on the sixth time domain resource.

S430, the network device sends sixth scheduling information to the first terminal device on the sixth time domain resource. Correspondingly, the first terminal device receives sixth scheduling information from the network device on a sixth time domain resource.

And the sixth scheduling information indicates that the first terminal device cancels the sending of the third data on the fifth time-frequency resource. The starting time of the sixth time domain resource is later than the starting time of the fourth time domain resource and earlier than the starting time of the fifth time domain resource. It is to be understood that the active BWP of the terminal device has switched to the second BWP before the start time of the sixth time-domain resource.

The sixth scheduling information may be a display instruction to cancel transmission of the third data. For example, the sixth scheduling information includes a cancellation indication field indicating that the transmission of the third data is cancelled. Further, the sixth scheduling information may further include at least one of an identification number of the first terminal device and a hybrid automatic repeat request (HARQ) process number.

The sixth scheduling information may also be an implicit indication to cancel the transmission of the third data. For example, the sixth scheduling information includes information of a tenth time-frequency resource, which indicates that data transmission in the tenth time-frequency resource is cancelled. The tenth time frequency resource is partially or completely overlapped with the fifth time frequency resource. And after receiving the sixth scheduling information, the terminal device further determines whether to cancel the transmission of the third data or cancel part of the third data according to whether the tenth time-frequency resource and the fifth time-frequency resource are overlapped. And when the tenth time-frequency resource comprises the complete fifth time-frequency resource, canceling all the third data from being transmitted. And when the tenth time-frequency resource comprises part of the fifth time-frequency resource, canceling the transmission of the third data carried on the part of the time-frequency resource overlapped with the tenth time-frequency resource. And when the fifth time frequency resource and the tenth time frequency resource are not overlapped completely, the third data is not cancelled.

The sixth scheduling information may also be referred to as UL CI. When the UL CI adopts the implicit indication manner, the specific design of the CI may refer to the related description in the section 11.2 transmission interruption indication (ITI) in the 3GPP Technical Specification (TS) 38.213 V15.7.0, and the ITI is also referred to as PI. And the network equipment sends CI to the terminal equipment, and the CI indicates the time-frequency resource information without data transmission. And after receiving the CI, the terminal equipment determines whether the time frequency resource used for data transmission is preempted or whether the data transmission is cancelled by judging whether the time frequency resource indicated by the CI is overlapped with the scheduled time frequency resource used for data transmission.

S440, optionally, the network device sends the fifth scheduling information to the second terminal device on the eighth time domain resource. Correspondingly, the second terminal device receives the fifth scheduling information from the network device on the eighth time domain resource.

And the fifth scheduling information indicates the second terminal device to transmit fifth data on a ninth time-frequency resource, and the ninth time-frequency resource is partially or completely overlapped with the fifth time-frequency resource. And the time domain resource corresponding to the ninth time frequency resource is a ninth time domain resource. The starting time of the eighth time domain resource is later than the starting time of the sixth time domain resource and earlier than the starting time of the ninth time domain resource. Optionally, the second terminal device sends the fifth data through the PUSCH.

And S450, the second terminal equipment sends fifth data to the network equipment on the ninth time-frequency resource. Correspondingly, the network device receives the fifth data from the second terminal device on the ninth time-frequency resource.

It is to be appreciated that the first terminal device cancels the transmission of the third data on the fifth time-frequency resource. Correspondingly, the network device may not receive the third data on the fifth time-frequency resource any more, but receive the fifth data from the second terminal device on the ninth time-frequency resource.

It will be appreciated that the fifth data is here sent on the new active BWP, i.e. on the second BWP. Optionally, the priority of the fifth data is higher than the priority of the third data.

The scheduling process in fig. 13 is described below by taking an example that the fourth time domain resource is a symbol #0 on slot # n, the fifth time domain resource is a slot # (n +5), the sixth time domain resource is a symbol #0 on slot # (n +3), the eighth time domain resource is a symbol #13 on slot # (n +3), and the ninth time frequency resource and the fifth time frequency resource are completely overlapped. The specific scheduling timing relationship is shown in fig. 14.

The network device sends the third scheduling information on the symbol #0 of slot # n to instruct the first terminal device to send third data on slot # (n +5), and simultaneously instruct the first terminal device to switch the active BWP to the second BWP. The network device may determine that the first terminal device has completed the handover of BWP before the symbol #0 of slot # (n +3) according to the BWP handover capability of the first terminal device. Before slot # (n +3), the network device receives the second terminal device SR, and requests the network device to allocate scheduling resources to the second terminal device, whereas no available resources are available at slot # (n +5), and the priority of the uplink data of the second terminal device is higher than that of the uplink data of the first terminal device. Thus, the network device transmitting UL CI on symbol #0 of slot # (n +3) instructs the first terminal device to cancel transmitting the third data on the fifth time domain resource. And the network device sends fifth scheduling information to the second terminal device at the symbol #13 of slot # (n +3), and instructs the second terminal device to send fifth data on a fifth time domain resource.

The first terminal device receives the third scheduling information from the network device on symbol #0 of slot # n, and executes the BWP switch command. After completing BWP switching, the first terminal device monitors the downlink control signaling, and cancels sending of the third data to the network device through the PUSCH on slot # (n +5) after monitoring the UL CI at symbol #0 of slot # (n + 3).

The second terminal device receives the fifth scheduling information from the network device on symbol #13 of slot # (n +3), indicating that the fifth data is to be transmitted on the fifth time domain resource.

It is to be understood that the above-mentioned fifth scheduling information and fifth data may both be transmitted on the second BWP; it is also possible that the fifth data is transmitted on the second BWP and the fifth scheduling information is transmitted on the active BWP of the other carrier. If the terminal device supports activation of multiple BWPs on one carrier, it may be that the fifth data is transmitted on the second BWP and the fifth scheduling information is transmitted on another BWP other than the first BWP and the second BWP on the carrier.

It is to be understood that, in order to implement the functions in the above embodiments, the network device and the terminal device include hardware structures and/or software modules for performing the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and method steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software driven hardware depends on the particular application scenario and design constraints imposed on the solution.

Fig. 15 and 16 are schematic structural diagrams of a possible communication device provided in an embodiment of the present application. These communication devices can be used to implement the functions of the terminal device or the network device in the above method embodiments, so that the beneficial effects of the above method embodiments can also be achieved. In the embodiment of the present application, the communication apparatus may be the terminal device 130 or the terminal device 140 shown in fig. 1, may also be the radio access network device 120 shown in fig. 1, and may also be a module (e.g., a chip) applied to the terminal device or the network device.

As shown in fig. 15, the communication device 300 includes a processing unit 310 and a transceiving unit 320. The communication apparatus 300 is used to implement the functions of the terminal device or the network device in the method embodiments shown in fig. 3, fig. 11 or fig. 13.

When the communication apparatus 300 is used to implement the functions of the terminal device in the method embodiment shown in fig. 3: the transceiving unit 320 is configured to receive first scheduling information at an nth time unit, where the first scheduling information instructs a terminal device to switch an active bandwidth part BWP from a first BWP to a second BWP, and n is a positive integer; the transceiving unit 320 is further configured to receive second scheduling information, where the second scheduling information indicates the terminal device to transmit the first data or receive the first data on the first time domain resource. The processing unit 310 is configured to determine whether to switch the activated BWP from the first BWP to a second BWP according to whether the first time domain resource overlaps with a second time domain resource, where the second time domain resource is a time domain resource between an nth time unit and an n + k time units, the n + k time units are time units for the terminal device to complete BWP switching, and k is a positive integer.

When the communication apparatus 300 is used to implement the functions of the network device in the method embodiment shown in fig. 3: the transceiving unit 320 is configured to transmit first scheduling information at an nth time unit, where the first scheduling information instructs a terminal device to switch an active BWP from a first BWP to a second BWP, and n is a positive integer; the transceiving unit 320 is further configured to transmit second scheduling information, where the second scheduling information instructs the terminal device to transmit the first data or receive the first data on the first time domain resource. The processing unit 310 is configured to determine whether to switch the active BWP from the first BWP to a second BWP according to whether the first time domain resource overlaps with a second time domain resource, where the second time domain resource is a time domain resource between an nth time unit and an n + k time unit, the n + k time unit is a time unit for the terminal device to complete BWP switching, and k is a positive integer.

When the communication apparatus 300 is used to implement the functions of the terminal device in the method embodiment shown in fig. 11: the transceiving unit 320 is configured to receive third scheduling information from the network device on a fourth time domain resource, the third scheduling information instructing the terminal device to switch the active BWP from the first BWP to the second BWP, and the third scheduling information further instructing the terminal device to receive third data on a fifth time domain resource. The processing unit 310 is configured to switch the active BWP from the first BWP to the second BWP. The transceiving unit 320 is further configured to receive fourth scheduling information from the network device on a sixth time domain resource, where the fourth scheduling information indicates that the terminal device receives fourth data on a seventh time domain resource. The transceiving unit 320 is further configured to receive the fourth data from the network device on the seventh time domain resource. The transceiving unit 320 is further configured to receive the third data from the network device on the fifth time domain resource.

When the communication apparatus 300 is used to implement the functions of the network device in the method embodiment shown in fig. 11: the transceiving unit 320 is configured to transmit third scheduling information to the terminal device on the fourth time domain resource, where the third scheduling information indicates that the terminal device switches the active BWP from the first BWP to the second BWP, and the third scheduling information further indicates that the terminal device receives third data on the fifth time domain resource. The processing unit 310 is configured to switch the active BWP from the first BWP to the second BWP. The transceiving unit 320 is further configured to send fourth scheduling information to the terminal device on a sixth time domain resource, where the fourth scheduling information indicates that the terminal device receives fourth data on a seventh time domain resource. The transceiving unit 320 is further configured to send the fourth data to the terminal device on the seventh time domain resource. The transceiving unit 320 is further configured to send the third data to the terminal device on the fifth time domain resource.

When the communication apparatus 300 is used to implement the functions of the terminal device in the method embodiment shown in fig. 13: the transceiving unit 320 is configured to receive third scheduling information from the network device on a fourth time-frequency resource, where the third scheduling information indicates that the terminal device switches the active BWP from the first BWP to the second BWP, and the third scheduling information further indicates that the terminal device transmits third data on a fifth time-frequency resource. The processing unit 310 is configured to switch the active BWP from the first BWP to the second BWP before a sixth time-domain resource. The transceiving unit 320 is further configured to receive sixth scheduling information from the network device on a sixth time-domain resource, where the sixth scheduling information indicates that the terminal device cancels transmitting the third data on the fifth time-frequency resource.

When the communication apparatus 300 is used to implement the functions of the network device in the method embodiment shown in fig. 13: the transceiving unit 320 is configured to send third scheduling information to the first terminal device on the fourth time-frequency resource, where the third scheduling information indicates that the first terminal device switches the activated BWP from the first BWP to the second BWP, and the third scheduling information further indicates that the first terminal device sends third data on the fifth time-frequency resource. The processing unit 310 is configured to switch the active BWP of the first terminal device from the first BWP to the second BWP before the sixth time-domain resource. The transceiving unit 320 is further configured to send sixth scheduling information to the first terminal device on the sixth time domain resource, where the sixth scheduling information indicates that the first terminal device cancels sending the third data on the fifth time frequency resource.

More detailed descriptions about the processing unit 310 and the transceiver unit 320 can be directly obtained by referring to the related descriptions in the method embodiments shown in fig. 3, fig. 11, or fig. 13, which are not repeated herein.

As shown in fig. 16, the communication device 400 includes a processor 410 and an interface circuit 420. Processor 410 and interface circuit 420 are coupled to one another. It is understood that the interface circuit 420 may be a transceiver or an input-output interface. Optionally, the communication device 400 may further include a memory 430 for storing instructions executed by the processor 410 or for storing input data required by the processor 410 to execute the instructions or for storing data generated by the processor 410 after executing the instructions.

When the communication device 400 is used to implement the method shown in fig. 3, fig. 11 or fig. 13, the processor 410 is configured to perform the functions of the processing unit 310, and the interface circuit 420 is configured to perform the functions of the transceiving unit 320.

When the communication device is a chip applied to a terminal device, the terminal device chip implements the functions of the terminal device in the above method embodiment. The terminal device chip receives information from other modules (such as a radio frequency module or an antenna) in the terminal device, wherein the information is sent to the terminal device by the network device; or, the terminal device chip sends information to other modules (such as a radio frequency module or an antenna) in the terminal device, where the information is sent by the terminal device to the network device.

When the communication device is a chip applied to a network device, the network device chip implements the functions of the network device in the above method embodiments. The network device chip receives information from other modules (such as a radio frequency module or an antenna) in the network device, wherein the information is sent to the network device by the terminal device; or, the network device chip sends information to other modules (such as a radio frequency module or an antenna) in the network device, where the information is sent by the network device to the terminal device.

It is understood that the Processor in the embodiments of the present Application may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The general purpose processor may be a microprocessor, but may be any conventional processor.

The method steps in the embodiments of the present application may be implemented by hardware, or may be implemented by software instructions executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash Memory, Read-Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in a network device or a terminal device. Of course, the processor and the storage medium may reside as discrete components in a network device or a terminal device.

In the above embodiments, all or part of the implementation may be realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer program or instructions may be stored in or transmitted over a computer-readable storage medium. The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server that integrates one or more available media. The usable medium may be a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape; or an optical medium, such as a DVD; it may also be a semiconductor medium, such as a Solid State Disk (SSD).

In the embodiments of the present application, unless otherwise specified or conflicting with respect to logic, the terms and/or descriptions in different embodiments have consistency and may be mutually cited, and technical features in different embodiments may be combined to form a new embodiment according to their inherent logic relationship.

In the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. In the description of the text of the present application, the character "/" generally indicates that the former and latter associated objects are in an "or" relationship; in the formula of the present application, the character "/" indicates that the preceding and following related objects are in a relationship of "division".

It is to be understood that the various numerical references referred to in the embodiments of the present application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of the present application. The sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of the processes should be determined by their functions and inherent logic.

Claims

1. A method of communication, comprising:

receiving third scheduling information from the network device on a fourth time domain resource, where the third scheduling information instructs the terminal device to switch the activated bandwidth portion BWP from the first BWP to the second BWP, and the third scheduling information further instructs the terminal device to transmit third data on a fifth time frequency resource, where a time domain resource corresponding to the fifth time frequency resource is a fifth time domain resource, and a start time of the fifth time domain resource is later than an end time of the fourth time domain resource;

switching the active BWP from the first BWP to the second BWP before a sixth time-domain resource, a starting time of the sixth time-domain resource being later than a starting time of the fourth time-domain resource, the starting time of the sixth time-domain resource being earlier than a starting time of the fifth time-domain resource;

and receiving sixth scheduling information from the network device on the sixth time domain resource, where the sixth scheduling information indicates the terminal device to cancel sending the third data on the fifth time frequency resource.

2. The method of claim 1, wherein the sixth scheduling information comprises a cancellation indication field indicating that the transmission of the third data is cancelled.

3. The method according to claim 1, characterized in that the sixth scheduling information comprises information of a tenth time-frequency resource indicating that data transmission in the tenth time-frequency resource is cancelled, the tenth time-frequency resource being partially or completely overlapping with the fifth time-frequency resource.

4. The method according to any of claims 1-3, wherein the third scheduling information comprises an index of the second BWP.

5. The method according to any of claims 1 to 3, wherein the third scheduling information is received on the first BWP; the sixth scheduling information is received on the second BWP.

6. A method of communication, comprising:

sending third scheduling information to a first terminal device on a fourth time domain resource, where the third scheduling information instructs the first terminal device to switch an activated bandwidth portion BWP from a first BWP to a second BWP, and the third scheduling information further instructs the first terminal device to send third data on a fifth time frequency resource, where a time domain resource corresponding to the fifth time frequency resource is a fifth time domain resource, and a start time of the fifth time domain resource is later than an end time of the fourth time domain resource;

switching an active BWP of the first terminal device from the first BWP to the second BWP before a sixth time-domain resource, a starting time of the sixth time-domain resource being later than a starting time of the fourth time-domain resource, the starting time of the sixth time-domain resource being earlier than a starting time of the fifth time-domain resource;

and sending sixth scheduling information to the first terminal device on the sixth time domain resource, where the sixth scheduling information indicates that the first terminal device cancels sending the third data on the fifth time frequency resource.

7. The method of claim 6, wherein the sixth scheduling information comprises a cancellation indication field indicating that the transmission of the third data is cancelled.

8. The method of claim 6, wherein the sixth scheduling information comprises information of a tenth time-frequency resource indicating that data transmission in the tenth time-frequency resource is cancelled, the tenth time-frequency resource partially overlapping or completely overlapping with the fifth time-frequency resource.

9. The method according to any of claims 6 to 8, wherein the third scheduling information comprises an index of the second BWP.

10. The method according to any of claims 6 to 8, wherein the third scheduling information is sent on the first BWP; the sixth scheduling information is transmitted on the second BWP.

11. The method according to any one of claims 6 to 8, further comprising:

and sending fifth scheduling information to the second terminal equipment on an eighth time domain resource, wherein the fifth scheduling information indicates that the second terminal equipment sends fifth data on a ninth time frequency resource, and the ninth time frequency resource is partially overlapped or completely overlapped with the fifth time frequency resource.

12. The method of claim 11, further comprising:

receiving the fifth data from the second terminal device on the ninth time-frequency resource.

13. A communications apparatus comprising means for performing a method as claimed in any of claims 1 to 5 or 6 to 12.

14. A communications device comprising a processor and interface circuitry for receiving signals from or transmitting signals to or from a communications device other than the communications device, the processor being arranged to implement the method of any of claims 1 to 5 or 6 to 12 by logic circuitry or executing code instructions.

15. A computer-readable storage medium, in which a computer program or instructions are stored which, when executed by a communication apparatus, carry out the method of any one of claims 1 to 5 or 6 to 12.