Method and device for cross-carrier scheduling of primary cells

Abstract

The present disclosure describes a method, system, and device for switching a primary cell for cross-carrier scheduling for a user equipment (UE), wherein a secondary cell is configured to schedule the primary cell. One method includes receiving downlink control information (DCI) from a network base station by a UE via a physical downlink control channel (PDCCH), and the DCI is used to switch the cross-carrier scheduling of the primary cell. Another method includes receiving a media access control (MAC) control element (CE) by the UE from a network base station, and the MAC CE is used to switch the cross-carrier scheduling of the primary cell. Another method includes performing a shutdown of the cross-carrier scheduling of the primary cell by the secondary cell for the UE, and restoring the factor for scheduling the primary cell in the primary cell by the UE, and / or restoring the non-fallback downlink control information (DCI) for scheduling the primary cell in the primary cell by the UE.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications. In particular, the present disclosure relates to methods and devices for scheduling a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) on a primary cell (PCell) or a primary secondary cell (PSCell) using a physical downlink control channel (PDCCH) of a secondary cell (SCell). Background Art

[0002] Wireless communication technology is driving the world towards an increasingly interconnected and networked society. High-speed and low-latency wireless communications rely on efficient network resource management and allocation between user devices and wireless access network nodes (including but not limited to wireless base stations). The next-generation network is expected to provide high-speed, low-latency and ultra-reliable communication capabilities and meet the needs of different industries and users.

[0003] For the fifth generation mobile communication technology, the primary cell can schedule the secondary cell. There are some difficulties and / or problems in the existing system. One difficulty / problem may include that the physical downlink control channel (PDCCH) of the primary cell can schedule the physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) on the secondary cell, but there is a difficulty / problem in scheduling the PDCCH of the secondary cell that schedules the PDSCH or PUSCH on the primary cell. The present disclosure can solve at least some of the difficulties associated with the existing system to improve the performance of wireless communications. Another difficulty / problem may include that, considering the dynamic spectrum sharing (DSS) in the recent development of wireless communication technology, the resources of the PDCCH of the primary cell may be restricted / limited. In order to alleviate the restricted / limited PDCCH resources of the primary cell and / or unload the PDCCH transmission on the primary cell, the present disclosure proposes various embodiments for cross-carrier scheduling, including the secondary cell scheduling the PDSCH or PUSCH of the primary cell. Summary of the invention

[0004] This document relates to methods, systems and devices for wireless communications, and more specifically to methods, systems and devices for scheduling a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) on a primary cell (PCell) or a primary secondary cell (PSCell) using a physical downlink control channel (PDCCH) of a secondary cell (SCell).

[0005] In one embodiment, the present disclosure describes a method for wireless communication. The method includes switching cross-carrier scheduling of a primary cell for a user equipment (UE), wherein a secondary cell is configured to schedule the primary cell in the following manner: receiving downlink control information (DCI) from a network base station via a physical downlink control channel (PDCCH) by the UE, the DCI being used to switch cross-carrier scheduling of the primary cell.

[0006] In another embodiment, the present disclosure describes a method for wireless communication. The method includes switching a primary cell for a user equipment (UE) across carriers, wherein a secondary cell is configured to schedule the primary cell in the following manner: receiving a media access control (MAC) control element (CE) from a network base station by the UE, the MAC CE being used to switch the primary cell across carriers.

[0007] In another embodiment, the present disclosure describes a method for wireless communication. The method includes switching a primary cell for cross-carrier scheduling for a user equipment (UE) through a timer, wherein a secondary cell is configured or activated to schedule the primary cell, including: in response to receiving a DCI on the secondary cell within a time period of the timer to schedule the primary cell across carriers, the UE resets the timer; and in response to the time period of the timer expiring without receiving at least one DCI on the secondary cell to schedule the primary cell across carriers, the UE releases the cross-carrier scheduling of the primary cell by the secondary cell.

[0008] In another embodiment, the present disclosure describes a method for wireless communication. The method includes: performing a shutdown of cross-carrier scheduling of a primary cell by a secondary cell for a user equipment (UE); and restoring, by the UE, a factor in the primary cell for scheduling the primary cell.

[0009] In another embodiment, the present disclosure describes a method for wireless communication, including: performing a shutdown of cross-carrier scheduling of a primary cell by a secondary cell for a user equipment (UE); and restoring, by the UE, non-fallback downlink control information (DCI) in the primary cell for scheduling the primary cell.

[0010] In some other embodiments, an apparatus for wireless communication may include a memory storing instructions and a processing circuit system in communication with the memory. When the processing circuit system executes the instructions, the processing circuit system is configured to perform the above method.

[0011] In some other embodiments, a device for wireless communication may include a memory storing instructions and a processing circuit system in communication with the memory. When the processing circuit system executes the instructions, the processing circuit system is configured to perform the above method.

[0012] In some other embodiments, a computer-readable medium includes instructions that, when executed by a computer, cause the computer to perform the above method.

[0013] The above and other aspects and implementations thereof are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 An example of a wireless communication system including a radio network node and one or more user equipments is shown.

[0015] Figure 2 An example of a network node is shown.

[0016] Figure 3 An example of a user device is shown.

[0017] Figure 4 A flow chart of a method for wireless communication is shown.

[0018] Figure 5 A schematic diagram of an exemplary embodiment for wireless communications is shown.

[0019] Figure 6 An exemplary embodiment of a table used in an exemplary embodiment for wireless communications is shown.

[0020] Figure 7 A flow chart of a method for wireless communication is shown.

[0021] Figure 8 A flow chart of a method for wireless communication is shown.

[0022] Fig. 9 A flow chart of a method for wireless communication is shown.

[0023] Fig.10 A flow chart of a method for wireless communication is shown. DETAILED DESCRIPTION

[0024] The present disclosure will now be described in detail below with reference to the accompanying drawings, which form a part of the present disclosure and show by way of illustration specific examples of embodiments. However, it is noted that the present disclosure may be embodied in a variety of different forms, and therefore, the subject matter covered or claimed is intended to be construed as not being limited to any embodiment to be set forth below.

[0025] Throughout the specification and claims, terms may have nuanced meanings suggested or implied by the context rather than the explicitly stated meanings. Likewise, the phrases "in one embodiment" or "in some embodiments" as used herein do not necessarily refer to the same embodiment, and the phrases "in another embodiment" or "in other embodiments" as used herein do not necessarily refer to different embodiments. The phrases "in one implementation" or "in some implementations" as used herein do not necessarily refer to the same implementation, and the phrases "in another implementation" or "in other implementations" as used herein do not necessarily refer to different implementations. For example, the claimed subject matter includes all or part of a combination of exemplary embodiments or implementations.

[0026] Typically, terms can be understood at least in part from usage in context. For example, terms such as "and", "or" or "and / or" used in this article can include multiple meanings, which can depend at least in part on the context in which such terms are used. Typically, "or" if used to associate lists such as A, B or C, means A, B and C, where the inclusive meaning is used, and means A, B or C, where the exclusive meaning is used. In addition, the terms "one or more" or "at least one" used in this article (depending at least in part on the context) can be used to describe any feature, structure or characteristic in a single sense, or can be used to describe a combination of features, structures or characteristics in a plural sense. Similarly, terms such as "one", "an" or "the" can also be understood to express singular usage or plural usage, which depends at least in part on the context. In addition, the term "based on" or "determined by..." can be understood as not necessarily intended to convey a set of exclusive factors, on the contrary, additional factors that are not necessarily explicitly described can be allowed to exist, which depends at least in part on the context.

[0027] The present disclosure describes methods and apparatus for scheduling one or more cells using a single downlink control information (DCI).

[0028] Next-generation (NG) mobile communication systems are driving the world towards an increasingly connected and networked society. High-speed and low-latency wireless communications rely on efficient network resource management and allocation between user devices and radio access network nodes (including but not limited to radio base stations). NG networks are expected to provide high-speed, low-latency and ultra-reliable communication capabilities and meet the requirements of different industries and users.

[0029] The fourth generation of mobile communication technology (4G) long term evolution (LTE) or advanced LTE (LTE-A) and the fifth generation of mobile communication (5G) are facing increasing demands. Based on this development trend, 4G and 5G systems can develop support for enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC) and massive machine type communication (mMTC). According to dynamic spectrum sharing (DSS), some spectrum used for 4G can be reused for 5G.

[0030] In a 5G communication system, a secondary service cell (SCell) may be the only scheduling cell or scheduled cell, and a primary cell (PCell) or a primary secondary cell (PSCell) may be a scheduling cell and may not be a scheduled cell. A primary secondary cell (PSCell) may be a primary cell in a secondary cell group (SCG). There are some difficulties and / or problems with the current system. One difficulty / problem may include that the physical downlink control channel (PDCCH) of the PCell / PSCell may schedule the physical downlink shared channel (PDSCH) or the physical uplink shared channel (PUSCH) on the SCell, but the PDSCH or PUSCH on the PCell / PSCell may not be scheduled by the PDCCH of the SCell. Considering the DSS in the NR communication system, the PDCCH resources of the PCell / PSCell may be constrained.

[0031] The present disclosure describes various embodiments, including NR PDCCH enhancements for cross-carrier scheduling, including SCell's PDCCH scheduling PCell / PSCell's PDSCH or PUSCH to at least alleviate the restricted / limited PDCCH resources PCell / PSCell and / or offload data transmission on the PDCCH of the PCell / PSCell. When the capacity limitation of the PDCCH of the PCell / PSCell changes dynamically, the various embodiments described in the present disclosure support dynamic switching of the primary cell to be scheduled by the secondary cell across carriers.

[0032] Figure 1A wireless communication system 100 is shown that includes a radio network node 118 and one or more user equipment (UE) 110. The radio network node may include a network base station, which may be a nodeB (NB, such as a gNB) in a mobile telecommunication context. Each UE may wirelessly communicate with the radio network node via one or more radio channels 115. For example, a first UE 110 may wirelessly communicate with the radio network node 118 via a channel including multiple radio channels during a specific time period. The network base station 118 may send high-layer signaling to the UE 110. The high-layer signaling may include configuration information for communication between the UE and the base station. In one implementation, the high-layer signaling may include a radio resource control (RRC) message.

[0033] Figure 2 An example of an electronic device 200 for implementing a network base station is shown. The example electronic device 200 may include a radio transmission / reception (Tx / Rx) circuit system 208 for transmitting / receiving communications with UEs and / or other base stations. The electronic device 200 may also include a network interface circuit system 209 for enabling the base station to communicate with other base stations and / or a core network (e.g., optical or wired interconnects, Ethernet, and / or other data transmission media / protocols). The electronic device 200 may optionally include an input / output (I / O) interface 206 for communicating with an operator or the like.

[0034] The electronic device 200 may also include a system circuit system 204. The system circuit system 204 may include (multiple) processors 221 and / or a memory 222. The memory 222 may include an operating system 224, instructions 226, and parameters 228. The instructions 226 may be configured to perform functions of a network node for one or more of the processors 124. The parameters 228 may include parameters for supporting the execution of the instructions 226. For example, the parameters may include network protocol settings, bandwidth parameters, radio frequency mapping allocations, and / or other parameters.

[0035] Figure 3An example of an electronic device for implementing a terminal device 300 (e.g., a user equipment (UE)) is shown. UE 300 may be a mobile device, such as a smart phone or a mobile communication module provided in a vehicle. UE 300 may include a communication interface 302, a system circuit system 304, an input / output interface (I / O) 306, a display circuit system 308, and a storage device 309. The display circuit system may include a user interface 310. The system circuit system 304 may include any combination of hardware, software, firmware, or other logic / circuitry systems. The system circuit system 304 may be implemented, for example, with one or more systems on a chip (SoC), application specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuit systems. The system circuit system 304 may be part of the implementation of any desired function in UE 300. In this regard, the system circuit system 304 may include logic that, for example, facilitates decoding and playing music and videos, such as MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating (as an example) a cellular phone call or data connection for an Internet connection; establishing, maintaining, and terminating a wireless network connection, a Bluetooth connection, or other connection; and displaying relevant information on a user interface 310. The user interface 310 and the input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, tactile feedback or other tactile output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements. Other examples of the I / O interface 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, universal serial bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0036] refer to Figure 3, the communication interface 302 may include a radio frequency (RF) transmission (Tx) and reception (Rx) circuit system 316 for processing signal transmission and reception through one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver that includes a modulation / demodulation circuit system, a digital-to-analog converter (DAC), a shaping table, an analog-to-digital converter (ADC), a filter, a waveform shaper, a filter, a preamplifier, a power amplifier, and / or other logic for transmission and reception through one or more antennas or (for some devices) through a physical (e.g., wired) medium. The transmitted and received signals may follow any of a variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As a specific example, the communication interface 302 may include a transceiver that supports transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA) +, 4G / Long Term Evolution (LTE), and 5G standards. However, the techniques described below are applicable to other wireless communication technologies, whether derived from the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards bodies.

[0037] refer to Figure 3 , the system circuit system 304 may include one or more processors 321 and a memory 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 to implement the desired functions of the UE 300. The parameters 328 may provide and specify configuration and operating options for the instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, or other data that the UE 300 will send or has received through the communication interface 302. In various implementations, the system power of the UE 300 may be provided by a power storage device such as a battery or a transformer.

[0038] The present disclosure describes the following embodiments, which may be partially or completely described in the above Figures 2 to 3 The method is implemented on the network base station and / or user equipment described in the embodiment.

[0039] refer to Figure 4, the present disclosure describes an embodiment of a method 400 for switching a cross-carrier scheduled primary cell for a user equipment (UE), wherein a secondary cell is configured to schedule the primary cell. The method 400 may include step 410: receiving downlink control information (DCI) from a network base station via a physical downlink control channel (PDCCH) by the UE, the DCI being used to switch the cross-carrier scheduled primary cell. In one implementation, the cross-carrier scheduling of the primary cell includes the PDCCH of the secondary cell (SCell) scheduling a physical shared channel on the primary cell. The primary cell may include at least one of a primary cell (PCell) in a primary cell group or a primary cell (PSCell) in a secondary cell group. The physical shared channel on the primary cell includes at least one of a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) on the primary cell.

[0040] The present disclosure describes various embodiments that use bandwidth parts (BWP) to support dynamic switching of scheduling of a primary cell by a secondary cell across carriers. In a carrier aggregation (CA) scenario, a primary cell (e.g., PCell or PSCell) may be configured to be scheduled by a secondary cell (e.g., SCell). In one implementation, the secondary cell is configured as a scheduling cell to schedule itself, and is also configured to support scheduling of the primary cell.

[0041] The various embodiments described in the present disclosure improve wireless communication technology and solve at least some problems / issues of previous systems, thereby bringing benefits. For example, in one embodiment, multiple BWPs are configured to support or not support cross-carrier scheduling of primary cells in combination with BWP switching indications, or they all support cross-carrier scheduling of primary cells and BWP switching indications and indicate whether the BWP supports SCell-schedule-PCell to achieve dynamic support for cross-carrier scheduling of primary cells. This can ensure that when the SCell supports scheduling of PCell / PSCell, changes in PDCCH capacity can be flexibly adapted. The dynamic release of cross-carrier scheduling of primary cells can reduce the complexity of blind detection and save power consumption of UE.

[0042] In one implementation of various embodiments, at least two BWPs are configured in the secondary cell. The search space index configured for one BWP of the secondary cell is different from the search space index configured for one BWP of the primary cell. At least one search space index configured in other BWPs of the secondary cell is the same as the search space index configured for one BWP of the primary cell. The activated BWP of the secondary cell is dynamically indicated by DCI to dynamically support cross-carrier scheduling of the primary cell.

[0043] The secondary cell may be configured to support cross-carrier scheduling of the primary cell. The primary cell may be configured with a bandwidth part (BWP) having a search space index. The secondary cell is configured with a first BWP having a first search space index, and the first search space index of the first BWP is the same as the search space index of the BWP in the primary cell; and the secondary cell is also configured with a second BWP having a second search space index, and the second search space index of the second BWP is different from the search space index of the BWP in the primary cell. The DCI includes a bandwidth part indication field (indicator). The bandwidth part indication field may be used to indicate which BWP is activated for cross-carrier scheduling of the primary cell by the secondary cell. For example, but not limited to, the field size of the bandwidth part indication field is configured as 1 bit, and the bandwidth part indication field "0" may be used to indicate that the first BWP is activated for cross-carrier scheduling of the primary cell by the secondary cell; and the bandwidth part indication field "1" may be used to indicate that the second BWP is activated for cross-carrier scheduling of the primary cell by the secondary cell. In response to the bandwidth part indication field indicating that the first BWP is activated, the secondary cell schedules the primary cell to be turned on across carriers; and in response to the bandwidth part indication field indicating that the second BWP is activated, the secondary cell schedules the primary cell to be turned off across carriers.

[0044] For example, refer to Figure 5 , cell A 510 is a primary cell and is configured with search space index = {0, 1, 2, 3, 10, 11, 12 and 13} in the BWP. Cell B 520 is a secondary cell and the configuration of cell B 520 supports cross-carrier scheduling of cell A 510. Cell B 520 is configured with search space index = {0, 1, 2 and 3} in a first BWP (BWP1) 522 and is configured with search space index = {20, 21, 22 and 23} in a second BWP (BWP2) 524. When the bandwidth part indication field in the DCI for cross-carrier scheduling of the primary cell by the secondary cell indicates that the activated BWP is BWP1, cross-carrier scheduling of the primary cell by the secondary cell is supported because cell B is configured to support cross-carrier scheduling of cell A and the same search space index is provided. When the bandwidth part indication field indicating activation of BWP in DCI is BWP2, even if cell B is configured to support cross-carrier scheduling of cell A, cross-carrier scheduling of the primary cell is not supported because they do not have the same search space index.

[0045] In another implementation of various embodiments, at least two BWPs are configured in the secondary cell, and each BWP is configured whether each BWP supports cross-carrier scheduling of the primary cell. The activated BWP of the secondary cell is dynamically indicated to the BWP supporting cross-carrier scheduling of the primary cell or the BWP not supporting cross-carrier scheduling of the primary cell to dynamically support cross-carrier scheduling of the primary cell.

[0046] The primary cell is configured with a bandwidth part (BWP) having a search space index. The secondary cell is configured with a first BWP having a first search space index, and the first BWP is configured to support cross-carrier scheduling; and the secondary cell is configured with a second BWP having a second search space index, and the second BWP is configured not to support cross-carrier scheduling. The DCI may include a bandwidth part indication field. The bandwidth part indication field may be used to indicate which BWP is activated for use by the secondary cell. For example, but not limited to, the field size of the bandwidth part indication field is configured as 1 bit, and the bandwidth part indication field "0" may be used to indicate that the first BWP is activated; and the bandwidth part indication field "1" may be used to indicate that the second BWP is activated for scheduling the primary cell across carriers by the secondary cell. In response to the bandwidth part indication field indicating that the first BWP is activated, the primary cell is dynamically turned on by the secondary cell for cross-carrier scheduling; and in response to the bandwidth part indication field indicating that the second BWP is activated, the primary cell is dynamically turned off by the secondary cell for cross-carrier scheduling.

[0047] For example, but not limited to, the configuration of the secondary cell (cell B) can support cross-carrier scheduling of the primary cell (cell A). In the BWP, cell A is configured with a search space index = {0, 1, 2, 3, 10, 11, 12 and 13}. Cell B is configured with a search space index = {0, 1, 2 and 3} in the first BWP (BWP1), and a search space index = {10, 11, 12 and 13} in the second BWP (BWP2). BWP1 is configured to support cross-carrier scheduling of the primary cell by the secondary cell (also known as SCell-schedule-PCell). BWP2 is configured not to support cross-carrier scheduling of the primary cell by the secondary cell. When the bandwidth part indication field for secondary cell scheduling in the DCI indicates that BWP1 is an activated BWP, cross-carrier scheduling of the primary cell by the secondary cell is supported because cell B is configured to support cross-carrier scheduling of cell A, and the same search space index can be provided, and BWP1 is configured to support SCell-schedule-PCell. When the bandwidth part indication field in the DCI indicates that BWP2 is an activated BWP, even if cell B is configured to support cross-carrier scheduling of cell A and the same search space index can be provided, SCell-schedule-PCell is not supported because BWP2 is configured not to support SCell-schedule-PCell.

[0048] In another implementation of various embodiments, at least two BWPs are configured in the secondary cell. The DCI indicates which BWP of the secondary cell is activated and whether the BWP of the secondary cell supports cross-carrier scheduling of the primary cell. Therefore, the activated BWP of the secondary cell is dynamically indicated by the DCI, and whether the BWP supports SCell-schedule-PCell is also dynamically indicated by the DCI, so as to dynamically support cross-carrier scheduling of the primary cell.

[0049] The DCI may include a bandwidth portion indication field including a cross-carrier scheduled primary cell indication field. The bandwidth portion indication field may be used to indicate which BWP is activated for use by the secondary cell. For example, but not limited to, the field size of the bandwidth portion indication field including the cross-carrier scheduled primary cell indication field is configured as 2 bits, the first bit represents the bandwidth portion indication field, and the indication "0" of the bandwidth portion indication field may be used to indicate that the first BWP is activated; and the bandwidth portion indication field "1" may be used to indicate that the second BWP is activated. The cross-carrier scheduled primary cell indication field may be used to indicate whether the secondary cell activates or releases the cross-carrier scheduled primary cell. For example, but not limited to, the second bit represents the cross-carrier scheduled primary cell indication field, and the indication "0" of the cross-carrier scheduled primary cell indication field may be used to indicate the release of the cross-carrier scheduled primary cell; and the cross-carrier scheduled primary cell indication field "1" may be used to indicate the activation of the cross-carrier scheduled primary cell indication field. In response to the bandwidth part indication field indicating that the BWP is activated and the cross-carrier scheduled main cell indication field indicating the activation of the cross-carrier scheduled main cell, the cross-carrier scheduled main cell by the secondary cell is dynamically turned on; and in response to the bandwidth part indication field indicating that the BWP is activated and the cross-carrier scheduled main cell indication field indicating the release of the cross-carrier scheduled main cell, the cross-carrier scheduled main cell by the secondary cell is dynamically turned off.

[0050] For example, but not limited to, the configuration of the secondary cell (cell B) supports cross-carrier scheduling of the primary cell (cell A). Cell A is configured with search space index = {0, 1, 2, 3, 10, 11, 12 and 13} in the BWP. Cell B is configured with search space index = {0, 1, 2 and 3} in the first BWP (BWP1) and search space index = {10, 11, 12 and 13} in the second BWP (BWP2). When the bandwidth part indication field for secondary cell scheduling in the DCI indicates that the activated BWP is BWP1, cross-carrier scheduling of the primary cell (also called SCell-schedule-PCell) is supported because cell B is configured to support cross-carrier scheduling of cell A, and the same search space index can be provided, and the cross-carrier scheduling of the primary cell indication field indicates support for SCell-schedule-PCell. When the bandwidth part indication field indicating the activation of BWP in the DCI is BWP2, even if cell B is configured to support cross-carrier scheduling of cell A and the same search space index can be provided, SCell-schedule-PCell is not supported because the cross-carrier scheduling primary cell indication field indicates that SCell-schedule-PCell is not supported.

[0051] In another implementation of various embodiments, at least two BWPs are configured in the secondary cell. The two BWPs are non-dormant BWPs. One non-dormant BWP is configured to support cross-carrier scheduling of the primary cell by the secondary cell; and the other non-dormant BWP is configured not to support cross-carrier scheduling of the primary cell by the secondary cell. When the SCell dormancy indication field in the DCI is used, it indicates that the non-dormant BWP supports cross-carrier scheduling of the primary cell by the secondary cell, or it indicates that the non-dormant BWP does not support cross-carrier scheduling of the primary cell by the secondary cell.

[0052] The secondary cell may be configured with a first non-sleeping BWP to support cross-carrier scheduling of the primary cell, and the secondary cell may be configured with a second non-sleeping BWP to not support cross-carrier scheduling of the primary cell. The DCI includes an SCell sleep indication field. The SCell sleep indication field may be used to indicate which BWP is activated for use by the second cell. For example, but not limited to, the field size of the SCell sleep indication field is configured to be 2 bits, and the second bit of the SCcell sleep indication field, which indicates "0", may be used to indicate that the first non-sleeping BWP is activated; and the SCell sleep indication field "1" may be used to indicate that the second non-sleeping BWP is activated. In response to the SCell sleep indication field indicating the use of the activated first non-sleeping BWP, the primary cell is dynamically turned on by cross-carrier scheduling by the secondary cell; in response to the SCell sleep indication field indicating the use of the activated second non-sleeping BWP, the primary cell is dynamically turned off by cross-carrier scheduling by the secondary cell.

[0053] For an example, the configuration of the secondary cell (cell B) can support cross-carrier scheduling of the primary cell (cell A). Cell A is configured with search space index = {0, 1, 2, 3, 10, 11, 12 and 13} in the BWP. Cell B is configured with search space index = {0, 1, 2 and 3} in the first non-dormant BWP (BWP1), and search space index = {10, 11, 12 and 13} in the second dormant BWP (BWP2) and dormant BWP3. BWP1 is configured to support cross-carrier scheduling of the primary cell (also known as SCell-schedule-PCell) by the secondary cell, and BWP2 is configured not to support SCell-schedule-PCell. In one implementation, when the SCell dormancy indication field indicates BWP1, SCell-schedule-PCell is supported because cell B is configured to support cross-carrier scheduling of cell A and the same search space index can be provided, and BWP1 is configured to support SCell-schedule-PCell. When the SCell sleep indication field indicates BWP2, even if cell B is configured to support cross-carrier scheduling of cell A and the same search space index can be provided, SCell-schedule-PCell is not supported because BWP2 is configured not to support SCell-schedule-PCell. Alternatively, in another implementation, when the first bit of the SCell sleep indication field for SCell scheduling in the DCI indicates a "0" value, the SCell sleep indication field indicates switching to a sleep BWP3. When the SCell sleep indication field for SCell scheduling in the DCI indicates a "1" value, the SCell sleep indication field indicates switching to a non-sleep BWP, and further, the second bit of the SCell sleep indication field indicates the index of the non-sleep BWP. When the second bit of the SCell sleep indication field indicates BWP1, SCell-schedule-PCell is supported because cell B is configured to support cross-carrier scheduling of cell A and the same search space index can be provided, and BWP1 is configured to support SCell-schedule-PCell. When the second bit of the SCell dormancy indication field indicates BWP2, even if cell B is configured to support cross-carrier scheduling of cell A and the same search space index can be provided, SCell-schedule-PCell is not supported because BWP2 is configured not to support SCell-schedule-PCell.

[0054] In another implementation of various embodiments, at least two BWPs are configured in the secondary cell, one of the BWPs is a non-dormant BWP, and the other BWP is a dormant BWP. When the SCell dormancy indication in the DCI is used to indicate the non-dormant BWP, it also indicates whether the non-dormant BWP supports cross-carrier scheduling of the primary cell by the secondary cell.

[0055] The DCI may include an SCell sleep indication field including a cross-carrier scheduled primary cell indication field. The SCell sleep indication field may be used to indicate whether a sleep BWP or a non-sleep BWP is activated for use by the second cell. For example, but not limited to, the field size of the SCell sleep indication field including the cross-carrier scheduled primary cell indication field is configured as 2 bits, and the first bit of the SCell sleep indication field, which indicates "0", may be used to indicate that the sleep BWP is activated; and the SCell sleep indication field "1" may be used to indicate that the non-sleep BWP is activated. The cross-carrier scheduled primary cell indication field may be used to indicate whether the secondary cell activates or releases the cross-carrier scheduled primary cell. For example, but not limited to, the second bit of the SCell sleep indication field is a cross-carrier scheduled primary cell indication field, and the indication "0" of the cross-carrier scheduled primary cell indication field may be used to indicate the release of the cross-carrier scheduled primary cell; and the cross-carrier scheduled primary cell indication field "1" may be used to indicate the activation of the cross-carrier scheduled primary cell indication field. In response to the SCell sleep indication field indicating the use of a non-sleep BWP and the cross-carrier scheduled main cell indication field indicating the activation of the cross-carrier scheduled main cell, the secondary cell cross-carrier scheduled main cell is dynamically turned on; and in response to the SCell sleep indication field indicating the use of a non-sleep BWP and the cross-carrier scheduled main cell indication field indicating the release of the cross-carrier scheduled main cell, the secondary cell cross-carrier scheduled main cell is dynamically turned off.

[0056] For an example, the configuration of the secondary cell (cell B) supports cross-carrier scheduling of the primary cell (cell A). Cell A is configured with search space index = {0, 1, 2, 3, 10, 11, 12 and 13} in BWP. Cell B is configured with search space index = {0, 1, 2 and 3} in non-sleeping BWP (BWP1) and sleeping BWP. When the SCell sleep indication field for SCell scheduling in the DCI indicates a "0" value, the SCell sleep indication field indicates a switch to the sleeping BWP2. When the SCell sleep indication field for SCell scheduling in the DCI indicates a "1" value, the SCell sleep indication field indicates a switch to the non-sleeping BWP1. The SCell sleep indication field in the DCI may include a cross-carrier scheduling primary cell indication field, which may indicate whether the non-sleeping BWP1 supports cross-carrier scheduling of the primary cell by the secondary cell. When the SCell sleep indication field for SCell scheduling in the DCI indicates a value of "1" and also indicates support for cross-carrier scheduling of the primary cell by the secondary cell (also called SCell-schedule-PCell), SCell-schedule-PCell is supported because cell B is configured to support cross-carrier scheduling of cell A and the same search space index can be provided. When the SCell sleep indication field for SCell scheduling in the DCI indicates a value of "1" but indicates that SCell-schedule-PCell is not supported, although cell B is configured to support cross-carrier scheduling of cell A and the same search space index can be provided, SCell-schedule-PCell is not supported.

[0057] In another implementation of various embodiments, dynamic cross-carrier scheduling of a primary cell by a secondary cell may be supported by a DCI having an indication of activation or release of cross-carrier scheduling of a primary cell by a secondary cell. A non-fallback DCI including a field indicating a configuration of activation / release of cross-carrier scheduling of a primary cell by a secondary cell may be used to indicate whether cross-carrier scheduling of a primary cell by a secondary cell is dynamically supported.

[0058] The DCI includes a non-fallback DCI, which includes a configurable field indicating a cross-carrier scheduled primary cell. When configured, this field can be used to indicate whether the secondary cell activates or releases the cross-carrier scheduled primary cell. For example, but not limited to, field "0" can be used to indicate the release of the cross-carrier scheduled primary cell; and field "1" can be used to indicate the activation of the cross-carrier scheduled primary cell indication field. In one implementation, the field may be an SCell-schedule-PCell field. In response to the field in the non-fallback DCI indicating the activation of the cross-carrier scheduled primary cell, the cross-carrier scheduled primary cell by the secondary cell is turned on; and in response to the field in the non-fallback DCI indicating the release of the cross-carrier scheduled primary cell, the cross-carrier scheduled primary cell by the secondary cell is turned off.

[0059] Optionally, in one implementation, the effective time point for turning on or off the cross-carrier scheduling of the primary cell by the secondary cell includes at least one of the following: a first time based on the time of receiving the DCI and the offset value; and a second time based on the time of the physical shared channel scheduled by the DCI and the offset value. The offset value is an integer equal to or greater than zero; and the offset value indicates an offset period determined by multiplying the integer with at least one of the following: an absolute time interval, an orthogonal frequency division multiplexing (OFDM) symbol, or a time slot.

[0060] For an example, the configuration of the secondary cell (cell B) supports cross-carrier scheduling of the primary cell (cell A). Cell A is configured with search space index = {0, 1, 2, 3, 10, 11, 12 and 13} in the BWP, and the activation / release of the SCell-schedule-PCell field is configured in a non-fallback DCI (e.g., DCI format 0_1 / 1_1) in at least one search space. Cell B is configured with search space index = {0, 1, 2 and 3} in BWP1, which is also configured to support SCell-schedule-PCell. When the activation / release of the SCell-schedule-PCell field in the non-fallback DCI indicates the release of the SCell-schedule-PCell, although cell B is configured to support cross-carrier scheduling of cell A and the same search space index can be provided, SCell scheduling is not supported. When the activation / release of the SCell-schedule-PCell field in the non-fallback DCI indicates activation of the SCell-schedule-PCell, since cell B is configured to support cross-carrier scheduling of cell A and the same search space index can be provided, SCell scheduling is supported.

[0061] For another example, the effective time of activation / release of SCell-schedule-PCell can be any one of the following times based on the offset value: (1) the offset value plus the time slot / symbol #n of the reception of DCI, which has an indication of activation / release of SCell-schedule-PCell; or (2) the offset value plus the time slot / symbol #n of the PDSCH / PUSCH scheduled by the DCI, which has an indication of activation / release of SCell-schedule-PCell. The offset value is an integer equal to or greater than 0, which can be represented by one of the following: the offset value multiplied by the absolute time interval, the offset value multiplied by the OFDM symbol, or the offset value multiplied by the time slot or subslot.

[0062] In another implementation of various embodiments, dynamic cross-carrier scheduling of a primary cell by a secondary cell may be supported by a DCI having an indication of activation or release of cross-carrier scheduling of a primary cell by a secondary cell. The DCI may be a fallback DCI indicating whether cross-carrier scheduling of a primary cell by a secondary cell is supported. The fallback DCI may include an indication field, which may include one of the following: a cyclic redundancy check (CRC) scrambled by a specific radio network temporary identification field (RNTI); at least one reserved bit in the fallback DCI; and a short message in the fallback DCI.

[0063] The DCI may include a fallback DCI, which includes an indication field indicating a cross-carrier scheduled primary cell. For example, but not limited to, the indication field "0" can be used to indicate the release of the cross-carrier scheduled primary cell; and the indication field "1" can be used to indicate the activation of the cross-carrier scheduled primary cell indication field. In response to the indication field in the fallback DCI indicating the activation of the cross-carrier scheduled primary cell, the cross-carrier scheduled primary cell by the secondary cell is dynamically turned on; and in response to the indication field in the fallback DCI indicating the release of the cross-carrier scheduled primary cell, the cross-carrier scheduled primary cell by the secondary cell is dynamically turned off. Optionally, the indication field in the fallback DCI includes at least one of the following: a cyclic redundancy check (CRC) scrambled by a specific radio network temporary identification field (RNTI); at least one reserved bit in the fallback DCI; and a short message in the fallback DCI.

[0064] For example, when the DCI may have a format of DCI format 1_0, the format has a CRC scrambled by a system information RNTI (SI-RNTI), a paging RNTI (P-RNTI), a random access RNTI (RA-RNTI), a MsgB-RNTI, or a cell RNTI (C-RNTI). The "frequency domain resource allocation" field of the DCI may include all 1s, and 1 bit in the reserved bits indicates the activation / release of the SCell-schedule-Pcell. In one implementation, when the DCI may have a format of DCI format 1_0 or DCI format 0_0 for unicast scheduling, an RNTI with a specific value to scramble the CRC may indicate the activation / release of the SCell-schedule-PCell. In another implementation, when the short message indication field indicates only a short message present in the DCI or both scheduling information and a short message are present in the DCI, the short message may be used to indicate the activation / release of the SCell-schedule-Pcell.

[0065] In another implementation of various embodiments, dynamic cross-carrier scheduling of a primary cell by a secondary cell may be supported by a DCI having an indication of activation or release of cross-carrier scheduling of the primary cell by the secondary cell. The blind decoding / control channel element (BD / CCE) scaling factor (or cell weight factor) of the two scheduling cells of the PCell may be configured to implicitly indicate activation / release of cross-carrier scheduling of the primary cell by the secondary cell.

[0066] The DCI may include a factor indicating a cross-carrier scheduled primary cell. The factor in the DCI may include one of the following: a blind decoding / control channel element (BD / CCE) scaling factor or a cell weight factor. When the BD / CCE scaling factor between the PCell and the SCell is (1, 0), that is, the BD / CCE of the PCell is 1 times the BD / CCE of each cell, and the BD / CCE of the SCell is 0 times the BD / CCE of each cell, it indicates the release of the cross-carrier scheduled primary cell. Therefore, when the factor in the DCI is equal to (1, 0) for the PCell and the SCell, respectively, the factor indicates the release of the cross-carrier scheduled primary cell. In response to the factor in the DCI indicating the activation of the cross-carrier scheduled primary cell, the cross-carrier scheduled primary cell by the secondary cell is dynamically turned on; and in response to the factor in the DCI indicating the release of the cross-carrier scheduled primary cell, the cross-carrier scheduled primary cell by the secondary cell is dynamically turned off.

[0067] For example, the BD / CCE scaling factors (or cell weight factors, which represent the number of scheduled PCells counted for the scheduling cells of the PCell and SCell, respectively) of the two scheduled cells of the PCell indicated in the DCI are configured. Figure 6In one implementation, the factor may include a 2-bit value 612, which represents the BD / CCE scaling factor between the PCell and the SCell 614. The 2-bit value "00" (621) represents the BD / CCE scaling factor of (0.33, 0.66); the 2-bit value "01" (622) represents the BD / CCE scaling factor of (0.5, 0.5); the 2-bit value "10" (623) represents the BD / CCE scaling factor of (0.66, 0.33); the 2-bit value "00" (624) represents the BD / CCE scaling factor of (1, 0). When the scaling factors of the BD / CCEs of the PCell and the SCell are (0.5, 0.5), the budget of the BD / CCE of the PCell used to schedule the PCell is 1 / 2 of the budget of the BD / CCE per cell, and the budget of the SCell used to schedule the PCell is 1 / 2 of the budget of the BD / CCE per cell. When the scaling factor between PCell and SCell BD / CCE is (1, 0), the BD / CCE of PCell is 1 times the BD / CCE of each cell, and the BD / CCE of SCell is 0 times the BD / CCE of each cell, which implicitly releases SCell-schedule-PCell.

[0068] Optionally and / or alternatively, in another implementation, the DCI may not need to indicate BWP switching. Optionally and / or alternatively, in another implementation, the DCI may be transmitted on the primary cell.

[0069] The various embodiments described in the present disclosure improve wireless communication technology and solve at least some of the problems / issues of previous systems, thereby bringing benefits. For example, in one embodiment, dynamic support for SCell-schedule-PCell is achieved by explicitly or implicitly indicating the activation / release of SCell-schedule-PCell. This can ensure that when SCell supports scheduling of PCell / PSCell, changes in PDCCH capacity can be flexibly adapted. Dynamic release of cross-carrier scheduling of primary cells can reduce the complexity of blind detection and save power consumption of UE.

[0070] refer to Figure 7, the present disclosure describes an embodiment of a method 700 for switching a cross-carrier scheduled primary cell for a user equipment (UE), wherein a secondary cell is configured to schedule the primary cell. The method 700 may include step 710: a media access control (MAC) control element (CE) is received by the UE from a network base station, and the MAC CE is used to switch the cross-carrier scheduled primary cell. In one implementation, the cross-carrier scheduling of the primary cell includes the PDCCH of the secondary cell (SCell) scheduling a physical shared channel on the primary cell. The primary cell may include at least one of a primary cell (PCell) in a primary cell group or a primary cell (PSCell) in a secondary cell group. The physical shared channel on the primary cell includes at least one of a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) on the primary cell.

[0071] The present disclosure describes various embodiments for supporting dynamic SCell-schedule-PCell by MACCE with activation or release indication of SCell-schedule-PCell. In a carrier aggregation (CA) scenario, a primary cell (e.g., PCell or PSCell) may be configured to be scheduled by a secondary cell (e.g., SCell). In one implementation, the secondary cell is configured as a scheduling cell to schedule itself, and is also configured to support scheduling of the primary cell.

[0072] The various embodiments described in the present disclosure improve wireless communication technology and solve at least some of the problems / issues of previous systems, thereby bringing benefits. For example, in one embodiment, the activation / release of SCell-schedule-PCell is indicated by an independent MAC CE or a joint encoding with other MAC CEs, thereby achieving dynamic support for SCell-schedule-PCell. This can ensure that when the SCell supports the scheduling of PCell / PSCell, changes in PDCCH capacity can be flexibly adapted. The dynamic release of the cross-carrier scheduled primary cell can reduce the complexity of blind detection and save power consumption of the UE.

[0073] In one implementation of various embodiments, a MAC CE may be used to indicate activation / release of an SCell-schedule-Pcell, and the MAC CE may include a subheader with a specific logical channel identifier (LCID). For example, the MAC CE includes a specific MAC CE, which includes a MAC subheader with a specific logical channel identifier (LCID) indicating a cross-carrier scheduled primary cell. For example, but not limited to, a field "0" in the MAC CE may be used to indicate the release of a cross-carrier scheduled primary cell; and a field "1" in the MAC CE may be used to indicate the activation of a cross-carrier scheduled primary cell indication field. In response to the field in the MAC CE indicating the activation of a cross-carrier scheduled primary cell, the cross-carrier scheduled primary cell by the secondary cell is dynamically turned on; and in response to the field in the MAC CE indicating the release of the activation of the cross-carrier scheduled primary cell, the cross-carrier scheduled primary cell by the secondary cell is dynamically turned off.

[0074] In another implementation of various embodiments, joint coding with other MAC CEs may be used to indicate activation / release of the SCell-schedule-PCell. For example, one or more reserved bits in the SCell activation / deactivation MAC CE are used to activate / release the SCell-schedule-PCell, that is, the SCell-schedule-PCell is activated / released while performing activation / deactivation of the SCell.

[0075] The MAC CE includes a joint MAC CE, which includes a reserved bit indicating a cross-carrier scheduled primary cell. Optionally and / or alternatively, the joint MAC CE includes an SCell activation / deactivation MAC CE. For example, but not limited to, the reserved bit "0" in the MAC CE can be used to indicate the release of the cross-carrier scheduled primary cell; and the reserved bit "1" in the MAC CE can be used to indicate the activation of the cross-carrier scheduled primary cell indication field. In response to the reserved bit indicating the activation of the cross-carrier scheduled primary cell, the cross-carrier scheduled primary cell by the secondary cell is dynamically turned on; and in response to the reserved bit indicating the release of the activation of the cross-carrier scheduled primary cell, the cross-carrier scheduled primary cell by the secondary cell is dynamically turned off.

[0076] refer to Figure 8, the present disclosure describes an embodiment of a method 800 for switching cross-carrier scheduling of a primary cell for a user equipment (UE) by a timer, wherein a secondary cell is configured or activated to schedule the primary cell. The method 800 may include step 810: in response to receiving a DCI on the secondary cell to schedule the primary cell across carriers within a time period of the timer, the UE resets the timer; and step 820: in response to the time period of the timer expiring without receiving at least one DCI on the secondary cell to schedule the primary cell across carriers, the UE releases the cross-carrier scheduling of the primary cell by the secondary cell.

[0077] In one implementation, cross-carrier scheduling of the primary cell includes scheduling of a physical shared channel on the primary cell by a PDCCH of a secondary cell (SCell). The primary cell may include at least one of a primary cell (PCell) in a primary cell group or a primary cell (PSCell) in a secondary cell group. The physical shared channel on the primary cell includes at least one of a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) on the primary cell.

[0078] In the previous embodiment, cross-carrier scheduling of the primary cell by the secondary cell (also called SCell-schedule-PCell) is dynamically supported. When cross-carrier scheduling of the primary cell by the secondary cell is released, deactivated, indicated as dormant or not supported, the BD / CCE budget scaling factor (or cell weight factor) used to schedule the PCell in the PCell can be dynamically restored.

[0079] refer to Fig. 9 , the present disclosure describes various embodiments of a method 900, which includes some or all of the following steps: step 910: performing a shutdown of cross-carrier scheduling of a primary cell by a secondary cell for a user equipment (UE); and step 920: restoring, by the UE, a factor in the primary cell for scheduling the primary cell. The factor in the primary cell includes at least one of the following: a blind decoding / control channel element (BD / CCE) scaling factor; or a cell weight factor.

[0080] The various embodiments described in the present disclosure improve wireless communication technology and solve at least some of the problems / issues of previous systems, thereby bringing benefits. For example, in one embodiment, when SCell-schedule-PCell is deactivated or released, the BD / CCE budget scaling factor (or cell weight factor) used to schedule the PCell in the PCell is dynamically restored. This ensures that when the SCell supports the scheduling of the PCell, changes in the PDCCH capacity can be flexibly adapted. Restoring the BD / CCE budget for PCell self-scheduling through the dynamic release of the SCell-schedule-PCell can keep the scheduling flexibility unchanged.

[0081] In one implementation of various embodiments, the scaling factor of the BD / CCE in the PCell used to schedule the PCell is restored by adjusting the BD / CCE scaling factors (or cell weight factors) of the two scheduled cells of the PCell to implicitly indicate the release of the SCell-schedule-PCell.

[0082] In response to the factor being configured as (1, 0) for the PCell and the SCell, respectively, the UE may disable cross-carrier scheduling of the primary cell by the secondary cell to indicate that the BD / CCE scaling factor is restored.

[0083] For an example, the BD / CCE scaling factors (or cell weight factors) of the two scheduled cells of the PCell are configured and indicated in the DCI. In one implementation, the BD / CCE scaling factor may be configured / fixed as a 2-bit value, such as Figure 6 As shown. For example, when the 2-bit value is "01", the scaling factor of the BD / CCE of the PCell and the SCell is (0.5, 0.5), which indicates that the budget of the BD / CCE of the PCell used to schedule the PCell is 1 / 2 of the budget of the BD / CCE per cell, and the budget of the SCell used to schedule the PCell is 1 / 2 of the budget of the BD / CCE per cell. When the 2-bit value indicates 11, the scaling factor between the PCell and SCell BD / CCE is (1, 0), which indicates that the BD / CCE of the PCell is 1 times the BD / CCE per cell, and the BD / CCE of the SCell is 0 times the BD / CCE per cell, thereby implicitly releasing the SCell-schedule-PCell, which also means restoring the scaling factor of the BD / CCE in the PCell used to schedule the PCell.

[0084] In another implementation of various embodiments, SCell-schedule-PCell is released through the previous embodiment, and the scaling factor of the BD / CCE in the PCell used to schedule the PCell can also be restored.

[0085] The UE may disable cross-carrier scheduling of the primary cell by the secondary cell to indicate that the BD / CCE scaling factors are restored to (1, 0) for the PCell and SCell, respectively.

[0086] For example, when BWP switching, DCI or MAC CE indicates that dynamic SCell-schedule-PCell is not supported, the scaling factor of the BD / CCE budget for scheduling PCell in PCell can be implicitly restored, so that the scaling factors of PCell and SCell are (1, 0). Therefore, the BD / CCE budget of PCell is 1 times the BD / CCE budget of each cell, and the BD / CCE budget of SCell is 0 times the BD / CCE budget of each cell, thereby releasing SCell-schedule-PCell, which means that the scaling factor of the BD / CCE budget for scheduling PCell in PCell is restored.

[0087] In the previous embodiment, cross-carrier scheduling of the primary cell by the secondary cell (also called SCell-schedule-PCell) is dynamically supported. When cross-carrier scheduling of the primary cell by the secondary cell is released, deactivated, indicated as dormant or not supported, the non-fallback DCI in the PCell for scheduling the PCell can be dynamically restored.

[0088] In some wireless systems, when operating in SCell-schedule-PCell mode, only fallback DCI can be used for PCell self-scheduling, and only non-fallback DCI can be used for PCell PDSCH scheduling by SCell. Once SCell-schedule-PCell is disabled or dynamically released, the PDSCH of PCell can only be scheduled by the fallback DCI in PCell, so the system efficiency will be reduced. Therefore, it is beneficial to restore the non-fallback DCI in PCell for scheduling PCell.

[0089] refer to Fig.10 , the present disclosure describes various embodiments of method 1000, which includes part or all of the following steps: step 1010: executing, for a user equipment (UE), shutting down cross-carrier scheduling of a primary cell by a secondary cell; and step 1020, restoring, by the UE, non-fallback downlink control information (DCI) in the primary cell for scheduling the primary cell.

[0090] The various embodiments described in the present disclosure improve wireless communication technology and solve at least some problems / issues of previous systems, thereby bringing benefits. For example, in one embodiment, when the SCell is deactivated or released, the non-fallback DCI for scheduling the PCell on the PCell is dynamically restored. This ensures that when the SCell supports scheduling of the PCell, changes in PDCCH capacity can be flexibly adapted. Restoring the non-fallback DCI for self-scheduling on the PCell through the dynamic release of the SCell-schedule-PCell can keep the scheduling flexibility unchanged.

[0091] In one implementation of various embodiments, when the SCell-schedule-PCell is disabled or dynamically released, the primary cell may support non-fallback DCI by switching to a BWP configured with non-fallback DCI.

[0092] When the UE turns off the cross-carrier scheduling of the primary cell by the secondary cell, the UE can switch from the second BWP configured with fallback DCI to the first BWP configured with non-fallback DCI to restore the non-fallback DCP in the primary cell for scheduling the primary cell. In one implementation, the primary cell can be configured with a first BWP with a first search space index, and the first BWP can be configured with a non-fallback DCI. The primary cell can be configured with a second BWP with a second search space index, and the second BWI can be configured with a fallback DCI.

[0093] For example, the secondary cell (cell B) can be configured to support cross-carrier scheduling of the primary cell (cell A). Cell A is configured with a search space index = {0, 1, 2, 3} in the first BWP (BWP1), wherein a non-fallback DCI is configured in the search space (SS) (e.g., SS#3), and cell A is configured with a search space index = {10, 11, 12, 13} in the second BWP (BWP2), wherein a non-fallback DCI is configured in any search space. Cell B is configured with a search space index = {0, 1, 2 and 3} in the first BWP (BWP1), and a search space index = {10, 11, 12 and 13} in the second BWP (BWP2). In the case where the activated BWP of cell B is BWP2, the activated BWP of cell A is BWP2, and SCell-schedule-PCell is supported. When SCell-schedule-PCell is disabled or dynamically released (for example, SCell-schedule-PCell is not supported through BWP switching, or SCell-schedule-PCell is released through DCI or MAC CE), the primary cell can work on BWP2 with only fallback DCI. At this time, non-fallback DCI can be supported on the primary cell through BWP switching to BWP1 of the primary cell.

[0094] In one implementation of various embodiments, non-fallback DCI can be implicitly activated by disabling or releasing SCell-schedule-PCell, where when SCell-schedule-PCell is enabled or activated, the non-fallback DCI configured in at least one search space in the activated BWP on the primary cell is disabled or released.

[0095] In response to the UE turning off the cross-carrier scheduling of the primary cell by the secondary cell, the UE enables the non-fallback DCI in the BWP, and the non-fallback DCI in the primary cell for scheduling the primary cell can be restored. In one implementation, the primary cell can be configured with a BWP with a first search space index, and the BWP can be configured with non-fallback DCI. When the UE turns on the cross-carrier scheduling of the primary cell by the secondary cell, the non-fallback DCI can be disabled.

[0096] For example, the secondary cell (cell B) can be configured to support cross-carrier scheduling of the primary cell (cell A). Cell A is configured with search space index = {0, 1, 2, 3} in the first BWP (BWP1), where non-fallback DCI is configured in the SS (e.g., SS#3). Cell B is configured with search space index = {0, 1, 2 and 3} in the first BWP (BWP1), and with search space index = {10, 11, 12 and 13} in the second BWP (BWP2). In the case where the activated BWP of cell B is BWP1, the activated BWP of cell A is BWP1, where SCell-schedule-PCell is supported and non-fallback DCI is disabled. When SCell-schedule-PCell is disabled or dynamically released (for example, SCell-schedule-PCell through BWP switching is not supported, or SCell-schedule-PCell is released through DCI or MAC CE), the primary cell operates on BWP1 of the primary cell, which means that disabling or releasing SCell-schedule-PCell also implicitly enables non-fallback DCI in BWP1 to restore support for non-fallback DCI on the primary cell.

[0097] The present disclosure describes methods, apparatuses, and computer-readable media for wireless communication. The present disclosure solves the problem of scheduling a primary cell by a secondary cell. The methods, devices, and computer-readable media described in the present disclosure can facilitate the performance of wireless transmissions between user equipment and a base station, thereby improving efficiency and overall performance. The methods, devices, and computer-readable media described in the present disclosure can improve the overall efficiency of a wireless communication system.

[0098] References to features, advantages, or similar language in this specification do not imply that all features and advantages that may be achieved with the present solution should or are included in any single implementation thereof. Rather, language referring to features and advantages is understood to mean that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present solution. Thus, discussion of features and advantages and similar language throughout the specification may, but does not necessarily, refer to the same embodiment.

[0099] In addition, the described features, advantages, and characteristics of the present solution may be combined in any suitable manner in one or more embodiments. Based on the description herein, one of ordinary skill in the relevant art will recognize that the present solution may be practiced without one or more of the specific features or advantages of a particular embodiment. In other cases, additional features and advantages that may not be present in all embodiments of the present solution may be recognized in certain embodiments.

Claims

1. A method for wireless communication, comprising: For the user equipment UE, determining that the secondary cell SCell used for cross-carrier scheduling of the primary cell PCell is deactivated or dormant; as well as Recover a blind decoding / control channel element BD / CCE scaling factor used by the UE in the primary cell for scheduling the primary cell.

2. The method according to claim 1, wherein: The BD / CCE scaling factor used for scheduling the primary cell in the primary cell is restored to 1.

3. The method according to claim 2, wherein: The BD / CCE scaling factor used for scheduling the primary cell in the secondary cell is restored to 0.

4. A method for wireless communication, comprising: For the user equipment UE, determining that the secondary cell SCell used for cross-carrier scheduling of the primary cell PCell is deactivated or dormant; as well as restoring the non-fallback downlink control information DCI used by the UE in the primary cell for scheduling the primary cell, The primary cell is configured with a first bandwidth part BWP having a first search space index, and the first BWP is configured with the non-fallback DCI.

5. The method according to claim 4, wherein: The second BWP configured with the fallback DCI is switched to the first BWP configured with the non-fallback DCI to restore the non-fallback DCI used by the UE in the primary cell for scheduling the primary cell; and The primary cell is configured with the second BWP having a second search space index, and the second BWP is configured with the fallback DCI.

6. The method according to claim 4, wherein: The non-fallback DCI in the first BWP is enabled to restore the non-fallback DCI used by the UE in the primary cell for scheduling the primary cell; and When the secondary cell used to schedule the primary cell is activated, the non-fallback DCI is disabled.

7. A wireless communication device, comprising a processor and a memory, wherein the processor is configured to read a code from the memory and implement the method according to any one of claims 1 to 3.

8. A computer program product comprising computer readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the method according to any one of claims 4 to 6.

Images