WO2023205213A1 - Ue rbw-redcap configuré pour décoder des pdsch se chevauchant - Google Patents

Ue rbw-redcap configuré pour décoder des pdsch se chevauchant Download PDF

Info

Publication number
WO2023205213A1
WO2023205213A1 PCT/US2023/019071 US2023019071W WO2023205213A1 WO 2023205213 A1 WO2023205213 A1 WO 2023205213A1 US 2023019071 W US2023019071 W US 2023019071W WO 2023205213 A1 WO2023205213 A1 WO 2023205213A1
Authority
WO
WIPO (PCT)
Prior art keywords
prbs
pdschs
rnti
pdsch
scheduled
Prior art date
Application number
PCT/US2023/019071
Other languages
English (en)
Inventor
Debdeep CHATTERJEE
Yingyang Li
Yi Wang
Gang Xiong
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Publication of WO2023205213A1 publication Critical patent/WO2023205213A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0045—Arrangements at the receiver end
    • H04L1/0052—Realisations of complexity reduction techniques, e.g. pipelining or use of look-up tables
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H04L27/2603—Signal structure ensuring backward compatibility with legacy system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/0012—Hopping in multicarrier systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties

Definitions

  • Embodiments pertain to wireless communications. Some embodiments relate to wireless networks including 3 GPP (Third Generation Partnership Project) and fifth-generation (5G) networks including 5G new radio (NR) (or 5G-NR) networks. Some embodiments relate to sixth-generation (6G) networks. Some embodiments relate to reduced-capacity (RedCap) user equipments (UEs) (RedCap UEs) and some embodiments relate to reduced- bandwidth (RBW) RedCap UEs (RBW-RedCap UEs).
  • 5G Fifth Generation Partnership Project
  • 5G fifth-generation
  • 5G 5G new radio
  • 6G sixth-generation
  • Some embodiments relate to reduced-capacity (RedCap) user equipments (UEs) (RedCap UEs) and some embodiments relate to reduced- bandwidth (RBW) RedCap UEs (RBW-RedCap UEs).
  • the 5GNR specifications cater to support of a diverse set of verticals and use cases, including enhanced mobile broadband (eMBB) as well as the newly introduced URLLC services.
  • eMBB enhanced mobile broadband
  • LPWA Low Power Wide Area
  • MTC Category M UEs
  • NB-IoT Category NB UEs
  • Rel-17 NR RedCap work item 3GPP has established a framework for enabling reduced capability NR devices suitable for a range of use cases, including the industrial sensors, video surveillance, and wearables use cases, with requirements on low UE complexity and sometimes also on low UE power consumption.
  • enhancements can be considered to improve the support for the mentioned use cases and also to expand RedCap into a new range of use cases such as smart grid.
  • FIG. 1 A illustrates an architecture of a network, in accordance with some embodiments.
  • FIG. IB and FIG. 1C illustrate a non-roaming 5G system architecture in accordance with some embodiments.
  • FIGs. ID, IE and IF illustrate some bandwidth options for RedCap UEs, in accordance with some embodiments.
  • FIGs. 2A and 2B illustrate two broadcast PDSCHs, in accordance with some embodiments.
  • FIGs. 3 A and 3B illustrate one broadcast PDSCH and one unicast PDSCH, in accordance with some embodiments.
  • FIG. 4 illustrates one broadcast PDSCH and one unicast PDSCH, in accordance with some embodiments.
  • FIGs. 5A, 5B, 5C and 5D illustrate reception of an SSB and one unicast PDSCH, in accordance with some embodiments.
  • FIGs. 6A and 6B illustrate reception of a CORESET and a unicast PDSCH, in accordance with some embodiments.
  • FIGs. 7 A and 7B illustrate reception of a CSI-RS and a unicast PDSCH, in accordance with some embodiments.
  • FIG. 8 illustrates a frequency region with localized PRBs and FDRA, in accordance with some embodiments.
  • FIG. 9A illustrates FDRA with a heady for frequency region in indication, in accordance with some embodiments.
  • FIG. 9B illustrates two partial RBG in the frequency region of 25 PRBs, in accordance with some embodiments.
  • FIG. 9C illustrates a single partial RBG in the frequency region of 25 PRBs, in accordance with some embodiments.
  • FIG. 10 illustrates a frequency region with distributed PRBs and FDRA, in accordance with some embodiments.
  • FIG. 11 illustrates frequency hopping between different frequency regions, in accordance with some embodiments.
  • FIG. 12 illustrates frequency hopping with a same FDRA in each frequency region, in accordance with some embodiments.
  • FIG. 13 illustrates frequency hopping across frequency regions with a second hop spanning two adjacent frequency regions, in accordance with some embodiments.
  • FIG. 14 illustrates a functional block diagram of a wireless communication device, in accordance with some embodiments.
  • Some embodiments are directed to a user equipment (UE) configured for operating in a fifth-generation (5G) new radio (NR) network.
  • the UE may decode signalling that schedules two physical downlink shared channels (PDSCHs) in a same time slot.
  • PDSCHs physical downlink shared channels
  • RBW-RedCap UE when the UE is a reduced-bandwidth (RBW) reduced-capacity (RedCap) UE (RBW-RedCap UE), the UE may determine if a total number of allocated physical resource blocks (PRBs) in an OFDM symbol for the two scheduled PDSCHs exceed a predetermined value (e.g., NBWPRBS) when the two scheduled PDSCHs either partially or fully overlap in time in non-overlapping PRBs.
  • PRBs physical resource blocks
  • the UE may also prioritize decoding of one of the two scheduled PDSCHs when the total number of allocated PRBs exceed the predetermined value and when the two scheduled PDSCHs either partially or fully overlap in time in non-overlapping PRBs. If a first of the two scheduled PDSCHs is a unicast PDSCH and a second of the two scheduled PDSCHs is a broadcast PDSCH, the UE may prioritize decoding of the unicast PDSCH, although the scope of the embodiments is not limited in this respect. These embodiments as well as others, are described in more detail below.
  • FIG. 1 A illustrates an architecture of a network in accordance with some embodiments.
  • the network 140A is shown to include user equipment (UE) 101 and UE 102.
  • the UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface.
  • PDAs Personal Data Assistants
  • the UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.
  • Any of the radio links described herein may operate according to any exemplary radio communication technology and/or standard.
  • LTE and LTE- Advanced are standards for wireless communications of high-speed data for UE such as mobile telephones.
  • carrier aggregation is a technology according to which multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thus increasing the bandwidth available to a single device.
  • carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.
  • Embodiments described herein can be used in the context of any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and further frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and further frequencies).
  • LSA Licensed Shared Access
  • SAS Spectrum Access System
  • Embodiments described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.
  • CP-OFDM Single Carrier or OFDM flavors
  • SC-FDMA SC-FDMA
  • SC-OFDM filter bank-based multicarrier
  • OFDMA filter bank-based multicarrier
  • 3GPP NR New Radio
  • any of the UEs 101 and 102 can comprise an Internet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short-lived UE connections.
  • any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB- loT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE).
  • NB narrowband
  • eNB-IoT enhanced NB- loT
  • FeNB-IoT Further Enhanced
  • An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the loT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network.
  • any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.
  • eMTC enhanced MTC
  • FeMTC enhanced MTC
  • the UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110.
  • the RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to- Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth-generation (5G) protocol, a New Radio (NR) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to- Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth-generation
  • NR New Radio
  • the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105.
  • the ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 102 is shown to be configured to access an access point (AP) 106 via connection 107.
  • the connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi) router.
  • WiFi wireless fidelity
  • the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 110 can include one or more access nodes that enable the connections 103 and 104.
  • These access nodes can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the nodes 111 and 112 can be transmission/reception points (TRPs). In instances when the nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs.
  • the RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro-RAN node, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node.
  • macro-RAN node e.g., macro-RAN node
  • femtocells or picocells e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells
  • LP low power
  • any of the RAN nodes can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102.
  • any of the nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • any of the nodes 111 and/or 112 can be a new generation Node-B (gNB), an evolved node-B (eNB), or another type of RAN node.
  • gNB Node-B
  • eNB evolved node-B
  • the RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113.
  • the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C).
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the nodes 111 and 112 and the serving gateway (S-GW) 122, and the SI -mobility management entity (MME) interface 115, which is a signaling interface between the nodes 111 and 112 and MMEs
  • the CN 120 comprises the MMEs 121, the S-GW
  • the MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • the MMEs 121 may manage mobility embodiments in access such as gateway selection and tracking area list management.
  • the HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the a RAN node (node 110) and the CN 120.
  • the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.
  • the P-GW 123 may terminate an SGi interface toward a PDN.
  • the P-GW 123 may route data packets between the network 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125.
  • AF application function
  • IP Internet Protocol
  • the P-GW 123 can also communicate data to other external networks 131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks.
  • the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS UMTS Packet Services
  • the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125.
  • the application server 184 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.
  • VoIP Voice-over-Internet Protocol
  • the P-GW 123 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120.
  • PCRF Policy and Charging Rules Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • the PCRF 126 may be communicatively coupled to the application server 184 via the P- GW 123.
  • the communication network 140 A can be an loT network or a 5G network, including 5G new radio network using communications in the licensed (5GNR) and the unlicensed (5GNR-U) spectrum.
  • One of the current enablers of loT is the narrowband-IoT (NB-IoT).
  • An NG system architecture can include the RAN 110 and a 5G network core (5GC) 120.
  • the RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs.
  • the core network 120 e.g., a 5G core network or 5GC
  • AMF access and mobility function
  • UPF user plane function
  • the AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some embodiments, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.
  • the NG system architecture can use reference points between various nodes as provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12).
  • TS 3GPP Technical Specification
  • each of the gNBs and the NG-eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth.
  • a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.
  • MN master node
  • SN secondary node
  • FIG. IB illustrates a non-roaming 5G system architecture in accordance with some embodiments.
  • a 5G system architecture 140B in a reference point representation. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5G core (5GC) network entities.
  • 5GC 5G core
  • the 5G system architecture MOB includes a plurality of network functions (NFs), such as access and mobility management function (AMF) 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, user plane function (UPF) 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (HSS) 146.
  • the UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third-party services.
  • DN data network
  • the AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality.
  • the SMF 136 can be configured to set up and manage various sessions according to network policy.
  • the UPF 134 can be deployed in one or more configurations according to the desired service type.
  • the PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system).
  • the UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).
  • the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs).
  • IMS IP multimedia subsystem
  • CSCFs call session control functions
  • the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B.
  • the P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B.
  • the S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain embodiments of emergency sessions such as routing an emergency request to the correct emergency center or PSAP.
  • the I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area.
  • the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator.
  • the UDM 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS).
  • TAS telephony application server
  • AS application server
  • the AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.
  • FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), Ni l (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM
  • FIG. 1C illustrates a 5G system architecture 140C and a servicebased representation.
  • system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156.
  • NEF network exposure function
  • NRF network repository function
  • 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.
  • service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services.
  • 5G system architecture 140C can include the following service-based interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), a Nudm 158E (a service-based interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158 A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the AU
  • any of the UEs or base stations described in connection with FIGS. 1 A-1C can be configured to perform the functionalities described herein.
  • NR next generation wireless communication system
  • 5G next generation wireless communication system
  • NR new radio
  • 3G LTE- Advanced with additional potential new Radio Access Technologies (RATs) to enrich people's lives with better, simple, and seamless wireless connectivity solutions.
  • RATs Radio Access Technologies
  • NR-unlicensed a short-hand notation of the NR-based access to unlicensed spectrum, is a technology that enables the operation of NR systems on the unlicensed spectrum.
  • FIGs. ID, IE and IF illustrate some bandwidth options for RedCap UEs, in accordance with some embodiments. These examples of bandwidth options are for RBW-RedCap UEs referred to as Reduced Bandwidth-RedCap (RBW-RedCap) UEs.
  • RBW-RedCap Reduced Bandwidth-RedCap
  • both radio frequency (RF) and baseband (BB) can be reduced to 5MHz which maximize potential complexity reduction.
  • the BB is reduced to 5MHz while the RF is still 20MHz since the complexity reduction by BW reduction of RF is not significant.
  • FIG. IF it keeps both the RF and control channel/signal in the BB as 5MHz and only the data channel in BB can be reduced to 5MHz.
  • FIG. IF provides the least complexity reduction, it allows more flexible scheduling which minimize the changes to existing NR operations.
  • a RBW-RedCap UE may be only capable of processing up to localized PRBs. For example, equals to 25 which corresponds to 5MHz bandwidth as shown in FIG. ID and FIG. IE.
  • the localized PRBs may have multiple possible locations within the DL/UL BWP or no limitation on the location of the PRBs within the DL/UL BWP.
  • a RBW-RedCap UE may be only capable of processing the DL or UL BWP of up to 20MHz. It is not limited that the PRBs are localized or distributed. For FIG> IF, the PRBs may have multiple possible locations within the DL/UL BWP or no limitation on the location of the PRBs within the DL/UL BWP.
  • the maximum number of REs in a slot that can be processed by a RBW-RedCap UE is limited to no more than a threshold.
  • the maximum number of REs may only include the REs of the PDSCH or PUSCH transmission(s) in a slot.
  • the maximum number of REs may include the REs of the PDSCH transmission(s) in a slot and one or more other channel s/signals in the slot, e.g., SSB, CORESET and/or CSI-RS.
  • the maximum number of REs may include the REs of the PUSCH transmission(s) in a slot and one or more other channel s/signals in the slot, e.g.
  • the threshold may the maximum number of REs per slot that can be processed by the UE. is a number of OFDM symbols used to determine a maximum number of REs per slot that can be processed by the UE. may be predefined, e.g.,
  • the threshold can be same or different for DL or UL transmission.
  • the sum of TBSs of multiple PDSCHs or PUSCHs in a slot is limited to be no more than a maximum value.
  • the sum of multiple PDSCHs or PUSCHs in a slot is limited to be no more than a maximum data rate.
  • Some embodiments are directed to a user equipment (UE) configured for operating in a fifth-generation (5G) new radio (NR) network.
  • the UE may decode signalling that schedules two physical downlink shared channels (PDSCHs) in a same time slot.
  • PDSCHs physical downlink shared channels
  • RBW-RedCap UE when the UE is a reduced-bandwidth (RBW) reduced-capacity (RedCap) UE (RBW-RedCap UE), the UE may determine if a total number of allocated physical resource blocks (PRBs) in an OFDM symbol for the two scheduled PDSCHs exceed a predetermined value (e.g., NBWPRBS) when the two scheduled PDSCHs either partially or fully overlap in time in non-overlapping PRBs.
  • PRBs physical resource blocks
  • the UE may also prioritize decoding of one of the two scheduled PDSCHs when the total number of allocated PRBs exceed the predetermined value and when the two scheduled PDSCHs either partially or fully overlap in time in non-overlapping PRBs. If a first of the two scheduled PDSCHs is a unicast PDSCH and a second of the two scheduled PDSCHs is a broadcast PDSCH, the UE may prioritize decoding of the unicast PDSCH, although the scope of the embodiments is not limited in this respect.
  • FIGs. 2A and 2B, FIGs. 3 A and 3B, and FIG. 4 illustrate two physical downlink shared channels (PDSCHs) in a same time slot.
  • a RBW-RedCap UE does not expect to decode two PDSCHs that partially or fully overlap in time in non-overlapping PRBs if the total number of allocated PRBs of the two PDSCHs in any OFDM symbol exceeds
  • a RBW-RedCap UE does not expect to decode two PDSCHs in the same slot if the total number of allocated PRBs of the two PDSCHs in any one OFDM symbol exceeds PRBs.
  • the predetermined value (e.g., NBWPRBS) is twenty-five (25) for a subcarrier spacing (SCS) of 15kHz.
  • a RBW-RedCap UE may not have the capability to decode two PDSCHs if the total number of allocated PRBs in any one OFDM symbol exceed 25 PRBs, although the scope of the embodiments is not limited in this respect.
  • the UE may decode both of the two scheduled PDSCHs when the total number of allocated PRBs does not exceed the predetermined value although the scope of the embodiments is not limited in this respect. In some embodiments, for a RBW- RedCap UE, the UE may decode both of the two scheduled PDSCHs or when the two scheduled PDSCHs are not partially or fully overlapping in time in nonoverlapping PRBs.
  • a first of the two scheduled PDSCHs is a unicast PDSCH and a second of the two scheduled PDSCHs is a broadcast PDSCH.
  • the UE may be configured to prioritize decoding of the unicast PDSCH when the total number of allocated PRBs exceeds the predetermined value and when the two scheduled PDSCHs either partially or fully overlap in time in non-overlapping PRBs.
  • decoding of a unicast PDSCH may be prioritized since there may be a timeline requirement (e.g., to report HARQ-ACK feedback).
  • a broadcast PDSCH e.g., SIBl/OSEpaging
  • the UE may prioritize decoding of the PDSCH scheduled with the RA-RNTI over the unicast PDSCH.
  • the broadcast PDSCH may be prioritized over a unicast PDSCH, although the scope of the embodiments is not limited in this respect.
  • the RA- RNTI schedules a special broadcast PDSCH that will schedule msg3 for transmission by the UE by a random-access response (RAR).
  • the RAR may be more important than a unicast PDSCH and should be prioritized over other PDSCHs including a unicast PDSCH, although the scope of the embodiments is not limited in this respect.
  • the signalling that schedules the two PDSCHs may comprise Radio Network Temporary Identifiers (RNTIs).
  • RNTIs Radio Network Temporary Identifiers
  • the UE may determine which one of the two scheduled PDSCHs to prioritize decoding based on the RNTI.
  • the UE may prioritize the decoding of one of the two scheduled PDSCHs that is scheduled with a Cell-RNTI (C-RNTI), a Modulation Coding Scheme C-RNTI (MCS-C-RNTI), or a Configured Scheduling RNTI (CS-RNTI) (i.e., unicast PDSCHs) over decoding of one of the two scheduled PDSCHs that is scheduled with a System Information RNTI (SI- RNTI), a Paging RNTI (P-RNTI) or a temporary C-RNTI (TC-RNTI) (i.e., broadcast PDSCHs), although the scope of the embodiments is not limited in this respect.
  • C-RNTI Cell-RNTI
  • MCS-C-RNTI Modulation Coding Scheme C-RNTI
  • CS-RNTI Configured Scheduling RNTI
  • SI- RNTI System Information RNTI
  • P-RNTI Paging RNTI
  • TC-RNTI temporary C-RNTI
  • the UE when the UE is a RBW-RedCap UE and when the UE prioritizes decoding of the first of the two scheduled PDSCHs, the UE may process a first number of PRBs that are allocated to the first of the two scheduled PDSCHs, and process a subset of a second number of PRBs that are allocated to the second of the two scheduled PDSCH up to the predetermined value.
  • the first number of PRBs and the subset of the second number of PRBs is that are processed may be less than or equal to the predetermined value (e.g., NBWPRBS).
  • a RBW-RedCap UE may not have the capability to decode two PDSCHs if they exceed the predetermined value. An example of this is illustrated in FIG. 3B.
  • the UE when the UE prioritizes decoding of one of the two scheduled PDSCHs, the UE may be configured to drop the other PDSCH, although the scope of the embodiments is not limited in this respect.
  • the UE when the UE is a RBW-RedCap UE and is configured to meet a preconfigured PDSCH decoding timeline, the UE may prioritize decoding of one of the two scheduled PDSCHs when the total number of allocated PRBs exceed the predetermined value and when the two scheduled PDSCHs either partially or fully overlap in time in non-overlapping PRBs.
  • the UE when the UE is a RBW-RedCap UE and is not configured to meet a preconfigured PDSCH decoding timeline (e.g., the decoding timeline is relaxed), the UE may not be configured to prioritize decoding of one of the two scheduled PDSCHs when the total number of allocated PRBs exceed the predetermined value.
  • the UE when the UE is a RBW-RedCap UE and the PDSCH decoding timeline is relaxed, the UE may decode both of the two scheduled PDSCHs even though the total number of allocated PRBs may exceed the predetermined value.
  • the decoding timeline may refer to a time within which the PDSCH needs to be decoded in accordance with the 3 GPP standards.
  • the UE when the UE is a RBW-RedCap UE and is configured to meet a preconfigured PDSCH decoding timeline, the UE may prioritize decoding of one of the two scheduled PDSCHs when the total number of allocated PRBs exceed the predetermined value and when the two scheduled PDSCHs either partially or fully overlap in time in non-overlapping PRBs.
  • the UE When the UE is a RBW-RedCap UE and the PDSCH decoding timeline is relaxed, the UE may decode one of the two scheduled PDSCHs when the two PDSCHs are scheduled in different slots and the total number of allocated PRBs exceeds the predetermined value.
  • the UE when the UE is a RBW-RedCap UE, the UE may have a maximum operating bandwidth of 20 MHz for frequency range one (FR1) and 100 MHz for FR2 and may be capable of reception of scheduled unicast PDSCHs with a total number of PRBs up to the predetermined value (e g., NBWPRBS).
  • FR1 frequency range one
  • NBWPRBS predetermined value
  • a RBW-RedCap UE may have the capability to decode up to 106 PRBs in a longer timeframe.
  • a non -RBW-RedCap UE may have a maximum operating bandwidth of 100 MHz or more for FR1 and 200 MHz or more for FR2 and capable of reception of PDSCHs scheduled with a total number of PRBs that exceed the predetermined value.
  • the UE may decode both of the scheduled PDSCHs regardless of whether the total number of allocated PRBs exceed the predetermined value or whether the two scheduled PDSCHs either partially or fully overlap.
  • the UE may include processing circuitry which may comprise a baseband processor.
  • the UE may also include memory configured to store a value representing the total number of allocated PRBs.
  • Some embodiments are directed to a non-transitory computer- readable storage medium that stores instructions for execution by processing circuitry of a user equipment (UE) configured for operating in a fifth-generation (5G) new radio (NR_ network.
  • the processing circuitry may be configured to decode signalling that schedules two physical downlink shared channels (PDSCHs) in a same time slot.
  • PDSCHs physical downlink shared channels
  • the processing circuitry may be configured to determine if a total number of allocated physical resource blocks (PRBs) in an OFDM symbol for the two scheduled PDSCHs exceed a predetermined value (e.g., NBWPRBS) when the two scheduled PDSCHs either partially or fully overlap in time in nonoverlapping PRBs.
  • the processing circuitry may also prioritize decoding of one of the two scheduled PDSCHs when the total number of allocated PRBs exceed the predetermined value and when the two scheduled PDSCHs either partially or fully overlap in time in non-overlapping PRBs.
  • Some embodiments are directed to a method performed by processing circuitry of a user equipment (UE) configured for operating in a fifthgeneration (5G) new radio (NR) network.
  • the method may comprise decoding signalling that schedules two physical downlink shared channels (PDSCHs) in a same time slot.
  • PDSCHs physical downlink shared channels
  • the method comprises determining if a total number of allocated physical resource blocks (PRBs) in an OFDM symbol for the two scheduled PDSCHs exceed a predetermined value (e.g., NBWPRBS) when the two scheduled PDSCHs either partially or fully overlap in time in nonoverlapping PRBs.
  • the method may also comprise prioritizing decoding of one of the two scheduled PDSCHs when the total number of allocated PRBs exceed the predetermined value and when the two scheduled PDSCHs either partially or fully overlap in time in non-overlapping PRBs.
  • a UE supports simultaneous receptions of partially or fully time-overlapping broadcast PDSCHs in RRC IDLE and RRC INACTIVE states.
  • RRC IDLE For an RBW-RedCap UE in idle or inactive state, due to low processing capability, certain relaxations may be defined to the decoding of PDSCH(s) scheduled with SI-RNTI, P-RNTI, RA- RNTI or TC-RNTI.
  • FIGs. 2A and 2B illustrate two broadcast PDSCHs, in accordance with some embodiments.
  • FIGs. 2A and 2B illustrate two examples for two broadcast PDSCHs allocated in one slot. It is assumed PDSCH 1, 2 & 3 have respectively 10 PRBs, while PDSCH 4 has 20 PRBs. PDSCH 1 & 2 are overlapped in time, while PDSCH 3 & 4 are overlapped in time. Note: localized PRB allocation are assumed for each PDSCH, though it may be allowed to schedule distributed PRBs for each PDSCH.
  • an RBW-RedCap UE does not expect that the number of allocated PRBs of a PDSCH exceeds PRBs.
  • the number of allocated PRBs of a PDSCH can be larger than the PDSCH decoding timeline can be relaxed.
  • the following options can be considered to handle the multiple PDSCH(s) scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI in the same slot.
  • the two PDSCHs may be just scheduled in the slot.
  • the two PDSCHs may be scheduled in different slots, however, due to the relaxed decoding timeline of one PDSCH, the decoding of the two PDSCH overlap in the slot. If the two PDSCHs are scheduled in the same slot, the two PDSCHs may be partially or fully overlapping in time in nonoverlapping PRBs. If the two PDSCHs are scheduled in the different slots, the two PDSCHs may be scheduled in overlapping or non-overlapping PRBs.
  • an RBW-RedCap UE in idle or inactive state, may be expected to decode two PDSCHs each scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI, with the two PDSCHs partially or fully overlapping in time in non-overlapping PRBs, if the total number of allocated PRBs of the two PDSCHs in any OFDM symbol does not exceed PRBs.
  • FIG. 2B since the total number of RPBs for broadcast PDSCH 3 & 4 in OFDM symbol 5/6/778 is 30 which exceed are not valid scheduling/configuration for the RBW-RedCap UE.
  • an RBW-RedCap UE may be expected to decode two PDSCHs in the same slot, each scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI, if the total number of allocated PRBs of the two PDSCHs in any OFDM symbol does not exceed PRBs.
  • the UE may prioritize the reception of one of the two PDSCHs. For example, the UE may only decode one of the two PDSCHs in a time. A de-prioritized PDSCH can be decoded after the decode of a prioritized PDSCH is completed or if the prioritized PDSCH is not received yet.
  • the prioritized PDSCH may be determined by the RNTI. For example, the PDSCH scheduled by RA-RNTI is prioritized for scheduling of msg3.
  • an RBW-RedCap UE in idle or inactive state, if an RBW-RedCap UE would decode two PDSCHs each scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI, with the two PDSCHs partially or fully overlapping in time in nonoverlapping PRBs, and the total number of allocated PRBs of the two PDSCHs in any OFDM symbol exceeds PRBs, the UE may only decode one of the two PDSCHs. The other PDSCH is dropped.
  • the prioritized PDSCH may be determined by the RNTI.
  • an RBW-RedCap UE in idle or inactive state, if an RBW-RedCap UE would decode two PDSCHs in a slot, each scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI, and the total number of allocated PRBs of the two PDSCHs in any OFDM symbol exceeds PRBs, the UE may only decode one of the two PDSCHs. The other PDSCH is dropped.
  • the prioritized PDSCH may be determined by the RNTI.
  • an RBW-RedCap UE in idle or inactive state, does not expect to decode two PDSCHs each scheduled with SI-RNTI, P-RNTI, RA- RNTI or TC-RNTI, with the two PDSCHs partially or fully overlapping in time in non-overlapping PRBs, if the total number of allocated PRBs of the two PDSCHs in any OFDM symbol exceeds
  • an RBW-RedCap UE in idle or inactive state, does not expect to decode two PDSCHs in the same slot, each scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI, if the total number of allocated PRBs of the two PDSCHs in any OFDM symbol exceeds PRBs.
  • an RBW-RedCap UE does not expect that the allocated PRBs of a PDSCH span more than localized PRBs.
  • the following options can be considered to handle the multiple PDSCH(s) scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI in the same slot.
  • an RBW-RedCap UE in idle or inactive state, may be expected to decode two PDSCHs each scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI, with the two PDSCHs partially or fully overlapping in time in non-overlapping PRBs, if the two PDSCHs are allocated within localized PRBs.
  • an RBW-RedCap Cap UE may be expected to decode two PDSCHs in the same slot, each scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI, if the two PDSCHs are allocated within localized PRBs.
  • an RBW-RedCap UE in idle or inactive state, if an RBW-RedCap UE would decode two PDSCHs each scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI, with the two PDSCHs partially or fully overlapping in time in nonoverlapping PRBs, and the two PDSCHs are not allocated within localized PRBs, the UE may only decode one of the two PDSCHs.
  • the prioritized PDSCH may be determined by the RNTI.
  • an RBW-RedCap Cap UE in idle or inactive state, if an RBW-RedCap Cap UE would decode two PDSCHs in the same slot, each scheduled with SI- RNTI, P-RNTI, RA-RNTI or TC-RNTI, and the two PDSCHs are not allocated within localized PRBs, the UE may only decode one of the two PDSCHs.
  • the prioritized PDSCH may be determined by the RNTI.
  • an RBW-RedCap UE in idle or inactive state, does not expect to decode two PDSCHs each scheduled with SI-RNTI, P-RNTI, RA- RNTI or TC-RNTI, with the two PDSCHs partially or fully overlapping in time in non-overlapping PRBs, if the two PDSCHs are not allocated within localized PRBs.
  • an RBW-RedCap Cap UE in idle or inactive state, does not expect to decode two PDSCHs in the same slot, each scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI, if the two PDSCHs are not allocated within localized PRBs.
  • a RBW-RedCap UE does not expect that the number of allocated REs of a PDSCH exceeds a maximum number of or 12 ⁇ p s j n a siot T e following options can be considered to handle the multiple PDSCH(s) scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC- RNTI in the same slot.
  • a RBW-RedCap UE in idle or inactive state, may be expected to decode two PDSCHs each scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI, with the two PDSCHs partially or fully overlapping in time in non-overlapping PRBs, if the total number of allocated REs of the two PDSCHs in a slot does not exceed REs.
  • the broadcast PDSCH 1 & 2 in FIG. 2A can still be decoded by the RBW- RedCap UE.
  • FIG. 2B since the total number of REs for broadcast PDSCH 3 & 4 is less than the limit e.g., where may be may equal to 14, the RBW-RedCap UE can decode PDSCH 3 & 4.
  • a RBW-RedCap UE in idle or inactive state, can decode two PDSCHs in the same slot each scheduled with SI-RNTI, P- RNTI, RA-RNTI or TC-RNTI, if the total number of allocated REs of the two PDSCHs in a slot does not exceed
  • a RBW-RedCap UE in idle or inactive state, if a RBW-RedCap UE would decode two PDSCHs each scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI, with the two PDSCHs partially or fully overlapping in time in nonoverlapping PRBs, and the total number of allocated REs of the two PDSCHs in a slot exceeds REs, the UE may only decode one of the two PDSCHs.
  • the prioritized PDSCH may be determined by the RNTI.
  • a RBW-RedCap UE in idle or inactive state, if a RBW-RedCap UE would decode two PDSCHs in the same slot each scheduled with SI-RNTI, P- RNTI, RA-RNTI or TC-RNTI, and the total number of allocated REs of the two PDSCHs in a slot exceeds REs, the UE may only decode one of the two PDSCHs.
  • the prioritized PDSCH may be determined by the RNTI.
  • a RBW-RedCap UE in idle or inactive state, does not expect to decode two PDSCHs each scheduled with SI-RNTI, P-RNTI, RA- RNTI or TC-RNTI, with the two PDSCHs partially or fully overlapping in time in non-overlapping PRBs, if the total number of allocated REs of the two PDSCHs in a slot exceeds
  • a RBW-RedCap UE in idle or inactive state, does not expect to decode two PDSCHs in the same slot each scheduled with SI- RNTI, P-RNTI, RA-RNTI or TC-RNTI, if the total number of allocated REs of the two PDSCHs in a slot exceeds
  • an RBW-RedCap UE does not expect that the sum of the TBSs of multiple PDSCH(s) scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI in the same slot is larger than a threshold T.
  • T can be predefined or reported as UE capability.
  • an RBW-RedCap UE does not expect that the sum of multiple PDSCH(s) scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI in the same slot exceeds a maximum data rate.
  • the maximum data rate can be predefined or reported as UE capability. For example, as defined in TS 38.306 data rate (in Mbps)
  • the parameters in the formula may be set based on the characteristic of the RBW-RedCap UE.
  • an RBW-RedCap UE in idle or inactive state, does not expect to decode more than one PDSCH scheduled with SI-RNTI, P- RNTI, RA-RNTI or TC-RNTI in a OFDM symbol. With this option, both two examples in FIG. 2A and 2B are invalid scheduling/configuration. [00111] In one embodiment, in idle or inactive state, an RBW-RedCap UE does not expect to decode more than PDSCH scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI in a slot.
  • a UE is expected to be able to decode a unicast PDSCH and a broadcast PDSCH for system information when the two PDSCH are partially or fully overlapping in time in non-overlapping PRBs.
  • certain relaxations may be defined to the decoding of a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI and, for P-RNTI triggered or autonomous SI acquisition, another PDSCH scheduled with SI-RNTI in the same slot.
  • FIGs. 3 A and 3B illustrate one broadcast PDSCH and one unicast
  • FIGs. 3 A and 3B illustrate two examples for one broadcast PDSCH plus one unicast PDSCH that are allocated and overlapped in one slot. It is assumed the broadcast PDSCH has 10 PRB and the unicast PDSCH has 20 PRBs. The two PDSCHs are overlapped in time. Note: localized PRB allocation are assumed for each PDSCH, though it may be allowed to schedule distributed PRBs for each PDSCH.
  • an RBW-RedCap UE does not expect that the number of allocated PRBs of a PDSCH exceeds PRBs, e.g., the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI.
  • the PDSCH decoding timeline can be relaxed.
  • Such PDSCH may be a PDSCH of a P-RNTI triggered SI acquisition, or other PDSCH scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI.
  • the following options can be considered to handle a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI and, for P-RNTI triggered or autonomous SI acquisition, another PDSCH scheduled with SI- RNTI in the same slot.
  • the above another PDSCH can be replaced by a PDSCH scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI too.
  • the two PDSCHs may be just scheduled in the slot.
  • the two PDSCHs may be scheduled in different slots, however, due to the relaxed decoding timeline of one PDSCH, the decoding of the two PDSCH overlap in the slot.
  • the two PDSCHs may be partially or fully overlapping in time in non-overlapping PRBs. If the two PDSCHs are scheduled in the different slots, the two PDSCHs may be scheduled in overlapping or non-overlapping PRBs.
  • a RBW-RedCap UE may be expected to decode the two PDSCHs if the total number of allocated PRBs of the two PDSCHs does not exceed PRBs. Otherwise, the RBW-RedCap UE may prioritize the reception of one of the two PDSCHs. For example, the UE may only decode one of the two PDSCHs. A de-prioritized PDSCH can be decoded after the decode of a prioritized PDSCH is completed or if the prioritized PDSCH is not received yet. The prioritized PDSCH may be determined by the RNTI. For example, the UE may prioritize the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS- RNTI.
  • a RBW-RedCap UE may be expected to decode the two PDSCHs that partially or fully overlap in time in non-overlapping PRBs, if the total number of allocated PRBs of the two PDSCHs does not exceed PRBs. Otherwise, the RBW-RedCap UE may only decode one of the two PDSCHs. The other PDSCH is dropped.
  • the prioritized PDSCH may be determined by the RNTI. For example, the UE may receive the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI. With this option, in FIG.
  • the RBW-RedCap UE may drop the broadcast PDSCH.
  • a RBW-RedCap UE may be expected to decode the two PDSCHs in a slot, if the total number of allocated PRBs of the two PDSCHs in any OFDM symbol does not exceed PRBs. Otherwise, the RBW-RedCap UE may only decode one of the two PDSCHs. The other PDSCH is dropped.
  • the prioritized PDSCH may be determined by the RNTI. For example, the UE may receive the PDSCH scheduled with C-RNTI, MCS-C- RNTI, or CS-RNTI.
  • UE may only receive a subset of PRBs of the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI in the OFDM symbol so that the total number of the received PRBs of the two PDSCHs in any OFDM symbol does not exceed PRBs.
  • UE may only receive a subset of PRBs of the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI in the OFDM symbol so that the total number of the received PRBs of the two PDSCHs in any OFDM symbol does not exceed
  • a RBW-RedCap UE does not expect to decode the two PDSCHs that partially or fully overlap in time in non-overlapping PRBs, if the total number of allocated PRBs of the two PDSCHs in any OFDM symbol exceeds
  • a RBW-RedCap UE does not expect to decode the two PDSCHs in the same slot, if the total number of allocated PRBs of the two PDSCHs in any OFDM symbol exceeds PRBs.
  • an RBW-RedCap UE does not expect that the allocated PRBs of a PDSCH span more than localized PRBs.
  • the following options can be considered to handle a PDSCH scheduled with C- RNTI, MCS-C-RNTI, or CS-RNTI and, for P-RNTI triggered or autonomous SI acquisition, another PDSCH scheduled with SI-RNTI in the same slot.
  • a RBW-RedCap UE may be expected to decode the two PDSCHs that partially or fully overlap in time in non-overlapping PRBs, if the two PDSCHs are allocated within localized PRBs. Otherwise, the RBW-RedCap UE may only decode one of the two PDSCHs.
  • the prioritized PDSCH may be determined by the RNTI. For example, the UE may not receive the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI.
  • a RBW-RedCap UE may be expected to decode the two PDSCHs in the same slot, if the two PDSCHs are allocated within localized PRBs. Otherwise, the RBW-RedCap UE may only decode one of the two PDSCHs.
  • the prioritized PDSCH may be determined by the RNTI. For example, the UE may not receive the PDSCH scheduled with C- RNTI, MCS-C-RNTI, or CS-RNTI.
  • UE may only receive a subset of PRBs of the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI in the OFDM symbol so that the received PRBs of the two PDSCHs are within localized
  • UE may only receive a subset of PRBs of the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI in the OFDM symbol so that the received PRBs of the two PDSCHs are within localized PRBs.
  • a RBW-RedCap UE does not expect to decode the two PDSCHs that partially or fully overlap in time in non-overlapping PRBs, if the two PDSCHs are not allocated within localized PRBs.
  • a RBW-RedCap UE does not expect to decode the two PDSCHs in the same slot, if the two PDSCHs are not allocated within localized PRBs.
  • a RBW-RedCap UE does not expect that the total number of allocated REs of a PDSCH in a slot does not exceed a maximum number ⁇ f REs in a slot, following options can be considered to handle a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI and, for P-RNTI triggered or autonomous SI acquisition, another PDSCH scheduled with SI-RNTI in the same slot.
  • a RBW-RedCap UE can decode the two PDSCHs that partially or fully overlap in time in non-overlapping PRBs, if the total number of allocated REs of the two PDSCHs in a slot does not exceed or
  • the RBW-RedCap UE may only decode one of the two PDSCHs.
  • the prioritized PDSCH may be determined by the RNTI. For example, the UE may not receive the PDSCH scheduled with C-RNTI, MCS-C- RNTI, or CS-RNTI. With this option, the in FIG. 3 A, since the total number of REs for broadcast PDSCH and unicast PDSCH is less than the limit e.g., may equal to 14, the RBW-
  • RedCap UE can decode the two PDSCHs.
  • a RBW-RedCap UE can decode the two PDSCHs in the same slot, if the total number of allocated REs of the two PDSCHs in a slot does not exceed ES. Otherwise, the
  • the RBW-RedCap UE may only decode one of the two PDSCHs.
  • the prioritized PDSCH may be determined by the RNTI. For example, the UE may not receive the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI.
  • UE may only receive a subset of REs of the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI so that the total number of the received REs of the two PDSCHs in the slot does not exceed REs
  • FIG. 4 illustrates one broadcast PDSCH and one unicast PDSCH, in accordance with some embodiments.
  • FIG. 4 illustrates another example for one broadcast PDSCH plus one unicast PDSCH that are allocated and overlapped in one slot. It is assumed the broadcast PDSCH has 10 PRB and the unicast PDSCH has 20 PRBs. Note: localized PRB allocation are assumed for each PDSCH, though it may be allowed to schedule distributed PRBs for each PDSCH. The total number of allocated REs is 1 2 380 which exceeds 12 ' 2b ⁇ 14 — 12 - 350 : The RBW-RedCap UE may not receive the last 12 - 30 REs of the unicast PDSCH.
  • pjE may only receive a subset of REs of the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI in the slot so that the total number of the received REs of the two PDSCHs in the slot does not exceed
  • a RBW-RedCap UE does not expect to decode the two PDSCHs that partially or fully overlap in time in non-overlapping PRBs, if the total number of allocated REs of the two PDSCHs in a slot exceeds or 12 ' ⁇ s ⁇ - A ⁇ y??1 REs .
  • a RBW-RedCap UE does not expect to decode the two PDSCHs in the same slot, if the total number of allocated REs of the two PDSCHs in a slot exceeds
  • an RBW-RedCap UE does not expect that the sum of the TBS of a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS- RNTI and the TBS of another PDSCH scheduled with SI-RNTI in the same slot for P-RNTI triggered or autonomous SI acquisition is larger than a threshold T.
  • T can be predefined or reported as UE capability.
  • an RBW-RedCap UE does not expect that the sum of the TBS of a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS- RNTI and the TBS of another PDSCH scheduled with SI-RNTI in the same slot for P-RNTI triggered or autonomous SI acquisition exceeds a maximum data rate.
  • the maximum data rate can be predefined or reported as UE capability. For example, as defined in TS 38.306, data rate (in Mbps)
  • the parameters in the formula may be set based on the characteristic of the RBW-RedCap UE.
  • a RBW-RedCap UE does not expect to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI and, for P-RNTI triggered or autonomous SI acquisition, another PDSCH scheduled with SI-RNTI that partially or fully overlap in time in non-overlapping PRBs.
  • a RBW-RedCap UE does not expect to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI and, for P-RNTI triggered or autonomous SI acquisition, another PDSCH scheduled with SI-RNTI in the same slot.
  • an RBW-RedCap UE may expect to have received at most X PDCCHs for DCI formats 1 0, 1 1, or 1 2 with CRC scrambled by any RNTI scheduling X PDSCH receptions for which the UE has not received any corresponding PDSCH symbol and at most Y PDCCHs for DCI formats 0 0, 0 1, or 0 2 with CRC scrambled by any RNTI scheduling Y PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol.
  • a RBW-RedCap UE does not expect to be scheduled or configured to process more than X ongoing PDSCH receptions and more than Y ongoing PUSCH transmissions.
  • the above PDSCH receptions include any dynamically scheduled or semi-statically configured PDSCH receptions including broadcast PDSCHs.
  • the above PUSCH transmissions include any dynamically scheduled or semi-statically configured PUSCH transmissions.
  • a PDSCH or PUSCH may be considered as ‘ongoing’ from the first or last symbol of the PDCCH that schedules the PDSCH or PUSCH, or from the first allocated time symbol of the PDSCH or PUSCH, or from a time that is 2 before the start of the PUSCH, ⁇ ⁇ 2 is the PUSCH preparation time for the corresponding UE processing capability defined in TS 38.214.
  • a PDSCH or PUSCH may be considered as ‘ongoing’ until an ACK is reported for the PDSCH or a toggled NDI is received in a DCI scheduling the HARQ process associated with the PDSCH, or until an ACK is received for the PUSCH or a toggled NDI is received in a DCI scheduling the HARQ process associated with the PUSCH.
  • an RBW-RedCap UE may be configured or scheduled a PDSCH, and one or multiple of the following channel s/signals: an SSB that can be configured by ssb-PositionsInBurst; a CORESET on which the RBW- RedCap UE needs to monitor PDCCH; and a CSI-RS resource that may be periodically configured or dynamically triggered.
  • the PDSCH and the one or multiple channel s/signals may be partially or fully overlapped in time. Due to low processing capability, certain relaxations may be defined for reception of PDSCH and the one or multiple other DL channel s/signals for the RBW-RedCap UE.
  • a RBW-RedCap UE is not capable of receiving more than PRBs in any OFDM symbol in a slot.
  • all the configured PRBs for the CORESET in the OFDM symbol are counted.
  • only the monitored PRBs in the CORESET in the OFDM symbol are counted based on search space set configurations.
  • a PRB in the CORESET is monitored if at least one PDCCH candidate of the UE is mapped to the PRB.
  • a PRB in a OFDM symbol is counted if at least one RE of the CSI-RS is mapped to the PRB.
  • the number of PRBs of a SSB if present is always counted.
  • the number of PRBs of a SSB if present is only counted when the RBW-RedCap UE needs to detect the SSB.
  • a RBW-RedCap UE does not expect that the number of allocated PRBs of a PDSCH exceeds
  • the UE may not expect that the total number of the PRBs of the PDSCH and the one or multiple channel s/signals would exceed PRBs in any OFDM symbol in a slot.
  • UE may not receive part or all of the CSI-RS resource or CSI-RS resource set. If the total number of the PRBs, after excluding part or all of CSI- RS resource or CSI-RS resource set, does not exceed PRBs in the OFDM symbol, UE may receive the PDSCH in the OFDM symbol.
  • UE may not receive the PDSCH in the OFDM symbol or drop the PDSCH in the slot.
  • the PDSCH may be punctured, or rate matched in the OFDM symbol if the number of received PRBs is to be reduced.
  • UE may receive a subset of PRBs of the PDSCH in the OFDM symbol if the total number of the received PRBs of the PDSCH and the one or multiple channel s/signals in any OFDM symbol does not exceed PRBs.
  • the PDSCH may be punctured, or rate matched in the OFDM symbol if the number of received PRBs is to be reduced.
  • a RBW-RedCap UE does not expect that the allocated PRBs of a PDSCH span more than localized PRBs.
  • the UE may not expect that the allocated PRBs of the PDSCH and the one or multiple channel s/signals span more than localized PRBs in any OFDM symbol in a slot.
  • UE may not receive part or all of the CSI-RS resource or C SIRS resource set. If the allocated PRBs, after excluding part or all of CSI-RS resource or CSI-RS resource set, are allocated within localized PRBs in the OFDM symbol, UE may receive the PDSCH in the OFDM symbol.
  • UE may not receive the PDSCH in the OFDM symbol or drop the PDSCH in the slot.
  • the PDSCH may be punctured, or rate matched in the OFDM symbol if the number of received PRBs is to be reduced.
  • UE may receive a subset of PRBs of the PDSCH in the OFDM symbol if remaining PRBs of the PDSCH and the one or multiple channel s/signals in any OFDM symbol are allocated within localized PRBs.
  • the PDSCH may be punctured, or rate matched in the OFDM symbol if the number of received PRBs is to be reduced.
  • a RBW-RedCap UE is not capable of receiving more than a maximum number of REs in a slot.
  • all the configured REs for the CORESET in the OFDM symbol are counted.
  • only the monitored REs in the CORESET in the OFDM symbol are counted.
  • a RE in the CORESET is monitored if at least one PDCCH candidate of the UE is mapped to the RE.
  • the allocated REs of the CSI-RS resource is counted. The number of REs of a SSB if present is always counted.
  • the number of REs of a SSB if present is only counted when the RBW-RedCap UE needs to detect the SSB.
  • a RBW-RedCap UE does not expect that the number of allocated REs of a PDSCH exceeds
  • the UE may not expect that the total number of the REs of the PDSCH and the one or multiple channel s/signals would exceed slot.
  • UE may not receive part or all of the CSI-RS resource or CSI-RS resource set. If the total number of the REs, after excluding part or all of CSI-RS resource or CSI-RS resource set, does not exceed SF or 12 ' REs in the slot, UE may receive the PDSCH in the slot.
  • UE may not receive the PDSCH.
  • UE may only receive a subset of REs of the PDSCH if the total number of the received REs of the PDSCH and the one or multiple channel s/signals in the slot does not exceed REs.
  • PDSCH may be punctured, or rate matched if the number of received REs is to be reduced.
  • FIGs. 5A, 5B, 5C and 5D illustrate reception of an SSB and one unicast PDSCH, in accordance with some embodiments.
  • FIGs. 5A, 5B, 5C and 5D illustrate four cases for reception of SSB and one unicast PDSCH that are allocated and overlapped in one slot. It is assumed the unicast PDSCH has 25 PRBs. Note: localized PRB allocation are assumed for the PDSCH, though it may be allowed to schedule distributed PRBs for the PDSCH.
  • FIG. 5A since the total number of RPBs for the SSB and the PDSCH in OFDM symbol 2/3/4Z5 exceeds the unicast PDSCH is not valid scheduling/configuration for the RBW-RedCap UE.
  • FIG. 5B since the total number of RPBs for the SSB and the PDSCH in OFDM symbol 2/3/4Z5 exceeds all allocated PRBs of the unicast PDSCH in OFDM symbol 2/3/4Z5 are not received for the RBW-RedCap UE.
  • FIG. 5B since the total number of RPBs for the SSB and the PDSCH in OFDM symbol 2/3/4Z5 exceeds all allocated PRBs of the unicast PDSCH in OFDM symbol 2/3/4Z5 are not received for the RBW-RedCap UE.
  • a NR UE may need to detect PDCCH in a CORSET and receive a PDSCH in the overlapped OFDM symbols. If a PDSCH scheduled by a PDCCH would overlap with resources in the CORESET containing the PDCCH, the resources corresponding to a union of the detected PDCCH that scheduled the PDSCH and associated PDCCH DM-RS are not available for the PDSCH.
  • precoderGranularity configured in a CORESET where the PDCCH was detected is set to 'allContiguousRBs', the associated PDCCH DM-RS are DM-RS in all REGs of the CORESET.
  • FIGs. 6A and 6B illustrate reception of a CORESET and a unicast PDSCH, in accordance with some embodiments.
  • FIGs. 6A and 6B illustrate two cases for reception of CORESET and one PDSCH that are allocated and overlapped in one slot. It is assumed the unicast PDSCH has 25 PRBs. Note: localized PRB allocation are assumed for the PDSCH, though it may be allowed to schedule distributed PRBs for the PDSCH.
  • FIGs. 7 A and 7B illustrate reception of a CSI-RS and a unicast PDSCH, in accordance with some embodiments.
  • FIGs. 7A and 7B illustrate two cases for reception of CSI-RS resource and one PDSCH that are allocated and overlapped in a slot. It is assumed the unicast PDSCH has 25 PRBs. Note: localized PRB allocation are assumed for the PDSCH, though it may be allowed to schedule distributed PRBs for the PDSCH.
  • a RBW-RedCap UE may not receive a number of last REs of the PDSCH.
  • a RBW-RedCap UE assumes SS/PBCH block transmission according to ssb-PositionsInBurst, and if the PDSCH resource allocation overlaps with PRBs containing SS/PBCH block transmission resources the RBW-RedCap UE shall assume that the PRBs containing SS/PBCH block transmission resources are not available for PDSCH in the OFDM symbols where SS/PBCH block is transmitted. Otherwise, RBW- RedCap UE may receive the PDSCH in the allocated PRBs for the PDSCH. The RBW-RedCap UE does not expect that the number of allocated PRN
  • RBW- RedCap UE may receive the PDSCH in the allocated PRBs for the PDSCH. The RBW-RedCap UE does not expect that the number of allocated PRBs of a PDSCH exceeds
  • UE can receive both the PDSCH and the CSI-RS resource.
  • the RBW-RedCap UE does not expect that the number of allocated PRBs of a PDSCH exceeds
  • a CORESET and a CSI-RS resource are configured in a same OFDM symbol, there is no limitation on the total number of occupied PRBs of the CORESET and the CSI-RS resource.
  • a CORESET and a SSB are configured in a same OFDM symbol, there is no limitation on the total number of occupied PRBs of the CORESET and the SSB.
  • a CSI-RS resource and a SSB are configured in a same OFDM symbol, there is no limitation on the total number of occupied PRBs of the CSI-RS resource and the SSB.
  • BB base band
  • 5MHz BW for BB processing allows two possible implementations unless specially described: 1) The 5MHz BW can be localized NBW PRBS; or, 2) The 5MHz BW can be distributed NBW PRBS if the 20MHz BW of RF is supported. For example, NBW equals to 25.
  • the localized NBW PRBS for the UE operation should be known first. Then, the PDCCH monitoring and the PDSCH or PUSCH transmission are restricted in the NBW PRBS.
  • FIG. 1C potentially allows different operations. Since UE is capable of PDCCH monitoring in 20MHz BW, there may be no limitation on PDCCH monitoring at all. Alternatively, though a CORESET of up to 20MHz can be supported by the UE, the number of detected PRBs for PDCCH monitoring in the CORESET may be still limited to no more than NBW PRBS.
  • the number of allocated PRBs of PDSCH or PUSCH transmission is limited to no more than NBW PRBS.
  • the allocated PRBs may be within localized NBW PRBS.
  • the allocated PRBs may be distributed NBW PRBS.
  • a frequency region of up to NBW consecutive PRBs may be identified first. Note: the different frequency regions may have same or different number of PRBs. Then, the allocated frequency resource for DL/UL transmission can be indicated within the identified frequency region. In one example, the UE may expect that the start or end of a frequency region can be aligned with the boundary of the Resource Block Group (RBG) of FDRA type 0 for the DL/UL BWP.
  • RBG Resource Block Group
  • the DL/UL BWP may be divided into localized frequency region.
  • the K frequency regions are not overlapped, where the size of the BWP is the size of the frequency region is Y.
  • the frequency region includes the PRBs with indexes & ' another option, the K frequency regions can be overlapped. Therefore, a larger number of frequency regions are supported in the DL/UL BWP which results more bits to identify a frequency region for frequency resource allocation.
  • FIG. 8 illustrates a frequency region with localized PRBs and FDRA, in accordance with some embodiments.
  • FIG. 8 illustrates one example of the localized frequency region and FDRA. In FIG.
  • a BWP of 48 PRBs is divided into 2 localized frequency regions of 24 PRBs.
  • the 24 PRBs in the frequency region is logically indexed by 0 to 23.
  • the existing FDRA can be used to allocate logical PRBs, e.g., from 4 to 16 as if it is a BWP of 24 consecutive PRBs.
  • the frequency region of up to NBW consecutive PRBs for DL/UL transmission of an RBW-RedCap UE can be predefined or determined by a fixed rule with respect to the CORESET #0 which is indicated by the cell-defining SSB (CD-SSB).
  • the frequency region may be semi -statically configured by high layer signaling, e.g., BWP configuration.
  • the frequency region may be activated by MAC CE.
  • the DCI format can dynamically indicate the active frequency region, which could be separated from or jointly coded with the BWP indicator. Consequently, to indicate an allocated frequency resource for DL/UL transmission, the existing FDRA scheme(s) defined in TS 38.214 can be applied within the frequency region.
  • the frequency resource for DL/UL transmission may be dynamically allocated within the DL/UL BWP of up to 20MHz, subjected to a limitation that the allocated PRBs must be within localized NBW PRBS.
  • a frequency region of up to NBW consecutive PRBs for DL/UL transmission of an RBW-RedCap UE is dynamically indicated by a header part of the FDRA field in a DCI format. Then, an allocated frequency resource for DL/UL transmission within the frequency region indicated by the header can be indicated by remaining part of the DFRA field, e.g., using the existing FDRA scheme(s) defined in TS 38.214.
  • FIG. 9 A illustrates FDRA with a heady for frequency region in indication, in accordance with some embodiments.
  • FIG. 9A illustrates one example of the construction of the FDRA field. For example, for a BWP of 20MHz, it may be divided into 4 frequency regions of 5MHz. Therefore, the size of the header can be 2 bits.
  • the resource block assignment information includes a bitmap indicating the Resource Block Groups (RBGs) that are allocated to the UE where a RBG is a set of consecutive PRBs.
  • RBG Resource Block Groups
  • the Size of RBG from TS 38.214 is cited in Table 1.
  • the applicable RBG size in the frequency region of Y consecutive PRBs may be determined by the Table 1 assuming a BWP size of Y PRBs. Based on Table 1, the applicable RBG size can be 2 or 4 for configuration 1 or 2.
  • the application of Configuration 1 or configuration 2 for the frequency region of Y consecutive PRBs may reuse the same configuration as the BWP. Alternatively, the application of Configuration 1 or configuration 2 for the frequency region of Y consecutive PRBs may be separately configured from the BWP.
  • the RBG size in the frequency region of Y consecutive PRBs may be configured by high layer signaling.
  • the resource block assignment information indicates to a UE a set of contiguously allocated non-interleaved or interleaved virtual resource blocks.
  • the required number of bits is ' G' + l..C2,0.
  • the k_th RBG may contain P PRB indexes starting from & ' - 1. The last RBG only consists of ma ( P) PRBs.
  • the boundary of the RBG in the frequency region of Y consecutive PRBs can be aligned with the boundary of the RBG of the DL/UL BWP.
  • FIG. 9B illustrates two partial RBG in the frequency region of 25 PRBs, in accordance with some embodiments.
  • FIG. 9B illustrates one example of RBG allocation in a frequency region of PRB indexes 25 to 49 in a BWP of 106PRBs. It is assumed RBG size of the BWP is 8 while RBG size of the frequency region is 4.
  • the first RBG of the frequency region consists of PRB indexes 25 to 27.
  • FIG. 9C illustrates a single partial RBG in the frequency region of 25 PRBs, in accordance with some embodiments.
  • FIG. 9C illustrates another example of RBG allocation in a frequency region of PRB indexes 27 to 51 in a BWP of 106PRBs. It is assumed RBG size of the BWP is 8 while RBG size of the frequency region is 4. To align with RBG boundary of the BWP, the first RBG of the frequency region only consists of PRB index 27. All other RBGs have equal size of 4 PRBs.
  • a UE may be provided by higher layers with an offset, in terms of a number of PRBs, with respect to the lowest PRB index within the frequency region of Y consecutive PRBs to indicate the start of the second RBG used for resource allocation within the region of Y consecutive PRBs and the first RBG within the frequency region may correspond to the PRBs corresponding to the indicated offset.
  • the value of the offset may range from 0 to RBGsize - 1, where RBGsize is the size of the RBG for scheduling within the frequency region of Y consecutive PRBs.
  • the values of the offsets for DL and UL may be provided separately to a UE.
  • the header for frequency region indication may be treated as a separate field in the DCI format, in addition to the DCI field indicating an allocated frequency resource for DL/UL transmission within the frequency region indicated by the separate DCI field.
  • the existing FDRA scheme(s) defined in TS 38.214 within the BWP can be applied.
  • the required number of bits is 13.
  • the bitmap size may be 14 bits.
  • a frequency region of up to NBW distributed PRBs may be identified first.
  • the frequency region can include non-consecutive PRBs.
  • the different frequency regions may have same or different number of PRBs.
  • the PRBs in the frequency region are indexed from 0 to Y-l, Y is the total number of PRBs in the frequency region. Therefore, the frequency region can be treated as Y consecutive logical PRBs.
  • the allocated frequency resource for DL/UL transmission can be indicated within the logical PRBs of identified frequency region.
  • the DL/UL BWP may be divided into combs and each comb is a frequency region, where the size of the BWP is Specifically, the frequency region
  • a frequency region can be a number equally spaced units in the DL/UL BWP. For s, it can be divided into i 1 ’W A ⁇ units which — 1 Therefore, the frequency region
  • X of a unit can be the size of a RBG as defined by Table 1 based on size ⁇ 5? of the DL/UL BWP.
  • the size X of a unit can be the size of a RBG as defined by Table 1 assuming a BWP size of Y PRBs.
  • the size X of a unit can be the size of a Precoding Resource Block Group (PRG) as defined in TS 38.214.
  • PRG Precoding Resource Block Group
  • FIG. 10 illustrates a frequency region with distributed PRBs and FDRA, in accordance with some embodiments.
  • FIG. 10 illustrates one example of the distributed frequency region and FDRA.
  • a BWP of 48 PRBs is divided into 2 distributed frequency regions of 24 PRBs.
  • the BWP consist of 12 units each with 2 PRBs.
  • the 24 PRBs in the frequency region is logically indexed by 0 to 23.
  • the existing FDRA can be used to allocate logical PRBs, e.g., from 4 to 16 as if it is a BWP of 24 consecutive PRBs. Note: the actual allocated PRBs are distributed in the DL/UL BWP.
  • the frequency region of up to NBW distributed PRBs for DL/UL transmission of a RBW-RedCap UE can be predefined or determined by a fixed rule with respect to the CORESET #0 which is indicated by the cell-defining SSB (CD-SSB).
  • the frequency region may be semi-statically configured by high layer signaling, e.g., BWP configuration.
  • the frequency region may be activated by MAC CE.
  • the DCI format can dynamically indicate the active frequency region, which could be separated from or jointly coded with the BWP indicator. Consequently, to indicate an allocated frequency resource for DL/UL transmission, the existing FDRA scheme(s) defined in TS 38.214 can be applied within logical PRBs of the frequency region.
  • the frequency resource for DL/UL transmission may be dynamically allocated within the DL/UL BWP of up to 20MHz, subjected to a limitation that the allocated PRBs must be within NBW PRBs.
  • a frequency region of up to NBW distributed PRBs for DL/UL transmission of a RBW-RedCap UE is dynamically indicated by a header part of the FDRA field in a DCI format. Then, an allocated frequency resource for DL/UL transmission within the logical PRBs of the frequency region indicated by the header can be indicated by remaining part of the DFRA field, e.g., using the existing FDRA scheme(s) defined in TS 38.214, as shown in FIG. 9 A. For example, for a BWP of 20MHz, it may be divided into 4 frequency regions of 5MHz. Therefore, the size of the header can be 2 bits.
  • the resource block assignment information includes a bitmap indicating the Resource Block Groups (RBGs) that are allocated to the UE where a RBG is a set of consecutive PRBs.
  • RBGs Resource Block Groups
  • the Size of RBG from TS 38.214 is cited in Table 1.
  • the applicable RBG size in the frequency region of Y consecutive PRBs may be determined by the Table 1 assuming a BWP size of Y PRBs. Based on Table 1, the applicable RBG size can be 2 or 4 for configuration 1 or 2.
  • the application of Configuration 1 or configuration 2 for the frequency region of Y consecutive PRBs may reuse the same configuration as the BWP. Alternatively, the application of Configuration 1 or configuration 2 for the frequency region of Y consecutive PRBs may be separately configured from the BWP.
  • the RBG size in the frequency region of Y consecutive PRBs may be configured by high layer signaling.
  • the resource block assignment information indicates to a UE a set of contiguously allocated non-interleaved or interleaved virtual resource blocks.
  • the header for frequency region indication may be treated as a separate field in the DCI format, in addition to the DCI field indicating an allocated frequency resource for DL/UL transmission within the frequency region indicated by the separate DCI field.
  • the existing FDRA defined in TS 38.214 within the BWP can be applied.
  • the bitmap size may be 14 bits.
  • the required number of bits is 13. In this option, if the total number of allocated PRBs is more than NBW for a UE, the UE may only receive or transmit in the NBW lowest allocated PRBs.
  • one or multiple frequency regions can be configured and one of the configured frequency regions can be dynamically indicated by the header part of the FDRA field in a DCI format.
  • Each frequency region is defined within the DL/UL BWP of up to 20MHz, subjected to a limitation of up to NBW PRBS.
  • a frequency region may consist of up to NBW consecutive PRBs, or up to NBW PRBS that can be distributed in the DL/UL BWP.
  • the frequency resource for DL/UL transmission within the frequency region indicated by the header can be indicated by the remaining part of the FDRA field, e.g., using the existing FDRA scheme(s) defined in TS 38.214, as shown in FIG. 9 A.
  • Option B shown in FIG. IE though the BB of a UE is limited to 5MHz, the UE has capability of 20MHz for the RF. It would be possible to configure a DL/UL BWP of up to 20MHz for the UE. Further, fast switching between different 5MHz subbands within the BWP may be possible for the UE since there is no change of RF operation.
  • Option C shown in FIG. IF since the control signaling can be transmitted in a BW of up to 20MHz, it is straightforward that the DL/UL BWP can be up to 20MHz for the UE.
  • the DL/UL BWP may be divided into localized frequency regions,
  • the frequency hopping across different frequency regions can be supported for frequency diversity gain.
  • the UE expects that each hop of the PDSCH or PUSCH transmission is located within a frequency region.
  • the starting PRB for a hop is determined in accordance with the DL/UL BWP.
  • the starting PRB in each hop for the PUSCH transmission is given by: [00218]
  • ⁇ tsrt is the starting RB within the DL/UL BWP, as calculated from the resource block assignment information of resource allocation type 1 or as calculated from the resource assignment for MsgA PUSCH
  • RB Q ffe tis the frequency offset in RBs between the two frequency hops.
  • the UE does not expect that a second or later hop of the PDSCH or PUSCH transmission will span two frequency regions.
  • FIG. 11 illustrates frequency hopping between different frequency regions, in accordance with some embodiments.
  • the UE expects that each hop of the PDSCH or PUSCH transmission is located within a frequency region and the same FDRA as the first hop applies in each frequency region. Assuming the first hop is allocated in the frequency region r with a start PRB in the frequency region
  • [RB] _start A FDRA which corresponds to a start PRB "R” “B” start” within the DL/UL BWP
  • the frequency region "r" “next" of the next hop is the frequency region which include the PRB with index (RB start+RB offset ) modiUj N_BWP A size ] or ( [RB] _start A region+"R" "B” offset” ) modiUj N_BWP A size ]
  • [RB] _start A region is the start PRB of frequency region r.
  • the start PRB of the next hop in the frequency region "r" _"next" is still [RB] _start A FDRA,
  • the parameter "R" "B” “offset” may be reinterpreted as the offset in unit of frequency region.
  • FIG. 12 illustrates frequency hopping with a same FDRA in each frequency region, in accordance with some embodiments.
  • FIG. 12 illustrates one example on the frequency hopping of PUSCH transmission with same FDRA within the different frequency regions.
  • the UE expects that each hop of the PDSCH or PUSCH transmission is located within a frequency region and the mirror of the FDRA is applied within the frequency region of every second hop.
  • FDRA indicated by a DCI format applies to the first hop.
  • the UE expects that the first hop of the PDSCH or PUSCH transmission must be located within a frequency region. For example, for a scheduled PDSCH or PUSCH transmission, the frequency resource is allocated within a frequency region. Then, as to other hops, it is allowed that the hop may cross the boundary of two frequency regions.
  • FIG. 13 illustrates frequency hopping across frequency regions with a second hop spanning two adjacent frequency regions, in accordance with some embodiments.
  • FIG. 14 illustrates a functional block diagram of a wireless communication device, in accordance with some embodiments.
  • Wireless communication device 1400 may be suitable for use as a UE or gNB configured for operation in a 5G NR network.
  • device 1400 may be a RedCap UE.
  • the communication device 1400 may include communications circuitry 1402 and a transceiver 1410 for transmitting and receiving signals to and from other communication devices using one or more antennas 1401.
  • the communications circuitry 1402 may include circuitry that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals.
  • the communication device 1400 may also include processing circuitry 1406 and memory 1408 arranged to perform the operations described herein.
  • the communications circuitry 1402 and the processing circuitry 1406 may be configured to perform operations detailed in the above figures, diagrams, and flows.
  • Some embodiments are directed to an apparatus for a user equipment (UE) configured for operating in a fifth-generation (5G) new radio (NR) network comprising processing circuitry and memory.
  • UE user equipment
  • 5G fifth-generation
  • NR new radio
  • the communications circuitry 1402 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium.
  • the communications circuitry 1402 may be arranged to transmit and receive signals.
  • the communications circuitry 1402 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc.
  • the processing circuitry 1406 of the communication device 1400 may include one or more processors.
  • two or more antennas 1401 may be coupled to the communications circuitry 1402 arranged for sending and receiving signals.
  • the memory 1408 may store information for configuring the processing circuitry 1406 to perform operations for configuring and transmitting message frames and performing the various operations described herein.
  • the memory 1408 may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer).
  • the memory 1408 may include a computer-readable storage device, read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media.
  • the communication device 1400 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.
  • PDA personal digital assistant
  • a laptop or portable computer with wireless communication capability such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly
  • the communication device 1400 may include one or more antennas 1401.
  • the antennas 1401 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals.
  • a single antenna with multiple apertures may be used instead of two or more antennas.
  • each aperture may be considered a separate antenna.
  • MIMO multiple-input multiple-output
  • the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting device.
  • the communication device 1400 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements.
  • the display may be an LCD screen including a touch screen.
  • the communication device 1400 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein.
  • the functional elements of the communication device 1400 may refer to one or more processes operating on one or more processing elements.
  • Minimum number of device receive branches The number of receive branches is related to the number of receive antennas. Reducing the number of receive branches therefore results in a reduction in the number of receive antennas and cost saving.
  • the requirements on the minimum number of receive branches depends on frequency bands. Some frequency bands (most of the FR1 frequency-division duplex (FDD) bands, a handful of FR1 time-division duplex (TDD) bands, and all FR2 bands) require a baseline NR device to be equipped with two receive branches, whereas some other frequency bands, mostly in the FR1 TDD bands, require the device to be equipped with four receive branches.
  • FDD frequency-division duplex
  • TDD time-division duplex
  • a RedCap UE is only required to have one receive branch.
  • a baseline NR device is required to be equipped with a minimum of four receive branches, it is yet to be decided whether a RedCap UE is required to have one or two receive branches.
  • Maximum number of downlink MIMO layers The maximum number of downlink MIMO layers for a RedCap UE is the same as the number of receive branches it supports. This is a reduction compared to the requirements for a baseline device.
  • a baseline NR device is required to support 256QAM in the downlink in FR1.
  • the support of downlink 256QAM is optional.
  • a RedCap UE is required to support 64QAM, same as the requirement for a baseline device.
  • Duplex operation Regarding duplex operations, the only relaxation is for operations in FDD bands.
  • a baseline NR device is required to support a full duplex (FD) operation in an FDD band, i.e., transmitting and receiving on different frequencies at the same time.
  • a typical full-duplex device incorporates a duplex filter to isolate the interference between the device’s transmit and receive paths.
  • the same device may need to support multiple FDD bands; therefore, multiple duplex filters may be needed to support the FD-FDD operation.
  • a RedCap UE For a RedCap UE, the support of FD-FDD is optional, i.e., it is not required to receive in the downlink frequency while transmitting in the uplink frequency, and vice versa. Such a duplex operation is referred to as half duplex FDD (HD-FDD). HD-FDD obviates the need for duplex filters. Instead, a switch can be used to select the transmitter or receive to connect to the antenna. As a switch is less expensive than multiple duplexers, cost savings are achieved. [00242] Furthermore, a RedCap UE is expected to operate in a single band at a time and will not support carrier aggregation and dual connectivity.
  • HD-FDD half duplex FDD
  • a system and method to receive multiple overlapped DL channels for UE with reduced bandwidth comprising,
  • the UE is expected to decode two PDSCHs each scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC- RNTI, subjected to one of the following conditions,
  • the UE does not expect that the sum of the TBSs of multiple PDSCH(s) scheduled with SI-RNTI, P- RNTI, RA-RNTI or TC-RNTI in the same slot is larger than a threshold
  • the UE does not expect that the sum of multiple PDSCH(s) scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI in the same slot exceeds a maximum data rate.
  • the UE does not expect to decode more than one PDSCH scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI in a OFDM symbol or a slot
  • the UE is expected to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI and, for P- RNTI triggered or autonomous SI acquisition, another PDSCH scheduled with SI-RNTI in the same slot, subjected to one of the following conditions,
  • the UE only receive a subset of PRBs of the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS- RNTI in the OFDM symbol
  • the UE does not expect that the sum of the TBS of a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI and the TBS of another PDSCH scheduled with SI-RNTI in the same slot for P-RNTI triggered or autonomous SI acquisition is larger than a threshold
  • the UE does not expect that the sum of the TBS of a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI and the TBS of another PDSCH scheduled with SI-RNTI in the same slot for P-RNTI triggered or autonomous SI acquisition exceeds a maximum data rate.
  • the UE does not expect to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI and, for P-RNTI triggered or autonomous SI acquisition, another PDSCH scheduled with SI-RNTI in a OFDM symbol or a slot.
  • the UE does not expect to be scheduled or configured to process more than X ongoing PDSCH receptions and more than Y ongoing PUSCH transmissions, X,Y are predefined
  • the UE is not capable of receiving more than any OFDM symbol in a slot.
  • the UE is not capable of receiving more than a maximum number of REs in a slot.
  • a system and method to enhance the transmission in separate initial BWP for UE with reduced bandwidth comprising,
  • a UE Detected by a UE, a Physical Downlink Control Channel (PDCCH) Received or transmitted by the UE, the PDSCH or PUSCH scheduled by the PDCCH
  • PDCCH Physical Downlink Control Channel
  • a frequency region of up to NBW consecutive PRBs is identified first, then, the allocated frequency resource for DL/UL transmission is indicated within the identified frequency region, where NBW is the maximum number of PRBs that is supported by the UE.
  • the frequency region for DL/UL transmission is predefined, or determined by a fixed rule with respect to the CORESET #0, or semi-statically configured by high layer signaling, or activated by MAC CE.
  • the frequency resource for DL/UL transmission is dynamically allocated within the DL/UL BWP, subjected to a limitation that the allocated PRBs must be within localized NBW PRBS.
  • a frequency region and the allocated frequency resource within the frequency region are indicated by the header part and remaining part of the DFRA field
  • a frequency region of up to NBW distributed PRBs is identified first, then, the allocated frequency resource for DL/UL transmission is indicated within the identified frequency region, where NBW is the maximum number of PRBs that is supported by the UE.
  • the DL/UL BWP is divided into multiple combs and each comb is a frequency region.
  • a frequency region is a number equally spaced units in the DL/UL BWP.
  • the frequency region for DL/UL transmission is predefined, or determined by a fixed rule with respect to the CORESET #0, or semi-statically configured by high layer signaling, or activated by MAC CE.
  • the frequency resource for DL/UL transmission is dynamically allocated within the DL/UL BWP, subjected to a limitation that the allocated PRBs must be within NBW PRBS.
  • the header for frequency region indication is a separate field in the DCI format
  • the frequency resource is indicated directly within the BWP
  • the UE expects that each hop of the PDSCH or PUSCH transmission is located within a frequency region
  • the UE expects that each hop of the PDSCH or PUSCH transmission is located within a frequency region and the same FDRA as the first hop applies in each frequency region.
  • the UE expects that each hop of the PDSCH or PUSCH transmission is located within a frequency region and the mirror of the FDRA is applied within the frequency region of every second hop.
  • the UE expects that the first hop of the PDSCH or PUSCH transmission must be located within a frequency region, while other hops are allowed to cross the boundary of two frequency regions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un UE configuré pour fonctionner dans un réseau NR 5G peut décoder une signalisation qui planifie deux canaux partagés de liaison descendante physiques (PDSCH) dans un même créneau temporel. Lorsque l'UE est un UE à largeur de bande réduite (RBW) à capacité réduite (RedCap), l'UE peut déterminer si un nombre total de blocs de ressources physiques (PRB) attribués dans un symbole OFDM pour les deux PDSCH planifiés dépasse une valeur prédéterminée lorsque les deux PDSCH planifiés se chevauchent soit partiellement soit complètement dans le temps dans des PRB non chevauchants. L'UE peut également donner la priorité au décodage de l'un des deux PDSCH planifiés lorsque le nombre total de PRB attribués dépasse la valeur prédéterminée et lorsque les deux PDSCH planifiés se chevauchent soit partiellement soit complètement dans le temps dans des PRB non chevauchants. Si un premier des deux PDSCH planifiés est un PDSCH de monodiffusion et un second des deux PDSCH planifiés est un PDSCH de diffusion générale, l'UE peut donner la priorité au décodage du PDSCH de monodiffusion.
PCT/US2023/019071 2022-04-20 2023-04-19 Ue rbw-redcap configuré pour décoder des pdsch se chevauchant WO2023205213A1 (fr)

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
CNPCT/CN2022/087832 2022-04-20
CN2022087830 2022-04-20
CNPCT/CN2022/087830 2022-04-20
CN2022087832 2022-04-20
US202263411414P 2022-09-29 2022-09-29
US63/411,414 2022-09-29
US202263412155P 2022-09-30 2022-09-30
US63/412,155 2022-09-30
US202363487536P 2023-02-28 2023-02-28
US63/487,536 2023-02-28

Publications (1)

Publication Number Publication Date
WO2023205213A1 true WO2023205213A1 (fr) 2023-10-26

Family

ID=88420520

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/019071 WO2023205213A1 (fr) 2022-04-20 2023-04-19 Ue rbw-redcap configuré pour décoder des pdsch se chevauchant

Country Status (1)

Country Link
WO (1) WO2023205213A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101515931B1 (ko) * 2010-05-03 2015-05-04 퀄컴 인코포레이티드 릴레이 백홀 전송들에서의 물리적 다운링크 공유 채널(pdsch)에 대한 자원 이용가능성
WO2020168351A1 (fr) * 2019-02-15 2020-08-20 Apple Inc. Systèmes et procédés de multiplexage intra-ue dans la nouvelle radio (nr)
WO2020198645A1 (fr) * 2019-03-28 2020-10-01 Ali Cirik Multiplexage et hiérarchisation dans une nouvelle radio
WO2021071415A1 (fr) * 2019-10-11 2021-04-15 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et appareil permettant de gérer des transmissions de liaison descendante configurées et dynamiques dans un réseau de communication sans fil

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101515931B1 (ko) * 2010-05-03 2015-05-04 퀄컴 인코포레이티드 릴레이 백홀 전송들에서의 물리적 다운링크 공유 채널(pdsch)에 대한 자원 이용가능성
WO2020168351A1 (fr) * 2019-02-15 2020-08-20 Apple Inc. Systèmes et procédés de multiplexage intra-ue dans la nouvelle radio (nr)
WO2020198645A1 (fr) * 2019-03-28 2020-10-01 Ali Cirik Multiplexage et hiérarchisation dans une nouvelle radio
WO2021071415A1 (fr) * 2019-10-11 2021-04-15 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et appareil permettant de gérer des transmissions de liaison descendante configurées et dynamiques dans un réseau de communication sans fil

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MODERATOR (NTT DOCOMO, INC.): "Summary on [108-e-R16-UE-features-MIMO-01]", 3GPP DRAFT; R1-2202510, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20220221 - 20220303, 3 March 2022 (2022-03-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052131097 *

Similar Documents

Publication Publication Date Title
US11888592B2 (en) UE configured for multiplexing HARQ-ACK bits of different priorities in a PUCCH transmission
US20240155636A1 (en) Multi-slot pdcch monitoring in search space sets for higher carrier frequency operation
EP4201007A1 (fr) Indication de taille de faisceau de répétitions pour des transmissions de liaison montante dans un réseau nr 5g
EP4278796A1 (fr) Surveillance de pdcch à multiples créneaux pour fréquences porteuses élevées
WO2022087620A1 (fr) Rétroaction harq-ack pour transmissions pdsch de multidiffusion
WO2022031617A1 (fr) Indication dmrs dans des créneaux spéciaux permettant des opérations de spectre non appariées
WO2023205213A1 (fr) Ue rbw-redcap configuré pour décoder des pdsch se chevauchant
US20240114507A1 (en) Multi-tti scheduling of pdsch and pusch by dci
US20240014995A1 (en) Timing for non-overlapping sub-band full duplex (sbfd) operations in 5g nr
US20240172243A1 (en) Sounding reference signal (srs) transmissions triggered via downlink control information (dci) formats without scheduling information
US20240178946A1 (en) Multiplexing of uplink control information (uci) with different physical layer priorities
US20240187190A1 (en) Out-of-order handling for tboms scheduling in 5g nr
US20240163026A1 (en) Type-1 harq-ack codebook generation for multi-pdsch scheduling
US20240155637A1 (en) Dci format configured for varied bit interpretations
WO2023172418A1 (fr) Opération de partie de bande passante (bwp) et gestion de collision pour des communications en duplex intégral
WO2023154275A1 (fr) Commande de puissance de transmission pour groupage de dmrs pour amélioration de couverture
WO2023014405A1 (fr) Surveillance de pdcch à créneaux multiples dans des ensembles d'espace de recherche configurés
WO2023014544A1 (fr) Trame de canal et trame de signal de synchronisation pour fonctionner dans la bande de 57 ghz à 71 ghz
WO2023158672A1 (fr) Transmission de canal pdsch basée sur accusé de réception harq-ack planifiée par plusieurs attributions de liaison descendante
WO2023081161A1 (fr) Gestion de panne pour la programmation de tboms dans un nr 5g
WO2022087619A1 (fr) Hiérarchisation et multiplexage de pucch et pusch pour une transmission inter-porteuses
EP4275310A1 (fr) Harq-ack avec groupage dans le domaine temporel pour pdsch ordonnancés par dci à multi-tti
EP4278795A1 (fr) Bande passante de transmission de pucch étendue pour opération à fréquence porteuse élevée

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23792469

Country of ref document: EP

Kind code of ref document: A1