EP4569948A1 - Drift compensation of configured scheduling - Google Patents

Abstract

Systems, methods, apparatuses, and computer program products for extended reality use cases by introducing optimized semi-persistent scheduling configuration or configured grant configuration schemes. One method may include receiving, from a network entity, at least one adaptive semi-persistent scheduling configuration or configured grant configuration; receiving, from the network entity, an indication to trigger a semi-persistent scheduling or configured grant alignment; and adding or removing drift to a semi-persistent scheduling starting subframe and slot or configured grant starting subframe and slot. The semi-persistent scheduling or configured grant alignment is associated with the at least one adaptive semi-persistent scheduling configuration or configured grant configuration.

Description

TITLE:

DRIFT COMPENSATION OF CONFIGURED SCHEDUEING

TECHNICAL FIELD:

[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Third Generation Partnership Project (3GPP) Long Term Evolution (LTE), fifth generation (5G) radio access technology (RAT), new radio (NR) access technology, sixth generation (6G), and/or other communications systems. For example, certain example embodiments may relate to systems and/or methods for improving radio resource allocation methods for extended reality (XR) use cases by introducing optimized semi-persistent scheduling/configured grant (SPS/CG) schemes.

BACKGROUND:

[0002] Examples of mobile or wireless telecommunication systems may include radio frequency (RF) 5G RAT, the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), LTE Evolved UTRAN (E-UTRAN), LTE- Advanced (LTE-A), LTE-A Pro, NR access technology, and/or MulteFire Alliance. 5G wireless systems refer to the next generation (NG) of radio systems and network architecture. A 5G system is typically built on a 5G NR, but a 5G (or NG) network may also be built on E-UTRA radio. It is expected that NR can support service categories such as enhanced mobile broadband (eMBB), ultra-reliable low-latency-communication (URLLC), and massive machine-type communication (mMTC). NR is expected to deliver extreme broadband, ultra-robust, low-latency connectivity, and massive networking to support the Internet of Things (loT). The next generation radio access network (NG-RAN) represents the RAN for 5G, which may provide radio access for NR, LTE, and LTE-A. It is noted that the nodes in 5G providing radio access functionality to a user equipment (e.g. , similar to the Node B in UTRAN or the Evolved Node B (eNB) in LTE or base station as a generic term) may be referred to as next-generation Node B (gNB) when built on NR radio, and may be referred to as next-generation eNB (NG-eNB) when built on E-UTRA radio.

SUMMARY:

[0003] In accordance with some example embodiments, a method may include receiving, from a network entity, at least one adaptive semi-persistent scheduling configuration or configured grant configuration. The method may further include receiving, from the network entity, an indication to trigger a semi-persistent scheduling or configured grant alignment. The semi-persistent scheduling or configured grant alignment may be associated with the at least one adaptive semi-persistent scheduling configuration or configured grant configuration. The method may further include adding or removing drift to a semi-persistent scheduling or configured grant starting subframe and slot, responsive to the indication and in accordance with the adaptive configuration.

[0004] In accordance with certain example embodiments, an apparatus may include means for receiving, from a network entity, at least one adaptive semi-persistent scheduling configuration or configured grant configuration. The apparatus may further include means for receiving, from the network entity, an indication to trigger a semi-persistent scheduling or configured grant alignment. The semi-persistent scheduling or configured grant alignment may be associated with the at least one adaptive semi-persistent scheduling configuration or configured grant configuration. The apparatus may further include means for adding or removing drift to a semi-persistent scheduling or configured grant starting subframe and slot, responsive to the indication and in accordance with the adaptive configuration.

[0005] In accordance with various example embodiments, a non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method. The method may include receiving, from a network entity, at least one adaptive semi-persistent scheduling configuration or configured grant configuration. The method may further include receiving, from the network entity, an indication to trigger a semi-persistent scheduling or configured grant alignment. The semi-persistent scheduling or configured grant alignment may be associated with the at least one adaptive semi-persistent scheduling configuration or configured grant configuration. The method may further include adding or removing drift to a semi-persistent scheduling or configured grant starting subframe and slot, responsive to the indication and in accordance with the adaptive configuration.

[0006] In accordance with some example embodiments, a computer program product may perform a method. The method may include receiving, from a network entity, at least one adaptive semi-persistent scheduling configuration or configured grant configuration. The method may further include receiving, from the network entity, an indication to trigger a semi-persistent scheduling or configured grant alignment. The semi-persistent scheduling or configured grant alignment may be associated with the at least one adaptive semi- persistent scheduling configuration or configured grant configuration. The method may further include adding or removing drift to a semi-persistent scheduling or configured grant starting subframe and slot, responsive to the indication and in accordance with the adaptive configuration.

[0007] In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to receive, from a network entity, at least one adaptive semi-persistent scheduling configuration or configured grant configuration. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to receive, from the network entity, an indication to trigger a semi-persistent scheduling or configured grant alignment. The semi- persistent scheduling or configured grant alignment may be associated with the at least one adaptive semi-persistent scheduling configuration or configured grant configuration. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to add or remove drift to a semi-persistent scheduling or configured grant starting subframe and slot, responsive to the indication and in accordance with the adaptive configuration.

[0008] In accordance with various example embodiments, an apparatus may include circuitry configured to perform receiving, from a network entity, at least one adaptive semi-persistent scheduling configuration or configured grant configuration. The apparatus may further include circuitry configured to perform receiving, from the network entity, an indication to trigger a semi-persistent scheduling or configured grant alignment. The semi- persistent scheduling or configured grant alignment may be associated with the at least one adaptive semi-persistent scheduling configuration or configured grant configuration. The apparatus may further include circuitry configured to perform adding or removing drift to a semi-persistent scheduling or configured grant starting subframe and slot, responsive to the indication and in accordance with the adaptive configuration.

[0009] In accordance with some example embodiments, a method may include configuring a user equipment with at least one adaptive semi-persistent scheduling configuration or configured grant configuration to a user equipment. The method may further include transmitting, to the user equipment, an indication to trigger a semi- persistent scheduling or configured grant alignment to the user equipment. The semi- persistent scheduling or configured grant alignment may be associated with the at least one adaptive semi-persistent scheduling configuration or configured grant configuration. [0010] In accordance with certain example embodiments, an apparatus may include means for configuring a user equipment with at least one adaptive semi-persistent scheduling configuration or configured grant configuration to a user equipment. The apparatus may further include means for transmitting, to the user equipment, an indication to trigger a semi-persistent scheduling or configured grant alignment to the user equipment. The semi- persistent scheduling or configured grant alignment may be associated with the at least one adaptive semi-persistent scheduling configuration or configured grant configuration. [0011] In accordance with various example embodiments, a non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method. The method may include configuring a user equipment with at least one adaptive semi-persistent scheduling configuration or configured grant configuration to a user equipment. The method may further include transmitting, to the user equipment, an indication to trigger a semi-persistent scheduling or configured grant alignment to the user equipment. The semi-persistent scheduling or configured grant alignment may be associated with the at least one adaptive semi- persistent scheduling configuration or configured grant configuration.

[0012] In accordance with some example embodiments, a computer program product may perform a method. The method may include configuring a user equipment with at least one adaptive semi-persistent scheduling configuration or configured grant configuration to a user equipment. The method may further include transmitting, to the user equipment, an indication to trigger a semi-persistent scheduling or configured grant alignment to the user equipment. The semi-persistent scheduling or configured grant alignment may be associated with the at least one adaptive semi-persistent scheduling configuration or configured grant configuration.

[0013] In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to configure a user equipment with at least one adaptive semi-persistent scheduling configuration or configured grant configuration to a user equipment. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to transmit, to the user equipment, an indication to trigger a semi-persistent scheduling or configured grant alignment to the user equipment. The semi-persistent scheduling or configured grant alignment may be associated with the at least one adaptive semi-persistent scheduling configuration or configured grant configuration.

[0014] In accordance with various example embodiments, an apparatus may include circuitry configured to perform configuring a user equipment with at least one adaptive semi-persistent scheduling configuration or configured grant configuration to a user equipment. The apparatus may further include function circuitry configured to perform transmitting, to the user equipment, an indication to trigger a semi-persistent scheduling or configured grant alignment to the user equipment. The semi-persistent scheduling or configured grant alignment may be associated with the at least one adaptive semi- persistent scheduling configuration or configured grant configuration.

BRIEF DESCRIPTION OF THE DRAWINGS:

[0015] For a proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein:

[0016] FIG. 1 illustrates an example of SPS or CG configurations for different combinations of frame-rate (periodicity), quality (class), and frame type (multimodality).

[0017] FIG. 2 illustrates an example of desynchronization.

[0018] FIG. 3 illustrates an example of drift for the two SPS configurations as a function of the timeslot.

[0019] FIG. 4 illustrates an example of time drift for different extended reality (XR) frame rates and SPS configurations.

[0020] FIG. 5 illustrates an example of a traffic pattern of XR video stream.

[0021] FIG. 6 illustrates an example of a signaling diagram for configuration and realignment of SPS cycle with XR frame arrival for DL transmission according to certain example embodiments.

[0022] FIG. 7 illustrates an example of a signaling diagram for configuration and realignment of CG cycle with XR frame arrival for uplink (UL) transmission according to certain example embodiments.

[0023] FIG. 8 illustrates an example of a flow diagram of a method according to various example embodiments.

[0024] FIG. 9 illustrates an example of a flow diagram of a method according to various example embodiments. [0025] FIG. 10 illustrates an example of a flow diagram of another method according to certain example embodiments.

[0026] FIG. 11 illustrates an example of a flow diagram of another method according to some example embodiments.

[0027] FIG. 12 illustrates an example of a flow diagram of another method according to various example embodiments.

[0028] FIG. 13 illustrates an example of various network devices according to some example embodiments.

[0029] FIG. 14 illustrates an example of a 5G network and system architecture according to certain example embodiments.

DETAILED DESCRIPTION:

[0030] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for improving radio resource allocation methods for XR use cases by introducing optimized SPS/CG schemes is not intended to limit the scope of certain example embodiments, but is instead representative of selected example embodiments.

[0031] 3GPP working groups system aspect (SA)4 and radio access network (RAN)l have adopted a quasi-periodic, multimodal, and multi-class traffic model for XR applications. Specifically, XR traffic exhibits a bursty pattern with high data rate, and typically two burst types/classes that may be classified by their size. Traffic periodicity may be due to a 3D video generation process that may create a sequence of frames at a given sampling rate. For example, sampling rates may be 30, 60, 90, and 120 frames per second (fps) or cycles per second (Hz). Compression techniques used to reduce the bitrate may generate multiple types of frames that can be classified according to their size distribution. Compression can be achieved using both intra-frame and inter-frame coding. Specifically, intra-frame coding may use lossy coding techniques that only require the information carried in the compressed frame for decoding. In contrast, interframe coding may apply differential techniques on multiple frames to encode and transmit only the differences across consecutive frames. Frames generated using intra- frame coding may be referred to as “I-frames,” while frames generated using interframe coding may be referred to as “P-frames” or “B-frames,” depending on which differential technique is used. Inter-frame coding may provide higher compression (up to 5 and 10 times for P and B frames, respectively) at the cost of creating dependencies across frames. Therefore, compression techniques may generate a multimodal distribution of the frame size due to the superposition of different types of XR frames, each with its own distribution.

[0032] Similarly, rate adaptation implemented at the application layer may generate multiple classes of bursts. For example, the XR application may dynamically adjust the bitrate according to the status of the network and viewport information of the user (e.g., orientation of user’s view). For example, an XR application may respond to the decrease of the end-to-end connection speed by reducing the quality of the 3D video stream and/or decreasing the frame rate. This may result in a decrease of the 3D media content carried by all different frames.

[0033] SPS may offer a reduction in overhead as compared to sending DL dynamic scheduling grants (e.g.. reduced physical downlink control channel (PDCCH) overhead). In addition to the lower PDCCH overhead, SPS may offload the computational burden from a dynamic gNB medium access control (MAC) scheduler. 3GPP NR Rel-16 introduced several DL SPS enhancements to support URLLC and time sensitive communication (TSC) transmission of small payloads. However, SPS is not well suited for XR use cases; for example, SPS is a method where DL radio resources for sending one transport block with a regular time-periodicity is configured for a UE. Up to eight simultaneous active SPS configurations may be configured for a UE (configured via radio resource control (RRC) signaling), with periodicity of any integer of a slot (N*14), and minimum periodicity in Rel-15 of 10 ms. DL SPS also relies on separate configuration (RRC-based) and activation/deactivation (PDCCH addressed to configured scheduling radio network temporary identifier (CS-RNTI) can either signal and activate the configured DL assignment or deactivate it). Similarly, semi-persistent resource allocation in UL may specify CGs.

[0034] SPS/CG currently only allows the definition of a static integer period for the radio resources allocated to a certain UE. The integer periodicity may be specified with subframe (SF) or slot or sub-slot granularity depending on the RRC configuration. The non- integer periodicity of XR traffic (e.g. , XR traffic with periodicity of 16.67 ms which is not aligned with 5G numerology) may result in a time drift between the starting slot (or subframe) of the SPS period and the periodic arrival of XR traffic. For DL, time drift accumulate may over time as XR traffic drifts apart from SPS, and eventually result in desynchronization between the SPS resource period and the XR traffic. As a result, this may cause the loss of the XR frames since packet transmission may be delayed until the next configured opportunity while the packet delay budget (PDB) is usually smaller than XR traffic periodicity (e.g., PDB may be equal to 10 ms or 15 ms against 16.67 ms for XR periodicity at 60 fps).

[0035] Furthermore, the multiple combinations of frame rate (periodicity), quality (resolution), and frame type (compression) that may be used by the rate adaptation algorithm of an XR application to scale the quality up or down may require multiple SPS/CG configurations that result in multiple time-drifts (e.g., at least one time drift for each pair of SPS configuration and XR frame rate). For example, in a scenario with 4 frame rates (e.g., 30, 60, 90, and 120 Hz), two resolution qualities (e.g., Full HD and 4K) and two frame types (e.g., I-frame and P-frame), 16 combinations may be possible corresponding to 16 dedicated SPS configurations, in particular, a dedicated period and a number of time- frequency resources (i.e., number of consecutive TTIs and PRBs) for each combination, as illustrated in FIG. 1. The period of these 16 combinations, however, may not perfectly match the period of the combination, thus potentially resulting in 16 time drifts. Therefore, compensating for a single time drift is insufficient since properties such as magnitude, sign, and derivate may depend on the XR class and active SPS/CG configuration.

[0036] As an example, a typical frame rate of an XR application may be 60 fps, which may correspond to an average interarrival time (or periodicity) of video frames equal to 16.67 ms. Subcarrier spacing (SCS) may be 15 kHz, and the network may have a configured periodicity for DL SPS equal to 16 ms using periodicityExt in SPS-Config (e.g., 16 slots). Every 16 ms, the base station may schedule dedicated radio resources for a certain UE running a XR service. As shown in FIG. 2 and Table 1 (below), after 2 cycles, the XR packet arrival time and the SPS resource period may become desynchronized by 1 ms. More specifically, when the SPS scheduling opportunity is ready for the UE, the packet may miss the DL granted resource since it has not arrived yet.

[0037] The top portion of FIG. 2 illustrates XR frame arrivals, while the bottom portion illustrates subframes and SPS scheduling opportunities (solid blocks). The gap between integer periodicity of SPS cycle and non-integer periodicity of XR frames may accumulate over time. Thus, the SPS cycle may drift apart from the frame arrival. In case of 60 fps and SPS periodicity of 16 ms, the third frame (z.e., the second P-frame) may miss the configured scheduling opportunity. The base station may detect this mismatch, and attempt to use dynamic scheduling for the XR packet. The possibility to serve the packet may depend on the load (note that XR services may have heavy traffic requirements and the network may become quickly saturated). The base station may also trigger a RRC reconfiguration, but frequent reconfiguration may become necessary to resynchronize the SPS cycle with the XR periodicity. RRC reconfiguration may introduce extra-delay and heavy signaling overhead in the transmission.

[0038] FIG. 3 depicts changes in time drift of the two SPS configurations with periodicity of 16 ms and 17 ms, respectively. Positive drift between XR and SPS may correspond to XR frame arriving late with respect to scheduling grant, whereas negative drift between XR and SPS may correspond to XR frame arriving early with respect to scheduling grant. We can observe that the gap keeps accumulating. Using configuration SPS 1 after the second SPS cycle, the XR frame may be late and miss the scheduling opportunity (see Table 1 above). In contrast, with configuration SPS 2, the XR frame may arrive earlier than the scheduling opportunity so the frame may be transmitted when the SPS allocation becomes available. However, after 31 cycles, XR frames may become delayed beyond their PDB (31x(17-16.67)~10 ms). As a result, time drift may cause 3.3% and 6.25% (z.e., 1/16 and 1/30) frame errors with SPS 1 and SPS 2 configurations, respectively. However, XR traffic may require 99% of frames to be delivered within their PDB.

[0039] Time drifts for typical values of XR frame rate and integer periodicities of SPS configuration are illustrated in FIG. 4, where the drift resulting from the difference between the integer SPS periodicity and non-integer XR periodicity accumulates. Positive drift refers to the XR frame arriving on late with respect to the scheduling grant, thus forcing the scheduler to postpone the transmission to the next grant or handling it with dynamic scheduling. SPS with negative drift may start losing frames when drift approaches the PDB (10 ms in case of AR/VR services) minus the frame transmission latency.

[0040] FIG. 5 shows that SPS/CG reconfiguration does not resolve challenges with time drift. FIG. 5 illustrates a sequence of frames generated by XR application with framerate change and SPS reconfiguration. At time T2, the XR application downscales the framerate from 60 fps to 30 fps (time T1 corresponds to the instant of the last frame arrival generated with frame rate 60 fps). The frame rate downscaling results in an increase of the interarrival time between consecutive frames that trigger the reconfiguration of the SPS allocation either through RRC reconfiguration or with other schemes. However, the time-drift due to the mismatch of integer and non-integer periodicity keeps accumulating even if the reconfiguration at time T2 has realigned the XR traffic with the new SPS configuration. As illustrated in FIG. 5, even the reconfiguration has realigned SPS and XR traffic at time T2, the third frame generated at 30 fps arrives at time T3 on late by 0.67 ms with respect to the SPS scheduling grant. [0041] Certain example embodiments described herein may have various benefits and/or advantages to overcome the disadvantages described above. For example, certain example embodiments may enable fast correction of only SPS/CG resources when drift becomes too large, covers variable drift due to, for example, a change of XR frame rate, and provide solutions both for DL SPS and UL CG.

[0042] Some example embodiments may provide a simple and efficient scheme to solve time drift due to periodicity mismatch between SPS/CG configuration and XR traffic, and may apply beyond XR traffic, namely applications with periodicity mismatch between SPS/CG and traffic arrival process. Furthermore, various example embodiments may allow requirements of XR traffic to be satisfied even if SPS/CG and XR periods does not match perfectly, and include multiple embodiments with different signaling overhead for the realignment procedure. This includes multiple XR application scenarios with different properties for frame rate like fixed and dynamic frame rate, XR resolution adaptation, periodic and quasi-periodic traffic. Thus, certain example embodiments discussed below are directed to improvements in computer- related technology.

[0043] Various example embodiments discussed herein may compensate for time drift between configured resources, such as SPS/CG and XR traffic. The drift may be caused by, for example, the periodicity mismatch between a CG and the XR traffic. If the drift grows too large, it may cause the loss or delay of packets. Proposed herein are techniques to decide “when” and “how much” to compensate the drift between several XR classes and SPS/CG configurations. In particular, certain embodiments may include autonomous compensation, where both the UE and the network may apply an offset to the SPS/CG allocation every predetermined time period, such as parameter PeriodicitySyncCycle. As another example embodiment, when the network and/or UE is triggered, in DL, the network may signal an offset to the UE when the drift becomes larger than a threshold, such as a parameter PeriodicitySyncTh. Both the UE and the network apply the offset signaled by the network. In UL, the UE may request the network to compensate for the drift when the drift becomes larger than the threshold, (e.g.. PeriodicitySyncTh'). The network may then decide the amount of the offset, and subsequently notify the UE. Both the UE and the network may then apply the signaled offset. The network may then autonomously decide to compensate the drift, and signal the offset to the UE. Both the UE and the network may then apply the signaled offset.

[0044] As used in some embodiments herein, “drift” may refer to the accumulated time offset between the SPS/CG resources and an XR frame. For example, “adding drift” may be used for SPS/CG resources selection, wherein a later subframe may be selected as a new start subframe of the allocated SPS/CG resource in order to achieve the alignment between an arrival time of XR frame and a starting subframe of the SPS/CG resource. Similarly, “removing drift” may also be used for SPS/CG resources selection, wherein an earlier subframe may be selected as a new start subframe of the allocated SPS/CG resource in order to achieve the alignment between an arrival time of XR frame and a starting subframe of the SPS/CG resource. [0045] Some example embodiments described below may include enhancements to the configuration of the SPS and CG resource allocation to align the SPS/CG resource allocation pattern in line with the drift of the XR traffic pattern at the RAN. This adaptation may use an extension of an information element (IE) configuration exchanged through RRC configuration messages. In addition, various example embodiments may include enhancements to control messages exchanged between the base station and UE in order to dynamically adapt SPS/CG cycles according to traffic pattern and/or UE status. This may be achieved by defining a new control command to shift the next SPS/CG cycle by a certain offset, and may be (carried by, for example, MAC control element (MAC CE) or downlink control information (DCI)). Furthermore, various embodiments may include a design of a scheme to track drift between SPS/CG and XR traffic classes, and to decide when to compensate the drift without signaling. The UE and base station may compute the drift and when to compensate the drift, and use the definition of new behavior in the standard to keep network and UE aligned. As an example, tracking and compensation of drift may be based on multiple pairs of threshold <PeriodicitySyncCycle, PeriodicitySyncTh> (one for each XR class-SPS configuration) to determine when to compensate for drift (z.e., how much and when to compensate). Since a single pair of thresholds may not account for all time drift, new UE behavior may be defined to use those thresholds and signaling scheme to enforce ad-hoc compensation.

[0046] As illustrated in FIG. 2, the mismatch between the non-integer periodicity of XR frame generation and integer SPS/CG cycle defined by SPS/CG parameters may result in the loss or delay of XR frames. In particular, let t G {0,1, 2, 3,...} be the sequence number that identifies the SPS cycle, T ^PS E H be the integer duration of SPS period of the k* SPS configuration (e.g., periodicity field of SPS-Config), Tj^XR G H be the noninteger periodicity of frames of the 1^th XR class, 8j G R be the difference between SPS cycle and XR periodicity of the 1^th XR class, and j(t) be the time drift of the 1^th XR class. Time drift may be set to zero at the beginning if the traffic is aligned with the SPS configuration: Vi, Aj(t)=O. The number of SPS configurations may be the same as the number of XR classes and i=k. If the number of SPS/CG configurations is smaller than the number of XR classes (for example, due to the assignment of a SPS/CG configuration to multiple XR classes), the assumption that the number of SPS/CG configurations is the same as the number of XR classes (z.e., i=k) may be relaxed by replicating any SPS/CG configuration that has been assigned to multiple XR classes. The drift of 2 subframes may be added to the 4^th SPS resource, then the 4^th SPS resource can be aligned with the starting of the P-frame.

[0047] Some example embodiments may use tjj G {0,1, 2, 3, . . . } to denote the SPS cycle when the XR traffic change from j* class to 1^th class (for example, when the frame rate changes from j =30 to i=60 fps). If the configured resource is aligned with the first packet at the beginning, the time drift for the 1^th XR class may change according to:

, where

5_ki = T_k ^sps - T,^XR. (2)

[0048] The formula in equations (1) and (2) for the computation of the drift may be used for both UL and DL if both entities know the XR class and SPS/CG configuration. In the case of one SPS/CG configuration for one XR class (that is, i=k), this may be insignificant since the active SPS/CG configuration may also indicate the XR class, and the difference between the XR and SPS/CG periods in equation (2) (i.e, 8_ii) can be indicated as a parameter. In some embodiments described below, one SPS/CG configuration is assigned to one XR class, and a single index “i” may be used to identify both. If multiple XR classes are assigned to the same SPS/CG configuration, the difference between each XR and SPS/CG periods in equation (2) (i.e, 8_ki) may be provided during the configuration. In various example embodiments, the network (for DL) or the UE (for UL) may estimate and indicate to the other entity the amount of the drift. [0049] To compensate for the time drift, the UE may be informed of the periodicity mismatch, and when to anticipate or postpone the beginning of the next SPS/CG cycle (or equivalently, the end of the current SPS/CG cycle). The following SPS/CG parameters may be specified for each SPS/CG configuration, for example, in the SPS- Config IE (index “i” indicates the i^th SPS/CG configuration and 1^th XR class):

[0050] PeriodicityDrift (|8 : a drift parameter obtained as absolute value defined in equation (2).

[0051] PeriodicityDriftSign (sign(8j)): indicates the sign of the drift (for example, one bit).

[0052] PeriodicitySyncCycle (Pj^C): indicates the number of SPS/CG cycles before compensating the drift in the next SPS/CG cycle (for example, anticipating or postponing the start of the next SPS/CG cycle). This threshold may be used by the network and the UE as a default realignment period.

[0053] Periodicity Sync Th (P^): a threshold for the drift amount that triggers the realignment procedure. The drift compensation procedure may be initiated by the network with the transmission of a dedicated command; however, for UL transmission, the realignment procedure may also be initiated by the UE by sending a request for realignment of CG cycle and traffic.

[0054] Depending on the implementation, PeriodicityDrift and Periodicity DriftSign can be merged into one parameter as well.

[0055] The pair of thresholds PeriodicitySyncCycle and PeriodicitySyncTh may be determined based on (i) the difference between the XR traffic class and SPS/CG periods (that is, the difference computed in equation (2)), (ii) how much drift the SPS/CG allocation can tolerate before the XR expected arrival falls outside the SPS/CG allocation, and/or (iii) the maximum frequency of drift compensation (that is, how many times the drift is compensated during a certain time interval). Factors (i) and (ii) may depend on the XR application, while (iii) may be a choice of the network operator. However, the maximum frequency may be bounded depending on the drift and tolerance before the XR frames falls outside the SPS/CG allocation. In some example embodiments, the two thresholds may be computed where 8j — Tj is the drift, D is how much drift the SPS/CG allocation can tolerate before the XR expected arrival falls outside the SPS/CG allocation, and is the maximum frequency of drift compensation measured in terms of SPS/CG cycles before compensation procedure takes place. Thresholds PeriodicitySyncCycle and PeriodicitySyncThbe may be computed by solving the following linear system of equations:

P < Dl

8i ■ Pl < P , r_pT I which can be solved by first fixing P = and then computing P₍ ^c = min p [.

[0056] Parameters PeriodicitySyncCycle and PeriodicitySyncThbe may enable the UE and the base station to know when the timing of the SPS/CG pattern shall be adjusted, and the adjustments can be carried out in a predictive manner. In order to provide further flexibility, new control messages and procedures may be used to (i) initiate the adjustment of the SPS/CG pattern (that is, the procedure started by the network), (ii) request an adjustment of the SPS/CG pattern (that is, the request triggered by the UE and alternative to (i)), and (iii) apply the adjustment in a specific cycle (that is, the command sent by the base station). The signaling may be implemented as new LI and/or L2 control messages.

[0057] In various example embodiments discussed herein, after a DL assignment is configured for SPS, a MAC entity may consider sequentially that the N* downlink DL occurs in the slot for which: (numberOfSlotsPerFrame x SEN + slot number in the frame) =

[(numberOfSlotsPerFrame x SENstart time + slotstart time + offsetstart time) + N x (periodicity + offsetperiodicity) x numberOfSlotsPerFrame I 10] modulo (1024 x numberOfSlotsPerFrame), where SFNstart time and slotstart time are the SFN and slot, respectively, of the first transmission of PDSCH where the configured DL assignment was initialized or reinitialized. Offsetstart time and offsetperiodicity may be the offsets to be applied to the slot and period, respectively, communicated by the network with a realignment message.

[0058] After an UL grant is configured for a CG Type 1, the MAC entity may consider sequentially that the N* (N >= 0) UL grant occurs in the symbol for which: [(SFN x numberOfSlotsPerFrame x numberOfSymbolsPerSlot) + [(slot number in the frame offsetstart time) x numberOfSymbolsPerSlot] + symbol number in the slot + offset- symboLtart time] = {timeReferenceSFN x numberOfSlotsPerFrame x numberOfSymbolsPerSlot + timeDomainOffset x numberOfSymbolsPerSlot + S + N xperiodicity + offsetperiodicity)') modulo (1024 x numberOfSlotsPerFrame x numberOfSymbolsPerSlot). After an UL grant is configured for a CG Type 2, the MAC entity may consider sequentially that the N* (N >= 0) UL grant occurs in the symbol for which:

[0059] [(SFN x numberOfSlotsPerFrame x numberOfSymbolsPerSlot) + (slot number in the frame x numberOfSymbolsPerSlot) + symbol number in the slot] = [(SFNstart time x numberOfSlotsPerFrame x numberOfSymbolsPerSlot + (slotstart time + offsetstart time) x numberOfSymbolsPerSlot + symbolstart time + offset- symbolstart time) + N x periodicity + offsetperiodicity)} modulo (1024 x numberOfSlotsPerFrame x numberOfSymbolsPerSlot). SFNstart time, slotstart time, and symbolstart time may correspond with the SFN, slot, and symbol, respectively, of the first transmission opportunity of physical uplink shared channel (PUSCH) where the configured UL grant was initialized or reinitialized. In the formula offsetstart time, offset- symbolstart time and offsetperiodicity may correspond with the offsets to be applied to the slot, symbol and period, respectively, communicated by the network with a realignment message.

[0060] FIG. 6 illustrates an example of a signaling diagram depicting an enhanced SPS configuration for the transmission of DL traffic. UE 620 and network entity (NE) 630 may be similar to UE 1320 and NE 1310, as illustrated in FIG. 13, according to certain example embodiments. The realignment can be implemented through a control command or performed directly by NE 630 and UE 620 using the new parameters communicated during the initial configuration.

[0061] In various example embodiments, the parameters may be set as: Periodicity SyncCycle=4 (P = 4), Periodicity Drift=(). \ (|8| = 0.25), and

PeriodicityDriftSign=-l (sign(8) = —1). These parameters may force by default to increase the starting slot by 1 every four SPS/CG cycles.

[0062] At 601, NE 630 may configure UE 620 with one or more of parameters PeriodicityDrift, PeriodicityDriftSign, and/or PeriodicitySyncCycle, PeriodicitySyncCycleTh, as discussed above.

[0063] At 602-604, NE 630 may transmit DL traffic to UE 620 according to currently specified SPS operations (that is, transmission is performed in the granted DL SPS resources).

[0064] At 605, when the accumulated time drift exceeds a certain threshold (for example, PeriodicitySyncCycleTh), NE 630 may inform UE 620 to apply the realignment, communicating at least which SPS cycle will be resynchronized and/or the offset to be applied to the starting slot or subframe (SF). As an example, FIG. 6 depicts this as occurring during the third and sixth SPS cycles.

[0065] At 606, UE 620 may add or remove the drift to SPS starting SF and slot.

[0066] At 607-609, NE 630 may transmit DL traffic to UE 620 according to currently specified SPS operations (that is, transmission is performed in the granted DL SPS resources).

[0067] At 610, when the accumulated time drift exceeds a certain threshold (for example, PeriodicitySyncCycleTh), NE 630 may inform UE 620 to apply the realignment, communicating at least which SPS cycle will be resynchronized and/or the offset to be applied to the starting slot or SF.

[0068] In various example embodiments, the realignment may be implemented through a control command or performed directly by NE 630 and UE 620 using the new parameters communicated during the initial configuration. [0069] FIG. 7 illustrates an example of a signaling diagram depicting an enhanced CG configuration for UL transmissions. UE 720 and NE 730 may be similar to UE 1320 and NE 1310, as illustrated in FIG. 13, according to certain example embodiments. The realignment can be requested by UE 720 and implemented through a control command sent by NE 730 or performed directly by UE 720 and NE 730 using the new parameters communicated during the initial configuration.

[0070] In various example embodiments, the parameters may be set as: Periodicity SyncCycle=4 (P = 4), Periodicity Drift=0. \ (|8| = 0.25), and

PeriodicityDriftSign=-l (sign(8) = —1). These parameters may force by default to increase the starting slot by 1 every four SPS/CG cycles.

[0071] At 701, NE 730 may configure UE 720 with one or more of parameters PeriodicityDrift, PeriodicityDriftSign, and/or PeriodicitySyncCycle, PeriodicitySyncCycleTh, as discussed above.

[0072] At 702, UE 720 may transmit UL traffic to NE 730 according to currently specified CG operations (that is, transmission is performed in the granted UL CG resources).

[0073] At 703, when the accumulated time drift exceeds the configured threshold PeriodicitySyncTh, UE 720 may transmit a request for realignment to NE 730 (message 1).

[0074] At 704, UE 720 may transmit UL traffic to NE 730 according to currently specified CG operations (that is, transmission is performed in the granted UL CG resources).

[0075] At 705, NE 730 may determine the amount of realignment (e.g.. the offset) and the CG cycle to be realigned, and communicate this information to UE 720 (message 2).

[0076] At 706, UE 720 may transmit UL traffic to NE 730 according to currently specified CG operations (that is, transmission is performed in the granted UL CG resources). [0077] At 707, UE 720 may add or remove drift to the CG starting SF and slot.

[0078] At 708-710, UE 720 may transmit UL traffic to NE 730 according to currently specified CG operations (that is, transmission is performed in the granted UL CG resources).

[0079] At 711, NE 730 may determine the amount of realignment (e.g., the offset) and the CG cycle to be realigned, and communicate this information to UE 720.

[0080] At 712, UE 720 and NE 730 may apply an offset to the starting slot and/or SF indicated by NE 730. In FIG. 7, offset is applied to CG cycles 4 and 7.

[0081] In various example embodiments, the decision on the compensation may be decided autonomously by NE 730 for the realignment decision for CG cycle 7, which is signaled in CG cycle 6. The decision may be made by NE 730 after a number of cycles PeriodicitySyncCycle from the previous re-alignment request (in the figure 4 CG cycles after CG cycle 3, hence in CG cycle 7). NE 730 can may decide based on other criteria; for example, if UE 720 sends a buffer status report (BSR) to transmit traffic before the CG allocation.

[0082] FIG. 8 illustrates an example of a flow diagram of a method that may be performed by a UE, such as UE 1320 illustrated in FIG. 13, according to various example embodiments. In particular, FIG. 8 depicts the realignment procedure implemented by the UE, where Pc (PeriodicitySyncCycle) is the realignment parameter used by the UE and the network by default to enforce the realignment. PT (PeriodicitySyncCycleTh) is the realignment parameter used by the UE to trigger the request of realignment. In this example, MAC CE is taken as example to carry realignment command.

[0083] At 801, the method may include determining whether XR class changes from j to i. If so, the method may include changing SPS configuration from j to i at 802, and at 803, updating drift of class A₍ (t — 1) = A_; (t — 1).

[0084] At 804, the method may include detecting a start of a new SPS cycle i. At 805, the method may include updating drift of class A₍ (t) = A_; (t — 1) + 8_L. [0085] At 806, the method may include determining whether a MAC CE realignment has been received. If yes, at 807, the method may include performing realignment by changing starting slot and/or SF; for example, (if sign (5_;) > 0), start slot may be decreased (remove offset), while (if sign(Aj) < 0), start slot may be increased (add offset). At 808, an incremental counter t may be increased by 1. After receiving the alignment indication, the realignment may be applied to the SPS/CG resource right after receiving the indication.

[0086] If it is determined at 806 that a MAC CE realignment has not been received, at 809, the method may include determining whether mod(t, P ) = 0; if yes, the method may proceed to 807. If not, at 810, the method may include determining whether Aj(t) > P ; if so the method may include, at 811, requesting realignment for the next period, and then proceeding to 808. Identifying the first subframe may be based upon PeriodicitySyncCycle (Pc), which may be used by the gNB and the UE as a default realignment period. For example, assuming PeriodicitySyncCycle^ (i.e.. the realignment occurs every 4^th SPS/CG resource) and the index of the first SPS/CG resource is 0, realignment may occur on the SPS/CG resource if mod (SPS/CG resource index, Periodicity SyncCycle)=Q where mod represents modulo operation.

[0087] The UE and gNB may continue updating the time drift Aj(t) at each SPS/CG iteration for the 1^th XR class. Upon reception of the realignment command and/or after a certain number of iterations (parameter PeriodicitySyncCycle) , the UE may increase or decrease the current SPS/CG cycle by an offset. This offset may depend on the time drift Aj(t), and may be computed, for example, as offset = Aj(t) = tj x 8, where tj measures the time instant when the 1^th SPS configuration of the 1^th XR class has been triggered. The time instant t_L can be computed as the difference between the absolute SPS iteration and the iteration when the traffic switches from j^th class to i-class: t_L = t — tj . Another way of computing the offset is by measuring the difference between the actual XR frame arrival and the starting slot/subframe of the dedicated SPS/CG configuration. In another embodiment, this offset can be communicated by the network. If the drift becomes larger than a certain threshold (Periodicity SyncTh), then the UE may initiate the realignment procedure by sending a realignment request to the network. [0088] In some example embodiments, once the necessary parameters, for example periodicity of XR traffic and SPS/CG resources, PeriodicitySyncCycle, are configured, the UE may be configured to execute the realignment process after a number of SPS/CG cycles equal to PeriodicitySyncCycle since the last realignment. Such behavior may be set as fallback behavior if no realignment command received.

[0089] FIG. 9 illustrates an example of a flow diagram of a method that may be performed by a UE, such as UE 1320 illustrated in FIG. 13, according to various example embodiments. The realignment can be implemented through a control command or performed directly by the UE or a NE (such as NE 1310 illustrated in FIG. 13) using the new parameters communicated during the initial configuration.

[0090] In various example embodiments, the parameters may be set as Periodicity SyncCycle=4 (P = 4), Periodicity Drift=0. \ (|8| = 0.25), and

PeriodicityDriftSign=-l (sign(8) = —1). These parameters may force by default to increase the starting slot by 1 every four SPS/CG cycles.

[0091] At 901, the method may include receiving a configuration from the NE with one or more of parameters Periodicity Drift, PeriodicityDriftSign, and/or PeriodicitySyncCycle, PeriodicitySyncCycleTh, as discussed above.

[0092] At 902-904, the method may include receiving DL traffic from the NE according to currently specified SPS operations (that is, transmission is performed in the granted DL SPS resources).

[0093] At 905, when the accumulated time drift exceeds a certain threshold (for example, PeriodicitySyncCycleTh), the method may include receiving instructions from the NE to apply the realignment, and an indication of at least which SPS cycle will be resynchronized and/or the offset to be applied to the starting slot or subframe (SF). This may occur during the third and sixth SPS cycles. [0094] At 906, the method may include adding or removing the drift to SPS starting SF and slot.

[0095] At 907-909, the method may include receiving DL traffic from the NE according to currently specified SPS operations (that is, transmission is performed in the granted DL SPS resources).

[0096] At 910, when the accumulated time drift exceeds a certain threshold (for example, PeriodicitySyncCycleTh), the method may include receiving instructions from the NE to apply the realignment, and an indication of at least which SPS cycle will be resynchronized and/or the offset to be applied to the starting slot or SF.

[0097] In various example embodiments, the realignment may be implemented through a control command or performed directly by the NE and UE using the new parameters communicated during the initial configuration.

[0098] FIG. 10 illustrates an example of a flow diagram of a method that may be performed by a NE, such as NE 1310 illustrated in FIG. 13, according to various example embodiments. The realignment can be implemented through a control command or performed directly by the NE or a UE (such as UE 1320 illustrated in FIG. 13) using the new parameters communicated during the initial configuration.

[0099] In various example embodiments, the PeriodicitySyncCycle= (P = 4), PeriodicityDrift=GA (|8| = 0.25), and PeriodicityDriftSign=A (sign(8) = —1). These parameters may force by default to increase the starting slot by 1 every four SPS/CG cycles.

[0100] At 1001, the method may include transmitting a configuration to the UE with one or more of parameters Periodicity Drift, PeriodicityDriftSign, and/or PeriodicitySyncCycle, PeriodicitySyncCycleTh, as discussed above.

[0101] At 1002-1004, the method may include transmitting DL traffic to the UE according to currently specified SPS operations (that is, transmission is performed in the granted DL SPS resources). [0102] At 1005, when the accumulated time drift exceeds a certain threshold (for example, PeriodicitySyncCycleTh), the method may include transmitting instructions to the UE to apply the realignment, communicating at least which SPS cycle will be resynchronized and/or the offset to be applied to the starting slot or subframe (SF). This may occur during the third and sixth SPS cycles.

[0103] At 1006-1008, the method may include transmitting DL traffic to the UE according to currently specified SPS operations (that is, transmission is performed in the granted DL SPS resources).

[0104] At 1009, when the accumulated time drift exceeds a certain threshold (for example, PeriodicitySyncCycleTh), the method may include transmitting instructions to the UE to apply the realignment, communicating at least which SPS cycle will be resynchronized and/or the offset to be applied to the starting slot or SF.

[0105] In various example embodiments, the realignment may be implemented through a control command or performed directly by the NE and UE using the new parameters communicated during the initial configuration.

[0106] FIG. 11 illustrates an example of a flow diagram of a method that may be performed by a UE, such as UE 1320 illustrated in FIG. 13, according to various example embodiments. The realignment can be requested by the UE and implemented through a control command sent by a NE or performed directly by the UE and the NE using the new parameters communicated during the initial configuration.

[0107] In some example embodiments, PeriodicitySyncCycle=‘ (P = 4), PeriodicityDrift=GA (|8| = 0.25), and PeriodicityDriftSign=- (sign(8) = —1). These parameters may force by default to increase the starting slot by 1 every four SPS/CG cycles.

[0108] At 1101, the method may include receiving a configuration with one or more of drift parameters PeriodicityDrift, PeriodicityDriftSign, and/or PeriodicitySyncCycle, PeriodicitySyncCycleTh, as discussed above. [0109] At 1102, the method may include transmitting UL traffic to the NE according to currently specified CG operations (that is, transmission is performed in the granted UL CG resources).

[0110] At 1103, when the accumulated time drift exceeds the configured threshold PeriodicitySyncTh, the method may include transmitting a request for realignment to the NE (message 1).

[0111] At 1104, the method may include transmitting UL traffic to the NE according to currently specified CG operations (that is, transmission is performed in the granted UL CG resources).

[0112] At 1105, the method may include receiving an indication of a determination of an amount of realignment (e.g., the offset) and the CG cycle to be realigned (message 2).

[0113] At 1106, the method may include transmitting UL traffic to the NE according to currently specified CG operations (that is, transmission is performed in the granted UL CG resources).

[0114] At 1107, the method may include adding or removing drift to the CG starting SE and slot.

[0115] At 1108-1110, the method may include transmitting UL traffic to the NE according to currently specified CG operations (that is, transmission is performed in the granted UL CG resources).

[0116] At 1111, the method may include receiving an indication of a determination of an amount of realignment (e.g.. the offset) and the CG cycle to be realigned (message 2).

[0117] At 1112, the method may include applying an offset to the starting slot and/or SE indicated by the NE.

[0118] In various example embodiments, the decision on the compensation may be decided autonomously by the NE for the realignment decision for CG cycle 7, which is signaled in CG cycle 6. The decision may be made by the NE after a number of cycles PeriodicitySyncCycle from the previous re-alignment request (in the figure 4 CG cycles after CG cycle 3, hence in CG cycle 7). The NE may decide based on other criteria; for example, if the UE sends a buffer status report (BSR) to transmit traffic before the CG allocation.

[0119] FIG. 12 illustrates an example of a flow diagram of a method that may be performed by a NE, such as NE 1310 illustrated in FIG. 13, according to various example embodiments. The realignment can be requested by a UE and implemented through a control command sent by the NE or performed directly by the UE and the NE using the new parameters communicated during the initial configuration.

[0120] In certain example embodiments, the parameters may be set as PeriodicitySyncCycle^ (P = 4), Periodicity Drift=0. \ (|8| = 0.25), and PeriodicityDriftSign=-l (sign(8) = —1). These parameters may force by default to increase the starting slot by 1 every four SPS/CG cycles.

[0121] At 1201, the method may include transmitting to the UE a configuration with one or more of drift parameters Periodicity Drift, PeriodicityDriftSign, and/or PeriodicitySyncCycle, PeriodicitySyncCycleTh, as discussed above.

[0122] At 1202, the method may include transmitting UL traffic to the NE according to currently specified CG operations (that is, transmission is performed in the granted UL CG resources).

[0123] At 1203, when the accumulated time drift exceeds the configured threshold PeriodicitySyncTh, the method may include transmitting a request for realignment to the NE (message 1).

[0124] At 1204, the method may include transmitting UL traffic to the NE according to currently specified CG operations (that is, transmission is performed in the granted UL CG resources).

[0125] At 1205, the method may include transmitting an indication of a determination of an amount of realignment (e.g., the offset) and the CG cycle to be realigned (message 2). [0126] At 1206, the method may include transmitting UL traffic to the NE according to currently specified CG operations (that is, transmission is performed in the granted UL CG resources).

[0127] At 1207, the method may include adding or removing drift to the CG starting SF and slot.

[0128] At 1208-1210, the method may include transmitting UL traffic to the NE according to currently specified CG operations (that is, transmission is performed in the granted UL CG resources).

[0129] At 1211, the method may include transmitting an indication of a determination of an amount of realignment (e.g., the offset) and the CG cycle to be realigned (message 2).

[0130] In various example embodiments, the decision on the compensation may be decided autonomously by the NE for the realignment decision for CG cycle 7, which is signaled in CG cycle 6. The decision may be made by the NE after a number of cycles PeriodicitySyncCycle from the previous re-alignment request (in the figure 4 CG cycles after CG cycle 3, hence in CG cycle 7). The NE may decide based on other criteria; for example, if the UE sends a buffer status report (BSR) to transmit traffic before the CG allocation.

[0131] FIG. 13 illustrates an example of a system according to certain example embodiments. In one example embodiment, a system may include multiple devices, such as, for example, NE 1310 and/or UE 1320.

[0132] NE 1310 may be one or more of a base station, such as an eNB or gNB, a serving gateway, a server, and/or any other access node or combination thereof.

[0133] NE 1310 may further comprise at least one gNB-CU, which may be associated with at least one gNB-DU. The at least one gNB-CU and the at least one gNB-DU may be in communication via at least one Fl interface, at least one X_n-C interface, and/or at least one NG interface via a 5GC. [0134] UE 1320 may include one or more of a mobile device, such as a mobile phone, smart phone, personal digital assistant (PDA), tablet, or portable media player, digital camera, pocket video camera, video game console, navigation unit, such as a global positioning system (GPS) device, desktop or laptop computer, single-location device, such as a sensor or smart meter, or any combination thereof. Furthermore, NE 1310 and/or UE 1320 may be one or more of a citizens broadband radio service device (CBSD).

[0135] NE 1310 and/or UE 1320 may include at least one processor, respectively indicated as 1311 and 1321. Processors 1311 and 1321 may be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or comparable device. The processors may be implemented as a single controller, or a plurality of controllers or processors.

[0136] At least one memory may be provided in one or more of the devices, as indicated at 1312 and 1322. The memory may be fixed or removable. The memory may include computer program instructions or computer code contained therein. Memories 1312 and 1322 may independently be any suitable storage device, such as a non-transitory computer-readable medium. The term “non-transitory,” as used herein, may correspond to a limitation of the medium itself (z.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM). A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memories may be combined on a single integrated circuit as the processor, or may be separate from the one or more processors. Furthermore, the computer program instructions stored in the memory, and which may be processed by the processors, may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.

[0137] Processors 1311 and 1321, memories 1312 and 1322, and any subset thereof, may be configured to provide means corresponding to the various blocks of FIGs. 1-12. Although not shown, the devices may also include positioning hardware, such as GPS or micro electrical mechanical system (MEMS) hardware, which may be used to determine a location of the device. Other sensors are also permitted, and may be configured to determine location, elevation, velocity, orientation, and so forth, such as barometers, compasses, and the like.

[0138] As shown in FIG. 13, transceivers 1313 and 1323 may be provided, and one or more devices may also include at least one antenna, respectively illustrated as 1314 and 1324. The device may have many antennas, such as an array of antennas configured for multiple input multiple output (MIMO) communications, or multiple antennas for multiple RATs. Other configurations of these devices, for example, may be provided. Transceivers 1313 and 1323 may be a transmitter, a receiver, both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.

[0139] The memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus, such as UE, to perform any of the processes described above (z.e., FIGs. 1-12). Therefore, in certain example embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain example embodiments may be performed entirely in hardware.

[0140] In certain example embodiments, an apparatus may include circuitry configured to perform any of the processes or functions illustrated in FIGs. 1-12. As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry), (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and/or digital hardware circuit(s) with software/firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions), and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0141] FIG. 14 illustrates an example of a 5G network and system architecture according to certain example embodiments. Shown are multiple network functions that may be implemented as software operating as part of a network device or dedicated hardware, as a network device itself or dedicated hardware, or as a virtual function operating as a network device or dedicated hardware. The NE and UE illustrated in FIG. 14 may be similar to NE 1310 and UE 1320, respectively. The user plane function (UPF) may provide services such as intra-RAT and inter-RAT mobility, routing and forwarding of data packets, inspection of packets, user plane quality of service (QoS) processing, buffering of DL packets, and/or triggering of DL data notifications. The application function (AF) may primarily interface with the core network to facilitate application usage of traffic routing and interact with the policy framework.

[0142] According to certain example embodiments, processors 1311 and 1321, and memories 1312 and 1322, may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceivers 1313 and 1323 may be included in or may form a part of transceiving circuitry.

[0143] In some example embodiments, an apparatus (e.g., NE 1310 and/or UE 1320) may include means for performing a method, a process, or any of the variants discussed herein. Examples of the means may include one or more processors, memory, controllers, transmitters, receivers, and/or computer program code for causing the performance of the operations.

[0144] In various example embodiments, apparatus 1320 may be controlled by memory 1322 and processor 1321 to receive, from a network entity, at least one adaptive semi- persistent scheduling configuration or configured grant configuration; receive, from the network entity, an indication to trigger a semi-persistent scheduling or configured grant alignment associated with the adaptive configuration; and add or remove drift to a semi- persistent scheduling or configured grant starting subframe and slot, responsive to the indication and in accordance with the adaptive configuration.

[0145] Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for receiving, from a network entity, at least one adaptive semi-persistent scheduling configuration or configured grant configuration; means for receiving, from the network entity, an indication to trigger a semi-persistent scheduling or configured grant alignment associated with the adaptive configuration; and means for adding or removing drift to a semi-persistent scheduling or configured grant starting subframe and slot, responsive to the indication and in accordance with the adaptive configuration.

[0146] In various example embodiments, apparatus 1310 may be controlled by memory 1312 and processor 1311 to configure a user equipment with at least one adaptive semi- persistent scheduling configuration or configured grant configuration to a user equipment; and transmit, to the user equipment, an indication to trigger a semi-persistent scheduling or configured grant alignment associated with the adaptive configuration to the user equipment.

[0147] Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for configuring a user equipment with at least one adaptive semi-persistent scheduling configuration or configured grant configuration to a user equipment; and means for transmitting, to the user equipment, an indication to trigger a semi-persistent scheduling or configured grant alignment associated with the adaptive configuration to the user equipment.

[0148] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “various embodiments,” “certain embodiments,” “some embodiments,” or other similar language throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an example embodiment may be included in at least one example embodiment. Thus, appearances of the phrases “in various embodiments,” “in certain embodiments,” “in some embodiments,” or other similar language throughout this specification does not necessarily all refer to the same group of example embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.

[0149] As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or,” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0150] Additionally, if desired, the different functions or procedures discussed above may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions or procedures may be optional or may be combined. As such, the description above should be considered as illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.

[0151] One having ordinary skill in the art will readily understand that the example embodiments discussed above may be practiced with procedures in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although some embodiments have been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the example embodiments.

[0152] Partial Glossary

[0153] 3GPP Third Generation Partnership Project

[0154] 5G Fifth Generation

[0155] 5GC Fifth Generation Core

[0156] 5GS Fifth Generation System

[0157] 6G Sixth Generation

[0158] AR Augmented Reality

[0159] ASIC Application Specific Integrated Circuit

[0160] BS Base Station

[0161] CBSD Citizens Broadband Radio Service Device

[0162] CG Configured Grant

[0163] CN Core Network

[0164] CPU Central Processing Unit

[0165] CS-RNTI Configured Scheduling Radio Network Temporary Identifier

[0166] DCI Downlink Control Information

[0167] DL Downlink

[0168] E2E End-to-End

[0169] eMBB Enhanced Mobile Broadband

[0170] eMTC Enhanced Machine Type Communication

[0171] eNB Evolved Node B

[0172] EPS Evolved Packet System

[0173] gNB Next Generation Node B

[0174] GPS Global Positioning System

[0175] HARQ Hybrid Automatic Repeat Request

[0176] HDD Hard Disk Drive

[0177] IE Information Element [0178] IIoT Industrial Internet of Things [0179] KPI Key Performance Indicator [0180] LTE Long-Term Evolution [0181]LTE-A Long-Term Evolution Advanced [0182] MAC Medium Access Control [0183] MIMO Multiple Input Multiple Output [0184] mMTC Massive Machine Type Communication [0185] MR Mixed Reliability [0186] MTC Machine Type Communication [0187] NAS Non-Access Stratum [0188] NE Network Entity [0189] NG Next Generation [0190]NG-eNB Next Generation Evolved Node B [0191]NG-RAN Next Generation Radio Access Network [0192] NR New Radio [0193] PDA Personal Digital Assistance [0194] PDB Packet Delay Budget [0195]PDCCH Physical Downlink Control Channel [0196] PDU Protocol Data Unit [0197]PUSCH Physical Uplink Shared Channel [0198] QoS Quality of Service [0199] RAM Random Access Memory [0200] RAN Radio Access Network [0201] RAT Radio Access Technology [0202] RE Resource Element [0203] RRC Radio Resource Control [0204] RS Reference Signal [0205] SCS Subcarrier Spacing [0206] SDU Service Data Unit

[0207] SF Subframe

[0208] SFN System Frame Number

[0209] SMF Session Management Function

[0210] SN Sequence Number

[0211] SPS Semi-Persistent Scheduling

[0212] SRB Signaling Radio Bearer

[0213] TB Transport Block

[0214] TSC Time Sensitive Communications

[0215] Tx Transmission

[0216] UE User Equipment

[0217] UL Uplink

[0218] UMTS Universal Mobile Telecommunications System

[0219] UPF User Plane Function

[0220]URLLC Ultra-Reliable and Low-Latency Communication

[0221]UTRAN Universal Mobile Telecommunications System Terrestrial Radio

Access Network

[0222] VR Virtual Reality

[0223] WLAN Wireless Local Area Network

[0224] XR Extended Reality

Claims

WE CLAIM:

1. An apparatus comprising: means for receiving, from a network entity, at least one adaptive semi-persistent scheduling configuration or configured grant configuration; means for receiving, from the network entity, an indication to trigger a semi- persistent scheduling or configured grant alignment, wherein the semi-persistent scheduling or configured grant alignment is associated with the at least one adaptive semi-persistent scheduling configuration or configured grant configuration; and means for adding or removing drift to a semi-persistent scheduling starting subframe and slot or configured grant starting subframe and slot, responsive to the indication and in accordance with the adaptive configuration.

2. The apparatus of claim 1, wherein the at least one received adaptive configuration comprises an indication of a sign of the drift.

3. The apparatus of any of claims 1 or 2, wherein the at least one received adaptive configuration comprises an indication of an absolute value of drift.

4. The apparatus of any of claims 1-3, wherein the at least one received adaptive configuration comprises an indication of a number of semi-persistent scheduling or configured grant cycles before compensating the drift in the next semi-persistent scheduling or configured grant cycle.

5. The apparatus of any of claims 1-4, wherein the at least one received adaptive configuration comprises an indication of a threshold for the drift amount that triggers a realignment procedure.

6. The apparatus of any of claims 1-5, further comprising: means for transmitting a request for realignment of the of the adaptive configuration to a network entity.

7. The apparatus of any of claims 1-6, further comprising: means for determining the drift is larger than the configured threshold.

8. The apparatus of any of claims 1-7, further comprising: means for determining whether a modulo operation is equal to 0.

9. The apparatus of any of claims 1-8, further comprising: means for performing realignment by adjusting the starting subframe and slot, wherein drift is added if the sign of the drift is less than zero, and drift is removed if the sign of the drift is greater than zero.

10. An apparatus comprising: means for configuring a user equipment with at least one adaptive semi-persistent scheduling configuration or configured grant configuration to a user equipment; and means for transmitting, in response to configuring the user equipment, an indication to trigger a semi-persistent scheduling or configured grant alignment, wherein the semi-persistent scheduling or configured grant alignment is associated with the at least one adaptive semi-persistent scheduling configuration or configured grant configuration.

11. The apparatus of claim 10, wherein the at least one received adaptive configuration comprises an indication of a sign of the drift.

12. The apparatus of any of claims 10 or 11, wherein the at least one received adaptive configuration comprises an indication of an absolute value of drift.

13. The apparatus of any of claims 10-12, wherein the at least one received adaptive configuration comprises an indication of a number of semi-persistent scheduling or configured grant cycles before compensating the drift in the next semi-persistent scheduling or configured grant cycle.

14. The apparatus of any of claims 10-13, wherein the at least one received adaptive configuration comprises an indication of a threshold for the drift amount that triggers a realignment procedure.

15. The apparatus of any of claims 10-14, further comprising: means for receiving a request for realignment of the of the adaptive configuration from the user equipment.