WO2025256567A1 - 通信方法及相关装置 - Google Patents

通信方法及相关装置

Info

Publication number
WO2025256567A1
WO2025256567A1 PCT/CN2025/100495 CN2025100495W WO2025256567A1 WO 2025256567 A1 WO2025256567 A1 WO 2025256567A1 CN 2025100495 W CN2025100495 W CN 2025100495W WO 2025256567 A1 WO2025256567 A1 WO 2025256567A1
Authority
WO
WIPO (PCT)
Prior art keywords
carrier
scheduled
information
carriers
identifier
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2025/100495
Other languages
English (en)
French (fr)
Inventor
王婷
唐浩
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2025256567A1 publication Critical patent/WO2025256567A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/231—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the layers above the physical layer, e.g. RRC or MAC-CE signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method and related apparatus.
  • the uplink and downlink carriers of one cell can be scheduled by carriers of another cell, and the downlink control information (DCI) for both uplink and downlink transmissions is transmitted on the same scheduled carrier.
  • DCI downlink control information
  • This application discloses a communication method and related apparatus that can flexibly and dynamically configure carrier waves, thereby improving communication performance.
  • this application discloses a first communication method that can be applied to a communication device, such as a terminal-side communication device.
  • This communication device is a terminal device, or a device within the terminal device (e.g., a chip, a chip system, or a circuit), or a device compatible with the terminal device.
  • the method includes: receiving first information, the first information including information about a carrier group, the carrier group including a scheduling carrier and a scheduled carrier; and determining at least two scheduling carriers of the scheduled carrier based on the first information.
  • the scheduling carrier and the scheduled carrier through the carrier group, at least two scheduling carriers of the scheduled carrier can be determined, enabling flexible carrier scheduling and dynamic switching of scheduling carriers, reducing scheduling latency and transmission latency, and improving communication performance.
  • this application discloses a second communication method that can be applied to a communication device, such as a network-side communication device.
  • This device can be a network equipment, or a device within a network equipment (e.g., a chip, a chip system, or a circuit), or a device compatible with a network equipment.
  • this method can be applied to a terminal device, or a device within a terminal device, or a device compatible with a terminal device.
  • the method includes: determining first information, the first information including information about the carrier group, the carrier group including a scheduling carrier and a scheduled carrier, the scheduled carrier corresponding to at least two scheduling carriers; and sending the first information.
  • the scheduling carrier and the scheduled carrier through the carrier group, at least two scheduling carriers of the scheduled carrier can be determined, enabling flexible carrier scheduling and dynamic switching of scheduling carriers, reducing scheduling latency and transmission latency, and improving communication performance.
  • the scheduled carrier is scheduled by at least two scheduled carriers in the carrier groups; or the scheduled carrier is scheduled by at least two scheduled carriers in the carrier groups.
  • the carrier group when a carrier group is configured with a scheduled carrier, the carrier group includes a scheduled carrier and a scheduled carrier scheduled by that scheduled carrier, requiring the scheduling carrier of the scheduled carrier to be determined from at least one other carrier group.
  • both the scheduled carrier and its scheduling carrier are contained within a carrier group, allowing at least two scheduling carriers of the scheduled carrier to be determined from the carrier group containing the scheduled carrier.
  • Configuring the scheduled carrier and the scheduled carrier with carrier groups facilitates determining the association between the scheduled carrier and the scheduled carrier, and also facilitates updating the carrier group information. When switching scheduled carriers, scheduling delay and transmission delay can be reduced, improving communication performance.
  • the information of the carrier group includes a carrier group identifier of the carrier group, a carrier identifier of the scheduled carrier in the carrier group, and a carrier identifier of the scheduled carrier in the carrier group.
  • the uplink and downlink carriers can be numbered together (joint numbering), or they can be numbered separately (independent numbering).
  • the carrier identifier of the uplink carrier can be called the uplink carrier identifier or the transmit carrier identifier, and the carrier identifier of the downlink carrier can be called the downlink carrier identifier or the receive carrier identifier.
  • the scheduled carrier includes an uplink scheduled carrier and/or a downlink scheduled carrier.
  • the method further includes: receiving second information, the second information including at least one of a carrier group identifier of a first carrier group, a carrier identifier of a first scheduled carrier, and a carrier identifier of a first scheduled carrier; and determining information about the carrier group based on the second information. It is understood that configuring the scheduled carrier and the scheduled carrier with the carrier group information in the first information is beneficial for determining the association between the scheduled carrier and the scheduled carrier, and for updating the carrier group information. This example, by updating the carrier group information through the second information, can reduce signaling overhead, improve update efficiency, and enhance communication performance.
  • it further includes: sending second information, the second information including at least one of a carrier group identifier of the first carrier group, a carrier identifier of the first scheduled carrier, and a carrier identifier of the first scheduled carrier.
  • the first information includes deactivated carriers in the first carrier group, the first scheduled carrier is an updated scheduled carrier in the first carrier group, and the first scheduled carrier is an active carrier.
  • the second information includes the carrier identifier of the first scheduled carrier and the carrier group identifier of the first carrier group. Determining the information of the carrier group based on the second information includes: updating the carrier identifier of the scheduled carrier in the information of the first carrier group based on the carrier group identifier of the first carrier group and the carrier identifier of the first scheduled carrier, thereby updating the scheduled carrier of the first carrier group.
  • the carrier identifier of the scheduled carrier in the first carrier group is updated to the carrier identifier of the first scheduled carrier, that is, the scheduled carrier in the first carrier group is updated to the first scheduled carrier.
  • Not updating the carrier identifier of the scheduled carrier in the first carrier group can reduce signaling overhead, thereby allowing the scheduled carriers to be scheduled through the first scheduled carrier, so that there are active scheduled carriers among these scheduled carriers, which is beneficial for timely scheduling of the scheduled carriers and improves communication performance.
  • the scheduled carriers in the first carrier group in the first information include the first scheduled carrier, and the first scheduled carrier is a deactivated carrier; the second information includes the carrier identifier of the first scheduled carrier; determining the information of the carrier group based on the second information includes deleting the carrier identifier of the first scheduled carrier from the information of the first carrier group.
  • the first scheduled carrier is an updated scheduled carrier of the first carrier group
  • the first scheduled carrier is an active carrier.
  • the second information includes the carrier identifier of the first scheduled carrier and the carrier group identifier of the first carrier group. Determining the information of the carrier group based on the second information includes: adding the carrier identifier of the first scheduled carrier to the information of the first carrier group based on the carrier group identifier of the first carrier group and the carrier identifier of the first scheduled carrier.
  • the carrier identifier of the first scheduled carrier is added from the first carrier group to which the first scheduled carrier is to be added, thereby enabling the scheduled carrier to correspond to more scheduled carriers, facilitating improved flexibility in data transmission.
  • the first information includes deactivated carriers in the first carrier group, the first scheduled carrier is an updated scheduled carrier in the first carrier group, and the first scheduled carrier is an active carrier.
  • the second information includes the carrier identifier of the first scheduled carrier and the carrier group identifier of the first carrier group.
  • the carrier identifier of the scheduled carrier in the first carrier group is updated to the carrier identifier of the first scheduled carrier; that is, the scheduled carrier in the first carrier group is updated to the first scheduled carrier.
  • Not updating the carrier identifier of the scheduled carriers in the first carrier group reduces signaling overhead, allowing the scheduled carriers to be scheduled through the first scheduled carrier. This ensures that there are active scheduled carriers among these scheduled carriers, facilitating timely scheduling of the scheduled carriers and improving communication performance.
  • the scheduled carrier in the first carrier group in the first information includes the first scheduled carrier, and the first scheduled carrier is a deactivated carrier.
  • the second information includes the carrier identifier of the first scheduled carrier.
  • the first scheduled carrier is an updated scheduled carrier of the first carrier group
  • the first scheduled carrier is an active carrier.
  • the second information includes the carrier identifier of the first scheduled carrier and the carrier group identifier of the first carrier group.
  • this application discloses a third communication method that can be applied to a communication device, such as a terminal-side communication device, which is a terminal device, a device within a terminal device, or a device compatible with a terminal device.
  • the method includes: receiving first information, the first information being used to determine the association between a scheduling carrier and a scheduled carrier; and determining at least two scheduling carriers of the scheduled carrier based on the first information.
  • the terminal device can determine at least two scheduling carriers of the scheduled carrier based on the association.
  • this application discloses a fourth communication method that can be applied to a communication device, such as a network-side communication device, which is a network device, a device within a network device, or a device compatible with a network device.
  • this method can be applied to a terminal device, a device within a terminal device, or a device compatible with a terminal device.
  • the method includes: determining first information, whereby the first information is used to determine the association between a scheduled carrier and a scheduled carrier, wherein the scheduled carrier corresponds to at least two scheduled carriers; and sending the first information.
  • the terminal device can determine at least two scheduled carriers of the scheduled carrier based on the association relationship.
  • the first information includes: configuration information of the scheduled carrier, which is used to determine the scheduling carrier of the scheduled carrier; or configuration information of the scheduling carrier, which is used to determine the scheduled carrier of the scheduling carrier; or an association table of the scheduling carrier and the scheduled carrier.
  • the method further includes: determining the carrier indicator field (CIF) of the scheduled carrier based on the location of the carrier identifier of the scheduled carrier.
  • CIF carrier indicator field
  • the value of the CIF of the scheduled carrier can be determined based on the carrier identifier of the scheduled carrier configured in the first information.
  • existing technologies configure the CIF and determine the carrier identifier of the scheduled carrier based on the CIF value. Compared to existing technologies, this method directly determines the value of the CIF of the scheduled carrier without indicating its value, improving the efficiency of determining the scheduled carrier and reducing signaling overhead.
  • the CIF is 0 when the scheduling carrier is a self-scheduled carrier.
  • the scheduling carrier is a self-scheduled carrier and/or a cross-scheduled carrier.
  • the scheduling carrier of this application can be both self-scheduled and cross-scheduled, offering greater flexibility.
  • a cell includes one or more downlink carriers and/or one or more uplink carriers.
  • the uplink and downlink carriers can be configured unpaired, meaning that the uplink carriers do not have fixed paired downlink carriers, and network devices can flexibly configure the carriers for terminal devices.
  • one possible example further includes: performing a blind detection of the physical downlink control channel (PDCCH) on the second scheduling carrier in the first time unit based on third information, wherein the third information is configuration information or predefined information.
  • the third information is configuration information or predefined information.
  • it also includes: sending a third message.
  • the third information includes at least one of the following: blind detection conditions; or carrier identifiers for priority detection; or time-domain patterns of the scheduled carriers.
  • the blind detection condition can be used to determine the PDCCH for blind detection of a carrier.
  • the protocol can predefine that the terminal device detects carriers with a carrier identifier less than a first threshold. It can be understood that performing PDCCH blind detection on carriers that meet the blind detection condition and not performing it on carriers that do not meet the condition reduces the number of blind detections, thus reducing the complexity of blind detection and saving energy for the terminal device. Similarly, performing PDCCH blind detection on carriers with priority detection carrier identifiers and not performing it on carriers with other identifiers reduces the number of blind detections, thus reducing the complexity of blind detection and saving energy for the terminal device.
  • network devices can be semi-statically configured to prioritize carrier identifiers for detection. This improves the configuration flexibility of the scheduled carriers used for updating PDCCH blind detection, facilitating the updating of scheduled carriers for PDCCH blind detection.
  • the network device can specify a scheduled carrier to be prioritized for detection within a certain period, and perform PDCCH blind detection on that scheduled carrier during that period.
  • the third information includes the carrier identifier of the scheduling carrier for each time unit.
  • it further includes: determining the number of PDCCH blind detections on the scheduled carrier based on the number of carriers of the scheduled carrier.
  • the scheduled carrier is not limited to uplink or downlink carriers; that is, the number of scheduled carriers of the scheduled carrier is the sum of the number of uplink scheduled carriers and the number of downlink scheduled carriers of the scheduled carrier, and the total number of scheduled carriers is the sum of the number of all uplink scheduled carriers and the number of all downlink scheduled carriers.
  • the number of PDCCH blind detections on the scheduled carrier is determined, including: determining the total number of scheduled carriers based on the number of scheduled carriers of the scheduled carrier; determining the blind detection ratio of the first scheduled carrier based on the number of scheduled carriers of the first scheduled carrier and the total number of scheduled carriers; and obtaining the number of PDCCH blind detections on the first scheduled carrier based on the product of the blind detection ratio of the first scheduled carrier and the maximum number of blind detections.
  • the number of blind detections of the PDCCH on the first scheduling carrier can be the product of the blind detection ratio of the first scheduling carrier and the maximum number of blind detections. If the product has a decimal, it can be rounded up or down, and the integer obtained can be used as the number of blind detections of the PDCCH on the first scheduling carrier.
  • the scheduled carrier is limited to downlink scheduled carriers, the number of scheduled carriers is the same as the number of downlink scheduled carriers, and the total number of scheduled carriers is the same as the total number of downlink scheduled carriers.
  • the number of PDCCH blind detections on the scheduled carrier is determined, including: determining the total number of downlink scheduled carriers based on the number of downlink scheduled carriers of the scheduled carrier; determining the blind detection ratio of the first scheduled carrier based on the number of downlink scheduled carriers and the total number of downlink scheduled carriers of the first scheduled carrier; and obtaining the number of PDCCH blind detections on the first scheduled carrier based on the product of the blind detection ratio of the first scheduled carrier and the maximum number of blind detections.
  • the scheduled carrier is limited to uplink scheduled carriers, the number of scheduled carriers is the same as the number of uplink scheduled carriers, and the total number of scheduled carriers is the same as the total number of uplink scheduled carriers.
  • the number of PDCCH blind detections on the scheduled carrier is determined, including: determining the total number of uplink scheduled carriers based on the number of uplink scheduled carriers of the scheduled carrier; determining the blind detection ratio of the first scheduled carrier based on the number of uplink scheduled carriers and the total number of uplink scheduled carriers of the first scheduled carrier; and obtaining the number of PDCCH blind detections on the first scheduled carrier based on the product of the blind detection ratio of the first scheduled carrier and the maximum number of blind detections.
  • the number of blind PDCCH detections may include the maximum number of blind PDCCH candidate detections and/or the maximum number of non-overlapping control channel elements (CCEs).
  • CCEs non-overlapping control channel elements
  • it further includes: receiving a first DCI, the first DCI being used to indicate whether a PDCCH blind detection is performed on the third scheduling carrier; or the first DCI being used to indicate whether a second DCI of a second scheduled carrier is blindly detected on the third scheduling carrier, the second scheduled carrier being scheduled by the third scheduling carrier.
  • it further includes: transmitting a first DCI, the first DCI being used to indicate whether a PDCCH blind detection is performed on the third scheduling carrier; or the first DCI being used to indicate whether a second DCI of a second scheduled carrier is blindly detected on the third scheduling carrier, the second scheduled carrier being scheduled by the third scheduling carrier.
  • the first DCI is used to schedule data transmission on the second scheduled carrier of the second scheduling carrier.
  • the first DCI can be understood as the DCI obtained by performing a PDCCH blind detection on the first scheduling carrier.
  • the third scheduling carrier can be understood as a carrier other than the second scheduling carrier.
  • the third scheduling carrier can schedule the scheduled carrier of the second scheduling carrier, or it can choose not to schedule the scheduled carrier of the second scheduling carrier. That is, the first DCI can indicate the scheduled carrier of the scheduling carrier transmitting the first DCI, and it can also indicate whether to perform a PDCCH blind detection on other scheduling carriers.
  • the first DCI may include a first indication field, which is used to indicate whether other scheduled carriers are blindly detected.
  • the first indication field has 1 bit, that is, one bit.
  • a value of 0 in this bit indicates that other scheduled carriers are not blindly detected, and a value of 1 in this bit indicates that other scheduled carriers are blindly detected; or, a value of 1 in this bit indicates that other scheduled carriers are not blindly detected, and a value of 0 in this bit indicates that other scheduled carriers are blindly detected.
  • the first indication field has s bits, i.e., s bits.
  • s represents the number of other scheduled carriers indicating whether blind detection is required.
  • One bit of this first indication field corresponds to one scheduled carrier, such as scheduled carrier c.
  • a bit value of 0 corresponding to scheduled carrier c indicates no blind detection of scheduled carrier c, and a bit value of 1 corresponding to scheduled carrier c indicates blind detection of scheduled carrier c; or, a bit value of 1 corresponding to scheduled carrier c indicates no blind detection of scheduled carrier c, and a bit value of 0 corresponding to scheduled carrier c indicates blind detection of scheduled carrier c.
  • the method further includes: receiving fourth information, which includes a first-level DCI and a second-level DCI; determining the scheduling carrier and time-frequency position of the second-level DCI based on the first-level DCI; and determining the scheduled carrier where the data transmission occurs based on the second-level DCI.
  • one possible example further includes: sending fourth information, which includes a first-level DCI and a second-level DCI.
  • the first-level DCI is used to determine the scheduling carrier and time-frequency location of the second-level DCI
  • the second-level DCI is used to determine the scheduled carrier where data transmission occurs. This provides greater flexibility and facilitates switching of scheduled carriers.
  • embodiments of this application disclose a communication device, including units, modules, or means for performing various steps of any of the above-described aspects or any implementation methods therein.
  • embodiments of this application disclose another communication device, which may be a terminal device or a network device, or a device within a terminal device or a network device, or a device compatible with a terminal device or a network device.
  • the communication device may include a processor configured to execute methods described in any of the above aspects or any possible examples by executing instructions stored in memory, or by using logic circuitry.
  • the communication device also includes one or more of a memory or transceiver for sending and receiving data and/or signaling.
  • this application discloses a seventh communication device, including a processor and a memory and a communication interface connected to the processor, the memory being used to store one or more programs and configured to be executed by the processor of the steps of any of the above aspects or any possible examples of the methods.
  • embodiments of this application disclose a communication system, which includes a terminal device or a network device.
  • embodiments of this application disclose a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the methods described in any of the above aspects or any possible examples.
  • embodiments of this application disclose a computer program product for storing a computer program that, when run on a computer, causes the computer to perform the methods described in any of the above aspects or any possible examples.
  • embodiments of this application disclose a first chip, including a processor and a memory, wherein the processor is used to call and execute instructions stored in the memory, causing a device equipped with the chip to perform the methods described in any of the above aspects or any possible examples.
  • embodiments of this application disclose a second type of chip, including: an input interface, an output interface, and a processing circuit.
  • the input interface, the output interface, and the processing circuit are connected through an internal connection path.
  • the processing circuit is used to execute the methods in any of the above aspects or any possible examples.
  • embodiments of this application disclose a third type of chip, including: an input interface, an output interface, and a processor.
  • a processor optionally, it also includes a memory.
  • the input interface, the output interface, the processor, and the memory are connected through an internal connection path.
  • the processor is used to execute code in the memory. When the code is executed, the processor is used to execute the method in any of the above aspects or any possible examples.
  • embodiments of this application disclose a chip system including at least one processor, a memory, and an interface circuit.
  • the memory, transceiver, and at least one processor are interconnected via lines.
  • At least one memory stores a computer program.
  • the computer program is executed by the processor using the methods described in any of the above aspects or any possible examples.
  • Figure 1A is a schematic diagram of the architecture of a communication system provided in an embodiment of this application.
  • FIGS 1B and 1C are schematic diagrams of the architecture of an NTN communication system provided in an embodiment of this application.
  • Figure 1D is a schematic diagram of the architecture of an IoT communication system provided in an embodiment of this application.
  • Figure 1E is a schematic diagram of the architecture of an IAB communication system provided in an embodiment of this application.
  • Figure 2 is a schematic diagram of a prior art method for switching scheduling carriers
  • FIG. 3 is a flowchart illustrating a communication method provided in an embodiment of this application.
  • FIGS. 4A and 4B are schematic diagrams of a carrier number provided in an embodiment of this application.
  • Figures 5A and 5B are schematic diagrams illustrating the relationship between a scheduling carrier and a scheduled carrier provided in an embodiment of this application.
  • FIG. 6 is a schematic diagram of a switching scheduling carrier provided in an embodiment of this application.
  • FIG. 7 is a schematic diagram of another switching scheduling carrier provided in an embodiment of this application.
  • Figure 8 is a schematic diagram of the structure of a communication device provided in an embodiment of this application.
  • FIG. 9 is a schematic diagram of another communication device provided in an embodiment of this application.
  • Figure 10 is a schematic diagram of the structure of a terminal device provided in an embodiment of this application.
  • LTE Long Term Evolution
  • NR New Radio
  • LTE-A LTE Advanced
  • D2D Device-to-Device
  • V2X Vehicle-to-Everything
  • M2M Machine-to-Machine
  • IoT Internet of Things
  • NB-IoT Narrow Band Internet of Things
  • FDM Frequency Division Duplex
  • FDD Fractional Direct Execution
  • TDD Time Division Duplex
  • NTN Non-Terrestrial Network
  • wireless projection communication systems integrated access and backhaul (IAB) communication systems
  • PLMN public land mobile network
  • NPN non-public network
  • the communication system may include a terminal device 101 and a network device 102.
  • the terminal device 101 can be wirelessly connected to the network device 102.
  • the link for direct communication between terminal devices 101 is a sidelink (SL).
  • the communication link for terminal device 101 to send data or signaling to network device 102 is an uplink (UL), and the communication link for network device 102 to send data or signaling to terminal device 101 is a downlink (DL).
  • UL uplink
  • DL downlink
  • Terminal devices 101 can communicate with each other using some air interface technology (such as NR or LTE). Terminal devices 101 and network devices 102 can also communicate with each other using some air interface technology (such as NR or LTE). Communication between terminal devices 101 and network devices 102, between network devices 102, and between terminal devices 101 can be conducted using licensed spectrum, unlicensed spectrum, or both. This application does not limit the spectrum resources (frequency domain resources) used by terminal devices 101 and network devices 102.
  • some air interface technology such as NR or LTE
  • Terminal devices 101 and network devices 102 can also communicate with each other using some air interface technology (such as NR or LTE). Communication between terminal devices 101 and network devices 102, between network devices 102, and between terminal devices 101 can be conducted using licensed spectrum, unlicensed spectrum, or both. This application does not limit the spectrum resources (frequency domain resources) used by terminal devices 101 and network devices 102.
  • terminal device 101 is a user-side entity used to receive or transmit signals, providing voice and/or data to the user.
  • Terminal device may also be referred to as terminal, user equipment (UE), access terminal, UE unit, UE station, mobile device, mobile station, mobile station, mobile terminal, mobile client, mobile unit, remote station, remote terminal, remote unit, wireless unit, wireless communication device, user agent, or user device, etc.
  • UE user equipment
  • Access terminal may be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, terminal in a future 5G communication system, terminal in a future evolved PLMN, or terminal in a future NPN, etc.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • the terminal device 101 can also be a wearable device.
  • Wearable devices also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes.
  • Wearable devices are portable devices worn directly on the body or integrated into a user's clothing or accessories.
  • Wearable devices are not merely hardware devices; they achieve powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include those with comprehensive functions, large size, and the ability to perform complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those focused on a specific application function that require interaction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.
  • the device for implementing the functions of the terminal device can be the terminal device itself, or it can be a device capable of supporting the terminal device in implementing the functions, such as a chip system or a chip, which can be installed in the terminal device.
  • the chip system can be composed of chips, or it can include chips and other discrete devices.
  • network device 102 may include at least one of (radio)access network (RAN) device, core network (CN) device, and data network (DN) device.
  • RAN radio access network
  • CN core network
  • DN data network
  • Access network equipment refers to nodes or devices used to support terminal devices in accessing the communication system.
  • the access network provides access services to terminal devices, enabling them to access the network.
  • Access networks can support both wired and wireless access.
  • the main functions of access network equipment include: managing radio resources, compressing Internet Protocol (IP) headers and encrypting user data streams, selecting the Mobile Management Entity (MME) when a user equipment attaches, routing user plane data to the Service Gateway (SGW), organizing and sending paging messages, organizing and sending broadcast messages, and configuring measurement and reporting for mobility or scheduling purposes. This ultimately facilitates the forwarding of control signals and user data between terminal devices and core network equipment.
  • Access network equipment can be simply referred to as the access network.
  • AN/RAN nodes may include, but are not limited to: access points (APs), enhanced node Bs (eNBs), home-evolved node Bs (HNBs), baseband units (BBUs), next-generation node Bs (gNBs), transmission reception points (TRPs), transmission points (TPs), or other access nodes, such as wireless relay nodes or wireless backhaul nodes.
  • AN/RAN nodes may be one or more antenna panels, or network nodes constituting gNBs or transmission points, such as BBUs or distributed units (DUs), or devices performing RAN functions in communication systems such as D2D, V2X, M2M, and U2U.
  • AN/RAN nodes can be radio controllers in cloud radio access network (CRAN) scenarios, open RAN (O-RAN or ORAN), access networks in communication systems that evolve after 5G communication systems, such as xNodeB in 6G communication systems, or access networks in PLMN networks that evolve after 5G communication systems, etc., without any limitation.
  • CRAN cloud radio access network
  • O-RAN open RAN
  • access networks in communication systems that evolve after 5G communication systems such as xNodeB in 6G communication systems
  • PLMN networks that evolve after 5G communication systems, etc., without any limitation.
  • the protocol stack architecture and functions of the access network device can be divided into two parts: one part is called a central unit (CU) and the other part is called a DU.
  • This type of network device can be called a RAN device that includes CU nodes and DU nodes.
  • the core network device can connect to one or more access network devices.
  • the core network device is responsible for maintaining the subscription data of the mobile network, managing the network elements of the mobile network, and providing terminal devices with functions such as session management, mobility management, policy management, and security authentication.
  • a terminal device when a terminal device attaches, it provides network access authentication; when the terminal device has a service request, it allocates network resources for the terminal device; when the terminal device moves, it updates network resources for the terminal device; when the terminal device is idle, it provides a fast recovery mechanism; when the terminal device detaches, it releases network resources for the terminal device; and when the terminal device has service data, it provides data routing functions, such as forwarding uplink information to the data network device in a 5G communication system; or forwarding downlink information received from the data network device to the access network device so that the access network device can send the downlink information to the terminal device.
  • data routing functions such as forwarding uplink information to the data network device in a 5G communication system; or forwarding downlink information received from the data network device to the access network device so that the access network device can send the downlink information to the terminal device.
  • core network equipment can correspond to different devices.
  • core network equipment in a 3G communication system, it can correspond to the Serving GPRS Support Node (SGSN) and/or the Gateway GPRS Support Node (GGSN); in a 4G communication system, it can correspond to the Mobility Management Entity (MME) and/or the Serving Gateway (S-GW); and in a 5G communication system, it can include control plane (CP) function network elements and user plane function (UPF) network elements.
  • SGSN Serving GPRS Support Node
  • GGSN Gateway GPRS Support Node
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • 5G communication system it can include control plane (CP) function network elements and user plane function (UPF) network elements.
  • CP control plane
  • UPF user plane function
  • the control plane function network elements can include policy control function (PCF) network elements, unified data management (UDM) network elements, application function (AF) network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, and location management function (LMF) network elements. These elements primarily perform functions such as access authentication, security encryption, and location registration for terminal devices, as well as the establishment, release, and modification of user plane transmission paths.
  • PCF policy control function
  • UDM unified data management
  • AF application function
  • AMF access and mobility management function
  • SMF session management function
  • LMF location management function
  • These elements primarily perform functions such as access authentication, security encryption, and location registration for terminal devices, as well as the establishment, release, and modification of user plane transmission paths.
  • the UPF network element is responsible for managing user plane data transmission and quality of service (QoS) control, traffic statistics, and other functions.
  • QoS quality of service
  • It can execute user packet forwarding according to the routing rules of the session management network element, such as sending uplink information to the data network or other user plane network elements, and forwarding downlink information to other user plane network elements or (R)AN network elements.
  • the session management network element such as sending uplink information to the data network or other user plane network elements, and forwarding downlink information to other user plane network elements or (R)AN network elements.
  • network elements may also be referred to as functional network elements, functional entities, nodes, devices, etc.
  • a network element can be a network component implemented on dedicated hardware, a software instance running on dedicated hardware, or an instance of virtualized functionality on a suitable platform.
  • the virtualization platform could be a cloud platform.
  • the above network elements may have other names, which are not limited in this application.
  • the data network device is used to provide business services to users.
  • the client is a terminal device
  • the server is the data network device.
  • the data network provided by the data network device may include a private network, such as a local area network (LAN).
  • the data network may also include an external network not controlled by the operator, such as the Internet.
  • the data network may also include a proprietary network jointly deployed by operators, such as a network providing Internet Protocol (IP) Multimedia Subsystem (IMS) services.
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • the terminal devices, network devices, and various network elements described above can all be referred to as communication devices, which can be general-purpose devices or special-purpose devices. This application does not specifically limit them.
  • the terminal device or network device includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer.
  • the hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also referred to as main memory).
  • the operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows.
  • the application layer includes applications such as browsers, address books, word processing software, and instant messaging software.
  • this embodiment does not specifically limit the structure of the execution entity of the method provided in this embodiment, as long as it can communicate according to the method provided in this embodiment by running a program that records the code of the method provided in this embodiment.
  • the execution entity of the method provided in this embodiment can be a terminal device or a network device, or a functional module in the terminal device or network device that can call and execute a program.
  • computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.).
  • magnetic storage devices e.g., hard disks, floppy disks, or magnetic tapes
  • optical discs e.g., compact discs (CDs), digital versatile discs (DVDs), etc.
  • smart cards e.g., compact discs (CDs), digital versatile discs (DVDs), etc.
  • flash memory devices e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.
  • the various storage media described herein may represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.
  • network devices and terminal devices included in the network architecture shown in Figure 1A are merely examples, and the embodiments of this application are not limited thereto.
  • it may also include more or fewer terminal devices communicating with network devices.
  • it may also include more or fewer core network devices communicating with network devices.
  • they are not described one by one in the accompanying drawings.
  • network devices and terminal devices are shown in the network architecture shown in Figure 1A, the application scenario may not be limited to network devices and terminal devices. For example, it may also include devices for carrying virtualized network functions. These are obvious to those skilled in the art and will not be described in detail here.
  • This application does not limit the location of the terminal equipment and network equipment; the terminal equipment and network equipment can be in a fixed state or in a mobile state.
  • the terminal equipment and network equipment can be deployed on land, or on water, in the air, etc.
  • network devices deployed in the air can be referred to as non-terrestrial network devices, and network devices deployed on the ground can be referred to as terrestrial network devices.
  • An NTN communication system includes at least one non-terrestrial network device, while network devices in a terrestrial communication system are all terrestrial network devices.
  • Terrestrial network devices, relative to non-terrestrial network devices, are stationary or move at a relatively slow speed.
  • non-terrestrial network devices, relative to terrestrial network devices can be high-speed mobile network devices.
  • Non-terrestrial network equipment may include satellites, high-altitude platforms (HAPs), drones, hot air balloons, low-Earth orbit satellites, medium-Earth orbit satellites, high-Earth orbit satellites, etc., without limitation.
  • HAPs high-altitude platforms
  • the term "satellite” in this application can refer to a collection of satellites and other network equipment related to satellite communication; therefore, in this application, the descriptions “satellite” and “satellite network equipment” are equivalent.
  • the RAN node in an NTN communication system, can be a satellite base station or a satellite.
  • the architecture of the NTN communication system will be described below with reference to Figures 1B to 1C.
  • satellite base stations provide communication services to terminal devices. For example, a satellite base station transmits downlink data to a terminal device, where the data is encoded using channel coding, and the channel-coded data is then transmitted to the terminal after constellation modulation. Similarly, a terminal transmits uplink data to a satellite base station, which can also be encoded using channel coding, and the encoded data is then transmitted to the satellite base station after constellation modulation. Furthermore, as shown in Figure 1B(b), a satellite base station can also communicate with a terrestrial base station; that is, a satellite can act as both a base station and a terminal device.
  • this application can be applied to inter-satellite link communication systems. For example, communication between satellite #1 and satellite #2 as shown in Figure 1C.
  • the inter-satellite link communication system can be divided into two main parts: an acquisition, pointing, and tracking (APT) subsystem (including the APT module and APT transmitter/receiver) and a communication subsystem (including the communication module and transceiver antennas).
  • the communication subsystem is primarily responsible for the transmission of inter-satellite information and forms the core of the inter-satellite communication system.
  • the APT subsystem is mainly responsible for the acquisition, alignment, and tracking between satellites. Acquisition refers to determining the direction of arrival of the incident signal. Alignment refers to adjusting the transmitted wave to aim at the receiving direction. Tracking refers to continuously adjusting the alignment and acquisition of the APT throughout the communication process. To minimize attenuation and interference in the channel while maintaining high security and transmission rate, the APT must be adjusted in real time to continuously adapt to changes.
  • APT systems are all optical systems, which have the disadvantage of being difficult to align and requiring mechanical adjustment of the pointing.
  • Most existing communication subsystems are optical communication systems, with some microwave band systems, and most use a single high-gain antenna.
  • Existing APT systems and communication subsystems are independent systems. The disadvantages are that optical communication is susceptible to vibration and other factors, resulting in unstable data rates; millimeter-wave frequencies are low, communication capacity is low, and the antenna requires mechanical adjustment of its pointing.
  • this application can be applied to scenarios where terminal devices communicate with each other, such as IoT communication systems.
  • Figure 1D is a schematic diagram of the architecture of an IoT communication system provided in an embodiment of this application.
  • Figure 1D uses a mobile phone and a television as examples of terminal devices.
  • the mobile phone and the television establish a network connection.
  • the mobile phone transmits the content that needs to be projected onto the television to the television.
  • the television After receiving the content transmitted by the mobile phone, the television displays the content on its screen.
  • Figure 1D shows a typical application scenario for IoT wireless screen projection.
  • IoT communication systems can also be applied to virtual reality (VR) games, data encoding and decoding in applications (APPs), and other application scenarios, which are not limited here.
  • VR virtual reality
  • APPs data encoding and decoding in applications
  • an IAB may include an IAB donor, an IAB node, and terminal devices.
  • the link between the IAB donor and the IAB node is a backhaul link
  • the link between the terminal device and the IAB node is an access link.
  • This application can be applied to both parties communicating in a backhaul link or to both parties communicating in an access link.
  • communication in the backhaul link can be regarded as communication between network devices
  • communication in the access link can be regarded as communication between a network device and a terminal device.
  • a cell can be understood as a coverage area of a wireless signal identified by a network device identification code or a global cell identification code.
  • a cell is a unit for managing wireless communication resources.
  • the frequency domain resources of a cell include at least one carrier, which is a continuous frequency domain resource used to carry information.
  • the information in this application may include one or more of control information, service data, and reference signals.
  • a carrier is characterized by its carrier frequency and carrier bandwidth.
  • a cell includes at least one downlink carrier and one or more uplink carriers.
  • the downlink carrier is used to carry wireless signals transmitted from the network device to the terminal device and is also called the receive carrier.
  • the uplink carrier is used to carry wireless signals transmitted from the terminal device to the network and is also called the transmit carrier.
  • the downlink and uplink carriers of a cell can be different, meaning uplink and downlink transmissions are performed on different frequency bands.
  • the downlink and uplink carriers of a cell can be the same, meaning uplink and downlink transmissions are performed on the same frequency band.
  • a cell's carrier waves acting as both frequency and time domain resources, constitute the cell's time-frequency resources.
  • carrier waves form time-frequency resources over time.
  • the information transmitted by network devices and terminal devices within a cell is carried on these time-frequency resources.
  • downlink carrier waves and time domain resources constitute the cell's downlink time-frequency resources
  • uplink carrier waves and time domain resources constitute the cell's uplink time-frequency resources.
  • the network device sends downlink signals or downlink information to the terminal device, with the downlink information carried on the downlink channel; the terminal device sends uplink signals or uplink information to the network device, with the uplink information carried on the uplink channel.
  • the terminal device can establish a wireless connection with a cell controlled by the network device.
  • the cell with which the terminal device has established a wireless connection is called the serving cell of the terminal device.
  • the configuration of the serving cell includes uplink configuration and downlink configuration, and the uplink configuration and downlink configuration correspond to each other.
  • PBCH Physical Broadcast Channel
  • PMCH Physical Multicast Channel
  • PCFICH Physical Control Format Indicator Channel
  • PHICH Physical Hybrid ARQ Indicator Channel
  • PDSCH Physical Downlink Control Channel
  • PDCCH Physical Uplink Control Channel
  • PRACH Physical Random Access Channel
  • PUSCH Physical Uplink Shared Channel
  • PUCCH Physical Uplink Control Channel
  • PRxSCH Physical Reception Link Shared Channel
  • PRxSCH is a physical layer data channel.
  • standard protocols such as 3GPP standard protocols
  • 3GPP standard protocols describe it from the perspective of the terminal device, that is, the physical layer data channel received by the terminal device.
  • the function of this channel is similar to that of PDSCH in LTE and 5G communication systems.
  • PRxSCH may be a physical layer data channel newly introduced in future communication systems (such as 6G communication systems).
  • future communication systems such as 6G communication systems
  • future communication systems may still use PDSCH to represent the physical downlink data channel or receive data channel of the terminal device, or other channel names may be used.
  • PTxSCH Physical Transmission Link Shared Channel
  • PTxSCH is a physical layer data channel.
  • standard protocols describe it from the perspective of the terminal device, i.e., the physical layer data channel transmitted by the terminal device.
  • This channel functions similarly to the PUSCH in LTE and 5G communication systems.
  • PTxSCH could be a newly introduced physical layer data channel in future communication systems (such as 6G).
  • future communication systems such as 6G
  • future communication systems might still use PUSCH to represent the physical uplink data channel or transmission data channel of the terminal device, or they could use other channel names.
  • Terminal devices perform uplink and downlink transmissions according to the scheduling of network devices.
  • a base station can send a PDCCH to the UE, which contains downlink control information (DCI).
  • the DCI can schedule either uplink or downlink transmissions for the UE.
  • it is divided into self-carrier scheduling and cross-carrier scheduling.
  • self-carrier scheduling the DCI and the PDSCH or PUSCH scheduled by that DCI are transmitted on the same component carrier (CC).
  • CC component carrier
  • cross-carrier scheduling the DCI and the PDSCH or PUSCH scheduled by that DCI are transmitted on different CCs.
  • the scheduling carrier of self-carrier scheduling can be simply referred to as a self-scheduled carrier.
  • Carrier a is a self-scheduled carrier because it can be scheduled, that is, scheduling information is transmitted on carrier a, and the scheduling information indicates that data and/or signaling transmission is performed on carrier a.
  • the scheduled carrier of carrier a is carrier a
  • the scheduling carrier of carrier a is carrier a.
  • a self-scheduled carrier can also be called a self-scheduled (or being)-scheduled carrier.
  • the scheduling carrier for cross-carrier scheduling can be simply referred to as a cross-scheduling carrier.
  • Carrier b being a cross-scheduling carrier can mean that data and/or signaling transmission on other carriers can be scheduled on carrier b, that is, scheduling information is transmitted on carrier b, and the scheduling information instructs data and/or signaling transmission to be performed on other carriers (such as carrier c).
  • the scheduled carrier in cross-carrier scheduling can be simply referred to as cross-scheduled carrier.
  • Carrier d being a cross-scheduled carrier can mean that data and/or signaling transmission on carrier d is scheduled by another carrier, such as transmitting scheduling information on carrier e, where the scheduling information instructs data and/or signaling transmission to be performed on carrier d.
  • the scheduled carrier can be a self-scheduled (or cross-scheduled) carrier and/or a carrier that spans multiple carriers.
  • a scheduled carrier is both a self-scheduled and cross-scheduled carrier, it can be scheduled by itself or by other carriers. In other words, the scheduled carrier can be scheduled by itself or by other carriers.
  • the scheduling carrier can be a self-scheduled carrier and/or a cross-scheduled carrier.
  • the scheduling carrier can schedule itself as well as other carriers.
  • the scheduling carrier can achieve both self-carrier scheduling and cross-carrier scheduling.
  • the scheduling carrier is a downlink carrier. Therefore, the self-scheduled carrier, the cross-scheduled carrier, and the self-scheduled carrier are all downlink carriers.
  • the cross-scheduled carrier may include downlink carriers and/or uplink carriers.
  • each user selects a suitable carrier for data transmission based on their own needs and channel conditions.
  • cross-carrier scheduling the system dynamically allocates user data traffic to different carriers based on the overall network load.
  • CC and carrier are not distinguished and can be substituted for each other.
  • cell configurations may include cross-carrier scheduling configurations (such as ⁇ crossCarrierSchedulingConfig ⁇ ).
  • cross-carrier scheduling configurations may include a scheduling cell identifier (such as ⁇ schedulingCellID ⁇ ) and a carrier indication field (CIF) within the scheduled carrier.
  • the CIF indicates the carrier scheduled by the scheduled carrier, i.e., it indicates the scheduled carrier.
  • a terminal device receives the cross-carrier scheduling configuration, it can determine the carrier identifier of the scheduled carrier based on the CIF in the cross-carrier scheduling configuration and perform data transmission based on that scheduled carrier.
  • the carrier of a secondary cell can be scheduled by the carrier of another cell, and only by one carrier.
  • This other cell can be either a primary cell (Pcell) or a secondary cell.
  • a primary cell's carrier can be scheduled by itself, or by itself and the carriers of a secondary cell.
  • self-carrier scheduling and cross-carrier scheduling are a choice.
  • the cell configuration of a secondary cell is shown below:
  • SEQUENCE represents a sequence.
  • CrossCarrierSchedulingConfig represents cross-carrier scheduling configuration
  • schedulingCellInfo represents scheduling cell information.
  • CHOICE represents selection, own represents self-carrier scheduling, and other represents cross-carrier scheduling.
  • schedulingCellId represents the scheduling cell identifier.
  • cif-Presence indicates whether the CIF exists in the DCI
  • cif-InSchedulingCell indicates the value of the CIF corresponding to this cell in the scheduling cell.
  • BOOLEAN represents a Boolean type, and INTEGER represents an integer type.
  • the scheduling carrier is a downlink carrier
  • the scheduled carrier can be an uplink carrier and/or a download carrier.
  • Uplink scheduling is used to determine the carrier used for uplink transmission, i.e., the scheduled carrier is an uplink carrier.
  • Downlink scheduling is used to determine the carrier used for downlink data transmission, i.e., the scheduled carrier is a downlink carrier.
  • DCI which transmits downlink control information of one or more cells through radio network temporary identifier (RNTI) may include the following coding steps: information element multiplexing, cyclic redundancy check (CRC) scrambling, channel coding, and rate matching.
  • RNTI radio network temporary identifier
  • DCI has various formats.
  • DCI formats include DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, DCI format 2_0, DCI format 2_1, DCI format 2_2, and DCI format 2_3.
  • a scheduling message such as a Data Channel Interchange (DCI)
  • DCI Data Channel Interchange
  • the network device sends a DCI to the terminal device.
  • the terminal device performs blind detection (PDCCH) on the received DCI, during which channel estimation and data demodulation can be performed.
  • PDCH blind detection
  • the PDCCH is used to carry DCI.
  • the PDCCH monitoring occasion is the time unit used to monitor the PDCCH.
  • the network device can configure the PDCCH monitoring occasion for the terminal device.
  • the network device can send DCI to the terminal device on the PDCCH within a PDCCH monitoring occasion.
  • the terminal device detects the PDCCH within the PDCCH monitoring occasion to obtain the DCI.
  • network devices can configure PDCCH monitoring periods, PDCCH monitoring offsets, and PDCCH monitoring modes for terminal devices, enabling the terminal devices to determine the location of PDCCH monitoring opportunities. If the PDCCH monitoring period is two time slots and the monitoring offset is 1, then the monitoring opportunity can be determined to be in the second time slot within each PDCCH period.
  • the PDCCH monitoring mode is configured using a 14-bit bitmap to specify the starting symbol of the PDCCH search space in the time slot to be monitored. These 14 bits correspond one-to-one with the 14 symbols of a time slot, where the most significant bit (leftmost bit) corresponds to the first symbol of a time slot, and the least significant bit (rightmost bit) corresponds to the last symbol of the same time slot.
  • One bit in these 14 bits is used to indicate whether the corresponding symbol is the starting symbol of the PDCCH search space. For example, if the 14 bits are "10000000000000", it means that the first symbol in a time slot where PDCCH needs to be monitored is the first symbol in the PDCCH search space, and the terminal device can search for PDCCH from the search space starting from the first symbol in each time slot where PDCCH needs to be monitored. As another example, if the 14 bits are "0100000000000”, it means that the terminal device can search for PDCCH from the search space starting from the second symbol in each time slot where PDCCH needs to be monitored.
  • the number of symbols in the search space is configured in the control resource set (CORESET) time domain length configuration through the duration field. For example, if this field indicates 2, it means that the search space lasts for 2 orthogonal frequency division multiplexing (OFDM) symbols.
  • CORESET control resource set
  • a time unit can be a time range, such as a moment.
  • a time unit can also be a unit of one or more time-domain resources, which is not limited here.
  • the units of time-domain resources can include frames, subframes, slots, sub-slots, mini-slots, symbols, etc.
  • a time unit includes the time unit corresponding to the PDCCH monitoring timing, or the time unit for PDCCH blind detection.
  • the time-domain symbol can be an OFDM symbol or a Discrete Fourier Transform-Spread-OFDM (DFT-s-OFDM) symbol.
  • DFT-s-OFDM Discrete Fourier Transform-Spread-OFDM
  • the units of frequency domain resources may include subcarrier, subcarrier spacing, bandwidth, resource block (RB), resource block group (RBG), bandwidth part (BWP), etc.
  • a control resource set is a set of control information resources, containing a collection of resource grids and parameter sets (such as DCI).
  • a CORESET includes one or more control channel elements (CCEs), and a CCE can consist of multiple resource element groups (REGs) (e.g., 6 REGs).
  • a REG is a resource unit for control channel resource allocation, comprising 12 consecutive resource element (RE) positions in the frequency domain and one symbol in the time domain.
  • An RE is the smallest resource unit, comprising one symbol in the time domain and one subcarrier in the frequency domain.
  • a DCI transmission can use 1, 2, 4, or 6 CCEs.
  • the aggregation level indicates how many CCEs are allocated to a PDCCH. For example, an aggregation level of 4 means that a PDCCH is allocated 4 CCEs.
  • the protocol divides CCEs into a common search space (CSS) and a specific search space for the terminal device. Different information can be searched in different search spaces. If the aggregation level in the common search space is either 4 or 8, the terminal device can first search the DCI with a granularity of 4 CCEs, and then search the DCI with a granularity of 8 CCEs during the search (blind detection).
  • the NR protocol specifies the maximum number of PDCCH blind detections within a time slot, as shown in Table 1.
  • the maximum number of PDCCH blind detections within a time slot can be the maximum sum of the number of PDCCH blind detections on all scheduled carriers within that time slot.
  • Table 1 describes the correlation between subcarrier spacing and the maximum number of PDCCH blind detections within a time slot. As shown in Table 1, with a subcarrier spacing of 15 kHz, the maximum number of PDCCH blind detections in a time slot is 44; with a subcarrier spacing of 30 kHz, the maximum number of PDCCH blind detections in a time slot is 36; with a subcarrier spacing of 60 kHz, the maximum number of PDCCH blind detections in a time slot is 22; and with a subcarrier spacing of 120 kHz, the maximum number of PDCCH blind detections in a time slot is 20.
  • the terminal device can retrieve data from the CORESET, perform rate matching and decoding on the data sequentially, and then compare it with a specific RNTI mask using CRC checksum. If they match, it indicates that the terminal device's DCI has been detected, and the blind detection of DCI is successful. Channel estimation and data demodulation can then be performed based on the DCI to send and/or receive data. If they do not match, the above steps can be repeated for the next data location until the blind detection of DCI is successful.
  • a cell can include downlink and uplink carriers, and may also include sidecar carriers. Furthermore, the uplink and downlink carriers of one cell are uniformly scheduled by the carriers of another cell, and the DCI of uplink and downlink data is transmitted on the same scheduled carrier. It is evident that the configuration of uplink and downlink carriers is not flexible enough.
  • the scheduled carrier is semi-statically configured; if the scheduled carrier changes, it can only be reconfigured through radio resource control (RRC) signaling, resulting in significant scheduling delays and poor communication performance.
  • RRC radio resource control
  • each box represents a time unit, such as a subframe.
  • D represents downlink
  • S represents a special subframe (which includes downlink and uplink symbols)
  • U represents uplink.
  • CC1, CC2, and CC3 represent different carriers.
  • the network device configures the scheduling carrier CC2 of the terminal device as CC1, meaning the network device can schedule data transmission on CC2 using control information on CC1.
  • the network device cannot send scheduling information on CC1.
  • the network device needs to reconfigure the scheduling carrier of CC2 via RRC signaling, such as configuring the scheduling carrier CC3 for CC2.
  • the network device can send the scheduling information of CC2 to the terminal device on CC3 in the sixth time unit, that is, through DCI scheduling in the sixth time unit, uplink transmission is performed on CC2 in the eighth time unit. Because uplink transmission can only occur in the eighth time unit, it results in a large scheduling delay and poor communication performance.
  • this application proposes a communication method that can flexibly and dynamically configure the carrier, thereby improving communication performance.
  • the embodiments shown below do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of this application, as long as it is possible to communicate according to the method provided in the embodiments of this application by running a program that records the code of the method provided in the embodiments of this application.
  • the execution subject of the method provided in the embodiments of this application can be a terminal-side device (such as a terminal device) or a network-side device (such as a network device), or a functional module in the terminal-side device or network-side device that can call and execute a program.
  • This method is applicable to application scenarios involving uplink communication, downlink communication, or side-link communication.
  • FIG. 3 is an interactive schematic diagram of a communication method provided in an embodiment of this application.
  • the communication devices involved in this method may include terminal devices and network devices, as described in the network architecture shown in Figures 1A to 1E.
  • the functions performed by the terminal device may be performed by a device in the terminal device (e.g., a chip, a chip system, or a circuit), or by a device compatible with the terminal device.
  • the network device in this embodiment may be the network device in the network architecture shown in Figure 2.
  • the functions performed by the network device may be performed by a device in the network device (e.g., a chip, a chip system, or a circuit), or by a device compatible with the network device.
  • Figure 3 illustrates the receiving of configuration information by the terminal device using network device configuration information. This method includes, but is not limited to, the following steps S300 to S302, wherein:
  • network devices determine the first information.
  • the first information includes carrier group information, where the carrier group includes a scheduling carrier and a scheduled carrier, and the scheduled carrier is scheduled by at least two scheduling carriers.
  • This application does not limit the type of the first information; it can be system information, such as a system information block (SIB).
  • the first information can be higher-layer signaling, such as RRC signaling, media access control-control element (MAC-CE), etc.
  • the first information can be physical layer signaling, such as DCI.
  • the scheduled carrier is scheduled by at least two scheduling carriers, which can be replaced by: the scheduled carrier corresponding to at least two scheduling carriers; or, the scheduling carrier of the scheduled carrier includes at least two scheduling carriers; or, the scheduled carrier has at least two scheduling carriers; or, the scheduled carrier is associated with at least two scheduling carriers.
  • both the scheduling carrier and the scheduled carrier are carriers.
  • Multiple carriers in a cell can be considered as a single carrier, such as a virtual carrier, which includes virtual carriers of multiple carriers in a cell.
  • the carriers in a cell include a virtual carrier and a virtual uplink carrier.
  • the carrier group can be configured with a scheduled carrier, that is, the carrier group includes one scheduled carrier and one or more scheduled carriers of the scheduled carrier.
  • the carrier group can be configured with scheduled carriers, that is, the carrier group includes one scheduled carrier and at least two scheduled carriers of the scheduled carrier.
  • the scheduled carrier is scheduled by a scheduled carrier in at least two carrier groups, or the scheduled carrier is scheduled by at least two scheduled carriers in a carrier group. That is, when a carrier group is configured with a scheduled carrier, the carrier group includes a scheduled carrier and the scheduled carrier scheduled by that scheduled carrier, thus requiring the scheduling carrier of the scheduled carrier to be determined from at least one other carrier group. When a carrier group is configured with a scheduled carrier, both the scheduled carrier and its scheduling carrier are contained within a carrier group, thus allowing at least two scheduling carriers of the scheduled carrier to be determined from the carrier group containing the scheduled carrier.
  • a carrier group can also be referred to as a carrier resource pool.
  • Each carrier resource pool can correspond to an identifier, serving as either a carrier group identifier or a carrier resource pool identifier.
  • a carrier resource pool can include an uplink carrier resource pool and a downlink carrier resource pool.
  • the uplink carrier resource pool includes multiple uplink carriers
  • the downlink carrier resource pool includes multiple downlink carriers.
  • Each uplink carrier resource pool and downlink carrier resource pool can correspond to an identifier.
  • the information of the carrier group includes a carrier group identifier, a carrier identifier of the scheduled carrier in the carrier group, and a carrier identifier of the scheduled carrier in the carrier group.
  • the corresponding carrier and the carrier group to which that carrier belongs can be determined based on the carrier identifier.
  • the carrier identifier can also be called the carrier index, carrier number, or carrier sequence number.
  • the uplink and downlink carriers can be numbered together, or in other words, the uplink and downlink carrier numbers are combined. For example, when there are 3 uplink and 3 downlink carriers in a cell, the uplink carrier identifiers can be 0, 3, and 5, and the downlink carrier identifiers can be 1, 2, and 4.
  • uplink and downlink carriers are numbered separately, or in other words, the uplink and downlink carriers are numbered independently.
  • the uplink carrier identifier can be called the uplink carrier identifier or transmit carrier identifier, such as UL/Tx Carrier ID.
  • the downlink carrier identifier can be called the downlink carrier identifier or receive carrier identifier, such as DL/Rx carrier ID.
  • the uplink and downlink carrier identifiers can be 0, 1, and 2.
  • a cell includes one or more downlink carriers and/or one or more uplink carriers.
  • the uplink and downlink carriers may not be paired, as shown in Figure 4A, where downlink carrier 5 has no fixed paired uplink carrier, and uplink carrier 2 has no fixed paired downlink carrier.
  • Network devices can flexibly configure the carriers of terminal devices; for example, downlink carrier 0 and uplink carrier 1 can be paired, and downlink carrier 3 and uplink carrier 4 can be paired.
  • the uplink carrier is used to transmit PUCCH, PUSCH, sounding reference signal (SRS), and/or RACH, etc.
  • the downlink carrier is used to receive PDCCH, PDSCH, channel state information-reference signal (CSI-RS), and/or SSB, etc.
  • CSI-RS channel state information-reference signal
  • FIG. 5A illustrates how uplink and downlink carriers are numbered separately.
  • solid lines represent scheduled uplink carriers
  • dashed lines represent scheduled downlink carriers.
  • the starting end of an arrow indicates a scheduled carrier, and the ending end indicates a scheduled carrier.
  • the carrier identifiers for both uplink and downlink carriers range from 0 to 6.
  • Downlink carriers 0, 1, 2, 3, and 4 can be self-scheduled carriers.
  • Downlink carriers 1 and 4 can also be cross-scheduled carriers.
  • Downlink carrier 1 in addition to scheduling itself can also schedule downlink carriers 2, 3, and 5, as well as uplink carriers 0 and 1.
  • Downlink carrier 4, in addition to scheduling itself can also schedule downlink carriers 5 and 6, as well as uplink carriers 1, 2, 3, 4, 5, and 6.
  • downlink carrier 0 downlink carrier 1, downlink carrier 4 and downlink carrier 6, and uplink carrier 0, uplink carrier 2, uplink carrier 3, uplink carrier 4 and uplink carrier 5 all have only one scheduled carrier.
  • the scheduling carrier can be a self-scheduled carrier and/or a cross-scheduled carrier.
  • downlink carrier 0 downlink carrier 1, downlink carrier 2, downlink carrier 3, and downlink carrier 4 are all self-scheduled carriers.
  • Downlink carrier 1 and downlink carrier 4 can also be cross-scheduled carriers.
  • Downlink carrier 6 is a cross-scheduled carrier.
  • the scheduled carrier can be a self-scheduled carrier and/or a carrier spanning multiple scheduled carriers.
  • downlink carrier 0, downlink carrier 1, downlink carrier 2, downlink carrier 3, and downlink carrier 4 are all self-scheduled carriers.
  • Downlink carrier 2 and downlink carrier 3 can also be cross-scheduled carriers.
  • Cross-scheduled carriers also include downlink carrier 5, downlink carrier 6, uplink carrier 1, uplink carrier 2, uplink carrier 3, uplink carrier 4, and uplink carrier 5 and uplink carrier 6 are all cross-scheduled carriers.
  • the scheduling carrier when the scheduling carrier can self-schedule and cross-schedule, the configuration is more flexible compared to the prior art where a secondary cell's carrier can only be scheduled by another primary or secondary cell's carrier. Compared to the prior art where self-schedule and cross-schedule are selective in secondary cell configurations, the scheduling carrier in this application can both self-schedule and cross-schedule, offering greater flexibility.
  • FIG. 5B Please refer to Figure 5B.
  • solid lines represent scheduled uplink carriers, and dashed lines represent scheduled downlink carriers.
  • the starting end of the arrow indicates the scheduled carrier, and the ending end indicates the scheduled carrier.
  • Uplink and downlink carriers are jointly numbered. When the number of uplink and downlink carriers is 7, the downlink carrier identifiers include 0, 2, 4, 6, 8, 10, and 12.
  • the uplink carrier identifiers include 1, 3, 5, 7, 9, 11, and 13.
  • Downlink carriers 0, 2, 4, 6, and 8 are self-scheduled carriers; downlink carriers 2 and 8 are also cross-scheduled carriers.
  • Downlink carrier 2 in addition to scheduling itself can also schedule downlink carriers 4, 6, and 10, as well as uplink carriers 1 and 3.
  • Downlink carrier 8, in addition to scheduling itself can also schedule downlink carriers 10 and 12, as well as uplink carriers 3, 5, 7, 9, 11, and 13.
  • the terminal device determines the CIF of the scheduled carrier based on the location of the carrier identifier of the scheduled carrier.
  • the terminal device can determine the value of the CIF of the scheduled carrier based on the carrier identifier of the scheduled carrier configured in the first information.
  • existing technologies configure the CIF and determine the carrier identifier of the scheduled carrier based on the CIF value. Compared to existing technologies, this approach directly determines the value of the CIF of the scheduled carrier without indicating its value, improving the efficiency of determining the scheduled carrier and reducing signaling overhead.
  • the scheduled carrier defaults to a self-scheduled carrier.
  • the carrier group information can only include the carrier identifier of either the scheduled carrier or the scheduled carrier, the scheduled carrier defaults to self-scheduled, and the CIF value is 0.
  • the scheduled carriers include uplink scheduled carriers and/or downlink scheduled carriers. That is, all scheduled carriers are uplink scheduled carriers, or all are downlink scheduled carriers, or the scheduled carriers include both uplink and downlink scheduled carriers.
  • the scheduled carrier includes both uplink and downlink scheduled carriers
  • the scheduled carriers in the carrier group are not distinguished as uplink and downlink carriers.
  • the carrier group shown in Figure 5A may include the following information A:
  • “Schedulingcarriergroup” refers to a carrier group.
  • the number following “Schedulingcarriergroup” indicates the carrier group identifier. Based on this information, there are 6 carrier groups. The number following the semicolon (:) indicates the carrier identifier of the scheduled carrier within the carrier group. Based on this information, downlink carrier 0, downlink carrier 1, downlink carrier 2, downlink carrier 3, downlink carrier 4, and downlink carrier 6 are the scheduled carriers. DL represents the downlink (scheduled) carrier, and UL represents the uplink (scheduled) carrier. If the carrier group information does not include the scheduled carrier, the scheduled carrier is considered a self-scheduled carrier, i.e., downlink carrier 0, downlink carrier 2, and downlink carrier 3 are self-scheduled carriers.
  • Downlink carrier 1 in addition to self-scheduling, can also be scheduled across downlink carriers 2, 3, and 5, as well as uplink carriers and uplink carrier 1.
  • Downlink carrier 4 in addition to self-scheduling, can also be scheduled across downlink carriers 5 and 6, as well as uplink carriers 1 to 6.
  • Downlink carrier 6 cannot be self-scheduled, but can be scheduled across uplink carrier 6.
  • downlink carrier 2 corresponds to two scheduled carriers, namely downlink carrier 1 and downlink carrier 2; when the scheduled carrier is downlink carrier 3, downlink carrier 3 corresponds to two scheduled carriers, namely downlink carrier 1 and downlink carrier 3; when the scheduled carrier is downlink carrier 5, downlink carrier 5 corresponds to two scheduled carriers, namely downlink carrier 1 and downlink carrier 4; when the scheduled carrier is uplink carrier 1, uplink carrier 1 corresponds to two scheduled carriers, namely downlink carrier 1 and downlink carrier 4; when the scheduled carrier is uplink carrier 6, uplink carrier 6 corresponds to two scheduled carriers, namely downlink carrier 4 and downlink carrier 6.
  • the carrier group shown in Figure 5B may include the following information B:
  • carriergroup represents a carrier group.
  • the number after “carriergroup” indicates the carrier group identifier.
  • the number after the semicolon (:) indicates the carrier identifier of the scheduled carrier in the carrier group.
  • the scheduled carriers are downlink carrier 0, downlink carrier 2, downlink carrier 4, downlink carrier 6, downlink carrier 8, downlink carrier 10, and downlink carrier 12, and uplink carrier 1, uplink carrier 3, uplink carrier 5, uplink carrier 7, uplink carrier 9, uplink carrier 11, and uplink carrier 13.
  • the scheduled carrier is considered a self-scheduled carrier, i.e., downlink carrier 0, downlink carrier 2, and downlink carrier 8 are self-scheduled carriers.
  • Uplink carrier 1 is only scheduled by downlink carrier 2.
  • Uplink carrier 3 and uplink carrier 10 are scheduled by downlink carrier 2 and downlink carrier 8.
  • Downlink carrier 4 is scheduled by itself and downlink carrier 2.
  • Uplink carrier 5, uplink carrier 7, uplink carrier 9, and uplink carrier 11 are scheduled by downlink carrier 8.
  • Downlink carrier 6 is scheduled by itself and downlink carrier 2.
  • Uplink carrier 13 is scheduled by downlink carriers 8 and 12.
  • Information A and information B show that the number of carrier groups configured with scheduled carriers (the number of scheduled carriers) is relatively larger than the number of carrier groups configured with scheduled carriers (the number of scheduled carriers).
  • carrier groups can be configured using scheduled carriers; that is, a carrier group includes a scheduled carrier and one or more scheduled carriers of that scheduled carrier.
  • carrier 3 corresponds to two scheduled carriers, namely carrier 2 and carrier 8; when the scheduled carrier is carrier 4, carrier 4 corresponds to two scheduled carriers, namely carrier 2 and carrier 4; when the scheduled carrier is carrier 6, carrier 6 corresponds to two scheduled carriers, namely carrier 2 and carrier 6; when the scheduled carrier is carrier 10, carrier 10 corresponds to two scheduled carriers, namely carrier 2 and carrier 8; when the scheduled carrier is carrier 13, carrier 10 corresponds to two scheduled carriers, namely carrier 8 and carrier 12.
  • the carrier group can be understood as a downlink carrier group.
  • a downlink carrier group can include a scheduled carrier and one or more downlink scheduled carriers of that scheduled carrier, or it can include a downlink scheduled carrier and at least two scheduled carriers of that downlink scheduled carrier.
  • the following example illustrates a downlink carrier group including a scheduled carrier and its downlink scheduled carriers, with uplink carriers and downlink carriers numbered separately.
  • the downlink carrier group shown in Figure 5A can include the following information C:
  • ⁇ DLSchedulingcarriergroup ⁇ represents a downlink carrier group.
  • the number following ⁇ DLSchedulingcarriergroup ⁇ indicates the carrier group identifier of the downlink carrier group. Based on this information, five downlink carrier groups can be identified. Since all scheduled carriers are downlink scheduled carriers, downlink (DL) information may not be indicated in the downlink carrier group information. The number following the semicolon (:) indicates the carrier identifier of the scheduled carrier in the downlink carrier group. Based on this information, downlink carriers 0, 1, 2, 3, and 4 can be identified as downlink scheduled carriers with scheduled carriers. By default, all scheduled carriers are self-scheduled carriers, meaning downlink carriers 0 through 4 can be self-scheduled. Downlink carrier 1, in addition to self-scheduling, can also be scheduled across downlink carriers 2, 3, and 5. Downlink carrier 4, in addition to self-scheduling, can also be scheduled across downlink carriers 5 and 6.
  • downlink carrier 2 corresponds to two scheduled carriers, namely downlink carrier 1 and downlink carrier 2; when the scheduled carrier is downlink carrier 3, downlink carrier 3 corresponds to two scheduled carriers, namely downlink carrier 1 and downlink carrier 3; when the scheduled carrier is downlink carrier 5, downlink carrier 5 corresponds to two scheduled carriers, namely downlink carrier 1 and downlink carrier 4.
  • the following example illustrates a downlink carrier group, which includes a downlink scheduled carrier and its scheduling carrier, uplink carrier, and downlink carrier joint numbering.
  • the carrier group shown in Figure 5B may include the following information D:
  • DLcarriergroup represents a downlink carrier group.
  • the number following DLcarriergroup indicates the carrier group identifier of the downlink carrier group. Based on the above information, it can be determined that there are 7 downlink carrier groups. Since uplink and downlink carriers are jointly numbered, downlink (DL) information may not be indicated in the downlink carrier group information. The number after the semicolon (:) indicates the carrier identifier of the (downlink) scheduled carrier in the downlink carrier group. Based on the above information, downlink carriers 0, 2, 4, 6, 8, 10, and 12 are identified as downlink scheduled carriers with scheduled carriers.
  • the scheduled carrier is a self-scheduled carrier, meaning downlink carriers 0, 2, and 8 can all be self-scheduled.
  • Downlink carrier 10 is scheduled across downlink carriers 2 and 8.
  • Downlink carrier 12 is scheduled across downlink carrier 8.
  • Information C and information D show that the number of downlink carrier groups configured with scheduled carriers (the number of downlink scheduled carriers) is relatively larger than the number of downlink carrier groups configured with scheduled carriers (the number of scheduled carriers).
  • downlink carrier groups can be configured with scheduled carriers, meaning that a downlink carrier group includes one scheduled carrier and one or more downlink scheduled carriers of that scheduled carrier.
  • downlink carrier 4 corresponds to two scheduled carriers, namely downlink carrier 2 and downlink carrier 4; when the scheduled carrier is downlink carrier 6, downlink carrier 6 corresponds to two scheduled carriers, namely downlink carrier 2 and downlink carrier 6; when the scheduled carrier is downlink carrier 10, downlink carrier 10 corresponds to two scheduled carriers, namely downlink carrier 2 and downlink carrier 8.
  • a carrier group can be considered as an uplink carrier group.
  • An uplink carrier group can include one scheduled carrier and one or more uplink scheduled carriers, or it can include one uplink scheduled carrier and at least two scheduled carriers of that uplink scheduled carrier.
  • the uplink carrier group shown in Figure 5A can include the following information E:
  • ULSchedulingcarriergroup represents the uplink carrier group.
  • the number after ULSchedulingcarriergroup indicates the carrier group identifier of the uplink carrier group. Based on the above information, it can be determined that there are 3 uplink carrier groups. The number after the semicolon (:) indicates the carrier identifier of the scheduled carrier in the uplink carrier group. Based on the above information, it can be determined that downlink carrier 1, downlink carrier 4, and downlink carrier 6 are scheduled carriers with uplink scheduled carriers. Since the scheduled carriers are all uplink scheduled carriers, the uplink (UL) information may not be indicated in the uplink carrier group information.
  • Downlink carrier 1 can be scheduled across uplink carrier 0 and uplink carrier 1.
  • Downlink carrier 4 can be scheduled across uplink carrier 1, uplink carrier 2, uplink carrier 3, uplink carrier 4, uplink carrier 5, and uplink carrier 6.
  • Downlink carrier 6 can be scheduled across uplink carrier 6.
  • uplink carrier 1 corresponds to two scheduled carriers, namely downlink carrier 1 and downlink carrier 4; when the scheduled carrier is uplink carrier 6, uplink carrier 6 corresponds to two scheduled carriers, namely downlink carrier 4 and downlink carrier 6.
  • the carrier group shown in Figure 5B may include the following information F:
  • ULcarriergroup represents an uplink carrier group.
  • the number after ULcarriergroup indicates the carrier group identifier of the uplink carrier group. Based on the above information, it can be determined that there are 7 uplink carrier groups. Since the uplink and downlink carriers are jointly numbered, the uplink (UL) information may not be indicated in the uplink carrier group information. The number after the semicolon (:) indicates the carrier identifier of the scheduled carrier in the uplink carrier group. Based on the above information, uplink carrier 1, uplink carrier 3, uplink carrier 5, uplink carrier 7, uplink carrier 9, uplink carrier 11, and uplink carrier 13 are uplink scheduled carriers with scheduled carriers. Uplink carrier 1 can be scheduled across downlink carrier 2. Uplink carrier 3 can be scheduled across downlink carrier 2 and downlink carrier 8.
  • Uplink carrier 5, uplink carrier 7, uplink carrier 9, and uplink carrier 11 can be scheduled across downlink carrier 8.
  • Uplink carrier 13 can be scheduled across downlink carrier 8 and downlink carrier 12.
  • Information E and information F show that the number of uplink carrier groups configured with uplink scheduled carriers (the number of uplink scheduled carriers) is relatively larger than the number of uplink carrier groups configured with scheduled carriers (the number of scheduled carriers).
  • uplink carrier groups can be configured with scheduled carriers, meaning that an uplink carrier group includes one scheduled carrier and one or more uplink scheduled carriers of that scheduled carrier.
  • uplink carrier 3 corresponds to two scheduled carriers, namely downlink carrier 2 and downlink carrier 8; when the scheduled carrier is uplink carrier 13, uplink carrier 13 corresponds to two scheduled carriers, namely downlink carrier 8 and downlink carrier 12.
  • the first information includes the configuration information of the carrier's BWP.
  • the first information includes the configuration of the downlink carrier, which includes the configuration of the downlink BWP; the first information also includes the configuration of the uplink carrier, which includes the configuration of the uplink BWP.
  • the time-frequency resources of the carrier may include the synchronization signal and physical broadcast channel block (SSB) of the downlink carrier, or may include the random access channel (RACH) resources of the uplink carrier.
  • SSB physical broadcast channel block
  • RACH random access channel
  • the network device sends the first information to the terminal device.
  • the terminal device receives the first information from the network device.
  • the terminal device determines at least two scheduling carriers of the scheduled carrier based on the first information.
  • At least two scheduling carriers of the scheduled carrier can be determined, which can realize flexible scheduling of carriers, dynamically switch scheduling carriers, reduce scheduling delay and transmission delay, and improve communication performance.
  • a box represents a time unit, such as a subframe.
  • D represents downlink
  • S represents a special subframe (which includes downlink and uplink symbols)
  • U represents uplink
  • CC1, CC2, and CC3 represent different carriers.
  • the scheduling carrier of CC2 includes CC1 and CC3.
  • the network device cannot send scheduling information on CC1.
  • the network device can schedule data transmission on CC2 by sending scheduling information on CC3.
  • the network device can transmit scheduling information on CC3 in the third time unit.
  • This scheduling information can schedule the terminal device to perform uplink transmission on CC2 in the fourth time unit without receiving reconfiguration information, reducing scheduling latency and transmission latency, and improving communication performance.
  • the method further includes: the terminal device receiving second information from the network device; and the terminal device determining information about the carrier group based on the second information.
  • the network device sends a second message to the terminal device.
  • the second information may include at least one of the carrier group identifier of the first carrier group, the carrier identifier of the first scheduled carrier, and the carrier identifier of the first scheduled carrier.
  • This application does not limit the first carrier group, the first scheduled carrier, and the first scheduled carrier, nor does it limit the relationship between them.
  • it includes at least one of the following three relationships, wherein:
  • the scheduled carriers in the first carrier group in the first information include the first scheduled carrier, and the first scheduled carrier is a deactivated carrier; the second information includes the carrier identifier of the first scheduled carrier.
  • the first scheduled carrier is the scheduled carrier updated by the first carrier group, and the first scheduled carrier is an active carrier.
  • the second information includes the carrier group identifier of the first carrier group and the carrier identifier of the first scheduled carrier.
  • the following describes how the terminal device determines the carrier group information based on the second information, taking into account different relationships and different types of second information.
  • the terminal device updates the carrier identifier of the scheduling carrier in the information of the first carrier group based on the carrier group identifier of the first carrier group and the carrier identifier of the first scheduling carrier.
  • the network device configures the carrier group identifier of the (first) carrier group to be updated and the carrier identifier of the (first) scheduled carrier in that carrier group to be updated through the second information.
  • the terminal device can obtain the information of the first carrier group based on the carrier group identifier of the first carrier group in the second information, and update the carrier identifier of the scheduled carrier in the information of the first carrier group based on the carrier identifier of the first scheduled carrier in the second information, thereby updating the scheduled carrier of the first carrier group.
  • the information of the first carrier group is Schedulingcarriergroup 5:6UL:6.
  • the second information includes carrier group identifier 5 and the carrier identifier 2 of the scheduling carrier, i.e., the carrier group identifier 5 of the first carrier group and the carrier identifier 2 of the first scheduling carrier
  • the updated information of the first carrier group is Schedulingcarriergroup 5:2UL:6.
  • the carrier identifier of the scheduling carrier in the first carrier group is updated to the carrier identifier of the first scheduling carrier; that is, the scheduling carrier in the first carrier group is updated to the first scheduling carrier.
  • Not updating the carrier identifier of the scheduled carrier in the first carrier group can reduce signaling overhead, thereby allowing the scheduled carriers within it to be scheduled through the first scheduling carrier. This ensures that there are active scheduling carriers among these scheduled carriers, facilitating timely scheduling of the scheduled carriers and improving communication performance.
  • the second information when the deactivated second scheduling carrier is a self-scheduled carrier, the second information also includes the carrier identifier of the deactivated second scheduling carrier.
  • the method further includes deleting the carrier identifier of the second scheduling carrier from the information of the first carrier group.
  • the information of the first carrier group is as shown in the aforementioned information A: Schedulingcarriergroup 1:1DL:1,2,3,5; UL:0,1. If the carrier identifier of the first scheduled carrier is 2 and the carrier identifier of the second scheduled carrier is 1 in the second information, then the identifiers of the scheduled carriers in the first carrier group are updated, and the carrier identifier of the second scheduled carrier is deleted, resulting in the information of the first carrier group: Schedulingcarriergroup 1:2DL:2,3,5; UL:0,1.
  • the carrier identifier of the scheduled carrier can be deleted from the carrier group to which the scheduled carrier belongs, thereby preventing the scheduled carrier from being scheduled.
  • the terminal device deletes the carrier identifier of the first scheduled carrier from the information of the first carrier group in the first information based on the carrier identifier of the first scheduled carrier.
  • the first scheduled carrier is a deactivated scheduled carrier
  • the network device configures the carrier identifier of the deactivated (first) scheduled carrier through the second information.
  • the terminal device can delete the carrier identifier of the first scheduled carrier from the information of the first carrier group based on the carrier identifier of the first scheduled carrier in the second information.
  • the carrier identifier of the deactivated (first) scheduled carrier is 5, and the carrier group information in the first information is as shown in the aforementioned information A
  • the carrier group identifiers of the first carrier group are 1 and 4
  • the information before deleting the carrier identifier of the first scheduled carrier in the first carrier group is Scheduledcarriergroup 1:1DL:1,2,3,5; UL:0,1 and Scheduledcarriergroup 4:4DL:4,5,6; UL:1,2,3,4,5,6,
  • the information after deleting the carrier identifier of the first scheduled carrier in the first carrier group is Scheduledcarriergroup1:1DL:1,2,3; UL:0,1 and Scheduledcarriergroup 4:4DL:4,6; UL:1,2,3,4,5,6.
  • deleting the carrier identifier of the first scheduled carrier in the first carrier group avoids using the deactivated scheduled carrier to transmit data, reducing signaling overhead and improving the efficiency of data transmission.
  • the terminal device adds the carrier identifier of the first scheduled carrier to the information of the first carrier group based on the carrier group identifier of the first carrier group and the carrier identifier of the first scheduled carrier.
  • the first scheduled carrier is the active scheduled carrier.
  • the network device configures the carrier group identifier of the (first) carrier group to be updated and the carrier identifier of the (first) scheduled carrier to be updated (added) in that carrier group through the second information.
  • the terminal device can obtain the information of the first carrier group based on the carrier group identifier of the first carrier group in the second information, and add the carrier identifier of the first scheduled carrier to the information of the first carrier group based on the carrier identifier of the first scheduled carrier in the second information.
  • the carrier identifier of the first scheduled carrier is 7, and the carrier group information in the first information is as shown in the aforementioned information A
  • the information of the first carrier group before adding the carrier identifier of the first scheduled carrier is Scheduledcarriergroup 1:1DL:1,2,3,5; UL:0,1 and Scheduledcarriergroup 4:4DL:4,5,6; UL:1,2,3,4,5,6.
  • the information of the first carrier group after adding the carrier identifier of the first scheduled carrier is Scheduledcarriergroup1:1DL:1,2,3,5,7; UL:0,1 and Scheduledcarriergroup 4:4DL:4,5,6,7; UL:1,2,3,4,5,6.
  • the second scheduling carrier can be any scheduling carrier other than the first scheduling carrier, such as the scheduling carrier of the carrier group following the carrier group identifier of the first carrier group, the scheduling carrier of the carrier group with the smallest carrier group identifier, or the scheduling carrier of the carrier group corresponding to the last carrier group identifier, etc.
  • the second scheduling carrier can be configured in the second information, or obtained through predefined or other information configuration. In this way, a deactivated scheduling carrier is configured, improving configuration flexibility.
  • the second information includes the carrier identifier of the first scheduled carrier, which is a deactivated scheduled carrier.
  • Determining the carrier group information based on the second information includes: determining the carrier group identifier of the first carrier group to which the first scheduled carrier belongs based on the carrier identifier of the first scheduled carrier; obtaining the information of the first carrier group based on the carrier group identifier of the first carrier group; and deleting the carrier identifier of the first scheduled carrier from the information of the first carrier group.
  • determining the carrier group identifier of the first carrier group based on the carrier identifier of the first scheduled carrier eliminates the need to configure the carrier group identifier of the first carrier group simultaneously, saving signaling.
  • the method for determining relation two applies to carrier groups configured with scheduled carriers.
  • the second information includes a carrier group identifier of a first carrier group and/or a carrier identifier of a first scheduled carrier, where the first scheduled carrier is a deactivated carrier, and the first carrier group is the carrier group to which the first scheduled carrier in the first information belongs.
  • Determining the information of the carrier group based on the second information includes: deleting the information of the first carrier group from the first information based on the carrier group identifier of the first carrier group or the carrier identifier of the first scheduled carrier. This deletes the information of the carrier group to which the deactivated scheduled carrier belongs.
  • the method for determining relationship three applies to carrier groups configured with scheduled carriers.
  • the second information includes the carrier identifier of the activated first scheduled carrier and the carrier identifier of the scheduled carrier of the first scheduled carrier.
  • Determining the carrier group information based on the second information includes: adding information of a second carrier group to the first information based on the carrier identifier of the first scheduled carrier and the carrier identifier of the scheduled carrier of the first scheduled carrier.
  • the second carrier group can be a carrier group other than the carrier group determined by the first information.
  • a new carrier group containing the activated scheduled carrier is added, and the information of that carrier group is determined.
  • other methods may also be included.
  • the terminal device determines that the first information is invalid, or deactivates, or releases the carrier group information in the first information; for relationship two, the terminal device determines that the carrier group information in the first information is still effective. For example, for relationship one, the information of the carrier group containing the first scheduled carrier is merged.
  • the second information can be system information, such as SIB; or it can be higher-layer signaling, such as RRC signaling, MAC CE, etc.; or it can be physical layer signaling, such as DCI, etc.
  • the second information may also include the carrier identifier of the deactivated scheduling carrier.
  • the carrier identifier of the deactivated scheduling carrier can also be indicated by another type of information.
  • the second information for Relationships 1 and 3 can be understood as information other than the first information, used to indicate the information for updating the carrier group.
  • the second information for Relationship 2 can be understood as an update instruction for the first information, used to indicate the update of the information for the first carrier group in the first information.
  • configuring the scheduled carrier and the scheduled carrier in the carrier group configuration helps to determine the association between the scheduled carrier and the scheduled carrier, and also facilitates the updating of the carrier group information.
  • scheduling latency and transmission latency can be reduced, thus improving communication performance.
  • the first information is used to determine the association between the scheduled carrier and the scheduled carrier, wherein the scheduled carrier can be scheduled by at least two scheduled carriers.
  • the terminal device can determine at least two scheduled carriers for the scheduled carrier based on the association.
  • the uplink and downlink carriers may not have a fixed association.
  • the network device can configure the association between the uplink and downlink carriers, enabling flexible configuration and management of the uplink and downlink carriers.
  • This application does not limit the method for configuring the association between the scheduled carrier and the scheduled carrier in the first information, and may include at least one of the following three configuration methods, wherein:
  • the first information includes the configuration of the scheduled carrier, used to determine at least two scheduled carriers for the scheduled carrier.
  • the configuration of the scheduled carrier may include the carrier identifier of the scheduled carrier and the carrier identifier of the scheduling carrier of the scheduled carrier.
  • the configuration of the scheduled carrier includes one or more scheduling carrier indicators, each scheduling carrier indicator indicating the scheduling carrier of the scheduled carrier.
  • the cell configuration (ServingCellConfig) corresponding to the first information can be as follows:
  • carrierConfig represents the carrier configuration
  • CrossCarrierSchedulingConfig represents the cross-carrier scheduling configuration
  • schedulingCarrierInfo represents the scheduling carrier information
  • schedulingCarrierId represents the scheduling carrier identifier
  • cif-InSchedulingCarrier represents the CIF value of the scheduled carrier in the scheduling carrier
  • CarrierIndex represents the carrier identifier.
  • the scheduling carrier configured in the first information of this application can be both self-scheduled and cross-scheduled, offering greater flexibility.
  • the scheduled carrier can be configured with at least two scheduling carriers, thereby determining at least two scheduling carriers for the scheduled carrier and achieving flexible cross-carrier scheduling.
  • the first information includes the configuration of the scheduling carrier, which is used to determine the scheduled carrier of the scheduling carrier.
  • the configuration of the scheduled carrier includes the carrier identifier of the scheduled carrier and the carrier identifier of the scheduled carrier's regulated carrier.
  • the configuration of the scheduled carrier includes one or more regulated carrier indications, each indicating the regulated carrier of the scheduled carrier. If the scheduled carrier is a self-scheduled carrier, then CIF can be 0.
  • the scheduled carrier can be configured as a list of regulated carriers, such as the downstream regulated carrier list (ScheduledCarrierDL-List) and/or the upstream regulated carrier list (ScheduledCarrierUL-List).
  • the cell configuration (ServingCellConfig) corresponding to the first information can be as follows:
  • scheduledCarrierInfo represents the scheduled carrier information
  • scheduledCarrier represents the scheduled carrier
  • scheduledCarrierId represents the carrier identifier of the scheduled carrier. It can be seen that the first information of the scheduled carrier configuration can represent at least one scheduled carrier through a list of scheduled carriers.
  • the first piece of information includes a table showing the relationship between the scheduled carrier and the scheduled carrier.
  • the association table can be configured using either a joint numbering or an independent numbering method for the CIF of the uplink scheduled carrier and the CIF of the downlink scheduled carrier. For example, refer to at least one row and/or at least one column in Tables 2 and 3, where Table 2 contains the joint numbering of the CIF of the uplink scheduled carrier and the CIF of the downlink scheduled carrier, and Table 3 contains the independent numbering of the CIF of the uplink scheduled carrier and the CIF of the downlink scheduled carrier.
  • the downlink carriers are identified by carrier identifiers 0-3, and the uplink carriers by carrier identifiers 4-6.
  • the carriers with identifiers 0, 1, 2, 4, 5, and 6 have a carrier identifier of 0 as their scheduling carrier; the carriers with identifiers 0, 1, 2, and 5 have a carrier identifier of 2 as their scheduling carrier. Therefore, carriers with identifier 0 can self-schedule and cross-scheduling, scheduling a total of 6 carriers.
  • the CIF (Combined Identifier) number, ranging from 0 to 6, can be represented by 3 bits of binary, corresponding to the scheduled carriers with identifiers 0, 1, 2, 4, 5, and 6 respectively.
  • Carriers with identifier 2 can self-schedule and cross-scheduling, scheduling a total of 4 carriers. This can be represented by 2 bits of binary, with CIF values ranging from 0 to 3, corresponding to the scheduled carriers with identifiers 2, 1, 0, and 5 respectively.
  • downlink carrier 0 corresponds to two scheduled carriers, namely downlink carrier 0 and downlink carrier 2; when the scheduled carrier is downlink carrier 1, downlink carrier 1 corresponds to two scheduled carriers, namely downlink carrier 0 and downlink carrier 2; when the scheduled carrier is downlink carrier 2, downlink carrier 2 corresponds to two scheduled carriers, namely downlink carrier 0 and downlink carrier 2; when the scheduled carrier is uplink carrier 5, uplink carrier 5 corresponds to two scheduled carriers, namely downlink carrier 0 and downlink carrier 2.
  • the downlink carriers are identified by carrier identifiers 0-3, and the uplink carriers by carrier identifiers 4-6.
  • the carriers with identifiers 0, 1, 2, 4, 5, and 6 have a carrier identifier of 0 as their scheduled carrier, and the carriers with identifiers 0, 2, 3, and 5 have a carrier identifier of 2 as their scheduled carrier. Therefore, the carrier with identifier 0 can self-schedule and cross-schedule, scheduling a total of 3 uplink carriers and 3 downlink carriers.
  • the CIFs are independently numbered, with uplink and downlink CIF values ranging from 0 to 2, which can be represented using 2 bits of binary.
  • the uplink CIF values 0-2 for carrier identifier 0 correspond to the uplink scheduled carriers with identifiers 0, 1, and 2, respectively.
  • the downlink CIF values 0-2 for carrier identifier 0 correspond to the downlink scheduled carriers with identifiers 4, 5, and 6, respectively.
  • the carrier with identifier 2 can self-schedule and cross-schedule, scheduling a total of 3 downlink carriers and 1 uplink carrier.
  • the uplink CIF value and downlink CIF value of carrier identifier 2 can be represented using 2 bits.
  • the uplink CIF value of carrier identifier 2 (0-3) corresponds to the downlink scheduled carriers with carrier identifiers of 0, 2, and 3, respectively.
  • the downlink CIF value of carrier identifier 2 (0) corresponds to the uplink scheduled carrier with carrier identifier 5.
  • downlink carrier 0 corresponds to two scheduled carriers, namely downlink carrier 0 and downlink carrier 2; when the scheduled carrier is downlink carrier 2, downlink carrier 2 corresponds to two scheduled carriers, namely downlink carrier 0 and downlink carrier 2; when the scheduled carrier is uplink carrier 5, uplink carrier 5 corresponds to two scheduled carriers, namely downlink carrier 0 and downlink carrier 2.
  • the uplink and downlink carriers in the above association table are labeled jointly; however, independent labels could also be used.
  • the three methods for determining the association between the scheduling carrier and the scheduled carrier described above are merely examples; other methods for determining the association between the scheduling carrier and the scheduled carrier should be protected in this application.
  • the two types of first information described above are also examples. In reality, other forms of first information may exist; at least two scheduling carriers that can determine the scheduled carrier through the first information should be protected in this application.
  • the scheduling information of that scheduled carrier can be obtained by performing PDCCH blind detection on one of the scheduled carriers.
  • This application does not limit which scheduled carriers of the scheduled carrier are subject to PDCCH blind detection.
  • the processing complexity of the terminal equipment can be considered, as well as at least one requirement such as latency, throughput, power consumption, and coverage, to determine the carrier to be subject to PDCCH blind detection or handover.
  • PDCCH blind detection can be predefined or configured to be performed on a scheduling carrier in a time unit. While ensuring that PDCCH blind detection can be performed in each time unit to achieve data scheduling, the complexity of blind detection is reduced and the communication performance is improved.
  • the following example illustrates the method of blind detection of PDCCH using the first scheduling carrier and the first scheduled carrier of the first scheduling carrier.
  • the method further includes: the terminal device performing a blind PDCCH detection on the first scheduling carrier in the first time unit based on third information.
  • the third piece of information is configuration information or predefined information.
  • This third piece of information can be system information, such as SIB, or higher-layer signaling, such as RRC signaling, MAC CE, etc., or physical layer signaling, such as DCI, etc., without limitation.
  • the first time unit can include any time unit corresponding to the PDCCH monitoring timing, or any time unit of PDCCH blind detection.
  • This application does not limit the content of the third information.
  • N scheduling carriers in the terminal device, it can indicate the number of blind detections of the PDCCH of the scheduling carrier corresponding to the first time unit, where the number of blind detections of the PDCCH of one scheduling carrier is 1 and the number of blind detections of the PDCCH of the remaining scheduling carriers is 0; or configure the search space of one scheduling carrier corresponding to the first time unit, and the search space of the remaining scheduling carriers can be understood as not configured, so that PDCCH blind detection is not performed through the remaining scheduling carriers; or configure the carrier identifier of one scheduling carrier corresponding to the first time unit, that is, when the search space of each scheduling carrier is pre-configured, PDCCH blind detection can also be performed in the first time unit through the scheduling carrier corresponding to the carrier identifier based on the carrier identifier.
  • the third information includes at least one of the following: blind detection conditions; or carrier identifiers that are prioritized for detection; or time-domain patterns for scheduling carriers.
  • the blind detection condition can be used to determine the carrier on which the PDCCH is located for blind detection.
  • the protocol can predefine the scheduling carriers corresponding to scheduling carriers whose carrier identifiers are less than a first threshold. It can be understood that performing PDCCH blind detection on scheduling carriers that meet the blind detection condition, and not performing PDCCH blind detection on scheduling carriers that do not meet the condition, reduces the number of blind detections, thereby reducing the complexity of blind detection and saving energy consumption of the terminal equipment. Similarly, performing PDCCH blind detection on scheduling carriers with priority detection carrier identifiers, and not performing PDCCH blind detection on scheduling carriers with other carrier identifiers, reduces the number of blind detections, thereby reducing the complexity of blind detection and saving energy consumption of the terminal equipment.
  • network devices can be semi-statically configured to prioritize carrier identifiers for detection. This improves the configuration flexibility of the scheduled carriers used for updating PDCCH blind detection, facilitating the updating of scheduled carriers for PDCCH blind detection.
  • the third information may include a carrier identifier that is prioritized for detection, wherein the carrier identifier may be one or more.
  • the network device can specify a scheduled carrier to be prioritized for detection within a certain period, and perform PDCCH blind detection on that scheduled carrier during that period.
  • the network device in the second time unit, can configure the search space for the PDCCH on scheduling carriers CC1 and CC3.
  • the network device can indicate to the terminal device via third information that the scheduling carrier to be detected first is CC1, thereby indicating that the search space on CC1 should be detected first in the second time unit.
  • uplink data arrives, and there are no downlink symbols on CC1.
  • the network device can indicate to the terminal device via third information or other third information that the scheduling carrier to be detected first is CC3, thereby indicating that the search space for the PDCCH on CC3 should be detected first in the third time unit. In this way, the terminal device blindly detects the PDCCH on CC3 and performs uplink transmission.
  • both scheduling carrier CC1 and scheduling carrier CC3 are configured with PDCCH search spaces.
  • the network equipment may consider not switching the scheduling carriers, and thus can use third information or other third-party information to indicate priority detection of the PDCCH search space on CC3.
  • the network device can configure a time-domain pattern for the scheduling carrier of the first time unit.
  • the terminal device determines the scheduling carrier for PDCCH blind detection in the corresponding time unit based on this time-domain pattern.
  • This time-domain pattern can be updated via semi-static instructions.
  • the network device can also configure a time-domain pattern for the scheduling carrier that is prioritized for detection over a certain period, as shown in Figure 7.
  • the third information may include a time-domain pattern of the scheduling carrier, which may correspond to one or more scheduling carrier identifiers within a time unit.
  • the third information includes the carrier identifier of the scheduling carrier in the first time unit.
  • the third information may include: CC1, CC2, CC3, CC3, CC3, CC3, CC3, CC1, CC1, CC1.
  • the scheduling carrier that is preferentially detected in the first and third time units is CC1
  • the scheduling carrier that is preferentially detected in the fourth to seventh time units is CC3
  • the scheduling carrier that is preferentially detected in the second, eighth, and tenth time units is CC2.
  • third information are merely examples. In reality, other third information can also be included. For example, some solutions are given below.
  • the third information may include the identifier of the carrier to be detected first and the time-domain pattern of the scheduled carrier.
  • the terminal device can determine the scheduled carrier to be blindly detected in that time unit based on the identifier of the carrier to be detected first.
  • the terminal device can determine the scheduled carrier to be blindly detected in a time unit from the multiple scheduled carriers based on the time-domain pattern of the scheduled carrier.
  • the terminal device can determine the scheduled carrier to be blindly detected in a time unit based on the identifier of the carrier to be detected first and the time-domain pattern of the scheduled carrier, which can further reduce the number and complexity of the scheduled carriers to be blindly detected.
  • the third information may include blind detection conditions and the identifier of the carrier to be detected first.
  • the terminal device can determine the scheduled carrier to be blind-detected from the one or more scheduled carriers based on the identifier of the carrier to be detected first.
  • the terminal device can determine the scheduled carrier to be blind-detected from the multiple scheduled carriers based on the blind detection conditions. In this way, the terminal device can determine the scheduled carrier to be blind-detected based on the blind detection conditions and the identifier of the carrier to be detected first, which can further reduce the number and complexity of the scheduled carriers to be blind-detected.
  • the third information may include blind detection conditions and a time-domain pattern of the scheduled carrier.
  • the terminal device can determine the blind-detected scheduled carrier from the one or more scheduled carriers based on the time-domain pattern of the scheduled carrier.
  • the terminal device can determine the blind-detected scheduled carrier within that time unit based on the blind detection conditions.
  • the terminal device can determine the blind-detected scheduled carrier within a time unit based on the time-domain pattern of the scheduled carrier. In this way, the terminal device can determine the blind-detected scheduled carrier based on the blind detection conditions and the time-domain pattern of the scheduled carrier, which can further reduce the number and complexity of the blind-detected scheduled carriers.
  • the third information may include blind detection conditions, the identifier of the carrier to be detected first, and the time-domain pattern of the scheduled carrier.
  • the terminal device can determine the scheduled carrier to be blindly detected within a time unit based on the blind detection conditions, the identifier of the carrier to be detected first, and the time-domain pattern of the scheduled carrier, which can further reduce the number and complexity of the scheduled carriers to be blindly detected.
  • some scheduling carriers schedule only downlink carriers, some schedule only uplink carriers, and some schedule both uplink and downlink carriers.
  • downlink carrier 0 schedules only downlink carriers
  • downlink carrier 6 schedules only uplink carriers
  • downlink carriers 1 and 4 schedule both uplink and downlink carriers.
  • Any carrier can have two or more scheduling carriers, and each scheduling carrier schedules a different number of carriers, requiring different blind detection attempts.
  • the method further includes: the terminal device determining the number of blind PDCCH detections on the scheduling carrier based on the number of scheduled carriers of the scheduling carrier.
  • the number of blind PDCCH detections for a scheduling carrier in the embodiments of this application may refer to the number of blind PDCCH detections for a scheduling carrier within a time slot, or the number of blind PDCCH detections for a scheduling carrier within a time unit. Specifically, this application does not limit this.
  • the number of blind PDCCH checks can include the maximum number of blind PDCCH candidate checks and/or the maximum number of non-overlapping CCEs, etc., which are not limited here.
  • the maximum number of blind PDCCH candidate checks can be the maximum number of blind PDCCH checks within a time slot, or the maximum number of blind PDCCH checks within a time unit.
  • Methods for determining the number of PDCCH blind detections may include at least one of the following methods.
  • the scheduled carrier is not limited to uplink or downlink carriers. That is, the number of scheduled carriers of the scheduled carrier is the sum of the number of uplink scheduled carriers and the number of downlink scheduled carriers of the scheduled carrier. The total number of scheduled carriers is the sum of the number of all uplink scheduled carriers and the number of all downlink scheduled carriers.
  • determining the number of PDCCH blind detections on the scheduling carrier based on the number of carriers of the scheduling carrier includes: determining the total number of carriers of the scheduling carrier based on the number of carriers of the scheduling carrier; determining the blind detection ratio of the first scheduling carrier based on the number of carriers of the first scheduling carrier and the total number of carriers of the scheduling carrier; and obtaining the number of PDCCH blind detections on the first scheduling carrier based on the product of the blind detection ratio of the first scheduling carrier and the maximum number of blind detections.
  • the number of blind detections of the PDCCH on the first scheduling carrier can be the product of the blind detection ratio of the first scheduling carrier and the maximum number of blind detections. If the product has a decimal, it can be rounded up or down, and the integer obtained can be used as the number of blind detections of the PDCCH on the first scheduling carrier.
  • the maximum number of blind detections can be determined by referring to the aforementioned scheme and Table 1.
  • the blind detection ratios for carriers 0, 2, 3, and 6 are 1/19, for carrier 1 it is 6/19, for carrier 4 it is 9/19, and for carrier 5 it is 0.
  • the subcarrier spacing of carriers 0, 1, and 2 is 15kHz
  • the subcarrier spacing of carriers 3 and 4 is 30kHz
  • the subcarrier spacing of carriers 5 and 6 is 60kHz.
  • the maximum number of blind detections for carriers 0, 1, and 2 is 44.
  • the maximum number of blind detections for carriers 3 and 4 is 36, and the maximum number of blind detections for carriers 5 and 6 is 22. Therefore, the number of blind detections for PDCCH on carriers 0 and 2 is 2 (1/19*44), and the number of blind detections for PDCCH on carrier 1 is 13 (6/19*44).
  • the number of blind detections for PDCCH on carrier 3 is 1 (1/19*36), and the number of blind detections for PDCCH on carrier 4 is 17 (9/19*36).
  • the number of blind detections for PDCCH on carrier 5 is 0, and the number of blind detections for PDCCH on carrier 6 is 1 (1/19*22).
  • Method 2 The scheduled carriers are limited to downlink scheduled carriers, the number of scheduled carriers is the same as the number of downlink scheduled carriers, and the total number of scheduled carriers is the same as the total number of downlink scheduled carriers.
  • the number of PDCCH blind detections on the scheduling carrier is determined based on the number of carriers of the scheduling carrier, including: determining the total number of downlink scheduled carriers based on the number of downlink scheduled carriers of the scheduling carrier; determining the blind detection ratio of the first scheduling carrier based on the number of downlink scheduled carriers of the first scheduling carrier and the total number of downlink scheduled carriers; and obtaining the number of PDCCH blind detections on the first scheduling carrier based on the product of the blind detection ratio of the first scheduling carrier and the maximum number of blind detections.
  • the number of blind detections of the PDCCH on the first scheduling carrier can be the product of the blind detection ratio of the first scheduling carrier and the maximum number of blind detections. If the product has a decimal, it can be rounded up or down, and the integer obtained can be used as the number of blind detections of the PDCCH on the first scheduling carrier.
  • the maximum number of blind detections can be determined by referring to the aforementioned scheme and Table 1.
  • the blind detection ratios for carriers 0, 2, and 3 are 1/10, for carrier 1 it is 4/10, for carrier 4 it is 3/10, and for carriers 5 and 6 it is 0.
  • the maximum number of blind detections for carriers 0, 1, and 2 is 44.
  • the maximum number of blind detections for carriers 3 and 4 is 36, and for carriers 5 and 6 it is 22.
  • the number of blind PDCCH checks on carriers 0 and 2 is 4 (1/10*44), and the number of blind PDCCH checks on carrier 1 is 16 (4/10*44).
  • the number of blind PDCCH checks on carrier 3 is 3 (1/10*36), and the number of blind PDCCH checks on carrier 4 is 10 (3/10*36).
  • the number of blind PDCCH checks on carriers 5 and 6 is 0.
  • Method 3 The scheduled carrier is limited to the uplink scheduled carrier, the number of scheduled carriers is the same as the number of uplink scheduled carriers, and the total number of scheduled carriers is the same as the total number of uplink scheduled carriers.
  • determining the number of PDCCH blind detections on the scheduling carrier based on the number of scheduled carriers of the scheduling carrier includes: determining the total number of uplink scheduled carriers based on the number of uplink scheduled carriers of the scheduling carrier; determining the blind detection ratio of the first scheduling carrier based on the number of uplink scheduled carriers of the first scheduling carrier and the total number of uplink scheduled carriers; and obtaining the number of PDCCH blind detections on the first scheduling carrier based on the product of the blind detection ratio of the first scheduling carrier and the maximum number of blind detections.
  • the number of blind detections of the PDCCH on the first scheduling carrier can be the product of the blind detection ratio of the first scheduling carrier and the maximum number of blind detections. If the product has a decimal, it can be rounded up or down, and the integer obtained can be used as the number of blind detections of the PDCCH on the first scheduling carrier.
  • the maximum number of blind detections can be determined by referring to the aforementioned scheme and Table 1.
  • the number of blind detections for carriers 0, 2, 3, 5, and 6 is 0, the blind detection ratio for carrier 1 is 2/9, and the blind detection ratio for carrier 4 is 6/9.
  • the maximum number of blind detections for carriers 0, 1, and 2 is 44.
  • the maximum number of blind detections for carriers 3 and 4 is 36, and the maximum number of blind detections for carriers 5 and 6 is 22. Therefore, the number of blind detections for the PDCCH on carriers 0, 2, 3, 5, and 6 is 0.
  • the number of blind PDCCH checks on carrier 1 is 9 (2/9*44), the number of blind PDCCH checks on carrier 4 is 24 (6/9*36), and the number of blind PDCCH checks on carrier 6 is 2 (1/9*22).
  • a method combining methods 2 and 3, such as determining the number of PDCCH blind detections on the scheduling carrier based on the number of scheduled carriers of the scheduling carrier includes: determining the total number of uplink scheduled carriers based on the number of uplink scheduled carriers of the scheduling carrier, and determining the total number of downlink scheduled carriers based on the number of downlink scheduled carriers of the scheduling carrier; determining the uplink blind detection ratio of the first scheduling carrier based on the number of uplink scheduled carriers and the total number of uplink scheduled carriers of the first scheduling carrier, and determining the downlink blind detection ratio of the first scheduling carrier based on the number of downlink scheduled carriers and the total number of downlink scheduled carriers of the first scheduling carrier; obtaining the first number of PDCCH blind detections on the first scheduling carrier based on the product of the uplink blind detection ratio and the maximum number of blind detections, and obtaining the second number of PDCCH blind detections on the first scheduling carrier based on the
  • the number of carriers of the scheduling carrier and its scheduled carriers are: carrier 0: 1 (DL); carrier 1: 6 (4DL, 2UL); carrier 2: 1 (DL); carrier 3: 1 (DL); carrier 4: 9 (3DL, 6UL); carrier 5: 0; carrier 6: 1 (UL). Therefore, the total number of downlink scheduled carriers of the scheduling carrier is 10, and the total number of uplink scheduled carriers of the scheduling carrier is 9.
  • the maximum number of blind detections for carriers 0, 1, and 2 is 44.
  • the maximum number of blind detections for carriers 3 and 4 is 36, and the maximum number of blind detections for carriers 5 and 6 is 22.
  • the second number of blind detections for PDCCH on carriers 0 and 2 is 4, the second number of blind detections for PDCCH on carrier 1 is 16, the second number of blind detections for PDCCH on carrier 3 is 3, the second number of blind detections for PDCCH on carrier 4 is 10, and the second number of blind detections for PDCCH on carriers 5 and 6 is 0.
  • the first blind detection count for PDCCH on carriers 0, 2, 3, 5, and 6 is 0.
  • the first blind detection count for PDCCH on carrier 1 is 9, on carrier 4 it is 24, and on carrier 6 it is 2. Therefore, the total number of blind detection counts for PDCCH on carriers 0 and 2 is 4 (4+0), and on carrier 1 it is 25 (16+9).
  • the number of blind detection counts for PDCCH on carrier 3 is 3 (3+0), and on carrier 4 it is 34 (10+24).
  • the number of blind detection counts for PDCCH on carrier 5 is 0, and on carrier 6 it is 2 (0+2).
  • the method also includes: the terminal device receiving a first DCI from the network device.
  • the network device sends the first DCI to the terminal device.
  • the first DCI is used to schedule data transmission on the second scheduled carrier of the second scheduling carrier.
  • the first DCI can be understood as the DCI obtained by performing a blind PDCCH detection on the first scheduling carrier.
  • the first DCI is used to indicate whether a PDCCH blind detection is performed on the third scheduling carrier.
  • the third scheduling carrier can be understood as a carrier other than the second scheduling carrier.
  • the third scheduling carrier can schedule the scheduled carrier of the second scheduling carrier, or it can choose not to schedule the scheduled carrier of the second scheduling carrier. That is to say, the first DCI can indicate the scheduled carrier of the scheduling carrier transmitting the first DCI, and it can also indicate whether to perform PDCCH blind detection on other scheduling carriers.
  • the first DCI may include a first indication field, which is used to indicate whether other scheduled carriers are blindly detected.
  • the first indication field has 1 bit, that is, one bit.
  • a value of 0 in this bit indicates that other scheduled carriers are not blindly detected, and a value of 1 in this bit indicates that other scheduled carriers are blindly detected; or, a value of 1 in this bit indicates that other scheduled carriers are not blindly detected, and a value of 0 in this bit indicates that other scheduled carriers are blindly detected.
  • the first indication field has s bits, i.e., s bits.
  • s represents the number of other scheduled carriers indicating whether blind detection is required.
  • One bit of this first indication field corresponds to one scheduled carrier, such as scheduled carrier c.
  • a bit value of 0 corresponding to scheduled carrier c indicates no blind detection of scheduled carrier c, and a bit value of 1 corresponding to scheduled carrier c indicates blind detection of scheduled carrier c; or, a bit value of 1 corresponding to scheduled carrier c indicates no blind detection of scheduled carrier c, and a bit value of 0 corresponding to scheduled carrier c indicates blind detection of scheduled carrier c.
  • This application does not limit the scheduling carrier corresponding to each bit in the first indicator field, and they can correspond to the carrier identifier of the scheduling carrier.
  • the carrier identifier of the scheduling carrier corresponding to the 0th bit is 0; the carrier identifier of the scheduling carrier corresponding to the 1st bit is 1, etc.
  • they can correspond to the carrier identifier of the active scheduling carrier. For example, if scheduling carriers 0, 2, and 3 are active carriers, and scheduling carrier 1 is a deactivated carrier, then the carrier identifier of the scheduling carrier corresponding to the 0th bit is 0; the carrier identifier of the scheduling carrier corresponding to the 1st bit is 2; and the carrier identifier of the scheduling carrier corresponding to the 2nd bit is 3.
  • the first DCI is used to indicate whether a PDCCH blind detection is performed on the third scheduling carrier, which corresponds to the second DCI on the second scheduled carrier. That is, the first DCI can indicate the scheduled carrier of the scheduling carrier that transmits the first DCI, and it can also indicate whether to blindly detect the second DCI on the third scheduling carrier, which is used to schedule data transmission on the second scheduled carrier of the third scheduling carrier.
  • the method further includes: the terminal device receiving fourth information from the network device, wherein the fourth information includes a first-level DCI and a second-level DCI; the terminal device determining the scheduling carrier and time-frequency position of the second-level DCI based on the first-level DCI; and the terminal device determining the scheduled carrier where the data transmission occurs based on the second-level DCI.
  • the network device sends the fourth piece of information to the terminal device.
  • the first-level DCI is used to determine the scheduling carrier and time-frequency location of the second-level DCI, while the second-level DCI is used to determine the scheduled carrier where data transmission occurs.
  • This approach offers greater flexibility and facilitates carrier switching compared to existing technologies where the scheduled carrier and the scheduling carrier are indicated by the same level of DCI signaling.
  • the communication device may include a transceiver unit 801 and a processing unit 802.
  • the transceiver unit 801 may be a device with signal input (receiving) or output (transmitting) capabilities, used for signal transmission with other network devices or other components within the device.
  • the processing unit 802 can be a device with processing capabilities, and may include one or more processors.
  • the processor can be a general-purpose processor or a dedicated processor.
  • the processor can be 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 device (e.g., a host node, relay node, or chip), execute software programs, and process data from the software programs.
  • the communication device may include a terminal device or a network device.
  • the functions performed by the terminal device may be performed by a device within the terminal device (e.g., a chip, a chip system, or a circuit), or by a device compatible with the terminal device.
  • the functions performed by the network device in this embodiment may be performed by a device within the network device (e.g., a chip, a chip system, or a circuit), or by a device compatible with the network device. Examples of network devices and terminal devices are provided below.
  • the communication device When the communication device is a terminal-side device, the communication device includes:
  • Transceiver unit 801 is used to receive first information, the first information including information of the carrier group, the carrier group including a scheduled carrier and a scheduled carrier;
  • Processing unit 802 is configured to determine at least two scheduling carriers of the scheduled carrier based on the first information.
  • the scheduled carrier is scheduled by at least two of the scheduled carriers in the carrier group; or the scheduled carrier is scheduled by at least two of the scheduled carriers in the carrier group.
  • the information of the carrier group includes the carrier group identifier of the carrier group, the carrier identifier of the scheduled carrier in the carrier group, and the carrier identifier of the scheduled carrier in the carrier group.
  • the scheduled carrier includes an uplink scheduled carrier and/or a downlink scheduled carrier.
  • the transceiver unit 801 is further configured to receive second information, the second information including at least one of a carrier group identifier of a first carrier group, a carrier identifier of a first scheduled carrier, and a carrier identifier of a first scheduled carrier;
  • Processing unit 802 is also configured to determine information about the carrier group based on the second information.
  • the scheduling carrier of the first carrier group in the first information includes a deactivated carrier, the first scheduling carrier is an updated scheduling carrier of the first carrier group, and the first scheduling carrier is an active carrier; the processing unit 802 is specifically used to update the carrier identifier of the scheduling carrier in the information of the first carrier group based on the carrier group identifier of the first carrier group and the carrier identifier of the first scheduling carrier.
  • the scheduled carrier in the first carrier group in the first information includes the first scheduled carrier, and the first scheduled carrier is a deactivated carrier; the processing unit 802 is specifically used to delete the carrier identifier of the first scheduled carrier in the information of the first carrier group in the first information based on the carrier identifier of the first scheduled carrier.
  • the first scheduled carrier is the scheduled carrier updated by the first carrier group, and the first scheduled carrier is an active carrier; the processing unit 802 is specifically used to add the carrier identifier of the first scheduled carrier to the information of the first carrier group based on the carrier group identifier of the first carrier group and the carrier identifier of the first scheduled carrier.
  • the first information is used to determine the association between the scheduled carrier and the scheduled carrier.
  • the first information includes: configuration information of the scheduled carrier, which is used to determine the scheduling carrier of the scheduled carrier; or configuration information of the scheduling carrier, which is used to determine the scheduled carrier of the scheduling carrier; or an association table of the scheduling carrier and the scheduled carrier.
  • the processing unit 802 is further configured to determine the carrier indication field (CIF) of the scheduled carrier based on the location of the carrier identifier of the scheduled carrier.
  • CIF carrier indication field
  • the scheduling carrier is a self-scheduled carrier
  • the CIF is 0.
  • the scheduling carrier is a self-scheduled carrier and/or a cross-scheduled carrier.
  • the processing unit 802 is also configured to perform a physical downlink control channel (PDCCH) blind detection on the second scheduling carrier in the first time unit based on third information, wherein the third information is configuration information or predefined information.
  • PDCCH physical downlink control channel
  • the third information includes at least one of the following: blind detection conditions; or carrier identifiers for priority detection; or time-domain patterns of the scheduled carriers.
  • the processing unit 802 is further configured to determine the number of PDCCH blind detections on the scheduling carrier based on the number of carriers of the scheduled carrier.
  • the transceiver unit 801 is further configured to receive a first DCI, the first DCI being used to indicate whether a PDCCH blind detection is performed on the third scheduling carrier; or the first DCI being used to indicate whether a second DCI of a second scheduled carrier is blindly detected on the third scheduling carrier, the second scheduled carrier being scheduled by the third scheduling carrier.
  • the transceiver unit 801 is further configured to receive fourth information, which includes a first-level DCI and a second-level DCI; determine the scheduling carrier and time-frequency position of the second-level DCI based on the first-level DCI; and the processing unit 802 is further configured to determine the scheduled carrier where the data transmission is located based on the second-level DCI.
  • the communication device When the communication device is a network-side device, the communication device includes:
  • Processing unit 802 is configured to determine first information, the first information including information of the carrier group, the carrier group including a scheduling carrier and a scheduled carrier, the scheduled carrier being scheduled by at least two scheduling carriers;
  • the transceiver unit 801 is used to send the first information.
  • the scheduled carrier is scheduled by at least two of the scheduled carriers in the carrier group; or the scheduled carrier is scheduled by at least two of the scheduled carriers in the carrier group.
  • the information of the carrier group includes the carrier group identifier of the carrier group, the carrier identifier of the scheduled carrier in the carrier group, and the carrier identifier of the scheduled carrier in the carrier group.
  • the scheduled carrier includes an uplink scheduled carrier and/or a downlink scheduled carrier.
  • the transceiver unit 801 is further configured to transmit second information, the second information including at least one of a carrier group identifier of a first carrier group, a carrier identifier of a first scheduled carrier, and a carrier identifier of a first scheduled carrier.
  • the first information includes a deactivated carrier of the first carrier group
  • the first scheduled carrier is an updated scheduled carrier of the first carrier group
  • the first scheduled carrier is an active carrier.
  • the second information includes a carrier identifier of the first scheduled carrier and a carrier group identifier of the first carrier group.
  • the first information includes the first scheduled carrier in the first carrier group, and the first scheduled carrier is a deactivated carrier, and the second information includes the carrier identifier of the first scheduled carrier.
  • the first scheduled carrier is the scheduled carrier updated by the first carrier group, and the first scheduled carrier is an active carrier.
  • the second information includes the carrier identifier of the first scheduled carrier and the carrier group identifier of the first carrier group.
  • the first information is used to determine the association between the scheduled carrier and the scheduled carrier.
  • the first information includes: configuration information of the scheduled carrier, which is used to determine the scheduling carrier of the scheduled carrier; or configuration information of the scheduling carrier, which is used to determine the scheduled carrier of the scheduling carrier; or an association table of the scheduling carrier and the scheduled carrier.
  • the scheduling carrier is a self-scheduled carrier
  • the CIF is 0.
  • the scheduling carrier is a self-scheduled carrier and/or a cross-scheduled carrier.
  • the transceiver unit 801 is also used to transmit third information, which is used to instruct the first event unit to perform a PDCCH blind detection on the second scheduling carrier.
  • the third information includes at least one of the following: blind detection conditions; or carrier identifiers for priority detection; or time-domain patterns of the scheduled carriers.
  • the transceiver unit 801 is further configured to transmit a first DCI, the first DCI being used to indicate whether a PDCCH blind detection is performed on a third scheduling carrier; or the first DCI being used to indicate whether a second DCI of a second scheduled carrier is blindly detected on the third scheduling carrier, the second scheduled carrier being scheduled by the third scheduling carrier.
  • the transceiver unit 801 is also used to send fourth information, which includes a first-level DCI and a second-level DCI; the first-level DCI is used to determine the scheduling carrier and time-frequency position of the second-level DCI, and the second-level DCI is used to determine the scheduled carrier where the data transmission is located.
  • each unit can also correspond to the description of the method embodiment shown in FIG3.
  • FIG. 9 is a schematic diagram of another communication device provided in an embodiment of this application.
  • This communication device can be a terminal device or a network device.
  • the functions performed by the terminal device can be performed by a device within the terminal device (e.g., a chip, a chip system, or a circuit), or by a device compatible with the terminal device.
  • the functions performed by the network device in this embodiment can be performed by a device within the network device (e.g., a chip, a chip system, or a circuit), or by a device compatible with the network device.
  • This communication device is used to implement the methods described in the method embodiments.
  • the communication device may include a processor 111 and a storage medium 112.
  • the processor 111 may also be called a processing unit, which can implement certain control functions.
  • the storage medium 112 may also be called a storage unit or a memory. Instructions 114 are stored on the storage medium 112. The instructions 114 can be executed on the processor 111, causing the communication device to perform any of the methods described in Figure 3 of the embodiments of this application.
  • the processor 111 may include instructions 113 that can be executed on the processor 111 to cause the communication device to perform any of the methods described in FIG3 in the embodiments of this application.
  • the communication device described in the above embodiments may be a first device or a second device, but the scope of the device described in this application is not limited thereto.
  • the communication device may be a standalone device or part of a larger device.
  • the communication device may be:
  • a collection of one or more ICs wherein the collection of ICs may optionally include a storage component for storing data and/or instructions;
  • ASIC such as modems
  • the terminal device 101 includes a processor, a memory, a control circuit, an antenna, and input/output devices.
  • the processor is mainly used to process communication protocols and communication data, control the entire terminal device, execute software programs, and process the data of the software programs.
  • the memory is mainly used to store software programs and data.
  • the radio frequency circuit is mainly used for the conversion between baseband signals and radio frequency signals and the processing of radio frequency signals.
  • the antenna is mainly used for transmitting and receiving radio frequency signals in the form of electromagnetic waves.
  • Input/output devices such as touch screens, displays, and keyboards, are mainly used to receive user input data and output data to the user.
  • the processor can read the software program from the storage unit, parse and execute the instructions of the software program, and process the data of the software program.
  • the processor performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit.
  • the RF circuit processes the baseband signal to obtain the RF signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna.
  • the RF circuit receives the RF signal through the antenna. This RF signal is further converted into a baseband signal and output to the processor.
  • the processor converts the baseband signal back into data and processes the data.
  • Figure 10 shows only one memory and processor. In actual terminal devices, multiple processors and memories may exist. Memory may also be referred to as storage medium or storage device, etc., and the embodiments of this application do not limit this.
  • the processor may include a baseband processor and a central processing unit (CPU).
  • the baseband processor is mainly used to process communication protocols and communication data, while the CPU is mainly used to control the entire terminal device, execute software programs, and process the data of the software programs.
  • the processor in Figure 10 integrates the functions of a baseband processor and a CPU.
  • the baseband processor and the CPU can be independent processors interconnected via technologies such as buses.
  • the terminal device may include multiple baseband processors to adapt to different network standards, and the terminal device may include multiple CPUs to enhance its processing capabilities.
  • the various components of the terminal device can be connected via various buses.
  • the baseband processor can also be described as a baseband processing circuit or a baseband processing chip.
  • the CPU can also be described as a central processing circuit or a central processing chip.
  • the function of processing communication protocols and communication data can be built into the processor or stored in the memory unit as a software program, which is then executed by the processor to implement the baseband processing function.
  • the antenna and control circuit with transceiver functions can be considered as the transceiver unit of terminal device 101, and the processor with processing functions can be considered as the processing unit of terminal device 101.
  • the transceiver unit can also be called a transceiver, transceiver device, or transceiver apparatus.
  • the device in the transceiver unit used to implement the receiving function can be considered as a receiving unit
  • the device in the transceiver unit used to implement the transmitting function can be considered as a transmitting unit; that is, the transceiver unit includes a receiving unit and a transmitting unit.
  • the receiving unit can also be called a receiver, receiver circuit, or receiving device
  • the transmitting unit can be called a transmitter, transmitter, or transmitting circuit.
  • the aforementioned receiving unit and transmitting unit can be integrated into a single unit, or they can be multiple independent units.
  • the aforementioned receiving unit and transmitting unit can be located in one geographical location or distributed across multiple geographical locations.
  • the transceiver unit is used to perform the operations performed by the transceiver unit 801 in the above embodiment.
  • the processing unit is used to perform the operations performed by the processing unit 802 in the above embodiment.
  • the terminal device 101 can also be used to perform any method performed by the terminal device or network device in the method embodiment of FIG3 above, which will not be described in detail here.
  • This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, can implement the relevant processes in the communication method provided in the above-described method embodiments.
  • This application also provides a computer program product for storing a computer program that, when run on a computer (or processor), causes the computer to execute one or more steps of any of the aforementioned communication methods. If the constituent modules of the aforementioned devices are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • This application provides a chip, including a processor, for calling and executing instructions stored in a memory, causing a communication device on which the chip is installed to perform any of the methods described above.
  • This application embodiment also provides another chip, including: an input interface, an output interface, and a processing circuit.
  • the input interface, the output interface, and the processing circuit are connected via internal connection paths.
  • the processing circuit is used to execute any of the methods described above.
  • the chip also includes a memory.
  • the input interface, the output interface, the processor, and the memory are connected via internal connection paths.
  • the processor is used to execute code in the memory. When the code is executed, the processor is used to execute any of the methods described above.
  • This application also provides a chip system including at least one processor and a communication interface.
  • the communication interface and the at least one processor are interconnected via a circuit.
  • the at least one processor is used to run computer programs or instructions to perform any of the methods described above.
  • This chip system may be composed of chips or may include chips and other discrete devices.
  • This application also provides a communication system, which includes a terminal device and a network device.
  • a communication system which includes a terminal device and a network device.
  • Non-volatile memory can be a hard disk drive (HDD), a solid-state drive (SSD), ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory.
  • Volatile memory can be RAM, which is used as an external cache.
  • Memory is any other medium capable of carrying or storing desired program code having an instruction or data structure form and accessible by a computer, but is not limited thereto.
  • the memory in the embodiments of this application can also be a circuit or any other device capable of implementing a storage function for storing program instructions and/or data.
  • processors mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • DSPs digital signal processors
  • ASICs application-specific integrated circuits
  • FPGAs field-programmable gate arrays
  • a general-purpose processor can be a microprocessor, or any conventional processor, etc.
  • the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component
  • the memory storage module
  • the disclosed systems, apparatuses, and methods can be implemented in other ways.
  • the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods.
  • multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.
  • the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
  • the units described as separate components may or may not be physically separate.
  • the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.
  • the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
  • the steps in the methods of this application can be adjusted, combined, or deleted according to actual needs.
  • Each step in each embodiment can be partially performed (for example, the terminal device may not perform the steps performed by the terminal device in the above embodiments).
  • the execution order of different steps can be changed.
  • the embodiments described herein can be combined with other embodiments, different embodiments can be combined with each other, and different steps of different embodiments herein can be combined.
  • the modules/units in the device of this application embodiment can be merged, divided, and deleted according to actual needs.
  • it may refer to a communication protocol or specification, such as the 3GPP communication protocol.
  • including can refer to a relationship of inclusion or an equality relationship.
  • A includes B, which could mean that A includes other content besides B, or that A and B are the same content.
  • At least one of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be single or multiple.

Landscapes

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

Abstract

本申请实施例提供一种通信方法及相关装置，其中方法包括：接收第一信息；基于第一信息确定被调度载波的至少两个调度载波；第一信息包括载波组的信息，载波组包括调度载波和被调度载波。采用本申请实施例，能够灵活动态配置载波，可提高通信性能。

Description

通信方法及相关装置
本申请要求于2024年6月14日提交中国专利局、申请号为202410777371.4、申请名称为“通信方法及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及相关装置。
背景技术
一个小区的上行载波和下行载波可以被另外一个小区的载波调度，上行传输和下行传输的下行控制信息(downlink control information，DCI)在同一个调度载波中传输。但该跨载波调度不够灵活。
发明内容
本申请实施例公开了一种通信方法及相关装置，能够灵活动态配置载波，可提高通信性能。
第一方面，本申请实施例公开了第一种通信方法，可以应用于通信装置，比如终端侧通信装置，该通信装置为终端设备，或者终端设备中的装置(例如，芯片，或者芯片系统，或者电路等)，或者是能够和终端设备匹配使用的装置。该方法包括：接收第一信息，所述第一信息包括所述载波组的信息，所述载波组包括调度载波和被调度载波；基于所述第一信息确定所述被调度载波的至少两个调度载波。如此，通过载波组配置调度载波和被调度载波，能够确定被调度载波的至少两个调度载波，可实现载波的灵活调度，动态地切换调度载波，降低了调度时延和传输时延，可以提高通信性能。
第二方面，本申请实施例公开了第二种通信方法，可以应用于通信装置，比如网络侧通信装置，该通信装置可以是网络设备，或者网络设备中的装置(例如，芯片，或者芯片系统，或者电路等)，或者是能够和网络设备匹配使用的装置。或者该方法可以应用于终端设备，或者终端设备中的装置，或者是能够和终端设备匹配使用的装置。该方法包括：确定第一信息，所述第一信息包括所述载波组的信息，所述载波组包括调度载波和被调度载波，所述被调度载波对应至少两个调度载波；发送所述第一信息。如此，通过载波组配置调度载波和被调度载波，能够确定被调度载波的至少两个调度载波，可实现载波的灵活调度，动态地切换调度载波，降低了调度时延和传输时延，可以提高通信性能。
结合第一方面，或者第二方面，在一种可能的示例中，所述被调度载波被至少两个所述载波组中的调度载波调度；或者所述被调度载波被所述载波组中的至少两个调度载波调度。如此，以调度载波配置载波组时，载波组包括一个调度载波和该调度载波调度的被调度载波，从而需要从至少一个其他的载波组中确定该被调度载波的调度载波。以被调度载波配置载波组时，被调度载波和该被调度载波的调度载波都包含于一个载波组内，从而可从被调度载波所在的载波组中确定该被调度载波的至少两个调度载波。第一信息以载波组配置调度载波和被调度载波，有利于确定调度载波和被调度载波的关联关系，且有利于更新载波组的信息。在切换调度载波时，可降低调度时延和传输时延，提高了通信性能。
结合第一方面，或者第二方面，在一种可能的示例中，所述载波组的信息包括所述载波组的载波组标识、所述载波组中调度载波的载波标识和所述载波组中被调度载波的载波标识。
可选地，上行载波和下行载波可以统一编号(联合编号)的，或者上行载波和下行载波可以单独编号(独立编号)的。上行载波的载波标识可以称为上行载波标识或发送载波标识，下行载波的载波标识可以称为下行载波标识或接收载波标识。
结合第一方面，或者第二方面，在一种可能的示例中，所述被调度载波包括上行被调度载波和/或下行被调度载波。
结合第一方面，在一种可能的示例中，还包括：接收第二信息，所述第二信息包括第一载波组的载波组标识、第一调度载波的载波标识和第一被调度载波的载波标识中的至少一个；基于所述第二信息确定所述载波组的信息。可以理解，第一信息以载波组配置调度载波和被调度载波，有利于确定调度载波和被调度载波的关联关系，且有利于更新载波组的信息。该示例通过第二信息更新载波组的信息，可以降低信令开销，提高了更新效率，可以提高通信性能。
结合第二方面，在一种可能的示例中，还包括：发送第二信息，所述第二信息包括第一载波组的载波组标识、第一调度载波的载波标识和第一被调度载波的载波标识中的至少一个。如此，通过第二信息更新载波组的信息，可以降低信令开销，提高更新效率，有利于提高通信性能。
结合第一方面，在一种可能的示例中，所述第一信息中所述第一载波组的调度载波包括去激活的载波，所述第一调度载波为所述第一载波组更新的调度载波，且所述第一调度载波为激活的载波，所述第二信息包括所述第一调度载波的载波标识和所述第一载波组的载波组标识；所述基于所述第二信息确定所述载波组的信息，包括：基于所述第一载波组的载波组标识和所述第一调度载波的载波标识，更新所述第一载波组的信息中调度载波的载波标识，进而更新所述第一载波组的调度载波。如此，在第一载波组中的调度载波去激活的情况下，对第一载波组中调度载波的载波标识进行了更新，且更新为第一调度载波的载波标识，即第一载波组中的调度载波更新为第一调度载波。对第一载波组中的被调度载波的载波标识不进行更新，可以降低信令开销，从而可通过第一调度载波调度其中的被调度载波，使得这些被调度载波存在激活的调度载波，有利于即时调度被调度载波，便于提高通信性能。
结合第一方面，在一种可能的示例中，所述第一信息中所述第一载波组中的被调度载波包括所述第一被调度载波，且所述第一被调度载波为去激活的载波，所述第二信息包括所述第一被调度载波的载波标识；所述基于所述第二信息确定所述载波组的信息，包括：在所述第一载波组的信息中删除所述第一被调度载波的载波标识。如此，在第一载波组中的第一被调度载波去激活的情况下，对第一载波组中第一被调度载波的载波标识进行删除，从而避免使用去激活的被调度载波传输数据，便于提高数据传输的有效性。
结合第一方面，在一种可能的示例中，所述第一被调度载波为所述第一载波组更新的被调度载波，且所述第一被调度载波为激活的载波，所述第二信息包括所述第一被调度载波的载波标识和所述第一载波组的载波组标识；所述基于所述第二信息确定所述载波组的信息，包括：基于所述第一载波组的载波组标识和所述第一被调度载波的载波标识，在所述第一载波组的信息中增加所述第一被调度载波的载波标识。如此，在增加了激活的第一被调度载波的情况下，从该第一被调度载波待增加的第一载波组中增加第一被调度载波的载波标识，从而使得调度载波能够对应更多的被调度载波，便于提高传输数据的灵活性。
结合第二方面，在一种可能的示例中，所述第一信息中所述第一载波组的调度载波包括去激活的载波，所述第一调度载波为所述第一载波组更新的调度载波，且所述第一调度载波为激活的载波，所述第二信息包括所述第一调度载波的载波标识和所述第一载波组的载波组标识。如此，可以在第一载波组中的调度载波去激活的情况下，对第一载波组中调度载波的载波标识进行了更新，且更新为第一调度载波的载波标识，即第一载波组中的调度载波更新为第一调度载波。对第一载波组中的被调度载波的载波标识不进行更新，可以降低信令开销，从而可通过第一调度载波调度其中的被调度载波，使得这些被调度载波存在激活的调度载波，有利于即时调度被调度载波，便于提高通信性能。
结合第二方面，在一种可能的示例中，所述第一信息中所述第一载波组中的被调度载波包括所述第一被调度载波，且所述第一被调度载波为去激活的载波，所述第二信息包括所述第一被调度载波的载波标识。如此，可以在第一载波组中的第一被调度载波去激活的情况下，对第一载波组中第一被调度载波的载波标识进行删除，从而避免使用去激活的被调度载波传输数据，可以降低信令开销，提高了数据传输的有效性。
结合第二方面，在一种可能的示例中，所述第一被调度载波为所述第一载波组更新的被调度载波，且所述第一被调度载波为激活的载波，所述第二信息包括所述第一被调度载波的载波标识和所述第一载波组的载波组标识。如此，可以在增加了激活的第一被调度载波的情况下，从该第一被调度载波待增加的第一载波组中增加第一被调度载波的载波标识，从而使得调度载波能够对应更多的被调度载波，便于提高传输数据的灵活性。
第三方面，本申请实施例公开了第三种通信方法，可以应用于通信装置，比如终端侧通信装置，该通信装置为终端设备，或者终端设备中的装置，或者是能够和终端设备匹配使用的装置。该方法包括：接收第一信息，所述第一信息用于确定调度载波和被调度载波的关联关系；基于所述第一信息确定所述被调度载波的至少两个调度载波。如此，终端设备可以基于关联关系确定被调度载波的至少两个调度载波。
第四方面，本申请实施例公开了第四种通信方法，可以应用于通信装置，比如网络侧通信装置，该通信装置为网络设备，或者网络设备中的装置，或者是能够和网络设备匹配使用的装置。或者该方法可以应用于终端设备，或者终端设备中的装置，或者是能够和终端设备匹配使用的装置。该方法包括：确定第一信息，所述第一信息用于确定调度载波和被调度载波的关联关系，所述被调度载波对应至少两个调度载波；发送第一信息。如此，终端设备可以基于关联关系确定被调度载波的至少两个调度载波。
结合第三方面，或者第四方面，在一种可能的示例中，所述第一信息包括：所述被调度载波的配置信息，所述被调度载波的配置信息用于确定所述被调度载波的调度载波；或者所述调度载波的配置信息，所述调度载波的配置信息用于确定所述调度载波的被调度载波；或者所述调度载波和所述被调度载波的关联关系表格。
结合第一方面，或者第二方面，或者第三方面，或者第四方面，在一种可能的示例中，还包括：基于所述被调度载波的载波标识所在的位置确定所述被调度载波的载波指示域(carrier indicator field，CIF)。如此，可基于第一信息中配置的被调度载波的载波标识确定该被调度载波的CIF的取值。而现有技术中配置CIF，基于CIF的取值确定被调度载波的载波标识。相比现有技术，可以直接确定被调度载波的CIF的取值，而无需指示被调度载波的CIF的取值，可提高确定被调度载波的效率，降低了信令开销。
结合第一方面，或者第二方面，或者第三方面，或者第四方面，在一种可能的示例中，在所述调度载波为自调度载波时，所述CIF为0。
结合第一方面，或者第二方面，或者第三方面，或者第四方面，在一种可能的示例中，所述调度载波为自调度载波和/或跨调度载波。如此，相比现有技术中辅小区的小区配置中自调度和跨调度为选择的关系，本申请的调度载波即可自调度又可以跨调度，灵活性更高。
可选地，载波无主辅之分。进一步地，下行载波之间无主辅之分；上行载波之间无主辅之分。因此，在调度载波能够自调度和跨调度时，与现有技术中一个辅小区的载波只能由另外一个主小区或辅小区的载波调度相比，配置更加灵活。
可选地，一个小区包括一个或多个下行载波，和/或一个或多个上行载波。该上行载波和下行载波可以不配对设置，即上行载波没有固定配对的下行载波，网络设备可以对终端设备的载波灵活配置。
结合第一方面，或者第三方面，在一种可能的示例中，还包括：基于第三信息在第一时间单元对第二调度载波进行物理下行控制信道(physical downlink control channel，PDCCH)盲检，所述第三信息为配置信息或预定义信息。如此，在保证每个时间单元都可以进行PDCCH盲检以实现数据调度的情况下，降低了盲检复杂度，利于提高通信性能。
结合第二方面，或者第四方面，在一种可能的示例中，还包括：发送第三信息。
结合第一方面，或者第二方面，或者第三方面，或者第四方面，在一种可能的示例中，所述第三信息包括以下至少一项：盲检条件；或者优先检测的载波标识；或者所述调度载波的时域图案。
其中，盲检条件可以用于确定对载波进行盲检的PDCCH，例如，协议可以预定义终端设备检测调度载波标识小于第一阈值的载波等。可以理解，对满足盲检条件的调度载波进行PDCCH盲检，对不满足盲检条件的调度载波不进行PDCCH盲检，降低了盲检的数量，进而降低盲检的复杂度，并可以节省终端设备的能耗。同理，对优先检测的载波标识的调度载波进行PDCCH盲检，对其余载波标识的调度载波不进行PDCCH盲检，降低了盲检的数量，进而降低盲检的复杂度，并可以节省终端设备的能耗。
可选地，网络设备可以半静态配置优先检测的载波标识。如此，提高了更新进行PDCCH盲检的调度载波的配置灵活性，利于更新进行PDCCH盲检的调度载波。
可选地，网络设备可以指示一段时间内优先检测的调度载波，在该段时间内优先检测该调度载波。也就是说，该段时间内优先对调度载波进行PDCCH盲检。
可选地，第三信息包括每个时间单元的调度载波的载波标识。
结合第一方面，或者第二方面，或者第三方面，或者第四方面，在一种可能的示例中，还包括：基于所述调度载波的被调度载波的载波个数，确定在所述调度载波上的PDCCH盲检的次数。
可选地，被调度载波不限定上行载波或下行载波，即调度载波的被调度载波的载波个数为调度载波的上行被调度载波的载波个数和下行被调度载波的载波个数之和，被调度载波的载波总数为所有的上行被调度载波的载波个数和下行被调度载波的载波个数之和。基于调度载波的被调度载波的载波个数，确定在调度载波上的PDCCH盲检的次数，包括：基于调度载波的被调度载波的载波个数确定被调度载波的载波总数，基于第一调度载波的被调度载波的载波个数和被调度载波的载波总数确定第一调度载波的盲检比例；基于第一调度载波的盲检比例和最大盲检次数的乘积，获取第一调度载波上的PDCCH盲检的次数。
其中，第一调度载波上的PDCCH盲检的次数可以为第一调度载波的盲检比例和最大盲检次数的乘积。在该乘积存在小数的情况下，可以对乘积进行向上取整或向下取整，将得到的整数作为第一调度载波上的PDCCH盲检的次数。
可选地，被调度载波限定为下行被调度载波，被调度载波的载波个数为下行被调度载波的载波个数，被调度载波的载波总数为下行被调度载波的载波总数。基于调度载波的被调度载波的载波个数，确定在调度载波上的PDCCH盲检的次数，包括：基于调度载波的下行被调度载波的载波个数确定下行被调度载波的载波总数，基于第一调度载波的下行被调度载波的载波个数和下行被调度载波的载波总数确定第一调度载波的盲检比例；基于第一调度载波的盲检比例和最大盲检次数的乘积，获取第一调度载波上的PDCCH盲检的次数。
可选地，被调度载波限定为上行被调度载波，被调度载波的载波个数为上行被调度载波的载波个数，被调度载波的载波总数为上行被调度载波的载波总数。基于调度载波的被调度载波的载波个数，确定在调度载波上的PDCCH盲检的次数，包括：基于调度载波的上行被调度载波的载波个数确定上行被调度载波的载波总数，基于第一调度载波的上行被调度载波的载波个数和上行被调度载波的载波总数确定第一调度载波的盲检比例；基于第一调度载波的盲检比例和最大盲检次数的乘积，获取第一调度载波上的PDCCH盲检的次数。
结合第一方面，或者第二方面，或者第三方面，或者第四方面，在一种可能的示例中，PDCCH盲检的次数可以包括最大盲检PDCCH候选次数(PDCCH candidates number)，和/或最大非重叠控制信道单元(control channel element，CCE)的个数(non-overlapping CCE number)。
结合第一方面，或者第三方面，在一种可能的示例中，还包括：接收第一DCI，所述第一DCI用于指示是否在第三调度载波上进行PDCCH盲检；或所述第一DCI用于指示是否在第三调度载波中盲检第二被调度载波的第二DCI，所述第二被调度载波被所述第三调度载波调度。
结合第二方面，或者第四方面，在一种可能的示例中，还包括：发送第一DCI，所述第一DCI用于指示是否在第三调度载波上进行PDCCH盲检；或所述第一DCI用于指示是否在第三调度载波中盲检第二被调度载波的第二DCI，所述第二被调度载波被所述第三调度载波调度。
在本申请实施例中，第一DCI用于调度第二调度载波的第二被调度载波上的数据传输。该第一DCI可以理解为对第一调度载波进行PDCCH盲检得到的DCI。第三调度载波可以理解为第二调度载波之外的载波。第三调度载波可以调度第二调度载波的被调度载波，或者不调度第二调度载波的被调度载波。也就是说，第一DCI可以指示传输第一DCI的调度载波的被调度载波，还可以指示是否对其他的调度载波进行PDCCH盲检。
比如，第一DCI中可以包括第一指示域，该第一指示域用于指示是否盲检其他调度载波。
可选地，第一指示域的比特数为1，即一个比特位，该比特位上的数值为0代表不盲检其他调度载波，该比特位上的数值为1代表盲检其他调度载波；或者，比特位上的数值为1代表不盲检其他调度载波，该比特位上的数值为0代表盲检其他调度载波。
可选地，第一指示域的比特数为s，即s个比特位。s为指示是否盲检的其他调度载波的载波个数。该第一指示域的一个比特位对应一个调度载波，比如调度载波c。调度载波c对应的比特位上的数值为0代表不盲检该调度载波c，调度载波c对应的比特位上的数值为1代表盲检该调度载波c；或者，调度载波c对应的比特位上的数值为1代表不盲检该调度载波c，调度载波c对应的比特位上的数值为0代表盲检该调度载波c。
结合第一方面，或者第三方面，在一种可能的示例中，还包括：接收第四信息，所述第四信息包括第一级DCI和第二级DCI；基于所述第一级DCI确定所述第二级DCI所在的调度载波和时频位置；基于所述第二级DCI确定数据传输所在的被调度载波。如此，与现有技术被调度载波和调度载波通过同一级DCI信令指示相比，灵活性更高，利于切换调度的载波。
结合第二方面，或者第四方面，在一种可能的示例中，还包括：发送第四信息，所述第四信息包括第一级DCI和第二级DCI，所述第一级DCI用于确定所述第二DCI所在的调度载波和时频位置，所述第二级DCI用于确定数据传输所在的被调度载波。如此，灵活性更高，有利于切换调度的载波。
第五方面，本申请实施例公开了一种通信装置，包括用于执行上述任一方面中或其中任意实现方法的各个步骤的单元或模块或手段(means)。
第六方面，本申请实施例公开了另一种通信装置，该通信装置可以为终端设备或网络设备，或者终端设备或网络设备中的装置，或者是能够和终端设备或网络设备匹配使用的装置。该通信装置可以包括处理器，该处理器用于通过执行存储器中的指令，或者，通过逻辑电路，使得该通信装置执行上述任一方面或任一可能的示例中的方法。
在一些可行的示例中，通信装置还包括存储器或收发器中的一项或多项，该收发器用于收发数据和/或信令。
第七方面，本申请公开了第七种通信装置，包括处理器和与处理器连接的存储器和通信接口，存储器用于存储一个或多个程序，并且被配置由处理器执行上述任一方面或任一可能的示例中的方法的步骤。
第八方面，本申请实施例公开了一种通信系统，该通信系统包括终端设备或网络设备。
第九方面，本申请实施例公开了一种计算机可读存储介质，计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述任一方面或任一可能的示例中的方法。
第十方面，本申请实施例公开了一种计算机程序产品，计算机程序产品用于存储计算机程序，当计算机程序在计算机上运行时，使得计算机执行上述任一方面或任一可能的示例中的方法。
第十一方面，本申请实施例公开了第一种芯片，包括处理器和存储器，处理器用于从存储器中调用并运行存储器中存储的指令，使得安装有芯片的设备执行上述任一方面或任一可能的示例中的方法。
第十二方面，本申请实施例公开了第二种芯片，包括：输入接口、输出接口和处理电路，输入接口、输出接口与处理电路之间通过内部连接通路相连，处理电路用于执行上述任一方面或任一可能的示例中的方法。
第十三方面，本申请实施例公开了第三种芯片，包括：输入接口、输出接口、处理器，可选地，还包括存储器，输入接口、输出接口、处理器以及存储器之间通过内部连接通路相连，处理器用于执行存储器中的代码，当代码被执行时，处理器用于执行上述任一方面或任一可能的示例中的方法。
第十四方面，本申请实施例公开了一种芯片系统，包括至少一个处理器，存储器和接口电路，存储器、收发器和至少一个处理器通过线路互联，至少一个存储器中存储有计算机程序；计算机程序被处理器执行上述任一方面或任一可能的示例中的方法。
附图说明
以下对本申请实施例用到的附图进行介绍。
图1A是本申请实施例提供的一种通信系统的构架示意图；
图1B和图1C分别是本申请实施例提供的一种NTN通信系统的构架示意图；
图1D是本申请实施例提供的一种IoT通信系统的构架示意图；
图1E是本申请实施例提供的一种IAB通信系统的构架示意图；
图2是现有技术的一种切换调度载波的示意图；
图3是本申请实施例提供的一种通信方法的流程示意图；
图4A和图4B分别是本申请实施例提供的一种载波的编号示意图；
图5A和图5B分别是本申请实施例提供的一种调度载波和被调度载波的关系示意图；
图6是本申请实施例提供的一种切换调度载波的示意图；
图7是本申请实施例提供的另一种切换调度载波的示意图；
图8是本申请实施例提供的一种通信装置的结构示意图；
图9是本申请实施例提供的另一种通信装置的结构示意图；
图10是本申请实施例提供的一种终端设备的结构示意图。
具体实施方式
本申请实施例的技术方案可以应用于各种通信系统，例如，长期演进(long term evolution，LTE)通信系统、新空口技术(new radio，NR)通信系统、高级的长期演进(LTE advanced，LTE-A)通信系统、设备到设备(device-to-device，D2D)通信系统、车联网(vehicle to everything，V2X)通信系统、机器到机器(machine to machine，M2M)通信系统、物联网(internet of things，IoT)通信系统、窄带物联网(narrow band internet of thing，NB-IoT)通信系统、感知通信一体化系统、频分双工(frequency division duplex，FDD)通信系统、时分双工(time division duplex，TDD)通信系统、非地面网络(non-terrestrial network，NTN)通信系统、无线投屏通信系统、接入回传一体化(integrated access and backhaul，IAB)通信系统、公共陆地移动网(public land mobile network，PLMN)通信系统、非公共网络(non-public network，NPN)通信系统，以及应用于5G通信系统之后演进的通信系统(如6G通信系统等)，或者可以为非(3rd generation partnership project，3GPP)通信系统等，不予限制。
为使本申请的目的、技术方案和优点更加清楚，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
请参阅图1A，图1A是本申请实施例提供的一种通信系统的网络架构示意图。如图1A所示，该通信系统可以包括终端设备101和网络设备102。其中，终端设备101可以通过无线方式与网络设备102相连。从链路的角度来说，终端设备101和终端设备101直接通信的链路为侧行链路(sidelink，SL)。终端设备101向网络设备102发送数据或信令的通信链路为上行链路(uplink，UL)，网络设备102向终端设备101发送数据或信令的通信链路为下行链路(downlink，DL)。
终端设备101与终端设备101之间可以采用某种空口技术(如NR或LTE技术等)相互通信。终端设备101与网络设备102之间也可以采用某种空口技术(如NR或LTE技术等)相互通信。终端设备101和网络设备102之间，网络设备102和网络设备102之间，以及终端设备101和终端设备101之间可以通过授权频谱(licensed spectrum或grantedspectrum)进行通信，或者可以通过免授权频谱(unlicensed spectrum或grant-freespectrum)进行通信，或者可以同时通过授权频谱和免授权频谱进行通信。本申请对终端设备101和网络设备102使用的频谱资源(频域资源)不做限定。
在本申请实施例中，终端设备101是用户侧的一种用于接收或发射信号的实体，可向用户提供语音和/或数据。终端设备或者可以称为终端(terminal)、用户设备(user equipment，UE)、接入终端、UE单元、UE站、移动设备、移动站、移动台(mobile station)、移动终端、移动客户端、移动单元(mobile unit)、远方站、远程终端、远程单元、无线单元、无线通信设备、用户代理或用户装置等。其中，接入终端可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、未来5G通信系统中的终端或者未来演进的PLMN中的终端，或者未来的NPN中的终端等。
作为示例而非限定，在本申请实施例中，终端设备101还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、衣服及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
在本申请实施例中，用于实现终端设备的功能的装置可以是终端设备，或者可以是能够支持终端设备实现该功能的装置，例如芯片系统或芯片，该装置可以被安装在终端设备中。其中，芯片系统可以由芯片构成，或者可以包括芯片和其他分立器件。
在本申请实施例中，网络设备102，可以包括(无线)接入网((radio)access network，(R)AN)设备、核心网设备(core network，CN)和数据网络设备(data network，DN)等中的至少一项。
其中，接入网设备是用于支持终端设备接入通信系统的节点或设备。也就是说，接入网给终端设备提供接入服务，以使终端设备接入(或访问)网络。接入网可以支持有线接入，还可以支持无线接入。接入网设备的主要功能包括：进行无线资源的管理、互联网协议(internet protocol，IP)头的压缩及用户数据流的加密、用户设备附着时进行移动管理实体(mobile management entity，MME)的选择、路由用户面数据至服务网关(service gateway，SGW)、寻呼消息的组织和发送、广播消息的组织和发送、以移动性或调度为目的的测量及测量报告的配置等，进而完成控制信号和用户数据在终端设备和核心网设备之间的转发。接入网设备可简称为接入网。
可选地，接入网由多个AN/RAN节点组成。AN/RAN节点可以包括但不限于：接入点(access point，AP)、增强型基站(enhance nodeB，eNB)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(baseband unit，BBU)、下一代基站(NR nodeB，gNB)、传输接收点(transmission reception point，TRP)、传输点(transmission point，TP)或某种其它接入节点，例如，无线中继节点、无线回传节点等。AN/RAN节点或者可以为一个或多个组成的天线面板，或者，还可以为构成gNB或传输点的网络节点，如BBU或分布式单元(distributed unit，DU)等，或者可以是D2D、V2X、M2M、U2U等通信系统中承担RAN功能的设备等。AN/RAN节点或者可以为云无线接入网(cloud radio access network，CRAN)场景下的无线控制器，或者可以为开放式接入网(open RAN，O-RAN或ORAN)，或者可以为5G通信系统之后演进的通信系统中的接入网，例如，6G通信系统中的xNodeB等，或者可以为5G通信系统之后演进的PLMN网络中的接入网等，在此不做限定。
可选地，将接入网设备的协议栈架构和功能分割为两部分，一部分称为集中式单元(central unit，CU)，另一部分称为DU，这类网络设备可以称为包括CU节点和DU节点的RAN设备。
在本申请实施例中，核心网设备可以连接一个或者多个接入网设备。核心网设备负责维护移动网络的签约数据，管理移动网络的网元，为终端设备提供会话管理、移动性管理、策略管理、安全认证等功能。示例性地，在终端设备附着的时候，为终端设备提供入网认证；在终端设备有业务请求时，为终端设备分配网络资源；在终端设备移动的时候，为终端设备更新网络资源；在终端设备空闲的时候，为终端设备提供快恢复机制；在终端设备去附着的时候，为终端设备释放网络资源；在终端设备有业务数据时，为终端设备提供数据路由功能，如在5G通信系统中，转发上行信息给数据网络设备；或者将从数据网络设备接收的下行信息，转发给接入网设备，以使接入网设备将该下行信息发送给终端设备。
在不同的通信系统中核心网设备可以对应不同的设备。比如，在3G通信系统中可以对应GPRS的服务支持节点(serving GPRS support node，SGSN)和/或GPRS的网关支持节点(gateway GPRS support node，GGSN)；在4G通信系统中可以对应移动性管理实体(mobility management entity，MME)和/或服务网关(serving gateway，S-GW)；在5G通信系统中可以包括控制面(control plane，CP)功能网元和用户面功能(user plane function，UPF)网元。
其中，控制面功能网元可以包括策略控制功能(policy control function，PCF)网元、统一数据管理(unified data management，UDM)网元、应用功能(application function，AF)网元、接入和移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、位置管理功能(location management function，LMF)网元等，主要完成终端设备的接入鉴权、安全加密、位置注册等功能，完成用户面传输路径的建立、释放和更改等功能。UPF网元负责管理用户面数据的传输及服务质量(quality of service，QoS)控制，流量统计等功能，可以根据会话管理网元的路由规则执行用户数据包转发，如上行信息发送到数据网络或其他用户面网元，下行信息转发到其他用户面网元或者(R)AN网元。如此，采用网络切片技术，实现网络功能分离，可以使得不同用户或用户组可以根据不同应用场景和需求，去灵活的、动态的定制网络能力。
本申请实施例并不限定核心网中各个网元的分布形式，除了以上描述的网元之外，还可以包括未描述的网元。在本申请实施例中，网元或者可以称为功能网元、功能实体、节点、设备等。网元可以是在专用硬件上实现的网络元件，也可以是在专用硬件上运行的软件实例，或者是在适当平台上虚拟化功能的实例，例如，上述虚拟化平台可以为云平台。在未来通信系统中，以上网元可以有其它的名称，本申请不做限定。
在本申请实施例中，数据网络设备用于为用户提供业务服务，一般客户端为终端设备，服务端为数据网络设备。数据网络设备所提供的数据网络可以包括私有网络，如局域网。数据网络或者可以包括不受运营商管控的外部网络，如Internet。数据网络或者可以包括运营商共同部署的专有网络，如提供互联网协议(internet protocol，IP)多媒体子系统(IP multimedia subsystem，IMS)服务的网络。
在一些实施例中，上述的终端设备、网络设备、各类网元均可以称之为通信装置，其可以是一个通用设备或者是一个专用设备，本申请实施例对此不作具体限定。
在本申请实施例中，终端设备或网络设备包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。该硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(还可称为主存)等硬件。该操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或Windows操作系统等。该应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。并且，本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是终端设备或网络设备，或者，是终端设备或网络设备中能够调用程序并执行程序的功能模块。
另外，本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
需要说明的是，图1A所示的网络架构中所包含的网络设备和终端设备的数量和类型仅仅是一种举例，本申请实施例并不限制于此。例如，还可以包括更多的或者更少的与网络设备进行通信的终端设备。又例如，还可以包括更多的或者更少的与网络设备进行通信的核心网设备。为简明描述，不在附图中一一描述。
此外，在如图1A所示的网络架构中，尽管示出了网络设备和终端设备，但是该应用场景中可以并不限于包括网络设备和终端设备，例如还可以包括用于承载虚拟化网络功能的设备等，这些对于本领域技术人员而言是显而易见的，在此不再一一赘述。
本申请对于终端设备和网络设备的位置不做限定，终端设备和网络设备可以处于固定状态，或可以处于移动状态。终端设备和网络设备可以部署在陆地上，或者可以部署在水面、空中等。
在本申请实施例中，可以将部署在空中的网络设备称为非地面网络设备，部署于地面的网络设备可以称为地面网络设备。NTN通信系统中包括至少一个非地面网络设备，地面通信系统中的网络设备均为地面网络设备。地面网络设备相对于非地面网络设备而言，是静止或移动速度较慢的网络设备。也就是说，非地面网络设备相对于地面网络设备而言，可以是高速移动的网络设备。
非地面网络设备可以包括卫星(satellite)、高空平台(high-altitude platform，HAP)、无人机、热气球、低轨卫星、中轨卫星、高轨卫星等等，在此不做限定。本申请中提及的卫星可以表示与卫星通信相关的卫星及其他网络设备的集合，因此，在本申请中，“卫星”与“卫星网络设备”这两种描述是等效的。
作为一种示例，在NTN通信系统中，RAN节点可以是卫星基站或卫星，下面结合图1B至图1C对NTN通信系统的架构进行说明。
如图1B的(a)和(b)所示，卫星基站为终端设备提供通信服务。例如，卫星基站向终端设备传输下行数据，其中数据采用信道编码进行编码，信道编码后的数据经过星座调制后传输给终端。又如，终端向卫星基站进行上行传输，上行传输也可以采用信道编码进行编码，编码后的数据经过星座调制后传输给卫星基站。另外，如图1B的(b)所示，卫星基站也可以与地面基站进行通信，即卫星可以作为基站，也可作为终端设备。
作为一种实现方式，本申请可以应用于卫星星间链路通信系统。例如，如图1C所示的卫星#1和卫星#2之间的通信。
如图1C所示，卫星星间链路通信系统可以分为：捕获瞄准跟踪(acquisition pointing and tracking，APT)子系统(包括APT模块和APT发射/接收机)和通信子系统(包括通信模块和收发天线)两大部分。其中，通信子系统主要负责星间信息的传输，通信子系统是星间通信系统的主体；APT子系统主要负责卫星之间的捕获、对准和跟踪。其中，捕获是指能够确定入射信号的来波方向。对准是指调整发射波瞄准接收方向。跟踪是指在整个通信过程中，不断APT调整对准和捕获。为了尽量减少信道中的衰减和干扰影响，同时要求具有较高的保密性和传输率，必须实时的调整APT来不断适应变化。
应理解，目前的APT系统均为光学系统，缺点在于光学对准难度大，需要机械调整指向。现有的通信子系统，多数为光通信系统，也有部分微波波段的系统，多采用单个高增益天线。现有的APT系统和通信子系统为独立的系统。缺点在于光通信容易受震动等影响，速率不稳定；毫米波频率低，通信容量低，天线需要机械调整指向。
作为又一种实现方式，本申请可以应用于终端设备与终端设备通信的场景，例如，IoT通信系统。
请参照图1D，图1D是本申请实施例提供的一种IoT通信系统的构架示意图。图1D以终端设备为手机和电视进行示例。如图1D所示，手机与电视建立网络连接。手机将需要投屏到电视上显示的内容传输给电视，电视接收到手机传输的内容之后，将该内容在显示屏上进行显示。
需要说明的是，图1D为一种典型的物联网无线投屏的应用场景。实际上，IoT通信系统还可以应用于虚拟现实(virtual reality，VR)游戏，应用程序(application，APP)中的数据编解码等应用场景，在此不做限定。
作为又一种实现方式，请参照图1E，图1E是本申请实施例提供的一种IAB通信系统的构架示意图。如图1E所示，IAB可以包括IAB父节点(IAB donor)，IAB节点(IAB node)和终端设备。IAB donor和IAB node之间的链路为回传链路(backhaul link)，终端设备和IAB node之间的链路为接入链路(access link)。本申请可以应用于回传链路中的通信双方，也可以应用于接入链路中的通信双方。该场景中，回传链路中的通信可以看作网络设备与网络设备之间的通信，接入链路中的通信可以看作网络设备与终端设备之间的通信。
应理解，上述系统应用场景仅为示例，本申请还可以适用于其他场景，此处不再一一列举。
为了便于理解本申请实施例，下面先给出本申请实施例可能出现的技术术语的定义。本申请的实施方式部分使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。
(1)小区和载波
小区可以理解为通过网络设备识别码或全球小区识别码进行标识的无线信号的覆盖区域。小区是对无线通信资源进行管理的单元，小区的频域资源包括至少一个载波，载波是用来承载信息的一块连续的频域资源。本申请中的信息可以包括控制信息、业务数据和参考信号中的一种或多种。载波以载波频点和载波带宽来表征。一个小区包括的至少一个载波中包括一个下行载波和一个或多个上行载波。下行载波用于承载网络设备向终端设备发送的无线信号，又可以称为接收载波。上行载波用于承载终端设备向网络发送的无线信号，又可以称为发送载波。根据不同的双工方式，例如，小区采用频分双工(FDD)方式时，一个小区的下行载波和上行载波可以不同，即在不同的频段上分别进行上行传输和下行传输。小区采用时分双工(TDD)方式时，一个小区的下行载波和上行载波可以相同，即在一个频段上进行上行传输和下行传输。
一个小区的载波作为频域资源与时域资源组成了该小区的时频资源，或者可以理解为载波随着时间的推移形成时频资源。网络设备与终端设备在该小区传输的信息承载在该小区的时频资源上。具体地，下行载波与时域资源组成该小区的下行时频资源，上行载波与时域资源组成了该小区的上行时频资源。
在本申请实施例中，网络设备向终端设备发送下行信号或下行信息，下行信息承载在下行信道上；终端设备向网络设备发送上行信号或上行信息，上行信息承载在上行信道上。终端设备为了与网络设备进行通信，可以与网络设备控制的小区建立无线连接。与终端设备建立了无线连接的小区称为该终端设备的服务小区。服务小区的配置包括上行配置和下行配置，且上行配置和下行配置对应。
可以理解的是，物理广播信道(physical broadcast channel，PBCH)、物理多播信道(physical multicast channel，PMCH)、物理控制格式指示信道(physical control format indicator channel，PCFICH)、物理混合自动重传(automatic repeat query，ARQ)指示信道(physical hybrid ARQ indicator channel，PHICH)、物理下行共享信道(physical downlink shared channel，PDSCH)、物理下行控制信道PDCCH在本申请的实施例中，仅作为下行数据信道、下行控制信道的一种举例，物理随机接入信道(physical random access channel，PRACH)、物理上行共享信道(physical uplink shared channel，PUSCH)和物理上行控制信道(physical uplink control channel，PUCCH)在本申请的实施例中上行数据信道和上行控制信道的一种举例，在不同的系统和不同的场景中，数据信道和控制信道可能有不同的名称，本申请的实施例对此并不作限定。
比如，物理接收链路共享信道(physical reception link shared channel，PRxSCH)。PRxSCH是一种物理层数据信道。一般地，标准协议(比如3GPP标准协议)是从终端设备的角度来描述的，即终端设备接收的物理层数据信道。该信道的功能类似与LTE通信系统和5G通信系统中的PDSCH，PRxSCH可以是在未来通信系统(比如6G通信系统)中新引入的物理层数据信道，当然未来通信系统(比如6G通信系统)也有可能依然采用PDSCH来代表终端设备的物理下行数据信道或者接收数据信道，或者，也可以采用其他信道的名称。
再比如，物理发送链路共享信道(physical transmission link shared channel，PTxSCH)。PTxSCH是一种物理层数据信道。一般地，标准协议是从终端设备的角度来描述的，即终端设备发送的物理层数据信道。该信道的功能类似与LTE通信系统和5G通信系统中的PUSCH，PTxSCH可以是在未来通信系统(比如6G通信系统)中新引入的物理层数据信道，当然未来通信系统(比如6G通信系统)也有可能依然采用PUSCH来代表终端设备的物理上行数据信道或者发送数据信道，或者，也可以采用其他信道的名称。
终端设备是根据网络设备的调度进行上行传输和下行传输。例如，基站可向UE发送PDCCH，该PDCCH中包含下行控制信息(downlink control information，DCI)，DCI可调度UE上行传输或下行传输。根据调度方式不同，分为自载波调度和跨载波调度。在自载波调度中，DCI和该DCI调度的PDSCH或PUSCH在同一个分量载波(component carrier，CC)中发送。在跨载波调度中，DCI和该DCI调度的PDSCH或PUSCH在不同的CC中发送。
在本申请实施例中，自载波调度的调度载波可以简称为自调度载波。载波a为自调度载波是指在载波a上可以调度本载波，即在载波a上传输调度信息，调度信息指示在载波a上进行数据和/或信令传输。也就是说，载波a的被调度载波为载波a，载波a的调度载波为载波a。自调度载波又可以称为自(被)调度载波。
在本申请实施例中，跨载波调度的调度载波可以简称为跨调度载波。载波b为跨调度载波可以是指在载波b上可以调度其他载波上的数据和/或信令传输，即在载波b上传输调度信息，调度信息指示在其他载波(比如载波c)上进行数据和/或信令传输。
在本申请实施例中，跨载波调度的被调度载波可以简称为跨被调度载波。载波d为跨被调度载波可以是指在载波d上的数据和/或信令传输是被另一个载波调度的，比如在载波e上传输调度信息，调度信息指示在载波d上进行数据和/或信令传输。
可选地，被调度载波可以为自(被)调度载波和/或跨被调度载波。当被调度载波既为自被调度载波又为跨被调度载波时，该被调度载波既可以被自己调度，也可以被其他载波调度。也就是说，该被调度载波既能被自载波调度，又能被跨载波调度。
可选地，调度载波可以为自调度载波和/或跨调度载波。当调度载波既为自调度载波又为跨调度载波时，该调度载波既可以调度自己，也可以调度其他载波。也就是说，调度载波既能实现自载波调度，又可以实现跨载波调度。
在本申请实施例中，调度载波为下行载波。因此，自调度载波和跨调度载波，以及自被调度载波均为下行载波。跨被调度载波可以包括下行载波和/或上行载波。
在自载波调度中，每个用户根据自身的需求和信道条件选择合适的载波进行数据传输；而在跨载波调度中，系统根据整个网络的负载情况，将用户的数据流量动态地分配到不同的载波上。通过整合这两种调度策略，可以在保证用户服务质量的同时，充分利用网络资源，降低拥塞风险，提高网络吞吐量。此外，整合后的调度方案还具有较好的扩展性和适应性，能够应对不同场景下的网络需求。
可选地，在本申请实施例的描述中，CC与载波不作区分，可相互替换。
在现有技术中，在小区配置(如servingCellConfig)中可以包括跨载波调度的配置(如crossCarierSchedulingCogfig)。该跨载波调度的配置中可以包括调度小区标识(如schedulingCellID)和在调度载波中的载波指示域CIF。其中，CIF用于指示调度载波调度的载波，即指示被调度载波。如此，终端设备接收跨载波调度的配置，可以基于跨载波调度的配置中的CIF确定被调度载波的载波标识，基于该被调度载波进行数据传输。
在现有技术中，一个辅小区(secondary cell，scell)的载波可以被另外一个小区的载波调度，且仅能被一个载波调度。该另外一个小区可以是主小区(primary cell，pcell)或辅小区。一个主小区的载波可以被自己调度，或被自己和一个辅小区的载波调度。辅小区的小区配置中自载波调度和跨载波调度为选择(choice)的关系。辅小区的小区配置如下所示：
其中，SEQUENCE表示序列。CrossCarrierSchedulingConfig表示跨载波调度配置，schedulingCellInfo表示调度小区信息。CHOICE表示选择，own表示自载波调度，other表示跨载波调度。schedulingCellId表示调度小区标识。cif-Presence表示CIF是否在DCI中存在，cif-InSchedulingCell表示该小区对应的CIF在调度小区中的取值。BOOLEAN表示布尔类型，INTEGER表示整型。
在本申请实施例中，调度载波为下行载波，被调度载波可以为上行载波和/或下载载波。上行调度用于确定上行传输使用的载波，即被调度载波为上行载波。下行调度用于确定下行数据传输使用的载波，即被调度载波为下行载波。
(2)DCI，通过无线网络临时协议(radio network temporary identifier，RNTI)传送一个或多个小区的下行链路控制信息，可以包括以下编码步骤：信息元复用、循环冗余校验(cyclic redundancy check，CRC)加扰、信道编码、速率匹配。
根据控制信息内容的不同，DCI有多种格式(format)。例如，NR中DCI格式分为DCI format 0_0、DCI format 0_1、DCI format 1_0、DCI format 1_1、DCI format 2_0、DCI format 2_1、DCI format 2_2、DCI format 2_3等。
在3GPP规定的协议版本15(Rel-15)中，两个通信装置之间进行数据传输之前会发送一个调度信息，例如，DCI等，根据该调度信息的指示进行数据传输。例如，以两个通信装置为网络设备和终端设备为例，在网络设备调度终端设备的数据信道进行数据传输之前，网络设备向终端设备发送一个DCI，终端设备对于接收到的DCI进行PDCCH盲检(blind detection)，盲检的处理过程中可进行信道估计和数据解调。
(3)PDCCH用于承载DCI，PDCCH监测时机(monitoring occasion)是用于监测PDCCH的时间单元。网络设备可以为终端设备配置PDCCH监测时机，网络设备可以在一个PDCCH监测时机内的PDCCH上向终端设备发送DCI。终端设备在PDCCH监测时机内检测PDCCH以获取DCI。
比如，网络设备可以为终端设备配置PDCCH监测周期、PDCCH监测偏移量和PDCCH监测模式，使得终端设备可以确定PDCCH监测时机的位置。如果PDCCH监测周期为2个时隙，监测偏移量为1，则可以确定监测时机位于每个PDCCH周期内的2个时隙中的第二个时隙。PDCCH监测模式是通过14比特长的位图(bitmap)配置需要监测的时隙中PDCCH搜索空间的起始符号，该14比特与一个时隙的14个符号一一对应，其中，最高位(最左边比特)对应一个时隙的第一个符号，最低位(最右边比特)对应该时隙的最后一个符号。该14比特中的一个比特用于指示对应的符号是否是PDCCH的搜索空间的起始符号，例如，该14比特为“1000000000000”，表示需要监测PDCCH的一个时隙内的第一个符号为PDCCH搜索空间的第一个符号，终端设备可以从每个需要监测PDCCH的时隙内的第一个符号开始的搜索空间内搜索PDCCH。再例如，该14比特为“0100000000000”，则表示终端设备可以从每个需要监测PDCCH的时隙内的第二个符号开始的搜索空间内搜索PDCCH。搜索空间的持续符号的个数在控制资源集合(control resource set，CORESET)时域长度配置中通过持续时间(duration)字段配置，比如该字段可以指示2，则表示搜索空间持续2个正交频分复用(orthogonal frequency division multiplexing，OFDM)符号。
在本申请实施例中，时间单元可以为一个时间范围，如时刻等。时间单元或者可以为一个或多个时域资源的单位，在此不做限定。其中，时域资源的单位可以包括帧(frame)，子帧(subframe)，时隙(slot)，子时隙(sub-slot)，迷你时隙(mini-slot)，符号(symbol)等。可选地，时间单元包括PDCCH监测时机对应的时间单元，或，PDCCH盲检的时间单元。
在本申请的实施例中，时域符号可以是OFDM符号，也可以是离散傅里叶变换扩频OFDM(discrete Fourier transform-spread-OFDM，DFT-s-OFDM)符号。如果没有特别说明，本申请实施例中的符号均指时域符号。
在本申请实施例中，频域资源的单位可以包括子载波(subcarrier)，子载波间隔，带宽，资源块(resource block，RB)，资源块组(RB group，RBG)，带宽部分(bandwidth part，BWP)等。
(4)控制资源集合CORESET，是一种控制信息的资源集合，包含资源格(resource grid)的集合，还包括一些参数集合(如DCI)。一个CORESET中包括一个或多个控制信道元素(control channel element，CCE)，一个CCE可以由多个资源元素组(resourceelement groups，REGs)(例如，6个REG)组成。其中，REG为控制信道资源分配的资源单元，在频域上包括12个连续的资源元素(resourceelement，RE)位置，时域为1个符号。RE为最小的资源单位，在时域上包括1个符号，在频域上包括1个子载波。
一个DCI传输占用的CCE的数目可以为1、2、4或6个等。聚合等级(aggregation level)表示为一个PDCCH分配了多少CCE。例如，聚合等级为4，表示一个PDCCH分配了4个CCE。在盲检时，协议将CCE划分为公共搜索空间(common search space，CSS)和终端设备的特定搜索空间(specific search space)，对于不同的信息可以在不同的搜索空间里搜索。若位于公共搜索空间里的聚合等级为4，8两种取值，则终端设备在搜索(盲检)时可以先按4个CCE为粒度搜索DCI，再按8个CCE为粒度搜索DCI。
NR协议规定了一个时隙内最大的PDCCH盲检的次数，可以参照表1。其中，一个时隙内最大的PDCCH盲检次数可以是指在该时隙内所有的调度载波上的PDCCH盲检的次数之和的最大值。
该表1用于描述子载波间隔和一个时隙内最大的PDCCH盲检的次数之间的关联关系。如表1所示，在15kHz的子载波间隔下，一个时隙的最大的PDCCH盲检的次数为44；在30kHz的子载波间隔下，一个时隙的最大的PDCCH盲检的次数为36；在60kHz的子载波间隔下，一个时隙的最大的PDCCH盲检的次数为22；在120kHz的子载波间隔下，一个时隙的最大的PDCCH盲检的次数为20。
表1
终端设备可以从CORESET内取出数据，对该数据依次进行解速率匹配以及译码，再通过CRC校验与特定的RNTI掩码进行对比，如果相同，则表示检测到终端设备的DCI，DCI的盲检成功，可以根据该DCI进行信道估计和数据解调，以发送数据和/或接收数据。如果不同，则可以对下一个位置的数据进行上述步骤，直至检测到DCI的盲检成功。
目前，一个小区可以包括下行载波和上行载波，还可以包括侧行载波。且一个小区的上行载波和下行载波统一被另外一个小区的载波调度，上下行数据的DCI在同一个调度载波中传输。可见，上行载波和下行载波的配置不够灵活。此外，调度载波是半静态配置的，如果调度的载波变更，仅可通过无线资源控制(radio resource control，RRC)信令重新配置，导致调度时延较大，通信性能差。
示例性地，请参照图2，图2中一个框格表示一个时间单元，比如时间单元为子帧。D表示下行，S表示特殊子帧(该子帧中包括下行符号和上行符号)，U表示上行。CC1、CC2和CC3表示不同的载波。如图2所示，网络设备为终端设备的CC2配置的调度载波为CC1，即网络设备可以通过在CC1上的控制信息调度CC2上的数据传输。在第3个时间单元内有上行业务到达时，因为在CC1上此时无下行传输的符号，从而网络设备无法在CC1上发送调度信息，而在CC3上有下行传输的符号，因此网络设备需要通过RRC信令重新配置CC2的调度载波，如为CC2配置调度载波CC3。而网络设备配置后可以在第6个时间单元在CC3上向终端设备发送CC2的调度信息，即通过在第6个时间单元上的DCI调度在第8个时间单元上的CC2上进行上行传输，因为在第8个时间单元才能上行传输，导致较大的调度时延，通信性能差。
基于此，本申请提出一种通信方法，能够灵活动态配置载波，可提高通信性能。
应理解，下文示出的实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可。例如，本申请实施例提供的方法的执行主体可以是终端侧装置(比如终端设备)或网络侧装置(比如网络设备)，或者，是终端侧装置或网络侧装置中能够调用程序并执行程序的功能模块。
还应理解，本申请实施例可以适用于网络侧装置和终端侧装置之间的通信，也适用于终端侧装置和终端侧装置之间的通信，也可以适用于网络侧装置和网络侧装置之间的通信，本申请对此不再限定。
该方法可适用于上行通信，下行通信或者侧行通信的应用场景。
以下实施例以网络设备和终端设备为例进行说明。
请参见图3，图3是本申请实施例提供的一种通信方法的交互示意图。该方法涉及的通信装置可以包括终端设备和网络设备，可参照图1A至图1E所示的网络架构的描述。本实施例中由终端设备执行的功能或者可以由终端设备中的装置(例如，芯片，或者芯片系统，或者电路)来执行，或者是能够和终端设备匹配使用的装置。本实施例中的网络设备可以是图2所示的网络架构中的网络设备，本实施例中由网络设备执行的功能或者可以由网络设备中的装置(例如，芯片，或者芯片系统，或者电路)来执行，或者是能够和网络设备匹配使用的装置。图3以网络设备配置信息，终端设备接收配置信息进行示例。该方法包括但不限于如下步骤S300至步骤S302，其中：
S300、网络设备确定第一信息。
在本申请实施例中，第一信息包括载波组的信息，载波组包括调度载波和被调度载波，被调度载波被至少两个调度载波调度。本申请对于第一信息的类型不做限定，第一信息可以为系统信息，比如系统信息块(systeminformation block，SIB)。或者第一信息可以为高层信令，比如RRC信令、媒体访问控制——控制元素(media access control-control element，MAC-CE)等。或者第一信息可以为物理层信令，比如DCI等。
本申请实施例中，被调度载波被至少两个调度载波调度，可以替换为：所述被调度载波对应至少两个调度载波；或者，所述被调度载波的调度载波包括至少两个；或者，所述被调度载波存在至少两个调度载波；或在，所述被调度载波与至少两个调度载波存在关联关系。
在本申请实施例中，调度载波和被调度载波均为载波。可以将一个小区中的多个载波作为一个载波，如，虚拟载波，该虚拟载波包括一个小区中的多个载波的虚拟载波。进一步地，小区中的载波包括一个虚拟载波和一个虚拟上行载波。
可以理解，将多个载波作为一个载波，可以实现符号级地动态调度，有利于提高调度效率。在一个超宽带载波中可以进行动态的频谱共享，频谱接入，频谱切换等，比如可以考虑时延，吞吐，能耗和覆盖等的需求灵活切换载波，可以选择性能最好的载波，有利于提高通信性能。
本申请对于载波组中调度载波和被调度载波的形式不做限定，载波组可以以调度载波进行配置，即载波组包括一个调度载波和该调度载波的一个或多个被调度载波。或者载波组可以以被调度载波进行配置，即载波组包括一个被调度载波和该被调度载波的至少两个调度载波。
基于这两种配置方式，在一些可行的示例中，被调度载波被至少两个载波组中的调度载波调度，或者被调度载波被载波组中的至少两个调度载波调度。也就是说，以调度载波配置载波组时，载波组包括一个调度载波和该调度载波调度的被调度载波，从而需要从至少一个其他的载波组中确定该被调度载波的调度载波。以被调度载波配置载波组时，被调度载波和该被调度载波的调度载波都包含于一个载波组内，从而可从被调度载波所在的载波组中确定该被调度载波的至少两个调度载波。
在本申请实施例中，载波组也可以称为载波资源池，每一载波资源池可以对应一个标识，作为载波组标识或载波资源池标识。进一步地，载波资源池可以包括上行载波资源池和下行载波资源池。上行载波资源池包括多个上行载波，下行载波资源池包括多个下行载波。上行载波资源池和下行载波资源池可以分别对应一个标识。
在一些可行的示例，所述载波组的信息包括所述载波组的载波组标识、所述载波组中调度载波的载波标识和所述载波组中被调度载波的载波标识。如此，可以根据载波标识确定对应的载波以及该载波所在的载波组。
其中，载波标识(carrier identifier，carrier ID)也可以称为载波序列(carrier index)，或载波编号，或载波序号。载波标识可以如图4A所示，上行载波和下行载波可以统一编号，或者说上行载波的编号和下行载波的编号为联合编号。比如，当一个小区内上行载波和下行载波的数量为3时，上行载波的载波标识可以为0、3和5，下行载波的载波标识可以为1、2和4。
载波标识可以如图4B所示，上行载波和下行载波单独编号，或者说上行载波的编号和下行载波的编号为独立编号。上行载波的载波标识可以称为上行载波标识或发送载波标识，如UL/Tx Carrier ID。下行载波的载波标识可以称为下行载波标识或接收载波标识，如DL/Rx carrier ID。当一个小区内上行载波和下行载波的数量为3时，上行载波和下行载波的载波标识可以为0、1和2。
可选地，一个小区包括一个或多个下行载波，和/或一个或多个上行载波。该上行载波和下行载波可以不配对设置，如图4A所示，下行载波5没有固定配对的上行载波，上行载波2没有固定配对的下行载波。网络设备可以对终端设备的载波灵活配置，比如下行载波0和上行载波1可以配对设置，下行载波3和上行载波4可以配对设置。
可选地，上行载波用于发送PUCCH、PUSCH、探测参考信号(sounding reference signal，SRS)、和/或、RACH等。
可选地，下行载波用于接收PDCCH、PDSCH、信道状态信息参考信号(channel state information-reference signal，CSI-RS)、和/或、SSB等。
下面以上行载波和下行载波单独编号进行示例，请参照图5A，图5A中实线表示调度上行载波，虚线表示调度下行载波。箭头的起始端表示调度载波，箭头的终止端表示被调度载波。如图5A所示，当上行载波和下行载波的数量为7时，上行载波和下行载波的载波标识均包括0至6。其中，下行载波0、下行载波1、下行载波2、下行载波3和下行载波4可以为自调度载波。下行载波1和下行载波4还可以为跨调度载波。下行载波1除了调度本身之外，还可以调度下行载波2、下行载波3和下行载波5，以及上行载波0和上行载波1。下行载波4除了调度本身之外，还可以调度下行载波5和下行载波6，以及上行载波1、上行载波2、上行载波3、上行载波4、上行载波5和上行载波6。
需要说明的是，示例中的被调度载波仅存在一个调度载波的情况。如图5A中，下行载波0、下行载波1、下行载波4和下行载波6，以及上行载波0、上行载波2、上行载波3、上行载波4和上行载波5都仅存在一个调度载波。
可选地，调度载波为自调度载波和/或跨调度载波。
示例性地，图5A中下行载波0、下行载波1、下行载波2、下行载波3和下行载波4均为自调度载波。下行载波1和下行载波4还可以为跨调度载波。下行载波6为跨调度载波。
可选地，被调度载波为自被调度载波和/或跨被调度载波。
示例性地，图5A中下行载波0、下行载波1、下行载波2、下行载波3和下行载波4均为自被调度载波。下行载波2和下行载波3还可以为跨被调度载波，跨被调度载波还包括下行载波5、下行载波6、上行载波1、上行载波2、上行载波3、上行载波4、上行载波5和上行载波6均为跨被调度载波。
在本申请实施例中，载波无主辅之分。进一步地，下行载波之间无主辅之分；上行载波之间无主辅之分。因此，在调度载波能够自调度和跨调度时，与现有技术中一个辅小区的载波只能由另外一个主小区或辅小区的载波调度相比，配置更加灵活。相比现有技术中辅小区的小区配置中自调度和跨调度为选择的关系，本申请的调度载波即可自调度又可以跨调度，灵活性更高。
请参照图5B，图5B中的实线表示调度上行载波，虚线表示调度下行载波。箭头的起始端表示调度载波，箭头的终止端表示被调度载波。上行载波和下行载波联合编号，当上行载波和下行载波的数量为7时，下行载波的载波标识包括0、2、4、6、8、10和12。上行载波的载波标识包括1、3、5、7、9、11和13。其中，下行载波0、下行载波2、下行载波4、下行载波6和下行载波8为自调度载波，下行载波2和下行载波8还为跨调度载波。下行载波2除了调度本身之外，还可以调度下行载波4、下行载波6和下行载波10，以及上行载波1和上行载波3。下行载波8除了调度本身之外，还可以调度下行载波10和下行载波12，以及上行载波3、上行载波5、上行载波7、上行载波9、上行载波11和上行载波13。
在一些可行的示例中，终端设备基于被调度载波的载波标识所在的位置确定被调度载波的CIF。如此，终端设备可基于第一信息中配置的被调度载波的载波标识确定该被调度载波的CIF的取值。而现有技术中配置CIF，基于CIF的取值确定被调度载波的载波标识。相比现有技术，可以直接确定被调度载波的CIF的取值，而无需指示被调度载波的CIF的取值，可提高确定被调度载波的效率，降低了信令开销。
可选地，载波组的信息不包括调度载波和被调度载波中的一个载波标识时，调度载波默认为自调度载波。也就是说，载波组的信息仅可以包括调度载波和被调度载波中的一个载波标识时，调度载波默认为自调度，CIF的取值为0。
可选地，被调度载波包括上行被调度载波和/或下行被调度载波。也就是说，被调度载波均为上行被调度载波，或者均为下行被调度载波，或者被调度载波包括上行被调度载波和下行被调度载波。
针对被调度载波包括上行被调度载波和下行被调度载波的情况，可以理解为载波组中的被调度载波不区分上行载波和下行载波。以载波组包括一个调度载波和该调度载波的被调度载波、上行载波和下行载波单独编号进行示例，图5A所示的载波组可以包括如下的信息A：
Schedulingcarriergroup 0:0
Schedulingcarriergroup 1:1DL:1,2,3,5；UL:0,1
Schedulingcarriergroup 2:2
Schedulingcarriergroup 3:3
Schedulingcarriergroup 4:4DL:4,5,6；UL:1,2,3,4,5,6
Schedulingcarriergroup 5:6UL:6
其中，Schedulingcarriergroup表示载波组。Schedulingcarriergroup后的数字表示载波组的载波组标识，根据以上信息可确定存在6个载波组。分号(:)后面的数字表示载波组中调度载波的载波标识，根据以上信息可确定下行载波0、下行载波1、下行载波2、下行载波3、下行载波4和下行载波6为调度载波。DL表示下行的(被调度)载波，UL表示上行的(被调度)载波。载波组的信息中不包括被调度载波的情况下，将调度载波视为自调度载波，即下行载波0、下行载波2和下行载波3为自调度载波。下行载波1除了自调度之外，还可以跨调度下行载波2、下行载波3和下行载波5，以及上行载波和上行载波1。下行载波4除了自调度之外，还可以跨调度下行载波5和下行载波6，以及上行载波1至上行载波6。下行载波6不能自调度，可以跨调度上行载波6。
在信息A的配置下，在被调度载波为下行载波2时，下行载波2对应两个调度载波，分别为下行载波1和下行载波2；在被调度载波为下行载波3时，下行载波3对应两个调度载波，分别为下行载波1和下行载波3；在被调度载波为下行载波5时，下行载波5对应两个调度载波，分别为下行载波1和下行载波4；在被调度载波为上行载波1时，上行载波1对应两个调度载波，分别为下行载波1和下行载波4；在被调度载波为上行载波6时，上行载波6对应两个调度载波，分别为下行载波4和下行载波6。
以载波组包括一个被调度载波和该被调度载波的调度载波、上行载波和下行载波联合编号进行示例，图5B所示的载波组可以包括如下的信息B：
carriergroup 0:0
carriergroup 1:1 2
carriergroup 2:2
carriergroup 3:3 2,8
carriergroup 4:4 2,4
carriergroup 5:5 8
carriergroup 6:6 2,6
carriergroup 7:7 8
carriergroup 8:8
carriergroup 9:9 8
carriergroup 10:10 2,8
carriergroup 11:118
carriergroup12:12 8
carriergroup 13:13 8,12
其中，carriergroup表示载波组。carriergroup后的数字表示载波组的载波组标识，根据以上信息可确定存在14个载波组。分号(:)后面的数字表示载波组中被调度载波的载波标识，根据以上信息可确定被调度载波为下行载波0、下行载波2、下行载波4、下行载波6、下行载波8、下行载波10和下行载波12，以及上行载波1、上行载波3、上行载波5、上行载波7、上行载波9、上行载波11和上行载波13。载波组的信息中不包括调度载波的情况下，将调度载波视为自调度载波，即下行载波0、下行载波2和下行载波8为自调度载波。上行载波1仅被下行载波2调度。上行载波3和上行载波10被下行载波2和下行载波8调度。下行载波4被自身和下行载波2调度，上行载波5、上行载波7、上行载波9和上行载波11被下行载波8调度。下行载波6被自身和下行载波2调度。上行载波13被下行载波8和下行载波12调度。通过信息A和信息B可以看出以被调度载波配置载波组的数量(被调度载波的数量)，相对与以调度载波配置载波组的数量(调度载波的数量)较多。为了节省信令，可以调度载波配置载波组，即载波组包括一个调度载波和该调度载波的一个或多个被调度载波。
在信息B的配置下，在被调度载波为载波3时，载波3对应两个调度载波，分别为载波2和载波8；在被调度载波为载波4时，载波4对应两个调度载波，分别为载波2和载波4；在被调度载波为载波6时，载波6对应两个调度载波，分别为载波2和载波6；在被调度载波为载波10时，载波10对应两个调度载波，分别为载波2和载波8；在被调度载波为载波13时，载波10对应两个调度载波，分别为载波8和载波12。针对被调度载波均为下行被调度载波的情况，由于调度载波为下行载波，载波组可以理解为下行载波组。一个下行载波组可以包括一个调度载波和该调度载波的一个或多个下行被调度载波，或者可以包括一个下行被调度载波和该下行被调度载波的至少两个调度载波。以下行载波组包括一个调度载波和该调度载波的下行被调度载波、上行载波和下行载波单独编号进行示例，图5A所示的下行载波组可以包括如下的信息C：
DLSchedulingcarriergroup 0:0
DLSchedulingcarriergroup 1:1 1,2,3,5
DLSchedulingcarriergroup 2:2
DLSchedulingcarriergroup 3:3
DLSchedulingcarriergroup 4:4 4,5,6
其中，DLSchedulingcarriergroup表示下行载波组。DLSchedulingcarriergroup后的数字表示下行载波组的载波组标识，根据以上信息可确定存在5个下行载波组。由于被调度载波均为下行被调度载波，下行载波组的信息中可以不指示下行链路(DL)的信息。分号(:)后面的数字表示下行载波组中调度载波的载波标识，根据以上信息可确定下行载波0、下行载波1、下行载波2、下行载波3和下行载波4为存在调度载波的下行被调度载波。默认调度载波均为自调度载波，即下行载波0至下行载波4均可自调度。下行载波1除了自调度之外，还可以跨调度下行载波2、下行载波3和下行载波5。下行载波4除了自调度之外，还可以跨调度下行载波5和下行载波6。
在信息C的配置下，在被调度载波为下行载波2时，下行载波2对应两个调度载波，分别为下行载波1和下行载波2；在被调度载波为下行载波3时，下行载波3对应两个调度载波，分别为下行载波1和下行载波3；在被调度载波为下行载波5时，下行载波5对应两个调度载波，分别为下行载波1和下行载波4。
以下行载波组包括一个下行被调度载波和该下行被调度载波的调度载波、上行载波和下行载波联合编号进行示例，图5B所示的载波组可以包括如下的信息D：
DLcarriergroup 0:0
DLcarriergroup 1:2
DLcarriergroup 2:4 2,4
DLcarriergroup 3:6 2,6
DLcarriergroup 4:8
DLcarriergroup 5:10 2,8
DLcarriergroup 6:12 8
其中，DLcarriergroup表示下行载波组。DLcarriergroup后的数字表示下行载波组的载波组标识，根据以上信息可确定存在7个下行载波组。由于上行载波和下行载波联合编号，下行载波组的信息中可以不指示下行链路(DL)的信息。分号(:)后面的数字表示下行载波组中(下行)被调度载波的载波标识，根据以上信息可确定下行载波0、下行载波2、下行载波4、下行载波6、下行载波8、下行载波10和下行载波12为存在调度载波的下行被调度载波。默认载波组中缺少调度载波的载波标识时调度载波为自调度载波，即下行载波0、下行载波2和下行载波8均可自调度。下行载波4和下行载波6除了自调度之外，还可以被下行载波2跨调度。下行载波10被下行载波2和下行载波8跨调度。下行载波12被下行载波8跨调度。通过信息C和信息D可以看出以下行被调度载波配置下行载波组的数量(下行被调度载波的数量)，相对与以调度载波配置下行载波组的数量(调度载波的数量)较多。为了节省信令，可以调度载波配置下行载波组，即下行载波组包括一个调度载波和该调度载波的一个或多个下行被调度载波。
在信息D的配置下，在被调度载波为下行载波4时，下行载波4对应两个调度载波，分别为下行载波2和下行载波4；在被调度载波为下行载波6时，下行载波6对应两个调度载波，分别为下行载波2和下行载波6；在被调度载波为下行载波10时，下行载波10对应两个调度载波，分别为下行载波2和下行载波8。
针对被调度载波均为上行被调度载波的情况，可以将载波组作为上行载波组。一个上行载波组可以包括一个调度载波和一个或多个上行被调度载波，或者可以包括一个上行被调度载波和该上行被调度载波的至少两个调度载波。以上行载波组包括一个调度载波和该调度载波的上行被调度载波、上行载波和下行载波单独编号进行示例，图5A所示的上行载波组可以包括如下的信息E：
ULSchedulingcarriergroup 0:1 0,1
ULSchedulingcarriergroup 1:4 1,2,3,4,5,6
ULSchedulingcarriergroup 2:6 6
其中，ULSchedulingcarriergroup表示上行载波组。ULSchedulingcarriergroup后的数字表示上行载波组的载波组标识，根据以上信息可确定存在3个上行载波组。分号(:)后面的数字表示上行载波组中调度载波的载波标识，根据以上信息可确定下行载波1、下行载波4和下行载波6为存在上行被调度载波的调度载波。由于被调度载波均为上行被调度载波，上行载波组的信息中可以不指示上行链路(UL)的信息。下行载波1可以跨调度上行载波0和上行载波1。下行载波4可以跨调度上行载波1、上行载波2、上行载波3、上行载波4、上行载波5和上行载波6。下行载波6可以跨调度上行的载波6。
在信息E的配置下，在被调度载波为上行载波1时，上行载波1对应两个调度载波，分别为下行载波1和下行载波4；在被调度载波为上行载波6时，上行载波6对应两个调度载波，分别为下行载波4和下行载波6。
以上行载波组包括一个上行被调度载波和该上行被调度载波的调度载波、上行载波和下行载波联合编号进行示例，图5B所示的载波组可以包括如下的信息F：
ULcarriergroup 0:1 2
ULcarriergroup 1:3 2,8
ULcarriergroup 2:5 8
ULcarriergroup 3:7 8
ULcarriergroup 4:9 8
ULcarriergroup 5:11 8
ULcarriergroup 6:13 8,12
其中，ULcarriergroup表示上行载波组。ULcarriergroup后的数字表示上行载波组的载波组标识，根据以上信息可确定存在7个上行载波组。由于上行载波和下行载波联合编号，上行载波组的信息中可以不指示上行链路(UL)的信息。分号(:)后面的数字表示上行载波组中被调度载波的载波标识，根据以上信息可确定上行载波1、上行载波3、上行载波5、上行载波7、上行载波9、上行载波11和上行载波13为存在调度载波的上行被调度载波。上行载波1可以被下行载波2跨调度。上行载波3可以被下行载波2和下行载波8跨调度。上行载波5、上行载波7、上行载波9和上行载波11可以被下行载波8跨调度。上行载波13可以被下行载波8和下行载波12跨调度。通过信息E和信息F可以看出以上行被调度载波配置上行载波组的数量(上行被调度载波的数量)，相对与以调度载波配置上行载波组的数量(调度载波的数量)较多。为了节省信令，可以调度载波配置上行载波组，即上行载波组包括一个调度载波和该调度载波的一个或多个上行被调度载波。
在信息F的配置下，在被调度载波为上行载波3时，上行载波3对应两个调度载波，分别为下行载波2和下行载波8；在被调度载波为上行载波13时，上行载波13对应两个调度载波，分别为下行载波8和下行载波12。
本申请对于第一信息中载波组的信息不做限定，除了上述的载波组标识和载波标识之外，还可以包括每个载波的时频资源等。其中，载波的时频资源可以包括载波的中心频点、载波的带宽等，如，第一信息包括载波的BWP的配置信息。进一步地，第一信息中包括下行载波的配置，下行载波的配置中包括下行BWP的配置；第一信息中包括上行载波的配置，上行载波的配置中包括上行BWP的配置。
可选地，载波的时频资源中可以包括下行载波的同步信号和物理广播信道块(synchronization signal and PBCH block，SSB)，或者可以包括上行载波的随机接入信道(random access channel，RACH)资源。
S301、网络设备向终端设备发送第一信息。
相应地，终端设备接收来自网络设备的第一信息。
S302、终端设备基于第一信息确定被调度载波的至少两个调度载波。
可以理解，在图3所示的方法中，通过载波组配置调度载波和被调度载波，能够确定被调度载波的至少两个调度载波，可实现载波的灵活调度，动态地切换调度载波，降低了调度时延和传输时延，提高通信性能。
示例性地，请参照图6，图6中的一个框代表一个时间单元，比如子帧，D表示下行，S表示特殊子帧(该子帧中包括下行符号和上行符号)，U表示上行，CC1、CC2和CC3表示不同的载波。如图6所示，CC2的调度载波包括CC1和CC3。在第3个时间单元上行业务到达时，由于CC1上最近无下行传输的符号，从而网络设备无法在CC1上发送调度信息，此时网络设备可以通过在CC3上发送调度信息调度CC2上的数据传输。如此，网络设备可以在第3个时间单元上在CC3上传输调度信息，该调度信息能够调度终端设备在第4个时间单元的CC2上进行上行传输，无需接收重新配置的信息，降低了调度时延和传输时延，提高通信性能。
可选地，该方法还包括：终端设备接收来自网络设备的第二信息；终端设备基于所述第二信息确定所述载波组的信息。
相应地，网络设备向终端设备发送第二信息。
在本申请实施例中，第二信息可以包括第一载波组的载波组标识、第一调度载波的载波标识和第一被调度载波的载波标识中的至少一个。本申请对于第一载波组、第一调度载波和第一被调度载波不做限定，且对于它们之间的关系不做限定，可选地，包括以下三种关系中的至少一种，其中：
关系一、第一信息中第一载波组的调度载波包括去激活的载波，第一调度载波为第一载波组更新的调度载波，且第一调度载波为激活的载波，第二信息包括第一载波组的载波组标识和第一调度载波的载波标识。
关系二、第一信息中第一载波组中的被调度载波包括第一被调度载波，且第一被调度载波为去激活的载波，第二信息包括第一被调度载波的载波标识。
关系三、所述第一被调度载波为所述第一载波组更新的被调度载波，且第一被调度载波为激活的载波，第二信息包括第一载波组的载波组标识和第一被调度载波的载波标识。
以下结合不同关系和不同的第二信息分别描述终端设备如何基于第二信息确定载波组的信息。
针对关系一的确定方法、终端设备基于第一载波组的载波组标识和第一调度载波的载波标识，更新第一载波组的信息中调度载波的载波标识。
可以理解，在关系一中，网络设备通过第二信息配置待更新的(第一)载波组的载波组标识和该载波组中待更新的(第一)调度载波的载波标识。如此，终端设备可以基于第二信息中第一载波组的载波组标识获取第一载波组的信息，并基于第二信息中第一调度载波的载波标识将第一载波组的信息中的调度载波的载波标识进行更新，进而更新了第一载波组的调度载波。
示例性地，假设去激活的调度载波的载波标识为6，第一信息中载波组的信息如前述的信息A所示，第一载波组的信息为Schedulingcarriergroup 5:6UL:6。在第二信息包括载波组标识5和调度载波的载波标识2，即第一载波组的载波组标识5，第一调度载波的载波标识2的情况下，更新第一载波组之后的信息为Schedulingcarriergroup 5:2UL:6。如此，在第一载波组中的调度载波去激活的情况下，对第一载波组中调度载波的载波标识进行了更新，且更新为第一调度载波的载波标识，即第一载波组中的调度载波更新为第一调度载波。对第一载波组中的被调度载波的载波标识不进行更新，可以降低信令开销，从而可通过第一调度载波调度其中的被调度载波，使得这些被调度载波存在激活的调度载波，有利于即时调度被调度载波，便于提高通信性能。
可选地，在去激活的第二调度载波为自调度载波时，第二信息还包括去激活的第二调度载波的载波标识。该方法还包括：在第一载波组的信息中删除第二调度载波的载波标识。
示例性地，假设第一载波组的信息如前述的信息A所示为Schedulingcarriergroup 1:1DL:1,2,3,5；UL:0,1。在第二信息中第一调度载波的载波标识2，第二调度载波的载波标识为1的情况下，更新第一载波组中调度载波的标识，并删除第二调度载波的载波标识，得到的第一载波组的信息为Schedulingcarriergroup 1:2DL:2,3,5；UL:0,1。如此，可以在调度载波为自调度载波，且调度载波去激活的情况下，在该调度载波所在的载波组中删除该调度载波的载波标识，从而避免该调度载波被调度。
针对关系二的确定方法、终端设备基于第一被调度载波的载波标识，在第一信息的第一载波组的信息中删除第一被调度载波的载波标识。
可以理解，在关系二中，第一被调度载波为去激活的被调度载波，网络设备通过第二信息配置去激活的(第一)被调度载波的载波标识。如此，终端设备可以基于第二信息中第一被调度载波的载波标识将第一载波组的信息中的第一被调度载波的载波标识进行删除。
示例性地，假设去激活的(第一)被调度载波的载波标识为5，第一信息中载波组的信息如前述的信息A所示，在第一载波组的载波组标识为1和4的情况下，删除第一载波组中第一被调度载波的载波标识之前的信息分别为Schedulingcarriergroup 1:1DL:1,2,3,5；UL:0,1和Schedulingcarriergroup 4:4DL:4,5,6；UL:1,2,3,4,5,6，删除第一载波组中第一被调度载波的载波标识之后的信息分别为Schedulingcarriergroup1:1DL:1,2,3；UL:0,1和Schedulingcarriergroup 4:4DL:4,6；UL:1,2,3,4,5,6。如此，在第一载波组中的第一被调度载波去激活的情况下，对第一载波组中第一被调度载波的载波标识进行删除，从而避免使用去激活的被调度载波传输数据，可以降低信令开销，提高了数据传输的有效性。
针对关系三的确定方法、终端设备基于所述第一载波组的载波组标识和所述第一被调度载波的载波标识，在所述第一载波组的信息中增加所述第一被调度载波的载波标识。
可以理解，在关系三中，第一被调度载波为激活的被调度载波，网络设备通过第二信息配置待更新的(第一)载波组的载波组标识和该载波组中待更新(待增加)的(第一)被调度载波的载波标识。如此，终端设备可以基于第二信息中第一载波组的载波组标识获取第一载波组的信息，并基于第二信息中第一被调度载波的载波标识在第一载波组的信息中增加第一被调度载波的载波标识。
示例性地，假设激活的第一被调度载波的载波标识为7，第一信息中载波组的信息如前述的信息A所示，在第一载波组的载波组标识为1和4的情况下，增加第一被调度载波的载波标识之前的第一载波组的信息分别为Schedulingcarriergroup 1:1DL:1,2,3,5；UL:0,1和Schedulingcarriergroup 4:4DL:4,5,6；UL:1,2,3,4,5,6，增加第一被调度载波的载波标识之后的第一载波组的信息为Schedulingcarriergroup1:1DL:1,2,3,5,7；UL:0,1和Schedulingcarriergroup 4:4DL:4,5,6,7；UL:1,2,3,4,5,6。如此，在增加了激活的第一被调度载波的情况下，从该第一被调度载波待增加的第一载波组中增加第一被调度载波的载波标识，可以降低信令开销，从而使得调度载波能够对应更多的被调度载波，便于提高传输数据的灵活性。
需要说明的是，以上三种确定方法仅为示例。实际上，还可包括其他的关系对应的确定方法。例如，第二信息包括第一调度载波的载波标识，该第一调度载波为去激活的调度载波，基于所述第二信息确定载波组的信息，包括：基于第一调度载波的载波标识确定第一调度载波所在的第一载波组的载波组标识，基于该第一载波组的载波组标识获取第一载波组的信息，将第一载波组的信息中的第一调度载波的载波标识更新为第二调度载波的载波标识。
其中，第二调度载波可以为除第一调度载波之外的任一调度载波，如第一载波组的载波组标识后的一个载波组的调度载波，或者可以为载波组标识最小的载波组的调度载波，或者可以为最后一个载波组标识对应的载波组的调度载波等。第二调度载波可以配置于第二信息中，或通过预定义或其他信息配置得到。如此，配置的是去激活的调度载波，可提高配置的灵活性。
又例如，第二信息包括第一被调度载波的载波标识，该第一被调度载波为去激活的被调度载波。基于所述第二信息确定载波组的信息，包括：基于第一被调度载波的载波标识确定该第一被调度载波所在的第一载波组的载波组标识，基于该第一载波组的载波组标识获取第一载波组的信息，将第一载波组的信息中的第一被调度载波的载波标识进行删除。如此，基于第一被调度载波的载波标识确定第一载波组的载波组标识，无需同时配置第一载波组的载波组标识，可节省信令。
又例如，针对关系二的确定方法适用于以被调度载波配置的载波组。以被调度载波配置的载波组，第二信息包括第一载波组的载波组标识和/或第一被调度载波的载波标识，该第一被调度载波为去激活的载波，第一载波组为第一信息中第一被调度载波所在的载波组。基于所述第二信息确定所述载波组的信息，包括：基于所述第一载波组的载波组标识或所述第一被调度载波的载波标识，在所述第一信息中删除所述第一载波组的信息。如此，将去激活的被调度载波所在的载波组的信息进行删除。
又例如，针对关系三的确定方法适用于以被调度载波配置的载波组。以被调度载波配置的载波组，第二信息包括激活的第一被调度载波的载波标识和第一被调度载波的调度载波的载波标识。基于所述第二信息确定载波组的信息，包括：基于第一被调度载波的载波标识和第一被调度载波的调度载波的载波标识，在所述第一信息中增加第二载波组的信息。其中，第二载波组可以为第一信息确定的载波组之外的载波组。如此，增加了激活的被调度载波所在的新的载波组，并确定该载波组的信息。除了以上的处理方法，还可以包括其他的方法，例如，针对关系一和关系三，终端设备确定第一信息失效，或者去激活，或者释放第一信息中载波组的信息；针对关系二，终端设备确定第一信息中的载波组的信息仍生效。又例如，针对关系一，将第一调度载波所在的载波组的信息进行合并。
本申请对于第二信息的类型不做限定，第二信息可以为系统信息，比如SIB，或者，第二信息可以为高层信令，比如RRC信令、MAC CE等，或者，第二信息可以为物理层信令，比如DCI等，在此不做限定。第二信息除了关系一描述的内容之外，还可以包括去激活的调度载波的载波标识。去激活的调度载波的载波标识还可通过另外一种信息指示。针对关系一和关系三的第二信息可理解为第一信息之外的信息，用于指示更新载波组的信息。针对关系二的第二信息可理解为第一信息的更新指令，用于指示更新第一信息中第一载波组的信息。
可以理解，第一信息以载波组配置调度载波和被调度载波，有利于确定调度载波和被调度载波的关联关系，且有利于更新载波组的信息。在切换调度载波时，可降低调度时延和传输时延，提高了通信性能。
在另一种可行的方式中，第一信息用于确定调度载波和被调度载波的关联关系，被调度载波可以被至少两个调度载波调度。如此，终端设备可以基于关联关系确定被调度载波的至少两个调度载波。
在本申请实施例中，上行载波和下行载波可以没有固定的关联关系。如此，与现有技术中上行载波和下行载波配对设置不同，网络设备可以配置上行载波和下行载波的关联关系，实现上行载波和下行载波的灵活配置和管理。
本申请对于第一信息中配置调度载波和被调度载波的关联关系的方法不做限定，可以包括以下三种配置方法中的至少一种，其中：
配置方法一、第一信息包括被调度载波的配置，用于确定该被调度载波的至少两个调度载波。
其中，被调度载波的配置可以包括被调度载波的载波标识以及被调度载波的调度载波的载波标识。可选地，被调度载波的配置包括一个或多个调度载波指示，每个调度载波指示用于指示被调度载波的调度载波。第一信息对应的小区配置(ServingCellConfig)可以如下所示：

其中，SEQUENCE、CrossCarrierSchedulingConfig、own、other、cif-Presence、BOOLEAN和INTEGER可参照前述。carrierConfig表示载波配置，CrossCarrierSchedulingConfig表示跨载波调度配置。schedulingCarrierInfo表示调度载波信息，schedulingCarrierId表示调度载波标识。cif-InSchedulingCarrier表示在调度载波中该被调度载波的CIF的取值，CarrierIndex表示载波标识。可见，相比现有技术中辅小区的小区配置中自调度和跨调度为选择的关系，本申请的第一信息中配置的调度载波即可自调度又可以跨调度，灵活性更高。且被调度载波可以配置至少两个调度载波，从而确定被调度载波的至少两个调度载波，实现灵活的跨载波调度。
配置方法二、第一信息包括调度载波的配置，用于确定该调度载波的被调度载波。
其中，调度载波的配置包括调度载波的载波标识，以及调度载波的被调度载波的载波标识。可选地，调度载波的配置包括一个或多个被调度载波指示，每个被调度载波指示用于指示调度载波的被调度载波。如果调度载波为自调度载波，则CIF可以为0。调度载波可以以被调度载波列表进行配置，如下行被调度载波列表(ScheduledCarrierDL-List)，和/或，上行被调度载波列表(ScheduledCarrierUL-List)。示例性地，第一信息对应的小区配置(ServingCellConfig)可以如下所示：
其中，SEQUENCE、own、other、cif-Presence、carrierConfig、cif-InSchedulingCarrier、CarrierIndex、BOOLEAN和INTEGER可参照前述，scheduledCarrierInfo表示被调度载波信息，scheduledCarrier表示被调度载波，scheduledCarrierId表示被调度载波的载波标识。可见，调度载波配置的第一信息中，可以通过被调度载波的列表表示调度载波的至少一个被调度载波。
配置方法三、第一信息包括调度载波和被调度载波的关联关系表格。
其中，关联关系表格可以按照上行被调度载波的CIF和下行被调度载波的CIF联合编号和独立编号中的一种方式进行配置。示例性地，请参照表2和表3中的至少一行和/或至少一列，其中，表2中上行被调度载波的CIF和下行被调度载波的CIF联合编号，表3中上行被调度载波的CIF和下行被调度载波的CIF独立编号。
表2
根据表2可知，存在4个下行载波和3个上行载波，且下行载波的载波标识为0-3，上行载波的载波标识为4-6。其中，载波标识为0、1、2、4、5、6的载波的调度载波的载波标识为0；载波标识为0、1、2、5的载波的调度载波的载波标识为2。可见，载波标识为0的载波可以自调度，还可以跨调度，共调度6个载波，CIF联合编号，取值为0-6，可以通过3比特的二进制表示，分别对应载波标识为0、1、2、4、5、6的被调度载波。载波标识为2的载波可以自调度，还可以跨调度，共调度4个载波，可以通过2比特的二进制表示，CIF的取值为0-3，分别对应载波标识为2、1、0、5的被调度载波。
在表2的配置下，在被调度载波为下行载波0时，下行载波0对应两个调度载波，分别为下行载波0和下行载波2；在被调度载波为下行载波1时，下行载波1对应两个调度载波，分别为下行载波0和下行载波2；在被调度载波为下行载波2时，下行载波2对应两个调度载波，分别为下行载波0和下行载波2；在被调度载波为上行载波5时，上行载波5对应两个调度载波，分别为下行载波0和下行载波2。
表3
根据表3可知，存在4个下行载波和3个上行载波，且下行载波的载波标识为0-3，上行载波的载波标识为4-6。其中，载波标识为0、1、2、4、5、6的载波的调度载波的载波标识为0，且载波标识为0、2、3、5的载波的调度载波的载波标识为2。可见，载波标识为0的载波可以自调度，还可以跨调度，共调度3个上行载波和3个下行载波。CIF独立编号，上行CIF和下行CIF的取值分别为0-2，可以通过2比特的二进制表示。载波标识为0的上行CIF的取值0-2分别对应载波标识为0、1、2的上行被调度载波。载波标识为0的下行CIF的取值0-2分别对应载波标识为4、5、6的下行被调度载波。载波标识为2的载波可以自调度，还可以跨调度，共调度3个下行载波和1个上行载波。可以通过2比特的二进制表示载波标识为2的上行CIF的取值和下行CIF的取值，载波标识为2的上行CIF的取值0-3分别对应载波标识为0、2、3的下行被调度载波。载波标识为2的下行CIF的取值0对应载波标识为5的上行被调度载波。
在表3的配置下，在被调度载波为下行载波0时，下行载波0对应两个调度载波，分别为下行载波0和下行载波2；在被调度载波为下行载波2时，下行载波2对应两个调度载波，分别为下行载波0和下行载波2；在被调度载波为上行载波5时，上行载波5对应两个调度载波，分别为下行载波0和下行载波2。
需要说明的是，以上关联关系表格中上行载波和下行载波采用联合标号的方式，实际上，还可以采用独立标号的方式。以上三种确定调度载波和被调度载波的关联关系的方法仅为示例，其他能确定调度载波和被调度载波的关联关系的方法应保护在本申请中。且以上两种第一信息也为示例。实际上，可能存在其他形式的第一信息，通过第一信息能够确定被调度载波的至少两种调度载波应保护在本申请中。
可以理解，在被调度载波存在至少两个调度载波时，可通过在一个调度载波中进行PDCCH盲检来获取该被调度载波的调度信息。本申请对于被调度载波的哪些调度载波进行PDCCH盲检不做限定，可以考虑终端设备的处理复杂度，还可以考虑时延、吞吐、能耗和覆盖等至少一个需求确定进行PDCCH盲检的载波或切换的载波。
在本申请实施例中，可以预定义或配置在一个时间单元对一个调度载波进行PDCCH盲检，在保证每个时间单元都可以进行PDCCH盲检以实现数据调度的情况下，降低了盲检复杂度，提高通信性能。
下面以第一调度载波和第一调度载波的第一被调度载波对PDCCH盲检的方法进行示例。
在一些可行的示例中，该方法还包括：终端设备基于第三信息在第一时间单元对第一调度载波进行PDCCH盲检。
其中，第三信息为配置信息或预定义信息。第三信息可以为系统信息，比如SIB，或高层信令，比如RRC信令、MAC CE等，或物理层信令，比如DCI等，在此不做限定。第一时间单元可以包括PDCCH监测时机对应的任一时间单元，或，PDCCH盲检的任一时间单元。
本申请对于第三信息的内容不做限定，在终端设备存在N个调度载波时，可以指示第一时间单元对应的调度载波的PDCCH的盲检次数，其中一个调度载波的PDCCH的盲检次数为1，其余的调度载波的PDCCH的盲检次数为0；或者配置第一时间单元对应的一个调度载波的搜索空间，其余的调度载波的搜索空间可理解为未配置，从而不通过其余的调度载波进行PDCCH盲检；或者配置第一时间单元对应的一个调度载波的载波标识，即在预先配置各个调度载波的搜索空间的情况下，也可基于该载波标识在第一时间单元通过该载波标识对应的调度载波进行PDCCH盲检。
在一些示例中，第三信息包括以下至少一项：盲检条件；或者优先检测的载波标识；或者调度载波的时域图案(pattern)。
其中，盲检条件可以用于确定进行盲检的PDCCH所在的载波，例如，协议可以预定义终端设备检测调度载波标识小于第一阈值的调度载波标识对应的调度载波等。可以理解，对满足盲检条件的调度载波进行PDCCH盲检，对不满足盲检条件的调度载波不进行PDCCH盲检，降低了盲检的数量，进而降低盲检的复杂度，并可以节省终端设备的能耗。同理，对优先检测的载波标识的调度载波进行PDCCH盲检，对其余载波标识的调度载波不进行PDCCH盲检，降低了盲检的数量，进而降低盲检的复杂度，并可以节省终端设备的能耗。
可选地，网络设备可以半静态配置优先检测的载波标识。如此，提高了更新进行PDCCH盲检的调度载波的配置灵活性，利于更新进行PDCCH盲检的调度载波。
可选地，第三信息中可以包括优先检测的载波标识，其中，该载波标识可以为一个或多个。
可选地，网络设备可以指示一段时间内优先检测的调度载波，在该段时间内优先检测该调度载波。也就是说，该段时间内优先对该调度载波进行PDCCH盲检。
示例性地，请参照图7，在第2个时间单元内，网络设备可以在调度载波CC1和调度载波CC3上配置PDCCH的搜索空间。网络设备可以通过第三信息指示终端设备优先检测的调度载波为CC1，从而指示在第2个时间单元内优先检测CC1上的搜索空间。在第3个时间单元内有上行数据到达，CC1没有下行符号，网络设备可以通过第三信息或其他的第三信息指示终端设备优先检测的调度载波为CC3，从而指示在第3个时间单元内优先检测CC3上的PDCCH的搜索空间。如此，终端设备盲检CC3上的PDCCH，并进行上行传输。
请继续参照图7，在第7个时间单元内，调度载波CC1和调度载波CC3上均配置有PDCCH的搜索空间。考虑到终端设备的处理复杂度和节能，网络设备可以考虑不切换调度载波，从而可以通过第三信息或其他的第三信息指示优先检测CC3上的PDCCH的搜索空间。
在本申请实施例中，网络设备可以配置第一时间单元的调度载波的时域图案。终端设备根据该时域图案在对应的时间单元确定该时间单元进行PDCCH盲检的调度载波。该时域图案可以通过半静态的指令更新。网络设备可以配置一段时间内优先检测的调度载波的时域图案，如图7所示。
可选地，第三信息中可以包括调度载波的时域图案，在一个时间单元内可以对应一个或多个调度载波标识。
在另外一些可行的示例中，第三信息包括第一时间单元的调度载波的载波标识。如图7所示，第三信息可以包括：CC1,CC2,CC3,CC3,CC3,CC3,CC3,CC1,CC1,CC1。如此，在第一个时间单元和第3个时间单元内优先检测的调度载波为CC1，在第四个时间单元到第7个时间单元内优先检测的调度载波为CC3，在第2个时间单元、第8个时间单元到第10个时间单元内优先检测的调度载波为CC2。
需要说明的是，以上三项第三信息仅为示例。实际上，还可以包括其他的第三信息。例如，下面给出的一些方案。
可选地，第三信息中可以包括优先检测的载波标识和调度载波的时域图案。当调度载波的时域图案中的一个时间单元内包括多个调度载波的标识时，终端设备可以根据优先检测的载波标识确定在该时间单元内盲检的调度载波。或者，当优先检测的载波标识包括多个调度载波的标识时，终端设备可以根据调度载波的时域图案从多个调度载波中确定在一个时间单元内盲检的调度载波。如此，终端设备可以根据优先检测的载波标识和调度载波的时域图案确定在一个时间单元内盲检的调度载波，可以进一步降低盲检的调度载波的数量和复杂度。
可选地，第三信息中可以包括盲检条件和优先检测的载波标识。当根据盲检条件确定出一个或多个调度载波时，终端设备可以根据优先检测的载波标识从一个或多个调度载波中确定盲检的调度载波。或者，当优先检测的载波标识包括多个调度载波的标识时，终端设备可以根据盲检条件从多个调度载波中确定盲检的调度载波。如此，终端设备可以根据盲检条件和优先检测的载波标识确定盲检的调度载波，可以进一步降低盲检的调度载波的数量和复杂度。
可选地，第三信息中可以包括盲检条件和调度载波的时域图案。当根据盲检条件确定一个或多个调度载波时，终端设备可以根据调度载波的时域图案从一个或多个调度载波中确定盲检的调度载波。或者，当调度载波的时域图案中的在一个时间单元内包括多个调度载波的标识时，终端设备可以根据盲检条件确定在该时间单元内盲检的调度载波。或者，当根据盲检条件确定处一个或多个调度载波时，终端设备可以根据调度载波的时域图案确定一个时间单元内盲检的调度载波。如此，终端设备可以根据盲检条件和调度载波的时域图案确定盲检的调度载波，可以进一步降低盲检的调度载波的数量和复杂度。
可选地，第三信息可以包括盲检条件，优先检测的载波标识和调度载波的时域图案。如此，终端设备可以根据盲检条件，优先检测的载波标识和调度载波的时域图案确定在一个时间单元内盲检的调度载波，可以进一步降低盲检的调度载波的数量和复杂度。
在本申请实施例中，有的调度载波仅调度下行载波，有的调度载波仅调度上行载波，有的调度载波即调度上行载波又调度下行载波。例如图5A中的下行载波0仅调度下行载波，下行载波6仅调度上行载波，下行载波1和下行载波4即调度上行载波又调度下行载波。任意一个载波都可以有两个或更多的调度载波，每个调度载波调度的载波数不同，需要不同的盲检次数。
本申请对于确定调度载波上的PDCCH盲检的次数的方法不做限定，在一些可行的示例中，该方法还包括：终端设备基于调度载波的被调度载波的载波个数，确定在调度载波上的PDCCH盲检的次数。
本申请实施例中的一个调度载波的PDCCH盲检的次数可以是指一个时隙内的一个调度载波的PDCCH盲检次数，或，一个时间单元内的一个调度载波的PDCCH盲检次数，具体的，本申请对此不作限定。
其中，PDCCH盲检的次数可以包括最大盲检PDCCH候选次数，和/或最大非重叠CCE的个数等，在此不做限定。其中，最大盲检PDCCH候选次数可以为前述的一个时隙内最大的PDCCH盲检的次数，或者，一个时间单元内的最大的PDCCH盲检的次数。
下面针对不同的被调度载波的载波个数分别介绍确定调度载波上的PDCCH盲检的次数的方法，并以第一调度载波进行示例。确定PDCCH盲检的次数的方法可以包括如下方法中的至少一个。
方法1、被调度载波不限定为上行载波或下行载波，即调度载波的被调度载波的载波个数为调度载波的上行被调度载波的载波个数和下行被调度载波的载波个数之和，被调度载波的载波总数为所有的上行被调度载波的载波个数和下行被调度载波的载波个数之和。
可选地，基于调度载波的被调度载波的载波个数，确定在调度载波上的PDCCH盲检的次数，包括：基于调度载波的被调度载波的载波个数确定被调度载波的载波总数，基于第一调度载波的被调度载波的载波个数和被调度载波的载波总数确定第一调度载波的盲检比例；基于第一调度载波的盲检比例和最大盲检次数的乘积，获取第一调度载波上的PDCCH盲检的次数。
其中，第一调度载波上的PDCCH盲检的次数可以为第一调度载波的盲检比例和最大盲检次数的乘积。在该乘积存在小数的情况下，可以对乘积进行向上取整或向下取整，将得到的整数作为第一调度载波上的PDCCH盲检的次数。最大盲检次数可参照前述方案和表1的内容。
示例性地，如图5A所示，调度载波和该调度载波的被调度载波的载波个数为：载波0:1(DL)；载波1:6；载波2:1(DL)；载波3:1(DL)；载波4:9；载波5:0；载波6:1(UL)，则调度载波的被调度载波的载波总数为1+6+1+1+9+0+1＝19，则载波0、载波2、载波3和载波6的盲检比例为1/19，载波1的盲检比例为6/19，载波4的盲检比例为9/19，载波5的盲检比例为0。如图5A所示，载波0、载波1和载波2的子载波间隔为15kHz，载波3和载波4的子载波间隔为30kHz，载波5和载波6的子载波间隔为60kHz。根据表1可知，载波0、载波1和载波2的最大盲检次数为44。载波3和载波4的最大盲检次数为36，载波5和载波6的最大盲检次数为22。因此，载波0和载波2上的PDCCH盲检的次数为2(1/19*44)，载波1上的PDCCH盲检的次数为13(6/19*44)。载波3上的PDCCH盲检的次数为1(1/19*36)，载波4上的PDCCH盲检的次数为17(9/19*36)。载波5上的PDCCH盲检的次数为0，载波6上的PDCCH盲检的次数为1(1/19*22)。
方法2、被调度载波限定为下行被调度载波，被调度载波的载波个数为下行被调度载波的载波个数，被调度载波的载波总数为下行被调度载波的载波总数。
可选地，基于调度载波的被调度载波的载波个数，确定在调度载波上的PDCCH盲检的次数，包括：基于调度载波的下行被调度载波的载波个数确定下行被调度载波的载波总数，基于第一调度载波的下行被调度载波的载波个数和下行被调度载波的载波总数确定第一调度载波的盲检比例；基于第一调度载波的盲检比例和最大盲检次数的乘积，获取第一调度载波上的PDCCH盲检的次数。
其中，第一调度载波上的PDCCH盲检的次数可以为第一调度载波的盲检比例和最大盲检次数的乘积。在该乘积存在小数的情况下，可以对乘积进行向上取整或向下取整，将得到的整数作为第一调度载波上的PDCCH盲检的次数。最大盲检次数可参照前述方案和表1的内容。
示例性地，如图5A所示，调度载波和该调度载波的下行被调度载波的载波个数为：载波0:1(DL)；载波1:4(DL)；载波2:1(DL)；载波3:1(DL)；载波4:3(DL)；载波5:0(DL)；载波6:0(DL)，则调度载波的下行被调度载波的载波总数为1+4+1+1+3+0+0＝10，则载波0、载波2和载波3的盲检比例为1/10，载波1的盲检比例为4/10，载波4的盲检比例为3/10，载波5和载波6的盲检比例为0。根据前述可知，载波0、载波1和载波2的最大盲检次数为44。载波3和载波4的最大盲检次数为36，载波5和载波6的最大盲检次数为22。因此，载波0和载波2上的PDCCH盲检的次数为4(1/10*44)，载波1上的PDCCH盲检的次数为16(4/10*44)。载波3上的PDCCH盲检的次数为3(1/10*36)，载波4上的PDCCH盲检的次数为10(3/10*36)。载波5和载波6上的PDCCH盲检的次数为0。
方法3、被调度载波限定为上行被调度载波，被调度载波的载波个数为上行被调度载波的载波个数，被调度载波的载波总数为上行被调度载波的载波总数。
可选地，基于调度载波的被调度载波的载波个数，确定在调度载波上的PDCCH盲检的次数，包括：基于调度载波的上行被调度载波的载波个数确定上行被调度载波的载波总数，基于第一调度载波的上行被调度载波的载波个数和上行被调度载波的载波总数确定第一调度载波的盲检比例；基于第一调度载波的盲检比例和最大盲检次数的乘积，获取第一调度载波上的PDCCH盲检的次数。
其中，第一调度载波上的PDCCH盲检的次数可以为第一调度载波的盲检比例和最大盲检次数的乘积的。在该乘积存在小数的情况下，可以对乘积进行向上取整或向下取整，将得到的整数作为第一调度载波上的PDCCH盲检的次数。最大盲检次数可参照前述方案和表1的内容。
示例性地，如图5A所示，调度载波和该调度载波的上行被调度载波的载波个数为：载波0:0(UL)；载波1:2(UL)；载波2:0(UL)；载波3:0(UL)；载波4:6(UL)；载波5:0(UL)；载波6:1(UL)，则调度载波的上行被调度载波的载波总数为0+2+0+0+6+0+1＝9，则载波0、载波2、载波3、载波5和载波6的盲检次数为0，载波1的盲检比例为2/9，载波4的盲检比例为6/9。根据前述可知，载波0、载波1和载波2的最大盲检次数为44。载波3和载波4的最大盲检次数为36，载波5和载波6的最大盲检次数为22。因此，载波0、载波2、载波3、载波5和载波6上的PDCCH盲检的次数为0。载波1上的PDCCH盲检的次数为9(2/9*44)，载波4上的PDCCH盲检的次数为24(6/9*36)，载波6上的PDCCH盲检的次数为2(1/9*22)。
需要说明的是，以上3种方法仅为示例，实际上，还可以包括其他的方法。例如，方法2和方法3结合的方法，如基于所述调度载波的被调度载波的载波个数，确定在所述调度载波上的PDCCH盲检的次数，包括：基于调度载波的上行被调度载波的载波个数确定上行被调度载波的载波总数，基于调度载波的下行被调度载波的载波个数确定下行被调度载波的载波总数；基于第一调度载波的上行被调度载波的载波个数和上行被调度载波的载波总数确定第一调度载波的上行盲检比例，基于第一调度载波的下行被调度载波的载波个数和下行被调度载波的载波总数确定第一调度载波的下行盲检比例；基于第一调度载波的上行盲检比例和最大盲检次数的乘积，获取第一调度载波上的PDCCH盲检的第一次数，基于第一调度载波的下行盲检比例和最大盲检次数的乘积，获取第一调度载波上的PDCCH盲检的第二次数；基于第一次数和第二次数的和值，得到第一调度载波上的PDCCH盲检的次数。
示例性地，如图5A所示，调度载波和该调度载波的被调度载波的载波个数为：载波0:1(DL)；载波1:6(4DL,2UL)；载波2:1(DL)；载波3:1(DL)；载波4:9(3DL,6UL)；载波5:0；载波6:1(UL)，则调度载波的下行被调度载波的载波总数为10，调度载波的上行被调度载波的载波总数为9。根据前述可知，载波0、载波1和载波2的最大盲检次数为44。载波3和载波4的最大盲检次数为36，载波5和载波6的最大盲检次数为22。因此，载波0和载波2上的PDCCH盲检的第二次数为4，载波1上的PDCCH盲检的第二次数为16。载波3上的PDCCH盲检的第二次数为3，载波4上的PDCCH盲检的第二次数为10。载波5和载波6上的PDCCH盲检的第二次数为0。载波0、载波2、载波3、载波5和载波6上的PDCCH盲检的第一次数为0。载波1上的PDCCH盲检的第一次数为9，载波4上的PDCCH盲检的第一次数为24，载波6上的PDCCH盲检的第一次数为2。可知，载波0和载波2上的PDCCH盲检的次数为4(4+0)，载波1上的PDCCH盲检的次数为25(16+9)。载波3上的PDCCH盲检的次数为3(3+0)，载波4上的PDCCH盲检的次数为34(10+24)。载波5上的PDCCH盲检的次数为0，载波6上的PDCCH盲检的次数为2(0+2)。
在一些可行的示例中，该方法还包括：终端设备接收来自网络设备的第一DCI。
相应地，网络设备向终端设备发送第一DCI。
在本申请实施例中，第一DCI用于调度第二调度载波的第二被调度载波上的数据传输。该第一DCI可以理解为对第一调度载波进行PDCCH盲检得到的DCI。
在一些可行的示例中，第一DCI用于指示是否在第三调度载波上进行PDCCH盲检。
其中，第三调度载波可以理解为第二调度载波之外的载波。第三调度载波可以调度第二调度载波的被调度载波，或者不调度第二调度载波的被调度载波。也就是说，第一DCI可以指示传输第一DCI的调度载波的被调度载波，还可以指示是否对其他的调度载波进行PDCCH盲检。
比如，第一DCI中可以包括第一指示域，该第一指示域用于指示是否盲检其他调度载波。
可选地，第一指示域的比特数为1，即一个比特位，该比特位上的数值为0代表不盲检其他调度载波，该比特位上的数值为1代表盲检其他调度载波；或者，比特位上的数值为1代表不盲检其他调度载波，该比特位上的数值为0代表盲检其他调度载波。
可选地，第一指示域的比特数为s，即s个比特位。s为指示是否盲检的其他调度载波的载波个数。该第一指示域的一个比特位对应一个调度载波，比如调度载波c。调度载波c对应的比特位上的数值为0代表不盲检该调度载波c，调度载波c对应的比特位上的数值为1代表盲检该调度载波c；或者，调度载波c对应的比特位上的数值为1代表不盲检该调度载波c，调度载波c对应的比特位上的数值为0代表盲检该调度载波c。
本申请对于第一指示域中各个比特位对应的调度载波不做限定，可以与调度载波的载波标识对应。例如，第0个比特位对应的调度载波的载波标识为0；第1个比特位对应的调度载波的载波标识为1等。或者可以与激活的调度载波的载波标识对应，例如，调度载波0、2、3为激活的载波，调度载波1为去激活的载波，则第0个比特位对应的调度载波的载波标识为0；第1个比特位对应的调度载波的载波标识为2，第2个比特位对应的调度载波的载波标识为3。
在一些可行的示例中，第一DCI用于指示是否在第三调度载波中进行PDCCH盲检，该PDCCH盲检对应第二被调度载波的第二DCI。也就是说，第一DCI可以指示传输第一DCI的调度载波的被调度载波，还可以指示是否盲检第三调度载波上的第二DCI，该第二DCI用于调度第三调度载波的第二被调度载波上的数据传输。
在一些可行的示例中，该方法还包括：终端设备接收来自网络设备的第四信息，其中，第四信息包括第一级DCI和第二级DCI；终端设备基于第一级DCI确定第二级DCI所在的调度载波和时频位置；终端设备基于第二级DCI确定数据传输所在的被调度载波。
相应地，网络设备向终端设备发送第四信息。
其中，第一级DCI用于确定所述第二级DCI所在的调度载波和时频位置，所述第二级DCI用于确定数据传输所在的被调度载波。如此，与现有技术被调度载波和调度载波通过同一级DCI信令指示相比，灵活性更高，利于切换调度的载波。
上述详细阐述了本申请实施例的方法，下面提供了本申请实施例的装置。
请参见图8，图8是本申请实施例提供的一种通信装置的结构示意图。该通信装置可以包括收发单元801和处理单元802。其中，收发单元801可以是具有信号的输入(接收)或者输出(发送)的装置，用于与其他网络设备或者设备中的其他器件进行信号的传输。
处理单元802可以是具有处理功能的装置，可以包括一个或者多个处理器。处理器可以是通用处理器或者专用处理器等。处理器可以是基带处理器、或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对装置(如，宿主节点、中继节点或芯片等)进行控制，执行软件程序，处理软件程序的数据。
该通信装置可以包括终端设备或网络设备，本实施例中由终端设备执行的功能或者可以由终端设备中的装置(例如，芯片，或者芯片系统，或者电路)来执行，或者是能够和终端设备匹配使用的装置。本实施例中由网络设备执行的功能或者可以由网络设备中的装置(例如，芯片，或者芯片系统，或者电路)来执行，或者是能够和网络设备匹配使用的装置。下面以网络设备和终端设备进行示例。
当通信装置为终端侧装置时，该通信装置包括：
收发单元801，用于接收第一信息，所述第一信息包括所述载波组的信息，所述载波组包括调度载波和被调度载波；
处理单元802，用于基于所述第一信息确定所述被调度载波的至少两个调度载波。
在一种可能的示例中，所述被调度载波被至少两个所述载波组中的调度载波调度；或者所述被调度载波被所述载波组中的至少两个调度载波调度。
在一种可能的示例中，所述载波组的信息包括所述载波组的载波组标识、所述载波组中调度载波的载波标识和所述载波组中被调度载波的载波标识。
在一种可能的示例中，所述被调度载波包括上行被调度载波和/或下行被调度载波。
在一种可能的示例中，收发单元801，还用于接收第二信息，所述第二信息包括第一载波组的载波组标识、第一调度载波的载波标识和第一被调度载波的载波标识中的至少一个；
处理单元802还用于基于所述第二信息确定所述载波组的信息。
在一种可能的示例中，所述第一信息中所述第一载波组的调度载波包括去激活的载波，所述第一调度载波为所述第一载波组更新的调度载波，且所述第一调度载波为激活的载波；处理单元802具体用于基于所述第一载波组的载波组标识和所述第一调度载波的载波标识，更新所述第一载波组的信息中调度载波的载波标识。
在一种可能的示例中，所述第一信息中所述第一载波组中的被调度载波包括所述第一被调度载波，且所述第一被调度载波为去激活的载波；处理单元802具体用于基于所述第一被调度载波的载波标识，在所述第一信息的所述第一载波组的信息中删除所述第一被调度载波的载波标识。
在一种可能的示例中，所述第一被调度载波为所述第一载波组更新的被调度载波，且所述第一被调度载波为激活的载波；处理单元802具体用于基于所述第一载波组的载波组标识和所述第一被调度载波的载波标识，在所述第一载波组的信息中增加所述第一被调度载波的载波标识。
在一种可能的示例中，所述第一信息用于确定调度载波和被调度载波的关联关系。
在一种可能的示例中，所述第一信息包括：所述被调度载波的配置信息，所述被调度载波的配置信息用于确定所述被调度载波的调度载波；或者所述调度载波的配置信息，所述调度载波的配置信息用于确定所述调度载波的被调度载波；或者所述调度载波和所述被调度载波的关联关系表格。
在一种可能的示例中，处理单元802还用于基于所述被调度载波的载波标识所在的位置确定所述被调度载波的载波指示域CIF。
在一种可能的示例中，在所述调度载波为自调度载波时，所述CIF为0。
在一种可能的示例中，所述调度载波为自调度载波和/或跨调度载波。
在一种可能的示例中，处理单元802还用于基于第三信息在第一时间单元对第二调度载波进行物理下行控制信道PDCCH盲检，所述第三信息为配置信息或预定义信息。
在一种可能的示例中，所述第三信息包括以下至少一项：盲检条件；或者优先检测的载波标识；或者所述调度载波的时域图案。
在一种可能的示例中，处理单元802还用于基于所述调度载波的被调度载波的载波个数，确定在所述调度载波上的PDCCH盲检的次数。
在一种可能的示例中，收发单元801还用于接收第一DCI，所述第一DCI用于指示是否在第三调度载波上进行PDCCH盲检；或所述第一DCI用于指示是否在所述第三调度载波中PDCCH盲检第二被调度载波的第二DCI，所述第二被调度载波被所述第三调度载波调度。
在一种可能的示例中，收发单元801还用于接收第四信息，所述第四信息包括第一级DCI和第二级DCI；基于所述第一级DCI确定所述第二级DCI所在的调度载波和时频位置；处理单元802还用于基于所述第二级DCI确定数据传输所在的被调度载波。
当通信装置为网络侧装置时，该通信装置包括：
处理单元802，用于确定第一信息，所述第一信息包括所述载波组的信息，所述载波组包括调度载波和被调度载波，所述被调度载波被至少两个调度载波调度；
收发单元801，用于发送所述第一信息。
在一种可能的示例中，所述被调度载波被至少两个所述载波组中的调度载波调度；或者所述被调度载波被所述载波组中的至少两个调度载波调度。
在一种可能的示例中，所述载波组的信息包括所述载波组的载波组标识、所述载波组中调度载波的载波标识和所述载波组中被调度载波的载波标识。
在一种可能的示例中，所述被调度载波包括上行被调度载波和/或下行被调度载波。
在一种可能的示例中，收发单元801，还用于发送第二信息，所述第二信息包括第一载波组的载波组标识、第一调度载波的载波标识和第一被调度载波的载波标识中的至少一个。
在一种可能的示例中，所述第一信息中所述第一载波组的调度载波包括去激活的载波，所述第一调度载波为所述第一载波组更新的调度载波，且所述第一调度载波为激活的载波，所述第二信息包括所述第一调度载波的载波标识和所述第一载波组的载波组标识。
在一种可能的示例中，所述第一信息中所述第一载波组中的被调度载波包括所述第一被调度载波，且所述第一被调度载波为去激活的载波，所述第二信息包括所述第一被调度载波的载波标识。
在一种可能的示例中，所述第一被调度载波为所述第一载波组更新的被调度载波，且所述第一被调度载波为激活的载波，所述第二信息包括所述第一被调度载波的载波标识和所述第一载波组的载波组标识。
在一种可能的示例中，所述第一信息用于确定调度载波和被调度载波的关联关系。
在一种可能的示例中，所述第一信息包括：所述被调度载波的配置信息，所述被调度载波的配置信息用于确定所述被调度载波的调度载波；或者所述调度载波的配置信息，所述调度载波的配置信息用于确定所述调度载波的被调度载波；或者所述调度载波和所述被调度载波的关联关系表格。
在一种可能的示例中，在所述调度载波为自调度载波时，所述CIF为0。
在一种可能的示例中，所述调度载波为自调度载波和/或跨调度载波。
在一种可能的示例中，收发单元801还用于发送第三信息，所述第三信息用于指示在第一事件单元对第二调度载波进行PDCCH盲检。
在一种可能的示例中，所述第三信息包括以下至少一项：盲检条件；或者优先检测的载波标识；或者所述调度载波的时域图案。
在一种可能的示例中，收发单元801还用于发送第一DCI，所述第一DCI用于指示是否在第三调度载波上进行PDCCH盲检；或所述第一DCI用于指示是否在所述第三调度载波中PDCCH盲检第二被调度载波的第二DCI，所述第二被调度载波被所述第三调度载波调度。
在一种可能的示例中，收发单元801还用于发送第四信息，所述第四信息包括第一级DCI和第二级DCI；所述第一级DCI用于确定所述第二级DCI所在的调度载波和时频位置，所述第二级DCI用于确定数据传输所在的被调度载波。
需要说明的是，各个单元的实现还可以对应参照图3所示的方法实施例的相应描述。
请参阅图9，图9是本申请实施例提供的另一种通信装置的结构示意图。该通信装置可以为终端设备或网络设备，本实施例中由终端设备执行的功能或者可以由终端设备中的装置(例如，芯片，或者芯片系统，或者电路)来执行，或者是能够和终端设备匹配使用的装置。本实施例中由网络设备执行的功能或者可以由网络设备中的装置(例如，芯片，或者芯片系统，或者电路)来执行，或者是能够和网络设备匹配使用的装置。该通信装置用以实现方法实施例中描述的方法。
如图9所示，该通信装置可以包括处理器111和存储介质112。处理器111还可以称为处理单元，可以实现一定的控制功能。存储介质112还可以称为存储单元，或存储器。存储介质112上存有指令114。该指令114可在处理器111上被运行，使得通信装置执行本申请实施例中图3描述的任一方法。
可选地，处理器111可以包括指令113，该指令113可以在处理器111上被运行，使得通信装置执行本申请实施例中图3描述的任一方法。
以上实施例描述中的通信装置可以是第一设备或第二设备，但本申请中描述的装置的范围并不限于此，该通信装置可以是独立的设备或者可以是较大设备的一部分。例如，通信装置可以是：
(1)独立的集成电路IC，或芯片，或芯片系统或子系统；
(2)具有一个或多个IC的集合，可选地，该IC集合可以包括用于存储数据和/或指令的存储部件；
(3)ASIC，例如调制解调器；
(4)可嵌入在其他设备内的模块；
请参阅图10，图10是本申请实施例提供的一种终端设备的结构示意图。为了便于说明，图10仅示出了终端设备的主要部件。如图10所示，终端设备101包括处理器、存储器、控制电路、天线、以及输入输出装置。处理器主要用于对通信协议以及通信数据进行处理，以及对整个终端设备进行控制，执行软件程序，处理软件程序的数据。存储器主要用于存储软件程序和数据。射频电路主要用于基带信号与射频信号的转换以及对射频信号的处理。天线主要用于收发电磁波形式的射频信号。输入输出装置，例如触摸屏、显示屏，键盘等主要用于接收用户输入的数据以及对用户输出数据。
当终端设备开机后，处理器可以读取存储单元中的软件程序，解析并执行软件程序的指令，处理软件程序的数据。当需要通过无线发送数据时，处理器对待发送的数据进行基带处理后，输出基带信号至射频电路，射频电路将基带信号进行处理后得到射频信号并将射频信号通过天线以电磁波的形式向外发送。当有数据发送到终端设备时，射频电路通过天线接收到射频信号，该射频信号被进一步转换为基带信号，并将基带信号输出至处理器，处理器将基带信号转换为数据并对该数据进行处理。
为了便于说明，图10仅示出了一个存储器和处理器。在实际的终端设备中，可以存在多个处理器和存储器。存储器还可以称为存储介质或者存储设备等，本申请实施例对此不做限制。
作为一种可选的实现方式，处理器可以包括基带处理器和中央处理器，基带处理器主要用于对通信协议以及通信数据进行处理，中央处理器主要用于对整个终端设备进行控制，执行软件程序，处理软件程序的数据。图10中的处理器集成了基带处理器和中央处理器的功能，本领域技术人员可以理解，基带处理器和中央处理器可以是各自独立的处理器，通过总线等技术互联。本领域技术人员可以理解，终端设备可以包括多个基带处理器以适应不同的网络制式，终端设备可以包括多个中央处理器以增强其处理能力，终端设备的各个部件可以通过各种总线连接。基带处理器还可以表述为基带处理电路或者基带处理芯片。中央处理器还可以表述为中央处理电路或者中央处理芯片。对通信协议以及通信数据进行处理的功能可以内置在处理器中，或者可以以软件程序的形式存储在存储单元中，由处理器执行软件程序以实现基带处理功能。
在一个例子中，可以将具有收发功能的天线和控制电路视为终端设备101的收发单元，将具有处理功能的处理器视为终端设备101的处理单元。收发单元还可以称为收发器、收发机、收发装置等。可选地，可以将收发单元中用于实现接收功能的器件视为接收单元，将收发单元中用于实现发送功能的器件视为发送单元，即收发单元包括接收单元和发送单元。示例性的，接收单元还可以称为接收机、接收器、接收电路等，发送单元可以称为发射机、发射器或者发射电路等。可选地，上述接收单元和发送单元可以是集成在一起的一个单元，或者可以是各自独立的多个单元。上述接收单元和发送单元可以在一个地理位置，或者可以分散在多个地理位置。
在一个实施例中，收发单元用于执行上述实施例中收发单元801执行的操作。处理单元用于执行上述实施例中处理单元802执行的操作。该终端设备101还可以用于执行上述图3方法实施例中终端设备或网络设备执行的任一方法，在此不再赘述。
本申请实施例还提供一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时可以实现上述方法实施例提供的通信方法中相关的流程。
本申请实施例还提供一种计算机程序产品，该计算机程序产品用于存储计算机程序，当计算机程序在计算机(或处理器)上运行时，使得计算机执行上述任一个通信方法中的一个或多个步骤。上述所涉及的设备的各组成模块如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在计算机可读取存储介质中。
本申请实施例提供一种芯片，包括处理器，用于从存储器中调用并运行存储器中存储的指令，使得安装有芯片的通信装置执行上述任一方法。
本申请实施例还提供另一种芯片，包括：输入接口、输出接口和处理电路，输入接口、输出接口与电路之间通过内部连接通路相连，处理电路用于执行上述任一方法。可选地，芯片还包括存储器。输入接口、输出接口、处理器以及存储器之间通过内部连接通路相连，处理器用于执行存储器中的代码，当代码被执行时，处理器用于执行上述任一方法。
本申请实施例还提供一种芯片系统，包括至少一个处理器和通信接口，通信接口和至少一个处理器通过线路互联，至少一个处理器用于运行计算机程序或指令，以执行包括上述任意方法。该芯片系统，可以由芯片构成，或者可以包含芯片和其他分立器件。
本申请实施例还提供一种通信系统，该系统包括终端设备和网络设备，具体描述可以参考图3所示的方法。
应理解，本申请实施例中提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是硬盘(hard disk drive，HDD)、固态硬盘(solid-state drive，SSD)、ROM、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是RAM，其用作外部高速缓存。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
还应理解，本申请实施例中提及的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器或者可以是任何常规的处理器等。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)集成在处理器中。
应注意，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本领域普通技术人员可以意识到，结合本文中所提供的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者可以不是物理上分开的，作为单元显示的部件可以是或者可以不是物理单元，即可以位于一个地方，或者可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，或者可以是各个单元单独物理存在，或者可以两个或两个以上单元集成在一个单元中。
本申请实施例方法中的步骤可以根据实际需要进行顺序调整、合并和删减。每个实施例的步骤可以部分执行(比如，终端设备可以不执行上述实施例中由终端设备执行的步骤)。不同步骤的执行顺序可以变更。本文所描述的实施例可以与其它实施例相结合，不同实施例之间可以相互结合，本文的不同实施例的不同步骤可以结合。
本申请实施例装置中的模块/单元可以根据实际需要进行合并、划分和删减。
在本文中提及“实施例”意味着，结合实施例描述的特定特征、结构或特性可以包含在本申请的至少一个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例，不是与其它实施例互斥的独立的或备选的实施例。
本申请中可以是指通信协议或者说规范，例如3GPP通信协议。
本申请实施例中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本申请实施例中，“包括”可以是包含关系，或者可以是相等关系。比如，A包括B，可以是A包含B之外还可以包含其他内容，或者，A和B为同一内容。
在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A，B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，或者可以是多个。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。

Claims (28)

  1. 一种通信方法，其特征在于，包括：
    接收第一信息，所述第一信息包括所述载波组的信息，所述载波组包括调度载波和被调度载波；
    基于所述第一信息确定所述被调度载波的至少两个调度载波。
  2. 根据权利要求1所述的方法，其特征在于，所述被调度载波被至少两个所述载波组中的调度载波调度；或者所述被调度载波被所述载波组中的至少两个调度载波调度。
  3. 根据权利要求1或2所述的方法，其特征在于，所述载波组的信息包括所述载波组的载波组标识、所述载波组中调度载波的载波标识和所述载波组中被调度载波的载波标识。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，还包括：
    接收第二信息，所述第二信息包括第一载波组的载波组标识、第一调度载波的载波标识和第一被调度载波的载波标识中的至少一个；
    基于所述第二信息确定所述载波组的信息。
  5. 根据权利要求4所述的方法，其特征在于，所述第一信息中所述第一载波组的调度载波包括去激活的载波，所述第一调度载波为所述第一载波组更新的调度载波，且所述第一调度载波为激活的载波，所述第二信息包括所述第一调度载波的载波标识和所述第一载波组的载波组标识；
    所述基于所述第二信息确定所述载波组的信息，包括：
    基于所述第一载波组的载波组标识和所述第一调度载波的载波标识，更新所述第一载波组的信息中调度载波的载波标识。
  6. 根据权利要求4所述的方法，其特征在于，所述第一信息中所述第一载波组中的被调度载波包括所述第一被调度载波，且所述第一被调度载波为去激活的载波，所述第二信息包括所述第一被调度载波的载波标识；
    所述基于所述第二信息确定所述载波组的信息，包括：
    基于所述第一被调度载波的载波标识，在所述第一载波组的信息中删除所述第一被调度载波的载波标识。
  7. 根据权利要求4所述的方法，其特征在于，所述第一被调度载波为所述第一载波组更新的被调度载波，且所述第一被调度载波为激活的载波，所述第二信息包括所述第一被调度载波的载波标识和所述第一载波组的载波组标识；
    所述基于所述第二信息确定所述载波组的信息，包括：
    基于所述第一载波组的载波组标识和所述第一被调度载波的载波标识，在所述第一载波组的信息中增加所述第一被调度载波的载波标识。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，还包括：
    基于所述被调度载波的载波标识所在的位置确定所述被调度载波的载波指示域CIF。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，还包括：
    基于第三信息在第一时间单元对第二调度载波进行物理下行控制信道PDCCH盲检，所述第三信息为配置信息或预定义信息。
  10. 根据权利要求9所述的方法，其特征在于，所述第三信息包括以下至少一项：
    盲检条件；或者
    优先检测的载波标识；或者
    所述调度载波的时域图案。
  11. 根据权利要求9或10所述的方法，其特征在于，还包括：
    基于所述调度载波的被调度载波的载波个数，确定在所述调度载波上的PDCCH盲检的次数。
  12. 根据权利要求11所述的方法，其特征在于，所述PDCCH盲检的次数包括最大盲检PDCCH候选次数，和/或最大非重叠控制信道单元CCE的个数。
  13. 根据权利要求9至12中任一项所述的方法，其特征在于，还包括：
    接收第一下行控制信息DCI，所述第一DCI用于指示是否在第三调度载波上进行PDCCH盲检；或所述第一DCI用于指示是否在所述第三调度载波中盲检第二被调度载波的第二DCI，所述第二被调度载波被所述第三调度载波调度。
  14. 一种通信方法，其特征在于，包括：
    确定第一信息，所述第一信息包括所述载波组的信息，所述载波组包括调度载波和被调度载波，所述被调度载波对应至少两个调度载波；
    发送所述第一信息。
  15. 根据权利要求14所述的方法，其特征在于，所述被调度载波被至少两个所述载波组中的调度载波调度；或者所述被调度载波被所述载波组中的至少两个调度载波调度。
  16. 根据权利要求14或15所述的方法，其特征在于，所述载波组的信息包括所述载波组的载波组标识、所述载波组中调度载波的载波标识和所述载波组中被调度载波的载波标识。
  17. 根据权利要求14至16中任一项所述的方法，其特征在于，还包括：
    发送第二信息，所述第二信息包括第一载波组的载波组标识、第一调度载波的载波标识和第一被调度载波的载波标识中的至少一个。
  18. 根据权利要求17所述的方法，其特征在于，
    所述第一信息中所述第一载波组的调度载波包括去激活的载波，所述第一调度载波为所述第一载波组更新的调度载波，且所述第一调度载波为激活的载波，所述第二信息包括所述第一调度载波的载波标识和所述第一载波组的载波组标识；或者
    所述第一信息中所述第一载波组中的被调度载波包括所述第一被调度载波，且所述第一被调度载波为去激活的载波，所述第二信息包括所述第一被调度载波的载波标识；或者
    所述第一被调度载波为所述第一载波组更新的被调度载波，且所述第一被调度载波为激活的载波，所述第二信息包括所述第一被调度载波的载波标识和所述第一载波组的载波组标识。
  19. 根据权利要求14至18中任一项所述的方法，其特征在于，还包括：
    发送第三信息，所述第三信息用于指示在第一时间单元对第二调度载波进行物理下行控制信道PDCCH盲检。
  20. 根据权利要求19所述的方法，其特征在于，所述第三信息包括以下至少一项：
    盲检条件；或者
    优先检测的载波标识；或者
    所述调度载波的时域图案。
  21. 根据权利要求19或20所述的方法，其特征在于，还包括：
    发送第一下行控制信息DCI，所述第一DCI用于指示是否在第三调度载波上进行PDCCH盲检；或所述第一DCI用于指示是否在所述第三调度载波中盲检第二被调度载波的第二DCI，所述第二被调度载波被所述第三调度载波调度。
  22. 一种通信装置，其特征在于，包括：包括用于执行如权利要求1至21中任一项所述的方法对应的单元。
  23. 一种通信装置，其特征在于，包括处理器，所述处理器用于运行计算机程序或指令以使得所述通信装置执行如权利要求1至21中任一项所述的方法。
  24. 根据权利要求23所述的通信装置，其特征在于，所述通信装置还包括存储器，所述存储器用于存储所述计算机程序或指令。
  25. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质包括指令，当所述指令被处理器运行时，使得根据权利要求1至21中任一项所述的方法被实现。
  26. 一种计算机程序产品，其特征在于，所述计算机程序产品包括一个或多个计算机程序，当所述计算机程序在计算机上运行时，使所述计算机执行如权利要求1至21中任一项所述的方法。
  27. 一种芯片，其特征在于，包括处理器，用于从存储器中调用并运行所述存储器中存储的指令，使得安装有芯片的通信装置执行如权利要求1至21中任意一项所述的方法。
  28. 一种通信系统，其特征在于，所述通信系统包括终端设备和网络设备，所述终端设备用于执行根据权利要求1至13中任一项所述的方法，所述网络设备用于执行根据权利要求14至21中任一项所述的方法。
PCT/CN2025/100495 2024-06-14 2025-06-11 通信方法及相关装置 Pending WO2025256567A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410777371.4 2024-06-14
CN202410777371.4A CN121152027A (zh) 2024-06-14 2024-06-14 通信方法及相关装置

Publications (1)

Publication Number Publication Date
WO2025256567A1 true WO2025256567A1 (zh) 2025-12-18

Family

ID=97990852

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/100495 Pending WO2025256567A1 (zh) 2024-06-14 2025-06-11 通信方法及相关装置

Country Status (2)

Country Link
CN (1) CN121152027A (zh)
WO (1) WO2025256567A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114073034A (zh) * 2019-07-05 2022-02-18 高通股份有限公司 多个跨载波调度分量载波(cc)
WO2022193247A1 (zh) * 2021-03-18 2022-09-22 北京小米移动软件有限公司 载波的调度方法及其装置、调度模式的切换方法及其装置
CN115209459A (zh) * 2021-04-09 2022-10-18 大唐移动通信设备有限公司 多载波的检测方法、装置及处理器可读存储介质
CN116982382A (zh) * 2021-03-19 2023-10-31 高通股份有限公司 用于跨越分量载波的控制信道重复的技术

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114073034A (zh) * 2019-07-05 2022-02-18 高通股份有限公司 多个跨载波调度分量载波(cc)
WO2022193247A1 (zh) * 2021-03-18 2022-09-22 北京小米移动软件有限公司 载波的调度方法及其装置、调度模式的切换方法及其装置
CN116982382A (zh) * 2021-03-19 2023-10-31 高通股份有限公司 用于跨越分量载波的控制信道重复的技术
CN115209459A (zh) * 2021-04-09 2022-10-18 大唐移动通信设备有限公司 多载波的检测方法、装置及处理器可读存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
PETER GAAL, QUALCOMM INCORPORATED: "Multi-cell PUSCH/PDSCH scheduling with a single DCI", 3GPP DRAFT; R1-2301429; TYPE DISCUSSION; NR_MC_ENH-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Athens, GR; 20230227 - 20230303, 17 February 2023 (2023-02-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052248561 *

Also Published As

Publication number Publication date
CN121152027A (zh) 2025-12-16

Similar Documents

Publication Publication Date Title
US11825476B2 (en) Communication of direct current (DC) tone location
JP7292268B2 (ja) ブロードキャストチャネルのためのレートマッチング
AU2016245681B2 (en) PUCCH resource allocation method in carrier aggregation and equipments thereof
JP2021503834A (ja) マルチキャリア通信のためのキャリア・スイッチング方法、装置およびシステム
TW201836422A (zh) 具有對時槽內躍頻的支援的單時槽短pucch
US12101737B2 (en) Paging occasion and paging early indication configuration for different types of user equipments
TWI542184B (zh) An up and down configuration of the instructions, determine the method and the base station, the terminal
WO2020029996A1 (zh) 检测dci的方法、配置pdcch的方法和通信装置
TW202139748A (zh) 針對應用的切片分配和介面
CN111278137A (zh) 上行资源的授权方法、装置及系统
TWI907670B (zh) 在多波束ｐｕｓｃｈ重複上的增強的非週期性或半持久性通道狀態資訊報告
WO2018228586A1 (zh) 一种通信方法、网络设备及用户设备
CN109937544A (zh) 异步ca处理
JP2023512807A (ja) 無線通信において、低減した能力のデバイスをサポートする方法及び装置
CN117460007A (zh) 一种小区状态切换方法及装置
WO2018228537A1 (zh) 信息发送、接收方法及装置
CN117941432A (zh) 用于多个传输接收点(m-trp)的多物理上行链路共享信道(pusch)调度
US12149459B2 (en) Technologies for reliable physical data channel reception in wireless communications
CN114503755A (zh) 用于上行链路传输跳过的处置的方法和设备
US20230354125A1 (en) Enhanced measurement object configurations and procedures
US12063661B2 (en) Compact downlink control information with preconfigured scheduling parameters
WO2025256567A1 (zh) 通信方法及相关装置
KR20240068649A (ko) 불연속 커버리지를 갖는 plmn에 대한 퍼블릭 랜드 모바일 네트워크(plmn) 스캐닝
WO2022021049A1 (en) Application link direction based network slice selection
WO2021204169A1 (zh) 一种通信方法和装置

Legal Events

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

Ref document number: 25821273

Country of ref document: EP

Kind code of ref document: A1