Frequency-domain resource scheduling method and related product

Abstract

Disclosed in the present application are a frequency-domain resource scheduling method and a related product. The method comprises: a terminal device receiving first configuration information sent by a network device, wherein the first configuration information indicates a multi-carrier frequency-domain resource configured for the terminal device, the multi-carrier frequency-domain resource meets constraint information of the multi-carrier frequency-domain resource that the terminal device can support, and the multi-carrier includes a first carrier and a second carrier; and on the basis of the multi-carrier frequency-domain resource, sending a signal on the first carrier and the second carrier. By using the method in the embodiments of the present application, the high-efficiency and high-quality joint scheduling of multi-carrier frequency-domain resources in a multi-carrier aggregation scenario can be achieved.

Description

Frequency domain resource scheduling method and related product

[0001] The present application claims priority from the Chinese patent application No. 202411059977.0 filed on August 2, 2024, and entitled "Frequency domain resource scheduling method and related product", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, in particular to a frequency domain resource scheduling method and related product. BACKGROUND

[0003] The fourth generation long term evolution (4G LTE) and 5G new radio (NR) wireless communication systems both support Intra-band carrier aggregation (CA) features to fully utilize the multiple component carrier (CC) spectrum resources of the same frequency band of the operator, and increase the UE uplink / downlink data rate and throughput. Among them, according to whether the multiple component carrier spectrum in the same frequency band is continuously allocated or non-continuously allocated, it can be divided into Intra-band contiguous CA feature and Intra-band non-contiguous CA feature.

[0004] In R18 5G NR, the multi-cell scheduling with a single DCI (MB-SC) feature using a single downlink control information (DCI) is introduced into the 3rd generation partnership project (3GPP) protocol. This feature supports a single DCI to schedule multiple carriers or cells simultaneously. This feature optimizes the protocol stack and DCI design for multi-carrier scheduling, increases the flexibility and spectrum utilization when multiple cells simultaneously carry scheduling data, and reduces the air interface signaling capability overhead of simultaneously scheduling multiple carriers. At the same time, this feature provides a way for network-side multi-carrier scheduling to jointly allocate frequency domain resources (FDRA).

[0005] In the prior art, for the continuous or discontinuous CA / (or) double connected (DC) of the uplink (UL) in-band of the NR, no more constraints and joint scheduling optimization considerations are made on the RB scheduling at the network side, but each uplink carrier is separately scheduled. Although the flexibility is large, the scheduling of the UE implementation is not fully considered, and the constraints of the radio frequency indicators are not considered. For example, a small number of resource blocks (RBs) are allocated for each carrier, which will generate a sharp and discrete type of spurious from the perspective of the UE radio frequency, and the UE will perform a large power backoff to meet the existing radio frequency indicators, and even generate intermodulation interference to other downlink bands. From the network perspective, two carriers are activated at the same time, but only a small number of UL RBs are scheduled for each carrier, and the scheduling efficiency is extremely low. Therefore, similar scheduling has little benefit of carrier aggregation but has great disadvantages, and a more efficient method should be used to optimize the scheduling of the continuous and discontinuous CA of the UL in-band. SUMMARY

[0006] Embodiments of the present application provide a frequency domain resource scheduling method and related products, which can realize efficient and high-quality joint scheduling of multiple carrier frequency domain resources in a multi-carrier aggregation scenario.

[0007] In a first aspect, the present application provides a frequency domain resource scheduling method. The method comprises: receiving first configuration information, the first configuration information indicating a plurality of carrier frequency domain resources configured for a terminal device, the plurality of carrier frequency domain resources satisfying constraint information of a plurality of carrier frequency domain resources that the terminal device can support, the plurality of carriers including a first carrier and a second carrier; and transmitting a signal on the first carrier and the second carrier according to the plurality of carrier frequency domain resources.

[0008] The first aspect scheme can be executed by a terminal device or a module (such as a chip system) in the terminal device, and can also be executed by a logical node, a logical module or software that can realize all or part of the functions of the terminal device, and the present application is not limited in this regard.

[0009] In embodiments of the present application, the network device obtains the constraint information of the plurality of carrier frequency domain resources that the terminal device can support, and sends the first configuration information to the terminal device according to the constraint information, to complete the configuration of the plurality of carrier frequency domain resources of the terminal device. In this way, the problems of low scheduling efficiency caused by configuring a small number of frequency domain resources for the plurality of carriers, and the reduction of signal quality caused by the terminal device to meet the radio frequency indicators, etc. can be avoided. The technical effects of improving the frequency domain resource scheduling efficiency and guaranteeing the signal transmission quality of the terminal device are achieved.

[0010] In a feasible implementation, the constraint information includes: a minimum proportion of discontinuous frequency domain resource scheduling that the terminal device can support in the span of the plurality of carrier frequency domain resources.

[0011] In an implementation, the minimum proportion of the multi-carrier frequency domain span occupied by the non-continuous frequency domain resource scheduling that the terminal device can support satisfies the following formula:

[0012] wherein W crb1 represents the frequency domain width resource configured for the terminal device on the first carrier, W crb2 represents the frequency domain width resource configured for the terminal device on the second carrier, f E2 represents the frequency corresponding to the terminal resource block RB allocated by the second carrier, f S1 represents the frequency corresponding to the starting RB allocated by the first carrier, and X% represents the minimum proportion of the multi-carrier frequency domain span occupied by the non-continuous frequency domain resource scheduling that the terminal device can support.

[0013] In an implementation, the constraint information comprises: the minimum frequency domain resource metric value that the terminal device can support.

[0014] In an implementation, the multi-carrier frequency domain resource and the minimum frequency domain resource metric value that the terminal device can support satisfy the following formula: W crb1 +W crb2 ≥Y

[0015] wherein W crb1 represents the frequency domain width resource configured for the terminal device on the first carrier, W crb2 represents the frequency domain width resource configured for the terminal device on the second carrier, and Y represents the minimum frequency domain resource metric value that the terminal device can support.

[0016] In an implementation, the constraint information comprises: the minimum number of RBs that the terminal device can support.

[0017] In an implementation, the multi-carrier frequency domain resource and the minimum number of RBs that the terminal device can support satisfy the following condition: L crb1 ×2 μ1 +L crb2 ×2 μ2 ≥Z

[0018] wherein L crb1 represents the number of RBs configured for the terminal device on the first carrier, L crb2 represents the number of RBs configured for the terminal device on the second carrier, μ1 represents a parameter corresponding to the subcarrier spacing on the first carrier, μ2 represents a parameter corresponding to the subcarrier spacing on the second carrier, and Z represents the minimum number of RBs that the terminal device can support.

[0019] In an implementation, Z satisfies: Z=Z1×max(N RB1 ×2 μ1 ,NRB2 x2 μ2 ); or Z = Z1 x min(N RB1 x2 μ1 , N RB2 x2 μ2 ); or

[0020] wherein Z1 represents a scaling factor, N RB1 represents the maximum number of RBs that can be configured on the first carrier, and N RB2 represents the maximum number of RBs that can be configured on the second carrier.

[0021] In the embodiments of the present application, the constraint condition set is a minimum proportion of non-continuous frequency domain resource scheduling in the frequency domain span of the multi-carrier or a minimum frequency domain width resource. That is, the minimum frequency domain resource of the multi-carrier is set. Firstly, the resource of the joint scheduling frequency domain is limited instead of being isolated, which guarantees the overall performance of the joint scheduling. Secondly, by limiting the minimum frequency domain resource of the multi-carrier scheduling, the problem of low scheduling efficiency and radio frequency performance deterioration caused by the network device configuring too few RB frequency domain resources for the UE can be effectively avoided.

[0022] In a possible implementation, before receiving the first configuration information, the method further includes: sending first information, the first information indicating constraint information of the multi-carrier frequency domain resource that the terminal device can support.

[0023] In a possible implementation, the first configuration information is carried in a downlink control information (DCI).

[0024] In a possible implementation, the first configuration information is carried in a first field of the DCI, and the first field indicates the multi-carrier frequency domain resource configured for the terminal device by using a bit map or a resource indication value (RIV).

[0025] In a possible implementation, the first configuration information is carried in a DCI of format 0_3; or the first configuration information is carried in a DCI of format 0_0 and / or format 0_1.

[0026] In the embodiments of the present application, the first configuration information is sent in a newly added field of the DCI, which can guarantee the sending efficiency of the first configuration information. The first configuration information is sent in two fields in an existing format of the DCI, which can reduce the modification of the format of the DCI, reduce the complexity of sending the first configuration information, and reduce the number of signaling interactions. The first configuration information is sent in two DCIs in an existing format, respectively, which can further reduce the modification of the format of the DCI and reduce the complexity of sending the first configuration information.

[0027] In a second aspect, the present application provides a frequency domain resource scheduling method. The method comprises: obtaining first information, wherein the first information comprises constraint information of a multi-carrier frequency domain resource that can be supported by a terminal device; and sending first configuration information, wherein the first configuration information comprises a multi-carrier frequency domain resource configured for the terminal device, and the multi-carrier frequency domain resource satisfies the constraint information of the multi-carrier frequency domain resource that can be supported by the terminal device.

[0028] The second aspect can be executed by a network device or a module (such as a chip system) in the network device, and can also be executed by a logic node, a logic module or software that can realize all or part of the functions of the network device, and the present application is not limited in this regard.

[0029] In a feasible implementation, obtaining the first information comprises: receiving the first information from the terminal device; or obtaining the first information according to preset information.

[0030] In a feasible implementation, the multi-carrier comprises a first carrier and a second carrier, and the method further comprises: receiving an uplink signal from the terminal device, wherein the uplink signal is transmitted on the first carrier and the second carrier according to the multi-carrier frequency domain resource.

[0031] In a third aspect, the present application provides a frequency domain resource scheduling method. The method comprises: obtaining third information, wherein the third information indicates that a carrier center position of a terminal device is allowed to be located within an interval between a first carrier and a second carrier in a multi-carrier; and sending second information to a network device, wherein the second information indicates a carrier center position set by the terminal device when transmitting the multi-carrier through a power amplifier (PA), and the carrier center position is determined according to a center frequency domain position of the interval between the first carrier and the second carrier in the multi-carrier, or the carrier center position is determined according to a center frequency domain position of a sum of a frequency bandwidth of the first carrier, a frequency bandwidth of the second carrier and the interval between the first carrier and the second carrier.

[0032] The third aspect can be executed by a terminal device or a module (such as a chip system) in the terminal device, and can also be executed by a logic node, a logic module or software that can realize all or part of the functions of the terminal device, and the present application is not limited in this regard.

[0033] In the embodiments of the present application, when the network device allows the carrier leakage of the terminal device to be located within the interval of the multi-carrier, the terminal device reports the carrier center position, so that the network device configures the frequency domain resource of the multi-carrier for the terminal device based on the carrier center position. The carrier leakage of the terminal device can be located within the interval of the two carriers, and the mirror image leakage of the carrier will not be located within the interval of the two carriers, which helps the terminal device to more easily meet the radio frequency index requirements within the interval without large power backoff.

[0034] In an implementation, the carrier center position is determined according to a center frequency domain position of the interval between the first carrier and the second carrier.

[0035] In an implementation, the multi-carrier frequency domain resource and the carrier center position satisfy:

[0036] wherein f c1 represents the carrier center position, f H1 represents a high boundary of a channel edge corresponding to the first carrier, f L2 represents a low boundary of a channel edge corresponding to the second carrier, the first carrier is a carrier with the smallest center frequency, the second carrier is a carrier with the largest center frequency, and N is a frequency fine adjustment value equal to or greater than 0.

[0037] In an implementation, the multi-carrier frequency domain resource satisfies: max[(f E2 -f L2 ), (f H1 -f S1 )]≤min(BW1,BW2)

[0038] wherein f E2 represents a frequency of an end RB allocated by the second carrier, f S1 represents a frequency of a start RB allocated by the first carrier, f L2 represents the low boundary of the channel edge of the second carrier, f H1 represents the high boundary of the channel edge of the first carrier, BW1 represents a bandwidth of the first carrier, and BW2 represents a bandwidth of the second carrier.

[0039] In an implementation, the carrier center position is determined according to a center frequency domain position of a sum of a frequency band width of the first carrier, a frequency band width of the second carrier, and an interval between the first carrier and the second carrier.

[0040] In an implementation, the multi-carrier frequency domain resource and the carrier center position satisfy:

[0041] wherein f c2 represents the reported carrier center position, f H2 represents the high boundary of the channel edge corresponding to the second carrier, f L1 represents the low boundary of the channel edge corresponding to the first carrier, the first carrier is the carrier with the smallest center frequency, the second carrier is the carrier with the largest center frequency, and N is the frequency fine adjustment value equal to or greater than 0.

[0042] In an implementation, the multi-carrier frequency domain resource further satisfies: max[(f H2 -f S2 ), (fE1 -f L1 )]≤min(BW1,BW2)

[0043] wherein, f E1 denotes the frequency of the last RB allocated by the first carrier, f S2 denotes the frequency of the first RB allocated by the second carrier, f H2 denotes the upper boundary of the second carrier channel edge, f L1 denotes the lower boundary of the first carrier channel edge, BW1 denotes the bandwidth of the first carrier, and BW2 denotes the bandwidth of the second carrier.

[0044] In an implementation, the third information is obtained according to preset information or is received from the network device.

[0045] In an implementation, the third information is carried in cell group configuration signaling.

[0046] In a fourth aspect, the present application provides a frequency domain resource scheduling method. The method comprises: sending third information to a terminal device, the third information indicating that a carrier center position of the terminal device is allowed to be located in an interval between a first carrier and a second carrier in a plurality of carriers; and receiving second information from the terminal device, the second information indicating a carrier center position set by the terminal device when the terminal device transmits the plurality of carriers through one power amplifier (PA), the carrier center position being determined according to a center frequency domain position of the interval between the first carrier and the second carrier in the plurality of carriers, or the carrier center position being determined according to a center frequency domain position of a sum of a frequency bandwidth of the first carrier, a frequency bandwidth of the second carrier, and the interval between the first carrier and the second carrier.

[0047] In a fifth aspect, the present application provides a frequency domain resource scheduling method. The method comprises: receiving second information from a terminal device, the second information indicating a carrier center position set by the terminal device when the terminal device transmits a plurality of carriers through one power amplifier (PA), the carrier center position being determined according to a center frequency domain position of an interval between a first carrier and a second carrier in the plurality of carriers, or the carrier center position being determined according to a center frequency domain position of a sum of a frequency bandwidth of the first carrier, a frequency bandwidth of the second carrier, and the interval between the first carrier and the second carrier; and sending second configuration information, the second configuration information comprising a plurality of carrier frequency domain resources configured for the terminal device, the plurality of carrier frequency domain resources being configured based on the carrier center position set by the terminal device.

[0048] The scheme of the fourth aspect or the fifth aspect can be executed by a network device or a module (such as a chip system, etc.) in the network device, and can also be executed by a logic node, a logic module, or software capable of realizing all or part of the functions of the network device, and no limitation is made in this regard.

[0049] In a sixth aspect, a communication apparatus is provided, which comprises units or modules for performing the method in any of the first to fifth aspects.

[0050] In a seventh aspect, an embodiment of the present application provides a communication apparatus, which comprises at least one processor coupled with a memory; wherein the at least one processor is configured to execute computer programs or instructions stored in the memory, so that the method in any of the first to fifth aspects is performed.

[0051] In an eighth aspect, an embodiment of the present application provides a communication system, which comprises a first apparatus and a second apparatus, wherein the first apparatus is configured to perform the method in any of the first aspect, and the second apparatus is configured to perform the method in any of the second aspect. Or the first apparatus is configured to perform the method in any of the third aspect, and the second apparatus is configured to perform the method in the fourth aspect or the fifth aspect.

[0052] In a ninth aspect, an embodiment of the present application provides a computer readable storage medium, which stores computer instructions, when the computer instructions are executed, the computer is caused to perform the method in any of the above aspects.

[0053] In a tenth aspect, an embodiment of the present application provides a computer program product, which comprises computer program codes, when the computer program codes are run by a computer, the computer is caused to perform the method in any of the above aspects.

[0054] In an eleventh aspect, an embodiment of the present application provides a chip, which is coupled with a memory, and is configured to read and execute program instructions in the memory, so that the apparatus in which the chip is located implements the method in any of the above aspects. BRIEF DESCRIPTION OF DRAWINGS

[0055] The drawings used by the embodiments of the present application are described below.

[0056] FIG. 1A is a wireless communication system architecture provided by an embodiment of the present application.

[0057] FIG. 1B is a connection diagram of a terminal device and a network device provided by an embodiment of the present application.

[0058] FIG. 1C is an example diagram of an O-RAN system provided by an embodiment of the present application.

[0059] FIG. 1D is a network element function division and protocol layer structure diagram of an O-RAN device provided by an embodiment of the present application.

[0060] FIG. 2A is a schematic diagram of in-band carrier aggregation provided by an embodiment of the present application.

[0061] FIG. 2B is a diagram illustrating a scattered distribution generated by the number of RBs of in-band UL CA according to an embodiment of the present application.

[0062] FIG. 3A is a flowchart illustrating a resource scheduling method according to an embodiment of the present application.

[0063] FIG. 3B is a diagram illustrating a carrier frequency domain resource in UL CA according to an embodiment of the present application.

[0064] FIG. 3C is a diagram illustrating a method of sending first configuration information to a UE by DCI according to an embodiment of the present application.

[0065] FIG. 4A is a diagram illustrating a composite SEM radio frequency index of UL in-band non-continuous CA according to an embodiment of the present application.

[0066] FIG. 4B is a flowchart illustrating another resource scheduling method according to an embodiment of the present application.

[0067] FIG. 4C is a diagram illustrating a method of sending third information to a UE by signaling by a network device according to an embodiment of the present application.

[0068] FIG. 4D is a diagram illustrating a frequency domain resource scheduling of a multi-carrier according to an embodiment of the present application.

[0069] FIG. 5A is a flowchart illustrating another frequency domain resource scheduling method according to an embodiment of the present application.

[0070] FIG. 5B is a diagram illustrating a frequency domain resource scheduling of a multi-carrier according to an embodiment of the present application.

[0071] FIG. 6 is a diagram illustrating a structure of a communication apparatus according to an embodiment of the present application.

[0072] FIG. 7 and FIG. 8 are diagrams illustrating a structure of a network device according to an embodiment of the present application.

[0073] FIG. 9 and FIG. 10 are diagrams illustrating a structure of a UE according to an embodiment of the present application. DETAILED DESCRIPTION

[0074] The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. In the embodiments of the present application, the terms "system" and "network" can be used interchangeably. Unless otherwise specified, " / " represents an "or" relationship between the objects before and after the " / " symbol, for example, A / B can represent A or B; in the present application, "and / or" is only used to describe the relationship between the associated objects, which means that there can be three relationships, for example, A and / or B can represent: A alone, A and B together, and B alone, where A and B can be singular or plural. In addition, in the description of the present application, "multiple" means two or more than two. "At least one of the following" or the like means any combination of the items, including any combination of single item or multiple items. For example, 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 one or more. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, the same items or similar items with basically the same function are distinguished by "first", "second", etc. The skilled in the art can understand that "first", "second", etc. do not limit the quantity and execution order, and "first", "second", etc. do not necessarily mean different.

[0075] In the embodiments of the present application, the reference to "one embodiment" or "some embodiments" means that the specific features, structures or characteristics described in connection with the embodiment are included in one or more embodiments of the present application. Therefore, the statements "in one embodiment", "in some embodiments", "in other some embodiments", "in other some embodiments" and the like appearing in different places in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized. The terms "include", "contain", "have" and their variants mean "include but not limited to", unless otherwise specifically emphasized. In addition, in the embodiments of the present application, the words "example", "for example" and the like are used to mean by way of example, illustration or description. Any embodiment or design scheme described as "example" in the present application should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. Rather, the word "example" is intended to present the concept in a specific manner.

[0076] In the embodiments of the present application, "information", "signal", "message", "channel", and "signaling" can be used interchangeably at times. It should be pointed out that when the distinction is not emphasized, the meanings expressed are matched. "Of", "corresponding", and "corresponding" can be used interchangeably at times. It should be pointed out that when the distinction is not emphasized, the meanings expressed are matched. In addition, " / " mentioned in the present application can be used to represent "or" relationship.

[0077] The following detailed description further illustrates the objectives, technical solutions and beneficial effects of the present application. It should be understood that the following is only a specific embodiment of the present application and does not limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made on the basis of the technical solutions of the present application shall be included in the protection scope of the present application.

[0078] In various embodiments of the present application, the terms and / or descriptions of different embodiments are consistent and can be mutually referred to if there is no special description and logical conflict. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0079] The system architecture related to the embodiments of the present application is introduced below.

[0080] The embodiments of the present application are mainly used for air interface physical layer process, and the system architecture can use the existing NR system architecture. The present application can be applied to the existing cellular communication system, and can also be used in any other wireless communication system with similar structure and function. Referring to FIG. 1A, FIG. 1A is a wireless communication system architecture provided by an embodiment of the present application. As shown in FIG. 1A, the wireless communication system can include network device 110 and terminal devices 101-106, which can specifically include mobile phones, vehicles, tablets, smart speakers, train detectors, gas station sensors, etc.

[0081] Referring to FIG. 1B, FIG. 1B is a connection diagram of a terminal device and a network device according to an embodiment of the present application. As shown in FIG. 1B, the terminal device and the network device are connected through the air interface.

[0082] The terminal involved in the embodiments of the present application can also be referred to as a terminal device, a user equipment (UE), and the like. The terminal device is an entity on the user side for receiving or transmitting signals, used for sending uplink signals to a network device or receiving downlink signals from the network device; the main functions include collecting data (part of the terminal device), receiving control information and downlink data of the network device, and transmitting electromagnetic waves to transmit uplink data to the network device. The terminal device can communicate with one or more core networks through the network device. The terminal device includes a handheld device with a wireless connection function, another processing device connected to a wireless modem, or a vehicle-mounted device, and the like. The terminal device can be a portable, pocket-sized, handheld, built-in computer, or vehicle-mounted mobile device. The terminal device can be widely used in various scenarios, such as cellular communication, D2D, V2X, point-to-point (P2P), machine-to-machine (M2M), machine type communication (MTC), internet of things (IoT), virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, remote medical treatment, smart power grid, smart furniture, smart office, smart wear, smart transportation, smart city, unmanned aerial vehicle, robot, remote sensing, passive sensing, positioning, navigation, autonomous delivery, and mobile, and the like.Some examples of the terminal device are: a user equipment (UE) of a 3GPP standard, a fixed device, a mobile device, a handheld device, a wearable device, a cellular phone, a smart phone, a session initiated protocol (SIP) phone, a notebook, a personal computer, a smart book, a vehicle, a satellite, a global positioning system (GPS) device, a drone, a helicopter, an aircraft, a ship, a remote control device, a smart home device, an industrial device, a personal communication service (PCS) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless webcam, a tablet, a palm computer, a mobile internet device (MID), a wearable device such as a smart watch, a VR device, an AR device, a wireless terminal in industrial control, a terminal in Internet of Vehicles, a wireless terminal in self-driving, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city such as a smart fuel dispenser, a terminal device on a high-speed rail, and a wireless terminal in a smart home such as a smart speaker, a smart coffee machine, a smart printer, etc. The terminal device can be a wireless device in the above various scenarios or an apparatus used in a wireless device, for example, a communication module, a modem, or a chip in the above devices, etc. The terminal device can also be referred to as a terminal, a terminal device, a UE, a mobile station (MS), a mobile terminal (MT), etc. The terminal device can also be a terminal device in a future wireless communication system. The terminal device can be used in a dedicated network device or a general-purpose device. The embodiments of the present application do not limit the specific technology and specific device form of the terminal device.

[0083] In this application, the communication device for realizing the function of the terminal device can be a terminal device, a terminal device with part of the function of the terminal device, or a device capable of supporting the function of the terminal device, such as a chip system, which can be installed in the terminal device or matched with the terminal device. In this application, the chip system can be composed of a chip or include a chip and other discrete devices. In the technical solutions provided in this application, the communication device is taken as an example for description.

[0084] The network device involved in the embodiments of the present application is used for receiving an uplink signal from a terminal device or transmitting a downlink signal to the terminal device. The network device can also be referred to as a base station (BS), a radio access network device, an access network element, a radio access network (RAN) node (or device or element), an access point (AP), a small tower, etc. The base station can be variously named or replaced by the following names in a broad sense, such as a radio access network (RAN) node, a NodeB, an evolved NodeB (eNB), a next generation NodeB (gNB), an access network device in an open radio access network (O-RAN), a relay station, an access point, a transmitting and receiving point (TRP), a transmitting point (TP), a master eNB (MeNB), a secondary eNB (SeNB), a multi-standard radio (MSR) node, a home base station, a network controller, an access node, a wireless node, an access point (AP), a transmission node, a transceiver node, a building baseband unit (BBU), a remote radio unit (RRU), an active antenna unit (AAU), a remote radio head (RRH), a centralized unit (CU), a distributed unit (DU), a radio unit (RU), a centralized unit control plane (CU-CP) node, a centralized unit user plane (CU-UP) node, a positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. The network device can also refer to a communication module, a modem, or a chip used in the foregoing devices or apparatuses.The network device can also be a mobile switching center, a device-to-device (D2D), vehicle-to-everything (V2X), machine-to-machine (M2M) communication device assuming a base station function, a network side device in a future communication system, and the like. The network device can support networks of the same or different access technologies. Embodiments of the present application do not limit the specific technology and specific device form adopted by the network device.

[0085] Referring to FIG. 1C, FIG. 1C is an example diagram of an O-RAN system according to an embodiment of the present application. As shown in FIG. 1C, the RAN node communicates with the CN device through a backhaul and communicates with the UE through an air interface. Specifically, the BBU in the RAN communicates with the CN device through a backhaul, and the RU in the access network device communicates with at least one UE through an air interface. The BBU communicates with at least one RU through a front-haul link. The BBU and the RU can be co-located or not co-located.

[0086] The BBU includes at least one CU and at least one DU, which can communicate through at least one mid-haul link.

[0087] Referring to FIG. 1D, FIG. 1D is a network element function division and protocol layer structure diagram of an O-RAN device according to an embodiment of the present application. As shown in FIG. 1D, in some examples, the CU is a logical node that carries the radio resource control (RRC) layer, the service data adaptation protocol (SDAP) layer, the packet data convergence protocol (PDCP) layer, and other control functions of the access network device. The CU is connected to network nodes such as the core network through some interfaces, which can be E2 interfaces and the like. Optionally, the CU can have part of the functions of the core network. The CU (e.g., the PDCP layer and higher layers) is connected to the DU (e.g., the RLC layer and lower layers) through some interfaces, which can be F1 interfaces and the like. In some examples, these interfaces (e.g., F1 interfaces) can provide control plane (C-Plane) and user plane (U-Plane) functions (e.g., interface management, system information management, UE context management, RRC message transmission, and the like). F1AP is an application protocol for the F1 interface, which defines the signaling procedures of F1 in some examples. The F1 interface supports control plane F1-C and user plane F1-U.

[0088] In some examples, the CU can be split into a CU-CP (control unit-control plane) and a CU-UP (control unit-user plane), where the CU-CP is a logical node carrying the RRC layer and the PDCP-C (control plane part of PDCP) layer, used to implement the control plane function of the CU. The CU-CP can interact with a network element in the core network used to implement the control plane function. The network element in the core network used to implement the control plane function can be an access and mobility function network element, such as an access and mobility management function (AMF) in a 5G system. The AMF network element is used to be responsible for mobility management in a mobile network, such as location updating of a terminal device, registration of the terminal device to a network, handover of the terminal device, and the like. The CU-UP is a logical node carrying the SDAP layer and the PDCP-U (user plane part of PDCP) layer, used to implement the user plane function of the CU. The CU-UP can interact with a network element in the core network used to implement the user plane function. The network element in the core network used to implement the user plane function, for example, a user plane function (UPF) in a 5G system, is used to be responsible for forwarding and receiving data in a terminal device. The above configuration of the CU and the DU is merely an example, and the CU and the DU can have functions according to needs. For example, the CU or the DU can be configured to have more protocol layer functions, or the CU or the DU can be configured to have partial processing functions of the protocol layer. For example, part of the functions of the RLC layer and the functions of the protocol layer above the RLC layer are arranged in the CU, and the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer are arranged in the DU. For another example, the functions of the CU or the DU can be divided according to the service type or other system requirements, for example, according to the delay. The functions that need to meet the delay requirement are arranged in the DU, and the functions that do not need to meet the delay requirement are arranged in the CU.

[0089] In some examples, a DU is a logical node that hosts radio link control (RLC) layer, medium access control (MAC) layer, higher physical layer (higher PHY) layer, and other functions. In some examples, a DU can control at least one RU. The DU is connected with the RUs through some interfaces, which can be a fronthaul interface. In some examples, the higher PHY layer includes parts of PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, and other processing functions.

[0090] In some examples, an RU is a logical node that hosts lower physical layer (lower PHY) and radio frequency (RF) processing. In some examples, an RU can be a 3GPP transmission reception point (TRP) or a remote radio head (RRH) or other similar functional entity. In some examples, the Low-PHY includes parts of PHY processing, such as fast Fourier transform (FFT), inverse fast Fourier transformation (IFFT), digital beamforming and filtering, and other processing functions. The RU communicates with one or more UEs over a wireless link.

[0091] The DU and the RU can be co-located or not co-located. The DU and the RU exchange control plane information and user plane information via a lower-layer split CUS-plane (LLS-CUS) interface through a fronthaul link. The LLS-CUS can include a LLS-C interface and a LLS-U interface that provide control plane (C-plane) and user plane (U-plane), respectively. In some examples, the control plane (C-plane) refers to real-time control between the DU and the RU. The DU and the RU exchange management information via a LLS-M interface of the fronthaul link, and the management plane (M-plane) refers to non-real-time management operations between the DU and the RU.

[0092] The DU and the RU can cooperate to jointly implement the functions of the PHY layer. One DU can be connected with one or more RUs. The functions of the DU and the RU can be configured in various manners according to design. For example, the DU is configured to implement baseband functions, and the RU is configured to implement radio frequency functions. For another example, the DU is configured to implement high-layer functions in the PHY layer, and the RU is configured to implement low-layer functions in the PHY layer or implement the low-layer functions and radio frequency functions. The high-layer functions in the PHY layer can include a part of functions of the PHY layer that are closer to the MAC layer, and the low-layer functions in the PHY layer can include another part of functions of the PHY layer that are closer to the radio frequency side.

[0093] In this application, the communication apparatus for implementing the access network functions as described above can be an access network device, can be a network device having part of the functions of the access network, or can be an apparatus capable of supporting the implementation of the access network functions, such as a chip system, a hardware circuit, a software module, or a hardware circuit plus a software module, which can be installed in or used in conjunction with the access network device. In the method of this application, the communication apparatus for implementing the functions of the access network device is taken as an example for description.

[0094] It should be understood that the number and types of devices in the communication system shown in FIG. 1A are only illustrative, and this application is not limited thereto. In actual applications, more terminal devices and more access network devices can be included in the communication system, and other network elements, such as network elements for implementing artificial intelligence functions, can also be included.

[0095] The prior art of the present embodiment is described below.

[0096] Referring to FIG. 2A, FIG. 2A is a schematic diagram of in-band carrier aggregation provided by the embodiment of the present application. As shown in (a) of FIG. 2A, it is in-band continuous carrier aggregation, that is, there are two component carriers (CCs) in the same frequency band, which are CC1 and CC2, and the frequencies of the two carriers are continuous. (b) of FIG. 2A is in-band non-continuous carrier, that is, there are two CCs in the same frequency band, and the frequencies of the two carriers are not continuous, but have a gap.

[0097] In particular, for uplink in-band carrier aggregation, from the perspective of the UE side, two radio frequency architectures are proposed, namely single power amplifier (PA) (single uplink (UL) transmission radio frequency link) and dual PA (two UL transmission radio frequency links). For the single PA radio frequency architecture, one uplink transmission link of the UE needs to simultaneously carry multiple carriers in one frequency band. For the dual PA radio frequency architecture, each uplink transmission link of the UE only needs to carry one carrier in one frequency band, for example, in a typical UL two-carrier scenario, two uplink transmission radio frequency links respectively carry two uplink carriers. Different uplink radio frequency architectures and different in-band carrier aggregation scenarios can have the following combinations.

[0098] Table 1

[0099] For the prior art of NR UL in-band continuous and in-band non-continuous CA / DC, no additional constraints and joint scheduling optimization considerations are made on the RB scheduling of the network side. The current technology is to separately schedule each uplink carrier, although the flexibility is large, but it fails to comprehensively consider the UE implementation for scheduling, and also fails to consider the constraints of radio frequency indicators.

[0100] Referring to FIG. 2B, FIG. 2B is a schematic diagram of the spur distribution generated by the number of RBs allocated for in-band UL CA according to an embodiment of the present application. As shown in FIG. 2B, corresponding to the case of allocating 1RB+1RB for two carriers (applicable to single PA or dual PA architecture), from the perspective of the UE radio frequency, a sharp discrete spur will be generated. That is, the output intermodulation distortion (IMD). Moreover, in order to meet the existing radio frequency indicator requirements, the UE will perform a large power backoff, and even generate intermodulation interference to other downlink frequency bands. From the perspective of the network, two carriers are simultaneously activated, but only a small number of UL RBs are scheduled for each carrier, and the scheduling efficiency is extremely low. Therefore, similar scheduling has little benefit of carrier aggregation but has great disadvantages, and a more efficient method should be used to optimize the scheduling of in-band continuous and UL in-band non-continuous CA.

[0101] Based on this, referring to FIG. 3A, a flowchart of a resource scheduling method is provided according to an embodiment of the present application, as shown in FIG. 3A, the method includes the following steps:

[0102] 101. The network device acquires first information, and the first information includes constraint information of a plurality of carrier frequency domain resources that can be supported by the terminal device.

[0103] The description of the network device and the terminal device in the embodiments of the present application can be referred to the foregoing description.

[0104] Optionally, the network device acquires the first information according to preset information, and the preset information includes protocol specification or default setting, etc.

[0105] Optionally, the network device receives the first information sent by the terminal device. That is, the terminal device sends the first information to the network device.

[0106] The constraint information of the multi-carrier frequency domain resource that the terminal device can support is that the multi-carrier frequency domain resource configured by the network device according to the constraint information can meet the demand of the terminal device. The multi-carrier indicates multiple carriers (corresponding to the carrier aggregation scenario), and specifically can include two or more than two carriers. The embodiments of the present application describe and illustrate the scenario of two carriers.

[0107] The embodiments of the present application provide the following several setting modes of the constraint information of the multi-carrier frequency domain resource that the terminal device can support:

[0108] 1. The minimum proportion of the non-continuous frequency domain resource scheduling that the terminal device can support accounts for the multi-carrier frequency domain span.

[0109] Exemplarily, the non-continuous frequency domain resource scheduling refers to the non-continuous frequency domain resource (or the actually scheduled RB resource) scheduled for CC1 and CC2. The multi-carrier frequency domain span refers to the span (or the sum of the actually scheduled RB resource and the interval not scheduled in the middle) between the starting position of the allocated RB of the carrier with the minimum center frequency and the ending position of the allocated RB of the carrier with the maximum center frequency.

[0110] Referring to FIG. 3B, FIG. 3B is a schematic diagram of the carrier frequency domain resource in the UL CA provided by the embodiments of the present application, as shown in (a) of FIG. 3B, the UL in-band continuous CA includes two continuous CCs, that is, CC1 and CC2. Among them, CC1 corresponds to bandwidth (bandwidth, BW) 1, and CC2 corresponds to BW2. The multi-carrier frequency domain span = f E2 -f S1 . The non-continuous frequency domain resource scheduling = W crb1 +W crb2 . Wherein W crb1 is the frequency domain width resource configured for the UE on the first carrier, W crb2 is the frequency domain width resource configured for the UE on the second carrier. f E2 indicates the frequency corresponding to the terminal resource block RB allocated by the second carrier, f S1 indicates the frequency of the starting RB allocated by the first carrier. Correspondingly, f E1 indicates the frequency corresponding to the terminal resource block RB allocated by the first carrier, f S2 indicates the frequency of the starting RB allocated by the second carrier.

[0111] Or as shown in (b) of FIG. 3B, two non-contiguous CCs, CC1 and CC2, are included in the UL in-band non-contiguous CA, i.e., there is a gap between CC1 and CC2. The meanings of other notations are the same as in (a) of FIG. 3B, which will not be repeated here.

[0112] Suppose that the minimum proportion of non-contiguous frequency domain resource scheduling that the UE can support occupies X% of the multi-carrier frequency domain span. Then the multi-carrier frequency domain resource configured for the UE needs to meet the following condition:

[0113] 2. The minimum frequency domain resource metric value that the terminal device can support.

[0114] Exemplarily, the minimum frequency domain resource that the UE can support refers to the minimum value of the sum of the frequency domain resources configured for multiple CCs in the UL CA that the UE can support. That is, W crb1 +W crb2 The minimum value.

[0115] (1) Suppose that the minimum frequency domain resource metric value that the UE can support is Y, Y is a frequency value. Then the multi-carrier frequency domain resource configured for the UE needs to meet the following condition: W crb1 +W crb2 ≥ Y (2)

[0116] (2) Suppose that the minimum frequency domain resource metric value is represented by the number of RBs, i.e., the minimum number of RBs that the UE can support is Z. Then the multi-carrier frequency domain resource configured for the UE needs to meet the following condition: L crb1 × 2 μ1 + L crb2 × 2 μ2 ≥ Z (3)

[0117] Wherein the relationship between Y and Z is: Wherein RBw refers to the frequency domain width of RB.

[0118] For example, when the subcarrier spacing (SCS) is 15 kHz, the frequency domain width of the corresponding RB is 15 kHz*12=180 kHz, then

[0119] L crb1 in formula (3) is the number of RBs allocated by the network side to the UE on the first carrier, L crb2 is the number of RBs allocated by the network side to the UE on the second carrier. W crb1 = L crb1 × SCS1; SCS1 is the subcarrier spacing of the first carrier. W crb2 = L crb2SCS2; SCS2 is a subcarrier spacing of the second carrier. SCS1 and SCS2 can be the same or different.

[0120] μ1 is a parameter corresponding to SCS1, and μ2 is a parameter corresponding to SCS2. For example, the value of μ corresponding to SCS is shown in the following table:

[0121] Table 2

[0122] That is, when SCS is 15 kHz, the value of μ is 0, and so on.

[0123] The minimum frequency domain resource metric value Z can be determined in any of the following ways: Z = Z1 x max(N RB1 x 2 μ1 , N RB2 x 2 μ2 ) (4) Z = Z1 x min(N RB1 x 2 μ1 , N RB2 x 2 μ2 ) (5)

[0124] N RB1 represents the maximum number of RBs that can be configured on the first carrier, and N RB2 represents the maximum number of RBs that can be configured on the second carrier. max() represents a maximum value function, and min() represents a minimum value function. Z1 represents a scaling factor, which can be a positive number greater than 1 or less than 1 or equal to 1.

[0125] 3. The minimum proportion of non-contiguous frequency domain resource scheduling to the frequency domain span of the multi-carrier that the terminal device can support, and the minimum frequency domain resource metric value.

[0126] That is, the constraint information includes two kinds of information in the aforementioned manner 1 and manner 2. The multi-carrier frequency domain resource configured by the network device for the UE needs to meet both conditions. For example, the frequency domain resource configured by the network device for the UE on the first carrier and the second carrier needs to meet both the proportion of non-contiguous frequency domain resource scheduling to the frequency domain span of the multi-carrier is greater than X%, and the sum of the frequency domain width resources of the first carrier and the second carrier is greater than Y.

[0127] The above embodiments describe the constraint relationship between the frequency domain resource on the carrier and the constraint information when the network device configures the frequency domain resource of the multi-carrier for the UE in the case of two carriers of the multi-carrier. In the case of three or more carriers of the multi-carrier, the constraint relationship is similar. Here, it is not repeated.

[0128] In the embodiments of the present application, the constraint condition is set as a minimum proportion of non-continuous frequency domain resource scheduling in the frequency domain span of the multi-carrier or a minimum frequency domain width resource. That is, the minimum frequency domain resource of the multi-carrier is set. In this way, firstly, the resource of the joint scheduling frequency domain is limited instead of isolated limitation, which guarantees the overall performance of joint scheduling. Secondly, by limiting the minimum frequency domain resource of the multi-carrier scheduling, the problems of low scheduling efficiency and radio frequency performance deterioration caused by the network device configuring too few RB frequency domain resources for the UE can be effectively avoided.

[0129] 102、The network device sends first configuration information to the terminal device according to the first information, and the first configuration information indicates the multi-carrier frequency domain resource configured for the terminal device, and the multi-carrier frequency domain resource satisfies the constraint information of the multi-carrier frequency domain resource that the terminal device can support, and the multi-carrier includes a first carrier and a second carrier. Correspondingly, the terminal device receives the first configuration information.

[0130] After the network device obtains the constraint information of the multi-carrier frequency domain resource that the UE supports according to the first information, the network device sends the first configuration information to the UE according to the constraint information, and configures the multi-carrier frequency domain resource for the UE, that is, configures the frequency domain resource on each carrier for the UE. The constraint relationship between the frequency domain resource on each carrier and the constraint information is shown in the foregoing formula (1) to formula (3), and will not be described here.

[0131] Optionally, the first configuration information is carried in downlink control information (DCI).

[0132] Optionally, the first configuration information is carried in a first field of DCI.

[0133] Optionally, the first field indicates the multi-carrier frequency domain resource configured for the terminal device through a bit map or a resource indication value (RIV). Wherein, R18 defines DCI format 0_3, and the frequency domain resources (or RB resources) of the first carrier and the second carrier can be respectively indicated through two fields in DCI format 0_3.

[0134] R15 defines DCI format 0_0 and DCI format 0_1. The first configuration information is carried in DCI of format 0_0 and format 0_1, which means that DCI format 0_0 and DCI format 0_1 respectively include a field for indicating the frequency domain resources of the first carrier and the second carrier. In order to realize joint scheduling of the two DCIs on the aggregated carrier, the time domain resources of DCI format 0_0 and DCI format 0_1 are the same.

[0135] Alternatively, the first configuration information can also be carried in two DCI format 0_0 respectively, or two DCI format 0_1 respectively. For example, in the first configuration information, the frequency domain resources of the first carrier are carried in the first DCI format 0_0, and the frequency domain resources of the second carrier are carried in the second DCI format 0_0.

[0136] Referring to FIG. 3C, FIG. 3C is a schematic diagram of sending the first configuration information to the UE through DCI according to an embodiment of the present application. As shown in (a) of FIG. 3C, the first configuration information (RB resources configured in the first carrier and the second carrier) is carried in a field in the DCI. As shown in (b) of FIG. 3C, the RB resources of the first carrier and the RB resources of the second carrier are respectively indicated by two fields (field 1 and field 2) in the DCI format 0_3. As shown in (c) of FIG. 3C, the RB resources of the first carrier and the RB resources of the second carrier are respectively indicated by a field (field 3) in the DCI format 0_0 and a field (field 4) in the DCI format 0_1.

[0137] It can be seen that, in the embodiments of the present application, the first configuration information is sent in a newly added field of the DCI, which can guarantee the sending efficiency of the first configuration information. The first configuration information is sent in two fields in an existing format of the DCI, which can reduce the modification of the format of the DCI, reduce the complexity of sending the first configuration information, and reduce the number of signaling interactions. The first configuration information is respectively sent in two existing formats of the DCI, which can further reduce the modification of the format of the DCI and reduce the complexity of sending the first configuration information.

[0138] In the embodiments of the present application, the network device obtains the constraint information of the multi-carrier frequency domain resources that the terminal device can support, and sends the first configuration information to the terminal device according to the constraint information, so as to complete the configuration of the multi-carrier frequency domain resources of the terminal device. In this way, the problems such as low scheduling efficiency caused by configuring only a small amount of frequency domain resources for the multi-carrier, and reduced signal quality caused by the terminal device to meet the radio frequency index can be avoided. The technical effects of improving the frequency domain resource scheduling efficiency and guaranteeing the signal transmission quality of the terminal device are achieved.

[0139] After receiving the first configuration information sent by the network device, the terminal device can send uplink signals to the network device based on the frequency domain resources of the multi-carrier configured in the first configuration information, including sending uplink signals on the first carrier according to the frequency domain resources of the first carrier, and sending uplink signals on the second carrier according to the frequency domain resources of the second carrier.

[0140] The above embodiments describe a scheme in which the network device schedules a proper number of multicarrier frequency domain resources for the terminal device based on the constraint information. In other cases, if the network device allows the carrier leakage of the terminal device to fall within the interval of the two uplink carriers, the network device can also schedule more accurate multicarrier frequency domain resources according to the center position of the carrier leakage reported by the terminal device.

[0141] As described in the prior art, the UL intra-band contiguous CA and the UL intra-band non-contiguous CA can be combined with the single PA architecture and the dual PA architecture respectively. Moreover, the radio frequency index based on the composite SEM of the UL intra-band non-contiguous CA is standardized for both radio frequency architectures. Referring to FIG. 4A, which is a schematic diagram of the composite SEM radio frequency index of the UL intra-band non-contiguous CA according to an embodiment of the present application, as shown in FIG. 4A, the frequency domain position far from the carrier is a spurious region, the frequency domain position close to the single carrier is a △FOOB1 / △FOOB2 region, that is, the region where the SEM is located. The frequency domain position range of the carrier is a non-SEM region. The overlapping range of the two carriers is a shared region using a relaxed limit. That is, the farther the frequency domain position is from the carrier, the more stringent the radio frequency index needs to meet.

[0142] Although both radio frequency architectures have been standardized, the UL intra-band non-contiguous CA / DC is not widely adopted for the single PA architecture in the actual implementation of the terminal device. The reason is that the current radio frequency protocol standard does not optimize the support of the UL intra-band non-contiguous CA / DC for the single PA architecture, making it difficult to support the UL intra-band non-contiguous CA / DC using the single PA architecture in the actual implementation.

[0143] Based on this, another resource scheduling method is provided in the embodiments of the present application to optimize the support of the UL intra-band non-contiguous CA (or DC) for the single PA architecture. Referring to FIG. 4B, which is a flowchart of the method, as shown in (a) of FIG. 4B, the method includes the following steps:

[0144] 201. The terminal device acquires third information, which indicates that the carrier center position of the terminal device is allowed to be located in the interval between the first carrier and the second carrier in the multicarriers.

[0145] Optionally, the terminal device acquires the third information according to preset information. The preset information includes a protocol agreement, or a default setting, etc.

[0146] Optionally, the terminal device receives the third information from the network device. Correspondingly, step 201 can be replaced by:

[0147] Step 201a, the network device sends third information, and correspondingly, the terminal device receives the third information (as shown in (b) of FIG. 4B).

[0148] Exemplarily, the network device indicates the third information to the UE through signaling.

[0149] Referring to FIG. 4C, FIG. 4C is a schematic diagram of the network device sending the third information to the UE through signaling according to an embodiment of the present application. As shown in FIG. 4C, the third information is carried in cell group configuration signaling (CellGroupConfig) sent by the network device.

[0150] The third information can also be carried in other signaling, which is not limited in the embodiments of the present application.

[0151] 202, the terminal device sends second information, the second information indicating a carrier center position set by the terminal device when the terminal device transmits multiple carriers through one (single) power amplifier (PA), the carrier center position being determined according to a center frequency domain position of an interval between a first carrier and a second carrier in the multiple carriers.

[0152] The UE transmits discontinuous multiple carriers through one PA, that is, the UE supports UL in-band discontinuous CA through single PA architecture. The multiple carriers include the first carrier and the second carrier. The first carrier and the second carrier are in-band discontinuous carriers, and an interval is contained between the two carriers.

[0153] When the network device allows carrier leakage of the UE to fall within the interval of the two uplink carriers, the UE can send the second information to the network device to indicate the center position of the carrier leakage, or the carrier center position, or the direct current position. So that the network device configures the frequency domain resource of the multiple carriers of the UE based on the carrier center position.

[0154] The UE reports the carrier center position set by the UE to the network device, and the carrier center position is determined according to the center frequency domain position of the interval between the first carrier and the second carrier in the multiple carriers, that is, the carrier center position is located near the center position of the interval of the two carriers, or expressed as carrier center position = center position of the interval of the two carriers ± N, N being a frequency fine tuning value equal to or greater than 0.

[0155] Referring to FIG. 4D, FIG. 4D is a schematic diagram of frequency domain resource scheduling of multiple carriers according to an embodiment of the present application, as shown in FIG. 4D, which includes discontinuous first carrier CC1 and second carrier CC2. Wherein CC1 corresponds to first bandwidth BW1, and CC2 corresponds to second bandwidth BW2. The center position of the interval between CC1 and CC2 is f c When the network device allows the carrier center position of the UE to fall within the interval of the two carriers, the UE can report the carrier center position fc1 f c is located in the interval [f

[0156] wherein f H1 represents a channel edge high boundary corresponding to CC1, f L2 represents a channel edge low boundary corresponding to CC2, CC1 is a carrier with the smallest center frequency, and CC2 is a carrier with the largest center frequency.

[0157] N is used for fine tuning, so that the reported carrier center position meets the granularity of the capability report.

[0158] Optionally, the value of N is less than min(f c -f H1 , f L2 -f c ). To ensure that f c1 is located in the interval between the two carriers.

[0159] Optionally, the value of N is less than or equal to GB1 and less than or equal to GB2. GB1 represents the frequency difference between f H1 of BW1 and f crb1 of W E1 , and f E1 represents the frequency of the end RB allocated on CC1. GB2 represents the frequency difference between f L2 of BW2 and f crb2 of W S2 , and f S2 represents the frequency of the start RB allocated on CC2.

[0160] Exemplarily, the UE reports f c1 , wherein when the value of N is less than or equal to GB1, the image leakage (expressed as the image leakage of CC1 in the figure) of the frequency domain width resource W crb1 configured on CC1 can not fall into the interval between the two carriers. When the value of N is less than or equal to GB2, the image leakage (expressed as the image leakage of CC2 in the figure) of the frequency domain width resource W crb2 configured on CC2 can not fall into the interval between the two carriers. The image leakage refers to the image leakage signal generated with respect to the symmetric mirror position of the allocated frequency domain resource, with the carrier center f c1 as the center. The general cause is the imbalance between the in-phase component and the quadrature component of the local oscillator signal.

[0161] Optionally, the value of N can be reported by the terminal device, or determined by the network device, or agreed by both parties, etc.

[0162] It can be seen that in the embodiment of the present application, when the carrier leakage of the terminal device is allowed to be located in the interval of the multiple carriers, the terminal device reports the carrier center position set by itself, and the carrier center position is determined according to the center frequency domain position of the interval between the first carrier and the second carrier in the multiple carriers. The carrier leakage of the terminal device is located in the interval of the two carriers, which helps the terminal device to more easily meet the radio frequency index requirements in the interval without large power backoff.

[0163] Optionally, after receiving the second information, the network device can configure the frequency domain resource of the multiple carriers for the terminal device according to the second information. Therefore, the method can further include the following steps:

[0164] 203、The network device sends second configuration information, and the second configuration information includes the frequency domain resource of the multiple carriers configured for the terminal device, and the frequency domain resource of the multiple carriers is configured based on the carrier center position set by the terminal device. Correspondingly, the terminal device receives the second configuration information.

[0165] After receiving the second information, the network device sends the second configuration information to configure the frequency domain resource of the multiple carriers for the UE, and the frequency domain resource of the multiple carriers, that is, the RB resource configured on the first carrier and the second carrier, is configured based on the carrier center position indicated by the UE.

[0166] Exemplarily, the network device configures the frequency domain resource of the two carriers for the UE according to the foregoing formula (7). The configured frequency domain resource meets the value range requirement of N.

[0167] Further, the frequency domain resource configured by the network device can also ensure that the mirror leakage of the large bandwidth carrier does not fall into the extrapolated adjacent channel of the small bandwidth carrier. For details, refer to the foregoing FIG. 4D. The extrapolated adjacent channel of CC1 is adjacent to BW1, and the extrapolated adjacent channel of CC2 is adjacent to BW2. Assuming that BW1> BW2, CC1 is a large bandwidth carrier, and assuming that BW1< BW2, CC2 is a large bandwidth carrier. Therefore, the frequency domain resource configured by the network device can meet the following formula: max[(f E2 -f L2 ),(f H1 -f S1 )]≤min(BW1,BW2) (8)

[0168] The meanings of each symbol in formula (8) are the same as described above, and will not be repeated here.

[0169] It can be seen that in the embodiment of the present application, when the network device configures the frequency domain resource of the multiple carriers for the terminal device, it ensures that the mirror leakage of the large bandwidth carrier does not fall into the extrapolated adjacent channel of the small bandwidth carrier, which can help the terminal device to more easily meet the radio frequency index requirements of the extrapolated adjacent channel without large power backoff.

[0170] The above embodiments describe the case where the network device allows the carrier leakage of the terminal device to be located within the interval between two carriers. In other cases, the network device allows the carrier leakage of the terminal device to be located within the carrier with a larger frequency band bandwidth of the two carriers, or within the interval between the two carriers.

[0171] Referring to FIG. 5A, a flowchart of another frequency domain resource scheduling method provided by the embodiments of the present application is shown in (a) of FIG. 5A. The method includes the following steps:

[0172] 301. The terminal device acquires third information, which indicates that the carrier center position of the terminal device is allowed to be located within the interval between the first carrier and the second carrier of the multiple carriers.

[0173] Optionally, the terminal device acquires the third information according to preset information. The preset information includes protocol agreement, or default setting, etc.

[0174] Optionally, the terminal device receives the third information from the network device. Correspondingly, step 301 can be replaced by:

[0175] Step 301a, the network device sends the third information, and correspondingly, the terminal device receives the third information (as shown in (b) of FIG. 5A).

[0176] Exemplarily, the network device indicates the third information to the UE through signaling. For specific examples, refer to the related description of the foregoing step 201a, which is not repeated here.

[0177] 302. The terminal device sends second information, which indicates the carrier center position set by the terminal device when transmitting the multiple carriers through one (single) power amplifier PA. The carrier center position is determined according to the center frequency domain position of the sum of the frequency band width of the first carrier, the frequency band width of the second carrier and the interval between the first carrier and the second carrier.

[0178] The UE reports the carrier center position to the network device, and the carrier center position is determined according to the center frequency domain position of the sum of the frequency band width of the first carrier, the frequency band width of the second carrier and the interval between the first carrier and the second carrier, that is, the carrier center position is located near the center position of the whole of the two carriers and the interval between the two carriers, or expressed as the carrier center position = (center position of BW1+interval+BW2) ± N, N is a frequency fine tuning value equal to or greater than 0.

[0179] Specifically, refer to FIG. 5B, which is a schematic diagram of frequency domain resource scheduling of a plurality of carriers provided by an embodiment of the present application. As shown in FIG. 5B, it includes non-continuous first carrier CCl and second carrier CC2. CCl is a carrier with the smallest center frequency, and CC2 is a carrier with the largest center frequency. CCl corresponds to BW1, and CC2 corresponds to BW2. The center positions of CCl, CC2, and the interval between CCl and CC2 are f c’ , f H2 represents the high boundary of the channel edge corresponding to CC2. f L1 represents the low boundary of the channel edge corresponding to CCl. When the network device allows the center position of the carrier of the UE to be located within the interval of the two carriers or within the carrier with the larger bandwidth of the two carriers, the UE can report the center position f c2 of the carrier through the second message, which is located near f c’ , that is,

[0180] The meanings of the various symbols in formula (9) are the same as described above, and will not be described again here.

[0181] N is used for fine adjustment, so that the reported center position of the carrier meets the granularity of the capability report.

[0182] Optionally, the value of N is less than min(f c’ -f L1 , f H2 -f c’ ), so as to ensure that f c2 does not fall into the carrier with the smaller bandwidth.

[0183] Optionally, the value of N is less than or equal to GB3 and less than or equal to GB4. GB3 represents the frequency difference between f S1 of BW1 and f crb1 of W L1 , and f S1 represents the frequency of the start RB allocated on CCl. GB4 represents the frequency difference between f H2 of BW2 and f crb2 of W E2 , and f E2 represents the frequency of the end RB allocated on CC2.

[0184] Exemplarily, the UE reports f c2 , wherein when the value of N is less than or equal to GB3, the mirror leakage of the frequency domain width resource W crb1 configured on CCl can be ensured to fall into the extrapolated adjacent channel of CC2. When the value of N is less than or equal to GB4, the mirror leakage of the frequency domain width resource W crb2 configured on CC2 can be ensured not to fall into the extrapolated adjacent channel of CCl.

[0185] Optionally, the value of N can be reported by the terminal device, or determined by the network device, or agreed by both parties, etc.

[0186] It can be seen that in the embodiments of the present application, when the carrier leakage of the terminal device is allowed to be located within the interval between the multiple carriers, the terminal device reports the carrier center position set by itself, which is determined according to the center frequency domain position of the sum of the frequency bandwidth of the first carrier, the frequency bandwidth of the second carrier and the interval between the first carrier and the second carrier in the multiple carriers. The network device configures the multiple carrier frequency domain resources for the terminal device according to the carrier center position, which can make the carrier leakage of the terminal device located within the interval between the two carriers or within the carrier with larger bandwidth, and the mirror leakage of the carrier will not be located within the extrapolated adjacent channel of the two carriers, which helps the terminal device to more easily meet the radio frequency index requirements of the extrapolated adjacent channel without large power backoff.

[0187] Optionally, after receiving the second information, the network device can configure the frequency domain resources of the multiple carriers for the terminal device according to the second information. Therefore, the method can further include the following steps:

[0188] 303. The network device sends second configuration information, wherein the second configuration information includes the multiple carrier frequency domain resources configured for the terminal device, and the multiple carrier frequency domain resources are configured based on the carrier center position set by the terminal device. Correspondingly, the terminal device receives the second configuration information.

[0189] After receiving the second information, the network device sends the second configuration information to configure the multiple carrier frequency domain resources for the UE, and the multiple carrier frequency domain resources, i.e., the RB resources configured on the first carrier and the second carrier, are configured based on the carrier center position indicated by the UE.

[0190] Exemplarily, the network device configures the frequency domain resources of the two carriers for the UE according to the foregoing formula (9). The configured frequency domain resources meet the value range requirement of N.

[0191] Further, the frequency domain resources configured by the network device can also ensure that the mirror leakage of the large bandwidth carrier does not fall within the interval of the two carriers (assuming that there is no setting of the N value). Therefore, the frequency domain resources configured by the network device can meet the following formula: max[(f H2 -f S2 ), (f E1 -f L1 )]≤min(BW1,BW2) (10)

[0192] The meanings of each symbol in the formula are the same as described above, and will not be described here.

[0193] It can be seen that, in the embodiment of the present application, when the carrier leakage of the terminal device is allowed to be located in the interval between the multiple carriers, the terminal device reports the carrier center position set by itself, and the carrier center position is determined according to the center frequency domain position of the sum of the frequency bandwidth of the first carrier, the frequency bandwidth of the second carrier and the interval between the first carrier and the second carrier in the multiple carriers. The network device configures the multiple carrier frequency domain resources for the terminal device according to the carrier center position, so that the carrier leakage of the terminal device is located in the interval between the two carriers or in the carrier with a larger bandwidth, and the mirror leakage of the carrier is not located in the extrapolated adjacent channel of the two carriers and the interval between the two carriers, which helps the terminal device to more easily meet the radio frequency index requirements in the interval between the two carriers and in the extrapolated adjacent channel without large power backoff.

[0194] In the above FIGS. 4A-4D and FIGS. 5A-5B, the method for the network device to send the second configuration information can be the same as the method described in the foregoing FIGS. 3A-3C, that is, sent through DCI, or DCI format 0_3, or DCI format 0_0 and / or DCI format 0_1, which will not be described here again.

[0195] The embodiments of FIGS. 4A-4D or FIGS. 5A-5B can exist independently of the embodiments of the foregoing FIGS. 3A-3C, or can be combined. For example, the network device can configure the frequency domain resources of the multiple carriers for the terminal device based on the constraint information of the multiple carrier frequency domain resources supported by the terminal device and the carrier center position reported by the terminal device. To comprehensively implement joint scheduling of higher quality multiple carrier resources. This will not be described here again.

[0196] Please refer to FIG. 6, which is a structural schematic diagram of a communication apparatus provided in an embodiment of the present application. The communication apparatus can be used to execute any of the methods in the foregoing embodiments.

[0197] As shown in FIG. 6, the communication apparatus includes a processing module 1501 and a transceiver module 1502. The processing module 1501 can be one or more processors, and the transceiver module 1502 can be a transceiver or a communication interface. The communication apparatus can be used to implement the functions of the devices such as the first device and the second device involved in any of the method embodiments. These devices can be hardware devices, software functions running on special hardware, or virtualized functions instantiated on a platform (for example, a cloud platform). Optionally, the communication apparatus can further include a storage module 1503 for storing the program code and data of the communication apparatus.

[0198] In the first example, the communication apparatus can be a terminal device or a chip in a terminal device in FIG. 3A-FIG. 3C, and perform the steps performed by the terminal device in the above method embodiments. The transceiver module 1502 is configured to support communication with a network device or the like. The processing module 1501 can be configured to support the actions performed by the terminal device in the above method embodiments, except for sending and receiving.

[0199] Specifically, the transceiver module 1502 receives first configuration information, the first configuration information indicating a multi-carrier frequency domain resource configured for the terminal device, the multi-carrier frequency domain resource satisfying constraint information of a multi-carrier frequency domain resource that the terminal device can support, the multi-carrier including a first carrier and a second carrier; the processing module 1501 is configured to transmit signals on the first carrier and the second carrier in combination with the transceiver module 1502 according to the multi-carrier frequency domain resource.

[0200] In an implementation, the constraint information includes a minimum proportion of non-continuous frequency domain resource scheduling that the terminal device can support in a multi-carrier frequency domain span.

[0201] In an implementation, the multi-carrier frequency domain resource and the minimum proportion of non-continuous frequency domain resource scheduling that the terminal device can support in the multi-carrier frequency domain span satisfy the following formula:

[0202] Wherein W crb1 is a frequency domain width resource configured for the terminal device on the first carrier, W crb2 is a frequency domain width resource configured for the terminal device on the second carrier, f E2 represents a frequency corresponding to the last resource block RB allocated by the second carrier, f S1 represents a frequency of the start RB allocated by the first carrier; X% represents the minimum proportion of non-continuous frequency domain resource scheduling that the terminal device can support in the multi-carrier frequency domain span.

[0203] In an implementation, the constraint information includes a minimum frequency domain resource metric value that the terminal device can support.

[0204] In an implementation, the multi-carrier frequency domain resource and the minimum frequency domain resource metric value that the terminal device can support satisfy the following formula: W crb1 +W crb2 ≥Y

[0205] W crb1 is a frequency domain width resource configured for the terminal device on the first carrier, W crb2 is a frequency domain width resource configured for the terminal device on the second carrier, Y represents the minimum frequency domain resource metric value that the terminal device can support.

[0206] In a possible implementation, the constraint information includes: a minimum number of RBs that the terminal device can support.

[0207] In a possible implementation, the minimum number of RBs that the terminal device can support satisfies the following condition: L crb1 × 2 μ1 + L crb2 × 2 μ2 ≥ Z

[0208] L crb1 is the number of RBs configured to the terminal device on the first carrier, L crb2 is the number of RBs configured to the terminal device on the second carrier, μ1 represents a parameter corresponding to the subcarrier spacing on the first carrier, μ2 represents a parameter corresponding to the subcarrier spacing on the second carrier, and Z represents the minimum number of RBs that the terminal device can support.

[0209] In a possible implementation, Z satisfies: Z = Z1 × max(N RB1 × 2 μ1 , N RB2 × 2 μ2 ); or Z = Z1 × min(N RB1 × 2 μ1 , N RB2 × 2 μ2 ); or

[0210] wherein Z1 represents a scaling factor, N RB1 represents the maximum number of RBs that can be configured on the first carrier, and N RB2 represents the maximum number of RBs that can be configured on the second carrier.

[0211] In a possible implementation, before receiving the first configuration information, the transceiver 1502 is further configured to: send first information, the first information indicating constraint information of multi-carrier frequency domain resources that the terminal device can support.

[0212] In a possible implementation, the first configuration information is carried in downlink control information (DCI).

[0213] In a possible implementation, the first configuration information is carried in a first field of the DCI, and the first field indicates the multi-carrier frequency domain resources configured for the terminal device by using a bit map or a resource indication value (RIV).

[0214] In a possible implementation, the first configuration information is carried in DCI of format 0_3; or the first configuration information is carried in DCI of format 0_0 and / or format 0_1.

[0215] In the second example, the communication apparatus can be a network device or a chip in the network device in FIG. 3A-3C, and perform the steps performed by the network device in the method embodiments described above. The transceiver module 1502 is configured to support communication with the terminal device. The processing module 1501 is configured to support the actions in the method embodiments described above, except for the sending and receiving.

[0216] Specifically, the processing module 1501 or the transceiver module 1502 is configured to obtain first information, the first information including constraint information of multi-carrier frequency domain resources that the terminal device can support; and the transceiver module 1502 is configured to send first configuration information, the first configuration information including multi-carrier frequency domain resources configured for the terminal device, the multi-carrier frequency domain resources satisfying the constraint information of the multi-carrier frequency domain resources that the terminal device can support.

[0217] In an implementation, the obtaining of the first information includes receiving the first information from the terminal device, or obtaining the first information according to preset information.

[0218] In an implementation, the multi-carrier includes a first carrier and a second carrier, and the transceiver module 1502 is further configured to receive an uplink signal from the terminal device, the uplink signal being sent on the first carrier and the second carrier according to the multi-carrier frequency domain resources.

[0219] In the third example, the communication apparatus can be a terminal device or a chip in the terminal device in FIG. 4A-5B, and perform the steps performed by the terminal device in the method embodiments described above. The transceiver module 1502 is configured to support communication with a network device, etc. The processing module 1501 is configured to support the actions in the method embodiments described above, except for the sending and receiving.

[0220] Specifically, the processing module 1501 is configured to obtain third information in combination with the transceiver module 1502, the third information indicating that a carrier center position of the terminal device is allowed to be located in an interval between a first carrier and a second carrier in the multi-carrier; and the transceiver module 1502 is configured to send second information to the network device, the second information indicating a carrier center position set by the terminal device when sending the multi-carrier by using one power amplifier (PA), the carrier center position being determined according to a center frequency domain position of the interval between the first carrier and the second carrier in the multi-carrier, or the carrier center position being determined according to a center frequency domain position of a sum of a frequency bandwidth of the first carrier, a frequency bandwidth of the second carrier, and the interval between the first carrier and the second carrier.

[0221] In an implementation, the carrier center position is determined by the processing module 1501 according to the center frequency domain position of the interval between the first carrier and the second carrier.

[0222] In an implementation, the multi-carrier frequency domain resource and the carrier center position satisfy:

[0223] wherein f c1 represents the carrier center position, f H1 represents a high boundary of a channel edge corresponding to the first carrier, f L2 represents a low boundary of a channel edge corresponding to the second carrier, the first carrier is a carrier with the smallest center frequency, the second carrier is a carrier with the largest center frequency, and N is a frequency fine adjustment value equal to or greater than 0.

[0224] In an implementation, the multi-carrier frequency domain resource satisfies: max[(f E2 -f L2 ), (f H1 -f S1 )]≤min(BW1, BW2)

[0225] wherein f E2 represents a frequency of an end RB allocated by the second carrier, f S1 represents a frequency of a start RB available for transmission by the first carrier, f L2 represents a low boundary of a channel edge of the second carrier, f H1 represents a high boundary of a channel edge of the first carrier, BW1 represents a bandwidth of the first carrier, and BW2 represents a bandwidth of the second carrier.

[0226] In an implementation, the carrier center position is determined by the processing module 1501 according to a center frequency domain position of a sum of a frequency bandwidth of the first carrier, a frequency bandwidth of the second carrier, and a spacing between the first carrier and the second carrier.

[0227] In an implementation, the multi-carrier frequency domain resource and the carrier center position satisfy:

[0228] wherein f c2 represents the reported carrier center position, f H2 represents a high boundary of a channel edge corresponding to the second carrier, f L1 represents a low boundary of a channel edge corresponding to the first carrier, the first carrier is a carrier with the smallest center frequency, the second carrier is a carrier with the largest center frequency, and N is a frequency fine adjustment value equal to or greater than 0.

[0229] In an implementation, the multi-carrier frequency domain resource further satisfies: max[(f H2 -f S2 ), (f E1 -f L1 )]≤min(BW1, BW2)

[0230] wherein f E1 denotes the frequency of the last RB allocated by the first carrier, f S2 denotes the frequency of the first RB allocated by the second carrier, f H2 denotes the second carrier channel edge high boundary, f L1 denotes the first carrier channel edge low boundary, BW1 denotes the bandwidth of the first carrier, and BW2 denotes the bandwidth of the second carrier.

[0231] In an implementation, the third information is acquired according to preset information or is received from the network device.

[0232] In an implementation, the third information is carried in cell group configuration signaling.

[0233] In a fourth example, the communication apparatus can be the network device or a chip in the network device in FIG. 4A-FIG. 5B and perform the steps performed by the network device in the above method embodiments. The transceiver module 1502 is configured to support communication with the terminal device. The processing module 1501 is configured to support the actions of the above method embodiments performed by the network device, except for sending and receiving.

[0234] Specifically, the transceiver module 1502 is configured to send, to the terminal device, third information indicating that a carrier center position of the terminal device is allowed to be located in an interval between a first carrier and a second carrier in a plurality of carriers; and the transceiver module 1502 is further configured to receive, from the terminal device, second information indicating a carrier center position set by the terminal device when transmitting the plurality of carriers by using one power amplifier PA, the carrier center position being determined according to a center frequency domain position of the interval between the first carrier and the second carrier in the plurality of carriers, or the carrier center position being determined according to a center frequency domain position of a sum of a frequency bandwidth of the first carrier, a frequency bandwidth of the second carrier, and the interval between the first carrier and the second carrier.

[0235] Or specifically, the transceiver module 1502 is configured to receive, from the terminal device, second information indicating a carrier center position set by the terminal device when transmitting the plurality of carriers by using one power amplifier PA, the carrier center position being determined according to a center frequency domain position of the interval between the first carrier and the second carrier in the plurality of carriers, or the carrier center position being determined according to a center frequency domain position of a sum of a frequency bandwidth of the first carrier, a frequency bandwidth of the second carrier, and the interval between the first carrier and the second carrier; and the transceiver module 1502 is further configured to send second configuration information, the second configuration information including a plurality of carrier frequency domain resources configured for the terminal device, the plurality of carrier frequency domain resources being configured based on the carrier center position set by the terminal device.

[0236] Please refer to Figure 7, which is a simplified structural diagram of a network device provided by an embodiment of the present application, which can be used as an implementation manner of the network device of the present application.

[0237] The network device comprises a radio frequency signal transceiving and conversion part and a baseband part 42. The radio frequency signal transceiving and conversion part comprises a receiving module 41 part and a sending module 43 part (which can also be collectively referred to as a transceiving module). The radio frequency signal transceiving and conversion part is mainly used for the transceiving of radio frequency signals and the conversion between radio frequency signals and baseband signals; the baseband part 42 is mainly used for baseband processing and controlling the network device, etc. The receiving module 41 can also be referred to as a receiver, a receiver, a receiving circuit, etc. The sending module 43 can also be referred to as a transmitter, a transmitter, a transmitter, a transmitting circuit, etc. The baseband part 42 is usually the control center of the network device and can also be referred to as a processing module, which is used to execute the steps performed by the network device in any of the above methods. For details, please refer to the description of the related part above. The sending module 43 can comprise an antenna and a radio frequency circuit. 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 the transceiving of radio frequency signals in the form of electromagnetic waves.

[0238] The baseband part 42 can comprise one or more single boards, each of which can comprise one or more processors and one or more memories. The processor is used to read and execute the program in the memory to realize the baseband processing function and control the network device. If there are multiple single boards, the single boards can be interconnected to increase the processing capacity. As an optional implementation manner, multiple single boards can also share one or more processors, or multiple single boards can share one or more memories, or multiple single boards can share one or more processors at the same time.

[0239] Please refer to Figure 8, which is a structural diagram of a RAN chip provided by an embodiment of the present application, which can be used as another implementation manner of the network device of the present application.

[0240] The RAN chip is divided into CU, DU and RU. The CU is a platform for executing upper layer L2 (data link layer) and L3 (network layer) functions. The Midhaul and Backhaul interfaces are used to carry the traffic between the CU and the DU and between the CU and the core network. The DU executes L1 and part of L2 functions, and the RU executes L1 (physical layer) calculation and RF digital part functions; the Fronthaul and Backhaul interfaces are used to carry the traffic between the RU and the DU and between the CU and the DU. The integrated DU comprises the above-mentioned DU and RU functions.

[0241] The CU / DU hardware includes a chassis platform, a motherboard, peripherals, and cooling equipment. The motherboard contains processing units, memory, internal I / O interfaces, and external connection ports. Its hardware accelerator design has interfaces, and the hardware functional components include: storage of software, hardware, and system debugging interfaces, a single-board management controller.

[0242] The DU system is usually implemented using a multi-core processor and one or more hardware accelerators. Part of the DU protocol stack can be implemented in software running on the multi-core processor, and the computationally intensive L1 and L2 functions can be offloaded to FPGA / GPU-based hardware accelerators; or all L1 functions are offloaded to FPGA / GPU-based hardware accelerators, while other protocol stack contents are implemented in software running on the processor; or all the protocol stack is implemented in software running on the processor. The hardware accelerator supports interconnection with an x86 or non-x86 processor, and the accelerator has a multi-channel PCIe interface pointing to the CPU and is externally connected through GbE connection.

[0243] The RU includes three parts: the OPU (O-RAN Processing Unit) receives eCPRI frames from the O-RAN fronthaul and performs the fronthaul interface, the lowest layer L1 (encoding, scrambling, modulation, layer mapping, precoding), synchronization, beamforming, and resource unit mapping. The OPU can be implemented as a CPU, FPGA, or ASIC. The DPU (Digital Processing Unit of the O-RU) performs synchronization, DDC (digital down conversion in UL), DUC (digital up conversion in DL), CFR, and DPD to improve power amplifier efficiency by reducing the PAPR / ACLR of the RF front end; the DPU can be implemented as an FPGA or ASIC. The RF processing unit of the O-RU includes a transceiver module, an up / down converter, a power amplifier (PA), a low-noise amplifier (LNA), a Tx / Rx filter. All conversions between the analog and digital domains (DAC and ADC) (for example, (RF sampling, using RF, IF, and LO mixing for frequency conversion in upconversion and downconversion)) are performed within the transceiver module. Note that the physical and logical partitions within the RF processing unit do not require specific boundaries.

[0244] Please refer to FIG. 9, which is a simplified structure diagram of a UE provided by an embodiment of the present application, serving as an implementation manner of a terminal device in the present application.

[0245] For the convenience of understanding and illustration, in FIG. 9, the UE takes a mobile phone as an example. As shown in FIG. 9, the UE includes at least one processor, and can further include radio frequency circuitry, an antenna, and an input / output device. The processor can be used to process communication protocols and communication data, and can also be used to control the UE, execute software programs, process data of the software programs, and the like. The UE can further include a memory, which is mainly used to store software programs and data. The programs involved can be loaded into the memory when the communication device is manufactured, or can be loaded into the memory at a later time when needed. The radio frequency circuitry is mainly used for conversion between baseband signals and radio frequency signals, and processing of the radio frequency signals. The antenna is mainly used for receiving and transmitting radio frequency signals in the form of electromagnetic waves. The input / output device, such as a touch screen, a display screen, a keyboard, and the like, is mainly used to receive data input by a user and output data to the user. It should be noted that some types of UE can not have an input / output device.

[0246] When a signal needs to be sent, the processor performs baseband processing on the data to be sent, and outputs the baseband signal to the radio frequency circuitry. The radio frequency circuitry performs radio frequency processing on the baseband signal, and transmits the radio frequency signal in the form of electromagnetic waves through the antenna. When data is sent to the UE, the radio frequency circuitry receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data. For the convenience of illustration, only one memory and one processor are shown in FIG. 9. In actual UE products, there can be one or more processors and one or more memories. The memory can also be referred to as a storage medium or a storage device, etc. The memory can be independent of the processor, or can be integrated with the processor. The embodiments of the present application do not limit this.

[0247] In the embodiments of the present application, the antenna and the radio frequency circuitry with transceiving functions can be regarded as a receiving unit and a sending unit (which can also be collectively referred to as a transceiving unit) of the UE, and the processor with processing functions can be regarded as a processing unit of the UE. As shown in FIG. 9, the UE includes a receiving module 31, a processing module 32, and a sending module 33. The receiving module 31 can also be referred to as a receiver, a receiver, a receiving circuit, etc. The sending module 33 can also be referred to as a transmitter, a transmitter, a transmitter, a transmitting circuit, etc. The processing module 32 can also be referred to as a processor, a processing board, a processing device, etc.

[0248] It can be understood that the processor in the embodiments of the present application can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor.

[0249] Optionally, the memory can also store data. The processor and the memory can be separately arranged or integrated together. The memory can be a non-volatile memory such as a hard disk drive (HDD) or a solid-state drive (SSD), and can also be a volatile memory such as a random-access memory (RAM). The processor in the embodiments of the present application can also be a flash memory, a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM), a register, a hard disk, a mobile hard disk, a CD-ROM or any other form of storage medium well known in the art.

[0250] Optionally, the UE can include instructions (which can also be referred to as code or programs at times) that can be run on the processor.

[0251] Optionally, the UE can also include a transceiver and an antenna. The transceiver can be referred to as a transceiving unit, a transceiving module, a transceiver, a transceiving circuit, a transceiver, an input / output interface, etc., and is used to realize the transceiving function of the UE through the antenna.

[0252] Referring to FIG. 10, FIG. 10 is a schematic diagram of a chip structure in a UE according to an embodiment of the present application, which is an implementation manner of the terminal device in the present application.

[0253] The chip in the UE can also be referred to as baseband hardware, and the structure includes a processing system including one or more processors.

[0254] The baseband can be implemented in a processing system including one or more processors. Processors include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), GPUs, programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described herein. That is, the processor(s) of the baseband can be used to implement each of the processes described below and any other processes described herein.

[0255] The processing system can be implemented with a bus architecture, represented generally by the bus 1102. The bus 1102 can include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints. The bus 1102 communicatively couples various circuitry including one or more processors (generally represented by the processor 1104), memory, and computer-readable media (generally represented by the computer-readable medium 1106). The bus 1102 can also link various other circuitry, such as a timing source, peripherals, voltage regulators, and power management circuitry, which are well known in the art, and therefore, will not be further described. A bus interface provides an interface between the bus 1102 and a transceiver and between the bus 1102 and an interface.

[0256] The transceiver provides a communication interface or means for communicating with various other apparatus over the wireless transmission medium. The transceiver can be coupled to an antenna array, and the transceiver and antenna array can together function as a communication interface or means for communicating with a corresponding network type. At least one interface (e.g., network interface and / or user interface) provides a communication interface or means for communication over the internal bus or via an external transmission medium.

[0257] The processor is responsible for managing the bus and general processing, including the execution of software stored on the computer-readable medium. The software, when executed by the processor, causes the processing system to perform the various functions described infra for any particular apparatus.

[0258] The functions that the processor and memory and computer-readable medium can implement can be encoding, decoding, rate matching, de-rate matching, scrambling, descrambling, modulating, demodulating, layer mapping, FFT, IFFT, IDFT, precoding, RE mapping, channel equalization, de-RE mapping, digital BF, adding CP, de-CP, and so forth.

[0259] Embodiments of the present application provide a communication system, comprising the terminal device and the network device described above.

[0260] Embodiments of the present application provide a computer-readable storage medium, characterized in that the computer-readable storage medium stores computer instructions, when the computer instructions are executed, causing a computer to execute the method described in any of the above methods.

[0261] The embodiment of the present application provides a computer program product, which comprises computer program codes, and the computer program codes make the computer execute the method described in any of the above methods when the computer runs the computer program codes.

[0262] The embodiment of the present application provides a chip, which is coupled with a memory, and is used for reading and executing program instructions in the memory, so that the device where the chip is located implements the method described in any of the above methods.

[0263] In the above embodiments, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments. It should be noted that, for the above-mentioned method embodiments, in order to simply describe, they are all expressed as a combination of a series of actions, but those skilled in the art should know that the present application is not limited to the order of the actions described, because according to the present application, some steps can be performed in other order or simultaneously. Secondly, those skilled in the art should know that the embodiments described in the specification all belong to preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0264] In several embodiments provided in the present application, it should be understood that the disclosed device can be implemented by other means. For example, the device embodiments described above are only schematic, and the division of the above units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units or components shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical or other forms.

[0265] The units described as separate components above can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0266] The above description and the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that the technical solutions recorded in the foregoing embodiments can be modified, or some technical features can be replaced by equivalent; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

A resource scheduling method, characterized in that, The method comprises: receiving first configuration information, the first configuration information indicating a multicarrier frequency domain resource configured for the terminal device, the multicarrier frequency domain resource satisfying constraint information of a multicarrier frequency domain resource that the terminal device can support, the multicarrier including a first carrier and a second carrier; transmitting a signal on the first carrier and the second carrier according to the multicarrier frequency domain resource. The method of claim 1, wherein The constraint information comprises: a minimum proportion of non-continuous frequency domain resource scheduling in a multicarrier frequency domain span that the terminal device can support. The method according to claim 2, characterized in that The minimum ratio of the multi-carrier frequency domain resource and the non-continuous frequency domain resource scheduling supported by the terminal device occupies the minimum proportion of the multi-carrier frequency domain span, which satisfies the following formula: where W crb1 is the frequency-domain width resource configured for the terminal device on the first carrier, W crb2 is the frequency-domain width resource configured for the terminal device on the second carrier, f E2 denotes the frequency of the last resource block, RB, allocated by the second carrier, f S1 denotes the frequency of the first RB allocated by the first carrier; and X% denotes the minimum proportion of the multi-carrier frequency-domain span that the terminal device is capable of supporting for non-contiguous frequency-domain resource scheduling. The method according to any one of claims 1-3, characterized in that The constraint information comprises: a minimum frequency domain resource metric value that the terminal device can support. The method according to claim 4, characterized in that The multicarrier frequency domain resource and the minimum frequency domain resource metric value that the terminal device can support satisfy the following formula: W crb1 +W crb2 ≥Y W crb1 W is a frequency domain width resource on the first carrier configured to the terminal device crb2 Y is a frequency domain width resource on the second carrier configured to the terminal device, Y represents a minimum frequency domain resource measurement value that the terminal device can support. The method according to any one of claims 1 to 3, characterized in that The constraint information comprises: a minimum number of RBs that the terminal device can support. The method according to claim 6, characterized in that The multicarrier frequency domain resource and the minimum number of RBs that the terminal device can support satisfy the following condition: L crb1 x2 μ1 +L crb2 x2 μ2 ≥Z L crb1 L is the number of RBs configured to the terminal device on the first carrier crb2 L is the number of RBs configured to the terminal device on the second carrier, μ1 represents a parameter corresponding to the subcarrier spacing on the first carrier, μ2 represents a parameter corresponding to the subcarrier spacing on the second carrier, and Z represents the minimum number of RBs that the terminal device can support. The method of claim 7, wherein The Z satisfies: Z = Z1 x max(N RB1 ×2 μ1 ,N RB2 ×2 μ2 ); Or Z = Z1 x min(N RB1 x 2 μ1 , N RB2 x 2 μ2 ); or where Z1 represents a scaling factor, N RB1 represents the maximum number of RBs that can be configured on the first carrier, N RB2 represents the maximum number of RBs that can be configured on the second carrier. The method according to any one of claims 1 to 8, characterized in that Before the receiving first configuration information, the method further comprises: transmitting first information, the first information indicating constraint information of a multicarrier frequency domain resource that the terminal device can support. The method according to any one of claims 1 to 9, characterized in that The first configuration information is carried in a first field of DCI, and the first field indicates a multicarrier frequency domain resource configured for the terminal device by a bit map or a resource indication value (RIV). The method according to any one of claims 1 to 9, characterized in that The first configuration information is carried in DCI of format 0_3, or the first configuration information is carried in DCI of format 0_0 and / or format 0_1. A frequency domain resource scheduling method, characterized in that, The method comprises: obtaining first information, the first information including constraint information of a multicarrier frequency domain resource that the terminal device can support; transmitting first configuration information, the first configuration information including a multicarrier frequency domain resource configured for the terminal device, the multicarrier frequency domain resource satisfying the constraint information of the multicarrier frequency domain resource that the terminal device can support. The method of claim 12, wherein The obtaining first information comprises: receiving the first information from the terminal device; or obtaining the first information according to preset information. A resource scheduling method, characterized in that, The method comprises: obtaining third information, the third information indicating that a carrier center position of the terminal device is allowed to be located within an interval between a first carrier and a second carrier in the multicarrier; transmitting second information to a network device, the second information indicating a carrier center position set by the terminal device when transmitting the multicarrier through one power amplifier (PA), the carrier center position being determined according to a center frequency domain position of the interval between the first carrier and the second carrier in the multicarrier, or the carrier center position being determined according to a center frequency domain position of a sum of a frequency bandwidth of the first carrier, a frequency bandwidth of the second carrier, and the interval between the first carrier and the second carrier. The method of claim 14, wherein The method further comprises: receiving second configuration information from the network device, the second configuration information including a frequency domain resource of the multicarrier, the frequency domain resource of the multicarrier being configured based on the carrier center position set by the terminal device. The method according to claim 14 or 15, characterized in that The carrier center position is determined according to a center frequency domain position of a spacing between the first carrier and the second carrier, including that the carrier center position satisfies: wherein f c1 represents the carrier center position, f H1 represents the channel edge high boundary corresponding to the first carrier, f L2 represents the channel edge low boundary corresponding to the second carrier, the first carrier being the carrier with the smallest center frequency, the second carrier being the carrier with the largest center frequency, and N being a frequency fine tuning value equal to or greater than 0. The method according to claim 15 or 16, characterized in that The frequency domain resource of the multicarrier configured based on the carrier center position set by the terminal device comprises that the multicarrier frequency domain resource satisfies: max[(f E2 -f L2 ),(f H1 -f S1 )]≤min(BW1,BW2) wherein f E2 denotes the frequency of the last RB allocated by the second carrier, f S1 denotes the frequency of the first RB allocated by the first carrier, f L2 denotes the second carrier channel edge low boundary, f H1 denotes the first carrier channel edge high boundary, BW1 denotes the bandwidth of the first carrier, and BW2 denotes the bandwidth of the second carrier. The method according to claim 14 or 15, characterized in that The carrier center position is determined according to the center frequency domain position of the sum of the frequency band width of the first carrier, the frequency band width of the second carrier, and the interval between the first carrier and the second carrier, and includes that the carrier center position satisfies: wherein f c2 represents the reported carrier center position, f H2 represents a high boundary of a channel edge corresponding to the second carrier, f L1 represents a low boundary of a channel edge corresponding to the first carrier, the first carrier being the carrier with the smallest center frequency and the second carrier being the carrier with the largest center frequency; and N being a frequency fine tuning value equal to or larger than 0. The method according to claim 15 or 18, characterized in that The frequency domain resource of the multiple carriers is configured based on a carrier center position set by the terminal device, and the multiple carrier frequency domain resource satisfies: max[(f H2 -f S2 ),(f E1 -f L1 )]≤min(BW1,BW2) wherein f E1 denotes the frequency of the last RB allocated by the first carrier, f S2 denotes the frequency of the first RB allocated by the second carrier, f H2 denotes the second carrier channel edge high boundary, f L1 denotes the first carrier channel edge low boundary, BW1 denotes the bandwidth of the first carrier, and BW2 denotes the bandwidth of the second carrier. The method according to any one of claims 14-19, characterized in that The third information is obtained according to preset information; or The third information is received from the network device. The method comprises: A frequency domain resource scheduling method, characterized in that, The third information is sent to the terminal device, and the third information indicates that the carrier center position of the terminal device is allowed to be located in an interval between a first carrier and a second carrier in the multiple carriers; The second information is received from the terminal device, and the second information indicates a carrier center position set by the terminal device when the terminal device transmits the multiple carriers through one power amplifier (PA), the carrier center position is determined according to a center frequency domain position of the interval between the first carrier and the second carrier in the multiple carriers, or the carrier center position is determined according to a center frequency domain position of a sum of a frequency bandwidth of the first carrier, a frequency bandwidth of the second carrier and the interval between the first carrier and the second carrier. The method comprises: A frequency domain resource scheduling method, characterized in that, The second information is received from the terminal device, and the second information indicates a carrier center position set by the terminal device when the terminal device transmits the multiple carriers through one power amplifier (PA), the carrier center position is determined according to a center frequency domain position of the interval between the first carrier and the second carrier in the multiple carriers, or the carrier center position is determined according to a center frequency domain position of a sum of a frequency bandwidth of the first carrier, a frequency bandwidth of the second carrier and the interval between the first carrier and the second carrier; The second configuration information is sent, and the second configuration information comprises multiple carrier frequency domain resources configured for the terminal device, and the multiple carrier frequency domain resources are configured based on a carrier center position set by the terminal device. The method is used for implementing any one of claims 1 to 11, or the method is used for implementing any one of claims 14 to 20. A communication device, characterized by The device comprises a terminal device or a chip. The apparatus of claim 23, wherein The method is used for implementing any one of claims 12 to 13, or the method is used for implementing any one of claims 21 to 22. A communication device, characterized by The device comprises a network device or a chip. The apparatus of claim 25, wherein A communication device, characterized in that, The communication device comprises at least one processor coupled with a memory; The at least one processor is used to execute a computer program or instruction stored in the memory, so that the method in any one of claims 1 to 11 or 14 to 20 is implemented, or the method in any one of claims 12 to 13 or 21 to 22 is implemented. The computer readable storage medium stores a computer program, and when the computer program is executed, the method in any one of claims 1 to 11 or 14 to 20 is implemented, or the method in any one of claims 12 to 13 or 21 to 22 is implemented. A computer-readable storage medium, characterized by When the computer program is executed, the method in any one of claims 1 to 11 or 14 to 20 is implemented, or the method in any one of claims 12 to 13 or 21 to 22 is implemented. A computer program, characterized in that ​

Images