Method and apparatus for transmitting data and control information in a wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. An apparatus in a communication system and a method performed by the same are provided. The method performed by a user equipment (UE) in a wireless communication system, comprising: receiving, from a base station, configuration information relating to a switching between a primary serving cell (PCell) and a secondary serving cell (SCell); identifying a switching duration which comprises a first duration and a second duration based on the configuration information; receiving a plurality of semi-persistent scheduling (SPS) physical downlink shared channels (PDSCHs); generating a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook for the plurality of SPS PDSCHs; and transmitting, to the base station, a physical uplink control channel (PUCCH) for the HARQ-ACK codebook, wherein the HARQ-ACK codebook excludes HARQ-ACK information for at least one SPS PDSCH which overlaps with the switching duration.

Description

METHOD AND APPARATUS FOR TRANSMITTING DATA AND CONTROL INFORMATION IN A WIRELESS COMMUNICATION SYSTEM

[0001] The disclosure relates to communication technology, and more particularly, to an apparatus in a communication system and a method performed by the same.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz (THz) bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, 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 positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] The present disclosure provides method and apparatus for transmitting data and control information in a wireless communication system.

[0009] According to an aspect of an exemplary embodiment, there is provided method and apparatus for transmitting data and control information in a wireless communication system.

[0010] Aspects of the present disclosure provide efficient communication methods in a wireless communication system.

[0011] In order to illustrate the technical schemes of the embodiments of the disclosure more clearly, the drawings of the embodiments of the disclosure will be briefly introduced below. Apparently, the drawings described below only refer to some embodiments of the disclosure, and do not limit the disclosure. In the drawings:

[0012] FIG. 1 illustrates a schematic diagram of an example wireless network according to some embodiments of the disclosure;

[0013] FIGS. 2A and 2B illustrate example wireless transmission and reception paths according to some embodiments of the disclosure;

[0014] FIG. 3A illustrates an example user equipment (UE) according to some embodiments of the disclosure;

[0015] FIG. 3B illustrates an example gNB according to some embodiments of the disclosure;

[0016] FIG. 4 illustrates a block diagram of a first transceiving node according to some example embodiments of the disclosure;

[0017] FIG. 5 illustrates a block diagram of a second transceiving node according to some example embodiments of the disclosure;

[0018] FIG. 6 illustrates a flowchart of a method performed by a base station according to some example embodiments of the disclosure;

[0019] FIG. 7 illustrates a flowchart of a method performed by a UE according to some example embodiments of the disclosure;

[0020] FIGS. 8A-8C illustrate some examples of uplink transmission timing according to some example embodiments of the disclosure;

[0021] FIGS. 9A and 9B illustrate examples of time domain resource allocation tables according to some example embodiments of the disclosure;

[0022] FIG. 10 illustrates an example of a carrier-switching-pattern according to some example embodiments of the disclosure;

[0023] FIG. 11 illustrates an example of a carrier-switching-pattern according to some example embodiments of the disclosure;

[0024] FIG. 12 illustrates a flowchart of a method performed by a UE according to some example embodiments of the disclosure;

[0025] FIG. 13 illustrates a flowchart of a method performed by a base station according to some example embodiments of the disclosure.

[0026] FIG. 14 is a block diagram of a terminal or user equipment (UE) according to an embodiment of the disclosure.

[0027] FIG. 15 is a block diagram of a base station (BS) according to an embodiment of the disclosure.

[0028] FIG. 16 is a block diagram of a network entity according to an embodiment of the disclosure.

[0029] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0030] In describing the embodiments, descriptions related to technical contents well-known in the art and not associated directly with the disclosure will be omitted. Such an omission of unnecessary descriptions is intended to prevent obscuring of the main idea of the disclosure and more clearly transfer the main idea.

[0031] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.

[0032] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, in describing the disclosure, a detailed description of known functions or constitution incorporated herein will be omitted in the case that it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0033] Herein, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that perform the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).

[0034] Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks(or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.

[0035] As used in embodiments of the disclosure, a “~unit” may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word “~unit” does not always have a meaning limited to software or hardware. The “~unit” may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the “~unit” includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the “~unit” may be either combined into a smaller number of components and a “~unit,” or divided into additional components and a “~unit.” Moreover, the components and “~units” may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the “~unit” may include one or more processors.

[0036] It should be appreciated that the blocks in each flowchart and combinations of the flowcharts may be performed by one or more computer programs which include instructions. The entirety of the one or more computer programs may be stored in a single memory device or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0037] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like.

[0038] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0039] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0040] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0041] Hereinafter, the determination of priority between A and B in the present disclosure may refer to various actions such as selecting the one having a higher priority based on a predefined priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.

[0042] Hereinafter, "A or B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0043] In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0044] In addition, "at least one of A, B, or C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0045] Furthermore, "A / B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0046] Furthermore, "A, B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0047] Furthermore, "A and B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0048] Furthermore, “if condition A and condition B are satisfied,” as described in the present disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.

[0049] Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.

[0050] Furthermore, the terms “first ~”, “second ~”, etc., as described in the present disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, and may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.

[0051] Furthermore, even if “first ~” and “second ~” are described in the present disclosure, it may be understood that element(s) referred to by “first ~” and “second ~” may be the same or different. For example, in case of element(s) being information, first information and second information may both be same information and, in some cases, are separate and different information.

[0052] In addition, the terms “if ~” and “in case that ~” as used in the disclosure or claims may be interpreted to include the meanings of “when (or upon) ~,” “in response to ~,” “based on ~,” or “according to ~,” and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the present disclosure.

[0053] For example, the physical layer signaling may be referred to as Layer 1 (L1) signaling and may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

[0054] In addition, the term "not perform" as used in the present disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.

[0055] In addition, "transmitting a message including A and B" as described in the present disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.

[0056] In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.

[0057] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the present disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.

[0058] The drawings or flowcharts described below illustrate exemplary methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in a different order, or be repeated. In other examples, any step may be omitted or replaced with another step.

[0059] The methods and apparatuses proposed in the embodiments of the present disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the present disclosure may be modified and applied without significantly departing from the scope of the present disclosure, as would be understood by those skilled in the art.

[0060] In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0061] The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project (3GPP) technical specifications (TS) where appropriate.

[0062] Hereinafter, a base station is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a wireless access unit, a BS controller, or a node on a network.

[0063] Furthermore, the base station of the present disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the present disclosure may be equally applicable to 5G base station architectures in which such CU and DU functional splits are implemented.

[0064] A terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions.

[0065] In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a UE, and an uplink (UL) refers to a radio link through which a UE transmits a signal to a BS.

[0066] Furthermore, hereinafter, 5th generation (5G) mobile communication technologies (e.g., 5G new radio (NR)), 6th generation (6G) mobile communication technologies may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosure

[0067] In the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) refers to a physical channel through which data is transmitted, but the term PDSCH may also be used to refer to the data itself. That is, in the present disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel."

[0068] Hereinafter, in the context of the present disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), radio resource control (RRC), or medium access control (MAC) control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling.

[0069] In addition, L1 signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), downlink control information (DCI), user equipment (UE)-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.

[0070] Hereinafter, the expression that information is configured by the BS, as used in the present disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.

[0071] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.

[0072] In order to meet the increasing demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also called “Beyond 4G networks” or “Post-LTE systems”.

[0073] In order to achieve a higher data rate, 5G communication systems are implemented in higher frequency (millimeter, mmWave) bands, e.g., 60 GHz bands. In order to reduce propagation loss of radio waves and increase a transmission distance, technologies such as beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antenna, analog beamforming and large-scale antenna are discussed in 5G communication systems.

[0074] In addition, in 5G communication systems, developments of system network improvement are underway based on advanced small cell, cloud radio access network (RAN), ultra-dense network, device-to-device (D2D) communication, wireless backhaul, mobile network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancellation, etc.

[0075] In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM), and filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies have been developed.

[0076] In order to make the purpose, technical schemes and advantages of the embodiments of the disclosure clearer, the technical schemes of the embodiments of the disclosure will be described clearly and completely with reference to the drawings of the embodiments of the disclosure. Apparently, the described embodiments are a part of the embodiments of the disclosure, but not all embodiments. Based on the described embodiments of the disclosure, all other embodiments obtained by those of ordinary skill in the art without creative labor belong to the protection scope of the disclosure.

[0077] Before undertaking the DETAILED DESCRIPTION below, it can be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term “couple” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms “transmit,” “receive,” and “communicate,” as well as derivatives thereof, encompass both direct and indirect communication. The terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation. The term “or” is inclusive, meaning and / or. The phrase “associated with,” as well as derivatives thereof, means to include, be included within, connect to, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. 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 functionality associated with any particular controller can be centralized or distributed, whether locally or remotely. 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 only one item in the list can be needed. 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. For example, “at least one of: A, B, or C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A, B and C.

[0078] Moreover, various functions described below can be implemented or supported by one or more computer programs, each of which is formed from 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, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted 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 capable of being accessed by a computer, such as Read-Only Memory (ROM), Random Access Memory (RAM), a hard disk drive, a Compact Disc (CD), a Digital Video Disc (DVD), or any other type of memory. A “non-transitory” computer-readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer-readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.

[0079] Terms used herein to describe the embodiments of the disclosure are not intended to limit and / or define the scope of the present invention. For example, unless otherwise defined, the technical terms or scientific terms used in the disclosure shall have the ordinary meaning understood by those with ordinary skills in the art to which the present invention belongs.

[0080] It should be understood that “first”, “second” and similar words used in the disclosure do not express any order, quantity or importance, but are only used to distinguish different components. Similar words such as singular forms “a”, “an” or “the” do not express a limitation of quantity, but express the existence of at least one of the referenced item, unless the context clearly dictates otherwise. For example, reference to “a component surface” includes reference to one or more of such surfaces.

[0081] As used herein, any reference to “an example” or “example”, “an implementation” or “implementation”, “an embodiment” or “embodiment” means that particular elements, features, structures or characteristics described in connection with the embodiment is included in at least one embodiment. The phrases “in one embodiment” or “in one example” appearing in different places in the specification do not necessarily refer to the same embodiment.

[0082] As used herein, “a portion of” or “a part of” something means “at least some of” the thing, and as such may mean less than all of, or all of, the thing. As such, “a portion of” a thing includes the entire thing as a special case, i.e., the entire thing is an example of a portion of the thing.

[0083] As used herein, the term “set” may mean one or more. For example, a set of items may be a single item or a collection of two or more items.

[0084] In the disclosure, to determine whether a specific condition is satisfied or fulfilled, expressions, such as “greater than / larger than” or “less than / smaller than” are used by way of example and expressions, such as “greater than or equal to” or “less than or equal to” are also applicable and not excluded. For example, a condition defined with “greater than or equal to” may be replaced with “greater than” (or vice-versa), a condition defined with “less than or equal to” may be replaced with “less than” (or vice-versa), etc. As another example, “less than”, “less than or equal to” and “not greater than” may be used interchangeably. “Greater than”, “greater than or equal to”, and “not less than” may be used interchangeably.

[0085] It will be further understood that similar words such as the term “include” or “comprise” mean that elements or objects appearing before the word encompass the listed elements or objects appearing after the word and their equivalents, but other elements or objects are not excluded. Similar words such as “connect” or “connected” are not limited to physical or mechanical connection, but can include electrical connection, whether direct or indirect. “Upper”, “lower”, “left” and “right” are only used to express a relative positional relationship, and when an absolute position of the described object changes, the relative positional relationship may change accordingly.

[0086] The various embodiments discussed below for describing the principles of the disclosure in the patent document are for illustration only and should not be interpreted as limiting the scope of the disclosure in any way. Those skilled in the art will understand that the principles of the disclosure can be implemented in any suitably arranged wireless communication system. For example, although the following detailed description of the embodiments of the disclosure will be directed to LTE and / or 5G communication systems, those skilled in the art will understand that the main points of the disclosure can also be applied to other communication systems with similar technical backgrounds and channel formats with slight modifications without departing from the scope of the disclosure. The technical schemes of the embodiments of the present application can be applied to various communication systems, and for example, the communication systems may include global systems for mobile communications (GSM), code division multiple access (CDMA) systems, wideband code division multiple access (WCDMA) systems, general packet radio service (GPRS) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunications system (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, 5th generation (5G) systems or new radio (NR) systems, etc. In addition, the technical schemes of the embodiments of the present application can be applied to future-oriented communication technologies.

[0087] Hereinafter, the embodiments of the disclosure will be described in detail with reference to the accompanying drawings. It should be noted that the same reference numerals in different drawings will be used to refer to the same elements already described.

[0088] The text and drawings are provided as examples only to help readers understand the disclosure. They are not intended and should not be interpreted as limiting the scope of the disclosure in any way. Although certain embodiments and examples have been provided, based on the content disclosed herein, it will be apparent to those skilled in the art that changes may be made to the illustrated embodiments and examples without departing from the scope of the disclosure.

[0089] The following FIGS. 1- 3B describe various embodiments implemented by using orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication technologies in wireless communication systems. The descriptions of FIGS. 1- 3B do not mean physical or architectural implications for the manner in which different embodiments may be implemented. Different embodiments of the disclosure may be implemented in any suitably arranged communication systems.

[0090] According to some aspects of the present disclosure, a method performed by a user equipment (UE) in a communication system is provided. The method includes: receiving first information that configures switching between a primary serving cell (PCell) and a secondary serving cell (SCell) in time domain; receiving higher layer signaling that configures a set K1of first time unit timing values and a time domain resource allocation table for a serving cell c; determining, for the serving cell c, a set MA,cof occasions for candidate physical downlink shared channel (PDSCH) receptions, based on the set K1of first time unit timing values and a set R of row indexes of the time domain resource allocation table; and transmitting a physical uplink control channel (PUCCH) with a Type-1 hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook, wherein HARQ-ACK information bits in the Type-1 HARQ-ACK codebook are determined based on the set MA,cof occasions for candidate PDSCH receptions, wherein for a downlink time unit, in case that a PDSCH time resource for a row index r on the serving cell c overlaps with a non-operation period of the serving cell, the row index r is excluded from the set R of row indexes.

[0091] In combination with one or more aspects of the method performed by the UE described above, for example, it further includes, in case that a downlink time unit of the serving cell is the non-operation period, for the downlink time unit, excluding all row indexes from the setRof row indexes.

[0092] In combination with one or more aspects of the method performed by the UE described above, for example, it further includes, for a serving cell, not receiving a first downlink signal or channel on the serving cell, wherein the first downlink signal or channel is configured by higher layer signaling and overlaps with the non-operation period.

[0093] In combination with one or more aspects of the method performed by the UE described above, for example, it further includes, for a serving cell, not transmitting a first uplink signal or channel on the serving cell, wherein the first uplink signal or channel is configured by higher layer signaling and overlaps with the non-operation period.

[0094] In combination with one or more aspects of the method performed by the UE described above, for example, for a serving cell, the UE does not expect to receive a second downlink signal or channel on the serving cell scheduled by a DCI format, wherein the second downlink signal or channel overlaps with the non-operation period.

[0095] In combination with one or more aspects of the method performed by the UE described above, for example, for a serving cell, the UE does not expect to transmit a second uplink signal or channel on the serving cell scheduled by a DCI format, wherein the second uplink signal or channel overlaps with the non-operation period.

[0096] In combination with one or more aspects of the method performed by the UE described above, for example, it also includes, for a semi-persistent scheduling (SPS) PDSCH on a serving cell, in case that the SPS PDSCH overlaps with the non-operation period, not generating a HARQ-ACK information bit for the SPS PDSCH.

[0097] In combination with one or more aspects of the method performed by the UE described above, for example, it also includes, in case that there is more than one SPS PDSCH in a time unit of a serving cell, after resolving overlapping between the more than one SPS PDSCH and the non-operation period, receiving SPS PDSCHs by the UE according to a predefined method.

[0098] One or more aspects of the method performed by the UE described above further include, for example, determining overlapping PUCCHs and / or PUSCHs before considering a limitation for uplink transmissions due to the non-operation period.

[0099] According to some aspects of the present disclosure, a method performed by a base station in a communication system is provided. The method includes: transmitting, to a user equipment (UE), first information that configures switching between a primary serving cell (PCell) and a secondary serving cell (SCell) in time domain; transmitting, to the UE, higher layer signaling that configures a set K1of first time unit timing values and a time domain resource allocation table for a serving cell c; and receiving, from the UE, a physical uplink control channel (PUCCH) with a Type-1 hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook, wherein HARQ-ACK information bits in the Type-1 HARQ-ACK codebook are determined based on a set MA,cof occasions for candidate physical downlink shared channel (PDSCH) receptions, wherein for the serving cell c, the set MA,cof occasions for candidate PDSCH receptions is determined based on the set K1of first time unit timing values and a set R of row indexes of the time domain resource allocation table, wherein for a downlink time unit, in case that a PDSCH time resource for a row index r on the serving cell c overlaps with a non-operation period of the serving cell, the row index r is excluded from the set R of row indexes.

[0100] In combination with one or more aspects of the method performed by the base station described above, for example, in case that a downlink time unit of the serving cell is the non-operation period, for the downlink time unit, all row indexes are excluded from the setRof row indexes.

[0101] In combination with one or more aspects of the method performed by the base station described above, for example, for a serving cell, a first downlink signal or channel on the serving cell is not received, wherein the first downlink signal or channel is configured by higher layer signaling and overlaps with the non-operation period.

[0102] In combination with one or more aspects of the method performed by the base station described above, for example, for a serving cell, a first uplink signal or channel on the serving cell is not transmitted, wherein the first uplink signal or channel is configured by higher layer signaling and overlaps with the non-operation period.

[0103] In combination with one or more aspects of the method performed by the base station described above, for example, for a serving cell, the base station does not transmit a DCI format scheduling a second downlink signal or channel on the serving cell, wherein the second downlink signal or channel overlaps with the non-operation period.

[0104] In combination with one or more aspects of the method performed by the base station described above, for example, for a serving cell, the base station does not transmit a DCI format scheduling a second uplink signal or channel on the serving cell, wherein the second uplink signal or channel overlaps with the non-operation period.

[0105] In combination with one or more aspects of the method performed by the base station described above, for example, for a semi-persistent scheduling (SPS) PDSCH on a serving cell, in case that the SPS PDSCH overlaps with the non-operation period, a HARQ-ACK information bit for the SPS PDSCH is not generated.

[0106] In combination with one or more aspects of the method performed by the base station described above, in case that there is more than one SPS PDSCH in a time unit of a serving cell, after overlapping between the more than one SPS PDSCH and the non-operation period is resolved, SPS PDSCHs are received according to a predefined method.

[0107] In combination with one or more aspects of the method performed by the base station described above, for example, overlapping PUCCHs and / or PUSCHs are determined before considering a limitation for uplink transmissions due to the non-operation period.

[0108] According to some aspects of the disclosure, there is also provided a user equipment (UE) in a communication system. The UE includes a transceiver and one or more processors coupled with the transceiver and configured to perform one or more aspects of the methods described above as being performed by the UE.

[0109] According to some aspects of the disclosure, there is also provided a base station in a communication system. The base station includes a transceiver, and one or more processors coupled with the transceiver and configured to perform one or more aspects of the methods described above as being performed by the base station.

[0110] According to some aspects of the disclosure, there is also provided a computer-readable storage medium on which one or more computer programs are stored, wherein one or more aspects of the above-described methods performed by the UE can be implemented when the one or more computer programs are executed by one or more processors.

[0111] According to some aspects of the disclosure, there is also provided a computer-readable storage medium on which one or more computer programs are stored, wherein one or more aspects of the above-described methods performed by the base station can be implemented when the one or more computer programs are executed by one or more processors.

[0112] FIG. 1 illustrates an example wireless network 100 according to some embodiments of the disclosure. The embodiment of the wireless network 100 shown in FIG. 1 is for illustration only. Other embodiments of the wireless network 100 can be used without departing from the scope of the disclosure.

[0113] The wireless network 100 includes a gNodeB (gNB) 101, a gNB 102, and a gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one Internet Protocol (IP) network 130, such as the Internet, a private IP network, or other data networks.

[0114] Depending on a type of the network, other well-known terms such as “base station (BS)” or “access point” can be used instead of “gNodeB” or “gNB”. For convenience, the terms “gNodeB” and “gNB” are used in this patent document to refer to network infrastructure components that provide wireless access for remote terminals. And, depending on the type of the network, other well-known terms such as “mobile station”, “user station”, “remote terminal”, “wireless terminal” or “user apparatus” can be used instead of “user equipment” or “UE”. For example, the terms “terminal”, “user equipment” and “UE” may be used in this patent document to refer to remote wireless devices that wirelessly access the gNB, no matter whether the UE is a mobile device (such as a mobile phone or a smart phone) or a fixed device (such as a desktop computer or a vending machine).

[0115] gNB 102 provides wireless broadband access to the network 130 for a first plurality of User Equipments (UEs) within a coverage area 120 of gNB 102. The first plurality of UEs include a UE 111, which may be located in a Small Business (SB); a UE 112, which may be located in an enterprise (E); a UE 113, which may be located in a WiFi Hotspot (HS); a UE 114, which may be located in a first residence (R); a UE 115, which may be located in a second residence (R); a UE 116, which may be a mobile device (M), such as a cellular phone, a wireless laptop computer, a wireless PDA, etc. GNB 103 provides wireless broadband access to network 130 for a second plurality of UEs within a coverage area 125 of gNB 103. The second plurality of UEs include a UE 115 and a UE 116. In some implementations, one or more of gNBs 101-103 can communicate with each other and with UEs 111-116 using 5G, Long Term Evolution (LTE), LTE-A, WiMAX or other advanced wireless communication technologies.

[0116] The dashed lines show approximate ranges of the coverage areas 120 and 125, and the ranges are shown as approximate circles merely for illustration and explanation purposes. It should be clearly understood that the coverage areas associated with the gNBs, such as the coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on configurations of the gNBs and changes in the radio environment associated with natural obstacles and man-made obstacles.

[0117] As will be described in more detail below, one or more of gNB 101, gNB 102, and gNB 103 include a 2D antenna array as described in embodiments of the disclosure. In some implementations, one or more of gNB 101, gNB 102, and gNB 103 support codebook designs and structures for systems with 2D antenna arrays.

[0118] Although FIG. 1 illustrates an example of the wireless network 100, various changes can be made to FIG. 1. The wireless network 100 can include any number of gNBs and any number of UEs in any suitable arrangement, for example. Furthermore, gNB 101 can directly communicate with any number of UEs and provide wireless broadband access to the network 130 for those UEs. Similarly, each gNB 102-103 can directly communicate with the network 130 and provide direct wireless broadband access to the network 130 for the UEs. In addition, gNB 101, 102 and / or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0119] FIGS. 2A and 2B illustrate example wireless transmission and reception paths according to some embodiments of the disclosure. In the following description, the transmission path 200 can be described as being implemented in a gNB, such as gNB 102, and the reception path 250 can be described as being implemented in a UE, such as UE 116. However, it should be understood that the reception path 250 can be implemented in a gNB and the transmission path 200 can be implemented in a UE. In some implementations, the reception path 250 is configured to support codebook designs and structures for systems with 2D antenna arrays as described in embodiments of the disclosure.

[0120] The transmission path 200 includes a channel coding and modulation block 205, a Serial-to-Parallel (S-to-P) block 210, a size N Inverse Fast Fourier Transform (IFFT) block 215, a Parallel-to-Serial (P-to-S) block 220, a cyclic prefix addition block 225, and an up-converter (UC) 230. The reception path 250 includes a down-converter (DC) 255, a cyclic prefix removal block 260, a Serial-to-Parallel (S-to-P) block 265, a size N Fast Fourier Transform (FFT) block 270, a Parallel-to-Serial (P-to-S) block 275, and a channel decoding and demodulation block 280.

[0121] In the transmission path 200, the channel coding and modulation block 205 receives a set of information bits, applies coding (such as Low Density Parity Check (LDPC) coding), and modulates the input bits (such as using Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) to generate a sequence of frequency-domain modulated symbols. The Serial-to-Parallel (S-to-P) block 210 converts (such as demultiplexes) serial modulated symbols into parallel data to generate N parallel symbol streams, where N is a size of the IFFT / FFT used in gNB 102 and UE 116. The size N IFFT block 215 performs IFFT operations on the N parallel symbol streams to generate a time domain output signal. The Parallel-to-Serial block 220 converts (such as multiplexes) parallel time domain output symbols from the Size N IFFT block 215 to generate a serial time domain signal. The cyclic prefix addition block 225 inserts a cyclic prefix into the time domain signal. The up-converter 230 modulates (such as up-converts) the output of the cyclic prefix addition block 225 to an RF frequency for transmission via a wireless channel. The signal can also be filtered at a baseband before switching to the RF frequency.

[0122] The RF signal transmitted from gNB 102 arrives at UE 116 after passing through the wireless channel, and operations in reverse to those at gNB 102 are performed at UE 116. The down-converter 255 down-converts the received signal to a baseband frequency, and the cyclic prefix removal block 260 removes the cyclic prefix to generate a serial time domain baseband signal. The Serial-to-Parallel block 265 converts the time domain baseband signal into a parallel time domain signal. The Size N FFT block 270 performs an FFT algorithm to generate N parallel frequency-domain signals. The Parallel-to-Serial block 275 converts the parallel frequency-domain signal into a sequence of modulated data symbols. The channel decoding and demodulation block 280 demodulates and decodes the modulated symbols to recover the original input data stream.

[0123] Each of gNBs 101-103 may implement a transmission path 200 similar to that for transmitting to UEs 111-116 in the downlink, and may implement a reception path 250 similar to that for receiving from UEs 111-116 in the uplink. Similarly, each of UEs 111-116 may implement a transmission path 200 for transmitting to gNBs 101-103 in the uplink, and may implement a reception path 250 for receiving from gNBs 101-103 in the downlink.

[0124] Each of the components in FIGS. 2A and 2B can be implemented using only hardware, or using a combination of hardware and software / firmware. As a specific example, at least some of the components in FIGS. 2A and 2B may be implemented in software, while other components may be implemented in configurable hardware or a combination of software and configurable hardware. For example, the FFT block 270 and IFFT block 215 may be implemented as configurable software algorithms, in which the value of the size N may be modified according to the implementation.

[0125] Furthermore, although described as using FFT and IFFT, this is only illustrative and should not be interpreted as limiting the scope of the disclosure. Other types of transforms can be used, such as Discrete Fourier transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions. It should be understood that for DFT and IDFT functions, the value of variable N may be any integer (such as 1, 2, 3, 4, etc.), while for FFT and IFFT functions, the value of variable N may be any integer which is a power of 2 (such as 1, 2, 4, 8, 16, etc.).

[0126] Although FIGS. 2A and 2B illustrate examples of wireless transmission and reception paths, various changes may be made to FIGS. 2A and 2B. For example, various components in FIGS. 2A and 2B can be combined, further subdivided or omitted, and additional components can be added according to specific requirements. Furthermore, FIGS. 2A and 2B are intended to illustrate examples of types of transmission and reception paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communication in a wireless network.

[0127] FIG. 3A illustrates an example UE 116 according to some embodiments of the disclosure. The embodiment of UE 116 shown in FIG. 3A is for illustration only, and UEs 111-115 of FIG. 1 can have the same or similar configuration. However, a UE has various configurations, and FIG. 3A does not limit the scope of the disclosure to any specific implementation of the UE.

[0128] UE 116 includes an antenna 301, a radio frequency (RF) transceiver 302, a transmission (TX) processing circuit 303, a microphone 304, and a reception (RX) processing circuit 305. UE 116 also includes a speaker 306, a controller / processor 307, an input / output (I / O) interface 308, an input device(s) 309, a display 310, and a memory 311. The memory 311 includes an operating system (OS) 312 and one or more applications 313.

[0129] The RF transceiver 302 receives an incoming RF signal transmitted by a gNB of the wireless network 100 from the antenna 301. The RF transceiver 302 down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is transmitted to the RX processing circuit 305, where the RX processing circuit 305 generates a processed baseband signal by filtering, decoding and / or digitizing the baseband or IF signal. The RX processing circuit 305 transmits the processed baseband signal to speaker 306 (such as for voice data) or to controller / processor 307 for further processing (such as for web browsing data).

[0130] The TX processing circuit 303 receives analog or digital voice data from microphone 304 or other outgoing baseband data (such as network data, email or interactive video game data) from controller / processor 307. The TX processing circuit 303 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver 302 receives the outgoing processed baseband or IF signal from the TX processing circuit 303 and up-converts the baseband or IF signal into an RF signal transmitted via the antenna 301.

[0131] The controller / processor 307 can include one or more processors or other processing devices and execute an OS 312 stored in the memory 311 in order to control the overall operation of UE 116. For example, the controller / processor 307 can control the reception of forward channel signals and the transmission of backward channel signals through the RF transceiver 302, the RX processing circuit 305 and the TX processing circuit 303 according to well-known principles. In some implementations, the controller / processor 307 includes at least one microprocessor or microcontroller.

[0132] The controller / processor 307 is also capable of executing other processes and programs residing in the memory 311, such as operations for channel quality measurement and reporting for systems with 2D antenna arrays as described in embodiments of the disclosure. The controller / processor 307 can move data into or out of the memory 311 as required by an execution process. In some implementations, the controller / processor 307 is configured to execute the application 313 based on the OS 312 or in response to signals received from the gNB or the operator. The controller / processor 307 is also coupled to an I / O interface 308, where the I / O interface 308 provides UE 116 with the ability to connect to other devices such as laptop computers and handheld computers. I / O interface 308 is a communication path between these accessories and the controller / processor 307.

[0133] The controller / processor 307 is also coupled to the input device(s) 309 and the display 310. An operator of UE 116 can input data into UE 116 using the input device(s) 309. The display 310 may be a liquid crystal display or other display capable of presenting text and / or at least limited graphics (such as from a website). The memory 311 is coupled to the controller / processor 307. A part of the memory 311 can include a random access memory (RAM), while another part of the memory 311 can include a flash memory or other read-only memory (ROM).

[0134] Although FIG. 3A illustrates an example of UE 116, various changes can be made to FIG. 3A. For example, various components in FIG. 3A can be combined, further subdivided or omitted, and additional components can be added according to specific requirements. As a specific example, the processor / controller 340 can be divided into a plurality of processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Furthermore, although FIG. 3A illustrates that the UE 116 is configured as a mobile phone or a smart phone, UEs can be configured to operate as other types of mobile or fixed devices.

[0135] In some implementations, two or more UEs 116 may communicate directly using one or more sidelink channels (e.g., without using a base station as a medium for communication with each other). For example, the UE 116 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocol (which, for example, may include vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, etc.), mesh network, etc. In this case, the UE 116 may perform scheduling operations, resource selection operations, and / or other operations performed by the base station as described elsewhere herein. For example, the base station may configure the UE 116 via downlink control information (DCI), radio resource control (RRC) signaling, medium access control-control element (MAC-CE) or via system information (e.g., system information block (SIB)).

[0136] FIG. 3B illustrates an example gNB 102 according to some embodiments of the disclosure. The embodiment of gNB 102 shown in FIG. 3B is for illustration only, and other gNBs of FIG. 1 can have the same or similar configuration. However, a gNB has various configurations, and FIG. 3B does not limit the scope of the disclosure to any specific implementation of a gNB. It should be noted that gNB 101 and gNB 103 can include the same or similar structures as gNB 102.

[0137] As shown in FIG. 3B, gNB 102 includes a plurality of antennas 370a-370n, a plurality of RF transceivers 372a-372n, a transmission (TX) processing circuit 374, and a reception (RX) processing circuit 376. In certain embodiments, one or more of the plurality of antennas 370a-370n include a 2D antenna array. gNB 102 also includes a controller / processor 378, a memory 380, and a backhaul or network interface 382.

[0138] RF transceivers 372a-372n receive an incoming RF signal from antennas 370a-370n, such as a signal transmitted by UEs or other gNBs. RF transceivers 372a-372n down-convert the incoming RF signal to generate an IF or baseband signal. The IF or baseband signal is transmitted to the RX processing circuit 376, where the RX processing circuit 376 generates a processed baseband signal by filtering, decoding and / or digitizing the baseband or IF signal. RX processing circuit 376 transmits the processed baseband signal to controller / processor 378 for further processing.

[0139] The TX processing circuit 374 receives analog or digital data (such as voice data, network data, email or interactive video game data) from the controller / processor 378. TX processing circuit 374 encodes, multiplexes and / or digitizes outgoing baseband data to generate a processed baseband or IF signal. RF transceivers 372a-372n receive the outgoing processed baseband or IF signal from TX processing circuit 374 and up-convert the baseband or IF signal into an RF signal transmitted via antennas 370a-370n.

[0140] The controller / processor 378 can include one or more processors or other processing devices that control the overall operation of gNB 102. For example, the controller / processor 378 can control the reception of forward channel signals and the transmission of backward channel signals through the RF transceivers 372a-372n, the RX processing circuit 376 and the TX processing circuit 374 according to well-known principles. The controller / processor 378 can also support additional functions, such as higher-level wireless communication functions. For example, the controller / processor 378 can perform a Blind Interference Sensing (BIS) process such as that performed through a BIS algorithm, and decode a received signal from which an interference signal is subtracted. A controller / processor 378 may support any of a variety of other functions in gNB 102. In some implementations, the controller / processor 378 includes at least one microprocessor or microcontroller.

[0141] The controller / processor 378 is also capable of executing programs and other processes residing in the memory 380, such as a basic OS. The controller / processor 378 can also support channel quality measurement and reporting for systems with 2D antenna arrays as described in embodiments of the disclosure. In some implementations, the controller / processor 378 supports communication between entities such as web RTCs. The controller / processor 378 can move data into or out of the memory 380 as required by an execution process.

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

[0143] The memory 380 is coupled to the controller / processor 378. A part of the memory 380 can include an RAM, while another part of the memory 380 can include a flash memory or other ROMs. In certain embodiments, a plurality of instructions, such as the BIS algorithm, are stored in the memory. The plurality of instructions are configured to cause the controller / processor 378 to execute the BIS process and decode the received signal after subtracting at least one interference signal determined by the BIS algorithm.

[0144] As will be described in more detail below, the transmission and reception paths of gNB 102 (implemented using RF transceivers 372a-372n, TX processing circuit 374 and / or RX processing circuit 376) support aggregated communication with FDD cells and TDD cells.

[0145] Although FIG. 3B illustrates an example of gNB 102, various changes may be made to FIG. 3B. For example, gNB 102 can include any number of each component shown in FIG. 3A. As a specific example, the access point can include many backhaul or network interfaces 382, and the controller / processor 378 can support routing functions to route data between different network addresses. As another specific example, although shown as including a single instance of the TX processing circuit 374 and a single instance of the RX processing circuit 376, gNB 102 can include multiple instances of each (such as one for each RF transceiver).

[0146] Those skilled in the art will understand that, “terminal” and “terminal device” as used herein include not only devices with wireless signal receiver which have no transmitting capability, but also devices with receiving and transmitting hardware which can carry out bidirectional communication on a bidirectional communication link. Such devices may include cellular or other communication devices with single-line displays or multi-line displays or cellular or other communication devices without multi-line displays; a PCS (personal communications service), which may combine voice, data processing, fax and / or data communication capabilities; a PDA (Personal Digital Assistant), which may include a radio frequency receiver, a pager, an internet / intranet access, a web browser, a notepad, a calendar and / or a GPS (Global Positioning System) receiver; a conventional laptop and / or palmtop computer or other devices having and / or including a radio frequency receiver. “Terminal” and “terminal device” as used herein may be portable, transportable, installed in vehicles (aviation, sea transportation and / or land), or suitable and / or configured to operate locally, and / or in distributed form, operate on the earth and / or any other position in space. “Terminal” and “terminal device” as used herein may also be a communication terminal, an internet terminal, a music / video playing terminal, such as a PDA, a MID (Mobile Internet Device) and / or a mobile phone with music / video playing functions, a smart TV, a set-top box and other devices.

[0147] With the rapid development of information industry, especially the increasing demand from mobile Internet and internet of things (IoT), it brings unprecedented challenges to the future mobile communication technology. In order to meet the unprecedented challenges, the communication industry and academia have carried out extensive research on the fifth generation (5G) mobile communication technology to face the 2020s. At present in ITU report ITU-R M.[IMT.VISION], the framework and overall goals of the future 5G has been discussed, in which the demand outlook, application scenarios and important performance indicators of 5G are described in detail. With respect to new requirements in 5G, ITU report ITU-R M.[IMT.FUTURE TECHNOLOGY TRENDS] provides information related to the technology trends of 5G, aiming at solving significant problems such as significantly improved system throughput, consistent user experience, scalability to support IoT, delay, energy efficiency, cost, network flexibility, support of emerging services and flexible spectrum utilization. In 3GPP (3rd Generation Partnership Project), the first stage of 5G is already in progress. To support more flexible scheduling, the 3GPP decides to support variable hybrid automatic repeat request-acknowledgement (HARQ-ACK) feedback delay in 5G. In existing Long Term Evolution (LTE) systems, a time from reception of downlink data to uplink transmission of HARQ-ACK is fixed. For example, in Frequency Division Duplex (FDD) systems, the delay is 4 subframes. In Time Division Duplex (TDD) systems, a HARQ-ACK feedback delay is determined for a corresponding downlink subframe based on an uplink and downlink configuration. In 5G systems, whether FDD or TDD systems, for a determined downlink time unit (for example, a downlink slot or a downlink mini slot; for another example, a PDSCH time unit), the uplink time unit (for example, a PUCCH time unit) that can feedback HARQ-ACK is variable. For example, the delay of HARQ-ACK feedback can be dynamically indicated by physical layer signaling, or different HARQ-ACK delays can be determined based on factors such as different services or user capabilities.

[0148] The 3GPP has defined three directions of 5G application scenarios-eMBB (enhanced mobile broadband), mMTC (massive machine-type communication) and URLLC (ultra-reliable and low-latency communication). The eMBB scenario aims to further improve data transmission rate on the basis of the existing mobile broadband service scenario, so as to enhance user experience and pursue ultimate communication experience between people. mMTC and URLLC are, for example, the application scenarios of the Internet of Things, but their respective emphases are different: mMTC being mainly information interaction between people and things, while URLLC mainly reflecting communication requirements between things.

[0149] In some cases, the UE may be configured with a first number of serving cells. Due to the limited UE processing capability, the UE can only operate in a second number of serving cells simultaneously. For example, the second number is smaller than the first number. In this scenario, for example, in a carrier switching scenario, the data and control information reception / transmission method of the UE is required to be enhanced.

[0150] In order to at least solve the above technical problems, the example embodiments of the disclosure provide a method performed by a terminal, a terminal, a method performed by a base station, a base station and a non-transitory computer-readable storage medium in a wireless communication system. Hereinafter, various example embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0151] In the example embodiments of the disclosure, for the convenience of description, a first transceiving node and a second transceiving node are defined. For example, the first transceiving node may be a base station, and the second transceiving node may be a UE. For another example, the example embodiments of the disclosure may be applicable to the scenario of sidelink communication, in which case, the first transceiving node may be a UE, and the second transceiving node may be another UE. Therefore, the first transceiving node and the second transceiving node may each be any suitable communication node. In the following description, the base station is taken as an example (but not limited thereto) to illustrate the first transceiving node, and the UE is taken as an example (but not limited thereto) to illustrate the second transceiving node.

[0152] In describing a wireless communication system and in the disclosure described below, transferring methods (or configuration methods) of higher layer signaling or higher layer signals may be signal transferring methods for transferring information from a base station to a terminal over a downlink (DL) data channel of a physical layer or from a terminal to a base station over an uplink (UL) data channel of a physical layer, and examples of the signal transferring methods may include signal transferring methods for transferring information via Radio Resource Control (RRC) signaling, Packet Data Convergence Protocol (PDCP) signaling, or a Medium Access Control (MAC) Control Element (CE).

[0153] In the following description of the example embodiments of the disclosure, higher layer signaling may be signaling corresponding to at least one or a combination of one or more of the following signaling.

[0154] - MIB (master information block)

[0155] - SIB (system information block) or SIB X (X = 1,2, ...)

[0156] - RRC signaling

[0157] - MAC CE

[0158] Physical layer (Layer 1 (L1)) signaling may be signaling corresponding to at least one or a combination of one or more of the following signaling.

[0159] - PDCCH (physical downlink control channel)

[0160] - DCI (downlink control information)

[0161] - UE-specific DCI

[0162] - group common DCI

[0163] - common DCI (e.g., multicast DCI)

[0164] - scheduling DCI (e.g., DCI for scheduling downlink or uplink data)

[0165] - non-scheduling DCI (e.g., DCI other than DCI for scheduling downlink or uplink data)

[0166] - PUCCH (physical uplink control channel)

[0167] - UCI (uplink control information)

[0168] - Paging

[0169] - PRACH (physical random access channel)

[0170] - RAR (random access response)

[0171] In the example embodiments of the disclosure, uplink control signaling may include physical layer signaling and / or higher layer signaling. As described above, the physical layer signaling may include UCI and / or PUCCH and / or PRACH, and the higher layer signaling may include RRC signaling and / or a MAC CE.

[0172] In the example embodiments of the disclosure, downlink control signaling may include physical layer signaling and / or higher layer signaling. As mentioned above, the physical layer signaling may include one or more of PDCCH, DCI, UE-specific DCI, group common DCI, common DCI, scheduling DCI (e.g., DCI for scheduling downlink or uplink data), non-scheduling DCI, paging, and RAR, and the higher layer signaling may include one or more of a MIB, a SIB or SIB X (X = 1, 2, ...), RRC signaling or a MAC CE. Therefore, “configuring or indicating X through downlink control signaling” will be understood as configuring or indicating X through physical layer signaling, or configuring or indicating X through higher layer signaling, or configuring or indicating X through a combination of higher layer signaling and physical layer signaling.

[0173] FIG. 4 illustrates a block diagram of a first transceiving node 400 according to some example embodiments of the disclosure.

[0174] Referring to FIG. 4, the first transceiving node 400 may include a transceiver 401 and a controller 402.

[0175] The transceiver 401 may be configured to transmit first data and / or first control signaling to a second transceiving node, and / or receive second data and / or second control signaling from the second transceiving node.

[0176] The controller 402 may be an application specific integrated circuit or at least one processor. The controller 402 may be configured to control the overall operation of the first transceiving node 400, including controlling the transceiver 401 to transmit the first data and / or the first control signaling to the second transceiving node, and / or receive the second data and / or the second control signaling from the second transceiving node.

[0177] In some implementations, the controller 402 may be configured to perform one or more of operations in methods of various example embodiments described below, for example, operations that can be performed by a base station.

[0178] In the following description, the base station is taken as an example (but not limited thereto) to illustrate the first transceiving node, and the UE is taken as an example (but not limited thereto) to illustrate the second transceiving node. Downlink data (but not limited thereto) is used to illustrate the first data. Downlink control signaling (but not limited thereto) is used to illustrate the first control signaling. Uplink control signaling (but not limited thereto) is used to illustrate the second control signaling.

[0179] Herein, depending on the network type, the term “base station” or “BS” can refer to any component (or a set of components) configured to provide wireless access to a network, such as a Transmission Point (TP), a Transmission and Reception Point (TRP), an evolved base station (eNodeB or eNB), a 5G base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wireless network devices. Base stations may provide wireless access in accordance with one or more wireless communication protocols, e.g., 5G 3GPP new radio (NR) interface / access, Long Term Evolution (LTE), LTE advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc.

[0180] FIG. 5 illustrates a block diagram of a second transceiving node according to some embodiments of the disclosure.

[0181] Referring to FIG. 5, the second transceiving node 500 may include a transceiver 501 and a controller 502.

[0182] The transceiver 501 may be configured to receive first data and / or first control signaling from the first transceiving node, and transmit second data and / or second control signaling to the first transceiving node in a determined time unit.

[0183] The controller 502 may be an application specific integrated circuit or at least one processor. The controller 502 may be configured to control the overall operation of the second transceiving node and control the second transceiving node to implement the methods proposed in the example embodiments of the disclosure. For example, the controller 502 may be configured to determine the second data and / or the second control signaling and a time unit for transmitting the second data and / or the second control signaling based on the first data and / or the first control signaling, and control the transceiver 501 to transmit the second data and / or the second control signaling to the first transceiving node in the determined time unit.

[0184] In some implementations, the controller 502 may be configured to perform one or more of operations in methods of various example embodiments described below, for example, operations that can be performed by a terminal (UE).

[0185] In implementations described in connection with FIG. 4 or 5, the first data may be data transmitted by the first transceiving node to the second transceiving node. In the following examples, downlink data carried by a PDSCH (Physical Downlink Shared Channel) is taken as an example (but not limited thereto) to illustrate the first data.

[0186] In implementations described in connection with FIG. 4 or 5, the second data may be data transmitted by the second transceiving node to the first transceiving node. In the following examples, uplink data carried by a PUSCH (Physical Uplink Shared Channel) is taken as an example (but not limited thereto) to illustrate the second data.

[0187] In implementations described in connection with FIG. 4 or 5, the first control signaling may be control signaling transmitted by the first transceiving node to the second transceiving node. In the following examples, downlink control signaling is taken as an example (but not limited thereto) to illustrate the first control signaling. The downlink control signaling may be DCI (downlink control information) carried by a PDCCH (Physical Downlink Control Channel) and / or control signaling (e.g., higher signaling) carried by a PDSCH (Physical Downlink Shared Channel). For example, the DCI may be UE specific DCI, and the DCI may also be common DCI. The common DCI may be DCI common to a part of UEs, such as group common DCI, and the common DCI may also be DCI common to all of UEs in a serving cell (e.g., cell common DCI). The DCI may also be multicast DCI or broadcast DCI. The DCI may be uplink DCI (e.g., DCI for scheduling a PUSCH) and / or downlink DCI (e.g., DCI for scheduling a PDSCH).

[0188] It should be noted that in the description of the example embodiments of the disclosure, the following terms may be used interchangeably:

[0189] - DCI

[0190] - DCI format

[0191] - PDCCH

[0192] - grant

[0193] - dynamic grant.

[0194] In implementations described in connection with FIG. 4 or 5, the second control signaling may be control signaling transmitted by the second transceiving node to the first transceiving node. In the following examples, uplink control signaling is taken as an example (but is not limited thereto) to illustrate the second control signaling. The uplink control signaling may be UCI (Uplink Control Information) carried by a PUCCH (Physical Uplink Control Channel) and / or control signaling (e.g., higher signaling) carried by a PUSCH (Physical Uplink Shared Channel). A type of UCI may include one or more of: HARQ-ACK information, SR (Scheduling Request), LRR (Link Recovery Request), CSI (Chanel State Information), CG (Configured Grant) UCI, or UTO (unused transmission occasion)-UCI. In the example embodiments of the disclosure, when UCI is carried by a PUCCH, the UCI may be used interchangeably with the PUCCH.

[0195] In some implementations, a PUCCH with an SR may be a PUCCH with a positive SR and / or a negative SR. The SR may be the positive SR and / or the negative SR.

[0196] In some implementations, the CSI report may be Part 1 CSI and / or Part 2 CSI.

[0197] In implementations described in connection with FIG. 4 or 5, a time unit where the first transceiving node transmits the first data and / or the first control signaling may be a downlink time unit, such as a downlink slot.

[0198] In implementations described in connection with FIG. 4 or 5, a time unit where the second transceiving node transmits the second data and / or the second control signaling may be an uplink time unit, such as an uplink slot or PUCCH slot or PCell (primary cell) slot or PUCCH slot on PCell. The “PUCCH slot” may be understood as a PUCCH transmission slot.

[0199] In the example embodiments of the disclosure, a time unit (e.g., a downlink time unit or an uplink time unit) may be one or more slots, one or more sub-slots, one or more OFDM symbols, one or more spans, one or more subframes, one or more frames or one or more half frames.

[0200] FIG. 6 illustrates a flowchart of a method 600 performed by a base station according to some example embodiments of the disclosure.

[0201] Referring to FIG. 6, in operation S610, the base station transmits downlink data and / or downlink control signaling. For example, the base station transmits downlink data and / or downlink control signaling to the UE in a time unit.

[0202] In operation S620, the base station receives uplink data and / or uplink control signaling from the UE. For example, the base station receives the uplink data and / or the uplink control signaling from the UE in a time unit.

[0203] In some implementations, operations S610 and / or S620 may be performed based on the methods described according to various example embodiments of the disclosure (e.g., various methods / manners described below).

[0204] In some implementations, the method 600 may omit one or more of operation S610 or S620, or may include additional operations, for example, the operations performed by the base station based on the methods described according to various example embodiments of the disclosure (e.g., various methods / manners described below).

[0205] FIG. 7 illustrates a flowchart of a method 700 performed by a UE according to example embodiments of the disclosure.

[0206] Referring to FIG. 7, in operation S710, the UE may receive downlink (DL) data (e.g., downlink data carried by PDSCH(s)) and / or downlink control signaling from a base station. For example, the UE may receive the downlink data and / or the downlink control signaling from the base station based on predefined rules and / or received configuration parameters.

[0207] Optionally, in operation S720, the UE determines uplink (UL) data and / or uplink control signaling, and / or a transmission power of the uplink data and / or the uplink control signaling, and / or a time unit based on the downlink data and / or the downlink control signaling.

[0208] In operation S730, the UE transmits the uplink data and / or the uplink control signaling to the base station. For example, the UE transmits the uplink data and / or the uplink control signaling to the base station in the determined time unit. For another example, the UE transmits the uplink data and / or the uplink control signaling to the base station in the determined time unit according to the determined transmission power.

[0209] [HARQ / scheduling general timing]

[0210] In some implementations, operations S710 and / or S720 and / or S730 may be performed based on the methods described according to various example embodiments of the disclosure (e.g., various methods / manners described below).

[0211] In some implementations, the method 700 may omit one or more of operation S710, S720 or S730, or may include additional operations, for example, the operations performed by the UE (terminal) based on the methods described according to various example embodiments of the disclosure (e.g., various methods / manners described below).

[0212] In some implementations, acknowledgement / negative acknowledgement (ACK / NACK) for downlink transmission(s) may be performed through HARQ-ACK.

[0213] Some examples of uplink transmission timing will be described below with reference to FIGS. 8A-8C.

[0214] In an example, the UE receives a DCI format and receives a PDSCH according to time domain resources indicated by the DCI format. For example, a parameter K0 may be used to indicate a time unit interval (offset) between the PDSCH scheduled by the DCI format and the DCI format (e.g., a PDCCH carrying the DCI format), where K0 may be in units of slots, for example, PDSCH slots (e.g., slots of an active BWP in a serving cell where PDSCH is located). For example, FIG. 8A gives an example in which K0=1. In the example illustrated in FIG. 8A, the time unit interval from the PDSCH scheduled by the DCI format to the PDCCH carrying the DCI format is one slot. In the example embodiments of the disclosure, “the UE receives a DCI / DCI format” may refer to that “the UE detects the DCI / DCI format.”

[0215] In another example, the UE receives a DCI format and transmits a PUSCH based on time domain resources indicated by the DCI format. For example, a timing parameter K2 may be used to indicate a time unit interval between the PUSCH scheduled by the DCI format and the DCI format (e.g., a PDCCH carrying the DCI format), where K2 may be in units of slots, for example, PUSCH slots (e.g., slots of an active BWP in a serving cell where PUSCH is located). For example, FIG. 8B gives an example in which K2 = 1. In the example illustrated in FIG. 8B, the time unit interval between the PUSCH scheduled by the DCI format and the PDCCH carrying the DCI is one slot. K2 may also be used to indicate a time unit interval between a PDCCH for activating CG (configured grant) PUSCH(s) and the first activated CG PUSCH (e.g., CG PUSCH transmission occasion). In examples of the disclosure, unless otherwise specified, the PUSCH may be a dynamically scheduled PUSCH (e.g., scheduled by DCI) (e.g., which may be referred to as DG (dynamic grant) PUSCH, in the example embodiments of the disclosure) and / or a PUSCH not scheduled by DCI (e.g., CG PUSCH).

[0216] In yet another example, the UE receives a PDSCH, and may transmit HARQ-ACK information for the PDSCH reception in a PUCCH in a time unit (e.g., uplink time unit). For example, a timing parameter (which may also be referred to as a timing value) K1 (e.g., the higher layer parameter dl-DataToUL-ACK) may be used to indicate a time unit interval between the PUCCH with the HARQ-ACK information for the PDSCH reception and the PDSCH, and K1 may be in units of time units (e.g., uplink time units, such as PUCCH time units), such as slots or sub-slots. For example, FIG. 8A gives an example in which K1 = 3. In the example illustrated in FIG. 8A, the time unit interval between the PUCCH with the HARQ-ACK information for the PDSCH reception and the PDSCH is 3 slots. It should be noted that in the example embodiments of the disclosure, the timing parameter K1 may be used interchangeably with a time unit offset K1, the timing parameter K0 may be used interchangeably with a time unit offset K0, and the timing parameter K2 may be used interchangeably with a time unit offset K2.

[0217] The PDSCH may be a PDSCH scheduled by DCI and / or a SPS (semi-persistent scheduling) PDSCH. The UE periodically receives the SPS PDSCH after the SPS PDSCH is activated by the DCI. In examples of the disclosure, the SPS PDSCH may be equivalent to a PDSCH not scheduled by the DCI / PDCCH. After the SPS PDSCH is released (deactivated), the UE will no longer receive the SPS PDSCH.

[0218] In the example embodiments of the disclosure, HARQ-ACK may be HARQ-ACK for a SPS PDSCH reception (e.g., HARQ-ACK not indicated by DCI) and / or HARQ-ACK indicated by a DCI format (e.g., HARQ-ACK for a PDSCH reception scheduled by a DCI format, where the PDSCH reception may be a PDSCH reception providing a transport block (TB) with enabled HARQ-ACK information). Or, for example, HARQ-ACK may be HARQ-ACK for a DCI format without scheduling PDSCH.

[0219] In yet another example, the UE receives DCI (e.g., DCI indicating SPS PDSCH release (deactivation)), and may transmit HARQ-ACK information for the DCI in a PUCCH in a time unit (e.g., uplink time unit). For example, the timing parameter K1 may be used to indicate a time unit interval between the PUCCH with the HARQ-ACK information for the DCI and the DCI, and K1 may be in units of time units (e.g., uplink time units), such as slots or sub-slots. For example, FIG. 8C gives an example in which K1 = 3. In the example of FIG. 8C, the time unit interval between the PUCCH with the HARQ-ACK information for the DCI and the DCI is 3 slots. For example, the timing parameter K1 may be used to indicate a time unit interval between a PDCCH reception carrying DCI indicating SPS PDSCH release (deactivation) and the PUCCH feeding back HARQ-ACK for the PDCCH reception.

[0220] In some implementations, the UE may report (or signal / transmit) a UE capability to the base station or indicate the UE capability in operation S720. For example, the UE reports (or signals / transmits) the UE capability to the base station by transmitting a PUSCH. In this case, the PUSCH transmitted by the UE includes the UE capability information. A UE capability may be a UE capability parameter, or a value of a UE capability parameter.

[0221] In some implementations, the base station may configure higher layer signaling for the UE based on a UE capability received from the UE.

[0222] In some implementations, downlink channels (downlink resources) may include PDCCHs and / or PDSCHs. Uplink channels (uplink resources) may include PUCCHs and / or PUSCHs.

[0223] [Two levels of priorities]

[0224] In some implementations, the UE may be configured with two levels of priorities for uplink transmission (for example, the UE is configured with the higher layer parameterPUCCH-ConfigurationList). The PUCCH resource configured by the first PUCCH-Config is a PUCCH resource of a lower priority, and the PUCCH resource configured by the second PUCCH-Config is a PUCCH resource of a higher priority. For another example, the priority of a PUCCH or a PUSCH may be indicated by a DCI format, for example, by a physical layer priority index (phy-PriorityIndex) field.

[0225] When two or more uplink physical channels on a serving cell overlap (for example, overlap in time), or PUCCH(s) and PUSCH(s) overlap (for example, overlap in time), it is necessary to resolve the overlapping for the physical channels. “Resolving the overlapping for the physical channels” may refer to “resolving the collision of overlapping physical channels”. The resulting physical channels after resolving the overlapping for the physical channels do not overlap or collide. The overlapping of physical channels may be resolved by multiplexing and / or prioritization. The multiplexing may refer to multiplexing UCI of two or more physical channels in a physical channel. For example, the multiplexing of multiple PUCCHs and / or PUSCHs that overlap in time domain may include multiplexing UCI of the PUCCHs in a PUCCH or PUSCH. It should be noted that in the description of the example embodiments of the disclosure, “resolving the overlapping for the physical channels” may also be used interchangeably with “determining the overlapping for the physical channels”. The prioritization may refer to transmitting a physical channel of the higher priority and not transmitting a physical channel of the lower priority. It should be noted that in the description of the example embodiments of the disclosure, “Not transmitting a physical channel”, “cancelling the transmission of a physical channel”, “stopping the transmission of a physical channel”, and “deprioritizing the priority of a physical channel” may be used interchangeably. For example, the prioritization of two PUCCHs and / or PUSCHs overlapping in time domain by the UE may include that the UE transmits the PUCCH or the PUSCH of the higher priority and / or the UE does not transmit the PUCCH or the PUSCH of the lower priority. In embodiments of the disclosure, unless otherwise indicated, “resolving the overlapping of physical channels” may be understood as resolving the overlapping of physical channels with the same physical layer priority.

[0226] In some implementations, if the UE is configured / indicated to multiplex UCIs (e.g., HARQ-ACK) of different priorities via higher layer signaling (e.g., via higher layer parameteruci-MuxWithDiffPrio), when resolving the overlapping for physical channels with different priorities, the UE may multiplex UCIs (e.g., HARQ-ACK) with different priorities; otherwise (e.g., if the UE is not configured the parameter for multiplexing UCIs with different priorities), when resolving the overlapping for physical channels with different priorities, the UE performs prioritization for PUCCHs and / or PUSCHs with different priorities.

[0227] For example, the two levels of priorities may include a first priority and a second priority which are different from each other. In an example, the first priority may be higher than the second priority; for example, the first priority is the higher priority, and the second priority is the lower priority. In another example, the first priority may be lower than the second priority. However, embodiments of the disclosure are not limited to this, and for example, the UE may be configured with more than two levels of priorities. For the sake of convenience, in some example embodiments of the disclosure, description will be made considering that the first priority is higher than the second priority. It should be noted that all embodiments of the disclosure are applicable to situations where the first priority may be higher than the second priority; all embodiments of the disclosure are applicable to situations where the first priority may be lower than the second priority; and all embodiments of the disclosure are applicable to situations where the first priority may be equal to the second priority. In some example embodiments of the disclosure, the terms “first priority”, “higher priority”, “greater priority index” and “priority index 1” may be used interchangeably. In the example embodiments of the disclosure, the terms “second priority”, “lower priority”, “smaller priority index” and “priority index 0” may be used interchangeably.

[0228] [Sub-slot]

[0229] In some implementations, the UE may be configured with a sub-slot-based PUCCH transmission. For example, a sub-slot length parameter (which may also be referred to as a parameter with respect to a sub-slot length in the example embodiments of the disclosure) (e.g., the higher layer parameter sub-slotLengthForPUCCH) of each PUCCH configuration parameter of the first PUCCH configuration parameter and the second PUCCH configuration parameter may be 7 OFDM symbols or 6 OFDM symbols or 2 OFDM symbols. Sub-slot configuration length parameters in different PUCCH configuration parameters may be configured separately. If no sub-slot length parameter is configured in a PUCCH configuration parameter, the scheduling time unit of the PUCCH configuration parameter is one slot by default. If a sub-slot length parameter is configured in the PUCCH configuration parameter, the scheduling time unit of the PUCCH configuration parameter is L (L is the configured sub-slot configuration length) OFDM symbols.

[0230] The mechanism of a slot-based PUCCH transmission is basically the same as that of a sub-slot-based PUCCH transmission. In the disclosure, a slot may be used to represent a PUCCH occasion unit; for example, if the UE is configured with sub-slots, a slot which is a PUCCH occasion unit may be replaced with a sub-slot. For example, it may be specified by protocols that if the UE is configured with the sub-slot length parameter (e.g., the higher layer parameter sub-slotLengthForPUCCH), unless otherwise indicated, a number of symbols included in the slot of the PUCCH transmission is indicated by the sub-slot length parameter.

[0231] For example, if the UE is configured with the sub-slot length parameter, and a sub-slot n is the last uplink sub-slot overlapping with a PDSCH reception or PDCCH reception (e.g., SPS PDSCH release, and / or indicating SCell dormancy, and / or triggering a Type-3 HARQ-ACK codebook report and without scheduling PDSCH reception), then HARQ-ACK information for the PDSCH reception or PDCCH reception is transmitted in an uplink sub-slot n+k, where k is determined by the timing parameter K1 (the definition of the timing parameter K1 may refer to the previous description). For another example, if the UE is not configured with the sub-slot length parameter, and a slot n is the last uplink slot overlapping with a downlink slot where the PDSCH reception or PDCCH reception is located, then the HARQ-ACK information for the PDSCH reception or PDCCH reception is transmitted in an uplink slot n+k, where K is determined by the timing parameter K1.

[0232] [Multicast service (MBS)]

[0233] In the example embodiments of the disclosure, unicast may refer to a manner in which a network communicates with a UE, and multicast (or groupcast) may refer to a manner in which a network communicates with multiple UEs. For example, a unicast PDSCH may be a PDSCH received by one UE, and scrambling of the PDSCH may be based on a Radio Network Temporary Identifier (RNTI) specific to the UE, e.g., Cell-RNTI (C-RNTI). A multicast PDSCH may be a PDSCH received by more than one UE simultaneously, and scrambling of the multicast PDSCH may be based on a UE-group common RNTI. For example, the UE-group common RNTI for scrambling the multicast PDSCH may include an RNTI (which may be referred to as Group RNTI (G-RNTI) in the example embodiments of the disclosure) for scrambling of a dynamically scheduled multicast transmission (e.g., PDSCH) or an RNTI (which may be referred to as group configured scheduling RNTI (G-CS-RNTI) in the example embodiments of the disclosure) for scrambling of a multicast SPS transmission (e.g., SPS PDSCH). UCI of the unicast PDSCH may include HARQ-ACK information, an SR, or CSI of the unicast PDSCH reception. UCI of the multicast PDSCH may include HARQ-ACK information of the multicast PDSCH reception. In the example embodiments of the disclosure, “multicast” may also be replaced with “broadcast”.

[0234] [HARQ-ACK codebook]

[0235] In the example embodiment as shown in FIG. 7, in operation S710, the UE may receive downlink data (e.g., downlink data carried by PDSCH(s)) and / or downlink control signaling (e.g., DCI format(s) carried by PDCCH(s)) from the base station.

[0236] In operation S720, the UE may determine HARQ-ACK information bits transmitted in an uplink slot based on the downlink data and / or the downlink control signaling. For example, determining the HARQ-ACK information bits transmitted in the uplink slot includes at least one of the following:

[0237] - determining values of the HARQ-ACK information bits;

[0238] - determining the order of the HARQ-ACK information bits;

[0239] - determining a total number of the HARQ-ACK information bits.

[0240] In operation S730, the UE transmits the HARQ-ACK information bits to the base station. Here, the UE may transmit the HARQ-ACK information bits in a PUCCH or PUSCH.

[0241] In some implementations, a HARQ-ACK codebook may include HARQ-ACK information (in the disclosure, which may also be called HARQ-ACK information bits) for one or more PDSCH receptions and / or DCI format(s) (e.g., DCI format without scheduling PDSCH reception). HARQ-ACK information for a PDSCH reception may be understood as HARQ-ACK information for transport block(s) (TB(s)) included in the PDSCH reception. In case that the UE is configured with PDSCH CBG (code block group) transmission (for example, the parameterPDSCH-CodeBlockGroupTransmissionis configured), or in case that one PDSCH reception includes one or more CBGs, HARQ-ACK information for a PDSCH reception may be understood as HARQ-ACK information for the CBGs included in the PDSCH reception. If HARQ-ACK information for one or more PDSCH receptions and / or DCI(s) is multiplexed in a time unit (e.g., uplink time unit) for transmission (e.g., transmission in a PUCCH in a same time unit), the UE may generate the HARQ-ACK codebook based on a predefined rule. The UE generating the HARQ-ACK codebook may include ordering the HARQ-ACK information bits and / or compressing (e.g., bundling) the HARQ-ACK information bits. For example, if a TB or CBG in a PDSCH reception is successfully decoded, HARQ-ACK information for the TB or CBG in the PDSCH reception is positive ACK. The positive ACK may be represented by 1 in the HARQ-ACK codebook, for example. If a TB or CBG in a PDSCH reception is not successfully decoded, HARQ-ACK information for the TB or CBG in the PDSCH reception is negative ACK (NACK). The NACK may be represented by 0 in the HARQ-ACK codebook, for example. For example, the UE may generate the HARQ-ACK codebook based on pseudo-codes specified by protocols. In an example, if the UE receives a DCI format that indicates SPS PDSCH release (deactivation), the UE transmits HARQ-ACK information (ACK) for the DCI format. In another example, if the UE receives a DCI format that indicates secondary cell dormancy, the UE transmits HARQ-ACK information (ACK) for the DCI format. In yet another example, if the UE receives a DCI format that indicates to transmit HARQ-ACK information (e.g., a Type-3 HARQ-ACK codebook) of all HARQ-ACK processes of all configured serving cells, the UE transmits the HARQ-ACK information of all of the HARQ-ACK processes of all of the configured serving cells. In order to reduce a size of the Type-3 HARQ-ACK codebook, in an enhanced Type-3 HARQ-ACK codebook, the UE may transmit HARQ-ACK information of a specific HARQ-ACK process of a specific serving cell based on an indication of the DCI. In yet another example, if the UE receives a DCI format that schedules a PDSCH reception, the UE transmits HARQ-ACK information for the PDSCH reception. In yet another example, the UE receives a SPS PDSCH, and the UE transmits HARQ-ACK information for the SPS PDSCH reception. In yet another example, if the UE is configured by higher layer signaling to receive a SPS PDSCH, the UE transmits HARQ-ACK information for the SPS PDSCH reception. The reception of the SPS PDSCH configured by higher layer signaling may be cancelled by other signaling. In yet another example, if at least one uplink symbol (e.g., OFDM symbol) of the UE in a semi-static frame structure configured by higher layer signaling overlaps with a symbol of the SPS PDSCH reception, the UE does not receive the SPS PDSCH. In yet another example, if the UE is configured by higher layer signaling to receive a SPS PDSCH according to a predefined rule, the UE transmits HARQ-ACK information for the SPS PDSCH reception. It should be noted that, in the example embodiments of the disclosure, “'A' overlaps with 'B'” may mean that 'A' at least partially overlaps with 'B'. That is, “'A' overlaps with 'B'” includes a case where 'A' completely overlaps with 'B'. “'A' overlaps with 'B'” may mean that 'A' overlaps with 'B' in time domain and / or 'A' overlaps with 'B' in frequency domain.

[0242] In some implementations, if HARQ-ACK information transmitted (or multiplexed) in a same time unit (e.g., uplink time unit) does not include HARQ-ACK information for any DCI format, nor does it include HARQ-ACK information for a dynamically scheduled PDSCH reception (e.g., a PDSCH reception scheduled by a DCI format) and / or DCI, or the HARQ-ACK information transmitted (or multiplexed) in the same time unit (e.g., uplink time unit) only includes HARQ-ACK information for one or more SPS PDSCH receptions, the UE may generate HARQ-ACK information (e.g., HARQ-ACK information only for SPS PDSCH receptions) according to a rule for generating a HARQ-ACK codebook for SPS PDSCH receptions. The UE may multiplex the HARQ-ACK information only for SPS PDSCH receptions in a specific PUCCH resource. For example, if the UE is configured with a PUCCH list parameter for SPS (e.g.,SPS-PUCCH-AN-List), the UE multiplexes the HARQ-ACK information only for SPS PDSCH receptions in a PUCCH of a PUCCH list for SPS. For example, the UE determines a PUCCH resource in the PUCCH list for the SPS according to a number of HARQ-ACK information bits. If the UE is not configured with the PUCCH list parameter for SPS, the UE multiplexes the HARQ-ACK information only for SPS PDSCH receptions in a PUCCH resource specific to SPS HARQ-ACK (for example, the PUCCH resource is configured by the parametern1PUCCH-AN).

[0243] In some implementations, if HARQ-ACK information transmitted (or multiplexed) in a same time unit (e.g., uplink time unit) includes HARQ-ACK information for a DCI format, and / or a dynamically scheduled PDSCH reception (e.g., a PDSCH reception scheduled by a DCI format), the UE may generate HARQ-ACK information according to a rule for generating a HARQ-ACK codebook for a dynamically scheduled PDSCH reception and / or a DCI format. For example, the UE may determine to generate a semi-static HARQ-ACK codebook (e.g., Type-1 HARQ-ACK codebook) or a dynamic HARQ-ACK codebook (e.g., Type-2 HARQ-ACK codebook) according to a HARQ-ACK codebook configuration parameter for a PDSCH reception (e.g., the higher layer parameter pdsch-HARQ-ACK-Codebook). For example, if the UE is configured with the HARQ-ACK codebook configuration parameter (e.g., higher layer parameter pdsch-HARQ-ACK-Codebook) as semi-static, the UE may generate a semi-static HARQ-ACK codebook. If the UE is configured with the HARQ-ACK codebook configuration parameter (e.g., higher layer parameter pdsch-HARQ-ACK-Codebook) as dynamic, the UE may generate a dynamic HARQ-ACK codebook. The dynamic HARQ-ACK codebook may also be an enhanced dynamic HARQ-ACK codebook (e.g., Type-2 HARQ-ACK codebook based on grouping and HARQ-ACK retransmission). The UE may multiplex the HARQ-ACK information in a PUCCH resource for HARQ-ACK associated with dynamically scheduling, which may be configured in a resource set list parameter (e.g., parameter resourceSetToAddModList). The UE determines a PUCCH resource set (e.g., parameter PUCCH-ResourceSet) in a resource set list according to a number of HARQ-ACK information bits, and the PUCCH resource may be determined as a PUCCH in the PUCCH resource set according to a PRI (PUCCH Resource Indicator) field indication in the last DCI format.

[0244] In some implementations, if HARQ-ACK information transmitted (multiplexed) in a same time unit (e.g., uplink time unit) includes only HARQ-ACK information for SPS PDSCH receptions (e.g., PDSCH receptions not scheduled by DCI formats), the UE may generate the HARQ-ACK codebook according to a rule for generating a HARQ-ACK codebook for SPS PDSCH receptions (e.g., the pseudo-code for a HARQ-ACK codebook for SPS PDSCH receptions).

[0245] [Type-1 HARQ-ACK codebook]

[0246] The semi-static HARQ-ACK codebook (e.g., Type-1 HARQ-ACK codebook), may determine the size of the HARQ-ACK codebook and an order of HARQ-ACK information bits according to a semi-statically configured parameter (e.g., a parameter configured by higher layer signaling).

[0247] For a serving cell c, an active downlink BWP (bandwidth part), and an active uplink BWP, the UE determines a set of MA,coccasions for candidate PDSCH receptions for which the UE can transmit corresponding HARQ-ACK information in a PUCCH in an uplink slot nU.

[0248] MA,cmay be determined by at least one of the following:

[0249] a) a set of HARQ-ACK slot timing values K1 associated with the active uplink BWP on a primary cell or PUCCH-sScell (PUCCH switching SCell);

[0250] b) a set of row indexes of a time domain resource allocation (TDRA) table associated with the active downlink BWP;

[0251] c) where is the configuration of a downlink subcarrier spacing (SCS) of the downlink active BWP, and is the configuration of an uplink subcarrier spacing of the active uplink BWP.

[0252] d) a semi-static uplink and downlink frame structure configuration, such as the parametertdd-UL-DL-ConfigurationCommonand the parametertdd-UL-DL-ConfigurationDedicated.

[0253] e) a downlink slot offset parameter (e.g., the higher layer parameter ) for the serving cellcand its corresponding slot offset SCS (e.g., the higher layer parameter ), and a slot offset parameter (e.g., the higher layer parameter ) for a primary cell and its corresponding slot offset SCS (e.g., the higher layer parameter ).

[0254] In the description of the example embodiments of the disclosure, the set of the parameter K1 is used to determine a candidate uplink slot, and then determine candidate downlink slots according to the candidate uplink slot. The candidate downlink slots satisfy at least one of the following conditions: (i) if the time unit of the PUCCH is a sub-slot, the end of at least one candidate PDSCH reception in the candidate downlink slots overlaps with the candidate uplink slot in time domain; or (ii) if the time unit of the PUCCH is a slot, the end of the candidate downlink slots overlaps with the candidate uplink slot in time domain. It should be noted that in the description of the example embodiments of the disclosure, a starting symbol may be used interchangeably with a starting position, and an end symbol may be used interchangeably with an end position. In some implementations, the starting symbol may be replaced with the end symbol, and / or the end symbol may be replaced with the starting symbol.

[0255] A number of PDSCH receptions in a candidate downlink slot for which HARQ-ACK needs to be fed back is determined by a maximum value of a number of non-overlapping valid candidate PDSCH receptions in the downlink slot (e.g., the valid candidate PDSCH receptions may be candidate PDSCH receptions that do not overlap with semi-statically configured uplink symbols). Time domain resources occupied by the candidate PDSCH receptions may be determined by (i) a time domain resource allocation table configured by higher layer signaling (in the example embodiments of the disclosure, it may also be referred to as a table associated with time domain resource allocation) and (ii) a certain row in time domain resource allocation table dynamically indicated by a DCI. Each row in time domain resource allocation table may define information with respect to time domain resource allocation. For example, for the time domain resource allocation table, an indexed row defines a timing value (e.g., time unit (e.g., slot) offset (e.g., K0)) between a PDCCH and a PDSCH, and a start and length indicator (SLIV), or directly defines a starting symbol and allocation length. For example, for the first row of the time domain resource allocation table, a starting OFDM symbol is 0 and an OFDM symbol length is 4; for the second row of the time domain resource allocation table, the starting OFDM symbol is 4 and the OFDM symbol length is 4; and for the third row of the time domain resource allocation table, the starting OFDM symbol is 7 and the OFDM symbol length is 4. The DCI for scheduling the PDSCH may indicate any row in time domain resource allocation table. When all OFDM symbols in the downlink slot are downlink symbols, the maximum value of the number of non-overlapping valid PDSCHs in the downlink slot is 2. At this time, the Type-1 HARQ-ACK codebook may need to feed back HARQ-ACK information for two PDSCHs in the downlink slot on the serving cell.

[0256] FIGS. 9A and 9B illustrate examples of time domain resource allocation (TDRA) tables. Specifically, FIG. 9A shows a row of a time domain resource allocation table for scheduling one PDSCH, and FIG. 9B shows a row a of time domain resource allocation table for scheduling multiple PDSCHs. Referring to FIG. 9A, each row corresponds to a {K0, mapping type, SLIV} set that includes a timing parameter K0 value, a mapping type, and a SLIV. Referring to FIG. 9B, unlike Figure 9A, each row corresponds to multiple {K0, mapping type, SLIV} sets.

[0257] [Type-2 HARQ-ACK codebook]

[0258] In some implementations, the dynamic HARQ-ACK codebook (e.g., Type-2 HARQ-ACK codebook) and / or the enhanced dynamic HARQ-ACK codebook (e.g., Type-2 HARQ-ACK based on grouping and HARQ-ACK retransmission) may determine a size and an order of the HARQ-ACK codebook according to an assignment indicator. For example, the assignment indicator may be a DAI (Downlink Assignment Indicator). In the following embodiments, the assignment indicator as the DAI is taken as an example for illustration. However, the example embodiments of the disclosure are not limited thereto, and any other suitable assignment indicator may be adopted. It should be noted that the method for dynamic HARQ-ACK codebook in the disclosure may also be used for enhanced dynamic HARQ-ACK codebook.

[0259] In some implementations, the DAI may include at least one of a first DAI and a second DAI.

[0260] In some examples, the first DAI may be a C-DAI (Counter-DAI), and the first DAI may be a cumulative number of the downlink assignment index. The value of the first DAI field in a DCI format is a cumulative number of {serving cell, PDCCH monitoring occasion (MO)}-pair(s) up to the current serving cell and the current time unit, where the time unit may be a time unit of the PDCCH reception, for example, PDCCH monitoring occasion. The {serving cell, PDCCH MO}-pairs may include DCI formats scheduling PDSCH receptions and / or DCI formats having associated / corresponding HARQ-ACK information bits without scheduling PDSCH receptions. The first DAI may be included in a downlink DCI format. HARQ-ACK information for a PDSCH reception scheduled by a DCI format and / or a DCI format without scheduling PDSCH reception is transmitted in a same time unit (for example, transmitted in a same PUCCH in a same time unit). The second DAI may be T-DAI (Total-DAI). The second DAI may be a total number of the downlink assignment index. The value of the second DAI field in a DCI format may be a total number of {serving cell, PDCCH MO}-pair(s) up to the current time unit. The second DAI may be included in a downlink DCI format and / or an uplink DCI format. The second DAI included in an uplink DCI format may be also called UL DAI.

[0261] In some implementations, the first DAI may be sorted in the following order:

[0262] - first in ascending order of serving cell index (e.g. scheduled serving cell index), and

[0263] - second in ascending order of PDCCH MO index.

[0264] In some implementations, the first DAI may also be sorted in the following order. For example, if the UE reports a capability to support more than one PDSCH reception on a serving cell scheduled from a PDCCH MO (e.g., PDSCH receptions scheduled by more than one PDCCH), the first DAI may be sorted in the following order:

[0265] - first in increasing order of the PDSCH reception starting time (e.g., the PDSCH reception starting time for the same {serving cell, PDCCH MO}-pair),

[0266] - second in ascending order of serving cell index (e.g., scheduled serving cell index), and

[0267] - third in ascending order of PDCCH MO index.

[0268] In some examples, the first DAI may be a C-DAI (Counter-DAI). The first DAI may indicate an accumulative number of at least one of DCI scheduling PDSCH reception(s), DCI format(s) indicating SPS PDSCH release (deactivation), or DCI indicating secondary cell dormancy. For example, the accumulative number may be an accumulative number up to the current serving cell and / or the current time unit. For example, the C-DAI may also indicate: an accumulative number of {serving cell, time unit} pair(s) scheduled by PDCCH(s) up to the current time unit within a time window (which may also include a number of PDCCHs (e.g., PDCCHs indicating SPS release and / or PDCCHs indicating secondary cell dormancy)); or an accumulative number of PDCCH(s) up to the current time unit; or an accumulative number of PDSCH transmission(s) up to the current time unit; or an accumulative number of {serving cell, time unit} pair(s) in which PDSCH transmission(s) related to PDCCH(s) (e.g., scheduled by the PDCCH(s)) and / or PDCCH(s) (e.g., PDCCH indicating SPS release and / or PDCCH indicating secondary cell dormancy) is present, up to the current serving cell and / or the current time unit; or an accumulative number of PDSCH(s) with corresponding PDCCH(s) and / or PDCCHs (e.g., PDCCHs indicating SPS release and / or PDCCHs indicating secondary cell dormancy) already scheduled by a base station up to the current serving cell and / or the current time unit; or an accumulative number of PDSCHs (the PDSCHs are PDSCHs with corresponding PDCCHs) already scheduled by the base station up to the current serving cell and / or the current time unit; or an accumulative number of time units with PDSCH transmissions (the PDSCHs are PDSCHs with corresponding PDCCHs) already scheduled by the base station up to the current serving cell and / or the current time unit. The order of each bit in the HARQ-ACK codebook corresponding to at least one of PDSCH reception(s), DCI format(s) indicating SPS PDSCH release (deactivation), or DCI indicating secondary cell dormancy may be determined by the time when the first DAI is received and the information of the first DAI.

[0269] In some examples, the second DAI may indicate a total number of at least one of all PDSCH receptions, DCI indicating SPS PDSCH release (deactivation), or DCI format(s) indicating secondary cell dormancy. For example, the total number may be a total number of all serving cells up to the current time unit. For example, the T-DAI may refer to: a total number of {serving cell, time unit} pairs scheduled by PDCCH(s) up to the current time unit within a time window (which may also include a number of PDCCHs for indicating SPS release); or a total number of PDSCH transmissions up to the current time unit; or a total number of {serving cell, time unit} pairs in which PDSCH transmission(s) related to PDCCH(s) (e.g., scheduled by the PDCCH) and / or PDCCH(s) (e.g., a PDCCH indicating SPS release and / or a PDCCH indicating secondary cell dormancy) is present, up to the current serving cell and / or the current time unit; or a total number of PDSCHs with corresponding PDCCHs and / or PDCCHs (e.g., PDCCHs indicating SPS release and / or PDCCHs indicating secondary cell dormancy) already scheduled by a base station up to the current serving cell and / or the current time unit; or a total number of PDSCHs (the PDSCHs are PDSCHs with corresponding PDCCHs) already scheduled by the base station up to the current serving cell and / or the current time unit; or a total number of time units with PDSCH transmissions (e.g., the PDSCHs are PDSCHs with corresponding PDCCHs) already scheduled by the base station up to the current serving cell and / or the current time unit.

[0270] In the following examples, the first DAI as the C-DAI and the second DAI as the T-DAI are taken as an example (but not limited thereto) for illustration.

[0271] Tables 1 and 2 show a correspondence between the DAI field and or or Numbers of bits of the C-DAI and T-DAI are limited.

[0272] For example, in case that a C-DAI or T-DAI in a DCI format is represented with 2 bits, the value of the C-DAI or T-DAI in the DCI format may be determined by equations in Table 1. or is the value of the T-DAI in the DCI format received in a PDCCH Monitoring Occasion (MO) m, and is the value of the C-DAI in the DCI format for a serving cellcreceived in the PDCCH monitoring occasionm. Both and are related to a number of bits of the DAI field in the DCI format. MSB is the most significant bit and LSB is the least significant bit.

[0273]

[0274] For example, when the C-DAI or T-DAI is 1, 5 or 9, as shown in Table 1, all of the DAI field are indicated with “00”, and the value of or is represented as “1” by the equation in Table 1. Y may represent the value of the DAI corresponding to the number of DCI formats actually transmitted by the base station (the value of the DAI before conversion by the equation in the table).

[0275] For example, in case that the C-DAI or T-DAI in the DCI format is 1 bit, values greater than 2 may be represented by equations in Table 2.

[0276]

[0277] In some implementations, the UE may generate HARQ-ACK information bits in a PUCCH according to pseudo-code 1. For example, if the UE transmits HARQ-ACK information in a PUCCH (e.g., a PUCCH for any PUCCH format) in slot n, the UE determines HARQ-ACK information bits according to pseudo-code 1, where is the total number of HARQ-ACK information bits.

[0278] [Pseudo-code 1]

[0279] Denote the number of bits for the C-DAI and set

[0280] Denote the value of the C-DAI in a DCI format on serving cell in PDCCH monitoring occasion

[0281] Denote the value of the T-DAI in a DCI format in PDCCH monitoring occasion

[0282] Set - PDCCH monitoring occasion index: lower index corresponds to earlier PDCCH monitoring occasion

[0283] Set

[0284] Set

[0285] Set

[0286] Set

[0287] Set to the number of serving cells configured by higher layers for the UE

[0288] Set to the number of PDCCH monitoring occasion(s)

[0289] while

[0290] Set - serving cell index: lower indexes correspond to lower RRC indexes of corresponding cell

[0291] while

[0292] if PDCCH monitoring occasion is before an active DL BWP change on serving cell or an active UL BWP change on the PCell,and / or a DL BWP change is not triggered in PDCCH monitoring occasion

[0293]

[0294] else

[0295] if there is a DCI format indicating associated HARQ-ACK information on serving cell in PDCCH monitoring occasion

[0296] if

[0297]

[0298] end if

[0299]

[0300] if

[0301]

[0302] else

[0303]

[0304] end if

[0305] if UE is not configured with a PUCCH spatial bundling parameter (e.g., the parameterharq-ACK-SpatialBundlingPUCCH) and the UE is configured with reception of two transport blocks for at least one DL BWP of at least one serving cell (e.g., by the 3GPP parametermaxNrofCodeWordsScheduledByDCI),

[0306] = HARQ-ACK information bit corresponding to the first transport block of this cell

[0307] = HARQ-ACK information bit corresponding to the second transport block of this cell

[0308] elseif UE is configured with the PUCCH spatial bundling parameter (e.g., the parameterharq-ACK-SpatialBundlingPUCCH) and the UE is configured with reception of two transport blocks for at least one DL BWP of at least one serving cell (e.g., by the 3GPP parametermaxNrofCodeWordsScheduledByDCI), and is a monitoring occasion in which a DCI format scheduling two transport blocks can be received,

[0309] = binary AND operation of the HARQ-ACK information bits corresponding to the first and second transport blocks of serving cell

[0310]

[0311] else

[0312] = HARQ-ACK information bit of this cell

[0313]

[0314] end if

[0315] end if

[0316]

[0317] end if

[0318] end while

[0319]

[0320] end while

[0321]

[0322] if UE does not set and

[0323]

[0324] end if

[0325]

[0326] if

[0327]

[0328] end if

[0329] if UE is not configured with the PUCCH spatial bundling parameter (e.g., the parameterharq-ACK-SpatialBundlingPUCCH) and the UE is configured with reception of two transport blocks for at least one DL BWP of at least one serving cell (e.g., by the 3GPP parametermaxNrofCodeWordsScheduledByDCI),

[0330]

[0331] else

[0332]

[0333] end if

[0334] ，for any

[0335] In some implementations, for a HARQ-ACK codebook in a PUSCH, the UE may set after completing the c and m loops of generating the HARQ-ACK codebook in pseudo-code 1, where is UL DAI, the value of which may be determined according to Table 1 or 2.

[0336] [HARQ feedback mode]

[0337] In some implementations, whether to feed back HARQ-ACK information may be configured by higher layer parameters or dynamically indicated by a DCI. The mode of feeding back (or reporting) the HARQ-ACK information (HARQ-ACK feedback mode or HARQ-ACK reporting mode) may also be at least one of the following modes.

[0338] - HARQ-ACK feedback mode 1: transmitting ACK or NACK (ACK / NACK). For example, for a PDSCH reception, if the UE decodes a corresponding transport block (TB) correctly, the UE transmits ACK; and / or, if the UE does not decode the corresponding transport block correctly, the UE transmits NACK. For example, a HARQ-ACK information bit of the HARQ-ACK information provided according to the HARQ-ACK feedback mode 1 is an ACK value or a NACK value.

[0339] - HARQ-ACK feedback mode 2: transmitting NACK only (NACK-only). For example, for a PDSCH reception, if the UE decodes the corresponding transport block correctly, the UE does not transmit the HARQ-ACK information; and / or, if the UE does not decode the corresponding transport block correctly, the UE transmits NACK. For example, at least one HARQ-ACK information bit of the HARQ-ACK information provided according to the HARQ-ACK feedback mode 2 is a NACK value. For example, for the HARQ-ACK feedback mode 2, the UE does not transmit a PUCCH that would include only HARQ-ACK information with ACK values.

[0340] For the PDSCH reception of a HARQ process, if the UE is configured not to feed back HARQ-ACK information, the HARQ-ACK codebook does not include HARQ-ACK information for the PDSCH reception.

[0341] [Channel collision]

[0342] In some implementations, a PUSCH conflicting / colliding with other physical channel(s) may be at least one of:

[0343] - a PUSCH overlapping in time domain with PUCCH(s) and / or PDSCH(s) and / or PDCCH(s) on a same serving cell;

[0344] - in case that simultaneous transmission for PUSCH is not configured, a PUSCH overlapping in time domain with other PUSCH(s) on a same serving cell;

[0345] - in case that the simultaneous transmission for PUSCH is configured, a PUSCH overlapping in time domain with another PUSCH, on a same serving cell, with a same value of a control resource set (CORESET) pool index parameter (e.g., coresetPoolIndex); or

[0346] - a PUSCH overlapping in time domain with a PUCCH. For example, a PUSCH overlaps in time domain with a PUCCH on a different serving cell, and / or the serving cell does not support simultaneous transmission of the PUSCH and the PUCCH.

[0347] In some implementations, a PDSCH conflicting / colliding with other physical channel(s) may be at least one of:

[0348] - a PDSCH overlapping in time domain with other PUSCH(s) and / or PUCCH(s) and / or PDSCH(s) on a same serving cell;

[0349] - in case that simultaneous reception for PDSCH is not configured (for example, the UE is not configured with different values of the CORESET pool index parameter (e.g., coresetPoolIndex)), a PDSCH overlapping in time domain with other PUSCH(s) on a same serving cell;

[0350] - in case that simultaneous transmission for PDSCH is configured (for example, the UE is configured with a PDCCH configuration parameter (e.g.,PDCCH-Config) including a CORESET parameter (e.g., ControlResourceSet) with different values of the CORESET pool index parameter (e.g., coresetPoolIndex)), a PDSCH overlapping in time domain with another PDSCH on a same serving cell with a same value of the CORESET pool index parameter (e.g., coresetPoolIndex); or

[0351] - a PDSCH overlapping in both time domain and frequency domain with a PDCCH on a same serving cell.

[0352] In some implementations, a PUCCH conflicting / colliding with other physical channel(s) may be at least one of:

[0353] - a PUCCH overlapping in time domain with other PUCCH(s) and / or PUSCH(s); or

[0354] - a PUCCH overlapping in time domain with other PDSCH(s) on a same serving cell.

[0355] In some implementations, a PDCCH conflicting / colliding with other physical channel(s) may be at least one of:

[0356] - a PDCCH overlapping in time domain with other PUSCH(s) and / or PUCCH(s) on a same serving cell; or

[0357] - a PDCCH overlapping in both time domain and frequency domain with other PDSCH(s) on a same serving cell.

[0358] In the description of the example embodiments of the disclosure, “a set of overlapping channels” may be understood as that each channel of the set of overlapping channels overlaps (or collides) with at least one of channels in the set except this channel. The channels may include one or more PUCCHs and / or one or more PUSCHs. For example, “a set of overlapping channels” may include “a set of overlapping PUCCHs and / or PUSCHs”. As a specific example, when a first PUCCH overlaps with at least one of a second PUCCH and a third PUCCH, the second PUCCH overlaps with at least one of the first PUCCH and the third PUCCH, and the third PUCCH overlaps with at least one of the first PUCCH and the second PUCCH, the first PUCCH, the second PUCCH and the third PUCCH constitute a set of overlapping channels (PUCCHs). For example, the first PUCCH overlaps with the second PUCCH and the third PUCCH, and the second PUCCH and the third PUCCH do not overlap.

[0359] It should be noted that in the description of the example embodiments of the disclosure, “resolving overlapping channels” may be understood as resolving the collision of overlapping channels. For example, when a PUCCH overlaps with a PUSCH, resolving the overlapping or collision may include multiplexing UCI of the PUCCH in the PUSCH, or may include transmitting the PUCCH or PUSCH with a higher priority. For another example, when a PUCCH overlaps with one or another PUCCH, resolving the overlapping or collision may include multiplexing UCI in a PUCCH, or may include transmitting the PUCCH with a higher priority. For yet another example, when two PUSCHs on a same serving cell overlap, resolving the overlapping or collision may include transmitting a PUSCH with a higher priority of the two PUSCHs. “Resolving overlapping channels,” “resolving the overlapping for / among channels,” “determining the overlapping for / among channels,” and “determining the overlapping channels” may be used interchangeably.

[0360] It should be noted that, unless the context clearly indicates otherwise, all or one or more of the methods, steps or operations described in the example embodiments of the disclosure may be specified / predefined by protocols and / or configured by higher layer signaling and / or indicated by dynamic signaling. The dynamic signaling may be a PDCCH and / or DCI and / or a DCI format. For example, a SPS PDSCH and / or CG PUSCH may be dynamically indicated by a corresponding activated DCI / DCI format / PDCCH. All or one or more of the described methods, steps and operations may be optional. For example, if a certain parameter (e.g., parameter X) is configured, the UE performs a certain approach (e.g., approach A), otherwise (if the parameter, e.g., parameter X, is not configured), the UE performs another approach (e.g., approach B). Unless otherwise specified, the parameters in the example embodiments of the disclosure may be higher layer parameters. For example, the higher layer parameters may be parameters configured or indicated by higher layer signaling (e.g., RRC signaling).

[0361] It should be noted that in the description of the example embodiments of the disclosure, a PCell (Primary Cell) or PSCell (Primary Secondary Cell) in the example embodiments of the disclosure may be used interchangeably with a cell having a PUCCH. A serving cell may be used interchangeably with a cell.

[0362] It should be noted that in the description of the example embodiments of the disclosure, methods for downlink in the example embodiments of the disclosure may also be applicable to uplink, and methods for uplink may also be applicable to downlink. For example, a PDSCH may be replaced with a PUSCH, a SPS PDSCH may be replaced with a CG PUSCH, and downlink symbols may be replaced with uplink symbols, so that methods for downlink may be applicable to uplink.

[0363] It should be noted that in the description of the example embodiments of the disclosure, methods applicable to scheduling multiple PDSCHs / PUSCHs in the example embodiments of the disclosure may also be applicable to a PDSCH / PUSCH transmission with repetitions. For example, a PDSCH / PUSCH of multiple PDSCHs / PUSCHs may be replaced with a repetition of multiple repetitions of the PDSCH / PUSCH transmission.

[0364] It should be noted that in the description of the example embodiments of the disclosure, “configured with and / or indicated a transmission with repetitions” may be understood that a number of the repetitions of the transmission is greater than 1. For example, “configured with and / or indicated a PUCCH transmission with repetitions” may be understood that “the PUCCH transmission is repeated on more than one slot / sub-slot”. “Not configured with and / or indicated a transmission with repetitions” may be understood that a number of the repetitions of the transmission is equal to 1. For example, “not configured with and / or indicated a PUCCH transmission with repetitions” may be understood that “a number of the repetitions of the PUCCH transmission is equal to 1”. For example, the UE may be configured with a parameter related to a number of repetitions of a PUCCH transmission; when the parameter is greater than 1, it may mean that the UE is configured with a PUCCH transmission with repetitions, and the UE may repeat the PUCCH transmission on time units (e.g., slots); when the parameter is equal to 1, it may mean that the UE is not configured with a PUCCH transmission with repetitions. For example, the PUCCH transmission with repetitions may include only one type of UCI. If the PUCCH is configured with repetitions, in the description of the example embodiments of the disclosure, a repetition of the multiple repetitions of the PUCCH may be used as a PUCCH (or a PUCCH resource), or all of the repetitions of the PUCCH may be used as a PUCCH (or a PUCCH resource), or a specific repetition of the multiple repetitions of the PUCCH may be used as a PUCCH (or a PUCCH resource).

[0365] It should be noted that in the description of the example embodiments of the disclosure, when a PDCCH and / or DCI and / or a DCI format schedules multiple PDSCHs / PUSCHs, the PDSCHs / PUSCHs may be multiple PDSCHs / PUSCHs on a same serving cell and / or multiple PDSCHs / PUSCHs on different serving cells.

[0366] It should be noted that in the example embodiments of the disclosure, multiple approaches / methods can be combined in any order. In a combination, an approach / method may be performed one or more times, or an approach / method may not be performed.

[0367] It should be noted that multiple steps in the method of the disclosure may be implemented in any order.

[0368] It should be noted that in the description of the example embodiments of the disclosure, “canceling a transmission” may mean canceling the transmission of the entire uplink channel and / or cancelling the transmission of a part of the uplink channel.

[0369] It should be noted that in the description of the example embodiments of the disclosure, “an order from small to large” (e.g., an ascending order) may be replaced with “an order from large to small” (e.g., a descending order), and / or “an order from large to small” (e.g., a descending order) may be replaced with “an order from small to large” (e.g., an ascending order).

[0370] It should be noted that in the description of the example embodiments of the disclosure, a PUCCH / PUSCH with / including / with A may be understood as a PUCCH / PUSCH only carrying / including / with A, and may also be understood as a PUCCH / PUSCH with / including / with at least A.

[0371] It should be noted that in the description of the example embodiments of the disclosure, “slot” may be replaced with “sub-slot” or “time unit”.

[0372] It should be noted that in the description of the example embodiments of the disclosure, a time interval (or time unit interval) between a first physical channel and a second physical channel may be understood as a time interval (or time unit interval) between an end position (or end symbol) of the first physical channel and a starting position (or starting symbol) of the second physical channel, wherein the first physical channel is earlier than the second physical channel, or, a time interval (or time unit interval) between a time unit where the first physical channel is located and a time unit where the second channel is located. The time unit in which the physical channel is located may be understood as a time unit that overlaps with the end position (or end symbol) of the physical channel or a time unit that overlaps with the starting position (or starting symbol) of the physical channel.

[0373] In the description of example embodiments of the disclosure, the following descriptions may be used interchangeably:

[0374] - A time interval between a first physical channel and a second physical channel is a first time

[0375] - A time interval from a first physical channel to a second physical channel is a first time

[0376] - A time interval from a second physical channel to a first physical channel is a first time

[0377] - A first physical channel is earlier than a second physical channel by a first time

[0378] - A first physical channel is later than a second physical channel by a first time

[0379] - A second physical channel is later than (is after) a first physical channel by a first time or a second physical channel is earlier than (is before) a first physical channel by a first time

[0380] In the description of example embodiments of the disclosure, the following descriptions may be used interchangeably:

[0381] - A time interval between a first physical channel and a second physical channel is greater than (or not less than) a first time

[0382] - A time interval from a first physical channel to a second physical channel is greater than (or not less than) a first time

[0383] - A time interval from a second physical channel to a first physical channel is greater than (or not less than) the first time

[0384] - A first physical channel is earlier than a second physical channel by more than (or not less than) the first time

[0385] - A first physical channel is later than a second physical channel by more than (or not less than) the first time

[0386] - A second physical channel is later than a first physical channel by more than (or not less than) the first time

[0387] - A second physical channel is earlier than a first physical channel by more than (or not less than) the first time

[0388] - The first symbol of a first physical channel is no earlier than (not before) symbol L (symbol L may be defined as a next symbol starting after the last symbol of a second channel)

[0389] - The first symbol of a second physical channel is no earlier than (not before) symbol L (symbol L may be defined as a next symbol starting after the last symbol of the first channel)

[0390] It should be noted that in the description of the example embodiments of the disclosure, “greater than (or not less than)” may be replaced with “less than (or not greater than)”.

[0391] It should be noted that in the description of the timing / timeline relationship (or time relationship) of the example embodiments of the disclosure, “a physical channel” may be understood as “the start of the physical channel”, “the first symbol of the physical channel”, or “the start of the first symbol of the physical channel”, and these terms may be used interchangeably. “A physical channel” may also be understood as “the end of the physical channel”, "the last symbol of the physical channel”, or “the end of the last symbol of the physical channel”, and these terms may be used interchangeably.

[0392] It should be noted that in an example embodiment of the disclosure, the time of a physical uplink channel may be a time when the UE actually transmits the physical uplink channel, for example, the time considering TA (timing advance).

[0393] It should be noted that in the description of the example embodiments of the disclosure, “performing a predefined method (or step) if a predefined condition is satisfied” and “not performing the predefined method (or step) if the predefined condition is not satisfied” may be used interchangeably. “Not performing a predefined method (or step) if a predefined condition is satisfied” and “performing the predefined method (or step) if the predefined condition is not satisfied” may be used interchangeably.

[0394] It should be noted that in the description of the example embodiments of the disclosure, “configured with a parameter (or information)”, “provided with a parameter (or information)”, “configured with a parameter of a specific value (e.g., 'enable')” and “receiving a parameter (or information) “ may be used interchangeably. Being configured with one or more parameters may refer to being configured with a parameter list in an IE, the parameter list including one or more parameters. Being configured with multiple parameters may also mean that the parameters are configured in multiple IEs, respectively.

[0395] It should be noted that in the description of the example embodiments of the disclosure, “PUCCH with HARQ-ACK information” and “PUCCH including HARQ-ACK information” may be used interchangeably.

[0396] It should be noted that in the description of the example embodiments of the disclosure, “HARQ-ACK”, “HARQ-ACK feedback”, “HARQ-ACK information”, “HARQ-ACK information bit” and “HARQ-ACK codebook” may be used interchangeably.

[0397] It should be noted that in the description of the example embodiments of the disclosure, “determining HARQ-ACK information bits” and “generating HARQ-ACK information bits” may be used interchangeably.

[0398] It should be noted that in the description of the example embodiments of the disclosure, “uplink” and “downlink” may be used interchangeably, “channel”, “channel transmission”, “physical channel” and “physical channel transmission” may be used interchangeably, and “physical channel” and “physical channel resource” may be used interchangeably. “PUCCH” and “PUCCH resource” may be used interchangeably, and “PUSCH” and “PUSCH resource” may be used interchangeably. The terms “channel” and “signal” may be used interchangeably.

[0399] It should be noted that in the description of the example embodiments of the disclosure, two or more physical channels overlap may mean that the two or more physical channels overlap in the time domain and / or overlap in the frequency domain.

[0400] It should be noted that in the description of the example embodiments of the disclosure, the method applicable to RRC parameters may also be used for MAC CEs, and vice versa.

[0401] It should be noted that the embodiments of the disclosure may be applicable to one serving cell or multiple serving cells.

[0402] It should be noted that the embodiments of the disclosure may be applicable to one BWP or multiple BWPs. The BWP may be a DL BWP and / or UL BWP.

[0403] It should be noted that in the description of the example embodiments of the disclosure, “first and second” and “two” may be used interchangeably. For example, “first channel and second channel” may refer to two channels. In the description of example embodiments of the disclosure, “first and second” may also refer to two or more. For example, "first channel and second channel” may also refer to two or more channels.

[0404] It should be noted that in the description of the example embodiments of the disclosure, the behaviour of the UE (or base station) and the corresponding conditions of the behaviour of the UE (or base station) may be used interchangeably. For example, “the UE receives (or is configured with) first information (or parameter)” and “if the UE is configured with the first information (or parameter)” may be used interchangeably.

[0405] It should be noted that in the description of the example embodiments of the disclosure, receiving information carried by a DCI format may be understood as detecting a DCI format that carries the information.

[0406] It should be noted that in the example embodiments of the disclosure, the terms “index”, “identification”, “identifier”, and “number” may be used interchangeably.

[0407] It should be noted that satisfying a condition in the embodiments of the disclosure may be understood as satisfying at least the condition. That is, this condition and other conditions may be satisfied at the same time. For example, “satisfying a specific condition” in the embodiment of the disclosure may be replaced with “at least satisfying the specific condition”.

[0408] It should be noted that the UE may support the method described in the embodiments of the disclosure through capability reporting, and / or may enable the method described in the embodiments of the disclosure through higher layer signaling parameter configuration.

[0409] It should be noted that in the description of the example embodiments of the disclosure, the “beam” may be understood as a transmission configuration indicator (TCI) state / reference signal / channel / spatial relationship; or a TCI state ID / reference signal ID / channel ID / spatial relationship ID; or a spatial filter associated with a TCI state / reference signal / channel / spatial relationship; Or a spatial filter associated with a TCI state ID / reference signal ID / channel ID / spatial relationship ID. In example embodiments of the disclosure, the following descriptions may be used interchangeably:

[0410] - beam;

[0411] - spatial filter;

[0412] - spatial domain filter;

[0413] - spatial domain transmission filter;

[0414] - spatial setting;

[0415] - quasi co-location (QCL) assumption;

[0416] - QCL parameter (QCL-type (e.g., type D (typeD)) parameter / reference signal);

[0417] - TCI state;

[0418] - unified TCI state;

[0419] - spatial relationship;

[0420] - RS (reference signal);

[0421] - information related to sounding reference signal (SRS) (e.g., SRS resource indication (SRI)).

[0422] In some implementations, the RS may be an RS corresponding to a beam. For example, the RS may be CSI-RS or SSB.

[0423] In some examples, the UE may be configured or provided with an SRS resource set index parameter (e.g., SRS_resource_set_index) with two different values (e.g., value 0 and value 1). The first SRS resource set (the SRS resource set index parameter value is equal to 0) may correspond to a CORESET pool index parameter with a value of 0, and the other SRS resource set (SRS resource set index parameter value is equal to 1) may correspond to the CORESET pool index parameter with a value of 1.

[0424] In embodiments of the disclosure, the term “panel” may refer to a group of antenna ports or an antenna group. An uplink transmission configuration indicator (TCI) of each antenna panel may be used to indicate a beam for the antenna panel, which may be a beam associated with the indicated reference signal ID. An SRS set ID may be used to indicate the antenna panel ID, where each antenna panel is associated with one SRS set

[0425] In some implementations, the UE may be configured (e.g., by higher layer signaling) with a first number of carriers (or serving cells). The first number may be an integer equal to or greater than 2. For convenience of description, the first number is 2 in the example embodiments of the disclosure. It can be understood that the embodiments of the disclosure may also be applicable to situations where more than two carriers are configured. For example, the UE may be configured (e.g., by higher layer signaling) with a first carrier and a second carrier. For example, the first carrier is a primary serving cell (PCell) and the second carrier is a secondary serving cell (SCell). The PCell may be an FDD carrier (or band), and the SCell may be an SDL (supplementary DL) carrier (or band). In the description of the embodiments of the disclosure, “SDL” may be replaced by “SUL” (supplement UL).

[0426] In the description of the disclosure, for convenience of description and ease of understanding, the UE is configured with two carriers or two operation cases as an example. It should be understood that the principles of the technology of the disclosure may be correspondingly applicable to situations where the UE is configured with other numbers of carriers or other numbers of operation cases. For example, the UE may be configured with three carriers or three or more operation cases related to the three carriers. In this situation, the technology of the disclosure may also be applicable accordingly. In addition, in the description of the disclosure, for convenience of description, the first carrier is an FDD carrier and the second carrier is an SDL carrier as an example. It should be understood that this is only example and not intended to be limiting, and the principles of the disclosure may also be applied to a situation where the first carrier and the second carrier are other types of carriers, for example, a situation where the first carrier is an FDD carrier and the second carrier is an SUL carrier, or the first carrier is an SDL carrier and the second carrier is an FDD carrier, or the first carrier is an SDL carrier and the second carrier is an SUL carrier, and / or the like. In the following description, PCell is an example of the first carrier, and SCell is an example of the second carrier.

[0427] In some implementations, the UE may be configured with switching (e.g., carrier switching) on different time units between PCell and SCell. For example, the PCell operation and SCell operation (e.g., transmission (Tx) and / or reception (Rx) of data and / or control information) switch on different time units. For example, in a same time unit (or time, or time instance), the UE only operates on one serving cell.

[0428] In some implementations, the UE may be configured to operate in Case 1 and Case 2 in different time units via switching. In a same time unit (or time, or time instance), the UE only operates in one of Case 1 and Case 2. For example, Case 1 operation may correspond to PCell operation, and Case 2 operation may correspond to SCell operation. In a possible implementation, the UE may be configured or indicated with a transmission and / or reception mode / method in which the UE operates in Case 1 and Case 2 in different time units via switching.

[0429] Case 1: transmitting and / or receiving a channel / signal on the first carrier (or transmitting a channel / signal on the first carrier; or receiving a channel / signal on the first carrier). For example, Case 1 may be defined as: 1 antenna port Tx / 2 antenna port Rx on FDD carrier 1 and 0 antenna port transmit / 0 antenna port receive on carrier 2 (1 Tx / 2 Rx on FDD carrier 1 and 0 Tx / 0 Rx on carrier 2).

[0430] Case 2: transmitting and / or receiving a channel / signal on a second carrier (or transmitting a channel / signal on a second carrier; receiving a channel / signal on a second carrier). For example, Case 2 may be defined as 2 antenna port Rx on SDL carrier 2 and 0 antenna port Tx / 0 antenna port Rx on carrier 1 (2 Rx on SDL carrier 2 and 0 Tx / 0 Rx on carrier 1).

[0431] The above definitions of Case 1 and Case 2 are only examples, and Case 1 and Case 2 may also be defined as follows.

[0432] Case 1: 2 antenna port Rx on SDL carrier 2 and 0 antenna port Tx / 0 antenna port Rx on carrier 1 (2 Rx on SDL carrier 2 and 0 Tx / 0 Rx on carrier 1).

[0433] Case 2: 1 antenna port Tx / 2 antenna port Rx on FDD carrier 1 and 0 antenna port Tx / 0 antenna port Rx on carrier 2 (1 Tx / 2 Rx on FDD carrier 1 and 0 Tx / 0 Rx on carrier 2).

[0434] For example, Case 1 and Case 2 may also be defined as follows.

[0435] Case 1: transmitting or receiving data or control information on FDD carrier 1 (or PCell).

[0436] Case 2: receiving downlink data or control information on SDL carrier 2 (or SCell).

[0437] In some implementations, the configuration information received by the UE (for example, configuration information related to carrier switching) may include information for determining a time unit where the UE transmits and / or receives on the configured FDD carrier and SDL carrier.

[0438] In some implementations, the configuration information received by the UE (e.g., configuration information related to carrier switching) may include information for determining a time unit where the UE operates in configured Case 1 and Case 2.

[0439] The example embodiments of the disclosure are described below by taking determining a time unit where the UE operates in configured Case 1 and Case 2 as an example. It can be understood that the example embodiments of the disclosure may also be applied to the situation of determining a time unit where the UE transmits and / or receives on the configured FDD carrier and SDL carrier, where Case 1 may correspond to the UE transmitting and / or receiving on the configured FDD carrier, and Case 2 may correspond to the UE receiving on the configured SDL carrier.

[0440] The method of determining a time unit where the UE operates in the configured Case 1 and Case 2 and switching gap may be described in detail below. It should be understood that in the description of this disclosure, for convenience of description, the term “time unit” is used to express the meaning of “time domain resource” or “time domain position” in most cases. For example, “the time unit where operating in Case 1” means the time domain resource or time domain position or time unit position corresponding to Case 1, or it can be understood that which time units Case 1 corresponds to (for example, time units 1-2, or slots 1 and 2 and / or symbols 0-6, and / or the like). In addition, in the description of the disclosure, “time unit” is sometimes used to express the time domain granularity, such as slot, symbol, and / or the like. For example, “a pattern (e.g., carrier-switching-pattern) includes P time units” may mean that a pattern includes P time domain granularity units, such as P slots or symbols. In addition, it should be understood that the unit of time domain granularity may be one granularity or a combination of multiple granularities. For example, the unit of time domain granularity may be slot, for example, a time domain resource may be expressed as M1 slots; or the unit of time domain granularity may be slot and symbol, for example, a time domain resource may be expressed as M1 slots and N1 symbols. Thus, in the disclosure, the meaning of “time unit” may be determined depending on the context.

[0441] FIG. 10 illustrates an example of a carrier-switching-pattern according to some example embodiments of the disclosure.

[0442] As shown in FIG. 10, a periodicity (e.g., a first period / time) may include a second period / time (e.g., an operation period of PCell) and a third period / time (e.g., an operation period of SCell). For example, the PCell may operate at the start of each periodicity. The operation period of the PCell within a periodicity may be predefined or configured by higher layer signaling (e.g., RRC signaling). The SCell may operateat the remaining time within the periodicity except for the PCell operation period. The periodicity of the carrier switching mode may be predefined or configured by higher layer signaling (e.g., RRC signaling).

[0443] As used in embodiments of the disclosure, for a cell (PCell or SCell), the term “operation period” may refer to a time / period during which the UE can perform corresponding actions in the cell. For example, in case that the PCell corresponds to Case 1, the operation period of the PCell may refer to a time / period in which the UE can perform actions related to Case 1. In case that the SCell corresponds to Case 1, the operation period of the SCell may refer to a time during which the UE can perform actions related to Case 2. It can be understood that the term naming “operation period” is only an example and any suitable name can be used.

[0444] For a cell (PCell or SCell), the time / period other than the operation period / time within a periodicity may be called non-operation period. For example, referring to FIG. 10, the operation period of the PCell may be the non-operation period of the SCell, and the operation period of the SCell may be the non-operation period of the PCell. In some implementations, the non-operation period may also include a gap / period for carrier switching (which may be called carrier switching period / gap in the embodiments of the disclosure) and / or timing advance (TA) period. For example, the gap / period for carrier switching and / or timing advance (TA) period may be within the operation period of the SCell (as will be described in conjunction with FIG. 11).

[0445] It can be understood that although FIG. 10 only shows a single switching point within one periodicity, the embodiments of the disclosure are not limited thereto, and there may be multiple switching points within one periodicity.

[0446] In some implementations, a mode (e.g., taking the carrier switching mode in FIG. 10 as an example for explanation) may include a first number (e.g., P) of time units (also called a periodicity of P time units) (e.g., the first period in FIG. 10). In this carrier switching mode, the UE operates in Case 1 within a second number of consecutive time units (e.g., the second period in FIG. 10). The UE operates in Case 2 within the remaining time units (e.g., a third number of time units (e.g., the third period in FIG. 10), where the third number is equal to the first number minus the second number, that is, the third period is equal to the first period minus the second period). For example, the UE operates in Case 1 at the start of a periodicity. Or, the UE operates in Case 1 in the first N (where N is the second number) time units within a periodicity, and UE operates in Case 2 in the last M (where M is the second number) time units within the periodicity; or the UE operates in Case 1 in the last N (where N is the first number) time units within a periodicity, and UE operates in Case 2 in the first M (where M is the third number) time units within the periodicity. A periodicity may include only one switching point. The first number (or periodicity and offset (e.g., time unit offset)) and the second number may be configured by higher layer signaling.

[0447] In some implementations, there is a time interval / gap for carrier switching (e.g., Case 1 to Case 2 switching, and / or Case 2 to Case 1 switching). For example, the time interval / gap for Case 1 to Case 2 switching may be a fourth period / time, the time interval / gap for Case 2 to Case 1 switching may be a fifth period / time, the fourth period may be or may not be equal to the fifth period, the fourth period may be included in the second period or the third period, or the fifth period may be included in the second period or the third period. An example of carrier switching gap / period is described below in conjunction with FIG. 11.

[0448] FIG. 11 illustrates an example of a carrier-switching-pattern according to some example embodiments of the disclosure. Description of the same contents as in FIG. 10 will be omitted.

[0449] As shown in FIG. 11, there may be a carrier switching period / time in the carrier switching mode, for example, a time interval / gap (which may be called a first carrier switching period) for PCell to SCell switching and / or a time interval / gap (which may be called a second carrier switching period) for SCell to PCell switching. In some examples, the first carrier switching period may be equal to the second carrier switching period. In some examples, the first carrier switching period and the second carrier switching period may be different. In some examples, the first carrier switching period and the second carrier switching period may both be within the operation period of the SCell, as shown in FIG. 10. In this way, the transmission and reception on the PCell will not be affected by the carrier switching period. In some examples, the first carrier switching period and the second carrier switching period are located within the operation period of the SCell and the operation period of the PCell, respectively.

[0450] Due to the timing advance around the switching point (e.g., the boundary of the periodicity), an uplink transmission on the PCell may overlap with a downlink reception on the SCell. To resolve the collision, the DL transmission may not be allowed on the SCell in the potential overlapping period (i.e., the corresponding period is the non-operation period of the SCell), as indicated by the TA period in FIG. 11.

[0451] In some implementations, for a periodicity, a first carrier switching period starts after the end of a PCell operation period (e.g., the second period). For the periodicity, a second carrier switching period may end a timing advance period (TA period) before the start of a PCell operation period of the next periodicity. The carrier switching period can be just before the TA period, as shown in FIG. 11.

[0452] Referring to FIG. 11, considering the switching period, the operation period (third period) of the SCell may be called a nominal operation period. The period other than the carrier switching period (e.g., the first carrier switching period and the second carrier switching period) and the timing advance period within the SCell operation period (third period) may be an actual operation period of the SCell. The carrier switching period and timing advance period within the SCell operation period (third period) are the non-operation period of the SCell.

[0453] In some implementations, the carrier switching period (the first carrier switching period and the second carrier switching period) may be predefined or configured by higher layer signaling (e.g. RRC). The carrier switching period may be configured as an absolute time or a number of time units (e.g., a number of symbols). In case that the carrier switching period is configured as an absolute time, it may be necessary to convert the configured absolute time into a corresponding number of symbols. For SCell to PCell switching, the corresponding number of symbols may need to be determined based on the configured second carrier switching period and timing advance value, thereby determining the corresponding non-operation period. When the number of symbols determined based on the configured second carrier switching period and timing advance values (e.g., the number of symbols corresponding to the second carrier switching period and timing advance) is a non-integer number, a rounding up or down operation may be performed to determine the number of symbols corresponding to the non-operation period.

[0454] In some implementations, the first carrier switching period / gap is located at the end of the operation period of the PCell. For a first uplink signal or channel on the PCell, if the transmission time of the first uplink signal or channel (e.g., the actual transmission considering the TA) overlaps with the first carrier switching period / gap (e.g., in case that the TA is less than the first carrier switching period / gap), UE does not transmit the transmission of the first uplink signal or channel.

[0455] In some implementations, the UE may be configured with a semi-static HARQ-ACK codebook (e.g., a Type-1 HARQ-ACK codebook).

[0456] The UE may receive higher layer signaling that configures a set K1of first time unit timing values (the details and examples of timing parameter K1may refer to the previous description) and a time domain resource allocation table for serving cell c.

[0457] For serving cell c, the UE may determine a set MA,cof occasions for candidate PDSCH receptions based on the set K1of first time unit timing values and a set R of row indexes of the time domain resource allocation table.

[0458] The UE may transmit a PUCCH with / carrying a Type-1 HARQ-ACK codebook, where HARQ-ACK information bit(s) in the Type-1 HARQ-ACK codebook is / are determined based on the set MA,cof occasions for candidate PDSCH receptions.

[0459] In some implementations, for a downlink time unit, if the PDSCH time resource for row index r on serving cell c overlaps with the non-operation period or carrier switching period of the serving cell, the row index r is excluded from the set R of row indexes. Or, if a downlink time unit of the serving cell is the non-operation period, for the downlink time unit, all row indexes are excluded from the set R of row indexes. For example, for a downlink time unit, the rows in the the set R may be updated according to the following pseudo-code 2a. The occasion for candidate PDSCH receptions in downlink slot of serving cell c may then be determined according to the following pseudo-code 2. Here, j is the index of the occasion for candidate PDSCH receptions or SPS PDSCH release.

[0460] [Pseudo-code 2a]

[0461] while

[0462] if the UE is not configured with a time domain HARQ bundling enabling parameter (e.g., 3GPP parameterenableTimeDomainHARQ-Bundling) and is configured withtdd-UL-DL-ConfigurationCommon, ortdd-UL-DL-ConfigurationDedicatedand, for each slot to slot at least one symbol of the PDSCH time resource derived by row r is configured as UL or the UE does not receive the PDSCH corresponding to the row r when the downlink carrier aggregation via switching is configured (for example, the UE determines not to receive the PDSCH according to the embodiments of the disclosure), where is thek-th slot timing value in set where is a DL slot with a smallest index among DL slots overlapping with UL slot (or in UL slot ),

[0463]

[0464] end while

[0465] [Pseudo-code 2]

[0466] Set to the cardinality of the set R

[0467] Set m to the smallest last OFDM symbol index, as determined by the SLIV, among all rows of R

[0468] while

[0469] set

[0470] while

[0471] if for start symbol index S for row r

[0472] ;

[0473] else

[0474] ;

[0475] end if

[0476] end while

[0477]

[0478] ;

[0479] set m to the smallest last symbol index among all rows ofR;

[0480] end while

[0481] This method can reduce the number of information bits for HARQ-ACK and improve the reliability of HARQ-ACK transmission.

[0482] It should be noted that the UE may indicate a UE capability to support the Type-1 HARQ-ACK codebook through UE capability reporting. In some implementations, when receiving higher layer signaling indicating to enable the above-mentioned method (for example, indicating to enable the Type-1 HARQ-ACK codebook based on the downlink carrier aggregation via switching), the UE determines the Type-1 HARQ-ACK codebook by the above-mentioned method.

[0483] The non-operation period is an example description, and similar terminology may be used. For the non-operation period of a serving cell, the UE does not receive the first downlink signal or channel on the serving cell, or the UE does not receive the first downlink signal or channel on the serving cell that overlaps with the non-operation period. For the non-operation period of a serving cell, the UE does not transmit the first uplink signal or channel on the serving cell, or the UE does not transmit the first uplink signal or channel on the serving cell that overlaps with the non-operation period. The first uplink signal or channel is a semi-statically configured uplink signal or channel. The first downlink signal or channel is a semi-statically configured downlink signal or channel. It should be noted that the UE may report to support the behaviour through the UE capability, or the UE may report whether the behaviour is supported through the UE capability. For example, if the UE does not support the behaviour through the UE capability report, or the UE can report that it does not support the behaviour through the UE capability, then the UE does not expect that the first downlink signal of a serving cell (e.g., PCell and / or SCell) or channel overlaps with non-operation period of the serving cell, and / or the UE does not expect that the first uplink signal or channel of a serving cell (e.g., PCell) overlaps with the non-operation period of the serving cell.

[0484] In some implementations, the UE does not expect to receive a MAC CE indicating SCell deactivation and / or SCell activation, when the carrier switching is enabled or the carrier switching mode is configured. It should be noted that the UE may receive an RRC parameter to enable the carrier switching, for example, the carrier switching described in the embodiments of the disclosure. Or, when the carrier switching is enabled or carrier switching mode is configured for the UE, if the UE receives a MAC CE indicating SCell deactivation and / or SCell activation, the UE ignores the MAC CE.

[0485] In some implementations, the UE may report, through capability reporting, a capability to support to receive a MAC CE indicating SCell deactivation and / or SCell activation when the carrier switching is enabled or the carrier switching mode is configured. If the UE reports, through capability reporting, a capability to support (or indicate whether support) to receive a MAC CE indicating SCell deactivation and / or SCell activation when the carrier switching is enabled or the carrier switching mode is configured, the UE does not expect to receive a MAC CE indicating SCell deactivation and / or SCell activation when the carrier switching is enabled or the carrier switching mode is configured, or if the UE receives a MAC CE indicating SCell deactivation and / or SCell activation, the UE ignores the MAC CE.

[0486] In some implementations, optionally, in case that the UE reports, through capability reporting, a capability to support to receive a MAC CE indicating SCell deactivation and / or SCell activation when the carrier switching is enabled or the carrier switching mode is configured, when SCell is deactivated, the reception and transmission of PCell are not affected by the parameter of enabling carrier switching or the parameter of configuring carrier switching mode, or the UE ignores the parameter of enabling carrier switching or the parameter of configuring carrier switching mode, or disables the carrier switching mode, that is, the UE can operate in PCell at all times. When the SCell is activated, the reception and transmission of PCell are based on the determination of the parameter of enabling carrier switching or the parameter of configuring carrier switching mode.

[0487] In some implementations, it may be specified by protocols that the carrier switching mode is enabled or disabled in the next periodicity of the carrier switching mode after the MAC CE or RRC takes effect.

[0488] This can clarify the behaviour of the UE and ensure the consistency of understanding of reception and transmission between the UE and the network, thereby improving the reliability of transmission.

[0489] In some implementations, it can be specified by protocols that the continuous period during which the SCell operates cannot be greater than a predefined time. For example, the predefined time may be 7 slots (or milliseconds). For another example, the predefined time may be the maximum value of the timing parameter K1 minus 1 slot (or millisecond) to ensure that HARQ-ACKs for all PDSCHs on the PCell can be transmitted, thereby ensuring the reliability of HARQ-ACK transmission.

[0490] In some implementations, for the non-operation period of a serving cell, the UE does not expect to receive a DCI format scheduling a second downlink signal or channel on the serving cell, where the second downlink signal or channel overlaps with the non-operation period, or the UE does not expect to receive a DCI format scheduling a second uplink signal or channel on the serving cell, where the second uplink signal or channel overlaps with the non-operation period.

[0491] For a SPS PDSCH of a serving cell, if the SPS PDSCH overlaps with the non-operation period, the UE does not generate a HARQ-ACK information bit for the SPS PDSCH. The UE does not transmit the HARQ-ACK information bit for the SPS PDSCH. The UE does not receive the SPS PDSCH.

[0492] This method can reduce the number of information bits for HARQ-ACK and improve the reliability of HARQ-ACK transmission.

[0493] In some implementations, if there is more than one SPS PDSCH on a serving cell, after resolving the overlapping with the non-operation period (e.g., the symbols of the non-operation period), the UE may receive SPS PDSCH(s). For example, the UE may receive the SPS PDSCH(s) according to the following reception method.

[0494] - Step 0: set j = 0, where j is the number of selected PDSCH(s) for decoding.Qis the set of activated PDSCHs without corresponding PDCCH transmissions within a time unit (e.g., slot)

[0495] - Step 1: the UE receives PDSCH with lowest configured SPS configuration index (e.g. sps-ConfigIndex) within the setQ, set j to j + 1. Designate the received PDSCH as a survivor PDSCH.

[0496] - Step 2: The survivor PDSCH in step 1 and other PDSCH(s) partially or fully overlapping with the survivor PDSCH in step 1 are excluded from the setQ.

[0497] - Step 3: Repeat steps 1 and 2 until the setQis empty or j is equal to the number of unicast / multicast PDSCHs in a time unit (e.g., slot) supported by the UE.

[0498] Note that steps 1-3 above may be performed in other orders, some of steps 1-3 may be performed in combination, one or more of steps 1-3 above may be omitted, or additional steps may be added.

[0499] In some examples, for a SPS PDSCH of one or more SPS PDSCHs, the resolving the overlapping with the non-operation period (e.g., the symbols of the non-operation period) may include not receiving the SPS PDSCH in case that the SPS PDSCH overlaps with the non-operation period. For example, after resolving the overlapping between the one or more SPS PDSCHs and the non-operation period, at least one SPS PDSCH that does not overlap with the non-operation period can be obtained. The UE may receive the at least one SPS PDSCH based on steps 1-3 in the above method.

[0500] In one example, a HARQ-ACK codebook may be generated according to pseudo-code 3.

[0501] [Pseudo-code 3]

[0502] Set to the number of serving cells configured to the UE

[0503] Set to the number of SPS PDSCH configurations configured to the UE for serving cell c

[0504] Set to the number of DL slots for SPS PDSCH receptions on serving cell c with HARQ-ACK information multiplexed on the PUCCH

[0505] Set - HARQ-ACK information bit index

[0506] Set - serving cell index

[0507] while

[0508] Set - PS PDSCH configuration index

[0509] while

[0510] Set - slot index

[0511] while

[0512] if {

[0513] the UE is configured to receive SPS PDSCHs from slot to slot for SPS PDSCH configuration on serving cell c, excluding SPS PDSCHs that are not required to be received (or that the UE does not receive) in any slot among overlapping SPS PDSCHs, or based on a UE capability for a number of PDSCH receptions in a slot, or due to other reasons described in the embodiments of the disclosure (e.g., due to the non-operation period), or due to overlapping with a set of symbols (e.g., OFDM symbols) in the semi-static frame structure that are indicated as uplink by higher layer signalling (e.g., parameter tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated), where may be determined by a higher layer parameter, and HARQ-ACK information for all SPS PDSCH is associated with the PUCCH

[0514] }

[0515] = HARQ-ACK information bit for this SPS PDSCH reception

[0516]

[0517] end if

[0518]

[0519] end while

[0520]

[0521] end while

[0522]

[0523] end while

[0524] In some implementations, the UE determines overlapping PUCCH(s) and / or PUSCH(s) before considering a limitation for UL transmissions due to the non-operation period. For example, the UE may resolve the overlapping PUCCH(s) and / or PUSCH(s) to determine at least one uplink channel. For the determined at least one uplink channel, the UE may determine whether the at least one uplink channel overlaps with non-operation period. For example, the UE determines the overlapping PUCCH and / or PUSCH transmissions of a same priority index before considering a limitation for UL transmissions due to the non-operation period.

[0525] In some implementations, if carrier switching occurs between a downlink reception and its associated uplink transmission, the time interval between the downlink reception and the uplink transmission needs to additionally include the carrier switching period. If multiple carrier switching occur between a downlink reception and its associated uplink transmission, the time interval between the downlink reception and the uplink transmission needs to additionally include the corresponding multiple carrier switching periods. For example, the downlink reception is a PDCCH, and the uplink transmission is a PUSCH. For another example, the downlink reception is a PDSCH, and the uplink transmission is a PUCCH or PUSCH with HARQ-ACK for the PDSCH. For another example, the downlink reception is a PDCCH, and the uplink transmission is a PUCCH or PUSCH with HARQ-ACK for the PDCCH. For still another example, the downlink reception is a PDCCH, and the uplink transmission is an SRS. The carrier switching period may be reported by a UE capability. This method ensures that the UE has sufficient time to process uplink transmission, thereby ensuring the reliability of uplink transmission.

[0526] The embodiments of the disclosure specify methods for the UE to transmit and receive data and control information during carrier switching, which clarifies the behaviour of the UE, thereby increasing the reliability of communication. In particular, for a PDSCH that is not received due to carrier switching, the UE may not generate the corresponding HARQ-ACK information bit, which can reduce the used uplink control information resources, or improve the reliability of uplink control information transmission in case of using the same resources.

[0527] FIG. 12 illustrates a flowchart of a method 1200 performed by a UE, in accordance with some embodiments of the disclosure.

[0528] Referring to FIG. 12, in operation S1210, the UE receives first information that configures switching between a PCell and a SCell in time domain.

[0529] In operation S1220, the UE receives higher layer signaling that configures a set K1of first time unit timing values and a time domain resource allocation table for a serving cell c.

[0530] In operation S1230, the UE determines, for the serving cell c, a set MA,cof occasions for candidate physical downlink shared channel (PDSCH) receptions, based on the set K1of first time unit timing values and a set R of row indexes of the time domain resource allocation table.

[0531] In operation S1240, the UE transmits a PUCCH with a Type-1 HARQ-ACK codebook, wherein HARQ-ACK information bits in the Type-1 HARQ-ACK codebook are determined based on the set MA,cof occasions for candidate PDSCH receptions, wherein for a downlink time unit, in case that a PDSCH time resource for a row index r on the serving cell c overlaps with a non-operation period of the serving cell, the row index r is excluded from the set R of row indexes.

[0532] In some implementations, one or more of operations S1210 to S1240 may be performed based on methods described according to various embodiments of the disclosure.

[0533] In some implementations, method 1200 may omit one or more of operations S1210 to S1240, or may include additional operations, such as operations that may be performed by the UE described according to various embodiments of the disclosure.

[0534] FIG. 13 shows a flowchart of a method 1300 performed by a base station, in accordance with some embodiments of the disclosure.

[0535] Referring to FIG. 13, in operation S1310, the base station transmits, to a UE, first information that configures switching between a PCell and a SCell in time domain.

[0536] In operation S 1320, the base station transmits, to the UE, higher layer signaling that configures a set K1of first time unit timing values and a time domain resource allocation table for a serving cell c.

[0537] In operation S1330, the base station receives, from the UE, a PUCCH with a Type-1 HARQ-ACK codebook, where HARQ-ACK information bits in the Type-1 HARQ-ACK codebook are determined based on a set MA,cof occasions for candidate PDSCH receptions, where for the serving cell c, the set MA,cof occasions for candidate PDSCH receptions is determined based on the set K1of first time unit timing values and a set R of row indexes of the time domain resource allocation table, where for a downlink time unit, in case that a PDSCH time resource for a row index r on the serving cell c overlaps with a non-operation period of the serving cell, the row index r is excluded from the set R of row indexes.

[0538] In some implementations, one or more of operations S1310 to S1330 may be performed based on methods described according to various embodiments of the disclosure.

[0539] In some implementations, the method 1300 may omit one or more of operations S1310 to S1330, or may include additional operations, such as operations that may be performed by a base station described according to various embodiments of the disclosure.

[0540] FIG. 14 is a block diagram of a terminal or user equipment (UE) 1400 according to an embodiment of the disclosure.

[0541] The terminal is an electronic device capable of wireless communication, may include a User Equipment (UE), a portable phone, a smartphone, a tablet, an Internet of things (IoT) device, etc., having various form factors, and may perform wireless communication with a base station (BS) through a wireless channel.

[0542] Referring to FIG. 14, the UE 1400 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 1401, at least one processor (hereinafter, referred to as simply “processor”) 1402, and at least one memory (hereinafter, referred to as simply “memory”) 1403. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 1401, the processor 1402, and the memory 1403 of the UE 1400 may operate. However, components of the UE 1400 are not limited to the exemplary components illustrated in FIG. 14. In another embodiment, the UE 1400 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 1401, the processor 1402, or the memory 1403 may be integrated in the form of one component.

[0543] The transceiver 1401 may be a communication circuit or communication circuitry that enables the UE 1400 to perform wireless communication with a node or an entity of a network. For example, the transceiver 1401 may enable the UE 1400 to transmit or receive a signal to or from a BS through cellular communication, or to transmit or receive a signal to or from another UE through cellular communication. For example, the transceiver 1401 may support at least one of various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (1401) may include all subsequent generations of evolved wireless communications.

[0544] According to an embodiment, the UE 1400 may include a plurality of transceivers. For example, in the case of supporting evolved-universal terrestrial radio access-new radio (E-UTRA-NR) sual connectivity (EN-DC), the UE 1400 may include a first transceiver supporting the 4G LTE wireless communication and a second transceiver supporting the 5G NR wireless communication. According to another embodiment, in the case of supporting NR-dual connectivity (NR-DC), the UE 1400 may include a plurality of transceivers supporting the 5G NR wireless communication. According to still another embodiment, in the case of supporting near field wireless communication, the UE 1400 may separately include a transceiver supporting at least one standard in the group of wireless communication protocol standards as defined in the protocol standards for Bluetooth®, wireless local area network (WLAN) network (including institute of electrical and electronics engineers (IEEE) 802.11-2016 standard or its amendments, e.g., 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be, without being limited thereto).

[0545] According to an embodiment, the transceiver 1401 may include various circuit structures used to transmit or receive signals to or from a BS through a wireless channel. The signals may include control information and data. For example, the transceiver 1401 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 1401 may output a signal received through a wireless channel to the processor 1402 and may transmit, through a wireless channel, a signal output from the processor 1402.

[0546] The processor 1402 may control general operations of the UE 1400 according to embodiments of the disclosure. The processor 1402 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 1402 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1403, individually, collectively or in any combination thereof. Further, the processor 1402 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0547] The processor 1402 may be electrically, operatively, or communicatively coupled to the transceiver 1401 to control the transceiver 1401.

[0548] The processor 1402 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. For example, the processor 1402 may include a communication processor (CP) configured to control communication operations and an application processor (AP) configured to control execution of an upper layer (for example, an application layer) . In a specific embodiment, at least a part of the processor 1402 may be included in one chip and the other part of the processor 1402 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the transceiver 1401 or the memory 1403.

[0549] The processor 1402 may perform or control or cause an operation of the UE 1400 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1402 may control operations of the UE 1400 for processing a downlink signal received from a BS or generating and transmitting an uplink signal to a BS. To this end, the processor 1402 may execute a computer program, codes, or instructions stored in the memory 1403, so as to control other components of the UE 1400 to enable execution of various operations.

[0550] The memory 1403 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1403 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0551] The memory 1403 may be electrically, operatively, or communicatively coupled to the processor 1402 and may be accessed by the processor 1402.

[0552] The memory 1403 may store a computer program, codes, or instructions executable by the processor 1402. According to an embodiment, a computer program, codes, or instructions executable by the processor 1402 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1403, the processor 1402 may perform various functions according to an embodiment of the disclosure.

[0553] According to an embodiment of the disclosure, operations of the UE 1400 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1403 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0554] FIG. 15 is a block diagram of a base station (BS) 1500 according to an embodiment of the disclosure.

[0555] The BS 1500 may perform wireless communication with at least one user equipment (UE) located within the area of the BS 1500 through a wireless channel.

[0556] Referring to FIG. 15, the BS 1500 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 1501, at least one processor (hereinafter, referred to as simply “processor”) 1502, and at least one memory (hereinafter, referred to as simply “memory”) 1503. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 1501, the processor 1502, and the memory 1503 of the BS 1500 may operate. However, components of the BS 1500 are not limited to the exemplary components illustrated in FIG. 15. In another embodiment, the BS 1500 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 1501, the processor 1502, or the memory 1503 may be integrated in the form of one component.

[0557] The transceiver 1501 may be a communication circuit or communication circuitry that enables the BS 1500 to perform wireless communication with a node or an entity of a network. For example, the transceiver 1501 may enable the BS 1500 to transmit or receive a signal to or from the UE X00 through cellular communication, or to transmit or receive a signal to or from another network entity through wireless communication. For example, the transceiver 1501 may support various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (1501) may include all subsequent generations of evolved wireless communications.. According to an embodiment, the transceiver 1501 may include various circuit structures used to transmit or receive signals to or from a UE through a wireless channel. The signals may include control information and data. For example, the transceiver 1501 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 1501 may output a signal received through a wireless channel to the processor 1502 and may transmit, through a wireless channel, a signal output from the processor 1502.

[0558] Meanwhile, according to an embodiment of the present disclosure, the BS 1500 may perform communication with a node or an entity of a network through wired or wireless communication. For example, the BS 1500 may perform wired or wireless communication with an adjacent BS, or a node or an entity of a core network through a backhaul network. Although not illustrated in FIG. 15, when the BS 1500 performs wired communication, the BS 1500 may further include a separate network interface for wired communication in addition to the transceiver 1501. The network interface may be referred to as network interface circuitry or communication interface circuitry.

[0559] The processor 1502 may control general operations of the BS 1500 according to embodiments of the disclosure. The processor 1502 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 1502 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1503, individually, collectively or in any combination thereof. Further, the processor 1502 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0560] The processor 1502 may be electrically, operatively, or communicatively coupled to the transceiver 1501 to control the transceiver 1501.

[0561] The processor 1502 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 1502 may be included in one chip and the other part of the processor 1502 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the transceiver 1501 or the memory 1503.

[0562] The processor 1502 may perform or control or cause an operation of the BS 1500 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1502 may control operations of the BS 1500 for generating and transmitting a downlink signal to a UE or processing an uplink signal received from a UE. Otherwise, the BS 1500 may transmit or receive a signal to or from a neighboring BS, transfer a signal received from a UE to an upper node of the network, or transmit a signal transferred from an upper node of the network to a UE. To this end, the processor 1502 may execute a computer program, codes, or instructions stored in the memory 1503, so as to control other components of the BS 1500 to enable execution of various operations.

[0563] The memory 1503 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1503 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0564] The memory 1503 may be electrically, operatively, or communicatively coupled to the processor 1502 and may be accessed by the processor 1502.

[0565] The memory 1503 may store a computer program, codes, or instructions executable by the processor 1502. According to an embodiment, a computer program, codes, or instructions executable by the processor 1502 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1503, the processor 1502 may perform various functions according to an embodiment of the disclosure.

[0566] According to an embodiment of the disclosure, operations of the BS 1500 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1503 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0567] The UE or the base station may perform various communication procedures related to the control plane or the user plane by cooperating with one or more network entities based on wireless communication. For example, the UE may communicate with network entity such as an Access and Mobility Management Function (AMF) or a Session Management Function (SMF) via the base station, or the base station may perform at least one communication procedure by directly transmitting and receiving signals to / from, or relaying signals between, the network entities.

[0568] The structure of the above-described network entity will be described in more detail with reference to the drawings.

[0569] FIG. 16 is a block diagram of a network entity 1600 according to an embodiment of the disclosure.

[0570] The network entity 1600 may include an entity (apparatus, device, or server, etc.) that performs one or more network functions (NFs) or a part of a network function constituting a core network (e.g., a 5th generation (5G) core (5GC)) in a communication system. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across a plurality of network entities. In addition, when an NF is implemented within the network entity, the NF may be implemented in the form of software, and in such a case, a program for operating the NF may be stored in memory of the network entity 1600.

[0571] A single NF may be implemented by one or more instances, which may be deployed on the same network entity or distributed across multiple network entities to operate. The instance may be a software unit that logically executes a specific network function, and may be implemented in a form that is decoupled from physical hardware resources. Further, one or more NFs may be implemented in the form of one network slice to operate to satisfy specifications required by a particular service.

[0572] The NF may include at least one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), a unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN).

[0573] Referring to FIG. 16, the network entity 1600 may include at least one network interface 1601, at least one processor 1602 (hereinafter, “processor”), and at least one memory 1603 (hereinafter, “memory”). As described above, a NF may be implemented in the form of a physical device such as the network entity 1600, or may be virtualized and executed in the form of an instance. When implemented as an instance, the NF need not necessarily include physical components as illustrated in FIG. 16. In such a case, the instance may be logically represented as comprising one or more logical functional elements.

[0574] According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the network interface 1601, the processor 1602, and the memory 1603 of the network entity 1600 may operate. However, components of the network entity 1600 are not limited to the exemplary components illustrated in FIG. 16. In another embodiment, the network entity 1600 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in an embodiment, the network interface 1601, the processor 1602, or the memory 1603 may be integrated in the form of one component.

[0575] The network interface 1601 is a collective term for a transmitter part of the network entity 1600 and a receiver part of the network entity 1600, and may be a communication circuit for transmitting or receiving a signal to or from a user equipment (UE), a base station (BS), or another network entity. Here, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for a wired communication. For example, the network interface 1601 may include a circuit, logic, hardware, etc., configured to exchange a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless communication or wired communication. The network interface 1601 may operate using various protocols (e.g., non-access stratum (NAS) protocol). The network interface 1601 may also be referred to, for convenience of description or depending on implementation, as communication circuitry, network interface circuitry, or a communication interface circuitry.

[0576] The processor 1602 may control general operations of the network entity 1600 according to embodiments of the disclosure. The processor 1602 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processings. The processor 1602 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1603, individually, collectively or in any combination thereof. Further, the processor 1602 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme. Further, it should be noted that, according to another embodiment, in a case where NF is implemented in the form of an instance, the network function may be not necessarily configured by physical hardware.

[0577] According to an embodiment, the processor 1602 may be electrically, operatively, or communicatively coupled to the network interface 1601 to control the network interface 1601.

[0578] The processor 1602 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 1602 may be included in one chip and the other part of the processor 1602 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the network interface 1601 or the memory 1603.

[0579] The processor 1602 may perform or control or cause an operation of the network entity 1600 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1602 may control operations of the network entity 1600 for exchanging a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless or wired communication, using various protocols (e.g., NAS protocol). To this end, the processor 1602 may execute a computer program, codes, or instructions stored in the memory 1603, so as to control other components of the network entity 1600 to enable execution of various operations.

[0580] The memory 1603 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1603 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0581] The memory 1603 may be electrically, operatively, or communicatively coupled to the processor 1602 and may be accessed by the processor 1602.

[0582] The memory 1603 may store a computer program, codes, or instructions executable by the processor 1602. According to an embodiment, a computer program, codes, or instructions executable by the processor 1602 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1603, the processor 1602 may perform various functions according to an embodiment of the disclosure.

[0583] According to an embodiment of the disclosure, operations of the network entity 1600 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1603 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0584] Those skilled in the art will understand that the above illustrative embodiments are described herein and are not intended to be limiting. It should be understood that any two or more of the embodiments disclosed herein may be combined in any combination. Furthermore, other embodiments may be utilized and other changes may be made without departing from the spirit and scope of the subject matter presented herein. It will be readily understood that aspects of the invention of the disclosure as generally described herein and shown in the drawings may be arranged, replaced, combined, separated and designed in various different configurations, all of which are contemplated herein.

[0585] Those skilled in the art will understand that the various illustrative logic blocks, modules, circuits, and steps described in this application may be implemented as hardware, software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various illustrative components, blocks, modules, circuits, and steps are generally described above in the form of their functional sets. Whether such function sets are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Technicians may implement the described function sets in different ways for each specific application, but such design decisions should not be interpreted as causing a departure from the scope of this application.

[0586] The various illustrative logic blocks, modules, and circuits described in this application may be implemented or performed by a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates or transistor logics, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0587] The steps of the method or algorithm described in this application may be embodied directly in hardware, in a software module executed by a processor, or in a combination thereof. The software module may reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, or any other form of storage medium known in the art. An example storage medium is coupled to a processor to enable the processor to read and write information from / to the storage medium. In an alternative, the storage medium may be integrated into the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a communication apparatus (e.g., a terminal or a base station). In an alternative, the processor and the storage medium may reside in a communication apparatus (e.g., a terminal or a base station) as discrete components.

[0588] In one or more example designs, the functions may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, each function may be stored as one or more pieces of instructions or codes on a computer-readable medium or delivered through it. The computer-readable medium includes both a computer storage medium and a communication medium, the latter including any medium that facilitates the transfer of computer programs from one place to another. The storage medium may be any available medium that may be accessed by a general purpose or special purpose computer.

[0589] The above description is only example implementations of the present invention, and is not intended to limit the scope of protection of the present invention, which is determined by the appended claims.

[0590] Meanwhile, although specific embodiments of the present disclosure have been described in detail, various modifications may be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims and equivalents thereof.

Claims

1.A method performed by a user equipment (UE) in a wireless communication system, comprising:receiving, from a base station, configuration information relating to a switching between a primary serving cell (PCell) and a secondary serving cell (SCell);identifying a switching duration which comprises a first duration and a second duration based on the configuration information;receiving a plurality of semi-persistent scheduling (SPS) physical downlink shared channels (PDSCHs);generating a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook for the plurality of SPS PDSCHs; andtransmitting, to the base station, a physical uplink control channel (PUCCH) for the HARQ-ACK codebook,wherein the HARQ-ACK codebook excludes HARQ-ACK information for at least one SPS PDSCH which overlaps with the switching duration.2.The method of claim 1,wherein the first duration comprises a time duration for switching from the PCell to the SCell, andwherein the second duration comprises a time duration for switching from the SCell to the PCell.3.The method of claim 1,wherein the UE does not detect a downlink control information (DCI) format scheduling a downlink channel or an uplink channel whose transmission or reception is in the switching duration.4.The method of claim 1,wherein the configuration information indicates a switching pattern,wherein the switching pattern comprises an operation period of the PCell, the first duration, an operation period of the SCell, and the second duration.5.A method performed by a base station in a wireless communication system, comprising:transmitting, to a user equipment (UE), configuration information relating to a switching between a primary serving cell (PCell) and a secondary serving cell (SCell);transmitting a plurality of semi-persistent scheduling (SPS) physical downlink shared channels (PDSCHs);receiving, from the UE, a physical uplink control channel (PUCCH) for a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook,wherein a switching duration is identified based on the configuration information,wherein the HARQ-ACK codebook excludes HARQ-ACK information for at least one SPS PDSCH which overlaps with the switching duration.6.The method of claim 5,wherein the switching duration comprises a first duration and a second duration,wherein the first duration comprises a time duration for switching from the PCell to the SCell, andwherein the second duration comprises a time duration for switching from the SCell to the PCell.7.The method of claim 5,wherein the UE does not detect a downlink control information (DCI) format scheduling a downlink channel or an uplink channel whose transmission or reception is in the switching duration.8.The method of claim 5,wherein the configuration information indicates a switching pattern,wherein the switching pattern comprises an operation period of the PCell, the first duration, an operation period of the SCell, and the second duration.9.A user equipment (UE) comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the UE to:receive, from a base station, configuration information relating to a switching between a primary serving cell (PCell) and a secondary serving cell (SCell);identify a switching duration which comprises a first duration and a second duration based on the configuration information;receive a plurality of semi-persistent scheduling (SPS) physical downlink shared channels (PDSCHs);generate a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook for the plurality of SPS PDSCHs; andtransmit, to the base station, a physical uplink control channel (PUCCH) for the HARQ-ACK codebook,wherein the HARQ-ACK codebook excludes HARQ-ACK information for at least one SPS PDSCH which overlaps with the switching duration.10.The UE of claim 9,wherein the first duration comprises a time duration for switching from the PCell to the SCell, andwherein the second duration comprises a time duration for switching from the SCell to the PCell.11.The UE of claim 9,wherein the UE does not detect a downlink control information (DCI) format scheduling a downlink channel or an uplink channel whose transmission or reception is in the switching duration.12.The UE of claim 9,wherein the configuration information indicates a switching pattern,wherein the switching pattern comprises an operation period of the PCell, the first duration, an operation period of the SCell, and the second duration.13.A base station comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the base station to:transmit, to a user equipment (UE), configuration information relating to a switching between a primary serving cell (PCell) and a secondary serving cell (SCell);transmit a plurality of semi-persistent scheduling (SPS) physical downlink shared channels (PDSCHs);receive, from the UE, a physical uplink control channel (PUCCH) for a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook,wherein a switching duration is identified based on the configuration information,wherein the HARQ-ACK codebook excludes HARQ-ACK information for at least one SPS PDSCH which overlaps with the switching duration.14.The base station of claim 13,wherein the switching duration comprises a first duration and a second duration,wherein the first duration comprises a time duration for switching from the PCell to the SCell, andwherein the second duration comprises a time duration for switching from the SCell to the PCell.15.The base station of claim 13,wherein the UE does not detect a downlink control information (DCI) format scheduling a downlink channel or an uplink channel whose transmission or reception is in the switching duration.

Images