Methods, architectures, apparatuses and systems to address scheduling restrictions during measurements

Abstract

Procedures, methods, architectures, apparatuses, systems, devices, and computer program products related to handling scheduling restrictions during measurements are described. For example, a WTRU may be configured to receive a measurement indication before the start of some measurement gap (MG) occasions (MGOs) in a preconfigured MG configuration. The WTRU may determine the changes to apply to the MGOs based on the received indication and / or characteristics of data in its buffer.

Description

METHODS, ARCHITECTURES, APPARATUSES AND SYSTEMS TO ADDRESS SCHEDULING RESTRICTIONS DURING MEASUREMENTSCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 552,355, filed February 12, 2024. The contents of this earlier filed application is incorporated herein by reference in its entirety.FIELD

[0002] The present disclosure is generally directed to the fields of communications, software and encoding, including, for example, to methods, architectures, apparatuses, systems related to addressing scheduling restrictions during measurements.BACKGROUND

[0003] The term extended Reality (XR) is an umbrella term referring to different types of immersive experiences, such as Virtual Reality (VR), Augmented Reality (AR) and Mixed Reality (MR), as well as the realities interpolated among them. Virtual Reality (VR) is a rendered version of a delivered visual and audio scene. The rendering is designed to mimic the visual and audio sensory stimuli of the real world as naturally as possible to an observer or user as they move within the limits defined by the application. Augmented Reality (AR) is when a user is provided with additional information or artificially generated objects, items, or content overlaid upon their current environment. Mixed Reality (MR) is an advanced form of AR where some virtual elements are inserted into a real physical scene with the intent to provide the illusion that these elements are part of the real scene. XR may include all of these real-and-virtual combined environments and human-machine interactions generated by computer technology and wearables.SUMMARY

[0004] According to certain embodiments, a WTRU may receive configuration information that may include one or more measurement gap (MG) configurations indicating parameters associated with each MG configuration including any of priority, periodicity of MGOs, and / or MGO length. The configuration information may also include or indicate a time offset for (e.g., associated with) receiving an indication (e.g., in DCI) on whether to skip measurements in an MGO (e.g., time window may be a minimum time in units of slots before the start of an MGO). The WTRU may receive, e.g., from higher layer(s), one or more PDUs. The WTRU may receive an indication (e.g.,in DCI) indicating to skip measurements. If the indication to skip measurements is received before the time offset of at least one MGO (e.g., the first MGO), and / or a second MGO overlaps or occurs consecutively after the first MGO, the WTRU may determine to skip measurements in at least one MGO based on the received indication and / or the priority values of the MG configurations associated with the MGOs.

[0005] Certain embodiments may include a method that may be implemented by a wireless transmit / receive unit (WTRU). The method may include receiving configuration information indicating (1) one or more measurement gap configurations respectively associated with at least one measurement gap occasion and / or (2) a time offset associated with receiving an indication of whether to skip measurements in one or more of the at least one measurement gap occasion. The method may include receiving the indication to skip measurements in the one or more of the at least one measurement gap occasion and, based on the indication to skip measurements being received before the time offset, determining to skip measurements in the one or more of the at least one measurement gap occasion based at least on a priority associated with the one or more measurement gap configurations.BRIEF DESCRIPTION OF THE DRAWINGS

[0006] A more detailed understanding may be had from the detailed description below, given by way of example in conjunction with drawings appended hereto. Figures in such drawings, like the detailed description, are examples. As such, the Figures (FIGs.) and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals ("ref.") in the FIGs. indicate like elements, and wherein:

[0007] FIG. 1 A is a system diagram illustrating an example communications system;

[0008] FIG. IB is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A;

[0009] FIG. 1C 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;

[0010] FIG. ID is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1 A;

[0011] FIG. 2 illustrates an example diagram depicting the determination of MG usage based on dynamic DL indication, according to some embodiments;

[0012] FIG. 3 illustrates an example diagram depicting the determination of measurements and / or data transmissions in a multi-part MG occasion, according to some embodiments;

[0013] FIG. 4 illustrates an example diagram depicting the selection of a preconfigured MI / MG patter, according to an embodiment;

[0014] FIG. 5A illustrates a diagram, according to some embodiments;

[0015] FIG. 5B illustrates a diagram, according to some embodiments;

[0016] FIG. 5C illustrates a diagram according to some embodiments;

[0017] FIG. 6 illustrates a flow diagram of a method, according to some embodiments; and

[0018] FIG. 7 illustrates a flow diagram of a method, according to some embodiments.DETAILED DESCRIPTION

[0019] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described, disclosed or otherwise provided explicitly, implicitly and / or inherently (collectively "provided") herein. Although various embodiments are described and / or claimed herein in which an apparatus, system, device, etc. and / or any element thereof carries out an operation, process, algorithm, function, etc. and / or any portion thereof, it is to be understood that any embodiments described and / or claimed herein assume that any apparatus, system, device, etc. and / or any element thereof is configured to carry out any operation, process, algorithm, function, etc. and / or any portion thereof.

[0020] The methods, apparatuses and systems provided herein are well-suited for communications involving both wired and wireless networks. An overview of various types of wireless devices and infrastructure is provided with respect to FIGs. 1A-1D, where various elements of the network may utilize, perform, be arranged in accordance with and / or be adapted and / or configured for the methods, apparatuses and systems provided herein.

[0021] FIG. 1A is a system 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. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access(TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), singlecarrier FDMA (SC-FDMA), zero-tail (ZT) unique-word (UW) discreet Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block- filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0022] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113, a core network (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. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a "station" and / or a "STA", may be configured to transmit and / or receive wireless signals and may include (or be) 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. Any of the WTRUs 102a, 102b, 102c and 102d, or any other WTRU mentioned or described herein, may be interchangeably referred to as a UE.

[0023] 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, e.g., to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or the networks 112. By way of example, the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a Home Node-B (HNB), a Home eNode-B (HeNB), a gNode-B (gNB), a NR Node-B (NR NB), 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.

[0024] 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 radionetwork controller (RNC), relay nodes, etc. 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. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in an embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each or any sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

[0025] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0026] More specifically, as noted above, 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. For example, 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 116 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and / or High-Speed Uplink Packet Access (HSUPA).

[0027] In an embodiment, 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).

[0028] In an embodiment, 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).

[0029] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, 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).

[0030] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, 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.

[0031] 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. In an embodiment, 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). In an embodiment, 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). In an embodiment, 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 any of a small cell, picocell or femtocell. As shown in FIG. 1 A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106 / 115.

[0032] 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. 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. Although not shown in FIG. 1 A, it will be appreciated that 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. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing an NR radio technology, the CN 106 / 115 may also be in communication with anotherRAN (not shown) employing any of a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi radio technology.

[0033] 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 other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). 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. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 114 or a different RAT.

[0034] 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). For example, 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.

[0035] FIG. IB is a system diagram illustrating an example WTRU 102. As shown in FIG. IB, 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 elements / peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0036] 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. IB depicts the processor 118 and the transceiver 120 as separate components, it willbe appreciated that the processor 118 and the transceiver 120 may be integrated together, e.g., in an electronic package or chip.

[0037] 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. For example, in an embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In an embodiment, 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.

[0038] Although the transmit / receive element 122 is depicted in FIG. IB as a single element, the WTRU 102 may include any number of transmit / receive elements 122. For example, the WTRU 102 may employ MIMO technology. Thus, in an 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.

[0039] 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. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, 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.

[0040] 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. In addition, 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), readonly 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. In other embodiments, 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).

[0041] 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 source134 may be any suitable device for powering the WTRU 102. For example, 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.

[0042] 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. In addition to, or in lieu of, the information from the GPS chipset 136, 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 location-determination method while remaining consistent with an embodiment.

[0043] The processor 118 may further be coupled to other elements / peripherals 138, which may include one or more software and / or hardware modules / units that provide additional features, functionality and / or wired or wireless connectivity. For example, the elements / peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (e.g., for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, and the like. The elements / 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.

[0044] 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 uplink (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). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the uplink (e.g., for transmission) or the downlink (e.g., for reception)).

[0045] FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0046] 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. In an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0047] Each of the eNode-Bs 160a, 160b, and 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 uplink (UL) and / or downlink (DL), and the like. As shown in FIG. 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0048] The CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any one of these elements may be owned and / or operated by an entity other than the CN operator.

[0049] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an SI interface and may serve as a control node. For example, 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.

[0050] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via the SI 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.

[0051] 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.

[0052] The CN 106 may facilitate communications with other networks. For example, 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. For example, 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. In addition, 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.

[0053] Although the WTRU is described in FIGs. 1A-1D 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.

[0054] In representative embodiments, the other network 112 may be a WLAN.

[0055] 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 into 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). In certain representative embodiments, the DLS may use an 802. l ie DLS or an 802.1 Iz 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.

[0056] When using the 802.1 lac infrastructure mode of operation or a similar mode of operations, 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 bythe STAs to establish a connection with the AP. In certain representative embodiments, Carrier sense multiple access with collision avoidance (CSMA / CA) may be implemented, for example in in 802.11 systems. For CSMA / CA, 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.

[0057] 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 nonadj acent 20 MHz channel to form a 40 MHz wide channel.

[0058] Very high throughput (VHT) STAs may support 20 MHz, 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. For the 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. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above-described operation for the 80+80 configuration may be reversed, and the combined data may be sent to a medium access control (MAC) layer, entity, etc.

[0059] Sub 1 GHz modes of operation are supported by 802.1 laf and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.1 laf and 802.1 lah relative to those used in802.1 In, and 802.1 lac. 802.1 laf supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802.1 lah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment,802.1 lah may support meter type control / machine-type communications (MTC), 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).

[0060] WLAN systems, which may support multiple channels, and channel bandwidths, such as802.1 In, 802.1 lac, 802.1 laf, and 802.1 lah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channelmay be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.1 lah, 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.

[0061] In the United States, the available frequency bands, which may be used by 802.1 lah, 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.1 lah is 6 MHz to 26 MHz depending on the country code.

[0062] FIG. ID is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0063] 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. In an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 180b may utilize beamforming to transmit signals to and / or receive signals from the WTRUs 102a, 102b, 102c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, 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. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0064] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or differentportions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., including a varying number of OFDM symbols and / or lasting varying lengths of absolute time).

[0065] 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. In the 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). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non- standalone configuration 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. For example, 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. In the non- standalone configuration, 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.

[0066] 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 functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and the like. As shown in FIG. ID, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0067] The CN 115 shown in FIG. ID may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and at least one Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0068] 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. For example, 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 protocol data unit (PDU) sessions with differentrequirements), 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, e.g., to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and / or the like. The AMF 162 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.

[0069] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP -based, non-IP based, Ethernet-based, and the like.

[0070] 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, e.g., 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 multihomed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

[0071] The CN 115 may facilitate communications with other networks. For example, the CN 115 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 115 and the PSTN 108. In addition, the CN 115 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. In an embodiment, 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.

[0072] In view of FIGs. 1 A-1D, and the corresponding description of FIGs. 1 A-1D, one or more, or all, of the functions described herein with regard to any of: WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a- b, SMFs 183a-b, DNs 185a-b, and / or any other element(s) / device(s) described herein, may be performed by one or more emulation elements / 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. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

[0073] 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. For example, 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.

[0074] 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. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0075] Embodiments disclosed herein are representative and do not limit the applicability of the apparatus, procedures, functions and / or methods to any particular wireless technology, any particular communication technology and / or other technologies. The term network in this disclosure may generally refer to one or more base stations or gNBs or other network entity which in turn may be associated with one or more Transmission / Reception Points (TRPs), or to any other node in the radio access network.

[0076] It is noted that, throughout example embodiments described herein, the terms “serving base station”, “base station”, “gNB”, collectively “gNB” may be used interchangeably to designate any network element such as, e.g., a network element acting as a serving base station. Embodiments described herein are not limited to gNBs and are applicable to any other type of base stations.

[0077] The term extended Reality (XR) is an umbrella term for different types of immersive experiences including, but not limited to, Virtual Reality (VR), Augmented Reality (AR) and Mixed Reality (MR) and the realities interpolated among them. Virtual Reality (VR) is a rendered version of a delivered visual and audio scene. The rendering is designed to mimic the visual (e.g., stereoscopic 3D) and audio sensory stimuli of the real world as naturally as possible to an observer or user as they move within the limits defined by the application. Augmented Reality (AR) is when a user is provided with additional information or artificially generated objects and / or items or content overlaid upon their current environment. Mixed Reality (MR) is an advanced form of AR where some virtual elements are inserted into the physical scene with the intent to provide the illusion that these elements are part of the real scene. XR may include real-and-virtual combined environments and human-machine interactions generated by computer technology and wearables.

[0078] The notion of immersion in the context of XR applications and / or services refers to the sense of being surrounded by the virtual environment as well as providing the feeling of being physically and spatially located in the virtual environment. The levels of virtuality may range from partial sensory inputs to fully immersive multi-sensory inputs leading to a virtual reality practically indiscernible from actual reality.

[0079] In example embodiments described herein, a UE or WTRU may correspond to any XR device and / or node which may come in variety of form factors. For example, a UE or WTRU (e.g., XR UE) may include, but is not limited to, one or more of the following: Head Mounted Displays (HMD), optical see-through glasses and camera see-through HMDs for AR and MR, mobile devices with positional tracking and camera, wearables, haptic gloves, haptic body suit, haptic shoes, etc. In addition to the above, several different types of XR UE may be envisioned based on XR device functions, for example, as display, camera, sensors, sensor processing, wireless connectivity, XR / Media processing and power supply, to be provided by one or more devices, wearables, actuators, controllers and / or accessories. One or more device, nodes and / or UEs may be grouped into a collaborative XR group for supporting any of XR applications, experience and / or services.

[0080] In XR services and applications, the traffic may include data and / or protocol data units (PDUs) that may be associated with an application data unit (ADU), PDU set or data burst. In an example, the PDUs belonging to a PDU set may be associated with different segments or components of an application frame, video frame or a video slice. A data burst may include one or more PDU sets that may be transmitted and / or received over a time window. For example, a number of PDUs in a PDU set or data burst transmitted in uplink (UL) and / or received in downlink (DL) may be dependent on the type of the media frame (e.g., 3D video frame, audio frame).

[0081] In legacy 3 GPP Rel-15 to Rel-18 procedures, the UE or WTRU can be configured with measurement objects (e.g., MeasObjectNR) for intra- and inter-frequency measurements. For example, the field ReferenceSignalConfig (e.g., in RRC) within each measObjectNR can configure the measurements for Synchronization Signal Block (SSB), channel state information reference signal (CSI-RS), or both.

[0082] Measurements can be gap assisted (e.g., for FR1 / FR2 inter-frequency measurements) or non-gap assisted (e.g., for FR2 intra-frequency measurements). Both types of measurements may impose scheduling restrictions, where the UE or WTRU may not be scheduled or perform transmissions / receptions on other signals / channels other than measurements.

[0083] The measurement gaps (MGs) may be needed and semi-statically configured in the WTRU by the network (e.g., gNB) when the WTRU does not have the capability to measure the target carrier frequency while simultaneously transmitting / receiving data signals / channels on the serving cell. The legacy specification (e.g., 3GPP TS 38.133) supports MG lengths (MGL) of 1.5, 3, 3.5, 4, 5.5, 6 ms with measurement gap repetition periodicities (MGRP) of 20, 40, 80, and 160 ms. Additionally, 1 data symbol before and after each consecutive SSBs within SSB measurement timing window configuration (SMTC) may be restricted from scheduling (e.g., perform transmissions or receptions on PDCCH / PxSCH).

[0084] According to legacy specifications, during scheduling restrictions (e.g., with / without MGs) due to measurements, the medium access control (MAC) entity in the UE: does not perform the transmission of hybrid automatic repeat request (HARQ) feedback, SR, and CSI; does not perform the transmission of sounding reference signal (SRS); does not transmit on uplink shared channel (UL-SCH) (except for Msg3) or not receive on downlink shared channel (DL-SCH); and does not monitor the physical downlink control channel (PDCCH) except for the case if the WTRU is waiting for Msg2 or Msg4 during random access (RA) procedure.

[0085] In typical XR applications, the WTRU transmits XR traffic that includes one or more PDUs / PDU sets in UL (e.g., pose, gesture, video data) and / or receives XR traffic in DL (e.g., video, audio, haptics). Such traffic may be transmitted and / or received periodically or aperiodically in one or more data flows (e.g., QoS flows). During UL transmissions, XR traffic may arrive from the application layer at the WTRU and / or from different devices, terminals and / or UEs (e.g., via sidelink) at different time instances. Such XR traffic may be characterized by different traffic attributes such as variable payload sizes per PDU set, variable number of PDUs per PDU set, variable per-PDU / PDU set level priority / importance and different levels of inter-dependencies between PDUs / PDUs sets in one or more flows. Such XR traffic (e.g., PDU / PDU sets) received by the WTRU from higher layers or other devices / terminals may also experience different delays,jitter, data rate and loss rate. To ensure that the QoS (e.g., PDU set delay bound (PSDB), PDU set error rate (PSER), PDU set integrated handling indication (PSIHI)) is met, it may be important for any procedures during data transmissions including prioritization, multiplexing, scheduling and / or resource allocation to be done on a timely basis considering the PDU set attributes. To ensure QoE / QoS, the PDUs within a PDU set or different PDU sets generated at the transmitting side of the application are expected to be delivered to the receiving side of the application within the data requirements.

[0086] In XR traffic, the different PDUs or PDU sets may contribute to different user experiences. As such, the PDUs / PDU sets may be associated with different importance and / or priority values from the application layer perspective. It is also possible that the one or more PDU sets transmitted sequentially in time domain may be inter-dependent with each other in different ways. In other words, unlike the existing QoS framework where all PDUs / PDU sets in a flow are provided with the same forwarding treatment by assuming equal importance / priority, the PDUs / PDU sets in a data burst for XR traffic may need to be differentiated and handled differently QoS-wise at the lower layers, irrespective of whether the PDUs / PDU sets are in one or more QoS flows, during scheduling and transmissions in UL and / or DL.

[0087] The inter-dependencies between the PDUs / PDU sets in a single or multiple QoS flows may result in different challenges for meeting the QoS at PDU set level during transmissions.

[0088] For ensuring proper connectivity between the WTRU and base station over the radio link, the WTRU may perform measurements of different measurement objects (e.g., Synchronization Signal Blocks (SSBs), CSI-RS, PRS) and transmit the measurement reports on timely basis. The WTRU may be configured with MGs and / or scheduling restrictions to allow dedicated time and / or frequency resources for (e.g., only for) performing measurements. Any interruptions during measurements may adversely impact the procedures associated with connectivity, coverage and mobility including radio link maintenance, link adaptation, beam management, etc. Such interruptions may consequently impact other user-plane procedures, such as QoS enforcement and scheduling.

[0089] In this regard, solutions that ensure proper handling of XR data and / or traffic for meeting QoS (e.g., meeting PDU set QoS during UL / DL transmissions) while minimizing any impacts on measurements (e.g. not compromising accuracy of measurements) are currently unknown or unavailable.

[0090] A WTRU supporting an XR service and / or experience may be receiving data units (e.g., PDUs, PDU sets or data bursts) from higher layers or different devices, such as AR glasses and haptics gloves (e.g., via SL). Such data units, which may have variable payload sizes, differentperiodicity and / or different inter-dependencies may be further processed and transmitted by the WTRU in the UL or received in DL. To avoid latency during scheduling of resources and transmissions of the data units, the WTRU may be configured with configured grants (CG). Alternatively, the WTRU may be allocated with dynamic UL grants. Both of such resources may be impacted when the WTRU is expected to perform measurements with or without MGs.

[0091] In the legacy 3 GPP Rel-15 to Rel-18 procedures, the MGs / restrictions are semi-statically configured via RRC signaling. Also, in legacy procedures, the WTRU prioritizes measurements over data transmissions. Rel-19 enhancements for XR include enabling transmission / reception in gaps / restrictions that are caused by radio resource management (RRM) measurements (from interfrequency RRM measurement gaps, or intra-frequency measurements, or other scheduling restrictions, etc.).

[0092] The semi-statically configured measurement gaps / restrictions may impact (e.g., severely impact) the QoS achievable for XR data / traffic. The impact may be more profound when high periodicity MGs / restrictions are configured. In such scenarios, the XR data may be buffered and delayed at the WTRU (in UL) or at the NW (in DL), and transmitted only after the MG / restriction duration. Additionally, the legacy periodicity values associated with MG may not be aligned with the non-integer periodicities of XR traffic (e.g., periodicities of 16.66ms for traffic with 60fps, 32.33ms for traffic with 120fps). Even when adjusted for the non-integer periodicities, the jitter during the arrival of data may cause misalignment with the MG / restrictions periodicities.

[0093] On the other hand, relaxing any scheduling restrictions / MGs may result in inconsistent measurements at the WTRU and may adversely impact the accuracy of measurements, e.g., RRM measurements, RSRP / RSRQ, etc. It is desirable that any impacts on accuracy and timeliness of measurements are minimized for ensuring connectivity and mobility.

[0094] Thus, certain example embodiments described herein may address at least the problem of how scheduling restrictions (e.g., with or without MG) can be adapted to meet XR traffic requirements and / or QoS while minimizing any impacts on measurements accuracy.

[0095] Certain example embodiments may be directed to the determination of MG usage based on dynamic DL indication. For example, according to an embodiment, a WTRU may be configured to monitor PDCCH for receiving a measurement indication (e.g., in DCI) before the start of some MG occasions (MGOs) in a preconfigured MG configuration. The WTRU may be configured to determine the changes to apply to the MGOs based on the received indication and characteristics of data in buffer.

[0096] As will be discussed in more detail below, according to certain example embodiments, a WTRU may receive configuration information from the network (NW). The configurationinformation may include or indicate one or more of the following: (i) one or more MG or SMTC configurations that may include or indicate periodicity of MG occasions (MGOs) and MGO length (e.g., number of MG symbols / slots per MGO), (ii) one or more measurement objects (e.g., SSBs, CSI-RS resources), (iii) association information indicating an association between the measurement objects and MG configurations, and / or (iv) PDCCH monitoring configuration associated with a measurement indication (e.g., in DCI) that may include or indicate periodicity, search space (SS) information, and / or start offset of the MOs (e.g., n slots before start of an MGO). For example, PDCCH monitoring occasions may be associated with all or a subset of the MGOs within the MG configuration or SMTC. In one example, PDCCH monitoring occasions for the measurement indication DCI may overlap with connected mode discontinuous reception (CDRX) non-active periods.

[0097] In an embodiment, the WTRU may receive, e.g., from higher layer(s), PDUs of PDU sets. According to one embodiment, the WTRU may receive, from the NW, the measurement indication in a monitoring occasion. For example, the measurement indication may indicate any of the following: a command or indication to perform measurements in MGO(s) (e.g., the indication may be received in a new DCI, a new field of a DCI, or a scheduling DCI with ‘zero’ resource allocation which may implicitly indicate to perform measurements), a command or indication to skip MGO(s) (e.g., the indication may be received in a new DCI, a new field of a DCI, or a scheduling DCI with non-zero resource allocation which may implicitly indicate to skip measurements), a command or indication to update MGO (e.g., a bitmap indicating a subset of slots in MGO that may be skipped, scaling value to apply to MGO length, e.g., to increase / decrease MGO length, update to apply to MGO periodicity, e.g., new MGO periodicity, scaling value to increase / decrease MGO periodicity, etc.), a priority value associated with measurements in MGO (e.g., absolute / relative priority value), request for measurements and / or a measurement report (e.g., the indication may request the WTRU to perform measurements on measurement objects / resources or cells, e.g., indexes / IDs of SSBs, CSI-RS resources, or target PCI), and / or a request for MG usage (e.g., request for whether any slots within the MGO are used / skipped).

[0098] According to an embodiment, e.g., if the received measurement indication indicates a command to perform, skip and / or update measurements, the WTRU may determine the slots and / or occasions for performing measurements based on the information received in the measurement indication and information of data in the buffer.

[0099] According to an embodiment, e.g., if the received measurement indication requests for MG usage, the WTRU may determine the MG usage based on any of: payload size of PDUs,remaining time of PDUs of PDU set, priority and / or importance of PDU set, elapsed time since last measurement, and / or RSRP of measurements of serving cell.

[0100] In an embodiment, the WTRU may transmit an indication on MG usage (e.g., bitmap indicating used and / or skipped slots in MGO). According to an embodiment, e.g., if the received measurement indication requests for measurements and / or a measurement report, the WTRU may determine the MG configuration to use when performing measurements based on the information received in the measurement indication (e.g., ID of measurement object) and the association information between the measurement objects and MG configuration. The WTRU may perform measurements based on the determined and / or indicated information associated with MG / MGOs. The WTRU may then transmit the PDUs.

[0101] According to example embodiments described herein, the network may include any of a base station (e.g., gNB, TRP, RAN node, access node), core network function (e.g., AMF, SMF, PCF, NEF) and / or application function (e.g., edge server function, remote server function), for example.

[0102] According to example embodiments herein, flows may correspond to any one or more of: QoS flows or data flows (e.g., flow of data consisting of one or more PDUs, PDU sets or data bursts, which may or may not be inter-dependent with one and another and / or associated with one or more QoS requirements, e.g. latency, data rate, reliability, RTT latency). Different flows, possibly originating from a common application / experience source and / or intended to a common destination device / WTRU or group of associated devices / WTRU may be referred to associated flows or correlated flows.

[0103] According to example embodiments herein, a data unit may refer to any one or more of: one or more frames (e.g., media, video and / or audio frame or slice / segment), PDUs, PDU sets, data bursts, group of frame s / PDUs / PDU-sets / data bursts. Such data units, which may be transmitted or received by the WTRU sequentially (e.g. one after the other) or in parallel (e.g. over different channels / links / resources), may or may not be inter-dependent with each other.

[0104] According to example embodiments herein, QoE may correspond to any one or more of: application and / or higher layer metrics and measurements, which may be directly or indirectly detectable and / or visible at the WTRU and / or application function. Such QoE metrics and measurements may or may not be directly visible / detectable at the base station, for example. Such QoE metrics and measurements may be determined and / or performed as a function of QoS metrics / parameters (e.g., latency, data rate, reliability, RTT / MTP latency)

[0105] According to example embodiments herein, forwarding configuration may correspond to any one or more of the following: radio bearers (e.g., data radio bearers (DRBs) and / or signalingradio bearers (SRBs), logical channels (LCHs), logical channel groups (LCGs)), configuration parameters in the individual layers within the AS protocol stack (e.g., SDAP, PDCP, RLC, MAC, PHY, other new protocol layers), configuration to be applied for assigning COUNT / SNs for PDUs / PDU sets / data bursts, parameters associated with logical channel prioritization (LCP) (e.g., priority, PBR, BSD), BWPs, carriers, radio links / interfaces (Uu links, SLs), and radio resources (e.g., set of one or more frequency / time / spatial resources such as symbols, slots, subcarriers, resource elements or beams). Radio resources may be associated with configurated grants (CG), dynamic grants (DG) and / or any other resource grants or grant free resources.

[0106] According to example embodiments herein, mapping configuration may correspond to any of the following: parameters and / or configurations associated with mapping from one or more data units, PDUs, SDUs, PDU sets, data bursts, application data units (e.g. ADU), QoS or data flows (e.g. associated or non-associated), which may originate from any of application layer, higher layers, and / or network to one or more radio bearers (e.g. DRBs, SRBs), sublayers or entities (e.g. SDAP, new layer, PDCP, RLC, MAC, PHY), LCHs, carriers or component carriers (e.g. CCs in CA configurations), BWPs, CG configurations / resources (e.g. CG periods, slots, PUSCH occasions, RBGs), HARQ processes and radio links / interfaces (e.g. Uu link or sidelinks), which may be used for delivering the data / PDUs in UL direction or DL direction, for example.

[0107] According to example embodiments herein, multi -PUSCH CG may correspond to one or more configured resources or configured grant (CG) configurations, where each CG configuration may include a set of consecutive or non-consecutive PUSCH occasions per symbol, per slot and / or per time window / duration (e.g., CG period). In an example, a multi-PUSCH CG may include one or more CG periods (e.g., each CG period may repeat periodically with a certain periodicity value). In an example, a CG period in a multi-PUSCH CG may include one or more consecutive or non- consecutive symbols or slots. In an example, a slot in a CG period of a multi-PUSCH CG may consist of one or more consecutive or non-consecutive PUSCH occasions. In an example, a PUSCH occasion in a slot / CG period of a multi-PUSCH CG may include one or more consecutive or non-consecutive symbols with a certain symbol length (e.g. time domain resources). In an example, a PUSCH occasion may include one or more resource blocks or resource block groups in the frequency domain.

[0108] According to example embodiments herein, the following definitions of traffic requirements and characteristics may apply. PDU Set Delay Budget (PSDB) may refer to time between reception of the first PDU (e.g., at the WTRU in UL) and the successful delivery of the last arrived PDU of a PDU Set (e.g., at the network in UL). PDU Set Integrated Handling Indication (PSIHI) may indicate whether all PDUs of the PDU Set are needed for the usage ofPDU Set by application layer. PDU Set Error Rate (PSER) may define an upper bound for a rate of non-congestion related PDU Set losses between RAN and the UE. Jitter may refer to variation with respect to an expected time instance during which one or more data units may be received or transmitted. For example, for a set of data units that may be expected to be received periodically at different periodic time instances, jitter may refer to the variation with respect to the periodic time instances (e.g., for a data unit that may be received T1 ms in advance or T2 ms later than an expected time instance at T, the jitter range is T2 - Tl). Jitter may refer to an instantaneous value or a statistical value (e.g. average, variance, standard deviation, max / min). Remaining delay may refer to the time duration remaining for receiving or transmitting one or more PDUs of a PDU set before the PSDB. Remaining delay may also be referred to as the time to live (TTL) associated with a PDU set.

[0109] According to example embodiments herein, measurements intervals (Mis), may correspond to any restrictions or gaps associated with measurements (e.g., RRM measurements, PRS measurements for positioning / sensing, SL-PRS measurements). Such measurements intervals (Mis) may correspond to any of inter-frequency measurement gaps, intra-frequency measurements (e.g., without measurement gaps), scheduling restrictions, SMTC configurations, prioritization window, etc., for example. Such measurements intervals (Mis) may apply with or without configuration of measurement gaps, for example. During Mis, there may be limited or no opportunities to perform any non-measurement related procedures including scheduling and / or data transmissions / receptions. The terms measurements intervals, scheduling restrictions, SMTC, measurement gaps or measurement prioritization window (MPW) may be used interchangeably in example embodiments herein.

[0110] According to example embodiments herein, measurements intervals (Mis) may correspond to one or more scheduling restrictions or measurement gap configurations or subconfigurations, where each MG occasion (MGO) in a MG configuration / sub-configuration may consist of a set of consecutive or non-consecutive symbols, slots and / or time windows / durations (e.g., MG period). In an example, an MI or MG config / sub-config / pattem may include one or more MG periods (e.g., each MG period may consist of one or more MGOs that may repeat periodically with a certain periodicity value). For example, an MG / MI sub-configuration may comprise of a subset of MG periods in an MG / MI configuration. In an example, an MGO in a MG configuration / sub-configuration may include one or more consecutive or non-consecutive symbols or slots, during which measurements may be made and / or RF retuning procedure may be done to a carrier frequency, bandwidth part or cell associated with the measurements. For example, an MG / MI sub-configuration may comprise of subset of the MGOs in an MG / MI configuration. Inan example, a slot in an MGO may include one or more consecutive or non-consecutive symbols with certain symbol length (e.g., time domain resources), during which measurements may be made and / or RF retuning procedure may be done. In an example, an MGO may include one or more resource blocks or resource block groups (e.g., frequency domain resources), corresponding to the frequency range / resources, carriers, bandwidth parts (BWPs), cells associated with the measurements.

[0111] According to example embodiments herein, MI or MG usage may refer to any of the number, location, position and / or timing of one or more MGOs in one or more symbols, slots and / or periods, which may be associated with one or more MG configurations, that may be used by the WTRU for performing measurements and / or other related procedures (e.g. RF retuning).

[0112] According to example embodiments herein, XR / applicati on-aware data transmissions / receptions or XR / application-aware QoS handling, may correspond to any of the following. Attributes associated with a PDU set, ADU or data burst. A PDU set (e.g., media unit, video frame) may comprise of one or more PDUs. Such PDUs within a PDU set or PDU sets within a data burst may be inter-dependent with each other at the application layer and / or lower layers (e.g., AS-layers). Such attributes may include any of, for example, the number of PDUs in a PDU set / data burst, payload sizes of one or more data units (e.g., PDUs / PDU set / data burst), the association / correlation between one or more data units, importance / priority of the data units, status of transmission (e.g., percentage of PDUs of one or more data units transmitted / received successfully), remaining delay for transmitting / receiving one or more PDUs within a PDU set / data burst with respect to delay bound(s) or delay deadlines, effective data rate and / or effective reliability associated with transmission of PDUs of one or more PDU sets / data bursts.

[0113] In an example, such attributes associated with the data units may be visible at one or more lower layers (e.g. at PDCP, RLC, MAC, PHY sub-layers / layers), possibly for supporting additional actions (e.g. prioritizing, mapping to an LCH, multiplexing into one or more TBs, scheduling, relaxing any scheduling restrictions / MGs, triggering / transmitting an indication) based on any one or more of the following:• Markings in the data units. For example, such markings may include sequence numbers, IDs, indexes, timestamps, priority / importance, start / end-marking, and time offset values (e.g. with respect to a reference time) in the header of data units. Such markings may be made by higher layers, any preceding sub-layer / layer or another device / UE.• Reception of an indication such as a control PDU (e.g. application / higher / NAS layer indication, PDCP control PDU, RLC control PDU, MAC CE, DCI / UCI / SCI), in a data / shared channel (e.g. PDSCH / PUSCH / PSSCH) or control channel (e.g.PDCCH / PUCCH / PSCCH). Such indication may be received by WTRU from a higher / preceding layer, from another device / WTRU (e.g. over SL) and from network, for example.• Mapping of the data units from a higher layer to a configuration associated with a lower layer. For example, the WTRU may have visibility of higher layer attribute(s) at a lower layer when mapping the PDUs to one or more radio bearers or logical channels (LCHs) that may be configured to provide similar forwarding treatment associated with the higher layer attribute(s) to the mapped PDU.• Tracking of the attributes of the PDUs at any buffer associated with sublayer, radio bearer and / or logical channel. For example, the WTRU may track the attributes associated with the data units based on any of the time elapsed since the reception of a first PDU of a PDU set, the remaining time for the PDUs of a PDU set for meeting PSDB, jitter between the arrival one or more PDUs (e.g. first PDU or last PDU) within / across PDU sets, percentage / payload size of remaining PDUs of a PDU set expected to be received.• Restrictions associated with the sublayer, radio bearer and / or logical channel to which the data units may be mapped to. For example, the WTRU may have visibility of the data units and determine the corresponding actions (e.g. perform prioritization per LCH. LCG or LCP, perform mapping to restricted resource configurations (e.g. CG configurations, CG periods or PUSCH occasions) based on the configured restrictions associated with the one or more sublayers, radio bearers and / or LCHs to which the data units may be mapped to.

[0114] In an example, a PDU set may be associated with PDU set-level QoS requirements (e.g. data rate, latency, error rate, reliability, priority / importance), which may be applicable for one or more or all PDUs associated with a PDU set. The different PDUs in a PDU set may be associated with individual PDU-level QoS requirements.

[0115] In an example, a data burst may refer to the data produced by the application in a short period of time, comprising PDUs from one or more PDU Sets. Such attributes, associations and inter-dependencies (e.g. intra-PDU set and / or inter-PDU set), including the start / end indication of a PDU set / data burst (e.g. via sequence number, start / end indication), start / end time, duration, payload sizes, periodicity, importance / priority and QoS (e.g. PSDB) may be visible to the AS- layers (e.g. with associated IDs) and / or handled at the AS layers with the awareness of the association during data transmission in UL and reception in DL.

[0116] In an example, an embodiment may include application / high layer importance / priority. For example, the different PDUs in a PDU set or all PDUs in a PDU set may be associated with different application / high layer importance / priority values. Such importance value maycorrespond to spatial importance (e.g., spatial position of the video frame whose data is carried by the PDU7PDU set, where PDUs / PDU set carrying FoV spatial positions may be associated with higher spatial importance than non-FoV spatial positions) or temporal importance (e.g., time sequence of the video / application frame whose data is carried by the PDU / PDU set, where PDUs / PDU sets carrying base video frames such as I-frame may be associated with higher temporal importance than differential video frames such as P-frame / B-frame). Such importance values may be visible to the AS layers (e.g., with associated IDs / markers / indications), possibly enabled by application awareness, during data transmission and reception.

[0117] In an example, the PDUs / PDU sets of an application may be encoded and delivered by the application to WTRU (in UL) or network (in DL) via one or more QoS / data flows. In this regard, the different QoS flows carrying the PDUs / PDU sets associated to an XR application / experience may be visible to the AS-layers (e.g. with associated IDs) and / or handled at the AS layers with the awareness of the association during data transmission and reception.

[0118] According to example embodiments herein, WTRU actions or WTRU behavior, possibly related to application actions and / or AS-layer actions, may correspond to any one or more of the following: performing measurements and / or reporting, determining of content or metadata of application (e.g. XR application), transmitting / forwarding of data units and / or ensuring QoS associated with the data units, and / or transmitting / forwarding of information / indications associated with connectivity with network and / or other UEs.

[0119] For example, the WTRU may perform measurements of one or more of reference signals or channels (e.g. SSB, CSI-RS, PRS, sidelink RS), GNSS signals, signals / channels in unlicensed bands / carriers, ultra-wideband signals, LIDAR signals, visual signals, etc., for example. In some examples, the WTRU may perform measurements of the radio link interfaces associated with the WTRU (e.g., Uu link, SL). In another example, the WTRU may perform measurements of positioning / spatial / pose (e.g., 6DoD / 3DoD orientation, location / position), rate of motion / movement, etc. of the user / WTRU and / or other objects (e.g., virtual or real) which the user may be interacting with. The WTRU may send / report the pose measurements to network, periodically or when detecting event triggers (e.g. change in pose measurements above / below a threshold). The WTRU may trigger transmission and / or measurement of reference signals in other one or more UEs (e.g., via Uu link and / or sidelink), possibly by configuring and / or transmitting an indication, for example. The WTRU may transmit one or more measurement reports associated with the configured / indicated measurements made by the WTRU to the base station and / or other UEs. Such reports may be transmitted by WTRU periodically, aperiodically (e.g., single-shot transmitted) or on semi-persistent basis (e.g., transmitted over a duration / window defined by astart and end occasion). In some examples, the WTRU may perform adaptations to measurements, including skipping, time-shifting (e.g. delaying, advancing), or extending, possibly based on configuration, indication or event trigger (e.g. when meeting certain conditions), for example.

[0120] For example, determining content or metadata may involve determining the importance and / or priority of the content in the data units. The importance may be associated with the spatial importance and / or temporal importance of content / data, for example. In an example, the spatial / temporal importance value may indicate the absolute or relative importance associated with the content. Spatial importance may be associated with one or more segments / tiles / slices / positions of in spatial dimension, for example. Temporal importance may be associated with one or more frames / subframes of in time dimension, for example.

[0121] With respect to the transmitting / forwarding of data units and / or ensuring QoS associated with the data units, for example, data units may include any of media / image / video frames, sensor data, and measurement data (e.g., pose measurements, link / channel measurements) determined by the UE, possibly for supporting an application / service / network request associated with the UE. For example, the WTRU may transmit and / or receive data, to / from one more destinations / entities including another UE / device (e.g., via SL), RAN node (e.g., gNB), CN function / entity, application function (e.g., hosted in WTRU or in network). For example, the WTRU may perform splitting / merging of data units in one or more QoS flows into one or more forwarding configurations during transmission / receptions.

[0122] In an example, the transmitting / forwarding of information / indications associated with connectivity with network and / or other UEs may include one or more of the following. For example, capability information may be sent to the network, including capability for supporting one or more traffic flows with different XR traffic patterns (e.g. periodic / aperiodic, PDU sets with variable payload sizes), capability for performing measurements with / without MGs, capability for performing application layer measurements (e.g., QoE measurements, application buffer measurements, RTT measurements), and / or capability for detecting changes to traffic patterns, for example. Transmitting inter-WTRU coordination capability information to network, including capability for supporting one or more interfaces, capability to coordinate and / or interact with other UEs / devices (e.g. via SL interfaces), which may be co-located or non co-located with the UE, capability to configure / trigger measurements in other UEs, for example. In an example, RACH preamble(s) may be transmitted for initial access or for (re)establi shing connectivity with a RAN node, cell or another UE. In an example, configuration information may be received, including receiving RRC configuration from gNB and / or NAS-layer configuration from CN. In an example, assistance data may be transmitted and / or received to / from network associated with traffic, QoS,scheduling, etc., for supporting UL / DL transmissions. In example, request(s) may be transmitted for radio resources and / or resource grants (e.g. dynamic grants, semi-static / configured grants).

[0123] The data units may include any of PDUs, PDU sets or data bursts associated with XR traffic may be transmitted with any one or more of the following information:• Start / end marking: For example, a PDU set or data burst may include markings / flags indicating the start and / or end of the associated data unit• Sequence Numbers (SNs): For example, SNs may be marked on a per PDU, per PDU set or per data burst basis. The different types of SNs may include COUNTS, hyper-frame numbers (HFNs) and PDU SNs.• QoS attributes: QFI, PSER, PSDB, PDU set integrated handling indication (PSIHI) (e.g. flag indicating whether all PDUs of a PDU set are required to be delivered)• PDU set attributes: type, total payload size (e.g. bits / bytes, number of PDUs), start PDU of a PDU set / data burst, end / last PDU of a PDU set / data burst (end marker)• Timing / count information: Timestamp indicating the time when PDU is generated or received in a buffer, remaining delay with respect to a delay budget (e.g. PSDB), hop count (e.g. number of traversed or remaining hops), timing offset with respect to a reference time (e.g. SFN, arrival time of first PDU of PDU set).

[0124] Such marking (e.g., in the PDU headers) may be used by the transmitting and / or receiving entities for performing certain actions associated with any of determining whether the data units may be prioritized and / or multiplexed in one or more TBs, the number of TBs that may be used, whether the data units may be delivered in one or more slots / periods, whether the data units may be delayed to subsequent slots / periods, and / or a number of repetitions that may be applied for the data units or a subset of the data units.

[0125] The data units including any of PDUs, PDU sets or data bursts associated with XR traffic, with the same or different QoS requirements / characteristics, may be mapped to one or more forwarding configurations using mapping configurations. The different forwarding configurations may be configured to achieve / enforce different QoS when transmitting the PDUs / PDU sets with multi -PUSCH CG. In an example, the PDU sets received from application in one or more QoS flows may be mapped using a mapping configuration (e.g., at SDAP, PDCP) to one or more forwarding configurations (e.g., DRBs with common / different PDCP entities or LCHs with different configurations), where the forwarding configurations may be possibly associated / grouped for achieving / ensuring PDU set level QoS. Upon mapping, a set of parameters (e.g., priority, PBR, BSD) and / or configurations (e.g., LCP restrictions) may be applied at theforwarding configurations for achieving / enforcing PDU set-level or data burst-level QoS for the PDUs / PDU sets in the buffers associated with the forwarding configurations.

[0126] In this regard, it is possible that the PDUs of different PDU sets or PDU sets of a data burst, received from application / higher layers may have different expected QoS (e.g., remaining delay) to be satisfied during transmission. In this case, based on the determination of the expected QoS for the PDUs / PDU sets received or to be received in QoS flows, the WTRU may apply certain mapping, buffer / queue management and / or adaptation mechanisms at one or more layers of the AS layer protocol stack (e.g., SDAP, PDCP, MAC) such that the expected QoS for the PDUs / PDU sets may be satisfied. In an example, where the WTRU may be configured to perform measurements (e.g., with MG) the WTRU may determine the mechanism / procedure to apply to the data units based on the expected QoS and the measurement attributes (e.g. MG duration). A similar approach may be applied when the WTRU expects to receive any of the PDU / PDU sets in DL from the network. For ensuring QoS of the data units, the different layers in the forwarding configuration may be configured with different configuration parameters. Such configuration parameters may include support for reordering of the PDUs / PDU sets at PDCP, support for AM / UM in RLC, LCP rules / restrictions and associated LCH parameters (e.g. PBR, BSD, priority) at MAC and number of HARQ transmissions, for example.

[0127] The term expected QoS may be used to denote the expected margin of a certain QoS metric (e.g. latency, data rate, reliability) before the arrival of the data that may include any of PDUs, PDU sets and / or data bursts or when the data is received at one or more buffers / sublayers at the UE. In an example, the expected QoS may correspond to a time duration available at WTRU from reception (e.g., from higher layers or another UE / device) to successful delivery of the data over the radio link (e.g., Uu link or sidelink). The expected QoS may also correspond to the remaining delay (e.g., with respect to PSDB or deadline such as PDU set delay deadline) or time- to-live (TTL) (e.g., maximum time available for buffering, processing and delivering) for an individual PDU, PDU set, or data burst for example. In this case, the expected QoS may be determined based on the indications / markers in the PDUs / PDU sets (e.g., QFI, timestamps, start / end markers, PDU set ID / index in the packet headers of the PDU / PDU sets), based on an indication from higher / preceding layers (e.g., control PDU), based on usage of timers which may be set when receiving the PDUs / PDU sets (e.g., arrival of first PDU of PDU set) and reset / stopped at the expiry of a configured time duration, for example. Similar mechanisms (e.g., based on indications / markers and / or timers) may be applied for changing between different mapping and / or forwarding configurations for ensuring expected QoS.

[0128] In some examples, the expected QoS maybe stricter or relaxed than the default QoS metric applied associated with the PDUs / PDU sets. For example, if a PDU set arrives late at the WTRU or the importance value for the PDU set is indicated to be high (e.g., above a threshold), having experienced more delay and jitter at the application layer (e.g., due to encoder) or reception over SL (e.g., due to congestion) or delays due to measurements, the expected latency to be satisfied during transmission over the Uu link for the PDU set will be stricter or lower than the default PSDB that is typically used for sending the PDUs of the PDU set. Alternatively, if a PDU set arrives early or the importance value for the PDU is indicated to be low (e.g., below a threshold), the expected latency during transmission over the Uu link may be considered to be more relaxed than the PSDB that is normally used for sending such PDUs. In summary, the expected QoS may vary dynamically based on the QoS experienced during reception and / or importance / priority indications, where for a fixed QoS (e.g., PDB, PER, PSDB, PSER) an increase / decrease in the expected QoS prior to reception may translate to decrease / increase in the expected QoS during transmission / reception over the radio link (e.g., Uu link, SL).

[0129] Some example embodiments may relate to WTRU actions when configured and / or indicated with measurements using Mis / MGs. In one embodiment, the WTRU may be configured or signaled with Mis / MGs to perform measurements of measurement objects (e.g., SSBs, CSL RS). The WTRU may be configured or signaled with resources to support transmission and / or receptions of data units that may include of any of PDUs, PDU sets and / or data bursts in one or more flows in UL and / or in DL, while meeting the QoS associated with the data units.

[0130] In an embodiment, the WTRU may assist the network for configuring and / or signaling associated with any of measurements, usage of Mis / MGs, and / or usage of the resources (e.g., multi-PUSCH CG) based on any one or more of the following: configurations, triggering events, conditions / criteria received from network and / or application. The WTRU may be configured with one or more conditions and / or configurations associated with the usage of Mis / MGs during data transmissions / receptions. Such conditions and / or configurations may be related to or may reflect an expected QoS to the achieved for the data units during UL / DL transmissions, or may reflect the attributes measurements expected to be made (e.g., amount, duration, accuracy of measurements).

[0131] Some example embodiments may relate to the WTRU transmitting information associated with measurements and / or MGs. In one embodiment, the WTRU may transmit information associated with measurements and Mis / MGs, including any information for configuring one or more MG configurations, info related to measurements (e.g., type of measurement objects), information related to usage of MGs (e.g., number of slots / symbols used / unused / skipped in an MGO, MG period, and / or MG configuration), and / or information formaking adaptations to the MG configurations. In an example, the information sent by the WTRU for configuring or indicating the usage of MIs / MGs may be associated with XR traffic (e.g., periodicity of PDUs / PDU sets, payload sizes of PDU set, association of PDUs to PDU sets) expected to be transmitted in UL or received in DL. Such information may enable the network to have awareness of the traffic characteristics, configure / allocate the measurement resources and configure / signal the MIs / MGs at UE. In another example, such information associated with MI / MG may be transmitted by the WTRU to one or more others WTRUs (over SL) where the UEs may be associated with a common group or XR experience.

[0132] In some example embodiments, the information and / or indications associated with configuration, usage or adaptations associated with MIs / MGs may be sent by the WTRU to network or other UEs as any one or more of the following message types: capability information, assistance information, preferred / selected configuration information (e.g. preferred / selected MG config / parameters, preferred measurement objects), status information / indication (e.g. associated with any of the AS-layers), usage information (e.g. expected usage in terms of number of symbols / slots in MGOs or MG configurations for measurements, or in terms of expected time for using the MGOs / MGs for measurements), measurement / status reports associated with data (e.g. pending data in buffer, data expected to be received, remaining delay, jitter), measurement reports associated with measurement objects (e.g. RSRP, RSRQ, CQI), and / or request / response messages (e.g., request for activation / deactivation of a MG configuration or set of parameters associated with an MG config, request for adapting parameters of MG config).

[0133] According to certain example embodiments, the information associated with measurements and MIs / MGs may be transmitted by a WTRU in any one or more of the following methods: periodically (e.g. using one or more configured periodicity values), aperiodically or dynamically (e.g. when detecting triggering events / conditions described herein or as an update indication when detecting a change in information sent previously), and / or semi-persistent (e.g. sent periodically with a periodicity value within a predefined start and end time occasions, or in a burst manner over a time window / duration).

[0134] In an example, the WTRU may switch between a first periodicity value and a second periodicity value for sending information, possibly based on the type of event detected (e.g., change in RSRP measurements of serving cell, change in type of PDU set to be transmitted in UL, buffer occupancy delay is greater than a threshold value, remaining delay for PDU set is less than a threshold value). In another example, the WTRU may change between sending information periodically and aperiodically based on whether any change and / or amount of change is determined in the information to be reported.

[0135] In some example embodiments, the WTRU may send the information / indications associated with measurements and / or Mis to network via any one or more of the following message types, for example: RRC signaling and / or messages (e.g. in RRC request, RRC resume request, RRC reconfiguration request messages via any of SRBO, SRB1, SRB2, SRB3, SRB4), control PDUs associated with any of the AS layers (e.g. SDAP control PDU, PDCP control PDU, RLC control PDU), UL MAC CE (e.g. new MAC CE, regular BSR, periodic BSR, padding BSR, enhanced BSR, pre-emptive BSR, delay status report (DSR) which may include remaining delay information and / or amount of time elapsed since data arrival in buffer, elastic BSR which may be scalable / adjustable by sending subsequent indications, possibly without cancelling an earlier BSR), UCI (e.g. single bit SR, multi-bit SR, feedback, ACK / NACK, CSI report), CG-UCI (e.g. legacy, new, enhanced, extended), UTO-UCI (e.g. legacy, new, enhanced, extended, which may include one or more bitmaps, extended bitmaps or ID / indexes associated with set of parameters such as start offset, periodicity, etc.), PUSCH (e.g. indication such as CG-UCI or UTO-UCI may be multiplexed in PUSCH along with data), non-AS (NAS) layer signaling (e.g. PDU session related messages), and / or application layer signaling / messages.

[0136] In some example embodiments, the information / indications associated with measurements and / or MI / MGs, sent by the WTRU to network or other UEs, may include a combination of one or more of the following: identifiers (IDs); priority / importance info of measurements / MIs; traffic characteristics and / or parameters associated with any of QoS flows, PDU sets, and data bursts; QoS requirements or expected QoS associated with the data; MI / MG usage; WTRU selected or preferred MI / MG configuration information; information on updated MI / MG configurations applied at UE; indication for activating and / or deactivating MI / MG configurations; and / or measurements information.

[0137] For example, in an embodiment, the WTRU may send one or more IDs / indexes including any one or more of the following: ID / indexes associated with MGs or scheduling restrictions configurations or parameters (e.g. MGO, MG periods, MI / MG configs, SMTC configs, BWPs, carriers, beams, SSBs, RS, cells), IDs / indexes associated with MG muting patterns (e.g. a muting pattern may indicate the occasions / slots over a time duration / window when there may not be any measurements in the MGOs), group ID (e.g. associated with group of MGOs, MG configurations), IDs associated with application (e.g. application ID, service ID, session ID, application configuration ID), IDs / indexes associated with resources (e.g. CG configs, TDRA, FDRA, CG periods, PUSCH occasions, BWP), IDs / indexes associated with traffic patterns (e.g. a traffic pattern may indicate the occasions / slots over a time duration / window when there may or may not be data for transmission), IDs of individual QoS flows, mapping configurations, forwardingconfigurations, and / or association ID (e.g. ID or SNs indicating the association and / or dependency between one or more PDUs, PDU sets, data bursts, flows).

[0138] With respect to priority / importance information of measurements / Mis, for example, the WTRU may provide information on the relative / ab solute priority values associated with measurements in one or more MGOs, MG periods or MG configuration. In another example, the WTRU may provide the priority information of the data that may be transmitted or delayed / buffered due to measurements with MG.

[0139] With respect to the traffic characteristics and / or parameters associated with any of QoS flows, PDU sets, and data bursts, for example, the WTRU may send information on traffic characteristics / patterns of the different QoS flows, including whether the data is periodic, aperiodic, semi-persistent, quasi-periodic, etc. The traffic characteristics may include the one or more periodicity values of the flow, for example. Such traffic characteristics may include those that may be impacted due to measurements with Mis, for example.

[0140] In an embodiment, the WTRU may send information on the payload sizes of PDU sets, and number of PDUs expected per PDU set in one or more flows. The information of payload size of PDU set or number of PDUs per PDU set may also include statistical / distribution info such as mean, min, max, standard deviation values. The information related to PDU set may include indication of start / first and / or end / last PDU of PDU set, and indication of the association / dependency of the PDUs in a PDU set (e.g. ID of PDU set, importance / priority value). Such information related to PDU set may be associated with the data expected to be transmitted or delayed due to measurements with MG, for example.

[0141] In an embodiment, the WTRU may send information on data bursts in one or more QoS flows, including the number of PDU sets (e.g. instantaneous, mean, max, min), payload size of data burst in units of bits / bytes (e.g. instantaneous, mean, max, min), periodicity, importance / priority, start and end indication of a data burst (e.g. ID of first PDU / PDU set, ID of last PDU / PDU set), and dependency info within data burst and across multiple data bursts (e.g. indicating whether PDU sets in one or more data bursts are dependent).

[0142] In an embodiment, the WTRU may send information related to the delay in UL and / or in DL, including remaining delay with respect to PSDB, and time elapsed since the PDUs / PDU set arrive at WTRU (e.g. at one or more buffers at UE). Such delay information which may be sent on a per flow, per radio bearer, per-LCH, per-PDU set or per PDU basis, may include the range, mean, maximum and minimum value, for example. Such delay info may be due to buffering of data during measurements, for example. In an embodiment, the WTRU may send information related to the jitter in UL and / or in DL. Such jitter info which may be sent on a per flow, per-radio bearer,per-LCH, per-PDU set or per PDU basis, may include the range, mean, maximum and minimum value, for example. Such jitter info may be due to buffering of data during measurements, for example. In an embodiment, the WTRU may send information on the importance / priority of any of the data units (e.g. PDUs, PDU sets, data bursts) to be transmitted / received in UL / DL. In an embodiment, the WTRU may send indications when detecting any changes to the UL / DL traffic patterns (e.g. changes to periodicity, changes to mean payload sizes, changes to jitter range). In an embodiment, the WTRU may send info on prediction of traffic pattern in UL and / or DL for upcoming / expected data (e.g. timing info indicating the PUSCH occasion, time slot or CG periods when the data is expected to arrive, payload size of expected data, importance of data expected, uncertainty and / or confidence level of expected data or prediction associated with the expected data over a time window / duration).

[0143] With respect to QoS requirements or expected QoS associated with the data, for example, the WTRU may send the QoS requirements or expected QoS of the one or more flows or data units (e.g. PDUs, PDU sets, data bursts), including data rate, latency, reliability, absolute / relative priority values, etc. The information on QoS requirements may also include statistical / distribution info such as mean, min, max, standard deviation values. In an embodiment, the WTRU may also indicate that such QoS requirements or expected QoS may be supported on different QoS granularities such as: per-PDU, per-PDU subgroup within a PDU set (e.g. one or more PDUs), per PDU set, per-group of PDU sets, per flow, per session. The WTRU may also indicate a time window (e.g. start time, duration, end time) during which such QoS requirements or expected QoS may be applicable to the different QoS granularities, for example. For example, the WTRU may send expected QoS information upon applying adjustments to the QoS due to delays during measurements. Such information may be determined based on the traffic attributes (e.g. remaining time) and the MI / MG attributes (e.g. length / duration of measurements), for example. In an embodiment, the WTRU may indicate the expected QoS to be achieved on the basis of different resource and / or MG granularities applied, such as: resource granularities (e.g., per group of one or more CG configurations, CG periods, time slots, PUSCH occasions, radio blocks, radio block groups) and / or MG granularities (e.g., per MG config, MG periods, per MGO, per BWP, per cell / carrier).

[0144] With respect to MI / MG usage, for example, the WTRU may send information / indications associated with the usage MI / MG including any of MGOs, MG periods or MG configurations. Such usage information may include the symbols / slots / occasions, possibly in a time window, expected to be used or not used during measurements. The length of an MGO in a MG period or MG configuration, in terms of number of symbols or slots, may be either the same or different, forexample. Such usage information may also include the frequency resources (e.g. resources blocks, resource block groups), bandwidth, carriers that are expected to be used or not used during measurements. Such usage information may also include the amount of PUSCH or PUCCH resources expected to be used or not used for transmitting the reports associated with the measurements.

[0145] In an embodiment, the WTRU may indicate information on the usage of MIs / MGs as any one or more of the following:• start offset of an MGO (e.g. start symbol / slot), MG period or MG configuration.• number of consecutive or non-consecutive symbol s / slots / MGOs where measurements may be done or skipped.• bitmap with a certain length corresponding to the number symbols / slots / occasions in one or more MG periods or MG configs, where a bit ‘ 1’ in the bitmap may indicate whether measurements are expected to be done and a bit ‘0’ may indicate whether the measurements are expected to be skipped by the UE, or vice-versa. Such bitmap may allow indicating the usage of non-consecutive symbols / slots / occasions.• Time-shift (e.g. in terms of symbols / slots / occasions) to be applied to an MGO, MG period or MG configuration. For example, the time shift may indicate the number of slots to advance or delay a MGO, during which the WTRU may expect to perform measurements.• Frequency shift to be applied to an MGO or MG configuration. For example, the frequency shift may indicate any of the new, update, or offset to apply to frequency resources, bandwidth, or carriers.• one or more gap values within or across multiple MGOs or MG configurations indicating the number symbols / slots / occasions expected to be used for relaxing the scheduling restrictions, performing data transmissions / receptions, or skipping measurements. Such gap value may be indicated in the form of a start offset symbol / occasion / slot / period of the gap and the length of the gap (e.g. number of symbols / occasions / slots / periods)• validity duration of the indicated MI / MG usage (e.g. in ms or in number of symbols / slots / periods during which the indicated MG usage may be assumed to be valid).

[0146] In an embodiment, the WTRU may determine to change the transmission frequency of the indication on MI / MG usage (e.g., number of times the indication is triggered in a time window) as a function of measurements quality (e.g., RSRP is above / below a threshold), data jitter range(e.g., min / max value), and / or jitter duration (e.g., whether the observed jitter is sustained over a duration), priority / importance of data and / or QoS of data (e.g. PSDB). For example, for a set of low priority PDUs, the WTRU may delay the indication on MG usage or transmit the indication with low periodicity after (e.g., only after) observation of a sustained (e.g., over a duration) delayed arrival time or high jitter. For the case of high priority PDU set, the WTRU may indicate the MG usage sooner or with high periodicity, for example.

[0147] In an embodiment, the WTRU may transmit the indication on MG usage in any one or more of the following: UCI (e.g., using preconfigured PUCCH resource, which may be configured with any of periodic resources with certain periodicity, on the basis of different granularities indicating per MG config, per-CG configuration, per-LCH, per-radio bearer, per-PDU set. Alternatively, the UCI may be multiplexed in PUSCH), UTO-UCI (e.g., with new information elements appended to existing UTO-UCI or one or more of existing information elements in existing UTO-UCI are repurposed / replaced with PUSCH usage information), MAC CE, and / or RRC signaling.

[0148] With respect to a WTRU selected or preferred MI / MG configuration information, for example, the WTRU may indicate to network one or more selected or preferred MI / MG or SMTC configurations and / or parameters associated with the MI / MG configurations (e.g. MGOs, MGO length, MG period, start offset of MGO). Such selection / preference information may include any of the number of active MG configurations, periodicity, length of MGO (e.g. number of consecutive and / or non-consecutive symbols / slots per MGO), number of MGOs per period, start offset of MGO), preferred measurement objects (e.g. SSB indexes, CSI-RS IDs), target cells (e.g. cell ID, PCI), target carri er s / b earns, and time / frequency resources associated with measurements. In an example, the WTRU may associate and / or indicate weight / probability values to different MG configurations when sending request related to preferred configuration. In this case, the weight / probability value may be determined based on the likelihood of a configuration to be applied during measurements or data transmissions, for example. The network may use such weight / probability info for determining and providing to WTRU a combined configuration and / or for activating / deactivating an MG configuration that may match with the weight values indicated by UE, for example. In an example, the WTRU may indicate uncertainty information (e.g. percentage / probability) associated with the usage of any of the MI / MG configurations over one or more time windows / duration.

[0149] With respect to the information on updated MI / MG configurations applied at UE, for example, the WTRU may transmit the information on any updated MG configurations and / or updated parameters associated with the MG configurations. The WTRU may also transmit thecause information (e.g. change of measurements, change of data attributes) for updating the MG configurations / parameters.

[0150] With respect to an indication for activating / deactivating MI / MG configurations, for example, the WTRU may send an indication to network to request for activating / deactivating one or more MG configuration and / or parameters associated with the configurations, possibly preconfigured in the WTRU. The WTRU may include the ID / index of the configurations / parameters when sending the request indication, for example.

[0151] Regarding the measurements information, for example, the WTRU may transmit RSRP, RSRQ, RSSI measurements of the signals, channels, radio links, carriers, and cells associated with the measurement objects from serving or neighbor cells. Such measurement objects may be configured or signaled to the UE. For example, the WTRU may send the QoS related measurements related to arrival time, delays, jitter and number of PDUs / PDU sets / data bursts received possibly over a time duration, change in the QoS (e.g. increase / decrease in data rate, latency, jitter, reliability), TTL associated with the PDUs / PDU sets / data bursts, remaining time for delivering the PDUs / PDU sets / data bursts.

[0152] Certain example embodiments described herein and in the following may use any one or more of the above information (e.g. assistance information, preferred configurations) sent by the WTRU to network.

[0153] Certain example embodiments may include a WTRU receiving configuration and / or signaling associated with data and / or measurements from the network. In an embodiment, the WTRU may receive information / indications for supporting any of the procedures, mechanisms, rules, or actions associated with MIs / MGs for measurements and / or data transmissions / receptions. Such indications may include configuration info associated with the MG configurations / parameters or signaling (e.g. dynamic indications of measurements to be done / skipped, dynamic activation / deactivation of MGOs, MG configurations and / or parameters), for example.

[0154] According to some example embodiments, the information / indications may be received by a WTRU from the network periodically (e.g. with one or more configured periodicity values), aperiodically / dynamically (e.g. as signaling indication, update to configurations / parameters or request / request messages) and / or on semi-persistent basis (e.g. received periodically over a time window / duration) .

[0155] In an embodiment, the WTRU may receive any of the information / indications (described herein) associated with MI / MG, for example, via any one or more of the following: RRC signaling and / or messages (e.g. dedicated / unicast signaling via any of SRBs, or broadcast / SIB), controlPDUs associated with any of the AS layers (e.g. SDAP control PDU, PDCP control PDU, RLC control PDU), DL MAC CE, DCI (e.g. UE-specific, group-common, cell-common), PUSCH, and / or Non-AS (NAS) layer signaling (e.g. a PDU Session Establishment Response or a PDU Session Modification Command). Examples of RRC messages may include RRC Reconfiguration, RRC Resume, etc. RRC signaling may be used for configuring any parameters (e.g. start offset of MGOs, MGO length, MG periods) associated with MI / MG configurations, SMTC configurations or prioritization windows. RRC signaling may be used for activating / deactivating any of measurement resources configurations (e.g. CSI-RS resource / report configurations), SMTC configurations, or MI / MG configurations. MAC CE may be used for receiving MG configurations and / or parameters associated with associated with MI / MG configurations. For example, MAC CE may be received in a bitmap format, where a bit in the bitmap may indicate the activation / deactivation of one or more of any of the following: symbols / slots for measurements, MGOs, MG periods, MG configurations. In an example associated with an MGO comprising of multiple slots, a bit ‘ 1’ may indicate using an associated slot for measurements and a bit ‘0’ may indicate using an associated slot for data transmissions / reception. DCI for measurement indication may be used for receiving info on the measurements to be performed by WTRU and / or subset of parameters associated with MI / MG configurations. DCI may be used for receiving activation / deactivation indication for any of one or more MGOs, a set of MGOs in an MG period, and MG configurations. The DCI associated with the measurement indication may be received in a preconfigured search space and / or PDCCH monitoring occasions.

[0156] In an embodiment, the information / indications associated with MIs / MGs (e.g. configurations and parameters) which may be received by WTRU from the network, via semistatic (e.g. RRC) or dynamic signaling (e.g. MAC CE or DCI), may include a combination of one or more of the following: MI / MG configurations / parameters, other resource configurations / parameters for data transmission / receptions, AS layer status information / indications, validity information, threshold values associated with measurements, and / or threshold values associated with data.

[0157] Types of MG configurations may include any of Type 1, Type 2, or Type 3. For Type 1, configuration parameters (e.g. MG length, MG repetition periodicity) may be provided via RRC signaling. In an example, the activation / deactivation of the Type 1 MG may be done via RRC signaling. Such activation / deactivation may correspond to periodic MG. For Type 2, configuration parameters may be provided via RRC signaling. At least a subset of the MG parameters (e.g. MGO) and activation / deactivation indication may be provided via dynamic signaling (e.g. DCI orMAC CE). Such activation / deactivation may correspond to aperiodic or semi-periodic MG. For Type 3, at least a subset of configuration parameters may be selected by UE.

[0158] An embodiment may include receiving enabling / disabling indication. For example, the WTRU may receive semi-static or dynamic indication indicating the enabling or disabling of any of an MI / MG configuration and enhanced / new MI / MG configuration (e.g. allowing dynamic adaptation of a subset of MG parameters).

[0159] The parameters associated with measurements and / or MI / MG configurations may include any one or more of the following: number of MG occasions in an MG period; number of slots / symbols in an MGO or MG period; start offset of an MGO and / or MG period; periodicity (e.g., associated with MGO repetition period); measurement resource configuration (e.g. time / frequency resources associated with measurement objects including CSI-RS, SSBs, PRS, SL- PRS); frequency range / bands (e.g. FR1, FR2, FR3, sub-THz, THz); layer where measurements may be made, processed and / or filtered (e.g. LI, L2, L3); bandwidth part and / or numerology info associated with channels, carriers, cells for performing measurements; target cells info for performing measurements, e.g., cell id / index / PCI associated with any of serving cell, neighbor cell, primary cell and secondary cells; target beams info for performing measurements (e.g. SSB indexes); transmission info associated with measurement objects (e.g. indexes / IDs associated with antenna ports, pathloss reference signal, spatial relation info, QCL info); hopping pattern (e.g. indicating intra-slot, inter-slot, inter-MGO hopping on whether to perform measurements or skip measurements); measurement repetitions (e.g. number of symbols / slots / occasions for performing repetitions of measurements on a set of measurement objects); and / or minimum distance between MGOs (e.g. minimum number of symbols / slots / occasions before measurements may be made with an MGO).

[0160] With respect to other resource configurations / parameters for data transmission / receptions, for example, the WTRU may receive one or more other resource configurations. The other resource configurations may include configured grant (CG) resources / configurations for UL transmissions, including the parameters: one or more PUSCH slots per CG occasion / period, periodicity, start offset, TDRA and FDRA info. The other resource configurations may also include semi-persistent scheduling (SPS) resources / configurations for DL data receptions. The parameters associated with SPS resources / configurations may include any of periodicity, start offset, duration, BWPs, numerology / SCS values, number of PRBs, number of occasions, number of PDSCH slots per occasion, maximum number / duration / length of PDSCH, one or more MCS values for the SPS PDSCH occasions, antenna ports, etc., for example. The other resource configurations may also include dynamic grant resources for UL data transmission(e.g. triggered by UCI, SR, BSR, MAC CE) and / or dynamic scheduling resources for DL data receptions (e.g. triggered by DCI, PDCCH, MAC CE).

[0161] In an embodiment, the WTRU may receive at least one set of configuration parameters associated with default forwarding configuration (e.g. default set of LCHs), which may be activated and / or used during normal scenarios for transmitting / receiving data, for example. The WTRU may also receive another set of configuration parameters which may be associated with exceptional operation, possibly activated and / or used when performing measurements with MIs / MGs or when detecting any of the triggering events / conditions (described herein), for example.

[0162] In an embodiment, the WTRU may receive default priority values associated with the resource configurations (e.g. CG). For example, a first resource configuration may be associated with a first priority value and second resource configuration may correspond to a second priority value. The first and second resource configurations may be associated with the same set of radio bearers or LCHs. A first set of priority values may be intended to achieve a default QoS performance (e.g. default latency, default data rate) and a second set of priority values may be intended to achieve exceptional QoS performance, for example, when transmitting delayed / buffered data during measurements.

[0163] In an embodiment, AS layer status information / indications may include IDs, for example, the WTRU may receive info on one or more IDs including any one or more of the following: IDs, e.g. C-RNTI, I-RNTI, NAS IDs, TMSI / IMSI; group IDs / indexes (e.g. associated with group of MG occasions, MG periods, MG configurations); and / or IDs / indexes of individual MG occasions, MG slots, MG periods, MG configurations.

[0164] In an embodiment, the WTRU may receive validity information associated with the configurations / parameters (e.g. MG configurations, MG periods, set of MGOs) indicating whether / when the configurations may be considered to be valid or invalid, based on one or more of triggering events / conditions. The WTRU may also receive information on whether the configurations are to be deactivated and / or released when determining them to be invalid. For example, the WTRU may receive info on whether the MG / MI configurations are to be considered as valid / invalid based on the RRC state of the WTRU (e.g. CONNECTED, INACTIVE, IDLE) and / or when transitioning between different RRC states. In another example, the WTRU may assume the MI / MG configurations to be valid or invalid based on whether the one or more timer values associated with the configurations are running or expire.

[0165] In an embodiment, for example, the threshold values may be associated with any of RSRP, RSRQ, RS SI, CQI, etc. Such measurement thresholds may correspond to the measurement objects (e.g. SSBs, CSI-RS) received from a serving cell or neighbor cell, for example.

[0166] According to some example embodiments, the threshold values associated with data may include buffer occupancy thresholds, PDU / PDU set payload size threshold values, delay threshold values, delay difference threshold values, reliability threshold values, and / or correlation time window.

[0167] For example, the buffer occupancy threshold values associated with any of forwarding configurations may indicate the maximum / minimum amount of data units in one or more granularities / types including PDUs, PDU sets and data bursts (e.g. in terms of total payload size / volume) that are in one or more buffers (e.g. SDAP buffer, PDCP buffer, LCH buffer at MAC).

[0168] For example, the payload size threshold values may be associated with one or more upper and / or lower bound values corresponding to the total size of payload (e.g. in the units of bits or bytes) of one or more PDUs, PDU sets and / or data bursts. In another example, the payload size threshold values may be associated with one or more upper and / or lower bound values corresponding to the total number of PDUs in a PDU set, or total number of PDU sets in a data burst.

[0169] For example, delay threshold values may be associated with one or more upper and / or lower bound values corresponding to maximum / minimum delay value and / or remaining delay values (e.g. with respect to PSDB or delay deadline) associated with reception, buffering and / or transmission of any of data units (e.g. PDUs, PDU sets, data bursts). Such delay threshold values may be intended to identify and / or determine the maximum / minimum latency tolerated by the network, application and / or UE, possibly as a result of delays due to processing, jitter, transmission, congestion, etc., for example.

[0170] For example, delay difference threshold values may be associated with one or more upper and / or lower bound values corresponding to the difference between a first delay value (e.g. default delay) and a second delay value (e.g. new / updated delay value).

[0171] For example, the reliability threshold values corresponding to the reliability achievable for one or more PDU set during transmission may be associated with a minimum (lower bound) or maximum (upper bound) number of repetitions or retransmissions of the PDUs of the PDU set. In this case, a TB carrying one or more PDUs of a PDU set is expected to be transmitted with at least N repetitions (e.g. over N PUSCH occasions with independent channel conditions) for meeting the PDU set reliability requirement. In another example, the reliability threshold maycorrespond to a certain percentage value of the PDU set that is received successfully to be considered as meeting the reliability requirement of the PDU set.

[0172] For example, the correlation time window may correspond to the minimum time difference between two events (e.g. RSRP measurements, buffer level measurements, PDU / PDU set arrival time), where the two events may be considered as correlated between one and another when they occur within the correlation time window. When the two events occur at time instances beyond the correlation time window, they may be considered as independent. In an example, the WTRU may use the correlation time window for determining whether to indicate / request the NW to activate / deactivate an MG / MI configuration.

[0173] Certain example embodiments described herein and in the following may use any of the one or more of the above information / indications received by the WTRU from the network.

[0174] Some example embodiments may relate to events and / or conditions for triggering WTRU actions associated with measurements and / or data. The WTRU may be configured with one or more events and / or conditions for performing certain actions associated with any of the following: determining new or updated MG usage (e.g. used / unused MG symbols / slots / occasions, MG periods, MG configs) over a time window, selecting an MI / MG configuration / pattern (e.g. over a time window), adapt / update the MI / MG configurations and / or the associated parameters (e.g. MG periodicity, MGO / MG length), transmitting an indication on MG usage, transmitting an indication for requesting to update / adapt any of the MG configurations or parameters associated with MI / MG configurations, transmit / receive data (e.g., even when the data transmission occasion or resource overlaps with MI / MG / MGO), determining new or updated traffic pattern over a time window (e.g. arrival of PDUs of PDU sets from higher layers or other devices / UEs, delay for processing and transmitting the data, jitter between arrival of different batches of inter-dependent data units, payload size of data units received and expected to be received).

[0175] In an embodiment, such triggering events / conditions may be associated with ensuring sufficient and accurate measurements are made the UE, and / or meeting expected QoS when transmitting / receiving the data units (e.g. PDUs, PDU sets, data bursts).

[0176] Such triggering events / conditions may indicate the time instances (e.g. symbols, occasions, slots, or periods) an action may be performed by UE. For example, the WTRU may indicate the number of MG occasions in a time window that are expected to be used and / or unused by WTRU for measurements. Alternatively, for example, the WTRU may increase / decrease the MG periodicity and / or decrease / increase the MGO length when the RSRP measurements made on the measurement objects (e.g. CSI-RS, SSBs) associated with the serving cell is higher than / less than a RSRP threshold value. In another example, the WTRU may perform datatransmission / reception instead of measurements, when the events / conditions are met, even when the resource (e.g. PUCCH, PUSCH, PDCCH, PDSCH) or data transmission / reception occasions overlap with that of the measurement occasions in MI / MG configurations. For example, the WTRU may perform data transmissions (e.g. initial transmissions or HARQ retransmissions) instead of measurements when the conditions for transmissions are met.

[0177] Such conditions / events may include a combination of one or more of the following: indication / request received from the network, measurements on measurement objects / channels / cells, property associated with MI / MG configuration^. g. MG symbol / slot, MGO, MGO length, MG period), indication / information from application / higher layers in WTRU or from another device / UE, buffer status and loading at forwarding configurations (e.g. DRBs / LCHs) in UE, change of configuration(s) at UE, timing / timestamp information (e.g., possibly associated with expected QoS), measurements on data / traffic, compensation based on status of expected QoS, and / or detection of QoS events (e.g. surge in payload size, reception of high importance data).

[0178] In an embodiment, the indication and / or request received from the network may include any one or more of the following:• a command or indication to do measurements in one or more MGOs, MG periods, MI / MG configs. For example, the indication may be received in a new DCI or in a scheduling DCI with ‘zero’ resource allocation in the symbols / slots / occasions overlapping with MG which may implicitly indicate to do measurements.• a command or indication to skip measurements in one or more MGOs, MG periods, MI / MG configs. For example, the indication may be received in a new DCI or in a scheduling DCI with non-zero resource allocation in the symbols / slots / occasions overlapping with MG, which may implicitly indicate to skip measurements.• a command or indication to update MGO. For example, the indication may include a bitmap indicating the MG symbols / slots / occasions / periods that may be skipped, scaling value to apply to the MGO length, changes to the MG periodicity (e.g. increase or decrease), changes to the start offset of MGO (e.g. time-offset to delay / advance the MGO), etc.• priority value associated with measurements in MGO. For example, the priority values indicated may be an absolute value or a relative value (e.g. relative to the RSRP range of the measurements made by WTRU on a configured / signaled RS).• request for type of measurements (e.g. measurements associated with serving cell, neighbor cells, target PCIs) and / or measurement objects (e.g. SSBs, CSI-RS) to be performed.• requests for MG usage (e.g. whether any symbols / slots within the MGO are used / skipped).

[0179] In an embodiment, the indication may be received semi-statically (during or after MG configuration) or signaled dynamically. The WTRU may transmit an indication, described in the example embodiments herein, based on the indication / request received from network, for example. In an embodiment, the indication / request be received by WTRU on the basis of any of the following: per symbol / slot, per MGO, per MG period (e.g. for a set of MGOs), per MI / MG config, per-CG configuration, per-CG period, per-PUSCH occasion, per-HARQ process, per PDU, per- PDU set, per data burst, per-QoS / data flow, per forwarding configuration (e.g. radio bearer or LCH), per-resource configuration, for example. Such indication / request may be received by WTRU in RRC, MAC CE, other control PDU or DCI).

[0180] With respect to measurements on measurement objects / channels / cells, for example, the WTRU may perform measurements over the Uu link and / or SL, e.g. measurements on measurement objects (e.g. SSBs, CSI-RS, any RS, PRS, SL-PRS) corresponding to RSRP, RSSI, CQI and CSI. Such measurements may be used for supporting control plane procedures (e.g. connectivity (re)establishment, initial access, cell (re) sei ection, beam (re)selection / management, beam maintenance, coverage and mobility / handover). Such measurements may be used for determining the expected QoS for the data units expected to be received and / or transmitted. The channel measurements made over a certain configured time duration may indicate whether more / less frequency measurements are expected (e.g. for supporting mobility) or whether the data units may be able to achieve the expected QoS during transmission and / or reception. The WTRU may trigger an action based on the measurements on Uu link and / or SL, for example. In an example, the WTRU may determine the radio link conditions based on the number of ARQ / HARQ (e.g. ACK / NACK) feedback messages and / or retransmissions made over the one or more HARQ processes associated with the forwarding configurations applied for sending the data units. As an example, a ReTx count above a threshold may translate to poor link conditions, and hence, reduced remaining delay or TTL. For example, the WTRU may be triggered to perform WTRU action(s) and / or send an indication to network when channel measurements made (e.g. RSRP, RSSI, RSRQ, CQI, CSI) increases / decreases with respect to a configured threshold and / or remains above / below a threshold for a certain time duration.

[0181] With respect to property associated with MI / MG configuration (e.g. MG symbol / slot, MGO, MGO length, MG period), for example, a WTRU may be configured with a property specific to the MI / MG configuration such as: priority value, measurement objects (e.g. SSBs, CSI- RS), measurement value (e.g. RSRP, RSRQ, CQI), target cell (e.g. serving cell, neighbor cell), and / or a configuration parameter enabling / disabling the specific action for the MI / MG configuration. For example, the WTRU may change the parameters of an MI / MG configuration associated with priority values above a threshold as long as the change impacts only other lower priority MI / MG configurations.

[0182] With respect to the indication / information from application / higher layers in WTRU or from another device / UE, for example, the WTRU may perform any of the WTRU actions (described above) when receiving an indication from application / higher layers or another WTRU (over SL). Such indication may include information on the change of traffic patterns associated with the generation, processing, transmission and / or reception of XR data units in one or more flows. In an example, the application or another WTRU may indicate to WTRU the information on the expected number of QoS flows which may be associated with the application, expected number of PDUs per PDU set, whether any of PDUs / PDU sets are dependent, expected frame / PDU set in a subsequent time instances (e.g. next frame generation instance), expected change in the distribution of importance / priority of PDUs generated, expected increase / decrease in latency (e.g. due to processing at codec / application or due to congestion / delays over SL), and / or jitter for delivering the data units in UL and / or DL, expected change in the TTL associated with the data units, expected change in UE / user motion / movement (e.g. increase / decrease in rate of motion), etc. For example, the WTRU may receive an indication from higher layers or another WTRU indicating the arrival of one or more data units (e.g. in a batch / burst) at UE. The information on the arrival of the PDUs may include the expected timing (e.g. time slot / frame) of data unit generation, and expected timing of reception at UE, for example. Such information may be indicated to WTRU via timestamps, and / or sequence numbers for example. Such info may be useful for determining the impact of measurements using MI / MG configurations on the expected QoS of data, for example. For example, the WTRU may be triggered to perform any of WTRU action(s) based on an indication of importance / priority of the data units. The WTRU may trigger an action (e.g. request to update the MG config) for retransmitting a lost / missing PDU and / or transmitting a delayed PDUs with compensation (e.g. low latency) when receiving an indication from higher layers containing a importance / priority value higher than a threshold, for example.

[0183] In an embodiment, the buffer status and loading at forwarding configurations (e.g. DRBs / LCHs) in the WTRU may include at least a condition associated with any of the followingor combinations of measurements (e.g. compared to a threshold) such as: the amount of XR data units in one or more buffers associated with forwarding configurations (e.g., possibly over a period of time or time window); the rate of arrival / departure of data units in one or more buffers associated with forwarding configurations; the average, max, min size / volume of the data units in an buffers associated with forwarding configurations (e.g. number of PDUs in LCH buffer); the amount of time spent by one or more data units in buffers associated with the forwarding configurations; and / or the number of forwarding configurations meeting a condition / threshold associated with the amount of data, arrival rate, data units (e.g. total payload size), etc.

[0184] For example, a WTRU may perform any of the actions described above or in example embodiments herein if at least one data unit in a forwarding configuration (e.g. UL LCH buffer waiting to be transmitted in UL) is in the buffer for a period of time larger than a threshold time value. For example, a WTRU may perform any of the actions described in example embodiments herein if the buffer status (e.g. total payload size) exceeds a threshold. For example, other buffer status metrics that may be monitored for determining the expected QoS include the number of data units buffered which are above / below a configured threshold in one or more associated forwarding configurations, and / or the rate of data units arrival / departure in the buffer with respect to a configured arrival / departure rate, for example.

[0185] With respect to the change of configuration(s) at the UE, for example, the WTRU may be triggered to perform any of WTRU action(s) when determining a change to a mapping configuration, forwarding configuration and / or resource configuration, including changing at least one of the parameters at the mapping configuration (e.g. mapping a QoS flow to a new forwarding configuration), changing parameters of DRB / LCHs (e.g. priority, PDB, PBR), changing LCP configuration (e.g. updates to LCP rules or restrictions), changing QoS of data units (e.g. PSDB, PSER, PSIHI), and / or changing resource configurations / parameters (e.g. CG, DG, SPS). For example, the WTRU may be triggered to perform a WTRU action(s) when the CDRX / discontinuous reception (DRX) configuration and any of the associated parameters applied at the WTRU is modified / updated, which may possibly impact the traffic pattern and / or CG resource usage.

[0186] With respect to timing / timestamp information (e.g., possibly associated with expected QoS), for example, the WTRU may track the timing related information (e.g. timestamp, sequence number, start / end marker or timing control PDU) in the one or more data units received in an earlier time window for determining the remaining latency or jitter. The timing information may then be used for determining whether / how QoS may be met for upcoming / new data units in the next time window using the configured resources (e.g. CG PUSCH occasions in one or moreslots / periods), for example. In an example, the timing information may be determined / indicated as a deadline / latency bound and / or survival time that may be satisfied on a per-PDU, per-PDU set, per-data burst or per-QoS flow basis. Such timing information may be determined across one or more associated / correlated QoS flows, including the correlated UL flows, for example. In another example, the timing information may also be determined / indicated on a count basis (e.g. data unit count). The WTRU may trigger an action, when determining new or updated timing information, for example. In another example, the WTRU may send information / indications / reports to network periodically or based on a setting / expiry of a timer.

[0187] With respect to the measurements on data / traffic, in an example, the WTRU may trigger an action, based on measurements of data arrival / jitter and / or determination of the time duration / jitter or change in the time duration / jitter between reception of consecutive PDUs associated with an PDU set or consecutive PDU sets associated with a data burst, and / or reception of data units in one or more correlated flows in UL and / or DL. For example, the WTRU may infer an increase / decrease in the jitter between consecutive PDUs for determining whether the processing load at application / higher layer or congestion over SL is high / low. In this case, for determining the time duration, the WTRU may set a timer when a first data unit (e.g. first PDU of a PDU set) arrives and reset the timer when an associated second data unit (e.g. second PDU of PDU set) arrives, for example.

[0188] With respect to compensation based on status of expected QoS, for example, the WTRU may be triggered to perform WTRU action(s) based on determination of expected QoS for one or more data units or length / amount of measurements, including indication on whether the data units may be either delayed or arrive early, during measurements using MI / MG configuration. In this case, the WTRU may trigger an action such that the delayed or early data units may be transmitted with a determined compensation amount, for example, by using configured resources (e.g. CG PUSCH occasions) or updated set of forwarding configuration parameters (e.g. priority, PBR). In an example, the action(s) may be triggered when detecting a change (e.g. higher / lower) in the expected QoS for the data units by a certain threshold or detecting a change in measurements (e.g. RSRP of serving cell is above / below certain threshold values). In an example, the WTRU may determine the delayed PDUs due to measurements to be transmitted using higher priority or an earlier CG PUSCH occasion / slot / period that enables satisfying a compensation amount, where the compensation amount may be determined by subtracting the expected latency from actual latency, for example.

[0189] With respect to the detection of QoS events (e.g. surge in payload size, reception of high importance data), for example, QoS events may include surge events associated with an increasein the number of data units or payload size, possibly over a time window, indicated / marked with high importance / priority, for example. Likewise, other QoS events may include QoS deflation associated with a decrease in the number of data units or payload size over a time window, for example. For example, the WTRU may be triggered to perform WTRU action(s) when detecting one or more QoS events, possibly by considering the indicated / determined time duration the QoS events are expected to persist. The WTRU may then perform other WTRU actions that may result in falling back to the default configurations, possibly after the end of the detected QoS events, for example. In an example, when a surge event (e.g. increase in total payload or number of PDU sets) is detected, the WTRU may trigger an action to update the MG configuration^. g. MGOs expected to be used or unused) for the duration of the surge. When determining reduction in the surge or end of surge event, the WTRU may fallback to using the default MG config.

[0190] Certain example embodiments may relate to the determination of MG usage based on dynamic DL indication. For example, according to some embodiments, a WTRU may receive configuration information for determining measurements and / or MG usage based on a dynamic DL indication.

[0191] In one embodiment, the WTRU may monitor PDCCH for receiving a measurement indication (e.g. in DCI) before the start of one or more MG occasions (MGOs). The WTRU may determine any changes to apply to the measurements and / or MGOs based on the received indication and / or the characteristics of the data in buffer. Such changes to the MGOs may include any of but not limited to, for example, skipping and / or performing measurements in some slots associated with the MGO, making adaptations to the MGOs (e.g. time-shifting by x slots) and / or performing measurements according to the adaptations. Such characteristics of data may include any of but not limited to, for example, remaining time of the data being less than a threshold value, and priority / importance of data being greater than a threshold value. For instance, a benefit of determining changes to measurements and / or MGO upon reception of a DL indication is to allow the WTRU to dynamically accommodate any data transmissions / receptions when such occasions overlap with MI / MG based on NW control and / or under certain conditions allowed by NW.

[0192] In an example embodiment, the WTRU may receive configuration information which may include one or more MI / MG and / or SMTC configurations, which may include or indicate at least the periodicity of MGOs and MGO length (e.g. number of MG symbols / slots per MGO). The WTRU may also receive configuration information on one or more measurement objects, including SSBs (e.g. indexes / IDs), CSI-RS (e.g. CSLRS resources / resource sets, CSI-RS report configuration), TRS and any other RS for measurements. The WTRU may also receive the association info (e.g. mapping relation, table) between the one or more measurementobjects / resources / reports and MI / MG / SMTC configurations, possibly indicating the MI / MG configurationto apply when signaled with the measurement objects, resources and / or reports.

[0193] In an example embodiment, the WTRU may also receive a PDCCH monitoring configuration associated with a measurement indication (e.g. in DCI), comprising at least one of a periodicity, search space (SS) info, aggregation level (AL), start offset of the MOs (e.g. n slots before start of an MGO) and parameters of a time window (e.g. length of window in terms of symbols, slots, ms and start offset). Such PDCCH monitoring configuration for the measurement indication may be associated with a cell-common, group-common or a UE-specific configuration, for example. The PDCCH monitoring occasions associated with the measurement indication may be associated with all or a subset of the MGOs within the MI / MG configurationor SMTC, for instance. For example, the periodicity of the monitoring occasions for the measurement indication may be the same or different than that of the MGOs in the MI / MG config. Additionally, the PDCCH monitoring occasions for the measurement indication may or may not overlap with the CDRX non-active periods. In this case when overlapping with the non-active periods, the WTRU may monitor PDCCH for receiving the measurement indication (e.g. in DCI) before the start of an MGO outside of the CDRX active periods, for example.

[0194] The WTRU may receive from higher layers or from another WTRU (over SL) one or more PDUs of PDU sets. The WTRU may select and / or forward the PDUs of the PDU sets to one or more radio bearers and / or LCHs based on a set of parameters associated with the PDUs and / or PDU set including importance / priority, arrival time window of the PDUs, payload sizes of the PDUs, QoS of the PDU / PDU set (e g. PSDB, PSIHI, PSER, PSDD), etc. The WTRU may determine the remaining delay of a PDU set based on the arrival time of the PDUs (e.g. time elapsed since the arrival of the first PDU of a PDU set in an LCH buffer) and the PSDB and / or PSDD. When any of the transmission occasions (TOs) or UL slots (e.g. in a TDD frame configuration) do not overlap with any of the MG / MGOs, the WTRU may transmit one or more indications in UL, possibly along with data. Such indications may include any of SR, BSR, DSR, UTO-UCI or CG-UCI, for example. Such indications may be new and / or conditional indications (e.g. conditional SR / BSR) for informing the NW on the presence of urgent data in WTRU buffer. In an example, when the data in buffer meets certain conditions (e.g. remaining time is less than threshold) the WTRU may transmit a conditional SR / BSR / DSR before the start of an MGO in MG config, possibly if there is an UL slot before the MGO. In this case, the WTRU may monitor for DCI (e.g. containing a DL dynamic indication) in PDCCH even when the PDCCH monitoring occasion may overlap with MG.

[0195] In an example embodiment, when the WTRU is configured with a multi-PUSCH CG configuration, the WTRU may transmit in a UTO-UCI indication, which may include the information on which of the resources (e.g. symbols, slots, PUSCH TOs) that may be used (e.g. for transmitting data) and / or unused. The WTRU may determine a PUSCH TO as valid and / or indicate a PUSCH TO as ‘used’ even when the PUSCH TO may overlap with a MGO in an MI / MG config, possibly to request the NW to allow data transmission over performing measurements, for example. Similarly, the WTRU may indicate a PUSCH TO as ‘unused’ when the PUSCH TO overlaps with a MGO in an MI / MG configuration, possibly to indicate the WTRU prefers to do measurements in the associated TO, for example. Such indication and / or information (e.g. in UTO- UCI) may be transmitted in a bitmap, for example. Such indication may provide the NW with the information / request on whether any of symbols, slots and / or occasions associated with data transmission overlapping with those of MI / MG configuration are used or unused, for example.

[0196] Certain example embodiments may relate to the receipt of a dynamic DL indication on measurements and / or MI / MG from a NW. For example, in an embodiment, the WTRU may receive from the NW the measurement indication (e.g. in DCI), possibly in a configured PDCCH monitoring occasion (e.g. within CDRX active or non-active period). Such measurement indication may be associated with an aperiodic MG or a semi-persistent MG, which activates and / or deactivates one or more MGOs, during which the WTRU may perform or skip measurements. Alternatively, the measurement indication, in part or entirely, may be received in a DL MAC CE or RRC signaling. The contents of measurement indication may include any of the following: a command or indication to do measurements in one or more MGOs; a command or indication to skip measurements in one or more MGOs; a command or indication to update / adapt one more parameters of MGOs; a command or indication to use / switch / activate / deactivate one or more MI / MG configs / patterns; One or more priority values associated with measurements in MGO; request for measurements and / or a measurement report; and / or a request for MG usage.

[0197] With respect to a command to do measurements in one or more MGOs, for example, such indication may be received in a new DCI format and / or in a new field of a DCI format (e.g. extended field). Such indication may be received in a scheduling DCI with ‘zero’ resource allocation which may implicitly indicate for the WTRU to do measurements in the MGOs / MI / MG.

[0198] With respect to a command to skip measurements in one or more MGOs, for example, such indication may be received in a new DCI format and / or in a new field of a DCI format (e.g. extended field). Such indication may be received in a scheduling DCI with ‘non-zero’ resource allocation which may implicitly indicate for the WTRU to skip measurements in the MGOs / MI / MG.

[0199] With respect to a command to update / adapt one more parameters of MGOs, for example, the indication may include a bitmap indicating a subset of symbols / slots in MGO that may be skipped. For example, the indication may include a scaling value to apply to modify the MGO length (e.g. ‘y’ scaling value to increase / decrease the MGO length). For example, an update to the MGO periodicity (e.g. new MGO periodicity, scaling value apply to increase / decrease MGO periodicity). For example, a time-shift value or start offset value (e.g. to advance or delay the start / end of an MGO by n symbols / slots / occasions / periods).

[0200] With respect to a command to use / switch / activate / deactivate one or more MI / MG configs / patterns, for example, activation of another preconfigured MG pattern, e.g. where another MG pattern may be associated with a different SSB periodicity or SMTC configuration.

[0201] With respect to one or more priority values associated with measurements in MGO, for example, an absolute priority value of ‘x’ may indicate the WTRU to perform measurements if the priority value associated with data is less than x. Otherwise, the WTRU may perform data transmission. For example, one or more relative priority values of ‘y 1, y2’ may be indicated, where the priority values may be relative to the RSRP measurements of a reference signal (e.g. path loss RS, spatial relation RS) associated with the serving cell. In this case, if RSRP >= threshold, the priority for measurements is yl. Otherwise, if RSRP < threshold the priority for measurements is y2, for example.

[0202] With respect to a request for measurements and / or a measurement report, for example, the indication may request the WTRU to perform measurements on any of the measurement objects, measurement resources, beams or cells (e.g. indexes / IDs of SSBs, CSI-RS resources, or target PCI). For example, the indication may include an id / index associated with measurement resources and / or measurement report (e.g. CSI-RS resource / resource set ID, CRI, CSI-RS report config ID / index).

[0203] With respect to a request for MG usage, for example, the indication may request whether any symbols / slots / occasions / periods within the MGO / MI / MG are used / skipped.

[0204] Certain example embodiments may relate to the determination of actions based on reception of a dynamic DL indication on measurements and / or MI / MG. For example, in an embodiment, the WTRU may determine the corresponding actions based on the received measurement indication. In an example, if the received measurement indication indicates a command to do / skip / update measurements in one or more MGOs, the WTRU may determine the symbols / slots / occasions / periods for performing measurements and / or skipping measurements based on the info received in the measurement indication. Additionally, the WTRU may determine the symbols / slots / occasions / periods for measurements based on the characteristics of data inbuffer. For example, the measurement indication may comprise of a bitmap, where each bit may correspond to one or more consecutive or non-consecutive symbols / slots in an MGO, where a bit ‘ 1’ may indicate to do measurements and a bit ‘0’ may indicate to skip measurements or vice- versa. The WTRU may determine to perform measurements in the slots indicated to do measurements and perform data transmissions in the slots indicated to skip measurements, for example.

[0205] In another example, if the received measurement indication indicates a command to update / adapt parameters of one or more MGOs in MI / MG config, the WTRU may determine the corresponding adaptation (e.g. time-shifting of MGOs, changing length of MGO, changing periodicity of MI / MG) and perform measurements according to the updated / adapted MGOs in the MI / MG configuration.

[0206] In another example, if the received measurement indication requests for MG usage, the WTRU may determine the corresponding MG usage (e.g. in one or more MGOs) based on any of the data and / or measurement attributes and the associated threshold values described above and as follows. For example, data attributes may include or relate to any one or more of payload size of PDUs, remaining time of PDUs of PDU set (e.g. with respect to PSDB or PSDD), and / or priority / importance of PDU set. For example, measurement attributes may include or relate to any one or more of elapsed time since last measurement (e.g. last symbol in a previous MGO), and / or RSRP / RSRQ of measurements (e.g. at LI, L2, L2) of the measurement objects (e.g. SSBs, CSL RS, TRS) associated with one or more cells (e.g. serving cell, neighbor cell, Pcell, Scells).

[0207] For example, the WTRU may determine the MG usage (e.g. skip measurements in an MGO) when the RSRP measurements made on serving cell is above a threshold value and / or the remaining delay of data in buffer is below another threshold value. The WTRU may transmit an indication on the MG usage to the NW. Such indication may be transmitted in a UCI (e.g. SR, enhanced / extended UTO-UCI), MAC CE or RRC signaling, for example.

[0208] In another example, if the received measurement indication requests for measurements and / or a measurement report (e.g. CSI report), the WTRU may determine the MI / MG configuration and / or MGOs to use when performing measurements based on the info received in the measurement indication (e.g. ID / indexes of measurement objects or resources, ID / index of measurement reports) and the configured association information between the measurement objects and MI / MG configurations.

[0209] In an example, upon receiving the measurement indication, the WTRU may transmit an UL indication to confirm the reception of the measurement indication. Such confirmationindication may be transmitted in a UCI (e.g. SR, PUCCH resource, HARQ-ACK, CSI report), MAC CE or RRC signaling, for example.

[0210] In an embodiment, the WTRU may perform measurements according to the determined / signaled info associated with measurements and / or MI / MG configurations. The WTRU may perform data transmissions before / after performing the measurements.

[0211] Certain example embodiments may relate to the performance of adaptations to MI and / or MG, e.g., based on UE-autonomous or NW-controlled approaches. For example, in an embodiment, the WTRU may perform one or more adaptations to the MI / MG configuration or pattern based on any of a reception of an indication from NW (e.g. measurement indication). Such adaptations may include any one or more of the following: modify the MG / MGO length (e.g. shorten length by K symbols / slots during overlap with data / PUSCH TOs), time-shift MG occasions (e.g. advance / delay MG start offset), skip MG occasions, change MG periodicity (e.g. one pattern with multiple periodicities where some MOs of a periodicity are fixed and MOs on another periodicity may be skipped), and / or select / switch to another preconfigured MG pattern, e.g., where another MG pattern may be associated with different SSB periodicity or SMTC configuration^. g. 20ms to 40ms periodicity). Such adaptations to the MGOs / MI / MG configurations may be done further based on any of measurements-based and / or data / traffic-based conditions / criteria. For example, measurements-based conditions may include any one or more of: type of measurement objects (e.g. SSBs in FR2), type of measurement events (e.g. Al, A2 or A3), change in L3 measurements made (e.g. in N MOs) is less than threshold, change in Ll-RSRP when the measurements made on a reference measurement object (e.g. reference SSB) over 2 MOs is less than a threshold, and / or number of times / occasions (e.g. count value) where measurements were skipped during previous MGOs is less than or equal to a max count value. For example, data / traffic-based conditions may include any one or more of the following: type of data (e.g. PDU set importance / priority > threshold), total payload size (e.g. combination of traffic in multi-modal flows), remaining time of PDU set < threshold, delay difference between dependent PDUs / PDU sets < synchronization threshold, and / or jitter in UL > threshold.

[0212] It is noted that any of the above adaptations may be conditioned on the amount of measurements and / or traffic attributes. For example, the amount of change or scaling value expected to be applied to the MG length may be associated or proportional with the amount of change determined in the LI and / or L3 measurements.

[0213] Additionally or alternatively, any of the above adaptations to the MI / MG configurations may be enabled with RRC signaling, MAC CE or DCI. The adaptations may be handled in UE- autonomous or NW-controlled approaches. For example, in a UE-autonomous case, if anypreconfigured conditions are met (e.g. measurements or data related conditions), the WTRU may determine / select an adaptation for the MI / MG config. Such adaptation may be signaled to NW (e.g. in MAC CE, UCI) so that the NW is aware that the WTRU is temporarily not doing measurements and may do scheduling or data transmissions / receptions. The WTRU may also indicate to the NW if it decides to perform measurements during the MGO / MG instead of data transmissions, e.g., if data may be delayed to after measurements. In the NW-controlled case, the NW may dynamically transmit an indication to WTRU (e.g. in MAC CE, DCI) on the adaptations to the MI / MG configuration to be applied at the UE. Such indication may be associated with an aperiodic MG or semi-persistent MG, for example, where any of the skipping / non- skipping / adaptations to the measurements / MG / MI may be done in a single-shot manner (e.g. for a single MGO) or for a number of occasions (e.g. multiple MGOs), possibly in a time window (e.g. within a start and end time).

[0214] In view of the above, in some example embodiments, the WTRU may receive configuration information from NW. For example, the configuration information may include or may indicate any one or more of one or more MG or SMTC configurations, which include or indicate periodicity of MG occasions (MGOs) and MGO length (e.g. number of MG symbols / slots per MGO), one or more measurement objects (e.g. SSBs, CSI-RS resources), association information indicating an association between the measurement objects and MG configurations, and / or DL control channel (e.g., PDCCH) monitoring configuration associated with a measurement indication (e.g. in DCI). For example, the monitoring configuration may include or indicate periodicity, search space (SS) information, start offset of the MOs (e.g. n slots before start of an MGO). For example, PDCCH monitoring occasions may be associated with all or a subset of the MGOs within the MG configurationor SMTC. In one example, PDCCH monitoring occasions for the measurement indication DCI may overlap with CDRX non-active periods.

[0215] In an embodiment, the WTRU may receive, e.g., from higher layer, PDUs of PDU sets. In an embodiment, the WTRU may receive, e.g., from NW, the measurement indication in a monitoring occasion. For example, the measurement indication may indicate any one or more of the following: a command or indication to do measurements in MGO(s) (e.g. indication may be received in a new DCI, a new field of a DCI, or a scheduling DCI with ‘zero’ resource allocation which may implicitly indicate to do measurements), a command or indication to skip MGO(s) (e.g. indication may be received in a new DCI, a new field of a DCI, or a scheduling DCI with non-zero resource allocation which may implicitly indicate to skip measurements), a command to update MGO (e.g. bitmap indicating a subset of slots in MGO that may be skipped, scaling value to apply to MGO length (e.g. to increase / decrease MGO length), update to apply to MGO periodicity (e.g.new MGO periodicity, scaling value to increase / decrease MGO periodicity), etc.), priority value associated with measurements in MGO (e.g. absolute / relative priority value), a request for measurements and / or a measurement report (e.g. indication may request the WTRU to perform measurements on measurement objects / resources or cells (e.g. indexes / IDs of SSBs, CSI-RS resources, or target PCI)), and / or a request for MG usage (e.g. request for whether any slots within the MGO are used / skipped)). In an embodiment, if the received measurement indication indicates a command to perform, skip and / or update measurements, the WTRU may determine the slots / occasions for performing measurements based on the information received in the measurement indication and / or information of data in buffer. In an embodiment, if the received measurement indication requests for MG usage, the WTRU may determine the MG usage and may transmit an indication on MG usage (e.g. bitmap indicating used / skipped slots in MGO). For example, the MG usage may be determined based on any one or more of: payload size of PDUs, remaining time of PDUs of PDU set, priority / importance of PDU set, elapsed time since last measurement, and / or RSRP of measurements of serving cell. In an embodiment, if the received measurement indication request for measurements and / or a measurement report, the WTRU may determine the MG configuration to use when performing measurements based on the information received in the measurement indication (e.g. ID of measurement object) and the association information between the measurement objects and MG configuration. In an embodiment, the WTRU may perform measurements based on the determined / indicated information associated with MG / MGOs. The WTRU may then transmit the PDUs.

[0216] FIG. 2 illustrates an example diagram depicting the determination of MG usage based on dynamic DL indication, according to some embodiments. As illustrated in the example of FIG. 2, the WTRU may monitor PDCCH for receiving a measurement indication (e.g. in DCI) before the start of MG MGOs. The WTRU may determine the changes to apply to the MGOs (e.g. whether to perform / skip measurements) based on the received indication and data in buffer.

[0217] Certain example embodiments may relate to the determination of measurements and / or data transmissions in a multi-part MG occasion. For example, in some embodiments, the WTRU may receive configuration information for determining MG usage in a multi-part MGO. In one embodiment, the WTRU may be configured with an MI / MG configuration that includes one or more MGOs, where each MGO may include at least two parts. The WTRU may perform measurements in the 1st part of an MGO and may determine whether to skip and / or adapt measurements in the 2nd part of the MGO based on the measurements done in the 1st part and the characteristics of data in buffer. In this case, the 2nd part of the MGO may be assumed to be valid(i.e. used for measurements), unless the WTRU transmits an indication requesting to skip / adapt the MGO, for example.

[0218] In an example embodiment, the WTRU may receive configuration information and / or parameters associated with one or more measurement configuration that includes measurement objects and / or resources (e.g. SSB, CSI-RS, TRS) and time / frequency measurement information (e.g. parameters of SMTC window). The WTRU may also receive one or more MI / MG configurations comprising of one or more measurement gap MGOs, where each MGO may consist of at least a 1st part and a 2nd part. The parameters of each of the 1st and 2nd parts of an MGO may include measurement length (e.g. number of symbol s / slots, ms), start offset (e.g. symbols / slots / frames with respect to SFN), density of measurements, repetition period, comb pattern, etc. For example, in time-domain, the symbols / slots / occasions associated with the 2ndpart of the MGO may occur after the 1stpart of MGO. In frequency domain, the resources / resource block / occasions associated with the 2ndpart of the MGO may occur following those in the 1stpart of the MGO. Alternatively, the occasions of the 2ndpart (e.g. in time and / or frequency domain) may interleave or occur in between any of the occasions associated with the 1stpart. Such interleaving of the occasions in the 1stand 2ndparts may follow a particular comb pattern, for example. When configured with multi-part MGO, the measurements in the 1st part of an MGO may not be skipped and those in the 2nd part of the MGO may be conditionally skipped / adapted by the UE, for example.

[0219] In an embodiment, the WTRU may also receive one or more conditions and / or threshold values associated with any of those described above and the following: measurements (e.g., RSRP / RSRQ / CQI of RS / SSB / cells (e.g., serving cell, neighbor cell), number / count of previously skipped MGOs, elapsed time since the last skipped MGO) and / or data characteristics (e.g., remaining time with respect to PSDB / PSDD / NW-configured value, payload size of PDUs / PDU set, priority / importance).

[0220] In an embodiment, the WTRU may receive from higher layers or from another WTRU (over SL) one or more PDUs of PDU sets. The WTRU may select and / or forward the PDUs of the PDU set to at least one radio bearer and / or LCH based on any of the importance / priority of the PDU set, arrival time of the PDUs, payload sizes of the PDUs, and QoS of the PDU / PDU set (e.g. PSDB, PSER).

[0221] In an MGO, the WTRU may perform measurements in at least the 1stpart of the MGO. The WTRU may determine the measurements status (e.g. whether to perform or skip / adapt measurements) in the 2nd part of the MGO based on configured conditions. For example, the WTRU may determine to skip measurements in one or more symbols / slots / occasions associatedwith the 2ndpart of an MGO when meeting any one or more of the following conditions: RSRP measurements in 1st part of MGO > RSRP threshold, change in RSRP between measurements in 1st part of MGO and measurements in a previous MGO (e.g. 1stand / or 2ndpart) < RSRP change threshold, number of MGOs skipped previously < max count threshold, elapsed time since last measurement < time threshold, remaining time of PDUs < remaining time threshold, and / or importance of data > importance threshold.

[0222] Certain example embodiments may relate to the transmission of an indication on measurements and / or MG usage. For example, upon determining the measurement status, the WTRU may transmit an indication to NW on the measurement status. Such indication may be transmitted in a UCI (e g. SR, UTO-UCI, HARQ-ACK, CSI report), UL MAC CE or RRC signaling. Such indication may be transmitted in a measurement report, which may include the measurements made on at least the 1stpart of an MGO, for example.

[0223] In an example, if the WTRU determines to skip measurements, the indication may include the information on skipped MGO, including any one or more of the following: bitmap / flag indicating whether the 2ndpart of MGO is skipped, number of skipped symbols / slots / occasions in 2nd part of MGO, scaling factor to apply to MGO length (e.g. indicating decreasing the length), change in periodicity or density of 2ndpart of MGO, and change in the comb pattern in the 2ndpart of MGO. For example, when sending the indication to skip the 2ndpart of MGO, the WTRU may indicate it is free to do data scheduling / transmissions / reception in any of the symbols / slots / occasions associated with the 2ndpart of MGO.

[0224] In an example, if the WTRU determines to not skip measurements, the indication may include the information on measurements that are expected in the MGO, including any one or more of the following: bitmap / flag indicating 2ndpart of MGO is not skipped, number of symbols / slots / occasions where measurements may be done in 2nd part of MGO, scaling factor to apply to MGO length (e.g. indicating increase of length), change in periodicity or density of 2ndpart of MGO, and change in the comb pattern for measurements in the 2ndpart of MGO. For example, when sending the indication to skip the 2ndpart of MGO, the WTRU may indicate it is not free to do data scheduling, transmissions and / or reception in any of the symbols, slots and / or occasions associated with the 2ndpart of MGO.

[0225] In an embodiment, the WTRU may perform measurements according to the transmitted information in the indication on multi-part MGO. The WTRU may then perform data transmissions before and / or after performing the measurements in the multi-part MGO. For example, the WTRU may transmit PDUs in the occasions where measurements are skipped (e.g. 2nd part of MGO) and / or in occasions non-overlapping with MGO.

[0226] In view of the above, an example embodiment may include the WTRU receiving configuration information. The configuration information may include or indicate any one or more of: measurement configuration, MG configuration, and / or conditions and / or threshold values. The measurement configuration may include or indicate measurement objects (e.g. SSB, CSI-RS) and time / frequency measurement info (e.g. SMTC window). For example, the measurement configuration may indicate the optional / non-optional target PCIs (e.g. which PCIs may be measured with / without skipping). In an example, the measurement configuration may indicate which subsets of SSBs from some cells that may be optional / non-optional and the associated SSB periodicities. The MG configuration may include or indicate one or more measurement gap occasions (MGOs), where each MGO may include at least a 1st part and a 2nd part. For example, the measurements in the 1st part of an MGO may not be skipped and those in the 2ndpart of the MGO may be conditionally skipped / adapted. In an example, the parameters of each of 1stand 2ndparts of MGO may include measurement length (e.g. number of symbols / slots), start offset, density of measurements, etc. The conditions and / or threshold values may be associated with measurements (e.g. RSRP threshold, number of previously skipped MGOs) and / or data characteristics (e.g. remaining time threshold, priority / importance).

[0227] In an embodiment, the WTRU may receive, e.g., from higher layers, PDUs of PDU sets. The WTRU may perform measurements in the 1st part of an MGO. The WTRU may determine the measurements skipping status in the 2nd part of the MGO based on configured conditions. For example, the WTRU may determine to skip measurements in 2nd part of MGO if any one or more of: RSRP measurements in 1st part of MGO > RSRP threshold, change in RSRP between measurements in 1st part of MGO and measurements in a previous MGO < RSRP change threshold, number of MGOs skipped previously < max count threshold, elapsed time since last measurement < time threshold, remaining time of PDUs < remaining time threshold, and / or importance of data > importance threshold.

[0228] In an embodiment, the WTRU may transmit an indication on the measurement skipping status. For example, an indication may be sent in a UCI (e.g. SR, UTO-UCI) or MAC CE. As an example, if the WTRU determines to skip measurements (e.g. free to do data scheduling), the indication may include the information on skipped MGO (e.g. number of skipped symbols / slots in 2ndpart of MGO, scaling factor to apply to MGO length). As an example, if the WTRU determines not to skip measurements, the indication / flag may indicate measurements are expected (e.g. not free to do data scheduling). According to an embodiment, the WTRU may transmit PDUs in the occasions where measurements are skipped (e.g. 2nd part of MGO) and / or in occasions nonoverlapping with MGO.

[0229] FIG. 3 illustrates an example diagram depicting the determination of measurements and / or data transmissions in a multi-part MG occasion, according to some embodiments. As illustrated in the example of FIG. 3, the WTRU determines the MG usage in the 2ndpart of an MGO (e.g. whether measurements in 2nd part is skipped or symbols / slots where measurements are skipped) based on conditions associated with measurements performed in 1stpart of MGO and data in WTRU buffer. The WTRU may transmit an indication on the determined usage in 2ndpart of MGO.

[0230] Some example embodiments may relate to the selection of a preconfigured MI / MG pattern. For example, in certain embodiments, the WTRU may receive configuration information for selecting a MI / MG pattern. In one embodiment, the WTRU be configured with one or more MI / MG patterns (as described elsewhere herein). The WTRU may select an MI / MG pattern based on characteristics of data (e.g. periodicity jitter) and measurements parameters (e.g. SMTC, SSB periodicity). Such selection of an MG pattern may be done to (re)align the timing between data transmissions and MGs, for example. The WTRU may transmit an indication requesting to activate the selected MG pattern(s) and may perform measurements based on the activated MG pattern(s).

[0231] In an example embodiment, the WTRU may receive configuration info and / or parameters associated with one or more MI / MG configurations or patterns. For example, each MI / MG pattern may comprise of a set of parameters including start offset slot / symbol, periodicity of MI / MG pattern, MGO length (e.g. number of symbols / slots / occasions), number of parts for measurements and non-measurements per MGO, validity time window, index / ID.

[0232] Additionally, in an embodiment, each MI / MG pattern may be associated / aligned with an SSB periodicity or periodicity of an SMTC window supported by target PCIs (e.g. serving cell, neighbour cells, PCell, PSCell, SCells). Similarly, in an embodiment, each MI / MG pattern may be associated with a data transmission periodicity and / or frame generation frequency (e.g. 60 fps, 120fps). The values of such periodicities may comprise any of integer periodicity values (e.g. 10ms, 20ms, 500ms), non-integer periodicity values (e.g. 16.66ms, 32.33ms) and rational number periodicity values (e.g. 50 / 3ms), for example.

[0233] Additionally, in an embodiment, a set of MGOs within an MI / MG pattern may be associated with a validity time window, comprising parameters: start offset (e.g. symbols, slots, ms), length of window (e.g. number of symbol s / slots / MGOs, ms) and repetition periodicity. Such validity time window may indicate the time duration during which the signalled / activated MI / MG pattern is assumed to be valid / active, for example. From the configured set of MI / MG patterns, at least one MI / MG pattern may be configured to be in an enabled / activated state and the remaining patterns may be in a disabled / deactivated state.

[0234] In an embodiment, the WTRU may receive in the configuration information, a set of conditions and / or threshold values for selecting an MI / MG pattern. Such conditions and / or threshold may include any of those described above and / or one or more of the following, for example: threshold values for amount of MGO (e.g. number of symbols, slots, occasions in MGO) overlapping with data TOs, threshold values for time difference between MGOs, threshold values for payload size, threshold values for jitter (e.g. determined based on the arrival time of PDUs with respect to an expected arrival time), and / or threshold values for the delay due to data buffering or remaining delay of data.

[0235] In some embodiments, the WTRU may determine and / or select a MI / MG pattern based on a data transmission pattern. For example, the WTRU may receive from higher layers or from another WTRU (over SL) one or more PDUs of PDU sets. The WTRU may a determine a data transmission pattern (e.g. in terms of number and locations of the slots or data TOs / PUSCH TOs (e.g. CG PUSCH) that may be used or unused for transmissions), possibly over a time window / period, based on any of the following. For example, if the payload of one or more PDUs of PDU sets multiplexed into a PUSCH TO is less than or equal to a first payload threshold value and / or greater than a second payload threshold value, the WTRU may determine the data / PUSCH TO as used. If the payload of the one or more PDUs of PDU sets multiplexed into a PUSCH occasion is less than the second payload threshold value, the WTRU may determine the data / PUSCH TO as unused. For example, if the remaining delay of the PDUs of a PDU set (e.g. considering any of arrival time, jitter, and buffering delay due to measurements / congestion) is less than or equal to a delay threshold associated with PSDB / PSDD, and / or the PDUs of the PDU set in the buffers may be multiplexed into the set PUSCH TOs, the WTRU may determine the set of data / PUSCH TOs as used. If the remaining delay of the PDUs of the PDU set is greater than the delay threshold and / or the PDUs may be delayed to the next slot or a period outside of the time window, the WTRU may determine the data / PUSCH TOs as unused. For example, if the number of repetitions of one or more PDUs (e.g. PDUs with a priority higher than a priority threshold value) of the PDU set is less than or equal to a first repetition threshold value and / or greater than a second repetition threshold value, the WTRU may determine the corresponding data / PUSCH TOs as used. The WTRU may determine any of the PUSCH TOs that do not contain any new or repetition PDUs as unused, for example.

[0236] In an embodiment, the WTRU may select / determine one or more MI / MG patterns from the configured set based on the determined data transmission pattern. In an example, the WTRU may select one or more patterns, where selection of multiple patterns may constitute a union, based on one or more of the following: number of slots / symbols / occasions in an MGO overlapping withthe data / PUSCH TOs in the data transmission pattern is less than or equal to a threshold value, time difference between the last MGO (e.g. in a previous MI / MG pattern) and the next MGO (e.g. in a new MI / MG pattern) is less than or equal to a first threshold value and greater than a second threshold value, and / or buffering delay of data due to measurements is less than or equal to a threshold value.

[0237] In some embodiments, a WTRU may transmit an indication on selected MI / MG pattern. For example, the WTRU may transmit an indication in UL to NW on the selected one or more MI / MG patterns, for example, containing the ID / index of the MI / MG patterns. Such UL indication may include a request for activation of the selected MG patterns. Such indication may include a bitmap, with bits corresponding to the one or more selected MI / MI patterns. Such indication may be transmitted before start of a MI / MG pattern validity time window. Such indication may be transmitted in any of UCI, new UCI (e.g. extended UTO-UCI), MAC CE or RRC signalling. Alternatively, such UL indication may include info on data transmission pattern (e.g. number of data / PUSCH TOs expected to be used / unused) and / or its association with an MI / MG pattern (e.g. number of used data / PUSCH TOs overlapping with the MGOs in an MI / MG pattern).

[0238] In an embodiment, the WTRU may receive a confirmation indication in DL from NW on the MI / MG pattern that may be used. Such DL indication may indication may indicate the activation / deactivation of the requested and / or new MI / MG patterns. Such DL indication may be received in DCI, DL MAC CE or RRC signalling, for example. The WTRU may perform measurements according to the selected / signaled MI / MG pattern. The WTRU may then perform data transmissions before / after performing the measurements using the MI / MG pattern.

[0239] In some embodiments, a WTRU may be configured with data prioritization window configuration for determining prioritization of data over measurements. For example, in an embodiment, the WTRU may be configured with one or more data prioritization window (DPW) configurations that may be used to perform prioritization between measurements and data transmissions / receptions (e.g. transmissions in PUCCH / PUSCH and receptions in PDCCH / PDSCH). The configurations parameters associated with a DPW configurationmay be comprised of start offset (e.g. with respect to SFN), periodicity, and / or length of an DPW occasion / active period (e.g. number of symbols / slots / ms), etc. The parameters associated with a DPW configuration may or may not be similar or aligned with those of an MI / MG config. The periodicity of DPW may be aligned with that of XR traffic periodicity (e.g. 16.66ms, 32.33ms), for example. In an example, the WTRU may or may not be configured with MI / MG configurations when configured with DPW, since the DPW may enable the WTRU to perform measurements in a similar manner as that of MI / MG.

[0240] In an example, when configured with an MG configuration, and an MGO of the MG configurationoverlaps with a DPW active period, the WTRU may determine to prioritize data transmissions over measurements if some preconfigured conditions are met (e.g. scheduling restrictions may be relaxed when conditions are met). When the DPW active time does not overlap with an MGO of MG configuration, the WTRU may perform data transmissions / receptions. Outside of the DPW active period and when MGO of MG configuration does not overlap with DPW, the WTRU may prioritize measurements over data transmissions.

[0241] The conditions for prioritizing data transmission over measurements or vice-versa within a DPW may include any of those described elsewhere herein (e.g. related to measurements and / or data / traffic attributes) and / or one or more of the following: explicit signaling or implicit signaling of prioritization. As an example, an embodiment may include explicit configuration / signalling (e.g. in DCI) of priority of data and measurement objects. For example, the WTRU may determine to perform measurements if indication / signalling is received from NW indicating the priority of measurements is greater than that of data. In this case, the priority of the data may be determined based on LI priority or L2 priority (e.g. priority associated with LCHs). As an example, an embodiment may include implicit signalling of prioritization. For example, when receiving in a scheduling DCI which may include the timing of the UL grant (e.g. in Kx offset) that may overlap with an MGO / MG, the WTRU may determine that measurements are skipped in the MG.

[0242] In view of the above, according to an example embodiment, a WTRU may receive configuration information. The configuration information may include or indicate one or more MG patterns and / or criteria including one or more MG patterns and / or criteria and / or threshold values for selecting a MG pattern. Each of the one or more MG patterns may include parameters including start offset slot / symbol, periodicity of MGOs, MGO length and / or index / ID. For example, each MG pattern may be associated / aligned with an SSB periodicity or SMTC window supported by target PCIs (serving cell and neighbour cells). For example, a set of MGOs within an MG pattern may be associated with a validity time window. For example, at least one MG pattern is enabled / activated and others are deactivated. The criteria and / or threshold values for selecting MG pattern may include, for example, a threshold for amount of MGO overlapping with data TOs, thresholds for time difference between MGOs, threshold for data buffering delay.

[0243] In an embodiment, the WTRU may receive, e.g., from higher layers, PDUs of PDU sets. The WTRU may determine the data transmission pattern (e.g. in a time window) based on PDU set info (e.g. payload, jitter, remaining time of PDU set, number of repetitions). The WTRU may select one or more MG patterns from configured set based on the data transmission pattern. For example, the WTRU may select one or more MG patterns (e.g. union of patterns) based on anyone or more of: number of slots / symbols in an MGO overlapping with the data transmission pattern < threshold 1, time difference between the last MGO (in previous MG pattern) and next MGO (in a new MG pattern) is < thresholdl and > threshold2, and / or buffering delay of data due to measurements < thresholds.

[0244] In an embodiment, the WTRU may transmit an indication with info on the selected MG patterns (e.g. IDs / indexes). For example, an indication may request activation of the selected MG patterns. For example, an indication may be transmitted before start of a MG pattern validity time window. Alternatively, for example, an indication may include information on data transmission pattern.

[0245] In an embodiment, the WTRU may receives a confirmation indication on the MG pattern(s) to use. For example, an indication may indicate activation of the requested and / or new MG patterns(s). In some embodiments, the WTRU may perform measurements using the indicated MG pattem(s) and transmit PDUs after the measurements.

[0246] FIG. 4 illustrates an example diagram depicting the selection of a preconfigured MI / MG patter, according to an embodiment. As illustrated in the example of FIG. 4, the WTRU may select and indicate a preconfigured MI / MG (e.g. MG pattern 3) which may be closely correlated with the data transmission pattern determined by UE. The WTRU may transmit an indication on the selection MG pattern.

[0247] Some example embodiments may relate to prioritization of data delayed due to measurements. For example, in an embodiment, a WTRU may receive configuration information on prioritization of data during and / or after measurements. In one embodiment, the WTRU may be configured to temporarily prioritizes the transmission of PDUs in some LCHs which may be delayed due to measurements. Such prioritization may be done by using an alternative scheduling configuration (e.g. alternative set of LCP / LCH parameters or CG resources) associated with MG, instead of the default scheduling configuration.

[0248] In an example embodiment, the WTRU may receive configuration information and / or parameters including any one or more of the following: measurement configuration, MI / MG configurations, at least a first and a second scheduling configurations, and / or a prioritization criteria / rules. For example, the measurement configuration may include or indicate measurement objects (e.g. SSB, CSI-RS, TRS) and time / frequency measurement info (e.g. SMTC window). For example, the MI / MG configurations may include or indicate parameters, such as start offset, repetition periodicity, MGO length, validity time window. For example, for at least the first and second scheduling configurations, the first configuration may be default (e.g. enabled / activated during configuration) and the second configuration may be associated with measurements and / orMI / MG configuration(e.g. conditionally enabled / activated before / after performing measurements using MG). For example, each scheduling configuration may comprise of a set of LCP / LCH parameters, including priority, PBR, BSD, group of restricted LCHs, resource parameters / restrictions (e.g. restrictions / associations between one or more CG configurations and LCHs, sub-carrier spacing, number of symbols / slots per CG PUSCH, number of CG PUSCH occasions per period). For each parameter, there may be a range of values or min / max that may be allowed to be used per scheduling configuration. For example, the priority value associated with an LCH1 in the second scheduling configuration may be allowed to be within a range [py to px] or use a max value of px. Alternatively, for example, each scheduling configurations may be associated with one or more CG configurations with different set of parameters (e.g. number of CG PUSCH TOs per period, TDRA parameters (e.g. number of symbols / slots), FDRA parameters (e.g. number of resources / resource blocks)). In an example, the second scheduling configuration may be applied only for temporarily prioritizing data in LCHs delayed due to measurements with MI / MG configuration. In another example, the first and second configurations may constitute different sub-configurations of one scheduling configurations (e.g. LCP / LCH parameters or CG resources). The prioritization criteria / rules may possibly be for temporarily prioritizing data / PDUs in buffer delayed due to measurements with MG. For example, the prioritization criteria may indicate that the second scheduling configuration may be applied for prioritization when the data is delayed by a measurement duration of at least by any of x ms, L MGOs, K slots / symbols or number of consecutive grants (e.g. CG PUSCH occasions). For example, when the prioritization criteria is met, the second scheduling configuration may be applied for a duration of no greater than y ms, N slots / symbols or for a duration scaled by a factor associated with the MGO length.

[0249] In an embodiment, the WTRU may receive from higher layers or from another WTRU (over SL) one or more PDUs of PDU sets. The WTRU may select and / or forward the PDUs of the PDU sets to one or more radio bearers (e.g. at SDAP sublayer) and / or to one or more LCHs (e.g. at PDCP sublayer) based on a set of parameters associated with the PDUs and / or PDU sets including importance / priority, arrival time window of the PDUs, payload sizes of the PDUs, QoS of the PDU / PDU set (e.g. PSDB, PSIHI, PSER, PSDD), etc. The WTRU may determine the remaining delay of a PDU set based on the arrival time of the PDUs (e.g. time elapsed since the arrival of the first PDU of a PDU set in an LCH buffer) and the PSDB / PSDD.

[0250] In an embodiment, if any of the data TOs or PUSCH occasions overlap with an MGO in an MI / MG config, the WTRU may determine the data TOs / PUSCHs to be invalid and perform measurements of the configured measurement objects during the MGO.

[0251] In certain example embodiments, a WTRU may determine to temporarily prioritize delayed data after measurements. For example, upon performing measurements, the WTRU may determine to temporarily prioritize the PDUs in the LCHs based on configured criteria using the second scheduling configuration. For example, the WTRU may prioritize the delayed PDUs / PDU sets in the LCH buffers using the second scheduling configuration over any other PDUs / PDU sets that may have arrived after the delayed PDUs / PDU sets before or during the measurements. In an example, if the priority of the initial set of PDUs is 4 (e.g. according to the first scheduling configuration), when the second scheduling configuration is used their priority may be changed to 2, possibly to compensate for the delay due to measurements. In this case, if a new set of PDUs arrive after the initial set of PDUs, the initial set of PDUs may be prioritized and scheduled / multiplexed / transmitted before the new set of PDUs if the priority of the new set of PDUs is lower than the updated priority of the initial set (e.g. less than 2). Otherwise, if the priority of the new set and the updated priority of the initial set is the same, both the new and initial set of PDUs may be prioritized and transmitted together (e.g. both receive the same forwarding treatment).

[0252] In an embodiment, the WTRU may transmit the PDUs upon applying the second scheduling configuration. The WTRU may also transmit an indication indicating temporary prioritization of the delayed PDUs in LCHs (e.g. ID / index of second scheduling configuration or LCHs IDs / indexes) and / or the information on the delayed PDUs (e.g. amount of delay, remaining time). The WTRU may indicate the cause (e.g. ID / index associated with triggering of measurements using MI / MG) for using second scheduling configuration when transmitting the PDUs.

[0253] In an embodiment, the WTRU may subsequently fallback and / or reapply the first scheduling configuration after applying the second scheduling configuration for a set of delayed PDUs / PDU sets in some LCHs for the duration indicated by the prioritization criteria.

[0254] In an example, where the WTRU may be configured with CG configuration (e.g. multi- PUSCH CG configuration), the WTRU may assume the PUSCH TOs overlapping with an MGO in a MG configurationto be invalid and drop the PUSCH TOs. The WTRU may perform measurements during the MGO. For transmitting the data delayed due to measurements with lower latency, a second scheduling configuration may be applied to the PUSCH TOs, where the second scheduling configuration may be associated with different / al ternative set of resources / parameters for the CG configuration (e.g. higher number of PRBs, higher number of PUSCH TOs, higher MCS). In this case, the WTRU may assume the second scheduling configuration for the CG configurationmay be implicitly active when the conditions associated with measurements / data aremet. Alternatively, the WTRU may determine the second configuration for the CG configurationto be active when receiving an indication / signaling (e.g. in DCI, MAC CE).

[0255] In view of the above, according to an example embodiment, a WTRU may receive configuration information. For example, the configuration information may include or indicate any one or more of measurement configuration information, MG configuration information, a first and a second scheduling configuration, and / or prioritization criteria for temporarily prioritizing data delayed due to measurements with MGOs. For example, the measurement configuration information may include or indicate measurement objects (e.g. SSB, CSI-RS) and time / frequency measurement info (e.g. SMTC window). For example, the MG configuration information may include or indicate periodicity of MGOs and MGO length. For example, with the first and a second scheduling configurations, the first configuration may be default and the second configuration may be associated with MG config. For example, each scheduling configuration may include a set of LCP / LCH parameters (e.g. priority, PBR, group of restricted LCHs, resource restrictions). Alternatively, for example, each scheduling configurationmay comprise of one or more CG configurations with different set of parameters (e.g. number of CGPUSCH TOs per period, TDRA parameters, FDRA parameters). For example, the second scheduling configuration may be applied only for temporarily prioritizing data in LCHs delayed due to measurements with MG. With respect to the prioritization criteria for temporarily prioritizing data delayed due to measurements with MGOs, for example, the second scheduling configuration may be applied for prioritization when data is delayed by a measurement duration of at least L MGOs or K slots / symbols or number of consecutive grants (e.g. PUSCH occasions). For example, upon triggering, the second scheduling configuration may be applied for a duration of no greater than N slots / symbols or for a duration scaled by a factor associated with the MGO length.

[0256] In an embodiment, the WTRU may receive, e.g., from higher layers, a set of PDUs of PDU sets. According to an embodiment, if the data transmission occasions (TOs) overlap with an MGO, the WTRU may perform measurements of measurement objects during the MGO, determine to prioritize the PDUs in the LCHs based on configured criteria, and transmit the PDUs upon applying the second scheduling configuration. For example, the WTRU may determine to prioritize the delayed PDUs using the second scheduling configurationover other PDUs that may have arrived later. For example, the WTRU may reapply the first scheduling configurationafter applying the second scheduling configurationfor the duration indicated by the prioritization criteria. For example, the WTRU may transmit an indication indicating temporary prioritization of PDUs in LCHs (e.g. ID / index of second scheduling config). As an example, the WTRU may indicate the cause for using second scheduling configuration.

[0257] FIG. 5 A depicts a diagram according to some embodiments. In an embodiment, a WTRU may be configured with (e.g., may receive configuration information indicating) a first MG configuration associated with one or more MGOs, e.g., MG01 in the example of FIG. 5A, and priority for (e.g., associated with) the first MG configuration. The WTRU may also be configured with (e.g., may receive configuration information indicating) a second MG configuration associated with one or more MGOs, e.g., MG02 in the example of FIG. 5A, and priority for (e.g., associated with) the second MG configuration. Further, the WTRU may be configured with a time offset for receiving a skipping indication, for example, in DCI. As discussed elsewhere herein in more detail, the WTRU may determine to (e.g., whether to) skip measurements in any of the MGOs based receiving the skipping indication and / or the priority values.

[0258] FIG. 5B illustrates an example scenario, according to certain embodiments. In the example of FIG. 5B, the WTRU may determine to skip measurements in MG01, but not skip measurements in MG02, if (e.g., based on) the skipping indication (e.g., received in or via DCI) is received before the time offset and / or if (e.g. based on) the priority of the MG configuration associated with the MG02 is less than the priority of the MG configuration associated with the MG01. Alternatively or additionally, the WTRU may determine to skip measurements in MG01 based on the priority of the MG configuration associated with MG01 being less than a threshold value and / or the priority of the MG configuration associated with MG02 being greater than a threshold value.

[0259] FIG. 5C illustrates another example scenario, according to certain embodiments. In the example of FIG. 5C, the WTRU may determine to skip measurements in both MG01 and MG02 if (e.g., based on) the indication being received before the time offset and / or based on the priority of the MG configuration associated with MG01 and the priority of the MG configuration associated with MG02 both being equal to or less than a threshold value.

[0260] FIG. 6 illustrates an example flow diagram of a method 600 for or relating to measurement gaps or scheduling restrictions to allow measurements, according to some embodiments. The example method 600 of FIG. 6 and accompanying disclosures herein may include, may be based on, or may be a synthesization of various embodiments or elements discussed in detail above.

[0261] For convenience and simplicity of exposition, the example of FIG. 6 may be described with reference to the architecture or system described above with respect to FIGs. 1A-1D, for instance. However, the example method 600 depicted in FIG. 6 may be carried out using different architectures as well. According to some embodiments, the method 600 of FIG. 6 may be performed or implemented by a UE or WTRU, such as the WTRU 102 described in the foregoing.

[0262] It is noted that the method 600 of FIG. 6 may include further steps, procedures or details as discussed in detail elsewhere in this disclosure. As such, the method 600 of FIG. 6 may be modified to include any of the steps, procedures, elements and / or details illustrated and / or discussed in the foregoing or the following. For example, additional details regarding the information, parameters, messages, signaling, configurations, etc. described in FIG. 6 have been discussed in detail above.

[0263] Moreover, it is noted that the method and / or blocks of FIG. 6 may be modified to include, or to be replaced by, any one or more of the procedures, elements or blocks discussed elsewhere herein. As such, one of ordinary skill in the art would understand that FIG. 6 is provided as one example and modifications thereto are possible while remaining within the scope of certain example embodiments.

[0264] As illustrated in the example of FIG. 6, the method 600 may include, at 605, receiving configuration information indicating any of (1) one or more measurement gap (MG) configurations or synchronization signal block (SSB) measurement timing window configurations (SMTCs) (e.g.,. including periodicity of MG occasions (MGOs) and / or MGO length), (2) one or more measurement objects, (3) association information indicating an association between the measurement objects and the MG configurations, and / or (4) physical downlink control channel (PDCCH) monitoring configuration associated with a measurement indication. At 610, the method 600 may include receiving one or more protocol data units (PDUs) of or associated with one or more protocol data unit (PDU) sets and, at 615, receiving a measurement indication in a monitoring occasion.

[0265] In some embodiments, the method 600 may include, at 620, determining at least one slot or occasion for performing the measurements based on information received in the measurement indication and information associated with data in a buffer of the WTRU. For example, the determining of the at least one slot or occasion for performing the measurements may be on condition that (e.g., based on) the measurement indication including an indication to perform, skip or update measurements.

[0266] According to certain embodiments, the method 600 may include, at 625, determining the MG usage and / or transmitting an indication of the MG usage. For example, the determining of the MG usage and / or the transmitting of an indication of the MG usage may be on condition that (e.g., based on) the measurement indication requesting MG usage.

[0267] In some embodiments, the method 600 may include, at 630, determining the MG configuration to use when performing the measurements based on the information received in the measurement indication and the association information. For example, the determining of the MGconfiguration to use may be on condition that (e.g., based on) the measurement indication includes a request for any of measurements and / or a measurement report.

[0268] According to certain embodiments, the method 600 may include, at 635, performing the measurements based on the determined MG configuration and, at 640, transmitting the PDUs.

[0269] In an embodiment, the one or more measurement gap (MG) configurations or synchronization signal block (SSB) measurement timing window configurations (SMTC) may include (an indication of) any of periodicity of MG occasions (MGOs) and / or MGO length. In an embodiment, the PDDCH monitoring configuration may include any of an indication of periodicity, search space (SS) information, and / or start offset of the measurement objects. In an embodiment, PDCCH monitoring occasions may be associated with all or a subset of the MGOs within the MG configuration or SMTCs. In an embodiment, PDCCH monitoring occasions for the measurement indication overlap with connected mode discontinuous reception (CDRX) nonactive periods. In an embodiment, the measurement indication indicates any of an indication to perform measurements in at least one MGO, an indication to skip at least one MGO, an indication to update at least one MGO, a priority value associated with measurements in a MGO, a request for any of measurements and a measurement report, and / or a request for MG usage. In an embodiment, the MG usage may be determined based on any of payload size of the PDUs, remaining time of PDUs in the PDU set, a priority or importance associate with the PDU set, an elapsed time since a last measurement, and / or a reference signal received power (RSRP) of measurements associated with a serving cell.

[0270] According to certain embodiments, a WTRU may receive configuration information that may include one or more MG configurations indicating parameters associated with each MG configuration including any of priority, periodicity of MGOs, and / or MGO length. The configuration information may also include or indicate a time offset for (e.g., associated with) receiving an indication (e.g., in DCI) on whether to skip measurements in an MGO (e.g., time window may be a minimum time in units of slots before the start of an MGO). The WTRU may receive, e.g., from higher layer(s), one or more PDUs. The WTRU may receive an indication (e.g., in DCI) indicating to skip measurements. If the indication to skip measurements is received before the time offset of at least one MGO (e.g., the first MGO), and / or a second MGO overlaps or occurs consecutively after the first MGO, the WTRU may determine to skip measurements in at least one MGO based on the received indication and / or the priority values of the MG configurations associated with the MGOs. For example, the WTRU may determine to skip measurements in the second MGO if the priority of the MG configurationassociated with the second MGO is less than the priority of the MG configurationassociated with the first MGO. As another example, theWTRU may determine to skip measurements in both the first and second MGOs if the priority of the associated MG configurations are equal or below a threshold value. The WTRU may perform measurements in the MGO that is not skipped. The WTRU may transmit PDUs in the occasion(s) associated with the MGO that is skipped.

[0271] FIG. 7 illustrates an example flow diagram of a method 700 for or relating to measurement gaps or scheduling restrictions to allow measurements, according to some embodiments. The example method 700 of FIG. 7 and accompanying disclosures herein may include, may be based on, or may be a synthesization of various embodiments or elements discussed in detail above.

[0272] For convenience and simplicity of exposition, the example of FIG. 7 may be described with reference to the architecture or system described above with respect to FIGs. 1A-1D, for instance. However, the example method 700 depicted in FIG. 7 may be carried out using different architectures as well. According to some embodiments, the method 700 of FIG. 7 may be performed or implemented by a UE or WTRU, such as the WTRU 102 described in the foregoing.

[0273] It is noted that the method 700 of FIG. 7 may include further steps, procedures or details as discussed in detail elsewhere in this disclosure. As such, the method 700 of FIG. 7 may be modified to include any of the steps, procedures, elements and / or details illustrated and / or discussed in the foregoing or the following. For example, additional details regarding the information, parameters, messages, signaling, configurations, etc. described in FIG. 7 have been discussed in detail above.

[0274] Moreover, it is noted that the method and / or blocks of FIG. 7 may be modified to include, or to be replaced by, any one or more of the procedures, elements or blocks discussed elsewhere herein. As such, one of ordinary skill in the art would understand that FIG. 7 is provided as one example and modifications thereto are possible while remaining within the scope of certain example embodiments.

[0275] As illustrated in the example of FIG. 7, the method 700 may include, at 705, receiving configuration information indicating (1) one or more measurement gap configurations respectively associated with at least one measurement gap occasion, and / or (2) a time offset associated with receiving an indication of whether to skip measurements in one or more of the at least one measurement gap occasion. In an embodiment, the method 700 may include, at 710, receiving the indication to skip measurements in the one or more of the at least one measurement gap occasion. In an embodiment, the method 700 may include, based on the indication to skip measurements being received before the time offset, at 715, determining to skip measurements in the one or more of the at least one measurement gap occasion based at least on a priority associated with the one or more measurement gap configurations.

[0276] In an embodiment, the one or more measurement gap configurations indicate any of (1) the priority associated with each of the measurement gap configurations, respectively, (2) a periodicity associated with the at least one measurement gap occasion, and / or (3) a length associated with the at least one measurement gap occasion.

[0277] According to some embodiments, the method 700 may include (although not illustrated in the example of FIG. 7) receiving one or more protocol data units (PDUs), and transmitting the protocol data units (PDUs) in an occasion associated with the one or more of the at least one measurement gap occasion in which the measurements are skipped.

[0278] In an embodiment, the method may include performing the measurements in at least one measurement gap occasion that is not skipped.

[0279] In an embodiment, the at least one measurement gap occasion may include a first measurement gap occasion and a second measurement gap occasion, and the determining at 715 may include determining to skip measurements in the second measurement gap occasion based on the priority of the measurement gap configuration associated with the second measurement gap occasion being less than the priority of the measurement gap configuration associated with the first measurement gap occasion.

[0280] In an embodiment, the at least one measurement gap occasion may include a first measurement gap occasion and a second measurement gap occasion, and the determining at 715 may include determining to skip measurements in the first and second measurement gap occasions based on the priority of the measurement gap configuration associated with the first measurement gap occasion and the priority of the measurement gap configuration associated with the second measurement gap occasion being equal to or below a threshold value.

[0281] In an embodiment, the indication of whether to skip the measurements may be, or may be received in, downlink control information (DCI).

[0282] In an embodiment, the time offset comprises any of a minimum time and / or minimum number of slots before the start of the one or more of the at least one measurement gap occasion.

[0283] Although features and elements are provided above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations may be made without departing from its spirit and scope, as will be apparent to those skilled in the art. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly provided as such. Functionally equivalent methods andapparatuses within the scope of the disclosure, in addition to those enumerated herein, will be apparent to those skilled in the art from the foregoing descriptions. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is to be understood that this disclosure is not limited to particular methods or systems.

[0284] In some example embodiments described herein, (e.g., configuration) information may be described as received by a WTRU from the network, for example, through system information or via any kind of protocol message. Although not explicitly mentioned throughout embodiments described herein, the same (e.g., configuration) information may be pre-configured in the WTRU (e.g., via any kind of pre-configuration methods such as e.g., via factory settings), such that this (e.g., configuration) information may be used by the WTRU without being received from the network.

[0285] Any characteristic, variant or embodiment described for a method is compatible with an apparatus device comprising means for processing the disclosed method, such as with a device comprising a processor configured to process the disclosed method, a computer program product comprising program code instructions and a non-transitory computer-readable storage medium storing program instructions.

[0286] The foregoing embodiments are discussed, for simplicity, with regard to the terminology and structure of infrared capable devices, i.e., infrared emitters and receivers. However, the embodiments discussed are not limited to these systems but may be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves such as acoustic waves.

[0287] It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting. As used herein, the term "video" or the term "imagery" may mean any of a snapshot, single image and / or multiple images displayed over a time basis. As another example, when referred to herein, the terms "user equipment" and its abbreviation "UE", the term "remote" and / or the terms "head mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and / or receive unit (WTRU); (ii) any of a number of embodiments of a WTRU; (iii) a wireless-capable and / or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU; (iii) a wireless-capable and / or wired-capable device configured with less than all structures and functionality of a WTRU; or (iv) the like. Details of an example WTRU, which may be representative of any WTRU recited herein, are provided herein with respect to FIGs. 1 A-1D. As another example, various disclosed embodiments herein supra and infra are described as utilizinga head mounted display. Those skilled in the art will recognize that a device other than the head mounted display may be utilized and some or all of the disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other device may include a drone or other device configured to stream information for providing the adapted reality experience.

[0288] In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and 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 internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0289] Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention. In view of the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are examples only, and should not be taken as limiting the scope of the following claims. For instance, the embodiments provided herein include handheld devices, which may include or be utilized with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.

[0290] Moreover, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices that include processors are noted. These devices may include at least one Central Processing Unit ("CPU") and memory. In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "computer executed" or "CPU executed."

[0291] One of ordinary skill in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. An electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU's operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particularelectrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.

[0292] The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read-Only Memory (ROM)) mass storage system readable by the CPU. The computer readable medium may include cooperating or interconnected computer readable medium, which exist exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods.

[0293] In an illustrative embodiment, any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and / or any other computing device.

[0294] There is little distinction left between hardware and software implementations of aspects of systems. The use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software may become significant) a design choice representing cost versus efficiency tradeoffs. There may be various vehicles by which processes and / or systems and / or other technologies described herein may be effected (e.g., hardware, software, and / or firmware), and the preferred vehicle may vary with the context in which the processes and / or systems and / or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and / or firmware vehicle. If flexibility is paramount, the implementer may opt for a mainly software implementation. Alternatively, the implementer may opt for some combination of hardware, software, and / or firmware.

[0295] The foregoing detailed description has set forth various embodiments of the devices and / or processes via the use of block diagrams, flowcharts, and / or examples. Insofar as such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, it will be understood by those within the art that each function and / or operation within such block diagrams, flowcharts, or examples may be implemented, individually and / or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In an embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors(DSPs), and / or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, may be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and / or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and / or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).

[0296] Those skilled in the art will recognize that it is common within the art to describe devices and / or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and / or processes into data processing systems. That is, at least a portion of the devices and / or processes described herein may be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and / or control systems including feedback loops and control motors (e.g., feedback for sensing position and / or velocity, control motors for moving and / or adjusting components and / or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing / communication and / or network computing / communication systems.

[0297] The herein described subject matter sometimes illustrates different components included within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures may be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components toachieve the same functionality is effectively "associated" such that the desired functionality may be achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated may also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being "operably couplable" to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and / or physically interacting components and / or wirelessly interactable and / or wirelessly interacting components and / or logically interacting and / or logically interactable components.

[0298] With respect to the use of substantially any plural and / or singular terms herein, those having skill in the art can translate from the plural to the singular and / or from the singular to the plural as is appropriate to the context and / or application. The various singular / plural permutations may be expressly set forth herein for sake of clarity.

[0299] It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "includes but is not limited to," etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, where only one item is intended, the term "single" or similar language may be used. As an aid to understanding, the following appended claims and / or the descriptions herein may include usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim including such introduced claim recitation to embodiments including only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and / or "an" should be interpreted to mean "at least one" or "one or more"). The same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of "two recitations," without other modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to "at least oneof A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). In those instances where a convention analogous to "at least one of A, B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, or C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B." Further, the terms "any of' followed by a listing of a plurality of items and / or a plurality of categories of items, as used herein, are intended to include "any of," "any combination of," "any multiple of," and / or "any combination of multiples of the items and / or the categories of items, individually or in conjunction with other items and / or other categories of items. Moreover, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero. And the term "multiple", as used herein, is intended to be synonymous with "a plurality".

[0300] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0301] As will be understood by one skilled in the art, for any and all purposes, such as in terms of providing a written description, all ranges disclosed herein also encompass any and all possible subranges and combinations of subranges thereof. Any listed range can be easily recognized as sufficiently describing and enabling the same range being broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein may be readily broken down into a lower third, middle third and upper third, etc. As will also be understood by one skilled in the art all language such as "up to," "at least," "greater than," "less than," and the like includes the number recited and refers to ranges which can be subsequently broken down into subranges as discussed above. Finally, as will be understood by one skilled in the art, a range includes each individual member. Thus, for example, a group having 1-3 cells refers to groupshaving 1, 2, or 3 cells. Similarly, a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth.

[0302] Moreover, the claims should not be read as limited to the provided order or elements unless stated to that effect. In addition, use of the terms "means for" in any claim is intended to invoke 35 U.S.C. §112, ([ 6 or means-plus-function claim format, and any claim without the terms "means for" is not so intended.

[0303] Although various embodiments have been described in terms of communication systems, it is contemplated that the systems may be implemented in software on microprocessors / general purpose computers (not shown). In certain embodiments, one or more of the functions of the various components may be implemented in software that controls a general-purpose computer.

[0304] In addition, although some example embodiments are illustrated and described herein, the invention is not intended to just be limited to the details shown. Rather, various modifications and variations may be made in the details within the scope and range of equivalents of the claims and without departing from the spirit or scope invention.REFERENCES

[0305] The following references may have been referred to hereinabove, each of which is incorporated herein by reference in its entirety:

[0306] 3GPP TR 38.835 -Technical Specification Group Radio Access Network; NR; Study on XR enhancements for NR (Release 18) (VI.0.0);

[0307] 3GPP TS 38.300 - NR and NG-RAN Overall Description Stage 2, V17.3.0;

[0308] 3GPP TS 38.133, NR Requirements for support of radio resource management, V18.4.0.ABBREVIATIONS AND ACRONYMS

[0309] 6DOF 6 Degrees of Freedom

[0310] ACK Acknowledgement

[0311] ADU Application Data Unit

[0312] AR Augmented Reality

[0313] AS Access stratum

[0314] AM Acknowledgement Mode

[0315] BLER Block Error Rate

[0316] BSR Buffer status report

[0317] BSD Bucket size duration

[0318] BWP Bandwidth Part

[0319] CAP Channel Access Priority

[0320] CAPC Channel access priority class

[0321] CCA Clear Channel Assessment

[0322] CCE Control Channel Element

[0323] CE Control Element

[0324] CG Configured grant or cell group

[0325] CP Cyclic Prefix

[0326] CP-OFDM Conventional OFDM (relying on cyclic prefix)

[0327] CQI Channel Quality Indicator

[0328] CRC Cyclic Redundancy Check

[0329] CSI Channel State Information

[0330] CW Contention Window

[0331] CWS Contention Window Size

[0332] CO Channel Occupancy

[0333] DAI Downlink Assignment Index

[0334] DCI Downlink Control Information

[0335] DFI Downlink feedback information

[0336] DG Dynamic grant

[0337] DL Downlink

[0338] DM-RS Demodulation Reference Signal

[0339] DRB Data Radio Bearer

[0340] eLAA enhanced Licensed Assisted Access

[0341] FDRA Frequency domain resource allocation

[0342] FeLAA Further enhanced Licensed Assisted Access

[0343] FoV Field of View

[0344] FPS Frames per second

[0345] HARQ Hybrid Automatic Repeat Request

[0346] LAA License Assisted Access

[0347] LBT Listen-Before-Talk

[0348] LCP Logical control prioritization

[0349] LCH Logical Channel

[0350] LTE Long Term Evolution e.g. from 3GPP LTE R8 and up

[0351] NACK Negative ACK

[0352] MAC Medium access control

[0353] MCS Modulation and Coding Scheme

[0354] MIMO Multiple Input Multiple Output

[0355] MT Mobile Termination

[0356] MTP Motion-to-photon

[0357] NAS Non-access stratum

[0358] NR New Radio

[0359] NW Network

[0360] OFDM Orthogonal Frequency-Division Multiplexing

[0361] PBR Prioritized bit rate

[0362] PDB Packet Delay Budget

[0363] PHY Physical Layer

[0364] PUCCH Physical Uplink Control Channel

[0365] PUSCH Physical Uplink Shared Channel

[0366] PDSCH Physical Downlink Shared Channel

[0367] PID Process ID

[0368] PO Paging Occasion

[0369] PRACH Physical Random Access Channel

[0370] PSDB PDU set delay budget

[0371] PSDD PDU set delay deadline

[0372] PSS Primary Synchronization Signal

[0373] QFI QoS flow identifier

[0374] RA Random Access (or procedure)

[0375] RACH Random Access Channel

[0376] RAR Random Access Response

[0377] RCU Radio access network Central Unit

[0378] RF Radio Front end

[0379] RLF Radio Link Failure

[0380] RLM Radio Link Monitoring

[0381] RNTI Radio Network Identifier

[0382] RO RACH occasion

[0383] RRC Radio Resource Control

[0384] RRM Radio Resource Management

[0385] RS Reference Signal

[0386] RSRP Reference Signal Received Power

[0387] RSSI Received Signal Strength Indicator

[0388] RLC Radio link control

[0389] RTT Round trip time

[0390] TO Transmission occasion

[0391] SDAP Service data adaptation protocol

[0392] SR Scheduling Request

[0393] SDU Service Data Unit

[0394] SLIV Start and Length Indicator value

[0395] SRS Sounding Reference Signal

[0396] SS Synchronization Signal

[0397] SSS Secondary Synchronization Signal

[0398] SWG Switching Gap (in a self-contained subframe)

[0399] SPS Semi-persistent scheduling

[0400] SUL Supplemental Uplink

[0401] TB Transport Block

[0402] TBS Transport Block Size

[0403] TDRA Time domain resource allocation

[0404] TRP Transmission / Reception Point

[0405] TSC Time-sensitive communications

[0406] TSN Time-sensitive networking

[0407] Uplink

[0408] URLLC Ultra-Reliable and Low Latency Communications

[0409] WBWP Wide Bandwidth Part

[0410] WLAN Wireless Local Area Networks and related technologies (IEEE 8O2.xx domain)

[0411] VR Virtual Reality

[0412] XR Extended Reality.

Claims

CLAIMSWhat is claimed is:

1. A wireless transmit / receive unit (WTRU), comprising: circuitry, including any of a processor, memory, transmitter and receiver, the circuitry configured to receive configuration information indicating (1) one or more measurement gap configurations respectively associated with at least one measurement gap occasion and (2) a time offset associated with receiving an indication of whether to skip measurements in one or more of the at least one measurement gap occasion; receive the indication to skip measurements in the one or more of the at least one measurement gap occasion; and based on the indication to skip measurements being received before the time offset, determine to skip measurements in the one or more of the at least one measurement gap occasion based at least on a priority associated with the one or more measurement gap configurations.

2. The WTRU of claim 1, wherein the one or more measurement gap configurations indicate any of (1) the priority associated with each of the measurement gap configurations, respectively, (2) a periodicity associated with the at least one measurement gap occasion, and (3) a length associated with the at least one measurement gap occasion.

3. The WTRU of any of claims 1-2, configured to: receive one or more protocol data units (PDUs); and transmit the protocol data units (PDUs) in an occasion associated with the one or more of the at least one measurement gap occasion in which the measurements are skipped.

4. The WTRU of any of claims 1-3, configured to perform the measurements in at least one measurement gap occasion that is not skipped.

5. The WTRU of any of claims 1-4, wherein the at least one measurement gap occasion comprises a first measurement gap occasion and a second measurement gap occasion, and the circuitry configured to determine to skip measurements in the second measurement gap occasion based on the priority of the measurement gap configuration associated with the second measurement gap occasion being less than the priority of the measurement gap configuration associated with the first measurement gap occasion.

6. The WTRU of any of claims 1-4, wherein the at least one measurement gap occasion comprises a first measurement gap occasion and a second measurement gap occasion, and the circuitry configured to determine to skip measurements in the first and second measurement gap occasions based on the priority of the measurement gap configuration associated with the first measurement gap occasion and the priority of the measurement gap configuration associated with the second measurement gap occasion being equal to or below a threshold value.

7. The WTRU of any of claims 1-6, wherein the indication of whether to skip the measurements is, or is received in, downlink control information (DCI).

8. The WTRU of any of claims 1-7, wherein the time offset comprises any of a minimum time and / or minimum number of slots before the start of the one or more of the at least one measurement gap occasion.

9. A method, implemented by a wireless transmit / receive unit (WTRU), the method comprising: receiving configuration information indicating (1) one or more measurement gap configurations respectively associated with at least one measurement gap occasion and (2) a time offset associated with receiving an indication of whether to skip measurements in one or more of the at least one measurement gap occasion; receiving the indication to skip measurements in the one or more of the at least one measurement gap occasion; and based on the indication to skip measurements being received before the time offset, determining to skip measurements in the one or more of the at least one measurement gap occasion based at least on a priority associated with the one or more measurement gap configurations.

10. The method of claim 9, wherein the one or more measurement gap configurations indicate any of (1) the priority associated with each of the measurement gap configurations, respectively, (2) a periodicity associated with the at least one measurement gap occasion, and (3) a length associated with the at least one measurement gap occasion.

11. The method of any of claims 9-10, comprising: receiving one or more protocol data units (PDUs); andtransmitting the protocol data units (PDUs) in an occasion associated with the one or more of the at least one measurement gap occasion in which the measurements are skipped.

12. The method of any of claims 9-11, comprising performing the measurements in at least one measurement gap occasion that is not skipped.

13. The method of any of claims 9-12, wherein the at least one measurement gap occasion comprises a first measurement gap occasion and a second measurement gap occasion, and the determining comprises determining to skip measurements in the second measurement gap occasion based on the priority of the measurement gap configuration associated with the second measurement gap occasion being less than the priority of the measurement gap configuration associated with the first measurement gap occasion.

14. The method of any of claims 9-13, wherein the at least one measurement gap occasion comprises a first measurement gap occasion and a second measurement gap occasion, and the determining comprises determining to skip measurements in the first and second measurement gap occasions based on the priority of the measurement gap configuration associated with the first measurement gap occasion and the priority of the measurement gap configuration associated with the second measurement gap occasion being equal to or below a threshold value.

15. The method of any of claims 9-14, wherein the indication of whether to skip the measurements is, or is received in, downlink control information (DCI).

16. The method of any of claims 9-15, wherein the time offset comprises any of a minimum time and / or minimum number of slots before the start of the one or more of the at least one measurement gap occasion.

Images