Method and apparatus for repetition transmission for downlink coverage enhancement in a wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method of operating a user equipment (UE) includes receiving, from a base station (BS), system information including configuration information associated with Message 4 (Msg4) physical downlink shared channel (PDSCH) repetition. The method also includes, during a four-step random access procedure, transmitting, to the BS, a Message 3 (Msg3) including an indication that the UE supports Msg4 PDSCH repetition, and in response to transmission of the Msg3, (i) receiving downlink control information (DCI) scheduling a Msg4 PDSCH repetition, and (ii) repeatedly receiving a Msg4 PDSCH scheduled by the DCI.

Description

METHOD AND APPARATUS FOR REPETITION TRANSMISSION FOR DOWNLINK COVERAGE ENHANCEMENT IN A WIRELESS COMMUNICATION SYSTEM

[0001] This disclosure relates generally to wireless networks. More specifically, this disclosure relates to repetition for downlink coverage enhancement.

[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 demand of wireless data traffic is rapidly increasing due to the growing popularity among consumers and businesses of smart phones and other mobile data devices, such as tablets, “note pad” computers, net books, eBook readers, and machine type of devices. In order to meet the high growth in mobile data traffic and support new applications and deployments, improvements in radio interface efficiency and coverage are of paramount importance.

[0009] To meet the demand for wireless data traffic having increased since deployment of 4G communication systems, and to enable various vertical applications, 5G communication systems have been developed and are currently being deployed. The enablers for the 5G / NR mobile communications include massive antenna technologies, from legacy cellular frequency bands up to high frequencies, to provide beamforming gain and support increased capacity, new waveforms (e.g., new radio access technologies [RATs]) to flexibly accommodate various services / applications with different requirements, new multiple access schemes to support massive connections, etc.

[0010] This disclosure provides apparatuses and methods for repetition for downlink coverage enhancement.

[0011] In one embodiment, a method of operating a user equipment (UE) is provided. The method includes receiving, from a base station (BS), system information including configuration information associated with Message 4 (Msg4) physical downlink shared channel (PDSCH) repetition. The method also includes, during a four-step random access procedure, transmitting, to the BS, a Message 3 (Msg3) including an indication that the UE supports Msg4 PDSCH repetition, and in response to transmission of the Msg3, (i) receiving downlink control information (DCI) scheduling a Msg4 PDSCH repetition, and (ii) repeatedly receiving a Msg4 PDSCH scheduled by the DCI.

[0012] In another embodiment, a method of operating a BS is provided. The method includes transmitting, to a UE, system information including configuration information associated with Msg4 PDSCH repetition. The method also includes, during a four-step random access procedure, receiving, from the UE, a Msg3 including an indication that the UE supports Msg4 PDSCH repetition, and in response to receiving the Msg3, (i) transmitting downlink control information (DCI) scheduling a Msg4 PDSCH repetition, and (ii) repeatedly transmitting a Msg4 PDSCH scheduled by the DCI.

[0013] In yet another embodiment, an electronic device is provided. The electronic device includes at least one processor including processing circuitry, and memory storing instructions. The instructions, when executed by the at least one processor individually or collectively, cause the electronic device to receive, from a BS, system information including configuration information associated with Msg4 PDSCH repetition. The instructions, when executed by the at least one processor individually or collectively, also cause the electronic device to, during a four-step random access procedure, transmit, to the BS, a Msg3 including an indication that the electronic device supports Msg4 PDSCH repetition, and in response to transmission of the Msg3, (i) receive DCI scheduling a Msg4 PDSCH repetition, and (ii) repeatedly receive a Msg4 PDSCH scheduled by the DCI.

[0014] Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

[0015] Before undertaking the DETAILED DESCRIPTION below, it may 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, 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 may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may 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 may be used, and only one item in the list may 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.

[0016] 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.

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

[0018] The following documents and standards descriptions are hereby incorporated by reference into the present disclosure as if fully set forth herein: [1] 3GPP, TS 38.300 v18.4.0, 5G; NR; NR and NG-RAN Overall Description; Stage 2; [2] 3GPP, TS 38.331 v18.4.0, 5G; NR; Radio Resource Control (RRC); Protocol specification; [3] 3GPP, TS 38.321 v18.4.0, NR; Medium Access Control (MAC) protocol specification; [4] 3GPP, TS 38.304 v18.4.0, NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state; and [5] 3GPP, TS 38.306 v18.4.0, NR; User Equipment (UE) radio access capabilities.

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

[0020] For a more complete understanding of this disclosure and its advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

[0021] FIG. 1 illustrates an example wireless network according to embodiments of the present disclosure;

[0022] FIGS. 2A and 2B illustrate example wireless transmit and receive paths according to embodiments of the present disclosure;

[0023] FIG. 3A illustrates an example UE according to embodiments of the present disclosure;

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

[0025] FIG. 4 illustrates an example procedure for 4-step CBRA with a Msg3 including a request / capability for Msg4 PDSCH repetition according to embodiments of the present disclosure;

[0026] FIGS. 5-7 illustrate example MAC subhheaders according to embodiments of the present disclosure;

[0027] FIG. 8 illustrates an example procedure for 2-step CBRA with MsgB PDSCH repetition according to embodiments of the present disclosure;

[0028] FIG. 9 illustrates an example procedure for Fallback CBRA with Msg4 PDSCH repetition according to embodiments of the present disclosure;

[0029] FIG. 10 illustrates an example method for repetition for downlink coverage enhancement according to embodiments of the present disclosure;

[0030] FIG. 11 illustrates another example method for repetition for downlink coverage enhancement according to embodiments of the present disclosure;

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

[0032] FIG. 13 is a block diagram of a base station (BS) according to an embodiment of the disclosure; and

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

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

[0035] In describing the embodiments, while numerous details are set forth for the purpose of illustration, it is understood that some aspects of the disclosure may be practiced with less than all of these details. Numerous variations and alternatives to the details provided herein are possible and are considered within the scope of the disclosure. In some instances, descriptions related to technical contents well-known in the art may be omitted so as to not obscure an understanding of the disclosure, and such omitted descriptions are understood to be within the scope of the disclosure.

[0036] 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.

[0037] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described herein in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth herein, but may be implemented in various different forms. Other features, aspects, and advantages of the subject matter described herein will become apparent from the disclosure. The following embodiments are merely examples to aid in an understanding of the disclosure and should not be construed to narrow the scope or spirit of the subject matter described herein in any way, but on the contrary, the disclosure covers all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims and equivalents thereof. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, terms which will be described herein 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.

[0038] Herein, it will be understood that each block of 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).

[0039] 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.

[0040] As used in embodiments of the disclosure, a “~unit / module” 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 / module” does not always have a meaning limited to software or hardware. The “~unit / module” may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the “~unit / module” 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 / module” may be either combined into a smaller number of components and a “~unit / module,” or divided into additional components and a “~unit / module.” Moreover, the components and “~units / modules” 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 / module” may include one or more processors.

[0041] 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.

[0042] 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, microprocessors, microcontrollers, digital　signal processors, FPGA, ASIC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like. The one processor or the combination of processors executes instructions that can be stored in a memory, such as the　operating system, in order to control the overall operation of the device.　Also, the one processor or the combination of processors is also capable of executing other processes and programs　resident in the memory, such as processes for the disclosure.

[0043] 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.

[0044] 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. Additionally, or alternatively, such software may be a computer program [product] comprising instructions which, 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.

[0045] 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.

[0046] 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.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] 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.

[0051] 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.

[0052] 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.

[0053] 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.

[0054] 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, elements 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.

[0055] 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.

[0056] 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.

[0057] 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. If a method step (e.g. transmit a signal) is performed according to the disclosure of the application in connection with one of the above terms (such as “in case that ~” or the like), it may be interpreted to include the meanings (disclosure) of a prior determination that a feature has a specific state “~” (e.g. a bit length is above X), and then perform the method step in response to said determination.

[0058] 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.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] In the embodiments of the present disclosure described herein, 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.

[0063] The drawings or flowcharts described herein illustrate example 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.

[0064] The process of the flowchart may be performed by a device. One or more of the steps of the　flowchart can be implemented by one or more processors / computer programs executing　instructions to perform the noted functions.

[0065] The methods and apparatuses proposed in the embodiments of the present disclosure may be disclosed in connection with drawings disclosing flowcharts to illustrate example methods that may be implemented according to the principles of the present disclosure. Such flowcharts may contain different branches and / or sub-branches. It is understood that the principles of the present disclosure do not only contain the combination of all branches / sub-branches disclosed in the embodiment, but the present disclosure also contains at least one isolated branch / isolated sub-branch, in particular to a single branch / single sub-branch.

[0066] 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.

[0067] 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.

[0068] 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 describedherein, 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) or similar technical specifications, e.g., from the European telecommunications standards institute (ETSI), where appropriate.

[0069] Hereinafter, a base station (BS) 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 wireless access unit, a BS controller, or a node on a network.

[0070] 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 5th generation (5G) base station architectures in which such CU and DU functional splits are implemented.

[0071] A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or any other device / system capable of performing communication functions.

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

[0073] Furthermore, hereinafter, 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

[0074] 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."

[0075] 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, ...), RRC, or 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 Layer 3 (L3) signaling.

[0076] 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), DCI, 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.

[0077] 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.

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

[0079] FIGS. 1 through 14, discussed below, and the various embodiments used to describe the principles of this disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of this disclosure may be implemented in any suitably arranged wireless communication system.

[0080] To meet the demand for wireless data traffic having increased since deployment of 4G communication systems and to enable various vertical applications, 5G / NR communication systems have been developed and are currently being deployed. The 5G / NR communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 28 GHz or 60GHz bands, so as to accomplish higher data rates or in lower frequency bands, such as 6 GHz, to enable robust coverage and mobility support. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are discussed in 5G / NR communication systems.

[0081] In addition, in 5G / NR communication systems, development for system network improvement is under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancelation and the like.

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

[0083] FIGS. 1-3B below describe various embodiments implemented in wireless communications systems and with the use of orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication techniques. The descriptions of FIGS. 1-3B are not meant to imply physical or architectural limitations to the manner in which different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any suitably arranged communications system.

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

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

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

[0087] Depending on the network type, the term “base station” or “BS” can refer to any component (or collection of components) configured to provide wireless access to a network, such as transmit point (TP), transmit-receive point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wirelessly enabled devices. Base stations may provide wireless access in accordance with one or more wireless communication protocols, e.g., 5G / NR 3rdgeneration partnership project (3GPP) NR, long term evolution (LTE), LTE advanced (LTE-A), high speed packet access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For the sake of convenience, the terms “BS” and “TRP” are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Also, depending on the network type, the term “user equipment” or “UE” can refer to any component such as “mobile station,” “subscriber station,” “remote terminal,” “wireless terminal,” “receive point,” or “user device.” For the sake of convenience, the terms “user equipment” and “UE” are used in this patent document to refer to remote wireless equipment that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile telephone or smartphone) or is normally considered a stationary device (such as a desktop computer or vending machine).

[0088] Dotted lines show the approximate extents of the coverage areas 120 and 125, which are shown as approximately circular for the purposes of illustration and explanation only. It should be clearly understood that the coverage areas associated with gNBs, such as the coverage areas 120 and 125, may have other shapes, including irregular shapes, depending upon the configuration of the gNBs and variations in the radio environment associated with natural and man-made obstructions.

[0089] As discussed in greater detail below, the wireless network 100 may have communications facilitated via one or more communication satellite(s) 104 that may be in orbit over the earth. The communication satellite(s) 104 can communicate directly with the BSs 102 and 103 to provide network access, for example, in situations where the BSs 102 and 103 are remotely located or otherwise in need of facilitation for network access connections beyond or in addition to common fronthaul and / or backhaul connections. The BSs can also be on board the communication satellite(s) 104. Various of the UEs (e.g., as depicted by UE 116) may be capable of at least some direct communication and / or localization with the communication satellite(s) 104.

[0090] A non-terrestrial network (NTN) refers to a network, or segment of networks using RF resources on board a communication satellite (or unmanned aircraft system platform) (e.g., communication satellite(s) 104). Taking into account the capabilities of providing wide coverage and reliable service, an NTN is envisioned to ensure service availability and continuity ubiquitously. For instance, an NTN can support communication services in unserved areas that cannot be covered by other terrestrial networks (TNs), in underserved areas that are experiencing limited communication services, for devices and passengers on board moving platforms, and for future railway / maritime / aeronautical communications, etc.

[0091] As described in more detail below, one or more of the UEs 111-116 include circuitry, programing, or a combination thereof, for repetition for downlink coverage enhancement. In certain embodiments, one or more of the gNBs 101-103 includes circuitry, programing, or a combination thereof, to support repetition for downlink coverage enhancement in a wireless communication system.

[0092] Although FIG. 1 illustrates one example of a wireless network, various changes may be made to FIG. 1. For example, the wireless network could include any number of gNBs and any number of UEs in any suitable arrangement. Also, the gNB 101 could communicate directly with any number of UEs and provide those UEs with wireless broadband access to the network 130. Similarly, each gNB 102-103 could communicate directly with the network 130 and provide UEs with direct wireless broadband access to the network 130. Further, the gNBs 101, 102, and / or 103 could provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0093] FIGS. 2A and 2B illustrate example wireless transmit and receive paths according to embodiments of the present disclosure. In the following description, a transmit path 200 may be described as being implemented in a gNB (such as gNB 102), while a receive path 250 may be described as being implemented in a UE (such as UE 116). However, it will be understood that the receive path 250 can be implemented in a gNB and that the transmit path 200 can be implemented in a UE. In some embodiments, the transmit path 200 and / or the receive path 250 is configured to implement and / or support repetition for downlink coverage enhancement as described in embodiments of the present disclosure.

[0094] The transmit 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, an add cyclic prefix block 225, and an up-converter (UC) 230. The receive path 250 includes a down-converter (DC) 255, a remove cyclic prefix 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.

[0095] In the transmit path 200, the channel coding and modulation block 205 receives a set of information bits, applies coding (such as a low-density parity check (LDPC) coding), and modulates the input bits (such as with Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) to generate a sequence of frequency-domain modulation symbols. The serial-to-parallel block 210 converts (such as de-multiplexes) the serial modulated symbols to parallel data in order to generate N parallel symbol streams, where N is the IFFT / FFT size used in the gNB 102 and the UE 116. The size N IFFT block 215 performs an IFFT operation on the N parallel symbol streams to generate time-domain output signals. The parallel-to-serial block 220 converts (such as multiplexes) the parallel time-domain output symbols from the size N IFFT block 215 in order to generate a serial time-domain signal. The add cyclic prefix block 225 inserts a cyclic prefix to the time-domain signal. The up-converter 230 modulates (such as up-converts) the output of the add cyclic prefix block 225 to an RF frequency for transmission via a wireless channel. The signal may also be filtered at baseband before conversion to the RF frequency.

[0096] A transmitted RF signal from the gNB 102 arrives at the UE 116 after passing through the wireless channel, and reverse operations to those at the gNB 102 are performed at the UE 116. The down-converter 255 down-converts the received signal to a baseband frequency, and the remove cyclic prefix 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 to parallel time domain signals. 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 signals to 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.

[0097] Each of the gNBs 101-103 may implement a transmit path 200 that is analogous to transmitting in the downlink to UEs 111-116 and may implement a receive path 250 that is analogous to receiving in the uplink from UEs 111-116. Similarly, each of UEs 111-116 may implement a transmit path 200 for transmitting in the uplink to gNBs 101-103 and may implement a receive path 250 for receiving in the downlink from gNBs 101-103.

[0098] 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 particular example, at least some of the components in FIGS. 2A and 2B may be implemented in software, while other components may be implemented by configurable hardware or a mixture of software and configurable hardware. For instance, the FFT block 270 and the IFFT block 215 may be implemented as configurable software algorithms, where the value of size N may be modified according to the implementation.

[0099] Furthermore, although described as using FFT and IFFT, this is by way of illustration only and should not be construed to limit the scope of this disclosure. Other types of transforms, such as Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions, can be used. It will be appreciated that the value of the variable N may be any integer number (such as 1, 2, 3, 4, or the like) for DFT and IDFT functions, while the value of the variable N may be any integer number that is a power of two (such as 1, 2, 4, 8, 16, or the like) for FFT and IFFT functions.

[0100] Although FIGS. 2A and 2B illustrate examples of wireless transmit and receive 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 particular needs. Also, FIGS. 2A and 2B are meant to illustrate examples of the types of transmit and receive paths that can be used in a wireless network. Any other suitable architectures can be used to support wireless communications in a wireless network.

[0101] FIG. 3A illustrates an example UE 116 according to embodiments of the present disclosure. The embodiment of the UE 116 illustrated in FIG. 3A is for illustration only, and the UEs 111-115 of FIG. 1 could have the same or similar configuration. However, UEs come in a wide variety of configurations, and FIG. 3A does not limit the scope of this disclosure to any particular implementation of a UE.

[0102] As shown in FIG. 3A, the UE 116 includes antenna(s) 305, a transceiver(s) 310, and a microphone 320. The UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, an input 350, a display 355, and a memory 360. The memory 360 includes an operating system (OS) 361 and one or more applications 362.

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

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

[0105] The processor 340 can include one or more processors or other processing devices and execute the OS 361 stored in the memory 360 in order to control the overall operation of the UE 116. For example, the processor 340 could control the reception of DL channel signals and the transmission of UL channel signals by the transceiver(s) 310 in accordance with well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0106] The processor 340 is also capable of executing other processes and programs resident in the memory 360, for example, processes for repetition for downlink coverage enhancement as discussed in greater detail below. The processor 340 can move data into or out of the memory 360 as required by an executing process. In some embodiments, the processor 340 is configured to execute the applications 362 based on the OS 361 or in response to signals received from gNBs or an operator. The processor 340 is also coupled to the I / O interface 345, which provides the UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. The I / O interface 345 is the communication path between these accessories and the processor 340.

[0107] The processor 340 is also coupled to the input 350, which includes for example, a touchscreen, keypad, etc., and the display 355. The operator of the UE 116 can use the input 350 to enter data into the UE 116. The display 355 may be a liquid crystal display, light emitting diode display, or other display capable of rendering text and / or at least limited graphics, such as from web sites.

[0108] The memory 360 is coupled to the processor 340. Part of the memory 360 could include a random-access memory (RAM), and another part of the memory 360 could include a Flash memory or other read-only memory (ROM).

[0109] Although FIG. 3A illustrates one example of UE 116, various changes may be made to FIG. 3A. For example, various components in FIG. 3A could be combined, further subdivided, or omitted and additional components could be added according to particular needs. As a particular example, the processor 340 could be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, the transceiver(s) 310 may include any number of transceivers and signal processing chains and may be connected to any number of antennas. Also, while FIG. 3A illustrates the UE 116 configured as a mobile telephone or smartphone, UEs could be configured to operate as other types of mobile or stationary devices.

[0110] FIG. 3B illustrates an example gNB 102 according to embodiments of the present disclosure. The embodiment of the gNB 102 illustrated in FIG. 3B is for illustration only, and the gNBs 101 and 103 of FIG. 1 could have the same or similar configuration. However, gNBs come in a wide variety of configurations, and FIG. 3B does not limit the scope of this disclosure to any particular implementation of a gNB.

[0111] As shown in FIG. 3B, the gNB 102 includes multiple antennas 370a-370n, multiple transceivers 372a-372n, a controller / processor 378, a memory 380, and a backhaul or network interface 382.

[0112] The transceivers 372a-372n receive, from the antennas 370a-370n, incoming RF signals, such as signals transmitted by UEs in the network 100. The transceivers 372a-372n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are processed by receive (RX) processing circuitry in the transceivers 372a-372n and / or controller / processor 378, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. The controller / processor 378 may further process the baseband signals.

[0113] Transmit (TX) processing circuitry in the transceivers 372a-372n and / or controller / processor 378 receives analog or digital data (such as voice data, web data, e-mail, or interactive video game data) from the controller / processor 378. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate processed baseband or IF signals. The transceivers 372a-372n up-converts the baseband or IF signals to RF signals that are transmitted via the antennas 370a-370n.

[0114] The controller / processor 378 can include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 378 could control the reception of uplink (UL) channel signals and the transmission of downlink (DL) channel signals by the transceivers 372a-372n in accordance with well-known principles. The controller / processor 378 could support additional functions as well, such as more advanced wireless communication functions. For instance, the controller / processor 378 could support beam forming or directional routing operations in which outgoing / incoming signals from / to multiple antennas 370a-370n are weighted differently to effectively steer the outgoing signals in a desired direction. Any of a wide variety of other functions could be supported in the gNB 102 by the controller / processor 378.

[0115] The controller / processor 378 is also capable of executing programs and other processes resident in the memory 380, such as an OS and, for example, processes to support repetition for downlink coverage enhancement as discussed in greater detail below. The controller / processor 378 can move data into or out of the memory 380 as required by an executing process.

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

[0117] The memory 380 is coupled to the controller / processor 378. Part of the memory 380 could include a RAM, and another part of the memory 380 could include a Flash memory or other ROM.

[0118] Although FIG. 3B illustrates one example of gNB 102, various changes may be made to FIG. 3B. For example, the gNB 102 could include any number of each component shown in FIG. 3B. Also, various components in FIG. 3B could be combined, further subdivided, or omitted and additional components could be added according to particular needs.

[0119] The Third-Generation Partnership Project (3GPP) has developed technical specifications and standards to define a fifth generation (5G) radio-access technology, known as 5G New Radio (NR). To improve NR downlink coverage, repetition of the Physical Downlink Control Channel (PDCCH) and Physical Downlink Shared Channel (PDSCH) are supported. The PDCCH can be used to schedule DL transmissions on the PDSCH and UL transmissions on Physical Uplink Shared Channel (PUSCH), where the Downlink Control Information (DCI) on the PDCCH includes DL assignments containing at least modulation and coding format, resource allocation, and hybrid-ARQ information related to DL-SCH, UL scheduling grants containing at least modulation and coding format, resource allocation, and hybrid-ARQ information related to the Uplink Shared Channel (UL-SCH), and other control information.

[0120] A UE monitors a set of PDCCH candidates in the configured monitoring occasions in one or more configured COntrol REsource SETs (CORESETs) according to the corresponding search space configurations. A CORESET refers to a PDCCH decode region which includes a set of physical resources. Search Space is an area within a CORESET that the UE should monitor to detect a specific PDCCH / DCI. A CORESET may have multiple search spaces. The search space is where the UE attempts blind decoding. By definition, each search space is a set of control channel elements at a different aggregation level(s). In other words, a search space tells how many candidates are there to decode at different aggregation levels.

[0121] There are two types of search spaces called "UE-specific search space" (USS) and "Common Search Space" (CSS). A USS is dedicated for each specific UE and informed to the UE via an RRC signaling message. This means that the UE needs to complete RRC establishment to get the information about the UE-specific search space. CSS is the search space that every UE needs to search for cell-common signals (e.g., a PDCCH for a system information block [SIB]). For example, the UE needs to detect a PDCCH for SIB1 reception and a PDCCH for random access channel (RACH) procedure (e.g., DCI for Msg2 / Msg4 reception). Different types of PDCCH are monitored in a CSS. A Type0-PDCCH configured bysearchSpaceSIB1is used to schedule SIB1, a Type0A-PDCCH configured bysearchSpaceOtherSystemInformationis used to schedule other SIBs, a Type1-PDCCH configured byra-SearchSpaceis used to schedule Msg2 and Msg4 in a RACH procedure, and a Type-2 PDCCH configured bypagingSearchSpaceandpeiSearchSpaceis used to schedule paging early indication (PEI) and Paging messages.

[0122] For PDSCH repetition, aggregation of multiple slots with Transport Block (TB) repetition is supported. The PDCCH repetition is operated by using two search spaces which are explicitly linked by configuration provided by the RRC layer, and are associated with corresponding CORESETs. For PDCCH repetition, two linked search spaces are configured with the same number of candidates, and two PDCCH candidates in two search spaces are linked with the same candidate index. When PDCCH repetition is scheduled to a UE, an intra-slot repetition is allowed and each repetition has the same number of CCEs and coded bits, and corresponds to the same DCI payload. PDCCH repetition by linking two common search spaces is not presently supported for a Type0-PDCCH configured bysearchSpaceSIB1, Type0A-PDCCH configured bysearchSpaceOtherSystemInformation, Type1-PDCCH configured byra-SearchSpace, and Type-2 PDCCH configured bypagingSearchSpaceandpeiSearchSpace.

[0123] Repetition is also supported in multi-TRP operation. There are presently two different operation modes for multi-TRP PDCCH: PDCCH repetition and Single Frequency Network (SFN) based PDCCH transmission. In both modes, the UE can receive two PDCCH transmissions, one from each TRP, carrying the same DCI. In PDCCH repetition mode, the UE can receive the two PDCCH transmissions carrying the same DCI from two linked search spaces each associated with a different CORESET. In SFN based PDCCH transmission mode, the UE can receive the two PDCCH transmissions carrying the same DCI from a single search space / CORESET using different TCI states.

[0124] For RRC connection reestablishment, TN to NTN reestablishment can be supported. For example, the network can indicate an enabling indication for TN to NTN RRC connection re-establishment, for example, in UE dedicated signaling or in SI of a current cell or in a SIB1 of the selected cell for RRC reestablishment. The UE can select NTN cell for RRC connection reestablishment, if the UE has NTN-specific assistance information acquired from the current cell and / or if TN to NTN RRC connection re-establishment is enabled and / or if the UE supports TN to NTN RRC connection reestablishment.

[0125] To improve DL coverage, repetition for PDCCH scheduling common signalling and PDSCH repetition for SIB1 and Msg4 are considered. Various embodiments of the present disclosure provide relevant UE capabilities, configuration signalling and UE procedures for PDCCH / PDSCH repetition.

[0126] To improve DL coverage, PDCCH repetition for CSS is considered. Various embodiments of the present disclosure provide UE procedures for PDCCH repetition for CSS. For example, in some embodiments, PDCCH repetition in CSS can be supported for PDCCH for SIB1, and / or PDCCH for other SIBs, and / or PDCCH for Msg2 in an RA procedure, and / or PDCCH for Msg4 in an RA procedure, and / or PDCCH for paging, and / or PDCCH for PEI.

[0127] In some embodiments, the network (NW) transmits a PDCCH repetition enabling indication and / or PDCCH repetition configuration. In embodiments such as these, the PDCCH repetition enabling indication and / or PDCCH repetition configuration can be pre-defined and / or transmitted in system information (e.g., the master information block [MIB] or SIB1) and / or in UE dedicated RRC signalling. In some embodiments, The PDCCH repetition enabling indication can be explicitly indicated by a one-bit RRC parameter or implicitly indicated by the PDCCH repetition configuration. In some embodiments, the UE receives the PDCCH repetition enabling indication and / or PDCCH repetition configuration and receives PDCCH repeatedly based on the PDCCH repetition enabling indication and / or the PDCCH repetition configuration.

[0128] As an example, the PDCCH repetition configuration can be included in SIB1 (e.g., inPDCCH-ConfigCommon). The PDCCH repetition configuration can include a new list of CSSs such that the maximum number of CSSs per cell can be extended from 4 (i.e., 4 is the current max number of CSS per cell) to X, where X can be an integer from 5, 6, 7, or 8. The PDCCH repetition configuration can include a search space linking ID which is used to link two CSSs. If two CSSs have the same search space linking ID, the UE assumes these CSSs are linked for PDCCH repetition.

[0129] In some embodiments, for Type0-PDCCH repetition for SIB1, two CSSs (e.g., the existing CSS which is identified bysearchSpaceSIB1, and a new CSS in the same BWP, e.g., identified bysearchSpaceSIB1-2) can be linked by a search space linking ID. In embodiments such as these, the UE monitors and / or detects Type0-PDCCH on both CSSs.searchSpaceSIB1-2 indicates the ID of the second search space for SIB1 message. In the initial DL BWP of the UE's PCell, the network sets this field to 0. If the field is absent, the UE does not receive SIB1 in this BWP. In some embodiments, this field is absent for the reduced capability (RedCap)-specific initial DL BWP, if it does not include a cell defining (CD)-SSB and the entire CORESET#0. In that case, a RedCap or enhanced RedCap (eRedCap) UE in an RRC_IDLE or RRC_INACTIVE state shall monitor the PDCCH to receive SIB1 using searchSpaceSIB1 in the initial DL BWP that includes the CD-SSB and the entire CORESET#0.

[0130] In some embodiments, for Type0A-PDCCH repetition for other SIBs, two CSSs, (e.g., the existing CSS which is identified bysearchSpaceOtherSystemInformation, and a new CSS in the same BWP, e.g., identified bysearchSpaceOtherSystemInformation2) can be linked by a search space linking ID. In embodiments such as these, the UE monitors and / or detects Type0A-PDCCH on both CSSs.searchSpaceOtherSystemInformation2indicates the ID of the search space linked to the search space indicated bysearchSpaceOtherSystemInformationfor other system information, (i.e.,SIB2and beyond). In some embodiments, this field is present only if a search space linking ID is configured for the search space indicated bysearchSpaceOtherSystemInformation, it is absent otherwise.

[0131] In some embodiments, for Type1-PDCCH repetition for Msg2 / 4, two CSSs, (e.g., the existing CSS which is identified byra-SearchSpace, and a new CSS in the same BWP, e.g., identified byra-SearchSpace2), can be linked by a search space linking ID. In embodiments such as these, the UE monitors and / or detects Type1-PDCCH on both CSSs.ra-SearchSpace2 indicates the ID of the search space linked to the search space indicated byra-SearchSpacefor random access procedure. In some embodiments, this field is present only if a search space linking ID is configured for the search space indicated byra-SearchSpace, and is absent otherwise.

[0132] In some embodiments, for paging, the UE monitors one paging occasion (PO) per DRX cycle. A PO is a set of PDCCH monitoring occasions and can include multiple time slots (e.g., subframes or OFDM symbols) where a paging DCI can be sent. One Paging Frame (PF) is one Radio Frame and may contain one or multiple PO(s) or starting points of a PO. The PF and PO for paging are determined by the following formulas: SFN for the PF is determined by (SFN + PF_offset) mod T = (T div N)*(UE_ID mod N); Index (i_s), indicating the index of the PO UE is required to monitor, is determined by i_s = floor (UE_ID / N) mod Ns.

[0133] In some embodiments, for Type2-PDCCH repetition for paging, two CSSs, (e.g., the existing CSS which is identified bypagingSearchSpace, and a new CSS in the same BWP, e.g., identified bypagingSearchSpace2) can be linked by a search space linking ID. In embodiments such as these, the UE monitors and / or detects Type2-PDCCH for paging on both CSSs.pagingSearchSpace2indicates the ID of the search space linked to the search space indicated bypagingSearchSpacefor paging. In some embodiments, this field is present only if a search space linking ID is configured for the search space indicated byra-SearchSpace, and is absent otherwise.

[0134] In some embodiments, if two CSSs for paging are linked by a search space linking ID, the PDCCH monitoring occasions for paging are determined according to the two linked CSS,pagingSearchSpaceandpagingSearchSpace2andfirstPDCCH-MonitoringOccasionOfPOandnrofPDCCH-MonitoringOccasionPerSSB-InPOifconfigured. In embodiments such as these, whenSearchSpaceId= 0 is configured forpagingSearchSpaceand / orpagingSearchSpace2, the PDCCH monitoring occasions for paging are same as for SIB1. WhenSearchSpaceId= 0 is configured forpagingSearchSpaceand / orpagingSearchSpace2, Ns is either 1 or 2. For Ns = 1, there is only one PO which starts from the first PDCCH monitoring occasion for paging in the PF. For Ns = 2, PO is either in the first half frame (i_s = 0) or the second half frame (i_s = 1) of the PF. WhenSearchSpaceIdother than 0 is configured forpagingSearchSpaceand / orpagingSearchSpace2,the UE monitors the (i_s + 1)thPO.

[0135] In some embodiments, for PEI, the UE monitors one PEI occasion per DRX cycle. A PEI occasion (PEI-O) is a set of PDCCH monitoring occasions (MOs) and can include multiple time slots (e.g., subframes or OFDM symbols) where a PEI can be sent). In some embodiments, in multi-beam operations, the UE assumes that the same PEI is repeated in all transmitted beams and thus the selection of the beam(s) for the reception of the PEI is up to UE implementation. In some embodiments, the time location of PEI-O for UE's PO is determined by a reference point and an offset. In embodiments such as these, the reference point is the start of a reference frame determined by a frame-level offset from the start of the first PF of the PF(s) associated with the PEI-O, provided bypei-FrameOffsetin SIB1. The offset is a symbol-level offset from the reference point to the start of the first PDCCH MO of this PEI-O, provided byfirstPDCCH-MonitoringOccasionOfPEI-Oin SIB1.

[0136] In some embodiments, for Type2-PDCCH repetition for PEI, two CSSs (e.g., the existing CSS which is identified bypei-SearchSpace, and a new CSS in the same BWP, e.g., identified bypei-SearchSpace2) can be linked by a search space linking ID. In embodiments such as these, the UE monitors and / or detects Type2-PDCCH for PEI on both CSSs.pei-SearchSpace2indicates the ID of search space linked to the search space indicated bypei-SearchSpacefor PEI. In some embodiments, this field is present only if a search space linking ID is configured for the search space indicated bypei-SearchSpace, and is absent otherwise.pei-SearchSpacecan be configured to one of the CSSs configured by commonSearchSpaceList with SearchSpaceId > 0. SearchSpaceId = 0 can be configured for the case of SS / PBCH block and CORESET multiplexing pattern 2 or 3.

[0137] In some embodiments, if two CSSs for PEI are linked by a search space linking ID, the PDCCH MOs for PEI are determined according topei-SearchSpace,pei-SearchSpace2, pei-FrameOffset,firstPDCCH-MonitoringOccasionOfPEI-OandnrofPDCCH-MonitoringOccasionPerSSB-InPOifconfigured. In embodiments such as these, whenSearchSpaceId= 0 is configured forpei-SearchSpaceand / orpei-SearchSpace2, the PDCCH MOs for PEI are same as for SIB1. WhenSearchSpaceId= 0 is configured forpei-SearchSpaceand / orpei-SearchSpace2, the UE monitors the PEI-O according tosearchSpaceZero. The UE determines first PDCCH MO for PEI-O based onpei-FrameOffsetandfirstPDCCH-MonitoringOccasionOfPEI-O, as for the case withSearchSpaceId> 0 configured. WhenSearchSpaceIdother than 0 is configured forpei-SearchSpaceand / orpei-SearchSpace2,the UE monitors the PEI-O according to the search space with the configuredSearchSpaceId.

[0138] In some embodiments, the PDCCH repetition configuration in SIB1 can include a repetition number R, which indicates the number of repeated PDCCH. In embodiments such as these, the PDCCH repetition configuration in SIB1 can implicitly indicate the enabling of PDCCH repetition. The repetition number R can indicate the number of PDCCH monitoring occasions to be monitored repeatedly. In one example, R is a fixed value signaled by the NW. In another example, the value of R depends on the measured RSRP of the current serving cell UE camped on. The mapping between the value of R and the value of measured RSRP can be signaled. A larger value of measured RSRP can be mapped to a smaller value of R.

[0139] In some embodiments, for RA procedure, if R (e.g., indicating the number of PDCCH monitoring occasions to be monitored repeatedly for Msg2 / 4) is signaled, a UE capable of receiving PDCCH repetitions for Msg2 / 4 monitors and / or detects (e.g., combines and decodes) R PDCCH monitoring occasions on the search space indicated byra-SearchSpace.

[0140] In some embodiments, for paging, if R (e.g., indicating the number of PDCCH repetition for paging, and / or the number of PDCCH monitoring occasions to be monitored repeatedly) is signaled, a UE capable of receiving PDCCH repetitions for paging monitors and / or detects (e.g., combines and decodes) R PDCCH monitoring occasions for the same PO. A PO is a set of 'S*X ' consecutive PDCCH monitoring occasions where 'S' is the number of actual transmitted SSBs determined according tossb-PositionsInBurstinSIB1and X is thenrofPDCCH-MonitoringOccasionPerSSB-InPOif configured or is equal to 1 otherwise. The [x*S+K]thPDCCH monitoring occasion for paging in the PO corresponds to the Kthtransmitted SSB, where x=0,1,...,X-1, K=1,2,...,S. The PDCCH monitoring occasions for paging which do not overlap with UL symbols (determined according totdd-UL-DL-ConfigurationCommon) are sequentially numbered from zero starting from the first PDCCH monitoring occasion for paging in the PF. WhenfirstPDCCH-MonitoringOccasionOfPOis present, the starting PDCCH monitoring occasion number of (i_s + 1)thPO is the (i_s + 1)thvalue of thefirstPDCCH-MonitoringOccasionOfPOparameter; otherwise, it is equal to i_s * S*X. In one example, the UE chooses R PDCCH monitoring occasions according to implementation starting from the first PDCCH monitoring occasion in its PO. In another example, the UE monitors R consecutive PDCCH monitoring occasions from the first PDCCH monitoring occasion in its PO which is the (i_s + 1)thPO. In a third example, ifnrofPDCCH-MonitoringOccasionPerSSB-InPOis configured, the UE selects one SSB from the S transmitted SSBs and monitors min (R, X) PDCCH monitoring occasions among the X PDCCH monitoring occasions of the selected SSB. If X > 1 and if R is not configured, when the UE detects a PDCCH transmission addressed to a P-RNTI within its PO, the UE is not required to monitor the subsequent PDCCH monitoring occasions for this PO.

[0141] In some embodiments, for PEI, if R (e.g., indicating the number of PDCCH repetitions for PEI, and / or the number of PDCCH monitoring occasions to be monitored repeatedly) is signaled, a UE capable of receiving PDCCH repetitions for PEI monitors and / or detects (e.g., combines and decodes) R PDCCH monitoring occasions for its PEI-O. In embodiments such as these, if R is not configured, when the UE detects a PEI within its PEI-O, the UE is not required to monitor and / or detect (e.g., combine and decode) the subsequent MO(s) associated with the same PEI-O. A PEI occasion is a set of 'S*X' consecutive PDCCH MOs, where 'S' is the number of actual transmitted SSBs determined according tossb-PositionsInBurstinSIB1, and X is thenrofPDCCH-MonitoringOccasionPerSSB-InPOif configured or is equal to 1 otherwise. The [x*S+K]thPDCCH MO for PEI in the PEI-O corresponds to the Kthtransmitted SSB, where x=0,1,...,X-1, K=1,2,...,S. The PDCCH MOs for PEI which do not overlap with UL symbols (determined according totdd-UL-DL-ConfigurationCommon) are sequentially numbered from zero starting from the first PDCCH MO for PEI in the PEI-O. In one example, a UE accoriding to implementation chooses R PDCCH monitoring occasions to monitor for its PEI-O, starting from the first PDCCH monitoring occasion in its PEI-O. In another example, the UE monitors R consecutive PDCCH monitoring occasions from the first PDCCH monitoring occasion in its PEI-O. In a third example, ifnrofPDCCH-MonitoringOccasionPerSSB-InPOis configured, the UE selects one SSB from the S transmitted SSBs and monitors min (R, X) PDCCH monitoring occasions among the X PDCCH monitoring occasions of the selected SSB.

[0142] In some embodiments, PDCCH repetition for beam failure recovery (BFR) is provided. In embodiments such as these, for PDCCH repetition for BFR, two search spaces, e.g., the existing search space, which is identified byrecoverySearchSpaceId, and a new SS in the same BWP, (e.g., identified byrecoverySearchSpaceId2), can be linked by a search space linking ID. The UE monitors and / or detects (e.g., combine and decodes) PDCCH for BFR RAR on both SSs.recoverySearchSpaceId2indicates the ID of search space linked to the search space indicated byrecoverySearchSpaceIdfor BFR. The network configures this search space to be within the linked DL BWP (i.e., within the DL BWP with the samebwp-Id) of the UL BWP in which theBeamFailureRecoveryConfigis provided. In some embodiments, this field is present only if a search space linking ID is configured for the search space indicated byrecoverySearchSpaceId, and is absent otherwise.

[0143] For example, in some embodiments, if the contention-free Random Access Preamble for beam failure recovery request was transmitted by the MAC entity, ifrecoverySearchSpaceId2is configured, the UE monitors and / or detects (e.g., combines and decodes) for a PDCCH transmission on the search space indicated byrecoverySearchSpaceIdandrecoverySearchSpaceId2of the SpCell identified by the C-RNTI while ra-ResponseWindow is running. In embodiments such as these, ifrecoverySearchSpaceId2is not configured, the UE monitors for a PDCCH transmission on the search space indicated byrecoverySearchSpaceIdof the SpCell identified by the C-RNTI while ra-ResponseWindow is running.

[0144] In some embodiments, if notification of a reception of a PDCCH transmission on the search space indicated byrecoverySearchSpaceIdorrecoverySearchSpaceId2is received from lower layers on the Serving Cell where the preamble was transmitted, and if PDCCH transmission is addressed to the C-RNTI, and if the contention-free Random Access Preamble for beam failure recovery request was transmitted by the MAC entity, the UE considers the Random Access procedure successfully completed. In some embodiments, Ifra-ResponseWindowconfigured inBeamFailureRecoveryConfigexpires and if a PDCCH transmission neither on the search space indicated byrecoverySearchSpaceIdaddressed to the C-RNTI nor on the search space indicated byrecoverySearchSpaceId2addressed to the C-RNTI has not been received on the Serving Cell where the preamble was transmitted, the UE considers the Random Access Response reception not successful.

[0145] In some embodiments, for beam failure recovery (BFR), if R (e.g., indicating the number of PDCCH monitoring occasions to be monitored repeatedly) is signaled, a UE capable of receiving PDCCH repetitions for BFR monitors and / or detects (e.g., combines and decodes) R PDCCH monitoring occasions on the search space indicated byrecoverySearchSpaceId.

[0146] In some embodiments, PDCCH repetition for Multicast Broadcast Service (MBS) is provided. For PDCCH repetition for MBS MCCH, two common search spaces, (e.g., the existing CSS which is identified bysearchSpaceMCCH (searchSpaceMulticastMCCH), and a new CSS in the same BWP, e.g., identified bysearchSpaceMCCH2 (searchSpaceMulticastMCCH2)), can be linked by a search space linking ID. In embodiments such as these, the UE monitors and / or detects (e.g., combines and decodes) PDCCH for MBS MCCH on both CSSs.searchSpaceMCCH2 (searchSpaceMulticastMCCH2)indicates the ID of search space linked to the search space indicated bysearchSpaceMCCH (searchSpaceMulticastMCCH)for MBS. IfsearchspaceMCCH2(searchSpaceMulticastMCCH2)is set to zero, PDCCH monitoring occasions for MCCH message reception in the MCCH transmission window are the same as PDCCH monitoring occasions forSIB1. IfsearchspaceMCCH2(searchSpaceMulticastMCCH2)is not set to zero, PDCCH monitoring occasions for MCCH message are determined based on search space indicated bysearchspaceMCCH2 (searchSpaceMulticastMCCH2).

[0147] In some embodiments, for PDCCH repetition for MBS MTCH, two common search spaces (e.g., the existing CSS which is identified bysearchSpaceMTCH (searchSpaceMulticastMTCH), and a new CSS in the same BWP, e.g., identified bysearchSpaceMTCH2 (searchSpaceMulticastMTCH2)) can be linked by a search space linking ID. In embodiments such as these, the UE monitors and / or detects (e.g., combine and decodes) the PDCCH for MBS MTCH on both CSSs.searchSpaceMTCH2 (searchSpaceMulticastMTCH2)indicates the ID of search space linked to the search space indicated bysearchSpaceMTCHf(searchSpaceMulticastMTCH)or MBS.

[0148] In some embodiments, PDCCH repetition for Small Data Transmission (SDT) is provided. For PDCCH repetition for SDT, two common search spaces (e.g., the existing CSS which is identified bysdt-SearchSpace, and a new CSS in the same BWP, e.g., identified bysdt-SearchSpace2) can be linked by a search space linking ID. In embodiments such as these, the UE monitors and / or detects (e.g., combines and decodes) the PDCCH for SDT on both CSSs.sdt-SearchSpace2indicates the ID of search space linked to the search space indicated bysdt-SearchSpacefor SDT.

[0149] In some embodiments, a UE capability of supporting the repetition of PDCCH for SIB1, and / or a UE capability of supporting repetition of PDCCH for other SIBs, and / or a UE capability of supporting repetition of PDCCH for Msg2 in RACH procedure, and / or a UE capability of supporting repetition of PDCCH for Msg4 in RACH procedure, and / or a UE capability of supporting repetition of PDCCH for PEI, and / or a UE capability of supporting repetition of PDCCH for paging, and / or a UE capability of supporting repetition of PDCCH for BFR RAR, and / or a UE capability of supporting repetition of PDCCH for MBS MCCH / MTCH, and / or a UE capability of supporting repetition of PDCCH for SDT, can be defined. For example, one or more of these UE capabilities can be signalled per UE or per frequency band or per frequency band combination, differentiated or not differentiated between FDD and TDD system, and / or between FR1 and FR2. As an example, in some embodiments, one or more capabilities can be applicable only if the UE supports an NTN. In another example, in some embodiments, the UE reports one or more capabilities in an RRC message (e.g., a UE capability information message) as a response to a UE capability inquiry sent by the NW.

[0150] In some embodiments, a UE capability of the supported number of repetitions of PDCCH for SIB1, and / or a UE capability of the supported number of repetitions of PDCCH for other SIBs, and / or a UE capability of the supported number of repetitions of PDCCH for Msg2 in RACH procedure, and / or a UE capability of the supported number of repetitions of PDCCH for Msg4 in RACH procedure, and / or a UE capability of the supported number of repetitions of PDCCH for PEI, and / or a UE capability of the supported number of repetitions of PDCCH for paging, and / or a UE capability of the supported number of repetitions of PDCCH for BFR RAR, and / or a UE capability of the supported number of repetitions of PDCCH for MBS MCCH / MTCH, and / or a UE capability of the supported number of repetitions of PDCCH for SDT, can be defined. One or more of these UE capabilities can be signalled per UE or per frequency band or per frequency band combination, differentiated or not differentiated between FDD and TDD system, and / or between FR1 and FR2. As an example, in some embodiments, one or more capabilities can be applicable only if UE supports NTN. In another example, in some embodiments, the UE reports one or more capabilities in an RRC message (e.g., a UE capability information message) as a response to a UE capability inquiry sent by the NW.

[0151] In some embodiments, a UE capability of supporting the repetition of PDSCH for SIB1 (e.g., within the shortest periodicity which can be 20ms), and / or a UE capability of the supported number of repetitions of PDSCH for SIB1 (e.g., within the shortest periodicity which can be 20ms) can be defined. In embodiments such as these, one or more of these UE capabilities can be signalled per UE or per frequency band or per frequency band combination, differentiated or not differentiated between FDD and TDD system, and / or between FR1 and FR2. As an example, in some embodiments, one or more capabilities can be applicable only if UE supports NTN. In another example, The UE reports one or more capabilities in an RRC message (e.g., a UE capability information message) as a response to a UE capability inquiry sent by the NW.

[0152] In some embodiments, in a 4-step Random Access (RA) procedure Msg4, a PDSCH can be transmitted from base station (BS) repeatedly to improve DL coverage. In some embodiments, when a UE performs an RA procedure for initial access to a cell, Message 4 (Msg4) PDSCH repetition is enabled automatically, and a UE capable of receiving Msg4 PDSCH repetitions includes a request / capability indication for Msg4 PDSCH repetition in the Message 3 (Msg3).

[0153] In some embodiments, the NW enables Msg4 PDSCH repetition by transmitting a configuration for Msg4 PDSCH repetition in system information or in UE dedicated signaling (e.g., an RRC message). In embodiments such as these, ff Msg4 PDSCH repetition is enabled, a UE capable of receiving Msg4 PDSCH repetitions includes a request / capability indication for Msg4 PDSCH repetition in the Msg3 when the UE performs an RA procedure. In some embodiments, the configuration of Msg4 PDSCH repetition can be per RACH configuration or per BWP or per Cell in a SIB or in RRC message. In some embodiments, the configuration for PUCCH repetition for Msg4 HARQ-ACK (i.e., a repetition number and a RSRP threshold in SIB19) can be used for Msg4 PDSCH repetition commonly.

[0154] In some embodiments, the configuration of Msg4 PDSCH repetition includes an explicit one-bit enabling indication. Alternatively, the configuration of Msg4 PDSCH repetition can include one or multiple repetition numbers which implicitly indicate the enabling of Msg4 PDSCH repetition. For instance, in some embodiments a bit string of L bits can used to indicate the repetition number. Each bit can indicate a repetition number and at most L repetition numbers can be indicated. The repetition number 1 shall be indicated together with at least one other repetition number. Alternatively, in some embodiments, a list of integers can be enumerated to indicate the repetition number(s).

[0155] In some embodiments, the configuration of Msg4 PDSCH repetition can include one threshold (e.g., an RSRP threshold). In embodiments such as these, the threshold is used to determine whether Msg4 PDSCH repetition is enabled or not. For instance, in some embodiments, if the RSRP of a DL reference signal is smaller than the threshold, Msg4 PDSCH repetition is enabled.

[0156] In some embodiments, the configuration of Msg4 PDSCH repetition can include one or more threshold(s) (e.g., RSRP threshold). In embodiments such as these, each threshold can be mapped to a repetition number. The thresholds are used to determine whether Msg4 PDSCH repetition is enabled or not. For instance, in some embodiments, if the RSRP of a DL reference signal is smaller than a threshold A and threshold A is the smallest among the configured thresholds that is larger than the RSRP of DL reference signal, Msg4 PDSCH repetition is enabled and the repetition number that is mapped to threshold A is used.

[0157] FIG. 4 illustrates an example procedure for 4-step CBRA with a Msg3 including a request / capability for Msg4 PDSCH repetition 400 according to embodiments of the present disclosure. An embodiment of the procedure illustrated in FIG. 4 is for illustration only. One or more of the components illustrated in FIG. 4 may be implemented in specialized circuitry configured to perform the noted functions or one or more of the components may be implemented by one or more processors executing instructions to perform the noted functions. Other embodiments of a procedure for 4-step CBRA with a Msg3 including a request / capability for Msg4 PDSCH repetition could be used without departing from the scope of this disclosure.

[0158] In the example of FIG. 4, the procedure 400 begins at operation 410. At operation 410, a UE 402 receives system information from a gNB 404. The system information includes a configuration for Msg4 PDSCH repetition.

[0159] At operation 420, the UE 402 transmits a Msg1 RA preamble to gNB 404, and at operations 430, the UE 402 receives a Msg2 RAR transmitted from the gNB 404 which includes an UL grant for a Msg3.

[0160] At operation 440, the UE 402 transmits a Msg3 MAC PDU using the UL grant. If Msg4 PDSCH repetition is enabled, if the UE 402 is capable of receiving Msg4 PDSCH repetitions, UE 402 transmits a Msg3 MAC PDU that includes a request / capability for Msg4 PDSCH repetition.

[0161] After transmitting the Msg3, at operation 450, the UE 402 receives a Msg4 transmitted from the BS. Based on the request / capability included in the Msg3, the network may indicate a number of Msg4 PDSCH repetitions and schedule the repeated Msg4 PDSCH transmissions in the DCI carried in the Msg4 PDCCH. If Msg4 PDSCH repetition is indicated / scheduled by the DCI Msg4 PDCCH, the UE receives repeated Msg4 PDSCH accordingly.

[0162] Although FIG. 4 illustrates one example procedure for 4-step CBRA with a Msg3 including a request / capability for Msg4 PDSCH repetition 400, various changes may be made to FIG. 4. For example, while shown as a series of operations, various operations in FIG. 4 could overlap, occur in parallel, occur in a different order, occur any number of times, be omitted, or replaced by other operations.

[0163] FIGS. 5-7 illustrate example MAC subhheaders 500-700 according to embodiments of the present disclosure. The embodiments of MAC subheaders of FIGS. 500-700 are for illustration only. Different embodiments of a MAC subheader could be used without departing from the scope of this disclosure.

[0164] FIG. 5 shows a MAC subheader 500 of a C-RNTI MAC CE where a 1st or 2nd Reserved bit in the MAC subheader is repurposed, denoted as the “U” field.

[0165] FIG. 6 shows a MAC subheader 600 of a UL CCCH / CCCH1 MAC SDU where a reserved bit in the MAC subheader is repurposed, denoted as the “U” field.

[0166] FIG. 7 shows a MAC subheader 700 of a UL CCCH / CCCH1 MAC SDU.

[0167] Although FIGS. 5-7 illustrate examples of MAC subheaders 500-700, various changes may be made to FIGS. 5-7. For example, various changes to reserved bits could be made, etc. according to particular needs.

[0168] In some embodiments, in a 4-step CBRA procedure, a request / capability for Msg4 PDSCH repetition can be included in the Msg3 as follows:

[0169] - If a C-RNTI MAC CE is included in the Msg3 MAC PDU:

[0170] ○ a 1stor 2ndReserved bit in MAC subheader of the C-RNTI MAC CE is repurposed as shown in FIG. 5, where the denoted U field is set to 1 to indicate the request / capability for Msg4 PDSCH repetition; or

[0171] - If a UL CCCH / CCCH1 MAC SDU is included in the Msg3 MAC PDU (a CCCH of size 48 bits and CCCH of size 64 bits are referred to as CCCH and CCCH1, respectively):

[0172] ○ one bit in the UL CCCH / CCCH1 message or one bit within the RRC setup / resume / reestablishment / systemInfo request message included in UL CCCH / CCCH1 message is used to indicate the request / capability for Msg4 PDSCH repetition; or

[0173] ○ a Reserved bit in MAC subheader of UL CCCH / CCCH1 MAC SDU is repurposed as shown in FIG 6., where the denoted U field is set to 1 to indicate the request / capability for Msg4 PDSCH repetition.

[0174] ○ in the MAC subheader for UL CCCH / CCCH1 MAC SDU, as shown in FIG. 7, the LX field is set to 1 and the LCID field is set to a value in Table 1 below. The LCID indicates the request / capability for Msg4 PDSCH repetition, where X1, X2, X3, X4, X5, X6, Z1, Z2, Z3, Z4, Z5, Z6 are integers smaller than 63, Y1, Y2, Y3, Y4, Y5, Y6, W1, W2, W3, W4, W5, W6 are integers between (216+ 328) and (216+ 383). LCID is the Logical Channel Identification (ID) that identifies the logical channel instance of the corresponding MAC SDU or the type of the corresponding MAC CE or padding for the DL-SCH and for the UL-SCH. LX is the LCID extension field that indicates the use of extended LCID space. The size of the LX field is 1 bit. The LX field set to 1 indicates the use of Table 1. Otherwise, an R bit is present instead (i.e., the bit is set to 0).

[0175]

[0176]

[0177] In some embodiments, in a 2-step Random Access (RA) procedure, a MsgB PDSCH can be transmitted from a base station (BS) repeatedly to improve DL coverage. PUCCH repetition for MsgB HARQ-ACK can be considered to improve UL coverage. In some embodiments, when a UE performs a 2-step RA procedure for initial access to a cell, MsgB PDSCH repetition is enabled automatically, and a UE capable of receiving MsgB PDSCH repetitions includes the request / capability indication for MsgB PDSCH repetition in MsgA.

[0178] In some embodiments, the NW enables MsgB PDSCH repetition by transmitting a configuration for Msg4 PDSCH repetition in system information or in UE dedicated signaling (e.g., an RRC message). In embodiments such as these, if MsgB PDSCH repetition is enabled, a UE capable of receiving MsgB PDSCH repetitions includes a request / capability indication for MsgB PDSCH repetition in MsgA when the UE performs an RA procedure. In some embodiments, the configuration of MsgB PDSCH repetition can be per RACH configuration or per BWP or per Cell in SIB or in RRC message. I some embodiments, the configuration for MsgB PDSCH repetition can be used for PUCCH repetition for MsgB HARQ-ACK commonly.

[0179] In some embodiments, the configuration of MsgB PDSCH repetition can include an explicit one-bit enabling indication. Alternatively, in some embodiments, the configuration of MsgB PDSCH repetition can include one or multiple repetition numbers which implicitly indicate the enabling of MsgB PDSCH repetition. For instance, in some embodiments, a bit string of L bits can be used to indicate the repetition number. In examples such as these, each bit can indicate a repetition number and at most L repetition numbers can be indicated. The repetition number 1 shall be indicated together with at least one other repetition number. Alternatively, in some embodiments, a list of integers can be enumerated to indicate the repetition number(s).

[0180] In some embodiments, the configuration of MsgB PDSCH repetition can include one threshold (e.g., an RSRP threshold). In embodiments such as these, the threshold can be used to determine whether MsgB PDSCH repetition is enabled or not. For instance, in some embodiments, if the RSRP of a DL reference signal is smaller than the threshold, MsgB PDSCH repetition is enabled.

[0181] In some embodiments, the configuration of MsgB PDSCH repetition can include one or more threshold(s) (e.g., an RSRP threshold). In embodiments such as these, each threshold can be mapped to a repetition number. In some embodiments, the thresholds are used to determine whether MsgB PDSCH repetition is enabled. For example, in some embodiments, if the RSRP of a DL reference signal is smaller than threshold B and threshold B is the smallest among the configured thresholds that is larger than the RSRP of DL reference signal, MsgB PDSCH repetition is enabled and the repetition number that is mapped to threshold B is used.

[0182] FIG. 8 illustrates an example procedure for 2-step CBRA with MsgB PDSCH repetition 800 according to embodiments of the present disclosure. An embodiment of the procedure illustrated in FIG. 8 is for illustration only. One or more of the components illustrated in FIG. 8 may be implemented in specialized circuitry configured to perform the noted functions or one or more of the components may be implemented by one or more processors executing instructions to perform the noted functions. Other embodiments of a procedure for 2-step CBRA with MsgB PDSCH repetition could be used without departing from the scope of this disclosure.

[0183] In the example of FIG. 8, the procedure 800 begins at operation 810. At operation 810, a UE 802 receives system information from a gNB 804. The system information includes a configuration for MsgB PDSCH repetition.

[0184] At operation 820, the UE 802 transmits a MsgA RA preamble and MsgA PUSCH payload containing a MAC PDU. If MsgB PDSCH repetition is enabled, and UE 802 is capable of receiving MsgB PDSCH repetitions, then UE 802 transmits a MsgA MAC PDU that includes a request / capability indication for MsgB PDSCH repetition.

[0185] At operation 830, after transmitting MsgA, UE802 receives a MsgB including a success RAR. Based on the request / capability included in the MsgA, the network may indicate a number of MsgB PDSCH repetitions and schedule the repeated MsgB PDSCH transmissions in the DCI carried in the MsgB PDCCH. If the MsgB PDSCH repetition is indicated / scheduled by DCI in MsgB PDCCH, the UE receives the repeated MsgB PDSCH transmissions accordingly.

[0186] Although FIG. 8 illustrates one example procedure for 2-step CBRA with MsgB PDSCH repetition800, various changes may be made to FIG. 8. For example, while shown as a series of operations, various operations in FIG. 8 could overlap, occur in parallel, occur in a different order, occur any number of times, be omitted, or replaced by other operations.

[0187] In some embodiments, in a 2-step CBRA procedure, a request / capability for MsgB PDSCH repetition can be included in the MsgA as follows:

[0188] - If a C-RNTI MAC CE is included in the MsgA MAC PDU:

[0189] ○ a Reserved bit in MAC subheader of C-RNTI MAC CE is repurposed as shown in FIG. 5, where the denoted U field is set to 1 to indicate the request / capability for MsgB PDSCH; or

[0190] - If a UL CCCH / CCCH1 MAC SDU is included in the MsgA MAC PDU (a CCCH of size 48 bits and CCCH of size 64 bits are referred to as CCCH and CCCH1, respectively):

[0191] ○ one bit in UL CCCH / CCCH1 message or one bit within the RRC setup / resume / reestablishment / system-Info request message included in UL CCCH / CCCH1 message is used to indicate the request / capability for MsgB PDSCH repetition; or

[0192] ○ a Reserved bit in MAC subheader of UL CCCH / CCCH1 MAC SDU is repurposed as shown in FIG. 6, where the denoted U field is set to 1 to indicate the request / capability for MsgB PDSCH repetition; or

[0193] ○ in the MAC subheader for UL CCCH / CCCH1 MAC SDU, as shown in FIG 7, the LX field is set to 1 and the LCID field is set to a value in the Table 2 below. The LCID indicates the request / capability for MsgB PDSCH repetition, where x1, x2, x3, x4, x5, x6, z1, z2, z3, z4, z5, z6, u1, u2, u3, u4, u5, u6 are integers smaller than 63, y1, y2, y3, y4, y5, y6, w1, w2, w3, w4, w5, w6, v1, v2, v3, v4, v5, v6 are integers between (216+ 328) and (216+ 383). LCID is the Logical Channel ID that identifies the logical channel instance of the corresponding MAC SDU or the type of the corresponding MAC CE or padding for the DL-SCH and for the UL-SCH. LX is the LCID extension field that indicates the use of extended LCID space. The size of the LX field is 1 bit. The LX field set to 1 indicates the use of Table 2. Otherwise, an R bit is present instead (i.e., the bit is set to 0).

[0194]

[0195]

[0196] FIG. 9 illustrates an example procedure for Fallback CBRA with Msg4 PDSCH repetition 900 according to embodiments of the present disclosure. An embodiment of the procedure illustrated in FIG. 9 is for illustration only. One or more of the components illustrated in FIG. 9 may be implemented in specialized circuitry configured to perform the noted functions or one or more of the components may be implemented by one or more processors executing instructions to perform the noted functions. Other embodiments of a procedure for Fallback CBRA with Msg4 PDSCH repetition could be used without departing from the scope of this disclosure.

[0197] In the example of FIG. 9, the procedure 900 begins at operation 910. At operation 910, a UE 902 receives system information from a gNB 904. The system information includes a configuration for Msg4 / MsgB PDSCH repetition.

[0198] At operation 920, UE transmits a MsgA RA preamble and MsgA PUSCH payload containing the MAC PDU. If MsgB PDSCH repetition is enabled, and UE 902 is capable of receiving MsgB PDSCH repetitions, then UE 902 transmits a MsgA MAC PDU that includes a request / capability indication for MsgB PDSCH repetition.

[0199] After transmitting the MsgA, the UE 902 receives a MsgB transmitted from the gNB 904. If UE 902 receives a fallback RAR in MsgB at operation 930, then UE 902 transmits a Msg3 MAC PDU using the UL grant included in the fallback RAR.

[0200] At operation 940, If Msg4 PDSCH repetition is enabled, and UE 902 is capable of receiving Msg4 PDSCH repetitions, UE 902 transmits a Msg3 MAC PDU that includes a request / capability for Msg4 PDSCH repetition. After transmitting the Msg3, at operation 950 the UE 902 receives a Msg4 transmitted from the gNB 904. Based on the request / capability included in the Msg3, the network may indicate a number of Msg4 PDSCH repetitions and schedule the repeated Msg4 PDSCH transmissions in the DCI carried in Msg4 PDCCH. If Msg4 PDSCH repetition is indicated / scheduled by DCI in Msg4 PDCCH, UE receives repeated Msg4 PDSCH accordingly.

[0201] Although FIG. 9 illustrates one example procedure for Fallback CBRA with Msg4 PDSCH repetition 900, various changes may be made to FIG. 9. For example, while shown as a series of operations, various operations in FIG. 9 could overlap, occur in parallel, occur in a different order, occur any number of times, be omitted, or replaced by other operations.

[0202] In some embodiments, the LCID in the MAC subheader for a UL CCCH / CCCH1 MAC SDU included in the Msg3 MAC PDU is used to indicate the request / capability for Msg4 PDSCH repetition. In embodiments such as these, when the NW configures both Msg4 PDSCH repetition and PUCCH repetition for Msg4 HARQ-ACK, one of a request / capability for Msg4 PDSCH repetition only, or a request / capability for PUCCH repetition for Msg4 HARQ-ACK only, or a request / capability for both Msg4 PDSCH repetition and PUCCH repetition for Msg4 HARQ-ACK can be transmitted in Msg3. In some embodiments, PUCCH repetition for Msg4 HARQ-ACK is enabled ifnumberOfMsg4HARQ-ACK-Repetitionsis configured andrsrp-ThresholdMsg4HARQ-ACKis not configured, or if both are configured and the RSRP of the downlink pathloss reference is less thanrsrp-ThresholdMsg4HARQ-ACK.

[0203] In some embodiments, for a UE capable of Msg4 PDSCH repetition and / or capable of PUCCH repetition for Msg4 HARQ-ACK, if Msg4 PDSCH repetition is enabled and PUCCH repetition for Msg4 HARQ-ACK is enabled, and if the UE is capable of both Msg4 PDSCH repetition and PUCCH repetition for Msg4 HARQ-ACK, the UE transmits a Msg3 MAC PDU that includes a request / capability for both Msg4 PDSCH repetition and PUCCH repetition for Msg4 HARQ-ACK. In circumstances such as these, the MAC entity uses one of the codepoints among Z1, Z2, Z3, Z4, Z5, Z6 in Table 1 for the LCID field in the MAC subheader for UL CCCH / CCCH1 MAC SDU included in the Msg3 MAC PDU. Otherwise, if Msg4 PDSCH repetition is enabled and if the UE is capable of Msg4 PDSCH repetition, the UE transmits a Msg3 MAC PDU that includes a request / capability for Msg4 PDSCH repetition only. In circumstances such as these, the MAC entity uses one of the codepoints among X1, X2, X3, X4, X5, X6 (or among Z1, Z2, Z3, Z4, Z5, Z6) in Table 1 for the LCID field in the MAC subheader for UL CCCH / CCCH1 MAC SDU included in the Msg3 MAC PDU. Otherwise, if PUCCH repetition for Msg4 HARQ-ACK is enabled and if the UE is capable of PUCCH repetition for Msg4 HARQ-ACK, the UE transmits a Msg3 MAC PDU that includes a request / capability for PUCCH repetition for Msg4 HARQ-ACK only. In circumstances such as these, the MAC entity uses one of the codepoints among 2, 3, 4, 5, 6, 7 (or among Z1, Z2, Z3, Z4, Z5, Z6) in Table 1 for the LCID field in the MAC subheader for UL CCCH / CCCH1 MAC SDU included in the Msg3 MAC PDU.

[0204] In some embodiments, for a UE capable of Msg4 PDSCH repetition and / or capable of PUCCH repetition for Msg4 HARQ-ACK, if Msg4 PDSCH repetition is enabled and if the UE is capable of Msg4 PDSCH repetition, the UE transmits a Msg3 MAC PDU that includes a request / capability for Msg4 PDSCH repetition only. In circumstances such as these, the MAC entity uses one of the codepoints among 2, 3, 4, 5, 6, 7 in Table 1 for the LCID field in the MAC subheader for UL CCCH / CCCH1 MAC SDU included in the Msg3 MAC PDU. Otherwise, if PUCCH repetition for Msg4 HARQ-ACK is enabled and if the UE is capable of PUCCH repetition for Msg4 HARQ-ACK, the UE transmits a Msg3 MAC PDU that includes a request / capability for PUCCH repetition for Msg4 HARQ-ACK only. In circumstances such as these, the MAC entity uses one of the codepoints among 2, 3, 4, 5, 6, 7 in Table 1 for the LCID field in the MAC subheader for UL CCCH / CCCH1 MAC SDU included in the Msg3 MAC PDU.

[0205] In some embodiments, the LCID in the MAC subheader for UL CCCH / CCCH1 MAC SDU included in the MsgA MAC PDU is used to indicate the request / capability for MsgB PDSCH repetition. In embodiments such as these, when the NW configures both MsgB PDSCH repetition and PUCCH repetition for MsgB HARQ-ACK, one of a request / capability for MsgB PDSCH repetition only, or a request / capability for PUCCH repetition for MsgB HARQ-ACK only, or a request / capability for both MsgB PDSCH repetition and PUCCH repetition for MsgB HARQ-ACK can be transmitted in MsgA. In some embodiments, PUCCH repetition for MsgB HARQ-ACK can be enabled by a configuration in a SIB or in a dedicated RRC message. In some embodiments, if a repetition number is configured, or if an explicit enabling indication is configured, or if a RSRP threshold is configured and the RSRP of the downlink pathloss reference is less than the RSRP threshold, or if both a repetition number is and a RSRP threshold are configured and the RSRP of the downlink pathloss reference is less than the RSRP threshold, PUCCH repetition for MsgB HARQ-ACKis considered enabled.

[0206] In some embodiments, for a UE capable of MsgB PDSCH repetition and / or capable of PUCCH repetition for MsgB HARQ-ACK, if MsgB PDSCH repetition is enabled and PUCCH repetition for MsgB HARQ-ACK is enabled and if the UE is capable of both MsgB PDSCH repetition and PUCCH repetition for MsgB HARQ-ACK, the UE transmits a MsgA MAC PDU that includes a request / capability for both MsgB PDSCH repetition and PUCCH repetition for MsgB HARQ-ACK. In circumstances such as these, the MAC entity uses one of the codepoints among z1, z2, z3, z4, z5, z6 in Table 2 for the LCID field in the MAC subheader for UL CCCH / CCCH1 MAC SDU included in the MsgA MAC PDU. Otherwise, if MsgB PDSCH repetition is enabled and if the UE is capable of MsgB PDSCH repetition, the UE transmits a MsgA MAC PDU that includes a request / capability for MsgB PDSCH repetition only. In circumstances such as these, the MAC entity uses one of the codepoints among x1, x2, x3, x4, x5, x6 (or among z1, z2, z3, z4, z5, z6) in Table 2 for the LCID field in the MAC subheader for UL CCCH / CCCH1 MAC SDU included in the MsgA MAC PDU. Otherwisse, if PUCCH repetition for MsgB HARQ-ACK is enabled and if the UE is capable of PUCCH repetition for MsgB HARQ-ACK, the UE transmits a MsgA MAC PDU that includes a request / capability for PUCCH repetition for MsgB HARQ-ACK only. In circumstances such as these, the MAC entity uses one of the codepoints among u1, u2, u3, u4, u5, u6 (or among z1, z2, z3, z4, z5, z6) in Table 2 for the LCID field in the MAC subheader for UL CCCH / CCCH1 MAC SDU included in the MsgB MAC PDU.

[0207] In some embodiments, for a UE capable of MsgB PDSCH repetition and / or capable of PUCCH repetition for MsgB HARQ-ACK, if MsgB PDSCH repetition is enabled and if the UE is capable of MsgB PDSCH repetition, the UE transmits a MsgA MAC PDU that includes a request / capability for MsgB PDSCH repetition and PUCCH repetition for MsgB HARQ-ACK. In circumstance such as these, the MAC entity uses one of the codepoints among u1, u2, u3, u4, u5, u6 in Table 2 for the LCID field in the MAC subheader for UL CCCH / CCCH1 MAC SDU included in the MsgA MAC PDU. Otherwise, if PUCCH repetition for MsgB HARQ-ACK is enabled and if the UE is capable of PUCCH repetition for MsgB HARQ-ACK, the UE transmits a MsgA MAC PDU that includes a request / capability for PUCCH repetition for MsgB HARQ-ACK. In circumstances such as these, the MAC entity uses one of the codepoints among u1, u2, u3, u4, u5, u6 in Table 2 for the LCID field in the MAC subheader for UL CCCH / CCCH1 MAC SDU included in the MsgA MAC PDU.

[0208] In some embodiments, for PDCCH repetition for Msg2 in an RA procedure, the NW transmits an enabling indication and / or configuration. In embodiments such as these, the enabling indication and / or configuration can be pre-defined and / or transmitted in system information (e.g., MIB or SIB1) and / or in UE dedicated RRC signalling. In some embodiments, the enabling indication can be explicitly indicated by a one-bit RRC parameter or implicitly indicated by the PDCCH repetition configuration. In embodiments such as these, the UE receives the PDCCH repetition enabling indication and / or configuration. Accordingly, the UE monitors PDCCH repeatedly, and combines and decodes the received PDCCH repetitions.

[0209] In some embodiments, the configuration for PDCCH repetition for Msg2 can include a repetition number N1, which indicates the number of PDCCH repetitions. In embodiments such as these, the configuration can implicitly indicate the enabling of PDCCH repetition for Msg2. The repetition number N1 can indicate the number of PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) to be monitored, combined and decoded. For example, in some embodiments, N1 can be a fixed value signaled by the NW. In another example, in some embodiments, the value of N1 can depend on the RSRP of a DL RS from the current serving cell the UE is camped on. The mapping between the value of N and the value of RSRP can be signaled. A larger value of RSRP can be mapped to a smaller value of N1.

[0210] In some embodiments, if N1 (e.g., indicating the number of PDCCH repetitions to be monitored / combined / decoded for Msg2) is signaled, a UE capable of supporting Msg2 PDCCH repetitions monitors and / or combines and / or decodes N1 PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) on the search space indicated byra-SearchSpace.

[0211] In some embodiments, the NW transmits multiple PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) for Msg2 as configured by a RA search space. In embodiments such as these, the PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) configured by the RA search space are grouped in the RAR window. Each group includes N1 PDCCH monitoring occasions (or PDCCH subframes / slots / symbols). Within a group, the UE can monitor and combine one or more or all N1 monitoring occasions (or PDCCH subframes / slots / symbols) and decode PDCCH to receive RAR. In some embodiments, the UE monitors the next group only if the RAR is not successfully received based on PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) from the previous group.

[0212] In some embodiments, the NW transmits one or multiple PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) for Msg2 as configured by RA search space. In embodiments such as these, in a RAR window the UE monitors a PDCCH occasion / subframe / slot / symbol as configured by RA search space, and considers it as the first PDCCH repetition. The UE then determines N1-1 additional PDCCH occasions / subframes / slots / symbols as the N1-1 PDCCH repetitions. Some embodiments, the additional N1-1 PDCCH repetitions start from the end of the first PDCCH repetition. The N1-1 PDCCH occasions / subframes / slots / symbols occur one after another in time without any gap between each two. In some embodiments, a time offset can be configured, which can be in units of a symbol / slot / subframe or in a time unit (e.g., millisecond, second, etc.). The additional N1-1 PDCCH repetitions start from the end of the first PDCCH repetition. The N1-1 PDCCH occasions / subframes / slots / symbols occur one after another in time with a gap of the configured offset between each two. In some embodiments, for the N1 PDCCH repetitions, the UE can combine one or more or all N1 repetitions (one indicated by RAR search space and N1-1 implicitly indicated) and decode PDCCH for Msg2.

[0213] In some embodiments, for PDCCH repetition for Msg4 in an RA procedure, the NW transmits an enabling indication and / or configuration. In embodiments such as these, the enabling indication and / or configuration can be pre-defined and / or transmitted in system information (e.g., MIB or SIB1) and / or in UE dedicated RRC signalling. The enabling indication can be explicitly indicated by a one-bit RRC parameter or implicitly indicated by the PDCCH repetition configuration. The UE receives the PDCCH repetition enabling indication and / or configuration. Accordingly, the UE monitors PDCCH repeatedly, and combines and decodes the received PDCCH repetitions.

[0214] In some embodiments, the configuration for PDCCH repetition for Msg4 can include a repetition number N2, which indicates the number of PDCCH repetitions. In embodiments such as these, the configuration can implicitly indicate the enabling of PDCCH repetition for Msg4. The repetition number N2 can indicate the number of PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) to be monitored, combined and decoded. For example, in some embodiments, N2 can be a fixed value signaled by the NW. In another example, In some embodiments, the value of N2 can depend on the RSRP of a DL RS from the current serving cell the UE is camped on. The mapping between the value of N2 and the value of RSRP can be signaled. A larger value of RSRP can be mapped to a smaller value of N2.

[0215] In some embodiments, if N2 (e.g., indicating the number of PDCCH repetitions to be monitored / combined / decoded for Msg4) is signaled, a UE capable of supporting Msg4 PDCCH repetitions monitors and / or combines and / or decodes N2 PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) on the search space indicated byra-SearchSpace.

[0216] In some embodiments, the NW transmits multiple PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) for Msg4 as configured by RA search space. In embodiments such as these, PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) configured by the RA search space are grouped in the contention resolution window. Each group includes N2 PDCCH monitoring occasions (or PDCCH subframes / slots / symbols). Within a group, the UE can monitor and combine one or more or all N2 monitoring occasions (or PDCCH subframes / slots / symbols) and decode PDCCH to receive Msg4. In some embodiments, the UE monitors the next group only if Msg4 PDCCH is not successfully received based on PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) from the previous group.

[0217] In some embodiments, the NW transmits one or multiple PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) for Msg4 as configured by RA search space. In embodiments such as these, in the contention resolution window the UE monitors a PDCCH occasion / subframe / slot / symbol as configured by RA search space, and considers it as the first PDCCH repetition for Msg4. The UE then determines N2-1 additional PDCCH occasions / subframes / slots / symbols as the N2-1 PDCCH repetitions. For example, in some embodiments, the additional N2-1 PDCCH repetitions start from the end of the first PDCCH repetition. In embodiments such as these, the N2-1 PDCCH occasions / subframes / slots / symbols occur one after another in time without any gap between each two. In another example, in some embodiments, a time offset can be configured, which can be in units of a symbol / slot / subframe or in a time unit (e.g., millisecond, second, etc.). In embodiments such as these, the additional N2-1 PDCCH repetitions start from the end of the first PDCCH repetition for Msg4. The N2-1 PDCCH occasions / subframes / slots / symbols occur one after another in time with a gap of the configured offset between each two. For the N2 PDCCH repetitions, the UE can combine one or more or all N2 repetitions (one indicated by RAR search space and N2-1 implicitly indicated) and decode the PDCCH for Msg4.

[0218] In some embodiments, for PDCCH repetition for other system information than SIB1 (OSI), the NW transmits an enabling indication and / or configuration. In embodiments such as these, the enabling indication and / or configuration can be pre-defined and / or transmitted in system information (e.g., a MIB or SIB1) and / or in UE dedicated RRC signalling. The enabling indication can be explicitly indicated by a one-bit RRC parameter or implicitly indicated by the PDCCH repetition configuration. The UE receives the PDCCH repetition enabling indication and / or configuration. Accordingly, the UE monitors PDCCH repeatedly, and combines and decodes the received PDCCH repetitions.

[0219] In some embodiments, the configuration for PDCCH repetition for OSI can include a repetition number N3, which indicates the number of PDCCH repetitions. In embodiments such as these, the configuration can implicitly indicate the enabling of PDCCH repetition for OSI. The repetition number N3 can indicate the number of PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) to be monitored, combined and decoded. For example, in some embodiments, N3 can be a fixed value signaled by the NW. In another example, in some embodiments, the value of N3 can depend on the RSRP of a DL RS from the current serving cell the UE is camped on. The mapping between the value of N3 and the value of RSRP can be signaled. A larger value of RSRP can be mapped to a smaller value of N3.

[0220] In some embodiments, if N3 (e.g., indicating the number of PDCCH repetitions to be monitored / combined / decoded for OSI) is signaled, a UE capable of supporting OSI PDCCH repetitions monitors and / or combines and / or decodes N3 PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) on the search space for OSI.

[0221] In some embodiments, the NW transmits multiple PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) for OSI as configured by OSI search space in an SI-window. The PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) configured by the OSI search space are grouped in the SI-window. Each group includes N3 PDCCH monitoring occasions (or PDCCH subframes / slots / symbols). Within a group, UE can monitor and combine one or more or all N3 monitoring occasions (or PDCCH subframes / slots / symbols) and decode PDCCH to receive the OSI. In some embodiments, the UE monitors the next group only if OSI PDCCH is not successfully received based on PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) from the previous group.

[0222] In some embodiments, the NW transmits multiple PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) for OSI as configured by OSI search space in an SI-window. I embodiments such as these, the UE can monitor and combine one or more or N3 consecutive monitoring occasions (or PDCCH subframes / slots / symbols) from the start of an SI-window, and decode PDCCH to receive the OSI.

[0223] In some embodiments, the NW transmits one or multiple PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) for OSI as configured by OSI search space. In embodiments such as these, in an SI-window the UE monitors a PDCCH occasion / subframe / slot / symbol as configured by OSI search space, and considers it as the first PDCCH repetition for OSI. The UE then determines N3-1 additional PDCCH occasions / subframes / slots / symbols as the N3-1 PDCCH repetitions. For example, in some embodiments, the additional N3-1 PDCCH repetitions start from the end of the first PDCCH repetition. The N3-1 PDCCH occasions / subframes / slots / symbols occur one after another in time without any gap between each two. In another example, in some embodiments, a time offset can be configured, which can be in units of a symbol / slot / subframe or in a time unit (e.g., millisecond, second, etc.). The additional N3-1 PDCCH repetitions start from the end of the first PDCCH repetition for OSI. The N3-1 PDCCH occasions / subframes / slots / symbols occur one after another in time with a gap of the configured offset between each two. For the N3 PDCCH repetitions, the UE can combine one or more or all N3 repetitions (one indicated by OSI search space and N3-1 implicitly indicated) and decode PDCCH for OSI.

[0224] In some embodiments, for PDCCH repetition for paging, the NW transmits an enabling indication and / or configuration. In embodiments such as these, the enabling indication and / or configuration can be pre-defined and / or transmitted in system information (e.g., a MIB or SIB1) and / or in UE dedicated RRC signalling. The enabling indication can be explicitly indicated by a one-bit RRC parameter or implicitly indicated by the PDCCH repetition configuration. The UE receives the PDCCH repetition enabling indication and / or configuration. Accordingly, the UE monitors PDCCH repeatedly, and combines and decodes the received PDCCH repetitions.

[0225] In some embodiments, the configuration for PDCCH repetition for paging can include a repetition number R, which indicates the number of PDCCH repetitions. In embodiments such as these, the configuration can implicitly indicate the enabling of PDCCH repetition for paging. In some embodiments, the repetition number R can indicate the number of PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) to be monitored, combined and decoded. For example, in some embodiments, R can be a fixed value signaled by the NW. In another example, in some embodiments, the value of R depends on the RSRP of a DL RS from the current serving cell the UE is camped on. The mapping between the value of R and the value of RSRP can be signaled. A larger value of RSRP can be mapped to a smaller value of R.

[0226] In some embodiments, for paging, the UE monitors one paging occasion (PO) per DRX cycle. A PO is a set of PDCCH monitoring occasions and can include multiple time slots (e.g., subframe or OFDM symbol) where paging DCI can be sent. One Paging Frame (PF) is one Radio Frame and may contain one or multiple PO(s) or starting point of a PO. The PF and PO for paging are determined by the following formulas: SFN for the PF is determined by (SFN + PF_offset) mod T = (T div N)*(UE_ID mod N); Index (i_s), indicating the index of the PO UE is required to monitor, is determined by i_s = floor (UE_ID / N) mod Ns.

[0227] In some embodiments, if R (e.g., indicating the number of PDCCH repetition for paging) is signaled, a UE capable of receiving PDCCH repetitions for paging monitors and / or detects (e.g., combines and decodes) R PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) for the same PO as configured by the search space for paging. A PO is a set of 'S*X ' consecutive PDCCH monitoring occasions where 'S' is the number of actual transmitted SSBs determined according tossb-PositionsInBurstinSIB1and X is thenrofPDCCH-MonitoringOccasionPerSSB-InPOif configured or is equal to 1 otherwise. The [x*S+K]thPDCCH monitoring occasion for paging in the PO corresponds to the Kthtransmitted SSB, where x=0,1,...,X-1, K=1,2,...,S. The PDCCH monitoring occasions for paging which do not overlap with UL symbols (determined according totdd-UL-DL-ConfigurationCommon) are sequentially numbered from zero starting from the first PDCCH monitoring occasion for paging in the PF. WhenfirstPDCCH-MonitoringOccasionOfPOis present, the starting PDCCH monitoring occasion number of (i_s + 1)thPO is the (i_s + 1)thvalue of thefirstPDCCH-MonitoringOccasionOfPOparameter; otherwise, it is equal to i_s * S*X.

[0228] In some embodiments, in case of X equals 1, for each PDCCH monitoring occasion / subframe / slot / symbol associated to an SSB, R-1 additional PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) are implicitly determined associated to the same SSB. In embodiments such as these, in a PO, the UE monitors a PDCCH occasion / subframe / slot / symbol associated to an SSB as configured by paging search space, and considers it as the first PDCCH repetition for paging. The UE then determines R-1 additional PDCCH occasions / subframes / slots / symbols as the R-1 PDCCH repetitions associated to the same SSB. For example, in some embodiments, the additional R-1 PDCCH repetitions start from the end of the first PDCCH repetition. The R-1 PDCCH occasions / subframes / slots / symbols occur one after another in time without any gap between each two. In another example, in some embodiments, a time offset can be configured, which can be in units of a symbol / slot / subframe or in time units (e.g., millisecond, second, etc.). The additional R-1 PDCCH repetitions start from the end of the first PDCCH repetition for paging. The R-1 PDCCH occasions / subframes / slots / symbols occur one after another in time with a gap of the configured offset between each two. For the R PDCCH repetitions, the UE can combine one or more or all R repetitions (one indicated by paging search space and R-1 implicitly indicated) and decode PDCCH for paging.

[0229] In some embodiments, in case of X larger than 1 (e.g., X can equal to R), the NW can configure a new paging search space with PDDCH repetition. In embodiments such as these, R can be configured in the new paging search space with PDDCH repetition. A UE supporting PDDCH repetition for paging receives PDCCH repetitions for paging according to the new paging search space. The UE monitors min (R, X) PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) among all PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) associated to an SSB. The first PDDCH repetition starts from the first PDCCH monitoring occasion (or PDCCH subframe / slot / symbol) in its PO, which is the (i_s + 1)thPO in a PF. For the R PDCCH repetitions, the UE can combine one or more or all R repetitions (one indicated by paging search space and R-1 implicitly indicated) and decode PDCCH for paging. If X > 1 and if R is not configured, the UE monitors PDCCH according to the paging search space without PDDCH repetition, when the UE detects a PDCCH transmission addressed to P-RNTI within its PO, the UE is not required to monitor the subsequent PDCCH monitoring occasions for this PO.

[0230] In some embodiments, for PDCCH repetition for PEI, the NW transmits an enabling indication and / or configuration. In embodiments such as these, the enabling indication and / or configuration can be pre-defined and / or transmitted in system information (e.g., a MIB or SIB1) and / or in UE dedicated RRC signalling. In some embodiments, the enabling indication can be explicitly indicated by a one-bit RRC parameter or implicitly indicated by the PDCCH repetition configuration. The UE receives the PDCCH repetition enabling indication and / or configuration. Accordingly, the UE monitors PDCCH repeatedly, and combines and decodes the received PDCCH repetitions.

[0231] In some embodiments, the configuration for PDCCH repetition for PEI can include a repetition number Q, which indicates the number of PDCCH repetitions. In embodiments such as these, the configuration can implicitly indicate the enabling of PDCCH repetition for paging. In some embodiments, the repetition number Q can indicate the number of PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) to be monitored, combined and decoded. In some embodiments, Q is a fixed value signaled by the NW. In some embodiments, the value of Q depends on the RSRP of a DL RS from the current serving cell the UE is camped on. The mapping between the value of Q and the value of RSRP can be signaled. A larger value of RSRP can be mapped to a smaller value of Q.

[0232] I some embodiments, for PEI, the UE monitors one PEI occasion per DRX cycle. A PEI occasion (PEI-O) is a set of PDCCH monitoring occasions (MOs) and can include multiple time slots (e.g., subframes or OFDM symbols) where PEI can be sent. In some embodiments, in multi-beam operations, the UE assumes that the same PEI is repeated in all transmitted beams and thus the selection of the beam(s) for the reception of the PEI is up to UE implementation. The time location of PEI-O for UE's PO is determined by a reference point and an offset. The reference point is the start of a reference frame determined by a frame-level offset from the start of the first PF of the PF(s) associated with the PEI-O, provided bypei-FrameOffsetin SIB1. The offset is a symbol-level offset from the reference point to the start of the first PDCCH MO of this PEI-O, provided byfirstPDCCH-MonitoringOccasionOfPEI-Oin SIB1.

[0233] In some embodiments, if Q (e.g., indicating the number of PDCCH repetition for PEI) is signaled, a UE capable of receiving PDCCH repetitions for PEI monitors and / or detects (e.g., combines and decodes) Q PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) for its PEI-O. In embodiments such as these, if Q is not configured, when the UE detects a PEI within its PEI-O, the UE is not required to monitor and / or detects (e.g., combine and decodes) the subsequent MO(s) associated with the same PEI-O. A PEI occasion is a set of 'S*X' consecutive PDCCH MOs, where 'S' is the number of actual transmitted SSBs determined according tossb-PositionsInBurstinSIB1, and X is thenrofPDCCH-MonitoringOccasionPerSSB-InPOif configured or is equal to 1 otherwise. The [x*S+K]thPDCCH MO for PEI in the PEI-O corresponds to the Kthtransmitted SSB, where x=0,1,...,X-1, K=1,2,...,S. The PDCCH MOs for PEI which do not overlap with UL symbols (determined according totdd-UL-DL-ConfigurationCommon) are sequentially numbered from zero starting from the first PDCCH MO for PEI in the PEI-O.

[0234] In some embodiments, in a case of X equals 1, for each PDCCH monitoring occasion / subframe / slot / symbol associated to an SSB, Q-1 additional PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) are implicitly determined associated to the same SSB. In a PEI-O, a UE monitors a PDCCH occasion / subframe / slot / symbol associated to an SSB as configured by PEI search space, and considers it as the first PDCCH repetition for PEI. The UE then determines Q-1 additional PDCCH occasions / subframes / slots / symbols as the Q-1 PDCCH repetitions associated to the same SSB. For example, in some embodiments, the additional Q-1 PDCCH repetitions start from the end of the first PDCCH repetition. The Q-1 PDCCH occasions / subframes / slots / symbols occur one after another in time without any gap between each two. In another example, in some embodiments, a time offset can be configured, which can be in units of a symbol / slot / subframe or in a time unit (e.g., millisecond, second, etc.). The additional Q-1 PDCCH repetitions start from the end of the first PDCCH repetition. The Q-1 PDCCH occasions / subframes / slots / symbols occur one after another in time with a gap of the configured offset between each two. For the Q PDCCH repetitions, the UE can combine one or more or all Q repetitions (one indicated by PEI search space and Q-1 implicitly indicated) and decode PDCCH for PEI.

[0235] In some embodiments, in case of X larger than 1 (e.g., X can equal to Q), the NW can configure a new PEI search space with PDDCH repetition. In embodiments such as these, Q can be configured in the new PEI search space with PDDCH repetition. A UE supporting PDDCH repetition for PEI receives PDCCH repetitions for PEI according to the new paging search space. The UE monitors min (Q, X) PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) among all PDCCH monitoring occasions (or PDCCH subframes / slots / symbols) associated to an SSB. The first PDDCH repetition starts from the first PDCCH monitoring occasion (or PDCCH subframe / slot / symbol) in its PEI-O. For the Q PDCCH repetitions, the UE can combine one or more or all Q repetitions (one indicated by PEI search space and Q-1 implicitly indicated) and decode PDCCH for PEI. If X > 1 and if Q is not configured, the UE monitors PDCCH according to the PEI search space without PDDCH repetition, when the UE successfully received a PDCCH within its PEI-O, the UE is not required to monitor the subsequent PDCCH monitoring occasions for this PEI-O.

[0236] In some embodiments, for RRC connection reestablishment, TN to NTN reestablishment can be supported. In embodiments such as these, the NW can indicate an enabling indication for TN to NTN RRC connection re-establishment, for example, in UE dedicated signalling or in SI of current cell or in SIB1 of the selected cell for RRC reestablishment. The UE can select an NTN cell for RRC connection reestablishment, if the UE has NTN-specific assistance information acquired from current cell and / or if TN to NTN RRC connection re-establishment is enabled and / or if UE supports TN to NTN RRC connection reestablishment.

[0237] FIG. 10 illustrates an example method for repetition for downlink coverage enhancement 1000 according to embodiments of the present disclosure. An embodiment of the method illustrated in FIG. 10 is for illustration only. One or more of the components illustrated in FIG. 10 may be implemented in specialized circuitry configured to perform the noted functions or one or more of the components may be implemented by one or more processors executing instructions to perform the noted functions. Other embodiments of a method for repetition for downlink coverage enhancement could be used without departing from the scope of this disclosure.

[0238] In the example of FIG. 10, the method 1000 begins at step 1010. At step 1010, a UE (such as UE 116 of FIG. 1) receives, from a BS (such as gNB 102 of FIG. 1), system information including configuration information associated with Msg4 PDSCH repetition.

[0239] At step 1020, during a four-step random access procedure, the UE transmits, to the BS, a Msg3 including an indication that the UE supports Msg4 PDSCH repetition.

[0240] At step 1030, during the four-step random access procedure, in response to transmission of the Msg3, the UE (i) receives DCI scheduling a Msg4 PDSCH repetition, and (ii) repeatedly receives a Msg4 PDSCH scheduled by the DCI.

[0241] In some embodiments, the configuration information associated with Msg4 PDSCH repetition may indicate that Msg4 PDSCH repetition is enabled, and the indication that the UE supports Msg4 PDSCH repetition may be included in the Msg3 in response to the information associated with the Msg4 PDSCH repetition indicating that Msg4 PDSCH repetition is enabled.

[0242] In some embodiments, the configuration information associated with Msg4 PDSCH repetition may be per bandwidth part (BWP).

[0243] In some embodiments, the configuration information associated with Msg4 PDSCH repetition may indicate a number of repetitions.

[0244] In some embodiments, the Msg3 may include an uplink CCCH message identified by an LCID.

[0245] In some embodiments, the LCID may indicate that the UE supports the Msg4 PDSCH repetition.

[0246] In some embodiments, the LCID may indicate at least one of: CCCH of size 48 bits for PDSCH repetition of Msg4, except for a reduced capability (RedCap) or enhanced (eRedCap) UE; CCCH of size 64 bits for PDSCH repetition of Msg4, except for a RedCap or eRedCap UE; CCCH of size 48 bits for PDSCH repetition of Msg4 of a RedCap UE; CCCH of size 64 bits for PDSCH repetition of Msg4 of a RedCap UE; CCCH of size 48 bits for PDSCH repetition of Msg4 of an eRedCap UE; CCCH of size 64 bits for PDSCH repetition of Msg4 of an eRedCap UE; CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK and PDSCH repetition of Msg4, except for except for a RedCap or eRedCap UE; CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK and PDSCH repetition of Msg4, except for a RedCap or eRedCap UE; CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK and PDSCH repetition of Msg4 of a RedCap UE; CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK and PDSCH repetition of Msg4 of a RedCap UE; CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK and PDSCH repetition of Msg4 of an eRedCap UE; and CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK and PDSCH repetition of Msg4 of an eRedCap UE.

[0247] Although FIG. 10 illustrates one example method for repetition for downlink coverage enhancement 1000, various changes may be made to FIG. 10. For example, while shown as a series of steps, various steps in FIG. 10 could overlap, occur in parallel, occur in a different order, occur any number of times, be omitted, or replaced by other steps.

[0248] FIG. 11 illustrates another example method for repetition for downlink coverage enhancement 1100 according to embodiments of the present disclosure. An embodiment of the method illustrated in FIG. 11 is for illustration only. One or more of the components illustrated in FIG. 11 may be implemented in specialized circuitry configured to perform the noted functions or one or more of the components may be implemented by one or more processors executing instructions to perform the noted functions. Other embodiments of a method for repetition for downlink coverage enhancement could be used without departing from the scope of this disclosure.

[0249] In the example of FIG. 11, the method 1100 begins at step 1110. At step 1110, a BS (such as gNB 102 of FIG. 1) transmits, to a UE (such as UE 116 of FIG. 1), system information including configuration information associated with Msg4 PDSCH repetition.

[0250] At step 1120, during a four-step random access procedure, the BS receives, from the UE, a Msg3 including an indication that the UE supports Msg4 PDSCH repetition.

[0251] At step 1130, during the four-step random access procedure, in response to reception of of the Msg3, the BS (i) transmits DCI scheduling a Msg4 PDSCH repetition, and (ii) repeatedly transmits a Msg4 PDSCH scheduled by the DCI.

[0252] In some embodiments, the configuration information associated with Msg4 PDSCH repetition may indicate that Msg4 PDSCH repetition is enabled, and the indication that the UE supports Msg4 PDSCH repetition may be included in the Msg3 in response to the information associated with the Msg4 PDSCH repetition indicating that Msg4 PDSCH repetition is enabled.

[0253] In some embodiments, the configuration information associated with Msg4 PDSCH repetition may be per bandwidth part (BWP).

[0254] In some embodiments, the configuration information associated with Msg4 PDSCH repetition may indicate a number of repetitions.

[0255] In some embodiments, the Msg3 may include an uplink CCCH message identified by an LCID.

[0256] In some embodiments, the LCID may indicate that the UE supports the Msg4 PDSCH repetition, by indicating at least one of: CCCH of size 48 bits for PDSCH repetition of Msg4, except for a reduced capability (RedCap) or enhanced (eRedCap) UE; CCCH of size 64 bits for PDSCH repetition of Msg4, except for a RedCap or eRedCap UE; CCCH of size 48 bits for PDSCH repetition of Msg4 of a RedCap UE; CCCH of size 64 bits for PDSCH repetition of Msg4 of a RedCap UE; CCCH of size 48 bits for PDSCH repetition of Msg4 of an eRedCap UE; CCCH of size 64 bits for PDSCH repetition of Msg4 of an eRedCap UE; CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK and PDSCH repetition of Msg4, except for except for a RedCap or eRedCap UE; CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK and PDSCH repetition of Msg4, except for a RedCap or eRedCap UE; CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK and PDSCH repetition of Msg4 of a RedCap UE; CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK and PDSCH repetition of Msg4 of a RedCap UE; CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK and PDSCH repetition of Msg4 of an eRedCap UE; and CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK and PDSCH repetition of Msg4 of an eRedCap UE.

[0257] Although FIG. 11 illustrates one example method for repetition for downlink coverage enhancement 1100, various changes may be made to FIG. 11. For example, while shown as a series of steps, various steps in FIG. 11 could overlap, occur in parallel, occur in a different order, occur any number of times, be omitted, or replaced by other steps.

[0258] FIG. 12 is a block diagram of a terminal or user equipment (UE) 1200 according to an embodiment of the disclosure. The UE of FIG. 12 corresponds to the UE of FIG. 3A.

[0259] The terminal is an electronic device capable of wireless communication and having various form factors, examples of the terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or any other device / system capable of performing wireless communication with a base station (BS) and / or another terminal through a wireless channel.

[0260] Referring to FIG. 12, the UE 1200 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 1201, at least one processor (hereinafter, referred to as simply “processor”) 1202, and at least one memory (hereinafter, referred to as simply “memory”) 1203. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 1201, the processor 1202, and the memory 1203 of the UE 1200 may operate. However, components of the UE 1200 are not limited to the example components illustrated in FIG. 12. In another embodiment, the UE 1200 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 1201, the processor 1202, or the memory 1203 may be integrated in the form of one component.

[0261] The transceiver 1201 may be a communication circuit or communication circuitry that enables the UE 1200 to perform wireless communication with a node or an entity of a network. For example, the transceiver 1201 may enable the UE 1200 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 1201 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 (1201) may include all subsequent generations of evolved wireless communications.

[0262] According to an embodiment, the UE 1200 may include a plurality of transceivers. For example, in the case of supporting evolved-universal terrestrial radio access-new radio (E-UTRA-NR) dual connectivity (EN-DC), the UE 1200 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 1200 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 1200 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).

[0263] According to an embodiment, the transceiver 1201 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 1201 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 1201 may output a signal received through a wireless channel to the processor 1202 and may transmit, through a wireless channel, a signal output from the processor 1202.

[0264] The processor 1202 may control general operations of the UE 1200 according to embodiments of the disclosure. The processor 1202 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1202 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1203, individually, collectively or in any combination thereof. Further, the processor 1202 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.

[0265] The processor 1202 may be electrically, operatively, and / or communicatively coupled to the transceiver 1201 to control the transceiver 1201.

[0266] The processor 1202 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 1202 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 1202 may be included in one chip (or IC) and the other part of the processor 1202 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 1201 or the memory 1203.

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

[0268] The memory 1203 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 1203 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.

[0269] The memory 1203 may be electrically, operatively, and / or communicatively coupled to the processor 1202 and may be accessed by the processor 1202.

[0270] The memory 1203 may store a computer program, codes, or instructions executable by the processor 1202. According to an embodiment, a computer program, codes, or instructions executable by the processor 1202 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 1203, the processor 1202 may perform various functions according to an embodiment of the disclosure.

[0271] According to an embodiment of the disclosure, operations of the UE 1200 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1203 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.

[0272] FIG. 13 is a block diagram of a base station (BS) 1300 according to an embodiment of the disclosure. The BS of FIG. 13 corresponds to the BS of FIG. 3B.

[0273] The BS 1300 may perform wireless communication with at least one user equipment (UE) located within the area of the BS 1300 through a wireless channel. The BS 1300 may perform communication with a node or an entity of a network through wired or wireless communication.

[0274] Referring to FIG. 13, the BS 1300 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 1301, at least one processor (hereinafter, referred to as simply “processor”) 1302, and at least one memory (hereinafter, referred to as simply “memory”) 1303. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 1301, the processor 1302, and the memory 1303 of the BS 1300 may operate. However, components of the BS 1300 are not limited to the example components illustrated in FIG. 13. In another embodiment, the BS 1300 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 1301, the processor 1302, or the memory 1303 may be integrated in the form of one component.

[0275] The transceiver 1301 may be a communication circuit or communication circuitry that enables the BS 1300 to perform wireless communication with a node or an entity of a network. For example, the transceiver 1301 may enable the BS 1300 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 1301 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 (1301) may include all subsequent generations of evolved wireless communications. According to an embodiment, the transceiver 1301 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 1301 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 1301 may output a signal received through a wireless channel to the processor 1302 and may transmit, through a wireless channel, a signal output from the processor 1302.

[0276] Meanwhile, according to an embodiment of the present disclosure, the BS 1300 may perform communication with a node or an entity of a network through wired or wireless communication. For example, the BS 1300 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. 13, when the BS 1300 performs wired communication, the BS 1300 may further include a separate network interface for wired communication in addition to the transceiver 1301. The network interface may be referred to as network interface circuitry or communication interface circuitry.

[0277] The processor 1302 may control general operations of the BS 1300 according to embodiments of the disclosure. The processor 1302 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1302 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1303, individually, collectively or in any combination thereof. Further, the processor 1302 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.

[0278] The processor 1302 may be electrically, operatively, and / or communicatively coupled to the transceiver 1301 to control the transceiver 1301.

[0279] The processor 1302 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 1302 may be included in one chip (or IC) and the other part of the processor 1302 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 1301 or the memory 1303.

[0280] The processor 1302 may perform or control or cause an operation of the BS 1300 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1302 may control operations of the BS 1300 for generating and transmitting a downlink signal to a UE or processing an uplink signal received from a UE. Otherwise, the BS 1300 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 1302 may execute a computer program, codes, or instructions stored in the memory 1303, so as to control other components of the BS 1300 to enable execution of various operations.

[0281] The memory 1303 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 1303 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.

[0282] The memory 1303 may be electrically, operatively, and / or communicatively coupled to the processor 1302 and may be accessed by the processor 1302.

[0283] The memory 1303 may store a computer program, codes, or instructions executable by the processor 1302. According to an embodiment, a computer program, codes, or instructions executable by the processor 1302 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 1303, the processor 1302 may perform various functions according to an embodiment of the disclosure.

[0284] According to an embodiment of the disclosure, operations of the BS 1300 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1303 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.

[0285] 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 a network entity (for example, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), rtc.) 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.

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

[0287] FIG. 14 is a block diagram of a network entity 1400 according to an embodiment of the disclosure.

[0288] The network entity 1400 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 1400.

[0289] 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.

[0290] 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), etc.

[0291] Referring to FIG. 14, the network entity 1400 may include at least one network interface 1401, at least one processor 1402 (hereinafter, “processor”), and at least one memory 1403 (hereinafter, “memory”). As described above, a NF may be implemented in the form of a physical device such as the network entity 1400, 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. 14. In such a case, the instance may be logically represented as comprising one or more logical functional elements.

[0292] According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the network interface 1401, the processor 1402, and the memory 1403 of the network entity 1400 may operate. However, components of the network entity 1400 are not limited to the example components illustrated in FIG. 14. In another embodiment, the network entity 1400 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 1401, the processor 1402, or the memory 1403 may be integrated in the form of one component.

[0293] The network interface 1401 is a collective term for a transmitter part of the network entity 1400 and a receiver part of the network entity 1400, 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 1401 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 1401 may operate using various protocols (e.g., non-access stratum (NAS) protocol). The network interface 1401 may also be referred to, for convenience of description or depending on implementation, as communication circuitry, network interface circuitry, or a communication interface circuitry.

[0294] The processor 1402 may control general operations of the network entity 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 processing operations. 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. 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.

[0295] According to an embodiment, the processor 1402 may be electrically, operatively, and / or communicatively coupled to the network interface 1401 to control the network interface 1401.

[0296] 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. In a specific embodiment, at least a part of the processor 1402 may be included in one chip (or IC) and the other part of the processor 1402 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the network interface 1401 or the memory 1403.

[0297] The processor 1402 may perform or control or cause an operation of the network entity 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 network entity 1400 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 1402 may execute a computer program, codes, or instructions stored in the memory 1403, so as to control other components of the network entity 1400 to enable execution of various operations.

[0298] 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.

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

[0300] 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.

[0301] According to an embodiment of the disclosure, operations of the network entity 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.

[0302] Any of the above variation embodiments can be utilized independently or in combination with at least one other variation embodiment. The above flowcharts illustrate example methods that can be implemented in accordance with the principles of the present disclosure and various changes could be made to the methods illustrated in the flowcharts herein. For example, while shown as a series of steps, various steps in each figure could overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, steps may be omitted or replaced by other steps.

[0303] Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims. None of the description in this application should be read as implying that any particular element, step, or function is an essential element that must be included in the claim scope. The scope of patented subject matter is defined by the claims.

[0304] 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, the method comprising:receiving, from a base station, a system information block (SIB) including information on a number of repetition slots for a message 4 (Msg4) physical downlink shared channel (PDSCH);receiving, from the base station, a Msg2 random access response (RAR) including an uplink (UL) grant for a Msg3 physical uplink shared channel (PUSCH);transmitting, to the base station, the Msg3 PUSCH including information indicating a support for a repetition of the Msg4 PDSCH; andreceiving, from the base station, the Msg4 PDSCH according to the number of repetition slots.2.The method of claim 1, further comprising:receiving, from the base station, downlink control information (DCI) scheduling the Msg4 PDSCH,wherein the information on the number of repetition slots for the Msg4 PDSCH is configured per bandwidth part (BWP).3.The method of claim 1,wherein a medium access control (MAC) protocol data unit (PDU) for the Msg3 includes a MAC subheader for a MAC service data unit (SDU) including UL common control channel (CCCH) SDU, andwherein the MAC subheader includes a logical channel identifier (LCID).4.The method of claim 3, wherein a value of the LDID is one of:a CCCH of size 48 bits for the repetition of the Msg4 PDSCH, except for a reduced capability (RedCap) UE;a CCCH of size 64 bits for the repetition of the Msg4 PDSCH, except for the RedCap UE;a CCCH of size 48 bits for the repetition of the Msg4 PDSCH of the RedCap UE;a CCCH of size 64 bits for the repetition of the Msg4 PDSCH of the RedCap UE;a CCCH of size 48 bits for the repetition of the Msg4 PDSCH of an enhanced RedCap (eRedCap) UE;a CCCH of size 64 bits for the repetition of the Msg4 PDSCH of the eRedCap UE;a CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH, except for the RedCap UE;a CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH, except for the RedCap UE;a CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH of the RedCap UE;a CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH of the RedCap UE;a CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH of the eRedCap UE; ora CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH of the eRedCap UE.5.A method performed by a base station in a wireless communication system, the method comprising:transmitting, to a user equipment (UE), a system information block (SIB) including information on a number of repetition slots for a message 4 (Msg4) physical downlink shared channel (PDSCH);transmitting, to the UE, a Msg2 random access response (RAR) including an uplink (UL) grant for a Msg3 physical uplink shared channel (PUSCH);receiving, from the UE, the Msg3 PUSCH including information indicating a support for a repetition of the Msg4 PDSCH; andtransmitting, to the UE, the Msg4 PDSCH according to the number of repetition slots.6.The method of claim 5, further comprising:transmitting, to the UE, downlink control information (DCI) scheduling the Msg4 PDSCH,wherein the information on the number of repetition slots for the Msg4 PDSCH is configured per bandwidth part (BWP).7.The method of claim 5,wherein a medium access control (MAC) protocol data unit (PDU) for the Msg3 includes a MAC subheader for a MAC service data unit (SDU) including UL common control channel (CCCH) SDU, andwherein the MAC subheader includes a logical channel identifier (LCID).8.The method of claim 7, wherein a value of the LDID is one of:a CCCH of size 48 bits for the repetition of the Msg4 PDSCH, except for a reduced capability (RedCap) UE;a CCCH of size 64 bits for the repetition of the Msg4 PDSCH, except for the RedCap UE;a CCCH of size 48 bits for the repetition of the Msg4 PDSCH of the RedCap UE;a CCCH of size 64 bits for the repetition of the Msg4 PDSCH of the RedCap UE;a CCCH of size 48 bits for the repetition of the Msg4 PDSCH of an enhanced RedCap (eRedCap) UE;a CCCH of size 64 bits for the repetition of the Msg4 PDSCH of the eRedCap UE;a CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH, except for the RedCap UE;a CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH, except for the RedCap UE;a CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH of the RedCap UE;a CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH of the RedCap UE;a CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH of the eRedCap UE; ora CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH of the eRedCap UE.9.A user equipment (UE) in a wireless communication system, the 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, a system information block (SIB) including information on a number of repetition slots for a message 4 (Msg4) physical downlink shared channel (PDSCH),receive, from the base station, a Msg2 random access response (RAR) including an uplink (UL) grant for a Msg3 physical uplink shared channel (PUSCH),transmit, to the base station, the Msg3 PUSCH including information indicating a support for a repetition of the Msg4 PDSCH, andreceive, from the base station, the Msg4 PDSCH according to the number of repetition slots.10.The UE of claim 9, wherein the instructions further cause the UE to:receive, from the base station, downlink control information (DCI) scheduling the Msg4 PDSCH,wherein the information on the number of repetition slots for the Msg4 PDSCH is configured per bandwidth part (BWP).11.The UE of claim 9,wherein a medium access control (MAC) protocol data unit (PDU) for the Msg3 includes a MAC subheader for a MAC service data unit (SDU) including UL common control channel (CCCH) SDU, andwherein the MAC subheader includes a logical channel identifier (LCID).12.The UE of claim 11, wherein a value of the LDID is one of:a CCCH of size 48 bits for the repetition of the Msg4 PDSCH, except for a reduced capability (RedCap) UE;a CCCH of size 64 bits for the repetition of the Msg4 PDSCH, except for the RedCap UE;a CCCH of size 48 bits for the repetition of the Msg4 PDSCH of the RedCap UE;a CCCH of size 64 bits for the repetition of the Msg4 PDSCH of the RedCap UE;a CCCH of size 48 bits for the repetition of the Msg4 PDSCH of an enhanced RedCap (eRedCap) UE;a CCCH of size 64 bits for the repetition of the Msg4 PDSCH of the eRedCap UE;a CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH, except for the RedCap UE;a CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH, except for the RedCap UE;a CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH of the RedCap UE;a CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH of the RedCap UE;a CCCH of size 48 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH of the eRedCap UE; ora CCCH of size 64 bits for PUCCH repetition of Msg4 HARQ-ACK and the repetition of the Msg4 PDSCH of the eRedCap UE.13.A base station in a wireless communication system, the 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), a system information block (SIB) including information on a number of repetition slots for a message 4 (Msg4) physical downlink shared channel (PDSCH),transmit, to the UE, a Msg2 random access response (RAR) including an uplink (UL) grant for a Msg3 physical uplink shared channel (PUSCH),receive, from the UE, the Msg3 PUSCH including information indicating a support for a repetition of the Msg4 PDSCH, andtransmit, to the UE, the Msg4 PDSCH according to the number of repetition slots.14.The base station of claim 13, wherein the instructions further cause the BS to:transmit, to the UE, downlink control information (DCI) scheduling the Msg4 PDSCH,wherein the information on the number of repetition slots for the Msg4 PDSCH is configured per bandwidth part (BWP).15.The base station of claim 13,wherein a medium access control (MAC) protocol data unit (PDU) for the Msg3 includes a MAC subheader for a MAC service data unit (SDU) including UL common control channel (CCCH) SDU, andwherein the MAC subheader includes a logical channel identifier (LCID).

Images