[go: up one dir, main page]

WO2025235293A1 - Réalité étendue dans un spectre sans licence - Google Patents

Réalité étendue dans un spectre sans licence

Info

Publication number
WO2025235293A1
WO2025235293A1 PCT/US2025/027310 US2025027310W WO2025235293A1 WO 2025235293 A1 WO2025235293 A1 WO 2025235293A1 US 2025027310 W US2025027310 W US 2025027310W WO 2025235293 A1 WO2025235293 A1 WO 2025235293A1
Authority
WO
WIPO (PCT)
Prior art keywords
wtru
channel
capc
channel access
pdu
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
PCT/US2025/027310
Other languages
English (en)
Inventor
Ahmed Mostafa
Jaya Rao
J. Patrick Tooher
Senay NEGUSSE
Tejaswinee LUTCHOOMUN
Tuong Duc HOANG
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
Publication of WO2025235293A1 publication Critical patent/WO2025235293A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0866—Non-scheduled access, e.g. ALOHA using a dedicated channel for access
    • H04W74/0875—Non-scheduled access, e.g. ALOHA using a dedicated channel for access with assigned priorities based access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal

Definitions

  • a fifth generation may be referred to as 5G.
  • a previous (legacy) generation of mobile communication may be, for example, fourth generation (4G) long term evolution (LTE).
  • 4G fourth generation
  • LTE long term evolution
  • a wireless transmit/receive unit may receive configuration information indicating a channel access reconfiguration condition.
  • the WTRU may determine a protocol data unit (PDU) parameter associated with a PDU.
  • the WTRU may determine, based on the PDU parameter and the channel access reconfiguration condition, that a channel access parameter of multiple channel access parameters is to be used for a channel sensing.
  • the WTRU may perform the channel sensing using the channel access parameter.
  • the WTRU may transmit the PDU based on the channel sensing.
  • PDU protocol data unit
  • the WTRU may send a reservation indication associated with one or more channel occupancy times (COTs).
  • COTs channel occupancy times
  • the reservation indication may indicate that the WTRU has a channel sensing advantage associated with the one or more COTs.
  • the WTRU may perform the channel sensing to acquire the one or more COTs.
  • the one or more COTs may include a number of consecutive COTs.
  • the WTRU may determine a first channel access parameter (e.g., of the multiple channel access parameters) based on the configuration information.
  • the WTRU may determine that the channel access reconfiguration condition has been satisfied (e.g., the channel access reconfiguration condition may be determined based on the configuration information).
  • the WTRU may determine to select a second channel access parameter for the channel sensing based on the determination that the channel access reconfiguration condition has been satisfied.
  • the WTRU may determine to select a second CAPC value based on the satisfaction of the channel access reconfiguration condition, and the second CAPC value may be associated with a higher priority than the first CAPC value.
  • the WTRU may determine a second channel sensing time duration based on the second CAPC value.
  • the WTRU may determine, based on the second channel sensing time duration, that a second remaining time duration associated with the latency budget for transmitting the remaining payload is equal to or higher than the remaining latency threshold.
  • the WTRU may select the second CAPC value for the channel sensing based on the determination that the second remaining time duration is equal to or higher than the remaining latency threshold.
  • the WTRU may determine, based on the configuration information, a maximum number of COTs associated with the second CAPC value.
  • the WTRU may determine a number of consecutive COTs based on the second CAPC value, the maximum number of COTs, and the remaining payload.
  • the WTRU may transmit the remaining payload using the number of consecutive COTs.
  • the PDU parameter may include a PDU set delay budget (PSDB), and the WTRU may determine the remaining latency threshold based on the PSDB.
  • PSDB PDU set delay budget
  • the WTRU may select a minimum contention window value based on the selection of the second CAPC value.
  • the second CAPC value may be associated with a plurality of contention window values, and the WTRU may select the minimum contention window value of the plurality of contention window values and perform the channel sensing based on the minimum contention window, value.
  • FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented;
  • FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;
  • WTRU wireless transmit/receive unit
  • 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. 1A 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. 1A according to an embodiment
  • FIG. 2 illustrates an example table of channel access priority class (CAPC) used, for example, for UL;
  • CAC channel access priority class
  • FIG. 3 illustrates an example for sensing at the end of COT for initiating consecutive COTs
  • FIG. 4 illustrates different approaches for channel access parameter selection.
  • FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a CN 106/115, 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.
  • WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d 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
  • a vehicle a drone
  • the communications systems 100 may also include a base station 114a and/or a base station 114b.
  • Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 110, and/or the other networks 112.
  • the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
  • the base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc.
  • BSC base station controller
  • RNC radio network controller
  • the base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum.
  • a cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e. , one for each sector of the cell.
  • the base station 114a 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 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 114a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115/116/117 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 UL Packet Access (HSUPA).
  • the base station 114a and the WTRUs 102a, 102b, 102c 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 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR).
  • a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • the base station 114a and the WTRUs 102a, 102b, 102c 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 102a, 102b, 102c 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 114a and the WTRUs 102a, 102b, 102c 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
  • GSM Global System for
  • the base station 114b 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 114b and the WTRUs 102c, 102d 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 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • the base station 114b and the WTRUs 102c, 102d 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.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required to access the Internet 110 via the CN 106/115.
  • the RAN 104/113 may be in communication with the CN 106/115, 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 102a, 102b, 102c, 102d.
  • 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/115 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/113 and/or the CN 106/115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/113 or a different RAT.
  • the CN 106/115 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/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d 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/113 or a different RAT.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links).
  • the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, 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) circuits, 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 114a) over the air interface 116.
  • 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 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., nickel-cadmium (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 114a, 114b) 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 locationdetermination 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.
  • FM frequency modulated
  • 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, and/or a humidity sensor.
  • 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, and/or a humidity sensor.
  • 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 downlink (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 WRTU 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 downlink (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 downlink (e.g., for reception)).
  • FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include eNode-Bs 160a, 160b, 160c, 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 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, 160c 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 160a, 160b, 160c 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 (or PGW) 166. While each of 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 160a, 160b, 160c 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 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, 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 160a, 160b, 160c in the RAN 104 via the S1 interface.
  • the SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • 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 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
  • the SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c 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 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c 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 CN 106 may provide the WTRUs 102a, 102b, 102c 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.
  • 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.
  • a WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP.
  • the AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
  • Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
  • Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
  • 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.11 z 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 via signaling.
  • 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 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.
  • High Throughput (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.
  • VHT STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels.
  • the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
  • a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
  • the data, after channel encoding may be passed through a segment parser that may divide the data into two streams.
  • Inverse Fast Fourier Transform (IFFT) processing, and time domain processing may be done on each stream separately.
  • IFFT Inverse Fast Fourier Transform
  • 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.11 af and 802.11 ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 n, and 802.11 ac.
  • 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non- TVWS spectrum.
  • 802.11 ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area.
  • 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).
  • 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, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • the available frequency bands which may be used by 802.11 ah, 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.11 ah is 6 MHz to 26 MHz depending on the country code.
  • the RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment.
  • the gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • the gNB 180a may transmit multiple component carriers to the WTRU 102a (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 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • the gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
  • WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
  • eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
  • Each of the gNBs 180a, 180b, 180c 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, dual connectivity, interworking between NR and E- UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node.
  • the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like.
  • Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
  • 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 machine type communication (MTC) access, and/or the like.
  • URLLC ultra-reliable low latency
  • eMBB enhanced massive mobile broadband
  • MTC machine type communication
  • the AMF 182 may provide a control plane function for switching between the RAN 113 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 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.
  • the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
  • DN local Data Network
  • one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-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 may 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 testing 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
  • a wireless transmit/receive unit may receive configuration information indicating one or more channel access parameters.
  • the WTRU may determine a protocol data unit (PDU) parameter (e.g., a PDU set delay budget associated with the PDU) associated with the PDU/a PDU set that includes the PDU.
  • PDU protocol data unit
  • the WTRU may determine, based on the PDU parameter, that a channel access parameter (e.g., channel access priority class (CAPC)) indicated in the configuration information is to be selected for channel sensing by the WTRU.
  • the WTRU may perform channel sensing using the channel access parameter.
  • the WTRU may determine a channel occupancy time (COT) based on the channel sensing.
  • COT channel occupancy time
  • the WTRU may determine a number of consecutive COTs based on determining that the channel access parameter is to be selected for the channel sensing by the WTRU.
  • the WTRU may send a reservation indication associated with the number of consecutive COTs.
  • the reservation indication may indicate that the WTRU has a channel sensing advantage associated with the number of consecutive COTs.
  • the reservation indication may indicate the number of consecutive COTs and/or the channel access parameter associated with the number of consecutive COTs.
  • the reservation indication may indicate a contention window size associated with the channel access parameter.
  • the WTRU may receive a reservation response to the reservation indication.
  • the WTRU may, based on receiving the reservation response, select the second channel access parameter for the channel sensing by the WTRU.
  • the WTRU may send the reservation indication on a COT before the COT used to send the PDU, and the reservation response may be received on the same COT via COT sharing.
  • the configuration information may indicate a maximum number of consecutive COTs associated with the channel access parameter.
  • the WTRU may determine the number of consecutive COTs based on a remaining payload size and/or the maximum number of consecutive COTs associated with the channel access parameter.
  • the WTRU may determine, based on the configuration information, a first channel access parameter.
  • the configuration information may indicate that the first channel access parameter is a default channel access parameter to use.
  • the WTRU may determine, based on the PDU parameter, that the second channel access parameter is to be selected to replace the first channel access parameter, for channel sensing.
  • the configuration information may indicate a triggering condition for the replacement of the first channel access parameter and/or a maximum number of consecutive COTs associated with the second channel access parameter.
  • CAPC configuration(s) may be used in one or more examples herein, for example, for meeting XR QoS requirements.
  • a WTRU may configure CAPC on unlicensed spectrum, for example, to meet the QoS requirements of XR traffic flows.
  • Retransmission(s) of XR PDUs may be performed on licensed spectrum, for example, after initially transmitting them on unlicensed spectrum.
  • a WTRU may monitor NR PDCCH transmission(s) to trigger PDU retransmission(s) on NR, for example, due to channel access/transmission failures on NR-U.
  • a wireless transmit/receive unit may receive configuration information indicating a channel access reconfiguration condition.
  • the WTRU may determine a protocol data unit (PDU) parameter associated with a PDU.
  • the WTRU may determine, based on the PDU parameter and the channel access reconfiguration condition, that a channel access parameter of multiple channel access parameters is to be used for a channel sensing.
  • the WTRU may perform the channel sensing using the channel access parameter.
  • the WTRU may transmit the PDU based on the channel sensing.
  • PDU protocol data unit
  • the WTRU may send a reservation indication associated with one or more channel occupancy times (COTs).
  • COTs channel occupancy times
  • the reservation indication may indicate that the WTRU has a channel sensing advantage associated with the one or more COTs.
  • the WTRU may perform the channel sensing to acquire the one or more COTs.
  • the one or more COTs may include a number of consecutive COTs.
  • the WTRU may determine a first channel access parameter (e.g., of the multiple channel access parameters) based on the configuration information.
  • the WTRU may determine that the channel access reconfiguration condition has been satisfied (e.g., the channel access reconfiguration condition may be determined based on the configuration information).
  • the WTRU may determine to select a second channel access parameter for the channel sensing based on the determination that the channel access reconfiguration condition has been satisfied.
  • the WTRU may determine a first channel access priority class (CAPC) value based on the configuration information.
  • the WTRU may determine a remaining payload to be transmitted.
  • the WTRU may determine a first channel sensing time duration based on the first CAPC value.
  • the WTRU may determine, based on the first channel sensing time duration, that a first remaining time duration associated with a latency budget for transmitting the remaining payload is lower than a remaining latency threshold.
  • the WTRU may determine that the channel access reconfiguration condition is satisfied based on determining that the first remaining time duration is lower than the remaining latency threshold.
  • the WTRU may determine to select a second CAPC value based on the satisfaction of the channel access reconfiguration condition, and the second CAPC value may be associated with a higher priority than the first CAPC value.
  • the WTRU may determine a second channel sensing time duration based on the second CAPC value.
  • the WTRU may determine, based on the second channel sensing time duration, that a second remaining time duration associated with the latency budget for transmitting the remaining payload is equal to or higher than the remaining latency threshold.
  • the WTRU may select the second CAPC value for the channel sensing based on the determination that the second remaining time duration is equal to or higher than the remaining latency threshold.
  • the WTRU may determine, based on the configuration information, a maximum number of COTs associated with the second CAPC value.
  • the WTRU may determine a number of consecutive COTs based on the second CAPC value, the maximum number of COTs, and the remaining payload.
  • the WTRU may transmit the remaining payload using the number of consecutive COTs.
  • the PDU parameter may include a PDU set delay budget (PSDB), and the WTRU may determine the remaining latency threshold based on the PSDB.
  • PSDB PDU set delay budget
  • the WTRU may select a minimum contention window value based on the selection of the second CAPC value.
  • the second CAPC value may be associated with a plurality of contention window values, and the WTRU may select the minimum contention window value of the plurality of contention window values and perform the channel sensing based on the minimum contention window, value.
  • XR traffic may include one or more of the following types: Video frames, Pose information, Audio packets, Data packets, or Haptic information.
  • XR traffic may be in different sizes and/or periodicities (e.g., 30-120 fps at rate 30-60 Mbps (video), 100 bytes every 4 ms (pose), or 100 fps at 0.756-1.12 Mbps (audio)).
  • XR traffic may be associated with different delay budgets (e.g., 10 ms (AR/VR), 15ms (CG), or 30ms (audio)).
  • XR traffic may be in different arrival types (e.g., Periodic, Quasi-periodic, or Event- triggered).
  • a PDU set may include a group of associated PDUs, for example, with a common delay budget (e.g., earlier information about upcoming traffic). Synchronization in one or more examples may be based on QoS requirement(s) on the drift between associated PDUs.
  • NR may be implemented on Unlicensed Spectrum (NR-U).
  • Unlicensed bands may be shared by other radios (e.g., WLAN, Bluetooth, etc.).
  • operating on unlicensed bands may include enforcing limitations on transmitting power and/or channel occupancy time (COT), for example, due to regulations.
  • COT(s) may be shared by consecutive DL and UL transmissions.
  • Operating on unlicensed bands may require sensing the channel before transmission.
  • Multiple channel access approaches may be used (e.g., two types of channel access: dynamic, semi-static (e.g., when no other unlicensed band technology is operating in the environment).
  • Type 1 e.g., this type may be similar to exponential random backoff, before first transmission
  • Type 2 e.g., this type may use fixed sensing time, before consecutive transmission during the same COT or COT sharing.
  • Configured grant(s) CGs
  • CAC Channel access priority class
  • a failure of access (e.g., due to occupied channel) which may be detected by channel sensing may be distinguished from a failure of transmission (e.g., due to low channel quality) which may be detected by receiving NACKs.
  • FIG. 2 illustrates an example table of channel access priority class (CAPC) used for UL. As shown in FIG.
  • CAC channel access priority class
  • a (e.g., each) CAPC value may be associated with one or more contention window sizes.
  • the one or more contention window sizes may include a minimum contention window size.
  • CAPC 3 may be associated with contention window sizes 15, 31, 63, etc., and a minimum contention window size 15 may be associated with CAPC 3.
  • NR-U may be used to support services associated with XR (e.g., XR may benefit from supporting XR services on NR-U) for supporting one or more of the following: higher capacity (e.g., augmenting radio resources across bands), offloading some traffic to unlicensed bands (e.g., this may be encouraged by operators), and/or enhanced reliability and QoS.
  • higher capacity e.g., augmenting radio resources across bands
  • offloading some traffic to unlicensed bands e.g., this may be encouraged by operators
  • enhanced reliability and QoS e.g., QoS.
  • scenario 1 single-band operation(s) (e.g., standalone NR-U) in which a WTRU communicates using NR-U (e.g., using NR-U only, for example, monitoring I loT environment via XR, where NR is occupied by a higher priority URLLC traffic)
  • scenario 2 dual-band operation(s) (e.g., NR aggregation to NR-U or vice versa), in which a WTRU communicates using both primary and secondary bands according to a WTRU capability (e.g., it can be based on band switching and using a single band at a time or simultaneous operation on both bands with limited of full capability of transmission and reception on the secondary band).
  • Feature(s) in one or more examples herein may be used to overcome channel sensing delay(s) before acquiring COT(s) for data transmission(s), for example, to support XR operation(s) on NR-U.
  • CAPO and/or CAPO adaptation may be described using CAPO and/or CAPO adaptation as an example.
  • the examples are applicable to an (e.g., any) unlicensed channel access parameter adaptation (e.g., CAPO, an energy detection threshold, a listen before talk (LBT) parameter, LBT bandwidth (BW), a LBT slot duration, an LBT procedure, an LBT type, and/or the number of LBT slots), and the use of the term CAPO herein may be understood to be replaceable by any other channel access parameter term.
  • CAPO channel access parameter adaptation
  • channel access parameter(s) in one or more examples herein may refer to one or more of: CAPC, an energy detection threshold, an LBT parameter, an LBT bandwidth (BW), an LBT slot duration, an LBT procedure, an LBT type, or the number of LBT slots.
  • a WTRU e.g., an XR WTRU
  • a WTRU may be configured to operate in unlicensed band(s) (e.g., NR-U).
  • the WTRU may use (e.g., require) a long COT, or multiple consecutive COTs, for meeting QoS requirements (e.g., PSDB) for certain types of traffic (e.g., XR video) without incurring large channel sensing delays.
  • QoS requirements e.g., PSDB
  • the WTRU may be enabled to meet its QoS requirements (e.g., PSDB requirement) on NR-U by one or more of the following: configuring multiple CAPCs for the same XR traffic type (e.g., to enable shorter channel sensing time) before acquiring COT(s) for uplink transmission(s) as remaining latency decreases; enabling the WTRU to reserve a COT on a specific set of resource blocks by decreasing its channel sensing time without violating unlicensed band regulations (e.g., using a minimum contention window value and/or sending a COT reservation indication to a gNB).
  • QoS requirements e.g., PSDB requirement
  • a WTRU may receive configuration information, including one or more of the following: a subset of channel access parameters (e.g., CAPC) values associated with XR data (e.g., CAPC 1 and CAPC 2 for XR video data; CAPC 1 may have, for example, lower priority / longer expected channel sensing time / longer COT) than CAPC 2); default channel access parameters (e.g., CAPC) and/or condition(s) for channel access parameters reconfiguration (e.g., condition(s) for CAPC reselection), for example, a remaining latency threshold and/or a buffer size threshold; a maximum number of consecutive COTs for a respective channel access parameter value (e.g., CAPC).
  • CAPC channel access parameters
  • the WTRU may receive one or more PDUs of PDU set(s) from application layer(s).
  • the WTRU may determine the information (e.g., one or more PDU parameters) associated with the PDU(s) (e.g., the total payload size, the number of PDU subsets, and/or PSDB), for example, based on the received PDU(s).
  • the WTRU may determine that a channel access parameter (e.g., CAPC) associated with the PDU is to be selected, for example, based on the information associated with the PDU(s).
  • the WTRU may determine, based on the PDU parameter, that a channel access parameter of multiple channel access parameters is to be selected for channel sensing.
  • the PDU parameter may be one or more of PSDB, a remaining latency threshold, a PDU set priority, a WTRU buffer size, and/or a WTRU buffer size threshold or limitations.
  • the WTRU may determine, based on the PDU parameter and the channel access reconfiguration condition, that a channel access parameter of multiple channel access parameters is to be used for a channel sensing.
  • the WTRU may trigger channel access parameter (e.g., CAPC) (re)selection for one or more COTs based on one or more of: PSDB, a remaining latency threshold, a PDU set priority, a WTRU buffer size, and/or a WTRU buffer size threshold or limitations.
  • CAPC channel access parameter
  • the WTRU may determine (e.g., select) a channel access parameter (e.g., CAPC) to be used for the transmission of the one or more PDUs of the PDU set(s), for example, based on determining that a channel access reconfiguration condition is satisfied.
  • the WTRU may determine a number of consecutive COTs (e.g., COTs shown at 328 and 332 in FIG. 3) based on determining that a channel access parameter (e.g., higher priority CAPC) is to be (re)selected, for example, for the channel sensing by the WTRU.
  • a channel access parameter e.g., higher priority CAPC
  • the WTRU may determine a number of consecutive COTs to be used (e.g., the number of consecutive COTs that may be required assuming a configured and WTRU-selected higher priority CAPC), for example, based on the remaining payload size and the maximum number of consecutive COTs for the higher priority CAPC.
  • the WTRU may send (e.g., shown at 322) a reservation indication (e.g., a reservation request) that indicates that the WTRU has a channel sensing advantage/priority associated with one or more COTs (e.g., the number of consecutive COTs).
  • the WTRU may transmit a reservation request to reserve COT(s) (e.g., a COT reservation advantage request as shown at 322 in FIG.3), including one or more of: the determined number of consecutive COTs (e.g., as required to meet PSDB requirement(s) associated with PDUs coming from application layer(s)); the CAPC to be used (e.g., the configured and the WTRU-selected higher priority CAPC to be used); or certain contention window values to be used (e.g., along with the selected high priority CAPC).
  • the WTRU may receive (e.g., as shown at 324 in FIG.
  • a reservation response (e.g., a confirmation or an approval) of the reservation request for a reservation advantage on a set of resource blocks (e.g., the COT reservation advantage on a set of resource blocks) from a base station (e.g., a gNB), for example, during the same COT in subsequent DL transmission via COT sharing.
  • the WTRU may update the current CAPC to a higher priority CAPC (e.g., CAPC 2 used for channel sensing as shown at 326 and 330 in FIG. 3).
  • the WTRU may initiate a COT using the determined channel access parameter (e.g., CAPC).
  • the WTRU may transmit the one or more PDUs in the WTRU-initiated COT.
  • FIG. 3 illustrates an example for sensing at the end of COT for initiating consecutive COTs.
  • the WTRU may perform channel sensing (e.g., Type-1 channel sensing) using CAPC 2 and determine a COT (e.g., the WTRU may initiate the COT of the consecutive COTs) based on the channel sensing.
  • channel sensing e.g., Type-1 channel sensing
  • the WTRU may perform channel sensing (e.g., Type-1 sensing) using a first CAPC value (e.g., CAPC-1).
  • the WTRU may determine to send a reservation indication (e.g., based on determining that a channel access parameter reconfiguration condition is satisfied).
  • the WTRU may receive a response to the reservation indication.
  • the WTRU may perform channel sensing (e.g., Type-1 sensing) using a second CAPC value (e.g., CAPC 2).
  • the WTRU may transmit information (e.g., some or all of the remaining payload) using a first COT (e.g., a first COT of consecutive COTs).
  • the WTRU may perform channel sensing (e.g., Type-1 sensing) using the second CAPC value (e.g., CAPC 2).
  • the WTRU may transmit information (e.g., some or all of the remaining payload) using a second COT (e.g., a second COT of consecutive COTs).
  • the WTRU may be configured with (e.g., a network configuration), one or more threshold values associated with any of the parameters described herein. Such threshold values for the parameters may be received by the WTRU via any of NAS, RRC, MAC CE, and/or DCI signaling.
  • CAPC configuration and/or COT reservation may be made for XR WTRUs.
  • a WTRU e.g., an XR WTRU
  • higher CAPC may enable shorter channel sensing time (e.g., at the expense of short channel occupancy time (COT)).
  • COT short channel occupancy time
  • XR high priority traffic e.g., XR video PDU sets
  • a WTRU e.g., an XR WTRU
  • QoS requirements e.g., PSDB requirement
  • the WTRU may be enabled to meet its QoS requirements by configuring multiple CAPCs for the same XR traffic type, for example, to enable shorter channel sensing time before acquiring COT(s) for uplink transmission(s) as the remaining latency decreases.
  • the WTRU may be enabled to meet its QoS requirements by providing a COT reservation priority or advantage (e.g., over other WTRUs) for consecutive COT reservation(s) (e.g., consecutive COT reservation(s) that does not contradict with unlicensed band access regulations).
  • a COT reservation priority or advantage e.g., over other WTRUs
  • consecutive COT reservation(s) e.g., consecutive COT reservation(s) that does not contradict with unlicensed band access regulations.
  • the WTRU may receive configuration Information in one or more examples herein.
  • the WTRU may receive configuration from the network, e.g., during RRC (re)configuration, information that may include any one or more of the following.
  • the second channel sensing time duration may be shorter than the first channel sensing time.
  • the COT duration for a CAPC may be configured by the network, for example, as a function of the PSDB of the UL traffic.
  • a CAPC from the subset of CAPCs may be set as the default initial CAPC for that traffic type.
  • the WTRU may receive one CAPC configuration per traffic flow, e.g., one CAPC configuration for a video flow and one CAPC configuration for an audio flow.
  • the CAPC configuration may include an identifier on the flow to which it is relevant or applicable (e.g., a multimodal service flow ID).
  • the information may include default channel access parameter(s) (e.g., CAPC) and conditions for channel access parameters (e.g., CAPC) (re)selection (e.g., a remaining latency threshold and/or a buffer size threshold).
  • CAPC channel access parameter
  • CAPC CAPC
  • re)selection e.g., a remaining latency threshold and/or a buffer size threshold.
  • CAPC configuration information may indicate a flexible selection of CAPC by WTRU. For example, based on information on the CAPC (e.g., one or more of: a COT duration, priority, and/or channel sensing time) and/or information on the XR traffic that the WTRU may receive (e.g., from the application), the WTRU may select the CAPC configuration that matches (e.g., best matches) the XR traffic.
  • information on the CAPC e.g., one or more of: a COT duration, priority, and/or channel sensing time
  • the WTRU may select the CAPC configuration that matches (e.g., best matches) the XR traffic.
  • CAPC configuration information may indicate a default CAPC with a capability of CAPC change under certain conditions (e.g., the remaining latency threshold, at which a CAPC change may be triggered when a remaining latency (e.g., the difference between current time and PSDB) is below the threshold).
  • a WTRU may determine a first channel sensing time duration based on the first CAPC value. The WTRU may determine, based on the first channel sensing time duration, that a first remaining time duration associated with a latency budget for transmitting the remaining payload is lower than a remaining latency threshold. The WTRU may determine that the channel access reconfiguration condition is satisfied based on determining that the first remaining time duration is lower than the remaining latency threshold.
  • CAPC configuration information may indicate association rules and/or conditions for (re)selecting CAPC and/or the related thresholds (e.g., thresholds for the remaining time regarding PSDB, thresholds for PSI) etc.
  • the association rules and/or conditions for (re)selecting CAPC may include a subset of CAPCs available based on a remaining time regarding PSDB or based on PDUs priority within a PDU set.
  • the association rules and/or conditions for (re)selecting CAPC may include a selection of a designated CAPC configuration for PDU set importance (PSI) exceeding a preconfigured threshold.
  • the association rules and/or conditions for (re)selecti ng CAPC may include a selection of a designated CAPC configuration for PSDB and/or the remaining time regarding PSDB going below a preconfigured threshold.
  • the association rules and/or conditions for (re)selecting CAPC may include a selection of a designated CAPC configuration for priority exceeding a preconfigured threshold.
  • CAPC configuration information may indicate the maximum number of consecutive COTs for a (e.g., each) CAPC.
  • a consecutive COT may be a COT that a WTRU (e.g., an XR WTRU) may acquire after a first COT on a specific set of resource blocks using COT reservation advantage (e.g., an action to increase the probability that a certain XR WTRU finishes channel sensing to reserve a COT on a specific set of resource blocks earlier than other WTRUs).
  • a WTRU e.g., an XR WTRU
  • the maximum number of consecutive COTs for a (e.g., each) CAPC may be configured by the network, for example, as a function of the PSDB of the UL traffic.
  • CAPC configuration information may include an indication to relax CAPC (e.g., lower CAPC) to provide a channel access priority to another WTRU.
  • the other (e.g., the second) WTRU may be a WTRU forming part of the XR experience (e.g., a haptics glove) which may be tethered to the primary (e.g., the first) WTRU.
  • the other WTRU may be any other WTRU being currently served by a source gNB.
  • CAPC configuration information may indicate channel sensing configurations (e.g., energy detection threshold and/or LBT type).
  • the WTRU may receive CAPC configuration, for example, from the network, and the CAPC configuration may include multiple parameters (e.g., multiple COT durations).
  • the WTRU may receive rules/conditions from the network on when to activate a parameter vs another (e.g., if PSDB of UL traffic is less than a preconfigured threshold, activate COT_duration1 , otherwise activate COT_duration2).
  • a channel access parameter (e.g., CAPC) may be selected.
  • a WTRU may be configured to determine channel access parameter(s) before transmission(s).
  • the WTRU may receive configuration information, for example, for a network.
  • the configuration information from the network may indicate to the WTRU to use default channel access parameter(s) (e.g., a default CAPC) for the transmission of PDU(s) or PDU set(s) until some conditions are met (e.g., conditions for changing those parameters).
  • the WTRU may be configured to flexibly adjust its channel access parameter(s) within a preconfigured set of values for the channel access parameter(s). For example, a WTRU may select a CAPC from a set of preconfigured CAPCs, for example, based on PDU set information while aligning with one or more CAPC selection association rules configured by a gNB.
  • a WTRU may determine which channel access parameters to use.
  • the WTRU may determine value(s) (e.g., channel access value(s)) of one or more channel access parameters (e.g., CAPC value, LBT type, etc.) and/or the number of COTs to use to access the channel and/or transmit the data in the buffer based on one or more of the following: the QoS associated with one or more PDUs/PDU sets in the buffer or the buffer status of the WTRU.
  • channel access value(s) e.g., channel access value(s)
  • channel access parameters e.g., CAPC value, LBT type, etc.
  • the WTRU may determine value(s) of the one or more channel access parameters and/or the number of COTs to use to access the channel and/or transmit the data in the buffer based on the QoS (e.g., PSDB, a remaining PSDB, PDU set delay deadline (PSDD), a nominal PSDB, PDU set error rate (PSER), the number of PDUs in the PDU set) associated with one or more PDUs/PDU sets in the buffer.
  • the WTRU may use the highest CAPC (e.g., CAPC 1) to access the channel.
  • the WTRU may then use subsequent COT(s) to transmit the lower priority data.
  • the WTRU may use the lower CAPC (e.g., CAPC 2) to access the channel.
  • the WTRU may then use the COT to transmit multiple PDU sets (e.g., both PDU set 1 and 2).
  • the WTRU may use the highest CAPC to access the channel.
  • the WTRU may use the COT to transmit the first PDU set (e.g., PDU set 1 only).
  • the WTRU may use lower CAPC (e.g., CAPC2) to access the channel.
  • the WTRU may then use the COT to transmit a first and second PDU set (e.g., both PDU set 1 and 2).
  • the WTRU may determine value(s) of the one or more channel access parameters and/or the number of COTs to use to access the channel and/or transmit the data in the buffer based on the buffer status (e.g., buffer size) of the WTRU.
  • the buffer size of the WTRU is smaller than a configured threshold, the WTRU may use one COT to transmit the whole buffer.
  • the WTRU may use the lowest CAPC to access the channel.
  • the WTRU may use multiple COTs (e.g., two COTs) to access the channel.
  • the WTRU may use the first CAPC (e.g., CAPC 1) to access the channel and transmit the first PDU set.
  • the WTRU may use the second CAPC (e.g., CAPC 2) to access the channel and transmit the second PDU set (e.g., PDU set 2).
  • FIG. 4 illustrates different (e.g., two) approaches for channel access parameter selection.
  • the WTRU may have two PDU sets (e.g., PDU set 1 associated with CAPC 1 and PDU set 2 associated with CAPC 2).
  • a first PDU set (e.g., PDU set 1) may have higher priority than a second PDU set (e.g., PDU set 2), and the value of CAPC 1 may be smaller than the value of CAPC 2 (e.g., lower CAPC value indicates/implies higher priority).
  • the WTRU may use two COTs to transmit the two PDU sets.
  • the WTRU may use CAPC 1 to access the channel to transmit PDU set 1.
  • the WTRU may then use CAPC 2 to access the channel to transmit PDU set 2.
  • the WTRU may use one COT to transmit one or more PDU sets (e.g., both PDU sets).
  • the WTRU may use CAPC 2 to access the channel to transmit PDU set 1 and/or 2 (e.g., both PDU set 1 and 2).
  • the WTRU may determine which approach to use based on the QoS of a PDU set (e.g., PDU set 1).
  • the WTRU may perform one or more of the following to determine channel access parameter(s) before transmission(s).
  • the WTRU may determine the channel access parameter(s) (e.g., CAPC) for a PDU set transmission.
  • the WTRU may determine the total number of COTs for a CAPC (e.g., the total number of required COTs for each CAPC) based on one or more of: a PDU set payload size, the number of resource blocks per channel, and other physical (PHY) layer information (e.g., channel state information (CSI) and modulation coding scheme (MCS)).
  • PHY physical
  • CSI channel state information
  • MCS modulation coding scheme
  • the WTRU may estimate sensing time (e.g., using type-1 channel access) for a configured CAPC (e.g., each of the configured CAPCs) deterministically (e.g., worstcase / average-case / best-case sensing time assuming highest / average / minimum contention window values).
  • the WTRU may estimate sensing time (e.g., using type-1 channel access) for a configured CAPC (e.g., each of the configured CAPCs) statistically (e.g., using historical records or channel occupancy status for estimating channel sensing time before successfully accessing an idle channel).
  • the WTRU may estimate the expected PDU set transmission time associated with a CAPC (e.g., the number of COTs x (sensing time + COT time)) for a configured CAPC (e.g., each of the configured CAPCs).
  • the WTRU may select a CAPC from the subset of configured CAPCs that meets the PSDB requirement (e.g., selecting a CAPC with the maximum difference between a PSDB and the expected PDU set transmission time to increase guard time due to uncertainty in unlicensed band; selecting a CAPC with a minimum priority as long as the PSDB requirement is met).
  • a WTRU may indicate the selected channel access parameter(s) (e.g., sending an indication of the selected channel access parameter(s)) before transmission(s).
  • the WTRU may indicate (e.g., explicitly indicate) the selected channel access parameter(s) (e.g., CAPC) via one or more of the following: uplink control information (UCI) transmission on physical uplink control channel (PUCCH), medium access control (MAC) control element (CE), radio resource control (RRC) signaling, or piggybacking this indication to the data transmitted on physical uplink shared channel (PUSCH).
  • UCI uplink control information
  • PUCCH physical uplink control channel
  • CE medium access control element
  • RRC radio resource control
  • the WTRU may sense the channel (e.g., for a number of sensing slots) according to the selected CAPC, for example, using type-1 channel access. If the channel is idle, the WTRU may transmit one or more PDUs
  • CAPC reselection and/or COT reservation advantage may be described in one or more examples herein.
  • a WTRU may be triggered for a reconfiguration of channel access parameter(s) (e.g., when a triggering condition is satisfied for the reconfiguration (e.g., a replacement of the current channel access parameteij).
  • the WTRU may increase the likelihood of meeting its QoS requirement(s) (e.g., PSDB requirement(s)), for example, by reconfiguring the channel access parameter(s) (e.g., changing CAPC) to reduce channel sensing time for acquiring a COT for transmission(s).
  • QoS requirement(s) e.g., PSDB requirement(s)
  • the WTRU may perform a channel access parameter reselection (e.g., CAPC reselection) procedure based on the status/value of one or more of: PSDB, a remaining latency threshold (e.g., a time offset associated with the PSDB), a PDU set priority, a WTRU buffer size, and/or a WTRU buffer size threshold or limitations.
  • a channel access reconfiguration criterion may be met in one or more examples herein.
  • the WTRU may determine a remaining payload to be transmitted (e.g., the size of the remaining payload to be transmitted).
  • the channel access parameter reselection procedure may be triggered based on one or more of the following: if the remaining time to meet the PSDB requirement is below a configured remaining latency threshold; if the remaining data size in the WTRU buffer is greater than a WTRU buffer size threshold; or an increase in the PDU set priority.
  • a channel access reconfiguration condition may be satisfied if a time duration for transmitting the remaining payload exceeds a latency threshold (e.g., a latency threshold associated with the PSDB).
  • the WTRU may determine a first channel access priority class (CAPC) value based on the configuration information. The WTRU may determine a remaining payload to be transmitted.
  • CAC channel access priority class
  • the WTRU may determine a first channel sensing time duration based on the first CAPC value.
  • the WTRU may determine, based on the first channel sensing time duration, that a first time duration for transmitting the remaining payload exceeds a latency threshold.
  • the WTRU may determine that the channel access reconfiguration condition is satisfied based on determining that the first time duration exceeds the latency threshold.
  • the WTRU may determine to select a second CAPC value based on the satisfaction of the channel access reconfiguration condition, and the second CAPC value may be associated with a higher priority than the first CAPC value.
  • the WTRU may determine a second channel sensing time duration based on the second CAPC value.
  • the WTRU may determine, based on the second channel sensing time duration, that a second time duration for transmitting the remaining payload does not exceed the latency threshold.
  • the WTRU may select the second CAPC value for the channel sensing based on the determination that the second time duration does not exceed the latency threshold.
  • the WTRU may reconfigure channel access parameter(s).
  • the WTRU may use one or more of the configuration information from the network (e.g., a contention window size, a COT for a (e.g., each) configured CAPC, and/or a remaining latency threshold) and from the application layer (e.g., the size of the remaining data and/or PSDB) to determine the number of consecutive COTs (e.g., the number of consecutive COTs required assuming one of the higher priority CAPCs) based on the remaining payload size and the maximum number of consecutive COTs for the higher priority CAPC.
  • the network e.g., a contention window size, a COT for a (e.g., each) configured CAPC, and/or a remaining latency threshold
  • the application layer e.g., the size of the remaining data and/or PSDB
  • the WTRU may indicate the reconfigured channel access parameter(s) (e.g., sending an indication of reconfigured channel access parameter(s)).
  • the channel access parameter reselection (e.g., a COT reservation advantage request or CAPC reconfiguration) may be indicated to the network using one or more of the following by the WTRU.
  • the WTRU may indicate the change (e.g., reconfiguration) of channel access parameter(s), for example, via short control signaling without LBT.
  • the WTRU may send a reservation indication.
  • the WTRU may append a COT reservation advantage request (e.g., piggybacked with data or sent separately in a consecutive transmission in the same COT), for example, via PUSCH.
  • the WTRU may indicate the channel access parameter reselection (e.g., reconfiguration) via one or more of the following: UCI on PUCCH, MAC CE, or RRC signaling.
  • the channel access parameter reselection indication may include one or more of the following: the number of consecutive COTs used (e.g., required) to meet PSDB requirement; the higher priority CAPC to be used; certain contention window value(s) to be used along with the selected CAPC (e.g., the high priority CAPC).
  • the WTRU may receive a response to a reservation indication (e.g., an explicit confirmation of COT reservation advantage on a set of resource blocks) from a base station (e.g., a gNB) via DCI on PDCCH and/or during the same COT in a subsequent DL transmission via COT sharing and/or via DCI on PDCCH.
  • a reservation indication e.g., an explicit confirmation of COT reservation advantage on a set of resource blocks
  • the WTRU may be permitted to perform this change (e.g., reconfig uration/reselection) autonomously, for example, without waiting for a network confirmation.
  • a COT reservation advantage may be given (e.g., assigned) to the WTRU in one or more of the following ways.
  • the base station e.g., a gNB
  • the WTRU may inform other WTRUs using configuration information about the reserved set of resource blocks (e.g., to force other WTRUs to choose the maximum contention window size for a type-1 channel access procedure for a period of time).
  • the WTRU may select a minimum contention window value based on the selection of the second CAPC value. For example, the WTRU may use the minimum contention window size for a type-1 channel access procedure for a limited number of consecutive COTs, for example, as indicated earlier in COT reservation advantage request (e.g., with/without changing CAPC).
  • the WTRU may start a type-1 channel access procedure for a consecutive COT, for example, during the current COT after a no-transmission gap.
  • the WTRU may change the current CAPC to a higher priority CAPC (e.g., replace the current CAPC with the higher priority CAPC).
  • the WTRU may sense the channel for a number of sensing slots, for example, according to the higher priority CAPC using type-1 channel access.
  • the WTRU may transmit the PDU(s) of the second PDU subset to the base station.
  • FIG. 3 illustrates an example for sensing at the end of COT for initiating consecutive COTs.
  • a WTRU may operate on unlicensed band(s) (e.g., NR-U).
  • the WTRU may have the capability to transmit and receive on licensed band(s) (e.g., NR).
  • licensed band(s) e.g., NR
  • unlicensed band(s) may be prone to channel access failure(s) and/or data transmission collision(s).
  • Retransmissions on more reliable licensed band resources may be performed (e.g., due to channel access failure(s) and/or data transmission collision(s) on unlicensed band(s)).
  • a WTRU may monitor PDCCH (e.g., NR PDCCH) and/or may trigger PDU retransmission(s) on NR for some urgent PDUs, for example, to meet XR-specific QoS requirements (e.g., PSDB or drift requirements) or overcome a possible lack of reliability of NR-U (e.g., due to channel access/transmission failures).
  • PDCCH e.g., NR PDCCH
  • PDU retransmission(s) on NR for some urgent PDUs, for example, to meet XR-specific QoS requirements (e.g., PSDB or drift requirements) or overcome a possible lack of reliability of NR-U (e.g., due to channel access/transmission failures).
  • XR-specific QoS requirements e.g., PSDB or drift requirements
  • a WTRU may receive configuration Information.
  • the WTRU may be configured to operate on NR-U and NR, for example, as primary and secondary band(s), respectively.
  • the WTRU may receive a first PDU subset for an uplink transmission from an application layer.
  • the WTRU may also receive PDU set information (e.g., the total payload size, the number of PDU subsets, PSDB, and/or the maximum drift threshold).
  • the WTRU may share PDU set information (e.g., some essential parts of PDU set information with a gNB) periodically (e.g., periodic update(s) of PDU’s priority, an update in the payload size, or the current status of meeting QoS requirements) or non-periodically (e.g., PSDB upon the PDU set arrival from the application layer).
  • PDU set information e.g., some essential parts of PDU set information with a gNB
  • periodically e.g., periodic update(s) of PDU’s priority, an update in the payload size, or the current status of meeting QoS requirements
  • non-periodically e.g., PSDB upon the PDU set arrival from the application layer
  • the WTRU may receive configuration information (e.g., from a gNB) that may include one or more of the following: a remaining latency threshold for triggering an NR retransmission procedure; the maximum number of transmission failures threshold (e.g., the maximum number of the total allowed channel access failures + NACKs) for triggering the NR retransmission procedure; a high priority CAPC configuration for indicating an NR retransmission request by WTRU on NR-U; or an NR search space configuration for NR PDCCH monitoring for potential NR retransmission(s).
  • configuration information e.g., from a gNB
  • a gNB may include one or more of the following: a remaining latency threshold for triggering an NR retransmission procedure; the maximum number of transmission failures threshold (e.g., the maximum number of the total allowed channel access failures + NACKs) for triggering the NR retransmission procedure; a high priority CAPC configuration for indicating an NR retransmission request
  • the WTRU may be monitoring the NR search space periodically (e.g., with a longer period than NR-U PDCCH monitoring since NR retransmissions are not frequent) or when triggered by the NR retransmission procedure (e.g., to save energy by not monitoring NR physical downlink control channel (PDCCH) unnecessarily).
  • NR-U PDCCH monitoring since NR retransmissions are not frequent
  • NR retransmission procedure e.g., to save energy by not monitoring NR physical downlink control channel (PDCCH) unnecessarily.
  • PDCCH physical downlink control channel
  • NR retransmission(s) may be triggered.
  • the WTRU may trigger retransmission(s) on NR to the gNB on NR (e.g., via SR) or NR-U (e.g., via short control packet(s) using the high priority CAPC) based on one or more of: PSDB, a remaining latency threshold, the number of NACKs (e.g., transmission failures), the number of channel access failures, and/or the maximum number of transmission failures threshold.
  • the WTRU may change the CAPC to a high priority CAPC.
  • the WTRU may indicate the retransmission(s) on NR to the gNB via an explicit indication on NR-U that may include: a) an indication of switching to an NR search space for NR PDCCH monitoring (e.g., switching may take place after a certain period of time (e.g., according to WTRU RF capability)), and b) an indication about some hybrid automatic repeat request (HARQ) process IDs that require urgent retransmission(s) on NR (e.g., since non-urgent retransmissions may take place on NR-U).
  • HARQ hybrid automatic repeat request
  • the WTRU may indicate retransmission(s) on NR to the gNB via an explicit indication on NR via scheduling request (SR) with the amount of needed radio resources for retransmissions.
  • the WTRU may begin monitoring NR PDCCH for a gNB confirmation of granting the NR retransmission(s) along with resources allocated for the retransmission(s) on NR (e.g., via DCI).
  • the WTRU may decrease NR PDCCH periodicity (e.g., since it may expect a resource allocation for the retransmission(s)).
  • a WTRU may be configured to transmit and/or receive on NR-U and NR.
  • the WTRU may be allocated resources (e.g., frequency resources) in the unlicensed (NR-U) and licensed (NR) band(s) for transmission/retransmission and reception of XR PDUs/PDU sets on both UL and DL.
  • the WTRU may be configured with a primary component carrier in an NR-U band and with one or more secondary component carriers in an NR band, in which case the (e.g., all) signaling and control plane data may be transmitted/received on the NR-U.
  • the primary component carrier may be in the NR band while one or more secondary component carriers may be configured in the NR-U band.
  • the WTRU may be served on both the NR-U and NR band by the same gNB.
  • the WTRU may be served by two or more gNBs where some of the gNBs serve on the NR-U band and the rest serve on the NR band.
  • the gNB may be connected via backhaul connection.
  • a WTRU may receive one or more PDUs of a PDU set and associated information.
  • the WTRU operating on an NR-U may receive, for example, from higher layers, one or more PDUs of a PDU set for UL transmission.
  • the WTRU may receive information related to the PDU set profile (e.g., the total payload size, the number of subsets of PDUs in the PDU set, PSDB, the priority importance of the PDU set, a threshold for the maximum tolerable drift between the arrival of PDUs of a PDU set, etc.).
  • the WTRU may obtain the information related to the PDU set profile as a packet header in the first PDU of the PDU set, for example, directly from the application layer.
  • the WTRU may receive information related to the PDU set profile (e.g., once) during a session (e.g., an XR session) establishment, in which case, the PDU set profile may be assumed to be the same for the (e.g., all) PDU sets in the XR session.
  • the WTRU may receive the information related to PDU set profile (e.g., periodically or aperiodically) when there is change in the application and/or XR session.
  • a WTRU may provide assistance information related to the PDU set profile.
  • a WTRU operating on an NR-U may provide information associated with the PDU set profile to the network, for example, for supporting retransmission(s) of urgent PDUs of the PDU set, which were initially transmitted in NR-U, in NR band.
  • the information regarding the PDU set profile may be sent to the network as assistance information and/or status information/indication, for example.
  • the WTRU may send to the network the information associated with multiple data flows associated with an application/service based on one or more of the following: during connectivity/session establishment and/or (re)configuration (e.g., during RRC connection, a PDU session, application session establishment and/or (re)configuration); when receiving higher layer/application information (e.g., when receiving an indication (e.g.
  • the WTRU may send information periodically or when a timer associated with sending of assistance information is set and/or expires.
  • a change in measurements and/or movements e.g., when pose/positioning measurements (e.g. location information, pose in 6D0F) are above/below pose threshold values; when detecting a change in time/timing attributes (e.g., the WTRU may send information periodically or when a timer associated with sending of assistance information is set and/or expires).
  • the WTRU may send to the network the information associated with the PDU set via access stratum (AS) layer signaling (e.g. RRC signaling and/or messages, MAC CE, or UCI) or Non-AS (NAS) layer signaling (e.g., PDU session related messages), for example.
  • AS access stratum
  • NAS Non-AS
  • a WTRU may receive configuration information for triggering transmission/retransmission on NR.
  • a WTRU operating on NR-U may switch the transmission/retransmission and/or reception of PDUs of a PDU set on NR, based on one or more parameters, threshold values and/or triggering conditions (e.g., received by the WTRU from the network as configuration information).
  • the configuration information received by WTRU may include one or more of the following parameters: a remaining time threshold (e.g., the WTRU may receive one or more delay threshold values corresponding to the remaining time of the PDU set for triggering retransmission(s) on NR); the number of transmission failures threshold (e.g., the WTRU operating in NR-U may receive one or more threshold values associated with the maximum number transmission failures to tolerate.
  • a remaining time threshold e.g., the WTRU may receive one or more delay threshold values corresponding to the remaining time of the PDU set for triggering retransmission(s) on NR
  • the number of transmission failures threshold e.g., the WTRU operating in NR-U may receive one or more threshold values associated with the maximum number transmission failures to tolerate.
  • the transmission failures may be due to channel access failures and/or NACKs triggered by decoding error(s)); high priority CAPC configuration (e.g., the WTRU operating on NR-U may receive a special CAPC configuration which is used to indicate higher priority and/or for triggering a request to perform retransmission(s) of one or more PDUs of a PDU set on NR; search space configuration for PDCCH monitoring (e.g., the WTRU operating on NR-U may receive one or more search space configurations which may be used after triggering retransmission request(s) on NR.
  • high priority CAPC configuration e.g., the WTRU operating on NR-U may receive a special CAPC configuration which is used to indicate higher priority and/or for triggering a request to perform retransmission(s) of one or more PDUs of a PDU set on NR
  • search space configuration for PDCCH monitoring e.g., the WTRU operating on NR-U may receive one or more
  • the WTRU may be configured to perform PDCCH monitoring on NR periodically with a longer periodicity, for example, to check if NW is requesting retransmission(s) on NR).
  • the WTRU operating on NR-U may receive the configuration information via AS layer signaling (e.g., RRC signaling/messages, MAC CE, or DCI) or Non-AS (NAS) layer signaling (e.g., PDU session related messages), for example.
  • AS layer signaling e.g., RRC signaling/messages, MAC CE, or DCI
  • NAS Non-AS
  • a WTRU may trigger a request for retransmission of PDUs/PDU-sets on NR.
  • the WTRU operating on NR-U may trigger a request for retransmission(s) of one or more PDUs of a PDU set on NR licensed band, for example, upon failures of transmissions/retransmissions.
  • the WTRU may trigger the request for retransmission(s) on NR when one or more of the following conditions are fulfilled/satisfied: when the number of failed transmissions on NR-U band exceeds the configured threshold related to the maximum number of transmission/retransmission failures as results of channel access failures and/or NACKs triggered by decoding error(s) at the NW; when the remaining time for the PDU set is less than the configured threshold value related to the remaining time.
  • the WTRU operating on NR-U may send a scheduling request (SR) on an NR band requesting for resources on the NR band for retransmission(s) of the PDUs/PDU sets which the WTRU has repeatedly failed to transmit/retransmit on NR-U.
  • the WTRU operating on NR-U may trigger a request for resources on an NR band for retransmission(s) by changing the CAPC to a higher priority CAPC as configured by the NW.
  • the WTRU operating on NR-U may send an explicit indication to the NW indicating a periodic switch for PDCCH monitoring on an NR band.
  • the WTRU may perform PDCCH monitoring and retransmission on an NR band.
  • the WTRU operating on NR-U may trigger a request for resources on the NR band for retransmission(s) and begin PDCCH monitoring on NR for a possible resource grant provided by the NW (e.g., via DCI).
  • the WTRU operating on NR-U may not send a request for resources on NR band and may periodically perform PDCCH monitoring on the NR band for a possible indication (e.g., via DCI) from NW to perform retransmission(s) of PDUs/PDU sets on NR resources.
  • the WTRU operating on NR-U may briefly switch to the NR band and/or use the NR resource(s) to retransmit the PDUs/PDU sets which repeatedly failed to be transmitted on the NR-U band.
  • a WTRU e.g., an XR WTRU
  • a WTRU may be configured to operate in unlicensed band(s) (e.g., NR-U).
  • the WTRU may use (e.g., require) a long COT, or multiple consecutive COTs, for meeting QoS requirements (e.g., PSDB) of certain types of traffic (e.g., XR video) without incurring large channel sensing delays.
  • QoS requirements e.g., PSDB
  • the WTRU may be enabled to meet its QoS requirements (e.g., PSDB requirement) on NR-U by one or more of the following: configuring multiple CAPCs for the same XR traffic type (e.g., to enable shorter channel sensing time) before acquiring COT(s) for uplink transmission(s) as remaining latency decreases; enabling the WTRU to reserve a COT on a specific set of resource blocks by decreasing its channel sensing time without violating unlicensed band regulations (e.g., using a minimum contention window value or sending a COT reservation indication to a gNB).
  • QoS requirements e.g., PSDB requirement
  • a WTRU may receive configuration information, including one or more of the following: a subset of channel access parameters (e.g., CAPC) values associated with XR data (e.g., CAPC 1 and CAPC 2 for XR video data; CAPC 1 may have, for example, lower priority / longer expected channel sensing time / longer COT) than CAPC 2); default channel access parameters (e.g., CAPC) and/or conditions for channel access parameters (e.g., CAPC) reselection (e.g., a remaining latency threshold and/or a buffer size threshold); a maximum number of consecutive COTs for a respective channel access parameter value (e.g., CAPC).
  • CAPC channel access parameters
  • the WTRU may receive one or more PDUs of PDU set(s) from application layer(s).
  • the WTRU may determine the information (e.g., one or more PDU parameters) associated with the PDU(s) (e.g., the total payload size, the number of PDU subsets, and/or PSDB) based on the received PDU(s).
  • the WTRU may determine that a channel access parameter associated with the PDU is to be selected, for example, based on the information associated with the PDU(s).
  • the WTRU may trigger channel access parameter (e.g., CAPC) (re)selection for one or more COTs based on one or more of: PSDB, a remaining latency threshold, a PDU set priority, a WTRU buffer size, and a WTRU buffer size threshold or limitations.
  • channel access parameter e.g., CAPC
  • the WTRU may determine (e.g., select) a channel access parameter (e.g., CAPC) to be used for the transmission of the one or more PDUs of the PDU set(s).
  • a channel access parameter e.g., CAPC
  • the WTRU may determine a number of consecutive COTs to be used (e.g., the number of consecutive COTs that may be required assuming a configured and WTRU-selected higher priority CAPC), for example, based on the remaining payload size and the maximum number of consecutive COTs for the higher priority CAPC.
  • the WTRU may transmit a reservation request to reserve COT(s) (e.g., a COT reservation advantage request), including one or more of: the determined number of consecutive COTs (e.g., as required to meet PSDB requirement(s) associated with PDUs coming from application layer(s)); the CAPC to be used (e.g., the configured and the WTRU-selected higher priority CAPC to be used); or certain contention window values to be used (e.g., along with the selected high priority CAPC).
  • a COT reservation advantage request including one or more of: the determined number of consecutive COTs (e.g., as required to meet PSDB requirement(s) associated with PDUs coming from application layer(s)); the CAPC to be used (e.g., the configured and the WTRU-selected higher priority CAPC to be used); or certain contention window values to be used (e.g., along with the selected high priority CAPC).
  • the WTRU may receive a confirmation or an approval of the reservation request for a reservation advantage on a set of resource blocks (e.g., the COT reservation advantage on a set of resource blocks) from a base station (e.g., a gNB), for example, during the same COT in subsequent DL transmission via COT sharing.
  • the WTRU may update the current CAPC to a higher priority CAPC.
  • the WTRU may initiate a COT using the determined channel access parameter (e.g., CAPC).
  • the WTRU may transmit the one or more PDUs in the WTRU-initiated COT.
  • FIG. 3 illustrates an example for sensing at the end of COT for initiating consecutive COTs.
  • retransmission(s) may be performed on licensed (e.g., licensed band(s)), for example, for unlicensed operation reliability enhancement.
  • a WTRU e.g., an XR WTRU
  • the WTRU may have the capability to transmit and receive on licensed band(s) (e.g., NR).
  • licensed band(s) e.g., NR
  • unlicensed band(s) may be prone to channel access failures and/or data transmission collisions.
  • Retransmission(s) (e.g., of XR data) may be performed on licensed band resources (e.g., licensed band resources that are more reliable than unlicensed band resources).
  • a WTRU may monitor NR PDCCH and/or may trigger PDU retransmission(s) on NR for some PDUs, for example, to meet QoS requirements or overcome lack of reliability of NR-U due to channel access/transmission failures.
  • the WTRU may be configured to operate on both NR-U and NR as primary and secondary bands, respectively.
  • the WTRU may receive a first PDU subset for uplink transmission(s) from an application layer.
  • the WTRU may receive PDU set information, (e.g., the total payload size, the number of PDU subsets, PSDB, and the maximum drift threshold).
  • the WTRU may receive configuration information from a base station (e.g., a gNB) that may include one or more of the following: a remaining latency threshold for triggering an NR retransmission procedure; the maximum number of transmission failures threshold (e.g., the maximum number of total allowed channel access failures + NACKs) for triggering the NR retransmission procedure; high priority CAPC configuration for indicating NR retransmission request(s) by the WTRU on NR-U; NR search space configuration for NR PDCCH monitoring for potential NR retransmission(s).
  • a base station e.g., a gNB
  • a remaining latency threshold for triggering an NR retransmission procedure
  • the maximum number of transmission failures threshold e.g., the maximum number of total allowed channel access failures + NACKs
  • high priority CAPC configuration for indicating NR retransmission request(s) by the WTRU on NR-U
  • NR search space configuration for NR PDC
  • the WTRU may trigger retransmission(s) on NR to a gNB on NR (e.g., via SR) or NR-U (e.g., via short control packet(s) using a high priority CAPC) based on one or more of: PSDB, a remaining latency threshold, the number of NACKs (e.g., transmission failures), the number of channel access failures, and/or a maximum number of transmission failures threshold.
  • the WTRU may begin monitoring NR PDCCH for a gNB confirmation of granting NR retransmission resource(s) (e.g., via DCI).
  • the processes described above may be implemented in a computer program, software, and/or firmware incorporated in a computer-readable medium for execution by a computer and/or processor.
  • Examples of computer-readable media include, but are not limited to, electronic signals (transmitted over wired and/or wireless connections) and/or computer-readable storage media.
  • Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and/or optical media such as compact disc (CD)-ROM disks, and/or digital versatile disks (DVDs).
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and/or any host computer.

Landscapes

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

Abstract

Une unité d'émission/réception sans fil (WTRU) peut recevoir des informations de configuration indiquant une condition de reconfiguration d'accès à un canal. La WTRU peut déterminer un paramètre d'unité de données de protocole (PDU) associé à une PDU. La WTRU peut déterminer, sur la base du paramètre de PDU et de la condition de reconfiguration d'accès à un canal, qu'un paramètre d'accès à un canal de multiples paramètres d'accès à un canal doit être utilisé pour une détection de canal. La WTRU peut effectuer la détection de canal à l'aide du paramètre d'accès à un canal. La WTRU peut transmettre la PDU sur la base de la détection de canal. Dans des exemples, la WTRU peut envoyer une indication de réservation associée à un ou plusieurs temps d'occupation de canal (COT). L'indication de réservation peut indiquer que la WTRU a un avantage de détection de canal associé auxdits COT. La WTRU peut effectuer la détection de canal pour acquérir lesdits COT.
PCT/US2025/027310 2024-05-06 2025-05-01 Réalité étendue dans un spectre sans licence Pending WO2025235293A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463643213P 2024-05-06 2024-05-06
US63/643,213 2024-05-06

Publications (1)

Publication Number Publication Date
WO2025235293A1 true WO2025235293A1 (fr) 2025-11-13

Family

ID=95899576

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2025/027310 Pending WO2025235293A1 (fr) 2024-05-06 2025-05-01 Réalité étendue dans un spectre sans licence

Country Status (1)

Country Link
WO (1) WO2025235293A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024023667A1 (fr) * 2022-07-25 2024-02-01 Lenovo (Singapore) Pte. Ltd. Priorité d'accès à un canal pour liaison latérale

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024023667A1 (fr) * 2022-07-25 2024-02-01 Lenovo (Singapore) Pte. Ltd. Priorité d'accès à un canal pour liaison latérale

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL: "Channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum", vol. RAN WG1, no. Toulouse, France; 20220822 - 20220826, 12 August 2022 (2022-08-12), XP052273816, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_110/Docs/R1-2205886.zip R1-2205886.docx> [retrieved on 20220812] *

Similar Documents

Publication Publication Date Title
US12362896B2 (en) Receiver bandwidth adaptation
JP7605875B2 (ja) 低減された待ち時間システムにおけるタイミングアドバンスおよび処理能力
CN112753194B (zh) 无线发射/接收单元和在其中实施的方法
US20200053835A1 (en) Uu interface enhancement for nr v2x
US20230309161A1 (en) Nr relays methods for supporting latency reduction for sl relays
US20250168824A1 (en) Wireless resource allocation schemes in vehicle-to-everything (v2x) communication
US20250287402A1 (en) Fbe channel access in sidelink unlicensed
WO2024010750A1 (fr) Procédés, architectures, appareils et systèmes de régulation de congestion dans un relais de liaison latérale à trajets multiples
WO2025235293A1 (fr) Réalité étendue dans un spectre sans licence
US20240276547A1 (en) Rx device determines how to feedback psfch
WO2024211424A1 (fr) Procédés et appareils pour utiliser des ressources réservées de liaison latérale pour déterminer un ou plusieurs ensembles de rb pour une transmission ssb
WO2024173313A1 (fr) Déclenchement d&#39;attribution de ressources basé sur uu
WO2024211426A1 (fr) Procédés et appareils pour une wtru d&#39;émission pour identifier une wtru de synchronisation et demander une émission s-ssb sur un ou plusieurs ensembles de rb
EP4666791A1 (fr) Déclenchement d&#39;attribution de ressources basé sur uu
WO2024173566A1 (fr) Procédé et appareil de transmission d&#39;une demande de planification sur la base d&#39;une condition
WO2024030625A1 (fr) Sélection de porteuse basée sur une mesure dans une liaison latérale à porteuses multiples
WO2024173455A1 (fr) Procédés et appareils de rapport de retransmissions autonomes
WO2024173454A1 (fr) Procédés et appareils pour la priorisation de retour d&#39;informations de demande de répétition automatique hybride pour autorisation configurée de liaison latérale
WO2024211428A1 (fr) Procédés et appareils pour une wtru de synchronisation pour indiquer des ensembles rb utilisés aux fins d&#39;une transmission ssb
WO2025174965A1 (fr) Systèmes, procédés et dispositifs associés au délestage de gnb de planification sl
WO2024173315A1 (fr) Détermination de données de bloc de transport
WO2025151693A1 (fr) Réalisation de mesures dans des réseaux sans fil utilisant un relais
WO2025034869A1 (fr) Détermination d&#39;une porteuse pour transmettre un psfch à un pscch/pssch de rétroaction
WO2024072926A1 (fr) Transmissions de signal de commande court
WO2024173463A1 (fr) Canal psfch de rétroaction pour une retransmission