WO2022067856A1 - Procédés et appareil de détermination de paramètres pour un équipement d'utilisateur à capacité réduite - Google Patents

Procédés et appareil de détermination de paramètres pour un équipement d'utilisateur à capacité réduite Download PDF

Info

Publication number
WO2022067856A1
WO2022067856A1 PCT/CN2020/119790 CN2020119790W WO2022067856A1 WO 2022067856 A1 WO2022067856 A1 WO 2022067856A1 CN 2020119790 W CN2020119790 W CN 2020119790W WO 2022067856 A1 WO2022067856 A1 WO 2022067856A1
Authority
WO
WIPO (PCT)
Prior art keywords
redcap
resource blocks
physical resource
determining
bandwidth
Prior art date
Application number
PCT/CN2020/119790
Other languages
English (en)
Inventor
Jing Dai
Chao Wei
Qiaoyu Li
Min Huang
Chenxi HAO
Hao Xu
Changlong Xu
Original Assignee
Qualcomm Incorporated
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 Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2020/119790 priority Critical patent/WO2022067856A1/fr
Publication of WO2022067856A1 publication Critical patent/WO2022067856A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • 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/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • 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

  • aspects of the present disclosure relate generally to wireless communications, and more particularly, to apparatuses and methods for determining parameters for a reduced capability user equipment (RedCap UE) .
  • RedCap UE reduced capability user equipment
  • Wireless communication networks are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on.
  • These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) .
  • multiple-access systems include code-division multiple access (CDMA) systems, time-division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, orthogonal frequency-division multiple access (OFDMA) systems, and single-carrier frequency division multiple access (SC-FDMA) systems.
  • CDMA code-division multiple access
  • TDMA time-division multiple access
  • FDMA frequency-division multiple access
  • OFDMA orthogonal frequency-division multiple access
  • SC-FDMA single-carrier frequency division multiple access
  • 5G communications technology may include: enhanced mobile broadband addressing human-centric use cases for access to multimedia content, services and data; ultra-reliable-low latency communications (URLLC) with certain specifications for latency and reliability; and massive machine type communications, which may allow a very large number of connected devices and transmission of a relatively low volume of non-delay-sensitive information.
  • URLLC ultra-reliable-low latency communications
  • massive machine type communications which may allow a very large number of connected devices and transmission of a relatively low volume of non-delay-sensitive information.
  • a base station may communicate with a RedCap UE.
  • a RedCap UE may have lower capabilities (e.g., bandwidth capability) than a non-RedCap UE. If the BS communicates with the RedCap UE based on parameters associated with the non-RedCap UE, the RedCap UE may be unable to transmit and/or receive information properly. Therefore, improvements in RedCap UE communication may be desirable.
  • aspects of the present disclosure include methods by a reduced capability user equipment (RedCap UE) for identifying a bandwidth capability associated with the RedCap UE for a frequency range, determining a number of physical resource blocks based on the bandwidth capability, determining a circular buffer size based on the number of physical resource blocks, and transmitting or receiving information based on the circular buffer size.
  • RedCap UE reduced capability user equipment
  • RedCap UE having a memory comprising instructions, a transceiver, and one or more processors coupled (e.g., operatively, communicatively, functionally, electronically, and/or electrically) with the memory and the transceiver, the memory storing instructions executable by the one or more processors to cause the RedCap UE to identify a bandwidth capability associated with the RedCap UE for a frequency range, determine a number of physical resource blocks based on the bandwidth capability, determine a circular buffer size based on the number of physical resource blocks, and transmit or receive, via the transceiver, information based on the circular buffer size.
  • An aspect of the present disclosure includes a RedCap UE including means for identifying a bandwidth capability associated with the RedCap UE for a frequency range, means for determining a number of physical resource blocks based on the bandwidth capability, means for determining a circular buffer size based on the number of physical resource blocks, and means for transmitting or receiving information based on the circular buffer size.
  • Some aspects of the present disclosure include non-transitory computer readable media having instructions stored therein that, when executed by one or more processors of a RedCap UE, cause the RedCap UE to identify a bandwidth capability associated with the RedCap UE for a frequency range, determine a number of physical resource blocks based on the bandwidth capability, determine a circular buffer size based on the number of physical resource blocks, and transmit or receive, via the transceiver, information based on the circular buffer size.
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
  • FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network
  • FIG. 2 is a schematic diagram of an example of a user equipment
  • FIG. 3 is a schematic diagram of an example of a base station
  • FIG. 4 illustrates examples of quantization tables indicating the n PRB of a RedCap UE according to aspects of the present disclosure
  • FIG. 5 illustrates additional examples of quantization tables indicating the n PRB of a RedCap UE according to aspects of the present disclosure
  • FIG. 6 is an example of a method for determining the circular buffer size of a RedCap UE according to aspects of the present disclosure.
  • processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • processors in the processing system may execute software.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes computer storage media. Storage media may be any available media that may be accessed by a computer.
  • such computer-readable media may comprise a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that may be used to store computer executable code in the form of instructions or data structures that may be accessed by a computer.
  • RAM random-access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable ROM
  • optical disk storage magnetic disk storage
  • magnetic disk storage other magnetic storage devices
  • combinations of the aforementioned types of computer-readable media or any other medium that may be used to store computer executable code in the form of instructions or data structures that may be accessed by a computer.
  • UE user equipment
  • the peak throughput, latency, and/or reliability may be relaxed in exchange for efficiency (e.g. power consumption and system overhead) and/or cost reduction.
  • Examples of such UE e.g., RedCap UE
  • wearables e.g., smart watches
  • IWSN industrial wireless sensor network
  • security devices e.g., surveillance cameras
  • the communication network may allow dynamic sharing of a soft buffer among different hybrid automatic repeat request (HARQ) processes as an UE implementation.
  • the communication network may specify limited buffer rate matching (LBRM) for peak data rate with a transport block size (TBS) that prevents a buffer being occupied by a single HARQ process.
  • LBRM limited buffer rate matching
  • TBS transport block size
  • R LBRM radio resource control
  • CB code block
  • RRC radio resource control
  • the TBS may be determined based on one or more of (1) a maximum number of multiple-input multiple-output (MIMO) layers (either UE-supported max layer or configured under the serving cell) , (2) a highest modulation order based on the configured MCS table (e.g., 8 for 256QAM, or 6 for 64QAM if the MCS table with highest modulation order as 256QAM is not configured) , (3) a highest coding rate of 948/1024, (4) 156 resource elements (REs) per physical resource block (PRB) slot (e.g., 14-symbol physical downlink shared channel (PDSCH) with 1-symbol demodulation reference signal (DMRS) ) , and/or (5) a bandwidth n PRB, LBRM obtained by ceiling-quantize the configured downlink (DL) bandwidth part (BWP) .
  • MIMO multiple-input multiple-output
  • the soft buffer size of a single HARQ process may approach approximately encoded bits.
  • lower coding rate may be supported for circular buffer.
  • a low full coding rate supported by the network may be 1/3 for a first base matrix (e.g., BG1) and 1/5 for a second base matrix (e.g., BG2) .
  • LBRM may be used for DL transmissions (e.g., PDSCH) , and is configurable for UL transmission (e.g., PUSCH) .
  • a RedCap UE may have reduced capabilities, such as a reduced maximum bandwidth, compared to a non-RedCap UE. Due to the reduced maximum bandwidth (e.g., 20 Megahertz (MHz) BWP configured) , the TBS LBRM determined via the methods above may exceed the capability of the RedCap UE, resulting in over processing capacity.
  • the processing capacity e.g., the soft buffer size, low density parity check (LDPC) decoding throughput, etc.
  • LDPC low density parity check
  • the circular buffer size (N cb ) and/or the LBRM TBS (TBS LBRM ) may be determined by the maximum bandwidth supported by the RedCap UE (e.g., 20 MHz in sub-6 Gigahertz (GHz) frequency bands (FR1) and/or 50 MHz or 100 MHz for millimeter wave frequency bands (FR2) ) .
  • the RedCap UE may first determine the number of PRBs (n PRB ) .
  • the RedCap UE may identify the n PRB used for computing the N cb and/or TBS LBRM for the RedCap UE based on entries of a quantization table.
  • the entries and/or the quantization table may be grouped based on the capabilities of the RedCap UE (e.g., based on the supported bandwidth (BW) of the RedCap UE) , frequency range (e.g., FR1 or FR2) , or other variables.
  • the RedCap UE may determine the n PRB used for computing the N cb and/or TBS LBRM for the RedCap UE by determining the n PRB, LBRM by quantizing a maximum number of physical resource blocks across configured downlink bandwidth parts for a downlink shared channel of a carrier and uplink bandwidth parts for an uplink shared channel of the carrier, determining the maximum n PRB (n PRB, MAX ) associated with the maximum BW supported by the RedCap UE, and identifying the lower of the n PRB, LBRM and n PRB, MAX .
  • the RedCap UE may select the lower of the two parameters as the n PRB used for computing the N cb and/or TBS LBRM for the RedCap UE.
  • the n PRB, MAX may be determined by the subcarrier spacing of the configured BWP with the maximum number of PRBs across all configured BWPs.
  • the RedCap UE may determine the n PRB used for computing the N cb and/or TBS LBRM for the RedCap UE by identifying a non-RedCap bandwidth capability associated with a non-RedCap UE for the frequency range, determining a scaling factor based on a ratio of the non-RedCap bandwidth capability of the non-RedCap UE and the bandwidth capability of the RedCap UE, determining the n PRB associated with the non-RedCap UE based on the non-RedCap bandwidth capability, and determining the n PRB of the RedCap UE by dividing the n PRB of the non-RedCap UE by the scaling factor.
  • the modulation order (Q m ) for the N cb and/or TBS LBRM calculation may be based on the maximum modulation order associated with the UE capability of the RedCap UE.
  • a different R LBRM e.g., higher than the R LBRM of the non-RedCap UE may be used.
  • FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100.
  • the wireless communications system (also referred to as a wireless wide area network (WWAN) ) includes at least one BS 105, UEs 110, an Evolved Packet Core (EPC) 160, and a 5G Core (5GC) 190.
  • the BS 105 may include macro cells (high power cellular base station) and/or small cells (low power cellular base station) .
  • the macro cells include base stations.
  • the small cells include femtocells, picocells, and microcells.
  • the UEs 110 described herein may include one or more RedCap UEs having less capabilities (e.g., bandwidth capability) than a non-RedCap UE.
  • the UE 110 may include a communication component 222 configured to communicate with the BS 105 via a cellular network, a Wi-Fi network, or other wireless and wired networks.
  • the UE 110 may include an identification component 224 configured to identify a bandwidth capability of the UE 110.
  • the UE 110 may include a determination component 226 configured to determine a number of physical resource blocks and/or a circular buffer size of the UE 110.
  • the communication component 222, the identification component 224, and/or the determination component 226 may be implemented using hardware, software, or a combination of hardware and software.
  • the BS 105 may include a communication component 322 configured to communicate with the UE 110.
  • the communication component 322 may be implemented using hardware, software, or a combination of hardware and software.
  • a BS 105 configured for 4G Long-Term Evolution (LTE) may interface with the EPC 160 through backhaul links interfaces 132 (e.g., S1, X2, Internet Protocol (IP) , or flex interfaces) .
  • LTE Long-Term Evolution
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • a BS 105 configured for 5G NR may interface with 5GC 190 through backhaul links interfaces 134 (e.g., S1, X2, Internet Protocol (IP) , or flex interface) .
  • NG-RAN Next Generation RAN
  • the BS 105 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity) , inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS) , subscriber and equipment trace, RAN information management (RIM) , paging, positioning, and delivery of warning messages.
  • the BS 105 may communicate directly or indirectly (e.g., through the EPC 160 or 5GC 190) with each other over the backhaul links interfaces 134.
  • the backhaul links 132, 134 may be wired or wireless.
  • the BS 105 may wirelessly communicate with the UEs 110. Each of the BS 105 may provide communication coverage for a respective geographic coverage area 130. There may be overlapping geographic coverage areas 130. For example, the small cell 105' may have a coverage area 130' that overlaps the coverage area 130 of one or more macro BS 105.
  • a network that includes both small cell and macro cells may be known as a heterogeneous network.
  • a heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) .
  • eNBs Home Evolved Node Bs
  • HeNBs Home Evolved Node Bs
  • CSG closed subscriber group
  • the communication links 120 between the BS 105 and the UEs 110 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 110 to a BS 105 and/or downlink (DL) (also referred to as forward link) transmissions from a BS 105 to a UE 110.
  • the communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity.
  • the communication links may be through one or more carriers.
  • the BS 105 /UEs 110 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc.
  • the component carriers may include a primary component carrier and one or more secondary component carriers.
  • a primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .
  • D2D communication link 158 may use the DL/UL WWAN spectrum.
  • the D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • D2D communication may be through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia,
  • the wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in a 5 GHz unlicensed frequency spectrum.
  • AP Wi-Fi access point
  • STAs Wi-Fi stations
  • communication links 154 in a 5 GHz unlicensed frequency spectrum.
  • the STAs 152 /AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
  • CCA clear channel assessment
  • the small cell 105' may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 105' may employ NR and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP 150. The small cell 105', employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.
  • a BS 105 may include an eNB, gNodeB (gNB) , or other type of base station.
  • Some base stations, such as gNB 180 may operate in one or more frequency bands within the electromagnetic spectrum.
  • the electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc.
  • two initial operating bands have been identified as frequency range designations FR1 (410 MHz –7.125 GHz) and FR2 (24.25 GHz –52.6 GHz) .
  • the frequencies between FR1 and FR2 are often referred to as mid-band frequencies.
  • FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles.
  • FR2 which is often referred to (interchangeably) as a “millimeter wave” (mmW) band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
  • EHF extremely high frequency
  • sub-6 GHz or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies.
  • millimeter wave or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.
  • Communications using the mmW /near mmW radio frequency band has extremely high path loss and a short range.
  • the mmW base station 180 may utilize beamforming 182 with the UE 110 to compensate for the path loss and short range.
  • the EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172.
  • MME Mobility Management Entity
  • MBMS Multimedia Broadcast Multicast Service
  • BM-SC Broadcast Multicast Service Center
  • PDN Packet Data Network
  • the MME 162 may be in communication with a Home Subscriber Server (HSS) 174.
  • HSS Home Subscriber Server
  • the MME 162 is the control node that processes the signaling between the UEs 110 and the EPC 160.
  • the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172.
  • IP Internet protocol
  • the PDN Gateway 172 provides UE IP address allocation as well as other functions.
  • the PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176.
  • the IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a packet switched (PS) Streaming Service, and/or other IP services.
  • the BM-SC 170 may provide functions for MBMS user service provisioning and delivery.
  • the BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and may be used to schedule MBMS transmissions.
  • PLMN public land mobile network
  • the MBMS Gateway 168 may be used to distribute MBMS traffic to the BS 105 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.
  • MMSFN Multicast Broadcast Single Frequency Network
  • the 5GC 190 may include a Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195.
  • the AMF 192 may be in communication with a Unified Data Management (UDM) 196.
  • the AMF 192 is the control node that processes the signaling between the UEs 110 and the 5GC 190.
  • the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195.
  • the UPF 195 provides UE IP address allocation as well as other functions.
  • the UPF 195 is connected to the IP Services 197.
  • the IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and/or other IP services.
  • IMS IP Multimedia Subsystem
  • the BS 105 may also be referred to as a gNB, Node B, evolved Node B (eNB) , an access point, a base transceiver station, a radio base station, an access point, an access node, a radio transceiver, a NodeB, eNodeB (eNB) , gNB, Home NodeB, a Home eNodeB, a relay, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a transmit reception point (TRP) , or some other suitable terminology.
  • the BS 105 provides an access point to the EPC 160 or 5GC 190 for a UE 110.
  • Examples of UEs 110 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device.
  • SIP session initiation protocol
  • PDA personal digital assistant
  • the UEs 110 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) .
  • the UE 110 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
  • one example of an implementation of the UE 110 may include a modem 220 having the communication component 222, the identification component 224, and/or the determination component 226.
  • the UE 110 may include a communication component 222 configured to communicate with the BS 105 via a cellular network, a Wi-Fi network, or other wireless and wired networks.
  • the UE 110 may include an identification component 224 configured to identify a bandwidth capability of the UE 110.
  • the UE 110 may include a determination component 226 configured to determine a number of physical resource blocks and/or a circular buffer size of the UE 110.
  • the UE 110 may include a variety of components, including components such as one or more processors 212 and memory 216 and transceiver 202 in communication via one or more buses 244, which may operate in conjunction with the modem 220 and the communication component 222 to enable one or more of the functions described herein related to communicating with the BS 105.
  • the one or more processors 212, modem 220, memory 216, transceiver 202, RF front end 288 and one or more antennas 265, may be configured to support voice and/or data calls (simultaneously or non-simultaneously) in one or more radio access technologies.
  • the one or more antennas 265 may include one or more antennas, antenna elements and/or antenna arrays.
  • the one or more processors 212 may include the modem 220 that uses one or more modem processors.
  • the various functions related to the communication component 222, the identification component 224, and/or the determination component 226 may be included in the modem 220 and/or processors 212 and, in an aspect, may be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors.
  • the one or more processors 212 may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiving device processor, or a transceiver processor associated with transceiver 202.
  • the modem 220 may configure the UE 110 along with the processors 212. In other aspects, some of the features of the one or more processors 212 and/or the modem 220 associated with the communication component 222 may be performed by transceiver 202.
  • the memory 216 may be configured to store data used and/or local versions of application 275. Also, the memory 216 may be configured to store data used herein and/or local versions of the communication component 222, the identification component 224, and/or the determination component 226, and/or one or more of the subcomponents being executed by at least one processor 212.
  • Memory 216 may include any type of computer-readable medium usable by a computer or at least one processor 212, such as random access memory (RAM) , read only memory (ROM) , tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof.
  • memory 216 may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining the communication component 222, the identification component 224, and/or the determination component 226, and/or one or more of the subcomponents, and/or data associated therewith, when UE 110 is operating at least one processor 212 to execute the communication component 222, the identification component 224, and/or the determination component 226, and/or one or more of the subcomponents.
  • Transceiver 202 may include at least one receiver 206 and at least one transmitter 208.
  • Receiver 206 may include hardware, and/or software code executable by a processor for receiving data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium) .
  • Receiver 206 may be, for example, a RF receiving device.
  • the receiver 206 may receive signals transmitted by at least one BS 105.
  • Transmitter 208 may include hardware, and/or software code executable by a processor for transmitting data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium) .
  • a suitable example of transmitter 208 may including, but is not limited to, an RF transmitter.
  • UE 110 may include RF front end 288, which may operate in communication with one or more antennas 265 and transceiver 202 for receiving and transmitting radio transmissions, for example, wireless communications transmitted by at least one BS 105 or wireless transmissions transmitted by UE 110.
  • RF front end 288 may be coupled with one or more antennas 265 and may include one or more low-noise amplifiers (LNAs) 290, one or more switches 292, one or more power amplifiers (PAs) 298, and one or more filters 296 for transmitting and receiving RF signals.
  • LNAs low-noise amplifiers
  • PAs power amplifiers
  • LNA 290 may amplify a received signal at a desired output level.
  • each LNA 290 may have a specified minimum and maximum gain values.
  • RF front end 288 may use one or more switches 292 to select a particular LNA 290 and the specified gain value based on a desired gain value for a particular application.
  • one or more PA (s) 298 may be used by RF front end 288 to amplify a signal for an RF output at a desired output power level.
  • each PA 298 may have specified minimum and maximum gain values.
  • RF front end 288 may use one or more switches 292 to select a particular PA 298 and the specified gain value based on a desired gain value for a particular application.
  • one or more filters 296 may be used by RF front end 288 to filter a received signal to obtain an input RF signal.
  • a respective filter 296 may be used to filter an output from a respective PA 298 to produce an output signal for transmission.
  • each filter 296 may be coupled with a specific LNA 290 and/or PA 298.
  • RF front end 288 may use one or more switches 292 to select a transmit or receive path using a specified filter 296, LNA 290, and/or PA 298, based on a configuration as specified by transceiver 202 and/or processor 212.
  • transceiver 202 may be configured to transmit and receive wireless signals through one or more antennas 265 via RF front end 288.
  • transceiver may be tuned to operate at specified frequencies such that UE 110 may communicate with, for example, one or more BS 105 or one or more cells associated with one or more BS 105.
  • the modem 220 may configure transceiver 202 to operate at a specified frequency and power level based on the UE configuration of the UE 110 and the communication protocol used by the modem 220.
  • the modem 220 may be a multiband-multimode modem, which may process digital data and communicate with transceiver 202 such that the digital data is sent and received using transceiver 202.
  • the modem 220 may be multiband and be configured to support multiple frequency bands for a specific communications protocol.
  • the modem 220 may be multimode and be configured to support multiple operating networks and communications protocols.
  • the modem 220 may control one or more components of UE 110 (e.g., RF front end 288, transceiver 202) to enable transmission and/or reception of signals from the network based on a specified modem configuration.
  • the modem configuration may be based on the mode of the modem and the frequency band in use.
  • the modem configuration may be based on UE configuration information associated with UE 110 as provided by the network.
  • one example of an implementation of the BS 105 may include a modem 320 having the communication component 322.
  • the BS 105 may include a communication component 322 configured to communicate with the UE 110.
  • the BS 105 may include a variety of components, including components such as one or more processors 312 and memory 316 and transceiver 302 in communication via one or more buses 344, which may operate in conjunction with the modem 320 and the communication component 322 to enable one or more of the functions described herein related to communicating with the UE 110.
  • the one or more processors 312, modem 320, memory 316, transceiver 302, RF front end 388 and one or more antennas 365 may be configured to support voice and/or data calls (simultaneously or non-simultaneously) in one or more radio access technologies.
  • the one or more processors 312 may include the modem 320 that uses one or more modem processors.
  • the various functions related to the communication component 322 may be included in the modem 320 and/or processors 312 and, in an aspect, may be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors.
  • the one or more processors 312 may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiving device processor, or a transceiver processor associated with transceiver 302.
  • the modem 320 may configure the BS 105 and processors 312. In other aspects, some of the features of the one or more processors 312 and/or the modem 320 associated with the communication component 322 may be performed by transceiver 302.
  • the memory 316 may be configured to store data used herein and/or local versions of applications 375. Also, the memory 316 may be configured to store data used herein and/or local versions of the communication component 322, and/or one or more of the subcomponents being executed by at least one processor 312.
  • Memory 316 may include any type of computer-readable medium usable by a computer or at least one processor 312, such as random access memory (RAM) , read only memory (ROM) , tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof.
  • memory 316 may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining the communication component 322, and/or one or more of the subcomponents, and/or data associated therewith, when the BS 105 is operating at least one processor 312 to execute the communication component 322, and/or one or more of the subcomponents.
  • Transceiver 302 may include at least one receiver 306 and at least one transmitter 308.
  • the at least one receiver 306 may include hardware, and/or software code executable by a processor for receiving data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium) .
  • the receiver 306 may be, for example, a RF receiving device.
  • receiver 306 may receive signals transmitted by the UE 110.
  • Transmitter 308 may include hardware, and/or software code executable by a processor for transmitting data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium) .
  • a suitable example of transmitter 308 may including, but is not limited to, an RF transmitter.
  • the BS 105 may include RF front end 388, which may operate in communication with one or more antennas 365 and transceiver 302 for receiving and transmitting radio transmissions, for example, wireless communications transmitted by other BS 105 or wireless transmissions transmitted by UE 110.
  • RF front end 388 may be coupled with one or more antennas 365 and may include one or more low-noise amplifiers (LNAs) 390, one or more switches 392, one or more power amplifiers (PAs) 398, and one or more filters 396 for transmitting and receiving RF signals.
  • LNAs low-noise amplifiers
  • PAs power amplifiers
  • LNA 390 may amplify a received signal at a desired output level.
  • each LNA 390 may have a specified minimum and maximum gain values.
  • RF front end 388 may use one or more switches 392 to select a particular LNA 390 and the specified gain value based on a desired gain value for a particular application.
  • one or more PA (s) 398 may be used by RF front end 388 to amplify a signal for an RF output at a desired output power level.
  • each PA 398 may have specified minimum and maximum gain values.
  • RF front end 388 may use one or more switches 392 to select a particular PA 398 and the specified gain value based on a desired gain value for a particular application.
  • one or more filters 396 may be used by RF front end 388 to filter a received signal to obtain an input RF signal.
  • a respective filter 396 may be used to filter an output from a respective PA 398 to produce an output signal for transmission.
  • each filter 396 may be coupled with a specific LNA 390 and/or PA 398.
  • RF front end 388 may use one or more switches 392 to select a transmit or receive path using a specified filter 396, LNA 390, and/or PA 398, based on a configuration as specified by transceiver 302 and/or processor 312.
  • transceiver 302 may be configured to transmit and receive wireless signals through one or more antennas 365 via RF front end 388.
  • transceiver may be tuned to operate at specified frequencies such that BS 105 may communicate with, for example, the UE 110 or one or more cells associated with one or more BS 105.
  • the modem 320 may configure transceiver 302 to operate at a specified frequency and power level based on the base station configuration of the BS 105 and the communication protocol used by the modem 320.
  • the modem 320 may be a multiband-multimode modem, which may process digital data and communicate with transceiver 302 such that the digital data is sent and received using transceiver 302.
  • the modem 320 may be multiband and be configured to support multiple frequency bands for a specific communications protocol.
  • the modem 320 may be multimode and be configured to support multiple operating networks and communications protocols.
  • the modem 320 may control one or more components of the BS 105 (e.g., RF front end 388, transceiver 302) to enable transmission and/or reception of signals from the network based on a specified modem configuration.
  • the modem configuration may be based on the mode of the modem and the frequency band in use.
  • the modem configuration may be based on base station configuration associated with the BS 105.
  • FIG. 4 illustrates examples of quantization tables indicating the n PRB of a RedCap UE.
  • a quantization table may include entries associating one or more values of n PRB, MAX of a UE (e.g., RedCap UE or non-RedCap UE) to one or more values of n PRB .
  • a first quantization table 400 and/or a second quantization table 450 may indicate the n PRB associated with the UE 110 (e.g., a RedCap) .
  • the UE 110 may identify the n PRB used for computing the N cb and/or TBS LBRM for the RedCap UE based on entries of the quantization table 400.
  • the entries and/or the quantization tables 400, 450 may be grouped based on the capabilities of the UE 110 (e.g., based on the supported bandwidth (BW) of the UE 110) , frequency range (e.g., FR1 or FR2) , or other variables.
  • the quantization tables 400, 450 may be modified tables from one or more quantization tables associated with a non-RedCap UE (not shown) , or stand-alone tables associated with the RedCap UE (e.g., the UE 110) .
  • the first quantization table 400 may be associated with the UE 110 configured to support a maximum bandwidth of 20 MHz in FR1.
  • the subcarrier spacings may be 15 kilohertz (kHz) , 30 kHz, or 60 kHz.
  • the UE 110 may determine that, for n PRB, MAX of 25 to 51, the n PRB used for determining the N cb and/or TBS LBRM for the UE 110 is be the corresponding n PRB, LBRM value indicated in the first quantization table 400, or 51.
  • the UE 110 may determine that, for n PRB, MAX of 52 to 107, the n PRB used for determining the N cb and/or TBS LBRM for the UE 110 is 107.
  • the second quantization table 450 may be associated with the UE 110 configured to support a maximum bandwidth of 20 MHz in FR1.
  • the subcarrier spacings may be 15 kHz or 30 kHz.
  • the UE 110 may determine that, for n PRB, MAX of less than 52, the n PRB used for determining the N cb and/or TBS LBRM for the UE 110 is be the corresponding n PRB, LBRM value indicated in the second quantization table 450, or 51.
  • the UE 110 may determine that, for n PRB, MAX of 52 to 107, the n PRB used for determining the N cb and/or TBS LBRM for the UE 110 is 107.
  • FIG. 5 illustrates additional examples of quantization tables indicating the n PRB of a RedCap UE.
  • a quantization table may include entries associating one or more values of n PRB, MAX of a UE (e.g., RedCap UE or non-RedCap UE) to one or more values of n PRB .
  • a first quantization table 500 and/or a second quantization table 550 may indicate the n PRB associated with the UE 110 (e.g., a RedCap) .
  • the UE 110 may identify the n PRB used for computing the N cb and/or TBS LBRM for the RedCap UE based on entries of the quantization table 500.
  • the entries and/or the quantization tables 500, 550 may be grouped based on the capabilities of the UE 110 (e.g., based on the supported bandwidth (BW) of the UE 110) , frequency range (e.g., FR1 or FR2) , or other variables.
  • the quantization tables 500, 550 may be modified tables from one or more quantization tables associated with a non-RedCap UE (not shown) , or stand-alone tables associated with the RedCap UE (e.g., the UE 110) .
  • the first quantization table 500 may be associated with the UE 110 configured to support a maximum bandwidth of 20 MHz in FR1.
  • the subcarrier spacings may be 15 kilohertz (kHz) , 30 kHz, or 60 kHz.
  • the UE 110 may determine that, for n PRB, MAX of 26 to 52, the n PRB used for determining the N cb and/or TBS LBRM for the UE 110 is be the corresponding n PRB, LBRM value indicated in the first quantization table 500, or 52.
  • the UE 110 may determine that, for n PRB, MAX of 53 to 107, the n PRB used for determining the N cb and/or TBS LBRM for the UE 110 is 107.
  • the second quantization table 550 may be associated with the UE 110 configured to support a maximum bandwidth of 20 MHz in FR1.
  • the subcarrier spacings may be 15 kHz or 30 kHz.
  • the UE 110 may determine that, for n PRB, MAX of less than 53, the n PRB used for determining the N cb and/or TBS LBRM for the UE 110 is be the corresponding n PRB, LBRM value indicated in the second quantization table 550, or 52.
  • the UE 110 may determine that, for n PRB, MAX of 53 to 107, the n PRB used for determining the N cb and/or TBS LBRM for the UE 110 is 107.
  • the UE 110 may determine the n PRB used for computing the N cb and/or TBS LBRM for the UE 110 by determining the n PRB, LBRM based on quantizing a maximum number of PRBs across configured DL BWP for a DL shared channel of a carrier and the UL BWP for an UL shared channel of the carrier and determining the n PRB, MAX associated with the maximum BW supported by the UE 110.
  • the UE 110 may compare the n PRB, LBRM and the n PRB, MAX to determine a lower value.
  • the UE 110 E may select the lower of the two values as the n PRB used for computing the N cb and/or TBS LBRM for the UE 110.
  • the n PRB, MAX may be determined by the subcarrier spacing of the configured BWP with the maximum number of PRBs across all configured BWPs.
  • the UE 110 may determine the n PRB used for computing the N cb and/or TBS LBRM for the UE 110 by identifying a non-RedCap bandwidth capability associated with a non-RedCap UE for the frequency range (e.g., FR1 or FR2) .
  • the UE 110 may determine a scaling factor based on a ratio of the non-RedCap bandwidth capability of the non-RedCap UE and the bandwidth capability of the UE 110, determining the n PRB associated with the non-RedCap UE based on the non- RedCap bandwidth capability, and determining the n PRB of the UE 110 by dividing the n PRB of the non-RedCap UE by the scaling factor.
  • the bandwidth capability of the non-RedCap UE may be 100 MHz and the bandwidth capability of the UE 110 (which is a RedCap UE) is 20 MHz.
  • the UE 110 may determine that the scaling factor is 5.
  • the UE 110 may identify the n PRB associated with the non-RedCap UE based on the non-RedCap bandwidth capability (e.g., 100 MHz) .
  • the n PRB associated with the non-RedCap UE may be 273.
  • the UE 110 may divide 273 by 5 to obtain 55 (rounded up to the nearest unit digit) or 54 (rounded down to the nearest unit digit) .
  • the BS 105 may transmit the scaling factor to the UE 110.
  • the modulation order (Q m ) for the N cb and/or TBS LBRM calculation may be based on the maximum modulation order associated with the UE capability of the UE 110.
  • the modulation order may be 6 for FR1, 4 for FR2 because the UE 110 may support 64 quadrature amplitude modulate (QAM) for FR1 and 16 QAM for FR2 for the DL communications.
  • the modulation order may be 4 for FR1 and FR2 because the UE 110 may support 64 QAM for both FR 1 and FR2 for the UL communications.
  • the LBRM may be configurable for UL for the soft buffer (e.g., cost) saving of the BS 105.
  • a different R LBRM (e.g., higher than the R LBRM of the non-UE 110) may be used.
  • FIG. 6 is an example of a method for determining the circular buffer size of a RedCap UE.
  • a method 600 may be performed by one or more of the processor 212, the memory 216, the applications 275, the modem 220, the transceiver 202, the receiver 206, the transmitter 208, the RF front end 288, the communication component 222, the identification component 224, and/or the determination component 226, and/or one or more other components of the UE 110 in the wireless communication network 100.
  • the method 600 may identify a bandwidth capability associated with the RedCap UE for a frequency range.
  • the identification component 224, the processor 212, the memory 216, the modem 220, and/or the applications 275 of the UE 110 may identify a bandwidth capability associated with the RedCap UE for a frequency range as described above.
  • the identification component 224, the processor 212, the memory 216, the modem 220, and/or the applications 275 may be configured to and/or may define means for identifying a bandwidth capability associated with the RedCap UE for a frequency range.
  • the method 600 may determine a number of physical resource blocks based on the bandwidth capability.
  • the determination component 226, the processor 212, the memory 216, the modem 220, and/or the applications 275 of the UE 110 may determine a number of physical resource blocks based on the bandwidth capability as described above.
  • the determination component 226, the processor 212, the memory 216, the modem 220, and/or the applications 275 may be configured to and/or may define means for determining a number of physical resource blocks based on the bandwidth capability.
  • the method 600 may determine a circular buffer size based on the number of physical resource blocks.
  • the determination component 226, the processor 212, the memory 216, the modem 220, and/or the applications 275 of the UE 110 may determine a circular buffer size based on the number of physical resource blocks as described above.
  • the determination component 226, the processor 212, the memory 216, the modem 220, and/or the applications 275 may be configured to and/or may define means for determining a circular buffer size based on the number of physical resource blocks.
  • the method 600 may transmit or receive, via the transceiver, information based on the circular buffer size.
  • the communication component 222, the transceiver 202, the receiver 206, the transmitter 208, the RF front end 288, the subcomponents of the RF front end 288, the processor 212, the memory 216, the modem 220, and/or the applications 275 of the UE 110 may transmit or receive, via the transceiver, information based on the circular buffer size as described above.
  • the transceiver 202 or the transmitter 208 may convert the digital signals to electrical signals and send to the RF front end 288.
  • the RF front end 288 may filter and/or amplify the electrical signals.
  • the RF front end 288 may send the electrical signals as electro-magnetic signals via the one or more antennas 265.
  • the RF front end 288 may receive the electrical signals converted from electro-magnetic signals.
  • the RF front end 288 may filter and/or amplify the electrical signals.
  • the transceiver 202 or the receiver 206 may convert the electrical signals to digital signals, and send the digital signals to the communication component 222.
  • the communication component 222 may send the digital signals to the transceiver 202 or the transmitter 208.
  • the communication component 222, the transceiver 202, the receiver 206, the transmitter 208, the RF front end 288, the subcomponents of the RF front end 288, the processor 212, the memory 216, the modem 220, and/or the applications 275 may be configured to and/or may define means for transmitting or receiving information based on the circular buffer size.
  • the method 600 may further include any of the methods above, wherein determining the number of physical resource blocks comprises identifying the number of physical resource blocks from a quantization table associated with the RedCap UE.
  • the quantization table may be stored in the memory 216 of the UE 110.
  • the method 600 may further include any of the methods above, wherein the quantization table comprises one or more numbers of physical resource blocks for each of one or more subcarrier spacings associated with the bandwidth capability of the RedCap UE.
  • the method 600 may further include any of the methods above, wherein a first subset of the one or more subcarrier spacings is associated with sub-6 Gigahertz frequency bands and a second subset of the one or more subcarrier spacings is associated with millimeter wave frequency bands.
  • the method 600 may further include any of the methods above, wherein determining the number of physical resource blocks comprises determining a number of limited buffer rate-matching (LBRM) physical resource blocks by quantizing a maximum number of physical resource blocks across configured downlink bandwidth parts for a downlink shared channel of a carrier and uplink bandwidth parts for an uplink shared channel of the carrier, determining a maximum bandwidth supported by the RedCap UE, comparing the number of LBRM physical resource blocks and the number of maximum bandwidth, determining a lower number of the number of LBRM physical resource blocks and the number of maximum bandwidth, and determining the number of physical resource blocks based on the lower number.
  • LBRM limited buffer rate-matching
  • the method 600 may further include any of the methods above, wherein determining the number of physical resource blocks comprises identifying a non-RedCap bandwidth capability associated with a non-RedCap UE for the frequency range, determining a scaling factor based on a ratio of the non-RedCap bandwidth capability of the non-RedCap UE and the bandwidth capability of the RedCap UE, determining a non-RedCap number of physical resource blocks based on the non-RedCap bandwidth capability, and determining the number of physical resource blocks by dividing the non-RedCap number of physical resource blocks by the scaling factor.
  • the method 600 may further include any of the methods above, wherein determining the circular buffer size comprises determining the circular buffer size based on a modulation order associated with the RedCap UE.
  • the method 600 may further include any of the methods above, further comprising encoding or decoding the information with a limited buffer rate-matching (LBRM) coding rate greater than a corresponding LBRM coding rate of a non-RedCap UE.
  • LBRM buffer rate-matching
  • aspects of the present disclosure include methods by a reduced capability user equipment (RedCap UE) for identifying a bandwidth capability associated with the RedCap UE for a frequency range, determining a number of physical resource blocks based on the bandwidth capability, determining a circular buffer size based on the number of physical resource blocks, and transmitting or receiving information based on the circular buffer size.
  • RedCap UE reduced capability user equipment
  • determining the number of physical resource blocks comprises identifying the number of physical resource blocks from a quantization table associated with the RedCap UE.
  • the quantization table comprises one or more numbers of physical resource blocks for each of one or more subcarrier spacings associated with the bandwidth capability of the RedCap UE.
  • a first subset of the one or more subcarrier spacings is associated with sub-6 Gigahertz frequency bands and a second subset of the one or more subcarrier spacings is associated with millimeter wave frequency bands.
  • determining the number of physical resource blocks comprises determining a number of limited buffer rate-matching (LBRM) physical resource blocks by quantizing a maximum number of physical resource blocks across configured downlink bandwidth parts for a downlink shared channel of a carrier and uplink bandwidth parts for an uplink shared channel of the carrier, determining a maximum bandwidth supported by the RedCap UE, comparing the number of LBRM physical resource blocks and the number of maximum bandwidth, determining a lower number of the number of LBRM physical resource blocks and the number of maximum bandwidth, and determining the number of physical resource blocks based on the lower number.
  • LBRM limited buffer rate-matching
  • determining the number of physical resource blocks comprises identifying a non-RedCap bandwidth capability associated with a non-RedCap UE for the frequency range, determining a scaling factor based on a ratio of the non-RedCap bandwidth capability of the non-RedCap UE and the bandwidth capability of the RedCap UE, determining a non-RedCap number of physical resource blocks based on the non-RedCap bandwidth capability, and determining the number of physical resource blocks by dividing the non-RedCap number of physical resource blocks by the scaling factor.
  • determining the circular buffer size comprises determining the circular buffer size based on a modulation order associated with the RedCap UE.
  • any of the methods above further comprising encoding or decoding the information with a limited buffer rate-matching (LBRM) coding rate greater than a corresponding LBRM coding rate of a non-RedCap UE.
  • LBRM buffer rate-matching
  • RedCap UE reduced capability user equipment
  • a reduced capability user equipment having a memory comprising instructions, a transceiver, and one or more processors coupled with the memory and the transceiver, the memory including instructions executable by the one or more processors to cause the RedCap UE to identify a bandwidth capability associated with the RedCap UE for a frequency range, determine a number of physical resource blocks based on the bandwidth capability, determine a circular buffer size based on the number of physical resource blocks, and transmit or receive, via the transceiver, information based on the circular buffer size.
  • RedCap UE reduced capability user equipment
  • determining the number of physical resource blocks comprises identifying the number of physical resource blocks from a quantization table associated with the RedCap UE.
  • the quantization table comprises one or more numbers of physical resource blocks for each of one or more subcarrier spacings associated with the bandwidth capability of the RedCap UE.
  • RedCap UE reduced capability user equipment
  • determining the number of physical resource blocks comprises determining a number of limited buffer rate-matching (LBRM) physical resource blocks by quantizing a maximum number of physical resource blocks across configured downlink bandwidth parts for a downlink shared channel of a carrier and uplink bandwidth parts for an uplink shared channel of the carrier, determining a maximum bandwidth supported by the RedCap UE, comparing the number of LBRM physical resource blocks and the number of maximum bandwidth, determining a lower number of the number of LBRM physical resource blocks and the number of maximum bandwidth, and determining the number of physical resource blocks based on the lower number.
  • LBRM limited buffer rate-matching
  • determining the number of physical resource blocks comprises identifying a non-RedCap bandwidth capability associated with a non-RedCap UE for the frequency range, determining a scaling factor based on a ratio of the non-RedCap bandwidth capability of the non-RedCap UE and the bandwidth capability of the RedCap UE, determining a non-RedCap number of physical resource blocks based on the non-RedCap bandwidth capability, and determining the number of physical resource blocks by dividing the non-RedCap number of physical resource blocks by the scaling factor.
  • determining the circular buffer size comprises determining the circular buffer size based on a modulation order associated with the RedCap UE.
  • RedCap UE reduced capability user equipment
  • the instructions are further executable by the one or more processors to cause the RedCap UE to encode or decode the information with a limited buffer rate-matching (LBRM) coding rate greater than a corresponding LBRM coding rate of a non-RedCap UE.
  • LBRM buffer rate-matching
  • An aspect of the present disclosure includes a reduced capability user equipment (RedCap UE) including means for identifying a bandwidth capability associated with the RedCap UE for a frequency range, means for determining a number of physical resource blocks based on the bandwidth capability, means for determining a circular buffer size based on the number of physical resource blocks, and means for transmitting or receiving information based on the circular buffer size.
  • RedCap UE reduced capability user equipment
  • means for determining the number of physical resource blocks comprises means for identifying the number of physical resource blocks from a quantization table associated with the RedCap UE.
  • the quantization table comprises one or more numbers of physical resource blocks for each of one or more subcarrier spacings associated with the bandwidth capability of the RedCap UE.
  • RedCap UE reduced capability user equipment
  • means for determining the number of physical resource blocks comprises means for determining a number of limited buffer rate-matching (LBRM) physical resource blocks by quantizing a maximum number of physical resource blocks across configured downlink bandwidth parts for a downlink shared channel of a carrier and uplink bandwidth parts for an uplink shared channel of the carrier, means for determining a maximum bandwidth supported by the RedCap UE, means for comparing the number of LBRM physical resource blocks and the number of maximum bandwidth, means for determining a lower number of the number of LBRM physical resource blocks and the number of maximum bandwidth, and means for determining the number of physical resource blocks based on the lower number.
  • LBRM limited buffer rate-matching
  • means for determining the number of physical resource blocks comprises means for identifying a non-RedCap bandwidth capability associated with a non-RedCap UE for the frequency range, means for determining a scaling factor based on a ratio of the non-RedCap bandwidth capability of the non-RedCap UE and the bandwidth capability of the RedCap UE, means for determining a non-RedCap number of physical resource blocks based on the non-RedCap bandwidth capability, and means for determining the number of physical resource blocks by dividing the non-RedCap number of physical resource blocks by the scaling factor.
  • means for determining the circular buffer size comprises means for determining the circular buffer size based on a modulation order associated with the RedCap UE.
  • RedCap UE reduced capability user equipment
  • LBRM buffer rate-matching
  • Some aspects of the present disclosure include non-transitory computer readable media having instructions stored therein that, when executed by one or more processors of a reduced capability user equipment (RedCap UE) , cause the RedCapUE to identify a bandwidth capability associated with the RedCap UE for a frequency range, determine a number of physical resource blocks based on the bandwidth capability, determine a circular buffer size based on the number of physical resource blocks, and transmit or receive, via the transceiver, information based on the circular buffer size.
  • RedCap UE reduced capability user equipment
  • determining the number of physical resource blocks comprises identifying the number of physical resource blocks from a quantization table associated with the RedCap UE.
  • the quantization table comprises one or more numbers of physical resource blocks for each of one or more subcarrier spacings associated with the bandwidth capability of the RedCap UE.
  • any of the non-transitory computer readable media above wherein a first subset of the one or more subcarrier spacings is associated with sub-6 Gigahertz frequency bands and a second subset of the one or more subcarrier spacings is associated with millimeter wave frequency bands.
  • determining the number of physical resource blocks comprises determining a number of limited buffer rate-matching (LBRM) physical resource blocks by quantizing a maximum number of physical resource blocks across configured downlink bandwidth parts for a downlink shared channel of a carrier and uplink bandwidth parts for an uplink shared channel of the carrier, determining a maximum bandwidth supported by the RedCap UE, compare the number of LBRM physical resource blocks and the number of maximum bandwidth, determining a lower number of the number of LBRM physical resource blocks and the number of maximum bandwidth, and determining the number of physical resource blocks based on the lower number.
  • LBRM limited buffer rate-matching
  • determining the number of physical resource blocks comprises identifying a non-RedCap bandwidth capability associated with a non-RedCap UE for the frequency range, determining a scaling factor based on a ratio of the non-RedCap bandwidth capability of the non-RedCap UE and the bandwidth capability of the RedCap UE, determining a non-RedCap number of physical resource blocks based on the non-RedCap bandwidth capability, and determining the number of physical resource blocks by dividing the non-RedCap number of physical resource blocks by the scaling factor.
  • determining the circular buffer size comprises determining the circular buffer size based on a modulation order associated with the RedCap UE.
  • any of the non-transitory computer readable media above further comprising instructions, when executed by the one or more processors, cause the RedCap UE to encode or decode the information with a limited buffer rate-matching (LBRM) coding rate greater than a corresponding LBRM coding rate of a non-RedCap UE.
  • LBRM buffer rate-matching
  • a CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA) , etc.
  • CDMA2000 covers IS-2000, IS-95, and IS-856 standards.
  • IS-2000 Releases 0 and A are commonly referred to as CDMA2000 1X, 1X, etc.
  • IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD) , etc.
  • UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
  • a TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM) .
  • GSM Global System for Mobile Communications
  • An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB) , Evolved UTRA (E-UTRA) , IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM TM , etc.
  • UMB Ultra Mobile Broadband
  • E-UTRA Evolved UTRA
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM TM
  • UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS) .
  • 3GPP LTE and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA.
  • UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP) .
  • CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) .
  • the techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies, including cellular (e.g., LTE) communications over a shared radio frequency spectrum band.
  • LTE Long Term Evolution
  • 5G for purposes of example
  • LTE terminology is used in much of the description below, although the techniques may be applicable other next generation communication systems.
  • Information and signals may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, computer-executable code or instructions stored on a computer-readable medium, or any combination thereof.
  • a specially-programmed device such as but not limited to a processor, a digital signal processor (DSP) , an ASIC, a FPGA or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof designed to perform the functions described herein.
  • DSP digital signal processor
  • a specially-programmed processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a specially-programmed processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the functions described herein may be implemented in hardware, software executed by a processor, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a non-transitory computer-readable medium. Other examples and implementations are within the scope and spirit of the disclosure and appended claims. For example, due to the nature of software, functions described above may be implemented using software executed by a specially programmed processor, hardware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage medium may be any available medium that may be accessed by a general purpose or special purpose computer.
  • computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • any connection is properly termed a computer-readable medium.
  • Disk and disc include compact disc (CD) , laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

Landscapes

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

Abstract

La présente invention concerne, selon certains aspects, des procédés, appareils, et supports lisibles par ordinateur destinés à identifier une capacité de bande passante associée à un UE RedCap pour une plage de fréquences, à déterminer un nombre de blocs de ressources physiques d'après la capacité de bande passante, à déterminer une taille de tampon circulaire d'après le nombre de blocs de ressources physiques, et à émettre ou à recevoir des informations d'après la taille de tampon circulaire.
PCT/CN2020/119790 2020-10-02 2020-10-02 Procédés et appareil de détermination de paramètres pour un équipement d'utilisateur à capacité réduite WO2022067856A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/119790 WO2022067856A1 (fr) 2020-10-02 2020-10-02 Procédés et appareil de détermination de paramètres pour un équipement d'utilisateur à capacité réduite

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/119790 WO2022067856A1 (fr) 2020-10-02 2020-10-02 Procédés et appareil de détermination de paramètres pour un équipement d'utilisateur à capacité réduite

Publications (1)

Publication Number Publication Date
WO2022067856A1 true WO2022067856A1 (fr) 2022-04-07

Family

ID=80949497

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/119790 WO2022067856A1 (fr) 2020-10-02 2020-10-02 Procédés et appareil de détermination de paramètres pour un équipement d'utilisateur à capacité réduite

Country Status (1)

Country Link
WO (1) WO2022067856A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024007273A1 (fr) * 2022-07-07 2024-01-11 北京小米移动软件有限公司 Procédé et appareil de détermination de débit de données de crête

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111567126A (zh) * 2020-04-08 2020-08-21 北京小米移动软件有限公司 配置信息传输方法及装置、通信设备及存储介质
CN111713136A (zh) * 2020-05-07 2020-09-25 北京小米移动软件有限公司 信息传输方法、装置及通信设备

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111567126A (zh) * 2020-04-08 2020-08-21 北京小米移动软件有限公司 配置信息传输方法及装置、通信设备及存储介质
CN111713136A (zh) * 2020-05-07 2020-09-25 北京小米移动软件有限公司 信息传输方法、装置及通信设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "UE Complexity Reduction for NR RedCap Devices", 3GPP DRAFT; R1-2006811, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200817 - 20200828, 8 August 2020 (2020-08-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051918261 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024007273A1 (fr) * 2022-07-07 2024-01-11 北京小米移动软件有限公司 Procédé et appareil de détermination de débit de données de crête

Similar Documents

Publication Publication Date Title
US11848897B2 (en) Methods and apparatus for subband full-duplex
US11115970B2 (en) Techniques for configuring transmission configuration states in wireless communications
US11050877B2 (en) Methods and apparatus for beam failure detection
US10849050B2 (en) Methods and apparatuses for rate matching
US11291006B2 (en) Techniques for configuring active spatial relations in wireless communications
US11930488B2 (en) Techniques for signaling uplink transmission configuration indicator states
US20200275475A1 (en) Configured grant operation for new radio unlicensed spectrum carrier aggregation
US20220007350A1 (en) Techniques for configuring search spaces for sidelink communication
US11696234B2 (en) Techniques for dynamic configuration of channel state information processing units
WO2022067856A1 (fr) Procédés et appareil de détermination de paramètres pour un équipement d'utilisateur à capacité réduite
US11765705B2 (en) Methods and apparatus for configuring RB sets
US11943166B2 (en) Techniques for hybrid automatic repeat request acknowledge resource indication for downlink semi-persistent scheduling
US20230045134A1 (en) Methods and apparatus for reference signal associations
EP3909173A1 (fr) Procédés et appareil de combinaison logicielle dynamique destinés aux transmissions à faisceaux multiples
US11729807B2 (en) Techniques for triggering CSI report based on downlink grant signaling
US11799594B2 (en) Methods and apparatus for transmitting a reset negative acknowledgement
WO2021203369A1 (fr) Procédés et appareil pour déterminer la taille de bloc de transport de canal partagé de liaison montante physique (pusch) avec des informations de commande de liaison montante (uci)
WO2023142017A1 (fr) Procédés et appareil de partage de temps d'occupation de multiples canaux de liaison latérale
US20220232597A1 (en) Techniques for cross-carrier scheduling with multi-transmission and reception points and dynamic spectrum sharing
US20230189166A1 (en) Methods and apparatus for determining maximum power reduction for uplink transmission

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: 20955876

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20955876

Country of ref document: EP

Kind code of ref document: A1