Communication method, and terminal, network device, system, storage medium and program product

By sending a PDCCH on the BWP to schedule transmissions on BWPs that are not configured with a PDCCH, the problem of resource waste in BWP resource management is solved, and more efficient resource utilization is achieved.

WO2026236937A1PCT designated stage Publication Date: 2026-11-19BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/094681
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-13
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

How to efficiently schedule uplink and downlink transmissions on the bandwidth portion (BWP) to save resources and reduce the burden on the communication system, especially in future communication systems such as 6G, is a key issue in resource management.

Method used

By scheduling uplink and downlink transmissions on the first BWP and/or the second BWP using the Physical Downlink Control Channel (PDCCH) transmitted on the first BWP, resource scheduling for BWPs without PDCCH configuration is achieved, reducing resource waste.

Benefits of technology

Effective scheduling of transmissions on BWPs without configured PDCCH saves resource consumption, reduces the burden on the communication system, and improves resource utilization efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025094681_19112026_PF_FP_ABST
    Figure CN2025094681_19112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a communication method, and a terminal, a network device, a system, a storage medium and a program product. The communication method comprises: a terminal receiving a first physical downlink control channel (PDCCH) sent by a network device on a first bandwidth part (BWP), wherein the first PDCCH is used for scheduling transmission on the first BWP and / or a second BWP, and the transmission on the first BWP and / or the second BWP comprises uplink transmission and / or downlink transmission. The present disclosure can reduce resource consumption and alleviate the burden on a communication system.
Need to check novelty before this filing date? Find Prior Art

Description

Communication methods, terminals, network devices, systems, storage media and software products Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to communication methods, terminals, network devices, systems, storage media, and program products. Background Technology

[0002] A Bandwidth Part (BWP) is a contiguous set of physical resource blocks (PRBs) on a given carrier. BWPs can be classified into several types, such as initial BWP, active BWP, and default BWP. Summary of the Invention

[0003] This disclosure provides communication methods, terminals, network devices, systems, storage media, and program products.

[0004] According to a first aspect of the present disclosure, a communication method is proposed, the method comprising: a terminal receiving a first physical downlink control channel (PDCCH) transmitted by a network device on a first bandwidth portion (BWP), the first PDCCH being used to schedule transmissions on the first BWP and / or a second BWP, the transmissions on the first BWP and / or the second BWP including uplink transmissions and / or downlink transmissions.

[0005] According to a second aspect of the present disclosure, a communication method is proposed, the method comprising: a network device transmitting a first physical downlink control channel (PDCCH) to a terminal on a first bandwidth portion (BWP), the first PDCCH being used to schedule transmissions on the first BWP and / or a second BWP, the transmissions on the first BWP and / or the second BWP including uplink transmissions and / or downlink transmissions.

[0006] According to a third aspect of the present disclosure, a terminal is provided, comprising: a transceiver module, configured to receive a first physical downlink control channel (PDCCH) transmitted by a network device on a first bandwidth portion (BWP), wherein the first PDCCH is used to schedule transmissions on the first BWP and / or a second BWP, and the transmissions on the first BWP and / or the second BWP include uplink transmissions and / or downlink transmissions.

[0007] According to a fourth aspect of the present disclosure, a network device is provided, comprising: a transceiver module configured to transmit a first physical downlink control channel (PDCCH) to a terminal on a first bandwidth portion (BWP), wherein the first PDCCH is configured to schedule transmissions on the first BWP and / or a second BWP, and the transmissions on the first BWP and / or the second BWP include uplink transmissions and / or downlink transmissions.

[0008] According to a fifth aspect of the present disclosure, a terminal is provided, comprising: one or more processors; wherein the terminal is configured to execute the first aspect and any one of the communication methods in the first aspect.

[0009] According to a sixth aspect of the present disclosure, a network device is provided, comprising: one or more processors; wherein the network device is configured to perform the second aspect and any one of the communication methods in the second aspect.

[0010] According to a seventh aspect of the present disclosure, a communication system is provided, including a terminal and a network device, wherein the terminal is configured to implement the first aspect and any one of the communication methods in the first aspect, and the network device is configured to implement the second aspect and any one of the communication methods in the second aspect.

[0011] According to an eighth aspect of the present disclosure, a storage medium is provided that stores instructions which, when executed on a communication device, cause the communication device to perform a communication method as described in the first aspect and any one thereof, or the second aspect and any one thereof.

[0012] According to a ninth aspect of the present disclosure, a program product is provided, comprising: a computer program, which, when executed by a communication device, causes the communication device to perform a communication method as described in the first aspect and any one of the first aspects or the second aspect and the second aspect.

[0013] In this disclosure, a first physical downlink control channel (PDCCH) is transmitted to the terminal on the first bandwidth portion (BWP). The first PDCCH is used to schedule transmissions on the first BWP and / or the second BWP, and the transmissions on the first BWP and / or the second BWP include uplink transmissions and / or downlink transmissions. That is, when there are uplink and / or downlink transmissions on the first BWP and / or the second BWP, they can be scheduled by the first PDCCH, thereby saving resource consumption and reducing the burden on the communication system. Attached Figure Description

[0014] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0015] Figure 1 is a schematic diagram of a communication system architecture according to an embodiment of the present disclosure.

[0016] Figure 2 is a schematic diagram of a communication method interaction according to an embodiment of the present disclosure.

[0017] Figure 3 is a flowchart illustrating a communication method according to an embodiment of the present disclosure.

[0018] Figure 4 is a flowchart illustrating a communication method according to an embodiment of the present disclosure.

[0019] Figure 5a is a schematic diagram of the structure of the terminal proposed in an embodiment of this disclosure.

[0020] Figure 5b is a schematic diagram of the structure of the network device proposed in an embodiment of this disclosure.

[0021] Figure 6a is a schematic diagram of the structure of a communication device proposed in an embodiment of this disclosure.

[0022] Figure 6b is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation

[0023] This disclosure provides communication methods, terminals, network devices, systems, storage media, and program products.

[0024] In a first aspect, embodiments of this disclosure provide a communication method, the method comprising: a terminal receiving a first physical downlink control channel (PDCCH) transmitted by a network device on a first bandwidth portion (BWP), the first PDCCH being used to schedule transmissions on the first BWP and / or a second BWP, the transmissions on the first BWP and / or the second BWP including uplink transmissions and / or downlink transmissions.

[0025] In some alternative embodiments of the first aspect, the second BWP is not configured with a PDCCH.

[0026] In some alternative embodiments of the first aspect, the method further includes: the terminal receiving a first parameter sent by the network device; the terminal determining, based on the first parameter, that the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP; the first parameter being used to determine whether the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP.

[0027] In some alternative embodiments of the first aspect, the first parameter indicates whether the first PDCCH carries a Bandwidth Partial Identifier (BIF); or, the first parameter indicates whether the first PDCCH carries both a BIF and a Cell Identifier (CIF); or, the first parameter indicates whether the first PDCCH is used to schedule uplink and / or downlink transmissions on a second BWP.

[0028] In some alternative embodiments of the first aspect, the first parameter indicates that the first PDCCH carries a BIF, the BIF carried by the first PDCCH being a first value, the first value being used to indicate that the first PDCCH schedules uplink and / or downlink transmissions on the first BWP.

[0029] In some alternative embodiments of the first aspect, the method further includes: the terminal receiving a second parameter sent by the network device, the second parameter being used to determine the first BWP.

[0030] In some alternative embodiments of the first aspect, the second parameter indicates the BIF corresponding to the first BWP, or the second parameter indicates both the BIF and CIF corresponding to the first BWP.

[0031] In some alternative embodiments of the first aspect, the method further includes: the terminal receiving a third parameter sent by the network device, the third parameter being used to determine the second BWP.

[0032] In some alternative embodiments of the first aspect, the third parameter indicates the BIF corresponding to the second BWP, the BIF being carried in the first PDCCH; or, the third parameter indicates the BIF and CIF corresponding to the second BWP, the BIF and CIF being carried in the first PDCCH.

[0033] In some alternative embodiments of the first aspect, the terminal supports a first capability, which is to support uplink and / or downlink transmissions scheduled on a second BWP via the first PDCCH.

[0034] In some alternative embodiments of the first aspect, the method further includes: the terminal reporting the first capability, wherein the first capability is to support uplink and / or downlink transmissions scheduled on the second BWP via the first PDCCH.

[0035] In some alternative embodiments of the first aspect, the first capability is terminal-level.

[0036] In some alternative embodiments of the first aspect, the terminal supports the first capability in both the time division duplex (TDD) band and the frequency division duplex (FDD) band.

[0037] In some alternative embodiments of the first aspect, the terminal supports the first capability across different frequency ranges.

[0038] In a second aspect, a communication method is provided, the method comprising: a network device transmitting a first physical downlink control channel (PDCCH) to a terminal on a first bandwidth portion (BWP), the first PDCCH being used to schedule transmissions on the first BWP and / or a second BWP, the transmissions on the first BWP and / or the second BWP including uplink transmissions and / or downlink transmissions.

[0039] In some alternative embodiments of the second aspect, the second BWP is not configured with a PDCCH.

[0040] In some alternative embodiments of the second aspect, the method further includes: the network device sending a first parameter to the terminal, for the terminal to determine, based on the first parameter, that the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP; the first parameter is used to determine whether the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP.

[0041] In some alternative embodiments of the second aspect, the first parameter indicates whether the first PDCCH carries a Bandwidth Partial Identifier (BIF); or, the first parameter indicates whether the first PDCCH carries both a BIF and a Cell Identifier (CIF); or, the first parameter indicates whether the first PDCCH is used to schedule uplink and / or downlink transmissions on a second BWP.

[0042] In some alternative embodiments of the second aspect, the first parameter indicates that the first PDCCH carries a BIF, the BIF carried by the first PDCCH is a first value, and the first value is used to indicate that the first PDCCH schedules uplink and / or downlink transmissions on the first BWP.

[0043] In some alternative embodiments of the second aspect, the method further includes: the network device sending a second parameter to the terminal, the second parameter being used to determine the first BWP.

[0044] In some alternative embodiments of the second aspect, the second parameter indicates the BIF corresponding to the first BWP, or the second parameter indicates both the BIF and CIF corresponding to the first BWP.

[0045] In some alternative embodiments of the second aspect, the method further includes: the network device sending a third parameter to the terminal, the third parameter being used to determine the second BWP.

[0046] In some alternative embodiments of the second aspect, the third parameter indicates the BIF corresponding to the second BWP, the BIF being carried in the first PDCCH; or, the third parameter indicates the BIF and CIF corresponding to the second BWP, the BIF and CIF being carried in the first PDCCH.

[0047] In some alternative embodiments of the second aspect, the terminal supports a first capability, which is to support uplink and / or downlink transmissions scheduled on the second BWP via the first PDCCH.

[0048] In some alternative embodiments of the second aspect, the method further includes: the network device receiving the first capability reported by the terminal, the first capability being to support scheduling uplink and / or downlink transmissions on a second BWP via a PDCCH on the first BWP.

[0049] In some alternative embodiments of the second aspect, the first capability is terminal-level.

[0050] In some alternative embodiments of the second aspect, the terminal supports the first capability in both the time division duplex (TDD) band and the frequency division duplex (FDD) band.

[0051] In some alternative embodiments of the second aspect, the terminal supports the first capability across different frequency ranges.

[0052] Thirdly, a terminal is provided, comprising: a transceiver module, configured to receive a first physical downlink control channel (PDCCH) transmitted by a network device on a first bandwidth portion (BWP), wherein the first PDCCH is used to schedule transmissions on the first BWP and / or a second BWP, and the transmissions on the first BWP and / or the second BWP include uplink transmissions and / or downlink transmissions.

[0053] Fourthly, a network device is provided, comprising: a transceiver module for transmitting a first physical downlink control channel (PDCCH) to a terminal on a first bandwidth portion (BWP), wherein the first PDCCH is used to schedule transmissions on the first BWP and / or a second BWP, and the transmissions on the first BWP and / or the second BWP include uplink transmissions and / or downlink transmissions.

[0054] Fifthly, a terminal is provided, comprising: one or more processors; wherein the terminal is configured to execute the first aspect and any one of the communication methods in the first aspect.

[0055] A sixth aspect provides a network device, comprising: one or more processors; wherein the network device is configured to perform the second aspect and any one of the communication methods described in the second aspect.

[0056] A seventh aspect provides a communication system, including a terminal and a network device, wherein the terminal is configured to implement the first aspect and any one of the communication methods in the first aspect, and the network device is configured to implement the second aspect and any one of the communication methods in the second aspect.

[0057] Eighthly, a storage medium is provided that stores instructions, which, when executed on a communication device, cause the communication device to perform a communication method as described in the first aspect and any one thereof, or the second aspect and any one thereof.

[0058] Ninth aspect, a program product is provided, comprising: a computer program, which, when executed by a communication device, causes the communication device to perform a communication method as described in the first aspect and any one of the first aspects or the second aspect and the second aspect.

[0059] In a tenth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in an optional implementation of the first or second aspect.

[0060] Eleventhly, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described in the optional implementations of the first or second aspect above.

[0061] It is understood that the terminals, access network devices, first network elements, other network elements, core network devices, communication systems, storage media, program products, computer programs, chips, or chip systems involved in the embodiments of this disclosure are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0062] This disclosure provides communication methods, terminals, network devices, systems, storage media, and program products. In some embodiments, the terms "communication method" and "information processing method" can be used interchangeably, as can the terms "communication device" and "information processing device" and "communication device," and the terms "information processing system" and "communication system."

[0063] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0064] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. The technical environments of different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0065] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0066] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0067] In the embodiments of this disclosure, "multiple" refers to two or more.

[0068] In some embodiments, the terms “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0069] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0070] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0071] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0072] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0073] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0074] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0075] In some embodiments, the apparatus and device may be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they may also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "body", etc.

[0076] In some embodiments, "network" can be interpreted as devices included in the network, such as access network devices, core network devices, etc.

[0077] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)," "base station (BS)," "radio base station," or "fixed station." In some embodiments, it may also be understood as "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," or "bandwidth part (BWP)."

[0078] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)," "user terminal," "mobile station (MS)," "mobile terminal (MT)," "subscriber station," "mobile unit," "subscriber unit," "wireless unit," "remote unit," "mobile device," "wireless device," "wireless communication device," "remote device," "mobile subscriber station," "access terminal," "mobile terminal," "wireless terminal," "remote terminal," "handset," "user agent," "mobile client," "client," etc.

[0079] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0080] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0081] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0082] In 5G NR, cell bandwidth is expected to be larger than in LTE, but the UE's receive and transmit bandwidth does not necessarily need to be the same as the cell bandwidth. The UE's receive and transmit bandwidth can be adjusted to a subset of the total cell bandwidth (BWP). This bandwidth can be reduced during periods of low activity to save power; the bandwidth location can be changed to support different services. Bandwidth adaptation is achieved by configuring BWP(s), which tells the terminal which BWP is currently active.

[0083] A BWP is a set of consecutive physical resource blocks (PRBs) on a given carrier. These PRBs are selected from consecutive subsets of common resource blocks of a given set of parameters (u), where u defining the BWP can have three different parameters: subcarrier spacing (SCS); symbol length; and cyclic prefix (CP) length.

[0084] BWPs can be divided into several types, such as initial BWP, activated BWP, and default BWP.

[0085] Initial BWP: The initial BWP is used to execute the initial access procedure. It includes the requested Remaining Minimum System Information (RMSI), Control Resource Set (CORESET), and parameters such as RMSI frequency location, bandwidth, and SCS. It can set 24 to 96 different resource blocks (RBs), and can be relaxed to a wider BWP after RMSI decoding.

[0086] Activate BWP (UE-Specific): An activated BWP is defined as a UE-specific BWP and can also be used to perform the initial access procedure. This is the first BWP the UE uses to begin data transmission after RRC configuration / reconfiguration. The first activated BWP should be different from the default BWP;

[0087] Default BWP (UE-specific): The default BWP is also a UE-specific BWP and is configured during RRC reconfiguration. If it is not configured, the initial BWP can be assumed to be the default BWP. When the BWP timer expires, each UE will switch back to the default BWP.

[0088] For each serving cell, the network can configure at least one initial BWP, including a downlink bandwidth portion and one (if the serving cell is configured with an uplink) or two (if a supplementary uplink (SUL) is used) uplink bandwidth portions. Additionally, the network can configure extra uplink and downlink BWPs.

[0089] BWP configuration is divided into uplink and downlink parameters, as well as general and dedicated parameters. Common parameters (in BWP-UplinkCommon and BWP-DownlinkCommon) are cell-specific, and the network ensures necessary alignment with parameters corresponding to other UEs. The initial BWP common parameters for the Primary Cell (PCell) are also provided through system information. For all other serving cells, the network provides common parameters through dedicated signaling.

[0090] The UE can be configured with up to 4 BWPs for downlink and uplink, but at any given time, only one BWP can be activated for downlink and one for uplink.

[0091] The concept of BWP allows the terminal to operate with narrow bandwidth, and when the user needs more data (burst traffic), it can notify the gNB to enable wider bandwidth.

[0092] When a gNB is configured with a BWP, it includes the following parameters: BWP parameter set (u), BWP bandwidth size and frequency location (NR Absolute Radio Frequency Channel Number, NR-ARFCN) and CORESET.

[0093] For the downlink, the UE will not receive the Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Channel State Information-Reference Signal (CSI-RS), or Tracking Reference Signal (TRS) located outside the active BWP.

[0094] Each downlink (DL) BWP includes at least one CORESET with a UE-specific Search Space (USS), while at least one configured DL BWP for the primary carrier includes a CORESET with a Common Search Space (CSS).

[0095] For the uplink, the UE will not transmit the Physical Uplink Shared Channel (PUSCH) or Physical Uplink Control Channel (PUCCH) outside of the active BWP.

[0096] Normally, a UE can only receive and transmit within the frequency range of its active BWP. However, there are exceptions. A UE can perform Radio Resource Management (RRM) measurements or transmit Sound Reference Signals (SRS) outside of its active BWP during measurement intervals.

[0097] However, as traffic volume increases, BWP may consume more and more resources. How to conserve resources and reduce the burden on the communication system is a technical problem that needs to be solved. For example, future 6G will need to consider this issue, but it is not limited to 6G.

[0098] Therefore, this disclosure provides a communication method in which a terminal receives a first PDCCH sent by a network device. The first PDCCH is used to schedule transmissions on the first BWP and / or the second BWP, and the transmissions on the first BWP and / or the second BWP include uplink transmissions and / or downlink transmissions. In other words, when there are uplink and / or downlink transmissions on the first BWP and / or the second BWP, they can be scheduled by the first PDCCH, thereby saving resource consumption and reducing the burden on the communication system.

[0099] Figure 1 is a schematic diagram of a communication system architecture according to an embodiment of the present disclosure.

[0100] As shown in Figure 1, the communication system 100 includes a terminal 101 and a network device 102.

[0101] In some embodiments, terminal 101 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0102] In some embodiments, network device 102 may include at least one of access network device and core network device.

[0103] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system.

[0104] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0105] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0106] In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of the aforementioned one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC).

[0107] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0108] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0109] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0110] Figure 2 is a schematic diagram of a communication method interaction according to an embodiment of the present disclosure. As shown in Figure 2, this embodiment of the present disclosure relates to a communication method for a communication system 100, the method including:

[0111] In step S2101a, network device 102 sends the first parameter to terminal 101.

[0112] In some embodiments, terminal 101 receives a first parameter sent by network device 102, and determines a first PDCCH for scheduling uplink and / or downlink transmissions on a second BWP based on the first parameter.

[0113] In some embodiments, the second BWP is any one or more BWPs other than the first BWP. That is, the first parameter indicates whether the "first PDCCH" can schedule "uplink and / or downlink transmissions on other BWPs besides the first BWP". This can be understood as the first parameter indicating whether the first PDCCH has the capability to schedule uplink and / or downlink transmissions on other BWPs. The specific BWP(s) on which the first PDCCH is used to schedule uplink and / or downlink transmissions, i.e., which BWP(s) the second BWP(s), can be determined by the "Bandwidth Part Identifier (BIF)" or "BIF and Cell Identifier (CIF)" or "second and third parameters" carried by the first PDCCH, as detailed in the following embodiments.

[0114] In some embodiments, the first parameter may be included in the configuration information corresponding to the first BWP and sent to the terminal, but it is not limited thereto.

[0115] In some embodiments, the PDCCH is not configured on the second BWP.

[0116] For example, the second BWP can be any one or more BWPs other than the first BWP that are not configured with a PDCCH. That is, the first parameter indicates whether the "first PDCCH" can schedule "uplink and / or downlink transmissions on BWPs other than the first BWP that are not configured with a PDCCH".

[0117] Optionally, network devices can configure PDCCH at the BWP granularity. That is, some BWPs can be configured with PDCCH, while others can be left unconfigured. For uplink and / or downlink transmissions on BWPs without PDCCH configuration, PDCCH scheduling can be achieved using the PDCCH on configured BWPs, thereby saving resources. In the disclosed embodiments, the first BWP can be a BWP with PDCCH configuration, and the second BWP can be a BWP without PDCCH configuration.

[0118] It is understandable that there can be multiple first BWPs and multiple second BWPs. That is, multiple BWPs can be configured with PDCCH, and multiple BWPs can be without PDCCH. If there are multiple first and second BWPs, there can be a corresponding relationship between them. The second BWP corresponding to the first BWP, or the first BWP corresponding to the second BWP, can be determined through network device configuration or dynamic indication. For specific solutions, please refer to steps S2102 and S2103.

[0119] In some embodiments, the first parameter is used to determine whether the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP. It is understood that, for a terminal, the PDCCH on some BWPs may be used to schedule uplink and / or downlink transmissions on other BWPs, while the PDCCH on some BWPs may only be used to schedule uplink and / or downlink transmissions on that specific BWP. Therefore, the network device can send the first parameter to enable the terminal to determine whether the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP.

[0120] In some embodiments, a BWP can be understood as a time-frequency domain resource. For example, a first BWP can be a first time-frequency domain resource, and a second BWP can be a second time-frequency domain resource. The time-frequency domain resource includes time-domain resources and frequency-domain resources. Time-domain resources include, for example, time slots and symbols, while frequency-domain resources include, for example, frequency bands, frequencies, and subcarriers.

[0121] It should be noted that the BWP in this disclosure can be replaced with a carrier. For example, the first BWP can be replaced with the first carrier, and the second BWP can be replaced with the second carrier. When the BWP is replaced with a carrier, a cell can support multiple carriers.

[0122] In step S2101b, terminal 101 determines, based on the first parameter, that the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP.

[0123] In some embodiments, the terminal can determine the first PDCCH for scheduling uplink and / or downlink transmissions on the second BWP based on the first parameter, thereby determining the resources and parameters corresponding to the uplink and / or downlink transmissions on the second BWP by listening to the first PDCCH.

[0124] Optionally, the first parameter indicates whether the first PDCCH carries a BIF.

[0125] For example, if the first PDCCH carries a BIF, it indicates that the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP. Therefore, the first parameter can indicate whether the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP by indicating whether the first PDCCH carries a BIF. The second BWP is one or more BWPs without a configured PDCCH.

[0126] For example, the first parameter is a second value, used to indicate that the first PDCCH carries a BIF. If the first parameter is a second value, the terminal can determine that the first PDCCH carries a BIF, and thus can determine that the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP.

[0127] For example, the first parameter is a third value, used to indicate that the first PDCCH does not carry a BIF. If the first parameter is a third value, the terminal can determine that the first PDCCH does not carry a BIF, and thus can determine that the first PDCCH is not used to schedule uplink and / or downlink transmissions on the second BWP.

[0128] For example, the second value can be 1 or true, and the third value can be 0 or false, but this disclosure is not limited thereto.

[0129] For example, a first parameter is configured to instruct the first PDCCH to carry a BIF. For example, the first parameter is not configured to instruct the first PDCCH to carry a BIF.

[0130] Optionally, if the BWPs are uniformly numbered across cells, the first parameter can indicate whether the first PDCCH carries a BIF. "Uniformly numbered across cells" can be understood as grouping the BWPs from different cells together and numbering them sequentially, meaning each cell's BWP has a different number. In other words, the BIFs corresponding to the BWPs of different cells are different. For example, the BWPs of cell #1 are numbered #1, #2, and #3, meaning the BIFs corresponding to the BWPs of cell #1 are #1, #2, and #3. The BWPs of cell #2 are numbered #4, #5, and #6, meaning the BIFs corresponding to the BWPs of cell #2 are #4, #5, and #6. In this case, the first PDCCH can carry the BIF, and even without carrying the cell identifier, the BWP corresponding to the BIF can be uniquely identified. Accordingly, the first parameter can also indicate whether the first PDCCH carries a BIF. The terminal can determine whether the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP based on whether the first PDCCH carries a BIF according to the first parameter, or it can determine the second BWP based on the BIF carried on the first PDCCH.

[0131] Optionally, the first parameter indicates whether the first PDCCH carries the BIF and cell indicator (CIF).

[0132] For example, if the first PDCCH carries BIF and CIF, it indicates that the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP. Therefore, the first parameter can indicate whether the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP by indicating whether the first PDCCH carries BIF and CIF. The second BWP is one or more BWPs without a configured PDCCH.

[0133] In other words, the first parameter indicates whether the first PDCCH carries BIF and CIF, enabling the terminal to determine whether the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP. For example, if the first PDCCH carries BIF and CIF, the terminal can determine that the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP. If the first PDCCH does not carry BIF and CIF, the terminal can determine that the first PDCCH is not used to schedule uplink and / or downlink transmissions on the second BWP.

[0134] For example, the first parameter is a second value, used to indicate that the first PDCCH carries BIF and CIF. If the first parameter is a second value, the terminal can determine that the first PDCCH carries BIF and CIF, and thus can determine that the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP.

[0135] For example, the first parameter is a third value, used to indicate that the first PDCCH does not carry BIF and CIF. If the first parameter is a third value, the terminal can determine that the first PDCCH does not carry BIF and CIF, and thus can determine that the first PDCCH is not used to schedule uplink and / or downlink transmissions on the second BWP.

[0136] For example, the second value can be 1 or true, and the third value can be 0 or false, but this disclosure is not limited thereto.

[0137] For example, a first parameter is configured to indicate that the first PDCCH carries both BIF and CIF. For example, the first parameter is not configured to indicate that the first PDCCH carries both BIF and CIF.

[0138] Optionally, CIF can be a serving cell index, but is not limited to this.

[0139] Optionally, if the BWPs are not uniformly numbered across cells, the first parameter can indicate whether the first PDCCH carries the BIF and CIF. "BWPs are not uniformly numbered across cells" can be understood as each cell's BWP being numbered individually and sequentially, and different cells may have the same BWP number. That is, different cells may have the same BIF corresponding to their BWPs. For example, the BWPs of cell #1 are numbered #1, #2, and #3, meaning the BIFs corresponding to cell #1 are #1, #2, and #3. Similarly, the BWPs of cell #2 are numbered #1, #2, and #3, meaning the BIFs corresponding to cell #2 are #1, #2, and #3. In this case, the first PDCCH can carry the BIF and CIF. The cell is identified by the CIF, and the BWP corresponding to that cell is identified by the BIF, thus uniquely identifying the BWP. For example, if the CIF is #1 and the BIF is #1, it indicates BWP #1 for cell #1; if the CIF is #2 and the BIF is #1, it refers to BWP #1 for cell #2. The terminal can determine whether the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP based on whether the first PDCCH carries BIF and CIF according to the first parameter, or it can determine the second BWP based on the BIF and CIF carried on the first PDCCH.

[0140] Optionally, the first parameter indicates whether the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP. That is, the first parameter can explicitly indicate whether the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP.

[0141] For example, the first parameter is a second value, used to indicate that the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP. If the first parameter is a second value, the terminal can use the first PDCCH to schedule uplink and / or downlink transmissions on the second BWP.

[0142] For example, the first parameter is a third value, used to indicate that the first PDCCH is not used for scheduling uplink and / or downlink transmissions on the second BWP. If the first parameter is a third value, the terminal can determine that the first PDCCH is not used for scheduling uplink and / or downlink transmissions on the second BWP.

[0143] For example, the second value can be 1 or true, and the third value can be 0 or false, but this disclosure is not limited thereto.

[0144] In some embodiments, the first parameter indicates that the first PDCCH carries a BIF, the BIF carried by the first PDCCH is a first value, and the first PDCCH carrying the BIF with the first value is used to schedule uplink and / or downlink transmissions on the first BWP.

[0145] Wherein, the first parameter indicates that the first PDCCH carries a BIF, so the terminal can determine, based on the first parameter, that the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP. That is, if it is determined that the first PDCCH can be used to schedule uplink and / or downlink transmissions on the second BWP, and if the BIF carried by the first PDCCH is a first value, the first PDCCH carrying the first value of the BIF is used to schedule uplink and / or downlink transmissions on the first BWP.

[0146] For example, the first value can be 0. When the first parameter indicates that the first PDCCH carries a BIF, the BIF is set to 0 when the first PDCCH is used to schedule the uplink / downlink transmission of the first BWP.

[0147] For example, the first value can be 1. When the first parameter indicates that the first PDCCH carries a BIF, the BIF is set to 1 when the first PDCCH is used to schedule the uplink / downlink transmission of the first BWP.

[0148] In some embodiments, if the first parameter indicates that the first PDCCH carries a BIF, the first PDCCH may carry one or more BIFs.

[0149] For example, a BIF carried can be the BIF of the first BWP or a BIF set to a first value, used to indicate that the first PDCCH carrying the first value is scheduling uplink and / or downlink transmissions on the first BWP. It is understood that, where the first PDCCH can be used to schedule uplink and / or downlink transmissions on the second BWP, in a given communication, the first PDCCH may also schedule only uplink and / or downlink transmissions on the first BWP.

[0150] For example, a BIF carried could be the BIF of a second BWP, used to indicate that the first PDCCH is scheduling uplink and / or downlink transmissions on the second BWP.

[0151] For example, the multiple BIFs carried may include the BIFs of a first BWP and a second BWP. The number of second BWPs can be one or more. That is, the multiple BIFs may include a BIF corresponding to a first BWP (e.g., 0) and one or more BIFs corresponding to each of the second BWPs (e.g., determined by a third parameter, see the following embodiments for details).

[0152] For example, the multiple BIFs carried are the BIFs corresponding to the multiple second BWPs.

[0153] In some embodiments, if the first parameter indicates that the first PDCCH carries BIF and CIF, the first PDCCH may carry one or more BIF and CIF.

[0154] For example, carry a CIF and a BIF to indicate the first BWP or the second BWP.

[0155] For example, it carries one CIF and multiple BIFs to indicate a first BWP and a second BWP, where the first BWP and the second BWP are different BWPs in the same cell. Or it can be used to indicate multiple second BWPs, where the multiple second BWPs are different BWPs in the same cell.

[0156] For example, it can carry multiple CIFs and one BIF to indicate a first BWP and a second BWP, where the first BWP and the second BWP are BWPs from different cells but have the same number. Or it can be used to indicate multiple second BWPs, where the multiple second BWPs are BWPs from different cells but have the same number.

[0157] For example, multiple CIFs and multiple BIFs can be carried to indicate a first BWP and a second BWP, where the first BWP and the second BWP are BWPs from different cells and have different numbers. Alternatively, they can be used to indicate multiple second BWPs, where the multiple second BWPs are BWPs from different cells and have different numbers, or some of the second BWPs may be BWPs from the same cell but with different numbers, or BWPs from different cells but with the same or different numbers.

[0158] In some embodiments, the uplink transmission may be a PUSCH, but is not limited thereto.

[0159] In some embodiments, the downlink transmission may be PDSCH, but is not limited to this.

[0160] In some embodiments, the name of the first parameter is not limited to this, and it may be, for example, "first information", "indication information", etc.

[0161] In step S2102, network device 102 sends the second parameter to terminal 101.

[0162] In some embodiments, terminal 101 receives a second parameter sent by network device 102.

[0163] In some embodiments, the second parameter is used to determine the first BWP. A second BWP may correspond to one or more second parameters to indicate the first BWP corresponding to the second BWP. The first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP. For example, no PDCCH is configured on the second BWP.

[0164] In some embodiments, the second parameter may be included in the configuration information corresponding to the second BWP and sent to the terminal, but it is not limited thereto.

[0165] Optionally, the second parameter indicates the BIF corresponding to the first BWP.

[0166] For example, the number of second parameters corresponding to the same second BWP can be one, and the first BWP corresponding to the second BWP is determined by the second parameter.

[0167] For example, if BWPs are uniformly numbered across cells, let's assume the second BWPs are BWP#1 and BWP#2. BWP#1 can correspond to one second parameter, and BWP#2 can correspond to another second parameter. Assume the second parameter corresponding to BWP#1 indicates that the BIF corresponding to the first BWP is #3, and the second parameter corresponding to BWP#2 indicates that the BIF corresponding to the first BWP is #4. Then BWP#1 corresponds to BWP#3, and BWP#2 corresponds to BWP#4. That is, the PDCCH on BWP#3 is used to schedule uplink transmissions and / or downlink transmissions on BWP#1. The PDCCH on BWP#4 is used to schedule uplink transmissions and / or downlink transmissions on BWP#2.

[0168] For example, the number of second parameters corresponding to the same second BWP can be multiple, and multiple first BWPs corresponding to the second BWP can be determined by multiple second parameters.

[0169] For example, if BWPs are uniformly numbered across cells, let's assume the second BWP is BWP#1. BWP#1 corresponds to two second parameters: one indicating that the BIF corresponding to the first BWP is #2, and the other indicating that the BIF corresponding to the other first BWP is #3. That is, based on the second parameters, two first BWPs, namely BWP#2 and BWP#3, can be identified. The PDCCH on both BWP#2 and BWP#3 can be used to schedule uplink and / or downlink transmissions on BWP#1. Optionally, the second parameters indicate the BIF and CIF corresponding to the first BWP.

[0170] For example, the number of second parameters corresponding to the same second BWP can be one, and the first BWP corresponding to the second BWP is determined by the second parameter.

[0171] For example, if BWPs are not uniformly numbered across cells, let's assume the second BWPs are BWP#1 and BWP#2 for cell #1. BWP#1 for cell #1 can correspond to one second parameter, and BWP#2 for cell #1 can correspond to another second parameter. Assuming the second parameter corresponding to BWP#1 for cell #1 indicates that the BIF for the first BWP is #3 and the CIF is #1, and the second parameter corresponding to BWP#2 for cell #1 indicates that the BIF for the first BWP is #2 and the CIF is #2, then BWP#1 for cell #1 corresponds to BWP#3 for cell #1, and BWP#2 for cell #1 corresponds to BWP#2 for cell #2.

[0172] In other words, the first BWP and the second BWP can be different BWPs within the same cell, such as BWP#1 and BWP#3 for cell #1. The first BWP and the second BWP can also be BWPs with the same ID from different cells, such as BWP#2 for cell #1 and BWP#2 for cell #2. Of course, the first BWP and the second BWP can also be BWPs from different cells with different IDs; this disclosure will not provide examples of all such cases.

[0173] For example, the number of second parameters corresponding to the same second BWP can be multiple, and multiple first BWPs corresponding to the second BWP can be determined by multiple second parameters.

[0174] For example, if the BWPs are not uniformly numbered between cells, for example, assume that the second BWP is BWP#1 of cell #1. BWP#1 of cell #1 corresponds to two second parameters. One second parameter indicates that the BIF of the first BWP is #2 and the CIF is #1. The other second parameter indicates that the BIF of the first BWP is #1 and the CIF is #2. That is to say, based on the second parameters, two first BWPs can be determined, namely BWP#2 of cell #1 and BWP#1 of cell #2. The PDCCH on BWP#2 of cell #1 and BWP#1 of cell #2 can be used to schedule uplink and / or downlink transmissions on BWP#1 of cell #1.

[0175] In some embodiments, the name of the second parameter is not limited, and it may be, for example, "second information", "indication information", etc.

[0176] In step S2103, network device 102 sends a third parameter to terminal 101.

[0177] In some embodiments, terminal 101 receives a third parameter sent by network device 102.

[0178] In some embodiments, the third parameter is used to determine the second BWP.

[0179] In some embodiments, the third parameter may be included in the configuration information of the second BWP and sent to the terminal.

[0180] Optionally, the third parameter indicates the BIF corresponding to the PDCCH sent by the second BWP on the first BWP.

[0181] For example, the number of third parameters corresponding to the same second BWP can be one, and the BIF corresponding to the PDCCH sent by the second BWP on the first BWP is determined by the third parameter.

[0182] For example, the second parameter indicates that uplink and / or downlink transmissions on the second BWP are scheduled via the first PDCCH. The third parameter indicates the BIF corresponding to the PDCCH transmitted by the second BWP on the first BWP.

[0183] For example, if BWPs are uniformly numbered across cells, let's assume the second BWP is BWP#1. The second parameter corresponding to BWP#1 indicates that the BIF corresponding to the first BWP is #3, and the third parameter corresponding to BWP#1 indicates that the BIF value corresponding to the PDCCH sent by BWP#1 on the first BWP (BWP#3) is #1. That is, if the terminal device receives the PDCCH on BWP#3 and the BIF value carried in the PDCCH is #1, then the terminal device determines that the PDCCH is used to schedule uplink and / or downlink transmissions on BWP#1.

[0184] It should be noted that the BIF value corresponding to the PDCCH sent on BWP#3 by BWP#1 indicated by the third parameter can be #1 or other values, such as other integers (e.g., #2). In other words, the BIF value indicated by the third parameter is not necessarily exactly the same as the BIF of the second BWP; they can be the same or different.

[0185] For example, the number of third parameters corresponding to the same second BWP can be multiple, and the BIF corresponding to the PDCCH sent by the second BWP on multiple first BWPs can be determined by the multiple third parameters.

[0186] For example, if BWPs are uniformly numbered across cells, let's assume the second BWP is BWP#1. BWP#1 corresponds to multiple second parameters. The second parameter corresponding to BWP#1 indicates that the BIF corresponding to the first BWP is #3, and another second parameter corresponding to BWP#1 indicates that the BIF corresponding to another first BWP is #4. For each second parameter, there is an associated third parameter, which indicates the BIF corresponding to the PDCCH sent by the second BWP on that first BWP.

[0187] For example, if the second parameter indicates that the BIF corresponding to the first BWP is #3, the third parameter associated with this second parameter indicates that the BIF value corresponding to the PDCCH sent by BWP#1 on the first BWP (BWP#3) is #1. That is, if the terminal device receives the PDCCH on BWP#3 and the BIF value carried in the PDCCH is #1, the terminal device determines that the PDCCH is used to schedule uplink and / or downlink transmissions on BWP#1.

[0188] For example, if the second parameter indicates that the BIF corresponding to the first BWP is #4, the third parameter associated with the second parameter indicates that the BIF value corresponding to the PDCCH sent by BWP#1 on the first BWP (BWP#4) is #1. That is, if the terminal device receives the PDCCH on BWP#4 and the BIF value carried in the PDCCH is #1, the terminal device determines that the PDCCH is used to schedule uplink and / or downlink transmissions on BWP#1.

[0189] It should be noted that the BIF value corresponding to the PDCCH sent by BWP#1 on BWP#3 / BWP#4 as indicated by the third parameter can be #1 or other values, such as other integers (e.g., #2). In other words, the BIF value indicated by the third parameter is not necessarily exactly the same as the BIF of the second BWP; they can be the same or different.

[0190] Optionally, the third parameter indicates the BIF and CIF corresponding to the second BWP.

[0191] For example, the number of third parameters corresponding to the same second BWP can be one. The third parameter determines the BIF and CIF corresponding to the PDCCH sent by the second BWP on the first BWP.

[0192] For example, the second parameter indicates that uplink and / or downlink transmissions on the second BWP are scheduled via the first PDCCH. The third parameter indicates the BIF and CIF corresponding to the PDCCH transmitted by the second BWP on the first BWP.

[0193] For example, the number of third parameters corresponding to the same second BWP can be multiple. The third parameters can be used to determine the BIF and CIF corresponding to the PDCCH sent by the second BWP on multiple first BWPs respectively.

[0194] It is understood that if BWPs are not uniformly numbered in the inter-cell area, the third parameter can indicate the BIF and CIF corresponding to the second BWP. For specific examples, please refer to the relevant embodiments where the third parameter indicates the BIF corresponding to the second BWP when BWPs are uniformly numbered in the inter-cell area. This disclosure will not elaborate further.

[0195] Optionally, the second and third parameters can correspond to a second BWP (e.g., BWP#2), wherein the number of second parameters can be one or more, and the number of third parameters can be one or more.

[0196] For example, the second parameter can be one, and the third parameter can also be one. Assuming the second parameter indicates BIF #1, the PDCCH on BWP #1 is used to schedule uplink and / or downlink transmissions on BWP #2. For instance, assuming the third parameter indicates BIF #2, when the PDCCH on BWP #1 carries BIF #2, the PDCCH on BWP #1 is used to schedule uplink and / or downlink transmissions on BWP #2. In other words, if the PDCCH on the BWP corresponding to the BIF indicated by the second parameter carries the BIF indicated by the third parameter, it can be used to schedule uplink and / or downlink transmissions on BWP #2.

[0197] It should be noted that the BIF indicated by the third parameter can be different from the BIF corresponding to the second BWP. For example, the BIF indicated by the third parameter can be #3. In this case, when the BIF carried in the PDCCH on BWP#1 is #3, the PDCCH on BWP#1 is used to schedule uplink and / or downlink transmissions on BWP#2. This disclosure only uses #3 as an example; the BIF indicated by the third parameter can also be other values ​​and is not limited to this.

[0198] For example, if there is one second parameter and multiple third parameters, assuming the BIF indicated by the second parameter is #1, then the PDCCH on BWP#1 is used to schedule uplink and / or downlink transmissions on BWP#2. For instance, assuming the BIFs indicated by the third parameters are #2 and #3, if the BIF carried by the PDCCH on BWP#1 is #2, then the PDCCH on BWP#1 is used to schedule uplink and / or downlink transmissions on BWP#2; if the BIF carried by the PDCCH on BWP#1 is #3, then the PDCCH on BWP#1 is used to schedule uplink and / or downlink transmissions on BWP#2. In other words, any BWP corresponding to a BIF indicated by the second parameter can be used to schedule uplink and / or downlink transmissions on BWP#2 as long as its PDCCH carries any BIF indicated by the third parameter.

[0199] It should be noted that the BIF indicated by the third parameter can be other values, and is not limited to this one.

[0200] For example, if there are multiple second parameters and one third parameter, and assuming the multiple second parameters indicate BIFs #1 and #3 respectively, then the PDCCH on both BWP#1 and BWP#3 can be used to schedule uplink and / or downlink transmissions on BWP#2. For instance, assuming the third parameter indicates BIF #2, if the PDCCH on BWP#1 carries BIF #2, then the PDCCH on BWP#1 is used to schedule uplink and / or downlink transmissions on BWP#2; if the PDCCH on BWP#3 carries BIF #2, then the PDCCH on BWP#3 is used to schedule uplink and / or downlink transmissions on BWP#2. In other words, any BWP corresponding to a BIF indicated by a second parameter, as long as its PDCCH carries the BIF indicated by the third parameter, can be used to schedule uplink and / or downlink transmissions on BWP#2.

[0201] For example, the second and third parameters can be sent in a table (list). For instance, the correspondence between the second and third parameters configured for BWP#2 can be shown in Table 1.

[0202] Table 1

[0203] For example, there can be multiple second parameters and multiple third parameters. Assuming the BIFs indicated by the multiple second parameters are #1, #3, and #4 respectively, then the PDCCHs on BWP#1, BWP#3, and BWP#4 can all be used to schedule uplink and / or downlink transmissions on BWP#2. Assuming the BIF indicated by the second parameter is #1, and the corresponding BIF indicated by the third parameter is #5, then when the BIF carried by the PDCCH on BWP#1 is #5, the PDCCH on BWP#1 can all be used to schedule uplink and / or downlink transmissions on BWP#2. Assuming the BIF indicated by the second parameter is #3, and the corresponding BIF indicated by the third parameter is #6, then when the BIF carried by the PDCCH on BWP#3 is #6, the PDCCH on BWP#3 can all be used to schedule uplink and / or downlink transmissions on BWP#2. Assuming the second parameter indicates BIF #4 and the corresponding third parameter indicates BIF #7, then when the PDCCH on BWP #4 carries BIF #7, all PDCCHs on BWP #4 can be used to schedule uplink and / or downlink transmissions on BWP #2. In other words, uplink and / or downlink transmissions on the second BWP can be scheduled by multiple first PDCCHs, and a third parameter can be configured for each of the multiple first PDCCHs. When a first PDCCH carries the corresponding third parameter, it can be used to schedule the second BWP.

[0204] For example, the second and third parameters can be sent in a table (list). For instance, the correspondence between the second and third parameters configured for BWP#2 can be shown in Table 2.

[0205] Table 2

[0206] It is understood that the specific indexes, numbers and correspondences in the above embodiments are exemplary and are not limited in this disclosure.

[0207] In some embodiments, the name of the third parameter is not limited, and it may be, for example, "third information", "Radio Resource Control (RRC) signaling", "indication information", etc.

[0208] In step S2104, network device 102 sends the first PDCCH to terminal 101 on the first BWP.

[0209] In some embodiments, terminal 101 receives a first PDCCH sent by network device 102 on a first BWP.

[0210] In some embodiments, the first PDCCH is used to schedule transmissions on the first BWP and / or the second BWP, where transmissions include uplink and / or downlink transmissions. For example, the first PDCCH can be configured to schedule uplink and / or downlink transmissions on the second BWP. When there are uplink and / or downlink transmissions on the first BWP, the PDCCH is used to schedule them. When there are uplink and / or downlink transmissions on the second BWP, the PDCCH is used to schedule them. When there are uplink and / or downlink transmissions on both the first and second BWPs, the PDCCH is used to schedule them. In this embodiment, the PDCCH is the first PDCCH.

[0211] In some embodiments, the terminal supports a first capability. The first capability is to support uplink and / or downlink transmissions scheduled on a second BWP via a first PDCCH.

[0212] Optionally, the terminal supports the first capability by default. That is, the first capability can be a mandatory capability for the terminal. In this case, the network device can assume that the terminal supports the first capability.

[0213] Optionally, the terminal may support the first capability. Other terminals besides this terminal may or may not support the first capability. That is, the first capability may be a non-mandatory capability for the terminal. In this case, the terminal may report the first capability to the network device, as detailed in step S2105 below. The first capability is to support uplink and / or downlink transmissions scheduled on the second BWP via the first PDCCH.

[0214] In step S2105, terminal 101 reports the first capability to network device 102.

[0215] In some embodiments, network device 102 receives a first capability reported by terminal 101.

[0216] In some embodiments, the first capability is to support uplink and / or downlink transmissions scheduled on the second BWP via the first PDCCH.

[0217] In some embodiments, the first capability is terminal-level.

[0218] Optionally, the terminal supports the first capability on both the Time Division Duplex (TDD) and Frequency Division Duplex (FDD) frequency bands. That is, the first capability does not distinguish between TDD and FDD. For example, for the first capability, TDD-FDD difference (DIFF) can be set to "no".

[0219] Optionally, the terminal supports the first capability across different frequency ranges. In other words, the first capability can be frequency-independent. For example, for the first capability, FR1-FR2 DIFF can be set to "no".

[0220] In other embodiments, if the terminal does not support the first capability, then the terminal does not support the first capability in either TDD or FDD. Alternatively, if the terminal does not support the first capability, then the terminal does not support the first capability in any of the different frequency ranges.

[0221] For example, the frequency range (FR) may include FR1 and FR2, where FR1 may be from 0.41 GHz to 7.125 GHz and FR2 may be from 24.25 GHz to 71 GHz. The terminal supports the first capability regardless of whether its frequency range is FR1 or FR2. Of course, FR1 and FR2 are merely two exemplary frequency ranges, and their corresponding range values ​​are also merely exemplary. The frequency range may include many more types and different range values, and this disclosure does not limit this.

[0222] In some embodiments, the first BWP and the second BWP may correspond to the same or different parameter sets (numerology, u). The parameter sets may include, but are not limited to, at least one of the following: SCS; symbol length; CP length.

[0223] In some embodiments, the reporting of a first capability can be done together with other capabilities. For example, the first capability can be defined in User Equipment-New Radio-Capability (UE-NR-Capability).

[0224] For example, the first capability can be called crossBWP-scheduling or cross-BWP scheduling, and this disclosure does not limit it in this way. The value of crossBWP-scheduling can be an enumerated {supported}. If the terminal reports the first capability, it means that the terminal supports crossBWP-scheduling.

[0225] For example, the first capability can be called cross-BWP-Scheduling-SameSCS, and its value can be ENUMERATED{supported}. If the terminal reports the first capability, it means that the terminal supports cross-BWP-Scheduling-SameSCS. Here, the first BWP and the second BWP can correspond to the same u.

[0226] For example, the first capability can be called cross-BWP-Scheduling-DiffSCS, and its value can be ENUMERATED{supported}. If the terminal reports the first capability, it means that the terminal supports cross-BWP-Scheduling-DiffSCS. The first BWP and the second BWP can correspond to different u values.

[0227] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2105. For example, step S2104 may be implemented as a standalone embodiment, but is not limited thereto. As another example, step S2105 may be implemented as a separate embodiment. This disclosure does not list all examples, but is not limited to any of them. The execution order of each step is also not limited; for example, step S2105 may be executed before or after step S2101, and this disclosure does not limit this.

[0228] In some embodiments, step S2101 is optional and may be omitted or replaced in different embodiments.

[0229] In some embodiments, step S2102 is optional and may be omitted or replaced in different embodiments.

[0230] In some embodiments, step S2103 is optional and may be omitted or replaced in different embodiments.

[0231] In some embodiments, step S2105 is optional and may be omitted or replaced in different embodiments.

[0232] In some embodiments, other optional implementations described before or after the specification corresponding to FIG2 may be referred to.

[0233] Figure 3 is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3, this embodiment of the present disclosure relates to a communication method executed by terminal 101, the method including:

[0234] Step S3101: Obtain the first parameter.

[0235] The optional implementation of step S3101 can be found in the optional implementation of step S2101 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0236] In some embodiments, terminal 101 receives a first parameter sent by network device 102, but is not limited thereto; it may also receive a first parameter sent by other entities.

[0237] In some embodiments, terminal 101 obtains a first parameter defined by the protocol.

[0238] In some embodiments, terminal 101 obtains the first parameter from the upper layer(s).

[0239] In some embodiments, the terminal 101 performs processing to obtain the first parameter.

[0240] In some embodiments, step S3101 is omitted, and the terminal 101 autonomously implements the function indicated by the first parameter, or the above function is default or default.

[0241] Step S3102: Obtain the second parameter.

[0242] The optional implementation of step S3102 can be found in the optional implementation of step S2102 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0243] In some embodiments, terminal 101 receives a second parameter sent by network device 102, but is not limited thereto; it may also receive a second parameter sent by other entities.

[0244] In some embodiments, terminal 101 obtains a second parameter defined by the protocol.

[0245] In some embodiments, terminal 101 obtains the second parameter from the upper layer(s).

[0246] In some embodiments, terminal 101 performs processing to obtain the second parameter.

[0247] In some embodiments, step S3102 is omitted, and the terminal 101 autonomously implements the function indicated by the second parameter, or the above function is default or default.

[0248] Step S3103: Obtain the third parameter.

[0249] The optional implementation of step S3103 can be found in the optional implementation of step S2103 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0250] In some embodiments, terminal 101 receives a third parameter sent by network device 102, but is not limited thereto; it may also receive a third parameter sent by other entities.

[0251] In some embodiments, terminal 101 obtains a third parameter defined by the protocol.

[0252] In some embodiments, terminal 101 obtains a third parameter from upper layer(s).

[0253] In some embodiments, terminal 101 performs processing to obtain a third parameter.

[0254] In some embodiments, step S3103 is omitted, and the terminal 101 autonomously implements the function indicated by the third parameter, or the above function is defaulted or set to default.

[0255] Step S3104: Obtain the first PDCCH on the first BWP.

[0256] The optional implementation of step S3104 can be found in the optional implementation of step S2104 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0257] In some embodiments, terminal 101 receives a first PDCCH sent by network device 102 on a first BWP, but is not limited thereto, and may also receive a first PDCCH sent by other entities.

[0258] In some embodiments, terminal 101 acquires the first PDCCH as defined by the protocol.

[0259] In some embodiments, terminal 101 obtains the first PDCCH from the upper layer(s).

[0260] In some embodiments, terminal 101 performs processing to obtain a first PDCCH.

[0261] In some embodiments, step S3104 is omitted, and the terminal 101 autonomously implements the function indicated by the first PDCCH, or the above function is default or default.

[0262] Step S3105: Report the first capability.

[0263] The optional implementation of step S3105 can be found in the optional implementation of step S2105 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0264] In some embodiments, terminal 101 reports the first capability to network device 102, but is not limited thereto; it may also report the first capability to other entities.

[0265] The communication method involved in the embodiments of this disclosure may include at least one of steps S3101 to S3105. For example, step S3104 may be implemented as a standalone embodiment, but is not limited thereto. As another example, step S3105 may be implemented as a separate embodiment. This disclosure does not list all examples, but is not limited to any of them. The execution order of each step is also not limited; for example, step S3105 may be executed before or after step S3101, and this disclosure does not limit this.

[0266] In some embodiments, step S3101 is optional and may be omitted or replaced in different embodiments.

[0267] In some embodiments, step S3102 is optional and may be omitted or replaced in different embodiments.

[0268] In some embodiments, step S3103 is optional and may be omitted or replaced in different embodiments.

[0269] In some embodiments, step S3105 is optional and may be omitted or replaced in different embodiments.

[0270] In some embodiments, other optional implementations may be described before or after the specification corresponding to FIG3.

[0271] Figure 4 is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 4, this embodiment of the present disclosure relates to a communication method executed by a network device 102, the method comprising:

[0272] Step S4101: Send the first parameter.

[0273] The optional implementation of step S4101 can be found in the optional implementation of step S2101 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0274] In some embodiments, network device 102 sends a first parameter to terminal 101, but is not limited to this; it may also send the first parameter to other entities.

[0275] Step S4102: Send the second parameter.

[0276] The optional implementation of step S4102 can be found in the optional implementation of step S2102 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0277] In some embodiments, network device 102 sends a second parameter to terminal 101, but is not limited thereto; it may also send the second parameter to other entities.

[0278] Step S4103: Send the third parameter.

[0279] The optional implementation of step S4103 can be found in the optional implementation of step S2103 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0280] In some embodiments, network device 102 sends a third parameter to terminal 101, but is not limited thereto; it may also send the third parameter to other entities.

[0281] Step S4104: Send the first PDCCH on the first BWP.

[0282] The optional implementation of step S4104 can be found in the optional implementation of step S2104 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0283] In some embodiments, network device 102 sends a first PDCCH to terminal 101 on the first BWP, but is not limited thereto, and may also send the first PDCCH to other entities.

[0284] Step S4105: Acquire the first capability.

[0285] The optional implementation of step S4105 can be found in the optional implementation of step S2105 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0286] In some embodiments, network device 102 receives a first capability reported by terminal 101, but is not limited thereto; it may also receive a first capability sent by other entities.

[0287] In some embodiments, network device 102 acquires a first capability defined by a protocol.

[0288] In some embodiments, network device 102 obtains first capabilities from upper layer(s).

[0289] In some embodiments, network device 102 performs processing to obtain a first capability.

[0290] In some embodiments, step S4105 is omitted, and the network device 102 autonomously implements the function indicated by the first capability, or the above function is defaulted or set to default.

[0291] The communication method involved in the embodiments of this disclosure may include at least one of steps S4101 to S4105. For example, step S4104 may be implemented as a standalone embodiment, but is not limited thereto. As another example, step S4105 may be implemented as a separate embodiment. This disclosure does not list all examples, but is not limited to any of them. The execution order of each step is also not limited; for example, step S4105 may be executed before or after step S4101, and this disclosure does not limit this.

[0292] In some embodiments, step S4101 is optional and may be omitted or replaced in different embodiments.

[0293] In some embodiments, step S4102 is optional and may be omitted or replaced in different embodiments.

[0294] In some embodiments, step S4103 is optional and may be omitted or replaced in different embodiments.

[0295] In some embodiments, step S4105 is optional and may be omitted or replaced in different embodiments.

[0296] In some embodiments, other optional implementations may be described before or after the specification corresponding to Figure 4.

[0297] This disclosure provides a method for cross-BWP scheduling, as follows:

[0298] In some embodiments, PDCCH is configured at the BWP granularity, and PDCCH may or may not be configured on a BWP.

[0299] Example: PUCCH configuration is configured at the BWP granularity. A BWP can have a PDCCH configuration. A BWP can have no PDCCH configuration. Uplink / downlink transmissions (PUSCH / PDSCH) on a BWP with a configured PDCCH can only be scheduled by the PDCCH configured on that BWP. Uplink / downlink transmissions (PUSCH / PDSCH) on a BWP without a configured PDCCH can only be scheduled by the PDCCH on other BWPs with configured PDCCH.

[0300] In some embodiments, the network device configures whether a first BWP can schedule other BWPs across carriers using a first parameter.

[0301] Example: The first BWP is a BWP that configures the PDCCH. The PUSCH / PDSCH on the first BWP is scheduled by the first BWP. The first parameter is used to indicate whether the PDCCH on the first BWP carries the BWP identifier (the BWP identifier is uniformly numbered between cells). For example, the first parameter is set to a first value to indicate that the PDCCH on the first BWP carries the BWP identifier; for example, the first parameter is set to a second value to indicate that the PDCCH on the first BWP does not carry the BWP identifier (BIF BWP indicator). The first parameter is also used to indicate whether the PDCCH on the first BWP carries the BWP identifier and / or the cell identifier (the BWP identifier is not uniformly numbered between cells). For example, the first parameter is set to a first value to indicate that the PDCCH on the first BWP carries the BWP identifier and / or the cell identifier; for example, the first parameter is set to a second value to indicate that the PDCCH on the first BWP does not carry the BWP identifier (BIF BWP indicator) and / or the cell identifier. For example, the first parameter is set to a first value to indicate that the first BWP schedules other carriers across carriers. For example, the first parameter is set to a second value to indicate that the first BWP does not schedule other carriers across carriers. For example, the first value is 1 (true) and the second value is 0 (false). For example, the first value is 0 and the second value is 1. When the first parameter is set to the first value, and the PDCCH on the first BWP is used to schedule uplink / downlink transmissions (PUSCH / PDSCH) of the first BWP, the BIF is set to 0. For example, when the first parameter is set to the first value, the PDCCH on the first BWP may carry one or more BWP identifiers and / or cell identifiers.

[0302] Optionally, the PDCCH on the first BWP can be the first PDCCH.

[0303] In some embodiments, the network device configures the scheduling BWP of the second BWP through a second parameter and / or a third parameter.

[0304] Example: The second BWP is a BWP without a configured PDCCH. The PUSCH / PDSCH on the second BWP is scheduled by other BWPs. The network device configures one or more BWPs (third BWPs) to schedule the second BWP via a second parameter. For example, it configures the identifier (BWP ID) of one or more third BWPs. For instance, all BWPs on one or more cells have a unified number (each BWP's number is unique), and the second parameter indicates a BWP ID. Alternatively, BWPs on a single cell may have a unified number, but BWPs on different cells may have different numbers (a BWP's number on a single cell is unique, but numbers on different BWPs are not unique), and the second parameter indicates both the BWP ID and the cell identifier, such as the serving cell index. It is important to note that the second BWP can be scheduled across BWPs by one or more third BWPs. If the second BWP is scheduled across BWPs by one third BWP, the second parameter indicates a BWP ID or a (BWP ID + cell identifier). If the second BWP is scheduled across BWPs by multiple third BWPs, the second parameter indicates multiple BWP IDs or multiple (BWP ID + cell identifier).

[0305] Example: The third parameter indicates the BIF value corresponding to the second BWP, which is carried in the PDCCH on the third BWP. The PDCCH carrying this BIF is used to schedule uplink / downlink transmissions (PUSCH / PDSCH) on the second BWP. For example, all BWPs on one or more cells have a unified number (each BWP's number is unique), and the third parameter indicates a BWP ID. For example, BWPs on one cell have a unified number, but BWPs on different cells have different numbers (BWPs on one cell are unique, but numbers on different BWPs are not unique), and the third parameter indicates the BWP ID and cell identifier, such as the serving cell index.

[0306] In some embodiments, UE capabilities are defined to indicate whether the UE supports cross-BWP scheduling.

[0307] Example: This capability is used to indicate whether the UE supports cross-BWP scheduling. For instance, different capabilities can be used to indicate whether cross-BWP scheduling is supported, where the scheduling BWP and the scheduled BWP have the same numberology and the scheduling BWP and the scheduled BWP have different numberologies.

[0308] Example: The terminal capability granularity is per UE granularity.

[0309] Example: This terminal capability is either optional or required.

[0310] Example: This terminal does not distinguish between TDD and FDD frequency bands, that is, FDD-TDDDIFF is set to No.

[0311] Example: This terminal does not distinguish between FR1 and FR2. That is, FR1-FR2 DIFF is set to No.

[0312] Example: New terminal capabilities are defined in UE-NR-Capability, such as: `crossBWP-scheduling` (this is just an example; the specific naming is not limited), with a value of, for example, `ENUMERATED{supported}`. If a terminal reports this capability, it indicates that the terminal supports cross-BWP scheduling. `crossBWP-Scheduling-SameSCS`, with a value of, for example, `ENUMERATED{supported}`, indicates that the terminal supports cross-BWP scheduling, where the scheduling BWP and the scheduled BWP have the same numericality. `crossBWP-Scheduling-DiffSCS`, with a value of, for example, `ENUMERATED{supported}`, indicates that the terminal supports cross-BWP scheduling, where the scheduling BWP and the scheduled BWP have different numericalities.

[0313] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0314] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0315] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0316] Figure 5a is a schematic diagram of the terminal structure proposed in an embodiment of this disclosure. As shown in Figure 5a, the terminal 5100 may include at least one of a transceiver module 5101 and a processing module 5102. The transceiver module 5101 is used to receive a first physical downlink control channel (PDCCH) transmitted by a network device on a first bandwidth portion (BWP). The first PDCCH is used to schedule transmissions on the first BWP and / or the second BWP, and the transmissions on the first BWP and / or the second BWP include uplink transmissions and / or downlink transmissions.

[0317] In some embodiments, the PDCCH is not configured on the second BWP.

[0318] In some embodiments, the transceiver module 5101 is further configured to: receive a first parameter sent by the network device; determine, based on the first parameter, that the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP; and determine, based on the first parameter, whether the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP.

[0319] In some embodiments, the first parameter indicates whether the first PDCCH carries a Bandwidth Partial Identifier (BIF); or, the first parameter indicates whether the first PDCCH carries both a BIF and a Cell Identifier (CIF); or, the first parameter indicates whether the first PDCCH is used to schedule uplink and / or downlink transmissions on a second BWP.

[0320] In some embodiments, the first parameter indicates that the first PDCCH carries a BIF, the BIF carried by the first PDCCH is a first value, and the first value is used to indicate that the first PDCCH schedules uplink and / or downlink transmissions on the first BWP.

[0321] In some embodiments, the transceiver module 5101 is further configured to: receive a second parameter sent by the network device, the second parameter being used to determine the first BWP.

[0322] In some embodiments, the second parameter indicates the BIF corresponding to the first BWP, or the second parameter indicates both the BIF and CIF corresponding to the first BWP.

[0323] In some embodiments, the transceiver module 5101 is further configured to: receive a third parameter sent by the network device, the third parameter being used to determine the second BWP.

[0324] In some embodiments, the third parameter indicates the BIF corresponding to the second BWP, which is used to carry in the first PDCCH; or, the third parameter indicates the BIF and CIF corresponding to the second BWP, which are used to carry in the first PDCCH.

[0325] In some embodiments, the terminal supports a first capability, which is to support uplink and / or downlink transmissions scheduled on a second BWP via a first PDCCH.

[0326] In some embodiments, the transceiver module 5101 is further configured to: report a first capability, wherein the first capability is to support uplink and / or downlink transmissions scheduled on the second BWP via a first PDCCH.

[0327] In some embodiments, the first capability is terminal-level.

[0328] In some embodiments, the terminal supports the first capability in both the time division duplex (TDD) band and the frequency division duplex (FDD) band.

[0329] In some embodiments, the terminal supports the first capability across different frequency ranges.

[0330] Figure 5b is a schematic diagram of the network device proposed in an embodiment of this disclosure. As shown in Figure 5b, the network device 5200 may include at least one of a transceiver module 5201 and a processing module 5202. The transceiver module 5201 is used to transmit a first physical downlink control channel (PDCCH) to the terminal on a first bandwidth portion (BWP). The first PDCCH is used to schedule transmissions on the first BWP and / or a second BWP, and the transmissions on the first BWP and / or the second BWP include uplink transmissions and / or downlink transmissions.

[0331] In some embodiments, the PDCCH is not configured on the second BWP.

[0332] In some embodiments, the transceiver module 5201 is further configured to: send a first parameter to the terminal, for the terminal to determine, based on the first parameter, that the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP; the first parameter is used to determine whether the first PDCCH is used to schedule uplink and / or downlink transmissions on the second BWP.

[0333] In some embodiments, the first parameter indicates whether the first PDCCH carries a Bandwidth Partial Identifier (BIF); or, the first parameter indicates whether the first PDCCH carries both a BIF and a Cell Identifier (CIF); or, the first parameter indicates whether the first PDCCH is used to schedule uplink and / or downlink transmissions on a second BWP.

[0334] In some embodiments, the first parameter indicates that the first PDCCH carries a BIF, the BIF carried by the first PDCCH is a first value, and the first value is used to indicate that the first PDCCH schedules uplink and / or downlink transmissions on the first BWP.

[0335] In some embodiments, the transceiver module 5201 is further configured to: send a second parameter to the terminal, the second parameter being used to determine the first BWP.

[0336] In some embodiments, the second parameter indicates the BIF corresponding to the first BWP, or the second parameter indicates both the BIF and CIF corresponding to the first BWP.

[0337] In some embodiments, the transceiver module 5201 is further configured to: send a third parameter to the terminal, the third parameter being used to determine the second BWP.

[0338] In some embodiments, the third parameter indicates the BIF corresponding to the second BWP, which is used to carry in the first PDCCH; or, the third parameter indicates the BIF and CIF corresponding to the second BWP, which are used to carry in the first PDCCH.

[0339] In some embodiments, the terminal supports a first capability, which is to support uplink and / or downlink transmissions scheduled on a second BWP via a first PDCCH.

[0340] In some embodiments, the transceiver module 5201 is further configured to: receive a first capability reported by the terminal, the first capability being to support uplink and / or downlink transmissions on the second BWP via the PDCCH on the first BWP.

[0341] In some embodiments, the first capability is terminal-level.

[0342] In some embodiments, the terminal supports the first capability in both the time division duplex (TDD) band and the frequency division duplex (FDD) band.

[0343] In some embodiments, the terminal supports the first capability across different frequency ranges.

[0344] Figure 6a is a schematic diagram of a communication device according to an embodiment of this disclosure. The communication device 6100 can be a network device, a terminal, or a chip, chip system, or processor that supports the network device in implementing any of the above methods; alternatively, the network device can be an access network device, a core network device, etc. Optionally, the terminal can be a user equipment, etc. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0345] As shown in Figure 6a, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device, execute programs, and process program data. The communication device 6100 is used to execute any of the above methods. Optionally, the communication device can be a base station, a baseband chip, a terminal, a terminal chip, a DU, or a CU, etc.

[0346] In some embodiments, the communication device 6100 further includes one or more memories 6102 for storing instructions. Optionally, all or part of the memories 6102 may also be located outside the communication device 6100.

[0347] In some embodiments, the communication device 6100 further includes one or more transceivers 6103. When the communication device 6100 includes one or more transceivers 6103, the transceivers 6103 perform communication steps such as sending and / or receiving in the above method, such as step S2101a, but are not limited thereto. The processor 6201 performs other steps, such as step S2101b, but is not limited thereto.

[0348] In some embodiments, a transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, etc., may be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., may be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., may be used interchangeably.

[0349] In some embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6102, and the interface circuit 6104 can be used to receive signals from the memory 6102 or other devices, and can be used to send signals to the memory 6102 or other devices. For example, the interface circuit 6104 can read instructions stored in the memory 6102 and send the instructions to the processor 6101.

[0350] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6a. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal, smart terminal, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0351] Figure 6b is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of the chip 6200 shown in Figure 6b, but it is not limited thereto.

[0352] Chip 6200 includes one or more processors 6201, which are used to perform any of the above methods.

[0353] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, the interface circuit 6202 is connected to memory 6203, and the interface circuit 6202 can be used to receive signals from memory 6203 or other devices, and the interface circuit 6202 can be used to send signals to memory 6203 or other devices. For example, the interface circuit 6202 can read instructions stored in memory 6203 and send the instructions to processor 6201.

[0354] In some embodiments, the interface circuit 6202 performs communication steps such as sending and / or receiving in the above method, such as step S2101a, but is not limited thereto. The processor 6201 performs other steps, such as step S2101b, but is not limited thereto.

[0355] In some embodiments, the terms interface circuit, interface, transceiver pin, transceiver, etc., can be used interchangeably.

[0356] In some embodiments, chip 6200 further includes one or more memories 6203 for storing instructions. Optionally, all or part of the memories 6203 may be located outside of chip 6200.

[0357] This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 6100, cause the communication device 6100 to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0358] This disclosure also provides a program product that, when executed by the communication device 6100, causes the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0359] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method characterized by comprising: The method comprises: The terminal receives a first physical downlink control channel (PDCCH) sent by the network device on a first bandwidth part (BWP), wherein the first PDCCH is used for scheduling transmission on the first BWP and / or a second BWP, and the transmission on the first BWP and / or the second BWP includes uplink transmission and / or downlink transmission.

2. The method of claim 1, wherein, No PDCCH is configured on the second BWP.

3. The method according to claim 1 or 2, characterized in that, The method further comprises: The terminal receives a first parameter sent by the network device. The terminal determines, based on the first parameter, that the first PDCCH is used for scheduling uplink transmission and / or downlink transmission on the second BWP. The first parameter is used to determine whether the first PDCCH is used for scheduling uplink transmission and / or downlink transmission on the second BWP.

4. The method of claim 3, wherein: The first parameter indicates whether the first PDCCH carries a bandwidth part identifier (BIF); or The first parameter indicates whether the first PDCCH carries a BIF and a cell identifier (CIF); or The first parameter indicates whether the first PDCCH is used for scheduling uplink transmission and / or downlink transmission on the second BWP.

5. The method according to claim 3 or 4, characterized in that, The first parameter indicates that the first PDCCH carries a BIF, and the first PDCCH carries a first value of the BIF, wherein the first value is used to indicate that the first PDCCH schedules uplink transmission and / or downlink transmission on the first BWP.

6. The method according to any one of claims 1 to 5, characterized in that, The method further comprises: The terminal receives a second parameter sent by the network device, wherein the second parameter is used to determine the first BWP.

7. The method of claim 6, wherein, The second parameter indicates a BIF corresponding to the first BWP, or the second parameter indicates a BIF and a CIF corresponding to the first BWP.

8. The method according to any one of claims 1 to 7, characterized in that, The method further comprises: The terminal receives a third parameter sent by the network device, wherein the third parameter is used to determine the second BWP.

9. The method of claim 8, wherein, The third parameter indicates a BIF corresponding to the second BWP, wherein the BIF is carried in the first PDCCH; or the third parameter indicates a BIF and a CIF corresponding to the second BWP, wherein the BIF and the CIF are carried in the first PDCCH.

10. The method according to any one of claims 1-9, characterized in that, The terminal supports a first capability, wherein the first capability is to support scheduling uplink transmission and / or downlink transmission on the second BWP through the first PDCCH.

11. The method according to any one of claims 1-10, characterized in that, The method further comprises: The terminal reports a first capability, wherein the first capability is to support scheduling uplink transmission and / or downlink transmission on the second BWP through the first PDCCH.

12. The method according to claim 10 or 11, characterized in that, The first capability is a terminal-level capability.

13. The method of claim 12, wherein, The terminal supports the first capability on both a time division duplex (TDD) frequency band and a frequency division duplex (FDD) frequency band.

14. The method according to claim 12 or 13, characterized in that, The terminal supports the first capability on different frequency ranges.

15. A method of communication, comprising: The method comprises: The network device transmits a first physical downlink control channel (PDCCH) to a terminal on a first bandwidth part (BWP), the first PDCCH being used for scheduling a transmission on the first BWP and / or a second BWP, the transmission on the first BWP and / or the second BWP including uplink transmission and / or downlink transmission.

16. The method of claim 15, wherein, No PDCCH is configured on the second BWP.

17. The method according to claim 15 or 16, characterized in that, The method further includes: The network device transmits a first parameter to the terminal, the first parameter being used by the terminal to determine that the first PDCCH is used for scheduling uplink transmission and / or downlink transmission on the second BWP. The first parameter is used to determine whether the first PDCCH is used for scheduling uplink transmission and / or downlink transmission on the second BWP.

18. The method of claim 17, wherein The first parameter indicates whether the first PDCCH carries a bandwidth part identifier (BIF); or The first parameter indicates whether the first PDCCH carries a BIF and a cell identifier (CIF); or The first parameter indicates whether the first PDCCH is used for scheduling uplink transmission and / or downlink transmission on the second BWP.

19. The method of claim 17 or 18, wherein, The first parameter indicates that the first PDCCH carries a BIF, the BIF carried by the first PDCCH being a first value, the first value being used to indicate that the first PDCCH schedules uplink transmission and / or downlink transmission on the first BWP.

20. The method of any of claims 15-19, wherein, The method further includes: The network device transmits a second parameter to the terminal, the second parameter being used to determine the first BWP.

21. The method of claim 20, wherein, The second parameter indicates a BIF corresponding to the first BWP, or the second parameter indicates a BIF and a CIF corresponding to the first BWP.

22. The method of any of claims 15-21, wherein, The method further includes: The network device transmits a third parameter to the terminal, the third parameter being used to determine the second BWP.

23. The method of claim 22, wherein, The third parameter indicates a BIF corresponding to the second BWP, the BIF being carried in the first PDCCH; or the third parameter indicates a BIF and a CIF corresponding to the second BWP, the BIF and the CIF being carried in the first PDCCH.

24. The method of any of claims 15-22, wherein, The terminal supports a first capability, the first capability being support for scheduling uplink transmission and / or downlink transmission on the second BWP through the first PDCCH.

25. The method of any of claims 15-23, wherein, The method further includes: The network device receives a first capability reported by the terminal, the first capability being support for scheduling uplink transmission and / or downlink transmission on the second BWP through a PDCCH on the first BWP.

26. The method of claim 24 or 25, wherein, The first capability is a terminal-level capability.

27. The method of claim 26, wherein, The terminal supports the first capability on both a time division duplex (TDD) frequency band and a frequency division duplex (FDD) frequency band.

28. The method of claim 26 or 27, wherein, The terminal supports the first capability on different frequency ranges.

29. A terminal, characterized by The method further includes: The transceiver module is configured to receive a first physical downlink control channel (PDCCH) transmitted by a network device on a first bandwidth part (BWP), the first PDCCH being used for scheduling a transmission on the first BWP and / or a second BWP, the transmission on the first BWP and / or the second BWP including an uplink transmission and / or a downlink transmission.

30. A network device, comprising: The transceiver module is configured to receive a first physical downlink control channel (PDCCH) transmitted by a network device on a first bandwidth part (BWP), the first PDCCH being used for scheduling a transmission on the first BWP and / or a second BWP, the transmission on the first BWP and / or the second BWP including an uplink transmission and / or a downlink transmission. The transceiver module is configured to receive a first physical downlink control channel (PDCCH) transmitted by a network device on a first bandwidth part (BWP), the first PDCCH being used for scheduling a transmission on the first BWP and / or a second BWP, the transmission on the first BWP and / or the second BWP including an uplink transmission and / or a downlink transmission.

31. A terminal, characterized by One or more processors; The processor is configured to perform the communication method in any of claims 1-14. One or more processors; 32. A network device, comprising: The processor is configured to perform the communication method in any of claims 15-28. A terminal and a network device, wherein the terminal is configured to implement the communication method in any of claims 1-14, and the network device is configured to implement the communication method in any of claims 15-28. A storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the communication method in any of claims 1-14 or 15-28.

33. A communication system, characterized by A computer program that, when executed on a communication device, causes the communication device to perform the communication method in any of claims 1-14 or 15-28. ​ 34. A storage medium, characterized by ​ ​ 35. A program product, characterized by ​ ​