Method and apparatus for DCI size alignment of scheduled cells with multiple scheduling cells

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method for downlink control information (DCI) size alignment of a scheduled cell with a plurality of scheduled cells includes receiving first information of a first field of a first DCI format when on a primary cell (PCell) and second information of a second field of the first DCI format when on a secondary cell (SCell). The method further includes determining a first size of the first DCI format on the PCell, a second size of the first DCI format on the SCell, and a first number of padding bits equal to an absolute difference between the first size and the second size. When the SCell is deactivated, a second size is determined based on a first reference downlink (DL) bandwidth portion (BWP) of the SCell. The method further includes receiving the first DCI format in a physical downlink control channel (PDCCH) reception on the PCell or the SCell.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly to aligning downlink control information (DCI) sizes of a scheduled cell and a plurality of scheduling cells in a wireless communication system. Background Art

[0002] 5G mobile communication technology defines a wide frequency band so that high transmission rates and new services are possible, and can be realized not only in "below 6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands called mmWave (millimeter wave) including 28 GHz and 39 GHz. In addition, it has been considered to implement 6G mobile communication technology (called super 5G system) in terahertz (THz) frequency bands (e.g., 95 GHz to 3 THz frequency bands) in order to achieve a transmission rate fifty times that of 5G mobile communication technology and an ultra-low latency one-tenth of that of 5G mobile communication technology.

[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC) and massive machine type communication (mMTC), continued standardization is underway on beamforming and massive MIMO for mitigating radio wave path loss and increasing radio wave transmission distance in mmWave, parameter sets supporting dynamic operation for efficient utilization of mmWave resources and time slot formats (e.g., operating multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding and decoding methods such as LDPC (low-density parity check) codes for large-scale data transmission and polar codes for highly reliable transmission of control information, L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.

[0004] Currently, in view of the services that 5G mobile communication technology is to support, there are ongoing discussions on improvements and performance enhancements of initial 5G mobile communication technology, and there is already physical layer standardization on technologies, such as V2X (Vehicle to Everything) for assisting autonomous vehicles in making driving decisions based on information sent by the vehicle about the location and status of the vehicle and for enhancing user convenience, NR-U (New Radio Unlicensed) for system operation designed to comply with various regulatory requirements in unlicensed bands, NR UE power saving, non-terrestrial network (NTN) as UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable, and positioning.

[0005] In addition, there is continuous standardization of air interface architecture / protocols for technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancement including conditional switching and DAPS (Dual Active Protocol Stack) switching, and two-step random access (NR's two-step RACH) for simplifying the random access process. There is also continuous standardization of system architecture / services for 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE location.

[0006] As 5G mobile communication systems are commercialized, the number of connected devices, which has been growing exponentially, will be connected to the communication network, and it is accordingly expected that enhanced functionality and performance of the 5G mobile communication systems and integrated operations of the connected devices will be necessary. To this end, new research related to extended reality (XR) is arranged for efficiently supporting AR (augmented reality), VR (virtual reality), MR (mixed reality), etc., improving 5G performance and reducing complexity by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.

[0007] In addition, such development of 5G mobile communication systems will serve as the basis for not only developing new waveforms for providing coverage in the terahertz band for 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO) array antennas and massive antennas, metamaterial-based lenses and antennas for improving terahertz band signal coverage, and high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum) and RIS (Reconfigurable Intelligent Surface), but also developing full-duplex technology for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for utilizing satellites and AI (artificial intelligence) to achieve system optimization from the design stage and internalize end-to-end AI support functions, and next-generation distributed computing technology for implementing services at a complexity level that exceeds the operating capability limits of UEs by utilizing ultra-high performance communication and computing resources. Summary of the invention

[0008] Technical issues

[0009] Currently, it is necessary to enhance the alignment of DCI sizes between a scheduled cell and multiple scheduling cells in a wireless communication system.

[0010] Solution to the problem

[0011] The present disclosure relates to a wireless communication system, and more particularly, to aligning DCI sizes of a scheduled cell and a plurality of scheduling cells in the wireless communication system.

[0012] In one embodiment, a method is provided. The method includes: receiving: first information of a first field of a first DCI format when a first physical downlink control channel (PDCCH) providing a first DCI format is received on a primary cell (PCell), and second information of a second field of the first DCI format when a second PDCCH providing the first DCI format is received on a secondary cell (SCell). The first DCI format schedules a physical uplink shared channel (PUSCH) transmission on the PCell. The method also includes: determining: a first size of the first DCI format when a first PDCCH providing the first DCI format is received on the PCell, a second size of the first DCI format when a second PDCCH providing the first DCI format is received on the SCell, and a first number of padding bits equal to the absolute difference between the first size and the second size. When the SCell is deactivated, the second size is determined based on a first reference downlink (DL) bandwidth part (BWP) of the SCell. The method also includes receiving: a first DCI format in a first PDCCH reception on a PCell, wherein, when the first size is less than the second size, the first DCI format includes a first number of padding bits attached to multiple bits of the first field, or a first DCI format in a second PDCCH reception on a SCell, wherein, when the second size is less than the first size, the first DCI format includes a first number of padding bits attached to multiple bits of the second field.

[0013] In another embodiment, a user equipment (UE) is provided. The UE includes a transceiver configured to receive, when a first PDCCH providing a first DCI format is received on a PCell, first information of a first field of the first DCI format, and when a second PDCCH providing the first DCI format is received on an SCell, second information of a second field of the first DCI format. The first DCI format schedules PUSCH transmission on the PCell. The UE also includes a processor operably connected to the transceiver. The processor is configured to determine: a first size of the first DCI format when a first PDCCH providing the first DCI format is received on a PCell, a second size of the first DCI format when a second PDCCH providing the first DCI format is received on an SCell, and a first number of padding bits equal to the absolute difference between the first size and the second size. When the SCell is deactivated, the second size is determined based on a first reference DL BWP for the SCell. The transceiver is also configured to receive: a first DCI format in a first PDCCH reception on a PCell, wherein, when the first size is less than the second size, the first DCI format includes a first number of padding bits appended to a plurality of bits of the first field, or a first DCI format in a second PDCCH reception on a SCell, wherein, when the second size is less than the first size, the first DCI format includes a first number of padding bits appended to a plurality of bits of the second field.

[0014] In another embodiment, a base station is provided. The base station includes a transceiver configured to send: first information of a first field of a first DCI format when a first PDCCH providing a first DCI format is transmitted on a PCell, and second information of a second field of a first DCI format when a second PDCCH providing a first DCI format is transmitted on an SCell. The first DCI format schedules PUSCH reception on the PCell. The base station also includes a processor operably connected to the transceiver. The processor is configured to determine: a first size of the first DCI format when a first PDCCH providing a first DCI format is transmitted on a PCell, a second size of the first DCI format when a second PDCCH providing a first DCI format is transmitted on an SCell, and a first number of padding bits equal to the absolute difference between the first size and the second size. When the SCell is deactivated, the second size is determined based on the first reference DL BWP of the SCell. The transceiver is also configured to send: a first DCI format in a first PDCCH transmission on a PCell, wherein, when the first size is less than the second size, the first DCI format includes a first number of padding bits appended to a plurality of bits of the first field; or a first DCI format in a second PDCCH transmission on a SCell, wherein, when the second size is less than the first size, the first DCI format includes a first number of padding bits appended to a plurality of bits of the second field.

[0015] Other technical features may be apparent to those skilled in the art from the following drawings, descriptions and claims.

[0016] Before the following detailed description, it may be advantageous to set forth the definitions of certain words and phrases used throughout this patent document. The term "coupling" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are in physical contact with each other. The terms "send", "receive" and "communication" and their derivatives cover both direct and indirect communication. The terms "include" and "comprise" and their derivatives mean including but not limited to. The term "or" is inclusive, meaning and / or. The phrase "associated with ... " and its derivatives mean including, included in ..., interconnected with ..., including, included in ..., connected to or with ..., connected to or with ..., coupled to or with ..., can communicate with ..., collaborate with ..., interlace, juxtapose, approach, bind to or with ..., bind, have, have the property of ..., have to or with ..., etc. The term "controller" means any device, system or part thereof that controls at least one operation. Such a controller can be implemented in hardware or a combination of hardware and software and / or firmware. The function associated with any particular controller can be centralized or distributed, whether local or remote. The phrase "at least one of" when used with a list of items means that different combinations of one or more of the listed items can be used, and that only one of the items in the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0017] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or a portion thereof that are suitable for implementation in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disk (DVD) or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media in which data can be permanently stored and media in which data can be stored and rewritten later, such as rewritable optical disks or erasable memory devices.

[0018] Definitions for certain other words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals represent like parts:

[0020] Figure 1 An example of a wireless network according to an embodiment of the present disclosure is shown;

[0021] Figure 2 An example of a gNB according to an embodiment of the present disclosure is shown;

[0022] Figure 3 An example of a UE according to an embodiment of the present disclosure is shown;

[0023] Figure 4 illustrates examples of wireless transmit and receive paths according to the present disclosure;

[0024] Figure 5 illustrates examples of wireless transmit and receive paths according to the present disclosure;

[0025] Figure 6 A flowchart showing a process for a UE to align the size of a DCI format for scheduling on a primary cell from a primary cell or from a secondary cell when the UE monitors a PDCCH to detect a DCI format size greater than "3+1" according to an embodiment of the present disclosure;

[0026] Figure 7 A flowchart showing a process for a UE to determine the size of a DCI format for scheduling on a PCell via PDCCH reception on a SCell when the SCell is deactivated for the UE or the UE has a dormant active DL BWP on the SCell according to an embodiment of the present disclosure;

[0027] Figure 8 A block diagram showing a terminal (or user equipment (UE)) according to an embodiment of the present disclosure; and

[0028] Fig. 9 A block diagram of a base station (BS) according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0029] Fifth generation (5G) or New Radio (NR) mobile communications have been gathering increasing momentum recently with all the global technical activities from industry and academia regarding various candidate technologies. Candidate enablers for 5G / NR mobile communications include massive antenna technologies from traditional cellular frequency bands up to high frequencies to provide beamforming gain and support increased capacity, new waveforms (e.g., new radio access technologies (RATs)) to flexibly accommodate various services / applications with different requirements, new multiple access schemes to support massive connections, etc.

[0030] Discussed below Figures 1 to 9 The various embodiments used to describe the principles of the present disclosure in this patent document are illustrative only and should not be interpreted in any way to limit the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0031] The following documents are incorporated by reference into the present disclosure as if fully set forth herein: 3GPP TS 38.133 v17.2.0, “NR; Requirements for support of radio resource management”; 3GPP TS 38.211 v17.2.0, “NR; Physical channels and modulation”; 3GPP TS 38.212 v17.2.0, “NR; Multiplexing and Channel coding”; 3GPP TS 38.213 v17.2.0, “NR; Physical Layer Procedures for Control”; 3GPP TS 38.214 v17.2.0, “NR; Physical Layer Procedures for Data”; 3GPP TS 38.321 v17.1.0, “NR; Medium ACCES Control (MAC) protocol specification”, 3GPP TS 38.331 v17.1.0, “NR; Radio Resource Control (RRC) protocol specification"; and 3GPP TS 38.300Rel-17v17.1.0, "NR; NR and NG-RAN Overall Description; Stage 2"; and 3GPP TR 38.306v17.1.0, "NR; User Equipment (UE) radioaCCEs capabilities".

[0032] In order to meet the demand for wireless data traffic that has increased since the deployment of 4G communication systems and to realize various vertical applications, 5G / NR communication systems have been developed and are currently being deployed. 5G / NR communication systems are considered to be implemented in higher frequency (mmWave) bands (e.g., 28 GHz or 60 GHz bands) to achieve higher data rates, or in lower frequency bands (e.g., 6 GHz) to achieve robust coverage and mobility support. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed in 5G / NR communication systems.

[0033] In addition, in the 5G / NR communication system, system network improvements are being developed based on advanced small cells, cloud radio access network (RAN) ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, collaborative communications, coordinated multi-point (CoMP), receiving-end interference cancellation, etc.

[0034] The discussion of 5G systems and frequency bands associated therewith is for reference, as certain embodiments of the present disclosure may be implemented in 5G systems. However, the present disclosure is not limited to 5G systems or frequency bands associated therewith, and embodiments of the present disclosure may be used in conjunction with any frequency band. For example, aspects of the present disclosure may also be applied to 5G communication systems, 6G, or even later deployments that may use terahertz (THz) frequency bands.

[0035] The following Figure 1-3 Various embodiments are described that are implemented in a wireless communication system and utilizing Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) communication techniques. Figure 1-3 The description is not meant to imply physical or architectural limitations to the manner in which different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any suitably arranged communications system.

[0036] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown. Figure 1 The embodiment of the wireless network shown is for illustration only. Other embodiments of the wireless network 100 may be used without departing from the scope of the present disclosure.

[0037] like Figure 1As shown, the wireless network includes gNB 101 (e.g., base station, BS), gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one network 130 (such as the Internet, a proprietary Internet Protocol (IP) network, or other data network).

[0038] gNB 102 provides wireless broadband access to network 130 for a first plurality of user equipment (UE) within coverage area 120 of gNB 102. The first plurality of UEs includes UE 111, which may be located in a small business; UE 112, which may be located in an enterprise; UE 113, which may be a WiFi hotspot; UE 114, which may be located in a first residence; UE 115, which may be located in a second residence; and UE 116, which may be a mobile device such as a cellular phone, a wireless laptop, a wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 for a second plurality of UEs within coverage area 125 of gNB 103. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of gNBs 101-103 may communicate with each other and with UEs 111-116 using 5G / NR, Long Term Evolution (LTE), Long Term Evolution-Advanced (LTE-A), WiMAX, WiFi, or other wireless communication technologies.

[0039] Depending on the network type, the term "base station" or "BS" may refer to any component (or collection of components) configured to provide wireless access to a network, such as a transmission point (TP), a transmission-reception point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macro cell, a femto cell, a WiFi access point (AP), or other wireless enabling devices. The base station may provide wireless access according to one or more wireless communication protocols (e.g., 5G / NR Third Generation Partnership Project (3GPP) NR, Long Term Evolution (LTE), LTE Advanced (LTE-A), High Speed ​​Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc.). For convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. In addition, depending on the network type, the term "user equipment" or "UE" may refer to any component, such as a "mobile station", "subscriber station", "remote terminal", "wireless terminal", "reception point", or "user equipment". For convenience, the terms "user equipment" and "UE" are used in this patent document to refer to a remote wireless device that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered a fixed device (such as a desktop computer or vending machine).

[0040] The dashed lines illustrate the approximate extents of coverage areas 120 and 125, which are shown as approximately circular for purposes of illustration and explanation only. It should be clearly understood that coverage areas associated with a gNB, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the gNB and variations in the radio environment associated with natural and man-made obstacles.

[0041] As described in more detail below, one or more of the UEs 111-116 include circuitry, programming, or a combination thereof for aligning a DCI size of a scheduled cell with a plurality of scheduling cells in a wireless communication system. In certain embodiments, one or more of the gNBs 101-103 include circuitry, programming, or a combination thereof for aligning a DCI size of a scheduled cell with a plurality of scheduling cells in a wireless communication system.

[0042] although Figure 1 An example of a wireless network is shown, but Figure 1 Various changes may be made. For example, the wireless network may include any number of gNBs and any number of UEs in any suitable arrangement. In addition, gNB 101 may communicate directly with any number of UEs and provide those UEs with wireless broadband access to network 130. Similarly, each gNB 102-103 may communicate directly with network 130 and provide the UEs with direct wireless broadband access to network 130. In addition, gNBs 101, 102, and / or 103 may provide access to other or additional external networks, such as an external telephone network or other type of data network.

[0043] Figure 2 An example gNB 102 is shown according to an embodiment of the present disclosure. Figure 2 The embodiment of the gNB 102 shown in FIG. is for illustration only, and Figure 1 gNBs 101 and 103 may have the same or similar configurations. However, gNBs have a variety of configurations, and Figure 2 The scope of the present disclosure is not limited to any particular implementation of the gNB.

[0044] like Figure 2 As shown, the gNB 102 includes multiple antennas 205a-205n, multiple transceivers 210a-210n, a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0045] The transceivers 210a-210n receive incoming RF signals from the antennas 205a-205n, such as signals sent by UEs in the network 100. The transceivers 210a-210n downconvert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are processed by receive (RX) processing circuits in the transceivers 210a-210n and / or the controller / processor 225, which generate processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. The controller / processor 225 may further process the baseband signals.

[0046] Transmit (TX) processing circuitry in the transceivers 210a-210n and / or the controller / processor 225 receives analog or digital data (such as voice data, web data, email, or interactive video game data) from the controller / processor 225. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The transceivers 210a-210n up-convert the baseband or IF signal to an RF signal that is transmitted via the antennas 205a-205n.

[0047] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 225 may control the reception of UL channel signals and the transmission of DL channel signals by the transceivers 210a-210n according to well-known principles. The controller / processor 225 may also support additional functionality, such as more advanced wireless communication functionality. For example, the controller / processor 225 may support beamforming or directional routing operations, in which outgoing / incoming signals from / to multiple antennas 205a-205n are weighted differently to effectively direct the outgoing signals in a desired direction. The controller / processor 225 may support any of a wide variety of other functionality in the gNB 102.

[0048] The controller / processor 225 is also capable of executing programs and other processes residing in the memory 230, such as a process for aligning the DCI size of a scheduled cell with multiple scheduling cells in a wireless communication system. The controller / processor 225 can move data into or out of the memory 230 as required by the executed process.

[0049] The controller / processor 225 is also coupled to a backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or via a network. The interface 235 may support communication via any suitable wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (such as a cellular communication system supporting 5G / NR, LTE, or LTE-A), the interface 235 may allow the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, the interface 235 may allow the gNB 102 to communicate with a larger network (such as the Internet) via a wired or wireless local area network or via a wired or wireless connection. The interface 235 includes any suitable structure that supports communication via a wired or wireless connection, such as Ethernet or a transceiver.

[0050] Memory 230 is coupled to controller / processor 225. A portion of memory 230 may include RAM, and another portion of memory 230 may include flash memory or other ROM.

[0051] although Figure 2 An example of a gNB 102 is shown, but the Figure 2 For example, gNB 102 may include any number of Figure 2 Each component shown in . In addition, Figure 2 The various components in may be combined, further subdivided, or omitted, and additional components may be added according to specific needs.

[0052] Figure 3 An example UE 116 is shown in accordance with an embodiment of the present disclosure. Figure 3 The embodiment of UE 116 shown is for illustration only, and Figure 1 UEs 111-115 may have the same or similar configurations. However, UEs have a variety of configurations, and Figure 3 The scope of the present disclosure is not limited to any particular implementation of the UE.

[0053] like Figure 3 As shown, UE 116 includes antenna 305, transceiver 310, and microphone 320. UE 116 also includes speaker 330, processor 340, input / output (I / O) interface (IF) 345, input 350, display 355, and memory 360. Memory 360 includes operating system (OS) 361 and one or more applications 362.

[0054] Transceiver 310 receives incoming RF signals from antenna 305 transmitted by a gNB of network 100. Transceiver 310 downconverts the incoming RF signals to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is processed by RX processing circuitry in transceiver 310 and / or processor 340, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry transmits the processed baseband signal to speaker 330 (such as for voice data) or is processed by processor 340 (such as for web browsing data).

[0055] The TX processing circuit in the transceiver 310 and / or the processor 340 receives analog or digital voice data from the microphone 320, or receives other outgoing baseband data (such as web data, email, or interactive video game data) from the processor 340. The TX processing circuit encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The transceiver 310 up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna 305.

[0056] The processor 340 may include one or more processors or other processing devices and execute the OS 361 stored in the memory 360 to control the overall operation of the UE 116. For example, the processor 340 may control the transceiver 310 to receive DL channel signals and transmit UL channel signals according to well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0057] The processor 340 can also execute other processes and programs residing in the memory 360, such as a process for aligning the DCI size of a scheduled cell with multiple scheduling cells in a wireless communication system.

[0058] Processor 340 may move data into or out of memory 360 as required by the processes being executed. In some embodiments, processor 340 is configured to execute applications 362 based on OS 361 or in response to signals received from a gNB or operator. Processor 340 is also coupled to I / O interface 345, which provides UE 116 with the ability to connect to other devices such as laptops and handheld computers. I / O interface 345 is the communication path between these accessories and processor 340.

[0059] The processor 340 is also coupled to an input 350 and a display 355m, including, for example, a touch screen, a keypad, etc., which an operator of the UE 116 can use to enter data into the UE 116. The display 355 may be a liquid crystal display, a light emitting diode display, or other display capable of presenting text and / or at least limited graphics, such as from a website.

[0060] Memory 360 is coupled to processor 340. A portion of memory 360 may include random access memory (RAM), and another portion of memory 360 may include flash memory or other read-only memory (ROM).

[0061] although Figure 3 An example of UE 116 is shown, but the Figure 3 For example, they can be combined, further subdivided, or omitted Figure 3 , and additional components may be added as needed. As a specific example, processor 340 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, transceiver 310 may include any number of transceivers and signal processing chains, and may be connected to any number of antennas. In addition, although Figure 3 The UE 116 is shown configured as a mobile phone or smart phone, but the UE may be configured to operate as other types of mobile or stationary devices.

[0062] Figure 4 and Figure 5 Example wireless transmit and receive paths according to the present disclosure are shown. In the following description, transmit path 400 may be described as being implemented in a gNB (such as gNB 102) and receive path 500 may be described as being implemented in a UE (such as UE 116). However, it is understood that receive path 500 may be implemented in a gNB and transmit path 400 may be implemented in a UE. In some embodiments, receive path 500 is configured to support DCI size alignment of a scheduled cell with multiple scheduling cells in a wireless communication system.

[0063] like Figure 4 The transmit path 400 shown includes a channel coding and modulation block 405, a serial to parallel (S to P) block 410, an inverse fast Fourier transform (IFFT) block of size N 415, a parallel to serial (P to S) block 420, an add cyclic prefix block 425, and an upconverter (UC) 430. Figure 5The receive path 500 shown includes a downconverter (DC) 555, a remove cyclic prefix block 560, a serial to parallel (S to P) block 565, a size N fast Fourier transform (FFT) block 570, a parallel to serial (P to S) block 575, and a channel decoding and demodulation block 580.

[0064] like Figure 4 As shown, the channel coding and modulation block 405 receives a set of information bits, applies a codec (such as a low-density parity-check (LDPC) codec), and modulates the input bits (such as using quadrature phase-shift keying (QPSK) or quadrature amplitude modulation (QAM)) to generate a frequency-domain modulation symbol sequence.

[0065] Serial to parallel block 410 converts (e.g., demultiplexes) the serial modulation symbols into parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used in gNB 102 and UE 116. Size N IFFT block 415 performs an IFFT operation on the N parallel symbol streams to generate a time domain output signal. Parallel to serial block 420 converts (e.g., multiplexes) the parallel time domain output symbols from Size N IFFT block 415 to generate a serial time domain signal. Add cyclic prefix block 425 inserts a cyclic prefix to the time domain signal. Up converter 430 modulates (e.g., upconverts) the output of add cyclic prefix block 425 to RF frequency for transmission via a wireless channel. The signal may also be filtered at baseband before conversion to RF frequency.

[0066] The RF signal transmitted from gNB 102 reaches UE 116 after passing through the wireless channel, and an operation opposite to that at gNB 102 is performed at UE 116.

[0067] like Figure 5 As shown, the down converter 555 down-converts the received signal to the baseband frequency, and the cyclic prefix removal block 560 removes the cyclic prefix to generate a serial time domain baseband signal. The serial to parallel block 565 converts the time domain baseband signal to a parallel time domain signal. The size N FFT block 570 performs an FFT algorithm to generate N parallel frequency domain signals. The parallel to serial block 575 converts the parallel frequency domain signals into a sequence of modulated data symbols. The channel decoding and demodulation block 580 demodulates and decodes the modulation symbols to recover the original input data stream.

[0068] Each of gNBs 101-103 may implement Figure 4 The transmission path 400 shown is similar to the transmission to UE 111-116 in the downlink and can be implemented as follows Figure 5Receive path 500 is shown, which is similar to receiving from UE 111-116 in the uplink. Similarly, each of UE 111-116 can implement transmit path 400 for transmitting to gNB 101-103 in the uplink, and can implement receive path 500 for receiving from gNB 101-103 in the downlink.

[0069] Figure 4 and Figure 5 Each component in may be implemented using hardware only or a combination of hardware and software / firmware. As a specific example, Figure 4 and Figure 5 At least some components in can be implemented in software, while other components can be implemented by configurable hardware or a mixture of software and configurable hardware. For example, FFT block 570 and IFFT block 415 can be implemented as configurable software algorithms, where the value of size N can be modified according to the implementation.

[0070] In addition, although described as using FFT and IFFT, this is for illustration only and may not be construed as limiting the scope of the present disclosure. Other types of transforms may be used, such as discrete Fourier transform (DFT) and inverse discrete Fourier transform (IDFT) functions. It will be appreciated that for DFT and IDFT functions, the value of variable N may be any integer (e.g., 1, 2, 3, 4, etc.), while for FFT and IFFT functions, the value of variable N may be any integer (e.g., 1, 2, 4, 8, 16, etc.) that is a power of 2.

[0071] although Figure 4 and Figure 5 An example of a wireless transmit and receive path is shown, but the Figure 4 and Figure 5 For example, they can be combined, further subdivided, or omitted Figure 4 and Figure 5 There are various components in it, and additional components can be added according to specific needs. In addition, Figure 4 and Figure 5 It is intended to illustrate examples of the types of transmit and receive paths that may be used in a wireless network. Any other suitable architecture may be used to support wireless communications in a wireless network.

[0072] The present disclosure considers a scheduled cell, such as a primary cell (PCell), and multiple scheduling cells for a UE, such as a PCell and a secondary cell (SCell). For the same DCI format that can be used to schedule the UE on the scheduled cell from multiple scheduling cells, the size of the DCI format needs to be the same on the multiple scheduling cells, otherwise the total number of sizes of the DCI formats used for scheduling on the scheduled cell may exceed a predetermined maximum number of sizes of DCI formats that may be predetermined in the specification of the system operation or indicated by the UE as a capability.

[0073] For example, when the network supports coexistence of LTE radio access technology (RAT) and NR RAT on PCell, the scheduled cell has multiple scheduling cells related to the operation of dynamic spectrum sharing (DSS) of PCell. For the sake of simplicity of description, the present disclosure regards PCell as a scheduled cell, and regards PCell and SCell as scheduling cells. The embodiments of the present disclosure are applicable to any cell as a scheduled cell, and to any number of cells, and to any cell as a scheduling cell. The scheduling SCell may also be referred to as a special secondary cell or sSCell.

[0074] When PCell is a scheduled cell with two scheduling cells for the UE, since scheduling is applied to the same scheduled cell (PCell), the UE expects the DCI formats used for scheduling on the PCell from two different scheduling cells (PCell and SCell) to have the same size. For example, the size of DCI format 0_1 ​​used for scheduling on the PCell can be the same regardless of whether DCI format 0_1 ​​is provided by the first PDCCH reception on the PCell or the second PDCCH reception on the SCell.

[0075] As described in TS 38.213 for NR operation, the UE expects to monitor PDCCH candidates of up to 4 sizes of DCI formats, including up to 3 sizes of DCI formats and a CRC scrambled by the C-RNTI of each serving / scheduled cell. The UE counts the number of sizes of DCI formats per serving cell based on the number of configured PDCCH candidates in the corresponding search space set for the corresponding active DL BWP. For brevity, the above requirement may be referred to as a "3+1" DCI size budget or a "3+1" rule. When applicable, the UE performs zero padding on one or more DCI formats, as described in 38.212, in order to meet the "3+1" DCI size budget.

[0076] The first issue is the process of determining that the UE satisfies both: (i) a DCI size budget, such as the "3+1" rule for PCell as the scheduled cell, and (ii) size alignment of DCI formats between PCell and SCell when the DCI format is used for scheduling on PCell from both PCell and SCell. For example, the UE aligns both the size of DCI format 1_2 for PDCCH reception on PCell and the size of DCI format 1_2 for PDCCH reception on SCell to a first size for scheduling on PCell. Similarly, the UE aligns both the size of DCI format 0_2 for PDCCH reception on PCell and the size of DCI format 0_2 for PDCCH reception on SCell to a second size for scheduling on PCell. If the first size is different from the second size (e.g., the first size is larger than the second size) and exceeds the "3+1" DCI size budget, the UE needs to align the sizes of DCI format 0_2 and DCI format 1_2 for scheduling on the PCell (e.g., zero-pad DCI format 0_2 to achieve the same size as DCI format 1_2) in order to meet the "3+1" DCI size budget.

[0077] Such an operation is referred to as cross-cell DCI size alignment in the present disclosure. Therefore, it is necessary to determine the cross-cell DCI size alignment of the DCI format, where the corresponding PDCCH is monitored by the UE on both the PCell and the SCell for scheduling on the PCell. For example, the UE needs to apply such DCI size alignment to the DCI format on both the PCell and the SCell.

[0078] The second issue is the cross-cell DCI size alignment between PCell and SCell for scheduling by UE on PCell when SCell is a deactivated SCell for UE or UE has an active DL BWP as a dormant BWP on SCell. In this case, the UE does not have an active DL BWP (in case of SCell deactivation) or the active DL BWP is not used for PDCCH monitoring (in case of active dormant BWP on SCell) Therefore, the UE needs to determine the DL BWP of the SCell for DCI size determination or cross-cell DCI size alignment between PCell and SCell for scheduling on PCell.

[0079] Therefore, the UE is required to simultaneously meet both: (i) DCI size budget, such as the "3+1" rule for PCell as the scheduled cell, and (ii) cross-cell DCI size alignment between PCell and SCell for scheduling on PCell.

[0080] The UE is also required to determine a reference DL BWP for DCI size determination or cross-cell DCI size alignment between PCell and SCell for scheduling on PCell when the SCell is a deactivated SCell for the UE or an active DL BWP on the SCell for the UE is a dormant BWP.

[0081] When the UE is configured with scheduling on the primary cell from the primary cell and from the secondary cell, the UE may perform an initial cross-cell DCI size alignment (between PCell and SCell) before zero padding for the "3+1" DCI size budget. In this case, the UE determines the same size for the same DCI format on the PCell and SCell. However, if the satisfaction of the DCI size budget "3+1" for the PCell (as the scheduled cell) requires additional DCI size alignment that results in a change in the size of the DCI format for scheduling on the PCell, this additional DCI size alignment needs to be applied to the DCI formats on both the PCell and the SCell. When the UE performs zero padding before cross-cell DCI size alignment as described in TS 38.212 to meet the "3+1" DCI size budget, this operation of having two stages of cross-cell DCI size alignment between the PCell and the SCell for scheduling on the PCell may also be necessary. Therefore, the order of the operations is not important.

[0082] When the UE is configured with scheduling on a primary cell from a PCell and from a SCell, and the SCell is deactivated for the UE, the UE determines the size of the DCI format for scheduling on the PCell from the SCell based on a first reference BWP of the SCell, such as the BWP provided by firstActiveDownlinkBWP. When the active DL BWP for the UE on the SCell is a dormant BWP, the UE may determine the size of the DCI format for scheduling on the PCell from the SCell based on a second reference BWP of the SCell, such as the BWP provided by firstOutsideActiveTimeBWP or firstWithinActiveTimeBWP. In one example, the first reference BWP may be the same as the second reference BWP, for example, the UE may use the BWP on the SCell provided by firstActiveDownlinkBWP when the SCell is deactivated for the UE and when the UE has an active dormant BWP on the SCell. In another example, the UE requires the first reference BWP but not the second reference BWP, and the UE determines the size of the DCI format for scheduling from the SCell based on the dormant BWP.

[0083] In one embodiment, cross-cell DCI size alignment in the presence of the "3+1" rule is provided.

[0084] In one embodiment, for a UE configured with scheduling from SCell on PCell (in addition to self-scheduling on PCell), in order to simultaneously meet: (1) the "3+1" DCI size budget of PCell, and (2) size alignment of the same DCI format (such as DCI format 0_1 / 1_1 / 0_2 / 1_2) for scheduling on PCell provided by PDCCH reception on PCell or SCell, the UE first matches the DCI formats (associated with UE-specific search space (USS) sets) on the two scheduling cells (PCell and SCell) for scheduling on PCell in size, and then, when the "3+1" DCI size budget of PCell needs to be achieved, the same zero padding is applied to the same DCI format (such as DCI format 0_1 ​​or DCI format 1_1) on PCell and SCell for scheduling on PCell so as to align the corresponding sizes of the DCI formats on PCell and SCell for scheduling on PCell with another DCI format on PCell and SCell for scheduling on PCell.

[0085] In one embodiment, for a UE configured with scheduling from an SCell on a PCell and the SCell is deactivated for the UE or the UE has a dormant active DL BWP on the SCell, the UE determines a size alignment process for a DCI format for scheduling on the PCell based on a reference DL BWP on the SCell. The reference BWP on the SCell may be the first active DL BWP, or a BWP outside the first active time, or a BWP within the first active time, or an initial DL BWP, or a default BWP, etc. Compared to the case where the active DL BWP on the SCell is the dormant DL BWP of the UE, the reference BWP may be the same or different for the case where the UE's SCell is deactivated.

[0086] When the UE is configured with scheduling on the primary cell from the primary cell and from the secondary cell, the UE may perform an initial cross-cell DCI size alignment (between the PCell and the SCell) before zero padding for the "3+1" DCI size budget. In this case, the UE determines the same size for the same DCI format on the PCell and the SCell. However, if the satisfaction of the DCI size budget "3+1" for the PCell (as the scheduled cell) requires additional DCI size alignment that results in a change in the size of the DCI format for scheduling on the PCell, this additional DCI size alignment needs to be applied to the DCI formats on both the PCell and the SCell. This operation of cross-cell DCI size alignment with two stages between the PCell and the SCell for scheduling on the PCell may also be necessary when the UE performs zero padding before cross-cell DCI size alignment as described in TS 38.212 to satisfy the "3+1" DCI size budget. Therefore, the order of the operations is not important.

[0087] When the UE is configured with scheduling on a primary cell from a PCell and from an SCell, and the SCell is deactivated for the UE, the UE determines the size of the DCI format for scheduling on the PCell from the SCell based on the first reference BWP of the SCell (such as the BWP provided by firstActiveDownlinkBWP). When the active DL BWP for the UE on the SCell is a dormant BWP, the UE may determine the size of the DCI format for scheduling on the PCell from the SCell based on the second reference BWP of the SCell (such as the BWP provided by firstOutsideActiveTimeBWP or firstWithinActiveTimeBWP).

[0088] In one example, the first reference BWP may be the same as the second reference BWP, for example, when the SCell is deactivated for the UE and when the UE has an active dormant BWP on the SCell, the UE may use the BWP on the SCell provided by firstActiveDownlinkBWP. In another example, the UE requires the first reference BWP but not the second reference BWP, and the UE determines the DCI format size for scheduling on the PCell from the SCell based on the dormant BWP.

[0089] In one embodiment, cross-cell DCI size alignment in the presence of the "3+1" rule is provided.

[0090] In one embodiment, for a UE configured with scheduling on PCell from SCell (in addition to self-scheduling on PCell), in order to simultaneously meet: (1) the "3+1" DCI size budget for PCell, and (2) size alignment of the same DCI format (such as DCI format 0_1 / 1_1 / 0_2 / 1_2) for scheduling on PCell provided by PDCCH reception on PCell or SCell, the UE first matches the DCI formats (associated with USS sets) on the two scheduling cells (PCell and SCell) for scheduling on PCell in size, and then, when the "3+1" DCI size budget for PCell needs to be achieved, the same zero padding is applied to the same DCI format (such as DCI format 0_1 ​​or DCI format 1_1) on PCell and SCell for scheduling on PCell so as to align the corresponding sizes of the DCI formats on PCell and SCell for scheduling on PCell with another DCI format on PCell and SCell for scheduling on PCell.

[0091] In one embodiment, for a UE configured with scheduling on a PCell from an SCell and the SCell is deactivated for the UE or the UE has a dormant active DL BWP on the SCell, the UE determines a size alignment process for a DCI format for scheduling on the PCell based on a reference DL BWP on the SCell. The reference BWP on the SCell may be the first active DL BWP, or the BWP outside the first active time, or the BWP within the first active time, or the initial DL BWP, or the default BWP, etc. Compared to the case where the active DL BWP on the SCell is the dormant DL BWP of the UE, the reference BWP may be the same or different for the case where the UE's SCell is deactivated.

[0092] Throughout this disclosure, the term "configuration" or "higher layer configuration" and variations thereof (such as "configured", etc.) are used to refer to one or more of: system information signaling such as through a MIB or SIB (such as SIB1), common or cell-specific higher layer / RRC signaling, or dedicated or UE-specific or BWP-specific higher layer / RRC signaling.

[0093] In carrier aggregation (CA), two or more component carriers (CCs) corresponding to corresponding two or more serving cells are aggregated. A UE can simultaneously receive or transmit on one or more cells according to its capabilities: (1) A UE with a single timing advance capability for CA can simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells sharing the same timing advance (multiple serving cells grouped in one TAG); (2) A UE with multiple timing advance capabilities for CA can simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells with different timing advances (multiple serving cells grouped in multiple TAGs). NG-RAN ensures that each TAG contains at least one serving cell; and (3) A UE without CA capability can receive on a single CC and transmit on a single CC corresponding to only one serving cell (one serving cell in one TAG).

[0094] CA is supported for both contiguous and non-contiguous CCs in frequency. When CA is deployed, frame timing and SFN are aligned across cells that may be aggregated, or an offset of a multiple of the timeslot between PCell / PSCell and SCell is configured to the UE. The maximum number of CCs configured for a UE is, for example, 16 for DL ​​and 16 for UL.

[0095] When CA is configured for a UE, the UE has only one RRC connection with the network. One serving cell provides NAS mobility information upon RRC connection establishment / reestablishment / handover, and one serving cell provides security input upon RRC connection establishment / handover. This cell is called a PCell. Depending on the UE capabilities, an SCell can be configured to form a serving cell set together with the PCell. Therefore, the serving cell set configured for the UE includes one PCell and one or more SCells.

[0096] Reconfiguration, addition and removal of SCells can be performed via RRC. The network can also add, remove, keep or reconfigure SCells for use with the target PCell at intra-NR handover and during connection recovery from RRC_INACTIVE. When adding a new SCell, dedicated RRC signaling is used to send all required system information for the SCell, i.e., the UE does not need to obtain broadcast system information directly from the SCell when in connected mode.

[0097] In order to achieve reduced UE battery consumption when CA is configured, an activation / deactivation mechanism for cells is supported. When a SCell is deactivated, the UE does not need to receive the corresponding PDCCH or PDSCH, cannot send in the corresponding uplink, and does not need to perform CQI measurements. In contrast, when the SCell is active, the UE may receive PDSCH and PDCCH (if the UE is configured to monitor PDCCH from that SCell) and is expected to be able to perform CQI measurements. NG-RAN ensures that when a PUCCH SCell (a secondary cell configured with PUCCH) is deactivated, the SCells of the secondary PUCCH group (the group of SCells whose PUCCH signaling is associated with the PUCCH on the PUCCH SCell) may not be activated. NG-RAN ensures that the SCell mapped to the PUCCH SCell is deactivated before the PUCCH SCell is changed or removed.

[0098] When a serving cell set is reconfigured: (1) SCells added to the set are initially activated or deactivated; and (2) SCells remaining in the set (unchanged or reconfigured) do not change their activation state (activated or deactivated).

[0099] When switching from RRC_INACTIVE or resuming a connection: (1) SCell is activated or deactivated.

[0100] In order to achieve reduced UE battery consumption and reduced UE complexity when CA is configured, only one UL BWP and one DL BWP or only one DL / UL BWP pair for each uplink carrier may be activated at a time in the active serving cell, and all other BWPs configured by the UE are deactivated. On the deactivated BWP, the UE does not monitor the PDCCH, does not transmit on the PUCCH, PRACH and UL-SCH.

[0101] To enable fast SCell activation when CA is configured, a dormant BWP can be configured for the SCell. If the active BWP of the activated SCell is the dormant BWP, the UE stops monitoring PDCCH and sending SRS / PUSCH / PUCCH on the SCell, but continues to perform CSI measurements, AGC and beam management (if configured). DCI is used to control entry / exit of the dormant BWP for one or more SCells or one or more SCell groups.

[0102] The dormant BWP is one of the dedicated BWPs of the UE configured by the network via dedicated RRC signaling. SpCell and PUCCH SCell cannot be configured with a dormant BWP.

[0103] If the MAC entity is configured with one or more SCells, the network can activate and deactivate the configured SCells. When the SCell is configured, the SCell is deactivated unless the upper layer sets the parameter sCelltate to activated for the SCell.

[0104] The configured SCell is activated and deactivated in the following ways:

[0105] - receive the SCell activation / deactivation MAC CE described in clause 6.1.3.10;

[0106] - receive the enhanced SCell activation / deactivation MAC CE described in clause 6.1.3.55;

[0107] - Configure the sCellDeactivationTimer timer for each configured SCell (except the SCell configured with PUCCH, if any): the associated SCell is deactivated when it expires;

[0108] -Configure sCelltate for each configured SCell: If configured, the associated SCell is activated when the SCell is configured.

[0109] For each configured SCell, the MAC entity shall:

[0110] 1> If the SCell is configured with an sCelltate that is set to active during SCell configuration, or an SCell activation / deactivation MAC CE or enhanced SCell activation / deactivation MAC CE that activates the SCell is received:

[0111] 2> If the SCell is deactivated before receiving the enhanced SCell activation / deactivation MAC CE, and TRS is selected for SCell activation:

[0112] 3>Indicate the information about the TRS to the lower layer.

[0113] 2> If the SCell is deactivated before receiving the SCell activation / deactivation MAC CE or the enhanced SCell activation / deactivation MAC CE; or

[0114] 2> If the SCell configuration has sCelltate set to active during SCell configuration:

[0115] 3> If firstActiveDownlinkBWP-Id is not set to a dormant BWP:

[0116] 4> Activate SCell according to the timing for MAC CE activation defined in 3GPP TS 38.213 v17.2.0 and according to the timing for direct SCell activation defined in 3GPP TS 38.133 v17.2.0; that is, apply normal SCell operation including:

[0117] 5>SRS transmission on SCell;

[0118] 5>SCell CSI report;

[0119] 5>PDCCH monitoring on SCell;

[0120] 5>PDCCH monitoring for SCell;

[0121] 5>PUCCH transmission on SCell (if configured).

[0122] 3> Otherwise (i.e., firstActiveDownlinkBWP-Id is set to dormantBWP):

[0123] 4>Stop the bwp-InactivityTimer of this serving cell, if running.

[0124] 3> Activate the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id respectively.

[0125] 2> Start or restart the sCellDeactivationTimer associated with the SCell according to the timing for MAC CE activation defined in 3GPP TS 38.213v17.2.0 and the timing for direct SCell activation defined in 3GPP TS38.133v17.2.0;

[0126] 2> If the active DL BWP is not the dormant BWP:

[0127] 3> (re)initialize any suspended configured uplink grants of configured grant type 1 associated with this SCell according to the stored configuration (if any), and start in symbol according to the rules in clause 5.8.2;

[0128] 3>Trigger PHR according to clause 5.4.6.

[0129] 1> Otherwise, if a SCell activation / deactivation MAC CE or enhanced SCell activation / deactivation MAC CE for deactivating the SCell is received; or

[0130] 1> If the sCellDeactivationTimer associated with the activated SCell expires:

[0131] 2> Deactivate SCell according to the timing defined in 3GPP TS 38.213v17.2.0;

[0132] 2> Stop the sCellDeactivationTimer associated with SCell;

[0133] 2>Stop the bwp-InactivityTimer associated with SCell;

[0134] 2> Deactivate any active BWP associated with the SCell;

[0135] 2> Clear any configured downlink assignments and any configured uplink grant type 2 associated with the SCell respectively;

[0136] 2> Clear any PUSCH resources used for semi-persistent CSI reporting associated with the SCell;

[0137] 2>Suspend any configured uplink grant type 1 associated with the SCell;

[0138] 2>Flush all HARQ buffers associated with SCell;

[0139] 2>Cancel (if any) the triggered SCell's consistent LBT failure.

[0140] 1> If the PDCCH on the activated SCell indicates an uplink grant or a downlink assignment; or

[0141] 1> If the PDCCH on the serving cell scheduling the activated SCell indicates an uplink grant or downlink assignment for the activated SCell; or

[0142] 1> if a MAC PDU is sent in a configured uplink grant and no LBT failure indication is received from lower layers; or

[0143] 1> If a MAC PDU is received in a configured downlink assignment:

[0144] 2>Restart the sCellDeactivationTimer associated with the SCell.

[0145] 1> If SCell is deactivated:

[0146] 2> Do not send SRS on SCell;

[0147] 2> Do not report the CSI of SCell;

[0148] 2> Not sent on UL-SCH on SCell;

[0149] 2> Not sent on RACH on SCell;

[0150] 2>Do not monitor the PDCCH on SCell;

[0151] 2>Do not monitor the PDCCH for SCell;

[0152] 2>Do not send PUCCH on SCell.

[0153] The HARQ feedback of the MAC PDU containing the SCell activation / deactivation MAC CE or enhanced SCell activation / deactivation MAC CE shall not be affected by the PCell, PSCell and PUCCH SCell outage due to SCell activation / deactivation in 3GPP TS 38.133v17.2.0.

[0154] When the SCell is deactivated, the ongoing random access procedure (if any) on the SCell is terminated.

[0155] A serving cell may be configured with one or more BWPs, and the maximum number of BWPs per serving cell is specified in 3GPP TS 38.213 v17.2.0.

[0156] BWP switching of the serving cell is used to activate the inactive BWP and deactivate the active BWP at one time. BWP switching is controlled by the PDCCH indicating downlink assignment or uplink grant, by the bwp-InactivityTimer, by RRC signaling or by the MAC entity itself when initiating the random access procedure or when a consistent LBT failure on the SpCell is detected. After the RRC (re)configures the firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id for the SpCell (except the deactivated SCG or activated SCell), the DL BWP and / or UL BWP indicated by the firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id, respectively (as specified in 3GPP TS 38.331v17.1.0) are active without receiving a PDCCH indicating a downlink assignment or uplink grant. When RRC (re)configures the firstActiveDownlinkBWP-Id for the deactivated PSCell, if beam failure detection is configured for the deactivated SCG, the DL BWP switches to the firstActiveDownlinkBWP-Id. The active BWP of the serving cell is indicated by RRC or PDCCH (as specified in 3GPP TS 38.213v17.2.0). For unpaired spectrum, the DL BWP is paired with the UL BWP and BWP switching is common for both UL and DL.

[0157] For each SCell, the dormant BWP can be configured with dormantBWP-Id via RRC signaling as described in 3GPP TS 38.331 v17.1.0. Entering or leaving the dormant BWP of a SCell is accomplished by BWP switching per SCell or per dormant SCell group based on instructions from PDCCH (as specified in 3GPP TS 38.213 v17.2.0). The dormant SCell group configuration is configured via RRC signaling as described in 3GPP TS 38.331 v17.1.0. Upon receiving a PDCCH indicating leaving the dormant BWP, activate the DL BWP indicated by firstOutsideActiveTimeBWP-Id or by firstWithinActiveTimeBWP-Id (as specified in TS 38.331 v17.1.0 and TS 38.213 v17.2.0). Upon receiving a PDCCH indicating entry into a dormant BWP, the DL BWP indicated by dormantBWP-Id (as specified in TS 38.331 v17.1.0) is activated. Dormant BWP configuration for SpCell or PUCCH SCell is not supported.

[0158] For each activated serving cell configured with a BWP, the MAC entity shall:

[0159] 1> If the BWP is activated and the active DL BWP of the serving cell is not a dormant BWP:

[0160] 2>Send on the UL-SCH on the BWP;

[0161] 2> If PRACH opportunity is configured, send on RACH on the BWP;

[0162] 2>Monitoring the PDCCH on the BWP;

[0163] 2> If configured, PUCCH is sent on BWP;

[0164] 2> Report the CSI of the BWP;

[0165] 2> If configured, send SRS on the BWP;

[0166] 2> receiving DL-SCH on the BWP;

[0167] 2> (re)initialize any suspended configured uplink grants of configured grant type 1 on the active BWP according to the stored configuration (if any) and starting in symbol according to the rules in clause 5.8.2 of 3GPP TS 38.321 v17.1.0;

[0168] 2> If lbt-FailureRecoveryConfig is configured:

[0169] 3>Stop lbt-FailureDetectionTimer, if running;

[0170] 3> Set LBT_COUNTER to 0;

[0171] 3> Monitor LBT failure indications from lower layers as specified in clause 5.21.2 of 3GPP TS 38.321 v17.1.0.

[0172] 1> If BWP is activated and the active DL BWP of the serving cell is a dormant BWP:

[0173] 2>Stop the bwp-InactivityTimer of this serving cell, if running.

[0174] 2> do not monitor the PDCCH on the BWP;

[0175] 2> not monitoring the PDCCH for the BWP;

[0176] 2> do not receive DL-SCH on the BWP;

[0177] 2> Do not report CSI on the BWP, and report CSI other than the aperiodic CSI of the BWP;

[0178] 2> Do not send SRS on the BWP;

[0179] 2> Not sent on the UL-SCH on the BWP;

[0180] 2> Not sent on the RACH on the BWP;

[0181] 2> PUCCH is not sent on the BWP;

[0182] 2> Clear any configured downlink assignments and any configured uplink grant type 2 associated with the SCell respectively;

[0183] 2>Suspend any configured uplink grant type 1 associated with the SCell;

[0184] 2> If configured, if beam failure is detected, beam failure detection and beam failure recovery are performed on the SCell.

[0185] 1> If BWP is deactivated:

[0186] 2> Not sent on the UL-SCH on the BWP;

[0187] 2> Not sent on the RACH on the BWP;

[0188] 2> do not monitor the PDCCH on the BWP;

[0189] 2> PUCCH is not sent on the BWP;

[0190] 2> Do not report the CSI of the BWP;

[0191] 2> Do not send SRS on the BWP;

[0192] 2> do not receive DL-SCH on the BWP;

[0193] 2> Clear any configured downlink assignments and configured uplink grants of configured grant type 2 on the BWP;

[0194] 2> Suspend any configured uplink grant of configured grant type 1 on the inactive BWP.

[0195] When initiating a random access procedure on a serving cell, after selecting a carrier for performing the random access procedure as specified in clause 5.1.1 of 3GPP TS 38.321 v17.1.0, the MAC entity shall, for the selected carrier of this serving cell:

[0196] 1> If PRACH opportunity is not configured for active UL BWP:

[0197] 2> if the UE is a RedCap UE; and

[0198] 2> If initialUplinkBWP-RedCap is configured:

[0199] 3> Switch the active UL BWP to the BWP configured by initialUplinkBWP-RedCap.

[0200] 2> Otherwise:

[0201] 3> Switch the active UL BWP to the BWP indicated by initialUplinkBWP.

[0202] 2> If the serving cell is SpCell:

[0203] 3> if the UE is a RedCap UE; and

[0204] 3> If initialDownlinkBWP-RedCap is configured:

[0205] 4>Switch the active DL BWP to the BWP configured by initialDownlinkBWP-RedCap.

[0206] 3> Otherwise:

[0207] 4> Switch the active DL BWP to the BWP indicated by initialDownlinkBWP.

[0208] 1> Otherwise:

[0209] 2> If the serving cell is SpCell:

[0210] 3> If the active DL BWP does not have the same bwp-Id as the active UL BWP:

[0211] 4> Switch the active DL BWP to a DL BWP with the same bwp-Id as the active UL BWP.

[0212] 1> Stop the bwp-InactivityTimer associated with the active DL BWP of this serving cell, if running.

[0213] 1> If the serving cell is SCell:

[0214] 2> Stop the bwp-InactivityTimer associated with the active DL BWP of the SpCell, if running.

[0215] 1> Perform a random access procedure on the active DL BWP of the SpCell and the active UL BWP of this serving cell.

[0216] If the MAC entity receives a PDCCH for BWP switching of a serving cell, the MAC entity shall:

[0217] 1> if there is no ongoing random access procedure associated with the serving cell; or

[0218] 1> If an ongoing random access procedure associated with the serving cell is successfully completed when this PDCCH addressed to the C-RNTI is received (as specified in clauses 5.1.4, 5.1.4a and 5.1.5 of 3GPP TS 38.321 v17.1.0):

[0219] 2> Cancel (if any) the triggered consistent LBT failure of the serving cell;

[0220] 2> Perform BWP switching to the BWP indicated by the PDCCH.

[0221] If the MAC entity receives a PDCCH for BWP switching of the serving cell or dormant SCell group while a random access procedure associated with the serving cell is ongoing in the MAC entity, then, except for the reception of PDCCH for BWP switching addressed to C-RNTI for successful random access procedure completion (as specified in clauses 5.1.4, 5.1.4a and 5.1.5 of 3GPP TS 38.321v17.1.0) (in which case the UE should perform BWP switching to the BWP indicated by the PDCCH), whether to switch the BWP or ignore the PDCCH for BWP switching depends on the implementation of the UE. Upon receiving the PDCCH for BWP switching other than successful contention resolution, if the MAC entity decides to perform BWP switching, the MAC entity shall stop the ongoing random access procedure and initiate the random access procedure after performing the BWP switching; if the MAC decides to ignore the PDCCH for BWP switching, the MAC entity shall continue the ongoing random access procedure on the serving cell.

[0222] When an RRC (re)configuration for BWP switching of a serving cell is received while a random access procedure associated with a serving cell is being performed in the MAC entity, the MAC entity shall stop the ongoing random access procedure and initiate a random access procedure after performing the BWP switching.

[0223] Upon receiving an RRC (re)configuration for BWP handover of a serving cell, any triggered LBT failure in this serving cell is cancelled.

[0224] For each activated serving cell configured with bwp-InactivityTimer, the MAC entity shall:

[0225] 1> if defaultDownlinkBWP-Id is configured, and the active DL BWP is not the BWP indicated by defaultDownlinkBWP-Id, and the active DL BWP is not the BWP indicated by dormantBWP-Id (if configured); or

[0226] 1> If defaultDownlinkBWP-Id is not configured, and the active DL BWP is not initialDownlinkBWP, and the active DL BWP is not the BWP indicated by dormantBWP-Id (if configured):

[0227] 2> if a PDCCH addressed to a C-RNTI or CS-RNTI indicating a downlink assignment or uplink grant is received on an active BWP; or

[0228] 2> if a PDCCH addressed to a G-RNTI or G-CS-RNTI configured for multicast indicating downlink assignments is received on an active BWP; or

[0229] 2> if a PDCCH addressed to a C-RNTI or CS-RNTI indicating a downlink assignment or uplink grant is received for an active BWP; or

[0230] 2> If a MAC PDU is sent in a configured uplink grant and no LBT failure indication is received from lower layers; or

[0231] 2> If a MAC PDU is received in a configured downlink assignment for unicast or MBS multicast:

[0232] 3> If there is no ongoing random access procedure associated with the serving cell; or

[0233] 3> If an ongoing random access procedure associated with the serving cell is successfully completed when this PDCCH addressed to the C-RNTI is received (as specified in clauses 5.1.4, 5.1.4a and 5.1.5 of 3GPP TS 38.321 v17.1.0):

[0234] 4> Start or restart the bwp-InactivityTimer associated with the active DL BWP.

[0235] 2> If the bwp-InactivityTimer associated with the active DL BWP expires:

[0236] 3> If defaultDownlinkBWP-Id is configured:

[0237] 4> Perform BWP switching to the BWP indicated by defaultDownlinkBWP-Id.

[0238] 3> Otherwise:

[0239] 4>Execute BWP switch to initialDownlinkBWP.

[0240] - Note: If a random access procedure is initiated on an SCell, both the SCell and the SpCell are associated with the random access procedure.

[0241] 1> If PDCCH for BWP switching is received and the MAC entity switches the active DL BWP:

[0242] 2> if defaultDownlinkBWP-Id is configured and the MAC entity switches to a DL BWP that is not indicated by defaultDownlinkBWP-Id and not indicated by dormantBWP-Id (if configured); or

[0243] 2> If defaultDownlinkBWP-Id is not configured, and the MAC entity switches to a DL BWP that is not initialDownlinkBWP and is not indicated by dormantBWP-Id (if configured):

[0244] 3> Start or restart the bwp-InactivityTimer associated with the active DL BWP.

[0245] The MAC entity may be configured by RRC with a discontinuous reception (DRX) functionality that controls the UE's PDCCH monitoring activity for C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, AI-RNTI, SL-RNTI, SLCS-RNTI, and SL semi-persistent scheduling V-RNTI for the MAC entity. When using DRX operation, the MAC entity shall also monitor the PDCCH in accordance with the requirements found in other clauses of this specification. When in RRC_CONNECTED, if DRX is configured, the MAC entity may monitor the PDCCH discontinuously using the DRX operation specified in this clause for all activated serving cells; otherwise, the MAC entity shall monitor the PDCCH as specified in 3GPP TS 38.213 v17.2.0.

[0246] RRC controls DRX operation by configuring the following parameters:

[0247] -drx-onDurationTimer: duration when the DRX cycle starts;

[0248] -drx-SlotOffset: Delay before starting drx-onDurationTimer;

[0249] -drx-InactivityTimer: duration after the PDCCH opportunity when the PDCCH indicates a new UL or DL ​​transmission of the MAC entity;

[0250] -drx-RetransmissionTimerDL (per DL HARQ process, except broadcast process): maximum duration until a DL retransmission is received;

[0251] -drx-RetransmissionTimerUL (per UL HARQ process): maximum duration until a grant for UL retransmission is received;

[0252] -drx-LongCycleStartOffset: long DRX cycle and drx-StartOffset, which define the subframes where the long DRX cycle and the short DRX cycle start;

[0253] -drx-ShortCycle (optional): short DRX cycle;

[0254] -drx-ShortCycleTimer (optional): duration of the short DRX cycle that the UE should follow;

[0255] -drx-HARQ-RTT-TimerDL (for each DL HARQ process except the broadcast process): the minimum duration before a DL assignment that the MAC entity expects for HARQ retransmissions;

[0256] -drx-HARQ-RTT-TimerUL (per UL HARQ process): minimum duration before UL HARQ retransmission grant is expected by the MAC entity;

[0257] -drx-RetransmissionTimerSL (per SL HARQ process): maximum duration until a grant for SL retransmission is received;

[0258] -drx-HARQ-RTT-TimerSL (per SL HARQ process): minimum duration before the MAC entity expects a SL retransmission grant;

[0259] -ps-Wakeup (optional): Starts the associated drx-onDurationTimer configuration when the DCP is monitored but not detected;

[0260] -ps-TransmitOtherPeriodiCSI (optional): Configuration to report periodic CSI other than L1-RSRP on PUCCH during the duration indicated by drx-onDurationTimer, if DCP is configured but the associated drx-onDurationTimer is not started;

[0261] -ps-TransmitPeriodicL1-RSRP (optional): configuration to send periodic CSI as L1-RSRP on PUCCH during the duration indicated by drx-onDurationTimer, if DCP is configured but the associated drx-onDurationTimer is not started;

[0262] -uplinkHARQ-mode (optional): used to set the configuration of the HARQ mode for each UL HARQ process.

[0263] The service cells of the MAC entity can be configured by RRC in two DRX groups with separate DRX parameters. When RRC does not configure a secondary DRX group, there is only one DRX group, and all service cells belong to this one DRX group. When two DRX groups are configured, each service cell is uniquely assigned to any one of the two groups. The DRX parameters configured separately for each DRX group are: drx-onDurationTimer, drx-InactivityTimer. The DRX parameters common to the DRX group are: drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL and uplinkHARQ-mode (optional).

[0264] When DRX is configured, the active time of the serving cells in the DRX group includes this time in the following cases:

[0265] - the drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or

[0266] - drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or drx-RetransmissionTimerSL is running on any serving cell in the DRX group; or

[0267] -ra-ContentionResolutionTimer (as described in clause 5.1.5 of 3GPP TS 38.321 v17.1.0) or msgB-ResponseWindow (as described in clause 5.1.4a of 3GPP TS 38.321 v17.1.0) is running; or

[0268] - A Scheduling Request is sent on the PUCCH and is pending (as described in sections 5.4.4 or 5.22.15 of 3GPP TS 38.321 v17.1.0). If the serving cell is part of a non-terrestrial network, the Active Time starts after the first Scheduling Request transmission plus the UE-gNB RTT; or

[0269] -After successfully receiving a random access response for a random access preamble that was not selected by the MAC entity in a contention-based random access preamble, a PDCCH indicating a new transmission of the C-RNTI addressed to the MAC entity has not been received (as described in clauses 5.1.4 and 5.1.4a of 3GPP TS 38.321v17.1.0).

[0270] Cross-carrier scheduling using the carrier indicator field (CIF) allows a DCI format provided by a PDCCH on a serving / scheduling cell to schedule resources on another serving / scheduling cell, with the following example restrictions.

[0271] In one example, when cross-carrier scheduling from SCell to PCell is not configured to the UE, the UE can be scheduled for transmission or reception on the PCell only through the DCI format provided by PDCCH reception on the PCell.

[0272] In one example, when cross-carrier scheduling from SCell to PCell is configured for a UE: (1) the PDCCH on the SCell can provide a DCI format that schedules PDSCH reception on the PCell or PUSCH transmission from the UE; (2) the PDCCH on the PCell can provide a DCI format that schedules PDSCH reception on the PCell or PUSCH transmission from the UE; and (3) only one SCell can be configured for the UE for cross-carrier scheduling on the PCell.

[0273] In one example, when an SCell is configured for a UE as a scheduling cell, PDSCH reception or PUSCH transmission from the UE is scheduled by a DCI format provided by PDCCH reception on the SCell.

[0274] In one example, when the SCell is not configured to the UE as a scheduling cell, PDSCH reception or PUSCH transmission from the UE is scheduled by a DCI format provided by PDCCH reception on another serving cell.

[0275] In one example, PDCCH reception on the scheduling cell can have the same or a different set of parameters as the associated PDSCH reception or PUSCH transmission on the scheduled cell.

[0276] The physical downlink control channel (PDCCH) can be used to schedule DL transmission on PDSCH and UL transmission on PUSCH, where the downlink control information (DCI) on the PDCCH includes: (1) downlink assignment, which at least includes the modulation and coding format, resource allocation and hybrid ARQ information related to DL-SCH; and (2) uplink scheduling grant, which at least includes the modulation and coding format, resource allocation and hybrid ARQ information related to UL-SCH.

[0277] In addition to scheduling, the PDCCH can also be used for: (1) activation and deactivation of configured PUSCH transmissions with configured grants; (2) activation and deactivation of PDSCH semi-persistent transmissions; (3) notification of the timeslot format to one or more UEs; (4) notification of PRBs and OFDM symbols to one or more UEs where the UE can assume that no transmission is intended for the UE; (5) transmission of TPC commands for PUCCH and PUSCH; (6) transmission of one or more TPC commands for SRS transmission by one or more UEs; (7) switching of the active bandwidth portion of a UE ; (8) initiate a random access procedure; (9) instruct one or more UEs to monitor PDCCH during the next occurrence of DRX on duration; (10) in the IAB context, indicate the availability of soft symbols for IAB-DU; (11) trigger single HARQ-ACK codebook feedback; and (12) for shared spectrum channel access operations: (i) trigger search space set group switching; (ii) indicate the available RB set and channel occupancy duration to one or more UEs; and (iii) indicate downlink feedback information for the configured granted PUSCH (CG-DFI).

[0278] The UE monitors the PDCCH candidate set in the configured monitoring occasions in one or more configured control resource sets (CORESETs) according to the corresponding search space set configuration.

[0279] A CORESET consists of a set of PRBs with a duration of 1 to 3 OFDM symbols. Resource unit resource element groups (REGs) and control channel elements (CCEs) are defined within a CORESET, where each CCE includes a set of REGs. A control channel is formed by the aggregation of CCEs. Different code rates for the control channel are achieved by aggregating different numbers of CCEs. Interleaved and non-interleaved CCE to REG mapping is supported in a CORESET.

[0280] Polar codec is used for DCI format in PDCCH. Each resource element group carrying PDCCH carries its own DM-RS. QPSK modulates the codec symbols used for DCI format in PDCCH.

[0281] The UE can configure self-carrier and cross-carrier scheduling on the primary cell.

[0282] The UE may be configured for scheduling on the primary cell from the primary cell or from the secondary cell, TS 38.331. The UE is not provided with monitoringCapabilityConfig, or the UE is only provided with monitoringCapabilityConfig=r15monitoringcapability for the primary cell and for the secondary cell. The coresetPoolIndex is not provided to the UE on the primary cell or on the secondary cell.

[0283] SCS configuration μ for active DL BWP on primary cell P Less than or equal to the SCS configuration μ for the active DLBWP on the secondary cell S .

[0284] If the UE indicates the capability as described in TS 38.306 and the secondary cell is deactivated, or if the UE indicates the capability as described in TS 38.306 and the active DL BWP of the secondary cell is the dormant DL BWP of the UE, then α=1 applies to the procedures described in TS 38.306.

[0285] If μ P <μ S , the UE includes the primary cell only in In In the downlink cell, determine and And make sure and As described in the 3GPP standard specification. If μ P =μ S =μ, the UE includes the primary cell in In Once in a downlink cell, determine and As described in the 3GPP standard specifications.

[0286] For scheduling on a primary cell from a primary cell, the UE does not need to monitor more than 100 timeslots per time slot on the active DL BWP of the primary cell. PDCCH candidates or more per slot non-overlapping CCEs, where: α is provided by ccs-BlindDetectionSplit.

[0287] For scheduling from a secondary cell on a primary cell, the UE does not need to monitor more than the following on the active DL BWP of the secondary cell: (1) per time slot PDCCH candidates or more than the active DL BWP per slot of the secondary cell non-overlapping CCEs; and (2) per time slot PDCCH candidates or more than the active DL BWP per slot of the primary cell non-overlapping CCEs.

[0288] If μ P <μ S , the UE does not monitor the PDCCH candidates and non-overlapping CCEs scheduled from the secondary cell in the primary cell towards and count.

[0289] If μ P <μ S , the UE monitors the PDCCH candidates and non-overlapping CCEs scheduled from the secondary cell in the primary cell towards and count.

[0290] For the allocation of PDCCH candidates and non-overlapping CCEs to the search space set for scheduling on the primary cell from the primary cell, the UE uses replace And use replace This process is applied in the 3GPP standard specification.

[0291] The UE may apply DCI size alignment as described later.

[0292] If necessary, padding or truncation may be applied to the DCI format according to the following steps performed in the order shown in Table 1.

[0293] Table 1. Steps of DCI format

[0294]

[0295]

[0296]

[0297]

[0298] It is not expected that the UE processes a configuration that results in the following results after applying the above steps: (1) the total number of different DCI sizes that the cell is configured to monitor is greater than 4; (2) the total number of different DCI sizes with C-RNTI that the cell is configured to monitor is greater than 3; (3) the size of DCI format 0_0 in a UE-specific search space is equal to DCI format 0_1 ​​in another UE-specific search space; (4) the size of DCI format 1_0 in a UE-specific search space is equal to DCI format 1_1 in another UE-specific search space; (5) when at least one pair of corresponding PDCCH candidates of DCI formats 0_0 and 0_2 are mapped to the same resource, the size of DCI format 0_0 in the UE-specific search space is equal to DCI format 1_1 in another UE-specific search space. Formula 0_2; (6) when at least one pair of corresponding PDCCH candidates of DCI formats 1_0 and 1_2 are mapped to the same resource, the size of DCI format 1_0 in the UE-specific search space is equal to DCI format 1_2 in another UE-specific search space; (7) when at least one pair of corresponding PDCCH candidates of DCI formats 0_1 and 0_2 are mapped to the same resource, the size of DCI format 0_1 ​​in the UE-specific search space is equal to DCI format 0_2 in the same or another UE-specific search space; or (8) when at least one pair of corresponding PDCCH candidates of DCI formats 1_1 and 1_2 are mapped to the same resource, the size of DCI format 1_1 in the UE-specific search space is equal to DCI format 1_2 in the same or another UE-specific search space.

[0299] If DCI format 3_0 or DCI format 3_1 is monitored on the cell, after performing the DCI size alignment described in the 3GPP standard specification, DCI size alignment for DCI format 3_0 and DCI format 3_1 is performed as described in the 3GPP standard specification. The size of the DCI format configured to be monitored for the cell in the 3GPP standard specification refers to the size after performing the DCI size alignment described in the 3GPP standard specification.

[0300] If DCI format 3_0 or DCI format 3_1 is monitored on a cell and the total number of DCI sizes configured for the DCI formats and DCI format 3_0 or DCI format 3_1 monitored for the cell is greater than 4, zeros may be appended to DCI format 3_0 (if configured) and DCI format 3_1 (if configured) until the payload size of DCI format 3_0 or DCI format 3_1 is equal to the payload size of the smallest DCI format larger than DCI format 3_0 or DCI format 3_1 configured for monitoring for the cell.

[0301] It is not expected that the UE will process configurations that result in: (1) the total number of different DCI sizes and DCI formats 3_0 or DCI formats 3_1 configured for cell monitoring is greater than 4; and (2) the payload size of DCI format 3_0 or DCI format 3_1 is greater than the payload size of all other DCI formats configured for cell monitoring.

[0302] For a UE configured with scheduling on the primary cell from the SCell, if the number of information bits in DCI format 0_1 ​​carried by the PDCCH on the primary cell before padding is not equal to the number of information bits in DCI format 0_1 ​​carried by the PDCCH on the SCell for scheduling on the primary cell, zeros may be appended to the DCI format 0_1 ​​with the smaller size until the payload sizes are the same.

[0303] For a UE configured with scheduling on the primary cell from the SCell, if the number of information bits in DCI format 0_2 carried by the PDCCH on the primary cell before padding is not equal to the number of information bits in DCI format 0_2 carried by the PDCCH on the SCell for scheduling on the primary cell, zeros may be appended to the DCI format 0_2 with the smaller size until the payload sizes are the same.

[0304] For a UE configured with scheduling on the primary cell from the SCell, if the number of information bits in the DCI format 1_1 carried by the PDCCH on the primary cell before padding is not equal to the number of information bits in the DCI format 1_1 carried by the PDCCH on the SCell for scheduling on the primary cell, zeros may be appended to the DCI format 1_1 with a smaller size until the payload sizes are the same.

[0305] For a UE configured with scheduling on the primary cell from the SCell, if the number of information bits in DCI format 1_2 carried by the PDCCH on the primary cell before padding is not equal to the number of information bits in DCI format 1_2 carried by the PDCCH on the SCell for scheduling on the primary cell, zeros may be appended to the DCI format 1_2 with the smaller size until the payload sizes are the same.

[0306] In one embodiment, for a UE configured with scheduling from a SCell on a PCell (in addition to self-scheduling on the PCell), in order to simultaneously meet: (1) a "3+1" DCI size budget for the PCell, and (2) size alignment of the same DCI format for scheduling on the PCell (such as DCI format 0_1 / 1_1 / 0_2 / 1_2) provided by PDCCH reception on the PCell or SCell, the UE first matches the DCI formats (associated with the USS set) on the two scheduling cells (PCell and SCell) for scheduling on the PCell in size, and then, when the "3+1" DCI size budget for the PCell needs to be achieved, the same zero padding is applied to the same DCI format (such as DCI format 0_1 ​​or DCI format 1_1) on the PCell and SCell for scheduling on the PCell so as to align the corresponding sizes of the DCI formats on the PCell and SCell for scheduling on the PCell with another DCI format on the PCell and SCell for scheduling on the PCell.

[0307] When the UE monitors the PDCCH to detect DCI format 2_x on the primary cell, where x is from 0 to 7, as described in TS 38.212, the UE considers the primary cell as a scheduled cell and counts the size of DCI format 2_x toward the predetermined limit of "3+1" size of DCI formats that the UE can decode as scheduled cells. When the UE is provided with a USS set on the SCell to monitor the PDCCH with a DCI format that schedules PDSCH reception or PUSCH transmission on the PCell, the UE is configured with scheduling from the SCell on the PCell.

[0308] For example, the UE: (1) aligns DCI format 0_1 ​​on the PCell and on the SCell for scheduling PUSCH transmission on the PCell, (2) if the total number of sizes of DCI formats used for scheduling on the PCell is greater than "3+1" (including DCI format 2_x, where x is from 0 to 7, where the CRC is not scrambled by C-RNTI / MCS-C-RNTI / CS-RNTI as described in TS 38.212), the UE aligns the sizes of DCI format 0_1 ​​and DCI format 1_1, for example by applying zero padding to both DCI format 0_1 ​​on the PCell and DCI format 0_1 ​​on the SCell.

[0309] For example, the UE: (1) aligns DCI format 1_2 on the PCell and on the SCell for scheduling PDSCH reception on the PCell, and (2) if the total number of sizes of DCI formats used for scheduling on the PCell is greater than "3+1" (including DCI format 2_x, where x is from 0 to 7, where the CRC is not scrambled by C-RNTI / MCS-C-RNTI / CS-RNTI as described in TS 38.212), the UE aligns the sizes of DCI format 1_2 and DCI format 0_2, for example by applying zero padding to both DCI format 1_2 on the PCell and DCI format 1_2 on the SCell.

[0310] This embodiment can be applied to any scheduled cell configured to be scheduled by two or more scheduling cells (including self-scheduling or cross-carrier scheduling), including any SCell.

[0311] Figure 6 6 is a flowchart of a process 600 for aligning the size of a DCI format for scheduling on a primary cell from a primary cell or from a secondary cell when the UE monitors a PDCCH to detect more than a "3+1" DCI format size according to an embodiment of the present disclosure. The process 600 may be performed by a UE (e.g., Figure 1 111-116) as shown. Figure 6 The embodiment of process 600 shown in FIG. 6 is for illustration only. Figure 6 One or more of the components shown in the may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described.

[0312] like Figure 6As shown, a UE is configured for scheduling on a primary cell from a primary cell and from a secondary cell, 610. The UE aligns a size of a DCI format (e.g., 0_2) for scheduling on a primary cell from the primary cell and a size of the same DCI format for scheduling on a primary cell from a secondary cell, 620. The UE determines that zeros may be appended to a first DCI format (e.g., 0_2) for scheduling on a primary cell from the primary cell to obtain the same size as a second DCI format (e.g., 1_2) for scheduling on a primary cell from the secondary cell to achieve a predetermined number of sizes of DCI formats for scheduling on the primary cell, 630. The UE applies zero padding to both the first DCI format (e.g., 0_2) for scheduling on a primary cell from the primary cell and the same DCI format for scheduling on a primary cell from the secondary cell, 640.

[0313] In one example, the above UE behavior may be implemented in the specification as follows.

[0314] For a UE configured with scheduling on the primary cell from the SCell, if the number of information bits in DCI format 0_1 ​​carried by the PDCCH on the primary cell before padding is not equal to the number of information bits in DCI format 0_1 ​​carried by the PDCCH on the SCell for scheduling on the primary cell, zeros may be appended to the DCI format 0_1 ​​with the smaller size until the payload sizes are the same.

[0315] If application of step 4C in the 3GPP standard specification results in additional zero padding for DCI format 0_1 ​​scheduled on the primary cell, corresponding zeros may be appended to both DCI format 0_1 ​​monitored on the primary cell and DCI format 0_1 ​​monitored on the SCell for scheduling on the primary cell.

[0316] Similar text may apply to DCI format 1_1. Similar text may apply to DCI formats 0_2 and 1_2, where step 4C may be replaced by step 4B.

[0317] In another example, the above UE behavior may be implemented in the specification as follows.

[0318] For a UE configured with scheduling from an SCell on a primary cell, if the number of information bits in DCI format 0_1 ​​carried by the PDCCH on the primary cell before or after padding is not equal to the number of information bits in DCI format 0_1 ​​carried by the PDCCH on the SCell for scheduling on the primary cell, zeros may be appended to the DCI format 0_1 ​​with a smaller size until the payload sizes are the same.

[0319] Similar text may apply to DCI formats 1_1, 0_2, and 1_2.

[0320] In one embodiment, for a UE configured with scheduling from SCell on PCell and the SCell is deactivated for the UE or the UE has a dormant active DL BWP on the SCell, the UE determines the size alignment process of the DCI format for scheduling on the PCell based on the reference DL BWP on the SCell. The reference BWP on the SCell may be the first active DL BWP, or the BWP outside the first active time, or the BWP within the first active time, or the initial DL BWP, or the default BWP, etc. Compared with the case where the active DL BWP on the SCell is the dormant DL BWP of the UE, the reference BWP may be the same or different for the case where the UE's SCell is deactivated.

[0321] In one example, for a UE configured with scheduling from a SCell on a PCell, when the SCell is a deactivated serving cell for the UE, the UE determines the size of a DCI format (associated with a USS set) on the SCell for scheduling on the PCell based on information provided by one of the following: (1) the first active DL BWP; (2) the initial DL BWP; (3) the default DL BWP; (4) the lowest indexed (or highest indexed) DL BWP; (5) the most recent active DL BWP before SCell deactivation; or (6) a reference DL BWP indicated by a higher layer of the SCell.

[0322] In another example, for a UE configured with scheduling from a SCell on a PCell, when the active DLBWP of the SCell is a dormant BWP, the UE determines the size of the DCI format (associated with a USS set) on the SCell for scheduling on the PCell based on information provided by one of the following: (1) firstOutsideActiveTimeBWP; (2) firstWithinActiveTimeBWP; (3) first active DL BWP; (4) initial DL BWP; (5) default DL BWP; (6) lowest index (or highest index) DL BWP; (7) the most recent active DL BWP before changing to a dormant DL BWP on the SCell; or (8) a reference DL BWP indicated by a higher layer of the SCell.

[0323] Figure 7 Flowchart illustrating a process 700 for a UE to determine a size of a DCI format for receiving a DCI format scheduled on a PCell via a PDCCH on a SCell when the SCell is deactivated for the UE or the UE has a dormant active DL BWP on the SCell according to an embodiment of the present disclosure. Process 700 may be performed by a UE (e.g., Figure 1 111-116) as shown. Figure 7 The embodiment of process 700 shown in FIG. 7 is for illustration only. Figure 7 One or more of the components shown in the may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described.

[0324] The UE is configured for scheduling from the primary cell and from the secondary cell on the primary cell, 710. The UE is indicated that the secondary cell is a deactivated serving cell, or the UE changes the active DL BWP on the secondary cell to a dormant DL BWP, 720. The UE determines a DCI format for scheduling from the secondary cell on the primary cell based on information of a reference DL BWP for the secondary cell, 730. The UE performs an alignment procedure to obtain a DCI format for scheduling from the secondary cell on the primary cell and a DCI format for scheduling from the primary cell on the primary cell of the same size, 740.

[0325] In one example, the above UE behavior may be implemented in the specification as follows.

[0326] For a UE configured with scheduling from an SCell on a primary cell, if the number of information bits in DCI format 0_1 ​​carried by the PDCCH on the primary cell before padding is not equal to the number of information bits in DCI format 0_1 ​​carried by the PDCCH on the SCell for scheduling on the primary cell, zeros may be appended to the DCI format 0_1 ​​with a smaller size until the payload sizes are the same.

[0327] If the SCell is deactivated, the UE determines the number of information bits in DCI format 0_1 ​​carried by the PDCCH on the primary cell based on the configuration provided by the first active DL BWPfirstActiveDownlinkBWP-Id of the SCell. If the active DL BWP of the SCell is a dormant DL BWP, the UE determines the number of information bits in DCI format 0_1 ​​carried by the PDCCH on the primary cell based on the configuration provided by the DL BWPfirstOutsideActiveTimeBWP [or may be firstWithinActiveTimeBWP] of the SCell.

[0328] Similar text may apply to DCI formats 1_1, 0_2, and 1_2.

[0329] In an alternative implementation, when the SCell is deactivated for the UE or when the UE has a dormant active DLBWP on the SCell, the UE does not consider the DCI format associated with the search space set for PDCCH reception on the SCell for scheduling on the PCell.

[0330] When the UE indicates the capability to monitor PDCCH only in different time slots according to the USS set on the PCell and SCell for scheduling on the PCell, the UE may not perform the cross-cell "3+1" DCI size alignment as described in the present disclosure. The UE may also additionally indicate the capability not to perform cross-cell DCI size alignment when the UE only monitors PDCCH in different time slots according to the USS set on the PCell and SCell for scheduling on the PCell.

[0331] Figure 8 is a block diagram showing the structure of a UE according to an embodiment of the present disclosure.

[0332] like Figure 8 As shown, the UE according to the embodiment may include a transceiver 810, a memory 820, and a processor 830. The transceiver 810, the memory 820, and the processor 830 of the UE may operate according to the communication method of the above-mentioned UE. However, the components of the UE are not limited thereto. For example, the UE may include more or fewer components than the above-mentioned components. In addition, the processor 830, the transceiver 810, and the memory 820 may be implemented as a single chip. In addition, the processor 830 may include at least one processor. In addition Figure 8 The UE corresponds to Figure 1 UE 111, UE 112, UE 113, UE 114, UE 115 or UE 116 or Figure 3 UE.

[0333] The transceiver 810 is collectively referred to as a UE receiver and a UE transmitter, and can send / receive signals to / from a base station or a network entity. The signals sent to or received from a base station or a network entity may include control information and data. The transceiver 810 may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for amplifying the low noise and down-converting the frequency of the received signal. However, this is only an example of the transceiver 810, and the components of the transceiver 810 are not limited to the RF transmitter and the RF receiver.

[0334] In addition, the transceiver 810 may receive a signal through a wireless channel and output the signal to the processor 830 , and transmit a signal output from the processor 830 through a wireless channel.

[0335] The memory 820 may store programs and data required for the operation of the UE. In addition, the memory 820 may store control information or data included in a signal obtained by the UE. The memory 820 may be a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0336] The processor 830 may control a series of processes so that the UE operates as described above. For example, the transceiver 810 may receive a data signal including a control signal sent by a base station or a network entity, and the processor 830 may determine a result of receiving the control signal and the data signal sent by the base station or the network entity.

[0337] Fig. 9 is a block diagram showing the structure of a base station according to an embodiment of the present disclosure.

[0338] like Fig. 9 As shown, the base station according to the embodiment may include a transceiver 910, a memory 920, and a processor 930. The transceiver 910, the memory 920, and the processor 930 of the base station may operate according to the communication method of the above-mentioned base station. However, the components of the base station are not limited thereto. For example, the base station may include more or fewer components than the above-mentioned components. In addition, the processor 930, the transceiver 910, and the memory 920 may be implemented as a single chip. In addition, the processor 930 may include at least one processor. In addition, Fig. 9 The base station corresponds to Figure 1 BS (e.g., gNodeB (gNB) 101, gNB 102, and gNB 103) or Figure 2 gNB.

[0339] The transceiver 910 is collectively referred to as a base station receiver and a base station transmitter and can send signals to / receive signals from a terminal (UE), a network entity or other base stations. The signals sent to or received from a terminal or a network entity may include control information and data. The transceiver 910 may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal and an RF receiver for amplifying the frequency of the low noise and down-converting the received signal. However, this is only an example of the transceiver 910 and the components of the transceiver 910 are not limited to the RF transmitter and the RF receiver.

[0340] In addition, the transceiver 910 may receive a signal through a wireless channel and output it to the processor 930 , and transmit a signal output from the processor 930 through a wireless channel.

[0341] The memory 920 may store programs and data required for the operation of the base station. In addition, the memory 920 may store control information or data included in a signal obtained by the base station. The memory 920 may be a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0342] The processor 930 may control a series of processes so that the base station operates as described above. For example, the transceiver 910 may receive a data signal including a control signal transmitted by a terminal, and the processor 930 may determine a result of receiving the control signal and the data signal transmitted by the terminal.

[0343] The present disclosure achieves improved operation of 3GPP 5G NR systems by enhancing CA operation. The embodiments are general and can also be applied to various frequency bands in different frequency ranges (FR), such as FR1, FR2, FR3 and FR4, such as low bands (e.g., below 1 GHz), mid-bands (e.g., 1-7 GHz), and high / millimeter bands (e.g., 24-100 GHz and higher). In addition, the embodiments are general and can also be applied to various use cases and settings, such as single-panel UEs and multi-panel UEs, eMBB, URLLC and IIoT, mMTC and IoT, sidelink / V2X, operations with multiple TRPs / beams / panels, operations in unlicensed / shared spectrum (NR-U), non-terrestrial networks (NTN), aerial systems such as drones, operations with reduced capability (RedCap) UEs, private or non-public networks (NPN), etc.

[0344] The present disclosure relates to pre-5G or 5G or beyond 5G communication systems, which are provided to support one or more of the following: higher data rates, lower latency, higher reliability, improved coverage, and large-scale connectivity, etc. Various embodiments are applicable to UEs operating with other RATs and / or standards, such as different versions / generations of 3GPP standards (including beyond 5G, 5G Advanced, 6G, etc.), IEEE standards (such as 802.16 WiMAX and 802.11 Wi-Fi, etc.), etc.

[0345] The above flow charts illustrate example methods that can be implemented according to the principles of the present disclosure, and various changes can be made to the methods shown in the flow charts herein. For example, although shown as a series of steps, the various steps in each figure can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, a step can be omitted or replaced by another step.

[0346] Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. The present disclosure is intended to cover these changes and modifications that fall within the scope of the appended claims. The description in this application should not be interpreted as implying that any particular element, step or function is an essential element that must be included in the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. A method performed by a user equipment UE in a wireless communication system, comprising: take over: When a first physical downlink control channel PDCCH providing a first downlink control information DCI format is received on the primary cell PCell, first information of a first field of the first DCI format, and When a second PDCCH providing the first DCI format is received on a secondary cell SCell, second information of a second field of the first DCI format, wherein the first DCI format schedules a physical uplink shared channel PUSCH transmission on the PCell; Sure: When a first PDCCH providing the first DCI format is received on the PCell, a first size of the first DCI format, a second size of the first DCI format when a second PDCCH providing the first DCI format is received on the SCell, wherein the second size is determined based on a first reference downlink DL bandwidth part (BWP) of the SCell when the SCell is deactivated, and a first number of padding bits that is equal to the absolute difference between the first size and the second size; and take over: the first DCI format in the first PDCCH reception on the PCell, wherein when the first size is less than the second size, the first DCI format includes the first number of padding bits appended to a plurality of bits of the first field, or The first DCI format in the second PDCCH reception on the SCell, wherein when the second size is smaller than the first size, the first DCI format includes the first number of padding bits appended to a plurality of bits of the second field.

2. The method according to claim 1, wherein: The first reference DL BWP is a first active DL BWP of the SCell after activation of the SCell.

3. The method according to claim 1, wherein: When the active DL BWP on the SCell is a dormant DL BWP, the second size is determined based on a second reference DL BWP of the SCell.

4. The method according to claim 3, wherein: The second reference DL BWP of the SCell is the first active DL BWP of the SCell after switching from the dormant DL BWP of the SCell.

5. A user equipment UE in a wireless communication system, the UE comprising: A transceiver configured to receive: When a first physical downlink control channel PDCCH providing a first downlink control information DCI format is received on the primary cell PCell, first information of a first field of the first DCI format, and When a second PDCCH providing the first DCI format is received on a secondary cell SCell, second information of a second field of the first DCI format, wherein the first DCI format schedules a physical uplink shared channel PUSCH transmission on the PCell; and a processor operably connected to the transceiver, the processor configured to determine: When a first PDCCH providing the first DCI format is received on the PCell, a first size of the first DCI format, a second size of the first DCI format when a second PDCCH providing the first DCI format is received on the SCell, wherein the second size is determined based on a first reference downlink DL bandwidth part (BWP) of the SCell when the SCell is deactivated, and a first number of padding bits, which is equal to the absolute difference between the first size and the second size, Wherein, the transceiver is further configured to receive: the first DCI format in the first PDCCH reception on the PCell, wherein when the first size is less than the second size, the first DCI format includes the first number of padding bits appended to a plurality of bits of the first field, or The first DCI format in the second PDCCH reception on the SCell, wherein when the second size is smaller than the first size, the first DCI format includes the first number of padding bits appended to a plurality of bits of the second field.

6. The UE according to claim 5, wherein: The first reference DL BWP is a first active DL BWP of the SCell after activation of the SCell.

7. The UE according to claim 5, wherein: When the active DL BWP on the SCell is a dormant DL BWP, the second size is determined based on a second reference DL BWP of the SCell.

8. The UE according to claim 7, wherein: The second reference DL BWP of the SCell is the first active DL BWP of the SCell after switching from the dormant DL BWP of the SCell.

9. A method performed by a base station in a wireless communication system, the method comprising: send: When the first physical downlink control channel PDCCH providing the first downlink control information DCI format is transmitted on the primary cell PCell, the first information of the first field of the first DCI format, and When providing a second PDCCH transmission of the first DCI format on a secondary cell SCell, second information of a second field of the first DCI format, wherein the first DCI format schedules a physical uplink shared channel PUSCH reception on the PCell; and Sure: When a first PDCCH providing the first DCI format is transmitted on the PCell, a first size of the first DCI format, a second size of the first DCI format when a second PDCCH transmission providing the first DCI format is on the SCell, wherein the second size is determined based on a first reference downlink DL bandwidth part (BWP) of the SCell when the SCell is deactivated, and a first number of padding bits, which is equal to the absolute difference between the first size and the second size, send: the first DCI format in the first PDCCH transmission on the PCell, wherein when the first size is less than the second size, the first DCI format includes the first number of padding bits appended to a plurality of bits of the first field, or The first DCI format in the second PDCCH transmission on the SCell, wherein when the second size is smaller than the first size, the first DCI format includes the first number of padding bits appended to a plurality of bits of the second field.

10. The method according to claim 9, wherein: The first reference DL BWP is a first active DL BWP of the SCell after activation of the SCell.

11. The method according to claim 9, wherein: When the active DL BWP on the SCell is a dormant DL BWP, the second size is determined based on a second reference DL BWP of the SCell.

12. A base station in a wireless communication system, the base station comprising: The transceiver is configured to send: When the first physical downlink control channel PDCCH providing the first downlink control information DCI format is transmitted on the primary cell PCell, the first information of the first field of the first DCI format, and When providing a second PDCCH transmission of the first DCI format on a secondary cell SCell, second information of a second field of the first DCI format, wherein the first DCI format schedules a physical uplink shared channel PUSCH reception on the PCell; and a processor operably connected to the transceiver, the processor configured to determine: When the first PDCCH providing the first DCI format is transmitted on the PCell, the first size of the first DCI format, a second size of the first DCI format when the second PDCCH providing the first DCI format is transmitted on the SCell, wherein the second size is determined based on a first reference downlink DL bandwidth part (BWP) of the SCell when the SCell is deactivated, and a first number of padding bits, which is equal to the absolute difference between the first size and the second size, Wherein, the transceiver is further configured to send: the first DCI format in the first PDCCH transmission on the PCell, wherein when the first size is less than the second size, the first DCI format includes the first number of padding bits appended to a plurality of bits of the first field, or The first DCI format in the second PDCCH transmission on the SCell, wherein when the second size is smaller than the first size, the first DCI format includes the first number of padding bits appended to a plurality of bits of the second field.

13. The base station according to claim 12, wherein: The first reference DL BWP is a first active DL BWP of the SCell after activation of the SCell.

14. The base station according to claim 12, wherein: When the active DL BWP on the SCell is a dormant DL BWP, the second size is determined based on a second reference DL BWP of the SCell.

15. The base station according to claim 14, wherein: The second reference DL BWP of the SCell is the first active DL BWP of the SCell after switching from the dormant DL BWP of the SCell.

Images