Drift compensation for configured scheduling

Abstract

Systems, methods, apparatuses, and computer program products for extending actual use by introducing an optimized semi-persistent scheduling configuration or a configured authorized configuration scheme. A method may include receiving at least one adaptive semi-persistent scheduling configuration or a configured authorization configuration from a network entity; receiving, from the network entity, an indication to trigger semi-persistent scheduling or configured grant alignment; and adding or removing drift to the semi-persistent scheduling start subframe and time slot or the configured grant start subframe and time slot. Semi-persistent scheduling or configured grant alignment is associated with at least one adaptive semi-persistent scheduling configuration or configured grant configuration.

Description

Technical Field

[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE), 5th Generation (5G) Radio Access Technology (RAT), New Radio (NR) Access Technology, 6th Generation (6G), and / or other communication 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 an optimized semi-persistent scheduling / configured grant (SPS / CG) scheme. Background Art

[0002] Examples of mobile or wireless telecommunication systems may include radio frequency (RF) 5G RAT, universal mobile telecommunication system (UMTS) terrestrial radio access network (UTRAN), LTE evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), LTE-A Pro, NR access technology and / or multi-party alliances. 5G wireless system refers to the next generation (NG) wireless system and network architecture. 5G systems are typically built on 5GNR, but 5G (or NG) networks can also be built on E-UTRA radio. NR is expected to 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 a large amount of networking to support the Internet of Things (IoT). The next generation radio access network (NG-RAN) represents a RAN for 5G, which can provide radio access for NR, LTE and LTE-A. It should be noted that a node in 5G that provides radio access functionality to user equipment (e.g., similar to a Node B in UTRAN or an evolved Node B (eNB) or base station in LTE as a general term) may be referred to as a next-generation Node B (gNB) when built on an NR radio, and may be referred to as a next-generation eNB (NG-eNB) when built on an E-UTRA radio. Summary of the invention

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

[0004] According to certain example embodiments, an apparatus may include means for receiving at least one adaptive semi-persistent scheduling configuration or configured grant configuration from a network entity. The apparatus may also include means for receiving an indication from the network entity to trigger semi-persistent scheduling or configured grant alignment. The semi-persistent scheduling or configured grant alignment may be associated with at least one adaptive semi-persistent scheduling configuration or configured grant configuration. The apparatus may also include means for adding or removing drift to the semi-persistent scheduling or configured grant start subframes and time slots in response to the indication and according to the adaptive configuration.

[0005] According to various example embodiments, a non-transitory computer-readable medium including program instructions, which when executed by an apparatus, causes the apparatus to perform at least one method. The method may include receiving at least one adaptive semi-persistent scheduling configuration or configured grant configuration from a network entity. The method may also include receiving an indication from the network entity to trigger semi-persistent scheduling or configured grant alignment. The semi-persistent scheduling or configured grant alignment may be associated with at least one adaptive semi-persistent scheduling configuration or configured grant configuration. The method may also include, in response to the indication and according to the adaptive configuration, adding or removing drift to the semi-persistent scheduling or configured grant start subframe and time slot.

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

[0007] 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 receive at least one adaptive semi-persistent scheduling configuration or configured grant configuration from a network entity. The at least one memory and instructions, when executed by the at least one processor, may also cause the apparatus to at least receive an indication of triggering semi-persistent scheduling or configured grant alignment from the network entity. The semi-persistent scheduling or configured grant alignment may be associated with 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 also cause the apparatus to, in response to the indication and according to the adaptive configuration, add or remove drift to at least the semi-persistent scheduling or configured grant start subframe and time slot.

[0008] According to various example embodiments, an apparatus may include circuit means configured to perform receiving at least one adaptive semi-persistent scheduling configuration or configured grant configuration from a network entity. The apparatus may also include circuit means configured to perform receiving an indication from the network entity to trigger semi-persistent scheduling or configured grant alignment. The semi-persistent scheduling or configured grant alignment may be associated with at least one adaptive semi-persistent scheduling configuration or configured grant configuration. The apparatus may also include circuit means configured to perform adding or removing drift to the semi-persistent scheduling or configured grant start subframes and time slots in response to the indication and according to the adaptive configuration.

[0009] According to some example embodiments, a method may include configuring a user equipment with at least one adaptive semi-persistent scheduling configuration or a configured authorization configuration. The method may also include sending an indication to the user equipment for triggering semi-persistent scheduling or configured authorization alignment for the user equipment. The semi-persistent scheduling or configured authorization alignment may be associated with at least one adaptive semi-persistent scheduling configuration or configured authorization configuration.

[0010] According to certain example embodiments, an apparatus may include means for configuring a user equipment with at least one adaptive semi-persistent scheduling configuration or a configured authorization configuration. The apparatus may also include means for sending an indication to the user equipment for triggering semi-persistent scheduling or configured authorization alignment for the user equipment. The semi-persistent scheduling or configured authorization alignment may be associated with at least one adaptive semi-persistent scheduling configuration or configured authorization configuration.

[0011] According to various example embodiments, a non-transitory computer-readable medium including program instructions, which when executed by an apparatus, causes the apparatus to perform at least one method. The method may include configuring a user equipment with at least one adaptive semi-persistent scheduling configuration or a configured authorization configuration. The method may also include sending an indication to the user equipment for triggering semi-persistent scheduling or configured authorization alignment for the user equipment. The semi-persistent scheduling or configured authorization alignment may be associated with at least one adaptive semi-persistent scheduling configuration or configured authorization 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 configuration or a configured authorization configuration. The method may also include sending an indication to the user equipment for triggering semi-persistent scheduling or configured authorization alignment for the user equipment. The semi-persistent scheduling or configured authorization alignment may be associated with at least one adaptive semi-persistent scheduling configuration or configured authorization configuration.

[0013] According to certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions, which when executed by the at least one processor causes the apparatus to at least configure a user equipment with at least one adaptive semi-persistent scheduling configuration or a configured authorization configuration. The at least one memory and the instructions, when executed by the at least one processor, may also cause the apparatus to at least send an indication to the user equipment for triggering semi-persistent scheduling or configured authorization alignment for the user equipment. The semi-persistent scheduling or configured authorization alignment may be associated with at least one adaptive semi-persistent scheduling configuration or configured authorization configuration.

[0014] According to various example embodiments, an apparatus may include a circuit device configured to perform configuration of a user equipment having at least one adaptive semi-persistent scheduling configuration or a configured authorization configuration to a user equipment. The apparatus may also include a functional circuit device configured to perform sending an indication to the user equipment for triggering semi-persistent scheduling or configured authorization alignment for the user equipment. The semi-persistent scheduling or configured authorization alignment may be associated with at least one adaptive semi-persistent scheduling configuration or configured authorization configuration. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0016] Figure 1 Examples of SPS or CG configurations for different combinations of frame rate (periodicity), quality (category) and frame type (multimodality) are illustrated.

[0017] Figure 2 An example of desynchronization is illustrated.

[0018] Figure 3 An example of the drift of two SPS configurations as a function of time slot is illustrated.

[0019] Figure 4 Illustrated are examples of temporal drift for different extended reality (XR) frame rates and SPS configurations.

[0020] Figure 5 An example of a business model for XR video streaming is illustrated.

[0021] Figure 6 Illustrated are examples of signaling diagrams for configuration and realignment of SPS periods for DL ​​transmissions with XR frame arrivals, in accordance with certain example embodiments.

[0022] Figure 7 Illustrated is an example of a signaling diagram for configuration and realignment of CG periods with XR frame arrivals for uplink (UL) transmissions in accordance with certain example embodiments.

[0023] Figure 8 An example of a flow chart of a method according to various example embodiments is illustrated.

[0024] Fig. 9 An example of a flow chart of a method according to various example embodiments is illustrated.

[0025] Fig.10 An example of a flow chart of another method in accordance with certain example embodiments is illustrated.

[0026] Fig.11 An example of a flow chart of another method according to some example embodiments is illustrated.

[0027] Fig.12 An example of a flow chart of another method according to various example embodiments is illustrated.

[0028] Fig.13 Examples of various network devices are illustrated according to some example embodiments.

[0029] Fig.14 An example of a 5G network and system architecture is illustrated in accordance with certain example embodiments. DETAILED DESCRIPTION

[0030] It is 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 variety of different configurations. Therefore, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for improving the radio resource allocation method for XR use cases by introducing an optimized SPS / CG scheme is not intended to limit the scope of certain example embodiments, but is representative of selected example embodiments.

[0031] 3GPP working group System Aspect (SA) 4 and Radio Access Network (RAN) 1 have adopted quasi-periodic, multi-mode and multi-class service models for XR applications. Specifically, XR services exhibit burst patterns with high data rates, and typically two burst types / classes can be classified according to their size. The service periodicity may be due to a 3D video generation process that may create a sequence 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 for reducing the bit rate may generate multiple types of frames that may be classified according to their size distribution. Compression may be achieved using intra-frame and inter-frame coding. Specifically, intra-frame coding may use a lossy coding technique that requires only the information carried in the compressed frame for decoding. In contrast, inter-frame coding may apply a differential technique to multiple frames to encode and transmit only the difference between consecutive frames. Depending on which differential technique is used, frames generated using intra-frame coding may be referred to as "I frames", while frames generated using inter-frame coding may be referred to as "P frames" or "B frames". Inter-coding can provide higher compression (up to 5 and 10 times for P and B frames, respectively) at the expense of creating dependencies across frames. Thus, due to the superposition of different types of XR frames, the compression technique can generate a multimodal distribution of frame sizes, each XR frame having its own distribution.

[0032] Similarly, rate adaptation implemented at the application layer can generate multiple types of bursts. For example, an XR application can dynamically adjust the bit rate based on the state of the network and the user's viewport information (e.g., the direction of the user's view). 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 reducing the frame rate. This can result in a reduction in the 3D media content carried by all different frames.

[0033] Compared with transmitting DL dynamic scheduling grants, SPS can provide overhead reduction (e.g., reduced Physical Downlink Control Channel (PDCCH) overhead). In addition to the lower PDCCH overhead, SPS can also offload the computational burden from the dynamic gNB Medium Access Control (MAC) scheduler. 3GPP NR Rel-16 introduced several DL SPS enhancements to support URLLC and time-sensitive communication (TSC) transmissions with small payloads. However, SPS is not suitable for XR use cases; for example, SPS is a method for configuring the UE to use DL radio resources to transmit a transport block at regular time intervals. The UE can be configured with up to eight simultaneously active SPS configurations (configured via Radio Resource Control (RRC) signaling), with a periodicity of any integer number (N*14) of slots, and the minimum periodicity in Rel-15 is 10 ms. DL SPS also depends on separate configuration (based on RRC) and activation / deactivation (the PDCCH addressed to the configured scheduling Radio Network Temporary Identifier (CS-RNTI) can signal and activate the configured DL allocation, or deactivate it). Similarly, semi-persistent resource allocation in UL can specify CG.

[0034] SPS / CG currently only allows defining static integer periods for radio resources assigned to a specific UE. According to the RRC configuration, the integer periodicity can be specified with subframe (SF), slot, or sub-slot granularity. The non-integer periodicity of XR traffic (e.g., XR traffic with a 16.67 ms periodicity that is not aligned with 5G numerology) can cause a time drift between the start slot (or subframe) of the SPS period and the periodic arrival of XR traffic. For DL, as the XR traffic drifts away from the SPS, the accumulated time drift can vary over time and eventually cause desynchronization between the SPS resource period and the XR traffic. As a result, this can cause loss of XR frames because packet transmissions can be delayed until the next configured opportunity, while the Packet Delay Budget (PDB) is typically less than the XR traffic periodicity (e.g., PDB can be equal to 10 ms or 15 ms, while the XR periodicity for 60 fps is 16.67 ms).

[0035] Furthermore, multiple combinations of frame rate (periodicity), quality (resolution), and frame type (compression) that may be used by the rate adaptation algorithm of the XR application to scale up or down the quality may require multiple SPS / CG configurations resulting in multiple temporal shifts (e.g., at least one temporal shift 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-frames and P-frames), 16 combinations may correspond to 16 dedicated SPS configurations, and in particular the dedicated time periods and number of time-frequency resources (i.e., number of consecutive TTIs and PRBs) used for each combination, as shown in FIG. Figure 1 However, the periods of these 16 combinations may not exactly match the period of the combination, thus causing 16 time drifts. Therefore, compensation for a single time drift is not sufficient, since properties such as amplitude, sign, and derivative may depend on the XR class and the active SPS / CG configuration.

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

[0037] Figure 2 The top portion illustrates the XR frame arrival, while the bottom portion illustrates the subframes and SPS scheduling opportunities (solid blocks). The gaps between the integer periodicity of the SPS period and the non-integer periodicity of the XR frames can accumulate over time. Therefore, the SPS period can deviate from the frame arrival. In the case of 60fps and 16ms SPS periodicity, the third frame (i.e., the second P frame) can miss the configured scheduling opportunity. The base station can detect this mismatch and attempt to use dynamic scheduling for the XR packets. The possibility of serving the packets may depend on the load (note that XR services can have busy traffic demands and the network can become saturated quickly). The base station can also trigger RRC reconfiguration, but frequent reconfiguration may be necessary to resynchronize the SPS period with the XR periodicity. RRC reconfiguration can introduce additional delays and heavy signaling overhead in transmission.

[0038]

[0039]

[0040] Figure 3 The variation of time drift for two SPS configurations with periodicity of 16ms and 17ms, respectively, is depicted. A positive drift between XR and SPS may correspond to an XR frame arriving late relative to a scheduling grant, while a negative drift between XR and SPS may correspond to an XR frame arriving early relative to a scheduling grant. We can observe that the gaps keep accumulating. Using configuration SPS1 after the second SPS period, the XR frame may be late and miss the scheduling opportunity (see Table 1 above). In contrast, with configuration SPS2, the XR frame may arrive earlier than the scheduling opportunity, so the frame can be sent when the SPS allocation becomes available. However, after 31 periods, the XR frame may be delayed beyond its PDB (31×(17-16.67)≈10ms). As a result, the time drift may cause frame errors of 3.3% and 6.25% (i.e., 1 / 16 and 1 / 30) for SPS1 and SPS2 configurations, respectively. However, XR services may require 99% of frames to be delivered within their PDBs.

[0041] Figure 4 Typical values ​​of XR frame rates and the time drift of integer periodicities of SPS configurations are illustrated in Figure 1, where the drift generated by the difference between integer SPS periodicity and non-integer XR periodicity accumulates. Positive drift means that the XR frame arrives late relative to the scheduling grant, thus forcing the scheduler to delay the transmission until the next grant, or handle it with dynamic scheduling. SPS with negative drift can start to drop frames when the drift approaches the PDB (10ms in the case of AR / VR services) minus the frame transmission delay.

[0042] Figure 5 It is shown that SPS / CG reconfiguration does not address the challenge of temporal drift. Figure 5 The figure illustrates a sequence of frames generated by an XR application with a frame rate change and SPS reconfiguration. At time T2, the XR application scales down the frame rate from 60fps to 30fps (time T1 corresponds to the moment when the last frame generated at a frame rate of 60fps arrives). The frame rate reduction causes an increase in the inter-arrival time between consecutive frames, which triggers a reconfiguration of the SPS allocation through RRC reconfiguration or using other schemes. However, even though the reconfiguration at time T2 has realigned the XR service with the new SPS configuration, the time drift caused by the mismatch of integer and non-integer periodicities keeps accumulating. Figure 5As shown, even though the reconfiguration realigns the SPS and XR traffic at time T2, the third frame generated at 30fps arrives at time T3, 0.67ms later than the SPS scheduling grant.

[0043] Certain example embodiments described herein may have various benefits and / or advantages that overcome the above-mentioned disadvantages. For example, certain example embodiments may enable fast correction of only SPS / CG resources when the drift becomes too large, cover variable drift due to, for example, changes in XR frame rate, and provide solutions for DL ​​SPS and UL CG.

[0044] Some example embodiments may provide a simple and effective solution to the time drift caused by the periodic mismatch between the SPS / CG configuration and the XR service, and may be applied outside the XR service, i.e., an application with a periodic mismatch between the SPS / CG and the service arrival process. In addition, various example embodiments may allow the requirements of the XR service to be met even if the SPS / CG and XR periods are not perfectly matched, and include multiple embodiments with different signaling overheads for realignment procedures. This includes multiple XR application scenarios with different frame rate attributes, such as fixed and dynamic frame rates, XR resolution adaptation, periodic and quasi-periodic services. Therefore, some of the example embodiments discussed below relate to improvements in computer-related technologies.

[0045] Various example embodiments discussed herein may compensate for time drifts between configured resources such as SPS / CG and XR services. Drift may be caused by, for example, a periodic mismatch between CG and XR services. If the drift grows too large, it may cause packet loss or delay. Proposed herein is a technique for determining "when" and "how much" to compensate for drifts between several XR classes and SPS / CG configurations. In particular, certain embodiments may include autonomous compensation, wherein both the UE and the network may apply an offset to the SPS / CG allocation, such as a parameter PeriodicitySyncCycle, at each predetermined time period. As another example embodiment, when the network and / or UE is triggered, in DL, when the drift becomes greater than a threshold (such as, a parameter PeriodicitySyncTh), the network may signal the UE an offset. Both the UE and the network apply the offset signaled by the network. In UL, when the drift becomes greater than a threshold (e.g., PeriodicitySyncTh), the UE may request the network to compensate for the drift. The network may then determine the offset and subsequently notify the UE. Both the UE and the network may then apply the sent 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 sent offset.

[0046] As used in some embodiments herein, "drift" may refer to the accumulated time offset between the SPS / CG resources and the XR frame. For example, "add drift" may be used for SPS / CG resource selection, where a later subframe may be selected as a new start subframe of the allocated SPS / CG resources in order to achieve alignment between the arrival time of the XR frame and the start subframe of the SPS / CG resources. Similarly, "remove drift" may also be used for SPS / CG resource selection, where an earlier subframe may be selected as a new start subframe of the allocated SPS / CG resources in order to achieve alignment between the arrival time of the XR frame and the start subframe of the SPS / CG resources.

[0047] Some example embodiments described below may include enhancements to the configuration of SPS and CG resource allocations to align the SPS / CG resource allocation pattern with the drift of the XR service pattern at the RAN. The adaptation may use extensions configured by information elements (IEs) exchanged via RRC configuration messages. In addition, various example embodiments may include enhancements to control messages exchanged between a base station and a UE to dynamically adapt the SPS / CG cycle based on the service pattern and / or UE state. This can be achieved by defining a new control command to shift the next SPS / CG cycle by a certain offset, and may be carried (for example, by a MAC control element (MAC CE) or downlink control information (DCI)). In addition, various embodiments may include a design of a scheme that tracks drift between SPS / CG and XR service classes and decides when to compensate for the drift without signaling. The UE and base station can calculate the drift and when to compensate for the drift, and use the definition of new behavior in the standard to keep the network and UE aligned. As an example, tracking and compensation of drift can be based on multiple pairs of thresholds<PeriodicitySyncCycle,PeriodicitySyncTh> (one per XR Class-SPS configuration) to determine when to compensate for drift (ie, how much and when to compensate). Since a single pair of thresholds may not account for all temporal drifts, new UE behaviors may be defined to implement self-organizing compensation using those thresholds and signaling schemes.

[0048] like Figure 2 As shown, the mismatch between the non-integer periodicity of XR frame generation and the integer SPS / CG period defined by the SPS / CG parameters can cause the loss or delay of XR frames. In particular, let t∈{0, 1, 2, ...} be a sequence number identifying the SPS period, is the integer duration of the SPS period of the k-th SPS configuration (e.g., the Periodicity field of the SPS-Config), is the non-integer periodicity of the frame of the i-th XR class, δ i∈R is the difference between the SPS periodicity and the XR periodicity of the ith XR class, and Δ i (t) is the time drift of the ith XR class. If the traffic is aligned with the SPS configuration, the time drift can be set to zero at the beginning: The number of SPS configurations may be the same as the number of XR classes, with i = k. If the number of SPS / CG configurations is less than the number of XR classes (e.g., due to assigning SPS / CG configurations to multiple XR classes), the assumption that the number of SPS / CG configurations is the same as the number of XR classes (i.e., i = k) may be relaxed by replicating any SPS / CG configurations that have been assigned to multiple XR classes. A 2 subframe shift may be added to the fourth SPS resource, which may then be aligned with the start of the P frame.

[0049] When the XR service changes from the jth class to the ith class (for example, when the frame rate changes from j=30fps to i=60fps), some example embodiments may use t ji ∈{0, 1, 2, 3, ...} to represent the SPS period. If the configured resources are aligned with the first packet at the beginning, the time drift of the i-th XR class can be changed according to:

[0050]

[0051] in

[0052]

[0053] If both entities know the XR class and the SPS / CG configuration, the formulas for calculating the drift in equations (1) and (2) can be used for UL and DL. In the case of one SPS / CG configuration for one XR class (i.e., i=k), this may not be important because the active SPS / CG configuration may also indicate the XR class, and the difference between the XR and SPS / CG periods (i.e., δ_ii) in equation (2) may 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 periodicity and the SPS / CG period (i.e., δ_ki) in equation (2) may be provided during configuration. In various example embodiments, the network (for DL) or the UE (for UL) may estimate the amount of drift and indicate the amount of drift to the other entity.

[0054] To compensate for time drift, the UE may be informed of periodic mismatches and when to predict or postpone the start of the next SPS / CG period (or equivalently, the end of the current SPS / CG period). For example, the following SPS / CG parameters may be specified for each SPS / CG configuration in the SPS-Config IE (index "i" indicating the i-th SPS / CG configuration and the i-th XR class):

[0055] PeriodicityDrift(|δ i |): Drift parameter obtained as the absolute value defined in equation (2).

[0056] PeriodicityDriftSign(sign(δ i )): Sign indicating the drift (e.g., one bit).

[0057] PeriodicitySyncCycle(P i C ): Indicates the number of SPS / CG cycles before compensating for drift in the next SPS / CG cycle (e.g., anticipating or postponing the start of the next SPS / CG cycle). This threshold can be used by the network and UE as a default realignment period.

[0058] PeriodicitySyncTh(P i T ): The threshold of the amount of drift that triggers the realignment procedure. The drift compensation procedure can be initiated by the network by sending a dedicated command; however, for UL transmissions, the realignment procedure can also be initiated by the UE by sending a request for realignment of the CG cycle and service.

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

[0060] The thresholds PeriodicitySyncCycle and PeriodicitySyncTh pair 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 XR is expected to arrive outside the SPS / CG allocation, and / or (iii) the maximum frequency of drift compensation (i.e., how many times drift is compensated during a certain time interval). Factors (i) and (ii) may depend on the XR application, while (iii) may be the choice of the network operator. However, the maximum frequency before the XR frame falls outside the SPS / CG allocation may be limited depending on the drift and tolerance. In some example embodiments, two thresholds may be calculated, where It's drift. is how much drift the SPS / CG allocation can tolerate before XR is expected to arrive outside of the SPS / CG allocation, and is the maximum frequency of drift compensation measured according to the SPS / CG period before the compensation procedure occurs. The thresholds PeriodicitySyncCycle and PeriodicitySyncThbe can be calculated by solving the following linear equation system:

[0061]

[0062]

[0063] This can be done by first fixing Then calculate Come for solution.

[0064] The parameters PeriodicitySyncCycle and PeriodicitySyncThbe can enable the UE and the base station to know when the timing of the SPS / CG mode should be adjusted, and the adjustment can be performed in a predictive manner. In order to provide additional flexibility, new control messages and procedures can be used to (i) initiate adjustment of the SPS / CG mode (i.e., a procedure initiated by the network), (ii) request adjustment of the SPS / CG mode (i.e., a request triggered by the UE and a replacement of (i)), and (iii) apply the adjustment in a specific period (i.e., a command sent by the base station). The signaling can be implemented as new L1 and / or L2 control messages.

[0065] In various example embodiments discussed herein, after configuring DL allocations for SPS, the MAC entity may sequentially consider the Nth downlink DL to occur in a time slot for which: (numberOfSlotsPerFrame×SFN+number of time 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 timeThe SFN and timeslot of the first PDSCH transmission when the configured DL allocation is initialized or reinitialized, respectively. start time and offset periodicity It may be the offset to be applied to the time slot and time period respectively, communicated by the network with the realignment message.

[0066] After configuring UL grant for CG type 1, the MAC entity may sequentially consider the Nth (N>=0)th UL grant to appear in the following symbols: [(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+[(time slot number in frame offset start time )×numberOfSymbolsPerSlot]+offset-symbol start time ]=(timeReferenceSFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+timeDomainOffset×numberOfSymbolsPerSlot+S+N×(periodicity+offset periodicity )) modulo (1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot). After configuring UL grant for CG type 2, the MAC entity may sequentially consider that the Nth (N>=0) UL grant appears in the following symbols:

[0067] [(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(number of slots in a frame×numberOfSymbolsPerSlot)+number of symbols in a 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 The offset may correspond to the SFN, time slot and symbol of the first transmission opportunity of the physical uplink shared channel (PUSCH), respectively, in which the configured UL grant is initialized or reinitialized. start time in,offset-symbol start time and offset periodicity May correspond to offsets respectively to be applied to the time slots, symbols and periods transmitted by the network with the realignment message.

[0068] Figure 6 An example of a signaling diagram depicting an enhanced SPS configuration for DL ​​traffic transmission is shown. According to some example embodiments, UE 620 and network entity (NE) 630 may be similar to UE 1320 and NE 1310, such as Fig.13 The realignment may be achieved by control commands or performed directly by the NE 630 and UE 620 using new parameters communicated during initial configuration.

[0069] In example embodiments, these parameters may be set to: PeriodicitySyncCycle=4 (P=4), PeriodicityDrift=0.1 (|δ|=0.25), and PeriodicityDriftSign=-1 (sign(δ)=-1). These parameters may by default force the start slot to increase by 1 every four SPS / CG cycles.

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

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

[0072] At 605, when the accumulated time drift exceeds a certain threshold (e.g., PeriodicitySyncCycleTh), the NE 630 can notify the UE 620 to apply realignment, transmitting at least which SPS period will be resynchronized and / or the offset to be applied to the starting time slot or subframe (SF). As an example, Figure 6 It is depicted as occurring during the third SPS period and the sixth SPS period.

[0073] At 606, the UE 620 can add or remove drift to the SPS starting SF and time slot.

[0074] At 607 to 609, the NE 630 can send DL traffic to the UE 620 according to the currently specified SPS operation (i.e., perform transmission in the authorized DLSPS resource).

[0075] At 610, when the accumulated time drift exceeds a certain threshold (e.g., PeriodicitySyncCycleTh), the NE 630 can notify the UE 620 to apply realignment, transmitting at least which SPS period will be resynchronized and / or the offset to be applied to the starting time slot or SF.

[0076] In various example embodiments, the realignment can be achieved through a control command, or directly performed by the NE 630 and the UE 620 using new parameters transmitted during the initial configuration.

[0077] Figure 7 An example of a signaling diagram depicting an enhanced CG configuration for UL transmission is illustrated. According to certain example embodiments, as Fig.13 shown, the UE 720 and the NE 730 can be similar to the UE 1320 and the NE 1310. The realignment can be requested by the UE 720 and achieved through a control command sent by the NE 730, or directly performed by the UE 720 and the NE 730 using new parameters transmitted during the initial configuration.

[0078] In multiple example embodiments, these parameters can be set to: PeriodicitySyncCycle = 4 (P = 4), PeriodicityDrift = 0.1 (|δi| = 0.25), and PeriodicityDriftSign = -1 (sign(δ) = -1). These parameters can default to forcing the starting time slot to be incremented by 1 every four SPS / CG periods.

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

[0080] At 702, UE 720 may send UL traffic to NE 730 according to the currently specified CG operation (ie, perform transmission in the authorized UL CG resources).

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

[0082] At 704, UE 720 may send UL traffic to NE 730 according to the currently specified CG operation (ie, perform transmission in the authorized UL CG resources).

[0083] At 705, the NE 730 may determine the realignment amount (eg, offset) and the CG period to be realigned and transmit this information to the UE 720 (message 2).

[0084] At 706, UE 720 may send UL traffic to NE 730 according to the currently specified CG operation (ie, perform transmission in the authorized UL CG resources).

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

[0086] At 708 to 710, the UE 720 may send UL traffic to the NE 730 according to the currently specified CG operation (ie, perform transmission in the authorized UL CG resources).

[0087] At 711 , NE 730 may determine the realignment amount (eg, offset) and the CG period to be realigned and transmit this information to UE 720 .

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

[0089] In various example embodiments, for the realignment decision for CG cycle 7, the decision regarding compensation may be made autonomously by the NE 730, which is signaled in CG cycle 6. After a number of cycles from the previous realignment request PeriodicitySyncCycle (in Figure 4 In the example, the CG period is after CG period 3, and therefore in CG period 7), the decision may be made by NE 730. NE 730 may decide based on other criteria; for example, if UE 720 sends a buffer status report (BSR) to send traffic before the CG is allocated.

[0090] Figure 8 The diagram illustrates a method that can be performed by, for example, Fig.13 An example of a flowchart of a method performed by the UE 1320 shown in FIG. 1320. In particular, Figure 8 describes the realignment procedure implemented by the UE, where P C (PeriodicitySyncCycle) is the realignment parameter used by the UE and the network by default to implement realignment. T (PeriodicitySyncCycleTh) is a realignment parameter used by the UE to trigger a realignment request. In this example, MACCE is taken as an example of carrying a realignment command.

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

[0092] At 804, the method may include detecting the start of a new SPS period i. At 805, the method may include updating the class Δ i (t) = Δ j (t-1)+δ i Drift.

[0093] At 806, the method may include determining whether a MAC CE realignment has been received. If so, at 807, the method may include performing a realignment by changing the starting time slot and / or SF; for example (if sign (δ i )>0), the starting time slot can be reduced (offset removed), and (if sign(δ i )<0) the starting time slot may be increased (increase offset). At 808, the increment counter t may be increased by 1. After receiving the alignment indication, the realignment may be applied to the SPS / CG resources immediately after receiving the indication.

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

[0095] The UE and gNB may continue to update the time drift Δ at each SPS / CG iteration of the i-th XR class i (t). Upon receiving a realignment command and / or after a certain number of iterations (parameter PeriodicitySyncCycle), the UE may increase or decrease the current SPS / CG period by an offset. The offset may depend on the time drift Δ i (t), and can be calculated as offset = Δ i (t) = t i ×δ, where t i The time when the i-th SPS configuration of the i-th XR class is triggered is measured. The time t i can be calculated as the difference between the absolute SPS iteration and the iteration when the service is switched from class j to class i: t i =tt ji Another way to calculate the offset is by measuring the difference between the actual XR frame arrival and the start slot / subframe of the dedicated SPS / CG configuration. In another embodiment, the offset can be communicated through the network. If the drift becomes larger than a certain threshold P i T (PeriodicitySyncTh), the UE may initiate a realignment procedure by sending a realignment request to the network.

[0096] In some example embodiments, once the necessary parameters are configured, such as the periodicity of XR services and SPS / CG resources, PeriodicitySyncCycle, the UE can be configured to perform the realignment procedure after a number of SPS / CG cycles equal to PeriodicitySyncCycle since the last realignment. If no realignment command is received, such behavior can be set as a fallback behavior.

[0097] Fig. 9 The diagram illustrates a method that can be performed by, for example, Fig.13 The example of a flowchart of a method performed by a UE 1320 shown in FIG. 1320. The realignment may be achieved by a control command, or by a UE or NE (such as Fig.13 The NE 1310 shown executes directly using the new parameters transmitted during initial configuration.

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

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

[0100] At 902 to 904, the method may include receiving DL traffic from the NE according to the currently specified SPS operation (ie, performing transmission in the authorized DL SPS resources).

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

[0102] At 906, the method can include adding or removing drift to the SPS starting SF and time slot.

[0103] At 907 to 909, the method may include receiving DL traffic from the NE according to the currently specified SPS operation (ie, performing transmission in the authorized DL SPS resources).

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

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

[0106] Fig.10 The diagram illustrates a method that can be performed by a NE (such as Fig.13 The realignment may be accomplished by a control command, or by a NE or UE (such as Fig.13 The UE 1320 is shown to execute directly using the new parameters transmitted during the initial configuration.

[0107] In various example 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 1 every four SPS / CG cycles by default.

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

[0109] At 1002 to 1004, the method may include sending DL traffic to the UE according to the currently specified SPS operation (ie, performing transmission in the granted DL SPS resources).

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

[0111] At 1006 to 1008, the method may include sending DL traffic to the UE according to the currently specified SPS operation (ie, performing transmission in the authorized DL SPS resources).

[0112] At 1009, when the accumulated time drift exceeds a certain threshold (eg, 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 a starting time slot or SF.

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

[0114] Fig.11 The diagram illustrates a method that can be performed by, for example, Fig.13 An example of a flow chart of a method performed by a UE is shown as UE 1320. The realignment may be requested by the UE and implemented by a control command sent by the NE, or performed directly by the UE and NE using new parameters communicated during initial configuration.

[0115] In some example 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 1 every four SPS / CG cycles by default.

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

[0117] At 1102, the method may include sending UL traffic to the NE according to a currently specified CG operation (ie, performing transmission in authorized UL CG resources).

[0118] 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).

[0119] At 1104, the method may include sending UL traffic to the NE according to the currently specified CG operation (ie, performing transmission in the authorized UL CG resources).

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

[0121] At 1106, the method may include sending the UL traffic to the NE according to the currently specified CG operation (ie, performing transmission in the authorized UL CG resources).

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

[0123] At 1108 to 1110, the method may include sending UL traffic to the NE according to the currently specified CG operation (ie, performing transmission in authorized UL CG resources).

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

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

[0126] In various example embodiments, for the realignment decision for CG cycle 7, the decision regarding compensation may be made autonomously by the NE, which is signaled in CG cycle 6. This may be done multiple cycles after a previous realignment request PeriodicitySyncCycle (in Figure 4 In the example, the CG period is after CG period 3, hence in CG period 7) the decision is made by the NE. The NE may decide based on other criteria; for example, if the UE sends a buffer status report (BSR) to send traffic before the CG is allocated.

[0127] Fig.12 The diagram illustrates a method that can be performed by, for example, Fig.13 An example of a flow chart of a method performed by a NE of the illustrated NE 1310. The realignment may be requested by the UE and achieved by a control command sent by the NE, or performed directly by the UE and NE using new parameters communicated during initial configuration.

[0128] In certain example embodiments, these parameters may be set to PeriodicitySyncCycle=4 (P=4), PeriodicityDrift=0.1 (|δ|=0.25), and PeriodicityDriftSign=-1 (sign(δ)=-1). These parameters may default to forcing the start slot to increase by 1 every four SPS / CG cycles.

[0129] At 1201 , the method may include sending a configuration with one or more of the parameters PeriodicityDrift, PeriodicityDriftSign and / or PeriodicitySyncCycle, PeriodicitySyncCycleTh to the UE, as discussed above.

[0130] At 1202, the method may include sending UL traffic to the NE according to a currently specified CG operation (ie, performing transmission in authorized UL CG resources).

[0131] 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).

[0132] At 1204, the method may include sending UL traffic to the NE according to the currently specified CG operation (ie, performing transmission in the authorized UL CG resources).

[0133] At 1205, the method may include sending an indication of a determination of the amount of realignment (e.g., offset) and the CG period to be realigned (message 2).

[0134] At 1206, the method may include sending UL traffic to the NE according to the currently specified CG operation (ie, performing transmission in the authorized UL CG resources).

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

[0136] At 1208 to 1210, the method may include sending UL traffic to the NE according to the currently specified CG operation (ie, performing transmission in the authorized UL CG resources).

[0137] At 1211, the method may include sending an indication of a determination of the amount of realignment (e.g., offset) and the CG period to be realigned (Message 2).

[0138] In various example embodiments, for the realignment decision for CG cycle 7, the decision regarding compensation may be made autonomously by the NE, which is signaled in CG cycle 6. This may be done multiple cycles after a previous realignment request PeriodicitySyncCycle (in Figure 4 In the example, the CG period is after CG period 3, hence in CG period 7) the decision is made by the NE. The NE may decide based on other criteria; for example, if the UE sends a buffer status report (BSR) to send traffic before the CG is allocated.

[0139] Fig.13 An example of a system according to certain example embodiments is illustrated. In an example embodiment, the system may include a plurality of devices, such as NE 1310 and / or UE 1320 .

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

[0141] NE 1310 may also include 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 communicate with each other via at least one F1 interface, at least one X n -C interface and / or communicate via at least one NG interface of 5GC.

[0142] UE 1320 may include one or more mobile devices, such as mobile phones, smart phones, personal digital assistants (PDAs), tablets or portable media players, digital cameras, pocket cameras, video game consoles, navigation units, such as global positioning system (GPS) devices, desktop or laptop computers, single-location devices, such as sensors or smart meters, or any combination thereof. In addition, NE 1310 and / or UE 1320 may be one or more devices in a Citizen Broadband Wireless Service Device (CBSD).

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

[0144] At least one memory may be provided in one or more devices, as indicated by 1312 and 1322. The memory may be fixed or removable. The memory may include computer program instructions or computer codes contained therein. The memories 1312 and 1322 may be independently any suitable storage device, such as a non-transitory computer readable medium. The term "non-transitory" as used herein may correspond to a restriction on the medium itself (i.e., tangible, rather than a signal), rather than a restriction on data storage persistence (e.g., RAM versus 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 a processor, or may be separated from one or more processors. In addition, the computer program instructions stored in the memory and that may be 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.

[0145] Processors 1311 and 1321, memories 1312 and 1322, and any subset thereof may be configured to provide Figures 1 to 12 Although not shown, the device may also include positioning hardware, such as GPS or micro-electromechanical system (MEMS) hardware, which may be used to determine the location of the device. Other sensors are also permitted and may be configured to determine location, altitude, speed, orientation, etc., such as a barometer, compass, etc.

[0146] like Fig.13 As shown, transceivers 1313 and 1323 may be provided, and one or more devices may also include at least one antenna, shown as 1314 and 1324, respectively. The device may have many antennas, such as an antenna array configured for multiple-input multiple-output (MIMO) communication, or multiple antennas for multiple RATs. For example, other configurations of these devices may be provided. Transceivers 1313 and 1323 may be transmitters, receivers, both transmitters and receivers, or units or devices that may be configured for both sending and receiving.

[0147] The memory and computer program instructions may be configured with a processor for a specific device to cause a hardware device such as a UE to perform any of the above processes (ie, Figures 1 to 12 ). Thus, 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.

[0148] In certain example embodiments, an apparatus may include a Figures 1 to 12 As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) hardware circuit implementations only (such as implementations in analog and / or digital circuitry only), (b) a combination of hardware circuitry and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuit(s) and software / firmware, and (ii) any portion of a hardware processor(s) together with software (including digital signal processor(s)), software and memory(s) working together to cause a device (such as a mobile phone or server) to perform various functions, and (c) hardware circuit(s) and / or processor(s) (such as 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 the software is not required for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As another example, as used in this application, the term circuitry also encompasses implementations of only a hardware circuit or processor (or multiple processors) or portions of a hardware circuit or processor and its (or its) accompanying software and / or firmware. The term circuitry also encompasses (for example and if applicable to a particular claim element) a baseband integrated circuit 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.

[0149] Fig.14 An example of a 5G network and system architecture according to certain example embodiments is illustrated. Shown are multiple network functions that may be implemented as software operating as a component 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. Fig.14 The NE and UE shown 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 use of traffic routing and interact with the policy framework.

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

[0151] In some example embodiments, an apparatus (e.g., NE 1310 and / or UE 1320) may include components for performing the methods, processes, or any variants discussed herein. Examples of the equipment may include one or more processors, memories, controllers, transmitters, receivers, and / or computer program codes for causing the execution of operations.

[0152] In various example embodiments, device 1320 can be controlled by memory 1322 and processor 1321 to receive at least one adaptive semi-persistent scheduling configuration or configured authorization configuration from a network entity; receive an indication from the network entity that triggers a semi-persistent scheduling or configured authorization alignment associated with the adaptive configuration; and in response to the indication and according to the adaptive configuration, add or remove drift to the semi-persistent scheduling or configured authorization start subframe and time slot.

[0153] Certain example embodiments may be directed to an apparatus comprising components for performing any of the methods described herein, the apparatus comprising, for example, components for receiving at least one adaptive semi-persistent scheduling configuration or configured grant configuration from a network entity; components for receiving an indication from the network entity to trigger a semi-persistent scheduling or configured grant alignment associated with the adaptive configuration; and components for adding or removing drift to the semi-persistent scheduling or configured grant start subframes and time slots in response to the indication and in accordance with the adaptive configuration.

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

[0155] Certain example embodiments may relate to an apparatus comprising components for performing any of the methods described herein, the apparatus comprising, for example, components for configuring a user equipment with at least one adaptive semi-persistent scheduling configuration or a configured authorization configuration; and components for sending an indication to the user equipment for triggering a semi-persistent scheduling or configured authorization alignment associated with an adaptive configuration of the user equipment.

[0156] The features, structures, or characteristics of the example embodiments described throughout this specification may be combined in one or more example embodiments in any suitable manner. For example, the use 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 conjunction with the example embodiments may be included in at least one example embodiment. Thus, the appearance of the phrases "in various embodiments," "certain embodiments," "in some embodiments," or other similar language throughout this specification does not necessarily all refer to the same set of example embodiments, and the described features, structures, or characteristics may be combined in one or more example embodiments in any suitable manner.

[0157] As used herein, “at least one of: ” and “at least one of ” and similar expressions, where a list of two or more elements is connected by “and” or “or”, mean at least any one element, or at least any two or more elements, or at least all elements.

[0158] In addition, if necessary, the above-mentioned different functions or procedures can be performed in different orders and / or simultaneously with each other. In addition, if necessary, one or more described functions or procedures can be optional or can be combined. Therefore, the above description should be considered as an explanation of the principles and teachings of some example embodiments, rather than a limitation thereof.

[0159] Those skilled in the art will readily appreciate that the exemplary embodiments described above may be practiced with procedures in a different order and / or with hardware elements in a configuration different from that disclosed. Therefore, although some 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.

[0160] Partial Glossary

[0161] 3GPP Third Generation Partnership Project

[0162] 5G fifth generation

[0163] 5GC fifth generation core

[0164] 5GS fifth generation system

[0165] 6G Sixth Generation

[0166] AR Augmented Reality

[0167] ASIC Application-Specific Integrated Circuit

[0168] BS Base Station

[0169] CBSD Citizens Broadband Wireless Service Device

[0170] CG Configured Authorization

[0171] CN Core Network

[0172] CPU Central Processing Unit

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

[0174] DCI Downlink Control Information

[0175] DL Downlink

[0176] E2E End to End

[0177] eMBB Enhanced Mobile Broadband

[0178] eMTC Enhanced Machine Type Communication

[0179] eNB Evolved Node B

[0180] EPS Evolved Packet System

[0181] gNBNext Generation Node B

[0182] GPS Global Positioning System

[0183] HARQ Hybrid Automatic Repeat Request

[0184] HDD Hard Drive

[0185] IE Information Component

[0186] IIoT Industrial Internet of Things

[0187] KPI Key Performance Indicator

[0188] LTE Long Term Evolution

[0189] LTE-A Long Term Evolution Advanced

[0190] MAC Media Access Control

[0191] MIMO Multiple Input Multiple Output

[0192] mMTC Host Type Communication

[0193] MR Hybrid Reliability

[0194] MTC Machine Type Communication

[0195] NAS Non-Access Stratum

[0196] NE Network Entity

[0197] NG Next Generation

[0198] NG-eNB Next Generation Evolved Node B

[0199] NG-RAN Next Generation Radio Access Network

[0200] NR New Radio

[0201] PDA Personal Digital Assistant

[0202] PDB Packet Delay Budget

[0203] PDCCH Physical Downlink Control Channel

[0204] PDU Protocol Data Unit

[0205] PUSCH Physical Uplink Shared Channel

[0206] QoS Quality of Service

[0207] RAM Random Access Memory

[0208] RAN Radio Access Network

[0209] RAT Radio Access Technology

[0210] RE Resource Component

[0211] RRC Radio Resource Control

[0212] RS reference signal

[0213] SCS Subcarrier Spacing

[0214] SDU Service Data Unit

[0215] SF subframe

[0216] SFN System Frame Number

[0217] SMF session management functions

[0218] SN Serial Number

[0219] SPS Semi-Persistent Scheduling

[0220] SRB Signalling Radio Bearer

[0221] TB Transfer Block

[0222] TSC Time Sensitive Communications

[0223] TX

[0224] UE User Equipment

[0225] UL Uplink

[0226] UMTS Universal Mobile Telecommunications System

[0227] UPF User Plane Function

[0228] URLLC Ultra-Reliable Low Latency Communications

[0229] UTRAN Universal Mobile Telecommunications System Terrestrial Radio Access Network

[0230] VR Virtual Reality

[0231] WLAN Wireless Local Area Network

[0232] XR

Claims

1. A device, include: means for receiving at least one adaptive semi-persistent scheduling configuration or a configured grant configuration from a network entity; means for receiving an indication from the network entity to trigger 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; as well as Means for adding or removing a drift to a semi-persistent scheduling starting subframe and time slot, or a configured grant starting subframe and time slot, in response to the indication and according to the adaptive configuration.

2. The apparatus according to claim 1, wherein at least one of the received adaptive configurations include: An indication of the sign of the drift.

3. The apparatus according to any one of claims 1 or 2, wherein at least one of the received adaptive configurations include: An indication of the absolute value of the drift.

4. The apparatus according to any one of claims 1 to 3, wherein at least one of the received adaptive configurations include: An indication of a number of semi-persistent scheduling or configured grant periods before compensating for said drift in the next semi-persistent scheduling or configured grant period.

5. The apparatus according to any one of claims 1 to 4, wherein at least one of the received adaptive configurations include: An indication of a threshold amount of drift for triggering a realignment procedure.

6. The device according to any one of claims 1 to 5, further comprising: include: Means for sending a request for realignment of the adaptation configuration to a network entity.

7. The device according to any one of claims 1 to 6, further comprising: include: Means for determining that said drift is greater than said configured threshold.

8. The device according to any one of claims 1 to 7, further comprising: include: A component used to determine whether a modulo operation is equal to zero.

9. The device according to any one of claims 1 to 8, further comprising: include: Means for performing realignment by adjusting said starting subframe and time slot, wherein a drift is added if said sign of said drift is less than zero, and a drift is removed if said sign of said drift is greater than zero.

10. A device, include: means for configuring a user equipment with at least one adaptive semi-persistent scheduling configuration or a configured authorization configuration; as well as Means for sending an indication for triggering semi-persistent scheduling or configured grant alignment in response to configuring the user equipment, 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 according to claim 10, wherein at least one of the received adaptive configurations include: An indication of the sign of the drift.

12. The apparatus according to any one of claims 10 or 11, wherein at least one of the received adaptive configurations include: An indication of the absolute value of the drift.

13. The apparatus according to any one of claims 10 to 12, wherein at least one of the received adaptive configurations include: An indication of a number of semi-persistent scheduling or configured grant periods before compensating for the drift in the next semi-persistent scheduling or configured grant period.

14. The apparatus according to any one of claims 10 to 13, wherein at least one of the received adaptive configurations include: An indication of a threshold amount of drift for triggering a realignment procedure.

15. The device according to any one of claims 10 to 14, further comprising: include: Means for receiving a request from the user equipment for realignment of the adaptive configuration.

Images