WO2022153179A1 - Configuration de parties de bande passante dormante - Google Patents

Configuration de parties de bande passante dormante Download PDF

Info

Publication number
WO2022153179A1
WO2022153179A1 PCT/IB2022/050195 IB2022050195W WO2022153179A1 WO 2022153179 A1 WO2022153179 A1 WO 2022153179A1 IB 2022050195 W IB2022050195 W IB 2022050195W WO 2022153179 A1 WO2022153179 A1 WO 2022153179A1
Authority
WO
WIPO (PCT)
Prior art keywords
serving cell
dormant
bwp
transmissions
dormant bwp
Prior art date
Application number
PCT/IB2022/050195
Other languages
English (en)
Inventor
Hossein Bagheri
Hyejung Jung
Vijay Nangia
Alexander Johann Maria Golitschek Edler Von Elbwart
Original Assignee
Lenovo (Singapore) Pte. Ltd.
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 Lenovo (Singapore) Pte. Ltd. filed Critical Lenovo (Singapore) Pte. Ltd.
Publication of WO2022153179A1 publication Critical patent/WO2022153179A1/fr

Links

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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the subject matter disclosed herein relates generally to wireless communications and more particularly relates to configuring dormant bandwidth parts.
  • bandwidth parts may be used.
  • bandwidth parts may be dormant.
  • One embodiment of a method includes receiving, at a user equipment, a first dormant bandwidth part (BWP) configuration and a second dormant BWP configuration for a first serving cell.
  • the serving cell becomes dormant by setting an associated active BWP of the serving cell to a dormant BWP according to a corresponding dormant BWP configuration, and the UE does not monitor a physical downlink control channel (PDCCH) on the dormant BWP.
  • BWP dormant bandwidth part
  • PDCCH physical downlink control channel
  • the method includes determining whether the first serving cell is able to schedule uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof on at least one other serving cell, wherein: in response to determining that the first serving cell is able to schedule the UL transmissions, the DL transmissions, or the combination thereof on the at least one other serving cell, setting the dormant BWP for the first serving cell based on the first dormant BWP configuration; and, in response to determining that the first serving cell is not able to schedule the UL transmissions, the DL transmissions, or the combination thereof on the at least one other serving cell, setting the dormant BWP for the first serving cell based on the second dormant BWP configuration.
  • One apparatus for configuring dormant bandwidth parts includes a user equipment.
  • the apparatus includes a receiver that receives a first dormant bandwidth part (BWP) configuration and a second dormant BWP configuration for a first serving cell.
  • BWP dormant bandwidth part
  • a serving cell becomes dormant by setting an associated active BWP of the serving cell to a dormant BWP according to a corresponding dormant BWP configuration, and the UE does not monitor a physical downlink control channel (PDCCH) on the dormant BWP.
  • PDCCH physical downlink control channel
  • the apparatus includes a processor that determines whether the first serving cell is able to schedule uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof on at least one other serving cell, wherein: in response to determining that the first serving cell is able to schedule the UL transmissions, the DL transmissions, or the combination thereof on the at least one other serving cell, setting the dormant BWP for the first serving cell based on the first dormant BWP configuration; and in response to determining that the first serving cell is not able to schedule the UL transmissions, the DL transmissions, or the combination thereof on the at least one other serving cell, setting the dormant BWP for the first serving cell based on the second dormant BWP configuration.
  • UL uplink
  • DL downlink
  • Another embodiment of a method for configuring dormant bandwidth parts includes transmitting, from a network device, a first dormant bandwidth part (BWP) configuration and a second dormant BWP configuration for a first serving cell.
  • a serving cell becomes dormant by setting an associated active BWP of the serving cell to a dormant BWP according to a corresponding dormant BWP configuration, not transmitting a physical downlink control channel (PDCCH) on the dormant BWP.
  • PDCCH physical downlink control channel
  • the method includes setting the dormant BWP for the first serving cell based on the first dormant BWP configuration if the first serving cell is configured for cross carrier scheduling of at least one other serving cell for uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof. In certain embodiments, the method includes setting the dormant BWP for the first serving cell based on the second dormant BWP configuration if the first serving cell is not configured for cross carrier scheduling of at least one other serving cell for uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof.
  • Another apparatus for configuring dormant bandwidth parts includes a network device.
  • the apparatus includes a transmitter that transmits a first dormant bandwidth part (BWP) configuration and a second dormant BWP configuration for a first serving cell.
  • BWP dormant bandwidth part
  • a serving cell becomes dormant by setting an associated active BWP of the serving cell to a dormant BWP according to a corresponding dormant BWP configuration, not transmitting a physical downlink control channel (PDCCH) on the dormant BWP.
  • PDCCH physical downlink control channel
  • the apparatus includes a processor that: sets the dormant BWP for the first serving cell based on the first dormant BWP configuration if the first serving cell is configured for cross carrier scheduling of at least one other serving cell for uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof; and sets the dormant BWP for the first serving cell based on the second dormant BWP configuration if the first serving cell is not configured for cross carrier scheduling of at least one other serving cell for uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof.
  • Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for configuring dormant bandwidth parts
  • Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for configuring dormant bandwidth parts
  • Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for configuring dormant bandwidth parts
  • Figure 4 is a timing diagram illustrating one embodiment in which an sSCell becomes dormant after ‘T’ symbols, slots, milliseconds, and/or time units;
  • Figure 5 is a flow chart diagram illustrating one embodiment of a method for configuring dormant bandwidth parts.
  • Figure 6 is a flow chart diagram illustrating another embodiment of a method for configuring dormant bandwidth parts.
  • embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.
  • modules may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • VLSI very-large-scale integration
  • a module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
  • Modules may also be implemented in code and/or software for execution by various types of processors.
  • An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.
  • a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
  • operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices.
  • the software portions are stored on one or more computer readable storage devices.
  • the computer readable medium may be a computer readable storage medium.
  • the computer readable storage medium may be a storage device storing the code.
  • the storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • a storage device More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc readonly memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages.
  • the code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”) or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider an Internet Service Provider
  • the code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
  • the code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).
  • Figure 1 depicts an embodiment of a wireless communication system 100 for configuring dormant bandwidth parts.
  • the wireless communication system 100 includes remote units 102 and network units 104. Even though a specific number of remote units 102 and network units 104 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.
  • the remote units 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), aerial vehicles, drones, or the like.
  • the remote units 102 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like.
  • the remote units 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device, or by other terminology used in the art.
  • the remote units 102 may communicate directly with one or more of the network units 104 via UL communication signals. In certain embodiments, the remote units 102 may communicate directly with other remote units 102 via sidelink communication.
  • the network units 104 may be distributed over a geographic region.
  • a network unit 104 may also be referred to and/or may include one or more of an access point, an access terminal, a base, a base station, a location server, a core network (“CN”), a radio network entity, a Node-B, an evolved node-B (“eNB”), a 5G node-B (“gNB”), a Home Node-B, a relay node, a device, a core network, an aerial server, a radio access node, an access point (“AP”), new radio (“NR”), a network entity, an access and mobility management function (“AMF”), a unified data management (“UDM”), a unified data repository (“UDR”), a UDM/UDR, a policy control function (“PCF”), a radio access network (“RAN”), a network slice selection function (“NSSF”), an operations, administration, and management (“0AM”), a session management function (“SMF”)
  • RAN radio access
  • the network units 104 are generally part of a radio access network that includes one or more controllers communicably coupled to one or more corresponding network units 104.
  • the radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.
  • the wireless communication system 100 is compliant with NR protocols standardized in third generation partnership project (“3GPP”), wherein the network unit 104 transmits using an OFDM modulation scheme on the downlink (“DL”) and the remote units 102 transmit on the uplink (“UL”) using a single-carrier frequency division multiple access (“SC-FDMA”) scheme or an orthogonal frequency division multiplexing (“OFDM”) scheme.
  • 3GPP third generation partnership project
  • SC-FDMA single-carrier frequency division multiple access
  • OFDM orthogonal frequency division multiplexing
  • the wireless communication system 100 may implement some other open or proprietary communication protocol, for example, WiMAX, institute of electrical and electronics engineers (“IEEE”) 802.11 variants, global system for mobile communications (“GSM”), general packet radio service (“GPRS”), universal mobile telecommunications system (“UMTS”), long term evolution (“LTE”) variants, code division multiple access 2000 (“CDMA2000”), Bluetooth®, ZigBee, Sigfoxx, among other protocols.
  • WiMAX institute of electrical and electronics engineers
  • IEEE institute of electrical and electronics engineers
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • UMTS universal mobile telecommunications system
  • LTE long term evolution
  • CDMA2000 code division multiple access 2000
  • Bluetooth® ZigBee
  • ZigBee ZigBee
  • Sigfoxx among other protocols.
  • the network units 104 may serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link.
  • the network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and/or spatial domain.
  • a remote unit 102 may receive a first dormant bandwidth part (BWP) configuration and a second dormant BWP configuration for a first serving cell.
  • the serving cell becomes dormant by setting an associated active BWP of the serving cell to a dormant BWP according to a corresponding dormant BWP configuration, and the UE does not monitor a physical downlink control channel (PDCCH) on the dormant BWP.
  • PDCCH physical downlink control channel
  • the remote unit 102 may determine whether the first serving cell is able to schedule uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof on at least one other serving cell, wherein: in response to determining that the first serving cell is able to schedule the UL transmissions, the DL transmissions, or the combination thereof on the at least one other serving cell, setting the dormant BWP for the first serving cell based on the first dormant BWP configuration; and, in response to determining that the first serving cell is not able to schedule the UL transmissions, the DL transmissions, or the combination thereof on the at least one other serving cell, setting the dormant BWP for the first serving cell based on the second dormant BWP configuration. Accordingly, the remote unit 102 may be used for configuring dormant bandwidth parts.
  • a network unit 104 may transmit a first dormant bandwidth part (BWP) configuration and a second dormant BWP configuration for a first serving cell.
  • a serving cell becomes dormant by setting an associated active BWP of the serving cell to a dormant BWP according to a corresponding dormant BWP configuration, not transmitting a physical downlink control channel (PDCCH) on the dormant BWP.
  • PDCCH physical downlink control channel
  • the network unit 104 may set the dormant BWP for the first serving cell based on the first dormant BWP configuration if the first serving cell is configured for cross carrier scheduling of at least one other serving cell for uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof. In certain embodiments, the network unit 104 may set the dormant BWP for the first serving cell based on the second dormant BWP configuration if the first serving cell is not configured for cross carrier scheduling of at least one other serving cell for uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof. Accordingly, the network unit 104 may be used for configuring dormant bandwidth parts.
  • Figure 2 depicts one embodiment of an apparatus 200 that may be used for configuring dormant bandwidth parts.
  • the apparatus 200 includes one embodiment of the remote unit 102.
  • the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212.
  • the input device 206 and the display 208 are combined into a single device, such as a touchscreen.
  • the remote unit 102 may not include any input device 206 and/or display 208.
  • the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and/or the display 208.
  • the processor 202 may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations.
  • the processor 202 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller.
  • the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein.
  • the processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.
  • the memory 204 in one embodiment, is a computer readable storage medium.
  • the memory 204 includes volatile computer storage media.
  • the memory 204 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”).
  • the memory 204 includes non-volatile computer storage media.
  • the memory 204 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device.
  • the memory 204 includes both volatile and non-volatile computer storage media.
  • the memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit 102.
  • the input device 206 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like.
  • the input device 206 may be integrated with the display 208, for example, as a touchscreen or similar touch-sensitive display.
  • the input device 206 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen.
  • the input device 206 includes two or more different devices, such as a keyboard and a touch panel.
  • the display 208 may include any known electronically controllable display or display device.
  • the display 208 may be designed to output visual, audible, and/or haptic signals.
  • the display 208 includes an electronic display capable of outputting visual data to a user.
  • the display 208 may include, but is not limited to, a liquid crystal display (“LCD”), a light emitting diode (“LED”) display, an organic light emitting diode (“OLED”) display, a projector, or similar display device capable of outputting images, text, or the like to a user.
  • the display 208 may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like.
  • the display 208 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
  • the display 208 includes one or more speakers for producing sound.
  • the display 208 may produce an audible alert or notification (e.g., a beep or chime).
  • the display 208 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback.
  • all or portions of the display 208 may be integrated with the input device 206.
  • the input device 206 and display 208 may form a touchscreen or similar touch-sensitive display.
  • the display 208 may be located near the input device 206.
  • the receiver 212 receives a first dormant bandwidth part (BWP) configuration and a second dormant BWP configuration for a first serving cell.
  • a serving cell becomes dormant by setting an associated active BWP of the serving cell to a dormant BWP according to a corresponding dormant BWP configuration, and the UE does not monitor a physical downlink control channel (PDCCH) on the dormant BWP.
  • PDCCH physical downlink control channel
  • the processor 202 determines whether the first serving cell is able to schedule uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof on at least one other serving cell, wherein: in response to determining that the first serving cell is able to schedule the UL transmissions, the DL transmissions, or the combination thereof on the at least one other serving cell, setting the dormant BWP for the first serving cell based on the first dormant BWP configuration; and in response to determining that the first serving cell is not able to schedule the UL transmissions, the DL transmissions, or the combination thereof on the at least one other serving cell, setting the dormant BWP for the first serving cell based on the second dormant BWP configuration.
  • the remote unit 102 may have any suitable number of transmitters 210 and receivers 212.
  • the transmitter 210 and the receiver 212 may be any suitable type of transmitters and receivers.
  • the transmitter 210 and the receiver 212 may be part of a transceiver.
  • FIG. 3 depicts one embodiment of an apparatus 300 that may be used for configuring dormant bandwidth parts.
  • the apparatus 300 includes one embodiment of the network unit 104.
  • the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312.
  • the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.
  • the transmitter 310 transmits a first dormant bandwidth part (BWP) configuration and a second dormant BWP configuration for a first serving cell.
  • a serving cell becomes dormant by setting an associated active BWP of the serving cell to a dormant BWP according to a corresponding dormant BWP configuration, not transmitting a physical downlink control channel (PDCCH) on the dormant BWP.
  • PDCCH physical downlink control channel
  • the processor 302 sets the dormant BWP for the first serving cell based on the first dormant BWP configuration if the first serving cell is configured for cross carrier scheduling of at least one other serving cell for uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof; and sets the dormant BWP for the first serving cell based on the second dormant BWP configuration if the first serving cell is not configured for cross carrier scheduling of at least one other serving cell for uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof.
  • anew radio (“NR”) carrier may overlap with an LTE carrier.
  • dynamic spectrum sharing techniques may be used.
  • a secondary NR carrier may schedule the PCell and/or PSCell.
  • CCS cross carrier scheduling
  • each cell may be only scheduled by one cell.
  • DSS dynamic spectrum sharing
  • sSCell SCell
  • Mechanisms and/or rules to determine whether and when an sSCell may become dormant and/or non-dormant are described herein.
  • cross carrier scheduling for which a first cell (e.g., referred to as scheduling cell) schedules a second cell (e.g., referred to as scheduled cell) may be configured (e.g., via ServingCellConfig) for a serving cell.
  • ServingCellConfig Parameters of cross-carrier configuration (e.g., referred to as CrossCarrierSchedulingConfig) may be provided.
  • a user equipment does not monitor a PDCCH on a dormant bandwidth part (“BWP”) of an SCell, also the UE does not monitor a PDCCH for the dormant BWP.
  • BWP dormant bandwidth part
  • BD PDCCH blind decoding
  • SCS subcarrier spacing
  • X,Y non-overlapping control channel elements
  • CCEs non-overlapping control channel elements
  • soft distribution may mean there is no fixed split of BD and/or number of CCEs defined in a specification among a set of cells (e.g., other than a maximum number per each cell).
  • a maximum number per each cell may be different.
  • PDCCH monitoring there may be PDCCH monitoring.
  • URLLC ultrareliable low-latency communication
  • more PDCCH monitoring opportunities e.g., in terms of number of non-overlapping CCEs or number of BDs in a slot
  • URLLC configurations may be needed to ensure a latency for some of URLLC configurations.
  • limits on a number of PDCCH candidates, blind decodes, and/or number of non-overlapping CCEs may be defined per span (or set of symbols) and/or slot, wherein a ‘span’ or ‘PDCCH monitoring span’ is defined based on PDCCH monitoring occasions within a slot (e.g., and also across slots), considering a gap between (e.g., the beginning of) any two spans.
  • a set of spans in a downlink (“DL”) BWP of a carrier is defined via a pair of numbers (X, Y) (also referred to as ‘(X,Y) combination’), wherein ‘X’ defines a minimum gap between the start of any two spans of the set of spans, and ‘Y’ defines the maximum duration of a span.
  • the UE is not expected and/or does not monitor more PDCCH candidates or more non-overlapping CCEs in each scheduling cell and/or scheduled cell more than what is derived based on the limits on number of PDCCH candidates and/or number of non-overlapping CCEs, respectively.
  • sSCell scheduling the PCell may be referred to as an sSCell.
  • Some of the embodiments herein may be applicable to a cross-carrier scheduling operation in general instead of just a DSS operation (e.g., sSCell scheduling PCell).
  • mechanisms may be applicable to a PSCell for dual connectivity (e.g., special cell (“SpCell”), ‘primary cell’ may be used instead of PCell and a ‘secondary cell’ can be used instead of SCell).
  • SpCell special cell
  • a term special cell refers to a PCell of a master cell group (“MCG”) or the PSCell of a secondary cell group (“SCG”) depending on if a medium access control (“MAC”) entity is associated with the MCG or the SCG, respectively; otherwise, the term special cell refers to the PCell.
  • MCG master cell group
  • SCG secondary cell group
  • a special cell may support physical uplink control channel (“PUCCH”) transmission and contention-based random access and may always be activated.
  • PUCCH physical uplink control channel
  • a fact that distinguishes DSS from CCS is that a cell (e.g., PCell) can be scheduled via more than one cell. Some of the embodiments herein take this fact into account.
  • a UE configured with discontinuous reception (“DRX”) mode operation may be provided with the following for detection of a DCI format 2 6 in a PDCCH reception on a PCell or on a SpCell.
  • DRX discontinuous reception
  • a UE is provided with search space sets to monitor PDCCH for detection of DCI format 0 1 and DCI format 1 1 and one or both of DCI format 0 1 and DCI format 1 1 include a SCell dormancy indication field, where: 1) the SCell dormancy indication field is a bitmap with size equal to a number of groups of configured SCells, provided by dormancyGroupWithinActiveTime; 2) each bit of the bitmap corresponds to a group of configured SCells from the number of groups of configured Scells; 3) if the UE detects a DCI format 0 1 or a DCI format 1 1 that does not include a carrier indicator field, or detects a DCI format 0 1 or DCI format 1 1 that includes a carrier indicator field with value equal to 0: a) a 'O' value for a bit of the bitmap indicates an active DL BWP provided by dormantBWP-Id for the UE for each
  • an sSCell does not become dormant.
  • an sSCell is not allowed and/or expected to become dormant (e.g., dormancy indication is not applicable to the sSCell).
  • an sSCell belongs to a group of configured SCells from a number of (or set of) groups of configured SCells. In such embodiments, the UE ignores changing the active DL BWP of the sSCell as indicated by DCI format 2 6 or ignores the dormancy indication for the sScell.
  • the UE upon reception and/or detection of a DCI format (e.g., DCI format 2 6, DCI format 0 1, or DCI format 1 1) in a PDCCH reception (e.g., on PCell and/or sSCell), does not set (or update, modify, and/or change) the active DL BWP of the sSCell to an active DL BWP provided by dormantBWP-Id if the bit of the bitmap associated with the sSCell is ‘O’.
  • the UE does not set a DL BWP of an sSCell as active DL BWP if the bit of the bitmap provided by dormantBWP-Id associated with the sSCell is ‘O’.
  • a higher layer indication (e.g., radio resource control (“RRC”) or MAC control element (“CE”) (“MAC-CE”)) indicates if an sSCell is allowed to become dormant if indicated (e.g., via DCI format 2 6, DCI format 0 1, or DCI format 1 1) to become dormant (e.g., which is indicated by a bit of a bitmap associated with the sSCell (or Scell group comprising the sSCell) being ‘0’).
  • RRC radio resource control
  • CE MAC control element
  • a rule determines if an sSCell is allowed to become dormant if indicated (e.g., via DCI format 2_6) to become dormant (e.g., which is indicated by a bit of a bitmap associated with the sSCell (or Scell group comprising the sSCell) being ‘0’).
  • a DCI format corresponding to URLLC operation e.g., DCI format x-2 or a DCI format with priority indicator field
  • the sSCell is not allowed to become dormant (e.g., a dormancy indication is not applicable to the sSCell).
  • a UE is configured to monitor a DCI format corresponding to URLLC operation (e.g., DCI format x-2 or a DCI format with priority indicator field) for PCell (or sSCell) scheduling on sSCell, the sSCell is not allowed to become dormant (e.g., dormancy indication is not applicable to the sSCell).
  • a DCI format corresponding to URLLC operation e.g., DCI format x-2 or a DCI format with priority indicator field
  • the sSCell is not allowed to become dormant (e.g., dormancy indication is not applicable to the sSCell).
  • a UE capability signaling and/or UE reports if an sSCell is allowed to become dormant (or dormancy for the sSCell is supported) if indicated (e.g., via DCI format 2 6, DCI format 0 1, or DCI format 1 1 which is indicated by a bit of a bitmap associated with the sSCell (or Scell group comprising the sSCell) being ‘0’).
  • a DCI format (e.g., DCI format 2 6, DCI format 0 1, or DCI format 1 1) indicates if a dormancy indication (e.g., when the bit of the bitmap associated with the sSCell (or Scell group comprising the sSCell) is ‘0’) is applicable to the sSCell.
  • a field in a DCI format indicates if the dormancy indication is applicable to the sSCell.
  • a first higher layer signaling e.g., RRC, MAC-CE, UE capability signaling and/or reporting
  • a first physical layer signaling such as a DCI indication
  • a first rule e.g., rules in the third embodiment
  • a second higher layer signaling e.g., RRC, MAC-CE, UE capability signaling and/or reporting
  • a second rule e.g., rules in the third embodiment
  • a higher layer signaling e.g., RRC, MAC-CE, UE capability signaling and/or reporting
  • a physical layer signaling such as a DCI indication
  • a rule e.g., rules in the third embodiment indicates and/or determines if the sSCell can only be a PUCCH SCell or a non-PUCCH SCell.
  • a UE for an SCell is configured with two different DormantBWP configurations (e.g., DormantBWP-Config): one for the case that the SCell is an sSCell and one for the case that the SCell is not an sSCell.
  • DormantBWP-Config two different DormantBWP configurations
  • a UE is configured with one DormantBWP configuration, but with two parameter values for one parameter of the DormantBWP configuration: one for the case that the SCell is an sSCell and one for the case that the SCell is not an sSCell.
  • sSCell is not allowed to be part of any SCell group.
  • an sSCell is not allowed and/or not expected to belong to any groups of configured SCells by dormancyGroupOutsideActiveTime and/or dormancyGroupWithinActiveTime.
  • a UE is not expected to receive a higher layer parameter dormancyGroupOutsideActiveTime and/or dormancyGroupWithinActiveTime for the sSCell.
  • a higher layer parameter dormancyGroupOutsideActiveTime and/or dormancyGroupWithinActiveTime is not applicable and/or valid for an sSCell.
  • sSCell may go to dormancy but after some application delay.
  • the sSCell may become dormant as indicated a DCI format (e.g., by DCI format 2 6, DCI format 0 1, or DCI format 1 1), but the dormancy may apply after a certain time.
  • a DCI format e.g., by DCI format 2 6, DCI format 0 1, or DCI format 1 1
  • FIG. 4 is a timing diagram 400 illustrating one embodiment in which an sSCell becomes dormant after ‘T’ symbols, slots, milliseconds, and/or time units.
  • the timing diagram 400 is illustrated over a time 402.
  • an active DL BWP of sSCell is indicated to set to a dormant DL BWP.
  • an active DL BWP of sSCell is set for the dormant DL BWP.
  • the time between the first time 404 and the second time 406 is time duration 408 ‘T’.
  • time duration ‘T’ is applied from the last symbol corresponding to the indication (e.g., last symbol of PDCCH carrying such indication or last symbol of the control resource set (“CORESET”) in which the indication is sent).
  • the UE upon reception and/or detection of an indication for the sSCell (or Scell group comprising the sSCell) to become dormant, sets the active DL BWP of the sSCell to an active DL BWP provided by dormantBWP-Id if the bit of the bitmap associated with the sSCell (or Scell group comprising the sSCell) is ‘0’ a certain time after the reception and/or detection of the indication.
  • sufficient time may be allowed for another SCell to become an sSCell.
  • a second SCell automatically becomes the sSCell. This may be applicable if there is no delay in applying the dormancy (e.g., certain time is zero).
  • the second SCell may be configured by higher layer signaling to become sSCell if the current sSCell becomes dormant
  • first and second SCells there could be a mapping between first and second SCells. For instance, there may be an RRC field for the sSCell indicating a second SCell identifier (“ID”) to replace the sSCell if the sSCell becomes dormant.
  • ID SCell identifier
  • the certain time is determined based on: 1) a time that a UE is reporting (e.g., by UE capability signaling at what time the UE is capable); and/or 2) UE's PDSCH, PDCCH, and/or physical uplink shared channel (“PUSCH”) processing capability.
  • a dormancy indication applies to all SCells within the same SCell group as the sSCell at the same time (e.g., after the certain time).
  • the certain time is affected by a subcarrier spacing (“SCS”) of the active DL BWP of an SCell to become dormant and/or by the subcarrier spacing of the active DL BWP of an SCell to become an sSCell and/or by the subcarrier spacing of the active DL BWP of PCell (e.g., if PCell becomes self-scheduled with sSCell becoming dormant) and/or by the subcarrier spacing of the active DL BWP of the serving cell on which the dormancy indication by DCI is received.
  • SCS subcarrier spacing
  • a certain time is determined with respect to a smallest SCS from a set of SCS of an active DL BWP within the SCells indicated to become dormant.
  • the certain time is determined with respect to a smallest SCS from a set of SCS of an active DL BWP within the SCells indicated to become dormant (or in another example, the activated and/or dormant SCells or alternatively the configured SCells) and the set of SCS of the active DL BWP within the SCells becoming sSCell.
  • the certain time is applied to transition from the PCell being schedulable by the sSCell to PCell becoming self-schedulable only.
  • a first certain time is applied to transition from the PCell being schedulable by the sSCell to PCell becoming self-schedulable only, and a second certain time is applied to transition from the PCell being schedulable by the first sSCell to PCell becoming schedulable by the second sSCell.
  • an sSCell may go to dormancy but not very frequently.
  • the sSCell cannot go to dormancy more than ‘m’ times in a time window ‘w’ having a number of symbols, slots, and/or time units.
  • ‘m’ and ‘w’ are determined based on higher layer signaling, UE- capability signaling, and/or reporting.
  • ‘m’ and/or ‘w’ are specified in the specifications.
  • a UE is not expected to receive an indication setting the active DL BWP of the sSCell to the dormant DL BWP of the sSCell more than ‘m’ times in a time window of ‘w’ symbols, slots, and/or time units.
  • PDCCH may be monitored in a subset of spans in a dormant DL BWP of an sSCell (e.g., for PCell scheduling).
  • Figure 5 is a flow chart diagram illustrating one embodiment of a method 500 for configuring dormant bandwidth parts.
  • the method 500 is performed by an apparatus, such as the remote unit 102.
  • the method 500 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the method 500 includes receiving 502 a first dormant bandwidth part (BWP) configuration and a second dormant BWP configuration for a first serving cell.
  • the serving cell becomes dormant by setting an associated active BWP of the serving cell to a dormant BWP according to a corresponding dormant BWP configuration, and the UE does not monitor a physical downlink control channel (PDCCH) on the dormant BWP.
  • PDCH physical downlink control channel
  • the method 500 includes determining 504 whether the first serving cell is able to schedule uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof on at least one other serving cell, wherein: in response to determining that the first serving cell is able to schedule the UL transmissions, the DL transmissions, or the combination thereof on the at least one other serving cell, setting the dormant BWP for the first serving cell based on the first dormant BWP configuration; and, in response to determining that the first serving cell is not able to schedule the UL transmissions, the DL transmissions, or the combination thereof on the at least one other serving cell, setting the dormant BWP for the first serving cell based on the second dormant BWP configuration.
  • the method 500 further comprises setting an active BWP of the first serving cell to the dormant BWP if the first serving cell is not enabled to schedule a primary cell. In some embodiments, the method 500 further comprises receiving a first indication indicating a group of serving cells to become dormant, wherein the group of serving cells includes the first serving cell.
  • the method 500 further comprises receiving a second indication indicating whether the first serving cell is allowed to transition to the dormant BWP, and, in response to determining that the first serving cell is able to schedule the UL transmissions, the DL transmissions, or the combination thereof on the at least one other serving cell, setting an active BWP of the first serving cell to the dormant BWP based on the first dormant BWP configuration.
  • the second indication indicates: whether the first serving cell is allowed to transition to the dormant BWP outside a discontinuous reception (DRX) active time; and whether the first serving cell is allowed to transition to the dormant BWP within the DRX active time.
  • DRX discontinuous reception
  • the first serving cell is not enabled to become dormant more than a number of times in a period of time.
  • the UE not monitoring the PDCCH on the dormant BWP comprises not monitoring the PDCCH on a first set of spans of a plurality of spans and monitoring the PDCCH on a second set of spans of the plurality of spans.
  • the method 500 further comprises setting an active BWP of the first serving cell to the dormant BWP after a certain time from reception of an indication indicating a group of serving cells to become dormant, wherein the group of serving cells includes the first serving cell.
  • the certain time is determined based on a subcarrier spacing (SCS) of a BWP of the first serving cell, and a SCS of a BWP of the at least one other serving cell.
  • the method further comprises determining a second serving cell for monitoring the PDCCH corresponding to the at least one other serving cell.
  • the second serving cell is determined based on the first serving cell and a higher layer mapping between the first serving cell and the second serving cell.
  • FIG. 6 is a flow chart diagram illustrating another embodiment of a method 600 for configuring dormant bandwidth parts.
  • the method 600 is performed by an apparatus, such as the network unit 104.
  • the method 600 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the method 600 includes transmitting 602 a first dormant bandwidth part (BWP) configuration and a second dormant BWP configuration for a first serving cell.
  • BWP dormant bandwidth part
  • a serving cell becomes dormant by setting an associated active BWP of the serving cell to a dormant BWP according to a corresponding dormant BWP configuration, not transmitting a physical downlink control channel (PDCCH) on the dormant BWP.
  • the method 600 includes setting 604 the dormant BWP for the first serving cell based on the first dormant BWP configuration if the first serving cell is configured for cross carrier scheduling of at least one other serving cell for uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof.
  • UL uplink
  • DL downlink
  • the method 600 includes setting 606 the dormant BWP for the first serving cell based on the second dormant BWP configuration if the first serving cell is not configured for cross carrier scheduling of at least one other serving cell for uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof.
  • UL uplink
  • DL downlink
  • the method 600 further comprises transmitting a first indication indicating a group of serving cells to become dormant, wherein the group of serving cells includes the first serving cell. In some embodiments, the method 600 further comprises transmitting a second indication indicating whether the first serving cell is allowed to transition to the dormant BWP, and the second indication is indicated via the first indication.
  • the second indication indicates: whether the first serving cell is allowed to transition to the dormant BWP outside a discontinuous reception (DRX) active time; and whether the first serving cell is allowed to transition to the dormant BWP within the DRX active time.
  • the first serving cell is not enabled to become dormant more than a number of times in a period of time.
  • a method of a user equipment comprises: receiving a first dormant bandwidth part (BWP) configuration and a second dormant BWP configuration for a first serving cell, wherein a serving cell becomes dormant by setting an associated active BWP of the serving cell to a dormant BWP according to a corresponding dormant BWP configuration, and the UE does not monitor a physical downlink control channel (PDCCH) on the dormant BWP; and determining whether the first serving cell is able to schedule uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof on at least one other serving cell, wherein: in response to determining that the first serving cell is able to schedule the UL transmissions, the DL transmissions, or the combination thereof on the at least one other serving cell, setting the dormant BWP for the first serving cell based on the first dormant BWP configuration; and in response to determining that the first
  • the method further comprises setting an active BWP of the first serving cell to the dormant BWP if the first serving cell is not enabled to schedule a primary cell.
  • the method further comprises receiving a first indication indicating a group of serving cells to become dormant, wherein the group of serving cells includes the first serving cell.
  • the method further comprises receiving a second indication indicating whether the first serving cell is allowed to transition to the dormant BWP, and, in response to determining that the first serving cell is able to schedule the UL transmissions, the DL transmissions, or the combination thereof on the at least one other serving cell, setting an active BWP of the first serving cell to the dormant BWP based on the first dormant BWP configuration.
  • the second indication indicates: whether the first serving cell is allowed to transition to the dormant BWP outside a discontinuous reception (DRX) active time; and whether the first serving cell is allowed to transition to the dormant BWP within the DRX active time.
  • DRX discontinuous reception
  • the first serving cell is not enabled to become dormant more than a number of times in a period of time.
  • the UE not monitoring the PDCCH on the dormant BWP comprises not monitoring the PDCCH on a first set of spans of a plurality of spans and monitoring the PDCCH on a second set of spans of the plurality of spans.
  • the method further comprises setting an active BWP of the first serving cell to the dormant BWP after a certain time from reception of an indication indicating a group of serving cells to become dormant, wherein the group of serving cells includes the first serving cell.
  • the certain time is determined based on a subcarrier spacing (SCS) of a BWP of the first serving cell, and a SCS of a BWP of the at least one other serving cell.
  • SCS subcarrier spacing
  • the method further comprises determining a second serving cell for monitoring the PDCCH corresponding to the at least one other serving cell.
  • an apparatus comprises a user equipment (UE).
  • the apparatus further comprises: a receiver that receives a first dormant bandwidth part (BWP) configuration and a second dormant BWP configuration for a first serving cell, wherein a serving cell becomes dormant by setting an associated active BWP of the serving cell to a dormant BWP according to a corresponding dormant BWP configuration, and the UE does not monitor a physical downlink control channel (PDCCH) on the dormant BWP; and a processor that determines whether the first serving cell is able to schedule uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof on at least one other serving cell, wherein: in response to determining that the first serving cell is able to schedule the UL transmissions, the DL transmissions,
  • the processor sets an active BWP of the first serving cell to the dormant BWP if the first serving cell is not enabled to schedule a primary cell.
  • the receiver receives a first indication indicating a group of serving cells to become dormant, wherein the group of serving cells includes the first serving cell.
  • the receiver receives a second indication indicating whether the first serving cell is allowed to transition to the dormant BWP, and, in response to determining that the first serving cell is able to schedule the UL transmissions, the DL transmissions, or the combination thereof on the at least one other serving cell, setting an active BWP of the first serving cell to the dormant BWP based on the first dormant BWP configuration.
  • the second indication indicates: whether the first serving cell is allowed to transition to the dormant BWP outside a discontinuous reception (DRX) active time; and whether the first serving cell is allowed to transition to the dormant BWP within the DRX active time.
  • DRX discontinuous reception
  • the first serving cell is not enabled to become dormant more than a number of times in a period of time.
  • the UE not monitoring the PDCCH on the dormant BWP comprises not monitoring the PDCCH on a first set of spans of a plurality of spans and monitoring the PDCCH on a second set of spans of the plurality of spans.
  • the processor sets an active BWP of the first serving cell to the dormant BWP after a certain time from reception of an indication indicating a group of serving cells to become dormant, and the group of serving cells includes the first serving cell.
  • the certain time is determined based on a subcarrier spacing (SCS) of a BWP of the first serving cell, and a SCS of a BWP of the at least one other serving cell.
  • SCS subcarrier spacing
  • the processor determines a second serving cell for monitoring the PDCCH corresponding to the at least one other serving cell.
  • the second serving cell is determined based on the first serving cell and a higher layer mapping between the first serving cell and the second serving cell.
  • a method of a network device comprises: transmitting a first dormant bandwidth part (BWP) configuration and a second dormant BWP configuration for a first serving cell, wherein a serving cell becomes dormant by setting an associated active BWP of the serving cell to a dormant BWP according to a corresponding dormant BWP configuration, not transmitting a physical downlink control channel (PDCCH) on the dormant BWP; setting the dormant BWP for the first serving cell based on the first dormant BWP configuration if the first serving cell is configured for cross carrier scheduling of at least one other serving cell for uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof; and setting the dormant BWP for the first serving cell based on the second dormant BWP configuration if the first serving cell is not configured for cross carrier scheduling of at least one other serving cell for uplink (UL) transmissions, downlink
  • PDCCH physical down
  • the method further comprises transmitting a first indication indicating a group of serving cells to become dormant, wherein the group of serving cells includes the first serving cell.
  • the method further comprises transmitting a second indication indicating whether the first serving cell is allowed to transition to the dormant BWP, and the second indication is indicated via the first indication.
  • the second indication indicates: whether the first serving cell is allowed to transition to the dormant BWP outside a discontinuous reception (DRX) active time; and whether the first serving cell is allowed to transition to the dormant BWP within the DRX active time.
  • DRX discontinuous reception
  • the first serving cell is not enabled to become dormant more than a number of times in a period of time.
  • an apparatus comprises a network device.
  • the apparatus further comprises: a transmitter that transmits a first dormant bandwidth part (BWP) configuration and a second dormant BWP configuration for a first serving cell, wherein a serving cell becomes dormant by setting an associated active BWP of the serving cell to a dormant BWP according to a corresponding dormant BWP configuration, not transmitting a physical downlink control channel (PDCCH) on the dormant BWP; and a processor that: sets the dormant BWP for the first serving cell based on the first dormant BWP configuration if the first serving cell is configured for cross carrier scheduling of at least one other serving cell for uplink (UL) transmissions, downlink (DL) transmissions, or a combination thereof; and sets the dormant BWP for the first serving cell based on the second dormant BWP configuration if the first serving cell is not configured for cross carrier scheduling of at least one other
  • the transmitter transmits a first indication indicating a group of serving cells to become dormant, and the group of serving cells includes the first serving cell.
  • the transmitter transmits a second indication indicating whether the first serving cell is allowed to transition to the dormant BWP, and the second indication is indicated via the first indication.
  • the second indication indicates: whether the first serving cell is allowed to transition to the dormant BWP outside a discontinuous reception (DRX) active time; and whether the first serving cell is allowed to transition to the dormant BWP within the DRX active time.
  • DRX discontinuous reception
  • the first serving cell is not enabled to become dormant more than a number of times in a period of time.

Landscapes

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

Abstract

Des appareils, des procédés et des systèmes sont divulgués pour configurer des parties de bande passante dormante. Un procédé (500) consiste à recevoir (502) une première configuration de partie de bande passante dormante (BWP) et une seconde configuration de BWP dormante pour une première cellule de desserte. La cellule de desserte devient dormante par établissement d'une BWP active associée de la cellule de desserte sur une BWP dormante selon une configuration de BWP dormante correspondante, et l'UE ne surveille pas un canal de commande de liaison descendante physique (PDCCH) sur la BWP dormante. Le procédé (500) consiste à déterminer (504) que la première cellule de desserte peut planifier des transmissions de liaison montante (UL), des transmissions de liaison descendante (DL), ou une combinaison de celles-ci sur au moins une autre cellule de desserte, et établir la BWP dormante pour la première cellule de desserte sur la base de la première configuration de BWP dormante.
PCT/IB2022/050195 2021-01-14 2022-01-11 Configuration de parties de bande passante dormante WO2022153179A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163137662P 2021-01-14 2021-01-14
US63/137,662 2021-01-14

Publications (1)

Publication Number Publication Date
WO2022153179A1 true WO2022153179A1 (fr) 2022-07-21

Family

ID=80050915

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2022/050195 WO2022153179A1 (fr) 2021-01-14 2022-01-11 Configuration de parties de bande passante dormante

Country Status (1)

Country Link
WO (1) WO2022153179A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220014342A1 (en) * 2020-07-09 2022-01-13 Qualcomm Incorporated Dormant bandwidth part (bwp) configuration for full-duplex operation

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020198972A1 (fr) * 2019-03-29 2020-10-08 Zte Corporation Configuration de planification spécifique à une partie de bande passante

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020198972A1 (fr) * 2019-03-29 2020-10-08 Zte Corporation Configuration de planification spécifique à une partie de bande passante

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL: "Discussion on SCell dormancy", vol. RAN WG4, no. Electronic Meeting; 20200817 - 20200828, 7 August 2020 (2020-08-07), XP051913984, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG4_Radio/TSGR4_96_e/Docs/R4-2011152.zip R4-2011152.doc> [retrieved on 20200807] *
ZTE CORPORATION: "Discussion on low latency SCell activation", vol. RAN WG1, no. Xi'an, China; 20190408 - 20190412, 30 March 2019 (2019-03-30), pages 1 - 6, XP051691301, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG1%5FRL1/TSGR1%5F96b/Docs/R1%2D1904156%2Ezip> [retrieved on 20190330] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220014342A1 (en) * 2020-07-09 2022-01-13 Qualcomm Incorporated Dormant bandwidth part (bwp) configuration for full-duplex operation
US11870734B2 (en) * 2020-07-09 2024-01-09 Qualcomm Incorporated Dormant bandwidth part (BWP) configuration for full-duplex operation

Similar Documents

Publication Publication Date Title
US11943035B2 (en) Beam failure recovery
US20230337200A1 (en) Requesting a waveform change
US20240129936A1 (en) Configuring a sidelink resource pool
WO2021260604A1 (fr) Transmissions de canal physique partagé descendant se chevauchant
WO2022153179A1 (fr) Configuration de parties de bande passante dormante
US20230397191A1 (en) Dual scheduling configuring
US20240114490A1 (en) Configuring demodulation reference signal bundling and transport block scheduling
WO2023144757A1 (fr) Exécution d&#39;opérations d&#39;écoute avant de parler pour des transmissions de canal de rétroaction de liaison latérale physique
US20240154664A1 (en) Configuring shared and ue specific beams and tci states
US20240032098A1 (en) Optionally performing a listen-before-talk operation
WO2022029728A1 (fr) Multiplexage d&#39;informations d&#39;accusé de réception de demande de répétition automatique hybride
WO2021181312A1 (fr) Détermination de motif de multiplexage sur la base de valeurs d&#39;espacement de sous-porteuse
US20230276455A1 (en) Restrictions based on a configured numerology
US20240205928A1 (en) Configuring physical downlink control channel occasions for monitoring
US20230261839A1 (en) Monitoring downlink control information formats
US20230284190A1 (en) Control information that schedules or activates multiple transmissions
US20230412341A1 (en) Tracking reference signal configuration
WO2023130343A1 (fr) États d&#39;indicateur de configuration de transmission pour des ressources de signal de référence de sondage
WO2023130297A1 (fr) Paramètres de commande de puissance correspondant à une reprise sur défaillance de faisceau
US20240187187A1 (en) Configuring a reference signal resource set based on quasi-co-location information
WO2023007407A1 (fr) Détermination d&#39;une ressource sur la base d&#39;une attribution de ressource
WO2023161850A1 (fr) Configuration d&#39;un indice d&#39;attribution de liaison latérale
WO2024033840A1 (fr) Configuration de largeurs de bande de porteuse pour la communication
WO2024033817A1 (fr) Communication d&#39;informations de partage de temps d&#39;occupation de canal
WO2023053092A1 (fr) Configuration d&#39;un dispositif sur la base de multiples ensembles d&#39;espaces de recherche

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

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

Country of ref document: EP

Kind code of ref document: A1