CN113677015A - Data processing method and related equipment - Google Patents

Data processing method and related equipment Download PDF

Info

Publication number
CN113677015A
CN113677015A CN202010414666.7A CN202010414666A CN113677015A CN 113677015 A CN113677015 A CN 113677015A CN 202010414666 A CN202010414666 A CN 202010414666A CN 113677015 A CN113677015 A CN 113677015A
Authority
CN
China
Prior art keywords
scheduling offset
bwp
scheduling
offset threshold
uplink
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010414666.7A
Other languages
Chinese (zh)
Inventor
铁晓磊
薛丽霞
黄雯雯
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN202010414666.7A priority Critical patent/CN113677015A/en
Priority to PCT/CN2021/089828 priority patent/WO2021227855A1/en
Publication of CN113677015A publication Critical patent/CN113677015A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/23Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02Power saving arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446Resources in time domain, e.g. slots or frames
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453Resources in frequency domain, e.g. a carrier in FDMA
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing energy consumption in communication networks in wireless communication networks

Landscapes

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

Abstract

The embodiment of the application discloses a data processing method. The method in the embodiment of the application comprises the following steps: the terminal device receives first configuration information and first indication information sent by the network device, wherein the first indication information is used for indicating a first scheduling offset threshold which takes effect in at least two first scheduling offset threshold candidates. When the first condition is satisfied, the terminal device determines a second scheduling offset threshold value effective on the second BWP according to the first scheduling offset threshold value effective. The method for determining the effective second scheduling offset threshold is beneficial to the terminal equipment to process the shared channel by using the scheduling offset threshold subsequently, and simultaneously, the problem of poor scheduling flexibility of the network equipment caused by the fact that one part of bandwidth is limited for scheduling and the other part of bandwidth is not limited for scheduling is solved.

Description

Data processing method and related equipment
Technical Field
The present application relates to the field of communications, and in particular, to a data processing method and related device.
Background
In a communication system where User Equipment (UE) power consumption is an important aspect of user experience, the third generation partnership project (3 GPP) proposes to reduce the power consumption of NR UEs at NR rel-16(new radio release 16). One aspect of reducing UE power consumption is to improve the mechanism for scheduling data by the base station, i.e., to save UE power consumption by using cross-slot scheduling. The principle of cross-slot scheduling is that a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH)/Physical Uplink Shared Channel (PUSCH) are separated by N slots (slot), where a slot offset between the PDCCH and the PDCCH-scheduled PDSCH can be represented as K0, a slot offset between the PDCCH and the PDCCH-scheduled PUSCH can be represented as K2, and a K0 set and a K2 set are configured by a base station or predefined between the base station and a UE, and K0 or K2 is indicated by Downlink Control Information (DCI).
The cross-time-slot PDSCH scheduling method has the advantages that the UE does not need to buffer PDSCH data in advance, the UE receives the PDSCH data according to the indication of the PDCCH after the PDCCH is decoded, and the UE can selectively and respectively switch a Radio Frequency (RF) module and a baseband (BB) module, so that the effect of saving power is achieved.
The benefit of scheduling PUSCH across slots is that the UE can relax PDCCH decoding time and the UE can down-step voltage, thus saving power consumption. However, in case that the base station is configured with only the minimum K0, and is not configured with the minimum K2, or the base station is configured with only the minimum K2, and is not configured with the minimum K0, the prior art does not specify how the UE and the base station determine the effective minimum K0 limit and the minimum K2 limit. Simply considering that there is no scheduling restriction without configuring the minimum scheduling offset parameter results in scheduling restrictions on one active BWP and no scheduling restrictions on another active BWP, which does not bring any power saving benefit to the UE, but rather scheduling restrictions.
Disclosure of Invention
The application provides a data processing method, which is used for providing a method for determining a scheduling offset threshold, is beneficial to processing a shared channel by using the scheduling offset threshold subsequently, and simultaneously avoids the problem of poor scheduling flexibility of network equipment caused by that one part of bandwidth is limited for scheduling and the other part of bandwidth is not limited for scheduling.
A first aspect of the present application provides a data processing method, including: the terminal device receives first configuration information sent by the network device, the first configuration information being used to configure at least two first scheduling offset threshold candidates for the first bandwidth portion BWP. The terminal device receives first indication information sent by the network device, wherein the first indication information is used for indicating a first scheduling offset threshold which takes effect in at least two first scheduling offset threshold candidates. The terminal device determines a second scheduling offset threshold value in effect on the second BWP according to the first scheduling offset threshold value in effect when a first condition is satisfied, the first condition being that the terminal device has been configured with at least two first scheduling offset threshold candidates and is not configured with a second scheduling offset threshold candidate of the second BWP. The first BWP is an uplink activated BWP, the second BWP is a downlink activated BWP, or the first BWP is a downlink activated BWP and the second BWP is an uplink activated BWP.
In the embodiment of the present application, a terminal device determines a second scheduling offset threshold that takes effect on a second BWP according to a first scheduling offset threshold that takes effect among first scheduling offset threshold candidates, and provides a method for determining the second scheduling offset threshold that takes effect and subsequent specific scheduling, and meanwhile, the problem of poor scheduling flexibility of a network device due to scheduling of a part of bandwidth being limited and scheduling of another part of bandwidth being not limited is avoided.
Optionally, in a possible implementation manner of the first aspect, the determining, by the terminal device in the above step, a second scheduling offset threshold that is effective on the second BWP according to the first scheduling offset threshold that is effective includes: the terminal device determines that the second scheduling offset threshold in effect is equal to the first scheduling offset threshold in effect.
In this possible implementation manner, when the terminal device is not configured with the second scheduling offset threshold candidate of the second BWP, the terminal device determines that the second scheduling offset threshold in effect is equal to the first scheduling offset threshold in effect, which is beneficial to subsequently process the shared channel by using the second scheduling offset threshold in effect, and meanwhile, the problem of poor scheduling flexibility of the network device due to the fact that one part of bandwidth is scheduled in a limited manner and the other part of bandwidth is scheduled in an unlimited manner is avoided.
Optionally, in a possible implementation manner of the first aspect, the step further includes: the terminal device receives second configuration information sent by the network device, wherein the second configuration information includes a plurality of first scheduling offsets and a plurality of second scheduling offsets. Wherein the scheduling offset for scheduling the first shared channel on the first BWP is one of the plurality of first scheduling offsets that is greater than or equal to the first scheduling offset threshold in effect. The scheduling offset used to schedule the second shared channel on the second BWP is one of the plurality of second scheduling offsets greater than or equal to the second scheduling offset threshold in effect.
In this possible implementation manner, the terminal device may reduce unnecessary data caching, and may relax the processing time of the shared channel, thereby achieving the effect of saving power consumption.
Optionally, in a possible implementation manner of the first aspect, the first scheduling offset threshold candidate in the foregoing step is an uplink scheduling offset threshold candidate, the first BWP is an uplink activated BWP, the first scheduling offset is an uplink scheduling offset, and the first shared channel is a physical uplink shared channel PUSCH; the second scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the second BWP is a downlink activated BWP, the second scheduling offset is a downlink scheduling offset, and the second shared channel is a physical downlink shared channel PDSCH. The scheduling offset for scheduling the first shared channel on the first BWP is: scheduling an offset between the PDCCH and PUSCH of the PUSCH on the first BWP to be one of greater than or equal to the first scheduling offset threshold in effect. The scheduling offset for scheduling the second shared channel on the second BWP is: scheduling an offset between the PDCCH and the PDSCH of the PDSCH on the second BWP to be one greater than or equal to the second scheduling offset threshold in effect.
In this possible implementation manner, when the terminal device is not configured with the downlink scheduling offset threshold candidate, the terminal device may determine the effective downlink scheduling offset threshold according to the effective uplink scheduling offset threshold, so as to avoid the problem of poor scheduling flexibility of the network device due to the limited scheduling of the PUSCH and the unlimited scheduling of the PDCCH.
Optionally, in a possible implementation manner of the first aspect, the first scheduling offset threshold candidate in the foregoing step is a downlink scheduling offset threshold candidate, the first BWP is a downlink activated BWP, the first scheduling offset is a downlink scheduling offset, and the first shared channel is a PDSCH; the second scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the second BWP is an uplink activated BWP, the second scheduling offset is an uplink scheduling offset, and the second shared channel is a PUSCH. The scheduling offset for scheduling the first shared channel on the first BWP is: scheduling an offset between the PDCCH and the PDSCH of the PDSCH on the first BWP to be one that is greater than or equal to the first scheduling offset threshold in effect. The scheduling offset for scheduling the second shared channel on the second BWP is: scheduling an offset between the PDCCH and the PUSCH for the PUSCH on the second BWP to be one of greater than or equal to the second scheduling offset threshold in effect.
In this possible implementation manner, when the terminal device is not configured with the uplink scheduling offset threshold candidate, the terminal device may determine the valid uplink scheduling offset threshold according to the valid downlink scheduling offset threshold, so as to avoid the problem of poor scheduling flexibility of the network device due to the fact that the PDSCH restricts scheduling and the PUCCH does not restrict scheduling.
Optionally, in a possible implementation manner of the first aspect, the first configuration information in the above step is further used to configure a second scheduling offset threshold candidate of the second BWP. The steps further include: and when a second condition is met and the received second indication information is used for indicating that the effective first scheduling offset threshold is updated to a preset value, the terminal equipment updates the effective second scheduling offset threshold to the preset value according to the second indication information, wherein the second condition is that the terminal equipment is configured with a first scheduling offset threshold candidate and a second scheduling offset threshold candidate.
In this possible implementation manner, after the terminal device has been configured with the valid downlink scheduling offset threshold and the valid uplink scheduling offset threshold, the network device may update the preset value by using the second indication information to indicate the scheduling offset threshold to be valid according to the scheduling offset threshold determined before the actual situation is changed, so that the network device may schedule the shared channel of the terminal device more flexibly.
A second aspect of the present application provides a data processing method, including: the terminal device receives first configuration information sent by the network device, wherein the first configuration information is used for configuring at least two first scheduling offset threshold candidates of the first BWP. The terminal device determines a preset value for the terminal device to process the first shared channel and/or the second shared channel when a first condition is satisfied, the first condition being that the terminal device is configured with at least two first scheduling offset threshold candidates and is not configured with a second scheduling offset threshold candidate of the second BWP. The first BWP is an uplink activated BWP, the second BWP is a downlink activated BWP, or the first BWP is a downlink activated BWP and the second BWP is an uplink activated BWP.
In the application, when a first condition is met, a terminal device determines a preset value, where the preset value is used for the terminal device to process a first shared channel and/or a second shared channel, a specific scheduling method is provided, and meanwhile, the problem of poor scheduling flexibility of a network device caused by that a part of bandwidth is limited for scheduling and another part of bandwidth is not limited for scheduling is avoided.
Optionally, in a possible implementation manner of the second aspect, the step further includes: the terminal device determines that the second scheduling offset threshold value effective on the second BWP is a preset value.
In this possible implementation manner, when the first condition is satisfied, the terminal device determines that the second scheduling offset threshold that takes effect on the second BWP is the preset value, and proposes a method for determining the second scheduling offset threshold that takes effect and subsequent specific scheduling, and meanwhile avoids the problem of poor scheduling flexibility of the network device due to that one part of bandwidth is scheduled in a limited manner and the other part of bandwidth is not scheduled in a limited manner.
Optionally, in a possible implementation manner of the second aspect, the determining, by the terminal device, that the second scheduling offset threshold effective on the second BWP is a preset value in the foregoing step includes: the terminal device determines that the second scheduling offset threshold effective on the second BWP and the first scheduling offset threshold effective on the first BWP are both equal to the preset value.
In this possible implementation manner, when the terminal device is not configured with the second scheduling offset threshold candidate of the second BWP, the terminal device determines that the second scheduling offset threshold in effect and the first scheduling offset threshold in effect are both equal to the preset value, which is beneficial to subsequently processing the shared channel by using the second scheduling offset threshold in effect, and meanwhile, the problem of poor scheduling flexibility of the network device due to the fact that one part of bandwidth is scheduled in a limited manner and the other part of bandwidth is scheduled in an unrestricted manner is avoided.
Optionally, in a possible implementation manner of the second aspect, the preset value in the above step is zero.
In this possible implementation manner, the network device may not limit the shared channel of the scheduling terminal device, so that the flexibility of the network device scheduling is improved.
Optionally, in a possible implementation manner of the second aspect, the step further includes: the terminal device receives second configuration information sent by the network device, wherein the second configuration information includes a plurality of first scheduling offsets and a plurality of second scheduling offsets. Wherein the scheduling offset for scheduling the first shared channel on the first BWP is one of the plurality of first scheduling offsets that is greater than or equal to the first scheduling offset threshold in effect. The scheduling offset used to schedule the second shared channel on the second BWP is one of the plurality of second scheduling offsets greater than or equal to the second scheduling offset threshold in effect.
In this possible implementation manner, the terminal device may reduce unnecessary data caching, and may relax the processing time of the shared channel, thereby achieving the effect of saving power consumption.
Optionally, in a possible implementation manner of the second aspect, the first scheduling offset threshold candidate in the foregoing step is an uplink scheduling offset threshold candidate, the first BWP is an uplink activated BWP, the first scheduling offset is an uplink scheduling offset, and the first shared channel is a physical uplink shared channel PUSCH; the second scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the second BWP is a downlink activated BWP, the second scheduling offset is a downlink scheduling offset, and the second shared channel is a physical downlink shared channel PDSCH.
In this possible implementation manner, when the terminal device is not configured with the downlink scheduling offset threshold candidate, the terminal device may determine the effective downlink scheduling offset threshold according to the effective uplink scheduling offset threshold, so as to avoid the problem of poor scheduling flexibility of the network device due to the limited scheduling of the PUSCH and the unlimited scheduling of the PDCCH.
Optionally, in a possible implementation manner of the second aspect, the first scheduling offset threshold candidate in the step is a downlink scheduling offset threshold candidate, the first BWP is a downlink activated BWP, the first scheduling offset is a downlink scheduling offset, and the first shared channel is a PDSCH; the second scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the second BWP is an uplink activated BWP, the second scheduling offset is an uplink scheduling offset, and the second shared channel is a PUSCH.
In this possible implementation manner, when the terminal device is not configured with the uplink scheduling offset threshold candidate, the terminal device may determine the valid uplink scheduling offset threshold according to the valid downlink scheduling offset threshold, so as to avoid the problem of poor scheduling flexibility of the network device due to the fact that the PDSCH restricts scheduling and the PUCCH does not restrict scheduling.
A third aspect of the present application provides a data processing method, including: the network device sends first configuration information to the terminal device, the first configuration information being used for configuring at least two first scheduling offset threshold candidates for the first BWP. When a first condition is met, the network device sends first indication information to the terminal device, wherein the first indication information is used for indicating a first scheduling offset threshold which takes effect in at least two first scheduling offset threshold candidates, and is also used for determining a second scheduling offset threshold which takes effect on the second BWP and is not configured to the terminal device, the second scheduling offset threshold which takes effect is determined according to the first scheduling offset threshold which takes effect, and the first condition is that the network device determines that at least two first scheduling offset threshold candidates are configured to the terminal device and a second scheduling offset threshold candidate of the second BWP is not configured to the terminal device. The first BWP is an uplink activated BWP, the second BWP is a downlink activated BWP, or the first BWP is a downlink activated BWP and the second BWP is an uplink activated BWP.
Optionally, in a possible implementation manner of the third aspect, the step further includes: the network device determines that the second scheduling offset threshold in effect is equal to the first scheduling offset threshold in effect.
Optionally, in a possible implementation manner of the third aspect, the step further includes: and the network equipment sends second configuration information to the terminal equipment, wherein the second configuration information comprises a plurality of first scheduling offsets and a plurality of second scheduling offsets. The network device schedules the first shared channel for the terminal device using any one of the first scheduling offsets that is greater than or equal to the first scheduling offset threshold in effect. The network device schedules the second shared channel for the terminal device using any one of the second scheduling offsets that is greater than or equal to the second scheduling offset threshold in effect.
Optionally, in a possible implementation manner of the third aspect, the first scheduling offset threshold candidate in the foregoing step is an uplink scheduling offset threshold candidate, the first BWP is an uplink activated BWP, the first scheduling offset threshold is an uplink scheduling offset threshold, and the first shared channel is a physical uplink shared channel PUSCH. The second scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the second BWP is a downlink activated BWP, the second scheduling offset threshold is an uplink scheduling offset threshold, and the second shared channel is a physical downlink shared channel PDSCH.
Optionally, in a possible implementation manner of the third aspect, the first scheduling offset threshold candidate in the foregoing step is a downlink scheduling offset threshold candidate, the first BWP is a downlink activated BWP, the first scheduling offset is a downlink scheduling offset, and the first shared channel is a PDSCH. The second scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the second BWP is an uplink activated BWP, the second scheduling offset is an uplink scheduling offset, and the second shared channel is a PUSCH.
Optionally, in a possible implementation manner of the third aspect, the first configuration information in the above step is further used to configure a second scheduling offset threshold candidate of the second BWP. The steps further include: and the network equipment sends the second indication information to the terminal equipment. And when a second condition is met, the second indication information is used for indicating that the effective first scheduling offset threshold is updated to a preset value, and is also used for updating the effective second scheduling offset threshold to the preset value according to the second indication information, wherein the second condition is that the network equipment configures a first scheduling offset threshold candidate and a second scheduling offset threshold candidate for the terminal equipment.
A fourth aspect of the present application provides a data processing method, including: the network device sends first configuration information to the terminal device, the first configuration information being used for configuring at least two first scheduling offset threshold candidates for the first BWP. When a first condition is met, the network device determines a preset value, wherein the preset value is used for scheduling the terminal device to process a first shared channel and/or a second shared channel, and the first condition is that the network device determines that at least two first scheduling offset threshold candidates are configured for the terminal device, and a second scheduling offset threshold candidate of a second BWP is not configured for the terminal device. The first BWP is an uplink activated BWP, the second BWP is a downlink activated BWP, or the first BWP is a downlink activated BWP and the second BWP is an uplink activated BWP.
Optionally, in a possible implementation manner of the fourth aspect, the step further includes: the network device determines that the second scheduling offset threshold in effect on the second BWP is a preset value.
Optionally, in a possible implementation manner of the fourth aspect, in the above step: the network device determining that the second scheduling offset threshold effective on the second BWP is a preset value, including: the network device determines that both the second scheduling offset threshold in effect on the second BWP and the first scheduling offset threshold in effect on the first BWP are preset values.
Optionally, in a possible implementation manner of the fourth aspect, the preset value in the step is zero.
Optionally, in a possible implementation manner of the fourth aspect, the step further includes: and the network equipment sends second configuration information to the terminal equipment, wherein the second configuration information comprises a plurality of first scheduling offsets and a plurality of second scheduling offsets. The network device schedules the first shared channel of the terminal device using any one of the first scheduling offsets that is greater than or equal to the first scheduling offset threshold in effect. The network device schedules the second shared channel for the terminal device using any one of the second scheduling offsets that is greater than or equal to the second scheduling offset threshold in effect.
Optionally, in a possible implementation manner of the fourth aspect, the first scheduling offset threshold candidate in the foregoing step is an uplink scheduling offset threshold candidate, the first BWP is an uplink activated BWP, the first scheduling offset is an uplink scheduling offset, and the first shared channel is a PUSCH. The second scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the second BWP is a downlink activated BWP, the second scheduling offset is a downlink scheduling offset, and the second shared channel is a PDSCH.
Optionally, in a possible implementation manner of the fourth aspect, the first scheduling offset threshold candidate in the foregoing step is a downlink scheduling offset threshold candidate, the first BWP is a downlink activated BWP, the first scheduling offset is a downlink scheduling offset, and the first shared channel is a PDSCH. The second scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the second BWP is an uplink activated BWP, the second scheduling offset is an uplink scheduling offset, and the second shared channel is a PUSCH.
A fifth aspect of the present application provides a terminal device, configured to execute the method in the foregoing first aspect or any possible implementation manner of the first aspect, or any possible implementation manner of the second aspect. In particular, the terminal device comprises means or unit for performing the method of the aforementioned first aspect or any possible implementation manner of the first aspect, the second aspect or any possible implementation manner of the second aspect.
A sixth aspect of the present application provides a network device configured to perform the method in the third aspect or any possible implementation manner of the third aspect, or any possible implementation manner of the fourth aspect. In particular, the network device comprises means or unit for performing the method of the aforementioned third aspect or any possible implementation manner of the third aspect, the fourth aspect or any possible implementation manner of the fourth aspect.
A seventh aspect of the present application provides a terminal device comprising a processor coupled with a memory for storing a computer program or instructions, the processor being configured to execute the computer program or instructions in the memory such that the terminal device performs the first aspect or any possible implementation of the first aspect, the second aspect or the method in any possible implementation of the second aspect.
An eighth aspect of the present application provides a network device, which includes a processor coupled with a memory, the memory being configured to store a computer program or instructions, and the processor being configured to execute the computer program or instructions in the memory, so that the network device performs the method of the third aspect or any possible implementation manner of the third aspect, the fourth aspect, or any possible implementation manner of the fourth aspect.
A ninth aspect of the present application provides a computer storage medium having stored therein instructions that, when executed on a computer, cause the computer to perform the method of the foregoing first aspect or any possible implementation manner of the first aspect, any possible implementation manner of the second aspect or the second aspect, any possible implementation manner of the third aspect or the third aspect, or any possible implementation manner of the fourth aspect or the fourth aspect.
A tenth aspect of the present application provides a computer program product which, when executed on a computer, causes the computer to perform the method of the preceding first aspect or any possible implementation manner of the first aspect, the second aspect or any possible implementation manner of the second aspect, the third aspect or any possible implementation manner of the third aspect, the fourth aspect or any possible implementation manner of the fourth aspect.
An eleventh aspect of the present application provides a communication system, including the terminal device (or a chip in the terminal device) in the first aspect or any possible implementation manner of the first aspect, the second aspect or any possible implementation manner of the second aspect, and the network device (or a chip in the network device) in any possible implementation manner of the third aspect or any possible implementation manner of the third aspect, the fourth aspect or any possible implementation manner of the fourth aspect. Alternatively, the communication system comprises the terminal device of the seventh aspect and the network device of the eighth aspect.
A twelfth aspect of the present embodiment provides a chip system, where the chip system includes a processor, and is configured to support a terminal device to implement the functions in the first aspect or any one of the possible implementations of the first aspect, or the second aspect or any one of the possible implementations of the second aspect. In one possible design, the system-on-chip may further include a memory for storing necessary program instructions and data for the terminal device. The chip system may be constituted by a chip, or may include a chip and other discrete devices.
A thirteenth aspect of the present embodiment provides a chip system, where the chip system includes a processor, and is configured to support a network device to implement the functions in any one of the foregoing third aspect or any one of the foregoing possible implementations of the third aspect, and any one of the foregoing fourth aspect or any one of the foregoing possible implementations of the fourth aspect. In one possible design, the system-on-chip may further include a memory, which stores program instructions and data necessary for the network device. The chip system may be constituted by a chip, or may include a chip and other discrete devices.
For technical effects brought by the third, fifth, seventh, ninth, tenth, eleventh, twelfth aspects or any one of possible implementation manners, reference may be made to technical effects brought by different possible implementation manners of the first aspect or the first aspect, and details are not described herein again.
For technical effects brought by the fourth, sixth, eighth, ninth, tenth, eleventh, thirteenth aspects or any one of possible implementation manners, reference may be made to technical effects brought by different possible implementation manners of the third aspect or the third aspect, and details are not described herein again.
Drawings
FIG. 1 is a schematic diagram of a network framework in an embodiment of the present application;
FIG. 2 is a schematic flow chart illustrating a data processing method according to an embodiment of the present application;
fig. 3 is a schematic diagram of a PDSCH time slot relationship between a PDCCH and PDCCH scheduling when a downlink scheduling offset is 0 in the embodiment of the present application;
fig. 4 is a schematic diagram of a PDSCH time slot relationship between a PDCCH and PDCCH scheduling when a downlink scheduling offset is 2 in the embodiment of the present application;
FIG. 5 is another schematic flow chart illustrating a data processing method according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a communication device in an embodiment of the present application;
fig. 7 is a schematic structural diagram of another communication device in the embodiment of the present application;
fig. 8 is another schematic structural diagram of a communication device in the embodiment of the present application;
fig. 9 is another schematic structural diagram of a communication device in the embodiment of the present application;
fig. 10 is a schematic structural diagram of another communication device in the embodiment of the present application;
fig. 11 is another schematic structural diagram of a communication device in the embodiment of the present application.
Detailed Description
The embodiment of the application provides a data processing method. The problem of poor scheduling flexibility of the network equipment caused by the fact that one part of bandwidth is limited for scheduling and the other part of bandwidth is not limited for scheduling is solved.
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. The "plurality" means two or more, and in view of this, the "plurality" may also be understood as "at least two" in the embodiments of the present application. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments.
Fig. 1 shows a schematic diagram of a communication system. The communication system may include a network device 101 and terminal devices 102 to 104 connected to the network device 101.
In the embodiment of the present application, only one network device 101 and three terminal devices 102 to 104 are taken as examples for schematic description. In practical applications, the communication system in the embodiment of the present application may have more network devices 101 and terminal devices 102, and one or more terminal devices 102 may also be used. The number of the network devices 101 and the number of the terminal devices 102 are not limited in the embodiment of the present application.
The network device 101 in the embodiment of the present application may be any device having a wireless transceiving function. Including but not limited to: a base station (e.g., a base station in a fifth generation communication system, a base station in a future communication system, etc.), a Radio Remote Unit (RRU), a wireless relay node, a wireless backhaul node, a transmission node (TRP), a wireless controller in a Cloud Radio Access Network (CRAN) scenario, and the like, which are not limited herein.
A terminal device in embodiments of the present application may refer to a device that provides voice and/or data connectivity to a user, a handheld device with wireless connection capability, or other processing device connected to a wireless modem. The terminal devices may be mobile terminals such as mobile telephones (or "cellular" telephones) and computers with mobile terminals, such as portable, pocket, hand-held, computer-included, or vehicle-mounted mobile devices, that exchange language and/or data with the network device. Such as Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and the like. A Terminal Device may also be referred to as a system, a Subscriber Unit (Subscriber Unit), a Subscriber Station (Subscriber Station), a Mobile Station (Mobile), a Remote Station (Remote Station), an Access Point (Access Point), a Remote Terminal (Remote Terminal), an Access Terminal (Access Terminal), a User Terminal (User Terminal), a User Agent (User Agent), a User Device (User Device), or a User Equipment (User Equipment). In addition, the terminal device may also be a chip system for implementing the UE function. The embodiments of the present application are described only by taking the terminal device as a UE as an example.
The third generation partnership project (3 GPP) standards organization is setting up protocol standards for fifth generation cellular mobile communication systems. Compared with a Long Term Evolution (LTE) system, the NR system supports a larger transmission bandwidth, more transmit/receive antenna arrays, a higher transmission rate, and a more flexible and less-granular scheduling mechanism, and the above characteristics of the NR system provide a wider application range, but greatly increase the power consumption burden of the UE.
In order to reduce the power consumption of the UE, the 3GPP introduced a power saving study (power saving) topic in NR rel-16, and aims to research a power saving scheme that enables the UE to be in various states (including connected state, idle state, inactive state, etc.). Among them, how to save the UE power consumption in the connected state is a research focus.
One aspect of reducing UE power consumption is to improve the mechanism for scheduling data by the base station, i.e., to save UE power consumption by using cross-slot scheduling.
For PDSCH, its slot offset K0 from PDCCH is indicated by the time domain resource allocation field in Downlink Control Information (DCI). K0-0 indicates that PDSCH and PDCCH are on the same slot (slot), K0-1 indicates PDSCH on the slot after PDCCH, and so on.
The slot is under 5GNR, and in case of LTE, the NR slot can be replaced with an LTE subframe.
The base station can schedule the PDSCH to the UE through the PDCCH, the time slot offset between the PDCCH and the scheduled PDSCH is more than or equal to or more than the minimum time slot offset value, if the minimum time slot offset value is more than 0, the scheduled PDSCH and the PDCCH are not in the same time slot, and therefore the UE can reduce unnecessary data caching, can relax the processing time of the PDCCH and achieve the effect of saving power consumption.
For PUSCH, its slot offset K2 from PDCCH is indicated by the time domain resource allocation field in DCI. K2 ═ 0 indicates that the PUSCH is on the same slot as the PDCCH, K2 ═ 1 indicates that the PUSCH is on the slot after the PDCCH, and so on. It should be noted that the UE needs a certain time to prepare PUSCH data, the length of this preparation time is specified in the protocol 38.214, and the resource scheduling base station needs to ensure that the interval between the PUSCH and the PDCCH is greater than the preparation time of the PUSCH.
NR supports configuring multiple Downlink (DL) bandwidth parts (BWPs) and multiple Uplink (UL) BWPs per carrier, and a base station may configure multiple DL BWPs and UL BWPs per carrier to a UE. But at the same time, only one DL BWP is active on one downlink carrier and only one UL BWP is active on one uplink carrier. The base station may dynamically switch the activated DL or UL BWP through the PDCCH. Illustratively, taking DL BWP handover as an example, the base station configures two BWPs, BWP1 is in active state, the UE monitors the PDCCH on BWP1, and upon detecting that BWP2 is indicated in the BWP indicator field of the PDCCH, the UE switches to BWP2, and at this time, the active BWP is switched from BWP1 to BWP 2. After BWP2 is activated, the UE listens for PDCCH on BWP 2.
Currently, TS38.212 discusses a scenario where both DL BWP and UL BWP are configured with scheduling offset, and a minimum K2 is configured for UL active BWP, and a minimum K0 is not configured for DL active BWP; or, when the DL active BWP is configured with the minimum K0 and the UL active BWP is not configured with the minimum K2, how to schedule is not specified.
In view of the above situation, embodiments of the present application provide a data processing method for solving the above situation.
The following describes a data processing method in the embodiment of the present application with reference to the network framework of fig. 1:
in the embodiment of the present application, a network device is a base station, and a terminal device is a UE.
In the embodiment of the present application, there are two cases according to the first and second differences, as follows:
in the first case: the first BWP is an uplink activated BWP, the first scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, and the first scheduling offset is an uplink scheduling offset; the second BWP is a downlink activated BWP, the second scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, and the second scheduling offset is a downlink scheduling offset.
In the second case: the first BWP is a downlink activated BWP, the first scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, and the first scheduling offset is a downlink scheduling offset; the second BWP is an uplink activated BWP, the second scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, and the second scheduling offset is an uplink scheduling offset.
In the embodiment of the present application, the data processing method is described only by taking the first case as an example, and the processing method of the second case is similar to the first processing method, and is not described herein again.
Referring to fig. 2, an embodiment of a data processing method in the embodiment of the present application includes:
201. the network device sends the first configuration information to the terminal device.
The first configuration information in this embodiment may include one first scheduling offset threshold candidate, or may include two or more first scheduling offset threshold candidates.
The first BWP and the second BWP in the embodiment of the present application belong to the same cell.
For a BWP, when the first configuration information has only one first scheduling offset threshold candidate, another first scheduling offset threshold candidate may default to zero, which is considered that the first configuration information is used to configure two first scheduling offset threshold candidates.
The base station sends first configuration information to the UE, where the first configuration information has multiple cases, and the following description describes the cases respectively:
in the first case: the first configuration information is used for configuring at least two uplink scheduling offset threshold candidates for uplink active BWP, but does not include downlink scheduling offset threshold candidates for downlink active BWP.
That is, the base station configures at least two uplink scheduling offset threshold candidates for the UE, and does not configure a downlink scheduling offset threshold candidate.
Wherein the uplink scheduling offset threshold candidate corresponds to the above-mentioned minimum K2, and the downlink scheduling offset threshold candidate corresponds to the above-mentioned minimum K0.
In the second case: the first configuration information is used for configuring at least two downlink scheduling offset threshold candidates for downlink active BWP, but does not include uplink scheduling offset threshold candidates for uplink active BWP.
That is, the base station configures at least two downlink scheduling offset threshold candidates for the UE, and does not configure an uplink scheduling offset threshold candidate.
In the third case: the first configuration information is used for configuring at least two downlink scheduling offset threshold candidates of the downlink active BWP and at least two uplink scheduling offset threshold candidates of the uplink active BWP.
That is, the base station configures at least two downlink scheduling offset threshold candidates and also configures at least two uplink scheduling offset threshold candidates for the UE.
The first condition is relative to the second condition, and when the first scheduling offset threshold candidate is an uplink scheduling offset threshold candidate and the second scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the first condition indicates the first condition. The first condition indicates a second condition when the first scheduling offset threshold candidate is a downlink scheduling offset threshold candidate and the second scheduling offset threshold candidate is an uplink scheduling offset threshold candidate.
In the embodiment of the present application, only the first condition is taken as an example to schematically illustrate the first case, and the first condition indicates that the processing manner of the second case is similar to that of the first case, and details are not described here again.
The first configuration information in the embodiment of the present application has a plurality of cases, and the three cases are only examples, and are not limited herein.
Optionally, the uplink scheduling offset threshold candidate or the downlink scheduling offset threshold candidate may be multiple (that is, the uplink scheduling offset threshold candidate of one uplink BWP may be multiple, and the downlink scheduling offset threshold candidate of one downlink BWP may be multiple), and the specific number is not limited herein.
Illustratively, when the first configuration information is the first case, the uplink scheduling offset threshold candidate includes two candidate values, which are 0 and 2, respectively.
Optionally, the first configuration information further includes a plurality of uplink scheduling offsets and a plurality of downlink scheduling offsets.
202. And the network equipment sends the second configuration information to the terminal equipment.
And the base station sends second configuration information to the UE, wherein the second configuration information comprises a plurality of uplink scheduling offsets and a plurality of downlink scheduling offsets.
The plurality of uplink scheduling offsets may also be referred to as an uplink scheduling offset set, and the plurality of downlink scheduling offsets may also be referred to as a downlink scheduling offset set.
Optionally, the uplink scheduling offset set includes a K2 set (i.e., a set of time offsets between the PDCCH and the PUSCH scheduled by the PDCCH) and a set of starting symbol (S) and length (L) of the PUSCH in this slot; the downlink scheduling offset set includes a set of K0 (i.e., a set of time offsets between the PDCCH and the PDSCH scheduled by the PDCCH) and a set of S and L of the PDSCH in this time slot.
Optionally, the uplink scheduling offset set includes a K2 set and a Start and Length Indicator (SLIV); the downlink scheduling offset set includes a K0 set and a SLIV.
Optionally, the base station may configure the uplink scheduling offset set and the downlink scheduling offset set to the UE through RRC signaling.
Illustratively, the K0 set includes {0, 2, 4, 6}, and the K2 set includes {0, 1, 2, 3, 4, 5, 6}, which indicates that the PDCCH is in the same time slot as the PDSCH scheduled by the PDCCH when K0 is 0, as shown in fig. 3, and indicates that the PDCCH is two time slots apart from the PDSCH scheduled by the PDCCH when K0 is 2, as shown in fig. 4.
Of course, the first configuration information in step 201 may include the second configuration information, or may not include the second configuration information, and is not limited herein. If the first configuration information includes a plurality of uplink scheduling offsets and a plurality of downlink scheduling offsets, step 202 may be omitted.
203. The network device determines a second scheduling offset threshold in effect on the second BWP.
When the first condition (i.e. the first condition of the first configuration information) is satisfied, there are various ways for the base station to determine the downlink scheduling offset threshold value effective on the downlink active BWP, which are respectively described below:
1. the base station determines that the effective downlink scheduling offset threshold value on the downlink active BWP is equal to the effective uplink scheduling offset threshold value on the uplink active BWP.
Illustratively, continuing with the example in steps 201 and 203, if the value of the effective uplink scheduling offset threshold is 1, the base station determines that the effective downlink scheduling offset threshold on the downlink active BWP is also 1.
2. The base station determines the effective downlink scheduling offset threshold on the downlink activated BWP as a preset value.
Optionally, when the first condition is satisfied, the base station determines that both the downlink scheduling offset threshold in effect on the downlink active BWP and the uplink scheduling offset threshold in effect on the uplink active BWP are equal to the preset value.
Alternatively, the preset value may be 0 or a non-zero value, and is not limited herein.
Illustratively, when the preset value is 0, the base station determines that the effective downlink scheduling offset threshold is 0, and continues the foregoing example, the effective uplink scheduling offset threshold is 1, or both the effective uplink scheduling offset threshold and the effective downlink scheduling offset threshold are 0.
In this embodiment of the present application, the valid downlink scheduling offset threshold has no relation with the size of the valid uplink scheduling offset threshold, that is, the valid downlink scheduling offset threshold may be greater than the valid uplink scheduling offset threshold, or may be smaller than or equal to the valid uplink scheduling offset threshold, and specifically, this is not limited here, and the valid downlink scheduling offset threshold is generally smaller than the valid uplink scheduling offset threshold.
204. The network equipment sends the first indication information to the terminal equipment.
When a first condition (namely, a first situation of the first configuration information) is met, the base station sends first indication information to the UE, where the first indication information is used to indicate an uplink scheduling offset threshold that takes effect among uplink scheduling offset threshold candidates, and the first condition is that the base station has configured an uplink scheduling offset threshold candidate to the UE and has not configured a downlink scheduling offset threshold candidate to the UE.
Optionally, the first indication information is Downlink Control Information (DCI) carried by a PDCCH, and 1 bit in the DCI indicates an effective uplink scheduling offset threshold among uplink scheduling offset threshold candidates for uplink active BWP.
For example, continuing with the example in step 201, it is assumed that when the first condition is satisfied, if the index (index) indicated by the first indication information is 0, the effective uplink scheduling offset threshold in the uplink scheduling offset threshold candidates (0 and 2) is the first one of the candidate values, that is, the effective uplink scheduling offset threshold is 0. If the index (index) indicated by the first indication information is 1, the effective uplink scheduling offset threshold in the uplink scheduling offset threshold candidates (0 and 2) is the second of the candidate values, that is, the effective uplink scheduling offset threshold is 2.
Optionally, the first indication information is used to indicate that the effective downlink scheduling offset threshold is a preset value.
Optionally, the first indication information is used to indicate that the effective downlink scheduling offset threshold is equal to the effective uplink scheduling offset threshold.
205. And the network equipment sends the second indication information to the terminal equipment.
When a second condition (namely, a third condition of the first configuration information) is met, the network device sends second indication information to the terminal device, wherein the second condition is that the base station has configured an uplink scheduling offset threshold candidate and a downlink scheduling offset threshold candidate for the UE.
Optionally, the second indication information is used to indicate that the uplink scheduling offset threshold that was effective before is updated to a preset value.
Optionally, the second indication information is used to indicate that the downlink scheduling offset threshold and the uplink scheduling offset threshold that are effective before are both updated to preset values.
Equivalently, the base station has previously configured the uplink scheduling offset threshold candidate and configured the downlink scheduling offset threshold candidate to the UE. The second indication information indicates the UE to update the uplink scheduling offset threshold which is effective before to a preset value, or indicates the UE to update the uplink scheduling offset threshold which is effective before and the downlink scheduling offset threshold to preset values according to the second indication information.
For example, continuing the previous example, the base station has configured the validated uplink scheduling offset threshold to be 0 to the UE before, and the base station sends the indication information to the UE, where the index value indicated by the second indication information is different from the last time, that is, the indication index is 1, the validated uplink scheduling offset threshold becomes 2 (that is, the preset value is 2), and the second indication information indicates that the validated uplink scheduling offset threshold is changed from 0 to 2, and is further used to indicate the UE to update the validated downlink scheduling offset threshold to be 2 according to the second indication information.
Optionally, after the UE receives the second indication information, the UE updates the scheduling offset threshold to a preset value, and then the UE processes the shared channel by using the preset value.
Optionally, the preset value is 0, which is equivalent to that the base station does not limit the shared channel for scheduling the UE, and is beneficial to improving the scheduling flexibility of the base station. Of course, the preset value may also be other values, such as a non-zero value of 1 or 2, which is beneficial for the UE to reduce unnecessary data buffering and to relax the processing time of the shared channel.
206. The terminal device determines a second scheduling offset threshold in effect on the second BWP.
When the first condition (i.e. the first condition of the first configuration information) is satisfied, there are various ways for the UE to determine the effective downlink scheduling offset threshold on the downlink active BWP, which are respectively described below:
1. and the UE determines that the effective downlink scheduling offset threshold on the downlink active BWP is equal to the effective uplink scheduling offset threshold on the uplink active BWP indicated in the indication information.
Illustratively, continuing with the example in steps 201 and 203, if the value of the effective uplink scheduling offset threshold is 0, the base station determines that the effective downlink scheduling offset threshold on the downlink active BWP is also 0.
Optionally, since the UE is not configured with the downlink scheduling offset threshold candidate, the UE determines that the downlink scheduling offset threshold candidate is the same as the uplink scheduling offset threshold candidate (for example, 0 and 2), and then determines the valid downlink scheduling offset threshold according to the index in the indication information.
2. And the UE determines the effective downlink scheduling offset threshold on the downlink activated BWP as a preset value.
Optionally, when the first condition is satisfied, the UE may determine that the downlink scheduling offset threshold validated on the downlink active BWP and the uplink scheduling offset threshold validated on the uplink active BWP are both equal to the preset value, without receiving the indication information sent by the base station or ignoring the uplink scheduling offset threshold validated in the indication information. That is, when the UE determines that the base station does not configure the effective uplink scheduling offset threshold on the uplink active BWP or does not configure the effective downlink scheduling offset threshold on the downlink active BWP, the base station determines that both the effective downlink scheduling offset threshold on the downlink active BWP and the effective uplink scheduling offset threshold on the uplink active BWP are the preset values.
Alternatively, the preset value may be 0 or a non-zero value, and is not limited herein.
Illustratively, when the preset value is 3, continuing the foregoing example, when the first condition is satisfied and the effective uplink scheduling offset threshold is 1, the UE determines that the effective downlink scheduling offset threshold is 3, or both the effective uplink scheduling offset threshold and the effective downlink scheduling offset threshold are 3.
When the second condition (i.e. the third condition of the first configuration information) is satisfied, the UE determines the downlink scheduling offset threshold value valid on the downlink active BWP in the following manner:
the base station has previously configured an uplink scheduling offset threshold candidate and a downlink scheduling offset threshold candidate to the UE. And the UE updates the effective uplink scheduling offset threshold value to a preset value according to the second indication information, and the UE also updates the effective downlink scheduling offset threshold value to a preset value according to the second indication information.
For example, continuing the previous example, the base station has configured the effective uplink scheduling offset threshold to be 0 to the UE before, the base station sends the indication information to the UE, the index value indicated by the second indication information is different from the last time, that is, the indication index is 1, the effective uplink scheduling offset threshold becomes 2 (that is, the preset value is 2), the UE changes the effective uplink scheduling offset threshold from 0 to 2 according to the second indication information, and the UE updates the effective downlink scheduling offset threshold to 2 according to the second indication information.
And the UE updates the effective uplink scheduling offset threshold value to a preset value according to the indication information and determines that the effective downlink scheduling offset threshold value is also updated to the preset value. And receiving the PDSCH and/or transmitting the PUSCH by using the updated preset value.
207. The network device schedules the first shared channel to the terminal device using any one of the first scheduling offsets that is greater than or equal to the first scheduling offset threshold in effect.
And after determining the effective uplink scheduling offset threshold, the base station schedules the PUSCH to the UE by using any uplink scheduling offset which is greater than or equal to the effective uplink scheduling offset threshold in the K2 set.
Illustratively, the K2 set includes {0, 1, 2, 3, 4, 5, 6}, and if the effective uplink scheduling offset threshold on uplink active BWP is 1, the base station schedules PUSCH to the UE using one of the values 1, 2, 3, 4, 5, or 6 in the K2 set. And if the effective uplink scheduling offset threshold value on the uplink activated BWP is 3, the base station uses one value of 3, 4, 5 or 6 in the K2 set to schedule the PUSCH to the UE.
208. The terminal device processes the first shared channel using the validated first scheduling offset threshold.
After determining the effective uplink scheduling offset threshold, the UE may process the downlink control channel according to the effective first scheduling offset threshold, and send the PUSCH to the base station according to the scheduling information of the downlink control channel.
The offset between the slot where the PUSCH starting symbol sent by the UE is located and the slot where the PDCCH starting symbol scheduling the PUSCH is located is an uplink scheduling offset that is greater than or equal to the effective uplink scheduling offset threshold.
The offset between the slot where the PDSCH starting symbol received by the UE is located and the slot where the PDCCH starting symbol scheduling the PDSCH is located is a downlink scheduling offset that is greater than or equal to the effective downlink scheduling offset threshold.
Illustratively, the K2 set includes {0, 1, 2, 3, 4, 5, 6}, and if the uplink scheduling offset threshold in effect on uplink activated BWP is 0, the UE determines that the value (0, 1, 2, 3, 4, 5, or 6) in the K2 set is greater than or equal to 0, so that the UE may know that the PDCCH-scheduled PUSCH may be transmitted to the base station in the time slot in which the PDCCH is located before receiving the PDCCH transmitted by the base station, and may also transmit the PDCCH-scheduled PUSCH to the base station in the first to sixth time slots after the time slot in which the PDCCH is located. Specifically, which slot the UE transmits PUSCH depends on the base station indicated K2.
For example, if the effective uplink scheduling offset threshold on the uplink active BWP is 3, the UE determines that the value (3, 4, 5, or 6) in the set K2 is greater than or equal to 3, and before receiving the PDCCH sent by the base station, the UE may know that the PDCCH-scheduled PDSCH may be sent to the base station in the third to sixth time slots after the time slot where the PDCCH is located. Specifically, which slot the UE transmits PUSCH depends on the base station indicated K2.
209. The network device schedules the second shared channel for the terminal device using any one of the second scheduling offsets that is greater than or equal to the second scheduling offset threshold in effect.
And after determining the effective downlink scheduling offset threshold, the base station schedules the PDSCH of the UE by using any downlink scheduling offset which is greater than or equal to the effective downlink scheduling offset threshold in the K0 set.
Illustratively, continuing with the above example, if the K0 set includes {0, 2, 4, 6}, and the effective downlink scheduling offset threshold on downlink active BWP is 1, the base station schedules PDSCH of UE using 2, 4 or 6 in the K0 set.
210. The terminal device processes the second shared channel using the validated second scheduling offset threshold.
And after determining the effective downlink scheduling offset threshold, the UE receives the PDSCH by using the effective downlink scheduling offset threshold.
And the UE receives the offset between the time slot of the PDSCH starting symbol and the time slot of the PDCCH starting symbol for scheduling the PDSCH, wherein the offset is a downlink scheduling offset which is greater than or equal to the effective downlink scheduling offset threshold.
Illustratively, the K0 set includes {0, 2, 4, 6}, and if the downlink scheduling offset threshold in effect on the downlink activation BWP is 0, the UE determines a value (0, 2, 4, or 6) greater than or equal to 0 in the K0 set, and before receiving the PDCCH sent by the base station, the UE may know in advance that the PDSCH sent by the base station may be received in the time slot where the PDCCH is located, and may also receive the PDSCH sent by the base station in the second, fourth, or sixth time slot after the time slot where the PDCCH is located. The PDSCH is specifically scheduled by the PDCCH on which time slot.
For example, if the threshold of the effective downlink scheduling offset on the downlink active BWP is 4, the UE determines that the value in the set K0 is greater than or equal to 4 (4 or 6), and after receiving the PDCCH sent by the base station, the UE may receive the PDSCH sent by the base station in the fourth or sixth time slot after the time slot where the PDCCH is located, where the PDSCH is scheduled by the PDCCH.
If the effective downlink scheduling offset threshold is 0, which is equivalent to not limiting the scheduling of the base station, the values in the K0 set or the K2 set configured by the base station are all available, which is beneficial to improving the scheduling flexibility of the base station. If the effective downlink scheduling offset threshold is a nonzero value such as 2 or 3, the UE is facilitated to reduce unnecessary data caching, and the processing time of the PDCCH can be relaxed.
The timing sequence between step 202 and step 201 in the embodiment of the present application is not limited, that is, step 202 may precede step 201. If the second indication information is not updated, step 205 may be absent. Step 205 may also follow step 210 if the second indication is updated. Step 206 may be after step 204 (i.e., the UE determines the effective downlink scheduling offset threshold according to the indication information), or step 206 may be before step 204 (i.e., the UE does not directly determine the effective downlink scheduling offset threshold as the preset value according to the indication information). Step 203 and step 204 have no timing limitation, that is, step 203 and step 204 can be executed simultaneously, and step 203 can also be executed after step 204. Step 207 and step 209 have no timing limitation, step 207 and step 209 are optional, step 208 and step 210 have no timing limitation, step 208 and step 210 are optional, and the details are not limited herein.
In the embodiment of the present application, when the UE is not configured with the valid downlink scheduling offset threshold candidate, the UE determines that the valid downlink scheduling offset threshold is equal to or a preset value of the valid uplink scheduling offset threshold, or when the UE is not configured with the valid uplink scheduling offset threshold candidate, the UE determines that the valid uplink scheduling offset threshold is equal to or a preset value of the valid downlink scheduling offset threshold. The UE is favorable for receiving the PDSCH by using the effective lower scheduling offset threshold value subsequently, and sending the PUSCH by using the effective upper scheduling offset threshold value, and meanwhile, the problem of poor scheduling flexibility of network equipment caused by uplink limited scheduling and downlink unlimited scheduling or downlink limited scheduling and uplink unlimited scheduling is avoided.
It can be understood that, when the first BWP is a downlink active BWP, the first scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, and the first scheduling offset is a downlink scheduling offset; the second BWP is an uplink activated BWP, the second scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, and when the second scheduling offset is an uplink scheduling offset, the processing flow is similar to the above, and details are not repeated here.
Referring to fig. 5, another embodiment of the data processing method in the embodiment of the present application includes:
501. the network device sends the first configuration information to the terminal device.
502. And the network equipment sends the second configuration information to the terminal equipment.
Steps 501 to 502 in this embodiment are similar to steps 201 to 202 in the embodiment shown in fig. 2, and are not described again here.
503. The network device determines a preset value.
When the first condition (i.e., the first case of the first configuration information) is satisfied, the base station determines a preset value, which is used for the base station to schedule a shared channel (PDSCH and/or PUSCH) of the UE.
Optionally, when the base station configures an uplink scheduling offset threshold candidate to the UE and does not configure a downlink scheduling offset threshold candidate to the UE, the base station directly determines a preset value and schedules the PDSCH of the UE using the preset value.
Optionally, when the base station configures an uplink scheduling offset threshold candidate to the UE and does not configure a downlink scheduling offset threshold candidate to the UE, the base station directly determines a preset value and uses the preset value to schedule the PDSCH and the PUSCH of the UE.
Alternatively, the preset value may be 0 or a non-zero value, and is not limited herein.
504. The terminal device determines a preset value.
When the first condition (i.e., the first case of the first configuration information) is satisfied, the UE determines a preset value, which is used for the UE to process a shared channel (PDSCH and/or PUSCH).
Optionally, when the base station configures an uplink scheduling offset threshold candidate to the UE and does not configure a downlink scheduling offset threshold candidate to the UE, the UE directly uses the preset value to send the PDSCH to the base station.
Optionally, when the base station configures an uplink scheduling offset threshold candidate to the UE and does not configure a downlink scheduling offset threshold candidate to the UE, the UE directly uses the preset value to send the PDSCH to the base station and receive the PDSCH.
Alternatively, the preset value may be 0 or a non-zero value, and is not limited herein.
505. The network equipment schedules the first shared channel of the terminal equipment by using any one first scheduling offset which is greater than or equal to a preset value in the plurality of first scheduling offsets.
And after determining the preset value, the base station schedules the PUSCH of the UE by using any uplink scheduling offset which is greater than or equal to the preset value in the K2 set.
Illustratively, the K2 set includes {0, 1, 2, 3, 4, 5, 6}, and if the preset value is 1, the base station schedules the PUSCH of the UE using 1, 2, 3, 4, 5, or 6 in the K2 set. If the preset value is 3, the base station uses 3, 4, 5 or 6 in the K2 set to schedule the PUSCH of the UE.
506. The terminal device processes the first shared channel using a preset value.
And after determining the preset value, the UE transmits the PUSCH to the base station by using the preset value.
The offset between the slot where the PUSCH starting symbol sent by the UE is located and the slot where the PDCCH starting symbol for scheduling the PUSCH is located is an uplink scheduling offset which is greater than or equal to a preset value.
Illustratively, the K2 set includes {0, 1, 2, 3, 4, 5, 6}, if the preset value is 0, the UE determines a value (0, 1, 2, 3, 4, 5, or 6) greater than or equal to 0 in the K2 set, and before receiving the PDCCH transmitted by the base station, the UE may know that the PDCCH-scheduled PUSCH may be transmitted to the base station in the time slot in which the PDCCH is located, and may also transmit the PDCCH-scheduled PUSCH to the base station in the first to sixth time slots after the time slot in which the PDCCH is located. Specifically, which slot the UE transmits PUSCH depends on the base station indicated K2.
For example, if the preset value is 0, the UE determines that the value (0, 1, 2, 3, 4, 5, or 6) in the K2 set is greater than or equal to 0, and before receiving the PDCCH sent by the base station, the UE may know that the PDCCH-scheduled PUSCH may be sent to the base station in the time slot in which the PDCCH is located, or may send the PDCCH-scheduled PUSCH to the base station in the first to sixth time slots after the time slot in which the PDCCH is located. Specifically, which slot the UE transmits PUSCH depends on the base station indicated K2.
For example, if the preset value is 3, the UE determines a value (3, 4, 5, or 6) greater than or equal to 3 in the K2 set, and before receiving the PDCCH transmitted by the base station, the UE may know that the PDCCH scheduled PDSCH may be transmitted to the base station in the third to sixth time slots after the time slot in which the PDCCH is located.
Specifically, which slot the UE transmits PUSCH depends on the base station indicated K2.
507. The network device schedules the second shared channel of the terminal device using any one of the second scheduling offsets greater than or equal to the preset value among the plurality of second scheduling offsets.
And after determining the preset value, the base station schedules the PDSCH of the UE by using any downlink scheduling offset which is greater than or equal to the preset value in the K0 set.
Illustratively, continuing with the above example, if the K0 set includes {0, 2, 4, 6}, and the preset value is 1, the base station schedules PDSCH of UE using 2, 4, or 6 in the K0 set.
508. The terminal device processes the second shared channel using a preset value.
And after determining the preset value, the UE receives the PDSCH by using the preset value.
And the UE receives the offset between the time slot of the PDSCH starting symbol and the time slot of the PDCCH starting symbol for scheduling the PDSCH, wherein the offset is a downlink scheduling offset which is greater than or equal to a preset value.
Illustratively, the K0 set includes {0, 2, 4, 6}, if the preset value is 0, the UE determines a value (0, 2, 4, or 6) greater than or equal to 0 in the K0 set, and before receiving the PDCCH sent by the base station, the UE may know in advance that the PDSCH sent by the base station may be received in the time slot in which the PDCCH is located, and may also receive the PDSCH sent by the base station in the second, fourth, or sixth time slot after the time slot in which the PDCCH is located. The PDSCH is specifically scheduled by the PDCCH on which time slot.
For example, if the preset value is 4, the UE determines a value (4 or 6) greater than or equal to 4 in the K0 set, and after receiving the PDCCH sent by the base station, the UE may receive the PDSCH sent by the base station in a fourth or sixth time slot after the time slot where the PDCCH is located, where the PDSCH is scheduled by the PDCCH.
If the preset value is 0, which is equivalent to not limiting the scheduling of the base station, the medium value of the K0 set or the K2 set configured by the base station is available, which is beneficial to improving the scheduling flexibility of the base station. If the effective downlink scheduling offset threshold is a nonzero value such as 2 or 3, the UE is facilitated to reduce unnecessary data caching, and the processing time of the PDCCH can be relaxed.
The timing sequence between step 502 and step 501 in the embodiment of the present application is not limited, that is, step 502 may precede step 501. Step 504 may precede step 503. Step 505 and step 507 have no timing limitation, step 505 and step 507 are optional, step 506 and step 508 have no timing limitation, step 506 and step 508 are optional, and the details are not limited herein.
According to the embodiment of the application, when the UE is not configured with the effective downlink scheduling offset threshold candidate, the UE determines the preset value and sends the PUSCH to the base station by using the preset value. Or when the UE is not configured with the effective uplink scheduling offset threshold candidate, the UE determines a preset value and receives the PDSCH sent by the base station by using the preset value. Meanwhile, the problem of poor scheduling flexibility of the base station caused by uplink limited scheduling and downlink unlimited scheduling or downlink limited scheduling and uplink unlimited scheduling is solved.
With reference to fig. 6, the data processing method in the embodiment of the present application is described above, and communication equipment in the embodiment of the present application is described below, where an embodiment of a terminal device in the embodiment of the present application includes:
referring to fig. 6, an embodiment of the present application provides a communication device 600, and specifically, the communication device 600 may be a terminal device, where the communication device 600 includes: a transceiver 601 and a processing unit 602.
A transceiving unit 601, configured to receive first configuration information sent by a network device, where the first configuration information is used to configure at least two first scheduling offset threshold candidates of a first bandwidth portion BWP.
The transceiving unit 601 is further configured to receive first indication information sent by the network device, where the first indication information is used to indicate a first scheduling offset threshold that takes effect in at least two first scheduling offset threshold candidates.
A processing unit 602, configured to determine a second scheduling offset threshold that is valid on the second BWP according to the valid first scheduling offset threshold when a first condition is satisfied, where the first condition is that the terminal device has been configured with at least two first scheduling offset threshold candidates and is not configured with a second scheduling offset threshold candidate of the second BWP.
The first BWP is an uplink activated BWP, the second BWP is a downlink activated BWP, or the first BWP is a downlink activated BWP and the second BWP is an uplink activated BWP.
Optionally, the processing unit 602 is specifically configured to determine that the second effective scheduling offset threshold is equal to the first effective scheduling offset threshold.
Optionally, the transceiver 601 is further configured to receive second configuration information sent by the network device, where the second configuration information includes a plurality of first scheduling offsets and a plurality of second scheduling offsets. Wherein the scheduling offset for scheduling the first shared channel on the first BWP is one of the plurality of first scheduling offsets that is greater than or equal to the first scheduling offset threshold in effect. The scheduling offset used to schedule the second shared channel on the second BWP is one of the plurality of second scheduling offsets greater than or equal to the second scheduling offset threshold in effect.
Optionally, the first scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the first BWP is an uplink activated BWP, the first scheduling offset is an uplink scheduling offset, and the first shared channel is a physical uplink shared channel PUSCH; the second scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the second BWP is a downlink activated BWP, the second scheduling offset is a downlink scheduling offset, and the second shared channel is a physical downlink shared channel PDSCH.
Optionally, the first scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the first BWP is a downlink activated BWP, the first scheduling offset is a downlink scheduling offset, and the first shared channel is a PDSCH; the second scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the second BWP is an uplink activated BWP, the second scheduling offset is an uplink scheduling offset, and the second shared channel is a PUSCH.
Optionally, the first configuration information is further used for configuring a second scheduling offset threshold candidate for the second BWP.
The processing unit 602 is further configured to update the effective second scheduling offset threshold to a preset value according to the second indication information when the second condition is met and the received second indication information is used to indicate that the effective first scheduling offset threshold is updated to the preset value, where the second condition is that the terminal device has been configured with the first scheduling offset threshold candidate and the second scheduling offset threshold candidate.
In this embodiment, operations performed by each unit in the terminal device are similar to those described in the embodiment shown in fig. 2 or fig. 5, and are not described again here.
In this embodiment, when the terminal device is not configured with the valid downlink scheduling offset threshold candidate, the processing unit 602 determines that the valid downlink scheduling offset threshold is equal to the valid uplink scheduling offset threshold, or when the terminal device is not configured with the valid uplink scheduling offset threshold candidate, the processing unit 602 determines that the valid uplink scheduling offset threshold is equal to the valid downlink scheduling offset threshold. The terminal equipment can receive the PDSCH by using the effective lower scheduling offset threshold value subsequently, and send the PUSCH by using the effective upper scheduling offset threshold value, and meanwhile, the problem of poor scheduling flexibility of the network equipment caused by uplink limited scheduling and downlink unlimited scheduling or downlink limited scheduling and uplink unlimited scheduling is avoided.
Referring to fig. 7, an embodiment of the present application provides another communication device 700, specifically, the communication device 700 may be a terminal device, where the communication device 700 includes: a transceiver unit 701 and a processing unit 702.
A transceiving unit 701, configured to receive first configuration information sent by a network device, where the first configuration information is used to configure at least two first scheduling offset threshold candidates of a first BWP.
A processing unit 702, configured to determine a preset value, where the preset value is used for the communication device to process the first shared channel and/or the second shared channel, when a first condition is satisfied, where the first condition is that the terminal device is configured with at least two first scheduling offset threshold candidates, and is not configured with a second scheduling offset threshold candidate of the second BWP.
The first BWP is an uplink activated BWP, the second BWP is a downlink activated BWP, or the first BWP is a downlink activated BWP and the second BWP is an uplink activated BWP.
Optionally, the processing unit 702 is further configured to determine that the second scheduling offset threshold in effect on the second BWP is a preset value
Optionally, the processing unit 702 is specifically configured to determine that both the second scheduling offset threshold effective on the second BWP and the first scheduling offset threshold effective on the first BWP are equal to a preset value.
Optionally, the preset value is zero.
Optionally, the transceiver 701 is further configured to receive second configuration information sent by the network device, where the second configuration information includes a plurality of first scheduling offsets and a plurality of second scheduling offsets. Wherein the scheduling offset for scheduling the first shared channel on the first BWP is one of the plurality of first scheduling offsets that is greater than or equal to the first scheduling offset threshold in effect. The scheduling offset used to schedule the second shared channel on the second BWP is one of the plurality of second scheduling offsets greater than or equal to the second scheduling offset threshold in effect.
Optionally, the first scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the first BWP is an uplink activated BWP, the first scheduling offset is an uplink scheduling offset, and the first shared channel is a physical uplink shared channel PUSCH; the second scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the second BWP is a downlink activated BWP, the second scheduling offset is a downlink scheduling offset, and the second shared channel is a physical downlink shared channel PDSCH.
Optionally, the first scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the first BWP is a downlink activated BWP, the first scheduling offset is a downlink scheduling offset, and the first shared channel is a PDSCH; the second scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the second BWP is an uplink activated BWP, the second scheduling offset is an uplink scheduling offset, and the second shared channel is a PUSCH.
In this embodiment, operations performed by each unit in the terminal device are similar to those described in the embodiment shown in fig. 2 or fig. 5, and are not described again here.
In this embodiment, when the terminal device is not configured with the valid downlink scheduling offset threshold candidate, the processing unit 702 determines that the valid downlink scheduling offset threshold is a preset value, or when the terminal device is not configured with the valid uplink scheduling offset threshold candidate, the processing unit 702 determines that the valid uplink scheduling offset threshold is a preset value. The terminal equipment can receive the PDSCH by using the effective lower scheduling offset threshold value subsequently, and send the PUSCH by using the effective upper scheduling offset threshold value, and meanwhile, the problem of poor scheduling flexibility of the network equipment caused by uplink limited scheduling and downlink unlimited scheduling or downlink limited scheduling and uplink unlimited scheduling is avoided.
Referring to fig. 8, an embodiment of the present application provides another communication device 800, where specifically, the communication device 800 may be a network device, and the communication device 800 includes: a transceiving unit 801 and a processing unit 802.
A transceiving unit 801, configured to send first configuration information to a terminal device, where the first configuration information is used to configure at least two first scheduling offset threshold candidates for a first BWP.
A processing unit 802, configured to send, to a terminal device, first indication information when a first condition is met, where the first indication information is used to indicate a first scheduling offset threshold that takes effect among at least two first scheduling offset threshold candidates, and is further used to determine that a second scheduling offset threshold that takes effect on a second BWP is not configured, where the second scheduling offset threshold that takes effect is determined according to the first scheduling offset threshold that takes effect, and the first condition is that a network device determines that at least two first scheduling offset threshold candidates have been configured to the terminal device and that a second scheduling offset threshold candidate of the second BWP is not configured to the terminal device.
The first BWP is an uplink activated BWP, the second BWP is a downlink activated BWP, or the first BWP is a downlink activated BWP and the second BWP is an uplink activated BWP.
Optionally, the processing unit 802 is further configured to determine that the second effective scheduling offset threshold is equal to the first effective scheduling offset threshold.
Optionally, the transceiver unit 801 is further configured to send second configuration information to the terminal device, where the second configuration information includes a plurality of first scheduling offsets and a plurality of second scheduling offsets.
Optionally, the processing unit 802 is further configured to schedule the first shared channel of the terminal device using any one of the plurality of first scheduling offsets that is greater than or equal to the effective first scheduling offset threshold.
Optionally, the processing unit 802 is further configured to schedule the second shared channel of the terminal device using any one of the plurality of second scheduling offsets that is greater than or equal to the second scheduling offset threshold in effect.
Optionally, the first scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the first BWP is an uplink activated BWP, the first scheduling offset threshold is an uplink scheduling offset threshold, and the first shared channel is a physical uplink shared channel PUSCH.
The second scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the second BWP is a downlink activated BWP, the second scheduling offset threshold is an uplink scheduling offset threshold, and the second shared channel is a physical downlink shared channel PDSCH.
Optionally, the first scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the first BWP is a downlink activated BWP, the first scheduling offset is a downlink scheduling offset, and the first shared channel is a PDSCH.
The second scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the second BWP is an uplink activated BWP, the second scheduling offset is an uplink scheduling offset, and the second shared channel is a PUSCH.
Optionally, the first configuration information is further used for configuring a second scheduling offset threshold candidate for the second BWP.
Optionally, the transceiver 801 is further configured to send second indication information to the terminal device. And when a second condition is met, the second indication information is used for indicating that the effective first scheduling offset threshold is updated to a preset value, and is also used for updating the effective second scheduling offset threshold to the preset value according to the second indication information, wherein the second condition is that the network equipment configures a first scheduling offset threshold candidate and a second scheduling offset threshold candidate for the terminal equipment.
In this embodiment, operations performed by each unit in the network device are similar to those described in the embodiment shown in fig. 2 or fig. 5, and are not described again here.
In this embodiment, when the network device does not configure the UE with the valid downlink scheduling offset threshold candidate, the processing unit 802 determines that the valid downlink scheduling offset threshold is equal to the valid uplink scheduling offset threshold, and when the network device does not configure the valid uplink scheduling offset threshold candidate to the UE, the processing unit 802 determines that the valid uplink scheduling offset threshold is equal to the valid uplink scheduling offset threshold. The method is beneficial to the network equipment to schedule the UE to process the shared channel by utilizing the effective lower scheduling offset threshold and the effective upper scheduling offset threshold, and simultaneously, the problem of poor scheduling flexibility of the network equipment caused by uplink limited scheduling and downlink unlimited scheduling or downlink limited scheduling and uplink unlimited scheduling is avoided.
Referring to fig. 9, an embodiment of the present application provides another communication device 900, specifically, the communication device 900 may be a network device, where the communication device 900 includes: a transceiving unit 901 and a processing unit 902.
A transceiving unit 901, configured to send first configuration information to a terminal device, where the first configuration information is used to configure at least two first scheduling offset threshold candidates of a first BWP.
A processing unit 902, configured to determine a preset value, where the preset value is used for scheduling the terminal device to process the first shared channel and/or the second shared channel, when a first condition is met, where the first condition is that the network device determines to configure at least two first scheduling offset threshold candidates to the terminal device, and does not configure a second scheduling offset threshold candidate for the second BWP to the terminal device.
The first BWP is an uplink activated BWP, the second BWP is a downlink activated BWP, or the first BWP is a downlink activated BWP and the second BWP is an uplink activated BWP.
Optionally, the processing unit 902 is further configured to determine that the second scheduling offset threshold in effect on the second BWP is a preset value.
Optionally, the processing unit 902 is specifically configured to determine that both the second scheduling offset threshold effective on the second BWP and the first scheduling offset threshold effective on the first BWP are preset values.
Optionally, the preset value is zero.
Optionally, the transceiver 901 is further configured to send second configuration information to the terminal device, where the second configuration information includes a plurality of first scheduling offsets and a plurality of second scheduling offsets.
Optionally, the processing unit 902 is further configured to schedule the first shared channel of the terminal device using any one of the plurality of first scheduling offsets, which is greater than or equal to the first scheduling offset threshold in effect.
Optionally, the processing unit 902 is further configured to schedule the second shared channel of the terminal device using any one of the plurality of second scheduling offsets, which is greater than or equal to the second scheduling offset threshold that is in effect.
Optionally, the first scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the first BWP is an uplink activated BWP, the first scheduling offset is an uplink scheduling offset, and the first shared channel is a PUSCH.
The second scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the second BWP is a downlink activated BWP, the second scheduling offset is a downlink scheduling offset, and the second shared channel is a PDSCH.
Optionally, the first scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the first BWP is a downlink activated BWP, the first scheduling offset is a downlink scheduling offset, and the first shared channel is a PDSCH.
The second scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the second BWP is an uplink activated BWP, the second scheduling offset is an uplink scheduling offset, and the second shared channel is a PUSCH.
In this embodiment, operations performed by each unit in the network device are similar to those described in the embodiment shown in fig. 2 or fig. 5, and are not described again here.
In this embodiment, when the network device does not configure the effective downlink scheduling offset threshold candidate to the UE, the processing unit 902 determines that the effective downlink scheduling offset threshold is the preset value, and when the network device does not configure the effective uplink scheduling offset threshold candidate to the UE, the processing unit 902 determines that the effective uplink scheduling offset threshold is the preset value. The method is beneficial to the network equipment to schedule the UE to process the shared channel by utilizing the effective lower scheduling offset threshold and the effective upper scheduling offset threshold, and simultaneously, the problem of poor scheduling flexibility of the network equipment caused by uplink limited scheduling and downlink unlimited scheduling or downlink limited scheduling and uplink unlimited scheduling is avoided.
Referring to fig. 10, another communication device 1000 is provided in the embodiment of the present application, and specifically, the communication device 1000 may be a terminal device, and for convenience of description, only a portion related to the embodiment of the present application is shown, and details of the specific technology are not disclosed, please refer to the method portion of the embodiment of the present application. The terminal device may be any terminal device including a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), a point of sale (POS), a vehicle-mounted computer, and the like, taking the terminal device as the mobile phone as an example:
fig. 10 is a block diagram illustrating a partial structure of a mobile phone related to a terminal device provided in an embodiment of the present application. Referring to fig. 10, the cellular phone includes: radio Frequency (RF) circuit 1010, memory 1020, input unit 1030, display unit 1040, sensor 1050, audio circuit 1060, wireless fidelity (WiFi) module 1070, processor 1090, and power source 1090. Those skilled in the art will appreciate that the handset configuration shown in fig. 10 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The following describes each component of the mobile phone in detail with reference to fig. 10:
RF circuit 1010 may be used for receiving and transmitting signals during a message transmission or call, and in particular, for processing downlink messages from a base station after being received by processor 1090; in addition, the data for designing uplink is transmitted to the base station. In general, RF circuit 1010 includes, but is not limited to, an antenna, at least one Amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, the RF circuitry 1010 may also communicate with networks and other devices via wireless communications. The wireless communication may use any communication standard or protocol, including but not limited to Global System for Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Messaging Service (SMS), and the like.
The memory 1020 may be used to store software programs and modules, and the processor 1090 executes various functional applications and data processing of the mobile phone by operating the software programs and modules stored in the memory 1020. The memory 1020 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 1020 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
The input unit 1030 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the cellular phone. Specifically, the input unit 1030 may include a touch panel 1031 and other input devices 1032. The touch panel 1031, also referred to as a touch screen, may collect touch operations by a user (e.g., operations by a user on or near the touch panel 1031 using any suitable object or accessory such as a finger, a stylus, etc.) and drive corresponding connection devices according to a preset program. Alternatively, the touch panel 1031 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 1090, and receives and executes commands sent from the processor 1090. In addition, the touch panel 1031 may be implemented by various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. The input unit 1030 may include other input devices 1032 in addition to the touch panel 1031. In particular, other input devices 1032 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a track ball, a mouse, a joystick, or the like.
The display unit 1040 may be used to display information input by a user or information provided to the user and various menus of the cellular phone. The Display unit 1040 may include a Display panel 1041, and optionally, the Display panel 1041 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. Further, the touch panel 1031 may cover the display panel 1041, and when the touch panel 1031 detects a touch operation on or near the touch panel 1031, the touch panel is transmitted to the processor 1090 to determine the type of the touch event, and then the processor 1090 provides a corresponding visual output on the display panel 1041 according to the type of the touch event. Although in fig. 10, the touch panel 1031 and the display panel 1041 are two separate components to implement the input and output functions of the mobile phone, in some embodiments, the touch panel 1031 and the display panel 1041 may be integrated to implement the input and output functions of the mobile phone.
The handset may also include at least one sensor 1050, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 1041 according to the brightness of ambient light, and the proximity sensor may turn off the display panel 1041 and/or the backlight when the mobile phone moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.
Audio circuitry 1060, speaker 1061, microphone 1062 may provide an audio interface between the user and the handset. The audio circuit 1060 can transmit the electrical signal converted from the received audio data to the speaker 1061, and the electrical signal is converted into a sound signal by the speaker 1061 and output; on the other hand, the microphone 1062 converts the collected sound signals into electrical signals, which are received by the audio circuit 1060 and converted into audio data, which are then processed by the audio data output processor 1090, and then transmitted to, for example, another cellular phone via the RF circuit 1010, or output to the memory 1020 for further processing.
WiFi belongs to short-distance wireless transmission technology, and the mobile phone can help the user to send and receive e-mail, browse web pages, access streaming media, etc. through the WiFi module 1070, which provides wireless broadband internet access for the user. Although fig. 10 shows the WiFi module 1070, it is to be understood that it does not belong to the essential component of the handset.
The processor 1090 is a control center of the mobile phone, connects various parts of the whole mobile phone by using various interfaces and lines, and executes various functions of the mobile phone and processes data by operating or executing software programs and/or modules stored in the memory 1020 and calling data stored in the memory 1020, thereby performing overall monitoring of the mobile phone. Optionally, processor 1090 may include one or more processing units; preferably, the processor 1090 may integrate an application processor, which handles primarily the operating system, user interface, applications, etc., and a modem processor, which handles primarily wireless communications. It is to be appreciated that the modem processor described above may not be integrated into processor 1090.
The handset also includes a power source 1090 (e.g., a battery) for powering the various components, which may preferably be logically coupled to the processor 1090 through a power management system that may be used to manage charging, discharging, and power consumption.
Although not shown, the mobile phone may further include a camera, a bluetooth module, etc., which are not described herein.
In this embodiment, the processor 1090 included in the terminal device may perform the functions in the foregoing embodiments shown in fig. 2 or fig. 5, which is not described herein again.
Referring to fig. 11, an embodiment of the present application provides another communication device 1100, and specifically, the communication device 1100 may be a network device, where the communication device 1100 includes:
referring to fig. 11, a schematic structural diagram of a communication device according to the foregoing embodiments is provided in an embodiment of the present application, where the communication device may specifically be a network device in the foregoing embodiments, and a structure of the communication device may refer to the structure shown in fig. 11.
The communication device includes at least one processor 1111, at least one memory 1112, at least one transceiver 1113, at least one network interface 1114, and one or more antennas 1115. The processor 1111, the memory 1112, the transceiver 1113 and the network interface 1114 are connected by a bus, for example, and in this embodiment, the connection may include various interfaces, transmission lines or buses, which is not limited in this embodiment. The antenna 1115 is connected to the transceiver 1113. The network interface 1114 is used to enable the communication device to connect to other communication devices via a communication link, for example, the network interface 1114 may include a network interface between the communication device and a core network device, such as an S1 interface, and the network interface may include a network interface between the communication device and other network devices (e.g., other access network devices or core network devices), such as an X2 or Xn interface.
The processor 1111 is mainly used for processing communication protocols and communication data, controlling the whole communication device, executing software programs, and processing data of the software programs, for example, for supporting the communication device to perform the actions described in the embodiments. The communication device may include a baseband processor for processing communication protocols and communication data, and a central processing unit for controlling the entire terminal device, executing software programs, and processing data of the software programs. The processor 1111 in fig. 11 may integrate functions of a baseband processor and a central processing unit, and those skilled in the art will understand that the baseband processor and the central processing unit may also be independent processors, and are interconnected through a bus or the like. Those skilled in the art will appreciate that the terminal device may include a plurality of baseband processors to accommodate different network formats, the terminal device may include a plurality of central processors to enhance its processing capability, and various components of the terminal device may be connected by various buses. The baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit can also be expressed as a central processing circuit or a central processing chip. The function of processing the communication protocol and the communication data may be built in the processor, or may be stored in the memory in the form of a software program, and the processor executes the software program to realize the baseband processing function.
The memory is used primarily for storing software programs and data. The memory 1112 may be separate and coupled to the processor 1111. Alternatively, the memory 1112 may be integrated with the processor 1111, for example, within a single chip. The memory 1112 can store program codes for executing the technical solutions of the embodiments of the present application, and the processor 1111 controls the execution of the program codes, and various executed computer program codes can also be regarded as drivers of the processor 1111.
Fig. 11 shows only one memory and one processor. In an actual terminal device, there may be multiple processors and multiple memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be a memory element on the same chip as the processor, that is, an on-chip memory element, or a separate memory element, which is not limited in this embodiment.
The transceiver 1113 may be configured to support reception or transmission of radio frequency signals between the communication device and the terminal, and the transceiver 1113 may be coupled to the antenna 1115. The transceiver 1113 includes a transmitter Tx and a receiver Rx. Specifically, the one or more antennas 1115 may receive rf signals, and the receiver Rx of the transceiver 1113 is configured to receive the rf signals from the antennas, convert the rf signals into digital baseband signals or digital intermediate frequency signals, and provide the digital baseband signals or digital intermediate frequency signals to the processor 1111, so that the processor 1111 may further process the digital baseband signals or digital intermediate frequency signals, such as demodulation and decoding. In addition, the transmitter Tx in the transceiver 1113 is also configured to receive a modulated digital baseband signal or a digital intermediate frequency signal from the processor 1111, convert the modulated digital baseband signal or the digital intermediate frequency signal into a radio frequency signal, and transmit the radio frequency signal through the one or more antennas 1115. Specifically, the receiver Rx may selectively perform one or more stages of down-mixing and analog-to-digital conversion processes on the rf signal to obtain a digital baseband signal or a digital intermediate frequency signal, wherein the order of the down-mixing and analog-to-digital conversion processes is adjustable. The transmitter Tx may selectively perform one or more stages of up-mixing and digital-to-analog conversion processes on the modulated digital baseband signal or the modulated digital intermediate frequency signal to obtain the rf signal, where the order of the up-mixing and the digital-to-analog conversion processes is adjustable. The digital baseband signal and the digital intermediate frequency signal may be collectively referred to as a digital signal.
A transceiver may also be referred to as a transceiver unit, transceiver, transceiving means, etc. Optionally, a device for implementing a receiving function in the transceiver unit may be regarded as a receiving unit, and a device for implementing a sending function in the transceiver unit may be regarded as a sending unit, that is, the transceiver unit includes a receiving unit and a sending unit, the receiving unit may also be referred to as a receiver, an input port, a receiving circuit, and the like, and the sending unit may be referred to as a transmitter, a sending circuit, and the like.
It should be noted that the communication device shown in fig. 11 may be specifically configured to implement the steps implemented by the network device in the method embodiment corresponding to fig. 2 or fig. 5, and implement the technical effect corresponding to the network device, and the specific implementation manner of the communication device shown in fig. 11 may refer to the description in the method embodiment of fig. 2, and is not described herein again.
An embodiment of the present application further provides a computer-readable storage medium storing one or more computer-executable instructions, where the computer-executable instructions are executed by a processor, and the processor executes the method according to a possible implementation manner of the communication device in the foregoing embodiment, where the communication device may specifically be a terminal device in the foregoing embodiment, that is, a terminal device in the method embodiment corresponding to fig. 2.
The present application further provides a computer-readable storage medium storing one or more computer-executable instructions, where the computer-executable instructions are executed by a processor, and the processor executes the method according to the possible implementation manner of the communication device in the foregoing embodiments, where the communication device may specifically be a network device in the foregoing embodiments, that is, a network device in the method embodiment corresponding to fig. 2.
An embodiment of the present application further provides a computer program product (or called computer program) storing one or more computers, and when the computer program product is executed by the processor, the processor executes the method that may be implemented by the communication device, where the communication device may specifically be the terminal device in the foregoing embodiment, that is, the terminal device in the method embodiment corresponding to fig. 2.
The embodiment of the present application further provides a computer program product storing one or more computers, and when the computer program product is executed by the processor, the processor executes the method that may be implemented by the communication device, where the communication device may specifically be the network device in the foregoing embodiment, that is, the network device in the method embodiment corresponding to fig. 2.
An embodiment of the present application further provides a chip system, where the chip system includes a processor, and is configured to support a communication device to implement functions related to possible implementation manners of the communication device. In one possible design, the system-on-chip may further include a memory, which stores program instructions and data necessary for the communication device. The chip system may be formed by a chip, or may include a chip and other discrete devices, where the communication device may specifically be the terminal device in the foregoing embodiment, that is, the terminal device in the method embodiment corresponding to fig. 2.
An embodiment of the present application further provides a chip system, where the chip system includes a processor, and is configured to support a communication device to implement functions related to possible implementation manners of the communication device. In one possible design, the system-on-chip may further include a memory, the memory being used to hold program instructions and data necessary for the communication device. The chip system may be formed by a chip, or may include a chip and other discrete devices, where the communication device may specifically be a network device in the foregoing embodiment, that is, a network device in the method embodiment corresponding to fig. 2.
An embodiment of the present application further provides a network system architecture, where the network system architecture includes the communication device, and the communication device may specifically be the terminal device and the network device in the method embodiment corresponding to fig. 2.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Claims (29)

1. A data processing method, comprising:
the method comprises the steps that a terminal device receives first configuration information sent by a network device, wherein the first configuration information is used for configuring at least two first scheduling offset threshold candidates of a first bandwidth part BWP;
the terminal equipment receives first indication information sent by the network equipment, wherein the first indication information is used for indicating a first scheduling offset threshold which takes effect in the at least two first scheduling offset threshold candidates;
determining, by the terminal device, a second scheduling offset threshold in effect on a second BWP according to the first scheduling offset threshold in effect when a first condition is satisfied, the first condition being that the terminal device has been configured with the at least two first scheduling offset threshold candidates and is not configured with a second scheduling offset threshold candidate of the second BWP;
the first BWP is an uplink activated BWP, and the second BWP is a downlink activated BWP, or the first BWP is a downlink activated BWP and the second BWP is an uplink activated BWP.
2. The method of claim 1, wherein determining, by the terminal device, a second scheduling offset threshold in effect on a second BWP based on the first scheduling offset threshold in effect comprises:
the terminal device determines that the second effective scheduling offset threshold is equal to the first effective scheduling offset threshold.
3. The method according to claim 1 or 2, characterized in that the method further comprises:
the terminal equipment receives second configuration information sent by the network equipment, wherein the second configuration information comprises a plurality of first scheduling offsets and a plurality of second scheduling offsets;
wherein the scheduling offset for scheduling the first shared channel on the first BWP is one of the first scheduling offsets that is greater than or equal to the first scheduling offset threshold in effect;
the scheduling offset for scheduling a second shared channel on the second BWP is one of the plurality of second scheduling offsets greater than or equal to the second scheduling offset threshold in effect.
4. The method of claim 3,
the first scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the first BWP is an uplink activated BWP, the first scheduling offset is an uplink scheduling offset, and the first shared channel is a physical uplink shared channel PUSCH; the second scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the second BWP is a downlink activated BWP, the second scheduling offset is a downlink scheduling offset, and the second shared channel is a physical downlink shared channel PDSCH;
the scheduling offset for scheduling the first shared channel on the first BWP is:
scheduling a scheduling offset between the PDCCH of the PUSCH on the first BWP and the PUSCH to be one that is greater than or equal to the effective first scheduling offset threshold;
the scheduling offset for scheduling the second shared channel on the second BWP is:
scheduling a scheduling offset between the PDCCH of the PDSCH on the second BWP and the PDSCH to be one greater than or equal to the effective second scheduling offset threshold.
5. The method of claim 3,
the first scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the first BWP is a downlink activated BWP, the first scheduling offset is a downlink scheduling offset, and the first shared channel is a PDSCH; the second scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the second BWP is an uplink activated BWP, the second scheduling offset is an uplink scheduling offset, and the second shared channel is a PUSCH;
the scheduling offset for scheduling the first shared channel on the first BWP is:
scheduling a scheduling offset between the PDCCH of the PDSCH on the first BWP and the PDSCH to be one greater than or equal to the effective first scheduling offset threshold;
the scheduling offset for scheduling the second shared channel on the second BWP is:
scheduling a scheduling offset between the PDCCH of the PUSCH on the second BWP and the PUSCH to be one that is greater than or equal to the second effective scheduling offset threshold.
6. The method according to any of claims 1 to 5, wherein the first configuration information is further used for configuring the second scheduling offset threshold candidate for the second BWP;
the method further comprises the following steps:
and when a second condition is met and the received second indication information is used for indicating that the effective first scheduling offset threshold value is updated to a preset value, the terminal equipment updates the effective second scheduling offset threshold value to the preset value according to the second indication information, wherein the second condition is that the terminal equipment is configured with the first scheduling offset threshold value candidate and the second scheduling offset threshold value candidate.
7. A data processing method, comprising:
the method comprises the steps that a terminal device receives first configuration information sent by a network device, wherein the first configuration information is used for configuring at least two first scheduling offset threshold candidates of a first BWP;
the terminal device determines a preset value for the terminal device to process a first shared channel and/or a second shared channel when a first condition is satisfied, the first condition being that the terminal device is configured with the at least two first scheduling offset threshold candidates and is not configured with a second scheduling offset threshold candidate of the second BWP;
the first BWP is an uplink activated BWP, and the second BWP is a downlink activated BWP, or the first BWP is a downlink activated BWP and the second BWP is an uplink activated BWP.
8. The method of claim 7, further comprising:
the terminal device determines the effective second scheduling offset threshold on the second BWP as the preset value.
9. The method of claim 8, wherein the determining, by the end device, the effective second scheduling offset threshold on the second BWP to be the preset value comprises:
the terminal device determines that the effective second scheduling offset threshold on the second BWP and the effective first scheduling offset threshold on the first BWP are both equal to the preset value.
10. The method according to any one of claims 7 to 9, the preset value being zero.
11. The method according to any one of claims 7 to 10, further comprising:
the terminal equipment receives second configuration information sent by the network equipment, wherein the second configuration information comprises a plurality of first scheduling offsets and a plurality of second scheduling offsets;
wherein the scheduling offset for scheduling the first shared channel on the first BWP is one of the plurality of first scheduling offsets greater than or equal to the effective first scheduling offset threshold;
the scheduling offset for scheduling the second shared channel on the second BWP is one of the plurality of second scheduling offsets greater than or equal to the second scheduling offset threshold in effect.
12. The method according to any one of claims 7 to 11,
the first scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the first BWP is an uplink activated BWP, the first scheduling offset is an uplink scheduling offset, and the first shared channel is a physical uplink shared channel PUSCH; the second scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the second BWP is a downlink activated BWP, the second scheduling offset is a downlink scheduling offset, and the second shared channel is a physical downlink shared channel PDSCH.
13. The method according to any one of claims 7 to 11,
the first scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the first BWP is a downlink activated BWP, the first scheduling offset is a downlink scheduling offset, and the first shared channel is a PDSCH; the second scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the second BWP is an uplink activated BWP, the second scheduling offset is an uplink scheduling offset, and the second shared channel is a PUSCH.
14. A data processing method, comprising:
the method comprises the steps that a network device sends first configuration information to a terminal device, wherein the first configuration information is used for configuring at least two first scheduling offset threshold candidates of a first BWP;
when a first condition is met, the network device sends first indication information to the terminal device, where the first indication information is used to indicate a first scheduling offset threshold that takes effect among the at least two first scheduling offset threshold candidates, and is also used for the terminal device to determine that a second scheduling offset threshold that takes effect on a second BWP is not configured, where the second scheduling offset threshold that takes effect is determined according to the first scheduling offset threshold that takes effect, and the first condition is that the network device determines that the at least two first scheduling offset threshold candidates have been configured to the terminal device, and a second scheduling offset threshold candidate of a second BWP is not configured to the terminal device;
the first BWP is an uplink activated BWP, and the second BWP is a downlink activated BWP, or the first BWP is a downlink activated BWP and the second BWP is an uplink activated BWP.
15. The method of claim 14, further comprising:
the network device determines that the second effective scheduling offset threshold is equal to the first effective scheduling offset threshold.
16. The method according to claim 14 or 15, characterized in that the method further comprises:
the network equipment sends second configuration information to the terminal equipment, wherein the second configuration information comprises a plurality of first scheduling offsets and a plurality of second scheduling offsets;
the network equipment schedules a first shared channel of the terminal equipment by using any one of the first scheduling offsets which is greater than or equal to the effective first scheduling offset threshold;
and the network equipment schedules the second shared channel of the terminal equipment by using any one of the second scheduling offsets which is greater than or equal to the effective second scheduling offset threshold value.
17. The method according to any one of claims 14 to 16,
the first scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the first BWP is an uplink activated BWP, the first scheduling offset threshold is an uplink scheduling offset threshold, and the first shared channel is a physical uplink shared channel PUSCH;
the second scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the second BWP is a downlink activated BWP, the second scheduling offset threshold is an uplink scheduling offset threshold, and the second shared channel is a physical downlink shared channel PDSCH.
18. The method according to any one of claims 14 to 16,
the first scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the first BWP is a downlink activated BWP, the first scheduling offset is a downlink scheduling offset, and the first shared channel is a PDSCH;
the second scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the second BWP is an uplink activated BWP, the second scheduling offset is an uplink scheduling offset, and the second shared channel is a PUSCH.
19. The method according to any of claims 14 to 18, wherein the first configuration information is further used for configuring the second scheduling offset threshold candidate for the second BWP;
the method further comprises the following steps:
the network equipment sends second indication information to the terminal equipment;
when a second condition is met, the second indication information is used to indicate that the first effective scheduling offset threshold is updated to a preset value, and is also used for the terminal device to update the second effective scheduling offset threshold to the preset value according to the second indication information, where the second condition is that the network device has configured the first scheduling offset threshold candidate and the second scheduling offset threshold candidate to the terminal device.
20. A data processing method, comprising:
the method comprises the steps that a network device sends first configuration information to a terminal device, wherein the first configuration information is used for configuring at least two first scheduling offset threshold candidates of a first BWP;
when a first condition is met, the network device determines a preset value, wherein the preset value is used for scheduling the terminal device to process a first shared channel and/or a second shared channel, and the first condition is that the network device determines to configure the at least two first scheduling offset threshold candidates for the terminal device and does not configure a second scheduling offset threshold candidate for the second BWP for the terminal device;
the first BWP is an uplink activated BWP, and the second BWP is a downlink activated BWP, or the first BWP is a downlink activated BWP and the second BWP is an uplink activated BWP.
21. The method of claim 20, further comprising:
the network device determines the effective second scheduling offset threshold on the second BWP to be the preset value.
22. The method of claim 21, wherein the network device determining the effective second scheduling offset threshold on the second BWP to be the predetermined value comprises:
the network device determines that the second effective scheduling offset threshold on the second BWP and the first effective scheduling offset threshold on the first BWP are both equal to the preset value.
23. The method according to any one of claims 20 to 22, wherein the preset value is zero.
24. The method of any one of claims 20 to 23, further comprising:
the network equipment sends second configuration information to the terminal equipment, wherein the second configuration information comprises a plurality of first scheduling offsets and a plurality of second scheduling offsets;
the network equipment schedules the first shared channel of the terminal equipment by using any one of the first scheduling offsets which is greater than or equal to the effective first scheduling offset threshold value;
and the network equipment schedules the second shared channel of the terminal equipment by using any one of the second scheduling offsets which is greater than or equal to the effective second scheduling offset threshold value.
25. The method of any one of claims 20 to 24,
the first scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the first BWP is an uplink activated BWP, the first scheduling offset is an uplink scheduling offset, and the first shared channel is a PUSCH;
the second scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the second BWP is a downlink activated BWP, the second scheduling offset is a downlink scheduling offset, and the second shared channel is a PDSCH.
26. The method of any one of claims 20 to 24,
the first scheduling offset threshold candidate is a downlink scheduling offset threshold candidate, the first BWP is a downlink activated BWP, the first scheduling offset is a downlink scheduling offset, and the first shared channel is a PDSCH;
the second scheduling offset threshold candidate is an uplink scheduling offset threshold candidate, the second BWP is an uplink activated BWP, the second scheduling offset is an uplink scheduling offset, and the second shared channel is a PUSCH.
27. A communications device comprising a processor coupled to a memory for storing a computer program or instructions, the processor being configured to execute the computer program or instructions in the memory such that the method of any of claims 1 to 13 is performed.
28. A communications device comprising a processor coupled to a memory for storing a computer program or instructions, the processor being configured to execute the computer program or instructions in the memory such that the method of any of claims 14 to 26 is performed.
29. A computer storage medium storing a program or instructions for implementing the method of any one of claims 1 to 26.
CN202010414666.7A 2020-05-15 2020-05-15 Data processing method and related equipment Pending CN113677015A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202010414666.7A CN113677015A (en) 2020-05-15 2020-05-15 Data processing method and related equipment
PCT/CN2021/089828 WO2021227855A1 (en) 2020-05-15 2021-04-26 Data processing method and related device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010414666.7A CN113677015A (en) 2020-05-15 2020-05-15 Data processing method and related equipment

Publications (1)

Publication Number Publication Date
CN113677015A true CN113677015A (en) 2021-11-19

Family

ID=78526424

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010414666.7A Pending CN113677015A (en) 2020-05-15 2020-05-15 Data processing method and related equipment

Country Status (2)

Country Link
CN (1) CN113677015A (en)
WO (1) WO2021227855A1 (en)

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10993254B2 (en) * 2018-02-16 2021-04-27 Qualcomm Incorporated Downlink control information signaling schemes for bandwidth part switching
US11032001B2 (en) * 2018-04-05 2021-06-08 Qualcomm Incorporated Timing parameter management for bandwidth part switching
US11382118B2 (en) * 2018-09-28 2022-07-05 Qualcomm Incorporated Minimum scheduling delay signaling
CN110536444A (en) * 2019-04-30 2019-12-03 中兴通讯股份有限公司 Fractional bandwidth switching method, device, service node, user terminal and medium

Also Published As

Publication number Publication date
WO2021227855A1 (en) 2021-11-18

Similar Documents

Publication Publication Date Title
CN112398633B (en) Information reporting method, terminal and network equipment
CN110299978B (en) Information transmission method, terminal and network equipment
JP7073583B2 (en) CSI processing unit and resource processing method, equipment and system
CN109788559B (en) Bandwidth part BWP switching method of asymmetric spectrum, terminal and network equipment
CN110324890B (en) Control method of partial bandwidth activation timer and terminal
CN109788546B (en) Transmission method of timing advance information, network equipment and terminal
CN112448734A (en) Radio frequency module, terminal equipment and signal transmitting method
CN107634785B (en) WiFi system, router and mobile terminal
CN112867049B (en) Measurement configuration method, device and system
CN107734586B (en) Antenna switching method and mobile terminal
CN107612643B (en) Channel detection method and channel detection equipment
CN110868240A (en) Frequency hopping method, terminal and network equipment during PUSCH (physical uplink shared channel) repeated transmission
CN110831172A (en) Determination method, terminal and network equipment
WO2018201938A1 (en) Resource mapping method, network device and terminal device
EP3860285A1 (en) Method and device for resource scheduling
CN111800794B (en) Method and equipment for determining demodulation reference signal position
CN110875808B (en) System information transmission method, network equipment and terminal
CN110635878B (en) Command processing method and terminal equipment
CN110139390B (en) Resource scheduling indication method, terminal and network equipment
CN110192407B (en) Data transmission method and equipment
CN111885689A (en) Antenna control method and device and terminal equipment
CN107534958B (en) Signal transmission method, base station and user equipment
CN113677015A (en) Data processing method and related equipment
CN110740024B (en) CSI reporting method, terminal and network equipment
CN111132187B (en) Determination method, terminal equipment and network equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination