Compensating for drift in configured scheduling

Abstract

A system, method, apparatus, and computer program product for augmented reality use cases by introducing an optimized semi-persistent scheduling or configured grant configuration scheme. One method may include receiving at least one adaptive semi-persistent scheduling or configured grant configuration from a network entity, receiving an indication from the network entity to trigger an adjustment of the semi-persistent scheduling or configured grant, and adding or removing drift to the semi-persistent scheduling start subframe and slot or the configured grant start subframe and slot. The adjustment of the semi-persistent scheduling or configured grant is associated with the at least one adaptive semi-persistent scheduling or configured grant configuration.

Description

[Technical Field]

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

[0002] Examples of mobile or wireless telecommunications systems may include radio frequency (RF) 5G RAT, 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 MultiFire Alliance. 5G wireless systems refer to the next generation (NG) of radio systems and network architectures. 5G systems are generally built on 5G NR, but 5G (or NG) networks may also be built on E-UTRA radios. NR is expected to be able to support service categories such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). NR is expected to provide ultra-wideband, ultra-robust, low-latency connectivity, and massive networking to support the Internet of Things (IoT). Next Generation Radio Access Network (NG-RAN) refers to the RAN for 5G, which can provide radio access for NR, LTE, and LTE-A. Note that the 5G node that provides radio access functionality to user equipment (e.g., similar to a Node B in UTRAN or an Evolved Node B (eNB) in LTE, or collectively a base station) may be called a Next Generation Node B (gNB) when built on NR radios, or a Next Generation eNB (NG-eNB) when built on E-UTRA radios. Summary of the Invention [Means for solving the problem]

[0003] According to some demonstrative embodiments, the method may include receiving at least one adaptive semi-persistent scheduling or configured grant configuration from a network entity. The method may further include receiving an indication from the network entity to trigger an adjustment of the semi-persistent scheduling or configured grant. The adjustment of the semi-persistent scheduling or configured grant may be associated with the at least one adaptive semi-persistent scheduling 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 in response to the indication and in accordance with the adaptive configuration.

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

[0005] According to various exemplary embodiments, a non-transitory computer-readable medium includes program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method. The method may include receiving at least one adaptive semi-persistent scheduling or configured grant configuration from a network entity. The method may further include receiving an indication from the network entity to trigger an adjustment of the semi-persistent scheduling or configured grant. The adjustment of the semi-persistent scheduling or configured grant may be associated with the at least one adaptive semi-persistent scheduling 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 in response to the indication and in accordance with the adaptive configuration.

[0006] According to some demonstrative embodiments, a computer program product may perform a method. The method may include receiving at least one adaptive semi-persistent scheduling or configured grant configuration from a network entity. The method may further include receiving an indication from the network entity to trigger an adjustment of the semi-persistent scheduling or configured grant. The adjustment of the semi-persistent scheduling or configured grant may be associated with the at least one adaptive semi-persistent scheduling 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 in response to the indication and in accordance with the adaptive configuration.

[0007] According to certain exemplary 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 to at least receive at least one adaptive semi-persistent scheduling or configured grant configuration from a network entity. The at least one memory and instructions, when executed by the at least one processor, may cause the apparatus to at least receive an indication from the network entity to trigger an adjustment of the semi-persistent scheduling or configured grant. The adjustment of the semi-persistent scheduling or configured grant may be associated with the at least one adaptive semi-persistent scheduling or configured grant configuration. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus to at least add or remove drift to a semi-persistent scheduling or configured grant starting subframe and slot in response to the indication and in accordance with the adaptive configuration.

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

[0009] According to some example embodiments, the method can include configuring a user equipment with at least one adaptive semi-persistent scheduling or configured grant configuration for the user equipment. The method can further include transmitting an indication to the user equipment to trigger an adjustment of the semi-persistent scheduling or configured grant to the user equipment. The adjustment of the semi-persistent scheduling or configured grant can be associated with the at least one adaptive semi-persistent scheduling or configured grant configuration.

[0010] According to certain example embodiments, an apparatus may comprise means for configuring a user equipment with at least one adaptive semi-persistent scheduling or configured grant configuration for the user equipment. The apparatus may further comprise means for transmitting an indication to the user equipment to trigger an adjustment of the semi-persistent scheduling or configured grant to the user equipment. The adjustment of the semi-persistent scheduling or configured grant may be associated with the at least one adaptive semi-persistent scheduling or configured grant configuration.

[0011] According to various exemplary embodiments, a non-transitory computer-readable medium comprising program instructions, which 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 or configured grant configuration for the user equipment. The method may further include transmitting an indication to the user equipment to trigger an adjustment of the semi-persistent scheduling or configured grant to the user equipment. The adjustment of the semi-persistent scheduling or configured grant may be associated with the at least one adaptive semi-persistent scheduling or configured grant configuration.

[0012] According to 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 or configured grant configuration for the user equipment. The method may further include transmitting an indication to the user equipment to trigger an adjustment of the semi-persistent scheduling or configured grant to the user equipment. The adjustment of the semi-persistent scheduling or configured grant may be associated with the at least one adaptive semi-persistent scheduling or configured grant configuration.

[0013] According to 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 to at least configure a user equipment with at least one adaptive semi-persistent scheduling or configured grant configuration for the user equipment. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus to at least transmit an indication to the user equipment to trigger an adjustment of the semi-persistent scheduling or configured grant to the user equipment. The adjustment of the semi-persistent scheduling or configured grant may be associated with the at least one adaptive semi-persistent scheduling or configured grant configuration.

[0014] According to various exemplary embodiments, the apparatus may comprise circuitry configured to configure a user equipment with at least one adaptive semi-persistent scheduling or configured grant configuration for the user equipment. The apparatus may further comprise functional circuitry configured to send an indication to the user equipment to trigger an adjustment of the semi-persistent scheduling or configured grant to the user equipment. The adjustment of the semi-persistent scheduling or configured grant may be associated with the at least one adaptive semi-persistent scheduling or configured grant configuration.

[0015] For a proper understanding of the exemplary embodiments, reference should be made to the accompanying drawings. [Brief explanation of the drawings]

[0016] [Figure 1] FIG. 1 shows an example of SPS or CG configurations for different combinations of frame rate (periodicity), quality (class), and frame type (multimodality). [Figure 2] FIG. 1 illustrates an example of desynchronization. [Figure 3] FIG. 10 illustrates an example of drift for two SPS configurations as a function of time slot. [Figure 4] FIG. 1 illustrates an example of time drift for different extended reality (XR) frame rates and SPS configurations. [Figure 5] FIG. 10 is a diagram illustrating an example of a traffic pattern of an XR video stream. [Figure 6] FIG. 1 illustrates an example of a signaling diagram for configuring and readjusting an SPS cycle with XR frame arrival for DL ​​transmission, according to certain exemplary embodiments. [Figure 7]FIG. 1 illustrates an example of a signaling diagram for configuring and readjusting a CG cycle with XR frame arrival for uplink (UL) transmission, according to certain exemplary embodiments. [Figure 8] FIG. 1 illustrates an example flowchart of a method in accordance with various exemplary embodiments. [Figure 9] FIG. 1 illustrates an example flowchart of a method in accordance with various exemplary embodiments. [Figure 10] FIG. 10 illustrates an example flowchart of another method in accordance with certain illustrative embodiments. [Figure 11] FIG. 10 illustrates an example flowchart of another method according to some exemplary embodiments. [Figure 12] FIG. 10 illustrates an example flowchart of another method in accordance with various exemplary embodiments. [Figure 13] FIG. 1 illustrates an example of various network devices in accordance with some exemplary embodiments. [Figure 14] FIG. 1 illustrates an example of a 5G network and system architecture in accordance with certain exemplary embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0017] It will be readily understood that the components of particular exemplary embodiments as generally described and illustrated in the Figures herein could be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of several exemplary 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 the particular exemplary embodiments, but instead is representative of selected exemplary embodiments.

[0018] The 3GPP Working Group's System Aspects (SA) 4 and Radio Access Network (RAN) 1 have adopted a quasi-periodic, multimodal, and multi-class traffic model for XR applications. Specifically, XR traffic exhibits a bursty pattern with high data rates and typically exhibits two burst types / classes that can be classified by their size. The traffic periodicity may be due to a 3D video generation process that can create a series of frames at a given sampling rate. For example, the sampling rate may be 30, 60, 90, and 120 frames per second (fps) or cycles per second (Hz). Compression techniques used to reduce bit rates can generate multiple types of frames that can be classified according to their size distribution. Compression can be achieved using both intraframe and interframe coding. Specifically, intraframe coding may use a lossy coding technique that requires only the information carried in the compressed frame for decoding. In contrast, interframe coding may apply a differential technique to multiple frames to encode and transmit only the difference across consecutive frames. Frames generated using intraframe coding may be called "I-frames," while frames generated using interframe coding may be called "P-frames" or "B-frames" depending on which differencing technique is used. Interframe coding can provide higher compression (up to 5x and 10x for P-frames and B-frames, respectively) at the cost of creating dependencies across multiple frames. Thus, compression techniques can generate a multimodal distribution of frame sizes through the superposition of different types of XR frames, each with its own distribution.

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

[0020] SPS can result in reduced overhead compared to sending DL dynamic scheduling grants (e.g., reduced physical downlink control channel (PDCCH) overhead). In addition to lower PDCCH overhead, SPS can offload computational load from the dynamic gNB medium access control (MAC) scheduler. 3GPP NR Rel-16 introduces several DL SPS enhancements to support small payload URLLC and time-constrained communication (TSC) transmissions. However, SPS is not well suited for XR use cases; for example, SPS is the method by which DL radio resources are configured for a UE to transmit one transport block with regular time periodicity. Up to eight simultaneously active SPS configurations can be configured for a UE (configured via radio resource control (RRC) signaling) with a periodicity of any integer number of slots (N*14) and a minimum periodicity in Rel-15 of 10 ms. DL SPS also relies on separate configuration (RRC-based) and activation / deactivation (a PDCCH addressed to a configured Scheduling Radio Network Temporary Identifier (CS-RNTI) can signal and activate a configured DL allocation or deactivate it). Similarly, semi-persistent resource allocation in the UL may specify a CG.

[0021] Currently, SPS / CG only allows the definition of a static integer period for the radio resources allocated to a particular UE. The integer periodicity can be specified at subframe (SF) or slot or subslot granularity, depending on the RRC configuration. Non-integer periodicity of XR traffic (e.g., XR traffic with a periodicity of 16.67 ms, which is not aligned with the 5G numbering system) can result in a time drift between the starting slot (or subframe) of the SPS period and the periodic arrival of the XR traffic. For DL, as XR traffic drifts away from SPS, the time drift accumulates over time, eventually resulting in desynchronization between the SPS resource period and the XR traffic. As a result, this can cause the loss of XR frames because packet transmissions can be delayed until the next configured opportunity while the packet delay budget (PDB) is typically smaller than the XR traffic periodicity (e.g., the PDB can be equal to 10 ms or 15 ms versus 16.67 ms for XR periodicity at 60 fps).

[0022] Furthermore, multiple combinations of frame rate (periodicity), quality (resolution), and frame type (compression) that may be used by an XR application's rate adaptation algorithm to scale quality up or down may require multiple SPS / CG configurations, resulting 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 four 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), as shown in FIG. 1, 16 dedicated SPS configurations may be possible, specifically, 16 combinations corresponding to dedicated periods per combination and several time-frequency resources (i.e., several consecutive TTIs and PRBs). However, the periodicity of these 16 combinations 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, as properties such as magnitude, sign, and derivative may depend on the XR class and active SPS / CG configuration.

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

[0024] The upper part of Figure 2 shows XR frame arrivals, while the lower part shows subframes and SPS scheduling opportunities (solid blocks). The gap between the integer periodicity of the SPS cycle and the non-integer periodicity of the XR frame may accumulate over time. Thus, the SPS cycle may drift away from frame arrivals. For 60 fps and a 16 ms SPS periodicity, the third frame (i.e., the second P-frame) may miss the configured scheduling opportunity. The base station can detect this discrepancy and attempt to use dynamic scheduling for the XR packets. The possibility of servicing the packets may depend on the load (note that XR services may have heavy traffic requirements and the network may quickly become saturated). The base station can also trigger an RRC reconfiguration, but frequent reconfigurations may be required to resynchronize the SPS cycle with the XR periodicity. The RRC reconfiguration may introduce extra delay and heavy signaling overhead in transmissions.

[0025] [Table 1]

[0026] Figure 3 shows the evolution of time drift for two SPS configurations with periodicities of 16 ms and 17 ms, respectively. A positive drift between XR and SPS may correspond to an XR frame arriving late relative to the scheduling grant, whereas a negative drift between XR and SPS may correspond to an XR frame arriving early relative to the scheduling grant. We can observe that the gap continues to accumulate. Using configuration SPS1 after the second SPS cycle, the XR frame may be late and miss the scheduling opportunity (see Table 1 above). In contrast, for configuration SPS2, the XR frame may arrive earlier than the scheduling opportunity, and thus the frame may be transmitted when an SPS allocation becomes available. However, after 31 cycles, the XR frames may end up delayed beyond their PDB (31 × (17 − 16.67) ≈ 10 ms). As a result, time drift can cause frame errors of 3.3% and 6.25% (i.e., 1 / 16 and 1 / 30) in the SPS1 and SPS2 configurations, respectively. However, XR traffic may require 99% of frames to be delivered within their PDB.

[0027] The time drift for typical values ​​of XR frame rate and integer periodicity of the SPS configuration is shown in Figure 4, where drift resulting from the difference between integer SPS periodicity and non-integer XR periodicity accumulates. Positive drift refers to an XR frame arriving late relative to the scheduling grant, thus causing the scheduler to postpone transmission to the next grant or handle it using dynamic scheduling. An SPS with negative drift may start to lose frames when the drift approaches the PDB (10 ms for AR / VR services) minus the frame transmission delay.

[0028] Figure 5 shows that SPS / CG reconfiguration does not solve the time drift issue. Figure 5 shows a series of frames generated by an XR application with a frame rate change and SPS reconfiguration. At time T2, the XR application downscales its frame rate from 60 fps to 30 fps (time T1 corresponds to the moment of arrival of the last frame generated at a frame rate of 60 fps). Frame rate downscaling results in an increase in the inter-arrival time between consecutive frames, which triggers reconfiguration of the SPS allocation either through RRC reconfiguration or other schemes. However, time drift due to the mismatch between integer and non-integer periodicity continues to accumulate even when the reconfiguration at time T2 realigns the XR traffic with the new SPS configuration. As shown in Figure 5, even when the reconfiguration at time T2 realigns the SPS and XR traffic, the third frame generated at 30 fps arrives at time T3, 0.67 ms late relative to the SPS scheduling grant.

[0029] Certain exemplary embodiments described herein may have various benefits and / or advantages for overcoming the above-mentioned drawbacks. For example, certain exemplary embodiments may enable fast correction of only SPS / CG resources when the drift becomes too large, cover variable drift due to, for example, XR frame rate changes, and provide a solution for both DL SPS and UL CG.

[0030] Some exemplary embodiments can provide a simple and efficient scheme for resolving time drift due to periodicity mismatch between SPS / CG configurations and XR traffic, and can be applied beyond XR traffic, i.e., beyond applications with periodicity mismatch between SPS / CG and traffic arrival processes. Furthermore, various exemplary embodiments enable XR traffic requirements to be met even when the SPS / CG and XR periods do not perfectly match, and can include multiple embodiments using different signaling overhead for the readjustment procedure. This includes multiple XR application scenarios with different frame rate characteristics, such as fixed and dynamic frame rates, XR resolution adaptation, and periodic and quasi-periodic traffic. Accordingly, certain exemplary embodiments described below are directed to improvements in computer-related technologies.

[0031] Various exemplary embodiments described herein can compensate for time drift between configured resources, such as SPS / CG and XR traffic. The drift can be caused, for example, by a periodicity mismatch between CG and XR traffic. If the drift becomes too large, it can cause packet loss or delay. Techniques are proposed herein for determining "when" and "how much" to compensate for the drift between some XR classes and SPS / CG configurations. In particular, certain embodiments can include autonomous compensation, where both the UE and the network can apply an offset to the SPS / CG allocation per predetermined time period, such as the parameter PeriodicitySyncCycle. As another exemplary embodiment, when the network and / or UE are triggered, in the DL, the network can signal an offset to the UE when the drift becomes larger than a threshold, such as the parameter PeriodicitySyncTh. Both the UE and the network apply the offset signaled by the network. In the UL, the UE can request the network to compensate for the drift when the drift becomes larger than a threshold (e.g., PeriodicitySyncTh). The network can then determine the amount of offset and subsequently notify the UE. Both the UE and the network can then apply the signaled offset. The network can then autonomously decide to compensate for the drift and signal the offset to the UE. Both the UE and the network can then apply the signaled offset.

[0032] As used in some embodiments herein, "drift" may refer to the cumulative time offset between an SPS / CG resource and an XR frame. For example, "adding drift" may be used for SPS / CG resource selection, where a later subframe may be selected as the new starting subframe of the allocated SPS / CG resource to achieve alignment between the arrival time of the XR frame and the starting subframe of the SPS / CG resource. Similarly, "removing drift" may also be used for SPS / CG resource selection, where an earlier subframe may be selected as the new starting subframe of the allocated SPS / CG resource to achieve alignment between the arrival time of the XR frame and the starting subframe of the SPS / CG resource.

[0033] Some exemplary embodiments described below may include extensions for configuring SPS and CG resource allocation to adjust the SPS / CG resource allocation pattern to accommodate drift in XR traffic patterns in the RAN. This adaptation can use extensions to information element (IE) configurations exchanged through RRC configuration messages. In addition, various exemplary embodiments may include extensions for controlling messages exchanged between the base station and the UE to dynamically adopt the SPS / CG cycle according to traffic patterns and / or UE conditions. This may be achieved by defining a new control command (e.g., carried by the MAC Control Element (MAC CE) or downlink control information (DCI)) to shift the next SPS / CG cycle by an offset. Furthermore, various embodiments may include the design of a scheme for tracking drift between the SPS / CG and XR traffic classes and determining when to compensate for the drift without signaling. The UE and base station may use new behavior definitions in the standard to calculate the drift and when to compensate for the drift and keep the network and UE coordinated. As an example, drift tracking and compensation may involve thresholds to determine when to compensate for drift (i.e., how much and when to compensate).<PeriodicitySyncCycle,PeriodicitySyncTh> The ad-hoc compensation may be based on multiple pairs of thresholds (one for each XR class-SPS configuration). Because a single threshold pair may not account for all time drifts, a new UE behavior may be defined to use those thresholds and signaling schemes to implement ad-hoc compensation.

[0034] As shown in Figure 2, a mismatch between the non-integer periodicity of XR frame generation and the integer SPS / CG cycle defined by the SPS / CG parameters can result in the loss or delay of XR frames. In particular, let t ∈ {0, 1, 2, 3, ...} be a sequence number identifying an SPS cycle,

[0035]

number

[0036]

number

[0037] Some example embodiments use t to indicate the SPS cycle when XR traffic changes from the jth class to the ith class (e.g., when the frame rate changes from j=30 to i=60 fps). ji ∈{0,1,2,3,...} can be used. If the configured resources are matched initially with the first packet, the time drift for the i-th XR class can vary according to:

[0038]

number

[0039]

number

[0040] The formulas in equations (1) and (2) for calculating drift can 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 (i.e., i = k), the active SPS / CG configuration can also indicate the XR class, and the difference between the XR and SPS / CG periods in equation (2) (i.e., δ_ii) can be indicated as a parameter, so this may not be important. In some embodiments described below, one SPS / CG configuration is assigned to one XR class, and a single index "i" can be used to identify both. In the case of multiple XR classes assigned to the same SPS / CG configuration, the difference between each XR and SPS / CG period in equation (2) (i.e., δ_ki) can be provided during configuration. In various exemplary embodiments, the network (for DL) or the UE (for UL) can estimate the amount of drift and indicate it to the other entity.

[0041] To compensate for the time drift, the UE may be informed of the periodicity mismatch and may be informed when to expect or postpone the start 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 (where index "i" indicates the ith SPS / CG configuration and the ith XR class):

[0042] PeriodicityDrift(|δ i |): Drift parameter obtained as an absolute value defined by equation (2).

[0043] PeriodicityDriftSign(sign(δ i )): indicates the sign of the drift (e.g., 1 bit).

[0044] PeriodicitySyncCycle

[0045]

number

[0046] PeriodicitySyncTh

[0047]

number

[0048] Depending on the implementation, PeriodicityDrift and PeriodicityDriftSign may be combined into one parameter.

[0049] The pair of thresholds, PeriodicitySyncCycle and PeriodicitySyncTh, may be determined based on (i) the difference between the XR traffic class and the SPS / CG period (i.e., the difference calculated in equation (2)), (ii) how much drift the SPS / CG allocation can tolerate before the expected arrival of the XR falls outside the SPS / CG allocation, and / or (iii) the maximum frequency of drift compensation (i.e., how much drift is compensated during a time interval). Factors (i) and (ii) may depend on the XR application, while (iii) may be the network operator's choice. However, the maximum frequency may be limited depending on the drift and tolerance before the XR frame falls outside the SPS / CG allocation. In some exemplary embodiments, two thresholds may be calculated, where:

[0050]

number

[0051]

number

[0052]

number

[0053]

number

[0054]

number

[0055]

number

[0056] The parameters PeriodicitySyncCycle and PeriodicitySyncThbe may enable the UE and base station to know when the timing of the SPS / CG pattern should be adjusted, and the adjustment may be performed in a predictive manner. To provide further flexibility, new control messages and procedures may be used to (i) initiate an SPS / CG pattern adjustment (i.e., a network-initiated procedure), (ii) request an SPS / CG pattern adjustment (i.e., a request triggered by the UE and an alternative to (i)), and (iii) apply the adjustment at a specific cycle (i.e., a command sent by the base station). The signaling may be implemented as new L1 and / or L2 control messages.

[0057] In various exemplary embodiments disclosed herein, after a DL allocation is configured for SPS, the MAC entity may sequentially consider the Nth downlink DL to occur in a slot, as follows: (numberOfSlotsPerFrame×SFN+number of slots in a frame)=[(numberOfSlotsPerFrame×SFN start time +slot start time +offset start time )+N×(periodicity+offset periodicity ) × numberOfSlotsPerFrame / 10] modulo(1024 × numberOfSlotsPerFrame), where SFN start time and slot start timeare the SFN and slot, respectively, of the first transmission of the PDSCH at which the configured DL allocation is initialized or reinitialized. start time and offset periodicity may be an offset applied to the respective slots and periods during which realignment messages are communicated by the network.

[0058] After the UL grants are configured for CG type 1, the MAC entity can sequentially consider the Nth (N>=0) UL grant to be made in symbols, as follows: [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) + [(number of slots in frame offset start time )×numberOfSymbolsPerSlot] + number of symbols in slot + offset-symbol start time ]=(timeReferenceSFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+timeDomainOffset×numberOfSymbolsPerSlot+S+N×(Periodicity+offset periodicity )) modulo(1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot). After UL grants are configured for CG type 2, the MAC entity can sequentially consider that every Nth (N >= 0) UL grant is made on a symbol, as follows:

[0059] [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) + (slot number in frame × numberOfSymbolsPerSlot) + symbol number in slot] = [(SFN start time ×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+(slot start time +offset start time )×numberOfSymbolsPerSlot+symbol start time+offset-symbol start time )+N×(periodicity+offset periodicity )]modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot). SFN start time , slot start time , and symbol start time may correspond to the SFN, slot, and symbol, respectively, of the first transmission opportunity on the physical uplink shared channel (PUSCH) at which the configured UL grant is initialized or reinitialized. start time , offset-symbol start time , and offset periodicity may correspond to the offsets applied to the slot, symbol, and period, respectively, communicated by the network using realignment messages.

[0060] Figure 6 shows an example of a signaling diagram illustrating an enhanced SPS configuration for transmission of DL traffic. The UE 620 and network entity (NE) 630 may be similar to the UE 1320 and NE 1310 as shown in Figure 13 according to a particular exemplary embodiment. The retuning may be performed by a control command or may be performed directly by the NE 630 and UE 620 using new parameters communicated during initial configuration.

[0061] In various exemplary embodiments, the parameters may be set as PeriodicitySyncCycle=4 (P=4), PeriodicityDrift=0.1 (|δ|=0.25), and PeriodicityDriftSign=−1 (sign(δ)=−1), which may force the start slot to increase by one every four SPS / CG cycles by default.

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

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

[0064] At 605, when the accumulated time drift exceeds a certain threshold (e.g., PeriodicitySyncCycleTh), the NE 630 may signal the UE 620 to apply a readjustment and communicate at least which SPS cycle is to be resynchronized and / or the offset to be applied to the starting slot or subframe (SF). As an example, Figure 6 shows this as occurring during the third and sixth SPS cycles.

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

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

[0067] At 610, when the cumulative time drift exceeds a certain threshold (e.g., PeriodicitySyncCycleTh), the NE630 may inform the UE620 to apply a readjustment and communicate at least which SPS cycle is to be resynchronized and / or the offset to be applied to the starting slot or SF.

[0068] In various exemplary embodiments, the retuning may be performed by a control command or may be performed directly by the NE 630 and the UE 620 using new parameters communicated during initial configuration.

[0069] Figure 7 shows an example of a signaling diagram illustrating an enhanced CG configuration for UL transmission. The UE 720 and NE 730 may be similar to the UE 1320 and NE 1310 as shown in Figure 13, according to certain exemplary embodiments. Retuning may be requested by the UE 720 and performed by a control command sent by the NE 730, or may be performed directly by the UE 720 and NE 730 using new parameters communicated during initial configuration.

[0070] In various exemplary embodiments, the parameters may be set as PeriodicitySyncCycle=4 (P=4), PeriodicityDrift=0.1 (|δ|=0.25), and PeriodicityDriftSign=−1 (sign(δ)=−1), which may force the start slot to increase by one every four SPS / CG cycles by default.

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

[0072] At 702, the UE 720 may transmit UL traffic to the NE 730 according to the currently specified CG operation (ie, transmission occurs in the granted UL CG resources).

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

[0074] At 704, the UE 720 may transmit UL traffic to the NE 730 according to the currently specified CG operation (ie, transmission occurs in the granted UL CG resources).

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

[0076] At 706, the UE 720 may transmit UL traffic to the NE 730 according to the currently specified CG operation (ie, transmission occurs in the granted UL CG resources).

[0077] At 707, the UE 720 may add or remove drift to the CG starting SF and slot.

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

[0079] At 711, the NE 730 may determine the amount of readjustment (eg, offset) and the CG cycle to be readjusted and communicate this information to the UE 720.

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

[0081] In various exemplary embodiments, the decision regarding compensation may be autonomously determined by the NE 730 for the readjustment decision for CG cycle 7, which is signaled in CG cycle 6. The decision may be made by the NE 730 several cycles, PeriodicitySyncCycle, since the previous readjustment request (in the figure, four CG cycles after CG cycle 3, thus in CG cycle 7). The NE 730 may also decide based on other criteria, for example, whether the UE 720 should send a buffer status report (BSR) to transmit traffic before the CG allocation.

[0082] 8 illustrates an example of a flowchart of a method that may be performed by a UE, such as the UE 1320 illustrated in FIG. 13, in accordance with various exemplary embodiments. In particular, FIG. 8 illustrates a retuning procedure performed by the UE, where P C (PeriodicitySyncCycle) is a realignment parameter used by the UE and the network by default to perform realignment. T (PeriodicitySyncCycleTh) is a realignment parameter used by the UE to trigger a request for realignment. In this example, the MAC CE is taken as an example to carry the realignment command.

[0083] At 801, the method may include determining whether the XR class changes from j to i. If so, the method may include changing the SPS configuration from j to i at 802 and determining the class drift Δi(t−1)=Δ j (t-1).

[0084] At 804, the method may include detecting the start of a new SPS cycle i. At 805, the method may include detecting a class drift Δi(t)=Δ j (t-1)+δ i This can include updating the

[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 the realignment by changing the starting slot and / or SF, for example, (sign(δ i )>0), the starting slot may be decreased (removing the offset), while (sign(δ i )<0), the starting slot may be incremented (an offset may be added). At 808, the increment counter t may be incremented by 1. After receiving the adjustment indication, a readjustment may be indicated to the SPS / CG resources immediately after receiving the indication.

[0086] If, at 806, it is determined that a MAC CE realignment has not been received, then, at 809, the method comprises:

[0087]

number

[0088]

number

[0089]

number

[0090] The UE and gNB calculate the time drift Δ i (t) can be continuously updated. Upon receiving a realignment command and / or after a certain number of iterations (parameter PeriodicitySyncCycle), the UE can increase or decrease the current SPS / CG cycle by an offset. This offset is determined by the time drift Δ i (t) and may depend on, for example, offset = Δ i (t)=t i × δ, where t i measures the time when the i-th SPS configuration of the i-th XR class is triggered. i is the difference between the absolute SPS iteration and the iteration when traffic switches from the jth class to the ith class: t i =tt ji Another way to calculate the offset is to measure 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.

[0091]

number

[0092] In some exemplary embodiments, once the required parameters, e.g., the periodicity of XR traffic and SPS / CG resources, PeriodicitySyncCycle, are configured, the UE may be configured to perform a retune process after a number of SPS / CG cycles equal to PeriodicitySyncCycle since the last retune. Such operation may be set as a fallback operation if a retune command is not received.

[0093] Figure 9 illustrates an example flowchart of a method that may be performed by a UE, such as the UE 1320 shown in Figure 13, in accordance with various exemplary embodiments. The retuning may be performed by a control command or may be performed directly by the UE or NE using new parameters communicated during initial configuration (such as the NE 1310 shown in Figure 13).

[0094] In various exemplary embodiments, the parameters may be set as PeriodicitySyncCycle=4 (P=4), PeriodicityDrift=0.1 (|δ|=0.25), and PeriodicityDriftSign=−1 (sign(δ)=−1). These parameters may force the start slot to increase by one every four SPS / CG cycles by default.

[0095] At 901, the method may include receiving a configuration from an NE having one or more of the parameters PeriodicityDrift, PeriodicityDriftSign, and / or PeriodicitySyncCycle, PeriodicitySyncCycleTh, as described above.

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

[0097] At 905, when the accumulated time drift exceeds a threshold (e.g., PeriodicitySyncCycleTh), the method may include receiving an instruction from the NE to apply a readjustment and an indication of at least which SPS cycles are to be resynchronized and / or an offset to be applied to the starting slot or subframe (SF). This may occur during the third and sixth SPS cycles.

[0098] At 906, the method may include adding or removing drift to the SPS starting SF and slot.

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

[0100] At 910, when the cumulative time drift exceeds a threshold (e.g., PeriodicitySyncCycleTh), the method may include receiving an instruction from the NE to apply a readjustment and an indication of at least which SPS cycle is to be resynchronized and / or an offset to be applied to the starting slot or SF.

[0101] In various exemplary embodiments, the retuning may be performed by a control command or may be performed directly by the NE and UE using new parameters communicated during initial configuration.

[0102] Figure 10 illustrates an example flowchart of a method that may be performed by an NE, such as the NE 1320 shown in Figure 13, according to various exemplary embodiments. The retuning may be performed by a control command or may be performed directly by the NE or UE (such as the UE 1320 shown in Figure 13) using new parameters communicated during initial configuration.

[0103] In various exemplary embodiments, PeriodicitySyncCycle=4 (P=4), PeriodicityDrift=0.1 (|δ|=0.25), and PeriodicityDriftSign=−1 (sign(δ)=−1). These parameters may force the start slot to increase by one every four SPS / CG cycles by default.

[0104] At 1001, the method may include transmitting a configuration to a UE using one or more of the parameters PeriodicityDrift, PeriodicityDriftSign, and / or PeriodicitySyncCycle, PeriodicitySyncCycleTh, as described above.

[0105] At 1002-1004, the method may include transmitting DL traffic to the UE according to currently specified SPS operations (ie, transmission is performed in granted DL SPS resources).

[0106] At 1005, when the accumulated time drift exceeds a threshold (e.g., PeriodicitySyncCycleTh), the method may include sending an instruction to the UE to apply realignment, communicating at least which SPS cycle is to be resynchronized and / or an offset to be applied to the starting slot or subframe (SF). This may be done during the third and sixth SPS cycles.

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

[0108] At 1009, when the cumulative time drift exceeds a certain threshold (e.g., PeriodicitySyncCycleTh), the method may include sending an instruction to the UE to apply a readjustment, communicating at least which SPS cycle is to be resynchronized and / or an offset to be applied to the starting slot or SF.

[0109] In various exemplary embodiments, the retuning may be performed by a control command or may be performed directly by the NE and UE using new parameters communicated during initial configuration.

[0110] Figure 11 illustrates an example flowchart of a method that may be performed by a UE, such as the UE 1320 shown in Figure 13, in accordance with various exemplary embodiments. Retuning may be requested by the UE, may be performed by a control command sent by the NE, or may be performed directly by the UE and the NE using new parameters communicated during initial configuration.

[0111] In some exemplary embodiments, PeriodicitySyncCycle=4 (P=4), PeriodicityDrift=0.1 (|δ|=0.25), and PeriodicityDriftSign=−1 (sign(δ)=−1). These parameters may force the start slot to increase by one every four SPS / CG cycles by default.

[0112] At 1101, the method may include receiving a configuration having one or more of drift parameters PeriodicityDrift, PeriodicityDriftSign, and / or PeriodicitySyncCycle, PeriodicitySyncCycleTh, as described above.

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

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

[0115] At 1104, the method may include transmitting UL traffic to the NE according to currently specified CG behavior (ie, transmission occurs in granted UL CG resources).

[0116] At 1105, the method may include receiving an indication of the amount of readjustment (eg, offset) and a determination of the CG cycle to be readjusted (Message 2).

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

[0118] At 1107, the method may include adding or removing drift to the CG start SF and slot.

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

[0120] At 1111, the method may include receiving an indication of an amount of readjustment (eg, offset) and a determination of a CG cycle to be readjusted (Message 2).

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

[0122] In various exemplary embodiments, the decision regarding compensation may be autonomously determined by the NE for the readjustment decision for CG cycle 7, which is signaled in CG cycle 6. The decision may be made by the NE several cycles, PeriodicitySyncCycle, after the previous readjustment request (in the figure, four CG cycles after CG cycle 3, thus in CG cycle 7). The NE may also decide based on other criteria, for example, whether the UE should send a buffer status report (BSR) to transmit traffic before the CG allocation.

[0123] Figure 12 illustrates an example flowchart of a method that may be performed by an NE, such as the NE 1310 shown in Figure 13, according to various exemplary embodiments. The retuning may be performed by a control command requested by the UE and sent by the NE, or may be performed directly by the UE and the NE using new parameters communicated during initial configuration.

[0124] In a particular exemplary embodiment, the parameters may be set as PeriodicitySyncCycle=4 (P=4), PeriodicityDrift=0.1 (|δ|=0.25), and PeriodicityDriftSign=−1 (sign(δ)=−1). These parameters may force the start slot to increase by one every four SPS / CG cycles by default.

[0125] At 1201, the method may include transmitting a configuration to a UE having one or more of drift parameters PeriodicityDrift, PeriodicityDriftSign, and / or PeriodicitySyncCycle, PeriodicitySyncCycleTh, as described above.

[0126] At 1202, the method may include transmitting UL traffic to the NE according to currently specified CG behavior (ie, transmission is performed on granted UL CG resources).

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

[0128] At 1204, the method may include transmitting UL traffic to the NE according to currently specified CG behavior (ie, transmission occurs on granted UL CG resources).

[0129] At 1205, the method may include transmitting an indication of the amount of readjustment (eg, offset) and the determination of the CG cycle to be readjusted (Message 2).

[0130] At 1206, the method may include transmitting the UL traffic to the NE according to currently specified CG behavior (ie, transmission occurs in granted UL CG resources).

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

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

[0133] At 1211, the method may include transmitting an indication of the amount of readjustment (eg, offset) and a determination of the CG cycle to be readjusted (Message 2).

[0134] In various exemplary embodiments, the decision regarding compensation may be autonomously determined by the NE for the readjustment decision for CG cycle 7, which is signaled in CG cycle 6. The decision may be made by the NE several cycles PeriodicitySyncCycle after the previous readjustment request (in the figure, four CG cycles after CG cycle 3, thus in CG cycle 7). The NE may also decide based on other criteria, for example, whether the UE should send a buffer status report (BSR) to transmit traffic before the CG allocation.

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

[0136] The 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 a combination thereof.

[0137] The NE 1310 may further include at least one gNB-CU that may be associated with at least one gNB-DU. The at least one gNB-CU and the at least one gNB-DU may communicate with at least one F1 interface, at least one X interface, and the like via 5GC. n -C interface, and / or at least one NG interface.

[0138] The UE 1320 may include one or more of a mobile device such as a mobile phone, smartphone, personal digital assistant (PDA), tablet, or portable media player, a digital camera, pocket video camera, video game console, a navigation unit such as a Global Positioning System (GPS) device, a desktop or laptop computer, a single location device such as a sensor or smart meter, or any combination thereof. Additionally, the NE 1310 and / or the UE 1320 may be one or more of a Citizens Broadband Wireless Service Device (CBSD).

[0139] The NE 1310 and / or the UE 1320 may include at least one processor, respectively denoted as 1311 and 1321. The processors 1311 and 1321 may be embodied by any computational or data processing device, such as a central processing unit (CPU), an application specific integrated circuit (ASIC), or similar device. The processor may be implemented as a single controller or as multiple controllers or processors.

[0140] As shown at 1312 and 1322, at least one memory may be provided in one or more of the devices. The memory may be fixed or removable. The memory may include computer program instructions or computer code contained therein. The memory 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 (i.e., tangible, not a signal), as opposed to a limitation to data storage persistence (e.g., RAM vs. ROM). A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memory may be combined on a single integrated circuit as the processor, or may be separate from one or more processors. Furthermore, the computer program instructions stored in the memory and processed by the processor may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.

[0141] The processors 1311 and 1321, memories 1312 and 1322, and any subset thereof, may be configured to provide means corresponding to the various blocks of Figures 1-12. Although not shown, the device may also include positioning hardware, such as a GPS or microelectromechanical systems (MEMS) hardware, that may be used to determine the location of the device. Other sensors are also permissible, and other sensors may be configured to determine position, altitude, speed, orientation, etc., such as a barometer, compass, etc.

[0142] As shown in Figure 13, transceivers 1313 and 1323 may be provided, and one or more devices may include at least one antenna, shown as 1314 and 1324, respectively. The devices may be equipped with many antennas, such as an array of antennas configured for multiple-input multiple-output (MIMO) communications, or multiple antennas for multiple RATs. For example, other configurations of these devices may be provided. The transceivers 1313 and 1323 may be units or devices that can be configured for transmitters, receivers, both transmitters and receivers, or both transmission and reception.

[0143] The memory and computer program instructions, together with a processor for a particular device, may be configured to cause a hardware apparatus, such as a UE, to perform any of the processes described above (i.e., FIGS. 1-12). Thus, in certain exemplary 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 exemplary embodiments may be performed entirely in hardware.

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

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

[0146] According to certain exemplary embodiments, the processors 1311 and 1321 and memories 1312 and 1322 may be included in or form part of processing or control circuitry. Additionally, in some exemplary embodiments, the transceivers 1313 and 1323 may be included in or form part of transmit / receive circuitry.

[0147] In some demonstrative embodiments, an apparatus (e.g., the NE 1310 and / or the UE 1320) may include means for performing any of the methods, processes, or variations described herein. Examples of means may include one or more processors, memories, controllers, transmitters, receivers, and / or computer program code for causing the execution of operations.

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

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

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

[0151] Certain example embodiments may be directed to an apparatus including 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 for the user equipment, and means for transmitting an indication to the user equipment to trigger an adjustment of the semi-persistent scheduling or configured grant associated with the adaptive configuration to the user equipment.

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

[0153] As used herein, "at least one of: " and "at least one of " and similar phrases, when a list of two or more elements is connected 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 of the elements.

[0154] Moreover, where appropriate, different functions or procedures described above may be performed in different orders and / or concurrently with one another. Moreover, where appropriate, one or more of the functions or procedures described may be optional or may be combined. Therefore, the foregoing description should be considered as illustrative of the principles and teachings of particular exemplary embodiments, and not limiting thereof.

[0155] Those skilled in the art will readily appreciate that the exemplary embodiments described above may be implemented with hardware elements in a different order and / or in different configurations than those disclosed. Thus, while several embodiments have been described based on these exemplary embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative configurations will be apparent while remaining within the spirit and scope of the exemplary embodiments.

[0156] Partial Glossary 3GPP Third Generation Partnership Project 5G Fifth Generation 5GC Fifth Generation Core (5th Generation Core) 5GS Fifth Generation System 6G Sixth Generation AR Augmented Reality ASIC Application Specific Integrated Circuit BS Base Station CBSD Citizens Broadband Radio Service Device CG Configured Grant CN Core Network CPU Central Processing Unit CS-RNTI Configured Scheduling Radio Network Temporary Identifier DCI Downlink Control Information DL Downlink E2E End-to-End eMBB Enhanced Mobile Broadband eMTC Enhanced Machine Type Communication eNB Evolved Node B EPS Evolved Packet System gNB Next Generation Node B GPS Global Positioning System HARQ Hybrid Automatic Repeat Request HDD Hard Disk Drive IE Information Element IIoT Industrial Internet of Things KPI Key Performance Indicator LTE Long-Term Evolution LTE-A Long-Term Evolution Advanced MAC Medium Access Control MIMO Multiple Input Multiple Output mMTC Massive Machine Type Communication MR Mixed Reliability MTC Machine Type Communication NAS Non-Access Stratum NE Network Entity NG Next Generation NG-eNB Next Generation Evolved Node B NG-RAN Next Generation Radio Access Network NR New Radio PDA Personal Digital Assistance (Personal Information Terminal) PDB Packet Delay Budget PDCCH Physical Downlink Control Channel PDU Protocol Data Unit PUSCH Physical Uplink Shared Channel QoS Quality of Service RAM Random Access Memory RAN Radio Access Network RAT Radio Access Technology RE Resource Element RRC Radio Resource Control RS Reference Signal SCS Subcarrier Spacing SDU Service Data Unit SF Subframe SFN System Frame Number SMF Session Management Function SN Sequence Number SPS Semi-Persistent Scheduling SRB Signaling Radio Bearer TB Transport Block TSC Time Sensitive Communications Tx Transmission UE User Equipment UL Uplink UMTS Universal Mobile Telecommunications System UPF User Plane Function URLLC Ultra-Reliable and Low-Latency Communication UTRAN Universal Mobile Telecommunications System Terrestrial Radio Access Network VR Virtual Reality WLAN Wireless Local Area Network XR Extended Reality

Claims

1. 1. An apparatus comprising: means for receiving at least one adaptive semi-persistent scheduling configuration or configured grant configuration from a network entity; means for receiving an indication for triggering an adjustment of semi-persistent scheduling or configured grant from a network entity, the adjustment of semi-persistent scheduling or configured grant being associated with at least one adaptive semi-persistent scheduling configuration or configured grant configuration; means for adding or removing drift to a semi-persistent scheduling start subframe and slot or a configured grant start subframe and slot in response to the indication and according to the adaptive configuration; An apparatus comprising:

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

3. 3. The apparatus of claim 1, wherein at least one received adaptive configuration comprises an indication of the magnitude of the drift.

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

5. 5. Apparatus according to any preceding claim, wherein at least one received adaptive configuration comprises an indication of a threshold for the amount of drift that triggers a retuning procedure.

6. Means for transmitting a request to a network entity for readjusting an adaptive configuration The apparatus of claim 1 , further comprising:

7. Means for determining that the drift is greater than a configured threshold The apparatus of claim 1 , further comprising:

8. Means for determining if modulo operation is equal to zero The apparatus of claim 1 , further comprising:

9. means for performing readjustment by adjusting the starting subframe and slot, where drift is added if the sign of the drift is less than zero, and where drift is removed if the sign of the drift is greater than zero; The apparatus of claim 1 , further comprising:

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

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

12. 12. Apparatus according to claim 10 or 11, wherein at least one received adaptive configuration comprises an indication of the magnitude of the drift.

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

14. 14. Apparatus according to any of claims 10 to 13, wherein at least one received adaptive configuration constitutes an indication of a threshold for the amount of drift that triggers a retuning procedure.

15. Means for receiving a request for readjustment of an adaptive configuration from a user equipment 15. The apparatus of claim 10, further comprising:

Images