Assistance for RAN for XR applications
Through WTRU adjusting the CDRX activity duration and the PDB value of network nodes according to the uplink data attributes, the CDRX management problem in XR applications is solved, and the power consumption and delay optimization is achieved, and the application performance is improved.
Patent Information
- Application Number
- CN202380034948.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-28
- Filing Date
- 2023-03-28
- Publication Date
- 2024-11-29
AI Technical Summary
Prior art In extended reality (XR) applications, it is difficult to effectively manage the duration of connection mode discontinuous reception (CDRX) activity in radio area networks (RANs), resulting in high power consumption and latency problems.
The wireless sending/receiving unit (WTRU) can determine and request to extend the duration of CDRX activity based on the attributes of the uplink data, and adjust the packet delay budget (PDB) value of the network node through auxiliary information to optimize the CDRX configuration and reduce power consumption. and delay.
By dynamically adjusting the CDRX configuration, the power consumption and latency of the WTRU are reduced, and the performance and user experience of XR applications are improved.
Smart Images

Figure CN119054352A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 324,463, filed on March 28, 2022, the disclosure of which is incorporated herein by reference in its entirety. Background Art
[0003] Mobile communications using wireless communications continue to evolve. The fifth generation of mobile communications radio access technology (RAT) may be referred to as 5G New Radio (NR). Previous generation (legacy) mobile communications RAT may be, for example, fourth generation (4G) Long Term Evolution (LTE). Summary of the invention
[0004] Systems, methods, and tools for assistance to a Radio Area Network (RAN) for extended reality (XR) applications are described herein.
[0005] A wireless transmit / receive unit (WTRU) may be configured to receive a configuration message from a network node. The configuration message may indicate a connected mode discontinuous reception (CDRX) activity duration (e.g., a first CDRX activity duration), and may indicate that the CDRX activity duration can be extended. The WTRU may determine uplink data (e.g., uplink extended reality media (XRM) data) to be transmitted to the network node. The WTRU may determine a time length for extending the first CDRX activity duration based on an attribute of the uplink XRM data. The WTRU may transmit auxiliary information to the network node. The auxiliary information may indicate a request to extend the first CDRX activity duration by the time length. The WTRU may receive a confirmation message from the network node. The confirmation message may indicate a second CDRX activity duration. The WTRU may receive (e.g., monitor) a physical downlink control channel (PDCCH) transmission during the second CDRX activity duration.
[0006] In various examples, the second CDRX activity duration may be equal to the first CDRX activity duration extended by a requested length of time or a CDRX activity duration different from the first CDRX activity duration extended by a requested length of time. The second CDRX activity duration may be measured relative to one or more of: a number of CDRX cycles, a duration in ms, a duration in symbols, a duration in slots, a duration in subframes, a duration in frames, a start of another CDRX cycle, or a duration indicated by the WTRU.
[0007] In each example, this attribute of this uplink data can indicate that this uplink data includes uplink attitude information.This attribute of this uplink data can indicate motion to photon (MTP) parameter or total round trip time parameter.In each example, this MTP parameter or this total round trip time parameter can be based on configured MTP delay requirement.In each example, this MTP parameter or this total round trip time parameter can be based on the header information included together with this uplink data.In each example, can determine this time length for extending this first CDRX activity duration based on the difference between the remaining time in this MTP parameter and this first CDRX activity duration.
[0008] In each example, the WTRU may also be configured to receive downlink XRM data from the network during the extended CDRX activity duration, wherein the downlink XRM data is received in response to the uplink data. The WTRU may also be configured to transmit the uplink data to the network node during the second CDRX activity duration.
[0009] The network node may be configured to determine an uplink packet delay budget (PDB) value associated with a first quality of service (QoS) flow and a downlink PDB value associated with a second QoS flow. The uplink PDB value and the downlink PDB value may be equal. The network node may determine a packet delay for the first QoS flow and the second QoS flow. The network node may adjust the uplink PDB value and the downlink PDB value based on the packet delay. The network node may modify at least one of a QoS profile, a QoS rule, or a service data flow (SDF) template based on the adjustment.
[0010] In each example, based on the packet delay obtained for the first QoS flow and the second QoS flow, the network node may determine that the uplink PDB value is too low. Based on the uplink PDB value being too low, the network node may increase the uplink PDB value and decrease the downlink PDB value. In each example, based on the packet delay obtained for the first QoS flow and the second QoS flow, the network node may determine that the uplink PDB value is too high. Based on the uplink PDB value being too high, the network node may decrease the uplink PDB value and increase the downlink PDB value. In each example, based on the packet delay obtained for the first QoS flow and the second QoS flow, the network node may determine that the downlink PDB value is too low. Based on the downlink PDB value being too low, the network node may decrease the uplink PDB value and increase the downlink PDB value. In each example, based on the packet delay obtained for the first QoS flow and the second QoS flow, the network node may determine that the downlink PDB value is too high. Based on the downlink PDB value being too high, the network node may increase the uplink PDB value and decrease the downlink PDB value. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented.
[0012] Figure 1B is an example of a method that can be used according to one embodiment. Figure 1A System diagram of an example wireless transmit / receive unit (WTRU) for use within the communication system illustrated in FIG.
[0013] Figure 1C is an example of a method that can be used according to one embodiment. Figure 1A System diagram of an example radio access network (RAN) and an example core network (CN) used within the communication system illustrated in FIG.
[0014] Figure 1D is an example of a method that can be used according to one embodiment. Figure 1A System diagram of yet another example RAN and yet another example CN used within the communication system illustrated in .
[0015] Figure 2 Examples of energy consumption for different WTRU activities are illustrated.
[0016] Figure 3 An example of a DRX cycle is illustrated. A short CDRX cycle and / or a long CDRX cycle may be configured using CDRX parameters.
[0017] Figure 4 An example of a virtual reality (VR) use case is illustrated.
[0018] Figure 5 An example of CDRX timing is illustrated.
[0019] Figure 6 An example of CDRX jitter is illustrated.
[0020] Figure 7 Examples of frame sizes are illustrated.
[0021] Figure 8 An example of uplink / downlink (UL / DL) coordination is illustrated.
[0022] Fig. 9 Examples of one or more goals for power conservation are illustrated.
[0023] Fig.10 An example of power saving for a WTRU is illustrated.
[0024] Fig.11 Examples of transmission options for assistance information from a WTRU are illustrated.
[0025] Fig.12 An example of linked quality of service (QoS) flows for extended reality (XR) / media services is illustrated.
[0026] Fig.13 An example of chained QoS flows using one or more QoS Flow Id (QFI) lists is illustrated.
[0027] Fig.14 An example of a WTRU configured to periodically change the start offset time of CDRX used to align with data reception based on the frame rate applied to the data is illustrated.
[0028] Fig.15 An example of a WTRU is illustrated which changes the on / active duration in a subsequent CDRX cycle when a triggering event is detected during a CDRX cycle. DETAILED DESCRIPTION
[0029] Figure 1A1 is a diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources (including wireless bandwidth). For example, the communication system 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), single carrier FDMA (SC-FDMA), zero tail unique word DFT spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.
[0030] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110 and other networks 112, but it should be understood 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 “STA”) may be configured to send and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.
[0031] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be base transceiver stations (BTS), Node Bs, eNode Bs, Home Node Bs, Home eNode Bs, gNBs, NR Node Bs, site controllers, access points (APs), wireless routers, and the like. While the base stations 114a, 114b are each depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.
[0032] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSC), radio network controllers (RNC), relay nodes, etc. Base station 114a and / or base station 114b may be configured to send and / or receive wireless signals on one or more carrier frequencies (which may be referred to as cells (not shown)). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, a cell associated with base station 114a may be divided into three sectors. Therefore, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to send and / or receive signals in a desired spatial direction.
[0033] 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).
[0034] More specifically, as noted above, the communication 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, etc. 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 use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink (DL) Packet Access (HSDPA) and / or High Speed UL Packet Access (HSUPA).
[0035] In one 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) that may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro).
[0036] In one 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).
[0037] In one 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 WTRUs 102a, 102b, 102c may together implement LTE radio access and NR radio access, for example using dual connectivity (DC) principles. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to / from multiple types of base stations (e.g., eNBs and gNBs).
[0038] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.
[0039] Figure 1A The base station 114b in the example may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one 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 one 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 another 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 a micro-micro cell base station or a femto cell base station. As Figure 1A As shown, base station 114b may have a direct connection to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.
[0040] 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 different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the text, the CN 106 / 115 may be 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 different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Figure 1AAlthough not shown in the figure, 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 utilize NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.
[0041] The CN 106 / 115 may also act 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 a circuit-switched telephone network that provides 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), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired communication networks and / or wireless communication 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 / 113 or a different RAT.
[0042] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication 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 via different wireless links). Figure 1A The illustrated WTRU 102c 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.
[0043] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.
[0044] 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 associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal decoding, 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. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
[0045] The send / receive element 122 may be configured to send a signal to a base station (e.g., base station 114a) or receive a signal from the base station via an air interface 116. For example, in one embodiment, the send / receive element 122 may be an antenna configured to send and / or receive an RF signal. In one embodiment, the send / receive element 122 may be a transmitter / detector configured to send and / or receive, for example, an IR, UV or visible light signal. In another embodiment, the send / receive element 122 may be configured to send and / or receive both an RF signal and an optical signal. It should be understood that the send / receive element 122 may be configured to send and / or receive any combination of wireless signals.
[0046] Although the transmit / receive element 122 Figure 1B Although depicted as a single element in the figure, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
[0047] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. For example, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.
[0048] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an 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 a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
[0049] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power to the other components in the WTRU 102. The power source 134 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, etc.
[0050] 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 from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.
[0051] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (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, etc. Peripheral device 138 may include one or more sensors, which may be one or more of the following: 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.
[0052] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for both UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via hardware (e.g., a choke) or via signal processing performed by a processor (e.g., a separate processor (not shown) or via the processor 118). In an embodiment, the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for both uplink (UL) (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.
[0053] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with one embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.
[0054] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-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 one embodiment, the evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.
[0055] Each of the evolved Node Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.
[0056] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements is depicted as being part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0057] The MME 162 may be connected to each of the evolved Node-Bs 162a, 162b, 162c in the RAN 104 via an S1 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, etc. 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.
[0058] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-evolved Node-B handover, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.
[0059] 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.
[0060] 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 be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts 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 other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers.
[0061] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments, such terminals may (eg, temporarily or permanently) use a wired communications interface with a communications network.
[0062] In a representative embodiment, the other network 112 may be a WLAN.
[0063] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STA) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and going to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and going to a target outside the BSS may be transmitted to the AP to be delivered to the corresponding target. Traffic between STAs within the BSS may be transmitted by the AP, for example, wherein the source STA may transmit traffic to the AP, and the AP may deliver traffic to the target STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Direct link establishment (DLS) may be utilized to transmit point-to-point traffic between the source STA and the target STA (e.g., directly between them). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad-hoc" communication mode.
[0064] When using the 802.11ac infrastructure operation mode or a similar operation mode, the AP may send a beacon on a fixed channel (such as a primary channel). The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a width dynamically set via signaling. The primary channel may be a working channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) may listen to the primary channel. If the primary channel is listened / 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.
[0065] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.
[0066] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz channels and / or 80MHz channels can be formed by combining continuous 20MHz channels. 160MHz channels can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and the data can be sent by sending STA. At the receiver of the receiving STA, the above-mentioned operation for 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC).
[0067] 802.11af and 802.11ah support operating modes below 1GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support instrument type control / machine type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).
[0068] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA (which supports the minimum bandwidth operation mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operation modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (which only supports a 1MHz operation mode) is sending to the AP, the entire available band may be considered busy even if most of the band remains idle and may be available.
[0069] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.
[0070] Figure 1D 1 is a system diagram illustrating the RAN 113 and the CN 115 according to one embodiment. As noted above, the RAN 113 may employ 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.
[0071] 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 one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to send signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to send wireless signals to and / or receive wireless signals from the WTRU 102a. In one embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, gNB 180a may transmit multiple component carriers to 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, 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).
[0072] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with parameter sets that may be scalable. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or Transmission Time Intervals (TTIs) of varying or scalable lengths (e.g., containing varying numbers of OFDM symbols and / or varying absolute time lengths over time).
[0073] 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 a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the evolved Node-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more evolved Node-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the evolved Node-B 160a, 160b, 160c may act as a mobility anchor for the WTRUs 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.
[0074] 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 UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.
[0075] Figure 1DThe illustrated CN 115 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0076] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of services utilized by the WTRU 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 mobile broadband (eMBB) access, services for machine type communication (MTC) access, etc. 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.
[0077] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating WTRU IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.
[0078] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.
[0079] 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 acts 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 other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to local data networks (DNs) 185a, 185b via the UPF 184a, 184b via an N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
[0080] Given that Figures 1A to 1D as well as Figures 1A to 1D Corresponding to the description of the present invention, one or more or all of the functions described herein with reference to one or more of the following may be performed by one or more simulation devices (not shown): WTRU102a-102d, base station 114a-114b, evolved Node B 160a-160c, MME 162, SGW 164, PGW 166, gNB 180a-180c, AMF 182a-182b, UPF 184a-184b, SMF 183a-183b, DN 185a-185b and / or any other device described herein. The simulation device may be one or more devices configured to mimic one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.
[0081] The simulation device may be designed to implement one or more tests of other devices in a laboratory environment and / or in a carrier network environment. For example, one or more simulation devices may perform one or more functions 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. One or more simulation devices may perform one or more functions or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device may be directly coupled to another device for testing purposes and / or may use over-the-air wireless communications to perform testing.
[0082] One or more simulation devices can perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test scenario in a test laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test equipment. Direct RF coupling and / or wireless communication via an RF circuit system (e.g., which can include one or more antennas) can be used by the simulation device to send and / or receive data.
[0083] References to timers herein may refer to a determination of a time or a determination of a time period. References to expiration of a timer herein may refer to a determination that a time has occurred or a time period has expired. References to timers herein may refer to a time, a time period, tracking a time, tracking a time period, etc. References to legacy technology or legacy handover may refer to a legacy technology such as LTE compared to NR, or a legacy version of a technology, for example, an older version / release of a technology (e.g., an older NR release) compared to a newer version / release of the technology (e.g., a newer NR release).
[0084] References herein to specific I-frame types, B-frame types, and P-frame types for video transmission are exemplary frame types. An I-frame may be understood as a frame type that is a reference frame. A reference frame may be a frame of a compressed video that is used to define a future frame. A reference frame may rely on intraframe compression techniques. B-frames and P-frames may be understood as non-reference frames, which may rely on inter-frame decoding using reference frames. A P-frame may be decoded based on a previous I-frame and / or P-frame. A B-frame may be decoded based on a previous I-frame or a future I-frame.
[0085] Systems, methods, and tools for assistance to a Radio Area Network (RAN) for extended reality (XR) applications are described herein.
[0086] A wireless transmit / receive unit (WTRU) may be configured to receive a configuration message from a network node. The configuration message may indicate a connected mode discontinuous reception (CDRX) activity duration (e.g., a first CDRX activity duration), and may indicate that the CDRX activity duration can be extended. The WTRU may determine uplink data (e.g., uplink extended reality media (XRM) data) to be transmitted to the network node. The WTRU may determine a time length for extending the first CDRX activity duration based on an attribute of the uplink XRM data. The WTRU may transmit auxiliary information to the network node. The auxiliary information may indicate a request to extend the first CDRX activity duration by the time length. The WTRU may receive a confirmation message from the network node. The confirmation message may indicate a second CDRX activity duration. The WTRU may receive (e.g., monitor) a physical downlink control channel (PDCCH) transmission during the second CDRX activity duration.
[0087] In various examples, the second CDRX activity duration may be equal to the first CDRX activity duration extended by a requested length of time or a CDRX activity duration different from the first CDRX activity duration extended by a requested length of time. The second CDRX activity duration may be measured relative to one or more of: a number of CDRX cycles, a duration in ms, a duration in symbols, a duration in slots, a duration in subframes, a duration in frames, a start of another CDRX cycle, or a duration indicated by the WTRU.
[0088] In each example, this attribute of this uplink data can indicate that this uplink data includes uplink attitude information.This attribute of this uplink data can indicate motion to photon (MTP) parameter or total round trip time parameter.In each example, this MTP parameter or this total round trip time parameter can be based on configured MTP delay requirement.In each example, this MTP parameter or this total round trip time parameter can be based on the header information included together with this uplink data.In each example, can determine this time length for extending this first CDRX activity duration based on the difference between the remaining time in this MTP parameter and this first CDRX activity duration.
[0089] In each example, the WTRU may also be configured to receive downlink XRM data from the network during the extended CDRX activity duration, wherein the downlink XRM data is received in response to the uplink data. The WTRU may also be configured to transmit the uplink data to the network node during the second CDRX activity duration.
[0090] The network node may be configured to determine an uplink packet delay budget (PDB) value associated with a first quality of service (QoS) flow and a downlink PDB value associated with a second QoS flow. The uplink PDB value and the downlink PDB value may be equal. The network node may determine a packet delay for the first QoS flow and the second QoS flow. The network node may adjust the uplink PDB value and the downlink PDB value based on the packet delay. The network node may modify at least one of a QoS profile, a QoS rule, or a service data flow (SDF) template based on the adjustment.
[0091] In each example, based on the packet delay obtained for the first QoS flow and the second QoS flow, the network node may determine that the uplink PDB value is too low. Based on the uplink PDB value being too low, the network node may increase the uplink PDB value and decrease the downlink PDB value. In each example, based on the packet delay obtained for the first QoS flow and the second QoS flow, the network node may determine that the uplink PDB value is too high. Based on the uplink PDB value being too high, the network node may decrease the uplink PDB value and increase the downlink PDB value. In each example, based on the packet delay obtained for the first QoS flow and the second QoS flow, the network node may determine that the downlink PDB value is too low. Based on the downlink PDB value being too low, the network node may decrease the uplink PDB value and increase the downlink PDB value. In each example, based on the packet delay obtained for the first QoS flow and the second QoS flow, the network node may determine that the downlink PDB value is too high. Based on the downlink PDB value being too high, the network node may increase the uplink PDB value and decrease the downlink PDB value.
[0092] Assistance information may be provided by the WTRU to assist the network. The network or the WTRU may use the assistance information to select between one or more connected mode discontinuous reception (CDRX) configurations. The network or the WTRU may use the assistance information to minimize wasted over-the-air transmissions. The assistance information may be provided by a user plane function (UPF), an access stratum (AS), or a network data analysis function (NWDAF) to assist the network in optimizing the CDRX configuration. A mechanism may be provided for signaling the assistance information from the WTRU to the network. A PDU header (e.g., a new PDU header) in a quality of service (QoS) flow may enable the transmission of the assistance information between the WTRU and the network.
[0093] Mechanisms may be provided for linking QoS flows. Mechanisms may be provided for handling strict round trip time (RTT) requirements for linked QoS flows. Mechanisms may be provided for determining when to send uplink (UL) traffic based on a send (e.g., preferred send) opportunity and QoS characteristics of the QoS flow. Mechanisms may be provided for the WTRU to change the CDRX configuration based on one or more metrics or events. Mechanisms may be provided for the WTRU to select a CDRX configuration (e.g., a new CDRX configuration) based on one or more metrics or events.
[0094] Examples of CDRX may be provided herein. A WTRU (e.g., a typical WTRU) may engage in activities (e.g., several activities) during its normal operation. The activities may be divided into broad categories, such as the following five broad categories: deep sleep; periodic activities in idle mode; periodic activities in connected mode; data transmission and reception; and control channel monitoring (e.g., when in connected mode or when in connected mode during a CDRX activity duration). In each example, control channel monitoring may refer to an activity in which the WTRU may not be engaged in any uplink data transmission or downlink data transmission, but may monitor a control channel (such as a PDCCH transmission) to receive DCI from a RAN node. In each example, control channel monitoring may refer to receiving a PDCCH transmission during an extended activity duration. Examples of DCI include DL scheduling information and / or UL scheduling information. Power consumption studies have shown that the WTRU may consume a large amount of power during this latter activity.
[0095] Figure 2 Examples of energy consumption for different WTRU activities are shown. Figure 2 As shown, control channel monitoring may be responsible for approximately 55% of the WTRU power consumption (even though it may account for less than 10% of the WTRU activity). To address this power consumption, the network may configure connected mode DRX for the WTRU. CDRX may control when the WTRU stops PDCCH monitoring (e.g., for power saving). CDRX may have an on-off cycle during which the WTRU may monitor the PDCCH during the on duration and wherein the WTRU may stop monitoring the PDCCH during the off duration. The network may indicate that DCI may not be transmitted to the WTRU during the off duration of the WTRU. The on duration of the cycle (also referred to as the active time) may be variable. The on duration of the cycle may be extended based on UL activity or DL activity. For some technologies (such as NR), WTRU support for CDRX may be requested, but the activation and configuration of the WTRU may be controlled by the RAN node through RRC signaling. If the RAN node configures CDRX, the RAN node may be considered active and the WTRU may follow CDRX for power saving.
[0096] Figure 3 An example of a discontinuous reception (DRX) cycle is illustrated. The CDRX parameters can be used to configure the short CDRX cycle and the long CDRX cycle. The start time of the on period of the long CDRX cycle and the periodicity of these on periods can be determined by a configurable parameter (drx-LongCycleStartOffset) (in Figure 3 The configurable parameter "Start offset of on period" may allow the RAN node to spread out the on periods of different WTRUs in time. This may provide the RAN node with some flexibility in scheduling these different WTRUs. The short CDRX cycle may have a maximum duration controlled by the short cycle timer. If the short cycle timer expires, a long cycle (e.g., Figure 3 shown between time t0 and time t1).
[0097] The on-period may be provided by the CDRX parameter drx-onDurationTimer. If (e.g., at any time) the WTRU is monitoring DCI and it receives a DL transmission (e.g., a new DL transmission), the WTRU may start or restart an inactivity timer (drx-InactivityTimer). The inactivity timer may be associated with a duration. The duration associated with the inactivity timer may extend the WTRU's activity duration (e.g., as Figure 3 t2). The extended activity duration (e.g., the extended activity time) may allow the WTRU to wake up to receive any potential retransmissions. The extended activity time may (e.g., may also) allow the RAN node to have some flexibility in transmitting additional transport blocks to the WTRU (e.g., because the RAN node may have more than one transport block waiting to be sent to the WTRU). If the activity time is extended, then if a short CDRX cycle is configured, the subsequent cycle may start as a short CDRX cycle. The subsequent cycle may (e.g., alternatively) start as a long CDRX cycle.
[0098] Configuration of the CDRX parameters may allow the RAN node to trade off WTRU power savings versus latency. In various examples, CDRX parameters that result in a large off period may provide significant power savings to the WTRU. However, if the RAN node happens to miss the WTRU active time, the RAN node may wait until the next active time to communicate with the WTRU. If the CDRX parameters are configured to result in a large active time (e.g., by comparison), the RAN node may communicate with the WTRU (e.g., more easily). However, the power saving gains may be minimized. In such a case, if the RAN node knows that there are no additional communications to be made with the WTRU, the RAN node may transmit a control message to the WTRU during the WTRU's active time. The control message may tell the WTRU to shorten the active time and immediately enter the off period. This may be achieved via a MAC CE (e.g., as Figure 3 , as shown at time t3).
[0099] CDRX may be a MAC procedure and may be considered a property of the WTRU. CDRX may not be associated with any specific data radio bearer (DRB) or signaling radio bearer (SRB) that may be configured for the WTRU. CDRX may apply to configured DRBs and SRBs (e.g., to all configured DRBs and SRBs). Configured CDRX parameters may not be coupled to the characteristics of the traffic to and from the WTRU (e.g., tightly coupled).
[0100] The serving cells of the MAC entity may be configured by RRC in a DRX group (e.g., two DRX groups) with DRX parameters (e.g., separate DRX parameters). If DRX groups (e.g., two DRX groups) are configured, each serving cell may be assigned (e.g., uniquely assigned) to any one of the groups (e.g., two groups).
[0101] In addition to the on / off mode (e.g. Figure 3 In addition to the micro-sleep period described in , there may be opportunities for micro-sleep periods. In each example, after the WTRU receives a transport block but fails to decode the transport block, the WTRU may request a retransmission. There may be a delay before the gNB may transmit the retransmission. During this delay, the WTRU may enter micro-sleep. Micro-sleep may be controlled by a timer (e.g., two additional timers, such as a hybrid automatic repeat request (HARQ) RTT timer and a HARQ retransmission timer).
[0102] Table 1 below shows possible values for configurable CDRX parameters:
[0103]
[0104]
[0105] Figure 4 Examples of virtual reality (VR) use cases are illustrated. This article may provide examples of use cases and typical media characteristics. In VR use cases (e.g., Figure 4 As shown), in the case where the WTRU may be a VR headset and in the case where a video feed for the VR headset may be provided by an application server, communications to and from the VR headset may be conducted via a network (e.g., a 5G network).
[0106] An example of a VR use case is described as follows: A user may change posture. In each example, a user may turn his or her head. Posture information may be captured by a sensor. The posture information may be transmitted to an application server as UL information. The application server may process the posture information and generate VR information (e.g., new VR information) for the headset. The VR information generated by the application server may include both video frames and audio frames. The application server may (e.g., may also) generate other user plane data. Video frames, audio frames, and user plane data may be transmitted to the VR headset as downlink information. The VR headset may process the video frames and audio frames that may be provided to the user.
[0107] In an example use case, a VR headset may request and / or use both uplink transmissions and downlink transmissions. Example characteristics of traffic in a VR use case may be one or more of the following:
[0108] - Uplink attitude information: usually small, but periodic (eg, every 4 milliseconds).
[0109] - Downlink video information: Mostly consists of video frames. The frame rate may depend on the quality (e.g., 60 / 90 / 120 frames per second (fps)). The size of the frame may be variable and may be very large. The importance of the frame may be variable—that is, some video frames may be more important than others.
[0110] - Downlink audio information: usually periodic (e.g., every 20 milliseconds), has little variation in size, and is usually small.
[0111] In some cases (e.g., posture information changes), DL transmissions may be triggered by UL transmissions. In order for the end user to have good QoE, there may be latency requirements between the physical movement of the user's head (which may cause changes in posture information (sometimes referred to as motion)) and the updated pictures (sometimes referred to as photons) in the VR headset. There may (e.g., may also) be (e.g., similarly exist) latency requirements between the physical movement of the user's head (motion) and the updated sound waves (sometimes referred to as "sound") reaching the end user's ears from the head-mounted speakers. Example characteristics may be one or more of the following: motion-to-photon latency in the range of 7ms to 15ms, while maintaining the required resolution of up to 8K, giving the user data rates of up to [1Gbit / s]; and motion-to-sound latency of [<20ms].
[0112] Examples of QoS may be provided (e.g., QoS in 5GS). In each example (e.g., in 5GS), the granularity of QoS may be applied per QoS flow. A QoS flow may be the lowest level of granularity within a system (e.g., a 5G system) and may be the location where policies and charging are implemented. QoS parameters and characteristics may be associated with a QoS flow. Each QoS flow may be identified by a QFI, which may be unique within a packet data unit (PDU) session. A RAN node may establish a DRB for each QoS flow, or a RAN node may combine more than one QoS flow into the same DRB. One or more SDFs (e.g., IP flows) may be mapped to a QoS flow. Services within the same QoS flow (e.g., all services) may receive the same treatment.
[0113] QoS characteristics of a QoS flow may include a packet data budget (PDB) and a packet error rate (PER). The PDB may provide (e.g., define) an upper bound on when packets may be delayed between the WTRU and the user plane function (UPF). The PER may provide (e.g., define) an upper bound on the rate of PDUs (e.g., IP packets) that have been processed by a transmitter of a link layer protocol but have not been successfully delivered to upper layers by a corresponding receiver.
[0114] Power saving improvements may be provided. CDRX may be a static configuration procedure. The WTRU may be configured with a single DRX configuration for a serving cell, with an on-cycle, timers, etc. This static configuration may not be suitable for XR / media services. This may lead to at least four problems: timing problems, jitter problems, frame size problems, and UL / DL coordination problems. Enhancements may be necessary to provide assistance to the RAN nodes, minimize the impact of these problems, and maximize power savings for XR / media services.
[0115] Figure 5An example of CDRX timing is illustrated. Improvements for addressing CDRX timing may be provided herein. Figure 5 A VR headset use case with three service data flows (gesture, video, and audio) is shown. The RAN node may map these flows to one or more DRBs. Figure 5 ), it may be assumed that the video frame rate is 60 frames per second (fps), which may result in video frames arriving at the RAN node approximately every 16.67 milliseconds. The RAN node may attempt to match the DRX cycle to this frame rate (e.g., to help avoid video frame delays). However, Table 1 shows that there may not be a DRX cycle that can match this frame rate. Since the granularity of the DRX cycle is every millisecond, a DRX cycle of 16 milliseconds or 17 milliseconds may be defined, but these DRX cycles may result in some frames arriving at the RAN node outside of the WTRU's active time. These video frames may be delayed until a subsequent active time. It should be noted that although shown for 60fps, the same problem may also occur for frame rates of 90fps and 120fps.
[0116] Figure 6 An example of CDRX jitter is illustrated. Improvements for addressing CDRX jitter may be provided herein. Figure 6 A VR headset use case (e.g., the same VR headset use case) with three service data streams (gesture, video, and audio) and a frame rate of 60fps is shown. Video frames may travel from the application server to the UPF over the data network, and travel from the UPF to the RAN node over (e.g., then over) the transport network. Therefore, there may be inherent jitter when the video frames arrive at the RAN node. Some video frames may have an inter-frame timing of less than 16.67 milliseconds, while other video frames may have an inter-frame timing of greater than 16.67 milliseconds. Even if the CDRX cycle matches the video frame rate, the jitter may mean that some video frames may arrive early, while other video frames may arrive late. For the latter case, the video frames may be delayed (e.g., may need to be delayed) and wait for the next activity time.
[0117] Figure 7 Examples of frame sizes are illustrated. Improvements for addressing frame sizes may be provided herein. Figure 7A VR headset use case is shown with three service data streams (gesture, video, and audio) and a frame rate of 60fps (e.g., the same VR headset use case). Video frames may be very large and may have different sizes and importance. The RAN node may transmit these frames over the air interface via multiple over-the-air transmissions. These transmissions (e.g., each of these transmissions) may trigger the WTRU's inactivity timer and extend the WTRU's active time. Extending the WTRU's active time may result in smaller power saving opportunities (e.g., due to an expected shorter DRX cycle to match the frame rate).
[0118] Figure 8 An example of UL / DL coordination is illustrated. Improvements for addressing UL / DL coordination may be provided herein. Figure 8 A VR headset use case is shown with three service data streams (e.g., gesture, video, and audio) and a frame rate of 60fps (e.g., the same VR headset use case). At time t1, the user may turn his or her head, which may cause gesture information to be transmitted to the application server. The transmission may occur in active time 1. The application server may respond with an updated video frame, which may arrive at the RAN node at time t2. The video frame may be delayed (e.g., may need to be delayed) to the next active time (e.g., because the WTRU is no longer in an active time). In each example, the time between the motion (e.g., transmitting the gesture information) and the photon (e.g., displaying the updated video frame) may be greater than the motion-to-photon requirement for these applications.
[0119] It may be possible (e.g., it may be necessary) to define how service data streams are mapped to QoS flows for XR / media services. An XR / media service may be composed of multiple service data streams. The service data stream may be mapped to multiple QoS flows (e.g., based on the expected treatment for these service data flows). It may be possible (e.g., it may be necessary) to define QoS characteristics (e.g., new QoS characteristics) for the XR / media service SDF mapped to the QoS flows. The service data flows of the XR / media service may be tightly coupled (e.g., additionally tightly coupled). In various examples, a UL service data flow carrying posture information may be linked to a downlink service data flow carrying video frame information or audio frame information. It may be possible (e.g., it may be necessary) to define QoS characteristics (e.g., new QoS characteristics) to address these linked QoS flows. If the QoS requirements of one of the linked flows are not met, the behavior of the WTRU and the network may be defined (e.g., it may be necessary).
[0120] Improvements may be provided with respect to UL Active Time. A WTRU may have many reasons to transmit UL traffic. The UL traffic may include user plane data (e.g., posture information), scheduling requests, CSI reports, HARQ ACKs, buffer status reports, power headroom reports, etc. The independent transmission timing of UL traffic in these forms (e.g., each of these forms) may limit the sleep time at the WTRU. It has been proposed that the transmission of UL signals / data may be limited to a time period (referred to as the UL Active Time). By doing so, the WTRU is more likely to enter a deeper sleep. Enhancements may be necessary to provide assistance to the RAN nodes so that the UL Active Time can be efficiently configured.
[0121] Fig. 9 An example of a goal for saving power is illustrated. The basic CDRX cycle may be divided between an on period (or active time) and an off period. A goal to maximize power saving may be to keep the active time as short as possible and to minimize the number of periods in which the active time is extended (e.g., as Fig. 9 ). To achieve these objectives, one or more of the following may be proposed: assistance information provided by the WTRU to assist the network; assistance information provided by the UPF to assist the network to optimize the CDRX configuration; a mechanism for signaling the assistance information from the WTRU to the network; a PDU header in the QoS flow to enable the transmission of assistance information between the WTRU and the network (e.g., a new PDU header); a mechanism for linking QoS flows; a mechanism for handling strict RTT requirements for linked QoS flows; a mechanism for determining when to send UL traffic based on a send opportunity (e.g., a preferred send opportunity) and QoS characteristics of a QoS flow; or a mechanism for the WTRU to change the CDRX configuration or select a CDRX configuration (e.g., a new CDRX configuration) based on one or more metrics or events.
[0122] Regarding assistance information that the WTRU may provide to assist the network, examples of the assistance information may include one or more of the following: power state, group of pictures (GOP) structure, extension of active time, or which QoS flows are linked. In each example, the network may use the assistance information to optimize the CDRX configuration. In each example, the WTRU may use the assistance information to select between one or more CDRX configurations. In each example, the assistance information may be used to minimize wasted air transmissions. Wasted air transmissions may refer to PDU transmissions over the wireless interface (between the WTRU and the RAN node) that are not required or do not match / align with respect to the CDRX configuration used by the WTRU. In each example, the WTRU may fail to receive a video I frame. The WTRU may not need to receive any future video P frames that rely on this I frame as a reference (for example, in this case).
[0123] Auxiliary information may be provided. For example, the auxiliary information may be provided by the UPF to assist the network in optimizing the CDRX configuration. A mechanism may be provided for signaling the auxiliary information from the WTRU to the network. A PDU header in the QoS flow may be provided, which may enable the transmission of auxiliary information between the WTRU and the network. A mechanism may be provided for linking QoS flows. A mechanism may be provided for handling strict RTT requirements for linked QoS flows. A mechanism may be provided for determining when to send UL traffic based on preferred transmission timing and QoS characteristics of the QoS flow. A mechanism may be provided for the WTRU to change the CDRX configuration or select a CDRX configuration based on one or more metrics or events.
[0124] The PDUs associated with a single video frame may be referred to as a burst set or burst of PDUs. These PDUs may arrive at the UPF as a burst, or these PDUs may be generated at the WTRU as a burst. These PDUs may need to (e.g., may need all) be correctly received at the WTRU or UPF. If the PDU is not correctly received at the WTRU or UPF, the video frame that the PDU attempts to convey may not be rendered correctly. This concept may be described in terms of video frames, but it may be applied to any PDU burst that may need to (e.g., need all) be correctly received in order to be useful. These PDUs are sometimes (e.g., also) referred to as PDU sets. A PDU set may consist of one or more PDUs carrying a payload of an information unit (e.g., a frame or video slice for an XRM service) generated at the application layer, and the one or more PDUs may have the same importance requirements at the application layer. The application layer may need PDUs (e.g., all PDUs) in the PDU set to use the corresponding information unit. In each example, if some PDUs are lost, the application layer may (e.g., still) recover parts of the information unit.
[0125] The terms "application server" and "application function" are used interchangeably. Examples of power savings may be provided. In each example, auxiliary information may be provided to the RAN node to allow the RAN node to do one or more of the following: configure CDRX parameters to better match the XR / media service traffic; dynamically change CDRX parameters when conditions for the transmission and reception of XR / media service traffic change; or provide multiple CDRX configurations to the WTRU, each configuration being customized to a specific condition for the transmission and reception of XR / media service traffic. These conditions generally refer to events that are monitored at the WTRU and may be affected by CDRX (e.g., the WTRU moves from battery power to mains / wall power). Some more example conditions are described below.
[0126] Fig.10An example of power saving for a WTRU is illustrated. At 0, it may be assumed that the WTRU is configured with one or more CDRX configurations. The RAN node may make configuration decisions based on QoS profile information received when a PDU session is established or modified. At 1, the WTRU may receive (e.g., from a network node) configuration information for auxiliary information (e.g., via a configuration message). In each example, the configuration information may include thresholds, averaging windows, timers, etc. The configuration may depend on the type of auxiliary information provided by the WTRU. At 2, the WTRU may monitor conditions based on the received configuration information. These conditions may trigger specific events at the WTRU. At 3a, specific conditions (e.g., from set a) may trigger the WTRU to transmit auxiliary information to the network node. This information may allow the RAN node to determine whether it needs to modify the CDRX parameters of the existing configuration, add a new CDRX configuration for the WTRU, or delete the existing configuration. At 3b, the WTRU may receive a new / modified CDRX configuration from the network node. At 4a, a specific condition (e.g., from set b) may trigger the WTRU to autonomously change from one CDRX configuration to another CDRX configuration, or autonomously change a CDRX parameter of a CDRX configuration. At 4b, the WTRU may transmit an indication to the RAN node that it has changed the CDRX configuration or has changed a parameter of the CDRX configuration (e.g., via a request indicating that the CDRX activity duration (e.g., the first CDRX activity duration) is extended by a length of time). The RAN node may then confirm the request (e.g., confirming the extended CDRX activity duration).
[0127] Examples of assistance information provided by a WTRU are described herein. The WTRU may provide assistance information that may be used by a network. The WTRU may monitor one or more metrics or events and transmit one or more types of information signals to the network. In response, the network may take some action. In various examples, the network may do one or more of the following: change the CDRX configuration; change the CDRX configuration within a time period; change the CDRX configuration until another event occurs; configure multiple CDRX configurations; remove PDUs; or change the scheduling of some PDUs. If the WTRU is configured with multiple CDRX configurations, the WTRU may monitor one or more metrics or events and autonomously change from one configured CDRX configuration to another configured CDRX configuration. If a specific event occurs (e.g., the monitored metric is below a threshold), the WTRU may be configured to transmit assistance information, autonomously change from one configured CDRX configuration to another configured CDRX configuration, or change parameters of the CDRX configuration. The WTRU may be configured to (e.g., alternatively) transmit assistance information to the network or periodically change from one configured CDRX configuration to another configured CDRX configuration.
[0128] One type of auxiliary information may be the current power state. The WTRU may provide this information as a percentage of the battery charge or as a relative indication of the battery charge (e.g., good, medium, poor). A threshold may be provided to the WTRU to determine the relative indication. The WTRU may report the power state periodically or based on certain triggering events. In each example, the WTRU may report the power state if the WTRU switches from mains / wall power to battery power, switches from battery power to mains / wall power, or if the power state drops below a first threshold or above a second threshold.
[0129] One type of assistance information may be an indication to the WTRU whether it wants the network to maximize throughput or minimize latency or maximize power savings. The RAN node actions for CDRX may depend on the WTRU preferences. The WTRU may make this determination based on the priority of the traffic, the current battery status, user-provided preferences received through a graphical user interface, etc.
[0130] One type of auxiliary information may be an indication of whether further transmissions on a QoS flow may be temporarily removed. In various examples, the WTRU may fail to decode a video I frame. The WTRU may not be able to decode any P frames or B frames based on the I frame. The WTRU may make this determination based on an indication from an application. The application may inform the PDU layer of the lost I frame. The WTRU may make this determination based on knowledge of which transport blocks carry I frame information. The WTRU may determine that the HARQ transmission of the transport block carrying the I frame data has failed. The WTRU may make this determination based on knowledge of which RLC PDUs carry I frame information. Based on a sequence number, the WTRU may determine that the RLC PDU carrying the I frame information is lost. The WTRU may signal the network to remove future PDUs on a specific QoS flow. The WTRU may specify the removal of a fixed number of future PDUs received on the QoS flow. In various examples, the WTRU may specify the removal of future PDUs received on the QoS flow for a fixed duration. In various examples, the WTRU may specify the removal of future PDUs received on the QoS flow until the next I frame is received on the QoS flow. In various examples, the network may decide to autonomously stop removing PDUs (e.g., if the network receives PDUs as I frames for the QoS flow). In various examples, the WTRU may indicate to the network that PDUs in an identified PDU set (e.g., all PDUs) may be removed, or a signal to the network may indicate that PDUs in a flow of an identified PDU set (e.g., all PDUs) may be removed.
[0131] One type of assistance information may be an indication of whether the WTRU supports multiple CDRX configurations and wants to activate multiple CDRX configurations. This may allow the RAN node to configure multiple concurrent CDRX configurations for the WTRU. The WTRU may signal which QoS flows may be considered as a group for a CDRX configuration.
[0132] One type of auxiliary information may be an indication of how the network should handle traffic from a QoS flow. The WTRU may preferably transmit (e.g., only transmit) downlink traffic for a QoS flow via a single over-the-air transmission. In each example, HARQ layer retransmissions may be too slow for 120fps video traffic. If the initial transmission fails (e.g., in such a case), the WTRU may request that over-the-air HARQ retransmissions not be attempted. In each example, the WTRU may preferably minimize the transmission time of the DL transmission. The indication may signal to the RAN node that the RAN node should attempt to maximize the transport block size to avoid transmitting traffic over multiple transport blocks. In each example, the WTRU may signal how long traffic from a QoS flow may be delayed before being sent to the WTRU. The WTRU may signal these indications as a result of dynamically changing conditions at the WTRU.
[0133] One type of auxiliary information (e.g., uplink extended reality media (XRM) data) may be an indication of the time that the WTRU may remain in active mode. If the power state of the WTRU changes, the WTRU may transmit the indication (e.g., to a network node). In each example, if the WTRU becomes mains / wall powered or the battery state exceeds a (pre-)configured threshold, the WTRU may signal the network that the WTRU may remain in active mode, for example, to facilitate scheduling by a RAN node. If the WTRU has transmitted uplink posture information and an updated video frame can be expected in response, the WTRU may transmit the indication (e.g., uplink XRM data). In order to meet strict motion-to-photon requirements (e.g., in this case), the WTRU may decide not to follow the configured CDRX and remain in active mode. The RAN node may use this information to try to schedule the updated video frame as early as possible. As part of this information, the WTRU may include an indication (e.g., uplink XRM data) about how long the WTRU intends to remain in the awake state (e.g., to extend the CDRX active duration). In various examples, this may be in terms of number of cycles, duration in milliseconds, duration in symbols, duration in time slots, duration in subframes, duration in frames, until the start of the next cycle, or until the WTRU transmits a duration indication (e.g., another indication that the WTRU may resume following the CDRX cycle).
[0134] One type of auxiliary information may be an indication of whether the service of the QoS flow is WTRU driven, server driven, or both. In each example, a WTRU driven flow may not cause a large amount of DL service unless triggered by an uplink transmission. In each example, a server driven flow may not cause a large amount of UL service unless triggered by an uplink transmission. If no uplink transmission can trigger any DL transmission, the RAN node may use this information to maximize power savings. In each example, for the WTRU driven case, the RAN node may configure a DRX configuration (e.g., two DRX configurations) for the WTRU. These DRX configurations may include a first DRX configuration and a second DRX configuration. When DL video service is expected due to uplink activity, the first DRX configuration may be used. When DL video service is not expected, the second DRX configuration may be used. The second DRX configuration may provide the WTRU with more sleep opportunities and power savings. If the auxiliary information indicates that the service is WTRU driven, the WTRU and the RAN node may use the first DRX configuration in the presence of uplink activity and the second DRX configuration in the absence of uplink activity.
[0135] One type of auxiliary information may be an indication of a traffic profile for a QoS flow. In various examples, for video, the WTRU may provide an indication of the size of the GOP (number of frames between consecutive I frames). The WTRU may provide an indication of the GOP structure, such as the number of B frames and P frames between I frames. The WTRU may provide an indication of the frame rate. The WTRU may provide an indication of the size of the I frames, B frames, and P frames.
[0136] One type of auxiliary information may be an indication of which QoS flows are linked (eg, so that activity on one QoS flow may be linked to a second QoS flow).
[0137] One type of auxiliary information may be the observed jitter of the traffic generated by the SDF or QoS flow. The WTRU may monitor the traffic generated on the SDF or QoS flow and may indicate the jitter between the arrival of a frame and the expected arrival of the frame. The indication may be an average of the jitter calculation values within a window. The indication may be calculated at the PMF of the WTRU and may be transmitted to the network (e.g., RAN node, UPF). The RAN node may use the indication to decide to extend the active time. The RAN node may determine that most frames have a jitter of K milliseconds. The RAN node may decide to dynamically change the period start time to compensate, rather than extending (e.g., always extending) the active time.
[0138] A video frame (e.g., a single video frame) may be sent via multiple IP packets. Therefore, the IP packets that make up the video frame may be generated in a burst at the WTRU. A burst of IP packets should be sent to the UPF before the next burst of IP packets.
[0139] The type of assistance information that the WTRU may provide is whether the generated SDF or PDUs of the QoS flow belong to the same burst arrival. The WTRU may mark the PDUs of the burst with an identifier (e.g., all PDUs). The RAN node or UPF may use the identifier to determine to remove specific PDUs of the QoS flow. In various examples, the RAN node or UPF may determine to remove the PDUs (e.g., all PDUs) that may be associated with the identifier (e.g., because an earlier PDU associated with the identifier was not successfully sent and a subsequent PDU may not be useful).
[0140] Examples of assistance information provided by the UPF are described herein. The UPF may transmit at least the following types of assistance information to the base station to assist in CDRX operations.
[0141] The type of auxiliary information may be observed jitter of arriving traffic on the service data flow. The UPF may monitor the arriving traffic on the service data flow and may indicate the jitter between the arrival of a frame and the expected arrival of the frame. The indication may be an average of the jitter calculation values within a window. The indication may be calculated at the PMF of the UPF and may be transmitted to a network RAN node or a WTRU. The RAN node may use the indication to decide to extend the active time. The RAN node may determine (e.g., alternatively determine) that most frames have a jitter of K milliseconds. The RAN node may decide to dynamically change the cycle start time to compensate, rather than extending (e.g., always extending) the active time.
[0142] A single video frame may be sent via multiple IP packets. Thus, the IP packets that make up the video frame may arrive at the UPF in a burst. A burst of IP packets may be sent to the WTRU before the next burst of IP packets. A second type of information that the UPF may provide is whether the arriving service data flow packets belong to the same burst arrival. The UPF may mark the packets of the burst (e.g., all packets) with an identifier. The RAN node may use this indication to remove specific packets of a QoS flow.
[0143] Examples of assistance information provided from an application server or application function are described herein.The application server may transmit at least the following types of assistance information to the network to assist in CDRX operations.
[0144] The first type of assistance information may be an indication of whether the XR application supports multiple CDRX configurations. This may allow the RAN node to configure multiple concurrent CDRX configurations for the WTRU. The application server may signal which QoS flows may be considered as a group for a CDRX configuration.
[0145] One type of auxiliary information may be an indication of how the network should handle traffic from a QoS flow. The application server may signal a preference for transmitting (e.g., only transmitting) downlink traffic for a QoS flow via a single over-the-air transmission. In each example, HARQ layer retransmissions may be too slow for 120fps video traffic. If the initial transmission fails (e.g., in such a case), the XR application may prefer not to attempt over-the-air HARQ retransmissions. In each example, the application server may signal a preference for minimizing the transmission time of DL transmissions. The indication may signal to the RAN node that the RAN node should attempt to maximize the transport block size to avoid transmitting traffic over multiple transport blocks. In each example, the application server may signal how long traffic from a QoS flow may be delayed before being sent to the WTRU.
[0146] One type of auxiliary information may be an indication of whether the service of the QoS flow is WTRU driven, server driven, or both. In each example, a WTRU driven flow may not cause a large amount of DL service unless triggered by an uplink transmission. In each example, a server driven flow may not cause a large amount of UL service unless triggered by an uplink transmission. If there is no uplink transmission that will trigger any DL transmission, the RAN node may use this information to maximize power savings. In each example, for the WTRU driven case, the RAN node may configure a DRX configuration (e.g., two DRX configurations) for the WTRU. These DRX configurations may include a first DRX configuration and a second DRX configuration. If DL video service is expected due to uplink activity, the first DRX configuration may be used. If DL video service is not expected, the second DRX configuration may be used. The second DRX configuration may provide the WTRU with more sleep opportunities and power savings. If the auxiliary information indicates that the service is WTRU driven, the WTRU and the RAN node may use the first DRX configuration in the presence of uplink activity and the second DRX configuration in the absence of uplink activity.
[0147] One type of auxiliary information may be an indication of a traffic profile for a QoS flow. In various examples, for video, the application server may provide an indication of the size of the GOP (the number of frames between consecutive I frames). The application server may provide an indication of the GOP structure, such as the number of B frames and P frames between I frames. The application server may provide an indication of the frame rate. The application server may provide an indication of the distribution of frame sizes (of I frames, B frames, and P frames).
[0148] One type of assistance information may be an indication of which SDFs or QoS flows are linked (eg, so that activity on one service data flow (SDF) or QoS flow may be linked to a second SDF or QoS flow).
[0149] The application server may provide assistance information by calling the NEF API. The NEF API may provide the WTRU with the XRM communication mode and XRM service profile related to the XR / media service. The XRM communication mode and XRM service profile related information may be used by the SMF (e.g., may be used later) to provide assistance to the RAN.
[0150] The procedure for configuring information about the XRM service may be modeled after the external parameter provisioning procedure.
[0151] The input to the NEF API may include one or more of the following: a service identifier; an XRM communication mode associated with the service; or an XRM service profile, which may identify whether the DL service is WTRU driven or server driven. The XRM communication mode may include at least the following information: frame rate, group of pictures (GOP) structure, or frame size distribution. The XRM service profile may indicate whether the UL transmission triggers a DL transmission from the application server. The XRM service profile may be part of the XRM communication mode.
[0152] The UDM may store the XRM communication modes and the XRM service profiles associated with the XRM services. The UDM may classify this information as "SMF associated" (e.g., following the principles of the external parameter provisioning procedure). The SMF may retrieve this information, combine / merge the overlapping parameters for the WTRU, and derive the CN-assisted RAN information. The latter may be communicated to the RAN node, for example, so that it can optimize the Uu resource allocation and CDRX configuration.
[0153] Examples of assistance information provided by a network data analysis function (NWDAF) are described herein. The NWDAF may (e.g., may also) provide assistance information to assist in CDRX operations. The NWDAF may collect information from WTRUs, UPFs, RAN nodes, application servers, and / or other network functions. The NWDAF may (e.g., may then) generate assistance information as an output to provide to the network for assisting in CDRX operations.
[0154] Typical inputs to the NWDAF may include one or more of the following: delay or jitter from the WTRU to the RAN node; delay or jitter from the RAN node to the UPF; delay or jitter from the WTRU to the UPF; delay or jitter from the UPF to the RAN node; delay or jitter from the RAN node to the WTRU; delay or jitter from the UPF to the WTRU; PDU set size (e.g., the number of PDUs in an I frame, the number of PDUs in a B frame, the number of PDUs in a P frame); a measurement of power savings for the WTRU (e.g., the RAN node may provide an indication of the ratio of off time to active time); or the RAN node or WTRU may provide an average number of HARQ transmissions for a transport block.
[0155] Typical outputs of the NWDAF may include one or more of the following: average DL jitter; average PDU set size (e.g., for I-frames, B-frames, and P-frames); GOP structure; or frame rate. These outputs may be transmitted to the RAN node to modify / add / delete the UE's CDRX configuration. These outputs may (e.g., may also) be used by the SMF to change the QoS rules provided to the WTRU, the QoS profile provided to the RAN node, or the SDF template provided to the UPF.
[0156] Examples of new signaling for supporting auxiliary information may be provided herein. Based on the type of information that may be transmitted from the WTRU, the signaling from the WTRU may be enhanced to include one or more of the following: power state; an indication of the WTRU's preference for maximizing throughput, minimizing latency, or maximizing power savings; an indication of temporarily removing packets for a QoS flow; an indication of support for multiple DRX or single DRX; an indication of QoS flows that may be grouped for CDRX configuration; an indication of keep-alive time; GOP information (size and structure); information about linked QoS flows; observed jitter for a QoS flow or SDF; or an indication of whether PDUs belong to the same burst arrival.
[0157] Fig.11 Examples of transmission options for assistance information from a WTRU are illustrated. Assistance information from a WTRU may be transmitted to the network using one or more of the following transmission options. Fig.11Four such options are shown, described further below, including a single action taken by the network (RAN node changes CDRX configuration). This can be extended to other network actions taken at the UPF and / or WTRU.
[0158] In the transmission option, the WTRU may provide certain types of assistance information to (eg, directly to) a RAN node using RRC signaling. These types of assistance information may be mapped to new IEs.
[0159] In the sending option, the WTRU may provide specific types of assistance information to the AMF via NAS signaling. These types of information may be mapped to IEs (e.g., new IEs) in existing NAS-MM messages or new NAS-MM messages.
[0160] In the sending options, the WTRU may provide specific types of auxiliary information to the SMF via NAS signaling. These types of information may be mapped to IEs (e.g., new IEs) in existing NAS-SM messages or new NAS-SM messages. In various examples, the information may be carried in a PDU Session Establishment Request message or a PDU Session Modification Request message. The SMF may provide specific types of information (e.g., PDBs or adjustments to PDBs) to the RAN node via the AMF. In various examples, the SMF may generate a QoS profile (e.g., a new QoS profile) or modify an existing QoS profile based on the information supplied (e.g., PDBs or adjustments to PDBs). The SMF provides (e.g., then provides) the QoS profile to the RAN node via the AMF. In various examples, the SMF may generate QoS rules (e.g., new QoS rules) or modify existing QoS rules based on the information supplied (e.g., PDBs or adjustments to PDBs). The QoS rules are provided (e.g., then provided) to the WTRU via the AMF. In each example, the SMF may generate an SDF template (e.g., a new SDF template) or modify an existing SDF template according to the supplied information (e.g., a PDB or adjustments to a PDB). The SDF template may (e.g., then) be provided to the UPF in an N4 message.
[0161] In the send option, the WTRU may provide certain types of information to an application server or application function over a user plane connection. The application server or application function may use the NEF to provide this information to the PCF, AMF, or SMF—to which entity it is provided depends on the type of information. In various examples, where the information directly affects the CDRX configuration, the information may be provided to the AMF, which may forward the information to the RAN node.
[0162] In order to enable some of the actions that the network may take in response to the type of information provided by the WTRU and UPF, PDU headers (e.g., new PDU headers) in the QoS flow may be required. In various examples, these new headers may include one or more of the following: frame type, priority, SDF ID, or burst identifier.
[0163] For the frame type, an indication may be included as to whether the PDUs carried by the QoS flow are from an I-frame, non-I-frame, B-frame, or P-frame. The WTRU or UPF may make this determination based on an indication carried in the SDF PDU, which may be based on deep packet inspection of the SDF PDU, may be based on known GOP and frame timing, or may be based on the number of SDF PDUs received. For the latter, the WTRU or UPF may assume that I-frames may result in a significantly larger number of SDF PDUs than B-frames and P-frames.
[0164] For priority, an indication of the priority of the PDUs carried by the QoS flow may be included.
[0165] For SDF ID, an identifier for the SDF that generates the PDU and is carried by the QoS flow may be included. The SDF ID may be unique in each QoS flow.
[0166] For the burst identifier, the WTRU and UPF may mark each PDU belonging to a QoS flow of a single frame or a single slice with the same identifier. In various examples, this may be a sequence number. The PDUs of a burst (e.g., all PDUs) may have the same sequence number. The PDUs of the next burst (e.g., all PDUs) may have the next sequence number. The WTRU and UPF may determine the PDUs belonging to the same burst based on an indication carried in the SDF PDU, which may be based on deep packet inspection of the SDF PDU, may be based on a known GOP, or may be based on frame timing.
[0167] Fig.12 Examples of chained QoS flows for XR / media services are illustrated. Examples related to QoS flows for XR / media services may be provided herein. XR / media services may have unique service characteristics and QoS requirements. This mapping of such characteristics and requirements into a QoS model (e.g., a 5G QoS model) may benefit from certain enhancements. In various examples, some SDFs may be chained, where traffic on one flow may trigger traffic on a second flow (e.g., gesture information on SDF1 triggers video information on SDF2, such as Fig.12As shown in FIG. 1 ). Since the traffic on the SDFs (e.g., the two SDFs) may be very different, the flows may be mapped to different QoS flows. The network (e.g., a 5G network) may need to handle the QoS flows (e.g., the two QoS flows) together (e.g., to meet the MTP requirements of XR / media services).
[0168] Each QoS flow may be identified by a QoS flow identifier (QFI), and each QoS flow may be associated with a QoS profile. The WTRU, RAN node, and UPF may use the QoS profile to determine how to handle the PDUs carried in the QoS flow. A QoS flow may be the smallest granularity at which a system (e.g., a 5G system) provides QoS support. The QoS support may be based on the QoS profile associated with the QoS flow. Both the UPF and the WTRU may maintain a mapping of the SDF to the QoS flow.
[0169] Examples of linking QoS flows may be provided. To link one or more SDFs, at least the following examples may be used.
[0170] In the chaining example, the QoS profile may include an indication of the chained QoS profiles (e.g., common to all QoS profiles). In various examples, as shown in the following table, the QoS profile may include a QoS Profile ID (QPI). The chained QoS profiles (e.g., all QoS profiles) may share the same QPI. The network entity may know which QoS flows are chained because these QoS flows may have QoS profiles that share the same QoS Profile ID. The QoS Profile ID may be provided by the SMF to the WTRU in the QoS rules and to the UPF in the QoS implementation rules.
[0171] Table 2 may provide the linking method for the modified QoS profile:
[0172]
[0173] Fig.13 An example of chained QoS flows using a list of QFIs is illustrated. In the chained example, a QoS rule or QoS enforcement rule may have an attribute (e.g., a new attribute) that includes a list of chained QoS flows. Chained QoS flows may be identified by their QFIs. For example, Fig.13 Three QoS flows identified by QFI1, QFI2, QFI3 are shown, where all QoS flows are linked.
[0174] In the chaining example, the QoS rules provided to the WTRU and the SDF template (e.g., PDR or QoS enforcement rules) provided to the UPF may include an indication of the chained SDF. In various examples, the QoS rules may provide the WTRU with a mapping of SDFs to QoS flows. The QoS rules may be extended to include (e.g., also include) a list of chained SDFs for each SDF. The WTRU may (e.g., may then) determine which QoS flows are chained based on the mapping of SDFs to QoS flows and the list of chained SDFs.
[0175] Examples of QoS parameters (e.g., new QoS parameters) in a QoS profile for XR / media services may be provided. A system (e.g., a 5G system) may incorporate QoS to enhance its ability to meet strict QoS requirements for XR / media services. This may improve the system's ability to meet these requirements. These parameters (e.g., additional parameters) may be taken from at least the following.
[0176] The QoS parameters of a QoS flow for an XR / media service may be an indication of the type of service carried by the flow. In various examples, this may be an indication of whether the service in the QoS flow is posture information, audio information, video information, or some other type of information. The type of service may (for example, may also) be represented by a numerical index, where the mapping of the index to the service type may be pre-configured in the system (for example, a 5G system). In the case where the flow carries more than one type of service, the indication may include a list of supported service types. The indication may include (for example, alternatively) the highest priority service type. The reception or transmission of a PDU with a QoS flow ID (QFI) indicating that the service is of a particular type may be any indication of an expected UL service or DL service (for example, an additional UP service or DL service) to the WTRU or base station and may therefore change the CDRX configuration.
[0177] The QoS parameters of a QoS flow for an XR / media service may be an indication of the direction of the traffic carried by the flow. In various examples, this may be an indication of whether the traffic is primarily from WTRU to UPF (UL), from UPF to WTRU (DL), or bidirectional (from WTRU to UPF and from UPF to WTRU).
[0178] The QoS parameter of a QoS flow of an XR / media service may be an indication of the priority of an SDF service carried by the flow or the priority of a type of service carried in the flow. The indication may be an indication of the relative priority (e.g., high, low, medium) of the SDF service or type of service. The indication may (e.g., alternatively) be a numerical indication of priority. In various examples, a higher number may indicate a higher priority, or a lower number may indicate a higher priority.
[0179] The QoS parameter for a QoS flow of an XR / media service may be an indication of the total RTT allowed. In various examples, the indication may refer to the time from a WTRU UL transmission to the receipt of a DL transmission triggered by the WTRU UL transmission. In various examples, the indication may refer to the sum of the PDB for the WTRU UL transmission and the PDB budget for the DL transmission triggered by the WTRU UL transmission. The QoS parameter may be associated with a linked QoS flow.
[0180] The QoS parameter of a QoS flow of an XR / media service may be an indication of a preferred instantaneous block error rate (BLER) or residual BLER for the transport blocks carrying the service data flow.
[0181] The QoS parameters of a QoS flow for an XR / media service may be an indication of how the RAN node may handle over-the-air retransmissions for that QoS flow. In various examples, the QoS parameters may specify a maximum number of over-the-air retransmissions, or the QoS parameters may specify that the RAN node may not allow any over-the-air retransmissions.
[0182] The QoS parameter of a QoS flow of an XR / media service may be an indication of the maximum jitter allowed for the traffic of the QoS flow.
[0183] The QoS parameters of the QoS flow of the XR / Media Service may be an indication of the frame rate and GOP structure of the SDF carrying the video traffic.
[0184] An example of the impact on the round trip time (RTT) of linked QoS flows may be provided. In examples where the XR / media service has linked QoS flows with RTT parameters (e.g., RTT requirements), PDB parameters may be set appropriately for each of the linked QoS flows (e.g., a first QoS flow and a second QoS flow). For example, there may be a PDB (e.g., UL PDB) for UL traffic on (e.g., associated with) one QoS flow (e.g., the first QoS flow), and there may be a PDB (e.g., DL PDB) for DL traffic on (e.g., associated with) a linked QoS flow (e.g., the second QoS flow) that is triggered by uplink traffic. It may be assumed that the RTT parameters are divided equally between the PDBs of the two QoS flows (e.g., the UL PDB associated with the first QoS flow is equal to the DL PDB associated with the second QoS flow).
[0185] It may be advantageous to dynamically change the PDB of linked QoS flows (e.g., dynamically change the UL PDB and / or DL PDB) based on some measured packet delay of each of the linked QoS flows (e.g., the first QoS flow and the second QoS flow). In each example, if the UL packet delay is lower (e.g., always lower) than the PDB of the QoS flow (e.g., the first QoS flow) carrying UL traffic (e.g., the first QoS flow) (e.g., the UL PDB is too high), the network may reduce the PDB of the QoS flow (e.g., the first QoS flow) and may increase the PDB of the linked QoS flow (e.g., the second QoS flow) carrying DL traffic triggered by UL transmission. In each example, if the UL packet delay is higher (e.g., always higher) than the PDB of the QoS flow (e.g., the first QoS flow) carrying UL traffic (e.g., the UL PDB is too low), the network may increase the PDB of the QoS flow (e.g., the first QoS flow) and may reduce the PDB of the linked QoS flow (e.g., the second QoS flow) carrying DL traffic triggered by UL transmission. In various examples, if the DL packet delay is higher (e.g., always higher) than the PDB of the QoS flow carrying the DL service (e.g., the second QoS flow) (e.g., the DL PDB is too low), the network may reduce the UL PDB of the first QoS flow and may increase the PDB of the linked QoS flow carrying the DL service triggered by the UL transmission (e.g., the second QoS flow). In various examples, if the DL packet delay is lower (e.g., always lower) than the PDB of the QoS flow carrying the DL service (e.g., the second QoS flow) (e.g., the DL PDB is too high), the network may increase the UL PDB of the first QoS flow and may reduce the PDB of the linked QoS flow carrying the DL service triggered by the UL transmission (e.g., the second QoS flow).
[0186] The UPF may measure packet delay and may obtain the average packet delay of QoS flow 1 (e.g., the first QoS flow). The measurement may be performed by the PMF in the UPF. The UPF may transmit the average packet delay measurement to the SMF. If the average packet delay is lower than the ULPDB, the SMF may decide to reduce the PDB of QoS flow 1 (e.g., the first QoS flow) and increase the PDB of the linked QoS flow (e.g., QoS flow 2 or the second QoS flow). The UPF or RAN node may determine that some packets of QoS flow 1 exceed the PDB and are removed. The UPF or RAN node may transmit an indication of the number of packets removed. The SMF may decide to increase the PDB of QoS flow 1 and reduce the PDB of the linked QoS flow (QoS flow 2). The WTRU, RAN node, and UPF may be notified of the change in the PDB so that the QoS flows may receive different QoS treatments.
[0187] The WTRU may measure packet delay and may obtain an average packet delay for QoS Flow 3. The measurement may be performed by a PMF in the WTRU. The WTRU may transmit the average packet delay measurement to the SMF via a session management (SM) message. If the average packet delay is below the PDB, the SMF may decide to reduce the PDB of QoS Flow 3 and increase the PDB of the linked QoS flow (QoS Flow 4). The WTRU or RAN node may determine that some packets of QoS Flow 3 exceed the PDB and are removed. The WTRU or RAN node may transmit an indication of the number of removed packets to the SMF. The SMF may decide to increase the PDB of QoS Flow 3 and reduce the PDB of the linked QoS flow (QoS Flow 4). The WTRU, RAN node and UPF may be notified of the change in the PDB so that the QoS flows may receive different QoS treatments. The WTRU may transmit SM messages periodically. If the average packet delay obtained exceeds a (pre) configured threshold, or if the number of removed packets exceeds a (pre) configured threshold, the WTRU may (e.g., alternatively) transmit an SM message. The WTRU may transmit an SM message if requested by the network.
[0188] The WTRU may add a tag (e.g., a new tag) to packets of a QoS flow (e.g., to assist in dynamically changing the PDB of a QoS flow). In various examples, this may include a timestamp of when the packets of the QoS flow were generated. The timestamp may be added to the header of the packet. The WTRU may (e.g., may additionally) include an indication of the obtained average packet delay for the linked QoS flow. The obtained average packet delay may be added to the header of the packet. The RAN node and UPF may use this to change the PDB of the linked QoS flow.
[0189] Information (e.g., additional information) can be added to the PDU header of a chained QoS flow with an RTT requirement (e.g., to help a system (e.g., a 5G system) determine when to remove a PDU that will not meet the RTT parameters associated with these chained QoS flows). Entities (UE, RAN node, or UPF) in a system (e.g., a 5G system) can determine whether a PDU will be able to meet the RTT parameters associated with a chained QoS flow. The RTT parameters can be associated with different PDUs (e.g., two different PDUs). These two different PDUs can be PDU_1 and PDU_2. PDU_1 (“initiating PDU”) can be transmitted through one QoS flow. PDU_2 (“responding PDU”) can be transmitted through a chained QoS flow. For example, a WTRU can transmit PDU_1 at time T1, and the RTT parameter can be set to 15 milliseconds for the chained QoS flow. If PDU_2 arrives at the UPF at time T1 + 16 milliseconds, the PDU may be too late to meet the RTT parameter. Therefore, the system (e.g., a 5G system) may not process the PDU, and the PDU can be removed. To allow entities in a system (e.g., a 5G system) to make this determination, the PDU header can be considered to include the time when the PDU was initially generated, which can be referred to as the round-trip start time (RTStartTime).
[0190] In examples, a WTRU can create PDU_1 for QoS flow 1 at time T1. The WTRU can set the RTStartTime to T1. This time can be included in the PDU header. When PDU_1 arrives at the UPF, the UPF stores the RTStartTime of PDU_1 such that the RTStartTime can be used for PDU_2 through the chained QoS flow. When the UPF receives traffic on the SDF of the chained QoS flow (PDU_2), the UPF can retrieve the stored RTStartTime and can include the RTStartTime in the PDU header. Based on this RTStartTime, an entity (e.g., each entity (WTRU, RAN node, UPF)) can determine how much time the network has left to process PDU_2. That is, the entity can determine the difference between the current time (T2) and the RTStartTime (T1). If T2 - T1 > RTT parameter, the entity can remove the PDU. If T2 - T1 < RTT, the entity can use the difference (RTT - (T2 - T1)) to customize the disposition given to the PDU. If the difference is small, the PDU can receive some preferential disposition.
[0191] In each example, the UPF may create PDU_1 for QoS flow 1 at time T1. The UPF may set RTStartTime to T1. This time may be included in the PDU header. When PDU_1 arrives at the WTRU, the WTRU may store the RTStartTime of PDU_1 such that the RTStartTime may be used for PDU_2 via the linked QoS flow. When the WTRU generates traffic on the SDF of the linked QoS flow (PDU_2), the WTRU may retrieve the stored RTStartTime and may include the RTStartTime in the PDU header. Based on this RTStartTime, an entity (e.g., each entity (WTRU, RAN node, UPF)) may determine how much time the network has reserved for processing PDU_2. That is, if the entity determines the difference between the current time (T2) and the RTStartTime (T1). If T2 - T1 > the RTT parameter, the entity may remove the PDU. If T2 - T1 < RTT, the entity may use the difference (RTT - (T2 - T1)) to customize the disposition given to the PDU. If the difference is small, the PDU may receive some preferred disposition.
[0192] This document may provide examples regarding UL activity times. If the WTRU has a PDU to transmit (e.g., as described herein), the WTRU may associate the PDU with a QoS flow and a 5QI label. Lower layers of the WTRU and the network (e.g., the base station and the UPF) may use the 5QI label to determine what kind of QoS handling the packet may require. Each 5QI may be associated with a PDB. The PDB may define an upper bound on the time for which a packet may be delayed between the N6 termination points at the WTRU and the UPF. The PDB may be used to support scheduling configurations and link layer functions (e.g., setting of scheduling priority weights and HARQ target operating points).
[0193] In system designs (e.g., current 5G systems), the WTRU may send a PDU when the PDU is ready to be transmitted, unless a higher priority PDU is waiting to be transmitted. The WTRU may not buffer (e.g., delay) a PDU unless there is a higher priority PDU in the queue.
[0194] The WTRU may be configured with UL Active Time, which represents a period of time during which the UE may preferably transmit UL data (e.g., as described herein). The DL data may (e.g., may also) be periodic, and when the WTRU may monitor the PDCCH for DL data, the WTRU may be configured with an on-duration or Active Time (e.g., as described herein). It may (e.g., may also) be preferred for the WTRU to send UL data during Active Time. Sending data during Active Time may be preferred because this may reduce the number of WTRU wake-up events. In various examples, sending data during Active Time may reduce the likelihood that the WTRU may need to wake up (e.g., wake up once) to send data and wake up again later to receive data.
[0195] When a PDU is received from upper layers, the WTRU may be configured to delay or buffer the PDU until a preferred transmission opportunity is approaching. Examples of preferred transmission opportunities are the WTRU's UL Active Time and OnDuration.
[0196] The WTRU may use the 5QI that may be associated with the PDU and the amount of time until the next preferred transmission opportunity to determine whether to delay or buffer the packet. In each example, the WTRU may determine not to delay or buffer a PDU associated with a 5QI value of 80 (e.g., because the value 80 indicates a relatively small PDB of only 10 ms).
[0197] In various examples, the WTRU may determine to delay or buffer PDUs associated with a 5QI value of 10 (eg, because a value of 10 indicates a relatively large PDB of only 1100 ms).
[0198] In various examples, when the preferred transmission opportunity is approaching in only 8 ms, the WTRU may determine to delay or buffer the PDUs associated with a 5QI value of 79 (e.g., because the value 79 indicates a PDB of 50 ms). The WTRU may determine that the buffering delay is a sufficiently low percentage of the total PDB.
[0199] In various examples, when the preferred transmission opportunity is approaching within 40 ms, the WTRU may determine not to delay or buffer the PDUs associated with a 5QI value of 79 (e.g., because the value 79 indicates a 50 ms PDB). The WTRU may determine that the buffering delay will be too large as a percentage of the total PDB.
[0200] The WTRU may receive information from the network that may be used by the WTRU to determine how much of the total PDB may be used by the WTRU to buffer a PDU to transmit the PDU at a preferred transmission opportunity. The WTRU may use the information from the network to determine how long a packet may be buffered. The information may be a value indicating a percentage. The information may be received in a NAS-SM container in a PDU SESSION SETUP ACCEPT or PDU SESSION MODIFY message. The information may be associated with a QoS flow (e.g., all QoS flows) for the PDU session, or there may be separate information associated with each QoS rule for the PDU session.
[0201] The WTRU may receive delay measurements from the UPF via PMF signaling. The delay measurements may indicate the delay between the WTRU and the UPF. The WTRU may use these measurements to determine how long the PDU may be buffered. In each example, the WTRU may determine that a PDU whose PDB is 50 ms may be buffered up to 6 ms (e.g., because the delay measurements from the UPF indicate that the PDU may experience a delay of 40 ms between the WTRU and the UPF (e.g., the WTRU may assume that 4 ms may be available for additional margin)).
[0202] An example of CDRX adaptation may be provided. The WTRU may change CDRX parameters or select a CDRX configuration to (re)align with data transmission / reception. In each example, the WTRU may be configured with one or more CDRX configurations that may periodically change parameters associated with the CDRX configuration or select a CDRX configuration (e.g., a new CDRX configuration) based on a realignment periodicity value. The network may configure a first configuration set (e.g., a default / initial CDRX configuration and / or a default parameter set associated with the CDRX configuration) for the WTRU, which the WTRU may initially use upon receiving the configuration (e.g., via a configuration message from a network node). The WTRU may (e.g., may also) be configured with a second configuration set (e.g., an alternative set of CDRX configurations, parameters, and / or parameter values), which the WTRU may periodically change to based on a configured realignment periodicity value. In one or more data streams, the WTRU may use any of the CDRX configurations or CRDX parameters to receive data in the DL or send data in the UL.
[0203] Parameters associated with the CDRX configuration configured in the WTRU may include at least one of: an offset start time slot for starting the CDRX cycle; a CDRX cycle duration; an on / active duration (e.g., the number of time slots / opportunities that the WTRU monitors for PDCCH, and the WTRU may indicate the number of timeslots / opportunities that can be extended); or an inactive duration (e.g., the number of time slots / opportunities that the WTRU remains active after receiving the PDCCH).
[0204] If any of the parameter value and / or CDRX configuration is changed, the WTRU may send an indication to the network indicating at least one of the following: the ID / index of the parameter, the parameter value, or the CDRX configuration. In the event of a confirmation indication received from the network node and / or after the configured duration has expired, the WTRU may use the corresponding parameter. The corresponding parameter may include a second CDRX activity duration. The second CDRX activity duration may be the first CDRX activity duration extended by the requested time length or a CDRX activity duration different from the first CDRX activity duration extended by the requested time length. The corresponding parameter may be an updated parameter (e.g., the extended first CDRX activity duration) or a second CRDX configuration (e.g., a new CRDX configuration with a different CDRX activity duration). If a rejection indication is received from the network, the WTRU may fall back to using the first configuration set (e.g., the default / initial CDRX configuration and / or the default parameter set).
[0205] In various examples, the parameters of the CDRX configuration may be associated with a frame rate corresponding to the data expected to be received or sent by the WTRU. For video data with a frame rate of 60 frames per second (fps), the WTRU may be expected to periodically receive data in the DL with a periodicity value of 1 / 60 or 16.66 ms. In order to receive such video data, the WTRU may be configured with a CDRX configuration having, for example, a parameter with a value of 16 ms for the CDRX cycle duration and a parameter with a value of 2 ms for the on / active duration. If such a CDRX configuration is used, after a number of time slots / opportunities that the WTRU may receive data in the DL during the on / active duration, the CDRX configuration may become misaligned with respect to the frame rate (e.g., possibly due to a non-integer periodicity value corresponding to the frame rate). The WTRU may be configured (e.g., in this case) with a realignment periodicity value of 64 ms or 4 consecutive on / active durations so that the WTRU may periodically change any of these parameters (e.g., offset the starting time slot or the on / active duration) or select a second CDRX configuration (e.g., a new CDRX configuration). The configured realignment periodicity may be based on auxiliary information, such as frame rate.
[0206] Fig.14 An example of a WTRU is illustrated that is configured to periodically change a start offset time of CDRX used to align with data reception based on a frame rate applied to the data. Such a method (e.g., such as Fig.14 ) may allow the WTRU to realign the reception of data with the reception of the frame rate.
[0207] Fig.15 An example of a WTRU is illustrated that changes the CDRX configuration in a subsequent CDRX cycle when a triggering event is detected during a CDRX cycle. The changed CDRX configuration may cause an updated on / active duration. In each example, if a triggering event is detected (e.g., which may be at any time during a CDRX cycle), the WTRU may change parameters associated with a first CDRX configuration (e.g., an initial CDRX configuration) or select a second CDRX configuration (e.g., a new CDRX configuration). The triggering event may include one or more of the following: connectivity / session (re)configuration; receipt of a higher layer / application layer indication; change / update of data flows per application; measurement of jitter; measurement of a radio link; detection of a change in the WTRU's mobility; or detection of a change in power state.
[0208] For connectivity / session (re)configuration, the triggering event may be the reception or sending of any signaling message associated with (re)configuration of RRC connection, RRC state, PDU session and application layer session.
[0209] For receiving a higher layer / application layer indication, the triggering event may be receiving an indication from a NAS layer or application hosted in the WTRU or in a network node (e.g., an attribute of uplink XRM data) indicating one or more of the following changes in the upcoming data in one or more CDRX cycles: motion to photon delay (MTP) parameter; total round trip time parameter; data type (e.g., the upcoming frame changes from a P / B frame to an I frame); higher layer frame failure (e.g., the application layer cannot decode an I frame); service characteristics (e.g., the number of PDUs in an expected PDU set is above / below a threshold, the expected PDB is above / below a threshold, the frame rate increases / decreases); data priority (e.g., the priority value of an expected PDU or PDU set is above / below a threshold); or a QFI or any QoS indication / marking (e.g., the expected QFI value is above / below a threshold).
[0210] For changing or updating the data flows of each application, the triggering event may be the addition of one or more new flows and / or the release of existing flows associated with the application.
[0211] For measurement of jitter, a trigger event may be a measured jitter value (eg, the difference between the expected time slot when data can be expected to be received and the actual time slot when data is received) in one or more data streams being above / below some threshold.
[0212] For measurements on a radio link, the trigger event may be the RSRP, RSRQ, and RSSI measurements of a signal, channel, beam, carrier, link, etc. (e.g., possibly associated with one or more data streams sent / received by the WTRU) being above / below some threshold.
[0213] For detecting a change in the WTRU's movement, a trigger event (e.g., indicated by uplink XRM data) may be whether the uplink XRM data includes uplink attitude information (e.g., orientation information) or whether attitude / positioning measurements (e.g., position information, attitude in 6DoF) are above / below an attitude / position threshold.
[0214] For detecting a change in power state, the triggering event may be a change in power state from mains / wall to battery. The WTRU may limit active time to maximize power savings. For detecting a change in power state, the triggering event may (e.g., may also) be a change in power state from battery to mains / wall. The WTRU may use a second DRX configuration with less power saving opportunities.
[0215] If any of the parameter value and / or CDRX configuration and / or CDRX active time is changed, the WTRU may transmit an indication to the network indicating one or more of: an ID / index of the parameter; a parameter value; a duration (e.g., a first CDRX active time) for extending the CDRX active time; or a CDRX configuration. In the event of receiving an acknowledgement indication from the network and / or after the configured duration has expired, the WTRU may use the corresponding updated parameter. The updated parameter may include a second CDRX active duration. The second CDRX active duration may be the first CDRX active duration extended by the requested time length or a CDRX active duration different from the first CDRX active duration extended by the requested time length. The updated parameter may include a second CDRX configuration (e.g., a new CDRX configuration). If a rejection indication is received from the network, the WTRU may fall back to using the first CDRX configuration (e.g., a default / initial CDRX configuration and / or a default set of parameters). In the network response, the network may indicate the use of a different ID / index of the parameter; a different parameter value; a different duration for extending the CDRX active time, or a different CDRX configuration.
[0216] In various examples, if any change in motion-to-photon (MTP) or RTT latency is detected, the WTRU may change parameters of the CDRX configuration, extend the first CDRX active time, or change to a second CDRX configuration (e.g., a new CDRX configuration). Such MTP latency may be typically measured between the transmission of UL data during a first on / active duration and the reception of DL data (e.g., which may be associated with the UL data) during a second on / active duration.
[0217] In various examples, the network configures the WTRU with one or more CDRX configurations targeting XRM services with MTP latency requirements or RTT latency requirements. The CDRX configuration may allow the WTRU to request the network to extend the CDRX activity time in order to meet the MTP latency (or RTT latency) requirements. The WTRU may (e.g., may also) be configured with the MTP latency (or RTT latency) requirements of the XRM service.
[0218] The WTRU may be configured with a CDRX configuration that allows the WTRU to request the network to extend the CDRX active time. In each example, the WTRU may determine that the uplink XRM data comes from an SDF that requires a low MTP delay. The WTRU may (e.g., may also) determine the expected downlink XRM response in the next K milliseconds based on the configured MTP delay (or RTT delay) requirement. In each example, the WTRU may check the header of the uplink XRM data and determine that the header includes an indication that downlink XRM data is expected in response to the uplink XRM data. The header may (e.g., may also) include an indication that downlink data is expected in the next K milliseconds. The K milliseconds may be referred to as a motion to photon delay (MTP) parameter or a total round trip time parameter. When the MTP parameter is greater than the time remaining in the current CDRX active time, the WTRU may determine to extend the CDRX active duration. The WTRU may determine that it may not be in the CDRX active time in the next K milliseconds and may request to extend the CDRX active time. In each example, the WTRU may determine that the current CDRX Active Time is expected to end in K1 milliseconds and that DL XRM traffic may arrive in K milliseconds (K>K1). The WTRU may request that the CDRX Active Time be extended for a duration of (K-K1) milliseconds (e.g., such that the WTRU is in the CDRX Active Time when DL XRM data is expected).
[0219] In various examples, the network may configure one or more CDRX configurations for the WTRU based on statistical information (e.g., average, standard deviation, minimum, maximum) related to the MTP delay provided by the WTRU in the assistance information (e.g., the attribute of the uplink XRM data is the MTP delay associated with the uplink XRM data), or the WTRU is configured by any of the CN entities (e.g., UPF, AMF, SMF) to the serving base station in the RAN. The WTRU may (e.g., may also) be configured with one or more MTP thresholds associated with the CDRX configuration (e.g., the maximum or minimum delay difference corresponding to the average / expected MTP delay value), which may indicate the effectiveness of using the CRDX configuration when sending and receiving data within the MTP delay.
[0220] The WTRU may initially be configured with a first CDRX configuration (e.g., an initial CDRX configuration) having a CDRX cycle duration of 16 ms (e.g., the time difference between the first time slot and the last time slot in the CDRX cycle is 16 ms), which may span and align with an average MTP latency value of 17 ms. The first CDRX configuration (e.g., the initial CDRX configuration) may allow the WTRU to send UL data in the first time slot of the on / active duration (t1) of the CDRX cycle, transition to sleep mode after the on / active duration times out, and receive DL data in the first time slot of the on / active duration (t1+16 ms) of the subsequent CDRX cycle. If CDRX is configured, the WTRU may determine the MTP latency based on a measurement of the time difference between the transmission and reception of the associated data or based on another indication received from the application / NAS layer. The WTRU may compare the MTP latency measured in the CDRX cycle with the configured threshold to determine whether the CDRX configuration is valid for sending or receiving data in the subsequent CDRX cycle. If the WTRU determines that the MTP delay is above / below the configured MTP threshold, the WTRU may change the parameters of the first CRDX configuration (e.g., the initial CDRX configuration) or select a second CDRX configuration (e.g., a new CDRX configuration) so that data transmission / reception can be aligned with the determined MTP delay.
[0221] In various examples, the WTRU may know the expected frame type (I, B, P) based on an indication from higher layers. If a failed transport block occurs on an I frame, or if higher layers indicate a failed I frame reception, the WTRU may stop processing future receptions from the data radio bearer until an indication is received from higher layers that the next I frame is expected. The WTRU may (e.g., may additionally) notify the RAN node that future transmissions on the radio bearer may be suspended.
[0222] Although the above features and elements are described in particular combinations, each feature or element may be used alone without the other features and elements of the preferred embodiments, or in various combinations with or without the other features and elements.
[0223] Although the implementations described herein may consider 3GPP specific protocols, it should be understood that the implementations described herein are not limited to such scenarios and are applicable to other wireless systems. For example, although the solutions described herein consider LTE, LTE-A, New Radio (NR) or 5G specific protocols, it should be understood that the solutions described herein are not limited to such scenarios and are also applicable to other wireless systems.
[0224] The processes described above may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (sent via wired and / or wireless connections) and / or computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as, but not limited to, built-in hard disks and removable disks), magneto-optical media, and / or optical media (such as compact disk (CD)-ROM disks and / or digital versatile disks (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for a WTRU, terminal, base station, RNC, and / or any host computer.
Claims
1. A wireless transmit / receive unit (WTRU), the wireless transmit / receive unit (WTRU) comprising: A processor, the processor being configured to: receiving a configuration message from a network node, wherein the configuration message indicates a first connected mode discontinuous reception (CDRX) activity duration and indicates that the first CDRX activity duration can be extended; determining uplink data to be transmitted to the network node; determining, based on attributes of the uplink data, a length of time for extending the first CDRX activity duration; transmitting assistance information to the network node, wherein the assistance information indicates a request to extend the first CDRX activity duration by the time length; receiving a confirmation message from the network node, wherein the confirmation message indicates a second CDRX activity duration; as well as A Physical Downlink Control Channel (PDCCH) transmission is received during the second CDRX activity duration.
2. The WTRU of claim 1 , wherein the uplink data is uplink extended reality media (XRM) data.
3. The WTRU of claim 1 , wherein the second CDRX Active Duration is equal to: The first CDRX activity duration extended by the requested length of time, or a CDRX activity duration different from the first CDRX activity duration extended by the requested length of time.
4. A WTRU according to claim 1, wherein the second CDRX activity duration is measured relative to one or more of the following: the number of CDRX cycles, the duration in ms, the duration in symbols, the duration in time slots, the duration in subframes, the duration in frames, the start of another CDRX cycle, or the duration indicated by the WTRU.
5. The WTRU of claim 1 , wherein the processor is further configured to receive downlink XRM data from the network during the extended CDRX activity duration, wherein the downlink XRM data is received in response to the uplink data.
6. The WTRU of claim 1, wherein the attribute of the uplink data indicates that the uplink data includes uplink posture information.
7. The WTRU of claim 1, wherein the attribute of the uplink data indicates a motion-to-photon (MTP) parameter or a total round-trip time parameter.
8. The WTRU of claim 7, wherein the MTP parameter or the total round trip time parameter is based on a configured MTP latency requirement.
9. The WTRU of claim 7, wherein the MTP parameter or the total round trip time parameter is based on header information included with the uplink data.
10. The WTRU of claim 7, wherein the length of time for extending the first CDRX Active Duration is determined based on a difference between the MTP parameter and a time remaining in the first CDRX Active Duration.
11. The WTRU of claim 1 , wherein the processor is further configured to: The uplink data is transmitted to the network node during the second CDRX activity duration.
12. A method implemented in a wireless transmit / receive unit (WTRU), the method comprising: receiving a configuration message from a network node, wherein the configuration message indicates a first connected mode discontinuous reception (CDRX) activity duration and indicates that the first CDRX activity duration can be extended; determining uplink data to be transmitted to the network node; determining, based on attributes of the uplink data, a length of time for extending the first CDRX activity duration; transmitting assistance information to the network node, wherein the assistance information indicates a request to extend the first CDRX activity duration by the time length; receiving a confirmation message from the network node, wherein the confirmation message indicates a second CDRX activity duration; as well as A Physical Downlink Control Channel (PDCCH) transmission is received during the second CDRX activity duration.
13. The method of claim 12, wherein the uplink data is uplink extended reality media (XRM) data.
14. The method of claim 12, wherein the second CDRX activity duration is equal to: The first CDRX activity duration extended by the requested length of time, or a CDRX activity duration different from the first CDRX activity duration extended by the requested length of time.
15. The method of claim 12, wherein the second CDRX activity duration is measured relative to one or more of: the number of CDRX cycles, the duration in ms, the duration in symbols, the duration in time slots, the duration in subframes, the duration in frames, the start of another CDRX cycle, or a duration indicated by the WTRU.
16. The method according to claim 12, further comprising: Downlink XRM data is received from the network during the extended CDRX activity duration, wherein the downlink XRM data is received in response to the uplink data.
17. The method of claim 12, wherein the attribute of the uplink data indicates that the uplink data includes uplink posture information.
18. The method of claim 12, wherein the attribute of the uplink data indicates a motion-to-photon (MTP) parameter or a total round-trip time parameter.
19. The method of claim 18, wherein the MTP parameter or the total round trip time parameter is based on a configured MTP latency requirement.
20. The method of claim 18, wherein the MTP parameter or the total round trip time parameter is based on header information included with the uplink data.
21. The method of claim 18, wherein the length of time for extending the first CDRX activity duration is determined based on a difference between the MTP parameter and a time remaining in the first CDRX activity duration.
22. The method according to claim 12, further comprising: The uplink data is transmitted to the network node during the second CDRX activity duration.
23. A network node for managing QoS flows, the network node comprising: A processor, the processor being configured to: determining an uplink packet delay budget (PDB) value associated with a first quality of service (QoS) flow and a downlink PDB value associated with a second QoS flow, wherein the uplink PDB value is equal to the downlink PDB value; determining a packet delay for the first QoS flow and the second QoS flow; adjusting the uplink PDB value and the downlink PDB value based on the packet delay; as well as At least one of a QoS profile, a QoS rule, or a service data flow (SDF) template is modified based on the adjustment.
24. The network node of claim 23, wherein the processor is further configured to: determining, based on the packet delays obtained for the first QoS flow and the second QoS flow, that the uplink PDB value is too low; and Based on the uplink PDB value being too low, the uplink PDB value is increased and the downlink PDB value is decreased.
25. The network node of claim 23, wherein the processor is further configured to: determining that the uplink PDB value is too high based on the packet delays obtained for the first QoS flow and the second QoS flow; and Based on the uplink PDB value being too high, the uplink PDB value is decreased and the downlink PDB value is increased.
26. The network node of claim 23, wherein the processor is further configured to: determining, based on the packet delays obtained for the first QoS flow and the second QoS flow, that the downlink PDB value is too low; and Based on the downlink PDB value being too low, the uplink PDB value is decreased and the downlink PDB value is increased.
27. The network node of claim 23, wherein the processor is further configured to: determining, based on the packet delays obtained for the first QoS flow and the second QoS flow, that the downlink PDB value is too high; and Based on the downlink PDB value being too high, the uplink PDB value is increased and the downlink PDB value is decreased.
