Multiple default beams for multiple PDSCH / PUSCH and multi-slot PDCCH monitoring

Abstract

An apparatus, method and system for associating multiple PDSCH / PUSCH default beams are disclosed. An apparatus includes a processor coupled to a transceiver, the processor and the transceiver configured to cause the apparatus to receive a CORESET configuration indicating multiple beams and corresponding durations for each beam indicated for at least a CORESET ID, and monitor at least one CORESET at different PDCCH monitoring occasions using different beams. Through the transceiver, the processor receives a first CORESET in a PDCCH transmission, which schedules multiple physical channel transmissions (i.e., PDSCH and / or PUSCH) and communicates with a RAN on multiple scheduled physical channels using multiple beams associated with the lowest CORESET ID configured in the device.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 170,955, entitled “MULTIPLE DEFAULT BEAMS FOR MULTIPLE PDSCH / PUSCH AND MULTI-SLOT PDCCH MONITORING,” filed on April 5, 2021 to Ankit Bhamri, Ali Ramadan Ali, Karthikeyan Ganesan, Alexander Johann Maria Golitschek Edler von Elbwart, and Sher Ali Cheema, which is incorporated herein by reference.

[0002] The subject matter disclosed herein relates generally to wireless communications, and more specifically, to multiple default beams for multiple Physical Downlink Shared Channels ("PDSCHs") and / or Physical Uplink Shared Channels ("PUSCHs") (i.e., "PDSCH / PUSCHs") and a multi-slot Physical Downlink Control Channel ("PDCCH"). [Background technology]

[0003] A particular wireless network may support Third Generation Partnership Project (“3GPP”) New Radio (“NR”) (i.e., 5th generation Radio Access Technology (“RAT”)) operation in frequency bands above 52.6 GHz (e.g., 52.6 GHz to 71 GHz). To extend NR operation beyond 52.6 GHz, beam management and scheduling behavior may be modified for the higher frequency regions. Summary of the Invention [Means for solving the problem]

[0004] Procedures are disclosed for associating multiple default beams for multiple PDSCH / PUSCHs and for monitoring the same Control Resource Set ("CORESET") on different beams at different monitoring occasions, which may be implemented by an apparatus, a system, a method, or a computer program product.

[0005] One method in a User Equipment ("UE") includes receiving a CORESET configuration from a radio access network ("RAN"), the CORESET configuration indicating multiple beams for at least a CORESET identifier ("ID") and a corresponding duration for each indicated beam, and monitoring at least one CORESET at different physical downlink control channel ("PDCCH") monitoring occasions using different beams. The method includes receiving a first CORESET in a PDCCH transmission, the first CORESET scheduling multiple physical channel transmissions, and communicating with the RAN over multiple scheduled physical channels using multiple beams associated with the lowest CORESET ID configured on the device, where communicating with the RAN over multiple scheduled physical channels includes receiving a downlink transmission, transmitting an uplink transmission, or a combination thereof.

[0006] One method in a RAN includes transmitting a CORESET configuration from a UE, the CORESET configuration indicating a number of beams and corresponding durations for each beam indicated for at least a CORESET ID. The method includes transmitting a first CORESET within a PDCCH monitoring opportunity, the first CORESET scheduling a number of physical channel transmissions, and communicating with the UE on the multiple scheduled physical channels using the multiple beams associated with the lowest CORESET ID configured on the device, where communicating with the RAN on the multiple scheduled physical channels includes transmitting downlink transmissions, receiving uplink transmissions, or a combination thereof.

[0007] A more particular description of the embodiments briefly described above will be given by reference to specific embodiments that are illustrated in the accompanying drawings, in which the embodiments will be described and explained with additional specificity and detail, with the understanding that these drawings illustrate only some embodiments and therefore should not be considered limiting in scope. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a schematic block diagram illustrating an embodiment of a wireless communication system for associating multiple default beams for multiple PDSCH / PUSCHs and monitoring the same CORESET on different beams at different monitoring occasions. [Diagram 2] FIG. 1 illustrates one embodiment of a New Radio ("NR") protocol stack. [Diagram 3] A figure showing an embodiment of updating the TCI / QCL / beams of multiple PDSCHs based on multiple TCI / QCL / beams activated for scheduling a CORESET. [Figure 4]A diagram showing an embodiment of updating the TCI / QCL / beams of multiple PDSCHs based on the TCI / QCL / beams activated for the lowest CORESET ID. [Diagram 5] FIG. 13 illustrates an embodiment in which the TCI / QCL / beams of multiple PDSCHs are updated based on the multiple TCI / QCL / beams activated for the lowest CORESET ID of some PDSCHs, while multiple TCI / QCL / beams are activated to schedule the CORESET for the remaining PDSCHs. [Figure 6] A figure showing an embodiment in which the TCI / QCL / beams of multiple PDSCHs are updated based on the TCI / QCL / beams activated for the lowest CORESET IDs of some PDSCHs, while applying the TCI / QCL / beams indicated by DCI to the remaining PDSCHs. [Figure 7] A diagram showing one embodiment of PDCCH monitoring using different TCI / QCL / beams for the same CORESET at different monitoring occasions within a PDCCH monitoring period. [Figure 8] A diagram showing one embodiment of PDCCH monitoring using different TCI / QCL / beams for the same CORESET on different monitoring occasions having an association pattern period shorter than the PDCCH monitoring period. [Figure 9] A diagram showing one embodiment of PDCCH monitoring using different TCI / QCL / beams for the same CORESET on different monitoring occasions having an association pattern period longer than the PDCCH monitoring period. [Figure 10] FIG. 1 is a block diagram illustrating an embodiment of a user equipment device that may be used to associate multiple default beams for multiple PDSCH / PUSCHs and to monitor the same CORESET on different beams at different monitoring occasions. [Figure 11]FIG. 1 is a block diagram illustrating an embodiment of a network device that may be used to associate multiple default beams for multiple PDSCH / PUSCHs and to monitor the same CORESET on different beams at different monitoring occasions. [Figure 12] 1 is a flow chart illustrating an embodiment of a first method for associating multiple default beams for multiple PDSCH / PUSCHs and monitoring the same CORESET on different beams at different monitoring occasions. [Figure 13] 11 is a flow chart illustrating an embodiment of a second method for associating multiple default beams for multiple PDSCH / PUSCHs and monitoring the same CORESET on different beams at different monitoring occasions. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, the embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.) or an embodiment combining software and hardware aspects.

[0010] For example, the disclosed embodiments may be implemented as hardware circuitry comprising custom very large scale integrated ("VLSI") circuits or off-the-shelf semiconductors such as gate arrays, logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code which may be organized as, for example, objects, procedures, or functions.

[0011] Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage devices may be tangible, non-transitory, and / or non-transmittable. The storage devices may not embody signals. In some embodiments, the storage devices use only signals to access the code.

[0012] Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device that stores the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0013] More specific examples of storage devices (a non-exhaustive list) include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or flash memory), a portable compact disk read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this specification, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0014] The code for carrying out the operations of the embodiments may be any number of lines and may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or in machine language, such as assembly language. The code may be performed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network ("LAN"), wireless LAN ("WLAN"), or wide area network ("WAN"), and connections to external computers may be made (e.g., via the Internet using an Internet Service Provider ("ISP").

[0015] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, one skilled in the art will recognize that the embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the embodiments.

[0016] Reference throughout this specification to "one embodiment," "an embodiment," or similar words means that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Thus, appearances throughout this specification of the phrases "in one embodiment," "in an embodiment," and similar words mean "one or more but not all embodiments," although they may, but do not necessarily, all refer to the same embodiment, unless expressly specified otherwise. The terms "including," "comprising," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise. A list of enumerated items does not imply that some or all of the items are mutually exclusive, unless expressly specified otherwise. The terms "a," "an," and "the" also mean "one or more," unless expressly specified otherwise.

[0017] As used herein, a list with the conjunction "and / or" includes any single item in the list or combination of items in the list. For example, a list of A, B, and / or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term "one or more of" includes any single item in the list or combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term "one of" includes only one of any single item in the list. For example, "one of A, B, and C" includes only A, only B, or only C, and excludes the combination of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C" includes only one of A, B, or C, and excludes the combination of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C, and combinations thereof" includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C.

[0018] Aspects of the embodiments are described below with reference to schematic flowchart illustrations and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowchart illustrations and / or schematic block diagrams, and combinations of blocks in the schematic flowchart illustrations and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing device to generate a machine such that the instructions, which are executed via the processor of the computer or other programmable data processing device, create means for implementing the functions / acts specified in the flowchart illustrations and / or block diagrams.

[0019] Code may also be stored in a storage device that can cause a computer, other programmable data processing device, or other device to function in a particular way, such that the instructions stored in the storage device produce an article of manufacture that includes instructions that implement the functions / acts specified in the flowchart illustrations and / or block diagrams.

[0020] The code may also be loaded into a computer, other programmable data processing apparatus, or other device such that a series of operational steps are executed on the computer, other programmable apparatus, or other device to generate a computer-implemented process such that the code executed on the computer or other programmable apparatus provides a process for implementing the functions / acts specified in the flowchart illustrations and / or block diagrams.

[0021] The call flow diagrams, flowchart diagrams, and / or block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the flowchart diagrams and / or block diagrams may represent a module, segment, or portion of code that includes one or more executable instructions of code for implementing a specified logical function(s).

[0022] It should also be noted that in some alternative embodiments, the functions noted in the blocks may differ from the order noted in the figures. For example, two blocks shown in succession may in fact be performed substantially simultaneously, or the blocks may sometimes be performed in the reverse order, depending on the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks of the illustrated figures, or portions thereof.

[0023] It should be understood that various arrow types and line types may be used in the call flows, flowcharts and / or block diagrams, but they are not intended to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the illustrated embodiment. For example, the arrows may indicate waiting or monitoring periods of unspecified duration between the recited steps of the depicted embodiment. It should also be noted that each block of the block diagrams and / or flowchart diagrams, and combinations of blocks in the block diagrams and / or flowchart diagrams, may be implemented by a dedicated hardware-based system that performs the specified functions or acts, or a combination of dedicated hardware and code.

[0024] The description of an element in each drawing may refer to the element in the previous drawing. Like numbers refer to like elements in all drawings, including alternative embodiments of like elements.

[0025] In general, the present disclosure describes systems, methods, and apparatus for associating multiple default beams for multiple PDSCH / PUSCHs and monitoring the same CORESET on different beams at different monitoring occasions. In certain embodiments, the methods may be performed using computer code embedded in a computer-readable medium. In certain embodiments, the apparatus or system may include a computer-readable medium including computer-readable code that, when executed by a processor, causes the apparatus or system to perform at least a portion of the solutions described below.

[0026] For NR operation above 52.6 GHz, beam management of multi-PDSCH / PUSCH scheduling becomes important for efficient operation. Currently, multi-slot PDCCH monitoring and single DCI-based scheduling for multiple PDSCH / PUSCH are defined for NR operation from 52.6 GHz to 71 GHz. However, the timing associated with beam-based operation can be enhanced for the new higher operating frequencies and new SCS (i.e., 480 kHz and / or 960 kHz) of NR. One of the issues discussed is determining the default beam / TCI / QCL when multiple PDSCHs are scheduled by a single DCI. As used herein, a beam may be defined by Quasi-Co-Location ("QCL") assumptions and / or by Transmission Configuration Indicator ("TCI") states. Thus, the terms "beam", "QCL assumptions", and "TCI states" are used interchangeably within this disclosure. Furthermore, the term “TCI / QCL / beam” may be used in the following description to refer to a beam, a TCI state, and / or a QCL hypothesis.

[0027] In this disclosure, a solution is defined on how to assign / determine multiple default beams for multiple PDSCHs. Another aspect discussed herein relates to the beam / TCI / QCL used for multi-slot PDCCH monitoring (i.e., CORESET) where one or more PDCCH monitoring opportunities can span a group of slots. A procedure and related signaling are defined herein for determining an appropriate beam for monitoring the same CORESET across multiple monitoring opportunities in a group of slots for multi-slot PDCCH monitoring.

[0028] Solutions are disclosed for associating multiple default beams for multiple PDSCH / PUSCHs and monitoring the same CORESET on different beams at different monitoring occasions. In some embodiments, the procedures and signaling described below may be performed to enable association of multiple default beams that apply to multiple PDSCH / PUSCHs scheduled by a single DCI. In some embodiments, the procedures and signaling described below may be performed to enable monitoring of the same CORESET on different beams at different monitoring occasions without additional Medium Access Control ("MAC") Control Element ("CE") activation.

[0029] FIG. 1 illustrates a wireless communication system 100 for associating multiple default beams for multiple PDSCH / PUSCHs and monitoring the same CORESET on different beams at different monitoring occasions according to an embodiment of the present disclosure. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network ("RAN") 120, and a mobile core network 140. The RAN 120 and the mobile core network 140 form a mobile communication network. The RAN 120 may be comprised of a base unit 121 with which the remote unit 105 communicates using a wireless communication link 123. Although a specific number of remote units 105, base units 121, wireless communication links 123, RAN 120, and mobile core network 140 are illustrated in FIG. 1, one skilled in the art will recognize that any number of remote units 105, base units 121, wireless communication links 123, RAN 120, and mobile core network 140 may be included in the wireless communication system 100.

[0030] In one implementation, the RAN 120 is compliant with a fifth generation ("5G") cellular system specified in the 3rd Generation Partnership Project ("3GPP") specifications. For example, the RAN 120 may be a Next Generation Radio Access Network ("NG-RAN") implementing a New Radio ("NR") radio access technology ("RAT") and / or a Long Term Evolution ("LTE") RAT. In another example, the RAN 120 may include a non-3GPP RAT (e.g., Wi-Fi or an Institute of Electrical and Electronics Engineers ("IEEE") 802.11 family compliant WLAN). In another implementation, the RAN 120 is compliant with an LTE system specified in the 3GPP specifications. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication network, such as the Worldwide Interoperability for Microwave Access ("WiMAX") or the IEEE 802.16 family standards, among other networks. This disclosure is not intended to be limited to any particular wireless communications system architecture or protocol implementation.

[0031] In one embodiment, the remote unit 105 may include computing devices such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smartphones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, gaming consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), etc. In some embodiments, the remote unit 105 includes wearable devices such as smart watches, fitness bands, optical head mounted displays, etc. Additionally, the remote unit 105 may be referred to as a UE, subscriber unit, mobile, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user terminal, wireless transmit / receive unit ("WTRU"), device, or other terminology used in the art. In various embodiments, the remote unit 105 includes a subscriber identification and / or identification module ("SIM") and a mobile equipment ("ME") that provides mobile terminal functions (e.g., wireless transmission, handover, voice encoding and decoding, error detection and correction, signaling, and access to the SIM). In particular embodiments, the remote unit 105 may include terminal equipment ("TE") and / or may be embedded in an equipment or device (e.g., a computing device as described above).

[0032] The remote units 105 may communicate directly with one or more of the base units 121 in the RAN 120 via uplink ("UL") and downlink ("DL") communication signals. Furthermore, the UL and DL communication signals may be carried over a wireless communication link 123. Furthermore, the UL communication signals may comprise one or more uplink channels, such as a physical uplink control channel ("PUCCH") and / or a physical uplink shared channel ("PUSCH"), and the DL communication signals may comprise one or more downlink channels, such as a physical downlink control channel ("PDCCH") and / or a physical downlink shared channel ("PDSCH"). Here, the RAN 120 is an intermediate network that provides the remote units 105 with access to the mobile core network 140.

[0033] In some embodiments, the remote unit 105 communicates with the application server 151 via a network connection with the mobile core network 140. For example, an application in the remote unit 105 (e.g., a web browser, a media client, a telephone and / or a voice over Internet protocol ("VoIP") application) may trigger the remote unit 105 to establish a protocol data unit ("PDU") session (or other data connection) with the mobile core network 140 through the RAN 120. The mobile core network 140 then uses the PDU session to relay traffic between the remote unit 105 and the application server 151 in the packet data network 150. The PDU session represents a logical connection between the remote unit 105 and the user plane function ("UPF") 141.

[0034] To establish a PDU session (or PDN connection), the remote unit 105 must register with the mobile core network 140 (also referred to as being "connected to the mobile core network" in the context of a fourth generation ("4G") system). It should be noted that the remote unit 105 may establish one or more PDU sessions (or other data connections) with the mobile core network 140. Thus, the remote unit 105 may have at least one PDU session for communicating with the packet data network 150. The remote unit 105 may establish additional PDU sessions for communicating with other data networks and / or other communication peers.

[0035] In the context of 5G systems ("5GS"), the term "PDU session" refers to a data connection that provides end-to-end ("E2E") user plane ("UP") connectivity between the remote unit 105 and a particular data network ("DN") through the UPF 141. A PDU session supports one or more Quality of Service ("QoS") flows. In certain embodiments, there may be a one-to-one mapping between QoS flows and QoS profiles such that all packets belonging to a particular QoS flow have the same 5G QoS Identifier ("5QI").

[0036] In the context of a 4G / LTE system, such as an Evolved Packet System ("EPS"), a Packet Data Network ("PDN") connection (also called an EPS session) provides an E2E UP connection between a remote unit and a PDN. The PDN connection procedure establishes an EPS bearer, i.e., a tunnel between the remote unit 105 and a PDN Gateway ("PGW", not shown) in the mobile core network 140. In a particular embodiment, there is a one-to-one mapping between EPS bearers and QoS profiles, such that all packets belonging to a particular EPS bearer have the same QoS Class Identifier ("QCI").

[0037] The base units 121 may be distributed across a geographic region. In certain embodiments, the base units 121 may also be referred to as an access terminal, an access point, a base, a base station, a Node-B ("NB"), an evolved Node B (abbreviated as eNodeB or "eNB" and also known as an evolved Universal Terrestrial Radio Access Network ("E-UTRAN") Node B), a 5G / NR Node B ("gNB"), a Home Node B, a relay node, a RAN node, or any other terminology used in the art. The base units 121 are generally part of a RAN, such as the RAN 120, and may include one or more controllers communicatively coupled to one or more corresponding base units 121. These and other elements of a radio access network are not shown, but are generally well known by those skilled in the art. The base units 121 connect to the mobile core network 140 via the RAN 120.

[0038] The base unit 121 may serve several remote units 105 within a service area, such as a cell or a cell sector, via wireless communication link 123. The base unit 121 may directly communicate with one or more of the remote units 105 via communication signals. In general, the base unit 121 transmits DL communication signals to serve the remote units 105 in time, frequency, and / or spatial domains. Furthermore, the DL communication signals may be carried via the wireless communication link 123. The wireless communication link 123 may be any suitable carrier in a licensed or unlicensed radio spectrum. The wireless communication link 123 facilitates communication between one or more of the remote units 105 and / or one or more of the base units 121.

[0039] It should be noted that during NR operation in an unlicensed spectrum (referred to as "NR-U"), the base unit 121 and the remote unit 105 communicate over an unlicensed (i.e., shared) radio spectrum. Similarly, during LTE operation in an unlicensed spectrum (referred to as "LTE-U"), the base unit 121 and the remote unit 105 also communicate over an unlicensed (i.e., shared) radio spectrum.

[0040] In one embodiment, the mobile core network 140 is a 5G core network ("5GC") or an evolved packet core ("EPC") and may be coupled to a packet data network 150, such as the Internet and private data networks, among other data networks. The remote units 105 may have a subscription or other account with the mobile core network 140. In various embodiments, each mobile core network 140 belongs to a single mobile network operator ("MNO") and / or public land mobile network ("PLMN"). This disclosure is not intended to be limited to any particular wireless communications system architecture or protocol implementation.

[0041] The mobile core network 140 includes several network functions ("NFs"). As shown, the mobile core network 140 includes at least one UPF 141. The mobile core network 140 also includes multiple control plane ("CP") functions, including, but not limited to, an access and mobility management function ("AMF") 143 that serves the RAN 120, a session management function ("SMF") 145, a policy control function ("PCF") 147, a unified data management function ("UDM"), and a user data repository ("UDR"). In some embodiments, the UDM is co-located with the UDR and is depicted as a combined entity "UDM / UDR" 149. Although a particular number and type of network functions are depicted in FIG. 1, one skilled in the art will recognize that any number and type of network functions may be included in the mobile core network 140.

[0042] The UPF 141 is responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU sessions for interconnecting data networks ("DNs") in the 5G architecture. The AMF 143 is responsible for termination of non-access stratum ("NAS") signaling, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. The SMF 145 is responsible for session management (i.e., session establishment, modification, release), remote unit (i.e., UE) Internet Protocol ("IP") address allocation and management, DL data notification, and traffic steering configuration of the UPF 141 for proper traffic routing.

[0043] The PCF 147 is responsible for the unified policy framework, providing policy rules to the CP function and accessing subscription information for policy decisions in the UDR. The UDM is responsible for generating Authentication and Key Agreement ("AKA") credentials, handling user identification, access authorization, and subscription management. The UDR is a repository of subscriber information and can be used to provide a number of network functions. For example, the UDR can store subscription data, policy related data, subscriber related data that is allowed to be exposed to third-party applications, etc.

[0044] In various embodiments, the mobile core network 140 may also include a Network Repository Function ("NRF") (which provides registration and discovery of Network Function ("NF") services, allowing NFs to identify appropriate services to each other and communicate with each other via application programming interfaces ("APIs")), a Network Exposure Function ("NEF") (responsible for providing easy access to network data and resources for customers and network partners), an Authentication Server Function ("AUSF"), or other NFs defined for 5GC. If an AUSF is present, the AUSF acts as an authentication server and / or authentication proxy, thereby enabling the AMF 143 to authenticate the remote unit 105. In certain embodiments, the mobile core network 140 may include an Authentication, Authorization, and Accounting ("AAA") server.

[0045] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, with each mobile data connection utilizing a particular network slice. Here, a "network slice" refers to a portion of the mobile core network 140 optimized for a particular traffic type or communication service. For example, one or more network slices may be optimized for enhanced mobile broadband ("eMBB") services. As another example, one or more network slices may be optimized for ultra-reliable low latency communications ("URLLC") services. In other examples, network slices may be optimized for machine type communications ("MTC") services, large scale MTC ("mMTC") services, Internet of Things ("IoT") services. In yet other examples, network slices may be deployed for particular application services, vertical services, particular use cases, and the like.

[0046] A network slice instance may be identified by a single network slice selection assistance information ("S-NSSAI"), whereas a set of network slices that the remote unit 105 is authorized to use is identified by a network slice selection assistance information ("NSSAI"), where "NSSAI" refers to a vector value that includes one or more S-NSSAI values. In certain embodiments, various network slices may include separate instances of network functions, such as the SMF 145 and the UPF 141. In some embodiments, different network slices may share some common network functions, such as the AMF 143. For ease of explanation, different network slices are not shown in FIG. 1, although their support is assumed.

[0047] Although FIG. 1 illustrates components of a 5G RAN and a 5G core network, the described embodiments for associating multiple default beams for multiple PDSCH / PUSCHs and monitoring the same CORESET on different beams at different monitoring occasions also apply to other types of communication networks and RATs, including IEEE 802.11 variants, Global System for Mobile Communications (GSM) (i.e., 2G digital cellular network), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), LTE variants, CDMA2000, Bluetooth, ZigBee, Sigfox, etc.

[0048] Further, in LTE variants where the mobile core network 140 is the EPC, the illustrated network functions may be replaced with appropriate EPC entities such as a mobility management entity ("MME"), a serving gateway ("SGW"), a PGW, a home subscriber server ("HSS"), etc. For example, the AMF 143 may be mapped to the MME, the SMF 145 may be mapped to the control plane portion of the PGW and / or to the MME, the UPF 141 may be mapped to the SGW and user plane portion of the PGW, the UDM / UDR 149 may be mapped to the HSS, etc.

[0049] In the following description, the term "gNB" is used for base station / base unit, but can be replaced by any other radio access node, e.g., RAN node, ng-eNB, eNB, Base Station (BS), Access Point (AP), NR BS, 5G NB, Transmission and Reception Point (TRP), etc. Furthermore, the term "UE" is used for mobile station / remote unit, but can be replaced by any other remote device, e.g., remote unit, MS, ME, etc. Furthermore, the operation is mainly described in the context of 5G NR. However, the solutions / methods described below are equally applicable to other mobile communication systems for associating multiple default beams for multiple PDSCH / PUSCH and monitoring the same CORESET on different beams at different monitoring occasions.

[0050] FIG. 2 illustrates a protocol stack 200 according to an embodiment of the present disclosure. FIG. 2 illustrates a UE 205, a RAN node 207 (e.g., gNB), and a 5G core network 209 (e.g., including an AMF), which represent a set of remote units 105 interacting with a base unit 121 and a mobile core network 140. As illustrated, the protocol stack 200 comprises a user plane protocol stack 201 and a control plane protocol stack 203. The user plane protocol stack 201 includes a physical ("PHY") layer 211, a medium access control ("MAC") sublayer 213, a radio link control ("RLC") sublayer 215, a packet data convergence protocol ("PDCP") sublayer 217, and a service data adaptation protocol ("SDAP") layer 219. The control plane protocol stack 203 includes a PHY layer 211, a MAC sublayer 213, an RLC sublayer 215, and a PDCP sublayer 217. The control plane protocol stack 203 also includes a radio resource control (“RRC”) layer 221 and a non-access stratum (“NAS”) layer 223.

[0051] The AS layer 225 (also referred to as the "AS protocol stack") of the user plane protocol stack 201 is composed of at least the SDAP sublayer 219, the PDCP sublayer 217, the RLC sublayer 215, the MAC sublayer 213, and the PHY layer 211. The AS layer 227 of the control plane protocol stack 203 is composed of at least the RRC sublayer 221, the PDCP sublayer 217, the RLC sublayer 215, the MAC sublayer 213, and the PHY layer 211. Layer 1 ("L1") constitutes the PHY layer 211. Layer 2 ("L2") is divided into the SDAP sublayer 219, the PDCP sublayer 217, the RLC sublayer 215, and the MAC sublayer 213. Layer 3 ("L3") includes the RRC sublayer 221 and the NAS layer 223 for the control plane, e.g., an Internet Protocol ("IP") layer or a PDU layer (not shown) for the user plane. L1 and L2 are called "lower layers", and L3 and above (e.g., the transport layer, the application layer) are called "higher layers" or "upper layers".

[0052] The physical layer 211 provides transport channels to the MAC sublayer 213. The MAC sublayer 213 provides logical channels to the RLC sublayer 215. The RLC sublayer 215 provides RLC channels to the PDCP sublayer 217. The PDCP sublayer 217 provides radio bearers to the SDAP sublayer 219 and / or the RRC layer 221. The SDAP sublayer 219 maps QoS flows in a PDU session to corresponding data radio bearers over the air interface, and the SDAP sublayer 219 interfaces the QoS flows to the 5GC (e.g., User Plane Function, UPF). The RRC layer 221 provides addition, modification, and release of carrier aggregation ("CA") and / or dual connectivity ("DC"). The RRC layer 221 also manages the establishment, configuration, maintenance, and release of signaling radio bearers ("SRBs") and data radio bearers ("DRBs"). In a particular embodiment, the RRC entity functions for detection of and recovery from radio link failures.

[0053] The NAS layer 223 is located between the UE 205 and the AMF in the 5GC 509. NAS messages are passed transparently through the RAN. The NAS layer 223 is used to manage the establishment of communication sessions and to maintain continuous communication with the UE 205 as the UE 205 moves between different cells of the RAN. In contrast, the AS layers 225 and 227 are between the UE 205 and the RAN (i.e., the RAN node 207) and carry information over the wireless part of the network. Although not shown in FIG. 2, the IP layer resides above the NAS layer 223, the transport layer resides above the IP layer, and the application layer resides above the transport layer.

[0054] The MAC layer 213 is the lowest sublayer in the Layer 2 architecture of the NR protocol stack. The MAC layer 213 connects to the PHY layer 211 below through transport channels and to the RLC layer 215 above through logical channels. Thus, the MAC layer 213 performs multiplexing and demultiplexing between logical and transport channels. The MAC layer 213 on the transmitting side builds MAC PDUs, known as transport blocks, from MAC service data units ("SDUs") received over logical channels, and the MAC layer 213 on the receiving side recovers MAC SDUs from MAC PDUs received over transport channels.

[0055] The MAC layer 213 provides data transfer services to the RLC layer 215 through logical channels, which are either control logical channels carrying control data (e.g., RRC signaling) or traffic logical channels carrying user plane data. Meanwhile, data from the MAC layer 213 is exchanged with the PHY layer 211 through transport channels classified as downlink or uplink. Data is multiplexed into the transport channels depending on how it is to be transmitted over the air.

[0056] The PHY layer 211 is responsible for the actual transmission of data and control information over the air interface, i.e., the PHY layer 211 carries all information from the MAC transport channel over the air interface on the transmitting side. Some of the important functions performed by the PHY layer 211 include coding and modulation, link adaptation (e.g., adaptive modulation and coding ("AMC")), power control, cell search and random access (for initial synchronization and handover purposes), and other measurements for the RRC layer 221 (intra- and inter-system) for 3GPP systems (i.e., NR and / or LTE systems). The PHY layer 211 performs transmissions based on transmission parameters such as modulation scheme, coding rate (i.e., modulation and coding scheme ("MCS")), number of physical resource blocks, etc.

[0057] According to Clause 10 of 3GPP Technical Specification ("TS") 38.213, to receive the PDCCH in NR Rel-15 / 16, the following procedures are applied.

[0058] If the UE is provided with the parameter monitoringCapabilityConfig for the serving cell, the UE gets the indication to monitor the PDCCH on the serving cell for PDCCH candidates and the maximum number of non-overlapping Control Channel Elements ("CCEs"). If the parameter monitoringCapabilityConfig="r15monitoringcapability", the indication is per slot as shown in Tables 10.1-2 and 10.1-3. Alternatively, if the parameter monitoringCapabilityConfig="r16monitoringcapability", the indication is per span as shown in Tables 10.1-2A and 10.1-3A.

[0059] However, if the UE is not provisioned with the parameter monitoringCapabilityConfig, the UE monitors the PDCCH on the serving cell for PDCCH candidates per slot and the maximum number of non-overlapping CCEs.

[0060] The UE may indicate the capability of monitoring the PDCCH according to one or more of the combinations (X, Y) = (2, 2), (4, 3), and (7, 3) for each SCS configuration of μ = 0 and μ = 1. A "span" is the number of consecutive symbols in a slot for which the UE is configured to monitor the PDCCH. Each PDCCH monitoring opportunity is within one span. If the UE monitors the PDCCH on a cell according to the combination (X, Y), the UE supports the PDCCH monitoring opportunity in any symbol of the slot with a minimum time interval of X symbols between the first symbols of two consecutive spans, including between slots. A span starts at the first symbol where the PDCCH monitoring opportunity starts and ends at the last symbol where the PDCCH monitoring opportunity ends, with a maximum number of symbols in the span being Y.

[0061] If the UE indicates the capability of monitoring the PDCCH according to multiple (X, Y) combinations, and the configuration of the search space configured in the UE for PDCCH monitoring on the cell separates every two consecutive PDCCH monitoring spans that are equal to or greater than the value of X for one or more of the multiple combinations (X, Y), the UE shall monitor the PDCCH according to the multiple combinations (X, Y) defined in Table 10.1-2A (Table 10.1-2A) and Table 10.1-3A (Table 10.1-3A).

[0062]

number

[0063] and

[0064]

number

[0065] The UE monitors the PDCCH on the cell according to the combination (X, Y) associated with the maximum number of . The UE expects to monitor the PDCCH according to the same combination (X, Y) in all slots on the active DL Bandwidth Part ("BWP") of the cell.

[0066] The UE's capability of monitoring the PDCCH per slot or per span on the active DL BWP of the serving cell is defined by the maximum number of PDCCH candidates and non-overlapping CCEs that the UE can monitor per slot or per span, respectively, on the active DL BWP of the serving cell.

[0067] According to 3GPP TS 38.213, clause 10.1, for NR Rel-15 / 16, the following details on search space configuration for PDCC monitoring are specified: For each DL BWP configured for the UE in the serving cell, the UE is provided by higher layers with a search space set of S≦10, and for each search space set from the S search space set, the UE is provided by SearchSpace with: · Index of the search space set by searchSpaceId, s, 0 <s<40 Association between a search space set s and a CORESET ρ by the parameter controlResourceSetId or the parameter controlResourceSetId-v1610 The PDCCH monitoring period of the ks slot and the PDCCH monitoring offset of the os slot according to the parameter monitoringSlotPeriodicityAndOffset PDCCH monitoring pattern within a slot, indicating the first symbol of the CORESET within the slot for PDCCH monitoring, according to the parameter monitoringSymbolsWithinSlot · Denote the number of slots in which the search space set s exists per duration, T s <k s Slot Duration The number of PDCCH candidates per CCE aggregation level L with parameters aggregationLevel1, aggregationLevel2, aggregationLevel4, aggregationLevel8, and aggregationLevel16 for CCE aggregation level 1, CCE aggregation level 2, CCE aggregation level 4, CCE aggregation level 8, and CCE aggregation level 16, respectively.

[0068]

number

[0069] An indication that the search space set s is either a Common Search space ("CSS") set or a UE-specific Search space ("USS") set by the parameter searchSpaceType.

[0070] If a search space set s is a CSS set, then the UE is provided by SearchSpace with: Instructions by parameters dci-Format0-0-AndFormat1-0 for monitoring PDCCH candidates for DCI format 0_0 and DCI format 1_0 For DCI format 2_0 and the corresponding CCE aggregation level, an instruction according to parameter dci-Format2-0 to monitor one or two PDCCH candidates or, if the UE is provided with the parameter freqMonitorLocations for a search space set, to monitor one PDCCH candidate per radio bearer ("RB") set. For DCI format 2_1, instruction by parameter dci-Format2-1 to monitor PDCCH candidates For DCI format 2_2, instruction by parameter dci-Format2-2 for monitoring PDCCH candidates For DCI format 2_3, instruction by parameter dci-Format2-3 for monitoring PDCCH candidates For DCI format 2_4, instruction by parameter dci-Format2-4 for monitoring PDCCH candidates For DCI format 2_6, instruction by parameter dci-Format2-6 for monitoring PDCCH candidates

[0071] If the search space set s is a USS set, the UE is provided with the following by SearchSpace: An indication by the parameter dci-Formats to monitor PDCCH candidates of either DCI format 0_0 and DCI format 1_0 or DCI format 0_1 ​​and DCI format 1_1, or An indication via parameter dci-FormatsExt to monitor PDCCH candidates for DCI format 0_0 and DCI format 1_0, or for DCI format 0_1 ​​and DCI format 1_1, or for DCI format 0_2 and DCI format 1_2, or, if the UE indicates the corresponding capability, for DCI format 0_1, DCI format 1_1, DCI format 0_2 and DCI format 1_2, or for DCI format 3_0, or for DCI format 3_1, or for DCI format 3_0 and DCI format 3_1.

[0072] The UE is further provided by SearchSpace with a bitmap with parameter freqMonitorLocations, which, if provided, indicates the index of one or more RB sets in search space set s, where the Most Significant Bit ("MSB") k in the bitmap corresponds to RB set k-1 in the DL BWP. For RB set k indicated in the bitmap, the first Physical Resource Block ("PRB") of the frequency domain monitoring location confined within the RB set is

[0073]

number

[0074] In the above formula,

[0075]

number

[0076] is the index of the first common RB in RB set k (i.e., from 3GPP TS 38.214),

[0077]

number

[0078] is provided by the parameter rb-Offset, or if the parameter rb-Offset is not provided,

[0079]

number

[0080] For each RB set having a corresponding value of 1 in the bitmap, the frequency domain resource allocation pattern of the monitoring location is the first one in the parameter frequencyDomainResources provided by the associated CORESET configuration.

[0081]

number

[0082] The bitwise ordering is determined based on the

[0083] If the parameter monitoringSymbolsWithinSlot instructs the UE to monitor the PDCCH within the same subset of up to three consecutive symbols in all slots in which the UE monitors the PDCCH for all search space sets, then the UE shall not expect a PDCCH SCS other than 15 kHz to be configured if the subset includes at least one symbol after the third symbol.

[0084] The UE does not expect to be provided with the first symbol and a number of consecutive symbols of the CORESET that are PDCCH candidates that map to symbols in different slots.

[0085] The UE shall not expect any two PDCCH monitoring opportunities on an active DL BWP of the same or different search space sets in the same CORESET to be separated by a non-zero number of symbols less than the CORESET period.

[0086] The UE determines the PDCCH monitoring opportunity on the active DL BWP from the PDCCH monitoring period, the PDCCH monitoring offset, and the PDCCH monitoring pattern in the slot. For a search space set s, the UE determines

[0087]

number

[0088] In the case of number n f Number in a frame with

[0089]

number

[0090] The UE determines that a PDCCH monitoring opportunity exists in slot (according to 3GPP TS 38.211).

[0091]

number

[0092] Starting from T s Monitor the PDCCH candidates in the search space set s for consecutive slots and select the next k s -T s Consecutive slots are not monitored for PDCCH candidates in search space set s.

[0093] A USS for a CCE aggregation level L ∈ {1, 2, 4, 8, 16} is defined by a set of PDCCH candidates for CCE aggregation level L.

[0094] With regard to the B52.6 PDCCH monitoring discussion in NR Rel-17, in one embodiment, the multi-slot PDCCH monitoring function is defined using a fixed pattern of N slots. In another embodiment, the multi-slot PDCCH monitoring function is defined using the Rel-16 function (pdcch-Monitoring-r16, (X,Y) span) as a baseline for defining new functions. In a third embodiment, the multi-slot PDCCH monitoring function is defined using a sliding window of N slots to define the multi-slot PDCCH monitoring function.

[0095] The specific values ​​of X, Y, and N may depend on the UE capabilities and the gNB configuration. For example, N may be defined as follows: N=[4] slots for 480 kHz SCS, and N=[8] slots for 960 kHz SCS. In another example, X may be defined as follows: X=[4] slots for 480 kHz SCS, and X[8] slots for 960 kHz SCS.

[0096] In a particular embodiment, using a fixed pattern of slot groups as a baseline for defining new capabilities, each slot group consists of X slots, where the slot groups may be contiguous and non-overlapping, where the capabilities refer to the Blind Detection and / or Control Channel Element ("BD / CCE") budget within Y contiguous [symbols or slots] within each slot group.

[0097] In a particular embodiment, using an (X, Y) span as a baseline for defining a new function, where X is the minimum time interval between the start of two consecutive spans, the function denotes the BD / CCE budget in a span of up to Y consecutive [symbols or slots], where Y≦X.

[0098] In a particular embodiment, when using a sliding window of X slots as a baseline for defining a new function, the function indicates the BD / CCE budget within the sliding window, where the sliding unit of the sliding window is [1] slot.

[0099] With regard to antenna ports and quasi-co-location ("QCL"), the UE may be configured with a list of up to M TCI state configurations in the higher layer parameter PDSCH-Config, where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC, to decode the PDSCH according to the detected PDCCH with DCI for the UE and a given serving cell. Each TCI state includes parameters for configuring the QCL relationship between one or two downlink reference signals and a Demodulation Reference signal ("DM-RS") port of the PDSCH, a DM-RS port of the PDCCH, or a Channel State Information Reference signal ("CSI-RS") port of a CSI-RS resource. Two antenna ports are said to be quasi-co-located if the characteristics of the channel on which the symbols of one antenna port are transmitted can be inferred from the channel on which the symbols of the other antenna port are transmitted. The channel characteristics considered for quasi-colocation include, but are not limited to, Doppler shift, Doppler spread, average delay, delay spread, and / or spatial Rx parameters.

[0100] A QCL relationship is configured by the higher layer parameter qcl-Type1 of the first DL RS and qcl-Type2 of the second DL RS (if configured). For two DL RSs, the QCL types must not be the same, regardless of whether the references are to the same DL RS or to different DL RSs. The pseudo-collocation type corresponding to each DL RS is given by the higher layer parameter qcl-Type in QCL-Info and can take one of the following values: "typeA": {Doppler shift, Doppler spread, average delay, delay spread} "type B": {Doppler shift, Doppler spread} "type C": {Doppler shift, average delay} "typeD": {spatial Rx parameters}

[0101] The UE receives an activation command which is used to map up to eight TCI states to code points of the DCI field "Transmission Configuration Indication" of one Component Carrier and / or Downlink Bandwidth Part ("CC / DL BWP") or a set of CC / DL BWPs, respectively, as described in clause 6.1.3.14 of 3GPP TS 38.321. When a set of TCI state IDs is activated for a set of CC / DL BWPs, the list of corresponding Component Carriers ("CC") is determined by the CC specified in the activation command, and the same set of TCI state IDs is applied to all DL BWPs within the indicated CC.

[0102] If the UE supports two TCI states in a codepoint of the DCI field "Transmission Configuration Indication", the UE may receive an activation command as described in 3GPP TS 38.321, clause 6.1.3.24, which is used to map up to eight combinations of one or two TCI states to a codepoint of the DCI field "Transmission Configuration Indication". The UE is not expected to receive more than eight TCI states in an activation command.

[0103] If the DCI field "Transmission Configuration Indication" is present in DCI format 1_2 and if the number of code points S in the DCI field "Transmission Configuration Indication" of DCI format 1_2 is smaller than the number of TCI code points activated by the activation command, only the code points activated in the first S are applied to DCI format 1_2, as described in 3GPP TS 38.321 clauses 6.1.3.14 and 6.1.3.24.

[0104] If the UE transmits a PUCCH with Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) information in slot n corresponding to a PDSCH carrying an activation command, the indicated mapping between the TCI state and the codepoint of the DCI field “Transmission Configuration Indication” is

[0105]

number

[0106] where m is the SCS configuration for the PUCCH. If the parameter tci-PresentInDCI is set to "enabled" or the parameter tci-PresentDCI-1-2 is configured for the CORESET scheduling the PDSCH and the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than timedurationForQCL, if applicable, then after the UE receives an initial higher layer configuration of the TCI state but before receiving an activation command, the UE may assume that the DM-RS port of the PDSCH of the serving cell is quasi-collocated with the Synchronization Signal / Physical Broadcast Channel ("SS / PBCH") block determined in the initial access procedure for parameter qcl-Type set to "typeA" and, if applicable, also for parameter qcl-Type set to "typeD".

[0107] For default beam determination, if the UE is configured with higher layer parameter tci-PresentInDCI set to "enabled" for the CORESET scheduling the PDSCH, the UE shall assume that a TCI field is present in DCI format 1_1 of the PDCCH transmitted on the CORESET. If the UE is configured with higher layer parameter tci-PresentDCI-1-2 for the CORESET scheduling the PDSCH, the UE shall assume that a TCI field with the DCI field size indicated by parameter tci-PresentDCI-1-2 is present in DCI format 1_2 of the PDCCH transmitted on the CORESET. If the PDSCH is scheduled with a DCI format in which the TCI field is not present and the time offset between the reception of the DL DCI and the corresponding PDSCH of the serving cell is greater than or equal to a threshold timedurationForQCL, if applicable, where the threshold is based on the reported UE capabilities (see 3GPP TS 38.306) for determining quasi-co-location of PDSCH antenna ports, the UE shall assume that the TCI state or QCL assumption of the PDSCH is identical to the TCI state or QCL assumption applied to the CORESET used for PDCCH transmission within the active BWP of the serving cell.

[0108] If the PDSCH is scheduled by a DCI format in which the TCI field is present, the TCI field in the DCI in the scheduling component carrier refers to the TCI state activated in the scheduled component carrier or DL ​​BWP, and the UE shall use the parameter TCI state according to the value of the "Transmission Configuration Indication" field in the detected PDCCH with DCI to determine the PDSCH antenna port quasi-co-location. If the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than a threshold timedurationForQCL, the UE may assume that the DM-RS port of the PDSCH of the serving cell is quasi-co-located with the RS of the TCI state with respect to the QCL type parameter given by the specified TCI state, where the threshold is based on the reported UE capabilities (see 3GPP TS 38.306).

[0109] If the UE is configured with a single slot PDSCH, the indicated TCI state should be based on the TCI state activated in the slot with the scheduled PDSCH. If the UE is configured with a multi-slot PDSCH, the indicated TCI state should be based on the TCI state activated in the first slot with the scheduled PDSCH, and the UE expects the activated TCI state to be the same across slots with the scheduled PDSCH. If the UE is configured with a CORESET associated with a search space set for cross-carrier scheduling and the UE is not configured with the parameter enableDefaultBeamForCCS, the UE expects that the parameter tci-PresentInDCI is set to "enabled" or the parameters tci-PresentDCI-1-2 are set for CORESET, and if one or more of the TCI states configured for the serving cells scheduled by the search space set include the parameter qcl-Type set to "typeD", the UE expects the time offset between the reception of a PDCCH detected in the search space set and the corresponding PDSCH to be equal to or greater than the threshold timedurationForQCL.

[0110] Independently of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, if the offset between reception of DL DCI and the corresponding PDSCH is smaller than the threshold timedurationForQCL and at least one TCI state configured for the serving cell of the scheduled PDSCH includes qcl-Type set to "typeD", the UE may assume that the DM-RS port of the PDSCH of the serving cell is quasi-colocated with the RS with respect to the QCL parameters used for the PDCCH quasi-colocation indication of the CORESET associated to the monitored search space with the lowest controlResourceSetId in the latest slot in which one or more CORESETs in the active BWP of the serving cell are monitored by the UE. In this case, if the parameter qcl-Type set to "typeD" of the PDSCH DM-RS differs from that of the overlapping PDCCH DM-RS in at least one symbol, the UE is expected to prioritize the reception of the PDCCH associated to that CORESET. This also applies to the case of intra-band CA (when the PDSCH and CORESET are on different component carriers).

[0111] If the UE is configured with the parameter enableDefaultTCIStatePerCORESETPoolIndex and the UE is configured with the higher layer parameter PDCCH-Config containing two different values ​​of CORESETPoolIndex in different ControlResourceSets, the UE may assume that the DM-RS port of the PDSCH associated with the value of the parameter CORESETPoolIndex of the serving cell is quasi-co-located with the RS with respect to the QCL parameter used for the PDCCH quasi-co-location indication of the CORESET associated with the monitored search space having the lowest controlResourceSetId in the CORESET, and one or more CORESETs associated with the same value of CORESETPoolIndex as the PDCCH scheduling that PDSCH in the active BWP of the serving cell in the latest slot are monitored by the UE. In this case, if the "QCL-TypeD" of a PDSCH DM-RS is different from the "QCL-TypeD" of an overlapping PDCCH DM-RS in at least one symbol and they are associated to the same CORESETPoolIndex, the UE is expected to prioritize reception of the PDCCH associated to that CORESET. This is also true for the intra-band CA case (when the PDSCH and CORESET are on different component carriers).

[0112] If the UE is configured with the parameter enableTwoDefaultTCI-States and at least one TCI codepoint indicates two TCI states, the UE may assume that the DM-RS port of the PDSCH or the PDSCH transmission opportunity of the serving cell is quasi-collocated with the RS with respect to the QCL parameter associated with the TCI state corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states. If the UE is configured with the higher layer parameter repetitionScheme set to "tdmSchemeA" or with the higher layer parameter repetitionNumber, the mapping of TCI states to PDSCH transmission opportunities is determined according to clause 5.1.2.1 by replacing the indicated TCI state with the TCI state corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states based on the activated TCI state in the slot with the first PDSCH transmission opportunity. In this case, the UE is expected to prioritize reception of the PDCCH associated to that CORESET if the "QCL-TypeD" in both TCI states corresponding to the lowest TCI codepoint among the two different TCI states differs from the "QCL-TypeD" of the overlapping PDCCH DM-RS in at least one symbol. This also applies in the case of intra-band CA (when the PDSCH and CORESET are on different component carriers).

[0113] In all the above cases, if none of the TCI states configured for the serving cell of a scheduled PDSCH is configured with qcl-Type set to "typeD", the UE shall derive other QCL assumptions from the TCI state indicated for that scheduled PDSCH, regardless of the time offset between reception of the DL DCI and the corresponding PDSCH.

[0114] If a PDCCH carrying a scheduling DCI is received on one component carrier and a PDSCH scheduled by that DCI is on another component carrier, and the UE is configured with the parameter enableDefaultBeam-ForCCS, the parameter timedurationForQCL is determined based on the subcarrier spacing of the scheduled PDSCH. If μPDCCH<μPDSCH, then the additional timing delay

[0115]

number

[0116] is added to the value of timeDurationForQCL, where d is defined in 3GPP TS 38.214, clause 5.2.1.5.1a-1, and otherwise d is zero.

[0117] In both cases, if the offset between reception of the DL DCI and the corresponding PDSCH is smaller than a threshold timedurationForQCL, and if no TCI field is present in the DL DCI, the UE shall derive the QCL assumption for the scheduled PDSCH from the activated TCI state with the lowest ID applicable for the PDSCH in the active BWP of the scheduled cell.

[0118] Beam management procedures in NR Rel-15 / 16 include initial beam acquisition, beam training, beam refinement, and beam failure detection and recovery. Beam management procedures heavily rely on constant / periodic exchange of reference signals between the network (e.g., gNB) and the UE for both UL and DL control / data channel transmissions, and corresponding measurement reports. Thus, the latency and overhead involved in such procedures are very high. Moreover, the problem is expected to be even more pronounced in the high frequency range, where the beams need to be very narrow to accommodate various use cases.

[0119] Therefore, we agree to further consider new parameter values ​​for at least the parameter maxNumberRxTxBeamSwitchDL. In certain embodiments, if the PDCCH triggering at 120 kHz or 480 kHz has a smaller subcarrier spacing than the AP-CSI-RS, there may be an additional beam switching time delay d for triggering the AP-CSI-RS.

[0120] It is agreed to consider whether / how to introduce beam switching gaps between signals / channels. In case of multi-PDSCH scheduling with single DCI, consider the QCL assumption that the UE should apply per PDSCH when the scheduling offsets of some of the scheduled PDSCHs are less than timedurationForQCL and some PDSCHs have scheduling offsets equal to or greater than timedurationForQCL. In case of multi-PDSCH scheduling with single DCI, consider the QCL assumption that the UE should apply per PDSCH when the scheduling offsets of all scheduled PDSCHs are less than timedurationForQCL. Note: If the current Rel-16 behavior is extended to multiple PDSCH scheduling, this may result in different QCL assumptions per PDSCH since the CORESET with the lowest ID may differ per slot, which may result in different TCI conditions per slot.

[0121] The solutions described herein disclose, among other things, procedures and signaling for multiple default beams / TCIs / QCLs for multiple PDSCH / PUSCH scheduling with a single DCI, where a CORESET can be associated with multiple beams / TCIs / QCLs (e.g., in the case of single or multiple TRPs) and corresponding time periods in which each of the default beams / TCIs / QCLs applies to multiple PDSCH / PUSCH transmissions. In various embodiments, in the case of multi-slot PDCCH monitoring, the CORESET can be monitored on different beams for different monitoring occasions within a PDCCH monitoring period.

[0122] According to an embodiment of the first solution, the UE is configured with a CORESET, which is associated with multiple TCIs / QCLs / beams to be activated by the MAC CE and time periods (sometimes referred to as QCLduration1, QCLduration2...) during which each of the TCIs / QCLs / beams can be applied as a default beam for multiple PDSCHs / PUSCHs scheduled by a single DCI.

[0123] 3 illustrates an example frame structure 300 illustrating updating TCI / QCL / beams of multiple PDSCHs based on multiple TCI / QCL / beams activated for scheduling CORESET (when TCI is not present in DCI and scheduling offset is greater than or equal to timedurationForQCL), in accordance with an embodiment of the present disclosure, where frame structure 300 illustrates DL / UL communication between UE 205 and RAN node 207.

[0124] In one implementation of the first solution, the following applies when multiple PDSCHs are scheduled with a DCI format in which the TCI field is absent, and the time offset between A) reception of the DL DCI and B) all corresponding PDSCHs of the serving cell is equal to or greater than the threshold timedurationForQCL. Note that the threshold timedurationForQCL is based on the reported UE capabilities, if applicable. In such a scenario, to determine the quasi-co-location of the PDSCH antenna ports, the UE assumes that the TCI state or QCL assumption for each of the PDSCHs is based on the TCI / QCL / beam (i.e., associated to the CORESET used for PDCCH transmission within the active BWP of the serving cell) that has a TCIduration equal to or greater than the scheduling offset of the PDSCH, for the scheduling PDCCH.

[0125] A TCI / QCL / beam is applicable as long as the TCIduration has not expired for that TCI / QCL / beam. When the TCIduration for that TCI / QCL / beam expires, the next TCI / QCL / beam is applied to the subsequent PDSCH.

[0126] As shown in FIG. 3, DCI 301 is received by UE 205 on a PDCCH. Here, the PDCCH schedules three PDSCH transmissions (i.e., a first PDSCH 303 (denoted as “PDSCH1”), a second PDSCH 305 (denoted as “PDSCH2”), and a third PDSCH 307 (denoted as “PDSCH3”)) for which no TCI field is present, and no TCI field is present in DCI 301. Since a time offset 309 between DCI 301 and first PDSCH 303 is equal to or greater than a threshold timedurationForQCL, UE 205 can process DCI 301 and switch beams before receiving first PDSCH 303. Thus, UE 205 applies the TCI / QCL / beams activated for the scheduling CORESET, i.e., the CORESET used for the PDCCH transmissions including DCI 301.

[0127] Thus, the UE 205 receives the first PDSCH 303 and the second PDSCH 305 using a first beam (e.g., associated with QCL1, i.e., the first QCL activated for the scheduling CORESET). However, because QCLduration1 expires before the third PDSCH 307 is scheduled, the UE 205 switches to the next beam (i.e., QCL assumption) and receives the third PDSCH 307 using a second beam (e.g., associated with QCL2, i.e., the second QCL activated for the scheduling CORESET).

[0128] 4 illustrates an example frame structure 400 illustrating updating TCI / QCL / beams of multiple PDSCHs based on TCI / QCL / beams activated for the lowest CORESET ID (when TCI is not present in DCI and scheduling offset is less than timedurationForQCL) in accordance with an embodiment of the present disclosure, where frame structure 400 illustrates DL / UL communication between UE 205 and RAN node 207.

[0129] In another implementation of the first solution, the following applies when multiple PDSCHs are scheduled by DCI format (TCI field may or may not be present), and the time offset between reception of DL DCI and all corresponding PDSCHs of the serving cell is less than a threshold timedurationForQCL. Note that the threshold timedurationForQCL is based on the reported UE capabilities, if applicable. In such a scenario, to determine the quasi-co-location of PDSCH antenna ports, the UE 205 assumes that the TCI state or QCL assumption for each of the PDSCHs is based on the TCI / QCL / beam with a TCIduration equal to or greater than the scheduling offset of the PDSCH for the scheduling PDCCH (i.e., associated with the lowest CORESET ID used for PDCCH transmission within the active BWP of the serving cell).

[0130] A TCI / QCL / beam is applicable as long as the TCIduration has not expired for that TCI / QCL / beam. When the TCIduration for that TCI / QCL / beam expires, the next TCI / QCL / beam is applied to the subsequent PDSCH.

[0131] As shown in FIG. 4, DCI 401 is received by UE 205 on PDCCH. Here, PDCCH schedules three PDSCH transmissions (i.e., first PDSCH 403 (denoted as “PDSCH1”), second PDSCH 405 (denoted as “PDSCH2”), and third PDSCH 407 (denoted as “PDSCH3”)). Because the time offset 409 between DCI 401 and first PDSCH 403 is less than the threshold timedurationForQCL, UE 205 may not be able to process DCI 401 and switch beams before reception of first PDSCH 403. Therefore, UE 205 applies the TCI / QCL / beam activated for the lowest CORESET ID. It does not matter if the TCI field is present in DCI 401 or not, because reception of all scheduled PDSCHs occurs before timedurationForQCL expires.

[0132] Thus, the UE 205 receives the first PDSCH 403 and the second PDSCH 405 using a first beam (e.g., associated with QCL1, i.e., the first QCL activated for the lowest CORESET ID). However, because QCLduration1 expires before the third PDSCH 407 is scheduled, the UE 205 switches to the next beam (i.e., QCL assumption) and receives the third PDSCH 407 using a second beam (e.g., associated with QCL2, i.e., the second QCL activated for the lowest CORESET ID).

[0133] 5 illustrates an example frame structure 500 showing updating the TCI / QCL / beams of multiple PDSCHs based on the TCI / QCL / beams activated for the lowest CORESET ID of some PDSCHs, while activating multiple TCI / QCL / beams to schedule the CORESET for the remaining PDSCHs (when no TCI is present in the DCI), in accordance with an embodiment of the present disclosure, where the frame structure 500 illustrates DL / UL communication between a UE 205 and a RAN node 207.

[0134] In another implementation of the first solution, the following applies when multiple PDSCHs are scheduled by a DCI format in which the TCI field is absent, and the time offset between the reception of the DL DCI and some of the corresponding PDSCHs of the serving cell is less than a threshold timedurationForQCL. Note that the threshold timedurationForQCL is based on the reported UE capabilities, if applicable. In such a scenario, to determine the quasi-co-location of the PDSCH antenna ports, the UE 205 assumes that the TCI state or QCL assumption for each of those corresponding PDSCHs is based on the TCI / QCL / beams (i.e., associated with the lowest CORESET ID used for PDCCH transmission within the active BWP of the serving cell) that have a TCIduration greater than or equal to the scheduling offset of their corresponding PDSCHs, for the scheduling PDCCH.

[0135] A TCI / QCL / beam is applicable as long as the TCIduration has not expired for that TCI / QCL / beam. When the TCIduration for that TCI / QCL / beam expires, the next TCI / QCL / beam is applied to the subsequent PDSCH.

[0136] For the remaining PDSCHs whose time offset is greater than or equal to the threshold timedurationForQCL, the UE assumes that the TCI state or QCL assumption for each of the PDSCHs is based on the TCI / QCL / beam (associated with the scheduling CORESET used for PDCCH transmission within the serving cell's active BWP) that has a TCIduration greater than or equal to the scheduling offset of the PDSCH, for the scheduling PDCCH.

[0137] As shown in FIG. 5, DCI 501 is received by UE 205 on a PDCCH. Here, the PDCCH schedules three PDSCH transmissions (i.e., a first PDSCH 503 (denoted as “PDSCH1”), a second PDSCH 505 (denoted as “PDSCH2”), and a third PDSCH 507 (denoted as “PDSCH3”)), and no TCI field is present in DCI 501. Because the time offset 509 between DCI 501 and first PDSCH 503 is less than a threshold timedurationForQCL, UE 205 can process DCI 501 and switch beams before reception of first PDSCH 503. Thus, UE 205 applies the TCI / QCL / beam activated for the lowest CORESET ID for at least reception of first PDSCH 503. However, because the time offset 509 between the DCI 501 and the last scheduled PDSCH (i.e., the third PDSCH 507) is greater than or equal to the threshold timedurationForQCL, the UE 205 may process the DCI 501 and switch beams before receiving the third PDSCH 507. Thus, the UE 205 applies the TCI / QCL / beam activated for the scheduling CORESET, (i.e., the CORESET used for the PDCCH transmission that includes the DCI 501) to all PDSCHs scheduled after the threshold timedurationForQCL (including the third PDSCH 607).

[0138] Thus, the UE 205 uses the first beam (e.g., QCL1, i.e., associated with the first QCL activated for the scheduling CORESET) to receive the first PDSCH 503 and the second PDSCH 505. However, because the time offset 509 between the DCI 501 and the last scheduled PDSCH (i.e., the third PDSCH 507) is greater than or equal to the threshold timedurationForQCL, the UE 205 switches to the beam associated with the scheduling CORESET (i.e., applicable based on the QCLduration) and receives the third PDSCH 507 using the beam associated with the QCL activated for the scheduling CORESET.

[0139] 6 illustrates an example frame structure 600 for updating the TCI / QCL / beam of multiple PDSCHs based on the TCI / QCL / beams activated for the lowest CORESET ID of some PDSCHs, while applying the TCI / QCL / beam indicated by the DCI for the remaining PDSCHs (TCIs present in the DCI), according to an embodiment of the present disclosure, where the frame structure 600 illustrates DL / UL communication between a UE 205 and a RAN node 207.

[0140] In another implementation of the first solution, the following applies when multiple PDSCHs are scheduled by the DCI format (TCI field is present), and the time offset between reception of the DL DCI and some of the corresponding PDSCHs of the serving cell is less than a threshold timedurationForQCL. Note that the threshold timedurationForQCL is based on the reported UE capabilities, if applicable. In such a scenario, to determine the quasi-co-location of PDSCH antenna ports, the UE 205 assumes that the TCI state or QCL assumption for each of those corresponding PDSCHs is based on the TCI / QCL / beams (associated with the lowest CORESET ID used for PDCCH transmission within the active BWP of the serving cell) that, for the scheduling PDCCH, have a TCIduration equal to or greater than the scheduling offset of their corresponding PDSCHs.

[0141] A TCI / QCL / beam is applicable as long as the TCIduration has not expired for that TCI / QCL / beam. When the TCIduration for that TCI / QCL / beam expires, the next TCI / QCL / beam is applied to the subsequent PDSCH.

[0142] For the remaining PDSCHs whose time offset is greater than or equal to the threshold timedurationForQCL, the UE applies the TCI state or QCL assumption to the remaining PDSCHs indicated by the TCI codepoints in the scheduling DCI format.

[0143] As shown in FIG. 6, DCI 601 is received by UE 205 on a PDCCH. Here, the PDCCH schedules three PDSCH transmissions (i.e., a first PDSCH 603 (denoted as “PDSCH1”), a second PDSCH 605 (denoted as “PDSCH2”), and a third PDSCH 607 (denoted as “PDSCH3”)), and no TCI field is present in DCI 601. Because the time offset 609 between DCI 601 and the first PDSCH 603 is less than a threshold timedurationForQCL, UE 205 can process DCI 601 and switch beams before reception of the first PDSCH 603. Thus, UE 205 applies the TCI / QCL / beam activated for the lowest CORESET ID for at least reception of the first PDSCH 603. However, because the time offset 609 between the DCI 601 and the last scheduled PDSCH (i.e., the third PDSCH 607) is greater than or equal to the threshold timedurationForQCL, the UE 205 may process the DCI 601 and switch beams before receiving the third PDSCH 607. Thus, the UE 205 applies the TCI / QCL / beam indicated in the DCI 601 to all PDSCHs scheduled after the threshold timedurationForQCL (including the third PDSCH 607).

[0144] Thus, the UE 205 receives the first PDSCH 603 and the second PDSCH 605 using a first beam (e.g., QCL1, i.e., associated with the first QCL activated for the scheduling CORESET). However, because the time offset 609 between the DCI 601 and the second PDSCH 605 is equal to or greater than the threshold timedurationForQCL, the UE 205 switches to the beam indicated by the DCI 601 (i.e., TCI state or QCL assumption) and receives the second PDSCH 605 and the third PDSCH 607 using the beam according to the DCI 601. Here, the second PDSCH 605 is received using the second beam (denoted as “TCI1”) indicated by the TCI field in the DCI 601, and the third PDSCH 607 is received using the third beam (denoted as “TCI2”) indicated by the TCI field in the DCI 601.

[0145] According to an embodiment of the second solution, the UE 205 is configured with a CORESET, which is associated with multiple TCIs / QCLs / beams to be activated by the MAC CE and the durations (which may be referred to as QCLduration1, QCLduration2...) that each of the TCIs / QCLs / beams is applicable for monitoring its CORESET on multiple monitoring occasions.

[0146] 7 illustrates an example frame structure 700 illustrating PDCCH monitoring using different TCI / QCL / beams for the same CORESET at different monitoring occasions within a PDCCH monitoring period, in accordance with an embodiment of the present disclosure, where frame structure 700 illustrates DL / UL communication between a UE 205 and a RAN node 207.

[0147] In one implementation of the second solution, the UE 205 is configured with multiple TCIs / QCLs / beams activated by the MAC CE of the CORESET to monitor at different monitoring occasions within a PDCCH monitoring period and / or a multi-slot PDCCH period. The associated duration / applicability time is used to determine which TCI / QCL / beam is used to monitor the CORESET at a given monitoring occasion. For each period, the same association of CORESET monitoring occasions and corresponding TCIs / QCLs / beams applies, as shown in Figure 7.

[0148] 8 illustrates an example frame structure 800 illustrating PDCCH monitoring using different TCI / QCL / beams for the same CORESET at different monitoring occasions having an association pattern period shorter than the PDCCH monitoring period, in accordance with an embodiment of the present disclosure, where frame structure 800 illustrates DL / UL communication between a UE 205 and a RAN node 207.

[0149] In another implementation of the second solution, the UE 205 is configured with multiple TCIs / QCLs / beams activated by the MAC CE of the CORESET to monitor at different monitoring occasions, and the association pattern can be repeated with a period independent of the PDCCH monitoring period. As shown in Figure 8, the association pattern between the CORESET monitoring occasions and the corresponding TCIs / QCLs / beams can be configured for a period that can have a duration shorter than the PDCCH monitoring period.

[0150] 9 illustrates an example frame structure 900 illustrating PDCCH monitoring using different TCI / QCL / beams for the same CORESET at different monitoring occasions having an association pattern period longer than the PDCCH monitoring period, in accordance with an embodiment of the present disclosure, where frame structure 900 illustrates DL / UL communication between a UE 205 and a RAN node 207.

[0151] In a further implementation of the second solution, the UE 205 is configured with multiple TCIs / QCLs / beams activated by MAC CEs of the CORESET to monitor at different monitoring occasions, and the association pattern can be repeated with a period independent of the PDCCH monitoring period. As shown in Figure 9, a period larger than the PDCCH monitoring period can be configured to repeat the same association pattern.

[0152] In another implementation of the second solution, the UE 205 is associated with TCI / QCL / beams of multiple TRPs (two or more) within the QCL duration, but different combinations of TCI / QCL / beams of multiple TRPs may be used within the PDCCH monitoring. Such configurations are activated by the MAC CE for the CORESET to monitor at different monitoring occasions, but any combination of associations of pattern periods and PDCCH monitoring periods shown in Figures 7 to 9 may be used.

[0153] In some embodiments of the second solution, the UE 205 is associated with multiple beams associated with multiple TRPs based on the lowest CORESET ID associated with each of the CORESETPoolIndexes (i.e., associated with the TRP). In some embodiments of the second solution, if multiple TCIs / QCLs / beams from multiple TRPs can be applied within a certain period, the QCL duration 0 of the first default beam is common regardless of the associated TRP, and the QCL duration 1 of the second default beam is common regardless of the associated TRP. In some embodiments of the second solution, multiple TRP TCIs / QCLs / beams sets can be utilized to improve the reliability / coverage of the same CORESET within a certain period. These multiple TRP TCIs / QCLs / beams sets are switched after the corresponding QCL durations expire.

[0154] 10 illustrates a user equipment device 1000 that may be used to associate multiple default beams for multiple PDSCH / PUSCHs and monitor the same CORESET on different beams at different monitoring occasions according to an embodiment of the present disclosure. In various embodiments, the user equipment device 1000 is used to implement one or more of the solutions described above. The user equipment device 1000 may be an embodiment of the remote unit 105, UE 205, and / or user equipment device 1000 described above. Additionally, the user equipment device 1000 may include a processor 1005, a memory 1010, an input device 1015, an output device 1020, and a transceiver 1025.

[0155] In some embodiments, the input device 1015 and the output device 1020 are combined into a single device, such as a touch screen. In particular embodiments, the user equipment device 1000 may not include the input device 1015 and / or the output device 1020. In various embodiments, the user equipment device 1000 may include one or more of the processor 1005, the memory 1010, and the transceiver 1025 and may not include the input device 1015 and / or the output device 1020.

[0156] As shown, the transceiver 1025 includes at least one transmitter 1030 and at least one receiver 1035. In some embodiments, the transceiver 1025 communicates with one or more cells (or wireless coverage areas) supported by one or more base units 121. In various embodiments, the transceiver 1025 is operable in an unlicensed spectrum. Additionally, the transceiver 1025 may include multiple UE panels supporting one or more beams. Additionally, the transceiver 1025 may support at least one network interface 1040 and / or application interface 1045. The application interface 1045 may support one or more APIs. The network interface 1040 may support 3GPP reference points such as Uu, N1, and PC5. As will be appreciated by one skilled in the art, other network interfaces 1040 may be supported.

[0157] In one embodiment, the processor 1005 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 1005 may be a microcontroller, microprocessor, central processing unit ("CPU"), graphics processing unit ("GPU"), co-processor, field programmable gate array ("FPGA"), or similar programmable controller. In some embodiments, the processor 1005 executes instructions stored in the memory 1010 to perform the methods and routines described herein. The processor 1005 is communicatively coupled to the memory 1010, the input device 1015, the output device 1020, and the transceiver 1025.

[0158] In various embodiments, the processor 1005 controls the user equipment device 1000 to implement the UE behaviors described above. In particular embodiments, the processor 1005 may include an application processor (also known as a “main processor”) that manages application domains and operating system (“OS”) functions, and a baseband processor (also known as a “baseband radio processor”) that manages radio functions.

[0159] In various embodiments, the transceiver 1025 receives a CORESET configuration from the RAN, the CORESET configuration indicating a plurality of beams (or TCI states or QCL assumptions) and corresponding durations per beam indicated for at least a CORESET ID. Through the transceiver 1025, the processor 1005 monitors at least one CORESET at different PDCCH monitoring occasions using different beams, and receives a first CORESET within a PDCCH transmission, the first CORESET scheduling a plurality of physical channel transmissions (i.e., PDSCH and / or PUSCH). Further, the processor 1005 communicates with the RAN over a plurality of scheduled physical channels using a plurality of beams associated with the lowest CORESET ID configured for the device, and communicating with the RAN over a plurality of scheduled physical channels includes receiving a downlink transmission, transmitting an uplink transmission, or a combination thereof.

[0160] In some embodiments, the first apparatus is configured with a time period for a QCL, and the multiple physical channel transmissions are scheduled by a single DCI that does not include a TCI field, and a time offset between receipt of the DCI and the multiple physical channel transmissions is equal to or greater than the time period of the QCL. In such embodiments, communicating with the RAN includes applying a default beam (i.e., a QCL assumption) associated with the first CORESET (i.e., a CORESET used for the PDCCH transmission), where the TCI period of the default beam is equal to or greater than the time offset between receipt of the DCI and the multiple physical channel transmissions.

[0161] In a particular embodiment, the first device applies at least the second default beam when communicating with the RAN over the multiple scheduled physical channels, in such an embodiment, the default beam for each scheduled instance of the physical channel is determined based on a time period associated with the default beam.

[0162] In some embodiments, the first apparatus is configured with a time period for a QCL, and the multiple physical channel transmissions are scheduled by a single DCI, and a time offset between receipt of the DCI and the multiple physical channel transmissions is less than the time period of the QCL. In such embodiments, communicating with the RAN on the multiple scheduled physical channels includes applying multiple default beams associated with the first CORESET, where a TCI period of the default beam is greater than or equal to the time offset between receipt of the DCI and the multiple physical channel transmissions.

[0163] In a particular embodiment, a default beam for each scheduled instance of a physical channel is determined based on a time period associated with the default beam.

[0164] In some embodiments, the first device is configured with a time period for a QCL, and the multiple physical channel transmissions are scheduled by a single DCI that does not include a TCI field, and a time offset between receipt of the DCI and a first portion (or a subset) of the multiple physical channel transmissions is less than the time period of the QCL. In such embodiments, communicating with the RAN includes applying a default beam associated with the lowest CORESET ID for the first portion of the multiple physical channel transmissions and switching to a beam associated with the first CORESET for the remaining portion of the multiple physical channel transmissions.

[0165] In some embodiments, the first device is configured with a time period of QCL, the multiple physical channel transmissions are scheduled by a single DCI including a TCI field indicating a set of beams, a time offset between receipt of the DCI and a first portion (or a subset) of the multiple physical channel transmissions is less than the time period of QCL, and communicating with the RAN includes applying a default beam associated with the lowest CORESET ID for the first portion of the multiple physical channel transmissions and switching to the set of beams indicated by the DCI for the remaining portion of the multiple physical channel transmissions.

[0166] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is equal to the period of the PDCCH monitoring opportunity. In such embodiments, for each PDCCH monitoring opportunity (i.e., monitoring period), the same association of beams for monitoring the CORESET is applied within the PDCCH monitoring period.

[0167] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is smaller than the period of the PDCCH monitoring opportunity. In such embodiments, for each PDCCH monitoring opportunity, the same association of beams for monitoring the CORESET is applied within the PDCCH monitoring period.

[0168] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is greater than the period of the PDCCH monitoring opportunity. In such embodiments, the association of beams for monitoring the CORESET is applied over multiple PDCCH monitoring periods.

[0169] In some embodiments, the CORESET configuration includes multiple beams (or TCI states or QCL assumptions).

[0170] The memory 1010, in one embodiment, is a computer-readable storage medium. In some embodiments, the memory 1010 includes a volatile computer storage medium. For example, the memory 1010 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, the memory 1010 includes a non-volatile computer storage medium. For example, the memory 1010 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 1010 includes both volatile and non-volatile computer storage media.

[0171] In some embodiments, memory 1010 stores data related to associating multiple default beams for multiple PDSCH / PUSCHs and monitoring the same CORESET on different beams at different monitoring occasions. For example, memory 1010 may store various parameters, panel / beam configurations, resource allocations, policies, etc., as described above. In certain embodiments, memory 1010 also stores program code and associated data, such as an operating system or other controller algorithms running on device 1000.

[0172] The input device 1015, in one embodiment, may include any known computer input device including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 1015 may be integrated with the output device 1020, for example as a touch screen or similar touch-sensitive display. In some embodiments, the input device 1015 includes a touch screen such that text may be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 1015 includes two or more different devices, such as a keyboard and a touch panel.

[0173] The output device 1020, in one embodiment, is designed to output visual, auditory, and / or tactile signals. In some embodiments, the output device 1020 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 1020 may include, but is not limited to, a liquid crystal display ("LCD"), a light emitting diode ("LED") display, an organic LED ("OLED") display, a projector, or similar display device capable of outputting images, text, and the like to a user. As another non-limiting example, the output device 1020 may include a wearable display that is separate from, but communicatively coupled to, the remainder of the user equipment device 1000, such as a smart watch, smart glasses, a head-up display, and the like. Additionally, the output device 1020 may be a component of a smartphone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, and the like.

[0174] In certain embodiments, the output device 1020 includes one or more speakers for generating sound. For example, the output device 1020 may generate an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 1020 includes one or more haptic devices for generating vibration, movement, or other haptic feedback. In some embodiments, all or a portion of the output device 1020 may be integrated with the input device 1015. For example, the input device 1015 and the output device 1020 may form a touch screen or similar touch-sensitive display. In other embodiments, the output device 1020 may be located near the input device 1015.

[0175] The transceiver 1025 communicates with one or more network functions of a mobile communications network via one or more access networks. The transceiver 1025 operates under the control of the processor 1005 to transmit and receive messages, data, and other signals. For example, the processor 1005 may selectively activate the transceiver 1025 (or a portion thereof) at particular times to transmit and receive messages.

[0176] The transceiver 1025 includes at least a transmitter 1030 and at least one receiver 1035. One or more transmitters 1030 may be used to provide UL communication signals, such as UL transmissions described herein, to the base unit 121. Similarly, one or more receivers 1035 may be used to receive DL communication signals from the base unit 121, as described herein. Although only one transmitter 1030 and one receiver 1035 are shown, the user equipment device 1000 may have any suitable number of transmitters 1030 and receivers 1035. Furthermore, the transmitter 1030 and receiver 1035 may be any suitable type of transmitter and receiver. In one embodiment, the transceiver 1025 includes a first transmitter / receiver pair used to communicate with a mobile communication network over a licensed radio spectrum and a second transmitter / receiver pair used to communicate with a mobile communication network over an unlicensed radio spectrum.

[0177] In certain embodiments, a first transmitter / receiver pair used to communicate with a mobile communications network over a licensed radio spectrum and a second transmitter / receiver pair used to communicate with a mobile communications network over an unlicensed radio spectrum may be combined into a single transceiver unit, such as a single chip that performs functions for use in both the licensed and unlicensed radio spectrum. In some embodiments, the first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, a particular transceiver 1025, transmitter 1030, and receiver 1035 may be implemented as physically separate components that access shared hardware and / or software resources, such as, for example, a network interface 1040.

[0178] In various embodiments, one or more transmitters 1030 and / or one or more receivers 1035 may be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-chip, an application specific integrated circuit ("ASIC"), or other type of hardware component. In particular embodiments, one or more transmitters 1030 and / or one or more receivers 1035 may be implemented and / or integrated into a multi-chip module. In some embodiments, other components, such as a network interface 1040 or other hardware components / circuits, may be integrated into a single chip with any number of transmitters 1030 and / or receivers 1035. In such embodiments, the transmitters 1030 and receivers 1035 may be logically configured as a transceiver 1025 using another common control signal, or as modular transmitters 1030 and receivers 1035 implemented in the same hardware chip or multi-chip module.

[0179] 11 illustrates a network apparatus 1100 that may be used to associate multiple default beams for multiple PDSCH / PUSCHs and monitor the same CORESET on different beams at different monitoring occasions according to an embodiment of the present disclosure. In an embodiment, the network apparatus 1100 may be an implementation of a RAN device, such as the base unit 121 and / or the RAN node 207, as described above. Additionally, the network apparatus 1100 may include a processor 1105, a memory 1110, an input device 1115, an output device 1120, and a transceiver 1125.

[0180] In some embodiments, the input device(s) 1115 and the output device(s) 1120 are combined into a single device, such as a touch screen. In particular embodiments, the network apparatus 1100 may not include the input device(s) 1115 and / or the output device(s) 1120. In various embodiments, the network apparatus 1100 may include one or more of the processor 1105, the memory 1110, and the transceiver 1125 and may not include the input device(s) 1115 and / or the output device(s) 1120.

[0181] As shown, the transceiver 1125 includes at least one transmitter 1130 and at least one receiver 1135, where the transceiver 1125 communicates with one or more remote units 105. Additionally, the transceiver 1125 may support at least one network interface 1140 and / or an application interface 1145. The application interface 1145 may support one or more APIs. The network interface 1140 may support 3GPP reference points such as Uu, N1, N2, and N3. As will be appreciated by one skilled in the art, other network interfaces 1140 may be supported.

[0182] In one embodiment, the processor 1105 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 1105 may be a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or similar programmable controller. In some embodiments, the processor 1105 executes instructions stored in the memory 1110 to perform the methods and routines described herein. The processor 1105 is communicatively coupled to the memory 1110, the input device 1115, the output device 1120, and the transceiver 1125.

[0183] In various embodiments, the network device 1100 is a RAN node (e.g., gNB) that communicates with one or more UEs as described herein. In such embodiments, the processor 1105 controls the network device 1100 to perform the RAN behavior described above. When operating as a RAN node, the processor 1105 may include an application processor (also known as a “main processor”) that manages application domains and operating system (“OS”) functions, and a baseband processor (also known as a “baseband radio processor”) that manages radio functions.

[0184] In some embodiments, via the transceiver 1125, the processor 1105 transmits a CORESET configuration to the UE, the CORESET configuration indicating a plurality of beams (or TCI states or QCL assumptions) and corresponding durations per beam indicated for at least the CORESET ID, and transmits a first CORESET at a PDCCH monitoring opportunity, the first CORESET scheduling a plurality of physical channel transmissions (i.e., PDSCH and / or PUSCH). Via the transceiver 1125, the processor 1105 further communicates with the UE over a plurality of scheduled physical channels using a plurality of beams associated with the lowest CORESET ID configured on the device, where communicating with the RAN over a plurality of scheduled physical channels includes transmitting a downlink transmission, receiving an uplink transmission, or a combination thereof.

[0185] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is equal to the period of the PDCCH monitoring opportunity. In such embodiments, for each PDCCH monitoring opportunity (i.e., monitoring period), the same association of beams for monitoring the CORESET is applied within the PDCCH monitoring period.

[0186] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is smaller than the period of the PDCCH monitoring opportunity. In such embodiments, for each PDCCH monitoring opportunity, the same association of beams for monitoring the CORESET is applied within the PDCCH monitoring period.

[0187] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is greater than the period of the PDCCH monitoring opportunity. In such embodiments, the association of beams for monitoring the CORESET is applied over multiple PDCCH monitoring periods.

[0188] In some embodiments, the CORESET configuration includes multiple beams (or TCI states or QCL assumptions) associated with multiple transmission and reception points within the RAN.

[0189] The memory 1110, in one embodiment, is a computer-readable storage medium. In some embodiments, the memory 1110 includes a volatile computer storage medium. For example, the memory 1110 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, the memory 1110 includes a non-volatile computer storage medium. For example, the memory 1110 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 1110 includes both volatile and non-volatile computer storage media.

[0190] In some embodiments, memory 1110 stores data related to associating multiple default beams for multiple PDSCH / PUSCHs and monitoring the same CORESET on different beams at different monitoring occasions. For example, memory 1110 may store parameters, configurations, resource allocations, policies, etc., as described above. In certain embodiments, memory 1110 also stores program code and associated data, such as an operating system or other controller algorithms operating on device 1100.

[0191] The input device 1115, in one embodiment, may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 1115 may be integrated with the output device 1120, for example, as a touch screen or similar touch-sensitive display. In some embodiments, the input device 1115 includes a touch screen, such that text may be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 1115 includes two or more different devices, such as a keyboard and a touch panel.

[0192] The output device 1120, in one embodiment, is designed to output visual, auditory, and / or tactile signals. In some embodiments, the output device 1120 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 1120 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, and the like to a user. As another non-limiting example, the output device 1120 may include a wearable display that is separate from, but communicatively coupled to, the rest of the network device 1100, such as a smart watch, smart glasses, a head-up display, and the like. Additionally, the output device 1120 may be a component of a smartphone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, and the like.

[0193] In certain embodiments, the output device(s) 1120 include one or more speakers for generating sound. For example, the output device(s) 1120 may generate an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device(s) 1120 include one or more haptic devices for generating vibration, movement, or other haptic feedback. In some embodiments, all or a portion of the output device(s) 1120 may be integrated with the input device(s) 1115. For example, the input device(s) 1115 and the output device(s) 1120 may form a touchscreen or similar touch-sensitive display. In other embodiments, the output device(s) 1120 may be located near the input device(s) 1115.

[0194] The transceiver 1125 includes at least a transmitter 1130 and at least one receiver 1135. One or more transmitters 1130 may be used to communicate with a UE, as described herein. Similarly, one or more receivers 1135 may be used to communicate with a network function in a public land mobile network ("PLMN") and / or a RAN, as described herein. Although only one transmitter 1130 and one receiver 1135 are shown, the network device 1100 may have any suitable number of transmitters 1130 and receivers 1135. Additionally, the transmitters 1130 and receivers 1135 may be any suitable type of transmitter and receiver.

[0195] 12 illustrates one embodiment of a method 1200 for associating multiple default beams for multiple PDSCH / PUSCHs and monitoring the same CORESET on different beams at different monitoring occasions in accordance with an embodiment of the disclosure. In various embodiments, the method 1200 is performed by a UE device, such as a remote unit 105, a UE 205, and / or a user equipment device 1000, as described above. In some embodiments, the method 1200 is performed by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, or the like.

[0196] The method 1200 starts by receiving 1205 a CORESET configuration from a RAN, the CORESET configuration indicating a number of beams (or TCI states or QCL assumptions) and corresponding durations for each beam indicated for at least a CORESET ID. The method 1200 includes monitoring 1210 at least one CORESET at different PDCCH monitoring occasions using different beams. The method 1200 includes receiving 1215 a first CORESET in a PDCCH transmission, the first CORESET scheduling 1215 a number of physical channel transmissions (i.e., PDSCH and / or PUSCH). The method 1200 includes 1220 communicating with the RAN over a number of scheduled physical channels using a number of beams associated with the lowest CORESET ID configured on the device, the number of scheduled physical channels including receiving a downlink transmission, transmitting an uplink transmission, or a combination thereof. The method 1200 ends.

[0197] 13 illustrates one embodiment of a method 1300 for associating multiple default beams for multiple PDSCH / PUSCHs and monitoring the same CORESET on different beams at different monitoring occasions in accordance with an embodiment of the disclosure. In various embodiments, the method 1300 is performed by an access network node, such as the base unit 121, the RAN node 207, and / or the network device 1100, as described above. In some embodiments, the method 1300 is performed by a processor, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, or the like.

[0198] The method 1300 starts by transmitting a CORESET configuration to a UE (1305), the CORESET configuration indicating a number of beams (or TCI states or QCL assumptions) and corresponding durations for each beam indicated for at least a CORESET ID. The method 1300 includes transmitting a first CORESET at a PDCCH monitoring opportunity (1310), the first CORESET scheduling a number of physical channel transmissions (i.e., PDSCH and / or PUSCH). The method 1300 includes communicating with the UE on a number of scheduled physical channels (1315) using a number of beams associated with the lowest CORESET ID configured on the device, the communicating with the RAN on a number of scheduled physical channels including transmitting a downlink transmission, receiving an uplink transmission, or a combination thereof. The method 1300 ends.

[0199] Disclosed herein is a first apparatus for associating multiple default beams for multiple PDSCH / PUSCHs and monitoring the same CORESET on different beams at different monitoring occasions according to an embodiment of the present disclosure. The first apparatus may be implemented by a UE device such as the remote unit 105, UE 205, and / or user equipment device 1000 described above. The first apparatus includes a processor coupled to a transceiver, the processor and the transceiver configured to cause the first apparatus to: receive a CORESET configuration from a RAN, the CORESET configuration indicating a plurality of beams (or TCI states or QCL assumptions) and corresponding durations for each beam indicated for at least a CORESET ID; monitor at least one CORESET at different PDCCH monitoring occasions using different beams; receive a first CORESET in a PDCCH transmission, the first CORESET scheduling a plurality of physical channel transmissions (i.e., PDSCH and / or PUSCH); and communicate with the RAN on a plurality of scheduled physical channels using a plurality of beams associated with a lowest CORESET ID configured on the device, where communicating with the RAN on a plurality of scheduled physical channels includes receiving a downlink transmission, transmitting an uplink transmission, or a combination thereof.

[0200] In some embodiments, the first apparatus is configured with a time period for a QCL, and the multiple physical channel transmissions are scheduled by a single DCI that does not include a TCI field, and a time offset between receipt of the DCI and the multiple physical channel transmissions is equal to or greater than the time period of the QCL. In such embodiments, communicating with the RAN includes applying a default beam (i.e., a QCL assumption) associated with the first CORESET (i.e., a CORESET used for the PDCCH transmission), where the TCI period of the default beam is equal to or greater than the time offset between receipt of the DCI and the multiple physical channel transmissions.

[0201] In a particular embodiment, the first device applies at least the second default beam when communicating with the RAN over the multiple scheduled physical channels, in such an embodiment, the default beam for each scheduled instance of the physical channel is determined based on a time period associated with the default beam.

[0202] In some embodiments, the first apparatus is configured with a time period for a QCL, and the multiple physical channel transmissions are scheduled by a single DCI, and a time offset between receipt of the DCI and the multiple physical channel transmissions is less than the time period of the QCL. In such embodiments, communicating with the RAN on the multiple scheduled physical channels includes applying multiple default beams associated with the first CORESET, where a TCI period of the default beam is greater than or equal to the time offset between receipt of the DCI and the multiple physical channel transmissions.

[0203] In a particular embodiment, a default beam for each scheduled instance of a physical channel is determined based on a time period associated with the default beam.

[0204] In some embodiments, the first device is configured with a time period for a QCL, and the multiple physical channel transmissions are scheduled by a single DCI that does not include a TCI field, and a time offset between receipt of the DCI and a first portion (or a subset) of the multiple physical channel transmissions is less than the time period of the QCL. In such embodiments, communicating with the RAN includes applying a default beam associated with the lowest CORESET ID for the first portion of the multiple physical channel transmissions and switching to a beam associated with the first CORESET for the remaining portion of the multiple physical channel transmissions.

[0205] In some embodiments, the first device is configured with a time period of QCL, the multiple physical channel transmissions are scheduled by a single DCI including a TCI field indicating a set of beams, a time offset between receipt of the DCI and a first portion (or a subset) of the multiple physical channel transmissions is less than the time period of QCL, and communicating with the RAN includes applying a default beam associated with the lowest CORESET ID for the first portion of the multiple physical channel transmissions and switching to the set of beams indicated by the DCI for the remaining portion of the multiple physical channel transmissions.

[0206] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is equal to the period of the PDCCH monitoring opportunity. In such embodiments, for each PDCCH monitoring opportunity (i.e., monitoring period), the same association of beams for monitoring the CORESET is applied within the PDCCH monitoring period.

[0207] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is smaller than the period of the PDCCH monitoring opportunity. In such embodiments, for each PDCCH monitoring opportunity, the same association of beams for monitoring the CORESET is applied within the PDCCH monitoring period.

[0208] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is greater than the period of the PDCCH monitoring opportunity. In such embodiments, the association of beams for monitoring the CORESET is applied over multiple PDCCH monitoring periods.

[0209] In some embodiments, the CORESET configuration includes multiple beams (or TCI states or QCL assumptions) associated with multiple transmission and reception points within the RAN.

[0210] Disclosed herein is a first method for associating multiple default beams for multiple PDSCH / PUSCH and monitoring the same CORESET on different beams at different monitoring occasions according to an embodiment of the present disclosure. The first method may be performed by a UE device entity such as the remote unit 105, UE 205, and / or user equipment device 1000 described above. The first method includes receiving a CORESET configuration from a RAN, the CORESET configuration indicating multiple beams (or TCI states or QCL assumptions) and corresponding durations per beam indicated for at least a CORESET ID. The first method includes monitoring at least one CORESET at different PDCCH monitoring occasions using different beams and receiving a first CORESET in a PDCCH transmission, the first CORESET scheduling multiple physical channel transmissions. The first method includes communicating with the RAN on multiple scheduled physical channels using multiple beams associated with the lowest CORESET ID configured in the device. Here, communicating with the RAN over a plurality of scheduled physical channels includes receiving a downlink transmission, transmitting an uplink transmission, or a combination thereof.

[0211] In some embodiments, the UE is configured with a time period for a QCL, and the multiple physical channel transmissions are scheduled by a single DCI that does not include a TCI field, and a time offset between receipt of the DCI and the multiple physical channel transmissions is equal to or greater than the time period of the QCL. In such embodiments, communicating with the RAN includes applying a default beam (i.e., a QCL assumption) associated with a first CORESET (i.e., a CORESET used for PDCCH transmission), where the TCI period of the default beam is equal to or greater than the time offset between receipt of the DCI and the multiple physical channel transmissions.

[0212] In certain embodiments, the UE applies at least a second default beam when communicating with the RAN over multiple scheduled physical channels, in such embodiments, the default beam for each scheduled instance of the physical channel is determined based on a time period associated with the default beam.

[0213] In some embodiments, the UE is configured with a time period for a QCL, and the multiple physical channel transmissions are scheduled by a single DCI, and a time offset between receipt of the DCI and the multiple physical channel transmissions is less than the time period of the QCL. In such embodiments, communicating with the RAN on the multiple scheduled physical channels includes applying multiple default beams associated with the first CORESET, where a TCI period of the default beam is greater than or equal to the time offset between receipt of the DCI and the multiple physical channel transmissions.

[0214] In a particular embodiment, a default beam for each scheduled instance of a physical channel is determined based on a time period associated with the default beam.

[0215] In some embodiments, the UE is configured with a time period for a QCL, and the multiple physical channel transmissions are scheduled by a single DCI that does not include a TCI field, and a time offset between receipt of the DCI and a first portion (or a subset) of the multiple physical channel transmissions is less than the time period of the QCL. In such embodiments, communicating with the RAN includes applying a default beam associated with the lowest CORESET ID for the first portion of the multiple physical channel transmissions and switching to a beam associated with the first CORESET for the remaining portion of the multiple physical channel transmissions.

[0216] In some embodiments, the UE is configured with a time period for a QCL, and the multiple physical channel transmissions are scheduled by a single DCI including a TCI field indicating a set of beams, a time offset between receipt of the DCI and a first portion (or a subset) of the multiple physical channel transmissions is less than the time period of the QCL, and communicating with the RAN includes applying a default beam associated with the lowest CORESET ID for the first portion of the multiple physical channel transmissions and switching to the set of beams indicated by the DCI for the remaining portion of the multiple physical channel transmissions.

[0217] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is equal to the period of the PDCCH monitoring opportunity. In such embodiments, for each PDCCH monitoring opportunity (i.e., monitoring period), the same association of beams for monitoring the CORESET is applied within the PDCCH monitoring period.

[0218] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is smaller than the period of the PDCCH monitoring opportunity. In such embodiments, for each PDCCH monitoring opportunity, the same association of beams for monitoring the CORESET is applied within the PDCCH monitoring period.

[0219] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is greater than the period of the PDCCH monitoring opportunity. In such embodiments, the association of beams for monitoring the CORESET is applied over multiple PDCCH monitoring periods.

[0220] In some embodiments, the CORESET configuration includes multiple beams (or TCI states or QCL assumptions) associated with multiple transmission and reception points within the RAN.

[0221] Disclosed herein is a second apparatus for associating multiple default beams for multiple PDSCH / PUSCH and monitoring the same CORESET on different beams at different monitoring occasions according to an embodiment of the present disclosure. The second apparatus may be implemented by an access network node, such as the base unit 121, the RAN node 207, and / or the network device 1100, as described above. The second apparatus includes a processor coupled to a transceiver, and the processor and the transceiver are configured to cause the second apparatus to transmit a CORESET configuration to a UE, the CORESET configuration indicating multiple beams (or TCI states or QCL assumptions) and corresponding durations for each beam indicated for at least a CORESET ID, and to transmit a first CORESET at a PDCCH monitoring occasion, the first CORESET scheduling multiple physical channel transmissions (i.e., PDSCH and / or PUSCH). Via the transceiver, the processor further communicates with the UE over the multiple scheduled physical channels using the multiple beams associated with the lowest CORESET ID configured on the device, and the step of communicating with the RAN over the multiple scheduled physical channels includes transmitting a downlink transmission, receiving an uplink transmission, or a combination thereof.

[0222] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is equal to the period of the PDCCH monitoring opportunity. In such embodiments, for each PDCCH monitoring opportunity (i.e., monitoring period), the same association of beams for monitoring the CORESET is applied within the PDCCH monitoring period.

[0223] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is smaller than the period of the PDCCH monitoring opportunity. In such embodiments, for each PDCCH monitoring opportunity, the same association of beams for monitoring the CORESET is applied within the PDCCH monitoring period.

[0224] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is greater than the period of the PDCCH monitoring opportunity. In such embodiments, the association of beams for monitoring the CORESET is applied over multiple PDCCH monitoring periods.

[0225] In some embodiments, the CORESET configuration includes multiple beams (or TCI states or QCL assumptions) associated with multiple transmission and reception points within the RAN.

[0226] Disclosed herein is a second method for associating multiple default beams for multiple PDSCH / PUSCHs and monitoring the same CORESET on different beams at different monitoring occasions according to an embodiment of the present disclosure. The second method may be performed by an access network node, such as the base unit 121, the RAN node 207, and / or the network device 1100, as described above. The second method includes transmitting a CORESET configuration to a UE, the CORESET configuration indicating multiple beams (or TCI states or QCL assumptions) and corresponding durations for each beam indicated for at least a CORESET ID, and transmitting a first CORESET within a PDCCH monitoring occasion, the first CORESET scheduling multiple physical channel transmissions. A second method includes communicating with a UE over multiple scheduled physical channels using multiple beams associated with a lowest CORESET ID configured on the device, where communicating with a RAN over the multiple scheduled physical channels includes transmitting a downlink transmission, receiving an uplink transmission, or a combination thereof.

[0227] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is equal to the period of the PDCCH monitoring opportunity. In such embodiments, for each PDCCH monitoring opportunity (i.e., monitoring period), the same association of beams for monitoring the CORESET is applied within the PDCCH monitoring period.

[0228] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is smaller than the period of the PDCCH monitoring opportunity. In such embodiments, for each PDCCH monitoring opportunity, the same association of beams for monitoring the CORESET is applied within the PDCCH monitoring period.

[0229] In some embodiments, the CORESET configuration includes a pattern of beams for monitoring the CORESET, and the period of the pattern is greater than the period of the PDCCH monitoring opportunity. In such embodiments, the association of beams for monitoring the CORESET is applied over multiple PDCCH monitoring periods.

[0230] In some embodiments, the CORESET configuration includes multiple beams (or TCI states or QCL assumptions) associated with multiple transmission and reception points within the RAN.

[0231] The embodiments may be embodied in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is therefore indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope. [Explanation of symbols]

[0232] 100 Wireless communication system 105 Remote Unit 120 Radio Access Network ("RAN") 121 Base Unit 123 Wireless Communication Links 140 Mobile Core Network 141 User Plane Function ("UPF") 143 Access and Mobility Management Function ("AMF") 145 Session Management Facility ("SMF") 147 Policy Control Function ("PCF") 149 Combined entity "UDM / UDR" 150 Packet Data Network 151 Application Server 200 Protocol Stack 201 User Plane Protocol Stack 203 Control Plane Protocol Stack 205 UE 207 RAN nodes 209 5G Core Network 211 Physical ("PHY") Layer 213 Medium Access Control (MAC) Sublayer 215 Radio Link Control (RLC) Sublayer 217 Packet Data Convergence Protocol (PDCP) Sublayer 219 Service Data Adaptation Protocol (SDAP) Layer 221 Radio Resource Control (RRC) Layer 221 RRC Sublayer 223 Non-Access Stratum (NAS) Layer 225 AS Layer 227 AS Layer 300 Frame Structure 301 DC 303 1st PDSCH 305 Second PDSCH 307 Third PDSCH 309 Time Offset 400 Frame Structure 401 DC 403 1st PDSCH 405 Second PDSCH 407 3rd PDSCH 409 Time Offset 500 Frame Structure 501 DC 503 1st PDSCH 505 Second PDSCH 507 3rd PDSCH 509 Time Offset 600 Frame Structure 601 DC 603 1st PDSCH 605 Second PDSCH 607 3rd PDSCH 609 Time Offset 700 Frame Structure 800 Frame Structure 900 Frame Structure 1000 User Equipment Device 1005 Processor 1010 Memory 1015 Input Devices 1020 output device 1025 Transceiver 1030 Transmitter 1035 Receiver 1040 Network Interface 1045 Application Interface 1100 Network Equipment 1105 Processor 1110 Memory 1115 Input Devices 1120 Output Device 1125 Transceiver 1130 Transmitter 1135 Receiver 1140 Network Interface 1145 Application Interface 1200 methods 1300 methods

Claims

1. A user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory, the at least one processor providing to the UE: receiving a control resource set (CORESET) configuration from a radio access network (RAN), the CORESET configuration indicating a number of beams for at least one CORESET identifier (ID) and a corresponding duration for each indicated beam, the corresponding duration for each indicated beam being a period during which a corresponding beam is applicable for at least one of downlink reception or uplink transmission by the UE; monitoring at least one CORESET in different physical downlink control channel (PDCCH) monitoring occasions using different beams; receiving a first CORESET within a PDCCH transmission, the first CORESET scheduling a plurality of physical channel transmissions; and communicating with the RAN on the multiple scheduled physical channels using the multiple beams associated with a lowest CORESET ID configured in the UE, where communicating with the RAN on the multiple scheduled physical channels includes at least one of receiving a downlink transmission, transmitting an uplink transmission, or both. U.E.

2. The UE is configured with a time period for quasi-co-location (QCL), and the multiple physical channel transmissions are scheduled by a single downlink control information (DCI) that does not include a transmission configuration indicator (TCI) field, and a time offset between reception of the DCI and the multiple physical channel transmissions is equal to or greater than the time period of QCL, and the at least one processor is configured to cause the UE to communicate with the RAN by applying a default beam associated with the first CORESET, the default beam having a TCI period that is equal to or greater than the time offset between the reception of the DCI and the multiple physical channel transmissions. The UE of claim 1.

3. The at least one processor is configured to cause the UE to apply at least a second default beam when communicating with the RAN on the multiple scheduled physical channels, the default beam for each scheduled instance of a physical channel being determined based on a time period associated with the default beam. The UE of claim 2.

4. The UE is configured with a time period for a QCL, and the multiple physical channel transmissions are scheduled by a single DCI, a time offset between reception of the DCI and the multiple physical channel transmissions is less than the time period of a QCL, and the at least one processor is configured to cause the UE to communicate with the RAN on the multiple scheduled physical channels by applying multiple default beams associated with the first CORESET, the default beam having a TCI period that is greater than or equal to the time offset between the reception of the DCI and the multiple physical channel transmissions. The UE of claim 1.

5. The at least one processor is configured to determine the default beam for each scheduled instance of a physical channel based on a time period associated with the default beam. The UE of claim 4.

6. the UE is configured with a time period for a QCL, the plurality of physical channel transmissions are scheduled by a single DCI that does not include a TCI field, a time offset between receipt of the DCI and a first portion of the plurality of physical channel transmissions is less than the time period of a QCL, and the at least one processor is configured to cause the UE to communicate with the RAN by applying a default beam associated with the lowest CORESET ID for the first portion of the plurality of physical channel transmissions and switching to a beam associated with the first CORESET for a remaining portion of the plurality of physical channel transmissions. The UE of claim 1.

7. the UE is configured with a time period of a QCL, the plurality of physical channel transmissions are scheduled by a single DCI including a TCI field indicating a set of beams, a time offset between receipt of the DCI and a first portion of the plurality of physical channel transmissions is less than the time period of a QCL, and the at least one processor is configured to cause the UE to communicate with the RAN by applying a default beam associated with the lowest CORESET ID for the first portion of the plurality of physical channel transmissions and switching to the set of beams indicated by the DCI for a remaining portion of the plurality of physical channel transmissions. The UE of claim 1.

8. The CORESET configuration involves a pattern of beams for monitoring the CORESET, and a period of the pattern is equal to a period of the PDCCH monitoring opportunity, and for each PDCCH monitoring opportunity, the same association of beams for monitoring the CORESET is applied within a PDCCH monitoring period. The UE of claim 1.

9. The CORESET configuration involves a pattern of beams for monitoring the CORESET, and a period of the pattern is smaller than a period of the PDCCH monitoring opportunity, and for each PDCCH monitoring opportunity, the same association of beams for monitoring the CORESET is applied within a PDCCH monitoring period. The UE of claim 1.

10. The CORESET configuration involves a pattern of beams for monitoring the CORESET, a period of the pattern is greater than a period of the PDCCH monitoring opportunity, and the association of beams for monitoring the CORESET is applied over a plurality of PDCCH monitoring periods. The UE of claim 1.

11. The CORESET configuration involves multiple beams associated with multiple transmission and reception points within the RAN. The UE of claim 1.

12. A method performed by a user equipment (UE), comprising: receiving a control resource set (CORESET) configuration from a radio access network (RAN), the CORESET configuration indicating a number of beams for at least a CORESET identifier (ID) and a corresponding duration for each indicated beam, the corresponding duration for each indicated beam being a period during which a corresponding beam is applicable for at least one of downlink reception or uplink transmission by the UE; monitoring at least one CORESET in different physical downlink control channel (PDCCH) monitoring occasions using different beams; receiving a first CORESET within a PDCCH transmission, the first CORESET scheduling a plurality of physical channel transmissions; and communicating with the RAN on the plurality of scheduled physical channels using the plurality of beams associated with a lowest CORESET ID configured for the UE, wherein communicating with the RAN on the plurality of scheduled physical channels comprises at least one of receiving a downlink transmission, transmitting an uplink transmission, or both. method.

13. A radio access network (RAN) apparatus comprising at least one memory and at least one processor coupled to the at least one memory, the at least one processor providing to the RAN apparatus: transmitting a control resource set (CORESET) configuration to a user equipment (UE), the CORESET configuration indicating a number of beams and a corresponding duration for each indicated beam for at least a CORESET identifier (ID), the corresponding duration for each indicated beam being a period during which a corresponding beam is applicable for at least one of downlink reception or uplink transmission by the UE; transmitting a first CORESET within a physical downlink control channel (PDCCH) monitoring opportunity, the first CORESET scheduling a plurality of physical channel transmissions; and communicating with the UE on the plurality of scheduled physical channels using the plurality of beams associated with a lowest CORESET ID configured for the UE, wherein communicating with the UE on the plurality of scheduled physical channels comprises at least one of transmitting a downlink transmission, receiving an uplink transmission, or both. RAN equipment.

14. the CORESET configuration comprises a pattern of beams for monitoring the CORESET; a periodicity of the pattern is less than or equal to a periodicity of the PDCCH monitoring opportunity, and for each PDCCH monitoring opportunity, the same association of beams for monitoring the CORESET is applied within a PDCCH monitoring period; and / or A period of the pattern is greater than a period of the PDCCH monitoring opportunity, and the association of beams for monitoring the CORESET is applied over a plurality of PDCCH monitoring periods. At least one of 14. The RAN apparatus of claim 13.

15. A processor for wireless communication, the processor comprising at least one controller coupled to at least one memory, the at least one controller providing to the processor: receiving a control resource set (CORESET) configuration from a radio access network (RAN), the CORESET configuration indicating a number of beams for at least one CORESET identifier (ID) and a corresponding duration for each indicated beam, the corresponding duration for each indicated beam being a period during which the corresponding beam is applicable for at least one of downlink reception or uplink transmission by the processor; monitoring at least one CORESET in different physical downlink control channel (PDCCH) monitoring occasions using different beams; receiving a first CORESET within a PDCCH transmission, the first CORESET scheduling a plurality of physical channel transmissions; and communicating with the RAN on the plurality of scheduled physical channels using the plurality of beams associated with a lowest configured CORESET ID, where communicating with the RAN on the plurality of scheduled physical channels includes at least one of receiving a downlink transmission, transmitting an uplink transmission, or both. Processor.

Images