Method and communication device for resource scheduling

Abstract

This application provides a resource scheduling method and a communication device. The method includes: receiving a first message on a first downlink carrier of a first cell, the first message indicating scheduling information of a Physical Downlink Shared Channel (PDSCH), wherein the PDSCH corresponds to a first downlink carrier of the first cell and a second downlink carrier of a second cell; receiving a second message indicating scheduling information of a Physical Uplink Shared Channel (PUSCH) of a first uplink carrier of the second cell; and transmitting the PUSCH on the first uplink carrier of the second cell according to the second message. The resource scheduling method of this application can schedule data on multiple carriers using a single Downlink Control Information (DCI), effectively reducing control signaling overhead, achieving diversified scheduling needs and communication, and improving system effectiveness.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a method for resource scheduling and a communication device. Background Technology

[0002] In Long Term Evolution Advance (LTE-A) systems, carrier aggregation (CA) technology is introduced to support greater transmission bandwidth. Currently, in carrier aggregation scenarios, user equipment (UE) can use downlink control information (DCI) to schedule a carrier's physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH).

[0003] However, with the increasing demand for communication, frequent resource scheduling may lead to excessive control signaling overhead.

[0004] Therefore, in order to reduce the overhead of control signaling, how to schedule data on multiple carriers using a single downlink control information (DCI) to meet diverse scheduling needs is an urgent technical problem that needs to be solved. Summary of the Invention

[0005] This application provides a resource scheduling method and communication device that can effectively reduce the overhead of control signaling, realize diversified communication scheduling needs, and improve system effectiveness.

[0006] In a first aspect, a resource scheduling method is provided, comprising: receiving a first message on a first downlink carrier of a first cell, the first message indicating scheduling information of a physical downlink shared channel (PDSCH), the PDSCH corresponding to a first downlink carrier of the first cell and a second downlink carrier of a second cell; receiving a second message indicating scheduling information of a physical uplink shared channel (PUSCH) of a first uplink carrier of the second cell; and transmitting the PUSCH on the first uplink carrier of the second cell according to the second message.

[0007] According to the solution provided in this application, the terminal device can schedule the PDSCH of the first downlink carrier of the first cell and the PDSCH of the second downlink carrier of the second cell by receiving a first message on the first downlink carrier of the first cell. In this scenario, the terminal device can then schedule the PUSCH of the first uplink carrier of the second cell according to the received second message and send the PUSCH to the network device, which effectively reduces the overhead of control signaling, meets diversified scheduling needs, and realizes diversified communication and system effectiveness.

[0008] For example, the PDSCH includes a first PDSCH and a second PDSCH, wherein the first PDSCH corresponds to the first cell and the second PDSCH corresponds to the second cell.

[0009] For example, the PDSCH includes a third PDSCH, wherein the third PDSCH corresponds to the first cell and the second cell.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, receiving the second message includes: receiving the second message on a second downlink carrier of the second cell; or receiving the second message on a first downlink carrier of the first cell; or receiving the second message on a third downlink carrier of the third cell.

[0011] For example, if the local carrier supports PUSCH scheduling, the terminal device can also receive DCI on the second downlink carrier of the second cell to indicate the scheduling information corresponding to the PDSCH of the third downlink carrier of the second cell.

[0012] For example, the terminal equipment may also receive DCI on the second downlink carrier of the second cell to instruct the terminal equipment to schedule the PUSCH or PDSCH of the second cell across carriers; and / or to instruct the terminal equipment to jointly schedule the PDSCH of the second cell and the PDSCH of the third cell.

[0013] For example, if the current carrier does not support PUSCH scheduling, the terminal device can also receive DCI on the first downlink carrier of the first cell to instruct the terminal device to schedule PDSCH on the first downlink carrier of the first cell across downlink carriers.

[0014] For example, the terminal equipment may also receive DCI on the first downlink carrier of the first cell to instruct the terminal equipment to schedule the PUSCH or PDSCH of the third cell across carriers; and / or to instruct the terminal equipment to jointly schedule the PDSCH of the first cell and the PDSCH of the third cell downlink.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, first configuration information of a first cell is received, the first configuration information of the first cell being used to indicate a first search space; a third message is detected in the first search space, the third message being used to indicate a scheduling message of a third PDSCH of a first downlink carrier of the first cell or a scheduling message of a first PUSCH of a second uplink carrier of the first cell; first configuration information of a second cell is received, the first configuration information of the second cell being used to indicate a second search space; and the first message is detected in the second search space.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, the first configuration information of the first cell is the same as the first configuration information of the second cell, the second search space is the same as the first search space, and the first message is detected in the first search space.

[0017] It should be understood that in the above possible implementations, both the self-scheduling and joint scheduling search spaces exist and are shared, meaning that the terminal device can also blindly detect the first message in the first search space.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, second configuration information of a first cell is received, the second configuration information of the first cell being used to indicate a third search space; a fourth message is detected in the third search space, the fourth message being used to indicate a scheduling message of a third PDSCH of a first downlink carrier of the first cell or a scheduling message of a first PUSCH of a second uplink carrier of the first cell; and the first message is detected in the third search space.

[0019] It should be understood that in the above possible implementations, there exists a self-scheduled search space, and the first message can also be blindly detected in the self-scheduled search space.

[0020] In conjunction with the first aspect, in some implementations of the first aspect, second configuration information of a second cell is received, the second configuration information of the second cell being used to indicate a fourth search space; and the second message is detected in the fourth search space.

[0021] In conjunction with the first aspect, in some implementations of the first aspect, third configuration information of a second cell is received, the third configuration information of the second cell is used to indicate a fifth search space, the fifth search space is used to detect the first message; the second configuration information of the second cell is the same as the third configuration information of the second cell, the fourth search space is the same as the fifth search space, and the second message is detected in the fifth search space.

[0022] It should be understood that in the above possible implementations, both the joint scheduling and the uplink scheduling search spaces exist and are shared, meaning that the terminal device can also blindly detect the second message in the joint scheduling search space.

[0023] In conjunction with the first aspect, in some implementations of the first aspect, fourth configuration information of the second cell is received, the fourth configuration information of the second cell is used to indicate a sixth search space, the sixth search space is used to detect the first message; and the second message is detected in the sixth search space.

[0024] It should be understood that in the above possible implementations, there exists a joint scheduling search space, and the second message is also blindly detected in the joint scheduling search space.

[0025] In conjunction with the first aspect, in some implementations of the first aspect, receiving first indication information, the first indication information being used to indicate the detection of the first message in a seventh search space, or the first indication information being used to indicate the detection of the first message information in an eighth search space, wherein the seventh search space includes a search space for carrying a fifth message, the fifth message being used to indicate the search space for the fifth PDSCH of the first downlink carrier of the first cell or the third PUSCH of the second uplink carrier of the first cell, and the eighth search space includes a search space for carrying the first message; receiving the first message on the first downlink carrier of the first cell includes: receiving the first message on the first downlink carrier of the first cell according to the first indication information.

[0026] For example, when the first indication information is used to indicate the detection of the first message in the eighth search space, the method further includes: receiving fifth configuration information, the fifth configuration information being used to indicate the eighth search space, the fifth configuration information including configuration information related to the second cell.

[0027] For example, when the first indication information is used to indicate the detection of the first message in the seventh search space, the method further includes: receiving sixth configuration information, the sixth configuration information being used to indicate the seventh search space, the seventh search space including the eighth search space, and the sixth configuration information including configuration information related to the first cell.

[0028] In summary, terminal devices can listen to at least one of the PDCCHs corresponding to self-scheduled, cross-carrier scheduled, and joint scheduled PDCCHs on the first cell and / or the second cell according to different configuration information.

[0029] Secondly, a resource scheduling method is provided, comprising: transmitting a first message on a first downlink carrier of a first cell, the first message indicating scheduling information of a physical downlink shared channel (PDSCH), the PDSCH corresponding to a first downlink carrier of the first cell and a second downlink carrier of a second cell; transmitting a second message indicating scheduling information of a physical uplink shared channel (PUSCH) of a first uplink carrier of the second cell; and receiving the PUSCH on the first uplink carrier of the second cell according to the second message.

[0030] According to the solution provided in this application, the network device can schedule the PDSCH of the first downlink carrier of the first cell and the PDSCH of the second downlink carrier of the second cell by sending a first message on the first downlink carrier of the first cell. In this scenario, the network device can then schedule the PUSCH of the first uplink carrier of the second cell according to the sent second message and receive the PUSCH sent by the terminal device, which effectively reduces the overhead of control signaling, meets diversified scheduling needs, and realizes diversified communication and system effectiveness.

[0031] For example, the PDSCH includes a first PDSCH and a second PDSCH, wherein the first PDSCH corresponds to the first cell and the second PDSCH corresponds to the second cell.

[0032] For example, the PDSCH includes a third PDSCH, wherein the third PDSCH corresponds to the first cell and the second cell.

[0033] In conjunction with the second aspect, in some implementations of the second aspect, sending the second message includes: sending the second message on a second downlink carrier of the second cell; or sending the second message on a first downlink carrier of the first cell; or sending the second message on a third downlink carrier of the third cell.

[0034] For example, if the local carrier supports PUSCH scheduling, the network device can also transmit DCI on the third downlink carrier of the second cell to indicate the scheduling information corresponding to the PDSCH of the third downlink carrier of the second cell.

[0035] For example, the network device may also transmit DCI on the fourth downlink carrier of the second cell to instruct the terminal device to schedule the PUSCH or PDSCH of the second cell across carriers; and / or to instruct the terminal device to jointly schedule the PDSCH of the second cell and the PDSCH of the third cell.

[0036] For example, if the local carrier does not support PUSCH scheduling, the network device can also send a DCI on the third downlink carrier of the first cell to instruct the terminal device to schedule PDSCH on the third downlink carrier of the first cell across downlink carriers.

[0037] For example, the network device may also transmit DCI on the fourth downlink carrier of the first cell to instruct the terminal device to schedule the PUSCH or PDSCH of the third cell across carriers; and / or to instruct the terminal device to jointly schedule the PDSCH of the first cell and the PDSCH of the third cell downlink.

[0038] In conjunction with the second aspect, in some implementations of the second aspect, a third message is transmitted on the first downlink carrier of the first cell, the third message being used to indicate a scheduling message for the third PDSCH of the first downlink carrier of the first cell or a scheduling message for the first PUSCH of the second uplink carrier of the first cell; first configuration information of the first cell is transmitted, the first configuration information of the first cell being used to indicate a first search space, the first search space being used to detect the third message; and first configuration information of the second cell is transmitted, the first configuration information of the second cell being used to indicate a second search space, the second search space being used to detect the first message.

[0039] In conjunction with the second aspect, in some implementations of the second aspect, second configuration information of the first cell is sent, the second configuration information of the first cell is used to indicate a third search space, the third search space is used to detect a fourth message and the first message, the fourth message is used to indicate the scheduling information of the fourth PDSCH of the first downlink carrier of the first cell or the scheduling information of the second PUSCH of the second uplink carrier of the first cell.

[0040] It should be understood that in the above possible implementations, there exists a self-scheduled search space, and the first message can also be blindly detected in the self-scheduled search space.

[0041] In conjunction with the second aspect, in some implementations of the second aspect, second configuration information of the second cell is sent, which is used to indicate a fourth search space, and the fourth search space is used to detect the second message.

[0042] In conjunction with the second aspect, in some implementations of the second aspect, third configuration information of the second cell is sent, which is used to indicate a fifth search space, and the fifth search space is used to detect the first message.

[0043] It should be understood that in the above possible implementations, both the joint scheduling and the uplink scheduling search spaces exist and are shared, meaning that the terminal device can also blindly detect the second message in the joint scheduling search space.

[0044] In conjunction with the second aspect, in some implementations of the second aspect, fourth configuration information of the second cell is sent, which is used to indicate a sixth search space, and the sixth search space is used to detect the first message and the second message.

[0045] It should be understood that in the above possible implementations, there exists a joint scheduling search space, and the second message is also blindly detected in the joint scheduling search space.

[0046] Thirdly, a communication device is provided, comprising: a transceiver unit configured to receive a first message on a first downlink carrier of a first cell, the first message indicating scheduling information of a Physical Downlink Shared Channel (PDSCH), the PDSCH corresponding to a first downlink carrier of the first cell and a second downlink carrier of a second cell; the transceiver unit is further configured to receive a second message indicating scheduling information of a Physical Uplink Shared Channel (PUSCH) of a first uplink carrier of the second cell; the transceiver unit is further configured to transmit the PUSCH on the first uplink carrier of the second cell according to the second message.

[0047] For example, the PDSCH includes a first PDSCH and a second PDSCH, wherein the first PDSCH corresponds to the first cell and the second PDSCH corresponds to the second cell.

[0048] For example, the PDSCH includes a third PDSCH, wherein the third PDSCH corresponds to the first cell and the second cell.

[0049] In conjunction with the third aspect, in some implementations of the third aspect, the transceiver unit is further configured to receive the second message on the second downlink carrier of the second cell; or receive the second message on the first downlink carrier of the first cell; or receive the second message on the third downlink carrier of the third cell.

[0050] In conjunction with the third aspect, in some implementations of the third aspect, the transceiver unit is further configured to receive first configuration information of a first cell, the first configuration information of the first cell being used to indicate a first search space; the processing unit is configured to detect a third message in the first search space, the third message being used to indicate a scheduling message of a third PDSCH of a first downlink carrier of the first cell or a scheduling message of a first PUSCH of a second uplink carrier of the first cell; the transceiver unit is further configured to receive first configuration information of a second cell, the first configuration information of the second cell being used to indicate a second search space; the processing unit is further configured to detect the first message in the second search space.

[0051] In conjunction with the third aspect, in some implementations of the third aspect, the processing unit is further configured to detect the first message in the first search space when the first configuration information of the first cell is the same as the first configuration information of the second cell.

[0052] In conjunction with the third aspect, in some implementations of the third aspect, the transceiver unit is further configured to receive second configuration information of the first cell, the second configuration information of the first cell being used to indicate a third search space; the processing unit is further configured to detect a fourth message in the third search space, the fourth message being used to indicate a scheduling message of the third PDSCH of the first downlink carrier of the first cell or a scheduling message of the first PUSCH of the second uplink carrier of the first cell; the processing unit is further configured to detect the first message in the third search space.

[0053] In conjunction with the third aspect, in some implementations of the third aspect, the transceiver unit is further configured to receive second configuration information of the second cell, the second configuration information of the second cell being used to indicate the fourth search space; the processing unit is further configured to detect the second message in the fourth search space.

[0054] In conjunction with the third aspect, in some implementations of the third aspect, the transceiver unit is further configured to receive third configuration information of the second cell, the third configuration information of the second cell being used to indicate a fifth search space, the fifth search space being used to detect the first message; the processing unit is further configured to detect the second message in the fifth search space when the second configuration information of the second cell is the same as the third configuration information of the second cell.

[0055] In conjunction with the third aspect, in some implementations of the third aspect, the transceiver unit is further configured to receive fourth configuration information of the second cell, the fourth configuration information of the second cell being used to indicate a sixth search space, the sixth search space being used to detect the first message; the processing unit is further configured to detect the second message in the sixth search space.

[0056] Fourthly, a communication device is provided, comprising: a transceiver unit configured to transmit a first message on a first downlink carrier of a first cell, the first message indicating scheduling information of a Physical Downlink Shared Channel (PDSCH), the PDSCH corresponding to a first downlink carrier of the first cell and a second downlink carrier of a second cell; the transceiver unit is further configured to transmit a second message indicating scheduling information of a Physical Uplink Shared Channel (PUSCH) on a first uplink carrier of the second cell; the transceiver unit is further configured to receive the PUSCH on the first uplink carrier of the second cell according to the second message.

[0057] For example, the PDSCH includes a first PDSCH and a second PDSCH, wherein the first PDSCH corresponds to the first cell and the second PDSCH corresponds to the second cell.

[0058] For example, the PDSCH includes a third PDSCH, wherein the third PDSCH corresponds to the first cell and the second cell.

[0059] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to transmit the second message on the second downlink carrier of the second cell; or transmit the second message on the first downlink carrier of the first cell; or transmit the second message on the third downlink carrier of the third cell.

[0060] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to transmit a third message on a first downlink carrier of the first cell, the third message being used to indicate a scheduling message for a third PDSCH of the first downlink carrier of the first cell or a scheduling message for a first PUSCH of the second uplink carrier of the first cell; the transceiver unit is further configured to transmit first configuration information of the first cell, the first configuration information of the first cell being used to indicate a first search space, the first search space being used to detect the third message; the transceiver unit is further configured to transmit first configuration information of a second cell, the first configuration information of the second cell being used to indicate a second search space, the second search space being used to detect the first message.

[0061] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to transmit second configuration information of the first cell, the second configuration information of the first cell being used to indicate a third search space, the third search space being used to detect a fourth message and the first message, the fourth message being used to indicate scheduling information of the fourth PDSCH of the first downlink carrier of the first cell or scheduling information of the second PUSCH of the second uplink carrier of the first cell.

[0062] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to send third configuration information of the second cell, the third configuration information of the second cell being used to indicate a fifth search space, the fifth search space being used to detect the first message.

[0063] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to send fourth configuration information of the second cell, the fourth configuration information of the second cell being used to indicate a sixth search space, the sixth search space being used to detect the first message and the second message.

[0064] Fifthly, a terminal device is provided, including a transceiver, a processor, and a memory. The processor controls the transceiver to transmit and receive signals, the memory stores a computer program, and the processor calls and runs the computer program from the memory, causing the terminal device to perform the method described in the first aspect or any possible implementation thereof.

[0065] Optionally, the processor may be one or more, and the memory may be one or more.

[0066] Optionally, the memory may be integrated with the processor, or the memory may be separated from the processor.

[0067] Optionally, the terminal device may also include a transmitter and a receiver.

[0068] In a sixth aspect, a network device is provided, comprising a transceiver, a processor, and a memory, the processor controlling the transceiver to transmit and receive signals, the memory storing a computer program, and the processor retrieving and running the computer program from the memory, causing the network device to perform the methods of the second aspect or any possible implementation thereof.

[0069] Optionally, the processor may be one or more, and the memory may be one or more.

[0070] Optionally, the memory may be integrated with the processor, or the memory may be separated from the processor.

[0071] Optionally, the network device may also include a transmitter and a receiver.

[0072] In a seventh aspect, a communication system is provided, including the aforementioned terminal equipment and / or network equipment.

[0073] In one possible design, the communication system may also include other devices that interact with the terminal device as provided in the embodiments of this application.

[0074] In another possible design, the communication system may also include other devices that interact with the network device as provided in the embodiments of this application.

[0075] Eighthly, a communication apparatus is provided, comprising a module or unit for implementing the method of the first aspect or any possible implementation thereof; or a module or unit for implementing the method of the second aspect or any possible implementation thereof.

[0076] In one design, the communication device is a communication chip, which may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0077] In another design, the communication device is a communication equipment (e.g., a terminal device, a P-CSCF device, or a gateway device), and the communication chip may include a transmitter for sending information or data, and a receiver for receiving information or data.

[0078] Ninth aspect, a computer-readable storage medium is provided that stores a computer program or code, which, when executed on a computer, causes the computer to perform the methods of the first aspect or any possible implementation thereof, and the methods of the second aspect or any possible implementation thereof.

[0079] In a tenth aspect, a chip is provided, comprising at least one processor coupled to a memory for storing a computer program, the processor for calling and running the computer program from the memory, such that a communication device having the chip mounted performs the methods of the first aspect or any possible implementation thereof, and the methods of the second aspect or any possible implementation thereof.

[0080] The chip may include an input circuit or interface for transmitting information or data, and an output circuit or interface for receiving information or data.

[0081] Eleventhly, a computer program product is provided, the computer program product comprising: computer program code, which, when executed by a terminal device, causes the terminal device to perform the method of the first aspect or any possible implementation thereof, or, when executed by a network device, causes the network device to perform the method of the second aspect or any possible implementation thereof.

[0082] According to the scheme of the embodiments of this application, multiple carriers' physical downlink shared channels can be scheduled through a single downlink control information, effectively reducing the overhead cost of control signaling, meeting diversified scheduling requirements, and realizing diversified communication and system effectiveness. Meanwhile, in carrier aggregation scenarios, a design scheme for the search space of joint scheduling of a carrier is provided, where joint PDSCH scheduling is configured for that carrier. Attached Figure Description

[0083] Figure 1 This is a schematic diagram of a communication system to which this application applies.

[0084] Figure 2 This is a schematic diagram applicable to the carrier aggregation scenario of this application.

[0085] Figure 3 This is a schematic diagram showing the distribution of PDCCH candidate positions under different aggregation levels as specified in the current protocol.

[0086] Figure 4 This is a schematic diagram illustrating cross-carrier scheduling applicable to this application.

[0087] Figure 5 This is a schematic diagram illustrating an example of the resource scheduling method applicable to this application.

[0088] Figure 6 This is an example diagram illustrating the determination of the search space applicable to this application.

[0089] Figure 7 This is an example diagram illustrating the determination of PDCCH monitoring timing applicable to this application.

[0090] Figure 8 This is another schematic diagram illustrating the determination of the search space applicable to this application.

[0091] Figure 9 This is another schematic diagram illustrating the resource scheduling method applicable to this application.

[0092] Figure 10 This is yet another example of a diagram illustrating the determination of the search space applicable to this application.

[0093] Figure 11 This is another schematic diagram illustrating the resource scheduling method applicable to this application.

[0094] Figure 12 This is yet another example of a diagram illustrating the determination of the search space applicable to this application.

[0095] Figure 13 This is a schematic diagram of a communication device to which this application applies.

[0096] Figure 14 This is another schematic diagram of a communication device to which this application applies.

[0097] Figure 15 This is a schematic diagram of a communication device to which this application applies.

[0098] Figure 16 This is a schematic diagram of a communication device to which this application applies. Detailed Implementation

[0099] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0100] The technical solutions of this application can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Advanced Long Term Evolution System LTE-A, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, and 5th Generation (5G) system or New Radio (NR), etc.

[0101] To facilitate understanding of the embodiments of this application, firstly, in conjunction with Figure 1 The communication system applicable to the embodiments of this application is described in detail.

[0102] Figure 1 This is a schematic diagram of a communication system 100 applicable to the channel resource transmission method of this application. For example... Figure 1 As shown, the communication system 100 includes: a network controller 110, at least one network device (e.g., network device 120 and network device 130) and at least one terminal device (e.g., terminal device 140 and terminal device 150).

[0103] Specifically, terminal devices 140 and 150 access the wireless network through network devices 120 and 130, respectively. The wireless communication network may include multiple network devices capable of supporting communication between multiple user devices. User devices can communicate with network devices via downlinks and uplinks. A downlink (or forward link) refers to the communication link from the network device to the user device, while an uplink (or reverse link) refers to the communication link from the user device to the network device. It should be understood that... Figure 1 This illustration uses only one network device as an example, but the embodiments of this application are not limited to this. For example, the system may include more network devices; similarly, the system may include more terminal devices. It should also be understood that the system may also be referred to as a network, and the embodiments of this application are not limited thereto.

[0104] The terminal device in this embodiment (e.g., terminal device 140 or terminal device 150) can be mobile or fixed. The terminal device communicates with one or more core networks (CNs) via a Radio Access Network (RAN). The terminal device can refer to a User Equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment. The terminal device can be a station (ST) in a Wireless Local Area Network (WLAN), or a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, and next-generation communication system, such as a terminal device in a 5G network or a terminal device in a future evolved Public Land Mobile Network (PLMN), etc., and the embodiments of this application are not limited thereto.

[0105] The network device in this application embodiment (e.g., network device 120 or network device 130) can be a device for communicating with terminal devices. The network device can be a network device (Base Transceiver Station, BTS) in the Global System for Mobile Communications (GSM) or Code Division Multiple Access (CDMA), a network device (NodeB, NB) in the Wideband Code Division Multiple Access (WCDMA) system, an evolved network device (eNB or eNodeB) in the LTE system, a radio controller in the Cloud Radio Access Network (CRAN) scenario, or the network device can be a relay station, access point, vehicle-mounted equipment, wearable device, or a network device in the 5G system, such as a Transmission Point (TP), Transmission Reception Point (TRP), base station, small base station equipment, etc., or a network device in the future evolved Public Land Mobile Network (PLMN) network, etc. The embodiments of this application are not limited.

[0106] In this embodiment, network device 120 and network device 130 can be controlled and / or scheduled by network controller 110. Network controller 110 can perform unified resource scheduling and management of the multiple network devices it controls based on information obtained and maintained from each network device. For example, it can send control messages and / or instruction information to the multiple network devices it controls.

[0107] It should be understood that the network controller 110 can be a separate physical device (such as...) Figure 1 (As shown), it can also be a software and / or hardware functional module integrated into a network device, which is not particularly limited in this application.

[0108] In NR, the network device (e.g., network device 120) to which the terminal device (e.g., terminal device 140) first connects is called the serving network device. After powering on, the terminal device 140 can select a suitable or acceptable cell through cell search, and then complete the connection with the network side through the attach procedure. After completing the attach procedure, the terminal device 140 can communicate with the network device 120.

[0109] It should be understood that Figure 1 This is a simplified illustration for ease of understanding only. The communication system 100 may also include other network devices and / or terminal devices. Figure 1 It was not drawn in the middle.

[0110] It should be noted that the technical solution of this application supports terminal devices in effectively realizing diversified resource scheduling in carrier aggregation scenarios. Figure 2 This is a schematic diagram applicable to the carrier aggregation scenario of this application, such as... Figure 2 As shown, a network device can schedule the PDSCH of multiple aggregated carriers (e.g., carrier 1 and carrier 2) by sending a Downlink Control Information (DCI), where each PDSCH corresponds to carrier 1 and carrier 2. Here, carrier 1 can be understood as the first downlink carrier of cell #A, and carrier 2 can be understood as the second downlink carrier of cell #B. For example, the aforementioned PDSCH includes PDSCH1 and PDSCH2, where PDSCH1 corresponds to the first downlink carrier of cell #A, and PDSCH2 corresponds to the second downlink carrier of cell #B; or, the PDSCH includes PDSCH3, where PDSCH3 corresponds to the first downlink carrier of cell #A and the second downlink carrier of cell #B. It should be understood that a cell includes at least one downlink carrier and zero or more uplink carriers. This application embodiment uses a cell including one downlink carrier and one uplink carrier as an example for illustration.

[0111] It should be understood that before data transmission between network devices and terminal devices, the terminal device can receive downlink control information (DCI) on the PDCCH and, according to the DCI's indication, receive downlink data on the Physical Downlink Shared Channel (PDSCH); or send uplink data on the Physical Uplink Shared Channel (PUSCH). The process of the terminal device receiving the DCI can be as follows: the network device configures a CORESET and search space for the terminal device; the terminal device blindly detects candidate DCI formats within the configured search space; then, it performs a CRC check on the received DCI; if the CRC check is successful, the terminal device decodes the DCI and obtains its content.

[0112] However, in carrier aggregation scenarios, with the increasing overhead of control signaling, when a joint scheduling PDSCH is configured for a carrier—that is, by transmitting a DCI on the first downlink carrier of cell #A (or the second downlink carrier of cell #B) to indicate the scheduling information of the PDSCH, where the PDSCH corresponds to the first and second downlink carriers of cell #A—how to design the joint scheduling search space for this carrier, and how to schedule the uplink of this carrier, are currently not considered.

[0113] In view of this, this application provides a communication method that enables terminal devices to schedule downlink data of multiple carriers through a single downlink control information in carrier aggregation scenarios, thereby reducing the overhead of control signaling; at the same time, it realizes the uplink scheduling requirements of carriers configured with joint scheduling PDSCH, and provides a scheme for configuring and determining the joint scheduling search space.

[0114] To better understand the technical solution of this application, a brief introduction to some of the terms used in this application will be given below.

[0115] 1. Control Channel

[0116] The control channel involved in this application can be used to carry resource scheduling information and other control information. For example, the control channel can be a physical downlink control channel (PDCCH), an enhanced physical downlink control channel (ePDCCH), a new radio physical downlink control channel (NR-PDCCH), and other downlink channels with the above functions defined as the network evolves. For ease of explanation, the method of transmitting the control channel in the embodiments of this application will be described in detail below using only PDCCH as an example. It should be understood that the channel can also be called a signal or other names, and the embodiments of this application do not particularly limit this.

[0117] For example, the Physical Downlink Control Channel (PDCCH) is used to carry Downlink Control Information (DCI). The PDCCH is primarily used for: (1) sending downlink scheduling information, also known as Downlink Assignment (DL Assigment), so that the UE can receive the PDSCH; (2) sending uplink scheduling information, also known as Uplink Grant (UL Grant), so that the UE can send the PUSCH; (3) sending aperiodic channel quality indicator (CQI) reporting requests; (4) notifying the UE of changes in the multicast control channel (MCCH); (5) sending uplink power control commands; (6) feeding back information related to the hybrid automatic repeat request (HARQ); and (7) including a radio network tempory identity (RNTI), which is implicitly included in the cyclic redundancy check (CRC), etc.

[0118] It should be understood that DCI generally has multiple DCI formats, and each DCI format and the specific information it includes differ according to its function. DCI can use scrambling such as system information-radionetwork temporary identity (SI-RNTI), paging-radionetwork temporary identity (P-RNTI), or random access-radio network temporary identity (RA-RNTI) to indicate cell-level information; it can also use scrambling such as cell-radio network temporary identity (C-RNTI), configured scheduling-radio network temporary identity (CS-RNTI), or semi-persistent configured scheduling-radio network temporary identity (SP-CSI-RNTI) to indicate UE-level information. A cell can schedule multiple UEs simultaneously in uplink and downlink, meaning a cell can send multiple scheduling messages per scheduling time unit. Each scheduling message is transmitted on an independent PDCCH, meaning that a cell can send multiple PDCCHs simultaneously within a single scheduling time unit.

[0119] 2. Control Channel Element (CCE), Resource Element Group (REG), and Aggregation Level (AL):

[0120] A Resource Element Group (REG) can be understood as the basic unit for downlink control signaling to allocate physical resources, used to define the mapping from downlink control signaling to resource elements (REs). For example, a CCE consists of 6 REGs, and one REG corresponds to one resource block (RB), meaning that a CCE is a contiguous resource block containing 72 REs.

[0121] It should be understood that the control area used for transmitting PDCCH is composed of logically divided Control Channel Units (CCEs). The basic unit of time-frequency resources of DCI carried on PDCCH is also CCE. A PDCCH can be transmitted on different aggregation levels (AL), where AL represents the number of CCEs contained in the search space. For example, AL can take values ​​of 1, 2, 4, 8, and 16. The embodiments of this application do not particularly limit the value of the aggregation level. Figure 3 A schematic diagram showing the distribution of PDCCH candidate positions at different aggregation levels is presented. Figure 3 As shown, when AL=1, it means that DCI is carried on 1 CCE, the size of each search space is 1 CCE, the number of PDCCH candidates is 6, the size of the search space is 6 CCEs, and these 6 CCEs are continuously distributed in the time-frequency resources; and so on. For the sake of simplicity, they will not be listed one by one here.

[0122] It should be noted that the search space shown in the figure corresponds to different shaded areas at the same aggregation level, with each shade representing a candidate location for PDCCH. For the sake of brevity, explanations of the same or similar cases will be omitted in the following text.

[0123] In addition, network devices can determine the aggregation level used for a particular PDCCH based on factors such as channel quality. For example, if the PDCCH is sent to a UE with good downlink channel quality (e.g., located in the cell center), then using one CCE to send the PDCCH may be sufficient; if the PDCCH is sent to a UE with poor downlink channel quality (e.g., located at the cell edge), then eight or even sixteen CCEs may be used to send the PDCCH to achieve sufficient robustness.

[0124] 3. Carrier aggregation

[0125] To meet the requirements of increased peak data rates for single users and improved system capacity, carrier aggregation technology was introduced in LTE-A to increase system transmission bandwidth. Carrier aggregation combines two or more component carriers (CCs) together to achieve greater transmission bandwidth. To ensure backward compatibility, each carrier has a maximum frequency of 20MHz. The carrier randomly accessed by the UE is called the primary carrier component (PCC), and the cell corresponding to the primary carrier is the primary cell (PCell). The primary cell maintains a Radio Resource Control (RRC) connection with the terminal equipment. The primary cell may include one downlink carrier and one uplink carrier. Carriers other than the primary carrier are called secondary carrier components (SCCs), and the cells corresponding to the secondary carriers are called secondary cells (SCells). These secondary cells provide additional radio resources. There is no RRC communication between the SCell and the terminal equipment. The secondary cell may include one downlink carrier.

[0126] It should be understood that the PCell is determined during connection establishment. The SCell is added / modified / released via RRC connection reconfiguration messages after the initial security activation process.

[0127] In practice, each carrier unit corresponds to an independent cell, and one carrier unit can usually be equated with one cell. In the embodiments of this application, the meanings of carrier and carrier unit can be understood as the same. The CA function can support continuous or non-contiguous carrier aggregation. In order to efficiently utilize fragmented spectrum, carrier aggregation supports aggregation between different carrier units, including: aggregation of carrier units with the same or different bandwidths; aggregation of adjacent or non-adjacent carrier units within the same frequency band; and aggregation of carrier units within different frequency bands. That is, carrier aggregation scenarios can be divided into three types, including: in-band continuous carrier aggregation, in-band non-contiguous carrier aggregation, and out-of-band non-contiguous carrier aggregation.

[0128] 4. Cross-carrier scheduling

[0129] Cross-carrier scheduling based on the carrier indicator field (CIF) supports scheduling radio resources on one serving cell using a PDCCH transmitted on one serving cell. That is, control information is transmitted on one carrier element (e.g., PDCCH), while the corresponding data channel resources are transmitted on another carrier element (e.g., PDSCH). In other words, when a cell is configured for cross-carrier scheduling, PDCCH cannot be transmitted on that cell, but downlink control information can be transmitted on other cells. In other words, the base station schedules the corresponding resources on its own cell by transmitting downlink control information in other cells.

[0130] It should be understood that Figure 4 A schematic diagram of PCell cross-carrier scheduling of SCell is shown, as follows: Figure 4 As shown, no PDCCH is configured on the SCell. Control information is transmitted through the PDCCH of the PCell, while the corresponding data information is transmitted on the PDSCH of the SCell. That is, the terminal device receives control information on the PCell and realizes the scheduling of resources on the SCell.

[0131] 5. Control resource set (CORESET)

[0132] A UE can be configured with multiple CORESETs. A CORESET can include time-frequency resources, which can be continuous or discontinuous resource units in the time-frequency domain. For example, each CORESET occupies an integer multiple of 6 RBs (72 subcarriers) in the frequency domain; each CORESET can be the number of time units in the time domain, such as the number of symbols in a subframe, time slot, or micro-time slot, typically occupying {1, 2, 3} symbols in the time domain, which can be located at any position within a time slot. The terminal device can listen to the PDCCH on one or more CORESETs.

[0133] In the embodiments of this application, for a network device, CORESET can be understood as the resources occupied by the transmission control channel; for a terminal device, the PDCCH search space of each terminal device belongs to the CORESET. In other words, the network device can determine the resources used to transmit the PDCCH from the CORESET, and the terminal device can determine the PDCCH search space from the CORESET.

[0134] 6. Search space (SS)

[0135] The search space for blind detection of terminal equipment includes a common search space (CSS) and a UE-specific search space (USS). The common search space is used to transmit cell-level public information, such as control information related to paging, random access response (RAR), and broadcast control channel (BCCH); this information is the same for all user equipment and must be monitored. The UE-specific search space is used to transmit user equipment-level information, such as user-level data scheduling and power control information scheduling. However, when there are insufficient available resources in the UE-specific search space, the common search space can also be used to transmit control information belonging to a specific user equipment.

[0136] It should be understood that this application does not exclude the possibility of redistributing or redefining the search space. Resources used to transmit terminal device-level information can all be defined as the UE-specific search space described in the embodiments of this application.

[0137] A search space is defined for a specific CCE aggregation level. A terminal device can have multiple search spaces, and the CCEs in each search space can be continuously distributed. If the UE is configured with carrier aggregation, the UE can listen to the set of PDCCH candidates for all active serving cells in each non-DRX subframe. This means that the terminal device needs to try to decode each PDCCH in the set according to the DCI format to be listened to. For the network device, when sending a PDCCH including the Carrier Indication Field (CIF), it knows which serving cell the PDCCH corresponds to and the set of possible PDCCH candidates for that PDCCH. However, for the UE, it is not sure what the CIF value included in the PDCCH is, that is, it is not sure which serving cell can send the PDCCH to the UE. The UE knows the set of CIFs that may be included in the PDCCH sent to the UE by each specific serving cell, so the UE can try all possible CIF values ​​to blindly detect the PDCCH on that serving cell. The search space S at aggregation levels AL=1, 2, 4, 8 is defined as follows. k (L) Defined as the set of PDCCH candidates, this set is called the search space of the terminal device.

[0138] For example, Table 1 provides an aggregation level AL, search space size, and the number M of PDCCH candidates to be monitored within a given search space. (L) The correspondence between them:

[0139] Table 1

[0140]

[0141] As can be seen, the size of the search space and the number of PDCCH candidates differ at different aggregation levels. Furthermore, the size of the search space M = M (L) •L, or in other words, the number of CCEs contained in the search space is the product of the aggregation level and the number of PDCCH candidates. The PDCCHs sent by network devices to different user devices can have different aggregation levels.

[0142] It should be understood that Table 1 is for ease of understanding only, taking into account the aggregation level AL, search space size, and the number of PDCCH candidates M to be monitored within a given search space as defined in the LTE protocol. (L) This explains the correspondence between the parameters, but this should not constitute any limitation on the embodiments of this application. This application also does not exclude the use of different aggregation levels (AL), search space size, and the number of PDCCH candidates (M) to be monitored within a given search space in other protocols. (L) The correspondence between them may be redefined, and the possibility of defining more parameters cannot be ruled out.

[0143] It should also be understood that the common search space and the UE-specific search space may overlap, as may the UE-specific search spaces belonging to different user equipments. If an overlapping area is occupied by one user equipment, other user equipments will no longer be able to use these CCE resources. During scheduling, network devices can select an available PDCCH candidate from the corresponding search space for each user equipment to be scheduled. If CCE resources can be allocated, scheduling will proceed; otherwise, scheduling will not be performed.

[0144] It should be noted that the terminal device can determine the corresponding search space based on the search space configuration information sent by the network device. For example, Table 2 shows the parameters that may be included in the configuration information associated with the search space and their specific meanings. In this embodiment, the configuration information used to determine the search space includes at least one parameter from Table 2.

[0145] Table 2

[0146]

[0147]

[0148] The process of determining the search space PDCCH for the terminal device mainly includes: determining the CORESET, determining the searchSpaceId, and determining the start and end CCE positions corresponding to the PDCCH candidates. Possible implementation steps may include: First, based on the current search space and the associated CORESET configuration, determining the candidate PDCCHs, where the start position of the time-domain symbol is determined by the current search space configuration, and the number of time-domain symbols is determined by the associated CORESET. Then, based on the current search space and the associated CORESET configuration, determining the CCE index (i.e., the start position and number of CCEs) of each candidate PDCCH within the CORESET; the specific CCE is determined through a search space function. Finally, the UE can identify its own DCI by performing blind CRC detection on the listening position.

[0149] When configuring the search space, the terminal device configures the number of PDCCH candidates corresponding to each PDCCH aggregation level. The terminal device can determine the position of each PDCCH candidate based on at least one of the following formulas:

[0150] or

[0151]

[0152] For any public search space, For the UE-specific search space Y p,-1 =n RNTI ≠0, A p =39827. If pmod3=0, A p =39829; if pmod3=1, A p =39839; if pmod3=2, D=65537; i=0,...,L-1; where p is the COERSET ID, s is the searchspace ID, and L is the aggregation level. For time slot numbering, Number the PDCCH candidates, N CCE,p The number of CCEs within COERSETp, numbered from 0 to N. CCE,p -1.

[0153] It should be understood that n CI For the carrier indication field, if a carrier is configured for cross-carrier scheduling, then n CI If n is a positive integer, then n is a negative integer.CI =0; if a carrier is configured for joint scheduling, then n CI This is a carrier indication field associated with the joint scheduling search space; this field is used to identify the joint scheduling search space. Here, n CID This serves as the identifier for a serving cell group, representing the ID of a serving cell group associated with the search space. The cells within this serving cell group can be jointly scheduled cells. Additionally, in This represents the number of PDCCH candidates corresponding to aggregation level L. This refers to the search space associated with a serving cell.

[0154] For public search spaces, For a specific search space of UE For all n CI The maximum value among the number of PDCCH candidates corresponding to the CCE aggregation level L in the searchspace; n RNTI It is the value of C-RNTI.

[0155] 7. PDCCH blind testing

[0156] Since the PDCCH is a command sent by the network device, and the UE has not received any other information besides some system information beforehand, the UE does not know the number, size, location, DCI format, or aggregation level of the control channel elements (CCEs) it occupies. Therefore, the UE can blindly detect all PDCCH candidates in the search space, either in a common search space or a UE-specific search space, according to the desired DCI format, using different ALs. In other words, the UE detects the downlink control channel (PDCCH) sent by the network device through blind detection, thereby obtaining the downlink control information (DCI) and processing the corresponding data services.

[0157] Although the UE does not know in advance what format the DCI will be included in the PDCCH it is to receive, nor which PDCCH candidate will be used for transmission of that DCI, the UE knows its current state and the DCI information it expects to receive in that state. For example, in the IDLE state, the UE expects to receive a paging message; after initiating Random Access, the UE expects a RAR; and when there is uplink data to be transmitted, it expects a UL Grant, etc.

[0158] The UE knows its search space and therefore knows which CCEs the DCI might be distributed on. For different desired information, the UE attempts to perform a CRC check between the corresponding Radio Network Temporary Identifier (RANI), possible DCI format, and possible Aggregation Level (AL) and the CCEs within its search space. If the CRC check is successful, the UE knows that this information is what it needs, and thus knows the corresponding DCI format, allowing it to further decode the DCI content.

[0159] For example, the UE doesn't know which aggregation level the received PDCCH uses, so it can try all possibilities. For instance, for the common search space, the UE can search at Aggregation Level = 4 and Aggregation Level = 8. When blindly detecting at AL = 4, 16 CCEs require 4 blind detections, resulting in 4 PDCCH candidates; when blindly detecting at AL = 8, 16 CCEs require 2 blind detections, resulting in 2 PDCCH candidates. Therefore, for the common space, there are a total of 4 + 2 = 6 PDCCH candidates. However, for a UE-specific search space, the UE needs to perform blind detection at Aggregation Levels = 1, 2, 4, and 8, resulting in a total of 6 + 6 + 2 + 2 = 16 PDCCH candidates.

[0160] It should be understood that the UE can perform blind detection of the PDCCH on both the PCell and the active SCell. Furthermore, a UE configured with CA can perform a maximum of 44 + 32 * the number of active secondary cells. Specifically, 44 blind detections are performed on the PCell, and 32 blind detections are performed on the SCell because it does not require a common search space for blind detection.

[0161] During blind detection in the search space, the UE needs to attempt decoding of all possible DCI formats, but does not need to match all DCI formats. The possible DCI formats depend on what information the UE expects to receive and the transmission mode. For example, if the UE expects to receive downlink data using TM3, when decoding a PDCCH scrambled with C-RNTI, the UE can use its own C-RNTI to attempt decoding DCI format 1A and DCI format 2A. If the UE also expects to receive System Information (SI) in the same subframe, it can use SI-RNTI to attempt decoding DCI format 1A and DCI format 1C. More precisely, the UE uses the payload length corresponding to the DCI format to attempt blind detection. Before successfully decoding the PDCCH, the UE can attempt decoding on every possible PDCCH candidate. In other words, terminal blind detection involves the UE first calculating the starting position of the blind detection CCE based on the UE ID and subframe number, and then truncating the guessed DCI length at the starting position of the CCE for decoding. If the CRC of the decoded information bits is the same as the CRC included in the PDCCH, then the information bits carried by the current PDCCH are considered to be the downlink control information (DCI) being transmitted.

[0162] The resource scheduling method provided in this application will now be described in detail with reference to the accompanying drawings and embodiments.

[0163] It should be understood that this application will describe various embodiments in conjunction with cells. A cell can be a cell corresponding to a network device. A cell can belong to a macro network device or a network device corresponding to a small cell. The small cell here can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0164] First, to better illustrate the technical solution of this application, self-scheduling and downlink joint scheduling are defined. For example, self-scheduling can be achieved by transmitting message #A on the first downlink carrier of cell #a. Message #A indicates the scheduling information of the PDSCH of the first downlink carrier of cell #a, or indicates the scheduling information of the PUSCH of the first uplink carrier of cell #a. Downlink joint scheduling can be achieved by transmitting message #B on the first downlink carrier of cell #a or the second downlink carrier of cell #b. Message #B indicates the scheduling information of the PDSCH, where the PDSCH corresponds to the first downlink carrier of cell #a and the second downlink carrier of cell #b. For example, the PDSCH may include PDSCH#1 and PDSCH#2, where PDSCH#1 corresponds to the first downlink carrier of cell #a and PDSCH#2 corresponds to the second downlink carrier of cell #b; or, the PDSCH may include PDSCH#3, which corresponds to the first downlink carrier of cell #a and the second downlink carrier of cell #b. It should be noted that this application does not limit the number of cells used for joint scheduling. Joint scheduling of downlink data can reduce the number of blind detections by terminal equipment and the overhead of DCI, effectively improving the scheduling efficiency of carrier resources.

[0165] Optionally, downlink joint scheduling may further include transmitting message #C on the first downlink carrier of cell #a. Message #C indicates scheduling information for the PDSCH, wherein the PDSCH may correspond to the first downlink carrier of cell #a, the second downlink carrier of cell #b, and the third downlink carrier of cell #c, etc. It should be understood that this application does not limit the number of carriers used for joint scheduling.

[0166] As an example and not a limitation, the technical solution provided in this application is applicable to carrier aggregation scenarios. Assume that the active cells of a terminal device include three cells: Cell#A, Cell#B, and Cell#C. Cell#A is the primary cell (PCell), and Cell#B and Cell#C are secondary cells (SCell1 and SCell2), respectively. PCell and SCell1 support joint scheduling. Taking PCell scheduling of SCell1 as an example, i.e., messages for joint scheduling are sent on PCell, the application details how to schedule the PUSCH of the first uplink carrier of SCell1 using three possible implementation methods. This reduces control signaling overhead, addresses diverse scheduling needs, and improves the effectiveness of the communication system.

[0167] Method 1:

[0168] Figure 5 This is a schematic diagram illustrating an example of the resource scheduling method applicable to this application.

[0169] It should be noted that in this implementation, predefined rules can be used: PCell and SCell1 support joint scheduling of PDSCH, and SCell1 supports self-scheduling of PUSCH. For example... Figure 5 As shown, the method 500 includes:

[0170] S510, the network device sends message #1 to the terminal device on the first downlink carrier of PCell (i.e., an example of the first cell); correspondingly, the terminal device receives message #1 from the network device on the first downlink carrier of PCell.

[0171] Message #1 is used to indicate the scheduling information of the PDSCH, which corresponds to the first downlink carrier of PCell1 and the second downlink carrier of SCell1.

[0172] For example, the PDSCH may include a first PDSCH and a second PDSCH, wherein the first PDSCH corresponds to PCell and the second PDSCH corresponds to SCell1; or, the PDSCH may include a third PDSCH, wherein the third PDSCH corresponds to both PCell and SCell1. That is, by receiving message #1 from the network device, the terminal device can receive downlink data transmitted on the first downlink carrier of PCell and the second downlink carrier of SCell1.

[0173] S520, the network device sends message #2 to the terminal device on the second downlink carrier of SCell1 (i.e., an example of the second cell); correspondingly, the terminal device receives message #2 from the network device on the second downlink carrier of SCell1.

[0174] In this context, message #2 is used to indicate the scheduling information of the PUSCH of the first uplink carrier of SCell1. That is, by receiving message #2 from the network device, the terminal device can obtain the scheduling information of the PUSCH#A of the first uplink carrier of SCell1 by the network device.

[0175] It should be noted that before sending scheduling information to the terminal device, the network device can send an indication message #A in advance to the terminal device. This indication indicates that the terminal device is configured to jointly schedule PDSCH on PCell and SCell1, and supports uplink self-scheduling of SCell1. It also specifies or predefines that scheduling information for joint scheduling is sent on PCell, and scheduling information for uplink scheduling is sent on SCell1. Optionally, the predefined rules also include: after the terminal device is configured for joint scheduling, it can also receive scheduling information on the second downlink carrier of SCell1 to schedule the PUSCH of the first uplink carrier of SCell1.

[0176] Correspondingly, after receiving the indication information #A, the terminal device can receive scheduling information #1 on the first downlink carrier of PCell, which is used to schedule PDSCH #A of the first downlink carrier of PCell and PDSCH #B of the second downlink carrier of SCell1, or to schedule PDSCH #C corresponding to the first downlink carrier of PCell and the second downlink carrier of SCell1; it can also receive scheduling information #2 on the second downlink carrier of SCell1, which is used to schedule PUSCH #A of the first uplink carrier of SCell1.

[0177] It should be understood that in the above steps S510 and S520, message #1 or message #2 includes, but is not limited to, downlink control information (DCI), uplink scheduling information, etc.

[0178] As an example and not a limitation, the network device may also send message #1 or message #2 to the terminal via cell-specific or UE-group-specific DCI on the PDCCH; or send message #1 or message #2 to the terminal device via UE-specific DCI.

[0179] Optionally, the terminal device may also receive the above message #1 or message #2 in at least one of the following ways: RRC signaling, media access control (MAC CE) management element, physical layer signaling (e.g., PDCCH), etc.

[0180] S530, according to the received message #2, the terminal device sends PUSCH#A to the network device on the first uplink carrier of SCell1; correspondingly, the network device receives PUSCH#A from the terminal device on the first uplink carrier of SCell1.

[0181] In one possible implementation, the network device may also send message #3 to the terminal device on the second downlink carrier of SCell1 to indicate the scheduling information of PDSCH#C of the second downlink carrier of SCell1.

[0182] In another possible implementation, the network device may also send message #4 to the terminal device on the second downlink carrier of SCell1, to instruct the terminal device to schedule PUSCH#B of the third uplink carrier of SCell2 or PDSCH#D of the third downlink carrier of SCell2 across carriers; and / or to instruct the terminal device to jointly schedule PDSCH. This PDSCH corresponds to the second downlink carrier of SCell1 and the third downlink carrier of SCell2. For example, this PDSCH includes PDSCH#E and PDSCH#F, where PDSCH#E corresponds to SCell1 and PDSCH#F corresponds to SCell2; or, this PDSCH includes PDSCH#G, which corresponds to both SCell1 and SCell2.

[0183] For example, a transport block carried in a PDSCH scheduled by a network device is mapped to a physical resource block on the downlink active bandwidth portion (BWP). If the physical resource block corresponds to a downlink carrier of cell 1, then the PDSCH corresponds to cell 1; if the physical resource block corresponds to both a downlink carrier of cell 1 and a downlink carrier of cell 2, then the PDSCH corresponds to both cell 1 and cell 2. In summary, under this possible implementation, the PUSCH of the first uplink carrier of SCell1 can be implemented through SCell1 self-scheduling, i.e., the network device sends message #2 on the second downlink carrier of SCell1 to instruct the terminal device to self-schedule the PUSCH#A of the first uplink carrier of SCell1; the PDSCH of the second downlink carrier of SCell1 can be implemented through PCell downlink joint scheduling or SCell1 self-scheduling, i.e., the network device sends message #3 on the third downlink carrier of SCell1 to instruct the terminal device to self-schedule the PDSCH#C of the second downlink carrier of SCell1; or sends message #1 on the first downlink carrier of PCell to instruct the terminal device to schedule the PDSCH#B of the second downlink carrier of SCell1.

[0184] It should be understood that the above embodiments of this application are for the case of aggregation of multiple cells (including at least one PCell and one SCell1), based on the downlink joint scheduling of SCell1's PDSCH, how the network device can effectively schedule the physical uplink shared channel (PUSCH) of the first uplink carrier of SCell1.

[0185] According to the scheme provided in the above embodiments, in the scenario of carrier aggregation, the network device can jointly schedule the first downlink carrier of PCell1 and the second downlink carrier PDSCH of SCell1 by sending message #1 on the first downlink carrier of PCell1, and at the same time, effectively realize the uplink scheduling requirements of the first uplink carrier of SCell1 by sending message #2 on the second downlink carrier of SCell1, thereby reducing the overhead cost of control signaling and realizing diversified scheduling requirements and the effectiveness of the communication system.

[0186] As an example and not a limitation, the above embodiment describes how to schedule uplink data for SCell1 when PCell and SCell1 support joint scheduling. This technical solution is a further optimization strategy for joint scheduling scenarios to meet diverse scheduling needs. Optionally, in this embodiment, the downlink joint scheduling and SCell1 uplink scheduling technical solutions can be decoupled, and the two can operate independently. That is, network devices and terminal devices can receive and send downlink data based on PCell and SCell1 supporting downlink joint scheduling, specifically corresponding to step S510 above. For simplicity, further details are omitted here.

[0187] It should be noted that in the above possible implementations, SCell1 is configured with downlink joint scheduling. Therefore, the information transmission between the network device and the terminal device can include one of the following: PCell self-scheduling, PCell downlink joint scheduling, PCell cross-carrier scheduling, and SCell1 self-scheduling. Thus, the terminal device can listen to at least one of the PDCCHs corresponding to PCell self-scheduling, PCell cross-carrier scheduling, and PCell joint scheduling on the PCell, or it can listen to at least one of the PDCCHs corresponding to SCell1 self-scheduling on SCell1, based on the configuration information. Figure 6 This diagram illustrates an example of a terminal device determining the search spaces of PCell and SCell1, as shown below. Figure 6 As shown, the method 600 includes:

[0188] S610, the network device determines configuration information #A and / or configuration information #B.

[0189] In this context, configuration information #A indicates search space #A, representing the search space for PCell self-scheduled PDSCH and / or PUSCH, used to carry PCell self-scheduled message #5; configuration information #B indicates search space #B, representing the search space for PCell and SCell1 jointly scheduled PDSCH, used to carry message #1.

[0190] It should be noted that each set of search space configuration information includes the search period, the number of time units for continuous searching in each search period, the monitoring timing in that time unit, the aggregation degree of Control Channel Units (CCEs) in each monitoring timing, the potential transmission location of the Physical Downlink Control Channel (PDCCH) under each CCE aggregation degree, and the Downlink Control Information (DCI) format, and at least one of the corresponding CORESETs. The parameters and their interpretations in the search space configuration information have already been explained in Table 2 above, and will not be repeated here.

[0191] In one possible implementation, if configuration information #A and configuration information #B are identical, meaning the search spaces for PCell self-scheduling and downlink joint scheduling coexist and can be shared, then from a signaling configuration perspective, configuration information #A must include at least the configuration parameters associated with the PCell, and all configuration parameters must be effective. Configuration information #A can be used to indicate search spaces #A and #B. Configuration information #B contains two parameters, nrofCandidates and searchSpaceId, which are associated SCell1 configurations; the other parameters correspond to the configurations on the PCell.

[0192] Optionally, the network device determines configuration information #A, which indicates the search space #A for PCell self-scheduling and carries the PCell self-scheduling message #5. It should be understood that this search space #A resides on the PCell. Alternatively, the network device may agree with the terminal device, or notify the terminal device via signaling, that the search space #A can also be used for the blind detection message #1. In this case, since the PCell self-scheduling search space #A exists, the network device does not need to determine configuration information #B, and the downlink joint scheduling search space is shared with the PCell self-scheduling search space.

[0193] In another possible implementation, if configuration information #A and configuration information #B are different, meaning the search spaces for PCell self-scheduling and downlink joint scheduling coexist and are independent of each other, then from a signaling configuration perspective, configuration information #A must include at least the configuration parameters associated with the PCell, and all configuration parameters must be effective; configuration information #B must contain two parameters, nrofCandidates and searchSpaceId, that are associated with SCell1 configuration, while the other parameters are configurations corresponding to the PCell. It should be understood that configuration information #A and configuration information #B are two independent search space configurations.

[0194] For example, when determining the search space #B used for joint scheduling, the nrofCandidates and searchSpaceId parameters are effective in the configuration information #B, while other configuration parameters are ineffective.

[0195] It should be noted that for PCell and SCell1 supporting joint scheduling, the joint scheduling information can be sent on either the PCell or the SCell. The network device can notify the UE of which cell's downlink carrier to receive the joint scheduling information via signaling, such as RRC signaling; or the network device can notify the UE of which cell's downlink carrier to receive the joint scheduling information via predefined rules, such as on the downlink carrier corresponding to the cell with the smaller cell index. Once the UE determines which cell to receive the joint scheduling information on, its determined joint scheduling search space is the search space for that cell. The determination of the search space can include multiple configuration parameters.

[0196] For example, once the UE determines that the joint scheduling information is transmitted on the PCell, its determined joint scheduling search space is also on the PCell. It should be understood that the search space for PCell self-scheduling is also on the PCell, and in this case, the search space for PCell self-scheduling can be shared with the search space for downlink joint scheduling.

[0197] Alternatively, in another possible implementation, for PCell downlink joint scheduling, the network device can also add a joint scheduling search space configuration in the configuration information #B, that is, directly configure two new parameters nrofCandidates and searchSpaceId in the configuration information #B to indicate the search space #B.

[0198] Optionally, when configuring joint scheduling of different cells, the cell group number can be used to notify the UE. Then, when determining the joint scheduling search space, the terminal device can determine it based on the aforementioned cell group number. Correspondingly, the configuration information #B above includes this cell number information.

[0199] For example, suppose the network device configures M cells for the terminal device and activates N cells, where N is less than or equal to M. Furthermore, the network device can divide the M cells into K cell groups and the N cells into L cell groups, where UEs within the K cell groups can perform joint scheduling. The network device can then notify the terminal device which cells support joint scheduling using cell group numbers 0 to K-1 and / or 0 to L-1. Optionally, the cell group numbers may or may not be included in the search space configuration information. Next, when determining the search space, the UE can map the cell group number to the formula used to determine the CCE index, i.e.

[0200]

[0201] S620, the network device sends configuration information #A and / or configuration information #B to the terminal device; correspondingly, the terminal device receives configuration information #A and / or configuration information #B from the network device.

[0202] As an example and not a limitation, network devices may send configuration information #A and / or configuration information #B to terminal devices via broadcast signaling, RRC proprietary signaling, Media Access Control (MAC) layer signaling, or physical layer signaling.

[0203] It should be noted that before sending search space configuration information to the terminal device, the network device can send an indication message #B in advance to indicate on which cell the terminal device will receive the search space configuration information next. Generally, the terminal device can receive this indication message #B on the PCell. This indication message #B includes, but is not limited to, configuration information. For example, by receiving this indication message #B, the terminal device can know which serving cells are configured for downlink joint scheduling and which serving cells support uplink cross-carrier scheduling, etc.

[0204] For example, after receiving the indication information #B, the terminal device knows that PCell and SCell1 are configured with joint scheduling PDSCH, and the predefined rules include: the terminal device can receive scheduling information #1 on the first downlink carrier of PCell, for scheduling PDSCH #A of the first downlink carrier of PCell and PDSCH #B of the second downlink carrier of SCell1, or for scheduling PDSCH #C corresponding to the first downlink carrier of PCell and the second downlink carrier of SCell1; it can also receive scheduling information #2 on the second downlink carrier of SCell1, for scheduling PUSCH #A of the first uplink carrier of SCell1.

[0205] Optionally, the predefined rules include: after the terminal device is configured for joint scheduling, it can achieve self-scheduling by transmitting PDCCH on the second downlink carrier of SCell1.

[0206] In one possible implementation, the network device sends configuration information #A to the terminal device. This configuration information #A indicates the search space #A for PCell self-scheduling and carries the PCell self-scheduling message #5. It should be understood that this search space #A is on the PCell. Alternatively, the network device may agree with the terminal device, or notify the terminal device via signaling, that the search space #A can also be used for blind detection messages #1, i.e., to indicate that downlink joint scheduling control information is also blindly detected in the search space #A.

[0207] S630, the terminal device determines the search space #A and / or search space #B based on the received configuration information #A and / or configuration information #B.

[0208] In one possible implementation, if configuration information #A and configuration information #B are identical, meaning the search spaces for PCell self-scheduling and downlink joint scheduling coexist and can be shared, then the terminal device can determine search space #A and search space #B based on configuration information #A. It should be understood that since joint scheduling information is sent on the PCell, the determined search space is also on the PCell; therefore, both search space #A and search space #B are on the PCell. If the network device wishes to jointly schedule multiple cells, the configuration information of the search space can be associated with a predefined cell or with an indicated cell.

[0209] It should be understood that when determining the search space #A for PCell self-scheduling, the terminal device determines the CORESET ID, searchSpaceId, and the number of candidates corresponding to each CCE aggregation level based on the received configuration information #A associated with the PCell. It also determines the CCE index corresponding to each PDCCH candidate, including the start index and end index, based on the configuration parameters and the above-mentioned formula for calculating the position of PDCCH candidates. This is to enable the terminal device to detect the DCI used for PCell self-scheduling and downlink joint scheduling among the determined PDCCH candidates.

[0210] It should also be understood that when determining the search space #B for joint scheduling, the terminal device determines which cell the search space #B is on based on predefined or configured information, and then determines the search space #B based on the received configuration information associated with that cell. The configuration information includes the CORESET ID, searchSpaceId, and the number of candidates corresponding to each CCE aggregation level. The associated configuration information can be configuration information for a single cell or configuration information for multiple cells. For example, if cell 1 and cell 2 are configured for downlink joint scheduling, and search space #B is predefined or configured on the downlink carrier of cell 1, then the search space can be determined based on the search space configuration information on cell 1 or cell 2, or it can be jointly determined based on the search space information on cell 1 and cell 2. For example, the searchSpaceId in the search space configuration information of cell 2, the number of candidates corresponding to each CCE aggregation level, and the CORESET ID corresponding to the same searchSpaceId on cell 1 and cell 2. Optionally, if cells are configured for downlink joint scheduling, the cell group ID can be used to indicate this; therefore, the cell group ID can also be included when determining the search space.

[0211] Optionally, the terminal device determines a search space #A based on configuration information #A. This search space #A is used for blind detection of PCell self-scheduled message #5. It should be understood that this search space #A resides on the PCell. Alternatively, the network device may agree with the terminal device, or notify the terminal device via signaling, that the search space #A can also be used for blind detection of message #1. In this case, with a PCell self-scheduled search space #A existing, the terminal device can perform downlink joint scheduling and blind detection of PCell self-scheduled messages within search space #A.

[0212] In another possible implementation, if configuration information #A and configuration information #B are different, meaning that the search spaces for PCell self-scheduling and downlink joint scheduling coexist and are independent of each other, then the terminal device can determine search space #A based on configuration information #A and search space #B based on configuration information #B. In this case, since the joint scheduling information is sent on the PCell, the determined search space is also on the PCell, so both search space #A and search space #B are on the PCell.

[0213] S640, Network device configuration information #C.

[0214] The configuration information #C indicates the search space #C, which represents the search space of SCell1's self-scheduled PUSCH, used to carry message #2.

[0215] It should be noted that if the search space #C is determined for use by the SCell1 self-scheduling PUSCH, then all configuration parameters in configuration information #C will take effect. Among these, the uplink scheduling DCI format includes format 0_1.

[0216] In S650, the network device sends configuration information #C to the terminal device; correspondingly, the terminal device receives configuration information #C from the network device.

[0217] The configuration information #C includes at least the configuration parameters associated with SCell1.

[0218] S660, the terminal device determines the search space #C based on the received configuration information #C.

[0219] It should be noted that the method by which the terminal device determines the search space #C of SCell1 self-scheduling is the same as the method mentioned in step S630 above for determining the search space #A of PCell self-scheduling. For the sake of brevity, it will not be repeated here.

[0220] For example, the number of search spaces in each search space is 10. That is, in the control resource set CORESET of a cell configured with joint scheduling (e.g., PCell and SCell1 mentioned above), the network device can configure 10 searchSpaceIds separately for downlink joint scheduling, or it can configure 10 searchSpaceIds separately for SCell1 uplink scheduling, or downlink joint scheduling and SCell1 uplink scheduling can share 10 searchSpaceIds.

[0221] For example, regarding the above configuration method, a possible configuration method is as follows: when the serving cell is configured with downlink joint scheduling, then searchSpaceId and nrofCandidates in searchspaceforcombination take effect, where CORESET ID is the CORESET ID corresponding to the same searchSpaceId on the cell that sends the joint scheduling DCI.

[0222] As an example, and not a limitation, when configuring joint scheduling for terminal devices, at least two cells support joint scheduling (e.g., PCell and SCell1). The configuration information determining the joint scheduling search space can be associated with any serving cell; that is, this configuration information can be included in the configuration information of any cell. For example, if PCell and SCell1 are configured for joint scheduling, then the configuration information determining the joint scheduling search space can be associated with PCell, or with SCell1, or with the scheduled cell, or with the cell sending the joint scheduling DCI, or with the serving cell with the highest / lowest index among the joint scheduling cells, etc. This application does not impose any limitations on this. It should be noted that the associated cell corresponds to n in the formula for determining the position of each PDCCH candidate. CI .

[0223] Optionally, in the methods provided above, the determination of the search space of PCell and SCell1 can be performed by the terminal device itself according to predefined rules; or it can be determined by the network device and notified to the terminal device through broadcast signaling, RRC proprietary signaling, MAC layer signaling, or physical layer signaling, etc. This application does not limit this.

[0224] As an example and not a limitation, the above embodiment further determines the search space for uplink scheduling of SCell1 based on the determination of the downlink joint scheduling search space. Optionally, in the embodiments of this application, the technical solutions for determining the joint scheduling search space and determining the uplink scheduling search space can be decoupled, and the two operate independently. That is, based on the support of downlink joint scheduling by PCell and SCell1, the network device can determine the configuration information of the joint scheduling search space and send the configuration information to the terminal device. The terminal device can also determine the corresponding search space according to the configuration information, specifically corresponding to steps S610 to S630 above. For simplicity, it will not be elaborated here. It should be noted that the PDCCH monitoring occasion is a time unit used to monitor PDCCH, and the relevant parameters are given in the search space configuration. Among them, the PDCCH monitoring occasion is determined by three parameters: the PDCCH monitoring period configured by RRC, the PDCCH monitoring offset, and the PDCCH monitoring mode.

[0225] For example, Figure 7 This diagram illustrates an example of determining when to monitor the PDCCH. Figure 7 As shown, assuming the PDCCH monitoring period is two time slots, the slot offset is 0, the number of CORESET time-domain symbols associated with the search space is 1, and the symbol positions are 4, 5, 10, and 11. The PDCCH monitoring mode uses a 14-bit bitmap configuration to indicate the symbol positions that need to be monitored. In this diagram, the 14-bit indication is a binary number (00001100001100), where each bit represents the position of a symbol, where 1 indicates that monitoring is required and 0 indicates that monitoring is not required. Therefore, under this configuration, the terminal device can detect candidate PDCCHs on sym4, sym5, sym10, and sym11 in the second time slot of each detection period.

[0226] As an example and not a limitation, this application also provides another possible implementation for determining the search space. Figure 8 This diagram illustrates an example of a terminal device determining the search space for downlink joint scheduling and SCell1 uplink scheduling, as shown below. Figure 8 As shown, the method 800 includes:

[0227] S810, the network device sends configuration information #11 and / or configuration information #22 to the terminal device; correspondingly, the terminal device receives configuration information #11 and / or configuration information #22 from the network device.

[0228] Among them, configuration information #11 is used to indicate search space #11, which represents the search space for PCell self-scheduling; configuration information #22 is used to indicate search space #22, which represents the search space for joint downlink scheduling of PCell and SCell1.

[0229] It should be understood that configuration information #11 includes at least the configuration parameters associated with the PCell, and configuration information #22 has two parameters, nrofCandidates and searchSpaceId, which are associated with the SCell1 configuration, while the other parameters are the configurations on the corresponding PCell.

[0230] S820, the terminal device determines the search space #11 based on configuration information #11, and / or determines the search space #22 based on configuration information #22.

[0231] Search space #11 is used to carry message #11, which indicates PDSCH #11 of PCell or PUSCH #11 of PCell; search space #22 is used to carry message #22, which indicates PDSCH #22 of PCell and PDSCH #33 of SCell1.

[0232] In one possible implementation, a predefined rule can be used: the search spaces for PCell self-scheduling and downlink joint scheduling are shared. For example, if a search space for PCell self-scheduling exists, the terminal device can detect message #22 in search space #11; that is, the terminal device detects message #22, which indicates joint downlink scheduling, in the PCell self-scheduling search space #11. Alternatively, if the search spaces for PCell self-scheduling and downlink joint scheduling coexist, message #22 can also be detected in search space #11.

[0233] In another possible implementation, predefined rules can be used: the search spaces for PCell self-scheduling and downlink joint scheduling coexist but are independent of each other. For example, the terminal device detects message #11 in the self-scheduling search space #11 and message #22 in the joint scheduling search space #22.

[0234] It should be understood that the implementation of steps S810 and S820 is the same as that of steps S620 and S630 above, and will not be repeated here for the sake of brevity.

[0235] The S830 network device sends configuration information #33 to the terminal device; correspondingly, the terminal device receives configuration information #3 from the network device.

[0236] The configuration information #33 is used to indicate the search space #33, which represents the search space for the uplink scheduling of SCell1 and is used to carry message #33; message #33 is used to indicate the PUSCH #22 of the first uplink carrier of SCell1.

[0237] The S840 terminal device determines the search space #33 based on configuration information #33.

[0238] Among them, search space #33 is used to detect DCI #33.

[0239] It should be noted that the method by which the terminal device determines the search space #33 of SCell1 self-scheduling is the same as the method mentioned in step S630 above for determining the search space #11 of PCell self-scheduling. For the sake of brevity, it will not be repeated here.

[0240] Based on the above technical solution, a joint scheduling method was designed to solve the problems in carrier aggregation scenarios, such as configuring and determining the search space for joint scheduling of a carrier when a carrier is configured with joint PDSCH scheduling, as well as the uplink scheduling requirements of the carrier. This effectively reduces the overhead cost of control signaling and solves the problems of diversified scheduling requirements and the effectiveness of the communication system.

[0241] Method 2:

[0242] Figure 9 This is another schematic diagram illustrating the resource scheduling method applicable to this application. The difference from Method 1 is that the PUSCH on the first uplink carrier of SCell1 supports uplink cross-carrier scheduling by PCell. In other words, no PDCCH is configured on SCell1, control information is transmitted through the PDCCH of PCell, while the corresponding data information is transmitted on the PDSCH of SCell1. That is, the terminal device receives control information on PCell and realizes the scheduling of resources on SCell1.

[0243] It should be noted that in this implementation, predefined rules can be used: PCell and SCell1 support joint scheduling of PDSCH, and SCell1 supports uplink cross-carrier scheduling of PUSCH. For example... Figure 9 As shown, the method 900 includes:

[0244] S910, the network device sends message #a to the terminal device on the first downlink carrier of PCell (i.e., an example of the first cell); correspondingly, the terminal device receives message #a from the network device on the first downlink carrier of PCell.

[0245] The message #a indicates the scheduling information of the PDSCH, which corresponds to the first downlink carrier of PCell1 and the second downlink carrier of SCell1.

[0246] For example, the PDSCH may include a first PDSCH and a second PDSCH, wherein the first PDSCH corresponds to PCell and the second PDSCH corresponds to SCell1; or, the PDSCH may include a third PDSCH, wherein the third PDSCH corresponds to both PCell and SCell1. That is, by receiving message #a from the network device, the terminal device can receive downlink data transmitted on the first downlink carrier of PCell and the second downlink carrier of SCell1.

[0247] For example, by receiving message #a sent by the network device, the terminal device can schedule PDSCH#a of the first downlink carrier of PCell1 and PDSCH#b of the second downlink carrier of SCell1.

[0248] In S920, the network device sends message #b to the terminal device on the first downlink carrier of PCell; correspondingly, the terminal device receives message #b from the network device on the first downlink carrier of PCell.

[0249] The message #b is used to indicate the scheduling information of the PUSCH of the first uplink carrier of SCell1 (i.e., an example of the second cell). That is, by receiving the message #b, the terminal device can obtain the scheduling information of the PUSCH#a of the first uplink carrier of SCell1 by the network device.

[0250] It should be noted that before sending scheduling information to the terminal device, the network device can send indication information #C in advance to the terminal device. This indication indicates that the terminal device is configured for downlink joint scheduling of PCell and SCell1, and supports uplink cross-carrier scheduling of SCell1 on PCell. It also notifies or predefines that scheduling information for joint scheduling is sent on PCell, and scheduling information for uplink cross-carrier scheduling is also sent on PCell. Optionally, the predefined rules include: after the terminal device is configured for joint scheduling, it can also receive scheduling information #3 on the first downlink carrier of PCell, used to schedule the PUSCH of the first uplink carrier of SCell1.

[0251] S930, according to the received message #b, the terminal device sends PUSCH#a to the network device on the first uplink carrier of SCell1; correspondingly, the network device receives PUSCH#a from the terminal device on the first uplink carrier of SCell1.

[0252] In one possible implementation, the network device may also send a message #c to the terminal device on the first downlink carrier of PCell1 to indicate the scheduling information of PDSCH#c on the second downlink carrier of SCell1.

[0253] In another possible implementation, the network device may also send message #d to the terminal device on the first downlink carrier of PCell to indicate the scheduling information of PUSCH#b of the third uplink carrier of SCell2 and / or the scheduling information of PDSCH#d of the third downlink carrier of SCell2; or to jointly schedule the PDSCH of multiple cells such as PCell, SCell1 and SCell2.

[0254] In the above possible implementations, since SCell1 supports cross-carrier scheduling, the second downlink carrier of SCell1 is not configured with a PDCCH, and the terminal device does not need to listen to the PDCCH of SCell1. In other words, SCell1 does not support self-scheduling on its own carrier, nor does it support cross-carrier scheduling of SCell1 and / or downlink joint scheduling of other cells.

[0255] It should be noted that when SCell1 and PCell support downlink joint scheduling and also support downlink cross-carrier scheduling by PCell, the terminal device can use two different DCI formats to schedule the PDSCH of the second downlink carrier of SCell1 respectively. Optionally, the DCI sizes of these two formats are aligned during blind detection, or these two DCI formats cannot be blindly detected simultaneously to avoid resource scheduling chaos. In addition, network devices can reduce the number of blind detections by terminal devices through semi-static configuration of RRC signaling.

[0256] Similarly, the DCI sizes for PCell uplink cross-carrier scheduling and downlink cross-carrier scheduling also need to be aligned during blind detection.

[0257] In summary, under this possible implementation, the PUSCH of the first uplink carrier of SCell1 can be implemented through PCell uplink cross-carrier scheduling. Specifically, the network device sends message #b on the first downlink carrier of PCell to instruct the terminal device to schedule the PUSCH#a of the first uplink carrier of SCell1 across carriers. The PDSCH of the second downlink carrier of SCell1 can be implemented through downlink joint scheduling or PCell cross-carrier scheduling. Specifically, the network device sends message #c on the first downlink carrier of PCell to instruct the terminal device to schedule the PDSCH#c of the second downlink carrier of SCell1 across carriers; or sends message #a on the first downlink carrier of PCell to instruct the terminal device to jointly schedule the PDSCH#b of the second downlink carrier of SCell1. Clearly, the cell for cross-carrier scheduling of SCell1 uplink or downlink data and the cell for joint scheduling of SCell1 downlink data are the same—PCell.

[0258] According to the scheme provided in the above embodiments, in the scenario of carrier aggregation, the terminal device can achieve joint scheduling of PDSCH of PCell and SCell1 by sending message #a on the first downlink carrier of PCell; at the same time, by sending message #b on the first downlink carrier of PCell, the uplink scheduling requirement of the first uplink carrier of SCell1 can be effectively realized, thereby reducing the overhead cost of control signaling and realizing diversified scheduling requirements and the effectiveness of the communication system.

[0259] As an example and not a limitation, the above embodiments demonstrate how to schedule uplink data on SCell1 when PCell and SCell1 support joint scheduling. This technical solution is a further optimization strategy for joint scheduling scenarios, meeting diverse scheduling needs. Optionally, in this embodiment, the downlink joint scheduling and SCell1 uplink scheduling technical solutions can be decoupled, and the two operate independently. That is, based on PCell and SCell1 supporting downlink joint scheduling, the network device can determine the configuration information of the joint scheduling search space and send the configuration information to the terminal device. The terminal device can also determine the corresponding search space based on the configuration information, specifically corresponding to step S910 above. For simplicity, it will not be elaborated here. It should be noted that in the above possible implementations, the terminal device can listen on PCell at least one of the PDCCHs corresponding to PCell self-scheduling, PCell cross-carrier scheduling, and downlink joint scheduling. Figure 10 This diagram illustrates an example of a terminal device determining the search space of the PCell, such as... Figure 10 As shown, the method 1000 includes:

[0260] S1010, the network device determines configuration information #a and / or configuration information #b.

[0261] The configuration information #a indicates the search space #a, which represents the search space for PCell self-scheduled PDSCH and / or PUSCH, and is used to carry PCell self-scheduled message #e; the configuration information #b indicates the search space #b, which represents the search space for PCell and SCell1 jointly scheduled PDSCH, and is used to carry message #a.

[0262] It should be noted that if configuration information #a and configuration information #b are the same, the search space for PCell self-scheduling and downlink joint scheduling can be shared; if configuration information #a and configuration information #b are different, the search spaces for PCell self-scheduling and downlink joint scheduling exist simultaneously and are independent of each other. The related signaling configuration is similar to step S610 above, and for simplicity, it will not be repeated here.

[0263] S1020, the network device sends configuration information #a and / or configuration information #b to the terminal device; correspondingly, the terminal device receives configuration information #a and / or configuration information #b from the network device.

[0264] S1030, the terminal device determines the search space #a and / or search space #b based on the received configuration information #a and / or configuration information #b.

[0265] It should be noted that if configuration information #a and configuration information #b are the same, the search space for PCell self-scheduling and downlink joint scheduling can be shared; if configuration information #a and configuration information #b are different, the search spaces for PCell self-scheduling and downlink joint scheduling are independent. The determination of the search space is similar to step S630 above, and for simplicity, it will not be repeated here.

[0266] It should be understood that, in the embodiments of this application, for the case of PCell cross-carrier scheduling SCell1, the scheduling information used for PCell self-scheduling and SCell1 cross-carrier scheduling is received and sent on SCell1, so the search space for self-scheduling and / or joint scheduling determined by the UE is also on SCell1.

[0267] S1040, Network device configuration information confirmed #c.

[0268] The configuration information #c is used to indicate the search space #c, which represents the search space of the PUSCH of the first uplink carrier of SCell1 across carrier scheduling of PCell, and is used to carry message #b.

[0269] In one possible implementation, if configuration information #b and configuration information #c are identical, meaning the search spaces for downlink joint scheduling and SCell1 uplink scheduling coexist and can be shared, then from a signaling configuration perspective, the two parameters nrofCandidates and searchSpaceId in configuration information #b are associated SCell1 configurations, while the other parameters are configurations corresponding to PCells. Therefore, configuration information #b can be used to indicate search spaces #b and #c.

[0270] Optionally, the network device determines configuration information #b, which is used to indicate the search space #b for downlink joint scheduling and to carry the joint scheduling message #a. It should be understood that this search space #b resides on the PCell. Additionally, the network device may, through an agreement with the terminal device or by signaling, specify that the search space #b can also be used for blind detection messages #b. That is, the network device does not need to determine configuration information #c; the search space for uplink scheduling on SCell1 is shared with the search space for downlink joint scheduling.

[0271] In another possible implementation, if configuration information #b and configuration information #c are different, meaning the search spaces for downlink joint scheduling and SCell1 uplink scheduling coexist and are independent of each other, then from a signaling configuration perspective, configuration information #b must include at least the configuration parameters associated with SCell1: nrofCandidates1 and searchSpaceId 1, while other parameters correspond to the configurations on the PCell. Configuration information #c must include at least the configuration parameters associated with SCell1: nrofCandidates2 and searchSpaceId 2. It should be understood that configuration information #b and configuration information #c are two independent search space configurations.

[0272] For example, network devices can also configure the same valid parameter nrofCandidates2 in configuration information #b and configuration information #c, meaning that downlink joint scheduling and uplink cross-carrier scheduling share the same nrofCandidates2. For the parameter searchSpaceId, the network device can configure it in one set of configuration information (e.g., configuration information #b), while the other set of configuration information #c can determine it through a predefined or notified offset value.

[0273] For example, a network device can jointly schedule PDSCH for PCell, configure the parameter searchSpaceId 1 in configuration information #b, and inform the terminal device of the offset value of the valid parameter searchSpaceId 2 in configuration information #c relative to the valid parameter searchSpaceId 1 in configuration information #b. Then, according to the formula searchSpaceId 2 = (searchSpaceId1 + offset)mode, the maximum number of search spaces is the valid parameter searchSpaceId 2 in configuration information #c.

[0274] S1050, the network device sends configuration information #c to the terminal device; correspondingly, the terminal device receives configuration information #c from the network device.

[0275] The configuration information #c includes at least the configuration parameters associated with SCell1.

[0276] S1060, the terminal device determines the search space #c based on the received configuration information #c.

[0277] In one possible implementation, if configuration information #b and configuration information #c are different, that is, the search spaces for downlink joint scheduling and SCell1 uplink scheduling exist simultaneously and are independent of each other, then the terminal device can determine the search space #b based on configuration information #b and the search space #c based on configuration information #c.

[0278] As an example and not a limitation, the above embodiments further determine the search space for uplink scheduling of SCell1 based on the determination of the downlink joint scheduling search space. Optionally, in the embodiments of this application, the technical solutions for determining the joint scheduling search space and determining the uplink scheduling search space can be decoupled, and the two operate independently. That is, based on the support for downlink joint scheduling by PCell and SCell1, the network device can determine the configuration information of the joint scheduling search space and send the configuration information to the terminal device. The terminal device can also determine the corresponding search space based on the configuration information, specifically corresponding to steps S1010 to S1030 above. For simplicity, further details are omitted here.

[0279] Based on the above technical solution, a joint scheduling method was designed to solve the problems in carrier aggregation scenarios, such as configuring and determining the search space for joint scheduling of a carrier when a carrier is configured with joint PDSCH scheduling, as well as the uplink scheduling requirements of the carrier. This effectively reduces the overhead cost of control signaling and solves the problems of diversified scheduling requirements and the effectiveness of the communication system.

[0280] Method 3:

[0281] Figure 11 This is another schematic diagram illustrating the resource scheduling method applicable to this application. The difference from Method 1 is that the PUSCH on the first uplink carrier of SCell1 is scheduled across uplink carriers by SCell2. In other words, no PDCCH is configured on SCell1; control information is transmitted via the PDCCH of SCell2, while the corresponding data information is transmitted via the PDSCH of SCell1. Thus, the terminal device receives control information on SCell2, enabling the scheduling of resources on SCell1. It should be noted that in this implementation, predefined rules can be used: PCell and SCell1 support joint scheduling of PDSCH, and SCell1 supports uplink cross-carrier scheduling of PUSCH. For example... Figure 11 As shown, the method 1100 includes:

[0282] S1110, the network device sends message #α to the terminal device on the first downlink carrier of PCell (i.e., an example of the first cell); correspondingly, the terminal device receives message #α from the network device on the first downlink carrier of PCell.

[0283] The message #α indicates the scheduling information of the PDSCH, which corresponds to the first downlink carrier of PCell1 and the second downlink carrier of SCell1.

[0284] For example, the PDSCH may include a first PDSCH and a second PDSCH, wherein the first PDSCH corresponds to PCell and the second PDSCH corresponds to SCell1; or, the PDSCH may include a third PDSCH, which corresponds to both PCell and SCell1. That is, the terminal device can schedule downlink data transmitted on the first downlink carrier of PCell and the second downlink carrier of SCell1 by receiving message #α from the network device.

[0285] For example, by receiving message #α sent by the network device, the terminal device can schedule PDSCH#1 of the first downlink carrier of PCell1 and PDSCH#2 of the second downlink carrier of SCell1.

[0286] S1120, the network device sends message #β to the terminal device on the third downlink carrier of SCell2 (i.e., an example of the third cell); correspondingly, the terminal device receives message #β from the network device on the third downlink carrier of SCell2.

[0287] The message #β is used to indicate the scheduling information of the PUSCH of the first uplink carrier of SCell1 (i.e., an example of the second cell). That is, the terminal device can obtain the scheduling information of the PUSCH#1 of the first uplink carrier of SCell1 by receiving the message #β sent by the network device.

[0288] S1130, according to the received message #β, the terminal device sends PUSCH#1 to the network device on the first uplink carrier of SCell1; correspondingly, the network device receives PUSCH#1 from the network device on the first uplink carrier of SCell1.

[0289] In one possible implementation, the network device may also send DCI#γ to the terminal device on the third downlink carrier of SCell2, for scheduling information of PUSCH#2 of the third uplink carrier of SCell2 and / or scheduling information of PDSCH#3 of the third downlink carrier of SCell2, etc.

[0290] It should be understood that network devices can also send downlink scheduling information on SCell2 to instruct terminal devices to schedule the PDSCH of the second downlink carrier of SCell1 across downlink carriers. However, considering that in this case, SCell1 supports both joint downlink scheduling of PDSCH with PCell and cross-carrier scheduling of PDSCH by SCell2, the PDSCH on SCell1 may be simultaneously scheduled by both PCell and SCell2 downlink. Therefore, it can be predefined that if SCell1 is configured for joint downlink scheduling with PCell and simultaneously scheduled across carriers by SCell2, then SCell2 is allowed to schedule the PUSCH of SCell1 across uplink carriers, and the downlink data of SCell1 can be scheduled through PCell cross-carrier scheduling and / or joint downlink scheduling. The purpose of this is to avoid multiple cells (e.g., PCell and SCell2) simultaneously scheduling the PDSCH of a single cell (e.g., SCell1). In other words, it can prevent a cell (e.g., SCell1) from being simultaneously scheduled for uplink / downlink data by two cells (e.g., PCell and SCell2), thereby effectively reducing problems such as garbled characters, resource conflicts, and channel congestion. In addition, terminal devices can report this as a capability to network devices. When network devices determine configuration information for the active cell where the terminal device is located, they can choose whether to configure and enable this function at the same time. This possible implementation method can, to some extent, enable flexible application of resource scheduling.

[0291] In summary, under this possible implementation, the PUSCH of the first uplink carrier of SCell1 can be implemented through uplink cross-carrier scheduling of SCell2. Specifically, the network device sends message #β on the third downlink carrier of SCell2 to instruct the terminal device to schedule the PUSCH#1 of the first uplink carrier of SCell1 across carriers. The PDSCH of the second downlink carrier of SCell1 can be implemented through downlink joint scheduling or PCell downlink cross-carrier scheduling. Specifically, the network device sends message #Σ on the first downlink carrier of PCell to instruct the terminal device to schedule the PDSCH#4 of the second downlink carrier of SCell1 across carriers; or sends message #α on the first downlink carrier of PCell to instruct the terminal device to jointly schedule the PDSCH#1 of the second downlink carrier of SCell1. Clearly, the cell for cross-carrier scheduling of uplink data in SCell1 is SCell2, while the cell for downlink joint scheduling or cross-carrier scheduling of downlink data in SCell1 is PCell; the two are different.

[0292] According to the scheme provided in the above embodiments, in the scenario of carrier aggregation, the terminal device can achieve joint scheduling of PDSCH of PCell and SCell1 by sending message #α on the first downlink carrier of PCell; at the same time, by sending message #β on the third downlink carrier of SCell2, the uplink scheduling requirement of the first uplink carrier of SCell1 is effectively realized, thereby reducing the overhead cost of control signaling and realizing diversified scheduling requirements and the effectiveness of the communication system.

[0293] As an example and not a limitation, the above embodiment describes how to schedule uplink data for SCell1 when PCell and SCell1 support joint scheduling. This technical solution is a further optimization strategy for joint scheduling scenarios to meet diverse scheduling needs. Optionally, in this embodiment, the downlink joint scheduling and SCell1 uplink scheduling technical solutions can be decoupled, and the two can operate independently. That is, network devices and terminal devices can receive and send downlink data based on PCell and SCell1 supporting downlink joint scheduling, specifically corresponding to step S1110 above. For simplicity, further details are omitted here.

[0294] It should be noted that, in the above possible implementations, the terminal device can listen to at least one of the PDCCHs corresponding to PCell self-scheduling, PCell cross-carrier scheduling and downlink joint scheduling on PCell, and can listen to at least one of the PDCCHs corresponding to SCell2 self-scheduling and SCell2 cross-carrier scheduling on SCell2. Figure 12 This diagram illustrates an example of a terminal device determining the search space for PCell and SCell2, as shown below. Figure 12As shown, the method 1200 includes:

[0295] S1210, the network device determines configuration information #aa and / or configuration information #bb.

[0296] Among them, the configuration information #aa is used to indicate the search space #aa, which represents the search space for PCell self-scheduled PDSCH and / or PUSCH, and is used to carry PCell self-scheduled messages #&; the configuration information #bb is used to indicate the search space #bb, which represents the search space for PCell and SCell1 jointly scheduled PDSCH, and is used to carry messages #α.

[0297] It should be noted that if configuration information #aa and configuration information #bb are the same, the search space for PCell self-scheduling and joint scheduling can be shared; if configuration information #aa and configuration information #bb are different, the search spaces for PCell self-scheduling and downlink joint scheduling exist simultaneously and are independent of each other. The related signaling configuration is similar to step S610 above, and for simplicity, it will not be repeated here.

[0298] S1220, the network device sends configuration information #aa and / or configuration information #bb to the terminal device; correspondingly, the terminal device receives configuration information #aa and / or configuration information #bb from the network device.

[0299] S1230, the terminal device determines the search space #aa and / or the search space #bb based on the received configuration information #aa and / or configuration information #bb.

[0300] It should be noted that if configuration information #aa and configuration information #bb are the same, the search space for PCell self-scheduling and joint scheduling can be shared; if configuration information #aa and configuration information #bb are different, the search spaces for PCell self-scheduling and joint scheduling are independent. The determination of the search space is similar to step S630 above, and for simplicity, it will not be repeated here.

[0301] S1240, Network device configuration information #cc.

[0302] The configuration information #cc is used to indicate the search space #cc, which represents the search space of the PUSCH of the first uplink carrier of SCell1 scheduled by SCell2 across carriers, and is used to carry the message #bb.

[0303] In one possible implementation, if configuration information #bb and configuration information #cc are different, it means that the search spaces for downlink joint scheduling and SCell1 uplink scheduling exist simultaneously and are independent of each other. Configuration information #bb and configuration information #cc are two independent search space configurations, and the related signaling configurations are similar to the above step S1040, which will not be repeated here for simplicity.

[0304] S1250, the network device sends configuration information #cc to the terminal device; correspondingly, the terminal device receives configuration information #cc from the network device.

[0305] The configuration information #cc includes at least the configuration parameters associated with SCell1: nrofCandidates and searchSpaceId.

[0306] S1260, the terminal device determines the search space based on the received configuration information #cc.

[0307] In one possible implementation, if configuration information #bb and configuration information #cc are different, it means that the search spaces for downlink joint scheduling and SCell1 uplink scheduling exist simultaneously and are independent of each other. The determination of the search space is similar to step S1060 above, and for simplicity, it will not be repeated here.

[0308] As an example and not a limitation, the above embodiments further determine the search space for uplink scheduling of SCell1 based on the determination of the downlink joint scheduling search space. Optionally, in the embodiments of this application, the technical solutions for determining the joint scheduling search space and determining the uplink scheduling search space can be decoupled, and the two operate independently. That is, based on the support of downlink joint scheduling by PCell and SCell1, the network device can determine the configuration information of the joint scheduling search space and send the configuration information to the terminal device. The terminal device can also determine the corresponding search space according to the configuration information, specifically corresponding to the above steps S1210 to S1230. For simplicity, it will not be elaborated here. According to the above technical solution, by designing a joint scheduling method, the problem of configuring and determining the search space for joint scheduling of a carrier configured with joint PDSCH scheduling in a carrier aggregation scenario, as well as the uplink scheduling requirements of the carrier, is solved. This effectively reduces the overhead cost of control signaling and solves the problems of diversified scheduling requirements and the effectiveness of the communication system.

[0309] The above possible embodiments illustrate how to schedule the PUSCH of the first uplink carrier of SCell1 in the uplink, based on PCell scheduling of SCell1, using three possible implementation methods. Similarly, the technical solution of this application is also applicable to the example of SCell1 (i.e., an example of the first cell) scheduling PCell (i.e., an example of the second cell). That is, when PCell and SCell1 support downlink joint scheduling, the network device can send a first message on the first downlink carrier of SCell1, which indicates the scheduling information of the Physical Downlink Shared Channel (PDSCH). Simultaneously, the network device sends a second message on the second downlink carrier of PCell, or on the first downlink carrier of SCell1, or on the third downlink carrier of SCell2, for uplink scheduling of the PUSCH of the first uplink carrier of PCell. The possible implementation steps are similar to the PCell scheduling of SCell1 scheme in the above embodiments, and for simplicity, will not be repeated here.

[0310] It should be understood that for network devices to implement uplink scheduling of the PUSCH of the first uplink carrier of PCell by sending the second message on the second downlink carrier of PCell, or on the first downlink carrier of SCell1, or on the third downlink carrier of SCell2, the DCI size needs to be aligned, and the DCI budget issue needs to be considered.

[0311] In particular, as the primary cell, PCell uses its common search space to transmit cell-level common information, such as control information related to Paging, RAR, and BCCH, regardless of whether cross-carrier scheduling is configured. This information is the same for all terminal devices and needs to be monitored.

[0312] It should be noted that the above embodiments are based on the scenario where PCell and SCell1 are configured for downlink joint scheduling, taking PCell scheduling SCell1 and SCell1 scheduling PCell as examples, to illustrate how network devices can effectively perform uplink scheduling on SCell1 and PCell, and to propose a scheme for configuring and determining the search space for joint scheduling. However, the technical solution of this application is not limited to this. The technical solution of this application is also applicable to the scenario where SCell1 and SCell2 are configured for downlink joint scheduling, and to the scenario where PCell, SCell1, and SCell2 are configured for downlink joint scheduling. That is, the technical solution of this application is also applicable to the scenario where Cell1 and Cell2 are jointly scheduled, and the DCI used for joint scheduling is transmitted on Cell3. The possible implementation methods for uplink data scheduling and the configuration and determination of the joint scheduling search space in this cell are basically similar to the above technical solution of this application, and will not be described in detail here for the sake of brevity.

[0313] For example, when SCell1 and SCell2 are configured for downlink joint scheduling, taking SCell1 scheduling SCell2 as an example, the network device sends scheduling information on SCell1. This scheduling information is used for downlink joint scheduling of the Physical Downlink Shared Channel (PDSCH) on SCell1 and SCell2. At this time, the network device can achieve uplink scheduling of the PUSCH of SCell2 through SCell2 self-scheduling, uplink cross-carrier scheduling of SCell1, or uplink cross-carrier scheduling of other SCell3. Possible implementations are similar to the above schemes and will not be elaborated here.

[0314] For example, when PCell, SCell1, and SCell2 are configured for joint scheduling, taking the simultaneous scheduling of SCell1 and SCell2 by PCell as an example, the network device sends scheduling information in PCell. This scheduling information is used for downlink joint scheduling of the Physical Downlink Shared Channel (PDSCH) of PCell, SCell1, and SCell2. In this case, the network device can achieve uplink scheduling of the PUSCH of SCell1 / SCell2 through SCell1 / SCell2 self-scheduling, PCell uplink cross-carrier scheduling, or other SCell3 uplink cross-carrier scheduling. Possible implementation methods are similar to the above technical solutions and will not be elaborated here.

[0315] It should be noted that the above embodiments take the activation of cells PCell, SCell1 and SCell2 as examples only to more clearly illustrate the technical solution of this application. In order to achieve the technical solution of this application, the number of activated cells only needs to be greater than or equal to 2. The number of activated cells should not constitute any limitation on this application.

[0316] It should also be noted that in the possible implementations described above in this application, downlink joint scheduling is supported between all cells. Network devices implement uplink data scheduling based on downlink joint scheduling between cells, effectively meeting diverse scheduling needs. It should be understood that the embodiments of this application are also applicable to uplink joint scheduling, where network devices implement downlink data scheduling based on uplink joint scheduling between cells. For example, if cell 1 and cell 2 support uplink joint scheduling, and the DCI used for joint scheduling can be sent in cell 1, the network device can perform uplink scheduling on the PUSCH of cell 2 based on this scenario. The specific implementation is similar to the embodiments described above, and for simplicity, it will not be repeated here. Furthermore, the determination of the search space for uplink joint scheduling can be similar to the determination of the search space for downlink joint scheduling, and will not be repeated here either.

[0317] The following describes a resource determination method applicable to embodiments of this application, related to cell activation. To better understand this technical solution, a brief introduction to the cell activation process is given first.

[0318] The base station can configure multiple secondary cells for the UE via signaling 1. Initially, the configured cells are deactivated, and the base station and UE cannot transmit data on deactivated cells. The base station needs to instruct the UE to activate the configured cells via signaling 2. After the cells are activated, the base station and UE can transmit data on the cells. In the above embodiments, the cells configured for joint scheduling (e.g., PCell, SCell1, and SCell2) are all activated cells. It should be noted that signaling 1 can also be used to instruct cell activation, meaning the base station activates the cell while configuring the cell information.

[0319] The cell activation process may include: the base station sending signaling 2 to the UE; correspondingly, the UE receiving signaling 2 from the base station, and after processing signaling 2, the UE can send HARQ information back to the base station, i.e., whether the UE correctly received signaling 2 sent by the base station. The base station sends signal 1 to the UE, which is used to achieve synchronization between the base station and the UE; correspondingly, the UE receiving signal 1 from the base station; after processing signal 1, the UE obtains the information required for cell activation based on measurement signal 1, including time and frequency synchronization information and reference signal power; the base station sends signal 2 to the UE; correspondingly, after receiving signal 2 from the base station, the UE sends a valid channel measurement report back to the base station; after receiving the valid channel measurement report sent by the UE, the base station considers the corresponding cell to be in an active state.

[0320] For example, signaling 1 can be Radio Resource Control (RRC) signaling, signaling 2 can be Media Access Control (MAC) Management Unit (MAC) CE signaling, signal 1 can be a Single Side Band (SSB) signal, and signal 2 can be a Channel State Information-Reference Signal (CSI-RS). During the cell activation process, the UE can use the SSB to obtain the information needed for cell activation. However, due to the long transmission, reception, and processing cycles of the SSB, the activation time for secondary cells is also long. Therefore, to reduce the activation time of secondary cells, a temporary reference signal can be introduced during the secondary cell activation process.

[0321] For example, a temporary reference signal may include CSI-RS or a tracking reference signal (TRS). A UE can use a TRS as a temporary reference signal for cell activation. The TRS can be periodic or aperiodic. For instance, the temporary reference signal can be limited to a periodic TRS, aperiodic TRS, or a combination of both. By indicating an aperiodic TRS, the base station can enable the UE to receive the TRS quickly, thus obtaining the necessary information for cell activation more rapidly. If the temporary reference signal is periodic, configuring a short-periodic TRS can also enable the UE to receive the TRS more quickly and complete cell activation. Similar to TRS, CSI-RS signaling also includes periodic and aperiodic CSI-RS. The temporary reference signal can be limited to a periodic CSI-RS, aperiodic CSI-RS, or a combination of both. Using CSI-RS instead of SSB has the same technical effect as using TRS. Compared to using a long-term SSB to complete cell activation, using a temporary reference signal can reduce cell activation delay.

[0322] Method 1:

[0323] The base station can configure a set of temporary reference signals for the UE via signaling 3. This set of temporary reference signals can be configured at the cell granularity or at the BWP granularity on the cell. The base station can send signaling 4 and signaling 5 for cell activation to the UE, where signaling 4 indicates at least one temporary reference signal in the configured set of reference signals. Signaling 4 and signaling 5 can be understood as the same signaling. This method can reduce the time for the UE to receive and process signaling, thereby further reducing the cell activation time. Optionally, the aforementioned set of temporary reference signals can be preset or predefined, that is, it can be negotiated and specified in advance between the base station and the UE.

[0324] For example, signaling 3 is RRC signaling, and signaling 4 and signaling 5 are both MAC CE signaling, and are the same MAC CE signaling. The base station activates the secondary cell through MAC CE signaling, and at the same time implicitly indicates the temporary reference signal on the cell to be activated.

[0325] It should be understood that the MAC CE signaling includes an index corresponding to the cell that needs to be activated. Firstly, an implicit predefined indication rule is established: after the UE receives the MAC CE cell activation signaling, this signaling implicitly indicates the temporary reference signal used for cell activation on that cell. For example, this reference signal can be predefined according to the following rules: all temporary reference signals in the set of temporary reference signals configured in signaling 3; or one or more temporary reference signals in the set of reference signals determined by the UE according to the predefined rules for temporary reference signals; or one or more temporary reference signals selected by the UE from the configured set of reference signals. The aforementioned predefined rules for temporary reference signals may include: the indicated reference signal is the temporary reference signal corresponding to the maximum or minimum resource index or other index determined by other methods in the temporary reference signal set on the cell to be activated; or, the indicated reference signal is the temporary reference signal corresponding to the maximum or minimum resource index or other index determined by other methods in the temporary reference signal set within a specific BWP on the cell to be activated, wherein the number of such specific BWPs is greater than or equal to 1, and the specific BWP can be the initial activated uplink or downlink BWP in the cell (the initial activated BWP is the BWP that is initially activated after a cell has been activated), and can be the N uplink / downlink BWPs with the lowest or highest index, where N is greater than or equal to 1.

[0326] Optionally, the temporary reference signal can be a TRS, which includes periodic TRS and aperiodic TRS. The MAC CE signaling implicitly indicates the aperiodic TRS corresponding to a predefined rule index within the aperiodic TRS set. Alternatively, the UE can also receive periodic TRS according to the periodic TRS configuration. That is, after receiving MAC CE signaling for cell activation, the UE can begin receiving the corresponding reference signal according to the configuration of aperiodic and periodic TRS. Alternatively, the temporary reference signal can be an aperiodic TRS, and the MAC CE signaling implicitly indicates the aperiodic TRS corresponding to a predefined rule index within the aperiodic TRS set. In other words, after receiving MAC CE signaling for cell activation, the UE can begin receiving the corresponding reference signal according to the aperiodic TRS configuration. Accordingly, the UE receives MAC CE signaling from the base station and simultaneously determines the temporary reference signal to be received according to predefined rules. Alternatively, the MAC CE may implicitly indicate a TRS corresponding to a predefined rule index in the TRS set. The TRS set includes periodic TRS and aperiodic TRS. That is, after the UE receives the MAC CE signaling for cell activation, if the implicitly indicated TRS is a periodic TRS, then the UE will receive the corresponding reference signal according to the periodic TRS configuration. If the implicitly indicated TRS is an aperiodic TRS, then the UE will receive the aperiodic TRS according to the aperiodic TRS configuration, or receive the corresponding TRS according to both the aperiodic TRS and the periodic TRS.

[0327] For example, to enable a base station to select whether to simultaneously trigger a temporary reference signal when sending MAC CE signaling to activate a cell, the base station can add an identifier indicating whether a temporary reference signal is triggered to the existing MAC CE signaling. This identifier can correspond to all cells; or multiple identifiers indicating whether a temporary reference signal is triggered can be added to the MAC CE signaling, in which case each cell can correspond to one identifier. For instance, the MAC CE signaling can indicate that cells 1, 3, and 5 are activated, while also carrying an identifier indicating whether cells 1, 3, and 5 simultaneously trigger the aforementioned predefined temporary reference signal; or cell 1 can correspond to an identifier for triggering a temporary reference signal, cell 3 to an identifier for not triggering a temporary reference signal, and cell 5 to an identifier for triggering a temporary reference signal.

[0328] For example, when configuring cell information via RRC signaling, the base station can add an identifier to the RRC signaling indicating whether a temporary reference signal (TRS) is simultaneously triggered or determined. After receiving the cell activation command, the UE determines whether to receive the predefined TRS based on whether the cell configuration information includes this identifier. For instance, if the base station adds and configures cell #a via RRC signaling, and the identifier for whether to simultaneously trigger a temporary reference signal is true or enabled, then upon receiving the MAC CE activation signaling, the UE simultaneously determines the TRS used for cell activation according to predefined rules. If the identifier for whether to simultaneously trigger a temporary reference signal is false or disabled, then upon receiving the MAC CE activation signaling, the UE does not determine the TRS used for cell activation according to predefined rules. For example, bits "1" and "0" can be used to represent whether the temporary reference signal trigger identifier is true or false. According to the predefined rule, when the flag used to trigger or determine the temporary reference signal in the RRC signaling received by the UE is 1, it means that the UE determines to receive the predefined temporary reference signal; otherwise, the UE determines not to receive the predefined temporary reference signal.

[0329] Optionally, the base station can also predefine rules with the UE: when the RRC signaling sent by the base station includes an identifier for triggering or determining a temporary reference signal, the UE determines to receive the predefined temporary reference signal based on the identifier; when the RRC signaling sent by the base station does not include an identifier for triggering or determining a temporary reference signal, the UE will not receive the identifier and thus determines not to receive the predefined temporary reference signal.

[0330] Alternatively, the base station can implement this through configuration with predefined rules: if there is no available set of temporary reference signals configured on the first active downlink BWP of a cell to be activated, then the UE will determine not to trigger the temporary reference signals simultaneously after receiving the cell activation signaling; if there is an available set of temporary reference signals on the BWP, then the UE will determine to trigger the temporary reference signals simultaneously after receiving the cell activation signal.

[0331] For example, a UE can report whether it supports the ability to simultaneously trigger cell activation and temporary reference signals. This capability can mean that all configured cells have the same capability, or that the capability differs for each cell. For instance, it might be supported on cell 1 but not on cell 2. The base station and the UE can determine whether cell activation signaling implicitly triggers temporary reference signals simultaneously based on the UE's capability. Furthermore, after the UE reports the above capability, the base station can configure whether the UE supports simultaneously triggering carrier activation and temporary reference signals on each cell based on the UE's capability. For UEs that support simultaneous triggering, the base station can configure a support or non-support flag in the cell configuration; for UEs that do not support simultaneous triggering, the base station can configure a non-support flag in the cell configuration.

[0332] Optionally, signaling 4 and signaling 5 can also be Radio Resource Control (RRC) or Downlink Control Information (DCI). By implementing method one to simultaneously indicate cell activation and temporary reference signals, signaling overhead can be reduced while lowering cell activation latency.

[0333] The above method one can simultaneously indicate cell activation and temporary reference signal, which can enhance the flexibility of temporary reference signal indication while reducing cell activation delay.

[0334] Method 2:

[0335] Taking signaling 3 as RRC signaling, signaling 4 as DCI, and signaling 5 as MAC CE as an example, the MAC CE is carried in the PDSCH, which is scheduled by the aforementioned DCI. That is, the base station schedules the PDSCH and triggers temporary reference signals for cell activation on the cell to be activated through a DCI. The PDSCH includes a MAC CE signaling, which indicates one or more cells to be activated. The DCI indicates the field of the temporary signal, which indicates the temporary reference signal for cell activation on the one or more cells. This field can be the CSI request field in the DCI.

[0336] It should be noted that in this possible implementation, the base station needs to send signaling 4 to the UE to indicate at least one temporary reference signal in the set of temporary reference signals used to activate the cell. The base station also needs to send signaling 5 to the UE, which is used for cell activation; optionally, the base station can send both signaling 4 and signaling 5 for cell activation to the UE simultaneously; correspondingly, the UE can receive both signaling 4 and signaling 5 simultaneously. The difference between Method 1 and Method 2 is that in Method 1, the base station can implicitly indicate the temporary reference signal for cell activation on the cell when sending signaling 5 for cell activation, i.e., the base station may not send signaling 4 to the UE. In Method 2, the base station needs to send both signaling 4 and signaling 5 to the UE. The interaction between the base station and the UE based on signaling 3 is similar to that in Method 1, and will not be elaborated here for simplicity.

[0337] For example, the temporary reference signal can be a TRS, which includes periodic TRS and aperiodic TRS. The MAC CE signaling implicitly indicates the aperiodic TRS corresponding to a predefined rule index within the aperiodic TRS set. Alternatively, the UE can also receive periodic TRS based on the periodic TRS configuration. That is, after receiving MAC CE signaling for cell activation, the UE can begin receiving the corresponding reference signal based on the configuration of both aperiodic and periodic TRS. Alternatively, the temporary reference signal can be an aperiodic TRS, and the MAC CE signaling implicitly indicates the aperiodic TRS corresponding to a predefined rule index within the aperiodic TRS set. In other words, after receiving MAC CE signaling for cell activation, the UE can begin receiving the corresponding reference signal based on the aperiodic TRS configuration. Accordingly, the UE receives MAC CE signaling from the base station and simultaneously determines the temporary reference signal to be received according to predefined rules.

[0338] Optionally, the base station can also configure multiple temporary reference signal sets for the UE via signaling 3. These temporary reference signal sets can be configured at the cell granularity or at the BWP granularity on the cell. Then, the signaling 4 sent by the base station to the UE can be used to indicate one or more temporary reference signal sets in the configured reference sets, or it can be used to indicate one or more temporary reference signals in at least one temporary reference signal set within the configured reference sets. The specific implementation has been explained above and will not be repeated here for simplicity.

[0339] According to the above embodiments, the base station can activate the cell by sending activation request information to the UE and combining it with predefined rules, thereby realizing diversified resource scheduling needs.

[0340] Method 3: The base station can configure a temporary reference signal set for the UE via signaling 3. This temporary reference signal set can be configured at the cell granularity or at the BWP granularity on the cell. The base station can send signaling 4 and signaling 5 for cell activation to the UE. Signaling 4 indicates at least one temporary reference signal in the temporary reference set configured in the secondary cell to be activated, and signaling 5 indicates the activation of at least one secondary cell. Signaling 4 and signaling 5 can be the same signaling, which can simultaneously trigger the activation of at least one secondary cell and the activation of the corresponding temporary reference signal on the secondary cell.

[0341] The aforementioned set of temporary reference signals includes at least one temporary reference signal. The temporary reference signal configuration may include at least one of the following: an index of the temporary reference signal, the number of temporary reference signal clusters in the time domain, the time-domain distance between different temporary reference signal clusters, frequency-domain resources of the temporary reference signal, the offset of the temporary reference signal, and an index of the bandwidth portion. Specifically, the temporary reference signal index is used to identify the configured temporary reference signal; the number of temporary reference signal clusters in the time domain is used to identify the number of temporary reference signal clusters, where a temporary reference signal cluster can be four CSI-RS resources contained in two time slots, or two CSI-RS resources contained in one time slot. For example, if two temporary reference signal clusters are configured, the base station transmits the temporary reference signal clusters twice in the time domain. The distance between different temporary reference signal clusters in the time domain represents the distance between adjacent temporary reference signal clusters when the number of temporary reference signal clusters in the time domain is greater than or equal to 2. This distance can be X time slots or Y milliseconds. The parameter set corresponding to the time slots is the same as that of the temporary reference signal, and the parameter set includes the subcarrier spacing and the cyclic prefix type. For different subcarrier spacings, the value range of X can be different. For example, for 15kHz, X is 2 to 10; for 30kHz, X is 4 to 20. The resources in the frequency domain of the temporary reference signal are used to identify the physical resource block index of the temporary reference signal in the frequency domain. The offset of the temporary reference signal is used to identify a time domain offset Z = (Z2 - Z1). The terminal device receives the trigger signaling of the temporary reference signal at time Z1 or sends the ACK / NACK feedback of the temporary reference signal at time Z1. The base station sends the triggered temporary reference signal at time Z2. Taking Z as an example, the unit of time-domain offset is time slots or milliseconds. If the unit of Z is time slots, then the minimum value of the time-domain offset Z is related to the subcarrier spacing u1 of the trigger signaling, or the subcarrier spacing u2 of the temporary reference signal, or the subcarrier spacing u3 corresponding to the PUCCH carrying the trigger signaling feedback information, or it is related to u1 and u2, or u1 and u3, or u2 and u3, or u1, u2 and u3. For example, the subcarrier spacing corresponding to the time slot is the same as u1, or the same as u2, or the same as u3, or the same as the maximum value of u1, u2 and u3, or the same as the minimum value of u1, u2 and u3; the index of the bandwidth part is the bandwidth part where the frequency domain of the temporary reference signal is located.

[0342] For example, signaling 3 is RRC signaling, and signaling 4 and signaling 5 are the same MAC CE signaling. The base station simultaneously activates the secondary cell and triggers a temporary reference signal on the secondary cell through a single MAC CE signaling. The MAC CE signaling contains at least one of the following fields:

[0343] Ci: Used to indicate the activation / deactivation status of secondary cell i. If the value of Ci is 1, then secondary cell i is activated; if the value of Ci is 0, then secondary cell i is deactivated. i is an integer greater than or equal to 1 and less than or equal to 31. The MAC CE signaling predefines 31 C fields, corresponding to C1 to C31.

[0344] Reserved bit R: Set to 0.

[0345] For each secondary cell i with a Ci value of 1 and in a deactivated state, it contains at least one of the following fields:

[0346] Bandwidth partial index j: downlink or uplink bandwidth partial index j on secondary cell i.

[0347] Temporary reference signal index k: Temporary reference signal index k configured in the bandwidth portion index j on secondary cell i. At this time, the temporary reference signal in each BWP is independently numbered, or the temporary reference signal index k on secondary cell i is independently numbered in secondary cell i, and the temporary reference signals in different BWPs are jointly numbered.

[0348] The number of clusters m in the time domain of temporary reference signals: This indicates the number of times the temporary reference signal corresponding to index k is transmitted in the time domain. m is an integer greater than or equal to 0.

[0349] Time-domain interval between two adjacent temporary reference signal clusters: If the number of clusters in the time domain of the temporary reference signal is greater than or equal to 2, it is used to indicate the time-domain interval between two adjacent clusters.

[0350] Transmission configuration indication status index: used to indicate the transmission configuration indication status of the temporary reference signal corresponding to the temporary reference signal index k, specifically the quasi-co-address source of the temporary reference signal.

[0351] Optionally, for secondary cells with a Ci value of 0, the same bit 0 is used to fill the fields related to the temporary reference signal in the MAC CE signaling.

[0352] Optionally, for a secondary cell with a Ci value of 1, if the current state of the secondary cell is active, then the MAC CE uses the same bit 0 to fill the field related to the temporary reference signal.

[0353] Optionally, after receiving MAC CE signaling, the UE will ignore the temporary reference signal configuration corresponding to the secondary cell with a Ci value of 0, and ignore the temporary reference signal configuration corresponding to the active secondary cell with a Ci value of 1.

[0354] Optionally, the bandwidth portion in the MAC CE signaling can be predefined as the first active bandwidth portion and does not need to be indicated in the MAC CE signaling.

[0355] Optionally, when the number of temporary reference signal clusters transmitted in the time domain is greater than or equal to 2, the time interval between two adjacent temporary reference signal clusters can be predefined, such as 2 milliseconds.

[0356] Optionally, the number of temporary reference signals transmitted in the time domain cluster is predefined as N, where N is an integer greater than or equal to 1, such as N=2.

[0357] Method 4: The base station can configure a temporary reference signal set for the UE via signaling 3. This temporary reference signal set can be configured at the cell granularity or at the BWP granularity on the cell. The base station can send signaling 4 and signaling 5 for cell activation to the UE. Signaling 4 indicates at least one temporary reference signal in the temporary reference signal set configured on the cell to be activated, and signaling 5 indicates the activation of at least one secondary cell. Signaling 4 and signaling 5 can be two signaling signals carried in the same PDSCH or transport block.

[0358] The aforementioned set of temporary reference signals includes at least one temporary reference signal. The temporary reference signal configuration may include at least one of the following: an index of the temporary reference signal, the number of temporary reference signal clusters in the time domain, the time-domain distance between different temporary reference signal clusters, frequency-domain resources of the temporary reference signal, the offset of the temporary reference signal, and an index of the bandwidth portion. Specifically, the temporary reference signal index is used to identify the configured temporary reference signal; the number of temporary reference signal clusters in the time domain is used to identify the number of temporary reference signal clusters, where a temporary reference signal cluster can be four CSI-RS resources contained in two time slots, or two CSI-RS resources contained in one time slot. For example, if two temporary reference signal clusters are configured, the base station transmits the temporary reference signal clusters twice in the time domain. The distance between different temporary reference signal clusters in the time domain represents the distance between adjacent temporary reference signal clusters when the number of temporary reference signal clusters in the time domain is greater than or equal to 2. This distance can be X time slots or Y milliseconds. The parameter set corresponding to the time slots is the same as that of the temporary reference signal, and the parameter set includes the subcarrier spacing and the cyclic prefix type. For different subcarrier spacings, the value range of X can be different. For example, for 15kHz, X is 2 to 10; for 30kHz, X is 4 to 20. The resources in the frequency domain of the temporary reference signal are used to identify the physical resource block index of the temporary reference signal in the frequency domain. The offset of the temporary reference signal is used to identify a time domain offset Z = (Z2 - Z1). The terminal device receives the trigger signaling of the temporary reference signal at time Z1 or sends the ACK / NACK feedback of the temporary reference signal at time Z1. The base station sends the triggered temporary reference signal at time Z2. Taking Z as an example, the unit of time-domain offset is time slots or milliseconds. If the unit of Z is time slots, then the minimum value of the time-domain offset Z is related to the subcarrier spacing u1 of the trigger signaling, or the subcarrier spacing u2 of the temporary reference signal, or the subcarrier spacing u3 corresponding to the PUCCH carrying the trigger signaling feedback information, or it is related to u1 and u2, or u1 and u3, or u2 and u3, or u1, u2 and u3. For example, the subcarrier spacing corresponding to the time slot is the same as u1, or the same as u2, or the same as u3, or the same as the maximum value of u1, u2 and u3, or the same as the minimum value of u1, u2 and u3; the index of the bandwidth part is the bandwidth part where the frequency domain of the temporary reference signal is located.

[0359] For example, signaling 3 is RRC signaling, and signaling 4 and signaling 5 are different MAC CE signaling within the same PDSCH or transport block. The base station triggers the activation of the secondary cell through the first MAC CE signaling and triggers a temporary reference signal on the secondary cell through the second MAC CE. The first MAC CE signaling contains at least one of the following fields: Cii: used to indicate the activation / deactivation status of secondary cell ii. If the value of Ci is 1, then secondary cell ii should be activated; if the value of Cii is 0, then secondary cell ii is deactivated. ii is an integer greater than or equal to 1 and less than or equal to 31. The MAC CE signaling predefines 31 C fields, corresponding to C1 to C31.

[0360] Reserved bit R: Set to 0;

[0361] The second MAC CE signaling contains at least one of the following fields:

[0362] Serving cell index f: Index f of the secondary cell to be activated;

[0363] For each secondary cell f, at least one of the following fields is included:

[0364] Bandwidth partial index jj: downlink or uplink bandwidth partial index jj on secondary cell f.

[0365] Temporary reference signal index kk: Temporary reference signal index kk configured in the bandwidth portion index jj on the secondary cell f. At this time, the temporary reference signal in each BWP is independently numbered, or the temporary reference signal index kk on the secondary cell f is independently numbered in the secondary cell, and the temporary reference signals in different BWPs are jointly numbered.

[0366] The number of clusters of temporary reference signals in the time domain, mm: This indicates the number of times the temporary reference signal corresponding to index kk is transmitted in the time domain. mm is an integer greater than or equal to 0.

[0367] Time-domain interval between two adjacent temporary reference signal clusters: If the number of clusters in the time domain of the temporary reference signal is greater than or equal to 2, it is used to indicate the time-domain interval between two adjacent clusters.

[0368] Transmission configuration indication status index: used to indicate the transmission configuration indication status of the temporary reference signal corresponding to the temporary reference signal index kk, specifically the quasi-co-address source of the temporary reference signal.

[0369] Optionally, the second MAC CE signaling includes at least one of the following fields:

[0370] For a secondary cell ii with a Cii value of 1 in the first MAC CE signaling and the secondary cell is in a deactivated state, it includes at least one of the following fields:

[0371] Bandwidth partial index jjj: The downlink or uplink bandwidth partial index jjj on the secondary cell ii.

[0372] Temporary reference signal index kkk: Temporary reference signal index kkk configured in the bandwidth portion index jjj on secondary cell ii. At this time, the temporary reference signal in each BWP is independently numbered, or the temporary reference signal index kkk on secondary cell ii. At this time, the temporary reference signal in the secondary cell is independently numbered, and the temporary reference signal in different BWPs is jointly numbered.

[0373] The number of clusters of temporary reference signals in the time domain mm: used to indicate the number of times the temporary reference signal corresponding to the index kkk is transmitted in the time domain, mm is an integer greater than or equal to 0;

[0374] Time-domain interval between two adjacent temporary reference signal clusters: If the number of clusters in the time domain of the temporary reference signal is greater than or equal to 2, it is used to indicate the time-domain interval between two adjacent clusters.

[0375] Transmission configuration indication status index: used to indicate the transmission configuration indication status of the temporary reference signal corresponding to the temporary reference signal index kkk, specifically the quasi-co-address source of the temporary reference signal.

[0376] Optionally, for secondary cells with a Cii value of 0, the same bit 0 is used to fill the fields related to the temporary reference signal in the MAC CE signaling.

[0377] Optionally, for a secondary cell with a Cii value of 1, if the current state of the secondary cell is active, then the MAC CE uses the same bit 0 to fill the field related to the temporary reference signal.

[0378] Optionally, after receiving MAC CE signaling, the UE will ignore the temporary reference signal configuration corresponding to the secondary cell with a Cii value of 0, and ignore the temporary reference signal configuration corresponding to the active secondary cell with a Cii value of 1.

[0379] Optionally, the bandwidth portion in the second MAC CE signaling can be predefined as the first active bandwidth portion and does not need to be indicated in the MAC CE signaling.

[0380] Optionally, when the number of temporary reference signal clusters transmitted in the time domain is greater than or equal to 2, the time interval between two adjacent temporary reference signal clusters can be predefined, such as 2 milliseconds. Optionally, the number of temporary reference signal clusters transmitted in the time domain is predefined as N, where N is an integer greater than or equal to 1, such as N=2.

[0381] It should be understood that the specific examples in the embodiments of this application are only for the purpose of helping those skilled in the art to better understand the embodiments of this application, and are not intended to limit the scope of the embodiments of this application.

[0382] It should also be understood that, in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The various embodiments described herein can be independent solutions or combinations based on internal logic, and all such solutions fall within the protection scope of this application.

[0383] It is understood that, in the above-described method embodiments, the methods and operations implemented by the terminal device can also be implemented by components (e.g., chips or circuits) that can be used in the terminal device, and the methods and operations implemented by the network device can also be implemented by components (e.g., chips or circuits) that can be used in the network device. The resource scheduling method applicable to the embodiments of this application has been described in detail above; the apparatus applicable to the embodiments of this application will be described below.

[0384] According to the aforementioned method, Figure 13 This is a schematic diagram of a communication device 10 applicable to embodiments of this application, such as a network device. Figure 13 As shown, the communication device 10 includes a transceiver unit 11 and a processing unit 12.

[0385] For example, the transceiver unit 11 is used to transmit a first message on a first downlink carrier of a first cell. The first message is used to indicate the scheduling information of the Physical Downlink Shared Channel (PDSCH). The PDSCH corresponds to the first downlink carrier of the first cell and the second downlink carrier of the second cell.

[0386] Optionally, the transceiver unit 11 is also used to send a second message, which is used to indicate the scheduling information of the Physical Uplink Shared Channel (PUSCH) of the first uplink carrier of the second cell.

[0387] Optionally, the transceiver unit 11 is also configured to receive PUSCH on the first uplink carrier of the second cell according to the second message.

[0388] It should be understood that the communication device 10 may correspond to the network device in the resource scheduling method 500 / 900 / 1100 according to the embodiments of this application, and the communication device 10 may include functions for performing... Figure 5 / Figure 9 / Figure 11 The network device 10 executes the method of resource scheduling 500 / 900 / 1100 as a module (or unit). Furthermore, each module (or unit) in the communication device 10 and the other operations and / or functions described above are respectively for implementing... Figure 5 / Figure 9 / Figure 11 The corresponding processes for resource scheduling methods 500 / 900 / 1100.

[0389] Specifically, the transceiver unit 11 is used to execute S510, S520 and S530 / S910, S920 and S930 / S1010, S1020 and S1030 in method 500 / 900 / 1100. The process of each module (or unit) executing the above-mentioned corresponding steps has been described in detail in method 500 / 900 / 1000, and will not be repeated here for the sake of brevity.

[0390] It should also be understood that the communication device 10 may correspond to the network device in the method 600 / 1000 / 1200 for determining the search space according to embodiments of this application, and the communication device 10 may include tools for performing... Figure 6 / Figure 10 / Figure 12 The network device executing the method 600 / 1000 / 1200 for determining the search space is a module (or unit). Furthermore, each module (or unit) in the communication device 10 and the other operations and / or functions described above are respectively for implementing... Figure 6 / Figure 10 / Figure 12 The corresponding procedures for determining the search space using methods 600 / 1000 / 1200.

[0391] Specifically, the transceiver unit 11 is used to execute S620 / 1020 / S1220 in method 600 / 1000 / 1200, and the processing unit 12 is used to execute S610 / S1010 / S1210 in method 600 / 1000 / 1200. The process of each module (or unit) executing the above-mentioned corresponding steps has been described in detail in method 600 / 1000 / 1200, and will not be repeated here for the sake of brevity.

[0392] It should be understood that Figure 13 The structure of the example communication device 10 is merely one possible configuration and should not be construed as limiting the embodiments of this application. This application does not exclude the possibility of other configurations of network devices in the future.

[0393] It should be understood that the communication device 10 according to the embodiments of this application can correspond to the network device for resource scheduling and search space determination in the foregoing method embodiments, and the above and other management operations and / or functions of each module in the communication device 10 are respectively for implementing the corresponding steps of the foregoing methods, and thus can also achieve the beneficial effects in the foregoing method embodiments.

[0394] It should also be understood that the processing module (or unit) in the embodiments of this application can be implemented by a processor, and the transceiver module (or unit) can be implemented by a transceiver.

[0395] According to the aforementioned method, Figure 14 This is a schematic diagram of a communication device 20 applicable to embodiments of this application, such as a terminal device. Figure 14 As shown, the communication device 20 includes a transceiver unit 21 and a processing unit 22.

[0396] For example, the transceiver unit 21 is used to receive a first message on a first downlink carrier of a first cell. The first message is used to indicate the scheduling information of the Physical Downlink Shared Channel (PDSCH). The PDSCH corresponds to the first downlink carrier of the first cell and the second downlink carrier of the second cell.

[0397] Optionally, the transceiver unit 21 is also configured to receive a second message, which indicates the scheduling information of the Physical Uplink Shared Channel (PUSCH) of the first uplink carrier of the second cell.

[0398] Optionally, the transceiver unit 21 is also configured to transmit PUSCH on the first uplink carrier of the second cell according to the second message.

[0399] It should be understood that the communication device 20 may correspond to the terminal device in the resource scheduling method 500 / 900 / 1100 according to the embodiments of this application, and the communication device 20 may include tools for performing... Figure 5 / Figure 9 / Figure 11 The terminal device executing the resource scheduling method 500 / 900 / 1100 is a module (or unit) of the method. Furthermore, each module (or unit) in the communication device 20 and the aforementioned other operations and / or functions are respectively for implementing... Figure 5 / Figure 9 / Figure 11 The corresponding processes for resource scheduling methods 500 / 900 / 1100.

[0400] Specifically, the transceiver unit 21 is used to execute S510, S520 and S530 / S910, S920 and S930 / S1110, S1120 and S1130 in method 500 / 900 / 1100. The process of each module (or unit) executing the above-mentioned corresponding steps has been described in detail in method 500 / 900 / 1100, and will not be repeated here for the sake of brevity.

[0401] It should be understood that the communication device 20 may also correspond to the terminal device in the method 600 / 1000 / 1200 for determining the search space according to the embodiments of this application, and the communication device 20 may include tools for performing... Figure 6 / Figure 10 / Figure 12The terminal device executes the method of determining the search space using methods 600 / 1000 / 1200, which is a module (or unit). Furthermore, each module (or unit) in the communication device 20 and the other operations and / or functions described above are respectively for implementing... Figure 6 / Figure 10 / Figure 12 The corresponding procedures for determining the search space using methods 600 / 1000 / 1200.

[0402] Specifically, the transceiver module 21 is used to execute S620 / S1020 / S1220 in method 600 / 1000 / 1200, and the processing unit 22 is used to execute S630 / S1030 / S1230 in method 600 / 1000 / 1200. The process of each module (or unit) executing the above-mentioned corresponding steps has been described in detail in method 600 / 1000 / 1200, and will not be repeated here for the sake of brevity.

[0403] It should be understood that Figure 14 The structure of the example communication device 20 is merely one possible configuration and should not be construed as limiting the embodiments of this application. This application does not exclude the possibility of other configurations of terminal devices that may appear in the future.

[0404] It should be understood that the communication device 20 according to the embodiments of this application can correspond to the terminal device for resource scheduling and search space determination in the foregoing method embodiments, and the above and other management operations and / or functions of each module in the communication device 20 are respectively for implementing the corresponding steps of the foregoing methods, and thus can also achieve the beneficial effects in the foregoing method embodiments.

[0405] It should also be understood that the processing module (or unit) in the embodiments of this application can be implemented by a processor, and the transceiver module (or unit) can be implemented by a transceiver.

[0406] According to the aforementioned method, Figure 15 This is a schematic diagram of a network device 30 applicable to an embodiment of this application. For example... Figure 15 As shown, the network device 30 includes a processor 31, a transceiver 32, and a memory 33.

[0407] It should be understood that the processor 31, transceiver 32, and memory 33 communicate with each other through internal interconnection paths to transmit control and / or data signals. In one possible design, the processor 31, transceiver 32, and memory 33 can be implemented using a chip. The memory 33 can store program code, and the processor 31 calls the program code stored in the memory 33 to implement the corresponding functions of the network device.

[0408] For example, the processor 31 is used to determine first configuration information of a first cell, which is used to indicate a first search space; and to determine first configuration information of a second cell, which is used to indicate the first search space.

[0409] For example, the transceiver 32 is configured to transmit a first message on a first downlink carrier of a first cell, the first message indicating scheduling information of a physical downlink shared channel (PDSCH), the PDSCH corresponding to the first downlink carrier of the first cell and the second downlink carrier of the second cell; transmit a second message indicating scheduling information of a physical uplink shared channel (PUSCH) on a first uplink carrier of the second cell; and receive the PUSCH on the first uplink carrier of the second cell according to the second message.

[0410] It is understood that, although not shown, network device 30 may also include other devices, such as input devices, output devices, batteries, etc.

[0411] Optionally, in some embodiments, memory 33 may store some or all of the instructions for executing the methods performed by the network device in the aforementioned methods. Processor 31 may execute the instructions stored in memory 33 in conjunction with other hardware (e.g., transceiver 32) to complete the steps performed by the network device in the aforementioned methods. For specific working processes and beneficial effects, please refer to the description in the foregoing method embodiments.

[0412] According to the aforementioned method, Figure 16 This is a schematic diagram of a terminal device 40 applicable to an embodiment of this application. For example... Figure 16 As shown, the terminal device 40 includes a processor 41, a transceiver 42, and a memory 43.

[0413] It should be understood that the processor 41, transceiver 42, and memory 43 communicate with each other through internal interconnection paths to transmit control and / or data signals. In one possible design, the processor 41, transceiver 42, and memory 43 can be implemented using a chip. The memory 43 can store program code, and the processor 41 calls the program code stored in the memory 43 to implement the corresponding functions of the terminal device.

[0414] For example, the processor 41 is used to detect a third message in a first search space; and to detect a first message in a second search space.

[0415] For example, the transceiver 42 is configured to receive a first message on a first downlink carrier of a first cell, the first message indicating scheduling information of a physical downlink shared channel (PDSCH), the PDSCH corresponding to the first downlink carrier of the first cell and the second downlink carrier of the second cell; receive a second message indicating scheduling information of a physical uplink shared channel (PUSCH) on a first uplink carrier of the second cell; and transmit a PUSCH on the first uplink carrier of the second cell according to the second message.

[0416] It is understood that, although not shown, terminal device 40 may also include other devices, such as input devices, output devices, batteries, etc.

[0417] Optionally, in some embodiments, the memory 43 may store some or all of the instructions for executing the methods performed by the terminal device in the aforementioned methods. The processor 41 may execute the instructions stored in the memory 43 in conjunction with other hardware (e.g., transceiver 42) to complete the steps performed by the terminal device in the aforementioned methods. For specific working processes and beneficial effects, please refer to the description in the foregoing method embodiments.

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

[0419] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0420] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0421] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0422] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0423] It should also be understood that the terms "first," "second," and "third," etc., mentioned in this document are merely for the purpose of clearly describing the technical solution of this application and should not constitute any limitation on this application.

[0424] As used in this specification, the terms "component," "module," "system," etc., are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process and / or an execution thread, and components may be located on a single computer and / or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. Components can communicate via local and / or remote processes, for example, through signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0425] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0426] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0427] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0428] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0429] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0430] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0431] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: Send a first capability, which indicates whether simultaneous triggering of cell activation and temporary reference signal is supported; Receive Radio Resource Control (RRC) signaling, the RRC signaling being used to configure a set of temporary reference signals at the cell granularity, wherein the set of temporary reference signals includes at least one of the temporary reference signals, and the RRC signaling includes a temporary reference signal configuration, wherein the temporary reference signal configuration includes an index of the temporary reference signal; The system receives Media Access Control Management Unit (MAC CE) signaling, which includes an activation / deactivation status indication field for secondary cell i and a temporary reference signal index indication field on secondary cell i, wherein the activation / deactivation status indication field of secondary cell i indicates the activation of secondary cell i. In response to the MAC CE signaling, the activation of secondary cell i is triggered, and the temporary reference signal on secondary cell i is received according to the temporary reference signal configuration and the temporary reference signal index indicated by the temporary reference signal index indication field on secondary cell i. The temporary reference signal configuration further includes at least one of the following: the number of temporary reference signal clusters in the time domain, the distance between different temporary reference signal clusters in the time domain, or the offset of the temporary reference signal.

2. The method according to claim 1, characterized in that, The temporary reference signal includes an aperiodic channel state information reference signal (CSI-RS) or an aperiodic tracking reference signal (TRS).

3. The method according to claim 1 or 2, characterized in that, The activation / deactivation status indication field of the secondary cell i indicates the activation of the secondary cell i, including: The activation / deactivation status indicator field of the secondary cell i is set to 1.

4. The method according to any one of claims 1-3, characterized in that, The temporary reference signal is used to obtain the information needed to complete cell activation.

5. The method according to any one of claims 1-4, characterized in that, When the MAC CE signaling is used to activate the secondary cell i, the MAC CE signaling includes a temporary reference signal index indication field on the secondary cell i.

6. A communication method, characterized in that, include: Receive a first capability, which indicates whether simultaneous triggering of cell activation and temporary reference signal is supported; Send Radio Resource Control (RRC) signaling, the RRC signaling being used to configure a set of temporary reference signals at the cell granularity, wherein the set of temporary reference signals includes at least one of the temporary reference signals, and the RRC signaling includes a temporary reference signal configuration, wherein the temporary reference signal configuration includes an index of the temporary reference signal; The MAC CE signaling is sent to the Media Access Control Management Unit. The MAC CE signaling is used to activate the secondary cell i and indicate the temporary reference signal on the secondary cell i. The MAC CE signaling includes an activation / deactivation status indication field of the secondary cell i and a temporary reference signal index indication field on the secondary cell i. The activation / deactivation status indication field of the secondary cell i indicates the activation of the secondary cell i. The temporary reference signal configuration further includes at least one of the following: the number of temporary reference signal clusters in the time domain, the distance between different temporary reference signal clusters in the time domain, or the offset of the temporary reference signal.

7. The method according to claim 6, characterized in that, The temporary reference signal includes an aperiodic channel state information reference signal (CSI-RS) or an aperiodic tracking reference signal (TRS).

8. The method according to claim 6 or 7, characterized in that, The activation / deactivation status indication field of the secondary cell i indicates the activation of the secondary cell i, including: The activation / deactivation status indicator field of the secondary cell i is set to 1.

9. The method according to any one of claims 6-8, characterized in that, The temporary reference signal is used to obtain the information needed to complete cell activation.

10. The method according to any one of claims 6-9, characterized in that, When the MAC CE signaling is used to activate the secondary cell i, the MAC CE signaling includes a temporary reference signal index indication field on the secondary cell i.

11. A communication method, characterized in that, include: The terminal device sends a first capability, which indicates whether it supports simultaneously triggering cell activation and temporary reference signals; The network device receives the first capability; The network device sends Radio Resource Control (RRC) signaling, which is used to configure a set of temporary reference signals at the cell granularity. The set of temporary reference signals includes at least one temporary reference signal. The RRC signaling includes a temporary reference signal configuration, which includes an index of the temporary reference signal. The terminal device receives the RRC signaling; The network device sends a Media Access Control Management Unit (MAC CE) signaling message, which includes an activation / deactivation status indication field for secondary cell i and a temporary reference signal index indication field on secondary cell i, wherein the activation / deactivation status indication field of secondary cell i indicates the activation of secondary cell i. The terminal device receives the MAC CE signaling; In response to the MAC CE signaling, the terminal device triggers the activation of the secondary cell i, and receives the temporary reference signal on the secondary cell i according to the temporary reference signal configuration and the temporary reference signal index indicated by the temporary reference signal index indication field on the secondary cell i. The temporary reference signal configuration further includes at least one of the following: the number of temporary reference signal clusters in the time domain, the distance between different temporary reference signal clusters in the time domain, or the offset of the temporary reference signal.

12. The method according to claim 11, characterized in that, The temporary reference signal includes an aperiodic channel state information reference signal (CSI-RS) or an aperiodic tracking reference signal (TRS).

13. The method according to claim 11 or 12, characterized in that, The activation / deactivation status indication field of the secondary cell i indicates the activation of the secondary cell i, including: The activation / deactivation status indicator field of the secondary cell i is set to 1.

14. The method according to any one of claims 11-13, characterized in that, The temporary reference signal is used to obtain the information needed to complete cell activation.

15. The method according to any one of claims 11-14, characterized in that, When the MAC CE signaling is used to activate the secondary cell i, the MAC CE signaling includes a temporary reference signal index indication field on the secondary cell i.

16. A communication system, characterized in that, include: Terminal device, configured to perform the method as described in any one of claims 1-5; A network device for performing the method as described in any one of claims 6-10.

17. A communication device, characterized in that, include: A processor for executing a computer program stored in a memory to cause the communication device to perform the method as described in any one of claims 1-5.

18. A communication device, characterized in that, include: A processor for executing a computer program stored in a memory to cause the communication device to perform the method as described in any one of claims 6-10.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when run in a computer, causes the computer to perform the method as claimed in any one of claims 1-5 or any one of claims 6-10.

20. A computer program product, characterized in that, The computer program product includes computer program code that, when executed by a computer, causes the computer to perform the method as claimed in any one of claims 1-5 or any one of claims 6-10.

21. A chip, characterized in that, include: A processor for retrieving and running a computer program from memory, causing a communication device on which the chip is mounted to perform the method as claimed in any one of claims 1-5 or any one of claims 6-10.

Images