Semi-persistent scheduling configuration including timer configuration

Abstract

Aspects of the present disclosure relate to providing efficient support for multiple traffic flows (e.g., data traffic flows) for various applications, such as augmented reality applications. Different traffic flows of the plurality of traffic flows may have different characteristics, such as different quality of service characteristics. A network entity, such as a base station, transmits a semi-persistent scheduling (SPS) configuration to one or more other devices, such as user equipment, in a wireless communication system. The SPS configuration includes one or more discontinuous reception (DRX) timer configurations that can be set by the network entity according to any characteristic of the one or more traffic flows. The network entity selects one or more timers and appropriate values for these timers based on characteristics of the one or more traffic flows to configure the SPS to support requirements of the one or more traffic flows.

Description

[0001] Related Applications

[0002] This application claims priority to U.S. patent application serial number 63 / 407,015, filed on September 15, 2022, entitled “Semi-persistent Scheduling Configurations Including Timer Configurations,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to wireless communications, and more particularly to including timer configurations in semi-persistent scheduling (SPS) configurations. Background Art

[0004] A wireless communication system may include one or more network communication devices (such as a base station), which may also be referred to as an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as a user equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of a wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0005] Devices in a wireless communication system can communicate with each other using various types of scheduling, one type of which is SPS. SPS refers to communicating using resources allocated to devices for a specific amount of time, and that amount of time is repeated at a regular or set periodic rate. Summary of the invention

[0006] The present disclosure relates to methods, devices, and systems that support SPS configurations including timer configurations. The techniques discussed herein provide efficient support for multiple service flows (e.g., data service flows) for various applications, such as extended reality (XR) applications. A network entity (such as a base station) sends an SPS configuration to one or more other devices (such as one or more UEs). These SPS configurations are optionally specific to XR. The SPS configuration includes one or more discontinuous reception (DRX) timer configurations, which the network entity can set based on the quality of service (QoS) or other characteristics of the corresponding service flow. By applying a DRX timer configuration specific to the SPS configuration, the network can efficiently support multi-stream XR applications using a single (e.g., common) DRX scheme.

[0007] Some implementations of the methods and apparatus described herein may also include: receiving first signaling indicating a downlink semi-persistent scheduling (SPS) configuration from a network entity, wherein the downlink SPS configuration includes a timer configuration set; receiving second signaling indicating a physical downlink shared channel (PDSCH) from the network entity at an SPS transmission timing of the downlink SPS configuration; and in response to receiving the PDSCH at the SPS transmission timing, starting a first timer set according to a corresponding timer value of the timer configuration set.

[0008] In some implementations of the methods and devices described herein, a timer configuration set includes: a discontinuous reception (DRX) retransmission timer and a DRX hybrid automatic repeat request (HARQ) round trip time (RTT) timer. Additionally or alternatively, starting the first timer is to start the DRX HARQ timer configured in the SPS configuration in the first symbol after the end of the corresponding transmission carrying the downlink HARQ feedback for the PDSCH. Additionally or alternatively, the timer configuration set includes a DRX inactive timer. Additionally or alternatively, starting the first timer is to start the DRX inactive timer in response to receiving the PDSCH on the SPS transmission opportunity. Additionally or alternatively, the timer configuration set includes a DRX on duration timer. Additionally or alternatively, the method and device also start the DRX on duration timer for each SPS transmission opportunity of the downlink SPS configuration. Additionally or alternatively, the method and device also regard the SPS transmission opportunity of the downlink SPS configuration as the DRX active time, and monitor the physical downlink control channel (PDCCH) at each SPS transmission opportunity. Additionally or alternatively, the SPS cycle includes multiple SPS transmission opportunities, and the method and apparatus further allocate a HARQ process identifier for each SPS opportunity within the SPS cycle based at least in part on the number of SPS transmission opportunities included in the SPS cycle and the current SPS transmission opportunity. Additionally or alternatively, the first signaling includes radio resource control signaling. Additionally or alternatively, the apparatus includes a user equipment.

[0009] Some implementations of the methods and apparatus described herein may further include: sending a first signaling indicating a downlink SPS configuration to a UE network entity, wherein the downlink SPS configuration includes a timer configuration set; and sending a second signaling indicating a PDSCH to the UE at an SPS transmission timing of the downlink SPS configuration.

[0010] In some implementations of the methods and apparatus described herein, a timer configuration set includes: a DRX retransmission timer and a DRX HARQ RTT timer. Additionally or alternatively, the timer configuration set includes a DRX inactivity timer. Additionally or alternatively, the timer configuration set includes a DRX on-duration timer. Additionally or alternatively, a plurality of SPS transmission opportunities are included in the SPS cycle, and for each SPS opportunity within the SPS cycle, a HARQ process identifier is assigned to the SPS opportunity based at least in part on the number of SPS transmission opportunities included in the SPS cycle and the current SPS transmission opportunity. Additionally or alternatively, the first signaling includes radio resource control signaling. Additionally or alternatively, the apparatus includes a base station. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1An example of a wireless communication system supporting SPS configuration including timer configuration according to aspects of the present disclosure is illustrated.

[0012] Figure 2 An example of multi-stream XR utilizing DRX and SPS is illustrated.

[0013] Figure 3 An example flow of operations performed by a MAC entity when DRX is configured is illustrated.

[0014] Figure 4 An example of an SPS configuration information element (IE) supporting SPS configuration including timer configuration according to aspects of the present disclosure is illustrated.

[0015] Figure 5 An example of using a DRX inactivity timer supporting an SPS configuration including a timer configuration according to aspects of the present disclosure is illustrated.

[0016] Figure 6 and Figure 7 An example of an SPS configuration IE supporting SPS configuration including timer configuration according to aspects of the present disclosure is illustrated.

[0017] Figure 8 and Fig. 9 An example of a block diagram of a device supporting SPS configuration including timer configuration according to aspects of the present disclosure is illustrated.

[0018] Figures 10 to 13 A flow chart of a method for supporting SPS configuration including timer configuration according to aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0019] The present disclosure relates to methods, apparatus, and systems that support SPS configurations including timer configurations. The techniques discussed herein provide efficient support for multiple service flows (e.g., data service flows) for various applications (such as XR applications). Different service flows in these multiple service flows may have different characteristics, such as different QoS characteristics. A network entity (such as a base station) sends an SPS configuration to one or more other devices (such as one or more UEs) in a wireless communication system. The SPS configuration includes one or more DRX timer configurations, and the network entity may set the DRX timer configuration for the UE based on any characteristics of the one or more service flows.

[0020] The DRX timer configuration includes a timer value for each of the one or more timers at the UE. For example, the timers may include one or more of the following: a DRX retransmission timer, a DRX HARQ RTT timer, a DRX inactivity timer, and a DRX on duration timer. The network entity selects one or more timers and appropriate values ​​for these timers based on the characteristics of one or more service flows to basically configure the SPS to support the requirements of one or more service flows.

[0021] For some services, such as XR services, an application may consist of multiple service (e.g., data) flows with different service characteristics. If a single DRX configuration matching one flow does not meet the packet delay budget (PDB) of other flows, one solution for supporting such services is to use multiple simultaneous DRX configurations, where each DRX configuration matches a service flow. Such a solution would be suitable for achieving both high UE energy saving gains and many satisfied UEs. However, implementing multiple simultaneously active DRX configurations comes at the cost of higher complexity and further enhancements are also needed.

[0022] Another solution for supporting such services is that when a single DRX configuration is used, SPS can be used to help schedule transmissions corresponding to different service flows in a timely manner. However, applying the same DRX configuration or timer value for each SPS configuration does not allow the DRX configuration to match the characteristics of different service flows. For example, the DRX configuration may allow for packet delays that exceed the PDB of one of the flows.

[0023] Using the techniques discussed herein, SPS configuration-specific DRX timer configurations allow the network to efficiently support multi-stream services, such as XR applications, using a single (e.g., common) DRX scheme. This allows for the same power efficiency or the same energy savings gains as using a single DRX configuration, but can accommodate different characteristics of different streams. Furthermore, this avoids the complexity of implementing multiple simultaneous DRX configurations.

[0024] Aspects of the disclosure are described in the context of a wireless communication system.Aspects of the disclosure are also illustrated and described with reference to device diagrams and flow diagrams.

[0025] Figure 1An example of a wireless communication system 100 that supports an SPS configuration including a timer configuration according to aspects of the present disclosure is illustrated. The wireless communication system 100 may include: one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technologies, including the Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G. Additionally, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0026] One or more network entities 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN), a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terms. The network entity 102 and the UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, the network entity 102 and the UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0027] The network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, the network entity 102 and the UE 104 may support wireless communications of signals associated with services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, the network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0028] One or more UEs 104 may be dispersed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, a subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, a station, a terminal, or a client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc. In some implementations, UE 104 may be stationary in the wireless communication system 100. In some other implementations, UE 104 may be mobile in the wireless communication system 100.

[0029] One or more UEs 104 may be devices in different forms or with different capabilities. Figure 1 Some examples of UE 104 are illustrated in FIG. Figure 1 As shown, the UE 104 may be able to communicate with various types of devices, such as a network entity 102, other UEs 104, or a network device (e.g., a core network 106, a packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network device). Additionally or alternatively, the UE 104 may support communication with other network entities 102 or UEs 104 that may act as relays in the wireless communication system 100.

[0030] The UE 104 may also be capable of supporting wireless communications directly with other UEs 104 via a communication link 114. For example, the UE 104 may support wireless communications directly with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, the UE 104 may support wireless communications directly with another UE 104 via a PC5 interface.

[0031] The network entity 102 may support communication with the core network 106 or with another network entity 102 or both. For example, the network entity 102 may be connected to the core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2 or another network interface). The network entities 102 may communicate with each other via the backhaul links 116 (e.g., via X2, Xn or another network interface). In some implementations, the network entities 102 may communicate directly with each other (e.g., between the network entities 102). In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities (which may be referred to as radio heads, smart radio heads, or transport reception points (TRPs)).

[0032] In some implementations, the network entity 102 can be configured in a decomposed architecture, which can be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 102 can include one or more of the following: a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near real-time RIC (near RTRIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) system, or any combination thereof.

[0033] The RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). In a decomposed RAN architecture, one or more components of the network entity 102 may be co-located, or one or more components of the network entity 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0034] The functional split between CU, DU and RU can be flexible, and different functions can be supported according to the functions performed at the CU, DU or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof). For example, a functional split of the protocol stack can be adopted between the CU and the DU, so that the CU can support one or more layers of the protocol stack and the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host high-level protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can be connected to one or more DUs or RUs, and one or more DUs or RUs can host lower protocol layers, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, media access control (MAC) layer) functions and signaling, and each DU or RU can be at least partially controlled by the CU.

[0035] Additionally or alternatively, a functional split of the protocol stack may be employed between the DU and the RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and the DU or between the DU and the RU may be within the protocol layer (e.g., some functions for the protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by different items of the CU, DU, or RU).

[0036] The CU may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU may be connected to one or more DUs via a medium-range communication link (e.g., F1, F1-c, F1-u), and the DU may be connected to one or more RUs via a fronthaul communication link (e.g., an open fronthaul (FH) interface). In some implementations, the medium-range communication link or the fronthaul communication link may be implemented according to interfaces (e.g., channels) between layers of a protocol stack supported by a corresponding network entity 102 communicating via such a communication link.

[0037] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., mobility management entity (MME), access and mobility management function (AMF)), and user plane entities that route packets or interconnections to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with the core network 106.

[0038] The core network 106 may communicate with the packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. The UE 104 may establish a session (e.g., a protocol data unit (PDU) session, etc.) with the core network 106 via the network entity 102. The core network 106 may use the established session (e.g., the established PDU session) to route traffic (e.g., control information, data, etc.) between the UE 104 and the application server 118. The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106).

[0039] In the wireless communication system 100, the network entity 102 and the UE 104 may use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, the network entity 102 and the UE 104 may support different resource structures. For example, the network entity 102 and the UE 104 may support different frame structures. In some implementations, such as in 4G, the network entity 102 and the UE 104 may support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, the network entity 102 and the UE 104 may support various frame structures (i.e., multiple frame structures). The network entity 102 and the UE 104 may support various frame structures based on one or more digital technologies.

[0040] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefixes. A first digital technology (e.g., μ = 0) may be associated with a first subcarrier spacing (e.g., 15kHz) and a conventional cyclic prefix. A first digital technology (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15kHz) may utilize one slot per subframe. A second digital technology (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30kHz) and a conventional cyclic prefix. A third digital technology (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60kHz) and a conventional cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ = 3) may be associated with a fourth subcarrier spacing (e.g., 120kHz) and a conventional cyclic prefix. A fifth digital technology (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240kHz) and a conventional cyclic prefix.

[0041] The time intervals of resources (e.g., communication resources) can be organized according to frames (also referred to as radio frames). Each frame can have a duration, for example, a duration of 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, a duration of 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0042] Additionally or alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols). In some implementations, the number (e.g., quantity) of time slots for a subframe may depend on the digital technology. For a conventional cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60kHz subcarrier spacing), a time slot may include 12 symbols. For a conventional cyclic prefix and an extended cyclic prefix, the relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame may depend on the digital technology. It should be understood that references to a first digital technology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15kHz) may be used interchangeably between subframes and time slots.

[0043] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc. based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some implementations, the network entity 102 and the UE 104 can perform wireless communications on one or more of the operating frequency bands. In some implementations, FR1 can be used by the network entity 102 and the UE 104 and other devices or apparatuses for cellular communication services (e.g., control information, data). In some implementations, FR2 may be used by the network entity 102 and UE 104 and other devices or apparatuses for short-range, high data rate capabilities.

[0044] FR1 may be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 may be associated with a first digital technology (e.g., μ=0) including a subcarrier spacing of 15 kHz; a second digital technology (e.g., μ=1) including a subcarrier spacing of 30 kHz; and a third digital technology (e.g., μ=2) including a subcarrier spacing of 60 kHz. FR2 may be associated with one or more digital technologies (e.g., at least 2 digital technologies). For example, FR2 may be associated with a third digital technology (e.g., μ=2) including a subcarrier spacing of 60 kHz; and a fourth digital technology (e.g., μ=3) including a subcarrier spacing of 120 kHz.

[0045] The network entity 102 sends signaling to the UE 104, the signaling including an SPS configuration 120. The SPS configuration 120 can be sent using any of a variety of different types of signaling, such as RRC signaling. The SPS configuration 120 includes one or more DRX timer configurations, which the network entity sets for use by the UE 104 based on any of the characteristics of one or more DL traffic flows in a plurality of downlink (DL) traffic flows (as shown in data 122). The UE 104 receives the data 122, and an application 124 at the UE 104 uses the data 122. The application 124 can be any of a variety of applications, such as an XR application. The application 124 receives the data 122 using one or more DRX timer configurations in the SPS configuration 120, and provides a response 126 (e.g., feedback) to the network entity 102 regarding the received data 122. For example, these timers may include one or more of the following: a DRX retransmission timer, a DRX HARQ RTT timer, a DRX inactivity timer, and a DRX on-duration timer, as discussed in more detail below.

[0046] In one or more implementations, the SPS configuration 120 consists of a set of timer configurations. For example, the SPS configuration 120 includes one or more information elements (IEs) that configure the values ​​of drx-RetransmissionTimerDL and / or drx-HARQ-RTT-TimerDL to be applied by the UE 104 when receiving a media access control (MAC) protocol data unit (PDU) at an SPS opportunity according to the SPS configuration 120.

[0047] Additionally or alternatively, the UE 104 considers the SPS transmission timing of the SPS configuration 120 as the DRX active time, for example, the UE 104 monitors the PDCCH at the SPS transmission timing. The SPS configuration 120 configures whether the UE 104 should consider the SPS transmission timing as the active time for the SPS configuration 120 through a new parameter or IE, for example, whether the UE 104 monitors the PDCCH on the SPS timing even if the SPS is outside the DRX active time defined by other drx timers / configurations.

[0048] Many end-user XR devices are expected to be power-constrained. Connected-mode DRX (C-DRX) can be used to help such XR devices save power and therefore operate longer without charging. However, XR traffic characteristics (such as non-integer traffic periodicity and jitter) may result in missing opportunities to schedule XR video frames within the on-duration of a DRX cycle. For example, a video frame may arrive after the on-duration and therefore need to be scheduled in the next DRX cycle, which in turn increases the associated latency. This latency increase may be undesirable because XR packets need to be delivered within the delay budget, otherwise they may be useless.

[0049] For XR services, where an XR application may consist of multiple flows with different service characteristics, the flows may be used by SPS to help schedule transmissions corresponding to different services in a timely manner when using a single DRX configuration. If a single DRX configuration matching one flow does not satisfy the PDBs of other flows, multiple simultaneous DRX configurations (each DRX configuration matching a service flow) are suitable for achieving both high UE energy saving gains and many satisfied UEs. However, achieving multiple simultaneously active DRX configurations comes at the cost of higher complexity and further enhancement / standardization work is required.

[0050] The SPS timing is provided according to the expected arrival of the service. This would be an alternative to introducing multiple simultaneous DRX configurations. However, since different service flows / QoS flows have different service characteristics, it is not efficient to apply the same drx timer value for each SPS configuration (e.g., applying the same drx-RetransmissionTimerDL or drx-HARQ-RTT-TimerDL value for each SPS configuration).

[0051] Figure 2 An example 200 of multi-stream XR with DRX and SPS is illustrated. In the top stream XR-Stream 1, the DRX On Duration box illustrates the active time in which the UE 104 monitors the PDCCH. In the bottom stream XR-Stream 2, the SPS box illustrates the time when the UE 104 will be awakened and monitor the PDSCH (e.g., data traffic). If the UE 104 receives a MAC PDU on an SPS transmission opportunity, the UE 104 will start a timer. For example, when the UE 104 sends HARQ feedback for the SPS transmission, it will start the drx-HARQ-RTT-TimerDL. After the drx-HARQ-RTT-TimerDL expires, the UE 104 starts the drx-RetransmissionTimerDL timer so that additional potential retransmissions can be monitored.

[0052] XR is an umbrella term for different types of reality, including virtual reality (VR), augmented reality (AR), and mixed reality (MR).

[0053] VR is a rendered version of the delivered visual and audio scene. The rendering is intended to mimic as naturally as possible the visual and auditory stimulation of the real world as the observer or user moves within the range defined by the application. Virtual reality typically (but not necessarily) requires the user to wear a head-mounted display (HMD) (to completely replace the user's field of view with simulated visual components), and headphones (to provide incidental audio to the user). It is also usually necessary to perform some form of head and motion tracking of the user in VR to allow the simulated visual and audio components to be updated, thereby ensuring that from the user's perspective, items and sound sources are consistent with the user's movements. Additional components for interacting with the virtual reality simulation can be provided, but are not strictly required.

[0054] AR refers to the user being provided with additional information or artificially generated items or content superimposed on their current environment. Such additional information or content is typically visual and / or auditory, and their observation of the current environment can be direct, without intermediate sensing, processing and rendering, or indirect, where their perception of their environment is relayed via sensors and can be augmented or processed.

[0055] MR is an advanced form of AR in which some virtual elements are inserted into the physical scene with the aim of providing the illusion that these elements are part of the real scene.

[0056] XR refers to all combined real and virtual environments and human-computer interactions generated by computer technology and wearable devices. It includes representative forms such as AR, MR and VR as well as areas interpolated between them. The level of virtuality ranges from partial sensory input to fully immersive VR. The key aspect of XR is the expansion of human experience, especially related to presence (represented by VR) and cognitive acquisition (represented by AR).

[0057] Many XR and cloud gaming (CG) use cases are characterized by quasi-periodic traffic (possibly with jitter) with high data rates in the DL (i.e., video streaming) combined with frequent uplink (UL) (i.e., attitude / control updates) and / or UL video streaming. Both DL and UL traffic are also characterized by relatively tight PDBs.

[0058] It is expected that the set of XR and CG services has a certain diversity, and the characteristics of the data stream (i.e., video) can change "dynamically" when the services are running on NR. Therefore, additional information about the running services from higher layers (e.g., QoS flow association, frame level QoS, application data unit (ADU) based QoS, XR specific QoS, etc.) can help facilitate informed selection of radio parameters. The term ADU (application data unit) can also be replaced by the term PDU set. It is obvious that XR application awareness by the UE 104 and the network entity 102 will improve the user experience, increase the NR system capacity to support XR services, and reduce UE power consumption.

[0059] An ADU or PDU set is the smallest data unit that can be processed independently by an application (such as for processing out-of-order service data). A video frame can be an I frame, a P frame, or can be composed of I slices and / or P slices. I frames / I slices are more important and larger than P frames / P slices. An ADU or PDU set can be one or more I slices, P slices, I frames, P frames, or a combination thereof.

[0060] A service-oriented design that considers the characteristics of XR services (e.g., (a) variable packet arrival rate: packets arrive at 30 to 120 frames / s with a certain jitter, (b) packets have variable and large packet size, (c) B / P frames depend on I frames, (d) there are multiple services / data streams in the uplink, such as gesture and video scenes) can achieve more efficient (e.g., in terms of meeting XR service requirements for more UEs, or in terms of UE energy saving) XR service delivery.

[0061] The latency requirement of XR traffic on the RAN side (ie, air interface) is modeled as PDB. The PDB is a finite time budget for packets sent from the network entity 102 to the UE 104 over the air.

[0062] For a given packet, the delay of the packet incurred in the air interface is measured from the time the packet arrives at the network entity 102 to the time the packet is successfully transmitted to the UE 104. If the delay is greater than a given PDB for the packet, the packet is considered to violate the PDB, otherwise the packet is considered to be successfully delivered.

[0063] The value of PDB may vary for different applications and service types, and may be 10 to 20 ms depending on the application.

[0064] The 5G arrival time of data bursts on the downlink can be quasi-periodic, i.e., with a period of jitter. Some factors that contribute to burst arrival jitter include: varying server rendering time, encoder time, Real-time Transport Protocol (RTP) packet time, link between server and 5G gateway, etc. The 3rd Generation Partnership Project (3GPP) agreed to use a truncated Gaussian distribution for simulation assumptions for XR evaluation model DL service arrival jitter, with a mean: 0ms, standard deviation: 2ms, range: [-4ms, 4ms] (baseline), [-5ms, 5ms] (optional).

[0065] Applications may have certain delay requirements for ADU / PDU sets that may not be adequately translated into packet delay budget requirements. For example, if the ADU delay budget (ADB) is 10ms, the PDB can be set to 10ms only if all packets of the ADU arrive at the 5G system at the same time. If the packets are scattered, the ADU delay budget is measured with the arrival of the first packet of the ADU or the last packet of the ADU. In either case, a given ADB will result in different PDB requirements for different packets of the ADU. It has been observed that specifying the ADB to the 5G system can be beneficial.

[0066] If the scheduler and / or UE 104 knows the delay budget for a packet / ADU, the network entity 102 can take this knowledge into account when scheduling transmissions, for example, by prioritizing transmissions that are close to their delay budget limit and by not scheduling (e.g., UL) transmissions; the UE 104 can also use such knowledge to determine: 1) whether UL transmissions corresponding to transmissions that exceed its delay budget (e.g., physical downlink control channel (PDCCH), UL gestures, or physical uplink shared channel (PUSCH) in response to PDSCH) can be discarded (additionally, there is no need to wait for retransmissions of PDSCH or retain erroneously received PDSCH in a cache for soft combining with retransmissions that never occurred); or 2) how much channel occupancy time can be shared with the network entity 102 when using unlicensed spectrum.

[0067] 1) The remaining delay budget for DL ​​transmission may be indicated to the UE 104 in downlink control information (DCI) (e.g., for grouping of video frames / slices / ADUs) or via a MAC control unit (MAC-CE) (e.g., for ADUs / video frames / slices), and 2) the remaining delay budget for UL transmission may be indicated to the network entity 102 via UL transmissions such as uplink control information (UCI), PUSCH transmissions, etc.

[0068] ADU-related QoS aspects of XR can be communicated to the RAN to optimize communications, such as ADU Error Rate (AER), ADU Delay Budget (ADB), and ADU Content Policy (referred to as ADP, which is the percentage of packets / bits of the ADU received in order to correctly decode the ADU).

[0069] In one or more models, the packet arrival rate is determined by the frame generation rate (e.g., 60fps). Therefore, the average packet arrival period is given by the inverse of the frame rate, e.g., 16.6667ms=1 / 60fps. The jitter-free periodic arrival gives the arrival time at the network entity 102 for a packet with index k (=1, 2, 3, ...) as follows:

[0070] k / F*1000[ms],

[0071] Where F is the given frame generation rate (per second).

[0072] Note that such periodic packet arrival implicitly assumes fixed delays contributed from the network side, including fixed video encoding time, fixed network transmission delay, etc.

[0073] However, in real systems, varying frame coding delays and network transfer times introduce jitter in the packet arrival times at the network entity 102. In this model, jitter is modeled as a random variable added on top of the periodic arrivals. The jitter follows a truncated Gaussian distribution with statistical parameters as shown in Table 1.

[0074] Table 1: Statistical parameters for jitter

[0075] parameter unit Baseline value for evaluation Optional value to evaluate average value ms 0 Standard Deviation (STD) ms 2 Truncation range ms [-4，4] [-5，5]

[0076] Note that the given parameter values ​​and the considered frame generation rate (60 or 120 in this model) ensure that the packet arrivals are in order (ie, the arrival time of the next packet is always greater than the arrival time of the previous packet).

[0077] Therefore, periodic arrival with jitter gives the arrival time for a packet with index k (=1, 2, 3, ...) as follows:

[0078] Offset + k / F*1000 + J [ms],

[0079] Where F is a given frame generation rate (per second) and J is a random variable capturing jitter. Note that the actual traffic arrival timing of traffic for each UE 104 may be shifted by any UE 104 specific offset.

[0080] The DRX function controls the UE's PDCCH monitoring activities to the MAC entity, resulting in discontinuous monitoring of the PDCCH.

[0081] RRC signaling controls DRX operation by configuring the following parameters:

[0082] -drx-onDurationTimer: Duration of the start of the drx cycle (PDCCH in

[0083] The duration of the opening is monitored);

[0084] -drx-SlotOffset: Delay before starting drx-onDurationTimer (e.g.

[0085] relative to subframe boundaries);

[0086] -drx-InactivityTimer: Duration after PDCCH opportunity, where

[0087] PDCCH (received during drx active time) indicates new UL or DL ​​transmission for the MAC entity;

[0088] -drx-RetransmissionTimerDL (each DL HARQ process except the broadcast process): maximum duration before a DL retransmission is received;

[0089] -drx-RetransmissionTimerUL (per UL HARQ process): after receiving

[0090] Maximum duration before grant for UL retransmission;

[0091] -drx-LongCycleStartOffset: Long DRX cycle and drx-StartOffset, which is defined

[0092] It defines the subframes where long DRX cycle and short DRX cycle are started;

[0093] -drx-ShortCycle (optional): short DRX cycle;

[0094] -drx-ShortCycleTimer (optional): The UE should follow the duration of the short DRX cycle.

[0095] duration;

[0096] -drx-HARQ-RTT-TimerDL (for each DL HARQ process except the broadcast process): minimum duration before a DL allocation for a HARQ retransmission expected by the MAC entity;

[0097] -drx-HARQ-RTT-TimerUL (per UL HARQ process): minimum duration before a UL HARQ retransmission grant is expected by the MAC entity;

[0098] -ps-Wakeup (optional): Configuration for starting the associated drx-onDurationTimer (after drx-SlotOffset from the start of the subframe) in case DCP (downlink control for energy saving) is monitored but no DCP is detected;

[0099] -ps-TransmitOtherPeriodicCSI (optional): Used to report on PUCCH for the duration indicated by drx-onDurationTimer, when DCP is configured but the associated drx-onDurationTimer is not started

[0100] Configuration of periodic channel state information (CSI) for non-L1-RRP;

[0101] -ps-TransmitPeriodicL1-RSRP (optional): used to transmit on PUCCH for the duration indicated by drx-onDurationTimer, if DCP is configured but the associated drxonDurationTimer is not started

[0102] Configuration of periodic CSI (i.e., L1-RRP);

[0103] -uplinkHARQ-Mode (optional): used to set the HARQ mode configuration for each UL HARQ process.

[0104] The service cells of the MAC entity can be configured by RRC in two DRX groups with separate DRX parameters. When RRC does not configure a secondary DRX group, there is only one DRX group and all service cells belong to this one DRX group. When two DRX groups are configured, each service cell is uniquely assigned to any one of the two groups. The DRX parameters configured separately for each DRX group are: drx-onDurationTimer, drxInactivityTimer. The DRX parameters common to the DRX group are: drx-SlotOffset, drxRetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drxShortCycleTimer (optional), drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL and uplinkHARQ-Mode (optional).

[0105] The MAC entity may be configured with a DRX function by RRC, which controls the UE's PDCCH monitoring activities for the MAC entity's C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, AI-RNTI, SL-RNTI, SLCS-RNTI and SL semi-persistent scheduling V-RNTI. When using DRX operation, the MAC entity shall also monitor the PDCCH in accordance with the requirements in other clauses of this specification. When in RRC_CONNECTED, if DRX is configured for all activated serving cells, the MAC entity may use the DRX operation specified in this clause to monitor the PDCCH discontinuously; otherwise, the MAC entity shall monitor the PDCCH as specified in 3GPP Technical Specification (TS) 38.213.

[0106] RRC controls DRX operation by configuring the following parameters:

[0107] -drx-onDurationTimer: duration when the DRX cycle starts;

[0108] -drx-SlotOffset: Delay before starting drx-onDurationTimer;

[0109] -drx-InactivityTimer: Duration after PDCCH opportunity, where

[0110] PDCCH indicates a new UL or DL ​​transmission for the MAC entity;

[0111] -drx-RetransmissionTimerDL (each DL HARQ process except the broadcast process): maximum duration before a DL retransmission is received;

[0112] -drx-RetransmissionTimerUL (per UL HARQ process): after receiving

[0113] Maximum duration before grant for UL retransmission;

[0114] -drx-LongCycleStartOffset: Long DRX cycle and drx-StartOffset, which is defined

[0115] It defines the subframes where long DRX cycle and short DRX cycle are started;

[0116] -drx-ShortCycle (optional): short DRX cycle;

[0117] -drx-ShortCycleTimer (optional): The UE should follow the duration of the short DRX cycle.

[0118] duration;

[0119] -drx-HARQ-RTT-TimerDL (for each DL HARQ process except the broadcast process): minimum duration before a DL allocation for a HARQ retransmission expected by the MAC entity;

[0120] -drx-HARQ-RTT-TimerUL (per UL HARQ process): minimum duration before a UL HARQ retransmission grant is expected by the MAC entity;

[0121] -drx-RetransmissionTimerSL (per SL HARQ process): after receiving

[0122] Maximum duration before grant for SL retransmission;

[0123] -drx-HARQ-RTT-TimerSL (per SL HARQ process): minimum duration before a SL retransmission grant is expected by the MAC entity;

[0124] -ps-Wakeup (optional): In the case where DCP is monitored but not detected,

[0125] Used to start the configuration of the associated drx-onDurationTimer;

[0126] -ps-TransmitOtherPeriodicCSI (optional): Used to report on PUCCH for the duration indicated by drx-onDurationTimer, when DCP is configured but the associated drx-onDurationTimer is not started

[0127] Configuration of periodic CSI for non-L1-RSRP;

[0128] -ps-TransmitPeriodicL1-RSRP (optional): used to transmit on PUCCH for the duration indicated by drx-onDurationTimer, if DCP is configured but the associated drx-onDurationTimer is not started

[0129] Configuration of periodic CSI (i.e., L1-RRP);

[0130] -downlinkHARQ-FeedbackDisabled (optional): used to implement the configuration of HARQ feedback for each DLHARQ process;

[0131] -uplinkHARQ-Mode (optional): used to set the configuration of HARQmodeA or HARQmodeB for each UL HARQ process.

[0132] The service cells of the MAC entity can be configured by RRC in two DRX groups with separate DRX parameters. When RRC does not configure a secondary DRX group, there is only one DRX group and all service cells belong to this one DRX group. When two DRX groups are configured, each service cell is uniquely assigned to any one of the two groups. The DRX parameters configured separately for each DRX group are: drx-onDurationTimer, drx-InactivityTimer. The DRX parameters common to the DRX group are: drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, downlinkHARQ-FeedbackDisabled (optional) and uplinkHARQ-Mode (optional).

[0133] When DRX is configured, the active time for the serving cell in the DRX group includes the time when:

[0134] - The drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or

[0135] - drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or drx-RetransmissionTimerSL is running on any serving cell in the DRX group; or

[0136] -ra-ContentionResolutionTimer (as in 3GPP TS 38.321 Section 5.7

[0137] 5.1.5) or msgB-ResponseWindow (as described in Section 5.1.4a)

[0138] is running; or

[0139] - Scheduling request is sent on PUCCH and is pending (e.g. 3GPP TS

[0140] 38.321 Section 5.7, Clause 5.4.4 or 5.22.1.5). If the serving cell is part of a non-terrestrial network, the active time starts after a scheduling request transmission is made when SR_COUNTER is 0 for all serving cells with (multiple)

[0141] SR configuration of the pending SR plus the UE-gNB RTT execution; or

[0142] - after successfully receiving a random access response to a random access preamble that was not selected by the MAC entity among the contention-based random access preambles, no PDCCH indicating a new transmission of the C-RNTI addressed to the MAC entity is received (e.g., 3GPP TS

[0143] 38.321 Section 5.7, 5.1.4 and 5.1.4a).

[0144] The following MAC timers are used for DRX operation in non-terrestrial networks:

[0145] - HARQ-RTT-TimerDL-NTN (for each DL HARQ process configured with HARQ feedback enabled): minimum duration before a DL allocation for a HARQ retransmission expected by the MAC entity;

[0146] - HARQ-RTT-TimerUL-NTN (each UL HARQ process configured with HARQModeA): minimum duration before a UL HARQ retransmission grant is expected by the MAC entity.

[0147] Figure 3 An example flow of operations 300 performed by a MAC entity when DRX is configured is illustrated. Operations 300 are shown, for example, in pseudo code.

[0148] For NR, if PDSCH is received during an SPS opportunity, the UE 104 monitors the PDCCH for potential HARQ retransmissions even if the SPS opportunity (configured downlink allocation) is not within the active time. Similar behavior has been specified for configured uplink grants (i.e., CG grants).

[0149] In one or more implementations, the SPS configuration consists of a set of timer configurations. For example, the SPS configuration may contain (multiple) IEs that configure the values ​​of drx-RetransmissionTimerDL and / or drx-HARQ-RTT-TimerDL, which will be applied by the UE when the MAC PDU is received at an SPS opportunity according to the SPS configuration. drx-RetransmissionTimerDL may also be referred to as a DRX retransmission timer, and drx-HARQ-RTT-TimerDL may also be referred to as a HARQ RTT timer.

[0150] In one example, when a PDSCH / MAC PDU is received at an SPS opportunity corresponding to an SPS configuration, the UE starts drx-HARQ-RTT-TimerDL in the first symbol after the end of the corresponding transmission carrying DL HARQ feedback, which is set to the value configured for the corresponding HARQ process in the SPS configuration IE. Similarly, when drx-HARQ-RTT-TimerDL expires, the UE starts drx-RetransmissionTimerDL, which is set to the value configured for the SPS configuration.

[0151] drx-RetransmissionTimerDL may be started when drx-HARQ-RTT-TimerDL expires, regardless of whether the PDSCH may be correctly decoded, e.g., NACK or ACK is reported as HARQ feedback.

[0152] Figure 4 An example of supporting an SPS configuration IE 400 including a timer configuration according to aspects of the present disclosure is illustrated. As shown, the SPS configuration IE 400 includes: drx-HARQ-RTT-TimerDL, which may have an integer value; and drx-RetransmissionTimerDL, which is set to a value configured for the SPS configuration when the drx-HARQ-RTT-TimerDL (which may have one of a plurality of enumerated values) expires.

[0153] Back to Figure 1In one or more implementations, the SPS configuration consists of a drx-inactivityTimer configuration (also referred to as a DRX inactivity timer or drx-InactivityTimer). In one example, the UE starts the drx-InactivityTimer for the case when a PDSCH is received at an SPS timing of an SPS timing. The drx-InactivityTimer can be set to a value configured for the corresponding SPS configuration. The drx-InactivityTimer can be started at a preconfigured offset after the SPS transmission timing to account for MAC processing delays, such as detection / decoding of PDSCH at the SPS transmission timing. In one example, the time offset is configured in the SPS configuration.

[0154] Starting the drx-InactivityTimer ensures a non-long period of DRX ("sleep period") between the SPS transmission opportunity and the subsequent activity time triggered by the starting of the drx-RetransmissionTimerDL.

[0155] Figure 5 An example 500 of using a DRX inactivity timer supporting an SPS configuration including a timer configuration according to aspects of the present disclosure is illustrated. As shown in example 500, the network needs to wait until the drx-HARQ-RTT-TimerDL timer expires before scheduling additional DL / UL transmissions to the UE, for example, when the drx-RetransmissionTimerDL is running, the UE is in active time and monitoring the PDCCH. Thus, for example, in response to receiving a PDSCH on an SPS transmission opportunity, starting the drx-InactivityTimer (if configured in the corresponding SPS configuration) allows the network, for example, to subsequently (without gaps) schedule additional DL packets of a DL data burst / PDU set.

[0156] In one or more implementations, the UE only needs to monitor the PDCCH for DL ​​DCI when the drx-InactivityTimer started in response to reception of the PDSCH on the SPS transmission opportunity is running.

[0157] Figure 6 An example of an SPS configuration IE 600 that supports SPS configuration including timer configuration according to aspects of the present disclosure is illustrated. As shown, the SPS configuration IE 600 includes: drx-HARQ-RTT-TimerDL and drx-RetransmissionTimerDL, such as Figure 4The SPS configuration IE 400 is shown. The SPS configuration IE 600 also includes a drx-InactivityTimer, which can have one of a plurality of enumerated values.

[0158] In one or more implementations, the SPS configuration consists of a drx-onDurationTimer configuration. The drx-onDurationTimer may also be referred to as a DRX on-duration timer. In one example, if the drx-onDurationTimer is configured in the SPS configuration, the UE starts the drx-onDurationTimer for each SPS transmission opportunity of the SPS configuration. For example, the UE starts the drx-onDurationTimer at the start of a time slot, symbol, or subframe of the SPS transmission opportunity.

[0159] In one example, the SPS configuration includes a drx-onDurationTimer configuration and a drx-HARQ-RTT-TimerDL and drx-retransmissionTimerDL configuration. The UE starts the drx-onDurationTimer at the start of a slot, symbol or subframe of an SPS transmission opportunity. In response to receiving a PDSCH on an SPS transmission opportunity, the UE starts the drx-HARQ-RTT-timerDL in the first symbol after the end of the corresponding transmission carrying DL HARQ feedback.

[0160] Figure 7 An example of an SPS configuration IE 700 that supports SPS configuration including timer configuration according to aspects of the present disclosure is illustrated. As shown, the SPS configuration IE 700 includes: drx-HARQ-RTT-TimerDL and drx-RetransmissionTimerDL, such as Figure 4 The SPS configuration IE 400 is shown. The SPS configuration IE 700 also includes drx-onDurationTimer, which can have a value of a plurality of enumeration values.

[0161] Back to Figure 1, the techniques discussed in this document address HARQ process determination for an SPS configuration with multiple SPS opportunities in each SPS cycle. In order to avoid gaps between SPS opportunities and the subsequent activity time of the UE triggered by the start of drx-RetransmissionTimerDL, an SPS configuration can consist of multiple SPS transmission opportunities within an SPS cycle. However, supporting more than one SPS transmission opportunity within an SPS cycle will require new UE behavior for associating SPS transmission opportunities with HARQ process IDs. According to the current formula, all SPS opportunities within an SPS cycle will be assigned the same HARQ process ID, as shown below.

[0162] For a downlink allocation without the configuration of harq-ProcID-Offset, the HARQ process ID associated with the timeslot where the DL transmission starts is derived from the following equation:

[0163] HARQ Process ID=[floor(CURRENT_slot×10 / (numberOfSlotsPerFrame×periodicity))]modulo nrofHARQ-Processes

[0164] Wherein CURRENT_slot=[(SFN×numberOfSlotsPerFrame)+time slot number in frame], and numberOfSlotsPerFrame refers to the number of consecutive time slots per frame specified in 3GPP TS 38.211.

[0165] For a downlink allocation with a configuration of harq-ProcID-Offset, the HARQ process ID associated with the timeslot where the DL transmission starts is derived from the following equation:

[0166] HARQ Process ID=[floor(CURRENT_slot×10 / (numberOfSlotsPerFrame×periodicity))]modulo nrofHARQ-Processes+harq-ProcID-Offset

[0167] Wherein CURRENT_slot=[(SFN×numberOfSlotsPerFrame)+time slot number in frame], and numberOfSlotsPerFrame refers to the number of consecutive time slots per frame specified in 3GPP TS 38.211.

[0168] In the presence of misaligned system frame numbers (SFNs) across carriers in a cell group, the SFN of the relevant serving cell is used to calculate the HARQ process ID for the configured downlink assignment.

[0169] Note that CURRENT_slot refers to the slot index of the first transmission opportunity of a bundle of configured downlink allocations.

[0170] In one or more implementations, a pattern is defined that defines an SPS opportunity within an SPS cycle. The pattern is repeated with a defined periodicity. In one example, the pattern is defined as a bitmap, wherein a first bit of the bitmap corresponds to a first SPS opportunity within the SPS cycle.

[0171] The new formula can allocate HARQ process IDs to SPS opportunities. In one example, the new formula is:

[0172] HARQ Process ID=[[floor(CURRENT_slot×10 / (numberOfSlotsPerFrame×periodicity))]x numberOfSPSoccasionPerPeriod+CURRENT_SPSoccasion]modulonrofHARQ-Processes

[0173] Where numberOfSPSoccasionsPerPeriod refers to the number of SPS transmission opportunities within one SPS period, and CURRENT_SPSoccasion refers to the index of the SPS transmission opportunity within the SPS period for which the HARQ process ID should be allocated. CURRENT_slot refers to the slot index of the first transmission opportunity of the configured downlink allocation set within the SPS period.

[0174] In one or more implementations, the UE treats the SPS transmission timing of the SPS configuration as DRX active time, for example, the UE monitors the PDCCH at the SPS transmission timing. This allows the network (e.g., the network entity 102) to override the SPS allocation by issuing a dynamic grant (DG). In one example, the SPS configuration configures whether the UE should treat the SPS transmission timing as the active time for the SPS configuration through a new parameter or IE, for example, whether the UE monitors the PDCCH on the SPS timing even if the SPS is outside the DRX active time defined by other drx timers or configurations. The benefit is that the network can always update or override the SPS grant even when the SPS timing is not within the DRX active time. Since XR services have variable packet sizes, this provides greater flexibility for the network or scheduler. It will also allow the network to have the UE start a drx-InactivityTimer, for example, when more transmissions are needed to send pending DL data in the network's cache. Whenever the network sends a DCI on an SPS transmission timing, the UE will start a drx-InactivityTimer, thereby extending the active time. The drx-InactivityTimer value depends on an implementation configured for SPS configuration. For the case where DCI is received on an SPS transmission opportunity, the UE uses the configured drx-InactivityTimer value. In an example, for the case where the SPS transmission opportunity falls within the active time, the UE applies traditional behavior, such as different UE behavior for DRX timer handling depending on whether the SPS opportunity falls within the UE's active time.

[0175] In one or more implementations, the CG configuration is configured with a maximum number of supported HARQ retransmissions for a corresponding PUSCH transmission associated with the CG configuration.

[0176] In one example, if the number of HARQ retransmissions is not equal to or greater than the configured maximum number of supported retransmissions, the UE shall start drx-HARQ-RTT-TimerUL only after PUSCH transmission and then start drx-RetransmissionTimerUL. For example, for the case where the maximum number of supported HARQ retransmissions for CG configuration is configured to be equal to 1, the UE shall start drx-HARQ-RTT-TimerUL only in response to the initial HARQ transmission on the CG resources, for example, the UE shall not start drx-HARQ-RTT-TimerUL after having performed the first retransmission of a CG PUSCH transmission.

[0177] In one or more implementations, the UL DCI includes an indication of whether the UE should start the drx-HARQ-RTT-TimerUL in response to a PUSCH transmission on UL CG resources. In one example, the UL DCI is a DCI that activates the CG configuration, such as a PDCCH addressed to the CS-RNTI. Information about whether to start the drx-HARQ-RTT-TimerUL after a PUSCH transmission on the CG UL resources can be signaled within a 1-bit field in the DCI. In one example, if the 1-bit field within the DCI that activates the CG configuration is set to "", the UE will not start the drx-HARQ-RTT-TimerUL after performing a PUSCH transmission on the UL CG resources activated by the UL CG activation DCI, and will not subsequently start the drx-RetransmissionTimerUL. Similarly, if the 1-bit field within the DCI activating the CG configuration is set to "1", the UE starts drx-HARQ-RTT-TimerUL and subsequently starts drx-RetransmissionTimerUL after performing PUSCH transmission on the UL CG resources activated by the UL CG activation DCI. In one example, the indication or field within the UL DCI is a new field, that is, a new DCI format for activating or deactivating the UL CG is introduced. According to another example, an existing field or a combination of existing fields within the DCI for activating or deactivating the UL CG is reused or repurposed to indicate whether the drx-HARQ-RTT-TimerUL should be started after PUSCH transmission on the UL CG resources.

[0178] In one or more implementations, the MAC control unit determines whether the UE should start the drx-HARQ-RTT-TimerUL after a PUSCH transmission on a CG UL resource. In one example, the MAC CE indicates, for each configured UL CG configuration, whether the UE should start the drx-HARQ-RTT-TimerUL after a PUSCH transmission on the corresponding CG UL resource. The MAC CE may consist of a bit map, where each field of the bit map corresponds to a configured UL CG configuration. In one example, a bit of the bit map set to "1" indicates that the UE should start the drx-HARQ-RTT-TimerUL after a PUSCH on a CG PUSCH resource of the corresponding CG configuration. A bit set to "0" indicates that the UE should not start the drx-HARQ-RTT-TimerUL after a PUSCH on a CG PUSCH resource of the corresponding CG configuration.

[0179] Therefore, the technology discussed herein includes various aspects of SPS configuration, and SPS configuration includes timer configuration. For example, SPS configuration consists of drx related timer configuration. In one or more implementations, Drx timer configuration is one or a combination of the following items: drx-HARQ-RTT-TimerDL, drx-retransmissionTimerDL, drx-OndurationTimer and dr-InactivityTimer. Additionally or alternatively, UE 104 starts drx-HARQ-RTT-TimerDL in the first symbol after the end of HARQ feedback transmission of PDSCH received on SPS transmission opportunity. Additionally or alternatively, UE 104 starts dr-InactivityTimer in response to receiving PDSCH on SPS transmission opportunity. Additionally or alternatively, UE 104 starts drx-OndurationTimer for each SPS transmission opportunity of SPS configuration. Additionally or alternatively, UE 104 regards the SPS transmission opportunity of the SPS configuration as the DRX active time. Additionally or alternatively, for the case where there are multiple SPS transmission opportunities within the SPS cycle, a new formula or rule for determining the HARQ process ID corresponding to the SPS transmission opportunity is introduced.

[0180] In some solutions, the network will use a single DRX scheme with an SPS configuration or a system with multiple simultaneously active DRX configurations. From an energy saving perspective, using a single DRX scheme with an SPS configuration does not allow efficient support of multi-stream XR applications because the same DRX timer configuration is applied for each service flow. On the other hand, supporting multiple active DRX configurations increases the complexity of the UE and requires further enhancements. Using the techniques discussed in this article provides some SPS enhancements that allow efficient support of multi-stream XR applications while still using a single DRX scheme.

[0181] Figure 8 An example of a block diagram 800 of a device 802 that supports SPS configuration including timer configuration according to aspects of the present disclosure is illustrated. The device 802 may be an example of a UE 104 as described herein. The device 802 may support wireless communications with one or more network entities 102, UE 104, or any combination thereof. The device 802 may include components for bidirectional communication, including components for sending and receiving communications (such as a processor 804, a memory 806, a transceiver 808, and an I / O controller 810). These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0182] The processor 804, the memory 806, the transceiver 808, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the present disclosure described herein. For example, the processor 804, the memory 806, the transceiver 808, or various combinations thereof, or components thereof may support methods for performing one or more of the operations described herein.

[0183] In some implementations, the processor 804, memory 806, transceiver 808, or various combinations or components thereof may be implemented in hardware (e.g., in a communications management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of components configured or otherwise supported for performing the functions described in the present disclosure. In some implementations, the processor 804 and the memory 806 coupled to the processor 804 may be configured to perform one or more of the functions described herein (e.g., execution of instructions stored in the memory 806 by the processor 804).

[0184] For example, according to the examples disclosed herein, the processor 804 may support wireless communication at the device 802. The processor 804 may be configured to or otherwise support: receiving a first signaling indicating a downlink SPS configuration from a network entity, wherein the downlink SPS configuration includes a timer configuration set; receiving a second signaling indicating a PDSCH from the network entity at an SPS transmission opportunity of the downlink SPS configuration; and in response to receiving the PDSCH at the SPS transmission opportunity, starting a first timer set according to a corresponding timer value of the timer configuration set.

[0185] Additionally or alternatively, the processor 804 may be configured to or otherwise support: wherein the timer configuration set includes a DRX retransmission timer and a DRX HARQ RTT timer; wherein starting the first timer is to start the DRXHARQ timer configured in the SPS configuration in the first symbol after the end of the corresponding transmission carrying the downlink HARQ feedback for the PDSCH; wherein the timer configuration set includes a DRX inactivity timer; wherein starting the first timer is to start the DRX inactivity timer in response to receiving the PDSCH on the SPS transmission opportunity; wherein the timer configuration set includes a DRX on duration timer; wherein the processor is also configured to start the DRX on duration timer for each SPS transmission opportunity of the downlink SPS configuration; wherein the processor is also configured to regard the SPS transmission opportunity of the downlink SPS configuration as the DRX active time, and monitor the PDCCH at each SPS transmission opportunity; wherein the SPS cycle includes multiple SPS transmission opportunities, and wherein the processor is also configured to allocate a HARQ process identifier for each SPS opportunity within the SPS cycle based at least in part on the number of SPS transmission opportunities included in the SPS cycle and the current SPS transmission opportunity; wherein the first signaling includes radio resource control signaling; wherein the device includes a user equipment.

[0186] For example, according to the examples disclosed herein, the processor 804 may support wireless communication at the device 802. The processor 804 may be configured to or otherwise support components for: receiving a first signaling indicating a downlink SPS configuration from a network entity, wherein the downlink SPS configuration includes a timer configuration set; receiving a second signaling indicating a PDSCH from the network entity at an SPS transmission opportunity of the downlink SPS configuration; and in response to receiving the PDSCH at the SPS transmission opportunity, starting a first timer set according to a corresponding timer value of the timer configuration set.

[0187] According to the examples disclosed herein, a processor 804 of a device 802 (such as a UE 104) may support wireless communication. The processor 804 includes at least one controller coupled to at least one memory and configured or operable to cause the processor to: receive first signaling indicating a downlink SPS configuration from a network entity, wherein the downlink SPS configuration includes a timer configuration set; receive second signaling indicating a PDSCH from the network entity at an SPS transmission opportunity of the downlink SPS configuration; and in response to receiving the PDSCH at the SPS transmission opportunity, start a first timer set according to a corresponding timer value of the timer configuration set.

[0188] Additionally or alternatively, the processor 804 may be configured to or otherwise support: wherein the timer configuration set includes a DRX retransmission timer and a DRX HARQ RTT timer; wherein starting the first timer includes starting the DRXHARQ timer configured in the SPS configuration in the first symbol after the end of the corresponding transmission carrying the downlink HARQ feedback for the PDSCH; wherein the timer configuration set includes a DRX inactivity timer; wherein starting the timer includes starting the DRX inactivity timer in response to receiving the PDSCH on the SPS transmission opportunity; wherein the timer configuration set includes a DRX on duration timer; starting the DRX on duration timer for each SPS transmission opportunity of the downlink SPS configuration; treating the SPS transmission opportunity of the downlink SPS configuration as the DRX active time, and monitoring the PDCCH at each SPS transmission opportunity; wherein the SPS cycle includes multiple SPS transmission opportunities, and a HARQ process identifier is also allocated for each SPS opportunity within the SPS cycle based at least in part on the number of SPS transmission opportunities included in the SPS cycle and the current SPS transmission opportunity; wherein the first signaling includes radio resource control signaling; wherein the method is implemented in a user equipment.

[0189] The processor 804 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 804 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 804. The processor 804 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 806) to cause the device 802 to perform various functions of the present disclosure.

[0190] The memory 806 may include random access memory (RAM) and read-only memory (ROM). The memory 806 may store computer-readable, computer-executable code, which includes instructions that, when executed by the processor 804, cause the device 802 to perform various functions described herein. The code may be stored in a non-transient computer-readable medium such as a system memory or another type of memory. In some implementations, the code may not be directly executed by the processor 804, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In addition, in some implementations, the memory 806 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0191] I / O controller 810 can manage input and output signals for device 802. I / O controller 810 can also manage peripheral devices that are not integrated into device 2402. In some implementations, I / O controller 810 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 810 can utilize an operating system, such as Or another known operating system. In some implementations, I / O controller 810 can be implemented as part of a processor such as processor 804. In some implementations, a user can interact with device 802 via I / O controller 810 or via hardware components controlled by I / O controller 810.

[0192] In some implementations, the device 802 may include a single antenna 812. However, in some other implementations, the device 802 may have more than one antenna 812 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be able to concurrently send or receive multiple wireless transmissions. The transceiver 808 may communicate bidirectionally via one or more antennas 812, wired or wireless links, as described herein. For example, the transceiver 808 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 808 may also include a modem to modulate packets to provide the modulated packets to one or more antennas 812 for transmission, and demodulate packets received from one or more antennas 812.

[0193] Fig. 9 An example of a block diagram 900 of a device 902 that supports SPS configuration including timer configuration according to aspects of the present disclosure is illustrated. The device 902 may be an example of a network entity 102 as described herein. The device 902 may support wireless communications with one or more network entities 102, UEs 104, or any combination thereof. The device 902 may include components for bidirectional communication, including components for sending and receiving communications (such as a processor 904, a memory 906, a transceiver 908, and an I / O controller 910). These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0194] The processor 904, memory 906, transceiver 908, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the present disclosure described herein. For example, the processor 904, memory 906, transceiver 908, or various combinations thereof, or components thereof may support methods for performing one or more of the operations described herein.

[0195] In some implementations, the processor 904, memory 906, transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of components configured or otherwise supported for performing the functions described in the present disclosure. In some implementations, the processor 904 and the memory 906 coupled to the processor 904 may be configured to perform one or more functions described herein (e.g., execution of instructions stored in the memory 906 by the processor 904).

[0196] For example, according to the examples disclosed herein, the processor 904 may support wireless communication at the device 902. The processor 904 may be configured to or otherwise support: sending a first signaling indicating a downlink SPS configuration to a UE network entity, wherein the downlink SPS configuration includes a timer configuration set; sending a second signaling indicating a PDSCH to the UE at an SPS transmission opportunity of the downlink SPS configuration.

[0197] Additionally or alternatively, the processor 904 may be configured to or otherwise support: wherein the timer configuration set includes a DRX retransmission timer and a DRX HARQ RTT timer; wherein the timer configuration set includes a DRX inactivity timer; wherein the timer configuration set includes a DRX on duration timer; wherein the SPS cycle includes multiple SPS transmission opportunities, and wherein for each SPS opportunity within the SPS cycle, a HARQ process identifier is assigned to the SPS opportunity based at least in part on the number of SPS transmission opportunities included in the SPS cycle and the current SPS transmission opportunity; wherein the first signaling includes radio resource control signaling; wherein the device includes a base station.

[0198] For example, according to the examples disclosed herein, the processor 904 may support wireless communication at the device 902. The processor 904 may be configured to or otherwise support components for: sending a first signaling indicating a downlink SPS configuration to a UE network entity, wherein the downlink SPS configuration includes a timer configuration set; and sending a second signaling indicating a PDSCH to the UE at an SPS transmission opportunity of the downlink SPS configuration.

[0199] Additionally or alternatively, the processor 904 may be configured to or otherwise support: wherein the timer configuration set includes a DRX retransmission timer and a DRX HARQ RTT timer; wherein the timer configuration set includes a DRX inactivity timer; wherein the timer configuration set includes a DRX on duration timer; wherein the SPS cycle includes multiple SPS transmission opportunities, and wherein for each SPS opportunity within the SPS cycle, a HARQ process identifier is assigned to the SPS opportunity based at least in part on the number of SPS transmission opportunities included in the SPS cycle and the current SPS transmission opportunity; wherein the first signaling includes radio resource control signaling; wherein the method is implemented in a base station.

[0200] The processor 904 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 904 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 904. The processor 904 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 906) to cause the device 902 to perform various functions of the present disclosure.

[0201] The memory 906 may include random access memory (RAM) and read-only memory (ROM). The memory 906 may store computer-readable, computer-executable code, which includes instructions that, when executed by the processor 904, cause the device 902 to perform various functions described herein. The code may be stored in a non-transient computer-readable medium such as a system memory or another type of memory. In some implementations, the code may not be directly executed by the processor 904, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In addition, in some implementations, the memory 906 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0202] I / O controller 910 can manage input and output signals for device 902. I / O controller 910 can also manage peripheral devices that are not integrated into device 2402. In some implementations, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 910 can utilize an operating system, such as

[0203] Or another known operating system. In some implementations, I / O controller 910 can be implemented as part of a processor such as processor 904. In some implementations, a user can interact with device 902 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0204] In some implementations, the device 902 may include a single antenna 912. However, in some other implementations, the device 902 may have more than one antenna 912 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be able to concurrently send or receive multiple wireless transmissions. The transceiver 908 may communicate bidirectionally via one or more antennas 912, wired or wireless links, as described herein. For example, the transceiver 908 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 908 may also include a modem to modulate packets to provide the modulated packets to one or more antennas 912 for transmission, and demodulate packets received from one or more antennas 912.

[0205] Fig.10 1000 is a flowchart of a method 1000 for supporting SPS configuration including timer configuration according to aspects of the present disclosure. The operations of the method 1000 may be implemented by the apparatus described herein or components thereof. For example, the operations of the method 1000 may be implemented by reference to Figures 1 to 9 The UE 104 described herein may be used to perform the functions described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0206] At 1005, the method may include receiving first signaling from a network entity indicating a downlink SPS configuration, wherein the downlink SPS configuration includes a set of timer configurations. The operations of 1005 may be performed according to examples described herein. In some implementations, aspects of the operations of 1005 may be described with reference to Figure 1 The device is used to perform the above.

[0207] At 1010, the method may include receiving second signaling indicating a PDSCH from a network entity at an SPS transmission opportunity of a downlink SPS configuration. The operations of 1010 may be performed according to examples described herein. In some implementations, aspects of the operations of 1010 may be described with reference to Figure 1 The device is used to perform the above.

[0208] At 1015, the method may include, in response to receiving a PDSCH on an SPS transmission opportunity, starting a first timer that is set according to a corresponding timer value of a timer configuration set. The operations of 1015 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1015 may be described with reference to Figure 1 The device is used to perform the above.

[0209] Fig.11 100 is a flowchart of a method 1100 for supporting SPS configuration including timer configuration according to aspects of the present disclosure. The operations of the method 1100 may be implemented by a device or component thereof as described herein. For example, the operations of the method 1100 may be implemented by a device or component thereof as described in reference to Figures 1 to 9 The UE 104 described herein performs. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0210] At 1105, the method may include: including a plurality of SPS transmission opportunities in the SPS cycle. The operations of 1105 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1105 may be described with reference to Figure 1 The device is used to perform the above.

[0211] At 1110, the method may include allocating a HARQ process identifier for each SPS opportunity within the SPS period based at least in part on the number of SPS transmission opportunities included in the SPS period and the current SPS transmission opportunity. The operations of 1110 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1110 may be described with reference to Figure 1 The device is used to perform the above.

[0212] Fig.12 1 is a flow chart of a method 1200 for supporting SPS configuration including timer configuration according to aspects of the present disclosure. The operations of the method 1200 may be implemented by the devices described herein or components thereof. For example, the operations of the method 1200 may be implemented by the devices described herein. Figures 1 to 9 The network entity 102 performs. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0213] At 1205, the method may include sending first signaling indicating a downlink SPS configuration to a UE network entity, wherein the downlink SPS configuration includes a timer configuration set. The operations of 1205 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1205 may be described with reference to Figure 1 The device is used to perform the above.

[0214] At 1210, the method may include sending a second signaling indicating a PDSCH to the UE on an SPS transmission opportunity of a downlink SPS configuration. The operations of 1210 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1210 may be described with reference to Figure 1 The device is used to perform the above.

[0215] Fig.13 1300 for supporting SPS configuration including timer configuration according to aspects of the present disclosure. The operations of the method 1300 may be implemented by the devices described herein or components thereof. For example, the operations of the method 1300 may be implemented by the devices described herein or components thereof. Figures 1 to 9 The network entity 102 performs. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0216] At 1305, the method may include: including a plurality of SPS transmission opportunities in the SPS cycle. The operations of 1305 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1305 may be described with reference to Figure 1 The device is used to perform the above.

[0217] At 1310, the method may include, for each SPS opportunity within the SPS period, assigning a HARQ process identifier to the SPS opportunity based at least in part on the number of SPS transmission opportunities included in the SPS period and the current SPS transmission opportunity. The operations of 1310 may be performed according to the examples described herein. In some implementations, aspects of the operations of 1310 may be described with reference to Figure 1 The device is used to perform the above.

[0218] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0219] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0220] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or sent via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination thereof. Features that implement the functions may also be physically located in various locations, including being distributed so that portions of the functions are implemented in different physical locations.

[0221] Computer readable medium includes both non-transient computer storage medium and communication medium, and communication medium includes any medium that promotes to transmit computer program from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.As an example and not limitation, non-transient computer readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage device, or can be used to carry or store desired program code parts in the form of instruction or data structure, and can be accessed by general or special-purpose computer or general or special-purpose processor Any other non-transient medium.

[0222] Any connection may be appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of computer-readable medium. Disks and optical disks as used herein include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and blue-ray disks, wherein disks typically reproduce data magnetically, and optical disks reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0223] As used herein, including in the claims, "or" used in a list of items (e.g., a list of items beginning with a phrase such as "at least one of..." or "one or more of..." or "one or both of...") represents an inclusive list, so that, for example, a list of at least one of A, B, or C represents A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Similarly, a list of at least one of A, B, or C represents A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on". In addition, as used herein (including in the claims), a "set" may include one or more elements.

[0224] When referring to a network entity, the terms "send," "receive," or "transmit" may refer to any part of a network entity of a RAN (e.g., base station, CU, DU, RU) that communicates with another device (e.g., directly or via one or more other network entities).

[0225] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "better than other examples." The detailed description includes specific details in order to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid confusing the concepts of the described examples.

[0226] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be clear to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to cause the UE to: receiving first signaling indicating a downlink semi-persistent scheduling (SPS) configuration from a network entity, wherein the downlink SPS configuration includes a timer configuration set; receiving, from the network entity, second signaling indicating a physical downlink shared channel (PDSCH) at an SPS transmission opportunity of the downlink SPS configuration; as well as In response to receiving the PDSCH at the SPS transmission opportunity, starting a first timer that is set according to a corresponding timer value of the timer configuration set.

2. The UE according to claim 1, wherein the timer configuration set comprises: Discontinuous Reception (DRX) retransmission timer and DRX Hybrid Automatic Repeat Request (HARQ) Round Trip Time (RTT) timer.

3. The UE according to claim 1, wherein starting the first timer is starting a DRX HARQ timer configured in the SPS configuration in a first symbol after the end of a corresponding transmission carrying downlink hybrid automatic repeat request (HARQ) feedback for the PDSCH. 4 . The UE of claim 1 , wherein the timer configuration set comprises a discontinuous reception (DRX) inactivity timer. 5 . The UE according to claim 4 , wherein starting the first timer is starting the DRX inactivity timer in response to receiving the PDSCH at the SPS transmission opportunity. 6 . The UE of claim 1 , wherein the timer configuration set comprises a discontinuous reception (DRX) on-duration timer. 7 . The UE according to claim 6 , wherein the at least one processor is configured to start the DRX on-duration timer for each SPS transmission opportunity of the downlink SPS configuration.

8. A UE according to claim 1, wherein the at least one processor is configured to: regard the SPS transmission timing of the downlink SPS configuration as a discontinuous reception (DRX) active time, and monitor a physical downlink control channel (PDCCH) at each SPS transmission timing.

9. A UE according to claim 1, wherein multiple SPS transmission opportunities are included in an SPS cycle, and wherein the processor is further configured to: allocate a hybrid automatic repeat request (HARQ) process identifier for each SPS opportunity within the SPS cycle based at least in part on the number of SPS transmission opportunities included in the SPS cycle and the current SPS transmission opportunity.

10. The UE of claim 1, wherein the first signaling comprises radio resource control signaling.

11. A base station device for wireless communication, comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to cause the base station to: Sending first signaling indicating a downlink semi-persistent scheduling (SPS) configuration to a user equipment (UE) network entity, wherein the downlink SPS configuration includes a timer configuration set; A second signaling indicating a physical downlink shared channel (PDSCH) is sent to the UE at an SPS transmission timing of the downlink SPS configuration.

12. A method performed by a user equipment (UE), the method comprising: receiving first signaling indicating a downlink semi-persistent scheduling (SPS) configuration from a network entity, wherein the downlink SPS configuration includes a timer configuration set; receiving, from the network entity, second signaling indicating a physical downlink shared channel (PDSCH) at an SPS transmission opportunity of the downlink SPS configuration; as well as In response to receiving the PDSCH at the SPS transmission opportunity, starting a first timer that is set according to a corresponding timer value of the timer configuration set.

13. A processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured to cause the processor to: receiving first signaling indicating a downlink semi-persistent scheduling (SPS) configuration from a network entity, wherein the downlink SPS configuration includes a timer configuration set; receiving, from the network entity, second signaling indicating a physical downlink shared channel (PDSCH) at an SPS transmission opportunity of the downlink SPS configuration; as well as In response to receiving the PDSCH at the SPS transmission opportunity, starting a first timer that is set according to a corresponding timer value of the timer configuration set.

14. The processor of claim 13, wherein the set of timer configurations comprises: Discontinuous Reception (DRX) retransmission timer and DRX Hybrid Automatic Repeat Request (HARQ) Round Trip Time (RTT) timer.

15. The processor of claim 13, wherein starting the first timer is starting a DRX HARQ timer configured in the SPS configuration in a first symbol after an end of a corresponding transmission carrying downlink hybrid automatic repeat request (HARQ) feedback for the PDSCH.

16. The processor of claim 13, wherein the set of timer configurations comprises a discontinuous reception (DRX) inactivity timer. 17 . The processor of claim 16 , wherein starting the first timer is starting the DRX inactivity timer in response to receiving the PDSCH on the SPS transmission opportunity.

18. The processor of claim 13, wherein the set of timer configurations comprises a discontinuous reception (DRX) on-duration timer.

19. The processor of claim 18, wherein the at least one controller is configured to start the DRX On Duration timer for each SPS transmission opportunity of the downlink SPS configuration.

20. The processor of claim 13, wherein the at least one controller is configured to: regard the SPS transmission timing of the downlink SPS configuration as a discontinuous reception (DRX) active time, and monitor a physical downlink control channel (PDCCH) at each SPS transmission timing.

Images