US20230354327A1 - Methods and apparatus for dynamic spectrum sharing - Google Patents

Methods and apparatus for dynamic spectrum sharing Download PDF

Info

Publication number
US20230354327A1
US20230354327A1 US18/019,288 US202118019288A US2023354327A1 US 20230354327 A1 US20230354327 A1 US 20230354327A1 US 202118019288 A US202118019288 A US 202118019288A US 2023354327 A1 US2023354327 A1 US 2023354327A1
Authority
US
United States
Prior art keywords
pcell
wtru
scell
maximum number
pdcch
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
US18/019,288
Other languages
English (en)
Inventor
Aata EL HAMSS
Paul Marinier
Faris Alfarhan
Ghyslain Pelletier
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent Holdings Inc
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 InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Priority to US18/019,288 priority Critical patent/US20230354327A1/en
Assigned to INTERDIGITAL PATENT HOLDINGS, INC. reassignment INTERDIGITAL PATENT HOLDINGS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: IDAC HOLDINGS, INC.
Assigned to IDAC HOLDINGS, INC. reassignment IDAC HOLDINGS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: PELLETIER, GHYSLAIN, MARINIER, PAUL, EL HAMSS, Aata, ALFARHAN, Faris
Publication of US20230354327A1 publication Critical patent/US20230354327A1/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0001Arrangements for dividing the transmission path
    • H04L5/0003Two-dimensional division
    • H04L5/0005Time-frequency
    • H04L5/0007Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/12Wireless traffic scheduling
    • H04W72/1263Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1273Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0091Signaling for the administration of the divided path
    • H04L5/0094Indication of how sub-channels of the path are allocated
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058Allocation criteria
    • H04L5/0064Rate requirement of the data, e.g. scalable bandwidth, data priority
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0078Timing of allocation
    • H04L5/0087Timing of allocation when data requirements change

Definitions

  • New Radio (NR) technology was specified by 3GPP and was designed to provide high flexibility for both control channels and data channels.
  • control channels NR supports different monitoring patterns as well as different physical downlink control channel (PDCCH) locations within a slot.
  • NR supports variable transmission duration, starting symbol within a slot, and flexible hybrid automatic repeat request (HARQ)-ACK feedback timing.
  • a carrier may support wireless transmit receive units (WTRUs) with different bandwidth capabilities, e.g. narrow band devices as well as broad band devices using a concept of bandwidth parts.
  • WTRUs wireless transmit receive units
  • different bandwidth capabilities e.g. narrow band devices as well as broad band devices using a concept of bandwidth parts.
  • different carrier spacing may be used on the same carrier simultaneously. For example, a large bandwidth part may be configured with a large subcarrier spacing (SCS) while a small bandwidth part be configured with a smaller SCS allowing different WTRUs with different capabilities to coexist on the same spectrum.
  • SCS subcarrier spacing
  • LTE Long Term Evolution
  • Sharing spectrum with LTE requires semi-statically reserving physical resources at least for an LTE control region. This may reduce a NR primary cell (PCell) capacity to transmit downlink control signaling and also may reduce the available resources for data within a slot since the data region should be preceded by a control region.
  • PCell primary cell
  • SCell Supporting NR secondary cell (SCell) scheduling for a NR PCell will create a reliability issue of downlink control information.
  • SCell NR secondary cell
  • a WTRU may not be capable of receiving or monitoring control channels on both cells simultaneously due to an increasing blind decoding effort. Accordingly, there is a need for methods for NR to share spectrum efficiently with LTE.
  • a wireless transmit receive unit may be configured to monitor physical downlink control channel (PDCCH) candidates of a primary cell (PCell) and a secondary cell (SCell).
  • the WTRU may be configured to determine a time duration for PDCCH candidate budgets for a set of symbols based on a subcarrier spacing associated with the PCell and a subcarrier spacing associated with the SCell.
  • the WTRU may be configured to determine a maximum number of PDCCH candidates to allocate to a search space monitoring occasion of the PCell and a search space monitoring occasion of the SCell.
  • the maximum number of PDCCH candidates may be based on a per-cell ratio.
  • the WTRU may be configured to allocate PDCCH candidates for the search space monitoring occasion of the PCell and the search space monitoring occasion of the SCell based on the determined maximum number of PDCCH candidates.
  • the WTRU may be configured to decode an allocated PDCCH candidate.
  • the WTRU may be configured to determine whether there are PCell and SCell search space monitoring occasions that overlap during the set of symbols, and to determine the maximum number of PDCCH candidates to allocate on a condition that there are overlapping search space monitoring occasions.
  • the per-cell ratio may be determined based on a number of configured PDCCH candidates on the PCell (N1) and a number of configured downlink control channel candidates on the SCell (N2).
  • the maximum number of PDCCH candidates for the PCell may be based on the number of configured PDCCH candidates for the PCell (N1) as a fraction of a total number of configured PDCCH candidates for the PCell and the SCell (N1 + N2).
  • FIG. 1 C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1 A according to an embodiment;
  • RAN radio access network
  • CN core network
  • FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1 A according to an embodiment
  • FIG. 2 shows an example method of switching between monitoring patterns
  • FIG. 3 shows an example method of switching between monitoring patterns
  • FIG. 4 shows an example of a WTRU switching between a first monitoring pattern, a transitioning time, and second monitoring pattern
  • FIG. 5 shows an example method of control channel switching
  • FIG. 6 shows an example method for monitoring PDCCH candidates of a PCell and an SCell for scheduling a PCell
  • FIG. 7 is a diagram illustrating a maximum number of PDCCH BD/non-overlapping CCEs for PCell scheduling
  • FIG. 9 illustrates an example search space prioritization using search space priority
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102 a , 102 b , 102 c , 102 d , a radio access network (RAN) 104 , a core network (CN) 106 , a public switched telephone network (PSTN) 108 , the Internet 110 , and other networks 112 , though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • Each of the WTRUs 102 a , 102 b , 102 c , 102 d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102 a , 102 b , 102 c , 102 d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-mounted display
  • the base stations 114 a , 114 b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (NR) NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114 a , 114 b are each depicted as a single element, it will be appreciated that the base stations 114 a , 114 b may include any number of interconnected base stations and/or network elements.
  • the cell associated with the base station 114 a may be divided into three sectors.
  • the base station 114 a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 114 a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • the base stations 114 a , 114 b may communicate with one or more of the WTRUs 102 a , 102 b , 102 c , 102 d over an air interface 116 , which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 116 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like.
  • the base station 114 a in the RAN 104 and the WTRUs 102 a , 102 b , 102 c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed Uplink (UL) Packet Access (HSUPA).
  • the base station 114 a and the WTRUs 102 a , 102 b , 102 c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • the base station 114 a and the WTRUs 102 a , 102 b , 102 c may implement a radio technology such as NR Radio Access, which may establish the air interface 116 using NR.
  • a radio technology such as NR Radio Access
  • the base station 114 a and the WTRUs 102 a , 102 b , 102 c may implement multiple radio access technologies.
  • the base station 114 a and the WTRUs 102 a , 102 b , 102 c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles.
  • DC dual connectivity
  • the air interface utilized by WTRUs 102 a , 102 b , 102 c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB).
  • the base station 114 a and the WTRUs 102 a , 102 b , 102 c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.11 i.e., Wireless Fidelity (WiFi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 1X, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • the base station 114 b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like.
  • the base station 114 b and the WTRUs 102 c , 102 d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the base station 114 b and the WTRUs 102 c , 102 d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • the base station 114 b and the WTRUs 102 c , 102 d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell.
  • a cellular-based RAT e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.
  • the base station 114 b may have a direct connection to the Internet 110 .
  • the base station 114 b may not be required to access the Internet 110 via the CN 106 .
  • the RAN 104 may be in communication with the CN 106 , which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102 a , 102 b , 102 c , 102 d .
  • the data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like.
  • QoS quality of service
  • the CN 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication.
  • the RAN 104 and/or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT.
  • the CN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
  • the CN 106 may also serve as a gateway for the WTRUs 102 a , 102 b , 102 c , 102 d to access the PSTN 108 , the Internet 110 , and/or the other networks 112 .
  • the PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite.
  • the networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers.
  • the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.
  • the WTRUs 102 a , 102 b , 102 c , 102 d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102 a , 102 b , 102 c , 102 d may include multiple transceivers for communicating with different wireless networks over different wireless links).
  • the WTRU 102 c shown in FIG. 1 A may be configured to communicate with the base station 114 a , which may employ a cellular-based radio technology, and with the base station 114 b , which may employ an IEEE 802 radio technology.
  • FIG. 1 B is a system diagram illustrating an example WTRU 102 .
  • the WTRU 102 may include a processor 118 , a transceiver 120 , a transmit/receive element 122 , a speaker/microphone 124 , a keypad 126 , a display/touchpad 128 , non-removable memory 130 , removable memory 132 , a power source 134 , a global positioning system (GPS) chipset 136 , and/or other peripherals 138 , among others.
  • GPS global positioning system
  • the processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 118 may be coupled to the transceiver 120 , which may be coupled to the transmit/receive element 122 . While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114 a ) over the air interface 116 .
  • a base station e.g., the base station 114 a
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • the WTRU 102 may include any number of transmit/receive elements 122 . More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116 .
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122 .
  • the WTRU 102 may have multi-mode capabilities.
  • the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.
  • the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124 , the keypad 126 , and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit).
  • the processor 118 may also output user data to the speaker/microphone 124 , the keypad 126 , and/or the display/touchpad 128 .
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132 .
  • the non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102 , such as on a server or a home computer (not shown).
  • the processor 118 may receive power from the power source 134 , and may be configured to distribute and/or control the power to the other components in the WTRU 102 .
  • the power source 134 may be any suitable device for powering the WTRU 102 .
  • the power source 134 may include one or more dry cell batteries (e.g., nickelcadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • the processor 118 may also be coupled to the GPS chipset 136 , which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102 .
  • location information e.g., longitude and latitude
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114 a , 114 b ) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.
  • the processor 118 may further be coupled to other peripherals 138 , which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like.
  • the peripherals 138 may include one or more sensors.
  • the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor and the like.
  • the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and DL (e.g., for reception) may be concurrent and/or simultaneous.
  • the full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118 ).
  • the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the DL (e.g., for reception)).
  • a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the DL (e.g., for reception)).
  • the RAN 104 may include eNode-Bs 160 a , 160 b , 160 c , though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment.
  • the eNode-Bs 160 a , 160 b , 160 c may each include one or more transceivers for communicating with the WTRUs 102 a , 102 b , 102 c over the air interface 116 .
  • the eNode-Bs 160 a , 160 b , 160 c may implement MIMO technology.
  • the eNode-B 160 a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102 a .
  • Each of the eNode-Bs 160 a , 160 b , 160 c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, and the like. As shown in FIG. 1 C , the eNode-Bs 160 a , 160 b , 160 c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG. 1 C may include a mobility management entity (MME) 162 , a serving gateway (SGW) 164 , and a packet data network (PDN) gateway (PGW) 166 . While the foregoing elements are depicted as part of the CN 106 , it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • the MME 162 may be connected to each of the eNode-Bs 162 a , 162 b , 162 c in the RAN 104 via an S1 interface and may serve as a control node.
  • the MME 162 may be responsible for authenticating users of the WTRUs 102 a , 102 b , 102 c , bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102 a , 102 b , 102 c , and the like.
  • the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.
  • the SGW 164 may be connected to each of the eNode Bs 160 a , 160 b , 160 c in the RAN 104 via the S1 interface.
  • the SGW 164 may generally route and forward user data packets to/from the WTRUs 102 a , 102 b , 102 c .
  • the SGW 164 may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102 a , 102 b , 102 c , managing and storing contexts of the WTRUs 102 a , 102 b , 102 c , and the like.
  • the SGW 164 may be connected to the PGW 166 , which may provide the WTRUs 102 a , 102 b , 102 c with access to packet-switched networks, such as the Internet 110 , to facilitate communications between the WTRUs 102 a , 102 b , 102 c and IP-enabled devices.
  • packet-switched networks such as the Internet 110
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may provide the WTRUs 102 a , 102 b , 102 c with access to circuit-switched networks, such as the PSTN 108 , to facilitate communications between the WTRUs 102 a , 102 b , 102 c and traditional land-line communications devices.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108 .
  • IMS IP multimedia subsystem
  • the WTRU is described in FIGS. 1 A- 1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
  • the other network 112 may be a WLAN.
  • the traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic.
  • the peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
  • the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
  • the IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in 802.11 systems.
  • the STAs e.g., every STA, including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off.
  • One STA (e.g., only one station) may transmit at any given time in a given BSS.
  • HT STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
  • the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
  • MAC Medium Access Control
  • Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.11af and 802.11ah relative to those used in 802.11n, and 802.11ac.
  • 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum.
  • 802.11ah may support Meter Type Control/Machine-Type Communications (MTC), such as MTC devices in a macro coverage area.
  • MTC Meter Type Control/Machine-Type Communications
  • MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
  • the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
  • WLAN systems which may support multiple channels, and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel which may be designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
  • the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.
  • Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • the available frequency bands which may be used by 802.11ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah is 6 MHz to 26 MHz depending on the country code.
  • FIG. 1 D is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an NR radio technology to communicate with the WTRUs 102 a , 102 b , 102 c over the air interface 116 .
  • the RAN 104 may also be in communication with the CN 106 .
  • the gNB 180 a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102 a .
  • the gNBs 180 a , 180 b , 180 c may implement carrier aggregation technology.
  • the gNB 180 a may transmit multiple component carriers to the WTRU 102 a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
  • the gNBs 180 a , 180 b , 180 c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102 a may receive coordinated transmissions from gNB 180 a and gNB 180 b (and/or gNB 180 c ).
  • CoMP Coordinated Multi-Point
  • the WTRUs 102 a , 102 b , 102 c may communicate with gNBs 180 a , 180 b , 180 c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
  • the WTRUs 102 a , 102 b , 102 c may communicate with gNBs 180 a , 180 b , 180 c using subframe or transmission time intervals (TTls) of various or scalable lengths (e.g., containing a varying number of OFDM symbols and/or lasting varying lengths of absolute time).
  • Tls subframe or transmission time intervals
  • the gNBs 180 a , 180 b , 180 c may be configured to communicate with the WTRUs 102 a , 102 b , 102 c in a standalone configuration and/or a non-standalone configuration. In the standalone configuration, WTRUs 102 a , 102 b , 102 c may communicate with gNBs 180 a , 180 b , 180 c without also accessing other RANs (e.g., such as eNode-Bs 160 a , 160 b , 160 c ).
  • eNode-Bs 160 a , 160 b , 160 c eNode-Bs
  • WTRUs 102 a , 102 b , 102 c may utilize one or more of gNBs 180 a , 180 b , 180 c as a mobility anchor point.
  • WTRUs 102 a , 102 b , 102 c may communicate with gNBs 180 a , 180 b , 180 c using signals in an unlicensed band.
  • WTRUs 102 a , 102 b , 102 c may communicate with/connect to gNBs 180 a , 180 b , 180 c while also communicating with/connecting to another RAN such as eNode-Bs 160 a , 160 b , 160 c .
  • WTRUs 102 a , 102 b , 102 c may implement DC principles to communicate with one or more gNBs 180 a , 180 b , 180 c and one or more eNode-Bs 160 a , 160 b , 160 c substantially simultaneously.
  • eNode-Bs 160 a , 160 b , 160 c may serve as a mobility anchor for WTRUs 102 a , 102 b , 102 c and gNBs 180 a , 180 b , 180 c may provide additional coverage and/or throughput for servicing WTRUs 102 a , 102 b , 102 c .
  • Each of the gNBs 180 a , 180 b , 180 c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184 a , 184 b , routing of control plane information towards Access and Mobility Management Function (AMF) 182 a , 182 b and the like. As shown in FIG. 1 D , the gNBs 180 a , 180 b , 180 c may communicate with one another over an Xn interface.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • the CN 106 shown in FIG. 1 D may include at least one AMF 182 a , 182 b , at least one UPF 184 a , 184 b , at least one Session Management Function (SMF) 183 a , 183 b , and possibly a Data Network (DN) 185 a , 185 b . While the foregoing elements are depicted as part of the CN 106 , it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • SMF Session Management Function
  • the AMF 182 a , 182 b may be connected to one or more of the gNBs 180 a , 180 b , 180 c in the RAN 104 via an N2 interface and may serve as a control node.
  • the AMF 182 a , 182 b may be responsible for authenticating users of the WTRUs 102 a , 102 b , 102 c , support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183 a , 183 b , management of the registration area, termination of non-access stratum (NAS) signaling, mobility management, and the like.
  • PDU protocol data unit
  • Network slicing may be used by the AMF 182 a , 182 b in order to customize CN support for WTRUs 102 a , 102 b , 102 c based on the types of services being utilized WTRUs 102 a , 102 b , 102 c .
  • different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and the like.
  • URLLC ultra-reliable low latency
  • eMBB enhanced massive mobile broadband
  • the AMF 182 a , 182 b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • radio technologies such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • the UPF 184 a , 184 b may be connected to one or more of the gNBs 180 a , 180 b , 180 c in the RAN 104 via an N3 interface, which may provide the WTRUs 102 a , 102 b , 102 c with access to packet-switched networks, such as the Internet 110 , to facilitate communications between the WTRUs 102 a , 102 b , 102 c and IP-enabled devices.
  • the UPF 184 , 184 b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, and the like.
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108 .
  • the CN 106 may provide the WTRUs 102 a , 102 b , 102 c with access to the other networks 112 , which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • IMS IP multimedia subsystem
  • the WTRUs 102 a , 102 b , 102 c may be connected to a local DN 185 a , 185 b through the UPF 184 a , 184 b via the N3 interface to the UPF 184 a , 184 b and an N6 interface between the UPF 184 a , 184 b and the DN 185 a , 185 b .
  • one or more, or all, of the functions described herein with regard to one or more of: WTRU 102 a - d , Base Station 114 a - b , eNode-B 160 a - c , MME 162 , SGW 164 , PGW 166 , gNB 180 a - c , AMF 182 a - b , UPF 184 a - b , SMF 183 a - b , DN 185 a - b , and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown).
  • the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions
  • the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
  • the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network.
  • the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation device may be directly coupled to another device for purposes of testing and/or performing testing using over-the-air wireless communications.
  • the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
  • the one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
  • RF circuitry e.g., which may include one or more antennas
  • CG Configured grant or cell group DG Dynamic grant CAPC Channel access priority class DFI Downlink feedback information HARQ PID HARQ Process ID eLAA enhanced Licensed Assisted Access FeLAA Further enhanced Licensed Assisted Access MAC CE MAC control element ACK Acknowledgement BLER Block Error Rate BWP Bandwidth Part CAP Channel Access Priority CCA Clear Channel Assessment CP Cyclic Prefix CP-OFDM Conventional OFDM (relying on cyclic prefix) CQI Channel Quality Indicator CRC Cyclic Redundancy Check CSI Channel State Information CW Contention Window CWS Contention Window Size CO Channel Occupancy DAI Downlink Assignment Index DCI Downlink Control Information DL Downlink DM-RS Demodulation Reference Signal DRB Data Radio Bearer HARQ Hybrid Automatic Repeat Request LAA License Assisted Access LBT Listen-Before-Talk LTE Long Term Evolution e.g.
  • New Radio is designed to provide high data rates, very low latency, and several new features as compared to LTE.
  • spectrum sharing may be used to allow both of these radio access technologies (RATs) to share the same frequency resources.
  • the spectrum sharing feature was designed for early deployments of NR that were expecting a higher number of LTE WTRUs compared to NR WTRUs. After the first deployments of NR, it is expected that the number of NR WTRUs may exceed the number of LTE WTRUs, which motivates a need to redesign and enhance the spectrum sharing feature to enable a more efficient way to share the spectrum between the networks of the two RATs.
  • a common deployment for NR is to have an LTE cell and a NR primary cell (PCell) sharing the same spectrum in a lower frequency region and to provide NR WTRUs with a secondary Cell (SCell) operating in a high frequency region so that a high data rate may be achieved.
  • PCell NR primary cell
  • SCell secondary Cell
  • a WTRU may be configured with control channels on both a PCell and an SCell that can schedule data within a PCell.
  • Embodiments are presented herein on how a WTRU may monitor control channels across different cells to schedule data within a PCell. A focus is on scheduling data on a PCell, but the embodiments presented herein may be applied for other scenarios such as control channels on an SCell and a PCell scheduling data on an SCell as well as control channels on different SCells scheduling data on an SCell.
  • a scheduled cell may be a cell on which a physical downlink shared channel (PDSCH) may be received and/or a physical uplink shared channel (PUSCH) may be transmitted.
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • a PCell may be a scheduled cell.
  • a scheduling cell may be a cell that can schedule a scheduled cell.
  • an SCell may schedule a PCell.
  • a scheduled PCell may schedule itself making the PCell a scheduling cell.
  • a WTRU may be semi-statically configured with a search space set in both a PCell and an SCell for scheduling data on the PCell. Some search spaces may only be present on a PCell, for example, a common search space. To avoid an increase in blind decoding effort while enabling dynamic load balancing, it is proposed to have dynamic signaling to switch or turn off some search spaces.
  • a WTRU may dynamically determine which search space set and/or control channel resources to monitor.
  • the determination on which search space set and/or control channel resources to monitor may be based on, for example: WTRU specific signaling; WTRU common signaling; monitoring pattern and scheduling activity (e.g., a WTRU may monitor control channels on a PCell only on some duration and if it is scheduled by the PCell, the duration may be extended); cell activation/deactivation; DRX cycle; and active BWP.
  • a WTRU may be configured to monitor all the search spaces in an SCell for scheduling a PCell. This may result in WTRU reachability issues. For example, if radio conditions deteriorate on the SCell, the WTRU may not be reached even if the PCell radio link is good.
  • a WTRU may trigger a monitoring of a configured search space on a PCell which may be considered a fallback mechanism.
  • a WTRU may have a common search space to monitor system information and other common signaling in a PCell, but this search space may not be suitable to schedule all WTRUs (blocking probability issue).
  • a WTRU may autonomously activate or start monitoring a search space.
  • a WTRU may perform radio link monitoring on an SCell. If the link quality is bad, the WTRU may switch to monitor control channels on a PCell and indicate or send an indication of the switching to a network entity, for example, a gNB.
  • the indication may be, for example: a transmission on a particular or any PRACH resource, initiation of a RACH procedure; an SR transmission; a special resource for a switching indication; an SRS transmission; or a triggering or inclusion of a MAC CE to indicate the SCell RLM condition of the SCell.
  • the MAC CE may be restricted for transmission on the PCell.
  • Scheduling information may be an uplink grant or a downlink assignment.
  • a property of scheduling information may be, for example: a frequency allocation; an aspect of time allocation, such as a duration; a priority; a modulation and coding scheme; a transport block size; a number of spatial layers; a number of transport blocks to be carried; a TCI state, an SRI; a number of repetitions; whether the grant is a configured grant type 1, type 2 or a dynamic grant; whether the repetition scheme is type A or type B; a configured grant index or a semi-persistent assignment index; a periodicity of a configured grant or assignment; a channel access priority class (CAPC); or any parameter provided in a DCI, by MAC or by RRC, for the scheduling grant or assignment.
  • CAC channel access priority class
  • a property of a grant or assignment may refer to a property of the data included in a corresponding TB.
  • An indication by a DCI may comprise an explicit indication.
  • the explicit indication may be, for example, by a DCI field or by an RNTI used to mask a CRC of a PDCCH.
  • An indication by a DCI may comprise an implicit indication.
  • the implicit indication may be by, for example, a property such as a DCI format, a DCI size, a CORESET or search space, an aggregation level, or an identity of a first control channel resource (e.g., index of first CCE) for a DCI.
  • a mapping between the property and the value may be signaled by, for example, RRC or MAC.
  • a WTRU may switch, activate, or deactivate PDCCH monitoring on a serving cell, BWP, search space, and/or CORESET for reception of downlink control and/or scheduling information corresponding to a particular cell based on reception of WTRU-common signaling.
  • the WTRU may monitor one or more WTRU common search spaces configured on a serving cell.
  • the WTRU may receive information on a WTRU common search space to indicate to the WTRU to switch, activate, or deactivate PDCCH monitoring on a serving cell, BWP, search space, and/or CORESET for reception of downlink control and/or scheduling information for another serving cell.
  • the information may be an indication and may be an explicit or implicit indication.
  • the information may be received in a DCI.
  • a WTRU may switch, activate, or deactivate PDCCH monitoring on a serving cell, BWP, search space, and/or CORESET for reception of downlink control and/or scheduling information corresponding to a particular cell based on reception of a number of DL signals compared to a threshold.
  • the DL signals may include DCls, PDSCHs, and/or PDCCHs.
  • the threshold may be predetermined or dynamically indicated.
  • the WTRU may switch, activate, or deactivate PDCCH monitoring if the number of DL signals is less than or greater than a threshold.
  • the WTRU may switch, activate, or deactivate PDCCH monitoring if the number of DL signals is less than or greater than a threshold during a particular time period.
  • a WTRU may switch, activate, or deactivate PDCCH monitoring on a serving cell, BWP, search space, and/or CORESET for reception of downlink control and/or scheduling information corresponding to a particular cell based on an activation or deactivation of a BWP.
  • the WTRU may start or stop monitoring PDCCH resources associated with scheduling a particular cell upon activation or deactivation of a BWP in that cell (e.g. after reception of a (de)activation BWP switch command or expiration of a BWP inactivity timer).
  • the WTRU may stop monitoring PDCCH resources associated with scheduling a PCell if the SCell BWP on which the PDCCH resources are in is deactivated.
  • the WTRU may start monitoring PDCCH on a different SCell BWP for scheduling the PCell (e.g. either the newly active BWP on the same SCell or a different BWP on a different active serving SCell) or the PCell itself.
  • the WTRU may monitor PDCCH on an SCell for PCell scheduling if the UL and/or DL active BWP on the PCell is from a configured subset of BWPs, a default BWP, an initial BWP, or a non-default BWP.
  • a WTRU may switch, activate, or deactivate PDCCH monitoring on a serving cell, BWP, search space, and/or CORESET for reception of downlink control and/or scheduling information corresponding to a particular cell based on detection of a beam failure.
  • the WTRU may start or stop monitoring PDCCH resources associated with scheduling a particular cell upon detection of a beam failure in the cell on which the PDCCH resources belong to or on the PCell.
  • the WTRU may start monitoring PDCCH on a different SCell for scheduling the PCell, upon beam failure detection on the SCell scheduling the PCell.
  • a WTRU may be configured to select which downlink control channels to monitor among the available control channels that schedule data on a PCell.
  • a WTRU may start a control channel selection procedure after being triggered by one or more of the triggers described herein.
  • a WTRU may be configured with two search space set monitoring patterns.
  • a first monitoring pattern may be to monitor physical resources of a search space set on both an SCell and a PCell for the first symbol within a slot and to monitor physical resources of a search space set on only the SCell in the second and third symbols of a slot.
  • a second monitoring pattern may be to monitor physical resources of a search space set on both an SCell and a PCell for the first symbol within a slot and to monitor physical resources of the search space set on only the PCell in the second and third symbols of a slot.
  • FIG. 2 shows a method of switching between monitoring patterns ( 200 ).
  • a WTRU may monitor, for example as a default, control channels (e.g.
  • a WTRU may be configured with three monitoring patterns with one monitoring pattern that may be applied during a switching or transition time.
  • FIG. 3 shows a method of switching monitoring patterns ( 300 ).
  • the WTRU may monitor control channels (PDCCHs) in a first monitoring pattern ( 310 ).
  • the first monitoring pattern may be a default monitoring pattern.
  • the WTRU may be triggered to switch monitoring patterns ( 320 ). After being triggered to change the monitoring pattern, the WTRU may switch to and use a second monitoring pattern during a transition time ( 330 ).
  • the WTRU may use a third monitoring pattern after transitioning ( 340 ).
  • the pattern configuration may include flexible symbols that may be assumed during the switching or transitioning time.
  • a WTRU may be configured, when it is triggered to switch the monitoring pattern, with the monitoring behavior during the flexible symbols.
  • a WTRU may be configured to monitor control resources on a PCell only, an SCell only, or both the SCell and the PCell, during the flexible symbols.
  • the WTRU may stop monitoring other PDCCH candidates during the transitioning time.
  • the WTRU may prioritize the last received DCI. For example, the WTRU may receive a first DCI in a first monitoring occasion and keep monitoring other monitoring occasions during the transition period. If the WTRU detects a second DCI, the WTRU may prioritize the second DCI.
  • the prioritization may help the WTRU to determine which uplink control channel to use in case of performing selection of an uplink control channel.
  • a WTRU may select an uplink control channel.
  • a WTRU may be configured with an uplink control channel (i.e., PUCCH resources) on an SCell.
  • the WTRU may use the uplink control channel of the SCell if the DCI that schedules data or triggers a CSI report of a PCell is received on the SCell control region.
  • the WTRU may receive a scheduling DCI on an SCell that assigns a PDSCH transmission on the PCell.
  • the WTRU may report HARQ ACK/NACK feedback on a PUCCH on the SCell.
  • a WTRU may determine an uplink control channel to use (e.g., a PUCCH on an SCell or a PUCCH on a PCell) based on a monitoring occasion where the scheduling or triggering DCI is received.
  • the WTRU may be configured to use a PUCCH on an SCell for a HARQ feedback/a-periodic CSI report if the DCI is received during a transition period from one monitoring pattern to another monitoring pattern.
  • the WTRU may use a PUCCH on a PCell during a transition period.
  • a WTRU may use the last used PUCCH cell (e.g., a PUCCH on an SCell or on a PCell) before the transition period.
  • a WTRU may start monitoring the configured search space sets on the PCell if there is a presence or absence of common signals on an SCell.
  • a WTRU may be configured with common search space sets on an SCell to monitor, for example, slot format indication, pre-emption indication, cancellation indication, or a new indication for this purpose (e.g., using a new DCI format). If the WTRU does not detect any common control message for a configured period, the WTRU may switch to monitor the configured search space set on the PCell.
  • the WTRU may provide the indication by transmission of a PRACH.
  • the WTRU may initiate a new random access (RA) procedure and transmit a preamble to a gNB to provide the indication.
  • RA random access
  • Such preamble may be transmitted by the WTRU on a subset of PRACH resources and may be a prioritized RACH procedure.
  • RRC may configure the WTRU with a PRACH resources (e.g., a subset of preambles and/or RACH occasions) that may be used and selected by the WTRU when transmitting a msg1 or a msgA for this purpose.
  • the WTRU may provide the indication by transmission of an SRS.
  • the transmission may be on a configured subset of resources.
  • the WTRU may monitor for a confirmation indication from a gNB ( 530 ) prior to switching to monitor control channels in the PCell.
  • the WTRU may monitor for a confirmation indication from the gNB while or after switching to monitor the control channels in PCell.
  • the WTRU may receive positive or negative confirmation of the switching request ( 540 ). If the gNB sends a negative command and/or the gNB does not respond for a configured time period, the WTRU may switch back to monitor control channels on the SCell ( 550 ). If the WTRU receives a positive confirmation of the switching request, the WTRU may switch to or continue monitoring (if it has already switched) on the requested cell.
  • the WTRU may be configured to receive one or more DCI carrying an explicit confirmation of the switching request.
  • the DCI may carry a bitfield with a value indicating a positive confirmation and another value indicating negative confirmation.
  • Such DCI may be a new format or may be reused from an existing format.
  • the WTRU may receive one or more DCI scheduling DL or UL data as confirmation of the switching request. For example, the WTRU may send a switching request and start monitoring both the PCell and the SCell. If the WTRU receives a DL or UL scheduling on the PCell using control channels on the PCell, the WTRU may interpret the scheduling as a confirmation of the switching request and stop monitoring control channels on the SCell. In an example, the WTRU may receive a DL or UL scheduling DCI using control channels on the SCell. The WTRU may interpret the scheduling as an indication to stop the control channel switching, and the WTRU may keep monitoring control channels on the SCell.
  • a WTRU may be configured to receive a trigger for an a-periodic CSI report after a configured period of requesting the control channel switch as confirmation of the switching request.
  • the WTRU may receive an aperiodic CSI report request after sending a control channel switching request.
  • the WTRU may stop monitoring control channels on the PCell and keep monitoring the SCell for control channels.
  • the WTRU may keep monitoring control channels on the two cells (i.e., SCell and PCell) until the WTRU receives an indication from the gNB to change the configuration. This may enable the network to receive the channel quality of the SCell before reconfiguring the downlink control channels.
  • a WTRU may be configured to receive an SCell activation or deactivation command as confirmation of the switching request.
  • the WTRU may receive a DCI or a MAC CE deactivating the SCell after a configured period of sending the control channel switching request.
  • the SCell deactivation command may be interpreted as a confirmation to monitor only control channels on the PCell.
  • the WTRU may receive a DCI or MAC CE activating the SCell, even though the SCell may already be activated. In this case, the activation command may be interpreted as a negative confirmation of the control channel switching request.
  • An active BWP of scheduling cells and a scheduled cell may have the same subcarrier spacing.
  • a maximum number of PDDCH candidates that a WTRU may process during a time slot, set of symbols, or time duration may be referred to as the maximum number of PDCCH candidates.
  • a maximum number of number of non-overlapping CCEs that a WTRU may process during a time slot, set of symbols, or time duration may be referred to as the maximum number of non-overlapping CCEs.
  • the maximum number of PDCCH candidates or maximum number of non-overlapping CCEs may be determined based on a WTRU capability or may be pre-defined in a specification.
  • a WTRU may support a maximum number of PDCCH candidates or non-overlapping CCEs per scheduled cell which may be divided or distributed across the scheduling cells of a scheduled cell. For example, in a case that a PCell is scheduled by both the PCell and an SCell, a maximum number of PDCCH candidates or non-overlapping CCEs may be divided or distributed across the PCell and the SCell.
  • FIG. 6 shows an example method for monitoring PDCCH candidates of a PCell and an SCell for scheduling a PCell.
  • a WTRU may determine a time duration for PDCCH candidate budgets for a set of symbols based on a subcarrier spacing associated with the PCell and a subcarrier spacing associated with the SCell ( 610 ).
  • the WTRU may determine a maximum number of PDCCH candidates to allocate to a search space monitoring occasion of the PCell and a search space monitoring occasion of the SCell ( 620 ).
  • the maximum number of PDCCH candidates are based on a per-cell ratio.
  • the WTRU may allocate PDCCH candidates for the search space monitoring occasion of the PCell and the search space monitoring occasion of the SCell based on the determined maximum number of PDCCH candidates ( 630 ).
  • the WTRU may decode an allocated PDCCH candidate ( 640 ).
  • the maximum number of PDCCH candidates or non-overlapping CCEs may be distributed equally over the scheduling cells (i.e., PCell and SCell) of a scheduled cell (i.e., PCell).
  • a WTRU may support a maximum of number of PDCCH candidates (M) and a maximum of number of non-overlapping CCE (C) for scheduling on a PCell.
  • M PDCCH candidates
  • C non-overlapping CCE
  • the WTRU may assume a maximum number of M/2 PDCCH candidates and a maximum number of C/2 non-overlapping CCEs on the PCell and a number maximum of M/2 PDCCH candidates and a maximum number of C/2 non-overlapping CCEs on the SCell.
  • a WTRU may be configured, using RRC signaling for example, with a portion of or fraction of the maximum number of PDCCH candidates or a fraction of the maximum number of non-overlapping CCEs to be assumed per scheduling cells of a scheduled cell.
  • the WTRU may be configured to determine the fraction of the maximum number of PDCCH candidates or non-overlapping CCEs to be assumed per scheduling cells of a scheduled cell based on a monitoring configuration of the search space sets. At the beginning of a slot or set of symbols, the WTRU may exclude the scheduling cells that do not have a search space monitoring occasion in the slot or set of symbols for the scheduled cell.
  • the WTRU may be configured with a first search space monitoring pattern within a PCell and a second search space monitoring pattern within an SCell for PCell scheduling.
  • the WTRU may determine that the PCell does not have any monitoring occasions within the slot or set of symbols for PCell scheduling and may assume that the maximum number of PDCCH candidates or non-overlapping CCEs are all within the SCell.
  • the WTRU may use the RRC configuration of the set of search spaces monitoring for scheduling on PCell to determine the maximum number of PDCCH candidates for scheduling.
  • An active BWP of scheduling cells and a scheduled cell may have the different subcarrier spacing.
  • a maximum number of PDDCH candidates and a maximum number of non-overlapping CCEs that a WTRU may process may be defined over a time duration.
  • Such time duration may be a smallest time slot of the different subcarrier spacing (i.e., time slot of the highest subcarrier spacing). For example, if the WTRU is configured with a 15 KHz, 30 KHz and 60 KHz subcarrier spacing, the time duration may be the time slot of the 60 KHz subcarrier spacing.
  • the maximum number of PDCCH candidates or non-overlapping CCEs per scheduled cell may be distributed equally over the scheduling cells of a scheduled cell per time duration.
  • the maximum number of PDCCH candidates or non-overlapping CCEs may be distributed over the scheduling cells of a scheduled cell based on the sub-carrier spacing of the scheduling cells.
  • a lower subcarrier spacing may be configured with a lower maximum number of PDCCH candidates or non-overlapping CCEs per time duration
  • a lower subcarrier spacing may be configured with a higher maximum number of PDCCH candidates or non-overlapping CCEs per time duration.
  • FIG. 7 is a diagram showing a maximum number of PDCCH blind decoding (BD) candidates (M) and maximum number of non-overlapping CCEs (C) for PCell scheduling.
  • the PCell is configured with a 15 KHz sub-carrier spacing and is configured with M1,1>M2,1 and C1,1>C2,1 per the first time duration.
  • the maximum number of PDCCH candidates (M) or non-overlapping CCEs (C) per scheduled cell may be distributed over the scheduling cells of a scheduled cell based on a time slot number or subframe number of the scheduling cell (i.e., M may be a function of time slot M(t) and C may be a function of time slot C(t)).
  • the maximum number of PDCCH candidates or non-overlapping CCEs may be higher in some time slots or subframes and may be lower for some time slots or sub-frames.
  • the SCell and the PCell are scheduling cells for the PCell and the SCell is configured with a 30 KHz subcarrier spacing and the PCell is configured with a 15 KHz subcarrier spacing.
  • the maximum number of PDCCH candidates is M2,1 and the maximum number of non-overlapping CCEs is C2,1.
  • the maximum number of PDCCH candidates is M2,2 and the maximum number of non-overlapping CCEs is C2,2, where M2,2>M2,1 and C2,2>C2,1.
  • a WTRU may be configured with a PCell and an SCell to schedule a PDSCH/PUSCH on the PCell.
  • the WTRU may dynamically determine a maximum number of PDCCH candidates and/or non-overlapping CCEs per scheduling cell.
  • a WTRU may distribute, or allocate, a maximum number of PDCCH candidates or non-overlapping CCEs per scheduled cell across the scheduling cells of the scheduled cell.
  • the distribution or allocation may refer to the processing power over the scheduling cells or how many PDCCH candidates may be processes per slot.
  • the maximum number of PDCCH candidates or non-overlapping CCEs may be based on configured PDCCH candidates.
  • a WTRU may determine that a portion of or fraction of (i.e., less than a maximum) a number of PDCCH candidates or non-overlapping CCEs per scheduled cell are allocated to scheduling cells.
  • the WTRU may determine a portion of the maximum number of PDCCH candidates or non-overlapping CCEs for a scheduling cell based on the configured number of PDCCH candidates or non-overlapping CCEs on search space sets on the scheduling cell over the total configured number of PDCCH/non-overlapping CCEs for the scheduled cell.
  • a WTRU may be configured with a PCell and an SCell to schedule a PDSCH/PUSCH on the PCell.
  • the WTRU may be configured with N1 PDCCH candidates on the PCell for PCell scheduling and N2 PDCCH candidates on the SCell for PCell scheduling.
  • the WTRU may determine the portion, or fraction, of the maximum number of PDCCH candidates for PCell scheduling on PCell is equal to N1/(N1+N2) and on the SCell is equal to N2/(N1+N2).
  • the WTRU may assume a maximum number of PDCCH candidates of MxN2/(N1+N2) on the PCell and MxN1/(N1+N2) on the SCell per time duration / time slot / set of symbols, where M is the maximum number of PDCCH candidates for PCell scheduling using all scheduling cells.
  • the WTRU may not monitor the remaining N1- MxN1/(N1+N2) candidates on the PCell and the remaining N2- MxN2/(N1+N2) candidates on the SCell. Similarly, for the number of non-overlapping CCEs, the WTRU may assume a maximum number of non-overlapping CCEs of CxK1/(K1+K2) on the PCell and CxK1/(K1+K2) on the SCell, where C is the maximum number of non-overlapping CCEs for PCell scheduling using all scheduling cells, and K1 and K2 are the configured number of non-overlapping CCEs per PCell and SCell respectively.
  • the WTRU may be configured to determine a portion of or fraction of the maximum number of PDCCH candidates or non-overlapping CCEs for a scheduling cell based on a frequency bandwidth configured for the CORESET(s) on the scheduling cell to schedule on the scheduled cell over the total frequency bandwidth configured for all CORESETs on different scheduling cells to schedule on the scheduled cell. In an embodiment, the WTRU may determine a portion of or a fraction of the maximum number of PDCCH candidates or non-overlapping CCEs for a scheduling cell based on the frequency bandwidth of the active bandwidth part of the scheduling cell over the total frequency bandwidth of the active bandwidth parts configured to schedule on the scheduled cell.
  • a WTRU may assume a maximum number of PDCCH candidates or non-overlapping CCEs for a scheduling cell per time duration or time slot or set of symbols to be equal to the number of PDCCH candidates/non-overlapping CCEs configured on the search space sets on the scheduling cell per time duration/time slot/set of symbols.
  • a WTRU may be configured with a PCell and an SCell to schedule a PDSCH/PUSCH on the PCell.
  • the WTRU may be configured with a search space set on the PCell with N1 PDCCH candidates and K1 non-overlapping CCEs to schedule on the PCell.
  • the WTRU may be configured with a search space set on the SCell with N2 PDCCH candidates and K2 non-overlapping CCEs to schedule on the PCell.
  • the WTRU may assume a maximum number of PDCCH candidates equal to N2 on the SCell and M-N2 on the PCell per time duration/time slot/set of symbols, where M is the maximum number of PDCCH candidates for PCell scheduling using all scheduling cells.
  • the UE may drop or not monitor N1-(M-N2) PDCCH candidates on PCell.
  • the WTRU may assume a maximum number of non-overlapping CCEs equal to K2 on the SCell and C-K2 on the PCell per time duration/time slot/set of symbols, where C is the maximum number of non-overlapping CCEs for PCell scheduling using all scheduling cells.
  • the WTRU may be configured with a set of search spaces having a total number of PDCCH candidates / total number of non-overlapping CCEs that exceeds the maximum number of PDDCH candidates / maximum number of non-overlapping CCEs per scheduled cell.
  • the WTRU may prioritize over the configured PDCCH candidates / non-overlapping CCEs and/or search spaces and may monitor only a subset of the configured PDCCH candidates / non-overlapping CCEs and/or search spaces.
  • the WTRU may prioritize between search spaces on different scheduling cells for a scheduled cell. At the beginning of a time slot/set of symbols/time duration, the WTRU may prioritize a search space by at least a search space priority or a search space index.
  • FIGS. 9 and 10 show examples of search space prioritization based on search space priority and search space index, respectively.
  • a WTRU may prioritize a search space based on search space priority.
  • the set of search spaces configured across different scheduling cells to schedule a cell may be configured with a priority parameter.
  • a priority parameter For example, for scheduling on a PCell, a set of search spaces may be configured on the PCell and an SCell and each search space may be associated with a priority.
  • the WTRU may select the search spaces in order of priority (e.g., increasing order of priority) until a maximum number of PDCCH candidates/number of non-overlapping CCEs per time slot/set of symbols/time duration is reached.
  • the WTRU may monitor the selected search spaces. As shown in FIG. 9 , the order or monitoring (p1, p2, p3, and p4) is PCell search space 0, PCell search space 1, SCell search space 0, and SCell search space 1.
  • a WTRU may prioritize a search space based on search space index, as shown in FIG. 10 .
  • a set of search spaces may be configured on the PCell and an SCell.
  • the WTRU may select the search spaces of the PCell in increasing order of search space index and after selecting all the search spaces within the PCell and if the maximum number of PDCCH candidates/non overlapping CCEs is not reached, the WTRU may select the search spaces of an SCell in increasing order of search space index until the maximum number of PDCCH candidates/number of non-overlapping CCEs per time slot/set of symbols/time duration is reached.
  • the WTRU may monitor the selected search spaces.
  • the order or monitoring (p1, p2, p3, and p4) is PCell search space 0, SCell search space 0, PCell search space 1, and SCell search space 1.
  • the WTRU may select the search space with a lower search space index from the PCell and select the search space with a lower search space index from the SCell. If the maximum number of PDCCH candidates/non overlapping CCEs is not reached, the WTRU may select the next search space index from the PCell and the next search space index from the SCell.
  • a WTRU may be configured with two search spaces on a PCell (i.e., search space 0 and search space 1) and two search spaces on an SCell (i.e., search space 0 and search space 1).
  • the WTRU may select the search space 0 of the PCell and if the maximum number of PDCCH candidates/non-overlapping CCEs is not reached, then the WTRU may select search space 0 of the SCell. If the maximum number of PDCCH candidates/non-overlapping CCEs is not reached, the WTRU may selects search space 1 of the PCell. If the maximum number of PDCCH candidates/non-overlapping CCEs is not reached, the UE may select search space 1 of the SCell (as shown in FIG. 5 B with p1/p2/p3/p4 is the priority of monitoring the search space).
  • a WTRUE may drop or not monitor some PDCCH candidates/CCEs within a search space if the search space is selected to be monitored because there are some remaining PDCCH candidate/non-overlapping CCEs that the WTRU may process, but the overall PDCCH candidates/CCEs configured for that search space will result in exceeding the maximum number of PDCCH candidates/number of non-overlapping CCEs per slot/set of symbols/time duration.
  • a WTRU may drop or not monitor PDCCH candidates of a certain aggregation level (AL).
  • the WTRU may be configured to select the CCEs with lower indices to monitor in case the configured CCEs for a search space may result in exceeding the maximum number of PDCCH candidates/number of non-overlapping CCEs.
  • ROM read only memory
  • RAM random access memory
  • register cache memory
  • semiconductor memory devices magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Steroid Compounds (AREA)
US18/019,288 2020-08-05 2021-08-05 Methods and apparatus for dynamic spectrum sharing Pending US20230354327A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/019,288 US20230354327A1 (en) 2020-08-05 2021-08-05 Methods and apparatus for dynamic spectrum sharing

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US202063061611P 2020-08-05 2020-08-05
US202163168080P 2021-03-30 2021-03-30
US202163185878P 2021-05-07 2021-05-07
US18/019,288 US20230354327A1 (en) 2020-08-05 2021-08-05 Methods and apparatus for dynamic spectrum sharing
PCT/US2021/044709 WO2022031950A1 (en) 2020-08-05 2021-08-05 Methods and apparatus for dynamic spectrum sharing

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2021/044709 A-371-Of-International WO2022031950A1 (en) 2020-08-05 2021-08-05 Methods and apparatus for dynamic spectrum sharing

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/645,998 Continuation US20240276495A1 (en) 2020-08-05 2024-04-25 Methods and apparatus for dynamic spectrum sharing

Publications (1)

Publication Number Publication Date
US20230354327A1 true US20230354327A1 (en) 2023-11-02

Family

ID=77499951

Family Applications (3)

Application Number Title Priority Date Filing Date
US18/019,288 Pending US20230354327A1 (en) 2020-08-05 2021-08-05 Methods and apparatus for dynamic spectrum sharing
US18/645,998 Pending US20240276495A1 (en) 2020-08-05 2024-04-25 Methods and apparatus for dynamic spectrum sharing
US18/677,257 Pending US20240314784A1 (en) 2020-08-05 2024-05-29 Methods and apparatus for dynamic spectrum sharing

Family Applications After (2)

Application Number Title Priority Date Filing Date
US18/645,998 Pending US20240276495A1 (en) 2020-08-05 2024-04-25 Methods and apparatus for dynamic spectrum sharing
US18/677,257 Pending US20240314784A1 (en) 2020-08-05 2024-05-29 Methods and apparatus for dynamic spectrum sharing

Country Status (7)

Country Link
US (3) US20230354327A1 (ja)
EP (1) EP4193547A1 (ja)
JP (2) JP7481573B2 (ja)
CN (2) CN117353881A (ja)
BR (1) BR112023002070A2 (ja)
TW (1) TWI811755B (ja)
WO (1) WO2022031950A1 (ja)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220417779A1 (en) * 2021-06-25 2022-12-29 Samsung Electronics Co., Ltd. Method for utilizing channel sparsity and coherence in csi feedback

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023211176A1 (ko) * 2022-04-27 2023-11-02 엘지전자 주식회사 무선 통신 시스템에서 신호를 모니터링하는 방법 및 장치

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210084620A1 (en) * 2017-11-14 2021-03-18 Idac Holdings, Inc. Methods for physical downlink control channel (pdcch) candidate determination
US20210168774A1 (en) * 2020-02-13 2021-06-03 Yingyang Li Transmission on a pcell scheduled by an scell pdcch in a 5g nr network
US20210274535A1 (en) * 2020-02-28 2021-09-02 Comcast Cable Communications, Llc Scheduling wireless communications

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160295597A1 (en) * 2013-07-26 2016-10-06 Intel IP Corporation Signaling interference information for user equipment assistance
SG10202009141VA (en) 2014-01-29 2020-11-27 Interdigital Patent Holdings Inc Uplink transmissions in wireless communications
KR102068816B1 (ko) 2018-02-21 2020-01-22 엘지전자 주식회사 무선 통신 시스템에서 bwp 또는 빔 전환에 따라 제어 채널을 구성하는 방법 및 장치
CN110830216B (zh) * 2018-08-10 2021-03-30 华为技术有限公司 确定载波聚合下监控pdcch候选数目的方法和装置
KR20200105406A (ko) * 2019-02-28 2020-09-07 한국전자통신연구원 비면허 대역을 지원하는 통신 시스템에서 제어 정보의 송수신 방법 및 장치
US20230054007A1 (en) * 2019-10-29 2023-02-23 Lg Electronics Inc. Method and device for transmitting and receiving wireless signal in wireless communication system
US11638143B2 (en) * 2020-03-04 2023-04-25 Samsung Electronics Co., Ltd. Blind detection and control channel element monitoring limits in carrier aggregation

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210084620A1 (en) * 2017-11-14 2021-03-18 Idac Holdings, Inc. Methods for physical downlink control channel (pdcch) candidate determination
US20210168774A1 (en) * 2020-02-13 2021-06-03 Yingyang Li Transmission on a pcell scheduled by an scell pdcch in a 5g nr network
US20210274535A1 (en) * 2020-02-28 2021-09-02 Comcast Cable Communications, Llc Scheduling wireless communications

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220417779A1 (en) * 2021-06-25 2022-12-29 Samsung Electronics Co., Ltd. Method for utilizing channel sparsity and coherence in csi feedback

Also Published As

Publication number Publication date
JP2023536878A (ja) 2023-08-30
TWI811755B (zh) 2023-08-11
BR112023002070A2 (pt) 2023-05-02
US20240276495A1 (en) 2024-08-15
WO2022031950A1 (en) 2022-02-10
JP7481573B2 (ja) 2024-05-10
CN115989708A (zh) 2023-04-18
CN117353881A (zh) 2024-01-05
JP2024099729A (ja) 2024-07-25
US20240314784A1 (en) 2024-09-19
EP4193547A1 (en) 2023-06-14
TW202211702A (zh) 2022-03-16

Similar Documents

Publication Publication Date Title
JP7138170B2 (ja) 無線システムにおける補助的なアップリンク送信
TWI758351B (zh) 無線傳輸/接收單元及由其實施的方法
US20230216565A1 (en) Beam indication based on tci state group
TW202402080A (zh) 頻寬部分操作系統及方法
US20230189245A1 (en) Methods and apparatus for downlink small data reception
US20240323873A1 (en) Methods and systems for efficient uplink (ul) synchronozation maintenance with a deactivated secondary cell group (scg)
US20240314784A1 (en) Methods and apparatus for dynamic spectrum sharing
US12132577B2 (en) Methods and apparatuses for improved voice coverage
US20240267846A1 (en) Wtru power saving in active time
WO2023211998A1 (en) Fbe channel access in sidelink unlicensed
WO2023081258A1 (en) Methods, architectures, apparatuses and systems for network energy savings
US20240373431A1 (en) Methods, architectures, apparatuses and systems for network energy savings
US20240340959A1 (en) Sidelink collision detection and indication
US20240357631A1 (en) Methods and apparatus to support large scale qos state transition
US20230363006A1 (en) Rach Enhancements for Radar Coexistence
US20240314835A1 (en) Enhanced channel access
US20240187160A1 (en) Methods for enabling carrier switching for uplink control information
EP4430903A1 (en) Methods on enhancing reliability and supporting mixed priority traffic in high frequency communications
TW202433988A (zh) 基於dl—dci中之utci選擇器之pdsch預設波束判定
CN117242835A (zh) 活动时间中的wtru功率节省

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTERDIGITAL PATENT HOLDINGS, INC., DELAWARE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:IDAC HOLDINGS, INC.;REEL/FRAME:062956/0506

Effective date: 20221216

Owner name: IDAC HOLDINGS, INC., DELAWARE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:EL HAMSS, AATA;MARINIER, PAUL;ALFARHAN, FARIS;AND OTHERS;SIGNING DATES FROM 20220929 TO 20221003;REEL/FRAME:062887/0156

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED